This application claims priority under 35 U.S.C. § 119 to an application entitled “Method for Transmitting and Receiving Control Information in a Mobile Communication System Supporting Multimedia Broadcast/Multicast Service” filed in the Korean Intellectual Property Office on Apr. 16, 2004 and assigned Serial No. 2004-26266, the contents of which are incorporated herein by reference.
1. Field of the Invention
The present invention relates generally to a mobile communication system supporting a Multimedia Broadcast/Multicast Service (MBMS), and in particular, to a method for efficiently transmitting control information for an MBMS service.
2. Description of the Related Art
As the communication technology develops, a service provided in a mobile communication system is evolving into a multimedia broadcast/communication service capable of supporting not only the conventional voice service but also a packet service and a multimedia service to enable the transmission of large amounts bulk data such as packet data and circuit data. In order to support the multicast broadcast/communication, there has been proposed a Multimedia Broadcast/Multicast Service (hereinafter referred to as an “MBMS service”) in which one or more multimedia data sources provide a service to a plurality of user equipments (UEs).
The MBMS service can transmit the same multimedia data to a plurality of recipients through a wireless network. The MBMS service can save wireless transmission resources by allowing a plurality of recipients to share one radio channel. The MBMS service supports the transmission of such multimedia data as real-time image and voice, still image, text, etc., and can simultaneously transmit voice data and image data based on a transfer mode of the multimedia data. This requires a large amount of transmission resources. In the MBMS service, because the same data should transmitted to a plurality of cells where users are located, point-to-point (PtP) connection or point-to-multipoint (PtM) connection is achieved according to the number of users located in each cell. The PtP connection allocates a dedicated channel to each UE and provides a desired MBMS service to the UE through the dedicated channel on an individual basis. However, the PtM connection allocates a common channel to multiple UEs requesting the same MBMS service and provides the MBMS service to the UEs through the common channel.
The following description will be made with reference to a 3rd Generation Partnership Project (3GPP) mobile communication network, which is a typical 3rd generation asynchronous mobile communication network.
The UE#1120, the UE#2121 and the UE#n 122 are UEs capable of receiving the MBMS service, and a plurality of UEs can be located in each cell. A basic service unit for the MBMS service is the cell, and the MBMS service is provided through a PtP channel or a PtM channel based on the radio environment of the cell and the number of UEs desiring to receive the MBMS service located in the cell. A counting process to determine the number of UEs is performed to determine which type of MBMS service is preferred.
In order to provide the MBMS service, a plurality of control information messages are transmitted, which include not only data for the MBMS service, but also information on the MBMS service, information on a channel over which the MBMS data is transmitted, information indicating a start time of the MBMS service, information on a change in transfer mode during transmission of the MBMS data, information on neighbor cells, if any, where the MBMS service is provided, and information on an MBMS service provided in the current cell.
Disclosed herein are control plain (C-Plain) signaling 201 and User plain (U-Plain) information 202. The C-Plain signaling 201 and the U-Plain information 202 are Non-Access Stratum (NAS) messages, which the UTRAN is not required to know because they are not used for wireless connection between a UE and the UTRAN. Unlike the NAS messages, messages directly used for the wireless connection between the UTRAN and the UE are called Access Stratum (AS) messages, and the AS messages indicate signaling used under a radio resource controller (RRC) 203.
The RRC 203 controls a physical layer (L1) 210, and a Medium Access Control (L2/MAC) 208, a Radio Link Control (L2/RLC) 206, a Packet Data Convergency Protocol (L2/PDCP) 204, and a Broadcast/Multicast Control (L2/BMC) 205 for Layer 2 (L2), all of which are related to an access to a UE and a UTRAN, to control all of the events related to a connection between the UE and the UTRAN. These include physical call setup, logical call setup, control information transmission/reception, and measurement data transmission/reception between the UE and the UTRAN.
The L2/PDCP 204 receives the U-Plain information 202 of a NAS layer, processes the received U-Plain information 202 using an appropriate protocol, and transmits the processing result to the L2/RLC 206. The L2/BMC 205 receives the data needed for the broadcast/multicast, processes the received data using an appropriate protocol, and transmits the processing result to the L2/RLC 206.
The L2/RLC 206 receives a control message output from the RRC 203, processes the received control message in an appropriate format in an RLC#1261 and an RLC#2262 taking a feature of the control message into consideration, and transmits the processing result to the L2/MAC 208 using logical channels 207. Further, the L2/RLC 206 receives data from the L2/PDCP 204 and the L2/BMC 205, processes the received data in an appropriate format in an RLC#1263 and an RLC#n 264, and transmits the processing result to the L2/MAC 208 using the logical channels 207. The number of RLC entities (261 to 264) included in the L2/RLC 206 is determined according to the number of types of the logical channels 207 and the number of radio links.
The logical channels 207 are roughly divided into a dedicated type and a common type according to whether they are for a specified UE(s) or for a plurality of UEs, and into a control type and a traffic type according to a feature of a message transmitted therethrough.
Table 1 illustrates types and functions of the logical channels 207 used in the 3GPP standard.
The L2/MAC 208, under the control of the RRC 203, manages radio resources between a UE and a UTRAN, manages a connection between the UE and the UTRAN, or maps data received from the L2/RLC 206 through logical channels to transport channels 209, and transmits the mapping result to the L1 layer 210.
Table 2 illustrates types and functions of the transport channels 209 used in the 3GPP standard and a mapping relation with the logical channels 207.
Aside from the transport channels described in Table 2, such transport channels as an uplink shared channel (USCH) and a common packet channel (CPCH) are defined in the current 3GPP.
As illustrated, data on the transport channels transmitted to the L1 layer 210 is mapped to physical channels through an appropriate process, and then transmitted to a UE or a UTRAN.
The physical channels include a Primary Common Control Physical Channel (P-CCPCH) for the transmission of a BCH, a Secondary Common Control Physical Channel (S-CCPCH) for the transmission of a PCH and a FACH, a Dedicated Physical Channel (DCH) for the transmission of a DCH, a Physical Downlink Shared Channel (PDSCH) for the transmission of a DSCH, a High Speed Physical Downlink Shared Channel (HS-PDSCH) for the transmission of a HS-DSCH, and a Physical Random Access Channel (PRACH) for the transmission of a RACH. In addition, the physical channels include a Pilot Channel, a Primary Synchronization Channel, a Secondary Synchronization Channel, a Paging Indicator Channel, an Acquisition Indicator Channel, and a Physical Common Packet Channel.
Aside from the foregoing logical channels, logical channels for supporting an MBMS service are defined in the 3GPP. The newly defined logical channels include an MBMS Traffic Channel (MTCH) over which MBMS data is transmitted for the MBMS service, and an MBMS Control Channel (MCCH) over which control information needed for reception of the MBMS service is transmitted. The two logical channels are mapped to the FACH which is a transport channel, and then transmitted to UEs scheduled to receive the MBMS service, through the S-CCPCH which is a physical channel.
The “control information” refers to (i) information on a transmission start and a transmission end of MBMS data, and a logical channel, a transport channel and a physical channel, over all of which MBMS data is transmitted, (ii) information on neighbor cells in which the same MBMS is provided, and (iii) information on MBMS services provided in the current cell. Information elements (IEs) needed for the control information messages can be separately defined for each individual message. The messages may overlap each other in terms of the IEs defined for each individual message.
In order to prevent the unnecessary overlapping of the IEs, there is a demand for a method to precisely define the IEs needed for each control information message and appropriately arrange the IEs according to a use of the control information messages. In addition, the number of the control information messages increases the amount of control information that a UE should receive for reception of an MBMS service and causes generation of periodically repeated control information messages to support mobility of the UE, a demand for preventing the duplicate reception of the IEs of the control information messages is required. Furthermore, there is a demand for a method that is capable of minimizing a reception time for which the UE receives the control information messages.
It is, therefore, an object of the present invention to provide a method for transmitting and receiving control information messages needed for an MBMS service.
It is another object of the present invention to provide a method for minimizing the signaling overhead in the process of transmitting control information messages for an MBMS service.
It is another object of the present invention to provide an efficient scheduling method for the transmission of control information messages for an MBMS service.
It is further another object of the present invention to provide a method for preventing the duplicate reception of control IEs having the same contents in the process of receiving control information messages for an MBMS service.
It is still another object of the present invention to provide a method for minimizing the power consumption of a UE in the process of receiving control information messages for an MBMS service.
According to one aspect of the present invention, there is provided a method for transmitting control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of generating an MBMS notification information message indicating a significant change in an MBMS service; and transmitting the MBMS notification information message to at least one user equipment (UE) located in a cell capable of providing the MBMS service; wherein the MBMS notification information message includes an MBMS service identifier (ID), a cause value indicating the cause for the notification, frequency information for the MBMS service, and continue reading information indicating whether to continuously receive control information messages transmitted after the MBMS notification information message.
According to another aspect of the present invention, there is provided a method for receiving control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of receiving a notification indicator (NI) for an MBMS service; if the received notification indicator is affirmative, determining if a current frame corresponds to a start time of a predetermined modification period (MP); if the current frame arrives at the start time of the modification period, receiving an MBMS notification information message for indicating a significant change in the MBMS service, the MBMS notification information message includes an MBMS service identifier (ID), a cause value indicating the cause for the notification, frequency information for the MBMS service, and continue reading information indicating whether to continuously receive control information messages transmitted after the MBMS notification information message; and checking the cause value of the MBMS notification information message, and performing an operation according to the cause value.
According to further another aspect of the present invention, there is provided a method for transmitting control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of generating an MBMS service list message including control information for at least one MBMS service of a current cell; and transmitting the MBMS service list message to at least one user equipment (UE) located in the current cell, wherein the MBMS service list message includes an MBMS service identifier (ID), information indicating a transfer mode of a corresponding MBMS service, and frequency information for the corresponding MBMS service.
According to further another aspect of the present invention, there is provided a method for receiving control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of determining if a current frame corresponds to a start time of a predetermined repetition period (RP), if there is a need for receiving an MBMS service list message including control information for at least one MBMS service of a current cell; if the current frame arrives the start time of the repetition period, receiving the MBMS service list message, the MBMS service list message includes an MBMS service identifier (ID), information indicating a transfer mode for a corresponding MBMS service, and frequency information for the corresponding MBMS service; determining if there is an ID of a joined MBMS service in the MBMS service list message; checking a transfer mode of the joined MBMS service, if there is an ID of the joined MBMS service in the MBMS service list message; and receiving the joined MBMS service according to whether the transfer mode of the joined MBMS service corresponds to point-to-multipoint (PtM), point-to-point (PtP), or no-RB (radio bearer).
According to further another aspect of the present invention, there is provided a method for transmitting control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of generating an MBMS common radio bearer (RB) information message including common control information for RBs, physical channels and transport channels used for MBMS services provided in a current cell; and transmitting the MBMS common RB information message to at least one user equipment (UE) located in the current cell, wherein the MBMS common RB information message includes an RB information list for RBs commonly used by the MBMS services, transport channel information and physical channel information.
According to further another aspect of the present invention, there is provided a method for receiving control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of receiving an MBMS common radio bearer (RB) information message, if there is a need for receiving the MBMS common RB information message including common control information for RBs, physical channels and transport channels used for MBMS services provided in a current cell, the MBMS common RB information message includes an RB information list for RBs commonly used by the MBMS services, transport channel information and physical channel information; and acquiring the RB information list, the transport channel information and the physical channel information, all of which are included in the MBMS common RB information message.
According to further another aspect of the present invention, there is provided a method for transmitting control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of generating an MBMS service point-to-multipoint (PtM) radio bearer (RB) information message including control information for MBMS services provided in a current cell and neighbor cells; and transmitting the MBMS service PtM RB information message to at least one user equipment (UE) located in the current cell, wherein the MBMS service PtM RB information message includes current cell RB information including an RB information list for RBs used by MBMS services provided in the current cell, transport channel information and physical channel information, and neighbor cell RB information including an RB information list for RBs used by MBMS services provided in the neighbor cells, transport channel information and physical channel information.
According to further another aspect of the present invention, there is provided a method for receiving control information for supporting a Multimedia Broadcast/Multicast Service (MBMS) service in a mobile communication system providing the MBMS service, the method including the steps of receiving an MBMS notification information message for indicating a significant change in an MBMS service, and receiving an MBMS service point-to-multipoint (PtM) radio bearer (RB) information message including control information for MBMS services provided in a current cell and neighbor cells according to the MBMS notification information message; determining if there is RB information for a joined MBMS service in the MBMS service PtM RB information message; and if there is RB information for the joined MBMS service, acquiring control information for the current cell and the neighbor cells for the joined MBMS service from the MBMS service PtM RB information message.
The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which:
Several preferred embodiments of the present invention will now be described in detail with reference to the annexed drawings. In the following description, a detailed description of known functions and configurations incorporated herein has been omitted for conciseness.
Control information necessary for an MBMS service includes:
Aside from the foregoing information, other control information can be additionally defined. Herein, there are two possible paths through which the control information can be provided to UEs scheduled to receive an MBMS service, and a path used is changed according to a feature of the control information.
A first method transmits the control information through a BCH, and control information that can be transmitted over the BCH can include system information for all of the MBMS services. The system information can include repetition periods of Notification Indicator Channel (NICH) information indicating the presence of the control information for the transmission and a start of an MBMS service, information on a FACH and an S-CCPCH, over both of which an MCCH is transmitted, and control information transmitted over the MCCH. There are 3 possible repetition periods defined: Modification Period (MP), Repetition Period (RP) and Access Info Period (AIP). A detailed description of the periods will be made later with reference to
A second method transmits the control information through an MCCH used for the transmission of the control information for an MBMS service. The control information that can be transmitted over the MCCH can include the information described in items 3 to 8 from among the forgoing necessary control information items. That is, a UE receives the control information of items 3 to 8 through an MCCH depending on the control information of items 1 and 2 received over a BCH. In this case, the control information items transmitted over the MCCH overlap each other in several information details. For example, in order to provide information indicating that a particular MBMS service is effective in a cell, it is necessary to transmit an identifier (ID) for the MBMS service. Also, the ID for the MBMS service is required in order to provide information on a channel type for the MBMS service and a channel over which the MBMS service is transmitted.
Embodiments of the present invention described below define the control information messages necessary for an MBMS service, and propose the following control information message formats to prevent the information elements (IEs) of the control information messages from undergoing a duplicate transmission. Control information messages transmitted over an MCCH, proposed in preferred embodiments of the present invention, include:
Table 3, Table 4, Table 5 and Table 6 below illustrate information elements (IEs) necessary for a description of the present invention for the foregoing control information messages, in which IEs newly defined in the present invention are underlined and expressed in bold. In the following tables, ‘Information Element/Group name’ indicates the names of IEs and the names of groups to which the IEs belong, ‘Need’ indicates whether a corresponding IE is mandatory (MP) or optional (OP), and ‘Multi’ indicates whether the number of IEs is one or several. In addition, ‘Type and reference’ indicates a type in which IEs are expressed, and for example, possible bit expressions include bit-string expression, octet expression, and integer expression. ‘Semantics description’ is a field in which a description is made of the meaning of a corresponding IE, a function of the IE, and which event will happen if the IE is not used. Although many of the possible IEs according to embodiments of the present invention are illustrated herein, particular IEs selected by a system designer can be omitted or unremunerated IEs can be added.
Table 3 illustrates a format of an MBMS Notification Info message and a description of respective IEs.
Table 4 illustrates a format of an MBMS Service List message.
Table 5 illustrates a format of an MBMS Common RB Info message.
Table 6 illustrates a format of an MBMS Service PtM RB Info message.
Referring first to
Reference numeral 410 represents an enlarged period of an MCCH denoted by reference numeral 401. Reference numeral 412 indicates an MBMS Notification Info message and the MBMS Notification Info message is transmitted at a start time of the MP. Reference numeral 411 indicates an MBMS Service PtM RB Info message for a particular MBMS service, and when the MBMS Service PtM RB Info message is transmitted at a start time of the MP or transmitted immediately after the MBMS Notification Info message 412 or when a transfer rate of an MCCH is high, the MBMS Service PtM RB Info message 411 can be transmitted together with the MBMS Notification Info message 412. Reference numeral 413 indicates an MBMS Service List message, and the MBMS Service List message 413 has a list of all of the MBMS services currently provided in or available in the current cell, guaranteeing the continuity of an MBMS service by taking the movement of a UE into consideration. A UE receiving or attempting to receive an MBMS service, receives a Common RB value tag through the MBMS Notification Info message 412 and the MBMS Service List message 413, and if the received Common RB value tag is different from a Common RB value tag currently stored in the UE, the UE receives an MBMS Common RB Info message 415. Reference numeral 414 indicates an MBMS Service PtM RB Info message having PtM RB information for another MBMS service.
In
Referring to
Upon arrival at the start time of the new MP, the UTRAN transmits in step 506 the MBMS Notification Info message, the MBMS Service PtM RB Info message, an MBMS Common RB Info message, and an MBMS Service List message. The MBMS Service List message and the MBMS Common RB Info message are illustrated in Table 4 and Table 5. The MBMS Common RB Info message does not include changes related to a new MBMS service indicated by the MBMS Notification Info message at the current transmission time, but corresponding changes can be transmitted at the time when the MBMS service is performed. The MBMS Service List message can indicate if an MBMS service indicated by the MBMS Notification Info message will be provided in the current cell. In step 507, the UTRAN determines if a counting operation is needed to determine a transfer mode of MBMS data, and if the counting operation is not required, the UTRAN proceeds to step 509. However, if the counting operation is needed, the UTRAN proceeds to step 508. The UTRAN retransmits the MBMS Notification Info message at a start time of a new AIP or RP in step 508, and then proceeds to step 509. In the MBMS Notification Info message, a different RACH access probability value from the value transmitted in step 506 is set.
In step 509, the UTRAN retransmits the MBMS Notification Info message, the MBMS Service PtM RB Info message, the MBMS Common RB Info message, and the MBMS Service List message at a start time of a new RP. In step 510, the UTRAN determines whether it is time to start a new MP. If it is time to start a new MP, the UTRAN proceeds to step 511, and if it is not time to start the new MP, the UTRAN returns to step 509.
In step 511, the UTRAN modifies IEs to be modified, if any, included in the MBMS Notification Info message, the MBMS Service PtM Info message, the MBMS Common RB Info message, and the MBMS Service List message. If the contents of the MBMS Common RB Info message are modified, the UTRAN modifies a corresponding Common RB value tag. An effective range of the Common RB value tag can be limited to the inside of a cell, or can be defined as several cells that transmit the same MBMS service. In the case where the effective range is limited to the inside of a cell, the Common RB value tag is modified only when MBMS-related RB information in the cell is modified. If the effective range is defined as several cells, the Common RB value tag can be modified when MBMS-related RB information of neighbor cells is modified. In step 512, the UTRAN retransmits the control information messages at a start time of a new MP.
FIGS. 6 to 9 are flowcharts illustrating operations of a UE upon receiving 4 control information messages transmitted over an MCCH, proposed in the present invention.
In step 603, the UE determines if the current frame is a start time of a new MP. The start time of the new MP can be can be determined through a BCH over which the MBMS system information can be transmitted. If it is determined in step 603 that the UE detects a start time of the new MP, the UE proceeds to step 605, and otherwise, proceeds to step 604 where it waits for a start time of a new MP. In step 605, the UE receives an MBMS Notification Info message through an MCCH, and determines in step 606 if the received MBMS Notification Info message is for an MBMS service joined by the UE or currently in service. During the “joining” process a UE informs the RNC/SGSN of an interest in a service, and the RNC/SGSN stores an ID of the UE and location information of the UE. When the service of interest starts, the UE begins to receive the service and is referred to as being currently in service.
The UE performs step 606 using an IE MBMS service ID included in the MBMS Notification Info message. If the received MBMS Notification Info message is not for an MBMS service joined by the UE or currently in service, the UE returns to step 601, and otherwise, proceeds to step 607 where it checks a cause value included in the MBMS Notification Info message. In
However, if the UE determines in step 608 that counting is not performed, it recognizes in step 610 that PtM RB change is performed, and performs a PtM RB change-related operation in step 611. If the UE recognizes in step 610 that the PtM RB change is not performed, it recognizes in step 612 that PtM RB release is performed, and then performs an operation necessary for the PtM RB release in step 613.
Herein, the “counting-related operation” refers to an operation of attempting an RRC connection or a PtM connection for counting. The “PtM RB change” means that PtM RB information for an MBMS service that the UE was receiving has been changed, and the UE performs an RB change operation by receiving Common RB Info or MBMS service PtM RB Info. The “PtM RB release operation” refers to an operation of releasing current RB information because it is not necessary to maintain the current RB due to an end of a session for the MBMS service that the UE was receiving.
If none of the causes of steps 608, 610 and 612 is recognized, a session for an MBMS service joined by the UE starts without the counting operation. Therefore, the UE checks the IEs required for the MBMS Notification Info message in at least one of steps 614 to 616.
In step 614, the UE checks an IE continue MCCH reading, and based on the check result, determines if it should receive control information messages transmitted over an MCCH successively after the MBMS Notification Info message. In step 615, the UE checks an IE Common RB value tag to determine if it should receive again a Common RB Info. In step 616, the UE checks IE Scheduling Info to determine an end time of an MBMS Service PtM RB Info message or an MBMS Common RB Info message. With the use of the IE Scheduling Info, the UE can correctly presume an end time of MBMS Service PtM RB Info message and the MBMS Common RB Info message without the necessity of continuously monitoring an MCCH. After checking all of the IEs of the MBMS Notification Info message, the UE performs a required operation in step 617. Herein, the “required operation” refers to an operation of receiving succeeding control information messages or storing required information.
In step 705, the UE determines if there is an ID for an MBMS service joined by the UE in the received MBMS Service List message, and ends the operation if there is no ID for the joined MBMS service. However, if there is an ID for the MBMS service joined by the UE in step 705, the UE determines in step 706 if a transfer mode for an MBMS service corresponding to the MBMS service ID corresponds to PtM depending on an IE Transfer mode included in the MBMS Service List message. If the transfer mode is PtM, the UE proceeds to step 707, and otherwise, proceeds to step 708. In step 707, the UE acquires an MBMS Short service ID, i.e. an MBMS Transmission Identity, corresponding to the ID of the MBMS service joined by the UE, and then proceeds to step 712. In step 708, the UE determines if the transfer mode of the MBMS service joined by the UE corresponds to PtP based on the IE Transfer mode. If the transfer mode corresponds to PtP, the UE proceeds to step 709, and otherwise, proceeds to step 710. In step 709, the UE performs an operation of receiving the MBMS service joined by the UE on a PtP basis. If the UE determines in step 710 that the MBMS service joined by the UE is not provided based on the IE Transfer mode, it performs in step 711 an operation of receiving the MBMS service joined by the UE in the current cell in which the UE is located. If the IE Transfer mode does corresponds to none of PtM, PtP and no-RB, the UE proceeds to step 712, determining that there is an error.
In any one of steps 712 to 714, the UE checks the IEs necessary for the MBMS Notification Info message. In step 712, the UE checks the IE Preferred frequency included in the MBMS Service List message to acquire the information on a frequency at which the MBMS service joined by the UE is provided. In step 713, the UE checks the IE continue MCCH reading to determine if it should continuously receive control information transmitted over an MCCH. In step 714, the UE checks the IE Common RB value tag to determine if it is necessary to receive an MBMS Common RB Info message. In step 715, the UE performs a required operation based on information acquired from the MBMS Service List message. Herein, the “required operation” refers to an operation of receiving succeeding control information messages or storing required information.
However, if the IDs are equal to each other in step 802, it means that there is RB information for the joined MBMS service in the MBMS Service PtM RB Info message. In step 803, the UE acquires the current cell RB information for the joined MBMS service from the MBMS Service PtM RB Info message. In step 805, the UE determines if there is information on a neighbor cell for the joined MBMS service. If there is information on a neighbor cell for the joined MBMS service, the UE acquires the information on a neighbor cell for the joined MBMS service in step 806, and otherwise, performs an operation of receiving the MBMS service in step 807. In step 806, the UE can acquire the neighbor cell information by receiving a separate MBMS Neighboring Cell PtM RB Info message. In step 807, the “operation of receiving the MBMS service” refers to an operation of setting up an RB and a physical channel used for receiving the MBMS service, based on the acquired RB information.
In step 902, the UE determines if a value tag stored in the UE is equal to a value tag included in other control information messages that the UE has previously received. If the value tag values are equal to each other, the UE proceeds to step 904 where it ends the operation without receiving the MBMS Common RB Info message.
However, if the value tag values are not equal to each other, the UE receives an MBMS Common RB Info message through an MCCH in step 903, and stores a value tag included in the MBMS Common RB Info message in step 904. In step 906, the UE acquires RB information included in the MBMS Common RB Info message received in step 903. In step 907, the UE acquires the physical channel information and the transport channel information from the MBMS Common RB Info message. The received RB information and physical channel/transport channel information are stored, preparing for the case where the UE sets up an RB to receive a corresponding MBMS service therethrough.
As described above, the present invention proposes a method for defining the control information messages transmitted over an MCCH, and minimizing a signaling overhead during the transmission of the defined control information messages. In addition, the present invention proposes a method for efficiently scheduling the control information messages before the transmission. In this manner, a UE receiving the control information messages can prevent duplicate reception of the same information elements and prevent an MCCH from being continuously received, thereby minimizing power consumption of the UE.
While the invention has been shown and described with reference to a certain preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
2004-26266 | Apr 2004 | KR | national |