CN101242353A

CN101242353A - Evolving communication system and its communication method

Info

Publication number: CN101242353A
Application number: CNA2007100790359A
Authority: CN
Inventors: 王云贵; 郭小龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-02-09
Filing date: 2007-02-09
Publication date: 2008-08-13
Anticipated expiration: 2027-02-09
Also published as: CN101242353B

Abstract

The invention discloses a progressed communication system and a communication method belonging to the field of wireless communication, which implements MBMS in LTE/SAE architecture. In this invention, MME and UPE locate in different network entities, MME connects with BM-SC by a signaling plane interface, a UPE-containing user plane access gateway connects with BM-SC by a user plane interface. MME is used for MBMS session management of MBMS provided by BM-SC, the user plane access gateway is used for sending MBMS data from BM-SC to a UE by a progressed access network. All MME constitute a MME pool, master MME and slave MME are differentiated in the MME pool, wherein the master MME is used for MBMS session management, and the slave MME is used for bearer service authorizing of UE.

Description

The communication system of evolution and communication means

Technical field

The present invention relates to wireless communication field, particularly the broadcast multi-broadcasting technology under the evolution architecture.

Background technology

Along with mobile communication technology and internet (Internet Protocol, abbreviation " IP ") the continuous development of technology, mobile communication system has experienced global system for mobile communications (Global System for MobileCommunications, abbreviation " GSM "), GPRS (General Packet RadioService, be called for short " GPRS ") network, constantly develop to 3-G (Generation Three mobile communication system) at present.3-G (Generation Three mobile communication system) is a kind ofly can provide polytype and high-quality multimedia service for the user, compatible and can realize global seamless covering with fixed network, also allow the various small portable terminals system that communicates of random time at any time simultaneously.

Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, be called for short " UMTS ") be a kind of third generation cordless communication network technical standard of third generation partner program (3rd Generation Partnership Project is called for short " 3GPP ") tissue definition.The UMTS network is made up of core net and Access Network, and core net comprises circuit domain and packet domain, and circuit domain provides based on Circuit-switched business (for example speech business), and packet domain provides the business based on packet switching (for example Internet (internet) visit).The terminal that the mobile subscriber uses is subscriber equipment (User Equipment is called for short " UE ").Multimedia broadcasting and multicast service (MultimediaBroadcast/Multicast Service, be called for short " MBMS ") are provided in the UMTS network, its bearer service framework as shown in Figure 1:

In MBMS bearer service framework, content supplier (Content Provider) provides multi-cast business data to broadcast multicast services center (Broadcast Multicast-Service Center is called for short " BM-SC "); BM-SC has functions such as service advices, member management, session transmissions, agency's transmission, safety, from the angle of UE, provides the source of IP multicast service.Gateway GPRS supporting node (GGSN) (Gateway GPRS Support Node, be called for short " GGSN ") be the entrance of IP multicast service, interface between it and the BM-SC is Gmb and Gi interface, wherein the Gmb interface is finished the Signalling exchange between GGSN and the BM-SC, is the border of MBMS bearer service network side; Gi interface transmission IP multicast service data etc.GPRS serving GPRS support node (Serving GPRS SupportNode, abbreviation " SGSN ") carries out MBMS bearer service controlled function and provide MBMS to be transferred to universal mobile telecommunications system grounding wireless access network (UMTS TerrestrialRadio Access Network for each independent UE, be called for short " UTRAN ")/the enhancing data wireless access network (GSM EDGE Radio Access Network is called for short " GERAN ") of global system for mobile communications and evolution thereof.Radio Access Network (UTRAN/GERAN) is responsible for efficiently, and the MBMS transmission data arrive the MBMS business domains of appointment.UE is responsible for activation/deactivation MBMS bearer service with receiving multicast business etc.

MBMS divides two kinds of broadcasting service and multicast services, and multicast service comprises signatory (Subscription), service advices (Service announcement), activation of service (Joining)/withdraw from that (Leaving), session begin (Session start)/stop (Session stop), MBMS notifies (MBMS notification), transfer of data processes such as (Data transfer).Broadcasting service comprises that service advices (Service announcement), session begin (Session start)/stop (Session stop), MBMS notifies processes such as (MBMS notification).

At present in 3GPP, each manufacturer's active research long-term evolving network (Long Term Evolved, be called for short " LTE ")/System Architecture Evolution network (System Architecture Evolved, be called for short " SAE "), the purpose of LTE provides a kind of network cheaply that can reduce time delay, raising user data rate, improved power system capacity and covering, use packet switching (Packet Switch is called for short " PS ") territory business, bearer network all is the IP carrying.At present popular a kind of LTE/SAE network architecture is as shown in Figure 2:

SAE has comprised wireless access network (belonging to LTE), the packet-based core networks (belonging to SAE) of evolution, the GPRS core net parts such as (belong to and leave over the UMTS/GPRS network, referring to above-mentioned UMTS network explanation) of evolution.

The wireless access network of evolution mainly contains base station (the Evolved NodeB of evolution, be called for short " ENB ") etc. functional entity, with Mobility Management Entity (Mobility ManagementEntity in the packet-based core networks of evolution, be called for short " MME ")/user entity (User Plane Entity, abbreviation " UPE ") interface that connects is S1, interface is divided into S1-MME and S1-UPE from function, S1-MME mainly carries Non-Access Stratum (Non Access Stratum is called for short " the NAS ") signaling between UE and the MME; S1-UPE finishes the user plane data transfer between UE and the UPE, may also comprise part control signaling message etc.

In the packet-based core networks of evolution, the function of MME is to preserve the MM Context of UE, as user's sign, and mobility management states, positional information etc., and UE authenticated.User's face IAD comprises UPE, 3GPP anchor point, SAE mobile management anchor point and the several functional entitys of SAE packet data network gateway.Anchor point IASA comprises the 3GPP anchor point between connecting system, SAE mobile management anchor point and the several functional entitys of SAE packet data network gateway.

The function of UPE is the entity of idle (IDLE) state UE of termination downlink data, triggers paging simultaneously, preserves user's face context of UE, as the IP address of UE and routing iinformation etc.Interface between MME and the UPE is S11, is responsible for communicating by letter between MME, the UPE, and the mobility management information of UE is mutual, partial session controlled function etc.MME is connected with the 3GPP core by the S3 interface, and the 3GPP anchor point connects the 3GPP core by the S4 interface, is responsible for mobility chain of command and the user face anchor point function of UE between 3GPP system (UMTS and SAE network etc.) respectively.And the SAE anchor point is responsible for the mobility anchor point function of UE between 3GPP and non-3 GPP system (comprising that WLAN (wireless local area network) (Wireless Local Area Network is called for short " WLAN ") 3GPP IP inserts).The SAE packet data network gateway is responsible for user's face anchor point function that UE is linked into Packet Data Network, and the Packet Data Network with the outside communicates by the SGi reference point, has the function of grouping route and forwarding.User's face IAD is also finished functions such as policy and charging enforcement function (Policy and Charging Enforcement Function is called for short " PCEF "), collecting charging information; Local subscribed services device (Home Subscriber Server, be called for short " HSS ") is used for storing user subscription information, and is mutual by carrying out between the packet-based core networks of S6 interface and evolution, transmits the contracting of UE, positional information etc.Policy charging rule function (Policy and Charging RulesFunction, be called for short " PCRF ") finish the policy control decision-making and control correlation function based on flow based charging, mutual by carrying out between the packet-based core networks of S7 interface and evolution, transmission policy control information etc.At present, such scheme the LTE/SAE framework in, the service of MBMS is not provided.

In the MBMS business that existing 3GPP network provides, the radio network controller of wireless access network (Radio Network Controller, abbreviation " RNC ") creates, preserves MBMS UE context, and set up MBMS and be carried to core net (Core Network, be called for short " CN "), CN provides the main process of MBMS business as follows to RNC:

1.MBMS registration/log off procedure: RNC recognizes that UE is professional when interested to certain MBMS, initiates registration process to network, when all UE withdraw from certain MBMS when professional, initiates log off procedure.In this process, RNC foundation/release MBMS business contexts and MBMS RAB thereof.As shown in Figure 3, RNC sends MBMS REGISTRATION REQUEST (MBMS register requirement) message to CN, wherein has cell parameters:

A) MBMS register requirement type (MBMS Registration Request Type), identifier register (register) are still nullified (deregister);

B) Temporary Mobile Group Identity (Temporary Mobile Group Identity is called for short " TMGI "), the multicast sign;

C), also to have the IP multicast address and the APN (Access Point Name is called for short " MBMS APN ") of this TMGI correspondence if MBMS register requirement type is when registration;

D) if transport layer adopts when not having the signaling of connection, also must have overall RNC sign (GlobalRNC-ID).

After CN receives the register requirement of RNC, reply MBMS REGISTRATIONRESPONSE (MBMS registers response) message, refusal (having the register requirement type) or reception MBMS registration for nullifying to RNC.

2.MBMS UE association/remove association process: main effect is that CN provides Active (activation) pattern UE MBMS context to RNC, and UE is associated with on the MBMS bearer service, comprises three kinds of situations:

A) before the MBMS session, in the beginning, session, as the UE that adds certain multicast service (a MBMSUE context is arranged), when its mobility association status changes PMM CONNECTED (the grouping mobile management connects) state into and set up a PS RAB (packet switched wirelss access bearer);

B) before the MBMS session, in the beginning, session, when the UE of a PMM CONNECTED state when the PS of existence RAB adds the MBMS bearer service;

C) in the MBMS session, when a UE transfers to PMM CONNECTED state by MBMS Service Request (MBMS service request) process.

As shown in Figure 4, CN sends MBMS UE LINKING REQUEST (the related request of MBMS UE) message to RNC, has following cell parameters:

A) one or more TMGI tabulations, the MBMS bearer service that sign UE adds or withdraws from;

B) if add the MBMS bearer service, then also has the point-to-point wireless access bearing sign (PTP RAB ID) of UE.

After CN receives the association request of RNC, reply MBMS UE LINKINGRESPONSE (MBMS UE associated response) message to RNC.

3. session begins: CN provides the positional information of idle pulley UE place RA (Routing Area) to RNC, if do not have the MBMS business contexts then set up the MBMS business contexts.As shown in Figure 5, CN sends MBMS Session Start Request (the MBMS session begins) message to RNC, have the session attribute parameter: MBMS bearer service sign (TMGI), service quality (QoS), MBMS service area (MBMS service Area), session identification (Session identifier), the session duration of estimating (estimated session duration), MBMS pattern (broadcast/multicast), MBMS data transmission period (time to MBMS data transfer), the RA tabulation (list of RAs) at idle condition UE place etc.Wherein base station controller (Base Station Controller is called for short " BSC ")/RNC for the broadcast bearer business will create a MBMS bearer context.The RNC store session is in the MBMS bearer context.The MBMS bearer context is changed to Acitve (activation) state, and replys MBMS Session Start Response (the MBMS session begins response) message, and have Iu loading end address information to CN.Wherein, begin in the request in session, above-mentioned session begins to have RA List of IdleMode UEs (route area list of idle pulley UE) cell in the request, have at least a RNC to go up RA in this tabulation so, otherwise RNC will not set up the MBMS carrying.This parameter is similar in the session updates process, carries to set up or to discharge MBMS.

But, CN only adds up the UE of idle pulley and notifies RNC, UE for enable mode need be added up (CN by MBMS UE association/go association process to provide support) voluntarily by RNC, and, the UE mobility management states changes, UE adds/withdraw from multicast etc. all needs CN notice RNC to carry out alternately, has increased signaling traffic load.

Simultaneously, LTE is the another one wireless communication system that the 3GPP tissue is born, adopt OFDM (Orthogonal Frequency Division Multiplexing is called for short " OFDM ") technology, thereby reach the speed that is issued to 100Mbps in the 20MHZ bandwidth.Because the importance of MBMS business, LTE research at the beginning, just MBMS as one of the business that must support, for this business of more effective support, the 3GPP tissue proposes to support the MBMS business with special carrier, the high speed business of TV class particularly, the characteristics of special carrier are: in this carrier wave on MBMS transmission business, relevant unicast service does not transmit.Under some scene, special carrier does not have special ascending physical signal resource, and this have only the scene of downlink resource to be called independent descending carrier.What also have proposition in addition is Multiplexing Carrier, has both transmitted also MBMS transmission business of unicast service.Therefore, if on the wireless access network node of evolution, preserve all MBMS UE contexts, will cause the waste of memory space.

Summary of the invention

The technical problem underlying that embodiment of the present invention will solve provides a kind of communication system and communication means of evolution, makes and can realize MBMS in the LTE/SAE framework.

For solving the problems of the technologies described above, embodiments of the present invention provide a kind of communication system of evolution, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise Mobility Management Entity MME and at least one user's face IAD of at least one chain of command, system also comprises at least one broadcast multicast services center BM-SC, MME is connected with BM-SC by the signaling plane interface, and user's face IAD is connected with BM-SC by interface in the user plane;

Multimedia broadcasting and multicast service MBMS that MME is used for BM-SC is provided carry out the MBMS session management;

User's face IAD is used for and will sends to user equipment (UE) from the MBMS data of the BM-SC Access Network by evolution.

Embodiments of the present invention also provide a kind of communication system of evolution, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise anchor point IASA between the user entity UPE of MME, at least one user's face of at least one chain of command and connecting system, each MME forms the MME pond, each UPE forms the UPE pond, system also comprises at least one BM-SC, and the MME pond is connected with BM-SC by IASA with the UPE pond;

It is main MME that a MME is arranged in the MME pond, the MBMS that is used for BM-SC is provided carries out the MBMS session management, and from the UPE pond, select a UPE, to send to UE from the MBMS data of BM-SC Access Network by this UPE by evolution, other MME is from MME, is used for the UE that participates in the MBMS that BM-SC provides is carried out the bearer service mandate.

Embodiments of the present invention also provide a kind of MBMS session start method, comprise following steps:

BM-SC sends session to MME and begins request message;

MME notifies user's face IAD and radio access network entity MBMS session to begin after the session of receiving BM-SC begins request message;

User's face IAD and radio access network entity are created the carrying of this MBMS after knowing that the MBMS session begins.

Embodiments of the present invention also provide a kind of MBMS service activation method, after MME receives that UE is used to add the request message of MBMS, create MBMS UE context, send the request message that is used for the MBMS mandate to BM-SC or IASA;

MME receives and has whether comprise indication MME be the response message that the MBMS of the information of main MME indication authorizes;

If the MME that indication information is is main MME, and do not create the MBMS bearer context of MBMS bearer service as yet, send the MBMS login request message, create the MBMS bearer context of this MBMS bearer service;

If the MME that indication information is is from MME, and do not create the MBMS associated context of MBMS bearer service on this MME as yet, perhaps the TA at UE place is not within existing TA tabulation, then be used for MBMS context-sensitive request message, create the MBMS associated context of this MBMS bearer service to main MME transmission.

BM-SC begins request message to main MME or by IASA to main MME transmission session;

Main MME is after receiving that session begins request message, from user's face IAD pond or UPE pond, select user's face IAD or UPE, and user's face IAD of selecting returned to the service bearer of setting up MBMS between this BM-SC or this user's face IAD and this BM-SC, perhaps, the UPE that selects is returned to this BM-SC by IASA;

Main MME notifies all corresponding in the tracing area list of selected user's face IAD or UPE and MBMS evolution base station nodes, and the MBMS session begins;

User's face IAD or UPE and evolution base station node are created the carrying of this MBMS after knowing that the MBMS session begins.

Embodiments of the present invention also provide a kind of MBMS register method, comprise following steps:

Knowing the potential reception user who has MBMS from MME, and be somebody's turn to do when from MME, not creating the associated context of this MBMS as yet, sending MBMS context relation request message to main MME;

Main MME is receiving MBMS context relation request message, or when knowing potential the receptions user who has this MBMS, if do not create the MBMS bearer context of this MBMS bearer service on this main MME as yet, then to BM-SC or IASA transmission MBMS login request message;

If main MME sends the MBMS login request message to IASA, and do not create the MBMS bearer context of MBMS bearer service on this IASA as yet, then this IASA sends the MBMS login request message to BM-SC.

Embodiment of the present invention compared with prior art, the main distinction and effect thereof are:

MME is positioned at different network entities with UPE, and MME is connected with BM-SC by the signaling plane interface, and the user's face IAD that comprises UPE is connected with BM-SC by interface in the user plane.The MBMS that MME is used for BM-SC is provided carries out the MBMS session management, and user's face IAD is used for and will sends to UE from the MBMS data of the BM-SC Access Network by evolution.Make and in the LTE/SAE framework, can realize MBMS.

Each MME forms the MME pond, and each user's face IAD is formed user's face IAD pond, distinguishes the scheme of principal and subordinate MME in the MME pond, has solved following problem:

1) all MME that UE connected ENB nodes in all LTE networks that add same MBMS send repeatedly Session Start (session begins), cause ENB may repeat in a large number to receive, and have set up redundant signaling and have connected.

2) all MME that UE connected that add same MBMS select user face nodes in user's face IAD pond, can not guarantee to choose same user face nodes, cause BM-SC to send redundant user face data, set up redundant being connected between a plurality of user's face IADs and the ENB to a plurality of user's face IADs.

By select user's face IAD by main MME, can keep original APN choice mechanism, and make and in a MBMS business, set up optimum user's face route, proof load equilibrium in whole evolvement network.And, preserve the MBMS bearer context by main MME, can reduce the synchronizing process between BM-SC and all MME, all MME and all ENB.In addition, carry out association between the master and slave MME, back up easily and recover, prevent Single Point of Faliure.

UPE also can separate with IASA (anchor point between connecting system), and each MME forms the MME pond, each UPE forms the UPE pond.The MME pond is connected with BM-SC by IASA with the UPE pond, it is main MME that a MME is arranged in the MME pond, the MBMS that is used for BM-SC is provided carries out the MBMS session management, and from the UPE pond, select a UPE, to send to UE from the MBMS data of BM-SC Access Network by this UPE by evolution, other MME is from MME, is used for the UE that participates in the MBMS that BM-SC provides is carried out the bearer service mandate.For realizing that in the LTE/SAE framework MBMS provides another kind of execution mode.Simultaneously, by in the MME pond, distinguishing principal and subordinate MME, solve redundant signalings a large amount of between MME and the ENB and has been connected, and set up the problem that redundancy is connected between user's face IAD and the ENB.

Description of drawings

Fig. 1 is according to MBMS bearer service configuration diagram in the prior art;

Fig. 2 is according to LTE/SAE network architecture schematic diagram in the prior art;

Fig. 3 is according to MBMS registration/log off procedure flow chart in the prior art;

Fig. 4 is according to MBMS UE association in the prior art/go association process flow chart;

Fig. 5 begins flow chart according to MBMS session in the prior art;

Fig. 6 is the communication system framework schematic diagram according to the evolution of first embodiment of the invention;

Fig. 7 is the MBMS service activation method flow chart according to second embodiment of the invention;

Fig. 8 is the MBMS session start method flow chart according to third embodiment of the invention;

Fig. 9 is the MBMS session start method flow chart according to four embodiment of the invention;

Figure 10 is the MBMS register method flow chart according to fifth embodiment of the invention;

Figure 11 is the MBMS session method of shutting down flow chart according to sixth embodiment of the invention;

Figure 12 is the MBMS cancellation method flow chart according to seventh embodiment of the invention;

Figure 13 is the MBMS service deactivation method flow chart according to eighth embodiment of the invention;

Figure 14 is the communication system framework schematic diagram according to the evolution of ninth embodiment of the invention;

Figure 15 carries out MBMS service activation method flow chart according to the last UE of the main MME of tenth embodiment of the invention;

Figure 16 is going up UE from MME and carry out MBMS service activation method flow chart according to eleventh embodiment of the invention;

Figure 17 is the flow chart according to MBMS registration process in the thirteenth embodiment of the invention;

Figure 18 is the flow chart according to MBMS log off procedure in the fifteenth embodiment of the invention;

Figure 19 is the communication system framework schematic diagram according to the evolution of sixteenth embodiment of the invention.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.

First execution mode of the present invention relates to the communication system of evolution, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise MME and at least one user's face IAD of at least one chain of command, with at least one BM-SC, MME is connected with BM-SC by the signaling plane interface, and user's face IAD is connected with BM-SC by interface in the user plane.The MBMS that MME is used for BM-SC is provided carries out the MBMS session management, and user's face IAD is used for and will sends to UE from the MBMS data of the BM-SC Access Network by evolution.

The framework of this system as shown in Figure 6.Below this framework is described.

The SGmb reference point connects MME and BM-SC, MME is responsible for the MBMS conversation management functional, preserve MBMS UE context and MBMS bearer context, carry out user's relevant control signaling and MBMS bearer service control signaling by the SGmb reference point with wide BM-SC, comprise activation of service (subscriber authorisation), deexcitation (user withdraws from) process; The MBMS session begins/stopped process etc.; And carry out the MBMSUE context and the MBMS bearer context is synchronous, QoS configuration etc.

The SGi reference point connects user's face IAD and BM-SC, in the packet-based core networks of evolution, exists one or more user's face IADs can be connected to BM-SC, and user's face IAD is responsible for user face data, is distributed to UE from BM-SC route MBMS data.Make and in the LTE/SAE framework, can realize MBMS.In addition, MBMS UE context and MBMS bearer context are kept among the MME, the user's face IAD that comprises UPE is preserved the MBMS bearer context, and need not to preserve the MBMSUE context, so that effective conserve system resources.

The framework that present embodiment is separated with MME based on user's face IAD certainly, also needs other requisite functional entitys in the LTE/SAE framework in this system, HSS for example, and PCRF etc., since less with the correlation of present embodiment, do not repeat them here.

Second execution mode of the present invention relates to the MBMS service activation method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in Figure 7.

In step 701, UE is registered to network, and this UE has set up default IP carrying, or has activated a session management related context for the MBMS business, and this session management related context is kept in MME and/or the user's face IAD.

In step 702, UE is on the session management related context of default IP carrying or activation, send multicast join message, as IPv4IGMP (Internet Group Management Protocol of internet protocol version four) or IPv6MLD Joining (multicast listener discovery of IPv 6 adds), this multicast join message has specific I P multicast address, shows that its preparation receives specific multicast MBMS bearer service.

In step 703, user's face IAD sends the MBMS authorization request message to BM-SC, and to obtain making UE receive the mandate of data, the BM-SC return authorization responds, and has the APN of Authorization result and MBMS business.Be not authorized to receive the MBMS data if point out UE in the MBMS authorization response, then the entire process flow process finishes, and does not have further message.This step is an optional step, preserves the collocation strategy of IP multicast address and BM-SC etc. on MME or the user's face IAD.

In step 704, user's face IAD sends the MBMS notice request to MME, has parameters such as IP multicast address.MME sends the MBMS push-notification-answer to user's face IAD, has cause value, points out whether MBMS UE context activation can be processed.MME is the current registration of the UE MME of (distributing by attaching process, routing region updating (Routeing Area Update is called for short " RAU ") process), preserves the current MM Context of UE (MM Context), for UE sets up default IP carrying.

In step 705, MME sends the message of asking MBMS UE context activation to UE, and request UE activates MBMS UE context, has IP multicast address, the parameters such as APN of MBMS business.

In step 706, after UE received the request message of MME, perhaps UE knew that the professional APN information of this MBMS can initiatively initiate request, create a MBMS UE context, send activation MBMS UE context request message to MME, have IP multicast address, parameters such as the professional APN of MBMS.

In step 707, MME creates MBMS UE context, sends the MBMS authorization request message to BM-SC, to obtain the mandate to this UE; The parameters such as IMSI International Mobile Subscriber Identity (International Mobile SubscriberIdentity, be called for short " IMSI "), MME sign that have UE.BM-SC authorizes UE, creates MBMS UE context, replys authorization response to MME.

In step 708,, then send the MBMS login request message to BM-SC if also do not create the MBMS bearer context of this MBMS bearer service on the MME.Be this MBMS bearer service distribution T MGI if desired, BM-SC will distribute a new TMGI.BM-SC replys the MBMS registration reply message to MME, has the MBMS bearer context information of this MBMS bearer service, and this MME correlated identities is added in the BM-SC upstream and downstream node listing parameter.After MME receives response, create the MBMS bearer context of this MBMS bearer service.If the last existing MBMS bearer context of creating this MBMS bearer service of MME, then this step can be skipped.

In step 709, if the evolvement network core net can provide MBMS operational program to the evolution wireless access network, then this step can be skipped; If be at least the RAB that this UE has set up a packet domain this moment, MME just provides MBMS UE context to radio access network entity, the MBMS UE context in the configuration radio access network entity.Therefore, this step is an optional step.

In step 710, MME sends activation MBMS context to UE and accepts message, has TMGI parameter etc.If occur failure (for example authorization failure etc.) in the said process, suitable cause value is returned in then MME refusal MBMS context activation request, and MME initiates the MBMS deactivation process, and the MBMS UE context of having set up is carried out deexcitation.

In step 711, after UE receives that activating the MBMS context accepts message, reply activation MBMS context to MME and finish message, confirm.

Activation of service process description shown in Figure 7: MME can be that unit adds up with TA (tracking territory) to UE.When MME received session and begins (Session Start), MME sent to all corresponding ENB of corresponding TA tabulation with Session StartRequest message, rather than all ENB.

In addition, in activation of service flow process shown in Figure 7, UE joins request and notifies MME, MME to be forwarded to the BM-SC mandate earlier by user's face IAD, and then request UE activation MBMS UE context, and promptly 705,706 steps may be interchangeable on order with 707,708 steps.

Another situation is, if Gmb reference point signaling separated into two parts is finished when user-dependent Gmb reference point signaling connects BM-SC by MME, the Gmb reference point signaling that bearer service is relevant connects BM-SC by user's face IAD and finishes.A kind of replacement scheme of this activation of service flow process is so: UE joins request and notifies MME, MME to be forwarded to the BM-SC mandate by user's face IAD, and then request UE activates MBMS UE context; When UE activated the MBMS context, MME notified user's face IAD to register BM-SC.Carry out gathering of TA tabulation by user's face IAD.Treat to be forwarded to when session begins corresponding ENB.

The 3rd execution mode of the present invention relates to the MBMS session start method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in Figure 8.

In step 801, BM-SC sends session to MME and begins request message, has session attribute TMGI, QoS, MBMS service area, broadcasting or multicast pattern, downstream node tabulation parameters such as (broadcast modes); For broadcast mode, the last establishment of MME MBMS bearer context is preserved the tabulation of above-mentioned service parameter and downstream node; MME replys response to BM-SC.

In step 802, MME sends session to user's face IAD and begins request message, has session attribute TMGI, QoS, MBMS service area, parameters such as broadcasting or multicast pattern.If in the core net of evolution, adopt IP multicast mode, then also have the IP multicast address that MME distributes in the request.For broadcast mode, user's face IAD is the user's face access gateway node by the MBMS bearer context middle and lower reaches node listing indication of MME.For multicast pattern, user's face IAD is the user's face IAD that is retained on the MME in the activation in the UE context, or user's face IAD of selecting when this step.

In step 803, user's face IAD initiates to create the MBMS load bearing process to BM-SC.For multicast pattern, set up point-to-point between user's face IAD and the BM-SC or based on the carrying of the point-to-multipoint of IP multicast (send IGMP and add message etc.).For broadcast mode, BM-SC understands the information of user's face IAD, and this step is an optional step.

In step 804, if user's face IAD does not have the MBMS bearer context, then create the MBMS bearer context, preserve relevant session attribute, reply session to MME and begin response message.

In step 805, MME sends session to radio access network entity and begins request message, has session attribute TMGI, QoS, MBMS service area, parameters such as broadcasting or multicast pattern.If in the core net of evolution, adopt IP multicast mode, then also have the IP multicast address that MME distributes in the request.For broadcast mode, radio access network entity is created the MBMS bearer context.Radio access network entity is preserved these session attributes.Radio access network entity is replied session to MME and is begun response message.

In step 806, if radio access network entity, the MBMS service bearer between user's face IAD is not also set up, and then carries out the MBMS service bearer and sets up process.If employing tunnel, as wireless universal packet service tunnel protocol (GPRS Tunneling Protocal, be called for short " GTP ") etc. mode, radio access network entity allocation of downlink Tunnel Identifier then, by MME or directly send to user's face IAD, for multicast pattern, this process may be carried out simultaneously with other processes (for example UE carries out in the MBMS activation of service process).If adopt IP multicast mode in the core net of evolution, then wireless access network is initiated adition process (IGMP Joining) by the IP multicast protocol, activates the IP multicast bear.If radio access network entity, the MBMS service bearer between user's face IAD is existing to be set up, and then this step can be skipped.

In step 807, radio access network entity distributes essential Radio Resource to give UE with transferring MBMS service data.

The 4th execution mode of the present invention relates to the MBMS session start method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in Figure 9.

In step 901, BM-SC sends session to MME and begins request message, has session attribute TMGI, QoS, MBMS service area, broadcasting or multicast pattern, downstream node tabulation parameters such as (broadcast modes); For broadcast mode, the last establishment of MME MBMS bearer context is preserved the tabulation of above-mentioned service parameter and downstream node.

In step 902, MME sends session to user's face IAD and begins request message, has session attribute TMGI, QoS, MBMS service area, parameters such as broadcasting or multicast pattern.If in the core net of evolution, adopt IP multicast mode, then also have the private ip multicast address that MME distributes in the request.For broadcast mode, user's face IAD is the user's face access gateway node by the MBMS bearer context middle and lower reaches node listing indication of MME.For multicast pattern, user's face IAD is the user's face IAD that is retained on the MME in the activation in the UE context, or user's face IAD of selecting when this step.

In step 903, if user's face IAD does not have the MBMS bearer context, then create the MBMS bearer context, preserve relevant session attribute, reply session to MME and begin response message.

In step 904, MME replys session to BM-SC and begins response message, for multicast pattern, has the address information of user's face IAD etc.

In step 905, MME sends session to radio access network entity and begins request message, has session attribute TMGI, QoS, MBMS service area, parameters such as broadcasting or multicast pattern.If in the core net of evolution, adopt IP multicast mode, then also have the IP multicast address that MME distributes in the request.For broadcast mode, radio access network entity is created the MBMS bearer context.Radio access network entity is preserved these session attributes.Radio access network entity is replied session to MME and is begun response message.

In step 906, if radio access network entity, the MBMS service bearer between user's face IAD is not also set up, and then carries out the MBMS service bearer and sets up process.If adopt tunnel (GTP etc.) mode, radio access network entity allocation of downlink Tunnel Identifier then, by MME or directly send to user's face IAD, for multicast pattern, this process may be carried out simultaneously with other processes (for example UE carries out in the MBMS activation of service process).If adopt IP multicast mode in the core net of evolution, then wireless access network is initiated adition process (IGMP Joining) by the IP multicast protocol, activates the IP multicast bear.If radio access network entity, the MBMS service bearer between user's face IAD is set up, then can skip this step.

In step 907, radio access network entity distributes essential Radio Resource to give UE with transferring MBMS service data.

The 5th execution mode of the present invention relates to the MBMS register method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in figure 10.

In step 1001, the UE that radio access network entity detects its access is professional when interested to MBMS, if the bearer context of this MBMS business not on it is then initiated the MBMS login request message to MME.

In step 1002, when MME receives the MBMS login request message of radio access network entity, if MME is the MBMS bearer context of this MBMS bearer service not, then create the MBMS bearer context of this MBMS bearer service, and initiate the MBMS login request message to BM-SC; BM-SC preserves the relevant information of MME, accepts the registration of MME, replys registration reply message to MME.

In step 1003, if this MBMS service conversation is in " Active " (activation) state, then the BM-SC initiation session begins process, i.e. flow process shown in Fig. 8 or 9.

In step 1004, MME preserves the relevant information of radio access network entity, and replys the MBMS registration reply message to radio access network entity, if reply registration failure message, then has the cause value of failure.

In step 1005, if this MBMS bearer service has been in state of activation, then MME and/or user's face IAD initiation session begin process.

The 6th execution mode of the present invention relates to MBMS session method of shutting down, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in figure 11.

In step 1101, BM-SC sends session to MME and stops request message, indicates this MBMS bearer service termination; MME replys session to BM-SC and stops response message.

In step 1102, MME stops request message to user's face access gateway node transmission session of MBMS bearer context middle and lower reaches node listing indication, indicates this MBMS bearer service termination.

In step 1103, user's face IAD initiates to discharge the MBMS load bearing process to BM-SC, if based on the carrying of IP multicast, what then send the IP multicast bear withdraws from message (for example IGMPLeaving (withdrawing from)), if bearer context is not in state of activation or bearer service is a broadcast mode on user's face IAD, then this step is an optional step.

In step 1104, user's face IAD discharges the MBMS bearer context, replys session to MME and stops response message.

In step 1105, MME sends session to radio access network entity and stops request message, indicates this MBMS bearer service termination.Radio access network entity is replied session to MME and is stopped response message.

In step 1106, if adopt tunnel (GTP etc.) mode between radio access network entity and user's face IAD, then radio access network entity discharges tunnel context.If adopt IP multicast mode in the core net of evolution, then wireless access network initiates to withdraw from process (IGMPLeaving), deexcitation IP multicast bear by the IP multicast protocol.

Need to prove above-mentioned steps 1102 to step 1104, also can carry out to step 1106 is parallel, do not distinguish sequencing with step 1105.

In step 1107, radio access network entity discharges the wireless network resource of distributing.

The 7th execution mode of the present invention relates to the MBMS cancellation method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in figure 12.

In step 1201a, it is interested in certain MBMS business that radio access network entity finds to no longer include on it any UE, then initiates the MBMS de-registration request message of this MBMS business to MME, to withdraw from this bearer service.

In step 1201b,, then initiate to discharge the MBMS load bearing process if the MBMS bearer context has been in state of activation on the radio access network entity.If adopt tunnel (GTP etc.) mode between radio access network entity and user's face IAD, then radio access network entity discharges tunnel context.If adopt IP multicast mode in the core net of evolution, then wireless access network initiates to withdraw from process (IGMP Leaving), deexcitation IP multicast bear by the IP multicast protocol.If the MBMS bearer context is not in state of activation on the radio access network entity, then skip this step.

In step 1201c, MME will remove in the downstream node list parameter of this radio access network entity sign from its bearer context, and replys MBMS to this radio access network entity and nullify response message.

In step 1202a, the MBMS bearer context middle and lower reaches node listing of finding certain MBMS business as MME is for empty, or without any MBMS UE context to should the MBMS bearer context, then MME initiates MBMS de-registration request message to BM-SC, has the professional APN of IP multicast address and MBMS; BM-SC is with this MME deletion from the downstream node tabulation of MBMS bearer context.

In step 1202b, if this MBMS bearer context middle and lower reaches node listing is empty, perhaps without any MBMS UE context to should the MBMS bearer context; Then this MME initiates to discharge the MBMS load bearing process, discharges the bearer context on MME, the user's face IAD and is bearing resource between user's face IAD and the BM-SC.

Specifically, this MBMS bearer context middle and lower reaches node listing of the last discovery of MME is empty, perhaps without any MBMS UE context to should the MBMS bearer context time, initiate to discharge MBMS to user's face IAD and discharge request message.User's face IAD discharges the bearer context of this MME request and is the bearing resource between user's face IAD and the BM-SC, replys MBMS to MME and discharges response message.

In step 1202c, BM-SC replys to MME and nullifies response message.

The 8th execution mode of the present invention relates to the MBMS anti-activating method, and present embodiment is based on the system architecture of first execution mode, and idiographic flow as shown in figure 13.

In step 1301, UE is at default IP carrying or ordinary groups data protocol (the PacketData Protocol that activates, abbreviation " PDP ") sends multicast on the context and withdraw from message (as IGMP/MLDleave), have specific I P multicast address in this message.

In step 1302, user's face IAD sends MBMS to BM-SC and withdraws from Indication message, and this message has IP multicast address, and the parameters such as IMSI of APN and UE indicate this UE will withdraw from certain MBMS multicast service.BM-SC sends the UE request that removes to user's face IAD, and this request has the professional APN parameter of MBMS of IP multicast address and UE etc., and the professional APN parameter of this MBMS is consistent with the professional APN of MBMS that UE carries out the MBMS activation of service.If preserve the collocation strategy of IP multicast address and BM-SC etc. on MME or the user's face IAD, this step is an optional step.

In step 1303, user's face IAD sends deletion MBMS UE context request to MME, has IP multicast address, parameters such as the professional APN of MBMS.MME sends MBMS deletion response to user's face IAD.

In step 1304, MME sends request MBMS UE context deexcitation message to UE, request UE deexcitation MBMS UE context, and this message has IP multicast address, parameters such as the professional APN of MBMS.

In step 1305, after UE receives request, send deexcitation MBMS UE context request message to MME, this message has IP multicast address, parameters such as the professional APN of MBMS.

In step 1306, if in the LTE/SAE evolvement network, exist PS RAB to connect (being that MME has downloaded this UE context to wireless access network) for this UE between MME and the wireless access network, then MME withdraws from the MBMS business of UE from Indication message and sends to radio access network entity, this message has IP multicast address, the professional APN of MBMS, and/or parameter such as TMGI, indication UE will withdraw from this MBMS business.The MBMS UE context of radio access network entity deletion UE is replied UE to MME and is withdrawed from response message.If in the LTE/SAE evolvement network, the information of UE does not offer wireless network, and then this step is an optional step.

In step 1307, MME sends MBMS to BM-SC and withdraws from Indication message, and this message has parameters such as IMSI.BM-SC deletes the MBMS UE context of this UE, replys to MME and withdraws from response, and MME deletes the MBMS UE context of this UE.

In step 1308, if going up all MBMS UE contexts of the MBMS bearer context correspondence of this MBMS business, deletes MME, then send the MBMS log off procedure to BM-SC.This step is an optional step.

In step 1309, MME sends deexcitation MBMS context to UE and accepts message, the MBMS UE context of this MBMS business of the last deletion of UE.

Be not difficult to find, in the present embodiment, the MBMS session management has comprised MBMS activation of service process, MBMS service deactivation process, MBMS session and has begun process, MBMS session stop procedures, MBMS registration process and MBMS log off procedure, for realizing that at the LTE/SAE framework MBMS provides guarantee.

The 9th execution mode of the present invention relates to the communication system of evolution, the present embodiment and first execution mode are roughly the same, its difference is, in the first embodiment, as long as MME has UE to connect, each MME all provides MBMS business by above-mentioned each flow process for the UE that connects, and in the present embodiment, further distinguishes principal and subordinate MME.

Specifically, as shown in figure 14, each MME forms the MME pond, each user's face IAD is formed user's face IAD pond, and it is main MME that a MME is arranged in the MME pond, is used to carry out the MBMS session management, and from user's face IAD pond, select user's face IAD, to send to UE from the MBMS data of the BM-SC Access Network by evolution by this user's face IAD, other MME is from MME, is used for the UE that participates in the MBMS that BM-SC provides is carried out the bearer service mandate.

Main MME goes up and preserves MBMS UE context and MBMS bearer context, management MBMS session (session begins/session stop procedures), and from user's face IAD pond, select the user face IAD of user's face IAD as MBMS data route.(for multicast pattern, first MME that is registered to BM-SC is main MME to main MME, or MME of static configuration by the BM-SC appointment; For broadcast mode, adopt the mode of static configuration MME).For non-MBMS business, user's face IAD triggers the MME of MBMS carrying foundation as main MME.

From MME, only preserve MBMS UE context, be responsible for the mandate of UE bearer service, related from MME and main MME foundation, associated context is kept at independently from MME or is present in the MBMSUE context, records the list information from MME in the tabulation of the downstream node of MBMS bearer context among the main MME.

Need to prove that in the specific implementation, on main MME, each bearer service is safeguarded a TA tabulation, corresponding to all from MME.Before this MBMS service conversation begins, more do not need to notify LTE network in new capital from all of MME among the TA.When this MBMS service conversation begins, main MME only in this TA tabulation corresponding LTE network node (being ENB) send session and begin request, the concrete session process of beginning will be described herein-after.After this MBMS service conversation begins, only in following two kinds of situations, main MME will initiate renewal process to the LTE of correspondence network node ENB:

1) when having UE to add this MBMS business among the new TA;

2) all withdraw from this MBMS when professional as all UE of a TA, promptly all to notify the UE number this TA of main MME from MME be 0 o'clock.

The detailed process that main MME initiates to upgrade to the LTE network node has dual mode, and a kind of is to adopt session to begin/session stop procedures; Another kind is to adopt the session updates process.

Following elder generation is introduced first kind of mode.If in a new TA, there is UE to add this MBMS when professional, main MME initiates renewal process to the LTE of correspondence network node ENB, then main MME all ENB in this new TA send session and begin request, and initiation session begins process, and the concrete session process of beginning will be described herein-after.If all UE in certain TA withdraw from this MBMS when professional, main MME initiates renewal process to the LTE of correspondence network node ENB, then main MME all ENB in this TA send session and stop request, the initiation session stopped process, and concrete session stop procedures will be described herein-after.

Adopt the session updates procedural mode to be introduced to second kind more below.The session updates process can be by any one realization in following two kinds of processing procedures.

1) main MME sends a session updates request message to ENB, has the bearer service sign of this MBMS business, and new TA tabulation and old TA tabulation.After ENB receives this message, carry out following processing:

If a. the TA at its place belongs to new TA tabulation, and ENB also do not create the MBMS bearer context of this MBMS bearer service, then creates the MBMS bearer context of this MBMS bearer service, and distributes relevant Radio Resource.

If b. the TA at its place belongs to old TA tabulation, and ENB created the MBMS bearer context of this MBMS bearer service, then deletes the MBMS bearer context of this MBMS bearer service, and discharges relevant Radio Resource.

2) main MME all ENB in TA send the session updates request, if in a new TA, there is UE to add this MBMS when professional, main MME initiates renewal process to the LTE of correspondence network node ENB, then has a start (beginning) sign in this session updates request; If all UE in certain TA withdraw from this MBMS when professional, main MME initiates renewal process to the LTE of correspondence network node ENB, then has a stop sign in this session updates request.After ENB receives this session updates request, processing procedure and last similar, if the start sign, and ENB does not also create the MBMS bearer context of this MBMS bearer service, then create the MBMS bearer context of this MBMS bearer service, and distribute relevant Radio Resource.If stop sign, and ENB created the MBMS bearer context of this MBMS bearer service, then deletes the MBMS bearer context of this MBMS bearer service, and discharges relevant Radio Resource.

For the process of the relevant Radio Resource of above-mentioned release, ENB may adopt mode such as timer to lag behind and carry out after a period of time again, begins request to avoid MME to send session immediately again, needs situation about redistributing after causing resource to discharge immediately again.

From MME, create and safeguard a MBMS associated context, remain with the tabulation＜TA of a MBMS bearer service in this context, the UE number＞.When this tabulation changes under following two kinds of situations, need notify main MME from MME:

1) before the MBMS service conversation begins, when beginning, carry out, UE (be in and activate and/or idle condition) joins this MBMS when professional from a new TA;

2) before the MBMS service conversation begins, when beginning, carry out, all UE among the TA (be in and activate and/or idle condition) withdraw from this MBMS when professional.

The tenth execution mode of the present invention relates to the MBMS service activation method, and present embodiment is based on the system architecture of second execution mode, and present embodiment is that main MME goes up the flow process that UE carries out the MBMS activation of service, specifically as shown in figure 15.

Step 1501 is identical to step 706 with step 701 respectively to step 1506, does not repeat them here.

In step 1507, main MME creates MBMS UE context, initiates the MBMS authorization request message to BM-SC, and to obtain the mandate to this UE, this message has the parameters such as IMSI, MME sign of UE.BM-SC authorizes UE, creates MBMS UE context, replys authorization response to MME, has Authorization result in response message, if authorize successfully, then has main MME information.

Then, in step 1508,, and also do not create the MBMS bearer context of this MBMS bearer service on this MME, then send the MBMS login request message to BM-SC if the main MME information of BM-SC indication is this MME.Be this MBMS bearer service distribution T MGI if desired, BM-SC will distribute a new TMGI.BM-SC replys the MBMS registration reply message to MME, has the MBMS bearer context information of this MBMS bearer service, and this MME correlated identities is added in the BM-SC upstream and downstream node listing parameter.After MME receives response, create the MBMS bearer context of this MBMS bearer service.

Step 1509 is identical to step 711 with step 709 respectively to step 1511, does not repeat them here.

Identical based on the MBMS service deactivation method of the system architecture of second execution mode with MBMS service deactivation method based on the system architecture of first execution mode, do not repeat them here.

The 11 execution mode of the present invention relates to the MBMS service activation method, and present embodiment is based on the system architecture of second execution mode, and present embodiment is for going up the flow process that UE carries out the MBMS activation of service from MME, specifically as shown in figure 16.

Step 1601 is identical to step 706 with step 701 respectively to step 1606, does not repeat them here.

In step 1607, create MBMS UE context from MME, initiate the MBMS authorization request message to BM-SC, to obtain the mandate to this UE, this request message has the parameters such as IMSI, MME sign of UE.BM-SC authorizes UE, creates MBMS UE context, replys authorization response to MME, has Authorization result in response message, if authorize successfully, then has main MME information.

In step 1608, if the main MME information of BM-SC indication is not this MME, and also do not create the MBMS associated context of this MBMS bearer service on this MME, perhaps the TA at UE place within existing TA tabulation, does not then send MBMS context relation request message to main MME.The TA information that has this UE place.If main MME goes up also the not MBMS bearer context of this MBMS bearer service, then initiate registration process (as step 1508) to BM-SC.Main MME is to replying MBMS context relation response message from MME, and this is added to the MBMS bearer context of main MME from MME sign and TA information.After receiving response from MME, create the MBMS associated context.

Step 1609 is identical to step 711 with step 709 respectively to step 1611, does not repeat them here.

The 12 execution mode of the present invention relates to the MBMS session start method, present embodiment is based on the system architecture of second execution mode, the MBMS session of present embodiment begins process and MBMS session based on the system architecture of first execution mode, and to begin process roughly the same, its difference is, in the present embodiment, BM-SC only begins request to main MME transmission session.Main MME selects user's face IAD of supporting this MBMS business, and main MME returns selected user's face IAD and gives BM-SC, perhaps sets up the MBMS carrying between this user's face IAD and the BM-SC and is connected.Main MME sends session according to all corresponding ENB in the TA tabulation of preserving for this MBMS is professional and begins request message.Certainly, if after the MBMS session begins, main MME adds this MBMS again, then still can initiate the MBMS session and begin flow process.

When MME recognizes that UE is arranged is professional when interested to certain MBMS, when promptly there is potential reception user in this MBMS, and when not creating the MBMS bearer context of this MBMS bearer service on this MME, will initiate registration process.The 13 execution mode of the present invention relates to the MBMS register method, and present embodiment is based on the system architecture of second execution mode, and idiographic flow as shown in figure 17.

In step 1701, recognize have UE that certain MBMS is served when interested from MME, and when not creating the MBMS bearer context of this MBMS bearer service on this MME, initiate MBMS context relation request message to main MME, this request message has the TA information at UE place and from the parameters such as sign of MME.

In step 1702, main MME recognizes that UE is interested in certain MBMS business, when perhaps receiving the MBMS context relation request message from MME,, then initiate the MBMS login request message to BM-SC if also do not create the MBMS bearer context of this MBMS bearer service on this main MME.After BM-SC receives the register requirement of main MME, the sign of this main MME is joined in the downstream node tabulation, and return the MBMS registration reply message.

In step 1703, main MME is to return MBMS context relation response message from MME.

The 14 execution mode of the present invention relates to MBMS session method of shutting down, present embodiment is based on the system architecture of second execution mode, the MBMS session stop procedures of present embodiment is roughly the same with the MBMS session stop procedures based on the system architecture of first execution mode, its difference is, in the present embodiment, BM-SC only stops request to main MME transmission session.Main MME all corresponding ENB in the TA tabulation of the professional corresponding user's face IAD of this MBMS and this MBMS business send sessions and stop message, notify that their releasing bearings are wireless, Internet resources etc.

When last all UE of MME withdraw from this MBMS business, MME will initiate log off procedure.The 15 execution mode of the present invention relates to the MBMS cancellation method, and present embodiment is based on the system architecture of second execution mode, and idiographic flow as shown in figure 18.

In step 1801, when MME recognizes that all UE withdraw from this MBMS carrying service, initiate related cancel request message to main MME, this request message has this MBMS service identification, parameters such as TA tabulation.After main MME receives request, will delete the tabulation of the downstream node from this MBMS bearer context, and reply related cancellation response from MME to this from MME.

In step 1802, if all UE have withdrawed from service from the relevant TA tabulation of MME, initiation session stopped process so, session stop procedures was done introduction hereinbefore, did not repeat them here.

In step 1803, if finding its all UE, main MME all withdrawed from this MBMS service request, then initiate the MBMS de-registration request to BM-SC.After BM-SC receives request, should delete from the downstream node tabulation by main MME, and reply response, main MME discharges the relevant bearer information of this MBMS business.

Wherein, all withdrawed from this MBMS business if main MME goes up all UE, but also had UE receiving this MBMS service from MME, then main MME does not initiate this log off procedure.For prevent master and slave MME go up between UE information asynchronous, be necessary to carry out other synchronization mechanism.

In step 1804, main MME sends session to user's face IAD of selecting and stops request, and this user's face IAD returns session to this main MME and stops response.

Be not difficult to find, in the present embodiment,, solved following problem by in the MME pond, distinguishing the scheme of principal and subordinate MME:

In addition, select user's face IAD, can keep original APN choice mechanism by main MME, and the proof load equilibrium.And, preserve the MBMS bearer context by main MME, can reduce the synchronizing process between BM-SC and all MME, all MME and all ENB; Carry out association between the master and slave MME, back up easily and recover, prevent Single Point of Faliure.

What deserves to be mentioned is, when the core net of evolvement network provides MBMS professional to the evolution wireless access network, the wireless access network of evolution does not need to preserve MBMS UE contextual information, the evolution core net provides mainly to the evolution wireless access network that session begins, session stop procedures, comprise the session updates process alternatively, and do not need more MBMS service log-on, MBMS UE association/go association process, and reducing Signalling exchange as much as possible, thus conserve system resources.Main procedure declaration is as follows:

1) session begins process: duplicate with the session process that begins in the 3rd or the 12 execution mode, do not repeat them here.The evolution core net is added up according to TA certain MBMS business, add up interested UE (being in the UE of activation and/or Idle state) number, if the UE number is greater than 0 among the TA, then evolution core net all ENB in this TA send session and begin request, and perhaps evolution core net provides the TA tabulation of UE distribution situation to ENB.Go up the process that UE carries out the MBMS activation of service referring to main MME/ from MME.

2) session stop procedures: identical with the session stop procedures in the 6th or the 14 execution mode, do not repeat them here.When session stopped, the evolution core net sent session to ENB and stops request, initiation session stopped process.ENB discharges MBMS bearer context that should the MBMS bearer service, and user's face context resource etc.

3) session updates process: identical with the session updates process of mentioning in the 9th execution mode, do not repeat them here.

The 16 execution mode of the present invention relates to the communication system of evolution, as shown in figure 19, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise the MME of at least one chain of command, the UPE and the IASA (anchor point between connecting system of at least one user's face, as the 3GPP anchor point, SAE mobile management anchor point, the SAE packet data network gateway), each MME forms the MME pond, each UPE forms the UPE pond.That is to say that UPE separates with IASA, the S5 interface between MME/UPE and the IASA transmits the relevant signaling of MBMS.Wherein, MME and UPE can be separated in the different entities, also can realize in an entity, if MME and UPE realize that in an entity it is inner processing procedure that then main MME selects the process of UPE.

This system also comprises at least one BM-SC, and the MME pond is connected with BM-SC by IASA with the UPE pond.It is main MME that a MME is arranged in the MME pond, the MBMS that is used for BM-SC is provided carries out the MBMS session management, and from the UPE pond, select a UPE, to send to UE from the MBMS data of BM-SC Access Network by this UPE by evolution, other MME is from MME, is used for the UE that participates in the MBMS that BM-SC provides is carried out the bearer service mandate.

In the present embodiment, be that example describes in an entity with MME and UPE, as shown in figure 19.

Main MME/UPE goes up and preserves MBMS UE context and MBMS bearer context, carry out the node registration to IASA, main MME/UPE is specified by IASA or BM-SC that (for multicast pattern, the MME/UPE of first registration in the MME pond is main MME/UPE, or MME/UPE of static configuration is main MME/UPE; For broadcast mode, adopt the mode of static configuration master MME/UPE).For non-MBMS service, IASA triggers the MME/UPE of MBMS carrying foundation as main MME/UPE.

From MME/UPE, only preserve MBMS UE context, and, do not need to register to IASA.Related from MME/UPE and main MME/UPE foundation, associated context is kept at independently from MME/UPE or is present in the MBMS UE context, records the list information from MME/UPE in the tabulation of the downstream node of MBMS bearer context among the main MME/UPE.

Be not difficult to find, present embodiment and the 9th execution mode are roughly the same, its difference is, in second execution mode, MME separates with UPE, and UPE and IASA be (being user's face IAD) in same entity, and in the present embodiment, UPE separates with IASA, and MME and UPE are in same entity.Therefore, it is all identical with respective process based on the system architecture of the 9th execution mode that MBMS session in the present embodiment begins process, MBMS session stop procedures, MBMS log off procedure, MBMS deactivation process, difference with, in the present embodiment, Signalling exchange between MME and the UPE is inside story, and the Signalling exchange between MME and the BM-SC need be transmitted by IASA.Modification for MBMS activation and/or MBMS register flow path is mainly as follows:

UE on main MME/UPE, carry out flow process that MBMS activates and flow process shown in Figure 15 roughly the same, its difference is, after the step 1506, after promptly main MME received the activation MBMS context request of UE, main MME/UPE initiated licensing process (may continue to use existing message " Create MBMS UE Context Request/Response " (creating MBMS UE context request/response)), MBMS registration process to IASA.IASA initiates same UE licensing process to BM-SC, if IASA does not set up the MBMS bearer context of this MBMS bearer service, then and then carries out the MBMS registration process after authorizing.Afterwards, the step of execution as step 1509 to shown in the step 1511.

UE is in that carry out flow process that MBMS activates and flow process shown in Figure 16 from MME/UPE roughly the same, its difference is, after the step 1606, after promptly receiving the activation MBMS context request of UE from MME, initiate licensing process (may continue to use existing message " Create MBMS UE Context Request/Response " (creating MBMS UE context request/response)) from MME/UPE to IASA, IASA initiates same UE licensing process to BM-SC.Then, receive the authorization response message of IASA from MME/UPE after, if UE place TA initiates related request upgrade (for example go up the UE statistics TA list information of original not this MBMS business from MME/UPE, or not within this tabulation) from MME/UPE to main MME/UPE.Afterwards, the step of execution as step 1609 to shown in the step 1611.

This shows that present embodiment is by distinguishing principal and subordinate MME in the MME pond, solved redundant signalings a large amount of between MME and the ENB and has been connected, and set up the problem that redundancy is connected between user's face IAD and the ENB.

In sum, in the embodiments of the present invention, MME is positioned at different network entities with UPE, and MME is connected with BM-SC by the signaling plane interface, and the user's face IAD that comprises UPE is connected with BM-SC by interface in the user plane.The MBMS that MME is used for BM-SC is provided carries out the MBMS session management, and user's face IAD is used for and will sends to UE from the MBMS data of the BM-SC Access Network by evolution.Make and in the LTE/SAE framework, can realize MBMS.

Because MME and UPE are separated in different network entities, therefore, MBMS UE context and MBMS bearer context can be kept among the MME, the user's face IAD that comprises UPE is preserved the MBMS bearer context, and need not to preserve MBMS UE context, effectively saved system resource.

The MBMS session management has comprised MBMS activation of service process, MBMS service deactivation process, MBMS session and has begun process, MBMS session stop procedures, MBMS registration process and MBMS log off procedure, for realizing that at the LTE/SAE framework MBMS provides guarantee.

By select user's face IAD by main MME, can keep original APN choice mechanism, and the proof load equilibrium.And, preserve the MBMS bearer context by main MME, can reduce the synchronizing process between BM-SC and all MME, all MME and all ENB.In addition, carry out association between the master and slave MME, back up easily and recover, prevent Single Point of Faliure.

The packet-based core networks of evolution provide by the Access Network to evolution that session begins, session stop procedures, comprise the session updates process alternatively, and do not need more MBMS service registry, MBMS UE association/go association process, MBMS is provided, reduce Signalling exchange as much as possible, saved system resource.

Though pass through with reference to some of the preferred embodiment of the invention, the present invention is illustrated and describes, but those of ordinary skill in the art should be understood that and can do various changes to it in the form and details, and without departing from the spirit and scope of the present invention.

Claims

1. the communication system of an evolution, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise Mobility Management Entity MME and at least one user's face IAD of at least one chain of command, it is characterized in that, described system also comprises at least one broadcast multicast services center BM-SC, described MME is connected with described BM-SC by the signaling plane interface, and described user's face IAD is connected with described BM-SC by interface in the user plane;

Multimedia broadcasting and multicast service MBMS that described MME is used for described BM-SC is provided carry out the MBMS session management;

Described user's face IAD is used for and will sends to user equipment (UE) from the MBMS data of the described BM-SC Access Network by described evolution.

2. the communication system of evolution according to claim 1 is characterized in that, preserves MBMS UE context and MBMS bearer context among the described MME, carries out described MBMS session management according to this MBMS UE context and MBMS bearer context;

Preserve the MBMS bearer context in described user's face IAD, will send to UE from the MBMS data of BM-SC Access Network by described evolution according to this MBMS bearer context.

3. the communication system of evolution according to claim 1 and 2 is characterized in that, each described MME forms the MME pond, and each described user's face IAD is formed user's face IAD pond;

It is main MME that a MME is arranged in the described MME pond, be used to carry out described MBMS session management, and from described user's face IAD pond, select user's face IAD, to send to UE from the MBMS data of described BM-SC Access Network by this user's face IAD by described evolution, other MME is from MME, is used for the UE that participates in the MBMS that described BM-SC provides is carried out the bearer service mandate.

4. the communication system of evolution according to claim 3 is characterized in that, described main MME is specified in the following manner by described BM-SC:

For multicast pattern, first MME that is registered to described BM-SC is main MME, or MME of static configuration is main MME;

For broadcast mode, adopt the mode of static configuration MME to specify main MME.

5. the communication system of evolution according to claim 3 is characterized in that, preserves MBMS UE context and MBMS bearer context among the described main MME, carries out described MBMS session management according to this MBMS UE context and MBMS bearer context;

The described MBMS UE context of from MME, preserving, and related with described main MME foundation, and associated context is kept at independently from MME or is present in the MBMS UE context;

Record described among the described main MME in the tabulation of the downstream node of MBMS bearer context from the MME list information.

6. the communication system of evolution according to claim 5, it is characterized in that, in described associated context of from MME, preserving, remain with the TA and the tabulation of UE number accordingly that comprise described MBMS, when under following two kinds of situations, causing this tabulation to change, give described main MME with this change notification:

Before described MBMS session begins, when beginning, carry out, when the TA of UE outside described tabulation that is in activated state and Idle state joins this MBMS;

Before the MBMS service conversation begins, when beginning, carry out, when all UE that are in activated state and Idle state withdraw from this MBMS among the TA in the described tabulation.

7. the communication system of evolution according to claim 3, it is characterized in that, in described main MME, for each MBMS safeguards that is followed the tracks of a territory TA tabulation, corresponding to all from MME, before this MBMS session begins, forbid and to give the Access Network of described evolution from the update notification of MME in the described TA tabulation; When this MBMS service conversation begins, described main MME only in described TA tabulation corresponding radio access network entity send session and begin request.

8. the communication system of evolution according to claim 7 is characterized in that, after described MBMS session began, described main MME was under following two kinds of situations, and corresponding radio access network entity is initiated renewal process in described TA tabulation:

When having UE to add described MBMS among the TA outside the described TA tabulation;

When all UE of the TA in the described TA tabulation withdraw from described MBMS;

Described main MME one of in the following manner in described TA tabulation corresponding radio access network entity initiate renewal process:

Adopt session begin/session stop procedures, adopt the session updates process.

9. the communication system of an evolution, comprise the Access Network of evolution and the packet-based core networks of evolution, wherein the packet-based core networks of evolution comprise anchor point IASA between the user entity UPE of MME, at least one user's face of at least one chain of command and connecting system, each described MME forms the MME pond, each described UPE forms the UPE pond, it is characterized in that, described system also comprises at least one BM-SC, and described MME pond is connected with described BM-SC by IASA with the UPE pond;

It is main MME that a MME is arranged in the described MME pond, the MBMS that is used for described BM-SC is provided carries out the MBMS session management, and from described UPE pond, select a UPE, to send to UE from the MBMS data of BM-SC Access Network by this UPE by described evolution, other MME is from MME, is used for the UE that participates in the MBMS that described BM-SC provides is carried out the bearer service mandate.

10. the communication system of evolution according to claim 9 is characterized in that,

Described MME and described UPE realize in same physical entity, or realize in different physical entities;

If described MME and described UPE realize that in same physical entity it is inner processing procedure that then described main MME selects the process of UPE.

11. the communication system of evolution according to claim 9 is characterized in that, preserves MBMS UE context and MBMS bearer context among the described main MME, carries out described MBMS session management according to this MBMS UE context and MBMS bearer context;

The described MBMS UE context of preserving from MME carries authorization of service according to this MBMS UE context.

12. the communication system of evolution according to claim 9 is characterized in that, described main MME is specified in the following manner by described IASA or BM-SC:

For multicast pattern, the MME of first registration is main MME, or MME of static configuration is main MME;

13. the communication system according to each described evolution in the claim 9 to 12 is characterized in that, described related from MME and described main MME foundation, associated context is kept at independently from MME or is present in the MBMS UE context;

14. a MBMS session start method is characterized in that, comprises following steps:

BM-SC sends session to MME and begins request message;

Described MME notifies the described MBMS session of described user's face IAD and radio access network entity to begin after the session of receiving described BM-SC begins request message;

Described user's face IAD and radio access network entity are created the carrying of this MBMS after knowing that described MBMS session begins.

15. a MBMS service activation method is characterized in that,

After MME receives that UE is used to add the request message of MBMS, create MBMS UE context, send the request message that is used for the MBMS mandate to BM-SC or IASA;

Described MME receives and has whether comprise indication MME be the response message that the MBMS of the information of main MME indication authorizes;

If described indication information is described MME is main MME, and do not create the MBMS bearer context of described MBMS bearer service as yet, send the MBMS login request message, create the MBMS bearer context of this MBMS bearer service;

If described indication information is described MME is from MME, and do not create the MBMS associated context of described MBMS bearer service on this MME as yet, perhaps the TA at UE place is not within existing TA tabulation, then be used for MBMS context-sensitive request message, create the MBMS associated context of this MBMS bearer service to main MME transmission.

16. MBMS service activation method according to claim 15 is characterized in that,

IASA receives the request message that is used for the MBMS mandate that described MME sends, and described IASA sends to described BM-SC and is used for the request message that MBMS authorizes;

If described IASA does not create the MBMS bearer context of described MBMS bearer service as yet, then after the mandate that obtains described MBMS, send the MBMS login request message to described BM-SC.

17. a MBMS session start method is characterized in that, comprises following steps:

Described main MME is after receiving that described session begins request message, from user's face IAD pond or UPE pond, select user's face IAD or UPE, and user's face IAD of selecting returned to the service bearer of setting up described MBMS between this BM-SC or this user's face IAD and this BM-SC, perhaps, the UPE that selects is returned to this BM-SC by described IASA;

Described main MME notifies all corresponding in the tracing area list of selected user's face IAD or UPE and described MBMS evolution base station nodes, and described MBMS session begins;

Described user's face IAD or UPE and described evolution base station node are created the carrying of this MBMS after knowing that described MBMS session begins.

18. a MBMS register method is characterized in that, comprises following steps:

Described main MME is receiving described MBMS context relation request message, or when knowing the potential reception user who has this MBMS, if do not create the MBMS bearer context of this MBMS bearer service on this main MME as yet, then send the MBMS login request message to BM-SC or IASA;

If described main MME sends the MBMS login request message to IASA, and do not create the MBMS bearer context of described MBMS bearer service on this IASA as yet, then this IASA sends the MBMS login request message to BM-SC.