A multimedia broadcast/multicast service (MBMS) in a universal mobile telecommunications system (UMTS) includes a UTRAN that provides an MBMS service. The MBMS service-related information is exchanged between the UTRAN and a terminal or between nodes in the UTRAN by using an MBMS identification so that a user group receiving MBMS data or a data of a specific MBMS service can be identified.

Patent
   RE45333
Priority
Jun 22 2002
Filed
Dec 11 2013
Issued
Jan 13 2015
Expiry
Jun 23 2023
Assg.orig
Entity
Large
0
97
all paid
1. In a wireless radio communication network that employs a radio network interface protocol, the protocol including a radio resource control (rrc) layer and a medium access control (mac) layer, a method of providing a point-to-multipoint service, the method comprising:
configuring, at the rrc layer, an identifier that identifies the point-to-multipoint service and distinguishes the point-to-multipoint service from other point-to-multipoint services;
at the mac layer, adding the identifier to a mac header of a data unit associated with the point-to-multipoint service, wherein the identifier in the mac header is used to distinguish between point-to-multipoint services; and
transmitting the data unit to a mobile terminal.
12. In a wireless radio communication network that employs a radio network interface protocol, the protocol including a radio resource control (rrc) layer and a medium access control (mac) layer, a method of receiving a point-to-multipoint service, the method comprising:
receiving a data unit including an identifier which identifies the point-to -multipoint service, wherein the identifier is included in a mac header of the data unit;
at the mac layer, identifying the data unit as being associated with the point-to-multipoint service using the identifier; and
transferring the data in the data unit to an upper layer, wherein the identifier in the mac header is used to distinguish between point-to-multipoint services, and wherein the identifier was configured by an rrc layer of the network.
0. 23. In a wireless radio communication network that employs a radio network interface protocol, the protocol including a radio resource control (rrc) layer and a medium access control (mac) layer, an apparatus capable of providing a point-to-multipoint service, the apparatus comprising:
a processor adapted to:
configure, at the rrc layer, an identifier that identifies the point-to-multipoint service and distinguishes the point-to-multipoint service from other point-to-multipoint services; and
add, at the mac layer, the identifier to a mac header of a data unit associated with the point-to-multipoint service, wherein the identifier in the mac header is used to distinguish between point-to-multipoint services; and
a transmitter adapted to transmit the data unit to a mobile terminal.
19. In a wireless radio communication network that employs a radio network interface protocol, the protocol including a radio resource control (rrc) layer and a medium access control (mac) layer, an apparatus capable of receiving a point-to-multipoint service, the apparatus comprising:
a receiver adapted to receive a data unit that includes an identifier which identifies the point-to-multipoint service, wherein the identifier is included in a mac header of the data unit; and
at the mac layer, a mac entity adapted for identifying the data unit as being associated with the point-to-multipoint service using the identifier, and transferring the data in the data unit to an upper layer, wherein the identifier in the mac header is used to distinguish between point-to-multipoint services, and wherein the identifier was configured by an rrc layer in the network.
2. The method of claim 1 further comprising:
generating the identifier for identifying the point-to-multipoint service at the rrc layer when a radio access bearer is established.
3. The method of claim 2 further comprising:
discarding the identifier when the radio access bearer is released.
4. The method of claim 1, wherein the point-to-multipoint service is a multimedia broadcast multicast service (MBMS).
5. The method of claim 1, wherein the identifier is a multimedia broadcast multicast service (MBMS) radio network temporary identifier (RNTI).
6. The method of claim 1, wherein the data unit is a protocol data unit.
7. The method of claim 1, wherein the data unit includes an indicator indicating identifier type.
8. The method of claim 1, wherein the identifier is managed by a controlling radio network controller (CRNC).
9. The method of claim 1, wherein the identifier is transferred from the rrc layer to the mac layer.
10. The method of claim 1, wherein the mac header includes a target channel type field (TCTF).
11. The method of claim 1, wherein transmitting the data unit to a mobile terminal comprises:
transmitting the data unit in a Forward access Channel (FACH) or a Downlink Shared Channel (DSCH).
13. The method of claim 12, wherein the point-to-multipoint service is a multimedia broadcast multicast service (MBMS).
14. The method of claim 12, wherein the data unit is a protocol data unit.
15. The method of claim 12, wherein the data unit includes an indicator indicating identifier type.
16. The method of claim 12, wherein the mac header includes a target channel type field (TCTF).
17. The method of claim 12, wherein the identifier is a multimedia broadcast multicast service (MBMS) radio network temporary identifier (RNTI).
18. The method of claim 12, wherein receiving the data unit comprises:
receiving the data unit in a Forward access Channel (FACH) or a Downlink Shared Channel (DSCH).
20. The apparatus of claim 19, wherein the point-to-multipoint service is a multimedia broadcast multicast service (MBMS).
21. The apparatus of claim 19, wherein the mac header includes a target channel type field (TCTF).
22. The apparatus of claim 19, wherein the receiver is further adapted to receive the data unit in a Forward access Channel (FACH) or a Downlink Shared Channel (DSCH).

This application
wherein the value ‘K’ corresponds to the number of S-CCPCH with which FACH channel transmitting MBMS data in a corresponding cell is mapped and the number of S-CCPCH corresponds to a list order of S-CCPCH channels existing in system information of the corresponding cell.

The terminal can be aware of channel information corresponding to the number of S-CCPCH through the S-CCPCH channel list of the system information transferred through the BCH channel. Accordingly, the terminal calculates the number of S-CCPCH by substituting first assigned MBMS RNTI to equation (1) and obtains information of the calculated S-CCPCH channel from the system information, thereby receiving transmitted MBMS data.

FIG. 8 shows a process of allocating a physical channel through MTMS RNTI, in which a terminal selects a physical channel for receiving a data of a corresponding MBMS service through MBMS RNTI assignment.

UTRAN RRC sets up a lower layer for transmission of MBMS data (S23). That is, UTRAN RRC allows a physical layer, MAC, RLC and PDCP layer of UTRAN to set a parameter such as the number of the physical channel S-CCPCH provided for service in a corresponding cell, a channel code and a scrambling code of each physical channel, a size of a data to be transmitted, a time interval for data transmission, a channel coding and a type of transport channel and a logical channel mapped with a corresponding physical channel. Through this process, the physical S-CCPCH transmitting a MBMS data is set up.

UTRAN RRC transmits channel information to the RRC of a terminal through system information of BCH (S24). The channel information refers to the parameter such as the number of the physical channel provided for service in a corresponding cell, a channel code and a scrambling code of each physical channel, a size of a data to be transmitted, a time interval for data transmission, a channel coding and a type of transport channel and a logical channel mapped with a corresponding physical channel.

The terminal RRC stores the physical channel information (S25), and the UTRAN assigns MBMS RNTI to a corresponding terminal through the MBMS RNTI assignment process (S26).

The terminal RRC obtain information on the physical channel S-CCPCH indicated by the MBMS RNTI and a transport channel and a logical channel mapped with the channel form the physical channel information (S27). That is, the terminal RRC obtains the parameter such as a channel code and a scrambling code of the physical channel S-CCPCH transmitting a data of the specific MBMS service, a size of a data to be transmitted, a time interval for data transmission, a channel coding and a type of transport channel and a logical channel mapped with a corresponding physical channel.

The terminal RRC sets a lower layer of the terminal by using the obtained channel information (S28). That is, a physical layer, MAC, RLC and PDCP layer of the terminal are set by using the obtained channel information. Through this process, the physical S-CCPCH for receiving a data of the corresponding MBMS service is set. Then, the terminal can receive the data of the MBMS service through the transport channel FACH.

Transmission Control Information Using MBMS RNTI

The RRC layer of MBMS controls the transport channel and the physical channel with respect to set-up, re-set-up and release of RB to which MBMS RAB is mapped.

In order to control the set-up/re-set-up and termination, an RRC message is exchanged between RNC and UE. That is, MBMS RNTI is inserted into the RRC message for a specific MBMS service to identify a specific MBMS service.

For example, an RRC of a terminal which has received a data of a specific MBMS service transfers feedback information on an MBMS data to the RRC of UTRAN, MBMS RNTI for a corresponding MBMS service is included in the feedback information to identify the corresponding feedback information. That is, the specific MBMS RNTI is included in the RRC message transmitting the feedback information.

As so far described, the multimedia service providing method of universal mobile telecommunication system of the present invention has the following advantages.

That is, when UTRAN provides an MBMS service, MBMS RNTI is used to give and take MBMS service-related information between UTRAN and the terminal or between nodes in UTRAN. Therefore, not only does a user group receiving an MBMS data can be easily recognized but also a data of a specific MBMS service can be easily recognized.

In addition, when data is transmitted to a plurality of terminals, that is, to a terminal group, by using a point-to-multipoint radio service, specific groups receiving the data can be discernible. Thus, only MBMS data corresponding to a corresponding terminal can be transferred from the MAC layer to the upper layer.

Moreover, MBMS RNTI indicates plural terminals with one identification information, so that the length of a header can be reduced compared with the use of RNTI as in the conventional art.

Furthermore, the use of an identifier temporarily assigned in UTRAN obtains an effect of protecting information of MBMS data compared with the use of a fixed message identifier.

Also, because MBMS RNTI indicates a specific radio resource, a radio resource can be automatically assigned to plural terminals even without an assignment control message, and thus, complexity of scheduling of MBMS data transmission can be reduced.

There may be many different types of services and a Service ID (or MTCH: MBMS Traffic Channel) corresponds to a service type. Thus, if there are 20 services, then there may be 20 Service ID's, for example. In this instance, the format of the MAC PDU may be [TCTF][MBMS-ID][MAC SDU], where “TCTF” is the Target Channel Type Field, “MBMS-ID” is the MBMS Identification code and “MAC SDU” is the MAC service data unit. In this instance, for example, the header contains [TCTF] and [MBMS-ID]. Although the header may have an extra field for the MBMS-ID, the MBMS-ID allows the MAC in the user equipment to filter those information that is unusable by identifying whether the specific MBMS-ID is in the list of those services that the particular user equipment is capable of receiving.

The MBMS-ID may be allocated and deallocated by the UTRAN or the core network. For example, the UTRAN or the core network may have a list of existing services. If a new service is needed or desired (either because the URAN or core network adds a new service or a new user equipment(s) enters a network that has the capability of receiving a new service that is not currently provided), then the UTRAN or the core network may include a new MBMS-ID in the list of services. Those user equipments that have the capability of receiving the new service represented by the new MBMS-ID will have the new MBMS-ID in its list of services capable of receiving at the MAC layer. If a service is no longer needed or desired (either because the URAN or core network deletes or cancels an existing service or an existing user equipment(s) leaves a network and the remaining user equipments do not need a particular service), then the UTRAN or the core network may delete the MBMS-ID(s) that corresponds to the service(s) that is no longer needed. Here, the MBMS-ID may be either a temporary ID (RNTI, for example) or a permanent ID.

FIG. 9 is a flow diagram showing a process of providing MBMS service in a mobile communication system according to an embodiment of the present invention. The communication system has a plurality of user equipments and a fixed station (such as the UTRAN and/or the core network), and it has a protocol including a physical layer and a plurality of upper layers above the physical layer.

Referring to FIG. 9, step 101 represents a fixed station sending a message (such as a broadcast or multicast message) to user equipments (UE) through the physical layer of the fixed station and the user equipments. The message is sent using a common channel or a dedicated logical channel, for example. The message contains an identification code corresponding to a specific MBMS service provided by the fixed station. This message may have a format including a header and data, and the identification code is contained in the header. The identification code may be a permanent code or temporary code. In a preferred embodiment, the fixed station may include multiple identification codes corresponding to multiple services available. In this case, for example, each identification code may correspond to a single specific MBMS service. In the present invention, a service corresponding to an identification code may be added or deleted by the fixed station. A service is added or deleted according to services required by the user equipment.

Then, in step 102, a first upper layer above the physical layer of the user equipment receives the message. The first upper layer may include a Medium Access Control (MAC) layer, for example. In a preferred embodiment, the message has a MAC packet data unit format including a header having a message type and the identification code. The message type is a target channel type field (TCTF).

The first upper layer of the user equipment determines whether to pass the message to a second upper layer of the user equipment in step 103. The first upper layer uses the identification code to determine whether to pass the message to the second upper layer of the user equipment. A list of identification codes is received from an upper layer above the first layer.

FIG. 10 is a flow diagram showing a process of providing MBMS service in a mobile communication system according to another preferred embodiment of the present invention.

Referring to FIG. 10, step 111 represents a fixed station sending a message to user equipments (UE) through the physical layer of the fixed station and the user equipments. In step 112, a first upper layer above the physical layer of a user equipment receives the message transmitted from the fixed station. Then, the user equipment compares the received identification code included in the received message with the identification code stored in its memory, for example, in step 113. If the received identification code matches an identification code in the memory of the user equipment, then the user equipment passes the message to a second upper layer, as shown in step 114.

FIG. 11 is a flow diagram showing a process of providing MBMS service in a mobile communication system according to still another preferred embodiment of the present invention.

Referring to FIG. 11, step 121 represents a fixed station generating a message including an identification code field corresponding to a specific MBMS. In step 122, the fixed station transmits the message via the physical layer for receipt by the first upper layer of the user equipment. Then, the first upper layer of the user equipment determines whether to pass the received message to its second upper layer in step 123.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Lee, Young-Dae, Lee, So-young, Yi, Seung-June

Patent Priority Assignee Title
Patent Priority Assignee Title
5457808, Feb 04 1992 NEC Corporation Point-to-multipoint communication network capable of retransmitting a multicast signal
5459725, Mar 22 1994 INTERGRAPH HARDWARE TECHNOLOGIES COMPANY INC Reliable multicasting over spanning trees in packet communications networks
6097949, Apr 15 1997 SK Telecom Co., Ltd. Method for providing closed user group service in mobile communication network
6104709, Jul 17 1998 Google Technology Holdings LLC Channel assignment within a broad-band communication system
6252868, Oct 05 1992 Telefonaktiebolaget LM Ericsson (publ) Digital control channels having logical channels supporting broadcast SMS
6252874, Jul 20 1998 D-Link Corporation Ethernet card and ethernet card improvement methods
6614810, Sep 14 1998 Samsung Electronics Co., Ltd. Method for processing data to be transmitted over common channel
6684081, May 10 2002 HMD Global Oy Method and system for separating control information and user data from multicast and broadcast services
6701155, Jan 11 2002 Nokia Technologies Oy Network initialized packet data protocol context activation for multicast/broadcast services
6751227, Nov 02 1999 Qualcomm Incorporated Signalling method
6804528, Nov 03 2000 Alcatel-Lucent USA Inc Apparatus and method for use in the multicast of traffic data in wireless multiple access communications systems
6839348, Apr 30 1999 Cisco Technology, Inc System and method for distributing multicasts in virtual local area networks
6839565, Feb 19 2002 Nokia Technologies Oy Method and system for a multicast service announcement in a cell
6965579, Mar 08 1999 LG Electronics Inc Communication system and method for operating multicast service in communication system
6965580, Aug 16 1999 Kabushiki Kaisha Toshiba Radio communication system using point-to-point and point-to-multipoint user information communications
7215948, Dec 07 1999 NEC Corporation Multicast communication method in a CDMA mobile communication system
7308278, May 18 2002 AEGIS 11 S A Selective service method in multicast system
7415046, Feb 19 2001 Acacia Research Group LLC Method, apparatus and computer programs for multiplexing and/or demultiplexing
7433334, Mar 08 1999 WSOU Investments, LLC Method for establishing a communication link between a user equipment and a radio network
7606226, Jun 22 2002 LG ELECTRONICS, INC Multimedia service providing method and radio mobile communication system
8077716, Jun 22 2002 LG Electronics Inc. Multimedia service providing method for radio mobile communication system
20010002757,
20020080737,
20020124069,
20030016698,
20030157949,
20030194992,
20030207696,
20030211855,
20040017809,
20040022218,
20040057387,
20040081192,
20040152473,
20040184471,
20050075124,
20050076369,
20050193309,
20060019641,
20060156370,
20060168504,
20060189272,
20060209870,
20080318518,
20090274446,
20100172279,
DE10107700,
EP1077539,
EP1148687,
IN546KOLNP2006,
IN548KOLNP2004,
IN911KOLNP2004,
JP11252009,
JP2000138676,
JP2000358267,
JP2001053675,
JP2001128205,
JP2001298407,
JP2001308856,
JP2002064878,
JP2002539490,
JP2003060699,
JP2005512273,
JP5219056,
JP7283782,
JP9270790,
KR100224852,
KR100249503,
KR1019988024467,
KR1019990037501,
KR1020000032645,
KR1020000037821,
KR1020000047263,
KR1020010026301,
KR1020020009282,
KR1020020019314,
KR1020020079453,
KR1020030029310,
KR1020040064869,
KR1020050014984,
KR19990053163,
KR20030069365,
WO54521,
WO105158,
WO110146,
WO233937,
WO241531,
WO3098871,
WO3105353,
WO2004002021,
WO2004017540,
WO2004028041,
WO2004028042,
WO2004042964,
WO2005013914,
WO2005067194,
WO9944313,
/
Executed onAssignorAssigneeConveyanceFrameReelDoc
Dec 11 2013LG Electronics Inc.(assignment on the face of the patent)
Date Maintenance Fee Events
Apr 01 2015ASPN: Payor Number Assigned.
May 29 2015M1551: Payment of Maintenance Fee, 4th Year, Large Entity.
May 08 2019M1552: Payment of Maintenance Fee, 8th Year, Large Entity.
May 09 2023M1553: Payment of Maintenance Fee, 12th Year, Large Entity.


Date Maintenance Schedule
Jan 13 20184 years fee payment window open
Jul 13 20186 months grace period start (w surcharge)
Jan 13 2019patent expiry (for year 4)
Jan 13 20212 years to revive unintentionally abandoned end. (for year 4)
Jan 13 20228 years fee payment window open
Jul 13 20226 months grace period start (w surcharge)
Jan 13 2023patent expiry (for year 8)
Jan 13 20252 years to revive unintentionally abandoned end. (for year 8)
Jan 13 202612 years fee payment window open
Jul 13 20266 months grace period start (w surcharge)
Jan 13 2027patent expiry (for year 12)
Jan 13 20292 years to revive unintentionally abandoned end. (for year 12)