WO2012016446A1

WO2012016446A1 - Method for issuing evolved multimedia broadcast multicast service(embms) and embms system

Info

Publication number: WO2012016446A1
Application number: PCT/CN2011/072599
Authority: WO
Inventors: 张现周; 张文英; 李虎虎; 李建辉
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-08-04
Filing date: 2011-04-11
Publication date: 2012-02-09
Also published as: CN102348164B; CN102348164A

Abstract

A method for issuing evolved multimedia broadcast multicast service(eMBMS) is provided in the invention, which includes the following steps: the different multicast broadcast radio network temporary identifier(RNTI) is allocated to the different eMBMS service; the eMBMS service is scrambled by using the allocated RNTI; and the scrambled eMBMS service is issued. An eMBMS system is also provided in the invention, which includes: a broadcast multicast service center (BM-SC) for providing the eMBMS service; a multi-cell/multicast coordination entity(MCE) for allocating the different RNTI to the different eMBMS; and an evolved node B(eNB) for scrambling the eMBMS service using the allocated RNTI, and issuing the scrambled eMBMS service. The invention saves the processing capacity of the user terminal processor, realizes the sharing of the physical layer wireless resources, and increasing the battery life ability.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to LTE (Long Term Evolution) mobile communication or, in particular, to an eMBMS (evolved MBMS) service delivery method and an eMBMS system. BACKGROUND OF THE INVENTION FIG. 1 is a structural block diagram of a related art eMBMS system, including four devices: MME (mobile management entity), MCE (Multi-cell/multicast Coordination Entity), multi-cell multicast Cooperative entity), eNB (eNodeb, enhanced node), eMBMS GW gateway; one MME can communicate with multiple MCEs through the M3 interface to exchange signaling; one MCE can pass E2 (E-UTRAN internal control plane interface, E-UTRAN) The internal control plane interface communicates with multiple eNBs to exchange signaling; the eMBMS gateway exchanges user plane data with the eNB through a M1 (User plane interface); the MME controls the eMBMS gateway through the Sm interface. The channel mapping in the eNB includes : The logical channel is mapped to the transport channel, and the transport channel is mapped to the physical channel. From the perspective of eMBMS, the MTCH (eMBMS Traffic Channel) and the MCCH (eMBMS Control Channel) are transmitted. The channel has MCH (eMBMS Channel, multicast broadcast channel), and the physical channel has PMCH (Physic eMBMS Channel, object Multicast broadcast channel), MTCH and MCCH are mapped to MCH, MCH is mapped to PMCH. One PMCH can carry MCH, one MCH carries MTCH and MCCH; MTCH can carry multiple MBMS data streams. PMCH through physical cell The ID and M_RNTI (eMBMS Radio Network Temporary Identifier) generate a scrambling code for distinguishing MBMS data. RNTI refers to a Radio Network Temporary Identifier „ such a UE (User Terminal) When decoding the eMBMS data, the M-RNTI is used to generate 4 sigma, the PDCCH (Physical Downlink Control Channel) is decoded, and then the PMCH is decoded. Only when the data of all the PMCHs is decoded, the MCH can be decoded. Then, can we distinguish whether it is MCCH or MTCH data. If it is MTCH data, only full decoding can distinguish the service. The inventor has found that in the above related art, although the user only pays attention to one service flow, it needs to decode the data of all the PMCHs, and the user terminal discards the other service flows, which wastes the capability of the processor and wastes the user terminal, for example. The precious energy of the mobile phone shortens the standby time of the user terminal, and the user body is in danger. SUMMARY OF THE INVENTION A primary object of the present invention is to provide an eMBMS service publishing method and an eMBMS system to solve at least the above problem that a user terminal cannot recognize an eMBMS service of interest. According to an aspect of the present invention, an eMBMS service publishing method is provided, including: allocating different RNTIs for different eMBMS services; using an allocated RNTI plus 4 e-EMBMS services; and issuing an eMBMS service with 4 specials. Preferably, the eMBMS service publishing method further includes: pre-setting the eNB to reserve a plurality of RNTIs, and the multi-cell multicast cooperative entity MCE establishes a resource pool by using the reserved RNTI, where the eNBs in the same multicast group reserve the same RNTI. Preferably, allocating different RNTIs for different eMBMS services includes: The broadcast multicast service center BM-SC decides to issue an eMBMS service, and sends a service release request to the mobility management entity MME, where the service identifier ID of the eMBMS service is carried; After receiving the service release request, the RNTI request is forwarded to the MCE, where the service ID of the eMBMS service is carried. After receiving the RNTI request, the MCE selects one RNTI from the multiple RNTIs of the resource pool to be carried in the RNTI response, and deletes from the resource pool. The selected RNTI establishes a mapping between the RNTI and the service ID, and returns an RNTI response to the MME. After receiving the RNTI response, the MME obtains the RNTI, carries the RNTI in the service release response, and returns a service release response to the BM-SC; BM-SC The RNTI is obtained from the service release response; the BM-SC provides the service ID of the RNTI and the eMBMS service to the user terminal UE. Preferably, using the allocated RNTI plus 4 e-EMBMS services includes: BM-SC decides to play the eMBMS service, and sends an MBMS session start request to the MME, where the service ID of the eMBMS service is carried; the MME forwards the MBMS session start request to the MCE; After receiving the MBMS session start request, the eNB establishes an M1 channel between the eNB and the MBMS gateway, and sends the RNTI corresponding to the service ID to the eNB according to the established mapping; the BM-SC sends the eMBMS service through the M1 channel. To the eNB; the eNB uses the RNTI plus 4 eMBMS services, especially from the M1 channel. Preferably, the eMBMS service publishing method further includes: the BM-SC plays the eMBMS service. Then, the MBMS session stop request is sent to the MME, where the service ID of the eMBMS service is carried; the MME forwards the MBMS session stop request to the MCE; after receiving the MBMS session stop request, the MCE releases the M1 channel between the eNB and the MBMS gateway, and then 艮According to the established mapping, the RNTI corresponding to the service ID is reclaimed into the resource pool. Preferably, the advertised eMBMS service includes: the eNB uploads the multicast broadcast channel MCH on the physical multicast broadcast channel PMCH, and uploads the multicast broadcast traffic channel MTCH and the multicast broadcast control channel MCCH on the MCH, and adds the MTCH 7 through the MTCH 7 Especially the eMBMS business. Preferably, the eMBMS service publishing method further includes: the UE decoding the 4 MB eMBMS service from the MTCH by using the RNTI. Preferably, the BM-SC provides the RNTI and the service ID of the eMBMS service to the UE through a website or a short message. According to another aspect of the present invention, an eMBMS system is provided, comprising: a Broadcast Multicast Service Center (BM-SC), configured to provide an eMBMS service; and an MCE, configured to allocate different RNTIs for different eMBMS services; Set to use the assigned RNTI plus 4 especially eMBMS services, and release the plus 4 eMBMS service. Preferably, the MCE includes: a resource pool, configured to save a plurality of RNTIs that are not used by the preset eNB; and an allocation module, configured to: after receiving the RNTI request from the BM-SC, select one RNTI to carry from the multiple RNTIs of the resource pool In the RNTI response, the selected RNTI is deleted from the resource pool, the mapping between the RNTI and the service ID is established, and the RNTI response is returned to the MME. The session module is configured to establish an MBMS session start request from the BM-SC, and establish with the eNB. The eNB to the M1 channel between the MBMS gateways, and according to the established mapping, sends the RNTI corresponding to the service ID in the MBMS session start request to the eNB. In the related art, the data flows of the different eMBMS services on the same MTCH share the M_RNTI of the PMCH, and the eMBMS service delivery method and the eMBMS system allocate different RNTIs for different eMBMS services, so the solution is solved. The user terminal of the related art cannot identify the problem of the eMBMS service concerned, thereby saving the processing capability of the user terminal processor, realizing the sharing of the physical layer wireless resources, and increasing the battery life capability. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in, are The illustrative embodiments of the present invention and the description thereof are intended to explain the present invention and are not intended to limit the invention. In the drawings: FIG. 1 is a structural block diagram of a related art eMBMS system; FIG. 2 is a flowchart showing an eMBMS service issuing method according to an embodiment of the present invention; FIG. 3 is a view showing a preferred embodiment according to the present invention. Flowchart for allocating RNTI; Figure 4 is a flow chart showing the scrambling eMBMS service in accordance with a preferred embodiment of the present invention; Figure 5 is a flow chart showing the RNTI resource release procedure in accordance with a preferred embodiment of the present invention; A block diagram of an MCE in accordance with a preferred embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The eMBMS system includes four devices: MME, MCE, eNB, eMBMS GW; one MME can pass M3 (control plane interface between E-UTRAN and EPC, control plane interface between E-UTRAN and EPC) and multiple MCEs Communication, exchange signaling; an MCE can communicate with multiple eNBs through the M2 interface to exchange signaling; the eMBMS gateway exchanges user plane data with the eNB through the M1 interface; the MME controls the eMBMS gateway through the Sm interface. Embodiments of the invention are implemented based on the eMBMS system. FIG. 2 is a flowchart of a method for issuing an eMBMS service according to an embodiment of the present invention, including: Step S10: allocating different RNTIs for different eMBMS services; Step S20, using the allocated RNTIs and adding 4 eMBMS services; In step S30, the eMBMS service with the 4th is released. In the related art, the data streams of different eMBMS services on the same MTCH are all scrambled by the M_RNTI of the PMCH, which causes the user terminal to focus on only one service flow, but needs to decode the data of all PMCHs. In the eMBMS service delivery method of this embodiment, different RNTIs are allocated to different eMBMS services, so when the user terminal can decode data, Decoding only the data scrambled by the RNTI of the eMBMS service to which it is concerned, which solves the problem that the user terminal of the related art cannot identify the eMBMS service concerned, thereby saving the processing capability of the user terminal processor and realizing the physical layer radio resource. Share, increase battery life. Preferably, the eNB reserves a plurality of RNTIs in advance, and the MCE establishes a resource pool by using the reserved RNTIs, where the eNBs in the same multicast group reserve the same RNTI, and the eNB is preset to not use some reserved RNTI. The RNTIs can be grouped, and a part of them are used for eMBMS services and placed on the MCE as a resource pool for unified management. This embodiment implements unified management of the RNTI by the MCE. Preferably, step S10 comprises:

The BM-SC decides to issue an eMBMS service, and sends a service publishing request to the MME, where the service ID of the eMBMS service is carried;

After receiving the service publishing request, the MME forwards the RNTI request to the MCE, where the MME carries the service ID of the eMBMS service;

After receiving the RNTI request, the MCE selects one RNTI from the multiple RNTIs of the resource pool to be carried in the RNTI response, deletes the selected RNTI from the resource pool, establishes a mapping of the RNTI and the service ID, and returns an RNTI response to the MME.

After receiving the RNTI response, the MME obtains the RNTI, carries it in the service release response, and returns a service release response to the BM-SC.

The BM-SC obtains the RNTI from the service release response;

The BM-SC provides the UE with the service ID of the RNTI and eMBMS services. The process is to uniformly manage the RNTI related to the eMBMS service as the resource, and bind the RNTI to the eMBMS service in time, and notify the UE and the eNB of the binding relationship respectively. The UE and the eNB use the same RNTI to process the data and complete the air. Communication of the interface. This process is less tampering with the existing business release process 4 and is therefore easy to implement. FIG. 3 illustrates a flow chart of allocating an RNTI according to a preferred embodiment of the present invention, including:

1. The BM-SC decides to publish the service on the website, and first sends an RNTI request message to the MME;

2. The MME receives the RNTI request message and forwards the message to the corresponding MCE. 3. The MCE receives the RNTI request message, allocates the RNTI resource, and sends the RNTI response to the MME.

4. The MME receives the RNTI response and forwards it to the BM-SC. Preferably, step S20 includes:

The BM-SC decides to play the eMBMS service, and sends an MBMS session start request to the MME, where the service ID of the eMBMS service is carried;

The MME forwards the MBMS session start request to the MCE;

After receiving the MBMS session start request, the MCE establishes an M1 channel between the eNB and the MBMS gateway with the eNB, and sends the RNTI corresponding to the service ID to the eNB according to the established mapping;

The BM-SC sends the eMBMS service to the eNB through the M1 channel; the eNB uses the RNTI to add 4 eMBMS services, especially from the M1 channel. This process has less modification to the existing eMBMS session establishment process, so it is easy to implement. 4 is a flow chart showing scrambling eMBMS services in accordance with a preferred embodiment of the present invention, including:

1. The BM-SC requests to play data, and the MME triggers the establishment of the eMBMS carrying process;

2. The MME sends an MBMS SESSION START REQUEST message (including the RNTI and the eMBMS session id) to the MCE;

3. The MCE sends an MBMS SESSION START REQUEST (including the RNTI and the eMBMS session id) to the relevant eNB, and simultaneously creates an eMBMS session instance.

4. The eNB receives the MBMS SESSION START REQUEST, creates an eMBMS session instance, saves the RNTI and session ID information, and sends an MBMS SESSION START RESPONSE message to the MCE.

5. After receiving the MBMS SESSION START RESPONSE response message of the eNB, the MCE sends an MBMS SESSION START RESPONSE to the MME;

6. After receiving the MBMS SESSION START RESPONSE message, the MME starts to send the media stream to the eNB. After that, the eNB sends the data to the UE by using the allocated RNTI, and completes the transmission of the multicast broadcast data. Send and receive. Preferably, the embodiment of the present invention further provides a method for releasing RNTI resources, including:

After the BM-SC plays the eMBMS service, it sends an MBMS session stop request to the MME, where the service ID of the eMBMS service is carried;

The MME forwards the MBMS session stop request to the MCE;

After receiving the MBMS session stop request, the MCE releases the M1 channel between the eNB and the MBMS gateway, and then reclaims the RNTI corresponding to the service ID into the resource pool according to the established mapping. By reclaiming resources in a timely manner, the efficiency of the eMBMS system can be further improved. Figure 5 is a flow chart showing the RNTI resource release process in accordance with a preferred embodiment of the present invention, including:

1. After the data is played, the occupied resources need to be released, and the BM-SC triggers the resource release process;

2. The MME sends an MBMS SESSION STOP REQUEST message to the MCE.

3. After receiving the MBMS SESSION STOP REQUEST message, the MCE releases the RNTI resource and sends a message MBMS SESSION STOP REQUEST message to the eNB;

4. The eNB receives the MBMS SESSION STOP REQUEST message;

5. The eNB releases the resource and the eMBMS service instance, and sends an MBMS SESSION STOP RESPONSE message to the MCE.

6. MCE) to the MBMS SESSION STOP RESPONSE message, release the eMBMS service instance, send the MBMS SESSION STOP RESPONSE message to the MME, and release the release. Preferably, step S30 includes: the eNB uploads the MCH on the PMCH, uploads the MTCH and the MCCH on the MCH, and adds the 4 eMBMS service through the MTCH. Preferably, the UE decodes the 4 MB eMBMS service from the MTCH using the RNTI. This embodiment is consistent with the related technologies in the physical resource allocation, and is easy to implement. Therefore, the UE can directly decode the eMBMS service from the MTCH by using the RNTI. The UE accesses the webpage, finds the corresponding service, saves the corresponding eMBMS session ID and RNTI, waits for the service to play, or immediately receives the data. Preferably, the BM-SC provides the UE with the service ID of the RNTI and the eMBMS service through a website or a short message. These methods are simple and easy. An embodiment of the present invention provides an eMBMS system, including: a BM-SC, configured to provide an eMBMS service; an MCE, configured to allocate different RNTIs for different eMBMS services; and an eNB configured to use an allocated RNTI plus 4 e-EMBMS services And released the 4th eMBMS business. In the related art, the data flows of different eMBMS services on the same MTCH share the M_RNTI of the PMCH, and the eMBMS system allocates different RNTIs for different eMBMS services, so the user terminal that solves the related technology cannot The problem of the eMBMS service concerned is identified, thereby saving the processing capability of the user terminal processor, realizing the sharing of the physical layer radio resources, and increasing the battery life capability. 6 shows a block diagram of an MCE 100 in accordance with a preferred embodiment of the present invention, comprising: a resource pool 10 configured to hold a plurality of RNTIs that are not used by a preset eNB; an allocation module 20 configured to receive from the BM-SC After the RNTI request, one RNTI is selected from the multiple RNTIs of the resource pool to be carried in the RNTI response, the selected RNTI is deleted from the resource pool, the mapping between the RNTI and the service ID is established, and the RNTI response is returned to the MME; the session module 30, After receiving the MBMS session start request from the BM-SC, the M1 channel between the eNB and the MBMS gateway is established with the eNB, and the RNTI corresponding to the service ID in the MBMS session start request is sent according to the established mapping. To the eNB. From the above description, it can be seen that the present invention allocates one RNTI for each eMBMS service, enabling the UE to demodulate data only by using the RNTI of the service concerned, so that the user terminal can distinguish the service characteristics as soon as possible, and abandon the physical layer. Data, and do not have to give up the eMBMS service that is not concerned, thereby saving the processing power of the processor, realizing the sharing of the wireless resources of the physical layer, and increasing the battery life. In addition, the method and system of the present invention reduce the allocation of radio resources, realize the dynamic allocation of wireless bandwidth, and allocate only RNTI, which reduces the complexity of the device and reduces the maintenance of the device. Complexity, reducing OPEX (Operating Expenses). Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be executed by a computing device The program code is implemented so that they can be stored in the storage device by the computing device, and in some cases, the steps shown or described can be performed in a different order than here, or they can be separately produced. The individual integrated circuit modules are implemented, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. An enhanced broadcast multicast eMBMS service publishing method, including:

Allocating different multicast broadcast radio network temporary identifiers RNTI for different eMBMS services;

Using the allocated RNTI plus 4 especially the eMBMS service;

The scrambled eMBMS service is released.

The method according to claim 1, wherein the method further comprises: presetting that the enhanced Node B eNB reserves a plurality of RNTIs, and the multi-cell multicast cooperative entity MCE establishes a resource pool by using the reserved RNTI, where The eNBs in the same multicast group reserve the same RNTI.

3. The method according to claim 2, wherein allocating different RNTIs for different eMBMS services comprises:

The broadcast multicast service center BM-SC determines to issue one of the eMBMS services, and sends a service release request to the mobility management entity MME, where the service identifier ID of the eMBMS service is carried;

After receiving the service publishing request, the MME forwards an RNTI request to the MCE, where the MME carries the service ID of the eMBMS service;

After receiving the RNTI request, the MCE selects one RNTI from the multiple RNTIs of the resource pool to be carried in the RNTI response, deletes the selected RNTI from the resource pool, and establishes the RNTI and Mapping the service ID, and returning an RNTI response to the MME;

After receiving the RNTI response, the MME obtains the RNTI from the RNTI, carries it in the service release response, and returns the service release response to the BM-SC.

Obtaining, by the BM-SC, the RNTI from the service release response;

The BM-SC provides the RNTI and the service ID of the eMBMS service to the user terminal UE.

4. The method of claim 3, wherein scrambling the eMBMS service using the allocated RNTI comprises: The BM-SC determines to play the eMBMS service, and sends an MBMS session start request to the MME, where the service ID of the eMBMS service is carried;

The MME forwards the MBMS session start request to the MCE; after receiving the MBMS session start request, the MCE establishes an M1 channel between the eNB and the MBMS gateway with the eNB, and then The established mapping, the RNTI corresponding to the service ID is sent to the eNB;

The BM-SC sends the eMBMS service to the eNB through the M1 channel;

The eNB uses the RNTI to add 4 the eMBMS service from the M1 channel.

The method according to claim 4, wherein the method further comprises:

After the BM-SC plays the eMBMS service, sending an MBMS session stop request to the MME, where the service ID of the eMBMS service is carried;

The MME forwards the MBMS session stop request to the MCE; after receiving the MBMS session stop request, the MCE releases the M1 channel between the eNB and the MBMS gateway, and according to the established mapping Retrieving the RNTI corresponding to the service ID into the resource pool.

6. The method according to claim 4, wherein the issuing the scrambled eMBMS service comprises: the eNB carrying a multicast broadcast channel MCH on a physical multicast broadcast channel PMCH, and carrying a multicast broadcast on the MCH The traffic channel MTCH and the multicast broadcast control channel MCCH are carried by the MTCH to carry the eMBMS service.

The method according to claim 6, wherein the method further comprises: the UE decoding the added eMBMS service from the MTCH by using the RNTI.

The method according to claim 3, wherein the BM-SC provides the RNTI and the service ID of the eMBMS service to the UE through a website or a short message.

9. An eMBMS system, including:

BM-SC, set to provide eMBMS services;

MCE, configured to allocate different RNTIs for different eMBMS services; The eNB is configured to use the allocated RNTI to add 4 to the eMBMS service, and issue the scrambled eMBMS service. The system of claim 9, wherein the MCE comprises:

a resource pool, configured to save a plurality of RNTIs that are not used by the eNB in advance;

An allocation module, configured to: after receiving an RNTI request from the BM-SC, select one RNTI from the multiple RNTIs of the resource pool to be carried in an RNTI response, and delete the selected one from the resource pool RNTI, establishing a mapping between the RNTI and the service ID, and returning the RNTI response to the MME;

a session module, configured to: after receiving an MBMS session start request from the BM-SC, establish an M1 channel between the eNB and an MBMS gateway with the eNB, and according to the established mapping, corresponding to The RNTI of the service ID in the MBMS Session Start Request is sent to the eNB.