CN100396051C - Transmission method for conversation data in group broad cast / broadcast service - Google Patents

Transmission method for conversation data in group broad cast / broadcast service Download PDF

Info

Publication number
CN100396051C
CN100396051C CNB2003101140720A CN200310114072A CN100396051C CN 100396051 C CN100396051 C CN 100396051C CN B2003101140720 A CNB2003101140720 A CN B2003101140720A CN 200310114072 A CN200310114072 A CN 200310114072A CN 100396051 C CN100396051 C CN 100396051C
Authority
CN
China
Prior art keywords
session data
session
repeat requests
information
network controller
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
Application number
CNB2003101140720A
Other languages
Chinese (zh)
Other versions
CN1617523A (en
Inventor
张海
张文林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB2003101140720A priority Critical patent/CN100396051C/en
Priority to PCT/CN2004/001277 priority patent/WO2005046261A1/en
Publication of CN1617523A publication Critical patent/CN1617523A/en
Application granted granted Critical
Publication of CN100396051C publication Critical patent/CN100396051C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1868—Measures taken after transmission, e.g. acknowledgments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

The present invention discloses a method for transmitting session data in multicast / broadcast services, which comprises: after a communication terminal detects the existence of unreceived multicast/broadcast service session data, the communication terminal sends a session data retransmission request to a wireless network controller to which the communication terminal belongs; the wireless network controller receives the session data retransmission request, and sends a session data retransmission request carrying session information to a service support center to which the wireless network controller belongs; the service support center receives the session data retransmission request, obtains session data needing to be retransmitted according to the session information, and then, the service support center sends a session data starting message to the wireless network controller ruled by the service support center; the wireless network controller which is ruled by the service support center and sends the data retransmission request receives the session data starting message, returns a session data receiving starting response to the service support center, establishes user plane resources, and retransmits the session data through the user plane resources. The present invention can purposefully retransmit session data, and realize the reasonable use of wireless networks and core network resources.

Description

The transmission method of session data in a kind of multicast/broadcast business
Technical field
The present invention relates to data transmission technology, be meant a kind of transmission method that is applied to session data in the multicast/broadcast business especially.
Background technology
Development along with the 3G (Third Generation) Moblie technology, the comparable second generation mobile communication of 3G (Third Generation) Moblie provides message transmission rate higher service, thereby make 3G (Third Generation) Moblie support multiple business form, for example visual telephone, picture download, high speed view Internet (Internet) etc.3G (Third Generation) Moblie supports a kind of user who has subscribed to some customizing messages in wireless network to send the form of service of this information simultaneously, and these information can be weather forecast, news film, the sports tournament collection of choice specimens etc.According to the characteristics that above-mentioned business sends simultaneously, 3G (Third Generation) Moblie has been introduced the definition of multicast/broadcast business.
In the data transmission procedure of unicast service, node in each branch, the capital then according to the end user's quantity that belongs to downstream node, sends the data of corresponding umber according to the quantity copy data that belongs to all end users of this node to this downstream node, like this, can take too much transfer resource, root node especially is in whole data transmission procedure, each end user who belongs to this root node is taking transfer resource all the time, as shown in Figure 1.
Yet, the multicast/broadcast business is on the transmission means of data, be with the essential distinction of unicast service: the multicast/broadcast business is being transferred to data the process of destination node from source node, what carry out all is that transmit in single footpath, that is: for an intermediate node, no matter its downstream comprises the node what expectations receive data, and its upstream node always sends a piece of data to this intermediate node; After this intermediate node is received data, the number of nodes that receives data according to its downstream expectation duplicates this data, and distribute this data to the node that each expectation of its downstream receives these data, like this, each bar branch of multicast/broadcast business data transmission tree all has only a piece of data to transmit, take a transfer resource, the transfer of data of root node and its downstream node also is so, as shown in Figure 2.The distinctive points of multicast service and broadcasting service only is: multicast service only sends corresponding information to the user who has subscribed to some information, and the broadcasting service then user of all in wireless network sends information.As seen from the above description, provide identical information to a large number of users simultaneously, can greatly save Internet resources by multicast/broadcast is professional.
Fig. 3 is for supporting the wireless network architecture schematic diagram of multicast/broadcast business, as shown in Figure 3, the wireless network architecture of supporting the multicast/broadcast business in the existing third generation partner program (3GPP) is that broadcast/multicast service center (BM-SC) 301 is by Gmb interface or Gi interface and gateway general packet radio service (GPRS) support node (GGSN, Gateway GPRS Support Node) 302 link to each other, and a BM-SC 301 can link to each other with a plurality of GGSN 302; GGSN 302 links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node) 303, and a GGSN 302 can link to each other with a plurality of SGSN 303; SGSN 303 can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) 304 by the Iu interface, UTRAN 304 links to each other with communication terminal 306 by the Uu interface then, SGSN 303 also can strengthen wireless access network (GERAN) 305 by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN 305 links to each other with communication terminal 306 by Um Interface then.
Wireless network repeatedly retransmits same session data usually, to guarantee that communication terminal can receive the multicast/broadcast session data that wireless network issues accurately and reliably.BM-SC can resend this session data after the regular hour after sending a session data.For other downstream nodes in the wireless network, as GGSN, SGSN, Radio Access Network (RAN, Radio Access Network) radio network controller (RNC in, Radio Network Controller) etc., the session data that resends is transmitted, the session data that resends and common multicast/cast service data are as broad as long, need set up corresponding multicast/multicast service carrying equally, then this session data be sent in the multicast group or all communication terminals in the wireless network.
But, session data is simply retransmitted, can't guarantee that communication terminal receives corresponding session data, yet session data is repeatedly retransmitted, will certainly cause waste of network resources, the professional advantage of saving Internet resources of multicast/broadcast is weakened greatly, and improved the cost of investment of multicast/broadcast business.And in whole wireless network, each regional network condition is also inconsistent, and the network performance of some wireless coverage areas is better, is positioned at these regional communication terminals and can correctly receives session data; The network performance of some wireless coverage areas is relatively poor, is positioned at these regional communication terminals and can't correctly receives session data.At present, there is not selectivity to retransmit the mechanism of session data, wireless zone or the communication terminal at needs re-transmission session data do not carry out when retransmitting session data, but in whole multicast group or whole wireless network, carry out, the re-transmission of session data has comprised not to be needed to carry out the zone that session data retransmits, and has wasted Internet resources.
Summary of the invention
In view of this, the object of the present invention is to provide the transmission method of session data in a kind of multicast/broadcast business, make the transmission of multicast/broadcast service conversation data more reliable, and can effectively save Internet resources.
In order to achieve the above object, the invention provides the transmission method of session data in a kind of multicast/broadcast business, communication terminal has detected unreceived multicast/broadcast service conversation data, and the method includes the steps of:
A, communication terminal send the session data repeat requests that carries session information to affiliated radio network controller;
B, radio network controller receive described session data repeat requests, send the session data repeat requests that carries session information to affiliated service support center;
C, service support center receive described session data repeat requests, obtain the session data that needs retransmit according to session information, and the radio network controller transmission session data to administration begins message then;
The transmission of D, described service support center administration the radio network controller of session data repeat requests receive described session data and begin message, return session data to this service support center and begin acceptance response, set up user-plane resources;
E, service support center are by described user-plane resources, the radio network controller that session data begins acceptance response that returned to administration retransmits session data, after radio network controller is received data retransmission, retransmit the session data of receiving to the communication terminal of administering.
Radio network controller described in the step B receives after the described session data repeat requests, further comprise: if the session data repeat requests of receiving is first session data repeat requests at this session data, radio network controller returns session data re-transmission response to the communication terminal of administration.
Further may further comprise the steps before the described steps A: A01, communication terminal generate random delay, and start the timing of random delay timer; A02, communication terminal judge whether to receive that the session data that radio network controller returns retransmits response in the time range of random delay timing, if, stop the timing of random delay timer, otherwise, execution in step A.
Carry out after the described steps A, further comprise: return execution in step A01.
Radio network controller described in the step B receives after the described session data repeat requests, further comprise: if the session data repeat requests of receiving is first session data repeat requests at this session data, radio network controller store session information.Described in the step B to affiliated service support center send carry the session data repeat requests of session information before, further comprise: radio network controller is according to the session information of storage, judge that whether the session data repeat requests receive is the initial session data repeat requests at this session data, if send the session data repeat requests that carries session information to affiliated service support center; Otherwise, do not operate.Session data described in the step C begins to carry in the message session information, sending session data to the radio network controller of administration described in the step C begins message and is: the service support center according to described session data under the radio network controller tabulation of multicast/broadcast business, radio network controller transmission session data to administration begins message, further comprise after the described step C: the radio network controller of service support center administration receives session data and begins message, judge whether to store described session information, if, return the session data that carries user-plane resources information to this service support center and begin acceptance response, set up user-plane resources, otherwise, return session data to described service support center and begin the refusal response.
Described step B further comprises: radio network controller recording communication terminal place cell information.
Described step C further comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, the radio network controller of mind-set administration returns session data and retransmits response in the service support.
Before affiliated service support center transmission carries the session data repeat requests of session information, further may further comprise the steps described in the step B: B1, radio network controller generate random delay, and start the timing of random delay timer; Whether B2, radio network controller receive in the time range of random delay timing that the session data that returns at the service support center retransmits response, if, stop the timing of random delay timer, otherwise, send the session data repeat requests that carries session information to affiliated service support center.Carry out after the described step B, further comprise: return execution in step B1.
Described step C comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, the service support center receives described session data repeat requests, storage sends the radio network controller information of session data repeat requests, obtain the session data that needs retransmit according to session information, according to the radio network controller information of storage, send session data to radio network controller and begin message then corresponding to described radio network controller information.
The repeat requests of session data described in the steps A further carries communication terminal information, radio network controller described in the step B receives after the described session data repeat requests, further comprise: radio network controller storing communication end message, the session data of receiving to the communication terminal re-transmission of administration described in the step e comprises: radio network controller retransmits the session data of receiving according to the communication terminal information of storage to the communication terminal corresponding to described communication terminal information of administering.
Obtaining the session data that needs retransmit according to session information described in the step C comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, the service support center is according to session information, request content provides server that session data corresponding to session information is provided, and content providing server provides described session data to this service support center.The center of service support described in the step C receives after the described session data repeat requests, further comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, and service support central store session information.The center of service support described in the step C receives after the described session data repeat requests, further comprise: the service support center is according to the session information of storage, judge that whether the session data repeat requests receive is the initial session data repeat requests at this session data, if, request content provides server that session data corresponding to session information is provided, otherwise, do not operate.
Session data described in the step D begins acceptance response and carries radio network controller information,
Further comprise after the described step D: service support central store radio network controller information,
User-plane resources is passed through at the center of service support described in the step e, the radio network controller that session data begins acceptance response that returned to administration retransmits session data, comprise: the service support center is according to the radio network controller information of storage, by user-plane resources, retransmit session data to described radio network controller.
Communication terminal is by random access procedure, or shared channel sends described session data repeat requests to radio network controller.
Communication terminal detects by sliding window mechanism whether unreceived session data is arranged.
The scheme that proposes according to the present invention, communication terminal is when having detected unreceived session data, send the session data repeat requests to network side, when network side retransmits session data, only receive the downstream node re-transmission session data of this session data to expectation, and can retransmit session data to the communication terminal of expectation reception session data, realized carrying out targetedly the purpose that session data retransmits, rationally using under the prerequisite of wireless network and core-network resources, making communication terminal and downstream node can receive the session data that its expectation receives more reliably.Save the cost of investment of multicast/broadcast business by the present invention, and improved user's satisfaction.In addition, the invention provides multiple implementation, can select neatly, and can not have under the situation of conflict several implementations to be made up, thereby realize the most desirable implementation that session data retransmits in the specific implementation process according to practical situations.
Description of drawings
Fig. 1 is a unicast service transmission course schematic diagram;
Fig. 2 is the professional transmission course schematic diagram of multicast/broadcast;
Fig. 3 is for supporting the wireless network architecture schematic diagram of multicast/broadcast business;
Fig. 4 is session data retransmission processes schematic diagram among the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.
Among the present invention, after communication terminal had detected unreceived session data, the RNC under it sent the session data repeat requests, and after RNC received the session data repeat requests, the service support center under it sent the session data repeat requests; After the session data repeat requests is received at the service support center, obtain the session data that needs re-transmission, send session data to the RNC of its administration then and begin message, the transmission of service support center administration the RNC of session data repeat requests return session data to the service support center and begin acceptance response, set up user-plane resources; The service support center obtains the session data that need to retransmit, by the user-plane resources set up to returning of its administration the session data RNC that begins acceptance response retransmit session data, RNC retransmits session data to communication terminal.The above service support center comprises SGSN, GGSN and BM-SC.
Fig. 4 is session data retransmission processes schematic diagram among the present invention, and as shown in Figure 4, the session data retransmission processes roughly may further comprise the steps:
Step 401～step 405: communication terminal has detected unreceived session data, and the RNC under it sends the session data repeat requests, and the request network side resends unreceived session data to it; After RNC received the session data repeat requests, the SGSN under it sent the session data repeat requests; After SGSN received the session data repeat requests, the GGSN under it sent the session data repeat requests; After GGSN received the session data repeat requests, the BM-SC under it sent the session data repeat requests.Above step is that reverse transfer repeat requests, foundation retransmit the tree process.
After step 406～step 409:BM-SC receives the session data repeat requests, obtain the session data that needs re-transmission, and in the time can sending this session data, initiate multi-medium broadcast/group broadcast service (MBMS, Multimedia Broadcast/Multicast Service) session begins process, send session data to the GGSN of its administration then and begin message, the transmission of this BM-SC administration after the GGSN of session data repeat requests receives that session data begins message, BM-SC under it returns session data and begins acceptance response, sets up user-plane resources; Having returned GGSN that session data begins acceptance response sends session data to the SGSN of its administration and begins message, the transmission of this GGSN administration after the SGSN of session data repeat requests receives that session data begins message, GGSN under it returns session data and begins acceptance response, sets up user-plane resources; Having returned SGSN that session data begins acceptance response sends session data to the RNC of its administration and begins message, the transmission of this SGSN administration after the RNC of session data repeat requests receives that session data begins message, SGSN under it returns session data and begins acceptance response, sets up user-plane resources.Above process is a forward session activation process.
Step 410～step 413:BM-SC retransmits session data by the user-plane resources of setting up to GGSN; After GGSN receives session data, retransmit this session data to SGSN by the user-plane resources of setting up; After SGSN receives session data, retransmit this session data to RNC by the user-plane resources of setting up; After RNC receives session data, retransmit session data to communication terminal.Above process is a forward session data transmission course.
Below specific implementation process of the present invention is described in detail, the implementation procedure that retransmits session data specifically may further comprise the steps:
Steps A 1: communication terminal has detected unreceived session data, for example, network side is given advance notice and can be sent session data to communication terminal, but this communication terminal is not received corresponding session data, or communication terminal detected unreceived session data by sliding window mechanism, needs network side to retransmit this session data.The RNC of communication terminal under it sends the session data repeat requests, carries session information in this session data repeat requests, and session information can comprise service identification and session identification.
After steps A 2:RNC receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this RNC returns session data re-transmission response by multicast/broadcast mode all communication terminals to its compass of competency, the data re-transmission request that accepted session of notifying communication terminal network side, the session information of storage of session data in MBMS business contexts (MBMS Service Context) then, and the information of recording communication terminal affiliated subdistrict, SGSN under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this RNC only carries out record to the information of communication terminal affiliated subdistrict.RNC can be by judging whether to store the session information that carries in the session data repeat requests, judge the session data repeat requests received and whether be first session data repeat requests at this session data, if store the session information that carries in the session data repeat requests, the session data repeat requests of then receiving is first session data repeat requests at this session data; If there is not the session information that carries in the storage of session data repeat requests, the session data repeat requests of then receiving is not first session data repeat requests at this session data.
Communication terminal can generate the random delay of certain hour scope before the RNC under it sends the session data repeat requests; Communication terminal waits for that in the time range of this random delay RNC returns session data and retransmits response then.If communication terminal is received the session data that RNC returns and retransmits response that then no longer the RNC under it sends the session data repeat requests, and stops the timing of random delay in the time range of random delay; If communication terminal is not received the session data that RNC returns and is retransmitted response in the time range of random delay, then the RNC under it sends the session data repeat requests, can directly finish the timing of random delay then, wait for that no longer RNC returns session data and retransmits response; Also can generate random delay once more or use former random delay, and continue in the time range of this random delay to wait for that the session data that RNC returns retransmits response, can so circulate repeatedly starts the random delay timing, as 4 times.Random delay by the communication terminal generation, can make each communication terminal that is positioned at same sub-district send the session data repeat requests to RNC constantly in difference, avoid because of the mass communication terminal sends the session data repeat requests at synchronization to RNC, and the network congestion that causes.
If RNC receives the session data repeat requests of other communication terminals of same sub-district at same session data, may be to receive first session data repeat requests and return session data at RNC to retransmit between the response session data repeat requests that other communication terminals of this sub-district send to all communication terminals in this sub-district.After RNC receives first session data repeat requests, if when receiving the session data repeat requests at this session data again, then just cell information is carried out record, so that it is when retransmitting session data, can only retransmit the sub-district re-transmission session data of this session data according to the cell information of record to needs, thereby be implemented in the area of wireless network coverage territory, retransmit session data targetedly, and then save Internet resources; And the RNC no longer SGSN under it sends the session data repeat requests, like this, can reduce the signaling traffic in the network, realizes saving the purpose of Internet resources.
After steps A 3:SGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, the session information of this SGSN storage of session data in MBMS bearer context (MBMS Bearer Context) then, GGSN under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this SGSN does not do any operation, promptly this SGSN no longer the GGSN under it send the session data repeat requests, like this, SGSN converges the signaling of session data repeat requests, reduce the signaling traffic in the network, realize saving Internet resources.
After steps A 4:GGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, the session information of this GGSN storage of session data in the MBMS bearer context then, BM-SC under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this GGSN does not do any operation, promptly this GGSN no longer the BM-SC under it send the session data repeat requests, like this, GGSN converges the signaling of session data repeat requests, reduce the signaling traffic in the network, realize saving Internet resources.
After steps A 5:BM-SC receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this BM-SC provides this session data according to the Information Request content providing server; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this BM-SC does not do any operation, promptly this BM-SC no longer request content provide server that this session data is provided, like this, BM-SC converges the signaling of session data repeat requests, reduce the signaling traffic in the network, realize saving Internet resources.
Steps A 6: after content providing server provides the session data that needs to retransmit to the BM-SC of queued session data, this BM-SC is in the time can sending this session data, initiate the MBMS session and begin process, downstream node tabulation according to multicast/broadcast business under this session data, send session data to the GGSN of its administration and begin message, this session data begins not only to carry session information in the message, also carries service quality (QoS) parameter, multicast/broadcast business domains information etc.
After steps A 7:GGSN receives that the session data that carries session information begins message, judge and whether store this session information in the MBMS bearer context, if store this session information in the MBMS bearer context, then this GGSN re-transmission of data that accepts session, BM-SC under it returns session data and begins acceptance response, set up user-plane resources, this session data begins information and the user-plane resources information that acceptance response carries this GGSN node; After BM-SC receives that session data begins acceptance response, storage GGSN nodal information and user-plane resources information, the GGSN nodal information is the routing iinformation that retransmits session data, user-plane resources information is the resource information that retransmits session data; This GGSN is according to the downstream node tabulation of multicast/broadcast business under this session data then, send session data to the SGSN of its administration and begin message, this session data begins not only to carry session information in the message, also carries qos parameter, multicast/broadcast business domains information etc.If do not store this session information in the MBMS bearer context, the then re-transmission of this GGSN refusal session data, the BM-SC under it returns session data and begins the refusal response.
After steps A 8:SGSN receives that the session data that carries session information begins message, judge and whether store this session information in the MBMS bearer context, if store this session information in the MBMS bearer context, then this SGSN re-transmission of data that accepts session, GGSN under it returns session data and begins acceptance response, set up user-plane resources, this session data begins information and the user-plane resources information that acceptance response carries this SGSN node; After GGSN receives that session data begins acceptance response, storage SGSN nodal information and user-plane resources information, the SGSN nodal information is the routing iinformation that retransmits session data, user-plane resources information is the resource information that retransmits session data; This SGSN is according to the downstream node tabulation of multicast/broadcast business under this session data then, send session data to the RNC of its administration and begin message, this session data begins not only to carry session information in the message, also carries qos parameter, multicast/broadcast business domains information etc.If do not store this session information in the MBMS bearer context, the then re-transmission of this SGSN refusal session data, the GGSN under it returns session data and begins the refusal response.
After steps A 9:RNC receives that the session data that carries session information begins message, judge and whether store this session information in the MBMS business contexts, if store this session information in the MBMS business contexts, then this RNC re-transmission of data that accepts session, SGSN under it returns session data and begins acceptance response, set up user-plane resources, this session data begins acceptance response and carries this RNC information and user-plane resources information; After SGSN received that session data begins acceptance response, storage RNC information and user-plane resources information, RNC information were the routing iinformations that retransmits session data, and user-plane resources information is the resource information that retransmits session data.If do not store this session information in the MBMS business contexts, the then re-transmission of this RNC refusal session data, the SGSN under it returns session data and begins the refusal response.
When steps A 10:BM-SC retransmits session data, no longer tabulate according to the downstream node of multicast/broadcast business under the re-transmission session data, all GGSN to its administration retransmit session data, but according to the GGSN nodal information of storing in the steps A 7, by the user-plane resources of setting up, to returning of its administration the session data corresponding GGSN that retransmits acceptance response retransmit session data.Can adopt error correcting capability coded system stronger, that reliability is higher to encode to the session data that retransmits, described coded system can be the forward error correction coded system or increases the redundancy coded system or deepen interleave depth coded system etc.
After steps A 11:GGSN receives and retransmits session data, no longer tabulate according to the downstream node of multicast/broadcast business under the re-transmission session data, all SGSN to its administration retransmit session data, but according to the SGSN nodal information of storing in the steps A 8, by the user-plane resources of setting up, to returning of its administration the session data corresponding SGSN that retransmits acceptance response retransmit session data.
After steps A 12:SGSN receives and retransmits session data, no longer tabulate according to the downstream node of multicast/broadcast business under the re-transmission session data, all RNC to its administration retransmit session data, but according to the RNC information of storing in the steps A 9, by the user-plane resources of setting up, to returning of its administration the session data corresponding RNC that retransmits acceptance response retransmit session data.
Steps A 13:RNC receives when retransmitting session data, according to the cell information of its record, retransmits session data by the multicast/broadcast mode to the communication terminal that is positioned at respective cell.
Session data described above retransmits in the implementation procedure, only comprise that RNC returns the operation that session data retransmits response to communication terminal, in fact, each upstream node of network side is after receiving first session data repeat requests, all can return session data to downstream node and retransmit response, avoid upstream node to receive the session data repeat requests at same session data of a large amount of downstream nodes to its transmission, reduce the flow of uplink session data re-transmission demand signalling, the specific implementation process is as follows:
Step B1～step B2 is identical with steps A 1～steps A 2.
After step B3:SGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this SGSN returns session data by the multicast/broadcast mode to all RNC of its administration and retransmits response, the notice RNC data re-transmission request that accepted session, and in the MBMS bearer context session information of storage of session data, GGSN under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this SGSN no longer the GGSN under it send the session data repeat requests.
RNC can generate the random delay in the certain hour scope before the SGSN under it sends the session data repeat requests; Communication terminal waits for that in the time range of this random delay the session data that SGSN returns retransmits response then.If RNC receives the session data that SGSN returns and retransmits response that then no longer the SGSN under it sends the session data repeat requests, and stops the timing of random delay in the time range of random delay; If RNC does not receive the session data that SGSN returns and retransmits response in the time range of random delay, then the SGSN under it sends the session data repeat requests, can directly finish the timing of random delay then, wait for that no longer SGSN returns session data and retransmits response; Also can generate random delay once more or use former random delay, and continue in the time range of this random delay to wait for that the session data that SGSN returns retransmits response, can so circulate repeatedly starts the random delay timing, as 4 times.By the random delay that RNC generates, can make each RNC that belongs to same SGSN send the session data repeat requests to SGSN constantly in difference, avoid SGSN to receive the request of high-volume conversation data re-transmission at synchronization, reduce the processing speed of this SGSN; And can avoid because of a large amount of RNC send the session data repeat requests at synchronization to SGSN, and the network congestion that causes.
If SGSN receives the session data repeat requests at same session data, may be to receive first session data repeat requests and return session data at SGSN to retransmit between the response session data repeat requests that other RNC of its administration send to the RNC of its administration.
After step B4:GGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this GGSN returns session data by the multicast/broadcast mode to all SGSN of its administration and retransmits response, the notice SGSN data re-transmission request that accepted session, and in the MBMS bearer context session information of storage of session data, BM-SC under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this GGSN no longer the BM-SC under it send the session data repeat requests.
SGSN can generate the random delay in the certain hour scope before the GGSN under it sends the session data repeat requests; Communication terminal waits for that in the time range of this random delay the session data that GGSN returns retransmits response then.If SGSN receives the session data that GGSN returns and retransmits response that then no longer the GGSN under it sends the session data repeat requests, and stops the timing of random delay in the time range of random delay; If SGSN does not receive the session data that GGSN returns and retransmits response in the time range of random delay, then the GGSN under it sends the session data repeat requests, can directly finish the timing of random delay then, wait for that no longer GGSN returns session data and retransmits response; Also can generate random delay once more or use former random delay, and continue in the time range of this random delay to wait for that the session data that GGSN returns retransmits response, can so circulate repeatedly starts the random delay timing, as 4 times.By the random delay that SGSN generates, can make each SGSN that belongs to same GGSN send the session data repeat requests to GGSN constantly in difference, avoid GGSN to receive the request of high-volume conversation data re-transmission at synchronization, reduce the processing speed of this GGSN; And can avoid because of a large amount of SGSN send the session data repeat requests at synchronization to GGSN, and the network congestion that causes.
If GGSN receives the session data repeat requests at same session data, may be to receive first session data repeat requests and return session data at GGSN to retransmit between the response session data repeat requests that other SGSN of its administration send to the SGSN of its administration.
After step B5:BM-SC receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this BM-SC returns session data by the multicast/broadcast mode to all GGSN of its administration and retransmits response, the notice GGSN data re-transmission request that accepted session, and provide this session data according to the Information Request content providing server; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this BM-SC no longer request content provide server that this session data is provided.
GGSN can generate the random delay in the certain hour scope before the BM-SC under it sends the session data repeat requests; Communication terminal waits for that in the time range of this random delay the session data that BM-SC returns retransmits response then.If GGSN receives the session data that BM-SC returns and retransmits response that then no longer the BM-SC under it sends the session data repeat requests, and stops the timing of random delay in the time range of random delay; If GGSN does not receive the session data that BM-SC returns and retransmits response in the time range of random delay, then the BM-SC under it sends the session data repeat requests, can directly finish the timing of random delay then, wait for that no longer BM-SC returns session data and retransmits response; Also can generate random delay once more or use former random delay, and continue in the time range of this random delay to wait for that the session data that BM-SC returns retransmits response, can so circulate repeatedly starts the random delay timing, as 4 times.By the random delay that GGSN generates, can make each GGSN that belongs to same BM-SC send the session data repeat requests to BM-SC constantly in difference, avoid BM-SC to receive the request of high-volume conversation data re-transmission at synchronization, reduce the processing speed of this BM-SC; And can avoid because of a large amount of GGSN send the session data repeat requests at synchronization to BM-SC, and the network congestion that causes.
If BM-SC receives the session data repeat requests at same session data, may be to receive first session data repeat requests and return session data at BM-SC to retransmit between the response session data repeat requests that other GGSN of its administration send to the GGSN of its administration.
Step B6～step B 13 is identical with steps A 6～steps A 13.
In addition, upstream node in store session information, also can be stored downstream node information after receiving the session data repeat requests that downstream node sends; Upstream node is no longer tabulated according to the downstream node of multicast/broadcast business under the re-transmission session data then, all downstream nodes transmission re-transmission session datas to its administration begin message, begin message but only send session data to the downstream node of having stored nodal information; Receive the downstream node that session data begins message does not need to judge whether this downstream node stores corresponding session information again, and the re-transmission of the data that directly accept session is set up user-plane resources and got final product, and the specific implementation process is as follows:
Step C1～step C2 is identical with steps A 1～steps A 2.
After step C3:SGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this SGSN storage sends the RNC information of session data repeat requests, and in the MBMS bearer context session information of storage of session data, GGSN under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this SGSN only stores the RNC information that sends the session data repeat requests, and no longer the GGSN under it sends the session data repeat requests.
After step C4:GGSN receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this GGSN storage sends the SGSN nodal information of session data repeat requests, and in the MBMS bearer context session information of storage of session data, BM-SC under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this GGSN only stores the SGSN nodal information that sends the session data repeat requests, and no longer the BM-SC under it sends the session data repeat requests.
After step C5:BM-SC receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this BM-SC storage sends the GGSN nodal information of session data repeat requests, and provides this session data according to the Information Request content providing server; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this BM-SC only stores the GGSN nodal information that sends the session data repeat requests, and no longer request content provides server that this session data is provided.
Step C6: after content providing server provides the session data that needs to retransmit to the BM-SC of queued session data, this BM-SC is in the time can sending this session data, initiate the MBMS session and begin process, according to the GGSN nodal information of storage, send session data to corresponding GGSN and begin message then.
After step C7:GGSN receives that session data begins message, the re-transmission of the data that accept session, BM-SC under it returns session data and begins acceptance response, sets up user-plane resources, and this session data begins information and the user-plane resources information that acceptance response carries this GGSN node; After BM-SC receives that session data begins acceptance response, storage GGSN nodal information and user-plane resources information.This GGSN sends session data to corresponding SGSN and begins message according to the SGSN nodal information of storage then.
After step C8:SGSN receives that session data begins message, the re-transmission of the data that accept session, GGSN under it returns session data and begins acceptance response, sets up user-plane resources, and this session data begins information and the user-plane resources information that acceptance response carries this SGSN node; After GGSN receives that session data begins acceptance response, storage SGSN nodal information and user-plane resources information.This SGSN sends session data to corresponding RNC and begins message according to the RNC information of storage then.
After step C9:RNC receives that session data begins message, the re-transmission of the data that accept session, SGSN under it returns session data and begins acceptance response, sets up user-plane resources, and this session data begins information and the user-plane resources information that acceptance response carries this RNC; After SGSN receives that session data begins acceptance response, storage RNC information and user-plane resources information.
Step C10～step C13 is identical with steps A 10～steps A 13.
In addition, more than in the description of each implementation procedure, all the sub-district with the RNC administration is the re-transmission that unit carries out session data, be that RNC retransmits session data to the communication terminal that is positioned at its administration sub-district, the most rationally and the most save for the use that makes Internet resources, can make RNC only retransmit this session data, make session data retransmit the transmission that realizes point-to-point to the communication terminal of needs re-transmission session data, thereby make taking of Internet resources reach minimum, the specific implementation process is as follows:
Step D1: communication terminal has detected unreceived session data, needs network side to retransmit this session data.The RNC of communication terminal under it sends the session data repeat requests, carries communication terminal information and session information in this session data repeat requests.
After step D2:RNC receives the session data repeat requests that carries session information, judge that whether the session data repeat requests receive is first session data repeat requests at this session data, if the session data repeat requests of receiving is first session data repeat requests at this session data, then this RNC returns session data to this communication terminal and retransmits response, notify this communication terminal network side to accept the session data repeat requests of its transmission, storing communication end message then, and in the MBMS business contexts session information of storage of session data, SGSN under it sends the session data repeat requests then, carries session information in this session data repeat requests; If the session data repeat requests of receiving is not first session data repeat requests at this session data, then this RNC carries out record to communication terminal information, and can return session data re-transmission response to this communication terminal.
Step D3～step D12 is identical with steps A 3～steps A 12.
Step D13:RNC receives when retransmitting session data, according to the communication terminal information of its record, retransmits session data to the respective communication terminal.
In the above implementation procedure, communication terminal can send the session data repeat requests by the RNC of random access procedure under it, also can send the session data repeat requests to RNC by shared channel.RNC under the communication terminal is meant the RNC at the current place of communication terminal.
Above-described first session data repeat requests is at after certain session data transmission, upstream node is received first session data repeat requests that the downstream node of its administration sends, i.e. the initial session data repeat requests of once transmitting at certain session data.For example, for communication terminal and network side, after carrying out the session data transmission of a multicast service, there is 50% communication terminal not receive this session data in the multicast group, these communication terminals all need to ask network side to retransmit this session data, therefore send the session data repeat requests to network side one after another, first session data repeat requests of receiving of network side so is and currently carries out the initial session data repeat requests that session data retransmits at 50% communication terminal; After session data carries out retransmitting the first time, still have in this communication terminal of 50% and not receive this session data, account for 10% of multicast group communication terminal quantity, these communication terminals still need network side that this session data is retransmitted once more, therefore send the session data repeat requests to network side one after another, at this moment, first session data repeat requests that network side is received is current initial session data repeat requests of carrying out the session data re-transmission at 10% communication terminal.
Do not have in the specific implementation process above-mentioned several implementations to be made up under the situation of conflict, thereby realize the optimal implementation of the present invention.
In a word, the above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.

Claims (19)

1. the transmission method of session data in the multicast/broadcast business is characterized in that communication terminal has detected unreceived multicast/broadcast service conversation data, and the method includes the steps of:
A, communication terminal send the session data repeat requests that carries session information to affiliated radio network controller;
B, radio network controller receive described session data repeat requests, send the session data repeat requests that carries session information to affiliated service support center;
C, service support center receive described session data repeat requests, obtain the session data that needs retransmit according to session information, and the radio network controller transmission session data to administration begins message then;
The transmission of D, described service support center administration the radio network controller of session data repeat requests receive described session data and begin message, return session data to this service support center and begin acceptance response, set up user-plane resources;
E, service support center are by described user-plane resources, the radio network controller that session data begins acceptance response that returned to administration retransmits session data, after radio network controller is received data retransmission, retransmit the session data of receiving to the communication terminal of administering.
2. method according to claim 1, it is characterized in that, radio network controller described in the step B receives after the described session data repeat requests, further comprise: if the session data repeat requests of receiving is first session data repeat requests at this session data, radio network controller returns session data re-transmission response to the communication terminal of administration.
3. method according to claim 2 is characterized in that, further may further comprise the steps before the described steps A:
A01, communication terminal generate random delay, and start the timing of random delay timer;
A02, communication terminal judge whether to receive that the session data that radio network controller returns retransmits response in the time range of random delay timing, if, stop the timing of random delay timer, otherwise, execution in step A.
4. method according to claim 3 is characterized in that, carries out after the described steps A, further comprises: return execution in step A01.
5. method according to claim 1, it is characterized in that, radio network controller described in the step B receives after the described session data repeat requests, further comprise: if the session data repeat requests of receiving is first session data repeat requests at this session data, radio network controller store session information.
6. method according to claim 5, it is characterized in that, described in the step B to affiliated service support center send carry the session data repeat requests of session information before, further comprise: radio network controller is according to the session information of storage, judge that whether the session data repeat requests receive is the initial session data repeat requests at this session data, if send the session data repeat requests that carries session information to affiliated service support center; Otherwise, do not operate.
7. method according to claim 5 is characterized in that, session data described in the step C begins to carry in the message session information,
Sending session data to the radio network controller of administration described in the step C begins message and is: the service support center according to described session data under the radio network controller tabulation of multicast/broadcast business, radio network controller transmission session data to administration begins message
Further comprise after the described step C: the radio network controller of service support center administration receives session data and begins message, judge whether to store described session information, if, return the session data that carries user-plane resources information to this service support center and begin acceptance response, set up user-plane resources, otherwise, return session data to described service support center and begin the refusal response.
8. method according to claim 1 is characterized in that, described step B further comprises: radio network controller recording communication terminal place cell information.
9. method according to claim 1, it is characterized in that, described step C further comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, the radio network controller of mind-set administration returns session data and retransmits response in the service support.
10. method according to claim 9 is characterized in that, before affiliated service support center transmission carries the session data repeat requests of session information, further may further comprise the steps described in the step B:
B1, radio network controller generate random delay, and start the timing of random delay timer;
Whether B2, radio network controller receive in the time range of random delay timing that the session data that returns at the service support center retransmits response, if, stop the timing of random delay timer, otherwise, send the session data repeat requests that carries session information to affiliated service support center.
11. method according to claim 10 is characterized in that, carries out after the described step B, further comprises: return execution in step B1.
12. method according to claim 1, it is characterized in that, described step C comprises: the service support center receives described session data repeat requests, if the session repeat requests of receiving is first session data repeat requests at this session data, storage sends the radio network controller information of session data repeat requests, obtain the session data that needs retransmit according to session information, according to the radio network controller information of storage, send session data to radio network controller and begin message then corresponding to described radio network controller information.
13. method according to claim 1 is characterized in that, the repeat requests of session data described in the steps A further carries communication terminal information,
Radio network controller described in the step B receives after the described session data repeat requests, further comprises: radio network controller storing communication end message,
The session data of receiving to the communication terminal re-transmission of administration described in the step e comprises: radio network controller retransmits the session data of receiving according to the communication terminal information of storage to the communication terminal corresponding to described communication terminal information of administering.
14. method according to claim 1, it is characterized in that, obtaining the session data that needs retransmit according to session information described in the step C comprises: if the session data repeat requests of receiving is first session data repeat requests at this session data, the service support center is according to session information, request content provides server that session data corresponding to session information is provided, and content providing server provides described session data to this service support center.
15. method according to claim 14, it is characterized in that, the center of service support described in the step C receives after the described session data repeat requests, further comprise: if the session data repeat requests of receiving is first session data repeat requests at this session data, service support central store session information.
16. method according to claim 15, it is characterized in that, the center of service support described in the step C receives after the described session data repeat requests, further comprise: the service support center is according to the session information of storage, judge that whether the session data repeat requests receive is the initial session data repeat requests at this session data, if request content provides server that session data corresponding to session information is provided, otherwise, do not operate.
17. method according to claim 1 is characterized in that,
Session data described in the step D begins acceptance response and carries radio network controller information,
Further comprise after the described step D: service support central store radio network controller information,
User-plane resources is passed through at the center of service support described in the step e, the radio network controller that session data begins acceptance response that returned to administration retransmits session data, comprise: the service support center is according to the radio network controller information of storage, by user-plane resources, retransmit session data to described radio network controller.
18. method according to claim 1 is characterized in that, communication terminal is by random access procedure, or shared channel sends described session data repeat requests to radio network controller.
19. method according to claim 1 is characterized in that, communication terminal detects by sliding window mechanism whether unreceived session data is arranged.
CNB2003101140720A 2003-11-11 2003-11-11 Transmission method for conversation data in group broad cast / broadcast service Expired - Fee Related CN100396051C (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CNB2003101140720A CN100396051C (en) 2003-11-11 2003-11-11 Transmission method for conversation data in group broad cast / broadcast service
PCT/CN2004/001277 WO2005046261A1 (en) 2003-11-11 2004-11-10 A transmission method of conversation data in multicasting/broadcasting service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2003101140720A CN100396051C (en) 2003-11-11 2003-11-11 Transmission method for conversation data in group broad cast / broadcast service

Publications (2)

Publication Number Publication Date
CN1617523A CN1617523A (en) 2005-05-18
CN100396051C true CN100396051C (en) 2008-06-18

Family

ID=34558467

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2003101140720A Expired - Fee Related CN100396051C (en) 2003-11-11 2003-11-11 Transmission method for conversation data in group broad cast / broadcast service

Country Status (2)

Country Link
CN (1) CN100396051C (en)
WO (1) WO2005046261A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1933651B (en) * 2005-09-12 2010-05-12 北京三星通信技术研究有限公司 Session accessing method in LTE system
CN1992707B (en) * 2005-12-29 2012-05-23 上海贝尔阿尔卡特股份有限公司 Fast restoration method of multicast service and network apparatus
US9602297B2 (en) * 2007-03-12 2017-03-21 Nokia Technologies Oy Establishment of reliable multicast/broadcast in a wireless network
CN101330648B (en) * 2007-09-19 2011-12-07 中兴通讯股份有限公司 Method for recovery of multimedia broadcast and multicast business of broadcast mode
CN102202207A (en) * 2011-06-13 2011-09-28 中兴通讯股份有限公司 Video call transmission method, system and enhanced broadcast multicast service center
CN104756447B (en) * 2013-09-25 2018-05-18 华为技术有限公司 A kind of method and Video Record Processor for recording session information
US10932095B2 (en) * 2017-11-22 2021-02-23 Huawei Technologies Co., Ltd. Method and system for multicast and broadcast services
CN110958068B (en) * 2018-09-27 2021-09-21 华为技术有限公司 Video transmission method and device
CN110022218B (en) * 2019-03-07 2021-06-04 金证财富南京科技有限公司 Multicast communication method, terminal device and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6404739B1 (en) * 1997-04-30 2002-06-11 Sony Corporation Transmitter and transmitting method, receiver and receiving method, and transceiver and transmitting/receiving method
CN1366752A (en) * 2000-04-06 2002-08-28 株式会社Ntt都科摩 Multicasting method, multicasting system, mobile station and base station

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6404739B1 (en) * 1997-04-30 2002-06-11 Sony Corporation Transmitter and transmitting method, receiver and receiving method, and transceiver and transmitting/receiving method
CN1366752A (en) * 2000-04-06 2002-08-28 株式会社Ntt都科摩 Multicasting method, multicasting system, mobile station and base station

Also Published As

Publication number Publication date
CN1617523A (en) 2005-05-18
WO2005046261A1 (en) 2005-05-19

Similar Documents

Publication Publication Date Title
US10966061B2 (en) Multicast service transmission method and device
RU2357369C2 (en) Method and device for transmitting and receiving data packets and mbms control information
AU2005204215B2 (en) Repairing errors in data of MBMS service
EP1819177B1 (en) A method of realizing data segmentation cascade and recombination and a transmitter
CN1910839B (en) Apparatus and method for establishing radio bearer of mobile terminal
EP1784946B1 (en) Method and device for acknowledging data in point-to-multipoint transmission systems
CN101151932B (en) Method and apparatus for transmitting/receiving MBMS transport blocks
US20060245386A1 (en) Method for notifying changes of cell information in multimedia broadcast/multicast service
EP1777873A1 (en) Method and apparatus for delivery of high rate data as part of a multimedia broadcast/multicast service
JP2008535364A5 (en)
WO2008131666A1 (en) Method, system, apparatus, receiving device, and transmitting device for data retransmission
CN103546826A (en) Video service transmitting method and device
WO2009100730A1 (en) Controlling point-to-multipoint transmissions of content data over a radio interface
CN100396051C (en) Transmission method for conversation data in group broad cast / broadcast service
CN101175252B (en) Method and network system for establishing conversation in multimedia broadcast multicast service
EP2878098B1 (en) User equipment node, server node and methods performed in such nodes for performing file repair procedure
CN101132392B (en) Single-carrier frequency broadcast system and method for implementing its business transmission
CN101459873B (en) Access method for MBMS service
CN102714582B (en) Control signaling processing in multimedia broadcast multicast service
CN102333331A (en) Method and apparatus for statistics of reverse retransmission rate of radio link protocol layer
WO2012013109A1 (en) Mbms service statistical feedback method and terminal
Hronec Study and Performance Evaluation of Multimedia Broadcast/Multicast Service in GERAN

Legal Events

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

Granted publication date: 20080618

Termination date: 20151111

EXPY Termination of patent right or utility model