EP1714407B1 - Emission et reception d'informations de commande pour service de diffusion/multi-diffusion des donnees multimedia dans un systeme de communication mobile - Google Patents

Emission et reception d'informations de commande pour service de diffusion/multi-diffusion des donnees multimedia dans un systeme de communication mobile Download PDF

Info

Publication number
EP1714407B1
EP1714407B1 EP05726448A EP05726448A EP1714407B1 EP 1714407 B1 EP1714407 B1 EP 1714407B1 EP 05726448 A EP05726448 A EP 05726448A EP 05726448 A EP05726448 A EP 05726448A EP 1714407 B1 EP1714407 B1 EP 1714407B1
Authority
EP
European Patent Office
Prior art keywords
point
control information
information
multipoint
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP05726448A
Other languages
German (de)
English (en)
Other versions
EP1714407A4 (fr
EP1714407A1 (fr
Inventor
Young-Dae Lee
Seung-June Yi
Sung-Duck Chun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP1714407A1 publication Critical patent/EP1714407A1/fr
Publication of EP1714407A4 publication Critical patent/EP1714407A4/fr
Application granted granted Critical
Publication of EP1714407B1 publication Critical patent/EP1714407B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • the present invention relates to a multimedia broadcast/multicast service (MBMS) and, more particularly, to transmitting and receiving control information for an MBMS.
  • MBMS multimedia broadcast/multicast service
  • the universal mobile telecommunications system is a third-generation mobile communications system evolving from the global system for mobile communications system (GSM), which is the European standard.
  • GSM global system for mobile communications system
  • the UMTS is aimed at providing enhanced mobile communications services based on the GSM core network and wideband code-division multiple-access technologies.
  • a related art UMTS network structure 1 is illustrated in Figure 1 .
  • a mobile terminal, or user equipment (UE) 2 is connected to a core network (CN) 4 through a UMTS terrestrial radio access network (UTRAN) 6.
  • the UTRAN 6 configures, maintains and manages a radio access bearer for communications between the UE 2 and the core network 4 to meet end-to-end quality of service requirements.
  • the UTRAN 6 includes a plurality of radio network subsystems (RNS) 8, each of which comprises one radio network controller (RNC) 10 for a plurality base stations, or Node Bs 12.
  • RNC radio network controller
  • the RNC 10 connected to a given base station 12 is the controlling RNC for allocating and managing the common resources provided for any number of UEs 2 operating in one cell.
  • One or more cells exist in one Node B.
  • the controlling RNC 10 controls traffic load, cell congestion, and the acceptance of new radio links.
  • Each Node B 12 may receive an uplink signal from a UE 2 and may transmit a downlink signals to the UE 2.
  • Each Node B 12 serves as an access point enabling a UE 2 to connect to the UTRAN 6, while an RNC 10 serves as an access point for connecting the corresponding Node Bs to the core network 4.
  • the serving RNC 10 is the RNC managing dedicated radio resources for the provision of services to a specific UE 2 and is the access point to the core network 4 for data transfer to the specific UE. All other RNCs 10 connected to the UE 2 are drift RNCs, such that there is only one serving RNC connecting the UE to the core network 4 via the UTRAN 6. The drift RNCs 10 facilitate the routing of user data and allocate codes as common resources.
  • the interface between the UE 2 and the UTRAN 6 is realized through a radio interface protocol established in accordance with radio access network specifications describing a physical layer (L1), a data link layer (L2) and a network layer (L3) described in, for example 3GPP specifications. These layers are based on the lower three layers of an open system interconnection (OSI) model that is a well-known in communications systems.
  • OSI open system interconnection
  • the radio interface protocol is divided horizontally into the physical layer, the data link layer, and the network layer, and is divided vertically into a user plane for carrying data traffic such as voice signals and Internet protocol packet transmissions and a control plane for carrying control information for the maintenance and management of the interface.
  • the physical layer provides information transfer service to a higher layer and is linked via transport channels to a medium access control (MAC) layer.
  • Data travels between the MAC layer and the physical layer via a transport channel. Also, data transmission is performed through a physical channel between different physical layers, namely, between physical layers of a sending side (transmitter) and a receiving side (transmitter).
  • the MAC layer of the second layer (L2) provides information transfer service to a higher layer and is linked via a logical channel to a radio link control (RLC) layer.
  • the RLC layer of the second layer (L2) supports the transmission of reliable data and can perform segmentation and concatenation functions for RLC service data units (SDU) received from an upper layer.
  • SDU RLC service data units
  • the radio resource control (RRC) layer located at the lowest portion of the third layer (L3) is only defined in the control plane and controls transport channels and physical channels with respect to the establishment, re-establishment, and release of radio bearers.
  • RRC radio resource control
  • a radio bearer (RB) is a service provided by a lower layer, such as the RLC layer or the MAC layer, for transferring data between the UE 2 and the UTRAN 6.
  • the establishment of an RB determines regulating characteristics of the protocol layer and channel needed to provide a specific service, thereby establishing the parameters and operational methods of the service.
  • MBMS Multimedia Broadcast/Multicast Service
  • MBMS refers to a method of providing streaming or background services to a plurality of UEs 2 using a downlink-dedicated MBMS radio bearer that utilizes at least one of point-to-multipoint and point-to-point radio bearer.
  • One MBMS service includes one or more sessions and MBMS data is transmitted to the plurality of terminals through the MBMS radio bearer only while the session is ongoing.
  • an MBMS may be carried out in a broadcast mode or a multicast mode.
  • the broadcast mode is for transmitting multimedia data to all UEs 2 within a broadcast area, for example the domain where the broadcast is available.
  • the multicast mode is for transmitting multimedia data to a specific UE 2 group within a multicast area, for example the domain where the multicast service is available.
  • the UTRAN 6 provides the MBMS service to the UEs 2 using the RB.
  • RBs used by the UTRAN 6 can be classified as a point-to-point RB or a point-to-multipoint RB.
  • the point-to-point RB is a bi-directional RB, including a logical channel DTCH (Dedicated Traffic Channel), a transport channel DCH (Dedicated Channel) and a physical channel DPCH (Dedicated Physical Channel) or SCCPCH (Secondary Common Control Physical Channel).
  • the point-to-multipoint RB is a uni-directional downlink RB, including a logical channel MTCH (MBMS Traffic Channel), a transport channel FACH (Forward Access Channel), and the physical channel SCCPCH, as shown in Figure 3 .
  • the logical channel MTCH is configured for each MBMS service provided to one cell and used to transmit user plane data of a specific MBMS service to the UEs 2.
  • the UTRAN 6 providing the MBMS service transmits MBMS-related control information to the plurality of terminals (UEs 2) through an MCCH (MBMS Control Channel).
  • MCCH MBMS Control Channel
  • the logical channel MCCH is the point-to-multipoint downlink channel and is mapped to the FACH, which is mapped to the SCCPCH.
  • the MBMS-related control information includes a session start for indicating the start of an MBMS service, a session stop for indicating the end of the MBMS service, an RB type indicator for indicating whether the MBMS service is provided via a point-to-point RB or a point-to-multipoint RB, RB information for providing point-to-multipoint RB information such as the MTCH if the RB is a point-to-multipoint RB, counting information for measuring the number of terminals desiring to receive the MBMS service, and re-counting information for re-counting the number of terminals desiring the MBMS service while the MBMS service is being provided.
  • the MBMS-related control information may be included in an independent message and transmitted, or can be entirely included in one MBMS control message.
  • the logical channel MCCH is used.
  • Channel mapping of the MCCH is similar to that of the MTCH. Namely, the MCCH is a point-to-multipoint downlink channel and is mapped to the transport channel FACH, which is mapped to the physical channel SCCPCH. For reference, only one MTCH is provided for one service, while only one MCCH is provided for one cell.
  • the terminal (UE) 2 wishing to receive an MBMS service must first receive MBMS control information through the MCCH. However, because the terminal 2 can receive only one SCCPCH for the MBMS, and the MCCH is transmitted through a different SCCPCH irrelative to the MTCH, the terminal cannot receive the MCCH if the terminal has already received one or more MBMS services.
  • An MBMS control information reception indication message (MCCH Indication Message) is used to indicate information to terminals receiving one or more MBMS services, i.e., receiving the MTCH.
  • the MCCH indication message is transmitted through the SCCPCH.
  • the MTCH is also transmitted through the SCCPCH.
  • the mobile terminal 2 receives one SCCPCH.
  • the UTRAN 6 transmits the MCCH indication message through the SCCPCH so that the mobile terminal 2 can receive the control information transmitted through the MCCH.
  • the MCCH indication message can be transmitted through the MTCH the mobile terminal 2 is receiving, or through an auxiliary channel, such as a Secondary MCCH (S-MCCH), wherein the S-MCCH is mapped to the same SCCPCH as the MTCH.
  • S-MCCH Secondary MCCH
  • the S-MCCH is an arbitrary channel, which can be a dedicated channel such as a DCCH (Dedicated Control Channel), a common channel such as a CCCH (Common Control Channel), or a new dedicated or common channel. No matter which channel is used, the MCCH indication information is transmitted through the same SCCPCH to which the MTCH is mapped.
  • the MCCH indication message is a 1-bit indication message.
  • the MCCH indication message is used to indicate that the mobile terminal 2 should receive the control information. Namely, when the mobile terminal 2 receives the MCCH indication message in the course of receiving the MTCH, the mobile terminal 2 switches the channel from the SCCPCH through which the MTCH is transmitted to the SCCPCH through which the MCCH is transmitted, and receives the MBMS control information transmitted through the MCCH. After the mobile terminal 2 receives the desired MBMS control information through the MCCH, the mobile terminal 2 then switches the SCCPCH to which the MTCH is mapped and receives the MTCH.
  • the 1-bit indication message only indicates to the mobile terminal 2 to receive the MCCH. This method is advantageous in that the transmission amount of the indication message can be maximized.
  • the related art MCCH indication message also has the following problems. First, the mobile terminal 2 does not know which service the MCCH indication message indicates to receive. Thus, the mobile terminal 2 may receive an MCCH indication message unnecessarily even when control information for a service the mobile terminal 2 does not want to receive is transmitted.
  • the mobile terminal 2 does not know which control information the MCCH indication message indicates to receive. Thus, when various types of control information are continuously transmitted, the mobile terminal 2 does not know which control information to receive, and further does not know at which time the MTCH should be received again. Moreover, if the same control information is transmitted repeatedly several times, the mobile terminal 2 will unnecessarily receive the already-received control message again.
  • EP 1 353 523 A1 discloses transmitting a Multimedia Broadcast/Multicast Service (MBMS) in as wireless communication system.
  • the MBMS service is initiated by a user who requests to receive the service.
  • the MBMS service is assigned an ID and a radio network control (RNC) service context is created to supply the user with a media stream.
  • RNC radio network control
  • the user equipment is notified over a common channel when the MBMS transmission starts and is supplied with the service ID and a physical layer description to setup the media stream connection.
  • the present invention is directed to a method for transmitting and receiving control information for an MBMS.
  • the present invention is embodied in a method for receiving a point-to-multipoint service in a wireless communication system, the method comprising, receiving a control information indication message for a point-to-multipoint service, the control information indication message having attribute information for receiving at least one control information message from a point-to-multipoint control channel, wherein the control information indication message and the at least one control information message are point-to-multipoint messages created from the same protocol layer, determining to receive the at least one control information message according to the attribute information, and receiving the at least one control information message through the point-to-multipoint control channel if a mobile terminal determines to receive the at least one control information message. If the mobile terminal determines not to receive the at least one control information message, the mobile terminal does not receive the at least one control information message.
  • the step of determining to receive the at least one control information message according to the attribute information comprises checking an update of the at least one control information message for the point-to-multipoint service subscribed by the mobile terminal based on the control information indication message and determining to receive the at least one control information message if the at least one control information message is updated.
  • the method further comprises switching from a previously received traffic channel to the point-to-multipoint control channel to receive the control information message.
  • the method comprises switching from a previously received traffic channel to the point-to-multipoint control channel upon determining to receive the at least one control information message.
  • the method also comprises processing the at least one control information message and switching from the point-to-multipoint control channel to a traffic channel to receive the point-to-multipoint service.
  • the attribute information comprises a point-to-multipoint service ID associated with the point-to-multipoint service. Furthermore, the step of determining to receive the at least one control information message according to the attribute information comprises checking the point-to-multipoint service ID if the point-to-multipoint service ID is included in the attribute information and determining which control information message is to be received from the point-to-multipoint control channel if the point-to-multipoint service ID is related to a point-to-multipoint service subscribed by the mobile terminal.
  • the mobile terminal continues to receive a traffic channel previously received prior to receiving the control information indication message.
  • the traffic channel may be one of a point-to-multipoint traffic channel and a point-to-point traffic channel.
  • the attribute information comprises at least one of a control information identifier associated with the at least one control information message, update information associated with the at least one control information message, and timing information associated with the point-to-multipoint service.
  • the update information indicates the update information of the at least one control information message for the point-to-multipoint service.
  • the timing information indicates which part of the point-to-multipoint control channel is to be received.
  • the timing information indicates a start time of the point-to-multipoint control channel reception.
  • the mobile terminal may receive the point-to-multipoint control channel during a duration according to the timing information.
  • the mobile terminal stops receiving the point-to-multipoint control channel at an end time according to the timing information.
  • the method comprises checking the control information identifier if the control information identifier is included in the attribute information and receiving the at least one control information message if the control information identifier is related to the mobile terminal.
  • the method comprises checking the update information if the update information is included in the attribute information, comparing the update information to previously stored update information, and receiving the at least one control information message if no update information has been previously stored or if the update information is different from the previously stored update information.
  • the method comprises checking the timing information if the timing information is included in the attribute information and receiving the at least one control information message according to a time interval indicated by the timing information.
  • control information indication message is received through an MTCH
  • control information indication message is received through an S-MCCH
  • point-to-multipoint control channel is an MCCH
  • traffic channel is an MTCH
  • a method for transmitting a point-to-multipoint service in a wireless communication system comprises transmitting a control information indication message for a point-to-multipoint service to a mobile terminal, the control information indication message having attribute information for transmitting at least one control information message through a point-to-multipoint control channel, wherein the control information indication message and the at least one control information message are point-to-multipoint messages created from the same protocol layer, and transmitting the at least one control information message through the point-to-multipoint control channel.
  • the mobile terminal determining to receive the at least one control information message comprises checking an update of the at least one control information message for the point-to-multipoint service subscribed by the mobile terminal based on the control information indication message and determining to receive the at least one control information message if the at least one control information message is updated.
  • the mobile terminal determines to receive the at least one control information message according to the attribute information, wherein the attribute information comprises a point-to-multipoint service ID associated with the point-to-multipoint service.
  • a method for the mobile terminal determining to receive the at least one control information message according to the attribute information comprises checking the point-to-multipoint service ID if the point-to-multipoint service ID is included in the attribute information and determining which control information message is to be received from the point-to-multipoint control channel if the point-to-multipoint service ID is related to a point-to-multipoint service subscribed by the mobile terminal.
  • the mobile terminal continues to receive a traffic channel previously received prior to receiving the control information indication message.
  • the traffic channel is one of a point-to-multipoint traffic channel and a point-to-point traffic channel.
  • the attribute information comprises at least one of a control information identifier associated with the at least one control information message, update information associated with the at least one control information message, and timing information associated with the point-to-multipoint service.
  • the update information indicates the update information of the at least one control information message for the point-to-multipoint service.
  • the timing information indicates which part of the point-to-multipoint control channel is to be received by the mobile terminal. Also, the timing information indicates a start time of the point-to-multipoint control channel transmission. Preferably, the network transmits the point-to-multipoint control channel during a duration according to the timing information. Alternatively, the network stops transmitting the point-to-multipoint control channel at an end time according to the timing information.
  • a method for the mobile terminal determining to receive the at least one control information message according to the attribute information comprises checking the control information identifier if the control information identifier is included in the attribute information and receiving the at least one control information message if the control information identifier is related to the mobile terminal.
  • a method for the mobile terminal determining to receive the at least one control information message according to the attribute information comprises checking the update information if the update information is included in the attribute information, comparing the update information to previously stored update information, and receiving the at least one control information message if no update information has been previously stored or if the update information is different from the previously stored update information.
  • a method for the mobile terminal determining to receive the at least one control information message according to the attribute information comprises checking the timing information if the timing information is included in the attribute information, and receiving the at least one control information message according to a time interval indicated by the timing information.
  • control information indication message is transmitted through an MTCH
  • control information indication message is transmitted through an S-MCCH
  • point-to-multipoint control channel is an MCCH
  • traffic channel is an MTCH
  • Figure 1 illustrates a related art network structure of a wireless communication system.
  • Figure 2 illustrates a related art radio interface protocol architecture based on a radio access network specification between the UE and the UTRAN.
  • Figure 3 illustrates related art channel mapping for an MBMS service for a mobile terminal.
  • figure 4 illustrates a diagram for selectively transmitting and receiving control information for an MBMS service in accordance with one embodiment of the invention.
  • the present invention relates to a method for minimizing data loss as a mobile terminal unnecessarily reads an MCCH for receiving MBMS control information in the course of receiving MBMS data.
  • the present invention provides a method for constructing an MBMS control information reception, indication message (MCCH indication message) and a method for receiving the MBMS control information using the same.
  • the present invention is implemented in a mobile communication system, such as a UMTS developed under 3GPP specifications, the present invention can also be applied to a communication system operating in conformity with a different specification.
  • an MCCH indication message comprises a service ID for identifying which service the control information is transmitted for and an RRC message ID for indicating what kind of control information is transmitted.
  • the MCCH indication message further comprises update information for indicating whether a currently transmitted MCCH indication message or currently transmitted control information (RRC message) transmitted through the MCCH is new or updated information or previously transmitted information.
  • the MCCH indication message also includes timing information for indicating a time interval for receiving the MCCH.
  • the MCCH indication message is preferably transmitted through the MTCH which is being received by the mobile terminal or through the S-MCCH mapped to the SCCPCH that transmits the MTCH.
  • the MCCH indication message may include at least one of the service ID, the RRC message ID, the update information and the timing information.
  • the RRC message ID includes a session start information for indicating the start of an MBMS service, a session stop information for indicating the end of the MBMS service, an RB type indicator for indicating what type of RB the MBMS services is p rovided by, RB information for providing point-to-multipoint RB information such as the MTCH if the RB type is a point-to-multipoint RB, counting information for measuring the number of terminals desiring to receive the MBMS service, and re-counting information for re-counting the number of terminals desiring the MBMS service while the MBMS service is being provided.
  • the update information is a type of value tag for informing the mobile terminal (UE) of the newness of a transmitted MCCH indication message or RRC message.
  • the update information may be divided into two types. One type is update information related to an MCCH indication message. The other type is update information related to an RRC message. Notably, the mobile terminal operates differently depending on the type of the update information.
  • the mobile terminal stores the update information of an MCCH indication message whenever the corresponding MCCH indication message is received. Furthermore, when an MCCH indication message is received, the mobile terminal compares the received update information included in the MCCH indication message with the previously stored update information. If no update information has been previously stored or if the two update information are different, the mobile terminal determines that the currently received update information is new information. If, however, the two update information are the same, the mobile terminal determines that the currently received update information is the same as the previously stored update information.
  • the MCCH indication message comprises the RRC message ID and the update information.
  • the terminal receives the MCCH indication message, it stores corresponding update information for each RRC message. Moreover, if a new MCCH indication message is received, the terminal compares the update information received with respect to the RRC message ID and previously stored update information. If no update information has been stored or if the two update information are different, the mobile terminal determines that the currently received update information is new information. If, however, the two update information are the same, the mobile terminal determines that the currently received update information is the same as the previously stored update information.
  • the timing information indicates information related to a time interval for the mobile terminal to receive the MCCH.
  • the time interval information may include at least one of an MCCH reception start time, reception end time and reception interval time.
  • the time interval information may be general timing information, frame information or slot information.
  • the mobile terminal checks the service ID. If the service ID is not related to the mobile terminal or to a service the mobile terminal is currently receiving or desires to receive, the mobile terminal disregards the received MCCH indication message and continues to receive the MTCH. If, however, the service ID corresponds to an MBMS service being received or desired to be received, the mobile terminal receives the control information transmitted through the MCCH by switching the reception channel from the MTCH to the MCCH.
  • the mobile terminal checks the RRC message ID. The mobile terminal then switches the reception channel from the MTCH to the MCCH to specifically receive the control information indicated by the RRC message ID among all control information transmitted through the MCCH.
  • the mobile terminal checks whether the received indication message is a new message by comparing the received update information with previously stored update information. If the received update information is the same as the previously stored update information, the mobile terminal determines that the received MCCH indication message is the same as a previously received MCCH indication message. Accordingly, the mobile terminal disregards the received MCCH indication message and continues to receive the MTCH. If, however, no update information has been previously stored or if the received update information is different from the previously stored update information, the mobile terminal stores the received update information and receives the control information transmitted through the MCCH by switching from the MTCH to the MCCH.
  • the mobile terminal receives the MCCH by switching the reception channel from the MTCH to the MCCH during a time interval indicated by the received timing information. If the timing information includes a reception start time, the mobile terminal begins receiving the MCCH from the start time indicated. If the timing information includes a reception end time, the mobile terminal terminates reception of the MCCH at the end time indicated. If the timing information includes a reception interval time, the mobile terminal receives the MCCH during the time interval indicated.
  • the MCCH indication message includes at least one of the service ID, the RRC message ID, the update information and the timing information. If at least one of these pieces of information are included in the MCCH indication message, the mobile terminal receives control information by performing a separate operation for each piece of information as described above.
  • the mobile terminal checks the service ID. If the received service ID is not related to the mobile terminal, the terminal disregards the received MCCH indication message and continues receiving the MTCH. If, however, the received service ID is a service ID of an MBMS being received or desired to be received by the mobile terminal, the terminal switches from the MTCH to the MCCH to receive control information transmitted through the MCCH. When the terminal receives the control information indicated by the RRC message ID among all control information transmitted through the MCCH, the mobile terminal operates according to the corresponding control information.
  • the terminal checks the service ID. If the received service ID is not related to the mobile terminal, the terminal disregards the received MCCH indication message and continues receiving the MTCH. If, however, the received service ID is a service ID of an MBMS being received or desired to be received by the mobile terminal, the terminal additionally checks the update information. If the received update information is the same as previously stored update information, the terminal disregards the received MCCH indication message and continues receiving the MTCH. If, however, there is no stored update information or if the previously stored update information is different from the currently received update information, the terminal stores the received update information. The mobile terminal then receives control information transmitted through the MCCH by switching from MTCH to the MCCH.
  • the terminal checks whether the received MCCH indication message or the RRC message to be transmitted through the MCCH is a new message by comparing the received update information with previously stored update information. If the received update information is the same as the previously stored update information, the mobile terminal disregards the received MCCH indication message and continues receiving the MTCH. If, however, there is no stored update information or if the previously stored update information is different from the currently received update information, the mobile terminal stores the received update information related to the MCCH indication message or the RRC message. The mobile terminal then switches from the MTCH to the MCCH to receive control information transmitted through the MCCH. When the mobile terminal receives the control information indicated by the RRC message ID among all the control information transmitted through the MCCH, the terminal performs a follow-up operation according to the corresponding control information.
  • the present invention presents the case where the MCCH indication message includes two among the service ID, the RRC message ID and the update information.
  • the present invention can readily be applied to the case where the MCCH indication message includes two or three among the service ID, the RRC message, the update information and the timing information, wherein the mobile terminal separately processes a corresponding operation with respect to each piece of information and receives control information accordingly.
  • a method for selective ly transmitting and receiving control information for an MBMS service is illustrated in Figure 4 .
  • a mobile terminal (UE) 50 is provided with a first MBMS service (MBMS1)
  • a second MBMS service (MBMS2) begins.
  • a UTRAN 100 informs the mobile terminal 50 about a session start of the second MBMS service.
  • an MCCH indication message includes a service ID, an RRC message ID, update information and timing information.
  • the terminal 50 receives MBMS 1 data at an L1/L2 layer through an MTCH1 (step S 10).
  • An RRC of the terminal 50 receives the MCCH indication message through the MTCH1 or the S-MCCH in the course of receiving the MBMS1 data (step S11).
  • the MCCH indication message is a control information reception indication message for the MBMS2.
  • the service ID has a value of 2 and the RRC message ID indicates a session start. Both the service ID and the RRC message ID are transmitted through the MCCH indication message.
  • the mobile terminal 50 checks the service ID and determines whether the MBMS2 service is a service the mobile terminal 50 desires to receive. If the MBMS2 is a service the mobile terminal 50 desires to receive, the terminal checks the update information to determine whether control information to be transmitted is new and whether the MCCH is to be received (step S12). If the MCCH is determined to be received, the RRC of the terminal 50 instructs lower layers, such as the PHY/MAC/RLC (L1/L2 layers), to switch the reception channel from the MTCH1 to the MCCH at a time indicated by the timing information (step S 13). According to the instruction of the RRC of the terminal, the lower layers switch the reception channel from the MTCH1 to the MCCH (step S 14). Consequently, because the MTCH1 and the MCCH are mapped to a different SCCPCH, the physical channel is also switched.
  • the PHY/MAC/RLC L1/L2 layers
  • the terminal RRC continuously receives an RRC message indicated by the RRC message ID through the MCCH (step S 15).
  • the terminal RRC receives a session start message of the MBMS2.
  • the terminal RRC Upon receiving the session start information of the MBMS2, the terminal RRC determines whether to continuously receive the MBMS1 or the new MBMS2. In this case, a user is informed about the session start of the MBMS2 and a follow-up operation is determined according to the user's decision (step S16). In this embodiment, it is assumed that the user desires to receive the MBMS2.
  • the terminal RRC instructs the lower layers such as the PHY/MAC/RLC to switch the reception channel from the MCCH to the MTCH2 (step S 17). Accordingly, the lower layers switch the reception channel from the MCCH to the MTCH2 so that the mobile terminal 50 (UE L1/L2) can receive MBMS2 data at the L1/L2 layer through the MTCH2.
  • the lower layers switch the reception channel from the MCCH to the MTCH2 so that the mobile terminal 50 (UE L1/L2) can receive MBMS2 data at the L1/L2 layer through the MTCH2.
  • the method for transmitting and receiving control information for an MBMS service in accordance with the present invention has many advantages. For example, if the terminal receives the MBMS control information reception indication message (MCCH indication message) in the course of receiving one or more MBMS services, the service ID, the RRC message ID and the update information included in the MBMS control information reception indication message are checked to determine whether to receive the MCCH. The mobile terminal is thus prevented from unnecessarily receiving the MCCH when control information to be received through the MCCH has already been received by the mobile terminal or when control information to be received corresponds to a service unrelated to the mobile terminal. Thus, a loss of MBMS data due to the unnecessary reception of the MCCH can be reduced.
  • the timing information is included and transmitted in the MBMS control information reception indication message. This prevents the mobile terminal from receiving the MCCH for an unnecessarily long time. Therefore, the loss of MBMS data is further reduced.
  • the present invention is described in the context of mobile communication, the present invention may also be used in any wireless communication systems using mobile devices, such as PDAs and laptop computers equipped with wireless communication capabilities. Moreover, the use of certain terms to describe the present invention should not limit the scope of the present invention to a certain type of wireless communication system. The present invention is also applicable to other wireless communication system using different air interfaces and/or physical layers, for example, TDMA, CDMA, FDMA, WCDMA, etc.
  • the preferred embodiments may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof.
  • article of manufacture refers to code or logic implemented in hardware logic (e.g., an integrated circuit chip, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), etc.) or a computer readable medium (e.g., magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.).
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • Code in the computer readable medium is accessed and executed by a processor.
  • the code in which preferred embodiments are implemented may further be accessible through a transmission media or from a file server over a network.
  • the article of manufacture in which the code is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media; signals propagating through space, radio waves, infrared signals, etc.
  • a transmission media such as a network transmission line, wireless transmission media; signals propagating through space, radio waves, infrared signals, etc.

Abstract

Afin de minimiser les pertes de données lorsque qu'un terminal mobile lit inutilement un canal de commande MBMS (MCCH) au cours de la réception de données MBMS, un message d'indication de la réception des informations de commande MBMS comportant des informations d'attributs des informations de commande pour un service MBMS est transmis au trémulant mobile. Le terminal mobile lit alors sélectivement le canal MCCH afin de recevoir les informations de commande conformément aux informations d'attributs contenues dans le message d'indication.

Claims (32)

  1. Procédé de réception d'un service point-multipoint dans un système de communication sans fil, le procédé comprenant l'étape consistant à :
    recevoir un message d'indication d'informations de commande pour un service point-multipoint (S11),
    caractérisé en ce que le message d'indication d'informations de commande possède des informations d'attribut pour recevoir au moins un message d'informations de commande du canal de commande point-multipoint, dans lequel le message d'indication d'informations de commande et le au moins un message d'informations de commande sont des messages point-multipoint créés à partir de la même couche de protocole ; le procédé comprenant en outre les étapes consistant à :
    déterminer de recevoir le au moins un message d'informations de commande conformément aux informations d'attribut (S12) ; et
    recevoir le au moins un message d'informations de commande (S15) par l'intermédiaire du canal de commande point-multipoint si un terminal mobile détermine de recevoir le au moins un message d'informations de commande.
  2. Procédé selon la revendication 1, dans lequel si le terminal mobile détermine de ne pas recevoir le au moins un message d'informations de commande, le terminal mobile ne reçoit pas le au moins un message d'informations de commande.
  3. Procédé selon la revendication 1, dans lequel l'étape consistant à déterminer de recevoir le au moins un message d'informations de commande conformément aux informations d'attribut (S12) comprend les étapes consistant à :
    contrôler une mise à jour du au moins un message d'informations de commande pour le service point-multipoint souscrit par le terminal mobile sur la base du message d'indication d'informations de commande ; et
    déterminer de recevoir le au moins un message d'informations de commande si le au moins un message d'informations de commande est mis à jour.
  4. Procédé selon la revendication 1, comprenant en outre l'étape consistant à effectuer une commutation (S14) d'un canal de trafic préalablement reçu vers le canal de commande point-multipoint pour recevoir le message d'informations de commande.
  5. Procédé selon la revendication 4, comprenant en outre l'étape consistant à effectuer une commutation d'un canal de trafic préalablement reçu vers un canal de commande point-multipoint sur détermination de réception du au moins un message d'informations de commande.
  6. Procédé selon la revendication 1, comprenant en outre les étapes consistant à :
    traiter (S16) le au moins un message d'informations de commande ; et
    commuter (S18) du canal de commande point-multipoint vers un canal de trafic pour recevoir le service point-multipoint.
  7. Procédé selon la revendication 1, dans lequel les informations d'attribut comprennent une identification de service point-multipoint associée au service point-multipoint.
  8. Procédé selon la revendication 7, dans lequel l'étape consistant à déterminer de recevoir le au moins un message d'informations de commande conformément aux informations d'attribut (S12) comprend les étapes consistant à :
    contrôler l'identification de service point-multipoint si identification de service point-multipoint est contenue dans les informations d'attribut ; et déterminer quel message d'informations de commande doit être reçu du canal de commande point-multipoint si l'identification de service point-multipoint se rapporte à un service point-multipoint souscrit par le terminal mobile.
  9. Procédé selon la revendication 8, dans lequel si l'identification de service point-multipoint ne se rapporte pas au service point-multipoint souscrit par le terminal mobile, le terminal mobile continue de recevoir un canal de trafic préalablement reçu avant de recevoir le message d'indication d'informations de commande.
  10. Procédé selon la revendication 9, dans lequel le canal de trafic est l'un parmi un canal de trafic point-multipoint et un canal de trafic point à point.
  11. Procédé selon la revendication 1, dans lequel les informations d'attribut comprennent au moins l'un parmi :
    un identificateur d'informations de commande associé au au moins un message d'informations de commande ;
    des informations de mise à jour associées au au moins un message d'informations de commande ; et
    des informations de rythme associées au service point-multipoint.
  12. Procédé selon la revendication 11, dans lequel les informations de mise à jour indiquent les informations de mise à jour du au moins un message d'informations de commande pour le service point-multipoint.
  13. Procédé selon la revendication 11, dans lequel les informations de rythme indiquent quelle partie du canal de commande point-multipoint doit être reçue.
  14. Procédé selon la revendication 11, dans lequel les informations de rythme indiquent un moment de début de la réception de canal de commande point-multipoint.
  15. Procédé selon la revendication 11, dans lequel le terminal mobile reçoit le canal de commande point-multipoint pendant une durée conforme aux informations de rythme.
  16. Procédé selon la revendication 11, dans lequel le terminal mobile arrête la réception du canal de commande point-multipoint à un moment de fin conformément aux informations de rythme.
  17. Procédé selon la revendication 11, comprenant en outre les étapes consistant à:
    contrôler l'identificateur d'informations de commande si l'identificateur d'informations de commande est contenu dans les informations d'attribut ; et
    recevoir le au moins un message d'informations de commande si l'identificateur d'informations de commande se rapporte au terminal mobile.
  18. Procédé selon la revendication 11, comprenant en outre les étapes consistant à:
    contrôler les informations de mise à jour si les informations de mise à jour sont contenues dans les informations d'attribut ;
    comparer les informations de mise à jour aux informations de mise à jour préalablement mémorisées ; et
    recevoir le au moins un message d'informations de commande si aucunes informations de mise à jour n'ont été préalablement mémorisées ou si les informations de mise à jour sont différentes des informations de mise à jour préalablement mémorisées.
  19. Procédé selon la revendication 11, comprenant en outre les étapes consistant à :
    contrôler les informations de rythme si les informations de rythme sont contenues dans les informations d'attribut ; et
    recevoir le au moins un message d'informations de commande conformément à un intervalle de temps indiqué par les informations de rythme.
  20. Procédé selon la revendication 1, dans lequel le message d'indication d'informations de commande est reçu par l'intermédiaire d'un canal de trafic de service de diffusion/multidiffusion de données multimédia MBMS, MTCH.
  21. Procédé selon la revendication 1, dans lequel le message d'indication d'informations de commande est reçu par l'intermédiaire d'un canal de commande de service de diffusion/multidiffusion de données multimédia secondaire MBMS, S-MCCH.
  22. Procédé selon la revendication 1, dans lequel le canal de commande point-multipoint est un canal de commande de service de diffusion/multidiffusion de données multimédia MBMS, MCCH.
  23. Procédé selon la revendication 6, dans lequel le canal de trafic est un canal de trafic de service de diffusion/multidiffusion de données multimédia MBMS, MTCH.
  24. Procédé de transmission d'un service point-multipoint dans un système de communication sans fil, le procédé comprenant l'étape consistant à :
    transmettre (S11) un message d'indication d'informations de commande pour un service point-multipoint vers un terminal mobile,
    caractérisé en ce que le message d'indication d'informations de commande possède des informations d'attribut pour transmettre au moins un message d'informations de commande par l'intermédiaire d'un canal de commande point-multipoint, dans lequel le message d'indication d'informations de commande et le au moins un message d'informations de commande sont des messages point-multipoint créés à partir de la même couche de protocole ; le procédé comprenant en outre l'étape consistant à :
    transmettre (S15) le au moins un message d'informations de commande par l'intermédiaire du canal de commande point-multipoint.
  25. Procédé selon la revendication 24, dans lequel les informations d'attribut comprennent au moins l'un parmi :
    un identificateur d'informations de commande associé au au moins un message d'informations de commande ;
    des informations de mise à jour associées au au moins un message d'informations de commande ; et
    des informations de rythme associées au service point-multipoint.
  26. Procédé selon la revendication 25, dans lequel les informations de mise à jour indiquent les informations de mise à jour du au moins un message d'informations de commande pour le service point-multipoint.
  27. Procédé selon la revendication 25, dans lequel les informations de rythme indiquent un moment de début de la transmission de canal de commande point-multipoint.
  28. Procédé selon la revendication 25, dans lequel le réseau transmet le canal de commande point-multipoint pendant une durée conforme aux informations de rythme.
  29. Procédé selon la revendication 25, dans lequel le réseau arrête la transmission du canal de commande point-multipoint à un moment de fin conformément aux informations de rythme.
  30. Procédé selon la revendication 24, dans lequel le message d'indication d'informations de commande est transmis par l'intermédiaire d'un canal de trafic de service de diffusion/multidiffusion de données multimédia MBMS, MTCH.
  31. Procédé selon la revendication 24, dans lequel le message d'indication d'informations de commande est transmis par l'intermédiaire d'un canal de commande de service de diffusion/multidiffusion de données multimédia secondaire MBMS, S-MCCH.
  32. Procédé selon la revendication 24, dans lequel le canal de commande point-multipoint est un canal de commande de service de diffusion/multidiffusion de données multimédia MBMS, MCCH.
EP05726448A 2004-02-13 2005-02-11 Emission et reception d'informations de commande pour service de diffusion/multi-diffusion des donnees multimedia dans un systeme de communication mobile Active EP1714407B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020040009772A KR101114175B1 (ko) 2004-02-13 2004-02-13 이동통신 시스템에서 점대점 서비스의 송수신방법
PCT/KR2005/000390 WO2005078963A1 (fr) 2004-02-13 2005-02-11 Emission et reception d'informations de commande pour service de diffusion/multi-diffusion de donnees multimedia dans un systeme de communication mobile

Publications (3)

Publication Number Publication Date
EP1714407A1 EP1714407A1 (fr) 2006-10-25
EP1714407A4 EP1714407A4 (fr) 2009-12-02
EP1714407B1 true EP1714407B1 (fr) 2012-05-30

Family

ID=34858716

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05726448A Active EP1714407B1 (fr) 2004-02-13 2005-02-11 Emission et reception d'informations de commande pour service de diffusion/multi-diffusion des donnees multimedia dans un systeme de communication mobile

Country Status (12)

Country Link
US (1) US7499455B2 (fr)
EP (1) EP1714407B1 (fr)
JP (1) JP4335259B2 (fr)
KR (1) KR101114175B1 (fr)
CN (1) CN100589344C (fr)
AU (1) AU2005213085B9 (fr)
BR (1) BRPI0507512A (fr)
ES (1) ES2386889T3 (fr)
RU (1) RU2342791C2 (fr)
UA (1) UA83286C2 (fr)
WO (1) WO2005078963A1 (fr)
ZA (1) ZA200606374B (fr)

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101041814B1 (ko) * 2005-02-15 2011-06-17 엘지전자 주식회사 무선 이동통신 시스템에서 점대다 멀티미디어 서비스 제공방법
EP1872535A1 (fr) * 2005-04-21 2008-01-02 Nokia Corporation Support de la transmission et de la reception de paquets de donnees
CN1330215C (zh) * 2005-04-21 2007-08-01 华为技术有限公司 多媒体广播组播业务中的异频/异系统测量方法
KR101284461B1 (ko) * 2005-05-12 2013-07-09 삼성전자주식회사 메쉬 네트워크에서 다중 채널 설정 방법 및 장치
CN100421516C (zh) * 2005-06-24 2008-09-24 华为技术有限公司 异频测量的测量时间确定方法、异频测量方法及通信终端
JP4926468B2 (ja) * 2005-12-07 2012-05-09 ローム株式会社 静電破壊保護回路及びこれを備えた半導体集積回路装置
KR101333918B1 (ko) * 2006-01-05 2013-11-27 엘지전자 주식회사 이동 통신 시스템의 점-대-다 서비스 통신
KR101211807B1 (ko) 2006-01-05 2012-12-12 엘지전자 주식회사 이동통신 시스템에서 무선단말의 동기상태 관리방법
US9456455B2 (en) 2006-01-05 2016-09-27 Lg Electronics Inc. Method of transmitting feedback information in a wireless communication system
EP1987607B1 (fr) 2006-02-06 2013-11-20 LG Electronics Inc. Récepteur à deux fréquences mbms (service de diffusion/multidiffusion multimédia)
EP1997294A4 (fr) 2006-03-22 2014-08-27 Lg Electronics Inc Considérations de sécurité pour lte d'umts
KR101387475B1 (ko) 2006-03-22 2014-04-22 엘지전자 주식회사 복수의 네트워크 엔터티를 포함하는 이동 통신시스템에서의 데이터 처리 방법
WO2007126192A1 (fr) 2006-05-02 2007-11-08 Lg Electronics Inc. Procédé de transmission de données dans un système mobile de communication
RU2432684C2 (ru) * 2006-07-24 2011-10-27 Эл Джи Электроникс Инк. Двухточечные радиоканалы для службы радиовещания
US9100930B2 (en) * 2006-09-14 2015-08-04 Innovative Sonic Limited Method of selecting operating frequency for user equipment in a wireless communications system and related apparatus
GB2444998A (en) * 2006-12-11 2008-06-25 Nec Corp Dedicated radio resource control
US9596009B2 (en) 2007-04-20 2017-03-14 Blackberry Limited Multicast control channel design
KR101477280B1 (ko) * 2007-06-18 2014-12-30 한국전자통신연구원 패킷 기반 이동통신 시스템에서 제어 정보 전송 방법 및이의 수신 방법
US8649795B2 (en) * 2007-09-05 2014-02-11 Blackberry Limited Multicast/broadcast single frequency network control information transmission
US8077649B2 (en) 2007-09-13 2011-12-13 Research In Motion Limited Indication of multicast control information
CN101425915B (zh) * 2007-10-30 2011-04-20 大唐移动通信设备有限公司 一种分层传输数据的传输方法及系统、设备
CN101483810B (zh) * 2008-01-07 2010-12-22 上海贝尔阿尔卡特股份有限公司 演进型多媒体广播/多播业务数据发送和接收方法及设备
CN101854589B (zh) * 2009-04-03 2013-12-04 中兴通讯股份有限公司 多媒体广播多播业务控制信令的传输方法和系统
CN101867880B (zh) * 2009-04-14 2014-04-30 中兴通讯股份有限公司 Mcch及mcch更新指示信息控制信息的承载、接收方法与装置
WO2010124441A1 (fr) * 2009-04-27 2010-11-04 深圳华为通信技术有限公司 Procédé d'obtention et d'indication d'informations mcch et équipement utilisateur et station de base correspondants
WO2010135870A1 (fr) * 2009-05-27 2010-12-02 华为技术有限公司 Procédé et appareil de transfert et d'acquisition des informations de commande de service de diffusion/multidiffusion multimédia
CN101959131B (zh) * 2009-07-13 2015-06-10 中兴通讯股份有限公司 Mbms通知信息的承载方法与装置
KR101670516B1 (ko) * 2009-08-11 2016-10-31 엘지전자 주식회사 무선 통신 시스템에서 ｍｂｍｓ를 위한 방법 및 장치
CN102036174B (zh) * 2009-09-29 2014-07-02 中兴通讯股份有限公司 一种mbms通知信息的传输方法及系统
CN102098621B (zh) * 2009-12-09 2015-01-28 中兴通讯股份有限公司 多播控制信道通知消息的接收方法及用户设备
KR101164725B1 (ko) * 2009-12-21 2012-07-12 한국전자통신연구원 사용자 위치에 따른 멀티미디어 브로트캐스트/멀티캐스트 서비스 제어 장치 및 방법
KR101903636B1 (ko) * 2010-01-07 2018-10-04 엘지전자 주식회사 무선 통신 시스템에서 제어 정보 송수신 방법 및 장치
CN102158807B (zh) * 2010-02-11 2015-01-28 中兴通讯股份有限公司 Mcch通知信息的监听方法及装置、用户设备
US8676138B2 (en) 2010-04-19 2014-03-18 Htc Corporation Method of handling system information reception and related communication device
US9686770B2 (en) * 2010-06-15 2017-06-20 Mediatek Inc. Methods to support MBMS service continuity and counting and localized MBMS service
US9185682B2 (en) 2010-06-15 2015-11-10 Mediatek Inc. Methods to support continuous MBMS reception without network assistance
GB2485237A (en) * 2010-11-08 2012-05-09 Nec Corp MBMS provided by unicast or broadcast/multicast in dependence on the number of interested users.
KR101742321B1 (ko) * 2010-12-21 2017-06-01 한국전자통신연구원 멀티미디어 브로드캐스트 및 멀티캐스트 서비스 카운팅 방법 및 장치
WO2013076456A1 (fr) * 2011-11-22 2013-05-30 Sca Ipla Holdings Inc Système et procédé de télé-appel de terminaux à l'état hors-ligne
US8690412B2 (en) * 2012-03-15 2014-04-08 Apple Inc. Backlight structures and backlight assemblies for electronic device displays
US9532185B2 (en) * 2012-05-02 2016-12-27 Qualcomm Incorporated Achieving fast EMBMS channel switching and adding in LTE
US20140369329A1 (en) * 2013-06-18 2014-12-18 Qualcomm Incorporated Lte and external wifi bandwidth aggregation
WO2016029356A1 (fr) * 2014-08-26 2016-03-03 华为技术有限公司 Procédé et dispositif de transmission d'informations de commande
CN110366272B (zh) * 2018-04-09 2021-10-15 华为技术有限公司 传输消息的方法和装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI109861B (fi) 1998-01-05 2002-10-15 Nokia Corp Menetelmä solun yleislähetyskapasiteetin tehokkaaksi hyödyntämiseksi
JP3617930B2 (ja) * 1998-09-30 2005-02-09 株式会社東芝 無線携帯端末装置、ゲートウェイ装置及び通信処理制御方法
US6934284B1 (en) * 2000-03-30 2005-08-23 Net Insight Ab Methods for establishing control signaling at link start-up
FI20001617A (fi) 2000-07-06 2002-01-07 Nokia Mobile Phones Ltd Tiedonsiirtomenetelmõ ja -jõrjestely
KR100790131B1 (ko) * 2001-08-24 2008-01-02 삼성전자주식회사 패킷 통신시스템에서 매체 접속 제어 계층 엔터티들 간의 시그널링 방법
EP1436946B1 (fr) * 2001-10-19 2007-02-28 Nokia Corporation Transmission de services multimedias par diffusion et multi-diffusion via une interface radio
JP2003244067A (ja) 2002-02-13 2003-08-29 Nippon Telegr & Teleph Corp <Ntt> マルチキャスト通信システム
US20030169723A1 (en) * 2002-03-05 2003-09-11 John Diachina Wireless communications apparatus, methods and computer program products using broadcast channel messaging for application transport
JP4002204B2 (ja) 2002-04-09 2007-10-31 三星電子株式会社 移動通信システムにおけるマルチメディア放送／マルチキャストサービスのための制御情報伝送装置及びその方法
US20040180675A1 (en) * 2002-11-06 2004-09-16 Samsung Electronics Co., Ltd. Method for transmitting and receiving control messages in a mobile communication system providing MBMS service
US20040137885A1 (en) * 2002-11-08 2004-07-15 Sinikka Sarkkinen Method of coupling user equipment information specific to a multicast/broadcast service with a multicast/broadcast service context of a controlling network entity
KR100954560B1 (ko) * 2003-01-10 2010-04-23 삼성전자주식회사 멀티미디어 브로드캐스트/멀티캐스트 서비스를 제공하는이동 통신 시스템에서 수신 데이터 오류 복구 방법
US20040209610A1 (en) * 2003-04-17 2004-10-21 Adwankar Sandeep M. Method and apparatus for managing wireless terminals
KR100651405B1 (ko) 2003-07-24 2006-11-29 삼성전자주식회사 이동통신 시스템에서 멀티미디어 브로드캐스트/멀티캐스트 서비스의 제어 정보 송수신 장치 및 방법

Also Published As

Publication number Publication date
EP1714407A4 (fr) 2009-12-02
CN100589344C (zh) 2010-02-10
AU2005213085A1 (en) 2005-08-25
AU2005213085B9 (en) 2008-06-05
JP4335259B2 (ja) 2009-09-30
WO2005078963A1 (fr) 2005-08-25
KR20050081511A (ko) 2005-08-19
US20050213583A1 (en) 2005-09-29
EP1714407A1 (fr) 2006-10-25
RU2342791C2 (ru) 2008-12-27
UA83286C2 (ru) 2008-06-25
BRPI0507512A (pt) 2007-07-03
US7499455B2 (en) 2009-03-03
CN1922803A (zh) 2007-02-28
KR101114175B1 (ko) 2012-02-22
RU2006128797A (ru) 2008-03-20
AU2005213085B2 (en) 2008-01-10
ES2386889T3 (es) 2012-09-04
ZA200606374B (en) 2008-01-08
JP2007522758A (ja) 2007-08-09

Similar Documents

Publication Publication Date Title
EP1714407B1 (fr) Emission et reception d&#39;informations de commande pour service de diffusion/multi-diffusion des donnees multimedia dans un systeme de communication mobile
US7346339B2 (en) Transmitting and receiving notification of control information for point to multipoint service in wireless communication system
US8131273B2 (en) Method for transmitting and receiving a MBMS service in mobile communication system
US7436764B2 (en) Notification of control information in wireless communication system
US7636330B2 (en) Transmitting/receiving point-to-multipoint service in wireless communication system
US8102800B2 (en) Discontinuously transmitting and receiving multimedia broadcast/multicast service data in mobile communication system
EP1636923B1 (fr) Appareil et procede permettant d&#39;etablir le phare radiogoniometrique d&#39;un terminal mobile
US20050213541A1 (en) Method for transmitting service information between network nodes for MBMS service in mobile communication system
MXPA06009241A (en) Transmitting and receiving control information for multimedia broadcast/multicast service in mobile communication system

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060803

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20091103

RIC1 Information provided on ipc code assigned before grant

Ipc: H04B 7/26 20060101AFI20050831BHEP

Ipc: H04W 48/12 20090101ALI20091028BHEP

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: LG ELECTRONICS INC.

17Q First examination report despatched

Effective date: 20091214

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIN1 Information on inventor provided before grant (corrected)

Inventor name: CHUN, SUNG-DUCK

Inventor name: YI, SEUNG-JUNE

Inventor name: LEE, YOUNG-DAE

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 560473

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602005034415

Country of ref document: DE

Effective date: 20120726

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2386889

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20120904

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120930

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 560473

Country of ref document: AT

Kind code of ref document: T

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120831

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121001

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20130301

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602005034415

Country of ref document: DE

Effective date: 20130301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120830

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130228

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130228

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130228

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120530

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20050211

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130211

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230105

Year of fee payment: 19

Ref country code: FI

Payment date: 20230105

Year of fee payment: 19

Ref country code: ES

Payment date: 20230316

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20230106

Year of fee payment: 19

Ref country code: IT

Payment date: 20230109

Year of fee payment: 19

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230524

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240108

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20240319

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FI

Payment date: 20240105

Year of fee payment: 20

Ref country code: DE

Payment date: 20240105

Year of fee payment: 20

Ref country code: GB

Payment date: 20240105

Year of fee payment: 20