CN1921641A - Method for processing MBMS business when transmission mode switching - Google Patents

Abstract

The invention relates to a method for processing MBMS service when converting transmission mode. Wherein, the invention is characterized in that: when the network based on the reported message of UE confirms said UE has received MBMS service at PTM mode, and when the transmission mode is converted into PTP, setting RLC rebuild instruction message element in the wireless carried rebuild setting message, and sending said wireless carried rebuild message to said UE; the UE via said message distributes wireless carried RB, and based on said RB to receive MBMS message. With said invention, when UE converts from PTM transmission mode into PTP transmission mode, it can rebuild RLC solid, with which to receive MBMS service normally.

Description

The method of processing MBMS business when transmission mode switching

Technical field

The present invention relates to the communications field, relate in particular to a kind of method of processing MBMS business when transmission mode switching.

Background technology

Multicast and broadcasting are a kind of technology that transmits data from a data source to a plurality of targets.In traditional mobile network, cell broadcaste service (CBS; Cell Broadcast Service) shares broadcast channel by the sub-district of low rate and send, belong to information series business to all users.

Now, people no longer are satisfied with phone and information series business to the demand of mobile communication, fast development along with Internet, a large amount of multimedia services emerge, the some of them applied business requires a plurality of users can receive identical data simultaneously, as video request program, television broadcasting, video conference, online education, interactive game etc.These mobile multi-media services are compared with general data, have characteristics such as data volume is big, longer duration, delay sensitive.Present IP multicasting technology only is applicable to wired IP network, is not suitable for the mobile network, because the mobile network has particular network structure, functional entity and wave point, these are all different with wired IP network.

In order to effectively utilize mobile network resource, the WCDMA/GSM global standardsization organize 3GPP to propose multimedia multicast and broadcasting service service (MBMS; Multimedia Broadcast/MulticastService), promptly in the mobile network, provides the point-to-multipoint service of a data source, realize that Internet resources are shared, raising utilization rate of network resource, the interface resource of especially eating dishes without rice or wine to a plurality of users send data.The MBMS of 3GPP definition can not only realize the classes of messages multicast and the broadcasting of plain text low rate, and can also realize the multicast and the broadcasting of high-speed multimedia business.

Be illustrated in figure 1 as the architecture of MBMS, as can be seen from the figure: in order to support the MBMS business, increased mobile network functional entity-broadcast multicast service center BM-SC newly, it is content provider's a inlet, be used for authorizing and initiating the MBMS bearer service, and plan transmits the MBMS content to schedule at mobile network.

In addition, in the architecture of MBMS, to UE, UTRAN (Universal TerrestrialRadio Access Network; UMTS Terrestrial radio access network), GERAN (RadioAccess Network; Wireless access network), SGSN (ServingGPRS support node; Serving GPRS Support Node), GGSN (Gateway GPRSsupport node; GGSN) etc. functional entity is expanded, and increases the relevant function of MBMS.

When carrying out the MBMS service, can adopt multicast pattern and broadcast mode.Because it is different that multicast and broadcast mode exist, cause also difference of its operation flow on business demand.Operation flow when Fig. 2 adopts multicast pattern to serve for MBMS, operation flow when Fig. 3 adopts broadcast mode to serve for MBMS contrasts two flow charts as can be seen, and multicast pattern needs user's corresponding multicast group of contracting, carry out activation of service, and produce corresponding charge information.

At data transfer phase, the MBMS business has two kinds of pattern: PTM (Point to Multipoint when transmitting between UTRAN and UE; Point is to multiple spot) pattern and PTP (Point to Point; Point-to-point) pattern.The PTM pattern sends identical data by the MTCH logic channel, and all add multicast service or can receive the interested UE of broadcasting service; Ptp mode sends data by the DTCH logic channel, has only a corresponding UE to receive.

The relevant controlled in wireless information of MBMS PTM transmission mode comprises business information, access information, radio bearer information, FLC (Fixed Length Code; Fixed-length code (FLC)) information etc., its protocol stack structure as shown in Figure 4, described information is all by RRC (Radio Resource Control; Radio Resource control) layer sends by logic channel MCCH.Because RLC (Radio Link Control; When wireless chain control layer) entity transmits MCCH message, the situation of exception error often appears, so RLC uses the AM pattern to transmit MCCH message.As shown in Figure 5, MCCH message is mapped on the FACH transmission channel and sends.

The technical scheme of prior art related to the present invention: the UE that has ordered the MBMS business need receive the control information on as shown in Figure 6 the MCCH.If the content of the service message of UE changes, then network is issued UE by MBMS MODIFIED SERVICES INFORMATION (the MBMS service message of change) on MCCH, if contain " MBMS required UEaction (MBMS service request UE action) " in this message and be set to ' Request PTP RB ' (point-to-point radio bearer is set up in request), the corresponding action of UE mainly contains following several situation so:

If 1 UE is under IDLE (free time) state, UE carries out the RRC connection so.

If 2 UE are under URA_PCH and the CELL_PCH state, UE carries out cell updating course so:

Send out a CELL UPDATE message and give network, network returns a CELL UPDATECONFIRM and gives UE, and network is sent out a RADIO BEARER RECONFIGURATION message again, as shown in Table 1, gives UE, and UE is configured according to the parameter that network issues.

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
						Message Type	MP		Message Type
UE Information elements
						RRC transaction identifier	MP		RRC transaction identifier 10.3.3.36
Integrity check info	CH		Integrity check info 10.3.3.16
						Integrity protection mode info	OP		Integrity protection mode info 10.3.3.19	The UTRAN should not include this IE unless it is performing an SRNS relocation or a handover from GERAN lu mode
Ciphering mode info	OP		Ciphering mode info 10.3.3.5	The UTRAN should not include this IE unless it is performing either an SRNS relocation or a handover from GERAN lu mode and a change in ciphering algorithm
						Activation time	MD		Activation time	Default value is

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
									10.3.3.1	″now″
Delay restriction flag	OP	Enumerated (TRUE)		This IE is always set to TRUE and included if the activation time is restricted according to subclause 8.6.3.1
						New U-RNTI	OP		U-RNTI 10.3.3.47
New C-RNTI	OP		C-RNTI 10.3.3.8
						New DSCH-RNTI	OP		DSCH-RNTI 10.3.3.9a	Should not be set in FDD.If received The UE should ignore it
New H-RNTI	OP		H-RNTI 10.3.3.14a		REL-5
						New Primary E-RNTI	OP		E-RNTI 10.3.3.10a		REL-6
New Secondary E-RNTI	OP		E-RNTI 10.3.3.10a		REL-6
						RRC State Indicator	MP		RRC State Indicator 10.3.3.35a
UTRAN DRX cycle length coefficient	OP		UTRAN DRX cycle length coefficient 10.3.3.49
						CN information elements
CN Information info	OP		CN Information info 10.3.1.3
						UTRAN mobility information elements
URA identity	OP		URA identity 10.3.2.6
						CHOICE specification mode	MP				REL-5
>Complete specification
						RB information elements
>>RAB information to reconfigure list	OP	1to< maxRABsetu p>
						>>>RAB information to reconfigure	MP		RAB information to reconfigure 10.3.4.11
>>RB information to reconfigure list	MP	1to <maxRB>		Although this IE is not always required，need is MP to align with ASN.1
						OP				REL-4
	>>>RB information to reconfigure	MP		RB information to reconfigure 10.3.4.18
>>RB information to be affected list						OP	1to <maxRB>
	>>>RB information to be affected	MP		RB information to be affected 10.3.4.17
>>RB with PDCP context relocation info list						OP	1to <maxRBallR ABs>		This IE is needed for each RB having PDCP and performing PDCP context relocation	REL-5
	>>>PDCP context relocation info	MP		PDCP context relocation info							REL-5

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
									10.3.4.1a
PDCP ROHC target mode	OP		PDCP ROHC target mode 10.3.4.2a		REL-5
						TrCH Information Elements
Uplink transport channels
						>>UL Transport channel information common for all transport channels	OP		UL Transport channel information common for all transport channels 10.3.5.24
>>Deleted TrCH information list	OP	1to <maxTrCH>
						>>>Deleted UL TrCH information	MP		Deleted UL TrCH information 10.3.5.5
>>Added or Reconfigured TrCH information list	OP	1to <maxTrCH>
						>>>Added or Reconfigured UL TrCH information	MP		Added or Reconfigured UL TrCH information 10.3.5.2
>>CHOICE mode	OP
						>>>FDD
>>>TDD				(no data)
						Downlink transport channels
>>DL Transport channel information common for all transport channels	OP		DL Transport channel information common for all transport channels 10.3.5.6
						>>Deleted TrCH information list	OP	1to <maxTrCH>
>>>Deleted DL TrCH information	MP		Deleted DL TrCH information 10.3.5.4
						>>Added or Reconfigured TrCH information list	OP	1to <maxTrCH>
>>>Added or Reconfigured DL TrCH information	MP		Added or Reconfigured DL TrCH information 10.3.5.1
						>Preconfiguration					REL-5
>>CHOICE Preconfiguration mode	MP			This value only applies in case the message is sent through GERAN lu mode
						>>>Predefined configuretion identity	MP		Predefined configuration identity 10.3.4.5
>>>Default configuration
						>>>>Default configuration mode	MP		Enumerated (FDD，TDD)	Indicates whether the FDD or TDD version of the default configuration shall be used
>>>>Default configuration idenrity	MP		Default configuration identity 10.3.4.0
						PhyCH information elements

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
						Frequency info	OP		Frequency info 10.3.6.36
Uplink radio resources
						Maximum allowed UL TX power	MD		Maximum allowed UL TX power 10.3.6.39	Default value is the existing maximum UL TX power
CHOICE channel requirement	OP
						>Uplink DPCH info			Uplink DPCH info 10.3.6.88
E-DCH Info	OP		E-DCH Info 10.3.6.97		REL-6
						Downlink radio resources
Downlink HS-PDSCH Information	OP		Downlink HS- PDSCH Information 10.3.6.23a		REL-5
						Downlink information common for all radio links	OP		Downlink information common for all radio links 10.3.6.24
Downlink information per radio link list	MP	1to <maxRL>		Although this IE is not always required，need is MP to align with ASN.1
						OP				REL-4
	>Downlink information for each radio link	MP		Downlink information for each radio link 10.3.6.27
MBMS PL Service Restriction Information						OP		Enumerated (TRUE)	Absence means that on the MBMS Preferred Layer (PL)no restrictions apply concerning the use of non- MBMS services i.e.the PL is not congested	REL-6

Table one

If 3 UE are in below the CELL_FACH, also not definition in the present standard.

If 4 UE are at CELL_DCH, UE carries out PMM (Packet MobilityManagement so; The data field mobile management) connects.

By the technical scheme of above-mentioned prior art as can be seen, there is following defective in it:

To the MBMS business, when the UE under URA_PCH and the CELL_PCH state was forwarding ptp mode to from the PTM pattern and transmits, UE need set up the RB of PTP according to the parameter that network issues.But before carrying out mode switch, if set up the RB of PTM, and, can't rebulid the RLC entity again, so this can cause original RLC entity can not normally receive the business of MBMS according to present technology.

Summary of the invention

In view of above-mentioned existing in prior technology problem, the method that the purpose of this invention is to provide a kind of processing MBMS business when transmission mode switching, by this method, solved as UE during, caused normally to receive the problem of MBMS business because of rebuilding the RLC entity from the PTM transport mode translations to the PTP transmission mode.

The objective of the invention is to be achieved through the following technical solutions:

The method of a kind of processing MBMS business when transmission mode switching provided by the invention comprises:

A, under the PTM pattern, received the MBMS business as the described UE of the validation of information that network based UE uploads, and when needing transport mode translations to become PTP, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and described radio bearer is reconfigured message be handed down to described UE;

B, described UE reconfigure message arrangement radio bearer RB according to described radio bearer, and receive MBMS message based on described RB.

Wherein, described steps A specifically comprises:

The parameter that A1, network based UE upload judges that whether UE has received MBMS message under the PTM pattern, if, execution in step A2 then; Otherwise, execution in step A3;

A2, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and the radio bearer after described the setting is reconfigured message be handed down to described UE;

A3, described radio bearer is reconfigured message be handed down to described UE.

Wherein, described step B specifically comprises:

B1, described UE receive and analyze described radio bearer configuration messages, obtain the message element in the described radio bearer configuration messages;

B2, according to the described message element configured radio bearer RB that gets access to;

B3, receive MBMS message based on the RB of described configuration.

Wherein, described step B1 specifically comprises:

B11, described UE receive and analyze whether have RLC reconstruction instruction message element in the described radio bearer configuration messages, if existence, then execution in step B12; Otherwise, execution in step B13;

B12, judge that described RLC rebuilds whether the instruction message element is actual value, if the RLC that then obtains in the described radio bearer configuration messages rebuilds the instruction message element, and the message element of configuration RB; Otherwise, execution in step B13;

B13, obtain the message element of the configuration RB in the described radio bearer configuration messages.

Wherein, described step B2 specifically comprises:

RLC in B21, the basis described radio bearer configuration messages that obtains rebuilds the instruction message element and rebuilds RLC, and based on the message element of the described configuration RB that obtains RB is configured;

Or

The message element of configuration RB in B22, the basis described radio bearer configuration messages that obtains is configured RB.

Wherein, in the steps A 2, described reconfiguring at radio bearer is provided with the process that RLC rebuilds the instruction message element and also comprises in the message:

The application entity of described RLC being rebuild instruction is revised as affirmation mode AM RLC entity or Unacknowledged Mode UM RLC entity.

As seen from the above technical solution provided by the invention, when the described UE of the validation of information that network based UE uploads has received the MBMS business under the PTM pattern, and when needing transport mode translations to become PTP, the present invention reconfigures at radio bearer and RLC is set in the message rebuilds the instruction message element, and described radio bearer is reconfigured message is handed down to described UE; Described UE reconfigures message arrangement radio bearer RB according to described radio bearer, and receives MBMS message based on described RB.By the present invention, as UE during, can rebuild the RLC entity from the PTM transport mode translations to the PTP transmission mode, and then the RLC entity by described reconstruction, normally receive the MBMS business.

Description of drawings

Fig. 1 is the architectural schematic of MBMS;

Operation flow when Fig. 2 adopts multicast pattern to serve for MBMS;

Operation flow when Fig. 3 adopts broadcast mode to serve for MBMS;

Fig. 4 is the schematic diagram of host-host protocol stack architecture under the MBMS PTM transmission mode;

Fig. 5 is mapped to the schematic diagram that transmits on the FACH transmission channel for MCCH message;

Fig. 6 is the standard information on the MCCH channel;

Fig. 7 is a flow chart of the present invention.

Embodiment

The invention provides a kind of method of processing MBMS business when transmission mode switching, its core is: when the described UE of the validation of information that network based UE uploads has received the MBMS business under the PTM pattern, and when needing transport mode translations to become PTP, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and described radio bearer is reconfigured message be handed down to described UE; Described UE reconfigures message arrangement radio bearer RB according to described radio bearer, and receives MBMS message based on described RB.

The flow process of embodiment provided by the invention as shown in Figure 7, comprising:

The parameter that step 11, network based UE upload judges whether UE has received MBMS message under the PTM pattern, if then execution in step 12; Otherwise, execution in step 13;

Step 12, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and the radio bearer after described the setting is reconfigured message be handed down to described UE, change step 14 then over to;

Step 13, described radio bearer is reconfigured message be handed down to described UE, change step 14 then over to.

After described UE receives described radio bearer reconstruction message, execution in step 14, promptly described UE receives also to analyze whether have RLC reconstruction instruction message element in the described radio bearer configuration messages, if exist, then execution in step 15; Otherwise, execution in step 17;

Step 15, judge that described RLC rebuilds whether the instruction message element is actual value,, rebuild the instruction message element according to described RLC and rebuild the RLC entity, and reconfigure message arrangement RB that execution in step 18 then according to described radio bearer if then execution in step 16; Otherwise, execution in step 17;

Step 17, reconfigure message arrangement RB according to described radio bearer, execution in step 18 then;

Step 18, receive MBMS message based on the RB of described configuration.

The specific implementation process of first embodiment provided by the invention comprises:

Step 101, the parameter that network based UE uploads judge whether UE has received the MBMS business under the PTM pattern.

If network is determined UE and received the MBMS business under the PTM pattern, then carries out following processing:

At first execution in step 102, promptly reconfigure at the radio bearer that is handed down to UE RLC reconstruction instruction is set in the message.

Shown in the black font in the content part, in RADIO BEARERRECONFIGURATION message, add option RLC re-establish indicator as shown in Table 2:

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
						Message Type	MP		Message Type
UE Information elements
						RRC transaction identifier	MP		RRC transaction identifier 10.3.3.36
Integrity check info	CH		Integrity check info 10.3.3.16
						Integrity protection mode info	OP		Integrity protection mode info 10.3.3.19	The UTRAN should not include this IE unless it is performing an SRNS relocation or a handover from GERAN lu mode
Ciphering mode info	OP		Ciphering mode info 10.3.3.5	The UTRAN should not include this IE unless it is performing either an SRNS relocation or a handover from GERAN lu mode and a change in ciphering algorithm
						Activation time	MD		Activation	Default value is

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
									time 10.3.3.1	″now″
Delay restriction flag	OP	Enumerate d(TRUE)		This IE is a1ways set to TRUE and included if the activation time is restricted according to subclause 8.6.3.1
						New U-RNTI	OP		U-RNTI 10.3.3.47
New C-RNTI	OP		C-RNTI 10.3.3.8
						New DSCH-RNTI	OP		DSCH-RNTI 10.3.3.9a	Should not be set in FDD.If received The UE should ignore it
New H-RNTI	OP		H-RNTI 10.3.3.14a		REL-5
						New Primary E-RNTI	OP		E-RNTI 10.3.3.10a		REL-6
New Secondary E-RNTI	OP		E-RNTI 10.3.3.10a		REL-6
						RRC State Indicator	MP		RRC State Indicator 10.3.3.35a
UTRAN DRX cycle length coefficient	OP		UTRAN DRX cycle length coefficient 10.3.3.49
						RLC re-establish indicator	OP		RLC re- establish indicator 10.3.3.35	This IE should be considered when UE transit from PTM to PTP for MBMS receiving.	REL-6
CN information elements
						CN Information info	OP		CN Information info 10.3.1.3
UTRAN mobility information elements
						URA identity	OP		URA identity 10.3.2.6
CHOICE specification mode	MP				REL-5
						>Complete specification
RB information elements
						>>RAB information to reconfigure list	OP	1to< maxRABse tup>
>>>RAB information to reconfigure	MP		RAB information to reconfigure 10.3.4.11
						>>RB information to reconfigure list	MP	1to <maxRB>		Although this IE is not always required， need is MP to align with ASN.1
OP				REL-4
					>>>RB information to reconfigure		MP		RB information to reconfigure 10.3.4.18
>>RB information to be affected list	OP	1to <maxRB>

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
						>>>RB information to be affected	MP		RB information to be affected 10.3.4.17
>>RB with PDCP context relocation info list	OP	1to <maxRBall RABs>		This IE is needed for each RB having PDCP and performing PDCP context relocation	REL-5
						>>>PDCP context relocation info	MP		PDCP context relocation info 10.3.4.1a		REL-5
PDCP ROHC target mode	OP		PDCP ROHC target mode 10.3.4.2a		REL-5
						TrCH Information Elements
Uplink transport channels
						>>UL Transport channel information common for all transport channels	OP		UL Transport channel information common for all transport channels 10.3.5.24
>>Deleted TrCH information list	OP	1to <maxTrCH >
						>>>Deleted UL TrCH information	MP		Deleted UL TrCH information 10.3.5.5
>>Added or Reconfigured TrCH information list	OP	1to <maxTrCH >
						>>>Added or Reconfigured UL TrCH information	MP		Added or Reconfigure d UL TrCH information 10.3.5.2
>>CHOICE mode	OP
						>>>FDD
>>>TDD				(no data)
						Downlink transport channels
>>DL Transport channel information common for all transport channels	OP		DL Transport channel information common for all transport channels 10.3.5.6
						>>Deleted TrCH information list	OP	1to <maxTrCH >
>>>Deleted DL TrCH information	MP		Deleted DL TrCH information 10.3.5.4
						>>Added or Reconfigured TrCH information list	OP	1to <maxTrCH >
>>>Added or Reconfigured DL	MP		Added or

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
						TrCH information			Reconfigure d DL TrCH information 10.3.5.1
>Preconfiguration					REL-5
						>>CHOICE Preconfiguration mode	MP			This value only applies in case the message is sent through GERAN lu mode
>>>Predefined configuration identity	MP		Predefined configuration identity 10.3.4.5
						>>>Default configuration
>>>>Default configuration mode	MP		Enumerated (FDD，TDD)	Indicates whether the FDD or TDD version of the default configuration shall be used
						>>>>Default configuration identity	MP		Default configuration identity 10.3.4.0
PhyCH information elements
						Frequency info	OP		Frequency info 10.3.6.36
Uplink radio resources
						Maximum allowed UL TX power	MD		Maximum allowed UL TX power 10.3.6.39	Default value is the existing maximum UL TX power
CHOICE channel requirement	OP
						>Uplink DPCH info			Uplink DPCH info 10.3.6.88
E-DCH Info	OP		E-DCH Info 10.3.6.97		REL-6
						Downlink radio resources
Downlink HS-PDSCH Information	OP		Downlink HS-PDSCH Information 10.3.6.23a		REL-5
						Downlink information common for all radio links	OP		Downlink information common for all radio links 10.3.6.24
Downlink information per radio link list	MP	1to <maxRL>		Although this IE is not aiways required， need is MP to align with ASN.1
						OP				REL-4
	>Downlink information for each radio link	MP		Downlink information for each radio link 10.3.6.27
MBMS PL Service Restriction Information						OP		Enumerated (TRUE)	Absence means that on the MBMS Preferred Layer (PL)no restrictions apply concerning	REL-6

Information Element/Group name	Need	Multi	Type and reference	Semantics description	Version
										the use of non- MBMS services i.e. the PL is not congested

Table two

After finishing above-mentioned setting up procedure, when network need to determine UE to rebuild the RLC entity, continue the described RLC of definition and rebuild instruction, message IE " RLC re-establish indicator " instruction is revised as AM or UM RLC entity are suitable for by only being applied to AM RLC entity.

Step 103, the radio bearer after will being provided with reconfigure message and are handed down to UE.

Step 104, described UE rebuild the instruction message element according to described RLC and rebuild the RLC entity, and reconfigure message arrangement RB according to described radio bearer.RB based on described configuration receives MBMS message at last.

If network determines UE and do not receiving the MBMS business before the transport mode translations under the PTM pattern, then this moment, UE need not to rebuild the RLC entity, and directly reconfigured element arrangements RB in the message according to described radio bearer, and received the MBMS business based on described RB.

Specific implementation method has two kinds:

The core of first kind of way is: network has known that it still is under the PTM state that UE is in PTP, when sending RADIO BEARER RECONFIGURATION to UE, if this is in the MBMS business that do not receive before UE under the pattern of PTM, so when the RADIO BEARERRECONFIGURATION message that sends, though include the instruction of rebuilding RLC in message, value all is arranged to FALSE.UE sees that the value of the instruction of described reconstruction RLC is FALSE after receiving RADIO BEARER RECONFIGURATION, then do not need to rebuild RLC, and only according to the element arrangements RB in the message of receiving.Implementation process is as follows:

At first execution in step 105, and promptly the network radio bearer that will be handed down to UE reconfigures and rebuilds RLC entity related content in the message and partly be made as FALSE;

Execution in step 106 then, be that described UE receives described radio bearer and reconfigures message, find that wherein rebuild RLC entity related content partly is made as FALSE, then no longer rebuild the RLC entity, directly reconfigure element arrangements RB in the message according to described radio bearer;

Last execution in step 107 promptly receives the MBMS business according to the RB that configuration obtains.

The core of second kind of processing method is: network has known that it still is under the PTM state that UE is in PTP, when sending RADIO BEARER RECONFIGURATION to UE, if this is in the MBMS business of not accepting before UE under the pattern of PTM, in the RADIO BEARERRECONFIGURATION message that sends, do not comprise the instruction of rebuilding RLC so.UE according to the element arrangements RB in the message of receiving, does not need to rebuild RLC after receiving RADIOBEARER RECONFIGURATION.Implementation process is as follows:

At first execution in step 108, and promptly network directly reconfigures message with radio bearer and is handed down to UE; Described radio bearer reconfigured and did not comprise in the message that RLC rebuilds instruction this moment.

Execution in step 109 then, and promptly described UE receives described radio bearer and reconfigures message, and reconfigure element arrangements RB in the message according to described radio bearer.

Last execution in step 110 promptly receives the MBMS business according to the RB that configuration obtains.

As seen from the above technical solution provided by the invention, when the described UE of the validation of information that network based UE uploads has received the MBMS business under the PTM pattern, and when needing transport mode translations to become PTP, the present invention reconfigures at radio bearer and RLC is set in the message rebuilds the instruction message element, and described radio bearer is reconfigured message is handed down to described UE; Described UE reconfigures message arrangement radio bearer RB according to described radio bearer, and receives MBMS message based on described RB.By the present invention, as UE during, can rebuild the RLC entity from the PTM transport mode translations to the PTP transmission mode, and then the RLC entity by described reconstruction, normally receive the MBMS business.

The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.

Claims (6)

1, a kind of method of processing MBMS business when transmission mode switching is characterized in that, comprising:

A, under the PTM pattern, received the MBMS business as the described UE of the validation of information that network based UE uploads, and when needing transport mode translations to become PTP, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and described radio bearer is reconfigured message be handed down to described UE;

B, described UE reconfigure message arrangement radio bearer RB according to described radio bearer, and receive MBMS message based on described RB.

2, method according to claim 1 is characterized in that, described steps A specifically comprises:

The parameter that A1, network based UE upload judges that whether UE has received MBMS message under the PTM pattern, if, execution in step A2 then; Otherwise, execution in step A3;

A2, reconfigure at radio bearer and RLC to be set in the message to rebuild the instruction message element, and the radio bearer after described the setting is reconfigured message be handed down to described UE;

A3, described radio bearer is reconfigured message be handed down to described UE.

3, method according to claim 2 is characterized in that, described step B specifically comprises:

B1, described UE receive and analyze described radio bearer configuration messages, obtain the message element in the described radio bearer configuration messages;

B2, according to the described message element configured radio bearer RB that gets access to;

B3, receive MBMS message based on the RB of described configuration.

According to the described method of described claim 3, it is characterized in that 4, described step B1 specifically comprises:

B11, described UE receive and analyze whether have RLC reconstruction instruction message element in the described radio bearer configuration messages, if existence, then execution in step B12; Otherwise, execution in step B13;

B12, judge that described RLC rebuilds whether the instruction message element is actual value, if the RLC that then obtains in the described radio bearer configuration messages rebuilds the instruction message element, and the message element of configuration RB; Otherwise, execution in step B13;

B13, obtain the message element of the configuration RB in the described radio bearer configuration messages.

5, method according to claim 3 is characterized in that, described step B2 specifically comprises:

RLC in B21, the basis described radio bearer configuration messages that obtains rebuilds the instruction message element and rebuilds RLC, and based on the message element of the described configuration RB that obtains RB is configured;

Or

The message element of configuration RB in B22, the basis described radio bearer configuration messages that obtains is configured RB.

6, method according to claim 2 is characterized in that, in the steps A 2, described reconfiguring at radio bearer is provided with the process that RLC rebuilds the instruction message element and also comprises in the message:

The application entity of described RLC being rebuild instruction is revised as affirmation mode AM RLC entity or Unacknowledged Mode UM RLC entity.

Images