CN1735065A

CN1735065A - Method for building bearing in multimedia broadcast/multicast service

Info

Publication number: CN1735065A
Application number: CN200410070069.8A
Authority: CN
Inventors: 张海
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2004-08-10
Filing date: 2004-08-10
Publication date: 2006-02-15
Anticipated expiration: 2024-08-10
Also published as: CN100388718C

Abstract

This invention discloses a method to create bearing in MBMS. Wherein, during the activation and deactivation process for MBMS business, using special MBMS context mark to replace MBMS_NSAPI and activate more than eleven MBMS bear businesses and avoid the complexity of hand operation. On this condition, it also uses extended TI mark to identify more than sixteen dual-direction information stream. There is another method of the invention to create bear in MBMS. During the activation and deactivation process for MBMS business, using special MBMS context mark to replace the MBMS_NSAPI and TI; then, it can not only activate more than eleven MBMS bear business, but also identifies more dual-direction information stream.

Description

The method that carrying is set up in the multi-medium broadcast/group broadcast service

Technical field

The present invention relates to multi-medium broadcast/group broadcast service (MBMS) technology, refer to the method that carrying is set up among a kind of MBMS of realization especially.

Background technology

Development along with the 3G (Third Generation) Moblie technology, 3G (Third Generation) Moblie can provide than the more service of high data rate of second generation mobile communication, thereby support the multiple business form, such as: services such as Internet network are downloaded, browsed at a high speed to visual telephone, picture.Wherein, have a class business features to be: can be simultaneously give customized in the wireless network should business all users send, such as: send weather forecast, news film, sports tournament collection of choice specimens or the like.So 3G (Third Generation) Moblie has been introduced the notion of broadcast/group broadcast.

Referring to shown in Figure 1, for an intermediate node, such as node 10, no matter its downstream comprises the node what expectations receive data, and its upstream node always sends a piece of data to this intermediate node; After this intermediate node is received data, the number of nodes that receives data according to its downstream expectation duplicates this data, and distribute this data to the node that each expectation of its downstream receives these data, such as: the node that the expectation of node 10 downstreams receives data comprises node 101 and node 102, and node 10 just duplicates two parts with the data of receiving.Like this, each bar branch of multicast/broadcast business data transmission tree all has only a piece of data to transmit, and takies a transfer resource, and the transfer of data of root node and its downstream node also is like this.The distinctive points of multicast service and broadcasting service only is: multicast service only sends corresponding information to the user who has subscribed to some information, and the broadcasting service then user of all in wireless network sends information.As seen from the above description, provide identical information to a large number of users simultaneously, can greatly save Internet resources by multicast/broadcast is professional.

Fig. 2 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service, as shown in Figure 2, in the existing third generation partner program (3GPP), support that the wireless network architecture of broadcasting/packet service is a broadcasting/packet service server (BM-SC) 201, BM-SC 201 is by Gmb interface or Gi interface and TPF critical point GPRS Support Node (GGSN, Gateway GPRS Support Node) 202 link to each other, and a BM-SC201 can link to each other with a plurality of TPF GGSN 202; TPF GGSN 202 links to each other by Gn/Gp interface and Serving GPRS Support Node (SGSN, Serving GPRS Support Node) 203, and a GGSN 202 can link to each other with a plurality of SGSN 203; SGSN 203 can link to each other with universal mobile telecommunications system (UMTS) land radio access web (UTRAN) 204 by the Iu interface, UTRAN 204 links to each other with user terminal (UE) 206 by the Uu interface then, SGSN 203 also can strengthen wireless access network (GERAN) 205 by Iu/Gb interface and global system for mobile communications (GSM) and link to each other, and GERAN 205 links to each other with UE 207 by Um Interface then.Wherein, GGSN and SGSN belong to the node in the core net in the wireless network (CN).

The processing procedure that MBMS multicast service relates to comprises as shown in Figure 3: subscribe to (Subscription), service declaration (Service announcement), add (Joining), session begins (Session Start), MBMS notice (MBMS notification), transfer of data (Data transfer), conversation end (Session Stop) and withdraw from (Leaving).Wherein, the Subscription process is used for allowing the user subscribe to required MBMS service in advance; Service announcement process is used for by the current service that can provide of BM-SC declaration; The Joining process is a MBMS activating multicast service process, UE is in the Joining process, informing network self is ready to become the member of current multicast group, receive corresponding professional multicast packet, this Joining process can be created the MBMS UE context of record UE information in the UE of network and adding multicast group; In the Session Start process, BM-SC is ready to transfer of data, and informing network is set up the bearing resource of corresponding core net and Access Network; MBMS notification process is used to notify UE MBMS multicast conversation to be about to begin; In the Data transfer process, BM-SC transfers data to UE by the bearing resource that session begins to set up in the process; The bearing resource that Session Stop process is used for Session Start process is set up discharges; The Leaving process makes the subscriber in the group leave multicast group, i.e. user's receiving multicast data no longer, and this process can be with corresponding MBMS UE context deletion.

MBMS activating multicast service process comprises the customizing messages that specific MBMS carries that UE has added for the user that each has activated multicast MBMS bearer service sets up MBMS UE context at UE, SGSN, GGSN and BSC/RNC in the MBMS UE context.When UE adds a MBMS carrying, MBMS UE context is created at UE, SGSN, GGSN, the MBMS UE context of being created is used as the contextual part of UE mobile management (MM) and preserves in UE and SGSN, preserve separately in GGSN, each MBMS that UE adds carries a MBMS UE context.

Referring to shown in the table one, MBMS UE context has and comprises: IP multicast address, APN (APN), Temporary Mobile Group Identity (TMGI), Linked NSAPI and IMSI etc.Wherein, IP multicast address is used to identify the MBMS carrying that a UE has added; The APN that APN has been defined for this IP multicast address; TMGI is a Temporary Mobile Group Identity of distributing to the MBMS carrying; Linked NSAPI is for being removed to carry the NSAPI of the PDP Context of IGMP/MLD signaling by UE; IMSI is a user ID; TI is an event identifier; MBMS NSAPI is used to identify a MBMS UE context.

Parameter	Definition	UE	SGSN	GGSN	RNC	BSC	BM-SC
Parameter	Definition	UE	SGSN	GGSN	RNC	BSC	BM-SC	IP multicast address	The MBMS carrying that UE of IP multicast address sign has added	X	X	X	X	Iu-X Gb-is undetermined	X
APN	The APN that this IP multicast address has been defined	X	X	X	X	Iu-X Gb-is undetermined	X	IP multicast address		X	X	X	X	Iu-X Gb-is undetermined	X
APN	The APN that this IP multicast address has been defined	X	X	X	X	Iu-X Gb-is undetermined	X	TMGI	Distribute to the Temporary Mobile Group Identity of MBMS carrying	X
Linked NSAPI	Remove to carry the NSAPI of the PDP Context of IGMP/MLD signaling by UE	X	X					TMGI		X
Linked NSAPI		X	X					IMSI	The IMSI identifying user	(1)	(1)	X	(2)	Undetermined	X
TI	Event identifier	X	X					IMSI	The IMSI identifying user	(1)	(1)	X	(2)	Undetermined	X
TI	Event identifier	X	X					MBMS_NSAPI	The network layer Service Access point identifies a MBMS UE context	X	X	X

Table one

In the table one, (1) is illustrated among UE and the SGSN, and effectively, the MM context comprises MBMS UE context to IMSI in the MM context; (2) be illustrated among the RNC, effectively, the UE context comprises MBMS UE context to IMSI in the UE context.

In the table one, MBMS_NSAPI is the Network layer Service Access Point Identifier (NSAPI) that is used for MBMS, and general, NSAPI and IMSI are used for the network layer routing function, and a NSAPI/IMSI is to being used to distribute a tunnel destination node sign (TEID).At UE, NSAPI identifies a PDP Service Access point; At SGSN and GGSN, NSAPI sign and the context-sensitive PDP Context of mobile management (MM).

The NSAPI information word is used to identify the Service Access point of GPRS the 3rd layer data transmission, 3GPP 24.008 agreements to the definition of NSAPI as shown in Table 2, NSAPI is made up of two bytes, and first byte is used to show that for NSAPI information element sign (IEI) this field is the value of NSAPI; Low 4 bits of second byte are the NSAPI value, and high 4 bits are 0, and the concrete value of NASPI as shown in Table 3.

8	7	6	5	4	3	2	1
8	7	6	5	4	3	2	1		NSAPI IEI	Byte 1
0	0	0	0	NSAPI				Byte 2	NSAPI IEI	Byte 1

Table two

Bit4 bit3 bit2 bit1 0000 keeps 0001 and keeps 0010 reservations, 0011 reservations, 0100 reservations, 0101 NSAPI, 50110 NSAPI, 60111 NSAPI, 71000 NSAPI, 81001 NSAPI, 91010 NSAPI, 10 1011 NSAPI, 11 1100 NSAPI, 12 1101 NSAPI, 13 1110 NSAPI, 14 1111 NSAPI 15

Table three

From the form of NSAPI as can be seen, the NSAPI value that can select for use for UE only is 5 to 15.The definition of above-mentioned NSAPI is at point-to-point (PTP) transmission, and MBMS_NSAPI in the MBMS business and the use of NSAPI and value are identical.

In addition, for the definition of TI as shown in Table 4, comprise two bytes in 3GPP 24.008 agreements, wherein second byte is expansion, is optionally, do not expand TI and just not uses second byte.5 to 8 bits of first byte of TI are Transaction Identifier TI, are used to distinguish maximum 16 different two-way news streams of a given PD (protocoldiscriminator) and given SAP, and a such message flow is called affairs.This Transaction Identifier TI comprises TI value (TIO) and TI sign (TI flag) two parts, the value of each TI all belongs to same incident, but same incident may be initiated by the not homonymy of interface, so it is which side of interface has been initiated incident that TI flag is used to identify, mark who distributed TI, can get 0 or 1, when the sender of message was the initiator of affairs, the TI flag of message was 0, otherwise was 1.In other words be exactly, TI flag is that 0 expression message sends from producing the TI side, and TI flag is that 1 expression message sends to generation TI side.

The expansion of TI allows a given SAP and given PD are distinguished maximum 256 different bidirectional flows, but the extension mechanism of TI does not generally use.EXT in the table four is equivalent to a sign, and in the current TI extension mechanism, the EXT value is 1; In TI extension mechanism in the future, can TI be further expanded by being 0 with the EXT value.That is to say that if do not use the TI extension mechanism, TI just only has a byte, is 1 if use TI extension mechanism and EXT value, TI is two bytes, is 0 if use extension mechanism and the EXT of TI, and then TI is just more than two bytes.

8	7	6	5	4	3	2	1
8	7	6	5	4	3	2	1		TI flag	TIO	-	-	-	-	Byte 1
EXT	TIE							Byte 2 (optional)	TI flag	TIO	-	-	-	-	Byte 1

Table four

In the MBMS business, NSAPI above-mentioned and TI mainly use in MBMS activation of service flow process and deexcitation flow process.Existing MBMS activation of service flow process may further comprise the steps as shown in Figure 4:

Step 401:SGSN sends a request MBMS context activation message RequestMBMS Context Activation to UE, be used to ask UE to activate a MBMS UE context, carry IP multicast address, APN, Linked NSAPI, Transaction Identifier (TI) in this message at least.Wherein, IP multicast address identifies the business that UE need activate; TI is selected by SGSN, and its value is not by the PDP Context of this other activation of UE and the used value of MBMS UE context.Here, TI can be not expansion, also can be to expand afterwards.

After step 402:UE creates a MBMS UE context, send one to SGSN and activate MBMS context request Activate MBMS Context Request, comprise in this request: IP multicast address, APN, MBMS_NSAPI, MBMS bearing capacity.Wherein, IP multicast address is used to identify the MBMS multicast service that UE starts adding/activation; APN indicates a specific GGSN; The MBMS bearing capacity is used to identify the manageable maximum QoS of UE; MBMS_NSAPI is selected by UE, and its value is not by the PDP Context of this other activation of UE and the used value of MBMS UE context.UE can issue the TI of self with SGSN in selected MBMS_NSAPI and the step 401, is kept in the MBMS UE context of being created.

Step 403:SGSN carries out safety function to current UE, as: to the UE authentication, this step can be omitted.

Step 404:SGSN creates a MBMS UE context that comprises MBMS_NSAPI, comprises TI in the step 401 and the MBMS_NSAPI in the step 402 in this MBMS UE context; And SGSN sends to GGSN and creates MBMS context request Create MBMS Context Request, comprises IP multicast address, APN, MBMS_NSAPI in this request.

Step 405:GGSN and BM-SC carry out Signalling exchange, seek the mandate to UE, if this UE authorizes, this step can be omitted.

Step 406:GGSN creates a MBMS UE context, and sends establishment MBMS context response Create MBMS Context Response to SGSN.In the MBMS UE context that GGSN creates, comprise MBMS_NSAPI.

Step 407: if for this UE has set up at least one packet domain RAB (PS RAB), SGSN provides MBMS UE context to RAN, does not comprise MBMS_NSAPI in this MBMS UE context.

Step 408:SGSN sends an activation MBMS context and accepts message Activate MBMSContext Accept to UE.

Existing MBMS service deactivation flow process may further comprise the steps as shown in Figure 5:

In a single day step 501:SGSN receives MBMS UE context deexcitation request message, the perhaps reason of SGSN oneself, and SGSN sends and contains the deexcitation MBMS context request message DeactivateMBMS Context Request of TI to UE.Wherein, TI is used to identify the MBMS UE context that need be deleted by UE, and the TI in this TI and the MBMS activation of service process in the step 401 is consistent, thereby can identify this MBMS UE context.

Step 502:UE deletes MBMS UE context, and accepts message Deactivate MBMS Context Accept to deexcitation MBMS context that contains TI of SGSN transmission.

Step 503: if currently be used for the MBMS transmission data for this UE has distributed special-purpose Radio Resource, RAN discharges this Radio Resource; If currently distributed shared Radio Resource to be used for the MBMS transmission data, RAN may determine remaining UEs is transferred in the middle of the private resource.Otherwise this step can be omitted.

Step 504: accept the reason of message or SGSN oneself if receive deexcitation MBMS context, the deletion MBMS context request message Delete MBMSContext Request that the SGSN transmission contains MBMS_NSAPI is to having the contextual GGSN of MBMS UE, and MBMS_NSAPI is used to identify this MBMS context.

Step 505:GGSN is according to MBMS_NSAPI deletion MBMS UE context, and sends deexcitation Indication message MBMS UE context of having confirmed successful deexcitation to BM-SC; After BM-SC receives the deexcitation Indication message, deletion MBMS UE context, and to acknowledge message of GGSN transmission.Wherein, the mutual step of GGSN and BM-SC also can be omitted.

Step 506:GGSN sends deletion MBMS context response information Delete MBMSContext Response to SGSN, and the MBMS UE context of having confirmed deexcitation after SGSN receives, is deleted the MBMS UE context of self.

From above-mentioned flow process as can be seen, the existing employing in the scheme that MBMS_NSAPI identifies MBMS UE context, consistent in the definition of MBMS_NSAPI and value space and the original PTP scheme.This is from the step 402 of existing MBMS activation of service process, and the principle that UE obtains MBMS_NSAPI can draw.So, the professional restriction that just can not surpass MBMS_NSAPI value space of the MBMS that the user can activate simultaneously, promptly the user can not activate simultaneously at most and surpass 11 MBMS business.

In original customer service, transmit whenever the user need carry out business, as make a phone call, when surfing the web, activate corresponding PDP Context and carry out the business transmission.After the use, UE discharges respective carrier and NSAPI.Because of the UE capabilities limits, UE can not carry out too many professional transmission simultaneously, carries out 4 at most simultaneously.Under these circumstances, NSAPI value space is 11 to be to satisfy the UE needs fully.

But for MBMS is professional, after the user once activates, for a long time will can deexcitation.The business such as the collection of choice specimens of scoring weather forecast, midday news, e-magazine, the weekend of ordering as the user.After the user once activates, will receive corresponding service at specific time waiting, therefore, the user can activate a lot of such business for a long time, therefore but these professional major parts can not begin simultaneously, can not require UE to have more multipotency power go to receive simultaneously these business.Because such business of the every activation of user will be created a MBMS UE context, take in 11 MBMS_NSAPI value spaces simultaneously.So, because the restriction in MBMS_NSAPI value space, the user just can not activate simultaneously more than 11 MBMS bearer services, otherwise the user needs some business that has activated of manual deexcitation, orders new business again.Such scheme is similar to the TV that has only eight channels in early days a bit, and for the dozens or even hundreds of television channel that TV station can provide, limited subscriber is watched more Polymera significantly.And, adopt manual mode deexcitation MBMS business concerning the user, very to bother, and reduced user's satisfaction; May not select more business for use, thereby reduce the effectiveness of operation of MBMS ISP and Mobile Network Operator because of the complexity of ordering simultaneously.

Summary of the invention

In view of this, main purpose of the present invention is to provide the method that carrying is set up among a kind of MBMS, and the user can be activated simultaneously more than 11 MBMS bearer services, has avoided the complexity of manual deexcitation.

Another object of the present invention is to provide the method that carrying is set up among a kind of MBMS, the user can be activated simultaneously more than 11 MBMS bearer services, and can identify more Bidirectional flow of information simultaneously.

For achieving the above object, technical scheme of the present invention is achieved in that

The method that carrying is set up in a kind of multi-medium broadcast/group broadcast service MBMS, this method comprises MBMS activation of service process and MBMS service deactivation process at least, wherein, MBMS activation of service process may further comprise the steps:

A11.SGSN sends the request MBMS context activation message that carries IP multicast address, APN APN, Linked NSAPI, Transaction Identifier TI to UE; UE receives back establishment MBMS UE context, returns the activation MBMS context request that carries IP multicast address, APN, MBMS bearing capacity to SGSN afterwards;

A12.SGSN creates MBMS UE context, sends the establishment MBMS context request that carries IP multicast address, APN to GGSN afterwards; After GGSN obtains the mandate of BM-SC to current UE, create MBMS UE context, return to SGSN afterwards and create the MBMS context response, SGSN allows UE to activate the MBMS context;

When needs deexcitation MBMS was professional, MBMS service deactivation process may further comprise the steps:

B11.SGSN sends the deexcitation MBMS context request that carries TI to UE, behind the UE deletion MBMS UE context, returns the deexcitation MBMS context that contains TI to SGSN and accepts message;

B12.SGSN will delete the deletion MBMS context request that the contextual GGSN transmission of MBMS UE carries the MBMS Context identifier to having, GGSN deletes corresponding MBMS UE context according to the MBMS Context identifier, and returning response to SGSN, SGSN receives back deletion MBMS UE context.

In the such scheme, described TI is the TI that has extended byte.Described MBMS Context identifier is combined by user ID, IP multicast address, APN; Or combine by user ID, IP multicast address; Or combine by user ID, Temporary Mobile Group Identity TMGI.Wherein, described user ID is IMSI International Mobile Subscriber Identity IMSI.

A21.SGSN sends the request MBMS context activation message that carries IP multicast address, APN APN, Linked NSAPI to UE; UE receives back establishment MBMS UE context, returns the activation MBMS context request that carries IP multicast address, APN, MBMS bearing capacity to SGSN afterwards;

A22.SGSN creates MBMS UE context, sends the establishment MBMS context request that carries IP multicast address, APN to GGSN afterwards; After GGSN obtains the mandate of BM-SC to current UE, create MBMS UE context, return to SGSN afterwards and create the MBMS context response, SGSN allows UE to activate the MBMS context;

B21.SGSN sends the deexcitation MBMS context request that carries the MBMS Context identifier to UE, behind the UE deletion MBMS UE context, returns the deexcitation MBMS context that contains the MBMS Context identifier to SGSN and accepts message;

B22.SGSN will delete the deletion MBMS context request that the contextual GGSN transmission of MBMS UE carries the MBMS Context identifier to having, GGSN deletes corresponding MBMS UE context according to the MBMS Context identifier, and returning response to SGSN, SGSN receives back deletion MBMS UE context.

In the such scheme, described MBMS Context identifier is combined by user ID, IP multicast address, APN; Or combine by user ID, IP multicast address; Or combine by user ID, TMGI.Wherein, described user ID is IMSI.

The method that carrying is set up among the MBMS provided by the present invention has following advantage and characteristics:

1) the present invention makes full use of the MBMS traffic performance, by using distinctive MBMS Context identifier to substitute MBMS NSAPI, the user can be activated simultaneously more than 11 MBMS bearer services, thereby allow the user can order more MBMS bearer services simultaneously easily, improve the satisfaction that the user uses the MBMS business, increase the effectiveness of operation of MBMS ISP and Mobile Network Operator.

2) can adopt different parameter combinations as the MBMS Context identifier, select manyly, more flexible, realize more convenient.

3) the present invention can also be by adopting expansion TI or replace the mode of TI by distinctive MBMS Context identifier, and sign is more than 16 Bidirectional flow of information.

4) the present invention only needs existing UE activation and deexcitation MBMS business procedure are transformed a little, and is very little to the existing procedure influence, is easy to realize.

Description of drawings

Fig. 1 is the transmission principle schematic diagram of multicast service;

Fig. 2 is for supporting the wireless network architecture schematic diagram of broadcasting/packet service;

Fig. 3 is a MBMS multicast service handling process schematic diagram in the prior art;

Fig. 4 is a MBMS activation of service schematic flow sheet in the prior art;

Fig. 5 is a MBMS service deactivation schematic flow sheet in the prior art;

Fig. 6 is MBMS activation of service schematic flow sheet among the present invention;

Fig. 7 is MBMS service deactivation schematic flow sheet among the present invention;

Fig. 8 is MBMS activation of service schematic flow sheet among the present invention;

Fig. 9 is MBMS service deactivation schematic flow sheet among the present invention.

Embodiment

From the occupation mode of existing NSAPI, NSAPI is used to identify the Service Access point of a user in the transmission of GPRS the 3rd layer data under the ptp mode, and identifies a data transmission tunnel from UE to GGSN with user's IMSI.But for the MBMS service bearer, the carrying from BM-SC to RNC is all only distinguished business, the user is not distinguished.MBC also is the RAB (RAB) that each MBMS bearer service is set up, this RAB can be mapped to a plurality of radio bearers (RB), these RB can be the point-to-point dedicated bearers at single UE, also at the shared carrying of a plurality of UE points in sub-district to multiple spot (PTM).Therefore, in the MBMS service application, no matter RNC is downwards PTP transmission or PTM transmission, all no longer has one-to-one relationship between the RB ID at a RAB ID of each user's MBMS_NSAPI, a control RNC (CRNC) definition, different bearer correspondence.That is to say that MBMS_NSAPI no longer has the function in identification data transmission tunnel, and only has the contextual effect of sign MBMS UE.

According to above-mentioned analysis, core concept of the present invention is: cancel the notion of MBMS_NSAPI, identified the MBMS UE context of appointment in the place of needs by the MBMS Context identifier.Here, the MBMS Context identifier can be combination or the combination of user ID and IP multicast address or the combination of user ID and IP multicast address and APN of user ID and TMGI, and wherein, user ID can be IMSI.

Based on thought of the present invention, MBMS activation of service flow process may further comprise the steps as shown in Figure 6 among the present invention:

Step 601:SGSN sends a request MBMS context activation message RequestMBMS Context Activation to UE, be used to ask UE to activate a MBMS UE context, carry IP multicast address, APN, Linked NSAPI, Transaction Identifier (TI) in this message at least.Wherein, IP multicast address identifies the business that UE need activate; TI is selected by SGSN, and its value is not by the PDP Context of this other activation of UE and the used value of MBMS UE context.Here, TI can be not expansion, also can be to expand afterwards.

After step 602:UE creates a MBMS UE context, send one to SGSN and activate MBMS context request Activate MBMS Context Request, comprise in this request: IP multicast address, APN, MBMS bearing capacity.Wherein, IP multicast address is used to identify the MBMS multicast service that UE starts adding/activation; APN indicates a specific GGSN; The MBMS bearing capacity is used to identify the manageable maximum QoS of UE.Here, UE no longer selects and preserves NSAPI, is kept in the MBMS UE context of being created but UE can issue SGSN in the step 601 TI of self.

Step 603:SGSN carries out safety function to current UE, as: to the UE authentication, this step can be omitted.

Step 604:SGSN creates a MBMS UE context, comprises the TI in the step 601 in this MBMS UE context, and SGSN sends to GGSN and creates MBMS context request Create MBMSContext Request, comprises IP multicast address, APN in this request.

Step 605:GGSN and BM-SC carry out Signalling exchange, seek the mandate to UE, if this UE authorizes, this step can be omitted.

Step 606:GGSN creates a MBMS UE context, and sends establishment MBMS context response Create MBMS Context Response to SGSN.In the MBMS UE context that GGSN creates, do not comprise MBMS_NSAPI.

Step 607: if for this UE has set up at least one packet domain RAB (PS RAB), SGSN provides MBMS UE context to RAN, does not comprise MBMS_NSAPI in this MBMS UE context.

Step 608:SGSN sends an activation MBMS context and accepts message Activate MBMSContext Accept to UE.

Owing to no longer contain NSAPI in the above-mentioned MBMS activation of service flow process, so above-mentioned activation process also no longer relates to distribution, preservation and the use at each user's NSAPI.

Existing MBMS service deactivation flow process may further comprise the steps as shown in Figure 7:

In a single day step 701:SGSN receives MBMS UE context deexcitation request message, the perhaps reason of SGSN oneself, and SGSN sends and contains the deexcitation MBMS context request message DeactivateMBMS Context Request of TI to UE.Wherein, TI is used to identify the MBMS UE context that need be deleted by UE, and the TI in this TI and the MBMS activation of service process in the step 601 is consistent, thereby can identify this MBMS UE context.

Step 702:UE deletes MBMS UE context, and accepts message Deactivate MBMS Context Accept to deexcitation MBMS context that contains TI of SGSN transmission.The TI here is used to identify the deleted MBMS UE of UE context.

Step 703: if currently be used for the MBMS transmission data for this UE has distributed special-purpose Radio Resource, RAN discharges this Radio Resource; If currently distributed shared Radio Resource to be used for the MBMS transmission data, RAN may determine remaining UEs is transferred in the middle of the private resource.Otherwise this step can be omitted.

Step 704: accept the reason of message or SGSN oneself if receive deexcitation MBMS context, the deletion MBMS context request message DeleteMBMS Context Request that the SGSN transmission contains MBMS UE Context identifier is to having the contextual GGSN of MBMS UE, and described MBMS UE Context identifier can be used to identify the deleted MBMS UE context of needs.

Step 705:GGSN is according to MBMS UE Context identifier deletion corresponding M BMS UE context, and sends deexcitation Indication message MBMS UE context of having confirmed successful deexcitation to BM-SC; After BM-SC receives the deexcitation Indication message, deletion MBMS UE context, and to acknowledge message of GGSN transmission.Wherein, the mutual step of GGSN and BM-SC also can be omitted.

Step 706:GGSN sends deletion MBMS context response information Delete MBMSContext Response to SGSN, and the MBMS UE context of having confirmed deexcitation after SGSN receives, is deleted the MBMS UE context of self.

In the step 704,705 of MBMS service deactivation process, described MBMS UE Context identifier can or be user ID+IP multicast address or for user ID+TMGI for user ID+IP multicast address+APN.Wherein, user ID can be IMSI.So, SGSN will carry user ID and MBMS Context identifier two parts information at least in the step 704 in the message that GGSN sends, such as: carry IMSI, IP multicast address, APN; Perhaps carry IMSI, IP multicast address; Perhaps carry IMSI, TMGI.

In order to make TI can identify more Bidirectional flow of information, can only adopt the TI after the expansion, so can identify 256 or more Bidirectional flow of information.Exactly concrete: value is carried out in the 1-7 position of TI second byte in the use table four, and the value of the first byte 5-7 position is invalid.The value of TI is not by the PDP Context of this other activation of UE and the used value of MBMS UE context, and does not select the reservation value after the TI expansion.According to the agreement regulation, the reservation value after the TI expansion is 0000000 to 0000110.

Adopt under the situation of expansion back TI, in the step 601 of MBMS activation of service flow process shown in Figure 6, TI after the TI that SGSN carries in the request MBMS context activation message that UE sends just becomes expansion, corresponding, the TI that relates in the subsequent step is exactly TI after the expansion of carrying in this step 601.Equally, for MBMS service deactivation flow process, involved TI is expansion back TI.

In this case, except the definition of TI, MBMS activation of service flow process and deexcitation flow process are identical with step 601～608 and step 701～706 respectively.

To handle and can activate simultaneously more MBMS business in order simplifying, to identify more Bidirectional flow of information simultaneously, also can cancel TI in cancellation MBMS_NSAPI, MBMS_NSAPI and TI are substituted by the MBMS Context identifier.This thought as shown in Figure 8, only relates to the variation of first two steps for MBMS activation of service flow process:

Step 801:SGSN sends a request MBMS context activation message RequestMBMS Context Activation to UE, is used to ask UE to activate a MBMS UE context, carries IP multicast address, APN, Linked NSAPI in this message at least.Wherein, IP multicast address identifies the business that UE need activate.

After step 802:UE creates a MBMS UE context, send one to SGSN and activate MBMS context request Activate MBMS Context Request, comprise in this request: IP multicast address, APN, MBMS bearing capacity.Wherein, IP multicast address is used to identify the MBMS multicast service that UE starts adding/activation; APN indicates a specific GGSN; The MBMS bearing capacity is used to identify the manageable maximum QoS of UE.Here, UE no longer selects and preserves NSAPI, also need not preserve TI again.

Step 803～808: with the processing of step 603 among Fig. 6～608 with describe identical.

Cancellation TI in cancellation MBMS_NSAPI, this thought as shown in Figure 9, also only relates to the variation of first two steps for MBMS service deactivation flow process:

In a single day step 901:SGSN receives MBMS UE context deexcitation request message, the perhaps reason of SGSN oneself, and SGSN sends and contains the deexcitation MBMS context request message Deactivate MBMS Context Request of MBMS Context identifier to UE.The MBMS Context identifier here is used to identify the MBMS UE context that need be deleted by UE.

Step 902:UE deletes MBMS UE context, and accepts message Deactivate MBMS Context Accept to deexcitation MBMS context that contains the MBMS Context identifier of SGSN transmission.The MBMS Context identifier here is used to identify the deleted MBMS UE of UE context.

Step 903～906: with the processing of step 703 among Fig. 7～706 with describe identical.

In such cases, the MBMS UE Context identifier described in step 901 and the step 902 can or be user ID+IP multicast address or is user ID+TMGI for user ID+IP multicast address+APN.Wherein, user ID can be IMSI.So, to carry user ID and MBMS Context identifier two parts information at least in the message that step 901 and step 902 send, such as: IMSI, IP multicast address, APN carried; Perhaps carry IMSI, IP multicast address; Perhaps carry IMSI, TMGI.

The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.

Claims

1, the method that carrying is set up in a kind of multi-medium broadcast/group broadcast service MBMS is characterized in that this method comprises MBMS activation of service process and MBMS service deactivation process at least, and wherein, MBMS activation of service process may further comprise the steps:

2, method according to claim 1 is characterized in that, described TI is the TI that has extended byte.

3, method according to claim 1 and 2 is characterized in that, described MBMS Context identifier is combined by user ID, IP multicast address, APN; Or combine by user ID, IP multicast address; Or combine by user ID, Temporary Mobile Group Identity TMGI.

4, method according to claim 3 is characterized in that, described user ID is IMSI International Mobile Subscriber Identity IMSI.

5, the method that carrying is set up in a kind of multi-medium broadcast/group broadcast service MBMS is characterized in that this method comprises MBMS activation of service process and MBMS service deactivation process at least, and wherein, MBMS activation of service process may further comprise the steps:

6, method according to claim 5 is characterized in that, described MBMS Context identifier is combined by user ID, IP multicast address, APN; Or combine by user ID, IP multicast address; Or combine by user ID, TMGI.

7, method according to claim 6 is characterized in that, described user ID is IMSI.