CN101304550B - System and method for providing multimedia broadcast multicast service - Google Patents

System and method for providing multimedia broadcast multicast service Download PDF

Info

Publication number
CN101304550B
CN101304550B CN2007101080287A CN200710108028A CN101304550B CN 101304550 B CN101304550 B CN 101304550B CN 2007101080287 A CN2007101080287 A CN 2007101080287A CN 200710108028 A CN200710108028 A CN 200710108028A CN 101304550 B CN101304550 B CN 101304550B
Authority
CN
China
Prior art keywords
entity
enb
multicast address
mbms
user
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.)
Active
Application number
CN2007101080287A
Other languages
Chinese (zh)
Other versions
CN101304550A (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 CN2007101080287A priority Critical patent/CN101304550B/en
Publication of CN101304550A publication Critical patent/CN101304550A/en
Application granted granted Critical
Publication of CN101304550B publication Critical patent/CN101304550B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The embodiment of the invention discloses a method for providing multimedia broadcasting/multicasting service (MBMS) which includes: a broadcasting/multicasting service center (BM-SC) initiates MBMS conversation interaction for the evolution of a base station node (ENB) by an MBMS conversation management entity; the MBMS conversation management entity is an entity except for the user plane entity. The embodiment of the invention further discloses another method for providing the MBMS and two systems for providing the MBMS. The application of the technical proposal of the invention can lead the MBMS service in the evolution network to provide the requirements that are in accordance with separating the control surface from the user plane.

Description

The method and system of multimedia broadcast/group broadcast service are provided
Technical field
The present invention relates to the evolvement network technology, the method and system of multimedia broadcast/group broadcast service (MBMS) particularly are provided.
Background technology
At present, the network architecture of the positive active research long-term evolving network (LTE, Long Term Evolved) of third generation partner program (3GPP)/System Architecture Evolution network (SAE, System Architecture Evolved).Fig. 1 shows a kind of fixed LTE/SAE network of network configuration diagram in the prior art.Referring to Fig. 1, the network entity that is comprised among this LTE has: Mobility Management Entity (MME, Mobility Management Entity), the universal land radio access web (EUTRAN) of SAE gateway (SAE GW), home subscriber server (HSS), evolution and policy charging rule function (PCRF, Policyand Charging Rules Function) etc.
Wherein, MME preserves the MM Context of subscriber equipment (UE), as user's sign, and mobility management states, positional information etc., and Non-Access Stratum (NAS, Non Access Stratum) signaling handled, be responsible for the safety of NAS signaling etc.
SAE gateway (SAE GW) comprises two parts: service SAE gateway (Serving SAE Gateway) and packet data network SAE gateway (PDN SAE Gateway), service SAE gateway may reside on the same or different physical entities with PDN SAE gateway.Wherein, service SAE gateway is preserved user's face context of UE, carry out functions such as Lawful Interception, grouped data route, service SAE gateway links to each other with MME by the S11 interface, be responsible between MME, user entity (UPE), carrying out the mobility management information of UE and session control information alternately; PDN SAE gateway is responsible for user's face anchor point function that UE is linked into Packet Data Network, communicate by SGi reference point and external packet data net, function with grouping route and forwarding, based on packet filtering function of each user etc., and responsible policy, billing enhancement function (PCEF, Policy and Charging Enforcement Function), that is: receive service quality (QoS) and the charging policy control information that comes from PCRF by the S7 interface, in addition, PDN SAE gateway also links to each other with service SAE gateway by the S5 interface, transmit carrying foundation/modification/control informations such as deletion, and the grouped data route etc.
MME links to each other with evolution UTRAN network (EUTRAN) by S1-MME interface, is responsible for the connection of chain of command; Service SAE gateway links to each other with the EUTRAN network by S1-U interface, is responsible for the connection of user's face.Simultaneously, MME is by the S3 interface, and service SAE gateway is connected with the Serving GPRS Support Node (SGSN) of 2G/3G respectively by the S4 interface, is responsible for mobility chain of command anchor point and the user face anchor point function of UE between 3G and SAE network respectively.
Multimedia broadcast/group broadcast service (MBMS) is a kind of business of utilizing high efficiency radio transmitting method identical data to be downloaded to a plurality of UE.In order in the LTE evolvement network, to realize the MBMS transmission, introduced the notion of single-frequency network area (SFN Area:Single Frequency Network Area), and this logic entity of many sub-district/multicast coordination entity (MCE, Multi_cell/multicast Coordination Entity).Below related notion is introduced:
The SFN zone: be made up of one group of sub-district that covers continuously, identical Radio Resource is used at same frequency band in these sub-districts, with synchronous transmission MBMS data.
Many cell MBMSs retaining zone (MCMSA, Multi-cell MBMS SynchronizationArea): be made up of one group of sub-district with continuous covering of same frequency band, these sub-districts can be carried out synchronously, and can be under the SFN pattern MBMS transmission data.
Maximum SFN zone (M-SFN area): the maximum magnitude that SFN regional geography position can be expanded, may be limited by MCMSA, MBMS retaining zone (MBMS SA) or operator's configuration.
MCE: be used to dispose the base-station node (ENB that all participate in the evolution of SFN enforcement, eNodeB) Radio Link control (RLC)/medium access control controls (MAC), to guarantee the identical data of each ENB transmission, make UE can receive the business of a plurality of sub-districts simultaneously, eat dishes without rice or wine to merge.The ENB that does not form SFN need not synchronously.
MBMS gateway (MBMS GW): support synchronous protocol, for the ENB in the SFN zone provides synchronizing information, to support wireless transmission synchronous, its physics realization can and/or be served the SAE gateway at PDN SAE gateway, or special physical entity.
At present, the network architecture that MBMS is provided under above-mentioned LTE/SAE framework is determined as yet, is in wireless access network (RAN) side but just provide MBMS to reach certain common recognition: MCE in the LTE network, and participating user face not; The transmission path of MBMS user's face is: BM-SC-〉MBMS GW-ENB, promptly the bearer path of MBMS data is: from BM-SC to MBMS GW again to ENB.
The network architecture schematic diagram of the evolvement network of a kind of MBMS of providing in the prior art is provided Fig. 2.Referring to Fig. 2, this network architecture is made up of the packet-based core networks (EPC, Evolved Packet Core) and the LTE RAN of evolution, and included network entity has: content supplier, broadcast/multicast service center (BM-SC), MBMS GW, MCE and ENB.
Wherein, MBMS GW comprises chain of command and user's face two parts, is responsible for session respectively and begins/set up, and participate in the content synchronization of MBMS.MBMS GW links to each other with ENB by user's face M1 interface; On the M1 interface, transport layer is based on IP multicast mode, but the content of MBMS will adopt Frame Protocol or tunnel protocol to transmit approx, to support content synchronization or other functions.
MCE links to each other with ENB by chain of command M2 interface, and this interface is used for coordinating when ENB sets up MBMS.Wherein, the master control role of MCE for coordinating, ENB is to the MCE feedback-related information.
Link to each other by the M3 interface between MBMS GW and the MCE, the M3 interface class is similar to the MBMS that the Iu interface is provided in the existing 3G standard, promptly when setting up the MBMS resource, MCE is similar to the radio network controller (RNC) in the existing 3G network, and MBMS GW is similar to Serving GPRS Support Node (SGSN).
Under the network architecture shown in Figure 2, a typical MBMS session begins (SS, Session Start), and flow process as shown in Figure 3.Referring to Fig. 3, this session begins flow process and may further comprise the steps:
Step 301:BM-SC sends session to MBMS GW and begins request (Session StartRequest), carries the MBMS business information in this request message, as the service area of QoS information, MBMS, session identification, expectation session persistence etc.
After step 302:MBMS GW receives that session begins request, judge whether to accept this MBMS, if can accept, then reply session and begin response (Session Start Response), in this response message, carry the downlink tunnel information of MBMS GW, user's face IP address and user's face Tunnel End Point Identifier (TEID, Tunnel Endpoint Identifier) as MBMS GW.Like this, BM-SC just can send data to this address and TEID in follow-up process.In this step, MBMS GW also may provide the tunnel information of its chain of command to BM-SC, as chain of command IP address and chain of command TEID, so that carry out follow-up signaling manipulation with BM-SC, as session updates, conversation end.In being described below, directly use downlink tunnel information to represent above implication, repeat no more.
The professional for this reason IP multicast address information that provides is provided step 303:MBMS GW, and begins to ask (MBMS Session Start Request) to send to MCE by the MBMS session.
Step 304:MCE returns the MBMS session and begins response (MBMS Session StartResponse).Do not carry the tunnel information of MCE in this response, because MCE does not have user plane functions.
Step 305~step 307:MCE sends MBMS conversation informing (MBMS SessionNotification) to ENB, and request ENB carries out Polling/Counting to following UE, obtaining the information of UE, as to the interested UE number of this business; Return to MCE after the ENB statistics.
Step 308:MCE judges which ENB can form the SFN zone, which can not, and provide IP multicast address information to corresponding ENB.
After step 309:ENB receives IP multicast address information, carry out operating based on the adding (Join) of IGMP agreement to corresponding IP multicast address.
Step 310~step 312:BM-SC sends data according to the tunnel information that MBMS GW provides to MBMSGW, and MBMS GW is to Join each ENB transmission data to it, and ENB receives that the back sends downwards, and corresponding UE can receive the MBMS data.
The present inventor finds in the process of invention: in the above-mentioned prior art scheme, session begins flow process and is based upon between BM-SC, MBMS GW and the MCE, cause MBMS GW not only to need to be responsible for the MBMS transfer of data, also need to carry out MBMS signaling control, this does not meet the common recognition that the chain of command reached in the LTE/SAE framework and user's face are separated.In addition, session modification flow process and session stop the participation that flow process also needs MBMS GW, and this does not meet the common recognition that the chain of command reached in the LTE/SAE framework and user's face are separated equally.
And MCE but also will carry out the control and management of MBMS signaling as a wireless side resource in technique scheme, and this has increased the complexity of MCE; And, require to exist between all ENB in MCE and the MBMS coverage to be connected, and all ENB are controlled, will be unfavorable for the expansion of the network design and the scope of business.In addition and since such scheme to the MCE ability require highly, cause system bottleneck easily.
Summary of the invention
The method of a kind of MBMS of providing is provided the embodiment of the invention, makes when providing MBMS in evolvement network, meets the requirement that chain of command and user's face are separated.
Also disclose the another kind of method that MBMS is provided in the embodiment of the invention, made when in evolvement network, providing MBMS, met the requirement that chain of command and user's face are separated.
The system of a kind of MBMS of providing also is provided the embodiment of the invention, when MBMS is provided, meets the requirement that chain of command and user's face are separated.
The embodiment of the invention also discloses another kind the system of MBMS is provided, when MBMS is provided, meet the requirement that chain of command and user's face are separated.
The technical scheme of the embodiment of the invention specifically is achieved in that
A kind of method that multimedia broadcast/group broadcast service MBMS is provided may further comprise the steps:
Broadcast/multicast service center BM-SC initiates the MBMS session interaction by the MBMS session management entity to the base-station node ENB of evolution; Described MBMS session management entity is the entity except that user entity.
A kind of method that MBMS is provided may further comprise the steps:
BM-SC initiates the MBMS session interaction by the MBMS session management entity to ENB; Described MBMS session management entity is the entity except that user entity;
In described MBMS session interaction, BM-SC obtains the downlink tunnel information of user entity, sets up the MBMS carrying between BM-SC and the user entity; ENB obtains the IP multicast address information of user entity, sets up the MBMS carrying between ENB and the user entity.
A kind of system that MBMS is provided comprises: BM-SC, MBMS session management entity and ENB;
Described BM-SC is used for initiating the MBMS session interaction by the MBMS session management entity to ENB;
Described MBMS session management entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction to ENB; Described MBMS session management entity is the entity except that user entity.
A kind of system that MBMS is provided comprises: BM-SC, a MBMS Business Entity MBMS session management entity, user entity and ENB;
Described BM-SC is used for initiating the MBMS session interaction by the MBMS session management entity to ENB; And be used for obtaining the downlink tunnel information of user entity at described MBMS session interaction, set up and user entity between the MBMS carrying;
Described MBMS session management entity is used for the MBMS session interaction according to the BM-SC initiation, and it is mutual to initiate corresponding M BMS session order to ENB; Described MBMS session management entity is the entity except that user entity;
Described ENB is used for obtaining at described MBMS session interaction the IP multicast address information of user entity, set up and user entity between the MBMS carrying.
As seen from the above technical solution, the embodiment of the invention is disclosed to be provided in evolvement network in the technical scheme of MBMS, BM-SC initiates the MBMS session interaction by the MBMS session management entity to ENB, and described MBMS session management entity is the entity except that user entity, so, make in MBMS session interaction process, need not the participation of user entity, meet the requirement that chain of command and user's face are separated.
Description of drawings
Fig. 1 shows a kind of fixed LTE/SAE network of network configuration diagram in the prior art
The network architecture schematic diagram of the evolvement network of a kind of MBMS of providing in the prior art is provided Fig. 2.
Fig. 3 begins the schematic flow sheet of flow process for existing typical MBMS session.
Fig. 4 is the schematic flow sheet of method that MBMS is provided in a preferred embodiment of the present invention.
The logic entity schematic diagram that Fig. 5 may relate to for the method that MBMS is provided in the embodiment of the invention.
Fig. 6 shows the composition structural representation of the system that MBMS is provided in the embodiment of the invention.
Fig. 7 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention one.
Fig. 8 is for setting up the method flow schematic diagram of MBMS session in the embodiment of the invention one.
Fig. 9 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention two.
Figure 10 is for setting up the method flow schematic diagram of MBMS session in the embodiment of the invention two.
Figure 11 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention three.
Figure 12 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention four.
Figure 13 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention five.
Figure 14 is for setting up the composition structural representation of second preferable system of MBMS session in the embodiment of the invention five.
Figure 15 is for setting up the composition structural representation of the 3rd preferable system of MBMS session in the embodiment of the invention five.
Figure 16 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention six.
Figure 17 is for setting up the method flow schematic diagram of MBMS session in the embodiment of the invention six.
Figure 18 is for setting up the composition structural representation of second preferable system of MBMS session in the embodiment of the invention six.
Figure 19 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention seven.
Figure 20 is for setting up the composition structural representation of second preferable system of MBMS session in the embodiment of the invention seven.
Figure 21 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention eight.
Figure 22 is for setting up the method flow schematic diagram of MBMS session in the embodiment of the invention eight.
Figure 23 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention nine.
Figure 24 is for setting up the composition structural representation of second preferable system of MBMS session in the embodiment of the invention nine.
Figure 25 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention ten.
Figure 26 is for setting up the first preferred approach schematic flow sheet of MBMS session in the embodiment of the invention ten.
Figure 27 is for setting up the composition structural representation of second preferable system of MBMS session in the embodiment of the invention ten.
Figure 28 is for setting up the second preferred approach schematic flow sheet of MBMS session in the embodiment of the invention ten.
Figure 29 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 11.
Figure 30 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention 12.
Figure 31 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 13.
Figure 32 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 14.
Figure 33 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 15.
Figure 34 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention 16.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
When MBMS is provided, need carry out the MBMS session interaction, comprising: the MBMS session begins Signalling exchange, MBMS session modification Signalling exchange and MBMS session and stops Signalling exchange.Wherein, the MBMS session stops signalling interactive process, the MBMS session modification signalling interactive process that just can carry out with the beared information that need not to obtain user entity, and need not to obtain the MBMS session that the beared information of user entity just can carry out and begin the signalling interactive process comparing class seemingly; And the MBMS session that the beared information that need obtain user entity just can carry out begins signalling interactive process, obtain MBMS session modification signalling interactive process comparing class that the beared information of user entity just can carry out seemingly with needs, therefore, provided corresponding solution at above-mentioned two kinds of situations in the embodiment of the invention.Here, beared information comprises: the IP multicast address information of the downlink tunnel information of the required user entity that obtains of BM-SC and the required user entity that obtains of ENB.The MBMS session that just can carry out at the beared information that need not to obtain user entity begins in the signalling interactive process, the beared information of pre-configured user entity in related entities.
Session stops Signalling exchange and similar with it MBMS session modification Signalling exchange and MBMS session and begins Signalling exchange at MBMS, the method of a kind of MBMS of providing is provided, and this method BM-SC initiates the MBMS session interaction by the MBMS session management entity to ENB; Described MBMS session management entity is the entity except that user entity.
Under the thought that chain of command and user's face are separated, MBMS GW only is responsible for the transmission of MBMS data, is called user entity.
In said method, the MBMS session management entity can be chain of command entity, coordination entity or ENB.Wherein, the chain of command entity is responsible for MBMS signaling management and control, belongs to the chain of command entity as entities such as MME; Coordination entity is responsible for determining the composition in SFN zone and be in charge of ENB relevant with certain MBMS under the coordination entity that MCE belongs to coordination entity.
When adopting ENB as the MBMS session management entity, the chain of command trend is: BM-SC-〉ENB.
When adopting coordination entity as the MBMS session management entity, the chain of command trend is: BM-SC-〉MCE-〉ENB.
When adopting the chain of command entity as the MBMS session management entity, the chain of command trend can be: BM-SC-〉MME-〉MCE-〉ENB, at this moment, the chain of command entity is initiated corresponding M BMS session interaction by coordination entity to ENB after receiving the MBMS session interaction that BM-SC initiates;
Chain of command trend also can be BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side, at this moment, the chain of command entity is after receiving the MBMS session interaction that BM-SC initiates, initiate corresponding M BMS session interaction to coordination entity and common ENB, the ENB of coordination entity in maximum SFN zone initiates corresponding M BMS session interaction;
The chain of command trend can also be BM-SC-〉MME-〉ENB, at this moment, the chain of command entity is initiated corresponding M BMS session interaction to ENB after receiving the MBMS session interaction that BM-SC initiates.
When adopting chain of command entity and coordination entity as the MBMS session management entity, chain of command trend is: BM-SC-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side, receive the MBMS session interaction of BM-SC initiation in the MBMS session management entity after, initiate corresponding M BMS session interaction by the chain of command entity to common ENB, the ENB of coordination entity in maximum SFN zone initiates corresponding M BMS session interaction.
Obtain MBMS session that the beared information of user entity just can carry out at needs and begin Signalling exchange and similar MBMS session modification Signalling exchange with it, the embodiment of the invention discloses the method for a kind of MBMS of providing, as shown in Figure 4.Fig. 4 is the schematic flow sheet of method that MBMS is provided in a preferred embodiment of the present invention.Referring to Fig. 4, this method may further comprise the steps:
Step 401:BM-SC initiates the MBMS session interaction by the MBMS session management entity to ENB; Described MBMS session management entity is the entity except that user entity.
Step 402: in described MBMS session interaction, BM-SC obtains the downlink tunnel information of user entity, sets up the MBMS carrying between BM-SC and the user entity.
Step 403: in described MBMS session interaction, ENB obtains the IP multicast address information of user entity, sets up the MBMS carrying between ENB and the user entity.
So far, finish the method flow that present embodiment provides MBMS.
As previously mentioned, MBMS session management entity except that user entity can be chain of command entity, coordination entity or ENB etc., be that BM-SC can initiate the MBMS session interaction to ENB by chain of command entity or coordination entity, also can directly initiate the MBMS session interaction to ENB.
In the method shown in Figure 4, user entity can be one or two: when user entity is one, can only provide a synchrodata source IP multicast address, two IP multicast address also can be provided, one as the synchrodata source, and another is as the non-synchronous data source; When user entity was two, one as the synchrodata source, and another is as the non-synchronous data source.Corresponding to synchrodata source and non-synchronous data source IP multicast address may be respectively with synchronously/asynchronous indication identifies.
ENB is classified: for example, the ENB in the maximum SFN zone is classified as a class, these ENB have identical frequency band, may form SFN; For belonging to this type of ENB, can also continue to be divided into two classes according to whether forming SFN.Common ENB is classified as a class, that is: can not forms the ENB of SFN with other ENB, for example single sub-district ENB (SC ENB, Single Cell ENB).Divide time-like to ENB, can also divide, for example, divide the ENB that forms SFN into a class, divide the ENB that does not form SFN into a class according to whether forming SFN.Certainly can also divide according to other standards, the present invention does not limit this.
Only have coordination entity in system, when not having the chain of command entity, the chain of command trend can be: BM-SC-〉MCE-〉ENB or BM-SC-〉ENB; When having chain of command entity and coordination entity simultaneously in the system, the trend of chain of command can be BM-SC-〉MME-〉MCE-〉ENB, also can be BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side, can also be BM-SC-〉MME-〉ENB.When adopting BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉when ENB chain of command arranged side by side moves towards, if there are two IP multicast address, then:
Can non-synchronous data source IP multicast address be provided or indicate the common ENB user entity corresponding to set up the MBMS carrying to common ENB by MME with non-synchronous data source IP multicast address; The IP multicast address in synchrodata source is provided by the ENB (generally being the ENB in the maximum SFN zone) of MCE under it, or MCE provides non-synchronous data source IP multicast address to the IP multicast address that its ENB that can form SFN down provides the synchrodata source to the ENB that can not form SFN.
Based on above-mentioned analysis, in order to introduce the disclosed technical scheme of the embodiment of the invention more intuitively, the logic entity that Fig. 5 shows provides MBMS in the present embodiment method may relate to.In evolvement network, except that logic entity illustrated in fig. 5, also there are other network entities certainly, as HSS, PCRF etc.In addition, in the Pool notion, a Pool exists a plurality of chain of command entities and user entity, but for brevity, Fig. 5 only illustrates the logic entity relevant with MBMS.Referring to Fig. 5:
S-ENB1,2,3 signs are in the ENB in the maximum SFN zone, and O-ENB4 is common ENB.In the following description, always we think that S-ENB1 and S-ENB2 can form SFN, although and S-ENB3 is in the maximum SFN zone, but because the Radio Resource identical with other ENB not can't be formed SFN.O-ENB4 can not form SFN because be common ENB.
According to the common recognition of having reached, the trend of user's face is BM-SC-〉MBMS GW-〉ENB, and chain of command is not determined as yet.
As mentioned above, user entity can be one or two:
When having only a user entity and this user entity that a synchrodata source IP multicast address only is provided, all ENB set up the MBMS carrying with this IP multicast address, receiving isochronous data, but the ENB that forms SFN, be the ENB in the SFN zone, carry out simultaneous operation, the ENB in other non-SFN zones does not carry out simultaneous operation after receiving synchrodata.For example, after the ENB in the non-SFN zone receives synchrodata, the timestamp packet header in can packet discard.
When having only a user entity and this user entity that two IP multicast address are provided, when difference corresponding synchrodata source and non-synchronous data source, or, when there being two user entities, when difference corresponding synchrodata source and non-synchronous data source, can be: the IP multicast address that the ENB in the SFN zone is corresponding with the synchrodata source be set up the MBMS carrying, receive data from the synchrodata source, the ENB IP multicast address corresponding with unsynchronized sources in the non-SFN zone set up the MBMS carrying, receives data from the non-synchronous data source; Also can be: the ENB that is in coordination entity administration is receiving isochronous data, and single sub-district ENB receives non-synchronous data; Can also be: ENB gets access to two IP multicast address, according to synchronously/asynchronous indication or pre-configured information, determine which IP multicast address to set up the MBMS carrying with.
When having two IP multicast address, can specify by which IP multicast address as the synchrodata source by BM-SC, which IP address is as the non-synchronous data source, and will indicate notice user entity and relevant MBMS session management entity accordingly; Also can determine, that is: when user entity provides IP multicast address information, provide and this IP multicast address corresponding synchronous/asynchronous indication by user entity.
In method shown in Figure 4, BM-SC obtains the downlink tunnel information of user entity, the mode of IP multicast address information that ENB obtains user entity can be: pre-configured mode or the mode that initiatively sends information to the mode or the user entity of user entity solicited message or pre-configured and the mode that combines to the user entity solicited message.
Wherein, pre-configured mode can be: the downlink tunnel information and the IP multicast address information of user entity all are configured among the BM-SC, in the process of Signalling exchange the IP multicast address information of user entity are sent to corresponding ENB by the MBMS session management entity by BM-SC; Perhaps, also can be that a part of beared information with user entity is configured among the BM-SC, another part beared information is configured in the MBMS session management entity, begin in the process of Signalling exchange in the MBMS session, ENB obtains the IP multicast address information of required user entity from the MBMS session management entity.
Mode to the user entity solicited message can be: to the user entity request, the information of being obtained is sent to corresponding ENB by the MBMS session management entity by BM-SC; Or, by other MBMS session management entity to the user entity request.
The mode that user entity initiatively sends information can be: initiatively IP multicast address information and downlink tunnel information are sent to corresponding M BMS session management entity or BM-SC by user entity, this situation may occur in user entity and trigger the transmission of MBMS data.
Pre-configured and the mode that combines to the user entity solicited message are above-mentioned pre-configured modes and to the combination of user entity solicited message.For example, a part of information can be pre-configured in BM-SC or the MBMS session management entity, not have pre-configured that part of information by BM-SC or MBMS session management entity to the user entity request again.For this mode that combines, can carry out feasible combination arbitrarily with reference to above-mentioned pre-configured mode with to the mode of user entity solicited message.Because the possibility of combination is very many, and, on the basis of above-mentioned disclosed dual mode, also be very easy to draw, therefore, repeat no more.
Corresponding to above-mentioned two kinds of methods that MBMS is provided, the system of a kind of MBMS of providing is disclosed respectively in the embodiment of the invention.Because the composition structure comparing class of two kinds of systems seemingly, describes below by the composition structure of same accompanying drawing to these two kinds of systems.
Fig. 6 shows the composition structural representation of the system that MBMS is provided in the embodiment of the invention.Referring to Fig. 6, corresponding to aforementioned: session stops Signalling exchange and similar with it MBMS session modification Signalling exchange and MBMS session and begins the method that MBMS is provided that Signalling exchange proposes at MBMS, and the system that present embodiment provided comprises:: BM-SC610, MBMS session management entity 620 and ENB640.
Wherein, BM-SC610 is used for initiating the MBMS session interaction by MBMS session management entity 620 to ENB640;
MBMS session management entity 610 is used for the MBMS session interaction according to the BM-SC610 initiation, initiates corresponding M BMS session interaction to ENB640; Described MBMS session management entity is the entity except that user entity.
In the said system, the MBMS session management entity can be coordination entity or ENB.When adopting ENB as the MBMS session management entity, the chain of command trend is: BM-SC-〉ENB; When adopting coordination entity as the MBMS session management entity, the chain of command trend is: BM-SC-〉MCE-〉ENB.
In the said system, the MBMS session management entity also can be the chain of command entity.At this moment, the chain of command trend can be: BM-SC-〉MME-〉MCE-〉ENB, the chain of command entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction by coordination entity to ENB;
Chain of command trend also can be BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side; ENB can comprise: ENB in the maximum SFN zone and common ENB; The chain of command entity is used for the MBMS session interaction according to the BM-SC initiation, initiate corresponding M BMS session interaction to coordination entity and common ENB, coordination entity is used for the MBMS session interaction according to the initiation of chain of command entity, and the ENB in maximum SFN zone initiates corresponding M BMS session interaction;
The chain of command trend can also be BM-SC-〉MME-〉ENB, at this moment, the chain of command entity is initiated corresponding M BMS session interaction to ENB after receiving the MBMS session interaction that BM-SC initiates.
In the said system, the MBMS session management entity can be chain of command entity and coordination entity; ENB can comprise: ENB in the maximum SFN zone and common ENB; Chain of command trend is: BM-SC-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side, and the chain of command entity is used for the MBMS session interaction of initiating according to BM-SC, initiates corresponding M BMS session interaction to common ENB; Coordination entity is used for the MBMS session interaction according to the BM-SC initiation, and the ENB in maximum SFN zone initiates corresponding M BMS session interaction.
Referring to Fig. 6, corresponding to aforementioned: obtain MBMS session that the beared information of user entity just can carry out at needs and begin Signalling exchange and the similar method that MBMS is provided that proposed of MBMS session modification Signalling exchange with it, the system that present embodiment provided comprises: BM-SC610, MBMS session management entity 620, user entity 630 and ENB640.
Wherein, BM-SC610 is used to obtain the downlink tunnel information of user entity 630, set up with user entity 630 between the MBMS carrying, and be used for by MBMS session management entity 620 to ENB640 initiation MBMS session interaction;
MBMS session management entity 620 is used for the MBMS session interaction according to the BM-SC610 initiation, initiates corresponding M BMS session interaction to ENB640; Described MBMS session management entity 620 is the entity except that user entity 630;
ENB640 is used to obtain the IP multicast address information of user entity 630, set up with user entity 630 between MBMS carry.
Preferably, the BM-SC in the system shown in Figure 6 can be used for the downlink tunnel information and/or the IP multicast address information of pre-configured user entity, and provides IP multicast address information to the MBMS session management entity; Correspondingly, the MBMS session management entity, the IP multicast address information that is used for coming from BM-SC sends to corresponding ENB.
Preferably, the BM-SC in the system shown in Figure 6 can be used for to the user entity solicited message, receives the downlink tunnel information and/or the IP multicast address information that come from user entity, and provides IP multicast address information to the MBMS session management entity; Correspondingly, user entity is used for the request according to BM-SC, returns the downlink tunnel information and/or the IP multicast address information of user entity to BM-SC; The MBMS session management entity, the IP multicast address information that is used for coming from BM-SC sends to corresponding ENB.
In system shown in Figure 6, the MBMS session management entity can be used for the IP multicast address information of pre-configured user entity, and provides described IP multicast address information to corresponding ENB.
Preferably, the MBMS session management entity in the system shown in Figure 6 is used for the MBMS session interaction of initiating according to BM-SC, to the user entity solicited message, and provides the information of BM-SC to user entity; Reception comes from the IP multicast address information of user entity, and provides described IP multicast address information to ENB; Correspondingly, user entity is used for the request according to the MBMS session management entity, returns the IP multicast address information of user entity to the MBMS session management entity, and the downlink tunnel information of user entity is provided or sets up the MBMS carrying with BM-SC to BM-SC; BM-SC is used to receive the downlink tunnel information that comes from user entity.
In system shown in Figure 6, the MBMS session management entity, can be used for to the user entity solicited message, reception comes from the downlink tunnel information and/or the IP multicast address information of user entity, and the downlink tunnel information of user entity is provided, the IP multicast address information of user entity is provided to ENB to BM-SC; BM-SC is used to receive the downlink tunnel information and/or the IP multicast address information of the user entity that comes from the MBMS session management entity.
Further, the number of user entity can be two; At this moment, BM-SC, can be used for the first user entity solicited message to described two user entities, reception comes from the downlink tunnel information of first user entity of first user entity and/or the IP multicast address information of the IP multicast address information and second user entity, and provides described IP multicast address information to the MBMS session management entity;
First user entity, can be used for request according to BM-SC, obtain the downlink tunnel information and/or the IP multicast address information of second user entity in described two user entities, write down the downlink tunnel information of second user entity, and return the downlink tunnel information of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity to BM-SC;
The MBMS session management entity, the IP multicast address information that can be used for coming from BM-SC sends to corresponding ENB.
When the number of user entity is two; The MBMS session management entity, can be used for beginning the first user entity solicited message of Signalling exchange to described two user entities according to the MBMS session that BM-SC initiates, reception comes from the downlink tunnel information of first user entity of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity, and the downlink tunnel information of first user entity is provided, the IP multicast address information of first user entity and second user entity is provided to ENB to BM-SC;
First user entity, can be used for request according to the MBMS session management entity, obtain the downlink tunnel information and/or the IP multicast address information of second user entity in described two user entities, write down the downlink tunnel information of second user entity, and return the downlink tunnel information of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity to the MBMS session management entity;
BM-SC can be used to receive the downlink tunnel information that comes from the MBMS session management entity.
In the system shown in Figure 6, the MBMS session management entity can be chain of command entity, coordination entity or ENB.Wherein, chain of command entity and coordination entity might exist simultaneously.Only have coordination entity in system, when not having the chain of command entity, the chain of command trend can be: BM-SC-〉MCE-〉ENB or BM-SC-〉ENB; When having chain of command entity and coordination entity simultaneously in the system, the trend of chain of command can be BM-SC-〉MME-〉MCE-〉ENB, also can be BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side, can also be BM-SC-〉MME-〉ENB.
In above-mentioned two kinds of method and systems, obtain MBMS session that user entity just can carry out at needs and begin Signalling exchange and the similar method and system that MBMS is provided that proposed of MBMS session modification Signalling exchange with it, than session stops Signalling exchange and similarly MBMS session modification Signalling exchange and MBMS session begin the method and system that MBMS is provided that Signalling exchange proposes with it at MBMS, more complicated, more alternately between the related network entity.Therefore, among 16 embodiment below, will obtaining MBMS session that user entity just can carry out with needs, to begin signalling interactive process be example, and the method and system that the invention provides MBMS is elaborated.
Need to prove that ENB of the present invention is effective ENB in the MBMS service area.That is to say that MBMS possibility specified services is the zone effectively, is called the MBMS service area, effectively ENB is above-mentioned ENB in service area.For example, the ENB in the described maximum SFN zone may refer to: the ENB in the common factor of maximum SFN zone and MBMS service area.
In the network architecture schematic diagram of following each embodiment, solid line is represented user's face trend, and dotted line is represented the information interaction between chain of command trend or network entity.
Embodiment one:
In the present embodiment, the network entity that system comprised of setting up the MBMS session has: BM-SC, user entity, MCE and ENB; Wherein, user entity is one, is designated as MBMS GW.In the present embodiment, the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.Present embodiment adopts pre-configured mode to make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.
Fig. 7 is the composition structural representation of system that MBMS is provided in the embodiment of the invention one.Referring to Fig. 7, the pre-configured mode of present embodiment can be the IP multicast address of the MBMS GW of configuration related service in BM-SC, MCE or ENB, and disposes the downlink tunnel information of the MBMSGW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; When MCE initiates the MBMS session and begins Signalling exchange, the IP multicast address information of the MBMS GW that disposed is sent to MCE at BM-SC, by MCE the IP multicast address information of MBMS GW is sent to corresponding ENB again;
Also can in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MCE; , need not BM-SC the IP multicast address information of MBMS GW is sent to MCE when MCE initiates the MBMS session and begins Signalling exchange at BM-SC, MCE can send to corresponding ENB with the IP multicast address information of the MBMS GW that disposed;
Can also be in advance in BM-SC the downlink tunnel information of configuration MBMS GW, the IP multicast address information of configuration MBMS GW in ENB like this, just need not BM-SC or MCE the IP multicast address information of MBMSGW is sent to ENB.
In the present embodiment, may link to each other by borde gateway between BM-SC and the MCE, for example, MBMSGW can be used as this gateway.By MCE ENB is coordinated, as previously mentioned:
If only there is an IP multicast address, then MCE sends to all relevant ENB with this IP multicast address information, and coordinates to form the identical Radio Resource of ENB use of SFN.All relevant ENB set up the MBMS carrying with this IP multicast address, add this IP multicast address that is:, and the ENB in the non-SFN zone does not carry out simultaneous operation.
If there are two IP multicast address, then MCE can offer the IP multicast address corresponding to the synchrodata source ENB in the SFN zone, to offer the ENB in the non-SFN zone corresponding to the IP multicast address in non-synchronous data source, here, ENB in the non-SFN zone, the ENB that promptly can not form SFN comprises common ENB and in the maximum SFN zone, but does not have Radio Resource or because other reasons can not be formed the ENB of SFN.
If there are two IP multicast address, MCE also can provide the IP multicast address information in synchrodata source to the ENB in being in maximum SFN zone, and the IP multicast address information in non-synchronous data source is provided to common ENB.
If there are two IP multicast address, MCE can also provide two IP multicast address to all ENB,, is determined to add which IP multicast address and receives the MBMS data according to synchronous/asynchronous indication or pre-configured information by ENB.
In the present embodiment, the method flow of setting up the MBMS session as shown in Figure 8.Referring to Fig. 8, this flow process may further comprise the steps:
Step 801:BM-SC sends Session Start Request to MCE, carries the MBMS business information in this request message, as the service area of QoS information, MBMS, session identification, expectation session persistence etc.If BM-SC disposes the IP multicast address information of MBMS GW, then send to MCE by Session Start Request.
Step 802:MCE returns response (Session Start Response) to BM-SC.
Step 803:MCE determines the composition of SFN.
In this step, the composition that MCE can decide SFN in the positional information of the quantity of ENB and/or ENB and/or professional priority and/or professional overlay area according to Radio Resource situation and/or UE.In this process, MCE may carry out the mutual of relevant information with ENB.
Step 804:MCE sends Session Start Request to relevant ENB.
If the IP multicast address information configuration is in BM-SC or among the MCE, then MCE need be carried on IP multicast address information among the Session Start Request in this step, sends to corresponding ENB.In this step, the method that MCE sends IP multicast address to ENB as previously mentioned:
If only there is an IP multicast address, then MCE sends to all relevant ENB with this IP multicast address information, and coordinates to form the identical Radio Resource of ENB use of SFN.All relevant ENB add this IP multicast address, and the ENB in the non-SFN zone does not carry out simultaneous operation.
If there are two IP multicast address, then MCE can offer the IP multicast address corresponding to the synchrodata source ENB in the SFN zone, to offer the ENB in the non-SFN zone corresponding to the IP multicast address in non-synchronous data source, here, ENB in the non-SFN zone, the ENB that promptly can not form SFN comprises common ENB and in the maximum SFN zone, but does not have Radio Resource or because other reasons can not be formed the ENB of SFN.
If there are two IP multicast address, MCE also can provide the IP multicast address information in synchrodata source to the ENB in being in maximum SFN zone, and the IP multicast address information in non-synchronous data source is provided to common ENB.
If there are two IP multicast address, MCE can also provide two IP multicast address to all ENB,, is determined to add which IP multicast address and receives the MBMS data according to synchronous/asynchronous indication or pre-configured information by ENB.
Only illustrate one as representative for the ENB that belongs to same type among the figure, for example, represented all ENB in the SFN zone with S-ENB1.In the following description this kind situation is repeated no more.
In this step, if disposed the IP multicast address information of MBMS GW in ENB, then MCE need not IP multicast address is sent to ENB.
Step 805:ENB uses IGMP to join and receives the MBMS data on the corresponding IP multicast address.
In this step, if only have an IP multicast address, the ENB in then non-SFN zone does not carry out simultaneous operation.In this step, ENB may return response at the described Session StartRequest of step 804 to MCE.
So far, finish to set up in the present embodiment method flow of MBMS session.
As seen from the above-described embodiment, present embodiment is by pre-configured mode, on the one hand, makes BM-SC get access to the downlink tunnel information of MBMS GW, and sets up the MBMS carrying according to downlink tunnel information of being obtained and corresponding M BMS GW; On the other hand, make ENB get access to the IP multicast address information of MBMS GW, set up the MBMS carrying with corresponding M BMS GW.So, user entity MBMS GW does not participate in setting up the chain of command Signalling exchange of MBMS session, and having realized meeting chain of command and the user's face MBMS business that requires that is separated in evolvement network provides.
Embodiment two:
In the present embodiment, the network entity that system comprised of setting up the MBMS session is identical with embodiment one, comprising: BM-SC, user entity, MCE and an ENB.In the present embodiment, the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.Employing makes BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity by the mode of BM-SC to MBMS GW solicited message.
Fig. 9 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention two.Referring to Fig. 9, in the present embodiment, BM-SC is specially to the method for MBMS GW solicited message:
At first by BM-SC to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW; Then, when MCE initiates the MBMS session and begins Signalling exchange, the IP multicast address information of MBMS GW is sent to MCE at BM-SC; At last, by MCE the IP multicast address information of MBMS GW is sent to corresponding ENB.
In the present embodiment, the method flow of setting up the MBMS session as shown in figure 10.Referring to Figure 10, this flow process may further comprise the steps:
Step 1001:BM-SC sends information request message (InformationRequest) to MBMS GW, to MBMS GW solicited message, may carry qos parameter in this message.
Step 1002:MBMS GW is to BM-SC return information response message (InformationResponse).
In this step, MBMS GW can carry the downlink tunnel information of MBMS GW in response message, as user's face IP address and the TEID of MBMS GW.Like this, BM-SC just can send data to this address and TEID in follow-up process.In this step, MBMS GW also may provide the tunnel information of its chain of command to BM-SC, as chain of command IP address and chain of command TEID, so that carry out follow-up signaling manipulation with BM-SC, as session updates, conversation end.
The class of operation that step 1003~step 1007 and step 701~step 705 is carried out seemingly, difference is: because the IP multicast address information of MBMS GW might be arranged among MCE or the ENB among the embodiment one, so, the IP multicast address information of in the Session Start Request that MCE sends, not necessarily carrying MBMS GW by BM-SC, the IP multicast address information of in the Session StartRequest that ENB sends, also not necessarily carrying MBMS GW by MCE.But, in the present embodiment, there is not the IP multicast address information of pre-configured MBMS GW among MCE and the ENB, therefore, in the Session Start Request that step 1003 and step 1006 sent, all carry the IP multicast address information of MBMSGW.
So far, finish to set up in the present embodiment method flow of MBMS session.
Embodiment three:
In the present embodiment, the network entity that system comprised of setting up the MBMS session is identical with embodiment one, comprising: BM-SC, user entity, MCE and an ENB.In the present embodiment, the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.Employing makes BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity by the mode of MCE to MBMS GW solicited message.
Figure 11 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention three.Referring to Figure 11, in the present embodiment, MCE is specially to the method for MBMS GW solicited message:
At first initiate the MBMS session to MCE and begin Signalling exchange by BM-SC; Then, to MBMS GW solicited message, obtain the IP multicast address information of MBMS GW, the information of BM-SC is offered MBMS GW, and the IP multicast address information of MBMS GW is sent to corresponding ENB by MCE; At last, the downlink tunnel information of MBMS GW is provided or joins BM-SC to BM-SC according to the BM-SC information of being obtained by MBMS GW.
In the present embodiment, MCE provides the method for IP multicast address information identical with embodiment one to ENB, do not repeat them here.
Embodiment four:
In the present embodiment, the network entity that system comprised of setting up the MBMS session is identical with embodiment one, comprising: BM-SC, user entity, MCE and an ENB.In the present embodiment, the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.Employing makes BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity by the mode of MCE to MBMS GW solicited message.
Figure 12 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention four.Referring to Figure 12, in the present embodiment, MCE is specially to the method for MBMS GW solicited message:
At first initiate the MBMS session to MCE and begin Signalling exchange by BM-SC; Then, to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW, the downlink tunnel information of MBMS GW is sent to BM-SC, and the IP multicast address information of MBMS GW is sent to corresponding ENB by MCE.So, downlink tunnel information, the ENB that makes BM-SC get access to MBMS GW gets access to the IP multicast address information of MBMS GW, and sets up MBMS carrying with corresponding user entity, and having realized meeting the be separated MBMS business of requirement of chain of command and user's face provides.
Embodiment five:
In the present embodiment, set up the MBMS session management entity that system comprised of MBMS session, on the basis of embodiment one to embodiment four described system, increased chain of command entity: MME.In the present embodiment, the system that sets up the MBMS session comprises: BM-SC, user entity, MCE, MME and an ENB.The MBMS session management entity is: MME, the chain of command trend is: BM-SC-〉MME-〉MCE-〉ENB.
Present embodiment can adopt the one similar pre-configured mode with embodiment, makes BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.
Figure 13 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention five.Referring to Figure 13, the pre-configured mode of present embodiment can be the IP multicast address of the MBMS GW of configuration related service in BM-SC, MME, MCE or ENB, and disposes the downlink tunnel information of the MBMS GW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; At BM-SC when MME initiates the MBMS session and begins Signalling exchange, the IP multicast address information of the MBMS GW that disposed is sent to MME, initiate the MBMS session by MME to MCE then and begin Signalling exchange, the IP multicast address information of MBMS GW is sent to MCE, by MCE the IP multicast address information of MBMS GW is sent to corresponding ENB again;
Also can in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MME; After MCE initiated the MBMS session and begins Signalling exchange, MME initiated the MBMS session to MCE and begins Signalling exchange at BM-SC, and the IP multicast address information of MBMSGW is sent to MCE, by MCE the IP multicast address information of MBMS GW was sent to corresponding ENB again;
Can also in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MCE; Begin in the Signalling exchange to the MBMS session that MCE initiates at BM-SC, and MME begins in the Signalling exchange to the MBMS session that MCE initiates, all need not to carry the IP multicast address information of MBMS GW, MCE can be when receiving that MBMS session that MME initiates begins Signalling exchange, and the IP multicast address information of the MBMS GW that disposed is sent to corresponding ENB;
Can also be in advance in BM-SC the downlink tunnel information of configuration MBMS GW, the IP multicast address information of configuration MBMS GW in ENB like this, just need not BM-SC, MME or MCE the IP multicast address information of MBMS GW is sent to ENB.
By above-mentioned pre-configured mode, on the one hand, make BM-SC get access to the downlink tunnel information of MBMS GW, and set up the MBMS carrying according to downlink tunnel information of being obtained and corresponding M BMS GW; On the other hand, make ENB get access to the IP multicast address information of MBMS GW, set up the MBMS carrying with corresponding M BMS GW.So, user entity MBMS GW does not participate in setting up the chain of command Signalling exchange of MBMS session, and having realized meeting chain of command and the user's face MBMS business that requires that is separated in evolvement network provides.
above-mentionedly added MME, the chain of command trend is BM-SC-MME-MCE-in the system of ENB, also can take two to embodiment four similar modes with embodiment, promptly adopt the mode of solicited message, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.Difference only is: being undertaken by MME alternately between BM-SC and the MCE, the chain of command trend is: BM-SC-〉MME-〉MCE-〉ENB.Below by the embodiment of two example explanation present embodiments corresponding to embodiment two to embodiment four described technical schemes.
For example, Figure 14 shows the composition structural representation of present embodiment corresponding to second preferable system of embodiment two described technical schemes.Referring to Figure 14, in the present embodiment, BM-SC is specially to the method for MBMS GW solicited message:
At first by BM-SC to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW; Then, begin in the Signalling exchange to the MBMS session that MME initiates, the IP multicast address information of MBMS GW is sent to MME, initiate the MBMS session by MME to MCE again and begin Signalling exchange, the IP multicast address information of MBMS GW is sent to MCE at BM-SC; At last, by MCE the IP multicast address information of MBMS GW is sent to corresponding ENB.
For example, Figure 15 shows the composition structural representation of present embodiment corresponding to the 3rd preferable system of embodiment four described technical schemes.Referring to Figure 15, in the present embodiment, MME is specially to the method for MBMS GW solicited message:
At first, initiate the MBMS session by BM-SC to MME and begin Signalling exchange; Then, to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW, the downlink tunnel information of MBMS GW is sent to BM-SC, and the IP multicast address information of MBMS GW is sent to MCE by MME; At last, by MCE the IP multicast address information of MBMS GW is sent to corresponding ENB.So, downlink tunnel information, the ENB that makes BM-SC get access to MBMS GW gets access to the IP multicast address information of MBMS GW, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.
Embodiment six:
In the present embodiment, the network entity that system comprised of setting up the MBMS session is identical with embodiment five, comprising: BM-SC, user entity, MCE, MME and an ENB.In the present embodiment, the MBMS session management entity is: MME, chain of command trend is: BM-SC-〉MME-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side.
Present embodiment both can have been taked the one similar pre-configured mode with embodiment, also can take the mode with embodiment two to embodiment four similar solicited messages, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.Be that example is elaborated in pre-configured mode below.
Figure 16 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention six.Referring to Figure 16, the pre-configured mode of present embodiment can be the IP multicast address of the MBMS GW of configuration related service in BM-SC or MME, and disposes the downlink tunnel information of the MBMS GW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; At BM-SC when MME initiates the MBMS session and begins Signalling exchange, the IP multicast address information of the MBMS GW that disposed is sent to MME, begin Signalling exchange by MME to MCE and common ENB initiation MBMS session then, the IP multicast address information of MBMS GW is sent to MCE and common ENB, by MCE the IP multicast address information of MBMS GW is sent to the ENB in the maximum SFN zone under the MCE again;
Also can in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MME; At BM-SC after MCE initiates the MBMS session and begins Signalling exchange, MME begins Signalling exchange to MCE and common ENB initiation MBMS session, the IP multicast address information of MBMS GW is sent to MCE and common ENB, by MCE the IP multicast address information of MBMS GW is sent to the ENB in the maximum SFN zone under the MCE again.
When having two IP multicast address, MME and MCE can provide IP multicast address to different classes of ENB respectively according to the mode identical with embodiment one, do not repeat them here.
In this preferred embodiment, corresponding to the above-mentioned mode that sets in advance, the method flow of setting up the MBMS session as shown in figure 17.Referring to Figure 17, this flow process may further comprise the steps:
Step 1701~step 1702:BM-SC obtains IP multicast address information and the downlink tunnel information of MBMS GW to MBMS GW solicited message.
Step 1703~step 1706:BM-SC sends to MME and MCE with the IP multicast address information of MBMS GW.
In this step, if only have an IP multicast address information, then BM-SC sends to MME and MCE with this IP multicast address information;
If there are two IP multicast address information, then BM-SC will send to MME corresponding to the IP multicast address in non-synchronous data source; When MCE sends IP multicast address information, can only send IP multicast address information corresponding to the synchrodata source, also two IP multicast address all can be sent to MCE.
Step 1707:MME sends Session Start Request to common ENB, and IP multicast address information is sent to common ENB.
In this step, if only have an IP multicast address information, then MME sends to common ENB with this IP multicast address; If there are two IP multicast address information, then MME will send to common ENB corresponding to the IP multicast address in non-synchronous data source.
Step 1708:MCE determines the composition of SFN.
The ENB of step 1709:MCE in maximum SFN zone sends Session Start Request.
In this step, MCE is carried on IP multicast address information among the Session Start Request and sends to corresponding ENB.To carry IP multicast address information identical with embodiment one step 804 for MCE in this step, do not repeat them here.
Step 1710:ENB uses IGMP to join and receives the MBMS data on the corresponding IP multicast address.
So far, finish to set up in this preferred embodiment the method flow of MBMS session
above-mentionedly added MME, the chain of command trend is BM-SC-MME-MCE-ENB and BM-SC-MME-in the ENB system arranged side by side, also can take two to embodiment four similar modes with embodiment, promptly adopt the mode of solicited message, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.Difference only is: being undertaken by MME alternately between BM-SC and the MCE, and MME sends to MCE and common ENB with the IP multicast address of MBMS GW, and MCE sends to ENB in the maximum SFN zone with the IP multicast address of MBMS GW.Provide an example below, please refer to present embodiment for the embodiment of similar other technologies scheme, and the associated description of embodiment two to embodiment four, do not repeat them here.
For example, Figure 18 shows the composition structural representation of present embodiment corresponding to second preferable system of embodiment four described technical schemes.Referring to Figure 18, in the present embodiment, MME is specially to the method for MBMS GW solicited message:
At first, initiate the MBMS session by BM-SC to MME and begin Signalling exchange; Then, to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW, the downlink tunnel information of MBMS GW is sent to BM-SC, and the IP multicast address information of MBMS GW is sent to MCE and common ENB by MME; At last, by MCE the IP multicast address information of MBMS GW is sent to ENB in the maximum SFN zone.So, downlink tunnel information, the ENB that makes BM-SC get access to MBMS GW gets access to the IP multicast address information of MBMS GW, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.
Embodiment seven:
In the present embodiment, the network entity that system comprised is identical with embodiment five, comprising: BM-SC, user entity, MCE, MME and an ENB.In the present embodiment, the MBMS session management entity is: MME and MCE, chain of command trend is: BM-SC-〉MCE-〉ENB and BM-SC-〉MME-〉ENB is arranged side by side.
Present embodiment both can have been taked the one similar pre-configured mode with embodiment, also can take the mode with embodiment two to embodiment four similar solicited messages, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.Be that example is elaborated in pre-configured mode below.
Figure 19 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention seven.Referring to Figure 19, the pre-configured mode of present embodiment can be in BM-SC, or disposes the IP multicast address of the MBMS GW of related service simultaneously in MME and MCE, and disposes the downlink tunnel information of the MBMS GW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; At BM-SC when MME and MCE initiate the MBMS session and begin Signalling exchange, the IP multicast address information of MBMS GW is sent to MME and MCE, the chain of command entity sends to MCE and common ENB with the IP multicast address of MBMS GW, and MCE sends to ENB in the maximum SFN zone with the IP multicast address of MBMS GW;
Also can in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MME and MCE; BM initiates the MBMS session to MME and MCE and begins Signalling exchange, and MME sends to MCE and common ENB with the IP multicast address of MBMS GW, and MCE sends to ENB in the maximum SFN zone with the IP multicast address of MBMS GW;
Can also be in advance in BM-SC the downlink tunnel information of configuration MBMS GW, the IP multicast address information of configuration MBMS GW in ENB like this, just need not BM-SC, MME or MCE the IP multicast address information of MBMS GW is sent to ENB.
When having two IP multicast address, MME and MCE can provide IP multicast address to different classes of ENB respectively according to the mode identical with embodiment one, particularly:
When having two IP multicast address information, two IP multicast address will have corresponding synchronous/asynchronous indication, at this moment, the IP multicast address information corresponding to indication synchronously can be sent to the ENB in the maximum SFN zone; To send to common ENB corresponding to the IP multicast address information of asynchronous indication.Perhaps, also the IP multicast address information corresponding to indication synchronously can be sent to the ENB in the SFN zone, will send to the ENB in the non-SFN zone in the maximum SFN zone corresponding to the IP multicast address information of asynchronous indication; To send to common ENB corresponding to the IP multicast address information of asynchronous indication.
above-mentionedly added MME, the chain of command trend is BM-SC-MCE-ENB and BM-SC-MME-in the ENB system arranged side by side, also can take two to embodiment four similar modes with embodiment, promptly adopt the mode of solicited message, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.Difference only is: BM-SC initiates the MBMS session to MME and MCE respectively and begins Signalling exchange, and MME sends to MCE and common ENB with the IP multicast address of MBMS GW, and MCE sends to ENB in the maximum SFN zone with the IP multicast address of MBMS GW.Below by the embodiment of an example explanation present embodiment corresponding to embodiment two to embodiment four described technical schemes.
For example, Figure 20 shows the composition structural representation of present embodiment corresponding to second preferable system of embodiment two described technical schemes.Referring to Figure 20, in the present embodiment, BM-SC is specially to the method for MBMS GW solicited message:
At first by BM-SC to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW; Then, begin in the Signalling exchange to the MBMS session of MME and MCE initiation at BM-SC, the IP multicast address information of MBMS GW is sent to MME and MCE, initiate the MBMS session by MME and MCE to corresponding ENB again and begin Signalling exchange, the IP multicast address information of MBMS GW is sent to corresponding ENB.In the said method, when only having an IP multicast address information, when having two IP multicast address, BM-SC provides the mode of IP multicast address to MME and MCE, and the mode that MME and MCE provide IP multicast address to ENB as previously mentioned, do not repeat them here.
Embodiment eight:
In the present embodiment, the network entity that system comprised is identical with embodiment one, comprising: BM-SC, user entity, MCE and an ENB.In the present embodiment, the MBMS session management entity is: ENB, the chain of command trend is: BM-SC-〉ENB.
Present embodiment both can have been taked the one similar pre-configured mode with embodiment, also can take the mode with embodiment two to embodiment four similar solicited messages, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.Be that example is elaborated in pre-configured mode below.
Figure 21 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention eight.Referring to Figure 21, this system generally is applied to mixed mode, and promptly ENB is not fixed as the Radio Resource that MBMS keeps specially, and these resources can be used for other business, as common point to point service, PTP.Like this, after ENB receives the Session Start Request that comes from BM-SC, its wireless resource information that can be used for this MBMS is reported MCE, and request MCE determines the composition in SFN zone according to these situations, and with the corresponding ENB of the result notification of resource distribution.
The pre-configured mode of present embodiment can be the IP multicast address of the MBMS GW of configuration related service in BM-SC or ENB, and disposes the downlink tunnel information of the MBMS GW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; When ENB initiates the MBMS session and begins Signalling exchange, the IP multicast address information of the MBMS GW that disposed is sent to ENB at BM-SC;
Also can be in advance in BM-SC the downlink tunnel information of configuration MBMS GW, the IP multicast address information of configuration MBMS GW in ENB like this, just need not BM-SC the IP multicast address information of MBMS GW is sent to ENB.
In this preferred embodiment, the method flow of setting up the MBMS session as shown in figure 22.Referring to Figure 22, this flow process may further comprise the steps:
Step 2201:BM-SC sends Session Start Request to ENB, carries QoS information etc. in this request message.If BM-SC disposes the IP multicast address information of MBMS GW, the IP multicast address information of further in this Session Start Request, carrying MBMS GW then.
Step 2202: each ENB reports wireless resource information to MCE.For example, can report by resource report (Resource Report).
Step 2203:MCE determines the composition of SFN.
Step 2204:MCE returns the result of resource distribution to ENB.For example, can in resource distribution message (Resource Configure), carry the resource distribution result.
Step 2205:ENB joins corresponding IP multicast address.
In this step, if there are two IP multicast address information, then which IP multicast address ENB can determine to join according to whether forming SFN, can certainly be according to whether belonging to maximum SFN zone or which IP multicast address is other standards determine to join.
So far, finish to set up in this preferred embodiment the method flow of MBMS session.
Be BM-SC-in chain of command trend〉in the system of ENB, also can take two to embodiment four similar modes with embodiment, promptly adopt the mode of solicited message, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.Difference only is: BM-SC and ENB rather than MCE carry out the MBMS session and begin Signalling exchange.The embodiment of these technical schemes is with reference to present embodiment, and embodiment two to embodiment four can draw, and do not repeat them here.
Embodiment nine:
In the present embodiment, the MBMS session management entity that system comprised on the basis of embodiment eight described systems, has increased chain of command entity: MME.In the present embodiment, system comprises: BM-SC, user entity, MCE, MME and an ENB.The MBMS session management entity is: MME, the chain of command trend is: BM-SC-〉MME-〉ENB.
Similar with embodiment eight, present embodiment both can have been taked the similar pre-configured mode with embodiment, also can take the mode with embodiment two to embodiment four similar solicited messages, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity.Be that example is elaborated in pre-configured mode below.
Figure 23 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention nine.Referring to Figure 23, the pre-configured mode of present embodiment can be the IP multicast address of the MBMS GW of configuration related service in BM-SC, MME or ENB, and disposes the downlink tunnel information of the MBMS GW of this business correspondence in BM-SC, particularly:
Can in BM-SC, dispose downlink tunnel information and the IP multicast address information of MBMS GW in advance; At BM-SC when MME initiates the MBMS session and begins Signalling exchange, the IP multicast address information of the MBMS GW that disposed is sent to MME, initiate the MBMS session by MME to ENB then and begin Signalling exchange, the IP multicast address information of MBMS GW is sent to corresponding ENB;
Also can in BM-SC, dispose the downlink tunnel information of MBMS GW in advance, the IP multicast address information of configuration MBMS GW in MME; After MME initiated the MBMS session and begins Signalling exchange, MME initiated the MBMS session to ENB and begins Signalling exchange at BM-SC, and the IP multicast address information of MBMSGW is sent to corresponding ENB;
Can also be in advance in BM-SC the downlink tunnel information of configuration MBMS GW, the IP multicast address information of configuration MBMS GW in ENB like this, just need not BM-SC or MME the IP multicast address information of MBMSGW is sent to ENB.
above-mentionedly added MME, the chain of command trend is BM-SC-MME-in the system of ENB, also can expand embodiment two to embodiment four according to embodiment eight described methods, promptly adopt the mode of solicited message, make BM-SC obtain the downlink tunnel information of user entity, the IP multicast address information that ENB obtains user entity, and set up MBMS carrying with user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.
The difference of present embodiment and embodiment eight described technical schemes is: increased network entity: MME between BM-SC and the ENB, promptly BM-SC begins Signalling exchange by MME to ENB initiation MBMS session.After ENB receives that the MBMS session begins the Signalling exchange request,, promptly report wireless resource information etc. to MCE with taking the mode identical to handle with embodiment eight.Provide an example below, please refer to present embodiment for the embodiment of similar other technologies scheme, and the associated description of embodiment two to embodiment four, do not repeat them here.
For example, Figure 24 shows the composition structural representation of present embodiment corresponding to second preferable system of embodiment four described technical schemes.Referring to Figure 24, in the present embodiment, MME is specially to the method for MBMS GW solicited message:
At first, initiate the MBMS session by BM-SC to MME and begin Signalling exchange; Then, to MBMS GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW, the downlink tunnel information of MBMS GW is sent to BM-SC, and the IP multicast address information of MBMS GW is sent to corresponding ENB by MME; By ENB the wireless resource information that it can be used for this MBMS is reported MCE again, request MCE determines the composition in SFN zone according to these situations, and with the corresponding ENB of the result notification of resource distribution.
More than have been described in detail only there being the technical scheme of a user entity in the system by nine embodiment.In actual applications, set up in the system of MBMS session and can comprise two user entities, in this case, can carry out suitable expansion to the various embodiments described above and obtain the corresponding techniques scheme.Be elaborated to there being the technical scheme of two user entities in the system below by several embodiment.In the following description, these two user entities are designated as respectively: MBMS GW and GW.
Embodiment ten:
Present embodiment is expanded on the basis of embodiment two, and the network entity that is comprised in the system is: BM-SC, MBMS GW, GW, MCE and ENB, and the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.In the present embodiment, two user entity MBMSGW and GW provide synchrodata source and non-synchronous data source respectively, are carried out alternately with two user entities respectively by BM-SC, obtain the IP multicast address information and the downlink tunnel information of two user's faces.
Figure 25 is for setting up the composition structural representation of first preferable system of MBMS session in the embodiment of the invention ten.Referring to Figure 25, in the present embodiment, BM-SC is specially to the method for MBMS GW and GW solicited message:
At first, respectively to MBMS GW and GW solicited message, get access to IP multicast address information and the downlink tunnel information of MBMSGW and GW by BM-SC respectively.Here, may also get access to synchronous or asynchronous indication simultaneously corresponding to IP multicast address.If do not get access to synchronous/asynchronous indication, also can indicate one of them user entity that synchronizing function is provided by BM-SC, the synchrodata source promptly is provided, and with this specified notification user entity and MCE.Being designated as the user entity that the synchrodata source is provided needs to carry out simultaneous operation after receiving data, for example, can add timestamp to data.
Then, initiate the MBMS session by BM-SC to MCE and begin Signalling exchange, provide this two IP multicast address to MCE.Here, can provide the synchronous/asynchronous indication corresponding to MCE simultaneously with IP multicast address.Provide different IP multicast address information and corresponding synchronous/asynchronous indication thereof by MCE to different ENB.Here, MCE can not repeat them here the mode that two IP multicast address offer ENB referring to the related description in the previous embodiment.
At last, ENB adds corresponding IP multicast address reception MBMS data.For example, S-ENB1 and S-ENB2 form SFN, and then S-ENB1 and S-ENB2 add the IP multicast address that the synchrodata source is provided; S-ENB3 is because no identical Radio Resource is defined as non-SFN ENB by MCE, and then S-ENB3 adds the IP multicast address in non-synchronous data source.Perhaps, S-ENB3 also can add the IP multicast address in synchrodata source, does not just handle simultaneous operation, like this, when S-ENB3 has corresponding radio resource or other reasons need add SFN the time, can handle immediately synchronously and need not add another IP multicast address again.
In the present embodiment, the first preferred approach flow process of setting up the MBMS session as shown in figure 26.Referring to Figure 26, this flow process may further comprise the steps:
Step 2601:BM-SC is respectively to MBMS GW and GW solicited message.
Step 2602:MBMS GW and GW return IP multicast address information and the downlink tunnel information of MBMS GW and GW self respectively to BM-SC.
In this step, suppose that GW is the non-synchronous data source, the IP multicast address of its distribution is an IP multicast address 1, and MBMS GW is the synchrodata source, and the multicast address of distribution is an IP multicast address 2.
Step 2603:BM-SC sends Session Start Request to MCE, carries QoS information and IP multicast address 1 and IP multicast address 2.
Step 2604:MCE returns response (Session Start Response) to BM-SC.
Step 2605:MCE determines the composition of SFN.
Step 2606:MCE sends to relevant ENB and carries the Session StartRequest of IP multicast address information.
In this step, MCE can provide IP multicast address 1 to common ENB and the ENB that can not form SFN, provides IP multicast address 2 to the ENB that can form SFN.Perhaps, MCE can provide IP multicast address 1 to common ENB, provides IP multicast address 2 to other ENB.
Step 2607:ENB adds operation to corresponding IP multicast address.
So far, finish to set up in the present embodiment the first preferred approach flow process of MBMS session.
Present embodiment also can be expanded on the basis of embodiment one, that is: the beared information with two user entities is configured on BM-SC and/or the MCE.Even can be that the beared information in that BM-SC and/or MCE dispose one of them user entity does not dispose the user entity solicited message of respective carrier information by BM-SC to another.For the embodiment under these situations, can carry out referring to present embodiment, do not repeat them here.
In the present embodiment, get access to the IP multicast address of two user entities at BM-SC after, can provide non-synchronous data source IP multicast address information to MME separately, synchrodata source IP multicast address information is provided or two IP multicast address information are all offered MCE to MCE.System in this case as shown in figure 27.At system shown in Figure 27, the second preferred approach flow process of setting up the MBMS session as shown in figure 28.Referring to Figure 28, this flow process may further comprise the steps:
Step 2801:BM-SC is respectively to MBMS GW and GW solicited message.
Step 2802:MBMS GW and GW return IP multicast address information and the downlink tunnel information of MBMS GW and GW self respectively to BM-SC.
In this step, suppose that GW is the non-synchronous data source, the IP multicast address of its distribution is an IP multicast address 1, and MBMS GW is the synchrodata source, and the multicast address of distribution is an IP multicast address 2.
Step 2803:BM-SC sends Session Start Request to MME, carries QoS information and IP multicast address 1, sends Session Start Request to MCE, carries QoS information and IP multicast address 2, may also carry IP multicast address 1.
Step 2804:MME and MCE return response to BM-SC respectively.
Step 2805:MME sends Session Start Request to common ENB, and IP multicast address 1 is provided.
Step 2806:MCE determines the composition of SFN.
Step 2807:MCE sends to relevant ENB and carries the Session StartRequest of IP multicast address information.
In this step, MCE can provide IP multicast address 1 to common ENB and the ENB that can not form SFN, provides IP multicast address 2 to the ENB that can form SFN.Perhaps, MCE can provide IP multicast address 1 to common ENB, provides IP multicast address 2 to other ENB.
Step 2808:ENB adds operation to corresponding IP multicast address.
So far, finish to set up in the present embodiment the second preferred approach flow process of MBMS session.
Embodiment 11:
In the present embodiment, the network entity that system comprised is identical with embodiment ten, for: BM-SC, MBMS GW, GW, MCE and ENB, the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.
In the present embodiment, two user entity MBMS GW and GW provide synchrodata source and non-synchronous data source respectively.At first, by the first user entity solicited message of BM-SC in two user entities, first user entity obtains, writes down the downlink tunnel information and the IP multicast address information of second user entity in two user entities, then, first user entity is to the entity of solicited message, and promptly BM-SC returns the downlink tunnel information of first user entity and the IP multicast address information of the IP multicast address information and second user entity.
Figure 29 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 11.Referring to Figure 29, in the present embodiment, BM-SC is specially to the method for MBMS GW solicited message:
At first, to MBMS GW solicited message, MBMS GW selects a GW to communicate again by BM-SC, obtains downlink tunnel information and the IP multicast address information of this GW, and the downlink tunnel information of record GW.Usually, GW provides the synchrodata source, after promptly MBMS GW receives the MBMS data from BM-SC, sends data to GW when ENB sends data, and GW does Synchronous Processing after receiving data, as adds timestamp, sends synchrodata to following ENB again.
Then, MBMS GW provides downlink tunnel information and the IP multicast address information of MBMS GW and the IP multicast address information of GW to BM-SC.
By BM-SC two IP multicast address information are begun Signalling exchange by the MBMS session again and send to MCE.
At last, by MCE different classes of according under the SFN, send corresponding IP multicast address or indication ENB adds corresponding IP multicast address to different ENB.
In the present embodiment, also can be by the first user entity solicited message of BM-SC in two user entities, first user entity according to the request of BM-SC to the second user entity solicited message, then, by the entity of first user entity to solicited message, be downlink tunnel information and the IP multicast address information that BM-SC returns first user entity, return the downlink tunnel information and the IP multicast address information of second user entity by second user entity to BM-SC.BM-SC gets access to after the downlink tunnel information and IP multicast address information of two user entities, can handle subsequent process according to the mode identical with BM-SC in the system shown in Figure 29, does not repeat them here.Here, can certainly be other MBMS session management entity to the entity of the first user entity solicited message, do not repeat them here.
Embodiment 12:
Present embodiment is expanded on the basis of embodiment four, and the network entity that is comprised in the system is: BM-SC, MBMS GW, GW, MCE and ENB, and the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.In the present embodiment, two user entity MBMSGW and GW provide synchrodata source and non-synchronous data source respectively, are carried out alternately with two user entities respectively by MCE, obtain the IP multicast address information and the downlink tunnel information of two user entities.
Figure 30 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention 12.Referring to Figure 30, in the present embodiment, MCE is specially to the method for MBMS GW and GW solicited message:
At first, initiate the MBMS session by BM-SC to MCE and begin Signalling exchange, to MBMS GW and GW solicited message, obtain downlink tunnel information and the IP multicast address information of MBMS GW and GW by MCE; Here, may also get access to synchronous or asynchronous indication simultaneously corresponding to IP multicast address.
Then, the downlink tunnel information of MBMS GW and GW is sent to BM-SC, and after the composition of determining SFN, the IP multicast address information of MBMS GW and GW is sent to corresponding ENB by MCE.Here, MCE can not repeat them here the mode that two IP multicast address offer ENB referring to the related description in the previous embodiment.
At last, ENB adds corresponding IP multicast address reception MBMS data.
So, downlink tunnel information, the ENB that makes BM-SC get access to MBMS GW and GW gets access to the IP multicast address information of MBMS GW and/or GW, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.
Embodiment 13:
Present embodiment is the combination of embodiment 11 and embodiment 12 schemes.In the present embodiment, the network entity that system comprised is: BM-SC, MBMS GW, GW, MCE and ENB, and the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.
In the present embodiment, two user entity MBMS GW and GW provide synchrodata source and non-synchronous data source respectively.By the first user entity solicited message of MCE elder generation in two user entities, first user entity obtains, writes down the downlink tunnel information and the IP multicast address information of second user entity in two user entities; Then, first user entity is to the entity of solicited message, and promptly MCE returns the downlink tunnel information of first user entity and the IP multicast address information of the IP multicast address information and second user entity; The downlink tunnel information of two user entities is provided to BM-SC by MCE at last.
Figure 31 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 13.Referring to Figure 31, in the present embodiment, MCE is specially to the method for MBMS GW solicited message:
At first, BM-SC initiates the MBMS session to MCE and begins Signalling exchange, by MCE to the MBMSGW solicited message, MBMS GW selects a GW to communicate again, obtain downlink tunnel information and the IP multicast address information of this GW, and downlink tunnel information and the IP multicast address information of MBMS GW and GW is offered MCE; Here, may also get access to synchronous or asynchronous indication simultaneously corresponding to IP multicast address.
Then, the downlink tunnel information of MBMS GW and GW is sent to BM-SC, and after the composition of determining SFN, the IP multicast address information of MBMS GW and GW is sent to corresponding ENB by MCE.Here, MCE can not repeat them here the mode that two IP multicast address offer ENB referring to the related description in the previous embodiment.
At last, ENB adds corresponding IP multicast address reception MBMS data.
So, downlink tunnel information, the ENB that makes BM-SC get access to MBMS GW and GW gets access to the IP multicast address information of MBMS GW and/or GW, and set up MBMS carrying with corresponding user entity, provide thereby realize meeting the be separated MBMS business of requirement of chain of command and user's face.
Embodiment 14:
Present embodiment will change MCE into by BM-SC to the MBMS of user entity solicited message session management entity on the basis of embodiment 11.In the present embodiment, the entity that system comprised is: BM-SC, MBMS GW, GW, MCE and ENB, and the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.
In the present embodiment, two user entity MBMS GW and GW provide synchrodata source and non-synchronous data source respectively.At first, begin Signalling exchange by MCE according to the MBMS session that BM-SC initiates, the first user entity solicited message in two user entities, first user entity obtains, writes down the downlink tunnel information and the IP multicast address information of second user entity in two user entities, then, first user entity is to the entity of solicited message, and promptly MCE returns the downlink tunnel information of first user entity and the IP multicast address information of the IP multicast address information and second user entity; At last, MCE returns to BM-SC with the downlink tunnel information of first user entity.
Figure 32 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 14.Referring to Figure 32, in the present embodiment, MCE is specially to the method for MBMS GW solicited message:
At first, begin Signalling exchange by MCE according to the MBMS session that BM-SC initiates, to the MBMSGW solicited message, MBMS GW selects a GW to communicate again, obtains downlink tunnel information and the IP multicast address information of this GW, and the downlink tunnel information of record GW.Usually, GW provides the synchrodata source, after promptly MBMS GW receives the MBMS data from BM-SC, sends data to GW when ENB sends data, and GW does Synchronous Processing after receiving data, as adds timestamp, sends synchrodata to following ENB again.
Then, MBMS GW provides downlink tunnel information and the IP multicast address information of MBMS GW and the IP multicast address information of GW to MCE.
By MCE the downlink tunnel information of MBMS GW is sent to BM-SC again.
At last, by MCE different classes of according under the SFN, send corresponding IP multicast address or indication ENB adds corresponding IP multicast address to different ENB.
Embodiment 15:
Present embodiment adopts the mode that is similar to embodiment 12, expands on the basis of embodiment three.The entity that is comprised in the system is: BM-SC, MBMS GW, GW, MCE and ENB, and the MBMS session management entity is: MCE, the chain of command trend is: BM-SC-〉MCE-〉ENB.In the present embodiment, two user entity MBMS GW and GW provide synchrodata source and non-synchronous data source respectively, carry out alternately with two user entities respectively by MCE, obtain the IP multicast address information of two user's faces, and directly downlink tunnel information is provided or joins BM-SC to BM-SC by two user entities.
Figure 33 is for setting up the composition structural representation of the system of MBMS session in the embodiment of the invention 15.Referring to Figure 33, in the present embodiment, MCE is specially to the method for MBMS GW and GW solicited message:
At first initiate the MBMS session to MCE and begin Signalling exchange by BM-SC; Then, respectively to MBMS GW and GW solicited message, obtain the IP multicast address information of MBMS GW and GW, the information of BM-SC is offered MBMS GW and GW, and the IP multicast address information of MBMS GW is sent to corresponding ENB by MCE; At last, by MBMS GW and GW according to the BM-SC information of being obtained to BM-SC provide MBMS GW and GW separately downlink tunnel information or join BM-SC.
In the present embodiment, MCE provides the method for IP multicast address information identical with method in the previous embodiment to ENB, does not repeat them here.
Embodiment 16:
Present embodiment is expanded according to the mode of embodiment 12 to embodiment 15 on the basis of embodiment nine.The entity that comprises in the system of present embodiment has: BM-SC, user entity, MCE, MME and an ENB.The MBMS session management entity is: MME, the chain of command trend is: BM-SC-〉MME-〉ENB.Be to be undertaken alternately with the various embodiments described above difference, obtain the IP multicast address information and the downlink tunnel information of user entity by MME rather than MCE and user entity.Describe below by an example, please refer to enforcement, do not repeat them here for the embodiment of other similar techniques schemes.
Figure 34 is for setting up the composition structural representation of a preferable system of MBMS session in the embodiment of the invention 16.Referring to Figure 34, in the present embodiment, MME is specially to the method for MBMS GW and GW solicited message:
At first, BM-SC initiates the MBMS session to MME and begins Signalling exchange, to MBMS GW and GW solicited message, obtains downlink tunnel information and the IP multicast address information of MBMS GW and GW by MMEFENB; Here, may also get access to synchronous or asynchronous indication simultaneously corresponding to IP multicast address.
Then, by MME the downlink tunnel information of MBMS GW and GW is sent to BM-SC, and the IP multicast address information of MBMS GW and GW is sent to ENB.
By ENB the wireless resource information that it can be used for this MBMS is reported MCE again, request MCE determines the composition in SFN zone according to these situations, and with the corresponding ENB of the result notification of resource distribution.
At last, ENB adds corresponding IP multicast address reception MBMS data.Here, the ENB mode that adds corresponding IP multicast address can not repeat them here referring to the related description in the previous embodiment.
As seen from the above-described embodiment, the disclosed technical scheme of setting up the MBMS session in evolvement network of the embodiment of the invention meets the common recognition that chain of command that the LTE/SAE network reached and user's face are separated.Simultaneously MCE only as the node of a wireless access network, handles the coordination of wireless network resource, does not carry out the control of MBMS signaling, perhaps only to having the ENB that is connected to carry out the signaling controlled function with MCE, is not very high to the Capability Requirement of MCE.In addition, can solid line to the smooth compatibility of the 2G/3G network of existing 3GPP R6/R7.
In technical scheme provided by the present invention, some key technologies are: the MBMS session begins Signalling exchange without user entity, but is directly initiated to chain of command entity, coordination entity or ENB by BM-SC.The beared information of user entity obtains in mode pre-configured, that initiatively send to user entity solicited message or user entity.
In addition, if some ENB may not have multicast protocol, as sending adding (Join) or receiving the IP multicast packet, at this situation, solution is: if ENB supports multicast protocol, then send Join, otherwise send Session Start Response to MCE, MME, BM-SC or MBMS GW (depending on that Session Start Request is which node sends to it), wherein carry the tunnel information (as user's face IP address and the TEID of ENB) that this ENB distributes, at last this information is passed to MBMS GW, like this at these ENB, can be by point-to-point reception data, rather than receive data by the IP multicast.
If some router on the network may not possess multicast protocol or BM-SC or ServingSAE GW and differ and receive Join message surely, at this situation, solution is: ENB is except sending Join, also send Session Start Response to MCE or MME or BM-SC or MBMS GW (being decided by that node sends to its), carry the tunnel information (as user's face IP address and the TEID of ENB) that this ENB distributes, be delivered at last on the MBMS GW.MBMS GW at a time between (as receive Join or begin to send data before) check that the ENB address that sends Session Start Response is whether in the address list that Join crosses, if, the address information of then ignoring the SessionStart Response of this ENB sends data according to the IP multicast when sending data.Otherwise, send to this ENB specially by the point-to-point carrying when sending data.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (37)

1. the method that multimedia broadcast/group broadcast service MBMS is provided is characterized in that, may further comprise the steps:
Broadcast/multicast service center BM-SC initiates the MBMS session interaction by the MBMS session management entity to the base-station node ENB of evolution;
Described MBMS session management entity is: the chain of command entity;
Receive the MBMS session interaction of BM-SC initiation at described chain of command entity after, further comprise: described chain of command entity is initiated corresponding M BMS session interaction by coordination entity to ENB;
Perhaps described MBMS session management entity is: the chain of command entity;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Receive the MBMS session interaction of BM-SC initiation at described chain of command entity after, further comprise: described chain of command entity is initiated corresponding M BMS session interaction to coordination entity and common ENB, and the ENB of coordination entity in maximum SFN zone initiates corresponding M BMS session interaction;
Perhaps described MBMS session management entity is: chain of command entity and coordination entity;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Receive the MBMS session interaction of BM-SC initiation in described MBMS session management entity after, further comprise: the chain of command entity is initiated corresponding M BMS session interaction to common ENB, and the ENB of coordination entity in maximum SFN zone initiates corresponding M BMS session interaction.
2. method according to claim 1 is characterized in that: described MBMS session interaction is:
The MBMS session begins Signalling exchange, MBMS session modification Signalling exchange or MBMS session and stops Signalling exchange.
3. the method that MBMS is provided is characterized in that, may further comprise the steps:
BM-SC initiates the MBMS session interaction by the MBMS session management entity to ENB; Described MBMS session management entity is the entity except that user entity;
In described MBMS session interaction, BM-SC obtains the downlink tunnel information of user entity, sets up the MBMS carrying between BM-SC and the user entity; ENB obtains the IP multicast address information of user entity, sets up the MBMS carrying between ENB and the user entity.
4. method according to claim 3 is characterized in that, described BM-SC obtains the downlink tunnel information of user entity, the mode of IP multicast address information that ENB obtains user entity is:
Pre-configured mode or the mode that initiatively sends information to the mode or the user entity of user entity solicited message or pre-configured and the mode that combines to the user entity solicited message.
5. method according to claim 4 is characterized in that, described pre-configured mode is specially:
The downlink tunnel information of configuration of user plane entity and IP multicast address information in BM-SC in advance; At BM-SC when described MBMS session management entity is initiated the MBMS session interaction, the IP multicast address information of user entity is sent to the MBMS session management entity, and the MBMS session management entity sends to corresponding ENB with the IP multicast address information of user entity;
Or, the downlink tunnel information of configuration of user plane entity in BM-SC in advance, the IP multicast address information of configuration of user plane entity in the MBMS session management entity; When the MBMS session management entity was initiated the MBMS session interaction, the MBMS session management entity sent to corresponding ENB with the IP multicast address information of user entity at BM-SC;
Or, the downlink tunnel information of configuration of user plane entity in BM-SC in advance, the IP multicast address information of configuration of user plane entity in ENB.
6. method according to claim 4 is characterized in that, described mode to the user entity solicited message is specially:
BM-SC obtains the downlink tunnel information and the IP multicast address information of user entity to the user entity solicited message; When the MBMS session management entity is initiated the MBMS session interaction, the IP multicast address information of user entity is sent to the MBMS session management entity at BM-SC; The MBMS session management entity sends to corresponding ENB with the IP multicast address information of user entity.
7. method according to claim 4 is characterized in that, described mode to the user entity solicited message is specially:
BM-SC is after the MBMS session management entity is initiated the MBMS session interaction, the MBMS session management entity is to the user entity solicited message, obtain the IP multicast address information of user entity, the information of BM-SC is offered user entity, the IP multicast address information of user entity is sent to corresponding ENB; User entity provides the downlink tunnel information of user entity or sets up the MBMS carrying with BM-SC to BM-SC according to the BM-SC information of being obtained.
8. method according to claim 4 is characterized in that, described mode to the user entity solicited message is specially:
BM-SC is after the MBMS session management entity is initiated the MBMS session interaction, the MBMS session management entity is to the user entity solicited message, obtain the downlink tunnel information and the IP multicast address information of user entity, the downlink tunnel information of user entity is sent to BM-SC, the IP multicast address information of user entity is sent to corresponding ENB.
9. according to each described method of claim 5 to 8, it is characterized in that described MBMS session management entity is: coordination entity.
10. according to each described method of claim 5 to 8, it is characterized in that described MBMS session management entity is: ENB;
After ENB initiated the MBMS session interaction, further comprise: ENB reported wireless resource information to coordination entity at BM-SC, and coordination entity is determined the composition in single frequency network SFN zone, and notifies corresponding ENB with resource distribution.
11. method according to claim 5 is characterized in that, described MBMS session management entity is: the chain of command entity;
Described pre-configured mode further comprises: the downlink tunnel information of configuration of user plane entity in BM-SC in advance, the IP multicast address information of configuration of user plane entity in coordination entity; When the MBMS session management entity was initiated the MBMS session interaction, the MBMS session management entity was initiated corresponding M BMS session interaction to coordination entity at BM-SC, and coordination entity sends to corresponding ENB with the IP multicast address information of user entity.
12., it is characterized in that described MBMS session management entity is: the chain of command entity according to each described method of claim 5 to 8;
Described MBMS session management entity sends to corresponding ENB with the IP multicast address information of user entity and is specially: the chain of command entity sends to corresponding ENB by coordination entity with the IP multicast address of user entity.
13., it is characterized in that described MBMS session management entity is: the chain of command entity according to each described method of claim 5 to 8;
Described MBMS session management entity sends to corresponding ENB with the IP multicast address information of user entity and is specially: the chain of command entity sends to coordination entity and common ENB with the IP multicast address of user entity, and coordination entity sends to ENB in the maximum SFN zone with the IP multicast address of user entity.
14. method according to claim 4 is characterized in that, described MBMS session management entity is: chain of command entity and coordination entity;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Described pre-configured mode is specially: the downlink tunnel information of configuration of user plane entity and IP multicast address information in BM-SC in advance; At BM-SC when chain of command entity and coordination entity are initiated the MBMS session interaction, the IP multicast address information of user entity is sent to chain of command entity and coordination entity, the chain of command entity sends common ENB with the IP multicast address of user entity, and coordination entity sends to ENB in the maximum SFN zone with the IP multicast address of user entity;
Or, the downlink tunnel information of configuration of user plane entity in BM-SC in advance, the IP multicast address information of configuration of user plane entity in chain of command entity and coordination entity; BM-SC initiates the MBMS session interaction to chain of command entity and coordination entity, and the chain of command entity sends to common ENB with the IP multicast address of user entity, and coordination entity sends to ENB in the maximum SFN zone with the IP multicast address of user entity.
15., it is characterized in that described MBMS session management entity is: chain of command entity and coordination entity according to each described method of claim 6 to 8;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Described MBMS session management entity sends to corresponding ENB with the IP multicast address information of user entity and is specially: the chain of command entity sends to common ENB with the IP multicast address of user entity, and coordination entity sends to ENB in the maximum SFN zone with the IP multicast address of user entity.
16., it is characterized in that described MBMS session management entity is: the chain of command entity according to each described method of claim 5 to 8;
At BM-SC after the chain of command entity is initiated the MBMS session interaction, further comprise: the chain of command entity is initiated corresponding M BMS session interaction to ENB, ENB reports wireless resource information to coordination entity, and coordination entity is determined the composition in SFN zone, and notifies corresponding ENB with resource distribution.
17., it is characterized in that the IP multicast address information of described user entity is: an IP multicast address information according to claim 5 to 8,11 or 14 each described methods;
Described ENB receives the MBMS data and is specially: when receiving the MBMS data, the ENB in the SFN zone carries out simultaneous operation, and the ENB in the non-SFN zone does not carry out simultaneous operation; Or all ENB carry out simultaneous operation.
18. according to claim 5 to 8 or 11 each described methods, it is characterized in that, the IP multicast address information of described user entity comprises: two IP multicast address information, and described two IP multicast address correspond respectively to synchrodata source and non-synchronous data source;
Described IP multicast address information with user entity sends to corresponding ENB and is specially: will send to the ENB in the SFN zone corresponding to the IP multicast address information in synchrodata source, will send to the ENB in the non-SFN zone corresponding to the IP multicast address information in non-synchronous data source;
Or, will send to the ENB in the maximum SFN zone corresponding to the IP multicast address information in synchrodata source, will send to common ENB corresponding to the IP multicast address information in non-synchronous data source.
19. method according to claim 18 is characterized in that, the IP multicast address information of described user entity further comprises: the synchronous/asynchronous indication corresponding with described two IP multicast address information;
Described IP multicast address information with user entity sends to corresponding ENB and is specially: described two IP multicast address information are sent to all ENB, ENB according to synchronously/asynchronous indication or pre-configured information or can not form the information of SFN, determine to set up the IP multicast address of described MBMS carrying.
20. method according to claim 14 is characterized in that, the IP multicast address information of described user entity comprises: two IP multicast address information, and described two IP multicast address correspond respectively to synchrodata source and non-synchronous data source;
The ENB that described IP multicast address information with user entity sends in the maximum SFN zone is: will send to the ENB in the maximum SFN zone corresponding to the IP multicast address information in synchrodata source; Or, will send to the ENB in the SFN zone corresponding to the IP multicast address information in synchrodata source, will send to the ENB in the non-SFN zone in the maximum SFN zone corresponding to the IP multicast address information in non-synchronous data source;
Described IP multicast address information with user entity sends to common ENB and is: will send to common ENB corresponding to the IP multicast address information in non-synchronous data source.
21. according to claim 5 or 11 described methods, it is characterized in that, described pre-configured mode is specially: the downlink tunnel information of pre-configured two user entities and/or IP multicast address information, and/or the synchronous/asynchronous indication corresponding with described two IP multicast address information.
22., it is characterized in that according to each described method of claim 6 to 8:
Described mode to the user entity solicited message is specially: respectively to two user entity solicited messages;
Or, the first user entity solicited message in described two user entities, first user entity obtains, writes down the downlink tunnel information and/or the IP multicast address information of second user entity in described two user entities, and first user entity returns the downlink tunnel information of first user entity and/or the IP multicast address information of the IP multicast address information and second user entity to the entity of solicited message;
Or, the first user entity solicited message in described two user entities, first user entity is to the second user entity solicited message, first user entity returns the downlink tunnel information and/or the IP multicast address information of first user entity to the entity of solicited message, and second user entity returns the IP multicast address information and/or the downlink tunnel information of second user entity to the entity of solicited message.
23. method according to claim 22 is characterized in that, the entity of described request information is: BM-SC, chain of command entity, coordination entity or ENB.
24. method according to claim 23 is characterized in that, after BM-SC obtains the downlink tunnel information of user entity, further comprises:
BM-SC specifies a user entity in described two user entities that the synchrodata source is provided, and sends the synchronous/asynchronous indication corresponding with described two user entities to user entity and MBMS session management entity.
25., it is characterized in that described MBMS session interaction is according to claim 3 to 8,11,14 or 20 each described methods:
The MBMS session begins Signalling exchange or MBMS session modification Signalling exchange.
26. the system that MBMS is provided comprises: BM-SC, MBMS session management entity and ENB is characterized in that:
Described BM-SC is used for initiating the MBMS session interaction by the MBMS session management entity to ENB;
Described MBMS session management entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction to ENB;
Described MBMS session management entity is: the chain of command entity;
Described chain of command entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction by coordination entity to ENB;
Perhaps described MBMS session management entity is: the chain of command entity;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Described chain of command entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction to coordination entity and common ENB;
Described coordination entity is used for the MBMS session interaction according to the initiation of chain of command entity, and the ENB in maximum SFN zone initiates corresponding M BMS session interaction;
Perhaps described MBMS session management entity is: chain of command entity and coordination entity;
Described ENB comprises: ENB in the maximum SFN zone and common ENB;
Described chain of command entity is used for the MBMS session interaction according to the BM-SC initiation, initiates corresponding M BMS session interaction to common ENB;
Described coordination entity is used for the MBMS session interaction according to the BM-SC initiation, and the ENB in maximum SFN zone initiates corresponding M BMS session interaction.
27. system according to claim 26 is characterized in that, described MBMS session interaction is:
MBMS session modification Signalling exchange or MBMS session stop Signalling exchange.
28. the system that MBMS is provided comprises: BM-SC, MBMS session management entity, user entity and ENB is characterized in that:
Described BM-SC is used for initiating the MBMS session interaction by the MBMS session management entity to ENB; And be used for obtaining the downlink tunnel information of user entity at described MBMS session interaction, set up and user entity between the MBMS carrying;
Described MBMS session management entity is used for the MBMS session interaction according to the BM-SC initiation, and it is mutual to initiate corresponding M BMS session order to ENB; Described MBMS session management entity is the entity except that user entity;
Described ENB is used for obtaining at described MBMS session interaction the IP multicast address information of user entity, set up and user entity between the MBMS carrying.
29. system according to claim 28 is characterized in that, described BM-SC is used for the downlink tunnel information and/or the IP multicast address information of pre-configured user entity, and provides IP multicast address information to the MBMS session management entity;
Described MBMS session management entity, the IP multicast address information that is used for coming from BM-SC sends to corresponding ENB.
30. system according to claim 28, it is characterized in that described BM-SC is used for to the user entity solicited message, reception comes from the downlink tunnel information and/or the IP multicast address information of user entity, and provides IP multicast address information to the MBMS session management entity;
Described user entity is used for the request according to BM-SC, returns the downlink tunnel information and/or the IP multicast address information of user entity to BM-SC;
Described MBMS session management entity, the IP multicast address information that is used for coming from BM-SC sends to corresponding ENB.
31. system according to claim 28 is characterized in that, described MBMS session management entity is used for the IP multicast address information of pre-configured user entity, and provides described IP multicast address information to corresponding ENB.
32. system according to claim 28 is characterized in that, described MBMS session management entity is used for the MBMS session interaction of initiating according to BM-SC, to the user entity solicited message, and provides the information of BM-SC to user entity; Reception comes from the IP multicast address information of user entity, and provides described IP multicast address information to ENB;
Described user entity is used for the request according to the MBMS session management entity, returns the IP multicast address information of user entity to the MBMS session management entity, and the downlink tunnel information of user entity is provided or sets up the MBMS carrying with BM-SC to BM-SC;
Described BM-SC is used to receive the downlink tunnel information that comes from user entity.
33. system according to claim 28, it is characterized in that, described MBMS session management entity, be used for to the user entity solicited message, reception comes from the downlink tunnel information and/or the IP multicast address information of user entity, and the downlink tunnel information of user entity is provided, the IP multicast address information of user entity is provided to ENB to BM-SC;
Described BM-SC is used to receive the downlink tunnel information and/or the IP multicast address information of the user entity that comes from the MBMS session management entity.
34. system according to claim 28 is characterized in that, described user entity is two;
Described BM-SC, be used for the first user entity solicited message to described two user entities, reception comes from the downlink tunnel information of first user entity of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity, and provides described IP multicast address information to the MBMS session management entity;
Described first user entity, be used for request according to BM-SC, obtain the downlink tunnel information and/or the IP multicast address information of second user entity in described two user entities, write down the downlink tunnel information of second user entity, and return the downlink tunnel information of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity to BM-SC;
Described MBMS session management entity, the IP multicast address information that is used for coming from BM-SC sends to corresponding ENB.
35. system according to claim 28 is characterized in that, described user entity is two;
Described MBMS session management entity, be used for the MBMS session interaction of initiating the first user entity solicited message to described two user entities according to BM-SC, reception comes from the downlink tunnel information of first user entity of first user entity and/or the IP multicast address information of the IP multicast address information and/or second user entity, and the downlink tunnel information of first user entity is provided, the IP multicast address information of first user entity and second user entity is provided to ENB to BM-SC;
Described first user entity, be used for request according to the MBMS session management entity, obtain the downlink tunnel information and/or the IP multicast address information of second user entity in described two user entities, write down the downlink tunnel information of second user entity, and return the downlink tunnel information of first user entity and/or the IP multicast address information of the IP multicast address information and second user entity to the MBMS session management entity;
Described BM-SC is used to receive the downlink tunnel information that comes from the MBMS session management entity.
36., it is characterized in that described MBMS session management entity is: chain of command entity, coordination entity or ENB according to each described system of claim 28 to 35.
37., it is characterized in that described MBMS session interaction is according to each described system of claim 28 to 35:
The MBMS session begins Signalling exchange or MBMS session modification Signalling exchange.
CN2007101080287A 2007-05-08 2007-05-08 System and method for providing multimedia broadcast multicast service Active CN101304550B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2007101080287A CN101304550B (en) 2007-05-08 2007-05-08 System and method for providing multimedia broadcast multicast service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2007101080287A CN101304550B (en) 2007-05-08 2007-05-08 System and method for providing multimedia broadcast multicast service

Publications (2)

Publication Number Publication Date
CN101304550A CN101304550A (en) 2008-11-12
CN101304550B true CN101304550B (en) 2011-10-05

Family

ID=40114217

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007101080287A Active CN101304550B (en) 2007-05-08 2007-05-08 System and method for providing multimedia broadcast multicast service

Country Status (1)

Country Link
CN (1) CN101304550B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101449444B1 (en) * 2010-02-12 2014-10-22 알까뗄 루슨트 Method for processing multimedia broadcast/multicast service session update
CN102905218B (en) * 2011-07-29 2018-01-26 北京三星通信技术研究有限公司 A kind of broadcast service data transmission method
AU2015401354B2 (en) 2015-07-06 2018-12-20 Huawei Technologies Co., Ltd. Evolved multimedia broadcast/multicast service embms system and management method
CN108476384B (en) * 2016-04-01 2021-03-23 华为技术有限公司 Data transmission method and related device
WO2018094693A1 (en) * 2016-11-25 2018-05-31 华为技术有限公司 Data transmission method, device, and system
CN109845216B (en) * 2016-11-29 2020-08-25 华为技术有限公司 Communication method and device
KR102293669B1 (en) * 2017-05-08 2021-08-25 삼성전자 주식회사 Session continuity support for 5g cellular network
CN110061820B (en) * 2018-01-19 2021-11-30 中兴通讯股份有限公司 Address sending method and device, storage medium and electronic device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642130A (en) * 2004-01-08 2005-07-20 华为技术有限公司 Multimedia multicast business registration method
CN1866896A (en) * 2006-06-13 2006-11-22 中国移动通信集团公司 Method for realizing mobile communication network multimedia enhancement service
CN101296404A (en) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 System and method for access to multicast service in next generation mobile communication network structure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642130A (en) * 2004-01-08 2005-07-20 华为技术有限公司 Multimedia multicast business registration method
CN1866896A (en) * 2006-06-13 2006-11-22 中国移动通信集团公司 Method for realizing mobile communication network multimedia enhancement service
CN101296404A (en) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 System and method for access to multicast service in next generation mobile communication network structure

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP-TSGSSA.Multimedia Broadcast/Multicast Service (MBMS)
3GPP-TSGSSA.Multimedia Broadcast/Multicast Service (MBMS) Architecture and functional description.《3GPP TS 23.246 V7.2.0 》.2007, *
Architecture and functional description.《3GPP TS 23.246 V7.2.0 》.2007,

Also Published As

Publication number Publication date
CN101304550A (en) 2008-11-12

Similar Documents

Publication Publication Date Title
KR100943901B1 (en) Method of Sharing Radio Protocol Entity for Broadcasting and Multicast
EP1440537B1 (en) Multicast support in packet switched wireless networks
US8068843B2 (en) Method for increasing system capacity by transmitting control Signal for MBMS data by combining RLC and PDCP messages
CN101304550B (en) System and method for providing multimedia broadcast multicast service
JP4217683B2 (en) Multimedia service method in wireless mobile communication system
US7680109B2 (en) Mobile multipoint service
KR100964684B1 (en) Method for providing broadcast and multicast service in mobile communication system
CN101340355B (en) Implementing method, system and apparatus for multimedia broadcast/multicast service
CN101299828B (en) System and method for providing multimedia broadcast multicast service
KR20050019388A (en) Method of transmitting or receiving packet data and related control information for multimedia broadcasting and multicast service
KR20040040724A (en) Up-link common channel and operation method of it in a mobile radio communication system
KR20050083637A (en) Mbms ptp and ptm channel change
CN101572859A (en) Synchronized method of common control information among network elements
WO2005018116A1 (en) Method for establishing common transport channel for mbms
CN101521850A (en) Transmission method and business switching method of MBMS business resource using information
KR100956817B1 (en) Method of processing packet data and an apparatus thereof
KR100790130B1 (en) Method for Indicating UE's Reception Session Receiving Of Session in Multimedia Broadcast/Multicast System
CN101442711A (en) Feedback method for multimedia broadcast and multicast business information through customer equipment
EP2061266B1 (en) Method, apparatus and system for sending MBMS service in IP load-carrying web
CN101370170A (en) Wireless resource coordination method
CN112566045A (en) Multimedia Broadcast Multicast Service (MBMS) transmission method and equipment
CN101141787A (en) Method of implementing multicast channel establishment, prelogin, release in broadband access system
CN101132392B (en) Single-carrier frequency broadcast system and method for implementing its business transmission
WO2021136655A1 (en) Methods for network node awareness of multicast or broadcast service in telecommunication network and related apparatus
CN101155051B (en) Method for establishing multicast data channel in radio communication system

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
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20081112

Assignee: Apple Computer, Inc.

Assignor: Huawei Technologies Co., Ltd.

Contract record no.: 2015990000755

Denomination of invention: System and method for providing multimedia broadcast multicast service

Granted publication date: 20111005

License type: Common License

Record date: 20150827

LICC Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model