Multimedia broadcast/multicast service announcement and notification

BACKGROUND OF THE INVENTION

00011. Field of Invention

0002The present invention relates to a method for sending and receiving Multimedia Broadcast/Multicast Service (MBMS) data in communication system, especially to a method of sending and receiving Service Announcement and Service notification in Multimedia Broadcast/Multicast Service with the aid of using cell broadcast.

00032. Description of Prior Art

0004Multimedia Broadcast/Multicast Service (hereinafter referred to as MBMS) is a new service under standardization by 3^rdGeneration Partnership Project (hereinafter referred to as 3GPP). The standard being developed is TS23.846, whose latest version is 1.1.1. MBMS service is a unidirectional point-to-multipoint (p-t-m) service, whose most remarkable characteristic is that it can make use of radio resources and network resources efficiently.

0005A system structure of MBMS is described in the following with reference to <figref idref="DRAWINGS">FIG. 1</figref>. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the MBMS network structure is based on the core network of General Packet Radio Service (hereinafter referred to as GPRS), and further adds new network elements. Broadcast and multicast service center <b>101</b> (hereinafter referred to as BM-SC) is the service control center of MBMS system. Gateway GPRS Supporting Node <b>102</b> (hereinafter referred to as GGSN) and Service GPRS Supporting Node <b>103</b> (hereinafter referred to as SGSN) compose the transmission network of MBMS service and provide route for the transmission of data. Home Location Register <b>106</b> (hereinafter referred to as HLR) stores the data related to user and can provide services such as user's authentication. UMTS Terrestrial Radio Access Network <b>104</b> (hereinafter referred to as UTRAN) provides radio resources for MBMS service over the air-interface. Uu<b>107</b> indicates a radio interface between terminal and access network. User Equipment <b>105</b> (hereinafter referred to as UE) is a terminal device for receiving data. Cell Broadcast Center <b>108</b> (hereinafter referred to as CBC) is a data source of cell broadcast. Radio resources used by MBMS service are not dedicated for one user, but are shared by all users using this service.

0006A MBMS multicast service flow is described in the following with reference to <figref idref="DRAWINGS">FIG. 2</figref>. As shown in <figref idref="DRAWINGS">FIG. 2</figref>, the MBMS multicast service flow includes the following steps:

0000In <b>200</b>, Subscription step, establishes the relationship between user and service provider, which allows the user to receive the related MBMS multicast service.

0000In <b>201</b>, Service announcement step, informs UEs about the types and service areas of forthcoming multicast services.

0000In <b>202</b>, Joining step, is the process by which a subscriber joins a multicast group, i.e. the user registers the network in which the MBMS multicast service types that he is willing to receive.

0000In <b>203</b>, MBMS multicast mode bearer set up step, establishes the network resources for MBMS multicast data transfer.

0000In <b>204</b>, MBMS notification step, informs UEs about forthcoming MBMS multicast data transfer.

0000In <b>205</b>, Data transfer step, indicates the phase when MBMS multicast service data are transferred from the network to the UEs.

0000In <b>206</b>, MBMS multicast mode bearer release step, indicates to release the network resources after MBMS service data transfer finishes.

0000In <b>207</b>, Leaving step, corresponding to <b>202</b> joining step, indicates that a subscriber is leaving a service group, i.e. the user no longer wants to receive Multicast mode data of a specific service.

0007The necessary flow of providing a MBMS broadcast service is described with reference to <figref idref="DRAWINGS">FIG. 3</figref>. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the MBMS broadcast service flow includes the flowing steps:

0000<b>300</b>, Service announcement step, informs UEs about the types and service areas of forthcoming services.

0000<b>301</b>, MBMS broadcast mode bearer setup step, establishes the network resources for MBMS broadcast data transfer.

0000<b>302</b>, MBMS notification step, informs the UEs about the forthcoming MBMS broadcast data transfer.

0000<b>303</b>, Data transfer step, indicates the phase when MBMS broadcast data are transferred from the network to the UEs.

0000<b>304</b>, MBMS broadcast mode bearer release step, indicates to release the network resources after MBMS broadcast service data transfer finishes.

0008In the MBMS Multicast service flow shown in <figref idref="DRAWINGS">FIG. 2</figref>, the operation in step <b>200</b>, <b>201</b> and <b>202</b> should be performed for different UEs respectively, and remaining steps are performed by all UEs in the same type of service. The series of steps can be performed repeatedly, and step <b>200</b>, <b>201</b>, <b>203</b>, <b>204</b> or <b>207</b> can be performed in parallel with other steps.

0009In the MBMS broadcast service flow shown in <figref idref="DRAWINGS">FIG. 3</figref>, this series of steps can be performed repeatedly and step <b>300</b> and <b>302</b> can be performed in parallel with other steps.

0010A Cell Broadcast indicates to transfer data by using a common service channel in a cell so as to enable all UEs staying in the cell capable of receiving the broadcast data of the cell. Refer to 3GPP standard TS25.324 (the latest version is 5.1.0) for the description of cell Broadcast/Multicast Control module BMC.

0011But in the steps shown in <figref idref="DRAWINGS">FIGS. 2 and 3</figref>, in existing standard TS23.846, it only mentioned that Service announcement steps can be completed by CBC, but the implementation method hasn't been given, and didn't mention with what devices and how to implement MBMS Service notification steps, which make it impossible to completely implement MBMS multicast service flow and MBMS broadcast service flow.

SUMMARY OF THE INVENTION

0012Therefore, an object of the present invention is to provide a method on how to use a cell broadcast to realize MBMS service announcement and MBMS service notification so as to make MBMS service be a complete flow. It is noted that the Cell Broadcast herein indicates a method of transmitting data via a common service channel over a air-interface of the cell, and it does not relates to specific devices such as CBC. When the cell broadcast is used to support the MBMS service announcement or MBMS service notification, messages sent from CBC and SGSN can all be sent out through cell broadcast.

0013According to one aspect of the present invention, a process of a UE receiving MBMS multicast service data is shown in <figref idref="DRAWINGS">FIG. 4</figref>, and includes the following steps:

0014<b>400</b>, Subscription step, indicates a process of the UE subscribing a specific type of MBMS service, which makes the UE establishing relationship with the specific type of MBMS and be authorized to receive this specific type of MBMS service in the future;

0000<b>401</b>, Service announcement step, indicates a process of the UE being informed of the MBMS multicast service types and relevant parameters by receiving the service announcement information included in cell broadcast;

0000<b>402</b>, Joining step, indicates a process of the UE joining the specific MBMS service multicast group, which corresponds to the MBMS service one to one, the multicast group including all subscribers who receive the MBMS service;

0000<b>403</b>, MBMS Service notification step, indicates that the UE is informed that the MBMS multicast service data, which is expected to receive by the UE, is forthcoming, by receiving MBMS Service notification information included in cell broadcast;

0000<b>404</b>, Data transfer step, indicates a process of the UE receiving the MBMS service multicast data;

0000<b>405</b>, Leaving step, indicates a process of the UE leaving the specific MBMS service multicast group that it is used to join.

0015A Process of a UTRAN sending the MBMS Multicast Service Data is Shown in <figref idref="DRAWINGS">FIG. 5</figref>, and Includes the Following Steps:

0000<b>500</b>, Service announcement step, indicates that the UTRAN sends information on MBMS service types and service areas via cell broadcast;

0000<b>501</b>, MBMS multicast mode bearer set up step, indicates a process of co-establishing the network resources for the MBMS service by the UTRAN and a core network;

0016<b>502</b>, MBMS service notification step, indicates that the UTRAN sends a MBMS service notification message via cell broadcast, the message indicating a forthcoming of a specific MBMS service data, and making all users of this multicast group prepare radio resources;

0000<b>503</b>, data transfer step, indicates that the UTRAN sends a real MBMS service data;

0000<b>504</b>, MBMS multicast mode bearer release step, indicates that after the transfer of the MBMS service data being completed, the UTRAN and other devices in the core network co-release the network resources for the MBMS multicast service.

0017A Process of the UE Receiving the MBMS Broadcast Service Data is Shown in <figref idref="DRAWINGS">FIG. 6</figref>, and Includes the Following Steps:

0000<b>600</b>, Service announcement step, indicates a process of the UE being informed of the MBMS broadcast service types and relevant parameters by receiving the service announcement information included in the cell broadcast;

0000<b>601</b>, MBMS service notification step, indicates that the UE is informed that the MBMS broadcast service data, which is expected to receive by the UE, is forthcoming, by receiving MBMS service notification information included in cell broadcast;

0000<b>603</b>, Data transfer step indicates a process of the UE receiving the MBMS broadcast service data;

0018A Process of the UTRAN Sending the MBMS Broadcast Service is Shown in <figref idref="DRAWINGS">FIG. 7</figref>, and Includes the Following Steps:

0000<b>700</b>, Service announcement step, indicates that the UTRAN sends information on MBMS service types and service areas via cell broadcast;

0000<b>701</b>, MBMS broadcast mode bearer setup step, indicates a process of co-establishing the network resources for the MBMS broadcast service by the UTRAN and the core network;

0019<b>702</b>, MBMS service notification step, indicates that the UTRAN sends a MBMS service notification message via cell broadcast, the message indicating a forthcoming of a specific MBMS service data, and making all users of this multicast group prepare radio resources;

0000<b>703</b>, data transfer step, indicates that the UTRAN sends a real MBMS service data;

0000<b>704</b>, MBMS broadcast mode bearer release step, indicates that after the transfer of the MBMS service data being completed, the UTRAN and other devices in the core network co-release the network resources for the MBMS broadcast service.

0020According to another aspect of the present invention, the method for transferring service announcement of Multimedia Broadcast/Multicast Service (MBMS) includes the following steps:

0021(a) Broadcast/Multicast Service Center (BM_SC) requests Cell Broadcast Center (CBC) to send a service announcement by a signaling message in a Multimedia Broadcast/Multicast Service (MBMS) service area, wherein said request can include sending times and sending time duration as parameters;

0000(b) After receiving the signaling message from BM_SC, Cell Broadcast Center (CBC) commands UMTS Terrestrial Radio Access Network (UTRAN) connected with it to send the service announcement through the signaling message;

0022(c) UMTS Terrestrial Radio Access Network (UTRAN) arranges the sending of Multimedia Broadcast/Multicast Service (MBMS) service announcement message in a prescribed time of one or more schedule periods according to the requirement of Cell Broadcast Center (CBC), adds brief description information to a schedule message for describing each schedule period and sends the schedule message; after receiving the schedule message, UE analyzes the schedule message and then configures its physical layer to prepare for receiving the Multimedia Broadcast/Multicast Service (MBMS) service announcement message;

0000(d) UMTS Terrestrial Radio Access Network (UTRAN) sends Multimedia Broadcast/Multicast Service (MBMS) service announcement message at the prescribed time.

0023Wherein the transfer times in the step (a) can be a plurality of times or infinite times.

0024In addition, after UMTS Terrestrial Radio Access Network (UTRAN) completes the sending of the Multimedia Broadcast/Multicast Service (MBMS) service announcement message, it may send confirmation information to Cell Broadcast Center (CBC). After receiving the confirmation information from UTRAN, Cell Broadcast Center (CBC) returns confirmation information to BM_SC subsequently.

0025In the above step (b), according to the requirement of BM_SC, Cell Broadcast Center (CBC) can require UMTS Terrestrial Radio Access Network (UTRAN) to send the service announcement periodically a plurality of times or infinite times.

0026In the above step (d), UMTS Terrestrial Radio Access Network (UTRAN) sends the Multimedia Broadcast/Multicast Service (MBMS) service announcement message a plurality of times according to the requirement of Cell Broadcast Center (CBC), and the step (c) and (d) can be repeated a plurality of times without a certain precedence order.

0027In addition, the service announcement message includes parameters of the Multimedia Broadcast/Multicast Service (MBMS) service types and service areas.

0028According to another aspect of the present invention, the method for transferring a Multimedia Broadcast/Multicast Service (MBMS) service notification includes the following steps:

0000(a) BM_SC sends the Multimedia Broadcast/Multicast Service (MBMS) data to GGSN;

0000(b) After receiving said data sent by BM_SC, GGSN sends said data to SGSN by tunneling technique;

0000(c) After receiving the signals from GGSN, SGSN informs UMTS Terrestrial Radio Access Network (UTRAN) of the forthcoming of the Multimedia Broadcast/Multicast Service (MBMS) data via a signaling message;

0000(d) Radio data Access Bearer (RAB) is established between UMTS Terrestrial Radio Access Network (UTRAN) and SGSN;

0000(e) SGSN sends the Multimedia Broadcast/Multicast Service (MBMS) data to UMTS Terrestrial Radio Access Network (UTRAN) via Radio data Access Bearer RAB;

0029(f) After receiving the described data from SGSN, UMTS Terrestrial Radio Access Network (UTRAN) arranges the sending time of a Multimedia Broadcast/Multicast Service (MBMS) service notification message, which includes to arrange sending at the prescribed time of one or more schedule periods, and to add a brief description information to the schedule message for describing each schedule period and to send the schedule message. After receiving the schedule message, UE analyzes the schedule message and configures its physical layer to prepare for receiving the Multimedia Broadcast/Multicast Service (MBMS) service notification message;

0000(g) UMTS Terrestrial Radio Access Network (UTRAN) sends the Multimedia Broadcast/Multicast Service (MBMS) service notification message at the prescribed time;

0000(h) UE requests UTRAN to allocate Radio Bearer (RB) via a signaling message, and a plurality of UEs can send requests to UMTS Terrestrial Radio Access Network (UTRAN) simultaneously;

0000(i) UMTS Terrestrial Radio Access Network (UTRAN) allocates the radio bearer (RB) according to the number of UEs and other comprehensive factors, and informs the UE;

0000(j) UMTS Terrestrial Radio Access Network (UTRAN) sends the Multimedia Broadcast/Multicast Service (MBMS) data to the UE via RB.

0030The above step (e), step (f) and step (g) can be performed without a certain precedence order.

0031The data transfer flow of MBMS broadcast service is similar with that of multicast service, except that it does not need the step (h), and in the step (i), UMTS Terrestrial Radio Access Network (UTRAN) allocates radio data bearer (RB) according to comprehensive factors without consideration of the number of UEs.

0032The step of UMTS Terrestrial Radio Access Network (UTRAN) sending a service notification or a service announcement message of Multimedia Broadcast/Multicast Service (MBMS) data via cell broadcast further includes the following steps:

0033(1) Multimedia Broadcast/Multicast Service Control Module (MBMSC) receives a signaling message sent from the core network nodes (SGSN, CBC), which informs UMTS Terrestrial Radio Access Network (UTRAN) to send a service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) and includes the necessary parameters for constructing the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS);

0034(2) Multimedia Broadcast/Multicast Service Control Module (MBMSC) requests Broadcast/Multicast Control protocol (BMC) with a primitive to send the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS), wherein said primitive includes the necessary parameters for constructing the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS);

0035(3) BMC constructs the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS), saves it in its own sending memory block, and starts up a counter for this message, and the initial value of the counter is equal to the required times for sending the message, and if the message is required to send for infinite times, the initial value of the counter is assigned with zero or negative value;

0036(4) BMC estimates the transmission rate (Vneed) needed on the CTCH according to all messages currently saved in the sending memory block, wherein said all messages include the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) and other broadcast messages, and if the actual transmission rate (Vctch) on the CTCH is 0, it means that this cell hasn't allocated CTCH resources and it won't continue to send broadcast message, and if the actual transmission rate is much smaller or larger than that needed on the CTCH, BMC reports the actual required transmission rate to RRC with a primitive and requests RRC to establish or adjust CTCH resources, during the period of BMC waiting for CTCH resources configured by RRC, if the actual transmission rate does not match with that required and it isn't equal to zero: when the actual transmission rate is much smaller than that required, BMC can still select some messages with high priority and short length to transfer; when the actual transmission rate is much larger than that needed, BMC also reports to RRC, but at this time, resources on CTCH will be wasted;

0037(5) RRC controls L1 and L2 with a primitive to establish CTCH or adjust CTCH configuration to make CTCH transmission rate match, and RRC informs BMC the new configuration parameters of CTCH with a primitive, and only if the actual transmission rate is not equal to zero, BMC will still continue to send the broadcast message as described in step (4);

0038(6) BMC adds descriptions for the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) to a pending-for-sending schedule message, and then BMC arranges the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) on a certain position of the schedule period following the schedule message for future sending;

0000(7) BMC sends the schedule message;

0000(8) BMC sends the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) at the prescribed time;

0039(9) After reducing the counter's value by 1, BMC judges: if the value of the counter is negative, it means that the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) is required to send infinite times, then proceeding to step (10) after adding 1 to the value of the counter; if the value of the counter is positive, proceeding to step (10) directly; if the value is zero, it means that the times of sending the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) has met the requirement, then BMC returns the confirmation information to Multimedia Broadcast/Multicast Service Control Module (MBMSC) with a primitive and the process of sending service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) is completed;

0040(10) BMC waits on-timing according to the time interval that the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) is required to send, when the time expires for sending the next service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS), proceeding to step (6).

0041The step of the UE receiving the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) via cell broadcast further includes the following steps:

0000(1) Multimedia Broadcast/Multicast Service Control Module (MBMSC) sends a request to BMC with a first primitive for receiving a service announcement message or a service notification message of Multimedia Broadcast/Multicast Service (MBMS);

0000(2) If BMC hasn't received any broadcast message before, proceeding to step (3); otherwise, proceeding to step (9);

0000(3) BMC informs RRC to receive broadcast message with a second primitive, which includes the parameters that can inform RRC only to receive a BMC preferred message at the prescribed time and to skip some messages;

0042(4) If RRC has not configured CTCH before, RRC configures link layer (L2) and physical layer (L1) to enable UE to receive information on the CTCH and feedbacks necessary CTCH configuration information with a third primitive to BMC at the same time, thereafter proceeding to step (5); if RRC has configured CTCH resources before, proceeding to step (5) directly;

0000(5) According to the requirement of BMC, RRC controls L2 and L1 with a fourth primitive to receive cell broadcast information on the CTCH at the prescribed time;

0000(6) After processing the data frame received from the CTCH accordingly, L1 and L2 submit it to BMC in the format of BMC message with a fifth primitive;

0043(7) BMC analyses the received message, and if it is the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS), BMC forwards it to Multimedia Broadcast/Multicast Service Control Module (MBMSC) with a sixth primitive, at the same time the reception is completed; if it is not the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS), proceeding to step (8);

0000(8) If the message received by BMC is the schedule message, proceeding to step (9); otherwise, proceeding to step (3);

0044(9) BMC analyses the schedule message that was received most recently, and checks whether the schedule period described by the schedule message includes the service announcement message or service notification message of Multimedia Broadcast/Multicast Service (MBMS) or not. If it is positive, proceeding to step (12), otherwise, BMC finds the position of the next schedule message and requests RRC to receive the next schedule message with the second primitive;

0000(10) RRC controls L1 and L2 to receive the next schedule message at the prescribe time with the fourth primitive;

0000(11) After processing the message received from the CTCH accordingly, L1 and L2 forward the schedule message to BMC with the fifth primitive, and then proceeding to step 9);

0045(12) BMC finds the position of the Multimedia Broadcast/Multicast Service (MBMS) service announcement message or service notification message, and requests RRC to receive Multimedia Broadcast/Multicast Service (MBMS) service announcement message or service notification message at the prescribed time with the second primitive;

0000(13) RRC controls L1 and L2 to receive the Multimedia Broadcast/Multicast Service (MBMS) service announcement message or service notification message at the prescribed time with the fourth primitive;

0000(14) After processing the message received from the CTCH accordingly, L1 and L2 forward the Multimedia Broadcast/Multicast Service (MBMS) service announcement message or service notification message to BMC with the fifth primitive;

0000(15) BMC forwards the Multimedia Broadcast/Multicast Service (MBMS) service announcement message or service notification message to Multimedia Broadcast/Multicast Service (MBMS) with the third primitive and the reception is completed.

BRIEF DESCRIPTION OF THE DRAWINGS

0046The above and other features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

0047<figref idref="DRAWINGS">FIG. 1</figref> illustrates a diagram of logical network apparatuses that can provide MBMS service.

0048<figref idref="DRAWINGS">FIG. 2</figref> illustrates a flow of MBMS multicast service.

0049<figref idref="DRAWINGS">FIG. 3</figref> illustrates a flow of MBMS broadcast service.

0050<figref idref="DRAWINGS">FIG. 4</figref> illustrates a flow of UE receiving MBMS multicast service data.

0051<figref idref="DRAWINGS">FIG. 5</figref> illustrates a flow of UTRAN sending MBMS multicast service data.

0052<figref idref="DRAWINGS">FIG. 6</figref> illustrates a flow of UE receiving MBMS broadcast service data.

0053<figref idref="DRAWINGS">FIG. 7</figref> illustrates a flow of UTRAN sending MBMS broadcast service data.

0054<figref idref="DRAWINGS">FIG. 8</figref> illustrates a message flow of a service announcement process in MBMS service.

0055<figref idref="DRAWINGS">FIG. 9</figref> illustrates a message flow of a data transfer in MBMS service.

0056<figref idref="DRAWINGS">FIG. 10</figref> illustrates a functional diagram that explains the process of a service announcement and a service notification in MBMS service.

0057<figref idref="DRAWINGS">FIG. 11</figref> illustrates an example of mapping CTCH onto S-CCPCH.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

0058A message flow of a service announcement process in MBMS multicast service In order to explain the process of a service announcement in MBMS service, <figref idref="DRAWINGS">FIG. 8</figref> gives a message flowchart of a service announcement process, which includes the parts of UE receiving and UTRAN sending. The description is as follows:

0000<b>801</b>. BM_SC requests CBC to send a service announcement in the service area of MBMS service through a signaling message. This request may include sending times and sending time duration as parameters and the sending times can be infinite times.

0059<b>802</b>. CBC commands UTRAN connected with it by a signaling message to send the service announcement; according to the requirement of BM_SC, Cell Broadcast Center (CBC) may require UTRAN to send the service announcement periodically a plurality of times or infinite times.

0060<b>803</b>. UTRAN arranges the time for sending the Multimedia Broadcast/Multicast Service (MBMS) service announcement message in proper time of one or more schedule periods according to the requirement of Cell Broadcast Center (CBC), adds the brief description information to the schedule message that describes each schedule period and sends the schedule message. After receiving the schedule message, UE analyses the schedule message and configures its physical layer to prepare for receiving the Multimedia Broadcast/Multicast Service (MBMS) service announcement message.

0061<b>804</b>. UTRAN sends the MBMS service announcement message at prescribed time. According to the requirement of CBC, the MBMS service announcement message may be sent a plurality of times, and therefore step <b>803</b> and <b>804</b> may be repeated a plurality of times without a certain precedence order.

0000<b>805</b>. After UTRAN completes the sending of the MBMS service announcement message, it sends a confirmation message to CBC.

0000<b>806</b>. After receiving the confirmation message from UTRAN, CBC returns a confirmation message to BM_SC subsequently.

0062The flow of a MBMS service announcement is the same as that of a MBMS broadcast service.

0063A transfer process of a MBMS multicast service data including MBMS service notification process

0064The function of MBMS service notification is to inform UE the forthcoming MBMS data so that UE can prepare radio resources. <figref idref="DRAWINGS">FIG. 9</figref> is an example of a MBMS data transfer. The function of the MBMS service notification will be explained with reference to the flow of this example:

0000<b>901</b>, BM_SC initiates an MBMS data transfer and sends MBMS data to GGSN.

0000<b>902</b>, GGSN sends the data to SGSN by tunneling technique.

0000<b>903</b>, SGSN informs UTRAN about the forthcoming of the MBMS data by a signaling message.

0000<b>904</b>, Radio data Access Bearer (hereinafter referred to as RAB) is established between UTRAN and SGSN.

0000<b>905</b>, SGSN sends MBMS data to UTRAN via RAB. Step <b>905</b>, <b>906</b> and <b>907</b> are executed without a certain precedence order.

0065<b>906</b>, UMTS Terrestrial Radio Access Network (UTRAN) arranges the time for sending the Multimedia Broadcast/Multicast Service (MBMS) service notification message, which includes to arrange it in proper time of one or more schedule periods for sending, to add the brief description information to the schedule message that describes each schedule period and to send the schedule message; after receiving the schedule message, UE analyses the schedule message and configures its physical layer to prepare for receiving the MBMS service notification message.

0000<b>907</b>, UTRAN sends the MBMS service notification message at the prescribed time.

0000<b>908</b>, UE requests UTRAN to allocate Radio resources (RB) by a signaling message. It is possible that there are a plurality of UEs to send requests to UTRAN simultaneously at this time.

0000<b>909</b>, UTRAN allocates radio bearer (hereinafter referred to as RB) according to the number of UEs and other comprehensive factors, and informs UE.

0000<b>910</b>, UTRAN sends the MBMS data to UE via RB.

0066The data transfer flow of MBMS broadcast service is similar with that of multicast service, except that it does not need step <b>908</b>.

0067A Process of UE Receiving a MBMS Service Announcement Message

0068For UE, the process of receiving a MBMS service announcement message in multicast service and in broadcast service is the same. This process will be explained in the following with reference to the functional diagram of <figref idref="DRAWINGS">FIG. 10</figref>:

00001. When MBMSC (MBMS Service Control module) decides to receive a MBMS service announcement message, MBMSC sends a request to BMC (Broadcast/Multicast Control protocol) with primitive P′1;

00002. If BMC has never received any broadcast message before, proceeding to step 3; otherwise, proceeding to step 9;

00693. BMC informs RRC to receive the broadcast message with primitive C′1. The parameters included in C′1 may inform RRC to receive RMC preferred message only at prescribed time and skip some messages. But in step 3, BMC must require RRC to receive all continuous broadcast messages;

00704. If RRC has not configured CTCH before, RRC configures link layer (L2) and physical layer (L1) to enable UE to receive information on the CTCH and feedbacks necessary CTCH configuration information to BMC with primitive C′2 at the same time, then proceeding to step 5; if RRC has configured CTCH resources before, proceeding to step 5 directly;

00005. According to the requirement of BMC, RRC controls L2 and L1 with primitive C′3 to receive Cell Broadcast Information on the CTCH at the prescribed time; RRC may control L1 to continuously receive CTCH BS (CTCH Block Set) or skip some CTCH BSs;

00716. After processing the data frame received from the CTCH accordingly, L1 and L2 submit it to BMC in the format of BMC message (i.e. BMC PDU) with primitive P′3. PDU means Protocol Data Unit, which indicates the message format that BMC can identify and create;

00007. BMC analyses the received message. If it is MBMS service announcement message, BMC forwards it with primitive P′2 to MBMSC, at the same time, the reception of this time is completed; otherwise, proceeding to step 8;

00008. If the message received by BMC is a schedule message, proceeding to step 9; otherwise, proceeding to step 3;

00729. BMC analyses the schedule message that was received most recently, and checks whether the schedule period described by the schedule message includes the Multimedia Broadcast/Multicast Service (MBMS) service announcement message. If so, proceeding to step 12; otherwise, BMC finds the position of the next schedule message and requests RRN to receive the next schedule message with primitive C′1;

000010. RRC controls L1 and L2 with primitive C′3 to receive the next schedule message at the prescribed time;

000011. After processing the message received from the CTCH accordingly, L1 and L2 forward the schedule message to BMC with primitive P′3, then proceeding to step 9;

000012. BMC finds the position of MBMS service announcement message, and requests RRC with primitive C′1 to receive MBMS service announcement message at the prescribed time;

000013. RRC controls L1 and L2 with primitive C′3 to receive MBMS service announcement message at the prescribed time;

000014. After processing the message received from the CTCH accordingly, L1 and L2 forwards MBMS service announcement message to BMC with primitive P′3;

000015. BMC forwards the MBMS service announcement message to MBMS with primitive P′2 and the reception of this time is completed.

0000Notice:

0073Cell broadcast is transferred through Common Traffic Channel (CTCH), which is a logical channel and is multiplexed with other logical channels into transfer channel FACH together by Medium Access Control sublayer MAC. FACH is then multiplexed together with other transfer channels into physical channel S-CCPCH by physical layer (PHY). An example of CTCH being eventually mapped onto S-CCPCH is shown in <figref idref="DRAWINGS">FIG. 11</figref>, in which CTCH is assigned periodically on the S-CCPCH, and this period is called as CTCH Transfer Interval (CTCH TTI). One CTCH BS that includes the whole or part content of Cell Broadcast Message can be transferred in a CTCH TTI.

0074Schedule period is composed of a group of CTCH BSs (from 1 to 255). The introduction of schedule period makes CTCH BSs transferred on the CTCH be organized into a continuous schedule period.

0075A Process of UTRAN Sending MBMS Service Announcement Message

0076For UTRAN, the process of sending MBMS service announcement message in multicast service and in broadcast service is the same. In addition, this process in all cells controlled by the UTRAN is the same also. This process will be explained in the following with reference to the functional diagram of <figref idref="DRAWINGS">FIG. 10</figref> by way of one cell as an example:

00771. MBMSC receives a signaling message M1 sent from core network node. Here, M1 informs UTRAN to perform the process of MBMS service announcement. M1 includes necessary parameters for MBMS service announcement, such as times for sending MBMS service announcement and the time interval. The core network node that sends M1 signaling message can be SGSN or CBC;

00002. MBMSC requests BMC with primitive P1 to send MBMS service announcement message. The primitive P1 includes necessary parameters for constructing MBMS service announcement message;

00783. After receiving the primitive P1, BMC constructs MBMS service announcement message and saves it in its own sending memory block, and starts up a counter for this message. The initial value of the counter is equal to the required times of sending message. If the message is required to send for infinite times, the initial value of the counter is assigned with zero or negative value;

00794. BMC estimates transmission rate (hereinafter referred to as Vneed) needed on the CTCH according to all messages (including MBMS service announcement messages and other broadcast messages) currently saved in the sending memory block. If the actual transmission rate (hereinafter referred to as Vctch) on the CTCH is 0 (i.e. this cell hasn't allocated CTCH resources) or is much smaller or larger than Vneed, BMC reports the actually needed transmission rate Vneed to RRC with primitive C1 and requests RRC to establish or adjust CTCH resources. During the period of BMC waiting for RRC configuring CTCH resources, if Vctch does not match but it isn't equal to zero: when Vctch is smaller than Vneed, BMC can still select some messages with high priority and short length to transfer; when Vctch is much larger than Vneed, resources on CTCH can completely meet the need of message transfer, but it will only result in waste. So as described above, BMC still needs to report to RRC;

00805. RRC controls L1 and L2 with primitive C3 to establish CTCH or adjust CTCH configuration to make CTCH transmission rate match with Vneed. RRC informs BMC the new configuration parameters of CTCH with primitive C2. What need to be mentioned is that after BMC receives the primitive C2, whether CTCH resource adjustment is performed successfully by RRC or not, only if Vctch is not equal to zero, BMC will still continue to send broadcast message as described in step 4;

00816. BMC adds descriptions for MBMS service announcement message to a pending-for-sending schedule message, and then BMC arranges MBMS service announcement message on a certain position of the schedule period following the schedule message for future sending;

00007. BMC sends the schedule message with primitive P3;

00008. BMC sends MBMS service announcement message at the prescribed time with primitive P3;

00829. After reducing the counter's value by one, BMC judges: if the value of the counter is negative, it means that MBMS service announcement message is required to send for infinite times, then proceeding to step 10 after adding 1 to the value of the counter; if the value of the counter is positive, proceeding to step 10 directly; if the value is zero, it means that the times of sending MBMS service announcement message has reached the requirement, then BMC returns confirmation information to MBMSC with primitive P2 and the process of MBMS service announcement for this time is completed;

000010. BMC waits on-timing according to the time interval that MBMS service announcement message is required to send, and when the time expires for sending the next MBMS service announcement message, proceeding to step 6.

0083A Process of UE Receiving MBMS Service Notification Message

0084For UE, the process of receiving MBMS service notification message in multicast service and in broadcast service is the same. This process will be explained in the following with reference to the functional diagram of <figref idref="DRAWINGS">FIG. 10</figref>:

00001. When MBMSC (MBMS Service Control module) decides to receive MBMS service notification message, MBMSC sends a request to BMC (Broadcast/Multicast Control protocol) with primitive P′1;

00002. If BMC has never received any broadcast message before, proceeding to step 3; otherwise, proceeding to step 9;

00853. BMC informs RRC to receive the broadcast message with primitive C′1. The parameters included in C′1 can inform RRC to receive RMC preferred message only at prescribed time and skip some messages. But in step 3, BMC must require RRC to receive all continuous broadcast messages;

00864. If RRC has not configured CTCH before, RRC configures link layer (hereinafter referred to as L2) and physical layer (hereinafter referred to as L1) to enable UE to receive information on the CTCH and feedbacks necessary CTCH configuration information with primitive C′2 to BMC at the same time, thereafter proceeding to step 5; if RRC has configured CTCH resources before, proceeding to step 5 directly;

00005. According to the requirement of BMC, RRC controls L2 and L1 with primitive C′3 to receive Cell Broadcast Information on the CTCH at the prescribed time; RRC can control L1 to continuously receive CTCH BS or skip some CTCH BSs;

00876. After processing the data frame received from the CTCH accordingly, L1 and L2 submit it to BMC in the format of BMC message (i.e. BMC PDU) with primitive P′3. PDU means Protocol Data Unit, which indicates the message format that BMC can identify and create;

00007. BMC analyses the received message. If it is a MBMS service notification message, BMC forwards it to MBMSC with primitive P′2, at the same time, the reception of this time is completed; otherwise, proceeding to step 8;

00008. If the message received by BMC is a schedule message, proceeding to step 9; otherwise, proceeding to step 3;

00889. BMC analyses the schedule message that was received most recently, and checks whether the schedule period described by the schedule message includes MBMS service notification message. If so, proceeding to step 12; otherwise, BMC finds the position of the next schedule message and requests RRC to receive the next schedule message with primitive C′1;

000010. RRC controls L1 and L2 with primitive C′3 to receive the next schedule message at the prescribed time;

000011. After processing the message received from the CTCH accordingly, L1 and L2 forwards the schedule message to BMC with primitive P′3 and then proceeding to step 9;

000012. BMC finds the position of the MBMS service notification message and requests RRC with primitive C′1 to receive MBMS service notification message at prescribed time;

000013. RRC controls L1 and L2 with primitive C′3 to receive MBMS service notification message at the prescribed time;

000014. After processing the message received from the CTCH accordingly, L1 and L2 forward the MBMS service notification message to BMC with primitive P′3;

000015. BMC forwards the MBMS service notification message to MBMSC with primitive P′2 and the reception of this time is completed.

0089A Process of UTRAN Sending a MBMS Service Notification Message

0090For UTRAN, the process of sending MBMS service notification message in multicast service and in broadcast service is the same. In addition, this process in all cells controlled by the UTRAN is the same also. This process will be explained in the following with reference to the functional diagram of <figref idref="DRAWINGS">FIG. 10</figref> by way of one cell as an example:

00911. MBMSC receives the signaling message M2 sent from core network node. Here, M2 informs UTRAN to perform the process of MBMS service notification. M2 includes necessory parameters for MBMS service notification, such as times for sending MBMS service announcement and the time interval. The core network node that sends M2 signaling message can be SGSN or CBC;

00002. MBMSC requests BMC to send MBMS service notification message with primitive P1. The primitive P1 includes necessary parameters for constructing MBMS service notification message;

00923. After receiving the primitive P1, BMC constructs MBMS service notification message and saves it in its own sending memory block, and starts up a counter for this message. The initial value of the counter is equal to the required times of sending message. If the message is required to send for infinite times, the initial value of the counter is assigned with zero or negative value;

00934. BMC estimates transmission rate (hereinafter referred to as Vneed) needed on the CTCH according to all messages (including MBMS service notification messages and other broadcast messages) currently saved in the sending memory block. If the actual transmission rate (hereinafter referred to as Vctch) on the CTCH is 0 (i.e. this cell hasn't allocated CTCH resources) or is much smaller or larger than Vneed, BMC reports the actually needed transmission rate Vneed to RRC with primitive C1 and requests RRC to establish or adjust CTCH resources. During the period of BMC waiting for RRC configuring the CTCH resources, if Vctch does not match but it isn't equal to zero: when Vctch is smaller than Vneed, BMC can still select some messages with high priority and short length to transfer; when Vctch is much larger than Vneed, resources on CTCH can completely meet the need of message transfer, but it will only result in waste. So as described in above, BMC still needs to report to RRC;

00945. RRC controls L1 and L2 with primitive C3 to establish CTCH or adjust CTCH configuration to make CTCH transmission rate match with Vneed. RRC informs BMC the new configuration parameters of CTCH with primitive C2. It should be noticed that after BMC receives the primitive C2, whether CTCH resource adjustment performed successfully by RRC or not, only if Vctch is not equal to zero, BMC will still continue to send broadcast messages as described in step 4;

00956. BMC adds descriptions for MBMS service notification message to a pending-for-sending schedule message, and then BMC arranges MBMS service notification message on a certain position of the schedule period following the schedule message for future sending;

00007. BMC sends the schedule message with primitive P3;

00008. BMC sends MBMS service notification message at the prescribed time with primitive P3;

00969. After reducing the counter's value by one, BMC judges: if the value of the counter is negative, it means that MBMS service notification message is required to send for infinite times, then proceeding to step 10 after adding 1 to the value of the counter; if the value of the counter is positive, proceeding to step 10 directly; if the value is zero, it means that the times of sending MBMS service notification message has met the requirement, then BMC returns confirmation information to MBMSC with primitive P2 and the process of MBMS Service notification for this time is completed;

000010. BMC waits on-timing according to the time interval that MBMS service notification message is required to send. When the time expires for sending the next MBMS service notification message, proceeding to step 6.

0097Message Structures Used in the Processes of MBMS Service Announcement and MBMS Service Notification

0000Schedule Message

0098A schedule message occupies one or more CTCH BSs included in a schedule period. The schedule message describes the schedule period that directly follows the schedule message to which the schedule message belongs, which makes continuous schedule messages be able to describe continuous schedule periods. Its structure is shown in Table 1. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 1</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of schedule message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="70PT" align="left" /><colspec colname="2" colwidth="35PT" align="left" /><colspec colname="3" colwidth="35PT" align="left" /><colspec colname="4" colwidth="77PT" align="left" /><tbody valign="top"><row><entry>Information Element</entry><entry /><entry>Plurality</entry><entry /></row><row><entry>(IE)</entry><entry>Need</entry><entry>existence</entry><entry>Semantics description</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Message Type</entry><entry>necessary</entry><entry /><entry /></row><row><entry>Offset to Begin CTCH</entry><entry>necessary</entry></row><row><entry>BS_index</entry></row><row><entry>Length of Scheduling</entry><entry>necessary</entry></row><row><entry>Period</entry></row><row><entry>New Message Bitmap</entry><entry>necessary</entry></row><row><entry>Message Description</entry><entry>necessary</entry><entry>1 To <the</entry><entry>Message description</entry></row><row><entry /><entry /><entry>length of</entry><entry>includes a plurality of</entry></row><row><entry /><entry /><entry>schedule</entry><entry>items, wherein each item</entry></row><row><entry /><entry /><entry>period></entry><entry>describes the message</entry></row><row><entry /><entry /><entry /><entry>content included in one</entry></row><row><entry /><entry /><entry /><entry>CTCH BS of the</entry></row><row><entry /><entry /><entry /><entry>schedule period. The i-th</entry></row><row><entry /><entry /><entry /><entry>item corresponds to the i-</entry></row><row><entry /><entry /><entry /><entry>th bit of new message</entry></row><row><entry /><entry /><entry /><entry>bitmap.</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0099Message Type, the sub-information element in schedule message, is included in all the cell broadcast message. It describes the message types, whose coding is shown in Table 2. <tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 2</entry></row><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Coding of Information Element in Schedule Message</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="84PT" align="center" /><colspec colname="2" colwidth="133PT" align="left" /><tbody valign="top"><row><entry>1</entry><entry>CBS Message</entry></row><row><entry>2</entry><entry>Schedule Message</entry></row><row><entry>3</entry><entry>CBS41 Message</entry></row><row><entry>4</entry><entry>MBMS Service Announcement</entry></row><row><entry /><entry>Message</entry></row><row><entry>5</entry><entry>MBMS Service Notification</entry></row><row><entry /><entry>Message</entry></row><row><entry>0, 6 . . . 255</entry><entry>Reserved for future use (PDU with</entry></row><row><entry /><entry>any coding herein shall be discarded</entry></row><row><entry /><entry>by the protocol of this version.)</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0100New message bitmap, the sub-information element in schedule message, is a map of bits, each bit of which corresponding to a CTCH BS in the schedule period. The bit value is 1, which indicates that CTCH BS includes a new message, and the bit value is 0, which indicates that CTCH BS includes an old message, whose structure is shown in Table 3. <tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 3</entry></row><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of new message bitmap of</entry></row><row><entry>Information Element in schedule message</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="9"><colspec colname="1" colwidth="35PT" align="center" /><colspec colname="2" colwidth="28PT" align="center" /><colspec colname="3" colwidth="35PT" align="center" /><colspec colname="4" colwidth="28PT" align="center" /><colspec colname="5" colwidth="21PT" align="center" /><colspec colname="6" colwidth="14PT" align="center" /><colspec colname="7" colwidth="21PT" align="center" /><colspec colname="8" colwidth="14PT" align="center" /><colspec colname="9" colwidth="21PT" align="center" /><tbody valign="top"><row><entry>CTCH</entry><entry>CTCH</entry><entry>CTCH</entry><entry>. . .</entry><entry /><entry /><entry /><entry /><entry>1</entry></row><row><entry>BS</entry><entry>BS</entry><entry>BS</entry></row><row><entry>Index</entry><entry>Index</entry><entry>Index</entry></row><row><entry>B</entry><entry>B + 1</entry><entry>B + 2</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry>2</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry>. . .</entry></row><row><entry /><entry>. . .</entry><entry>CTCH</entry><entry>CTCH</entry><entry>0</entry><entry>0</entry><entry>0</entry><entry>0</entry><entry>n</entry></row><row><entry /><entry /><entry>BS</entry><entry>BS</entry></row><row><entry /><entry /><entry>Index</entry><entry>Index</entry></row><row><entry /><entry /><entry>E-1</entry><entry>E</entry></row><row><entry namest="1" nameend="9" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0101There is a plurality of sub-information element message descriptions in a schedule message, whose number is equal to the number of CTCH BSs included in the schedule period described by the schedule message. Each CTCH BS is described by one message description, whose structure is shown in Table 4. <tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 4</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of Information Element Message description in schedule message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="63PT" align="left" /><colspec colname="2" colwidth="35PT" align="left" /><colspec colname="3" colwidth="56PT" align="left" /><colspec colname="4" colwidth="63PT" align="left" /><tbody valign="top"><row><entry>Information Element</entry><entry /><entry /><entry>Semantics</entry></row><row><entry>(IE)</entry><entry>Need</entry><entry>Type</entry><entry>description</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Message</entry><entry>necessary</entry><entry>Enumerated value</entry><entry /></row><row><entry>Description Type</entry><entry /><entry>(0 . . . 255)</entry></row><row><entry /><entry /><entry>Table 5</entry></row><row><entry>Message ID</entry><entry>Decision</entry><entry>Enumerated value</entry></row><row><entry /><entry>condition</entry><entry>(0 . . . 2¹⁶− 1)</entry></row><row><entry /><entry>MDT11</entry></row><row><entry>Offset to CTCH BS</entry><entry>Decision</entry><entry>Integer</entry></row><row><entry>index of first</entry><entry>condition</entry><entry>(0 . . . 255)</entry></row><row><entry>transmission</entry><entry>MDT22</entry></row><row><entry>MBMS service</entry><entry>Decision</entry><entry>IP</entry><entry>This Information</entry></row><row><entry>Identity</entry><entry>condition</entry><entry>multicast-address</entry><entry>Element is used to</entry></row><row><entry /><entry>MDT33</entry><entry /><entry>identify the types of</entry></row><row><entry /><entry /><entry /><entry>MBMS service</entry></row><row><entry>MBMS service</entry><entry>Decision</entry><entry>TMGI</entry><entry>This Information</entry></row><row><entry>Identity</entry><entry>condition</entry><entry /><entry>Element is used to</entry></row><row><entry /><entry>MDT44</entry><entry /><entry>identify the type of</entry></row><row><entry /><entry /><entry /><entry>MBMS service.</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0102The types of the message included by CTCH BSs are described by the Sub-information Element Message Description Type of Message Description Information Element, whose coding is shown in Table 5. <tables id="TABLE-US-00005" num="5"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 5</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Coding of the types of Sub-information Element Message</entry></row><row><entry>Description in Message Description Information Element</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="42PT" align="center" /><colspec colname="2" colwidth="175PT" align="left" /><tbody valign="top"><row><entry>Values</entry><entry>Interpretation</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>0</entry><entry>Repetition of new BMC message within schedule period</entry></row><row><entry>1</entry><entry>New messge</entry></row><row><entry>2</entry><entry>Reading advised</entry></row><row><entry>3</entry><entry>Reading optional</entry></row><row><entry>4</entry><entry>Repetition of old BMC message within schedule period</entry></row><row><entry>5</entry><entry>Old message</entry></row><row><entry>6</entry><entry>Schedule message</entry></row><row><entry>7</entry><entry>CBS41 message</entry></row><row><entry>8</entry><entry>MBMS service announcement message</entry></row><row><entry>9</entry><entry>MBMS serivce notification message</entry></row><row><entry>10. 255</entry><entry>Reserved for future use</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0103Since except for Message Description Types, other Sub-information Elements do not absolutely exist, their existence is determined by the decision conditions. The decision condition for each Sub-information existence is shown in Table 6. <tables id="TABLE-US-00006" num="6"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 6</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Decision Conditions for deciding whether a certain Sub-</entry></row><row><entry>information Elements exist in Information Element Message Description</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="63PT" align="left" /><colspec colname="2" colwidth="154PT" align="left" /><tbody valign="top"><row><entry>Decision condition</entry><entry>Interpretation</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>MDT11</entry><entry>If Message Description Types = 1 or 5, then:</entry></row><row><entry /><entry>The Information Element of Message Idenity exists.</entry></row><row><entry>MDT22</entry><entry>If Message Description Types = 0 or 4, then:</entry></row><row><entry /><entry>The Information Element of Offset to CTCH BS</entry></row><row><entry /><entry>index of first transmission exists and indicates the</entry></row><row><entry /><entry>offset of CTCH BS that is the first one including</entry></row><row><entry /><entry>broadcast message in this schedule period to</entry></row><row><entry /><entry>schedule message.</entry></row><row><entry>MDT33</entry><entry>If the Message Description Types = 8 (MBMS</entry></row><row><entry /><entry>service announcement message) and the message</entry></row><row><entry /><entry>structure in Table 8 is selected for use, then:</entry></row><row><entry /><entry>The Information Element of MBMS service Identity</entry></row><row><entry /><entry>exists and is identified by IP multicast address;</entry></row><row><entry>MDT44</entry><entry>If the Message Description Types = 9 (MBMS</entry></row><row><entry /><entry>service notification message), then: The Information</entry></row><row><entry /><entry>of MBMS service Identity exists and is identified</entry></row><row><entry /><entry>by TMGI;</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><br /> MBMS Service Announcement Message

0104MBMS service announcement message describes parameters such as MBMS service types and service areas, and may have two kinds of structures: the first kind of structure describes a plurality of MBMS services, as shown in Table 7; and the second kind of structure describes single MBMS service, as shown in Table 8. <tables id="TABLE-US-00007" num="7"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 7</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of the first kind of MBMS service announcement message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="77PT" align="left" /><colspec colname="2" colwidth="35PT" align="left" /><colspec colname="3" colwidth="105PT" align="left" /><tbody valign="top"><row><entry>Information Element</entry><entry /><entry /></row><row><entry>(IE)</entry><entry>Need</entry><entry>Semantics description</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Message Type</entry><entry>necessary</entry><entry /></row><row><entry>Service Number</entry><entry>necessary</entry><entry>The number of MBMS services</entry></row><row><entry /><entry /><entry>described in the message</entry></row><row><entry>MBMS service Identity 1</entry><entry /><entry>The Identity of the first MBMS</entry></row><row><entry /><entry /><entry>service: IP multicast address</entry></row><row><entry>APN 1</entry><entry /><entry>The domain name of access point,</entry></row><row><entry /><entry /><entry>for pointing to one GGSN</entry></row><row><entry>UE capability 1</entry><entry /><entry>The capability of UE required</entry></row><row><entry /><entry /><entry>by the first MBMS service</entry></row><row><entry>. . .</entry></row><row><entry>MBMS service Identity n</entry><entry /><entry>The Identity of the n-th MBMS</entry></row><row><entry /><entry /><entry>service, n = Service Number</entry></row><row><entry>APN n</entry></row><row><entry>UE capability n</entry><entry /><entry>The capability of UE required</entry></row><row><entry /><entry /><entry>by the n-th MBMS service</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0105<tables id="TABLE-US-00008" num="8"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 8</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of the second kind of MBMS service announcement message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="77PT" align="left" /><colspec colname="2" colwidth="35PT" align="left" /><colspec colname="3" colwidth="105PT" align="left" /><tbody valign="top"><row><entry>Information Element</entry><entry /><entry /></row><row><entry>(IE)</entry><entry>Need</entry><entry>Semantics description</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Message Type</entry><entry>necessary</entry><entry /></row><row><entry>MBMS Service Identity</entry><entry /><entry>Identity of this MBMS service:</entry></row><row><entry /><entry /><entry>IP multicast address</entry></row><row><entry>APN</entry></row><row><entry>UE capability</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><br /> MBMS Service Notification Message

0106MBMS service notification message is notification information about a certain forthcoming MBMS service and informs UE to prepare for the MBMS service. Its structure is shown in Table 9. <tables id="TABLE-US-00009" num="9"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 9</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>structure of MBMS service notification message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="77PT" align="left" /><colspec colname="2" colwidth="35PT" align="left" /><colspec colname="3" colwidth="105PT" align="left" /><tbody valign="top"><row><entry>Information Element</entry><entry /><entry /></row><row><entry>(IE)</entry><entry>Need</entry><entry>Semantics description</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Message Type</entry><entry>necessary</entry><entry /></row><row><entry>MBMS Service Group</entry><entry>necessary</entry><entry>Identity of the MBMS service</entry></row><row><entry>Identity</entry><entry /><entry>group: TMGI</entry></row><row><entry>QoS QOS</entry><entry>necessary</entry><entry>Quality of Service that can be</entry></row><row><entry /><entry /><entry>provided by this MBMS service</entry></row><row><entry>Random Mechanism</entry><entry>Optional</entry><entry>Pre-coding random mechanism</entry></row><row><entry>Random Value</entry><entry>Optional</entry></row><row><entry>Mask Value</entry><entry>Optional</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0107To avoid the air congestion resulted from simultaneous responses to access network when a plurality of UEs receive MBMS service notification message simultaneously, there should be such a mechanism that allows large number of UEs to respond at different time. Sub-information Element random mechanism, random value and mask value in the MBMS service notification message are all set for this. Random mechanism indicates which operation mode to be used by coding. IMSI of UE (the unique ID of an UE over the world), random value and mask value are participated in operation together and the operation results is used as time delay that UE initiates a response with time as the unit (e.g. millisecond). Table 10 shows the coding modes of random mechanism. <tables id="TABLE-US-00010" num="10"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 10</entry></row><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>coding of random mechanism of Sub-information Element in</entry></row><row><entry>MBMS service notification message</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49PT" align="center" /><colspec colname="2" colwidth="168PT" align="left" /><tbody valign="top"><row><entry>0</entry><entry>After IMSI modulo the random value, performing</entry></row><row><entry /><entry>bit-by-bit AND operation with the mask value.</entry></row><row><entry>1</entry><entry>After IMSI adding to the random value,</entry></row><row><entry /><entry>performing bit-by-bit AND operation with the</entry></row><row><entry /><entry>mask value.</entry></row><row><entry>2</entry><entry>After IMSI multiplying with the random value,</entry></row><row><entry /><entry>performing bit-by-bit AND operation with the</entry></row><row><entry /><entry>mask value.</entry></row><row><entry>3</entry><entry>After IMSI dividing by the random value,</entry></row><row><entry /><entry>performing bit-by-bit AND operation with the</entry></row><row><entry /><entry>mask value.</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

EFFECTS OF THE INVENTION

0000<ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0108"> 1. Effectively use the network resources: since the processes of MBMS service announcement and service notification are all performed via cell broadcast, the one-to-multiple characteristic of cell broadcast reduces the load of resources resulted from these two processes effectively; </li><li id="ul0001-0002" num="0109"> 2. Effectively reduce the standby time of UEs: since cell broadcast enable UEs to receive cell broadcasts in discontinuous mode, it remarkablely increases the lifetime of UEs' batteries; </li></ul>

0110Scalability: since cell broadcast uses messages of variable length, it can add parameters for future use effectively.