EP1915021B1 - Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralitée de porteuses - Google Patents

Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralitée de porteuses Download PDF

Info

Publication number
EP1915021B1
EP1915021B1 EP08001745A EP08001745A EP1915021B1 EP 1915021 B1 EP1915021 B1 EP 1915021B1 EP 08001745 A EP08001745 A EP 08001745A EP 08001745 A EP08001745 A EP 08001745A EP 1915021 B1 EP1915021 B1 EP 1915021B1
Authority
EP
European Patent Office
Prior art keywords
service
multicast
bearer
bearers
broadcast service
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.)
Not-in-force
Application number
EP08001745A
Other languages
German (de)
English (en)
Other versions
EP1915021A1 (fr
Inventor
Ralf Becker
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.)
Panasonic Corp
Original Assignee
Panasonic Corp
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 Panasonic Corp filed Critical Panasonic Corp
Priority to DE602005016735T priority Critical patent/DE602005016735D1/de
Priority to AT09164581T priority patent/ATE505914T1/de
Priority to EP09164581A priority patent/EP2101521B1/fr
Publication of EP1915021A1 publication Critical patent/EP1915021A1/fr
Application granted granted Critical
Publication of EP1915021B1 publication Critical patent/EP1915021B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1877—Measures taken prior to transmission
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the invention relates to a method providing a multicast or broadcast service to (the user of) a mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service is associated to a plurality of bearers for providing the multicast or broadcast service:
  • the invention relates to a mobile terminal for providing a multicast or broadcast service to a user, and to a network entity for providing a multicast or broadcast service to a mobile terminal via a radio access network of a mobile communication system.
  • the Internet Multicast Model provides basic mechanisms for distributing data with different QoS parameters to subsets of the multicast distribution trees.
  • the hosts which communicate with the multicast routers using the Internet Group Management Protocol (IGMP - see Fenner, "Internet Group Management Protocol, Version 2", RFC 2236, available at http://www.ietf.org ), can in principle actively adapt the QoS in a sub tree by joining/leaving multicast groups.
  • IGMP Internet Group Management Protocol
  • Mobile communications networks usually follow a network-centric approach for QoS provision, resulting in a different Broadcast/Multicast Service Model. Subscribed users are allowed to express their interest on a multicast session by IGMP or similar signaling to dedicated network nodes.
  • the data distribution tree along which service data are provided, however, is build autonomously and modified by the network when necessary, e.g. in response to handover. This approach is advantageous in particular since the radio network controller has the knowledge of available resources (e.g. by providing resource control functionality), and it allows end users to be provided with a more or less seamless service.
  • the first concept for a heterogeneous QoS in the MBMS Architecture was proposed as Option G in the 3GPP TR 23.846: "Multimedia Broadcast/Multicast (MBMS); Architecture and functional description (Release 6)", V6.1.0, December 2002 , available at http://www.3gpp.org (for an overview on the architecture and functional description of MBMS see 3GPP TS 23.246: “Multimedia Broadcast/Multicast (MBMS); Architecture and functional description (Release 6)", V6.5.0, January 2005 ).
  • the architecture in TR 23.846 defines a MBMS Bearer Service that may include multiple streams (optional or alternative), each mapping to a single RTP instance. Each stream is transported over a unique tunnel between GGSN (Gateway GPRS Support Node) and RNC (Radio Network Controller), which is maintained throughout the duration of a MBMS service.
  • GGSN Global System for Mobile communications
  • RNC Radio Network Controller
  • a RNC it is in principle possible for a RNC to choose a stream of a MBMS service at session start as well as changing/adding streams during the session.
  • appropriate mechanisms have to be implemented in the radio access network (RAN).
  • RAN radio access network
  • a necessary prerequisite is the communication and management of stream states and relations, which allows a RAN node to choose the (set of) appropriate streams according to the current conditions of a cell or downstream nodes
  • the 3GPP Multimedia Broadcast/Multicast Service (MBMS) Architecture currently only supports a very simple QoS model. It basically provides a non-scalable and non-adaptive service, where either all branches of a MBMS distribution tree are established with the same QoS or the whole service is cancelled. There is no negotiation of QoS values between network nodes, which implies that some of the branches may not be established if QoS requirements cannot be met by the according network nodes. This is relevant both at the beginning of a session or during a session, e.g. at each handover, when a new branch of the distribution tree has to be created/torn down.
  • mobile terminals are quite heterogeneous with respect to their provided capabilities, i.e., processing power, display size, etc.
  • the current MBMS architecture cannot cope with this heterogeneity or it can by subjecting all terminals (those with better and worse capacity) to a worst case scenario, where all adapt to the lowest quality.
  • the MBMS Architecture is, however, not optimal in view of accounting and service provision.
  • a single user service consisting of a plurality of alternative streams (for example, three different audio streams at different bit rates) or complementary streams (for example, three video streams at different bit rates and two audio stream at different bitrates) is provided using the 3GPP MBMS architecture
  • each of the alternative streams would need to be provided as three separate MBMS services, each comprising one of the alternative streams.
  • each possible combination of streams is provided as a separate MBMS user service to the users.
  • layered streams same would be provided in a respective MBMS User Service per layer combination. i.e. for example, when the service media is provided in three layers (base, enhancement 1, enhancement 2) there would need to be established three different MBMS services (base, base & enhancement 1, base & enhancement 1 & enhancement 2).
  • the lack of an adequate QoS model in MBMS and the implications from the MBMS architecture do not allow for QoS differentiation in individual branches of the distribution tree of a service.
  • the need for several parallel MBMS services required for providing alternative or complementary streams of an, actually, "single" service leads to an increased signaling overhead in the network and wastes resources in the UMTS network.
  • the UE receives 402 an MBMS User Service description in a service discovery or announcement procedure 401.
  • This MBMS User Service description describes all MBMS bearers contained in the MBMS User Service.
  • the individual bearers are identified by their respective TMGI (Temporary Mobile Group Identifier), which is dynamically allocated in the BM-SC (Broadcast/Multicast Service Center).
  • TMGI Temporal Mobile Group Identifier
  • the MBMS User Service description refers to two session descriptions session1.sdp and session2.sdp, which both define a bearer belonging to the MBMS service requested by the user.
  • the UE activates 403 all MBMS bearers contained in the MBMS User Service Description. It is to be noted that the activation of a bearer is to be understood as setting of a logical state in the distribution tree of the MBMS service to indicate that the respective UE requests the service. The activation of the bearers does not imply the reservation of resources in the network.
  • the BM-SC As soon as the BM-SC is ready to start the User Service, it sends 404 a MBMS Session Start Request for each bearer of the User Service to the network.
  • the RNCs send 405 MBMS notifications over the air to inform the UEs of upcoming data transmission.
  • the radio bearer information necessary for the reception of the bearers is included in these notifications.
  • the TMGI is used to identify the respective MBMS bearer.
  • the RNC allocates the radio resource required for service provision. Based on the information received in the notifications, the UEs may tune in to receive the data which are provided 406, 407 from the BM-SC via the CN/RAN to the UE.
  • the UEs will activate all bearers (carrying one or more of the individual streams of the service) and will expect that a notification for each bearer is received and that data is provided on each of the bearers belonging to the MBMS User Service.
  • a single MBMS service in an enhanced MBMS architecture allows providing a plurality of bearers transporting layered, alternative, or complementary streams within a single user service, it is clear that not all of the bearers listed in the MBMS User Service description need to be simultaneously provided to the UEs. However, if the UEs do not receive all bearers listed in the 3GPP MBMS User Service description, the UEs will consider this an error in service delivery and will act accordingly.
  • 3GPP TS 23.246 it is also, suggested that, in a heterogeneous 2G-3G system, the same MBMS user service may transfer its data on separate MBMS bearer services for 2G or 3G coverage, typically with different QoS.
  • the "different" 2G and 3G content streams for the same MBMS user service are sent on the different IP multicast address associated with 2G and 3G TMGIs.
  • 3GPP TS 26.346 “Multimedia Broadcast/Multicast Service; Protocols and Codecs (Release 6)", V1.5.0, November 2004 the user equipments are only aware of the respective stream provided in their 2G or 3G system.
  • WO 2004/051926 A1 relates to a method for performing a flexible multicast of multicast data to a multicast group within a telecommunication system wherein the multicast data is provided by a broadcast/multicast server and transferred to the users registered to the multicast group by means of channels.
  • multi-channel multicast groups B1,B2,...) are provided.
  • Each multi-channel multicast group offers at least one channel wherein a channel transports content.
  • the availability and configuration of the multi-channel multicast group is announced to the users by means of an announcement multicast group (A).
  • the user either initiates the changing to an announced multi channel multicast group or the user is forced by the operator to change in case the operator wants to control the allocation of resources.
  • One key aspect of the invention is the provision of information on the individual (layered/alternative/complementary) bearers' relationships to the mobile terminals receiving a multicast or broadcast service in order to facilitate a successful service reception.
  • the bearers' relationships may be provided in service description information for the multicast or broadcast service which indicates the bearers associated to the multicast or broadcast service and predetermined bearer combinations among the plurality of bearers.
  • Each predetermined bearer combination comprises at least one of said plurality of bearers and each predetermined bearer combination provides the multicast or broadcast service at predetermined quality of service parameters.
  • the mobile terminal may determine whether the at least one bearer indicated in at least one notification received from the network corresponds to one of the predetermined bearer combinations and may appropriately act upon this determination result.
  • each bearer of the multicast or broadcast service comprises one packet stream of the service (e.g. audio or video).
  • the service e.g. audio or video
  • more than one packet stream e.g. audio and video
  • an embodiment of the invention relates to a method for providing a multicast or broadcast service to the user of a mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service is associated to a plurality of bearers for providing the multicast or broadcast service.
  • the mobile terminal may receive service description information for the multicast or broadcast service, wherein the service description information indicates the plurality of bearers associated to the multicast or broadcast service. Further, the service description information indicates predetermined bearer combinations among the plurality of bearers, each predetermined bearer combination comprising at least one of the plurality of bearers and each predetermined bearer combination providing the multicast or broadcast service at predetermined quality of service parameters.
  • the mobile terminal may activate the plurality of bearers associated to the multicast or broadcast service. It should be noted that the activation of the bearers only indicates the mobile terminal's interest in the respective bearers activated, i.e. indicates the mobile terminal's interest in the multicast or broadcast service.
  • the mobile terminal may receive service notification information that indicates at least one bearer of the plurality of bearers being multicast or broadcast via the air interface of radio access network.
  • the mobile terminal may determine whether the at least one bearer indicated in the received service notification information corresponds to one of the predetermined bearer combinations. If this is the case, the mobile terminal may receive content data of the multicast or broadcast service via the at least one bearer indicated in the service notification information and providing the content data to the user of the mobile terminal.
  • the multicast or broadcast service is a MBMS User Service provided via an UMTS network.
  • the mobile terminal may also detect situations in which an error is detected due to the notification information not indicating an "allowed" bearer combination. In this respect, the mobile terminal may provide an error message to the user of the mobile terminal, if the at least one bearer indicated in the received service notification information does not correspond to one of the predetermined bearer combinations.
  • the mobile terminal may wait for the reception of further service notification information before providing the content data of the multicast or broadcast service to the user of the mobile terminal, if the at least one bearer indicated in the received service notification information does not correspond to one of the predetermined bearer combinations and may provide an error message to the user of the mobile terminal, if no further service notification information is received within a predetermined time span.
  • the mobile terminal may be implement routines that handle cases where an insufficient number of bearers for a provided quality of service level are provided from the network.
  • the service notification information further indicates parameters required for receiving the at least one bearer by the mobile terminal.
  • the terminal may be further notified on the parameters that enable same to tune to a respective one of the indicated bearers.
  • the service description information comprises tags defining the predetermined bearer combinations.
  • the service description information may (further) comprise a tag indicating the relationship between the predetermined bearer combinations.
  • the service description information may further define a priority for each of the predetermined bearer combinations.
  • the definition of combination priorities may indicate the order of desirable bearer combinations in terms of quality of service requirements for alternative bearer combinations.
  • the priority might indicate the order of layers. This enables the mobile terminals to fully understand the user service semantics.
  • the service notification information is provide in at least one notification message.
  • the notification information is provided via a broadcast radio channel.
  • Another embodiment of the invention relates to the operation of a network entity of the radio access network controlling the radio resources on the air interface of the radio access network.
  • this network entity is commonly referred to as the RNC (Radio Network Controller).
  • the network element may be also any other network element of the radio access network which controls the radio resources.
  • this network entity may correspond to a Node B responsible for radio resource control (RRC).
  • RRC radio resource control
  • the embodiment relates to a method providing a multicast or broadcast service to a mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service is again associated to a plurality of bearers for providing the multicast or broadcast service.
  • the network entity may first receive service context information of the multicast or broadcast service from a network entity of the core network of the mobile communication network.
  • This service context information indicates the plurality of bearers associated to the multicast or broadcast service.
  • the service context information indicates predetermined bearer combinations among the plurality of bearers, wherein each predetermined bearer combination comprises at least one of the plurality of bearers and provides the multicast or broadcast service at predetermined quality of service parameters.
  • the network entity may comprise a quality-of-service management function and may obtain therefrom (inter alia) quality-of-service constraints indicating a quality-of-service available for downstream transmission on the interface of the network entity through which the service request of the mobile terminal has been received.
  • the network entity may now select a bearer combination from the predetermined bearer combinations that can be provided within the quality-of-service constraints obtained from the quality-of-service management function.
  • the network entity may announce the transmission of the multicast or broadcast service on the selected bearers. Therefore, the network entity may for example transmit service notification information indicating the selected bearer combination to the mobile terminal. Further the network entity may continue with transmitting content data of the multicast or broadcast service to the mobile terminal via the at least one bearer of the selected bearer combination.
  • the network element may further allocate radio resources for the transmission of content data via the bearers of the selected bearer combination.
  • the resource reservation as well as the transmission of the notification information may be preformed after the network entity having received an indication on the start of the multicast or broadcast service, for example in a session start message.
  • the network entity may further relay service description information for the multicast or broadcast service to the mobile terminal, wherein the service description information indicates the plurality of bearers associated to the multicast or broadcast service.
  • This service description information may further indicate predetermined bearer combinations among the plurality of bearers.
  • Each predetermined bearer combination may comprise at least one of the plurality of bearers and each predetermined bearer combination may provide the multicast or broadcast service at predetermined quality of service parameters.
  • an embodiment of the invention foresees that the network entity monitors the quality-of-service constraints indicating the quality-of-service available for downstream transmission for the interface of the network entity through which the service request of the mobile terminal has been received utilizing the quality-of-service management function of the network entity and determines whether the monitored quality-of-service constraints still allow for providing the selected bearer combination to the mobile terminal.
  • the network entity may select another bearer combination from the predetermined bearer combinations providable within the quality-of-service constraints obtained from the quality-of-service management function based on the predetermined quality of service parameters for each of the predetermined bearer combination comprised in the service context information.
  • the network entity may transmit service notification information indicating the selected other bearer combination to the mobile terminal, and may further transmit content data of the multicast or broadcast service to the mobile terminal via the at least one bearer of the selected other bearer combination.
  • the network entity may also allocate radio resources for the transmission of content data via the bearers of the selected other bearer combination and may free the radio resources that have been previously allocated for the transmission of content data of the multicast and broadcast service.
  • the service description information is comprised in a user service description and a service description for each bearer of the plurality of bearers separately provided to the mobile terminal.
  • the user service description indicates an URI of each of the service descriptions associated to the plurality of bearers and defines the predetermined bearer combinations based on the URIs and each service description for a respective one of the plurality of bearers comprises a temporary identifier of the respective bearer.
  • the service notification information comprises the temporary identifier of each bearer comprised in the selected bearer combination.
  • Another embodiment of the invention relates to a mobile terminal for providing a multicast or broadcast service to a user.
  • the multicast or broadcast service is transmitted via a radio access network of a mobile communication system and is associated to a plurality of bearers for providing the multicast or broadcast service.
  • the mobile terminal may comprise a receiver for receiving service description information for the multicast or broadcast service.
  • the service description information indicates the plurality of bearers associated to the multicast or broadcast service. Further, the service description information indicates predetermined bearer combinations among the plurality of bearers. Each predetermined bearer combination may comprise at least one bearer of the plurality of bearers. Moreover, each predetermined bearer combination may provide the multicast or broadcast service at predetermined quality of service parameters.
  • the receiver of the mobile terminal may be further adapted to receive service notification information in response to the activation of the plurality of bearers.
  • the service notification information indicates at least one bearer of the plurality of bearers being multicast or broadcast via the air interface of radio access network.
  • the mobile terminal may comprise a transmitter for activating the plurality of bearers associated to the multicast or broadcast service, and a processing means for determining whether the at least one bearer indicated in the received service notification information corresponds to one of the predetermined bearer combinations.
  • the receiver of the mobile terminal may be adapted to receive content data of the multicast or broadcast service via the at least one bearer indicated in the service notification information, if the processing means has determined that the at least one bearer indicated in the received service notification information corresponds to one of the predetermined bearer combinations.
  • the mobile terminal comprised is adapted to provide the content data to the user of the mobile terminal.
  • the mobile terminal further comprises means adapted to perform the steps of the method for providing a multicast or broadcast service to the user of a mobile terminal according to one of the various embodiments and variations thereof above.
  • Another embodiment of the invention relates to a network entity for providing a multicast or broadcast service to a mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service is associated to a plurality of bearers for providing the multicast or broadcast service.
  • the network entity may be located in the radio access network and may be adapted to control the radio resources on the air interface of the radio access network.
  • the network entity may comprise a receiver for receiving a service context information of the multicast or broadcast service from a network entity of the core network of the mobile communication network.
  • This service context information indicates the plurality of bearers associated to the multicast or broadcast service as well as predetermined bearer combinations among the plurality of bearers.
  • Each predetermined bearer combination comprises at least one of the plurality of bearers and may provide the multicast or broadcast service at a predetermined quality of service parameters.
  • the network entity may include a processing means for obtaining from a quality-of-service management function of the network entity quality-of-service constraints indicating a quality-of-service available for downstream transmission on the interface of the network entity through which the service request of the mobile terminal has been received.
  • the processing means may be adapted to select a bearer combination from the predetermined bearer combinations providable within the quality-of-service constraints obtained from the quality-of-service management function based on the predetermined quality of service parameters for each of the predetermined bearer combination comprised in the service context information.
  • the network entity includes a transmitter for transmitting service notification information indicating the selected bearer combination to the mobile terminal, and for transmitting content data of the multicast or broadcast service to the mobile terminal via the at least one bearer of the selected bearer combination.
  • the network entity further comprises means adapted to perform the steps of the method for providing a multicast or broadcast service to the mobile terminal according to one of the various embodiments and variations thereof above.
  • Another embodiment of the invention relates to a computer readable medium storing instructions that, when executed by a processor of a mobile terminal, cause the provision of a multicast or broadcast service to the user of the mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service may be associated to a plurality of bearers for providing the multicast or broadcast service.
  • the mobile terminal may be caused to receive the multicast or broadcast service by receiving a service description information for the multicast or broadcast service, wherein the service description information indicates the plurality of bearers associated to the multicast or broadcast service, wherein the service description information further indicates predetermined bearer combinations among the plurality of bearers, each predetermined bearer combination comprising at least one of the plurality of bearers and each predetermined bearer combination providing the multicast or broadcast service at predetermined quality of service parameters.
  • the instructions may further cause the mobile terminal to receive the multicast or broadcast service by activating the plurality of bearers associated to the multicast or broadcast service, receiving service notification information in response to the activation of the plurality of bearers, wherein the service notification information indicates at least one bearer of the plurality of bearers being multicast or broadcast via the air interface of radio access network, and determining whether the at least one bearer indicated in the received service notification information corresponds to one of the predetermined bearer combinations. If so, the instructions may cause the mobile terminal to receive content data of the multicast or broadcast service via the at least one bearer indicated in the service notification information and to provide the content data to the user of the mobile terminal.
  • the computer readable medium further stores instructions that, when executed by the processor of the mobile terminal, cause the mobile terminal to execute the steps of the method for providing a multicast or broadcast service to the user of a mobile terminal according to one of the various embodiments and variations thereof above.
  • Another embodiment of the invention provides a computer readable medium storing instructions that, when executed by a processor of a network entity, cause the network entity to provide a multicast or broadcast service to a mobile terminal via a radio access network of a mobile communication system.
  • the multicast or broadcast service may be associated to a plurality of bearers for providing the multicast or broadcast service.
  • the network entity may be located in the radio access network and controlling the radio resources on the air interface of the radio access network.
  • the instructions when executed by the processor may cause the network entity to receive a service context information of the multicast or broadcast service from a network entity of the core network of the mobile communication network, wherein the service context information indicates the plurality of bearers associated to the multicast or broadcast service and wherein the service context information further indicates predetermined bearer combinations among the plurality of bearers.
  • Each predetermined bearer combination may comprise at least one of the plurality of bearers and each predetermined bearer combination may provide the multicast or broadcast service at a predetermined quality of service parameters.
  • the instructions may cause the network entity to obtain from a quality-of-service management function of the network entity quality-of-service constraints indicating a quality-of-service available for downstream transmission on the interface of the network entity through which the service request of the mobile terminal has been received, and to select a bearer combination from the predetermined bearer combinations providable within the quality-of-service constraints obtained from the quality-of-service management function based on the predetermined quality of service parameters for each of the predetermined bearer combination comprised in the service context information.
  • the instructions may cause the network entity to transmit service notification information indicating the selected bearer combination to the mobile terminal, and to transmit content data of the multicast or broadcast service to the mobile terminal via the at least one bearer of the selected bearer combination.
  • the computer readable medium further stores instructions that, when executed by the processor of the network entity, cause the network entity to execute the steps of the method for providing a multicast or broadcast service to the mobile terminal according to one of the various embodiments and variations thereof above.
  • the present invention is mainly described with respect to bandwidth requirements and the respective to QoS adaptation.
  • QoS differentiation and adaptation within the service description information might also be applied to any other QoS parameter, e.g. the loss rate, or a combination of parameters.
  • the MBMS Transport Services and MBMS User Service are enhanced.
  • An important aspect for the design of the enhanced multicast/broadcast service architecture is to cover a wide range of possibilities for content adaptation. For example available adaptive media codecs may be covered and a framework for future extensions may be provided.
  • adaptive media codecs are layered codecs such as MPEG2 or MPEG4. These codecs typically encode media information in (at least) two or more layers, whereby the lowest layer is the most important layer. Following (higher) layers depend on previous (lower) ones.
  • Content may also be encoded in several independent representations, e.g. using an MPEG-1 encoder that allows providing alternative streams having differing bandwidth requirements or differing error resilience.
  • MDC multiple description codec
  • a further design consideration is the availability of RAN (Radio Access Network) resources.
  • the RAN may be typically considered being the critical system where the establishment of transport bearers may represent a bottleneck due to scarce radio resources.
  • an enhanced multicast/broadcast service architecture should consider adaptation functionality to react on changing RAN resources in the RNCs (Radio Network Controllers).
  • an enhanced multicast/broadcast service architecture may allow for both, adaptation at the session start and during a session, e.g. at handovers.
  • MBMS data may be distributed to multiple users through a MBMS distribution tree that can go through many RNCs and many SGSNs.
  • GTP GPRS Tunneling Protocol
  • RNC Radio bearers
  • a Bearer Service e.g. UMTS/MBMS Bearer
  • a bearer service includes all aspects to enable the provision of a contracted QoS. These aspects are among others the control signaling, user plane transport and QoS management functionality.
  • a UMTS bearer service layered QoS architecture is shown in Fig. 2 . Each bearer service on a specific layer offers its individual services using services provided by the layers below.
  • the specific relations of the functions between the nodes (GGSN, SGSN, RNC, etc.) needed to specify, establish, modify and maintain a UMTS Bearer Service with a specific QoS may be implementation specific. This means that several technologies such as DiffServ, IntServ (see Braden et al., "Integrated Services in the Internet Architecture: an Overview", RFC1633, 1994 ), RSVP or MPLS may be used.
  • the allocation of these functions to the UMTS entities means that these entities may enforce the QoS commitments negotiated for the UMTS bearer service.
  • the specific realization of these functions may be implementation dependent and has only to maintain the specified QoS characteristics.
  • the QoS management functions of all UMTS entities together may ensure the provision of the negotiated service between the access points of the UMTS bearer service.
  • the functionality of the Service Manager as described in section 6.2.1.1 of 3GPP TS 23.107: "Technical Specification Group Services and System Aspects; Quality of Service (QoS) concept and architecture (Release 6)" (see version 6.1.0, March 2004 ) may be of particular interest.
  • the service manager coordinates the functions of the control plane (e.g. MBMS Bearer Context) for establishing, modifying and maintaining the service it is responsible for (see Fig. 3 ). Further, it provides all user plane QoS management functions with the relevant attributes (e.g. guaranteed bitrate, maximum bitrate, maximum packet size, loss rate, etc.).
  • the service manager may further offer services to other instances (e.g. MBMS Bearer Context management functions), may signal with peer service managers and may use services provided by other instances.
  • the service manager may further perform an attribute translation (e.g. application packet loss rate to RLC SDU loss rate, SDU Loss rate to Layer 1/Layer 2 block error rate) to request lower layer services. Furthermore, it may interrogate other control functions to receive permission for service provision.
  • an illustrative example of the latter is the typical flash-crowd phenomena, where a particular server and associated network segment is overloaded by users requests.
  • Another example may be the failure of a node in the service delivery path or the uncertainty about how many users will join multicast services like 3GPP MBMS.
  • an enhanced multicast/broadcast service architecture is to enable network-driven adaptation of the multicast/broadcast service.
  • the MBMS user will typically have little or no chance to negotiate the details of session delivery with the server (e.g. BM-SC).
  • the server e.g. BM-SC
  • the network-driven adaptation becomes important.
  • the QoS architecture is extended such that a differentiation of streams/bearers of a user service becomes possible at the network nodes (network entities) along the distribution tree of the MBMS User Service. In this manner, network-driven adaptation to changing resources, heterogeneous terminals and different network components is possible.
  • the MBMS User Service Context stores references to the bearers comprised in a service. Additionally, bearer relation information may be stored which defines the relation between the bearers, so that an adaptation node may perform activation/deactivation of bearers according to the downlink capabilities, e.g. the downstream QoS constraints.
  • the timeline of an MBMS User Service considered in the following for exemplary purposes only would be as follows: in the data plane, the service's content data (typically in form of optional/alternative/complementary streams) of the requested multimedia broadcast or multicast service is forwarded downstream on their MBMS bearers as long as the QoS requirements (constraints) are met by any of the intermediate network entities. If for example an intermediate node may not forward all bearers belonging to the user service, it filters the bearers by selecting a subset of available bearer services in order to adapt the overall session stream to the available QoS.
  • the relayed context information e.g. within the MBMS Bearer Context and the newly defined MBMS User Service Context
  • the information necessary to establish the MBMS Bearer Context and the newly defined MBMS User Service Context may be propagated downstream the distribution tree upon request.
  • the context information may further allow the network to react to sudden capacity changes (up-/downgrades) because the nodes are aware of all options, i.e. possible bearer combinations that would be available for service delivery.
  • the relayed context information describes the options for service configuration, i.e. the service semantics, and it may for example be stored in the MBMS User Service Context.
  • the service semantics may for example comprise information on the bearers belonging to a user service and their inter-relation (layered, alternative, complementary), possible stream combinations - in case of alternative streams -, etc.
  • a further design possibility may be forwarding information on the state of dropped and not dropped streams downstream.
  • the QoS profiles of the streams may be taken into account.
  • This information may be readily available from the MBMS Bearer Context present in the adaption node, which comprises the QoS profile for each established bearer. Alternatively, it may also be considered to signal this information within the service semantics and to store them in the user service context.
  • the radio access network may be considered the bottleneck in the 3GPP architecture and the core network may be considered over-provisioned.
  • filter entities i.e. "adaptation nodes”
  • the RNCs have knowledge about the available resources in the own radio domain. This makes them adequate for this functionality.
  • any network entity in the RAN or CN may act as a filter entity. However, it may be feasible to select those entities as filtering entities that are aware of the resources on the links downstream towards the mobile terminal receiving the requested service.
  • the initialization of a filter at the adapting network entity may be triggered using control messages. Therefore, the service semantics may be signaled downstream to the corresponding RNC using the MBMS Procedures. Service semantics may be understood as to refer to information on the streams conveying the user service, their inter-relation, and their QoS profiles.
  • these pieces of information reflecting the service semantics are provided within optional fields of the specified MBMS signaling messages.
  • intermediate nodes such as GGSNs and SGSNs may not need to parse and process the values of the message extensions if they do not understand them. They may only forward them downstream.
  • the adaptive QoS concept outlined above enables the provision of services supporting different paradigms for encoding a given content, e.g. layered, alternative or complementary.
  • This is a novel approach for providing MBMS Services and, as such, it has not yet been reflected in the current architecture.
  • MBMS User Service Context for storing the service semantics (e.g. information on bearers belonging to a service, their inter-relation, their QoS profiles, etc.) is thus compatible with the current MBMS architecture.
  • a multicast or broadcast service such as an MBMS User Service
  • a multicast or broadcast service consists of a plurality of bearers which may be alternative, complementary or layered.
  • each bearer is associated to predetermined QoS constraints which need to be met in order to deliver the respective bearer to the UE.
  • the QoS parameters associated to a respective bearer describe not only the bit rate required for delivering the bearer to the UE but also its contents (e.g. guaranteed bitrate, maximum bitrate, maximum packet size, loss rate, etc. of the stream(s) carried by the bearer).
  • QoS relationships exist between the MBMS bearers (or group of bearers), e.g. alternative, complementary or layered relationships.
  • the QoS of the MBMS User Service is autonomously adapted in the 3G network as discussed above.
  • QoS decision points in the RAN or CN (“adaption nodes") select/drop parts of the MBMS bearers according to available resources in the downlink based on the quality of service constraints obtained from the quality of service management function implemented in the adaption nodes.
  • the UEs are not aware of this selection/dropping process in the RAN and/or CN and therefore assume to receive all bearers of a MBMS User Service as indicated in the MBMS User Service description. Consequently, the dropped bearers are would be considered an error case by a conventional UE.
  • the UEs are consequently not aware that they actually receive the service at one of the available QoS levels. Therefore UEs cannot receive the MBMS User Service correctly.
  • a MBMS User Service is assumed to contain two MBMS bearers, which represent service alternatives. I.e. each bearer will deliver the same content, but encoded in different quality levels (e.g. audio-visual streams encoded at two different bitrates). Furthermore there might be an associated post-delivery procedure configured for each bearer (e.g. content reception reporting). As the MBMS bearers represent service alternatives only one is indented to be delivered to the UE.
  • the UE receives the MBMS User Service description, which includes descriptions for both MBMS bearers. According to normal behavior it requests both MBMS bearers.
  • the problem is that the UE is not aware that the MBMS bearers are alternatives and that it is only required to reserve resources for one of them. Therefore it must reserve resources for both bearers (e.g. streaming buffers), which leads to waste of resources in the UE (e.g. memory space). Additionally the UE may start the post delivery procedures for both bearers. However the network is only interested in receiving the post delivery procedures for the service (bearer), which was actually delivered to the UE. This leads to waste of network resources.
  • the key aspect of an embodiment of the invention is the introduction of a new grouping description as an extension of the standard MBMS User Service description.
  • the MBMS User Service description is based on XML.
  • a new element describes the grouping relations between the individual MBMS bearers, which are contained in the MBMS User Service.
  • the UEs are aware of MBMS bearer grouping and they know that not all groups of bearers might be received. Hence, the UEs are prepared to receive only a subset of all MBMS bearers. Therefore not receiving a MBMS bearer is not instantly considered an error case. On the other hand the UEs can determine if a complete group is received, which enables the UEs to realize if the MBMS User Service was received correctly.
  • the userSezviceDescription is the top-level element comprising all MBMS User Service description information.
  • the deliveryMethod element collects all information concerning a specific MBMS bearer of the MBMS User Service. All information describing the details of the MBMS bearer is contained in other dedicated metadata descriptions (also refereed to as media and session descriptions). Those are referenced by their unique URI in the deliveryMethod element.
  • each of the MBMS bearers listed in the deliveryMethod elements (by means of their associated URIs/ media or session descriptions) has a TMGI (Temporary Multicast Group Identifier) associated to the respective bearer. Concerning transport and media encoding parameters these information is contained in a separate SDP description, which is specified in the sessionDescriptionURI attribute of the deliveryMethod element.
  • the UE may associate the each URI in the MBMS User Service description with the TMGI of the bearer providing the content data described in the referenced service description.
  • the TMGIs of the bearers for which a MBMS notification is received at the UE allows the UE to determine whether the bearers identified by their TMGIs form a "valid" bearer combination, as will be described below. It should be noted that for MBMS services in multicast mode the referenced service descriptions may not indicate the bearers' TMGIs.
  • qosGroup element contains one or more qosGroupItem elements.
  • the qosGroup element is defined on the same level as the deliveryMethod element.
  • the qosGroupItems in a qosGroup define a group of MBMS bearers.
  • the same URI as used in the sessionDescriptionURI attribute of the deliveryMethod element uniquely identifies the individual MBMS bearer.
  • the TMGIs comprised within notification information received by the UE may be used to determine, whether a bearer group according to the definitions in the MBMS User Service description is provided by the network.
  • This extension may be used to support the description MBMS bearer group relationships.
  • a qosRelation element which is defined on the same level as the deliveryMethod element describes the general relationships between the bearer groups. Those groups can represent discrete alternatives, i.e. one of them is exclusively chosen, or depend on each other, e.g. represent layers of the same media. This is expressed in the discrete attribute of the qosRelation element.
  • a child-element of the qosRelation is the qosGroup element, which specifies the MBMS bearers belonging to a distinct group, like described in the exemplary XML definition above.
  • the extension proposed in this embodiment is the qosPrio attribute of the qosGroup element, which is needed to express the order of the defined bearer groups.
  • the exact meaning of this order depends on the qosRealtion tion element. Either it specifies the order of alternatives, e.g. best to worst alternative, or it specifies the order of the dependent groups, e.g. base layer and enhancement layer.
  • a MBMS User Service description may be defined as a collection of metadata, which describes the service delivered to the UEs. All necessary parameters to receive the service are contained in this description.
  • the MBMS bearers, which transmit the service content, are described by individual SDP descriptions. Those are referenced in the MBMS User Service description in a deliveryMethod element via a URI. Therefore each deliveryMethod element represents a separate MBMS bearer contained in the MBMS User Service.
  • the URI referencing the SDP description uniquely identifies this MBMS bearer.
  • a new element in the MBMS User Service description which is called qosGroup , groups the related MBMS bearers together.
  • Each MBMS bearer contained in such a qosGroup element belongs to the same group of bearers. Those are specified in a new qosGroupItem element, which is a child element of a qosGroup .
  • the URI of the SDP description of each MBMS bearer is used as bearer identifier.
  • the MBMS User Service consists of four MBMS bearers. Additionally two groups are specified by two qosGroup elements. In this example each group contains two of the MBMS bearers, which is expressed by the two qosGroupItem elements containing the URI of the SDP description of he respective bearer.
  • the UEs receiving a MBMS User Service delivering layered, complementary or alternative layers know the grouping relations between the individual MBMS bearers and are aware that an autonomous QoS adaptation might be performed in the network. Therefore the UEs are prepared to receive only a subset of all MBMS bearer contained in the MBMS User Service description. They can determine if a group is received completely, which enables the UEs to correctly receive the MBMS User Service.
  • the exemplary XML schemes above do not only resolve the problem of identifying MBMS bearers belonging to a certain group, but they may also define how these groups are interrelated (e.g. represent alternatives or layers).
  • the second XML schema proposed above introduces the description of the group inter-relationships. This is achieved by a new qosRelation element and an extension of the qosGroup element.
  • the qosRelation element specifies the general group relations, i.e. if the groups either represent separate media alternatives or belong to different layers of the same media.
  • the qosPrio attribute of the qosGroup element specifies the group hierarchy. This is either the order of the alternatives (e.g. best to worst alternative) or the order of the layers (e.g. base and enhancement layer), depending on the qosRelation element.
  • the qosRelation element in the example above shows that the described groups are to be treated discrete, i.e. represent service alternatives.
  • the qosPrio attribute shows that the first described group is the preferred one.
  • the UE will receive a MBMS notification message for each bearer that has been selected by its RNC for providing the content data of the respective bearers as defined in the metadata descriptions referenced in the MBMS User Service description.
  • the UE is aware of the TMGIs of the bearers providing the service, as - for example - same have been received in MBMS notification message(s) via a paging channel. Comparing the received TMGIs of the notification(s) with those defined by the respective descriptions referenced in the qosGroupItem elements of the respective qosGroup elements of the MBMS User Service description, the UE recognizes whether all bearers necessary to receive the service in a predetermined (bearer) configuration have been received.
  • the UE may receive the content data provided on the bearer(s) and may provide the content to the user of the U.E, for example by displaying the received video data, replaying a received audio signal; etc.
  • the UE may follow different strategies to cope with the situation. For example, the UE may indicate to the user that the service may not be provided, i.e. an error message may be triggered. Alternatively, the UE may await the reception of further notifications which possibly "complete" the set of indicated MBMS bearers of the MBMS User Service, such that the indicated bearers correspond to a bearer combination indicated in the MBMS User Service description. A timer may for example be used to ensure that a "valid" bearer combination is indicated to the UE within a predetermined time period. Upon expiry of the timer, the UE may decide to trigger an error message.
  • an exemplary operation of an MBMS multicast service in accordance with an exemplary embodiment of the invention will be outlined with reference to Fig. 5 .
  • the provision of an MBMS broadcast service is similar, except for not requiring the execution of the subscription, joining and leaving procedures as briefly outlined below.
  • a service provider which allows the user to receive the related MBMS multicast service is established.
  • the so-called Service Subscription is the agreement of a user to receive a service offered by service provider.
  • the service provider records the subscription information in the appropriate database in the network operator's network. (In UMTS a service provider may be a 3 rd party, but MBMS is controlled by the network operator.)
  • the next step is the MBMS user service announcement/discovery mechanism 401.
  • This mechanism allows users to request or to be informed about the range of MBMS user services available.
  • the available service may be for example operator specific MBMS user services as well as services from content providers outside of the PLMN.
  • the service announcement is used to distribute to users information about the service, parameters required for service activation (e.g. IP multicast address) and possibly other service related parameters (e.g. service start time). Commonly, this information is provided 502 in form of an Extended MBMS User Service description according to the embodiments of the invention described above.
  • MBMS User Services may account for the user' s location.
  • CBS Cell Broadcast Service
  • MBMS Broadcast mode to advertise MBMS Multicast and Broadcast user Services
  • MBMS Multicast mode to advertise MBMS Multicast user Services
  • PUSH mechanisms such as WAP, SMS-PP or MMS
  • URL e.g. via HTTP, FTP
  • MBMS user service announcement mechanisms may be used for MBMS user service announcement mechanisms.
  • MBMS activation 503 by a user is performed.
  • a subscriber joins a multicast group, i.e. the user indicates 403 to the network that he/she is willing to receive multicast mode data of a specific MBMS bearer service.
  • the MBMS multicast service activation procedure registers the user in the network to enable the reception of data from a specific multicast MBMS bearer service.
  • the activation is a signaling procedure between the UE and the network.
  • the procedure may establish MBMS UE contexts in UE, SGSN and GGSN and RNC for each activated multicast MBMS bearer service.
  • the UE may for example indicate the IP multicast addresses of the MBMS bearers (bearer services) of a MBMS User Service it desires to receive to the BM-SC.
  • the UE is provided with the TMGIs of the indicated MBMS bearers.
  • the IP multicast addresses of the bearer services in their media or session description may be used to establish a mapping between the bearer inter-relationships and their grouping to the TMGIs of the bearers.
  • the MBMS Registration is the procedure by which a downstream node informs an upstream node that it would like to receive session attributes and data for a particular MBMS bearer service in order to distribute it further downstream.
  • This procedure builds up a distribution tree for the delivery of MBMS session attributes and data from the BM-SC to the UEs interested in the service and establishes the MBMS Bearer Context in the network nodes in the distribution tree.
  • a MBMS Bearer Context is established 504 in the network nodes.
  • the MBMS Bearer Context comprises inter alia the QoS required for the respective MBMS bearer service as well as the minimum bearer capabilities the UE has to support.
  • the network nodes are not aware of the bearers belonging to a single MBMS User Service or of their relationship.
  • the MBMS Registration procedures may be adapted to establish 504 a MBMS User Service Context described below in the network nodes along the distribution tree which provides the networks nodes with information on the inter-relation of the MBMS bearer services.
  • the MBMS User Service Context which is also established in the RNC serving a UE requesting the MBMS service reflects the session semantics, i.e., it provides information about the bearer relations and describes additional bearer properties.
  • the following tables illustrate the content of this context according to an exemplary embodiment of the invention.
  • Table 1 - MBMS User Service Context Parameter Description/Value MBMS User Service ID Identifier of the MBMS User Service.
  • the MBMS User Service ID identifies for example the different IP multicast addresses of streams belonging to the service.
  • Each bearers information element may comprise different fields dependent on the bearers' interrelation. For each exemplified type (layered, alternative and, complementary) the information element will be described below. Table 2. 1 - Bearer IE for Layered Bearers Type of Bearers Type of relation between the bearers (e.g. layered, alternative, complementary, or void) to the other bearers in the MBMS service. If "void" the service consists of just one bearer. Bearer List This is a list containing Bearer List Elements (LEs) describing each a bearer of the type specified in the above field.
  • Bearer List This is a list containing Bearer List Elements (LEs) describing each a bearer of the type specified in the above field.
  • MBMS Bearer ID Identifier of the MBMS Bearer, for example the IP Multicast Address for identifying the MBMS Bearer context. Identifiers other than an IP Multicast Address may be used.
  • Forwarding State List containing the Forwarding State of the stream in this MBMS Bearer (e.g. "forward" or "drop") for each downstream node.
  • a network node may have several downstream nodes (e.g. several RNCs attached to an SGSN) to which the stream may or may not be forwarded. For each of the downstream node interfaces, the forwarding state of this stream/bearer is specified in this list.
  • Priority The priority of the MBMS Bearer.
  • Bearer List This is an array containing Bearer List Elements (LEs) each describing a bearer of the type specified in the above field.
  • Default Bearer Combination This field identifies the default bearer or combination of bearers for the MBMS User Service.
  • Alternative Bearer Combinations This field identifies which combinations (using the bearer identifiers) of bearers are reasonable alternatives to the default option above.
  • the alternative bearer combinations may define, e.g. lower bandwidth bearer combinations. Other combinations may, e.g.
  • MBMS Bearer ID identifier of the MBMS Bearer, for example the IP Multicast Address for identifying the MBMS Bearer context. Other identifiers are possible.
  • Forwarding State List containing the Forwarding State of the stream in this MBMS Bearer (e.g. "forward" or "drop") for each downstream node.
  • a network node may have several downstream nodes (e.g. several RNCs attached to an SGSN) to which the stream may or may not be forwarded.
  • Bearer List This is an array containing Bearer List Elements (LEs) describing each a bearer of the type specified in the above field.
  • Forwarding State List containing the Forwarding State of the stream in this MBMS Bearer (e.g. "forward” or "drop") for each downstream node.
  • a network node may have several downstream nodes (e.g. several RNCs attached to an SGSN) to which the stream may or may not be forwarded. For each of the downstream node interfaces, the forwarding state of this stream is specified in this list.
  • the RNC When maintaining the MBMS User Service Context above, the RNC is aware of the different combinations of bearers that are possible to provide the MBMS User Service as well as of their required QoS (MBMS Bearer Context).
  • the BM-SC is ready to send data - session start.
  • the session start may occur independently of the activation of the service by the user.
  • the session start procedure triggers the reservation of bearer resources for MBMS data transfer in the network.
  • the BM-SC proceeds with transmitting 509 the service content downstream.
  • MBMS session attributes such as QoS, estimated session duration if available are provided to the GGSN(s) and SGSN(s) that have previously registered for the corresponding MBMS bearer service and to all RNCs that are connected to a registered SGSN.
  • the RNC serving the UE requesting the MBMS User Service may request 506 the resources available on its interface towards the UE from its quality of service management function. This function provides the RNC with the QoS constraints on the downstream towards the UE for service provision. Based on the information obtained from the quality of service management function and its knowledge of the bearer relations (MBMS User Service Context) and their respective QoS requirements (MBMS Bearer Context), the RNC may select 507 a MBMS bearer combination which may be provide the requested MBMS User Service to the UE within the QoS constraints obtained from the quality of service management function. The RNC may thereby obtain the QoS constraints on all interfaces through which UEs have previously requested the service and may select for each of the interfaces (cells) an bearer combination that satisfies the respective QoS constraints.
  • MBMS User Service Context bearer relations
  • MBMS Bearer Context MBMS Bearer Context
  • the RNC may broadcast 508 MBMS notifications for the selected MBMS bearers to inform the UEs having requested the service on forthcoming (and potentially about ongoing) transmission of the respectively selected MBMS bearers. If not yet beeing transmitted, the RNC may start the multicast of content data on the selected MBMS bearers of the MBMS User Service.
  • a UE having announced its interest in a MBMS service will receive the MBMS notifications for the selected bearers in its cell and will start content data reception 510 from the selected bearers. Due to being informed on the bearer inter-relations by means of the MBMS User Service description, the UE may recognize whether "valid" bearer combination is provided, as explained above.
  • the BM-SC Broadcast/Multicast-Service Center
  • the session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network.
  • the procedure is propagated to all SGSNs and GGSNs that are registered for the corresponding MBMS bearer service and to RNCs that have an established lu bearer plane with an SGSN.
  • This MBMS multicast deactivation by the user is the process by which a subscriber leaves (stops being a member of) a multicast group, i.e. the user no longer wants to receive Multicast mode data of a specific MBMS bearer service.
  • Another embodiment of the present invention relates to the implementation of the above described various embodiments using hardware and software. It is recognized that the various above mentioned methods as well as the various logical blocks, modules, circuits described above may be implemented or performed using computing devices, as for example general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, etc. The various embodiments of the present invention may also be performed or embodied by a combination of these devices.
  • DSP digital signal processors
  • ASIC application specific integrated circuits
  • FPGA field programmable gate arrays
  • the various embodiments of the present invention may also be implemented by means of software modules which are executed by a processor or directly in hardware. Also a combination of software modules and a hardware implementation may be possible.
  • the software modules may be stored on any kind of computer readable storage media, for example RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROM, DVD, etc.

Claims (9)

  1. Procédé destiné à fournir un service de multidiffusion ou de diffusion à l'utilisateur d'un terminal mobile (UE) à travers un réseau d'accès radio d'un système de communication mobile, dans lequel le service de multidiffusion ou de diffusion est associé à une pluralité de porteuses afin de fournir le service de multidiffusion ou de diffusion, le procédé comprenant les étapes suivantes exécutées par le terminal mobile et qui consistent à:
    recevoir une information (502) de description de service pour le service de multidiffusion ou de diffusion depuis un centre de service de multidiffusion/diffusion (BM-SC), où la information de description de service indique la pluralité de porteuses (bearers) du service de multidiffusion ou de diffusion et
    où la information de description de service indique en plus des combinaisons prédéterminées des porteuses parmi la pluralité de porteuses, chaque combinaison prédéterminée des porteuses comprenant au moins l'une de ladite pluralité de porteuses et chaque combinaison prédéterminée des porteuses fournissant le service de multidiffusion ou de diffusion à une qualité prédéterminée de paramètres de service,
    activer l'ensemble de la pluralité de porteuses (403) du service de multidiffusion ou de diffusion,
    recevoir, pour chaque porteuse comprise dans une combinaison prédéterminée des porteuses sélectionnée parmi les combinaisons des porteuses, une notification (508) respective de service depuis l'unité de commande du réseau radio en réponse à l'activation de l'ensemble de la pluralité de porteuses du service de multidiffusion ou de diffusion,
    où la notification de service ou les notifications de service reçue(s) informent le terminal mobile de l'établissement de la porteuse ou des porteuses de la combinaison prédéterminée sélectionnée des porteuses destinée(s) à de fournir des données de contenu du service de multidiffusion ou de diffusion à travers l'interface radio du réseau d'accès radio, et
    recevoir des données de contenu du service (510) de multidiffusion ou de diffusion à travers ladite au moins une porteuse établie appartenant à la combinaison prédéterminée sélectionnée des porteuses et indiquée par la au moins une notification de service.
  2. Procédé selon la revendication 1, dans lequel le service de multidiffusion ou de diffusion est un Service Utilisateur MBMS fourni via un réseau UMTS.
  3. Procédé selon la revendication 1 ou 2, dans lequel une notification respective de service indique en plus des paramètres requis pour recevoir la au moins une porteuse par le terminal mobile.
  4. Procédé selon l'une des revendications 1 à 3, dans lequel un langage de balisage (mark up language) est utilisé pour décrire le contenu de la information de description de service.
  5. Procédé selon la revendication 4, dans lequel la information de description de service comprenne des étiquettes définissant lesdites combinaisons prédéterminées des porteuses.
  6. Terminal mobile (UE) destiné à fournir un service de multidiffusion ou de diffusion à un utilisateur, le service de multidiffusion ou de diffusion étant transmis à travers un réseau d'accès radio d'un système de communication mobile, où le service de multidiffusion ou de diffusion est associé à une pluralité de porteuses (bearers) afin de fournir le service de multidiffusion ou de diffusion, le terminal mobile comprenant:
    un récepteur destiné à recevoir une information (502) de description de service pour le service de multidiffusion ou de diffusion, où la information de description de service indique la pluralité de porteuses du service de multidiffusion ou de diffusion et
    où la information de description de service indique en plus des combinaisons prédéterminées des porteuses parmi la pluralité de porteuses, chaque combinaison prédéterminée des porteuses comprenant au moins une de ladite pluralité de porteuses et chaque combinaison prédéterminée des porteuses fournissant le service de multidiffusion ou de diffusion à une qualité prédéterminée de paramètres de service,
    un émetteur destiné à activer l'ensemble de la pluralité de porteuses (403) du service de multidiffusion ou de diffusion,
    le récepteur étant adapté pour recevoir, pour chaque porteuse comprise dans une combinaison prédéterminée sélectionnée des porteuses parmi les combinaisons des porteuses, une notification (508) respective de service depuis l'unité de commande du réseau radio en réponse à l'activation de l'ensemble de la pluralité de porteuses.
    où la notification de service ou les notifications de service reçue(s) informent le terminal mobile de l'établissement de la porteuse ou des porteuses de la combinaison prédéterminée sélectionnée des porteuses destinée(s) à fournir des données de contenu du service de multidiffusion ou de diffusion à travers l'interface radio du réseau d'accès radio, et
    où le récepteur est adapté pour recevoir des données de contenu du service (510) de multidiffusion ou de diffusion à travers ladite au moins une porteuse indiquée dans la au moins une notification de service, et
    le terminal mobile est adapté pour fournir des données de contenu à l'utilisateur du terminal mobile.
  7. Terminal mobile selon la revendication 6, comprenant en plus un moyen adapté pour exécuter les étapes du procédé selon l'une des revendications 2 à 5.
  8. Support lisible par ordinateur, stockant des instructions, qui, lorsqu'elles sont exécutées par un processeur d'un terminal mobile (UE), provoquent la fourniture d'un service de multidiffusion ou de diffusion à l'utilisateur du terminal mobile à travers un réseau d'accès radio d'un système de communication mobile, le service de multidiffusion ou de diffusion étant associé à une pluralité de porteuses (bearers) afin de fournir le service de multidiffusion
    ou de diffusion, en :
    recevant une information (502) de description de service pour le service de multidiffusion ou de diffusion, où la information de description de service indique la pluralité de porteuses du service de multidiffusion ou de diffusion et
    où la information de description de service indique en plus des combinaisons prédéterminées des porteuses parmi la pluralité de porteuses, chaque combinaison prédéterminée des porteuses comprenant au moins une de ladite pluralité de porteuses et chaque combinaison prédéterminée des porteuses fournissant le service de multidiffusion ou de diffusion à une qualité prédéterminée de paramètres de service,
    activant l'ensemble de la pluralité de porteuses (403) du service de multidiffusion ou de diffusion,
    recevant, pour chaque porteuse comprise dans une combinaison prédéterminée des porteuses sélectionnée parmi les combinaisons de porteuses, une notification (508) respective de service depuis l'unité de commande du réseau radio en réponse à l'activation de l'ensemble de la pluralité de porteuses,
    où la notification de service ou les notifications de service reçue(s) informent le terminal mobile de l'établissement de la porteuse ou des porteuses de la combinaison prédéterminée sélectionnée des porteuses destinée(s) à fournir des données de contenu du service de multidiffusion ou de diffusion à travers l'interface radio du réseau d'accès radio, et
    recevant des données de contenu du service (510) de multidiffusion ou de diffusion à travers ladite au moins une porteuse indiquée dans la information de notification de service.
  9. Support lisible par ordinateur selon la revendication 8, stockant en plus des instructions, qui, lorsqu'elles sont exécutées par le processeur du terminal mobile, amènent le terminal mobile à exécuter les étapes du procédé selon l'une des revendications 2 à 5.
EP08001745A 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralitée de porteuses Not-in-force EP1915021B1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
DE602005016735T DE602005016735D1 (de) 2005-02-16 2005-02-16 Unterstützung mobiler Endgeräte in einem Multicast- oder Broadcastdienst mit mehreren Trägern
AT09164581T ATE505914T1 (de) 2005-02-16 2005-02-16 Unterstützung mobiler endgeräte in einem multicast- oder rundfunkdienst mit mehreren trägern
EP09164581A EP2101521B1 (fr) 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralité de porteurs

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP05003303A EP1694086B1 (fr) 2005-02-16 2005-02-16 Fourniture d'informations concernant les relations entre les porteuses individuelles à des terminaux mobiles recevant un service de diffusion ou multidiffusion

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
EP05003303A Division EP1694086B1 (fr) 2005-02-16 2005-02-16 Fourniture d'informations concernant les relations entre les porteuses individuelles à des terminaux mobiles recevant un service de diffusion ou multidiffusion

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP09164581A Division EP2101521B1 (fr) 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralité de porteurs

Publications (2)

Publication Number Publication Date
EP1915021A1 EP1915021A1 (fr) 2008-04-23
EP1915021B1 true EP1915021B1 (fr) 2009-09-16

Family

ID=34933780

Family Applications (3)

Application Number Title Priority Date Filing Date
EP08001745A Not-in-force EP1915021B1 (fr) 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralitée de porteuses
EP05003303A Not-in-force EP1694086B1 (fr) 2005-02-16 2005-02-16 Fourniture d'informations concernant les relations entre les porteuses individuelles à des terminaux mobiles recevant un service de diffusion ou multidiffusion
EP09164581A Active EP2101521B1 (fr) 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralité de porteurs

Family Applications After (2)

Application Number Title Priority Date Filing Date
EP05003303A Not-in-force EP1694086B1 (fr) 2005-02-16 2005-02-16 Fourniture d'informations concernant les relations entre les porteuses individuelles à des terminaux mobiles recevant un service de diffusion ou multidiffusion
EP09164581A Active EP2101521B1 (fr) 2005-02-16 2005-02-16 Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralité de porteurs

Country Status (7)

Country Link
US (2) US7801480B2 (fr)
EP (3) EP1915021B1 (fr)
JP (3) JP4774060B2 (fr)
CN (2) CN101120611B (fr)
AT (3) ATE505914T1 (fr)
DE (3) DE602005016735D1 (fr)
WO (1) WO2006087067A1 (fr)

Families Citing this family (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7912457B2 (en) * 2004-04-21 2011-03-22 Qualcomm Incorporated Methods and apparatus for creation and transport of multimedia content flows
ATE519344T1 (de) * 2004-06-21 2011-08-15 Panasonic Corp Adaptive und skalierbare dienstqualitätsarchitektur für einzelträger- multicast/broadcast-dienste
US8544043B2 (en) * 2004-07-21 2013-09-24 Qualcomm Incorporated Methods and apparatus for providing content information to content servers
KR100934088B1 (ko) * 2004-12-09 2009-12-24 콸콤 인코포레이티드 멀티미디어 컨텐트 플로우들을 생성하고 분산 네트워크로 전달하기 위한 방법 및 장치
US8560651B2 (en) * 2006-03-07 2013-10-15 Cisco Technology, Inc. Method and system for streaming user-customized information
US8612619B2 (en) * 2006-03-31 2013-12-17 Alcatel Lucent Method and apparatus for improved multicast streaming in wireless networks
WO2008003882A2 (fr) * 2006-07-03 2008-01-10 France Telecom Procede de configuration d'un terminal multi reseaux et terminal multi-reseaux associe
RU2432684C2 (ru) * 2006-07-24 2011-10-27 Эл Джи Электроникс Инк. Двухточечные радиоканалы для службы радиовещания
US7925201B2 (en) * 2007-04-13 2011-04-12 Wideorbit, Inc. Sharing media content among families of broadcast stations
CN101325500B (zh) 2007-06-13 2012-12-12 华为技术有限公司 一种组播承载资源的控制方法及系统
CN102318232B (zh) * 2007-06-15 2014-12-10 Lg电子株式会社 用于通过单频网络模式的点对多点业务的网络信令
US8874721B1 (en) * 2007-06-27 2014-10-28 Sprint Communications Company L.P. Service layer selection and display in a service network monitoring system
US8625501B2 (en) 2007-09-24 2014-01-07 Qualcomm Incorporated Regulating broadcast overhead messages within a wireless communications network
US8630219B2 (en) 2007-09-24 2014-01-14 Qualcomm Incorporated Supporting a multicast session within a wireless communications network
WO2009049665A1 (fr) * 2007-10-15 2009-04-23 Ericsson Hungary Ltd Procédé et appareil à utiliser dans un réseau
GB2455545B (en) * 2007-12-13 2010-01-27 Nec Corp MBMS bearer establishment reconfiguration and release
JP2011507385A (ja) * 2007-12-13 2011-03-03 ポスコ アイシーティー カンパニー リミテッド マルチキャスト及びブロードキャストのためのシステム並びに方法
WO2009106126A1 (fr) * 2008-02-25 2009-09-03 Nokia Siemens Networks Oy Appareil et procédé concernant des adresses de multidiffusion ou des adresses source autorisées et non autorisées
US8599765B2 (en) * 2008-03-21 2013-12-03 Blackberry Limited Evolved packet system quality of service enforcement deactivation handling to prevent unexpected user equipment detach
CN101800938A (zh) * 2009-02-05 2010-08-11 华为技术有限公司 为mbms承载业务建立无线承载的方法、装置和系统
CN101483833B (zh) * 2009-02-06 2011-06-22 中兴通讯股份有限公司 接收紧急广播消息的方法及装置
CN102301811B (zh) * 2009-04-28 2014-02-12 上海贝尔股份有限公司 对用于mbsfn传输的无线资源进行动态调度的方法、mce和基站
WO2010132700A1 (fr) * 2009-05-13 2010-11-18 Nortel Networks Limited Suspension et reprise de session à l'aide d'une messagerie à option de liaison temporaire
US20110141963A1 (en) * 2009-12-16 2011-06-16 Electronics And Telecommunications Research Institute Method for supporting broadcast services in multicast broadcast service frequency network
US8626234B2 (en) * 2009-12-17 2014-01-07 Alcatel Lucent Method and apparatus for providing layered wireless networks
US9125174B2 (en) * 2010-03-25 2015-09-01 Htc Corporation Apparatuses and methods for selectively receiving multimedia broadcast/multicast service in a wireless communications system
US9930536B2 (en) 2010-07-15 2018-03-27 Rivada Networks, Llc. Methods and systems for dynamic spectrum arbitrage
US8711721B2 (en) 2010-07-15 2014-04-29 Rivada Networks Llc Methods and systems for dynamic spectrum arbitrage
US20130279394A1 (en) * 2010-11-08 2013-10-24 Sharp Kabushiki Kaisha Mobile communication system, mobile station device, base station device, sgsn, ggsn, mme, mbms gw and mobile communication method
US9042291B2 (en) 2010-12-29 2015-05-26 Motorola Solutions, Inc. Methods for assigning a plethora of group communications among a limited number of pre-established MBMS bearers in a communication system
US8861419B2 (en) * 2010-12-29 2014-10-14 Motorola Solutions, Inc. Methods for binding and unbinding a MBMS bearer to a communication group in a 3GPP compliant system
US9392576B2 (en) 2010-12-29 2016-07-12 Motorola Solutions, Inc. Methods for tranporting a plurality of media streams over a shared MBMS bearer in a 3GPP compliant communication system
CN103477679B (zh) 2011-02-15 2017-11-21 三星电子株式会社 用户设备优先级的功率余量报告方法和装置
CN102647665B (zh) * 2011-02-21 2015-02-04 华为技术有限公司 群组消息处理方法、设备及系统
US8996686B2 (en) * 2011-03-18 2015-03-31 Novell, Inc. Content delivery validation service
KR101948801B1 (ko) * 2011-04-11 2019-02-18 삼성전자주식회사 Ｍｂｍｓ 지원 사용자 장치의 데이터 수신 방법 및 장치
KR101929307B1 (ko) 2011-04-11 2018-12-17 삼성전자 주식회사 Ｃｓｇ 셀에서 단말이 셀 재선택 우선 순위를 효율적으로 제어하는 방법 및 장치
KR20120115953A (ko) 2011-04-11 2012-10-19 삼성전자주식회사 단말 획득 정보를 효율적으로 기지국에 전달하는 방법 및 장치
EP2706677B1 (fr) 2011-05-03 2016-08-10 Samsung Electronics Co., Ltd. Procédé et appareil pour qu'un équipement d'utilisateur recevant un service mbms traite une programmation semi-permanente de sous-trame mbsfn dans un système de communication sans fil
KR101990134B1 (ko) 2011-08-10 2019-06-17 삼성전자주식회사 듀얼 모드 단말의 성능 정보 보고 방법 및 장치
KR101935785B1 (ko) 2011-08-16 2019-04-03 삼성전자 주식회사 무선통신시스템에서 멀티미디어 방송 서비스를 수신하는 방법 및 장치
US8934423B2 (en) 2011-09-13 2015-01-13 Motorola Solutions, Inc. Methods for managing at least one broadcast/multicast service bearer
EP2761898A4 (fr) * 2011-09-30 2015-03-18 Sierra Wireless Inc Attribution dynamique d'identificateurs de message de diffusion cellulaire
US8867388B2 (en) 2011-11-19 2014-10-21 Motorola Solutions, Inc. Distributing content to a plurality of mobile stations using a downlink point-to-multipoint (PTM) bearers and downlink point-to-point (PTP) bearers
US8953478B2 (en) * 2012-01-27 2015-02-10 Intel Corporation Evolved node B and method for coherent coordinated multipoint transmission with per CSI-RS feedback
WO2013112021A1 (fr) 2012-01-27 2013-08-01 삼성전자 주식회사 Procédé et appareil d'émission et de réception de données au moyen de plusieurs porteuses dans des systèmes de communications mobiles
US9001737B2 (en) * 2012-03-29 2015-04-07 Qualcomm Incorporated EMBMS service activation and maintenance procedure in multi-frequency networks
US8811258B2 (en) * 2012-04-13 2014-08-19 Intel Corporation Enhanced local communications in mobile broadband networks
EP2862374B1 (fr) * 2012-06-14 2019-11-06 Sierra Wireless, Inc. Procédé et système pour des communications sans fil avec des dispositifs de machine à machine
US9445302B2 (en) 2012-06-14 2016-09-13 Sierra Wireless, Inc. Method and system for wireless communication with machine-to-machine devices
US9369976B2 (en) * 2012-06-27 2016-06-14 Qualcomm Incorporated Supporting coordinated universal time in LTE
CN103546826B (zh) * 2012-07-16 2017-07-21 上海贝尔股份有限公司 视频业务的传输方法和装置
CN104813616B (zh) * 2012-08-28 2019-02-15 塔塔咨询服务有限公司 发布数据的可靠性的动态选择的系统及方法
CN104620590B (zh) * 2012-09-20 2018-08-10 索尼公司 接收装置、发送/接收系统、接收方法
US8929270B2 (en) * 2012-10-29 2015-01-06 Qualcomm Incorporated Coordinated transmission rate and channel scheduling for wireless multicast and broadcast
US10182330B2 (en) * 2012-11-13 2019-01-15 Qualcomm, Incorporated Emergency alert using MBMS and cell broadcasting
US8867425B2 (en) 2012-12-21 2014-10-21 Motorola Solutions, Inc. Method and apparatus multimedia broadcast/multicast service coverage boost
US9042223B2 (en) 2012-12-21 2015-05-26 Motorola Solutions, Inc. Method and apparatus for multimedia broadcast multicast service
US9820134B2 (en) * 2013-01-25 2017-11-14 Koninklijke Kpn N.V. Proximity discovery, authentication and link establishment between mobile devices in 3GPP LTE
US9167479B2 (en) 2013-03-15 2015-10-20 Motorola Solutions, Inc. Method and apparatus for queued admissions control in a wireless communication system
US9781181B2 (en) * 2013-06-17 2017-10-03 Qualcomm Incorporated Multiple file delivery over unidirectional transport protocol sessions for a service
US9584985B2 (en) 2013-07-30 2017-02-28 Qualcomm Incorporated Managing a multimedia broadcast multicast service using an MBMS relay device
US9386067B2 (en) * 2013-12-30 2016-07-05 Sonic Ip, Inc. Systems and methods for playing adaptive bitrate streaming content by multicast
EP3113468B1 (fr) 2014-02-28 2020-04-08 Panasonic Intellectual Property Corporation of America Terminal de communication vocale, noeud intermédiaire, dispositif de traitement, procédé de connexion et programme
US9756098B2 (en) 2014-09-15 2017-09-05 Verizon Digital Media Services Inc. Multi-tenant over-the-top multicast
EP3001703A1 (fr) * 2014-09-29 2016-03-30 Alcatel Lucent Amélioration de la couverture de multidiffusion dans un réseau cellulaire
KR101740451B1 (ko) 2014-12-10 2017-05-26 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
US9832756B2 (en) * 2015-01-26 2017-11-28 Intel IP Corporation Mobile termination control techniques to support eMBMS
ES2935117T3 (es) * 2015-09-29 2023-03-01 Tlv Co Ltd Sistema de transmisión de datos, dispositivo de gestión, programa de transmisión de datos y método de transmisión de datos
EP3437347B1 (fr) * 2016-03-31 2022-02-09 Nokia Solutions and Networks Oy Appareils et procédés de gestion d'une distribution de services de diffusion/multidiffusion multimédia locale (mbms)
WO2017180049A1 (fr) * 2016-04-11 2017-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Procédés permettant de gérer une configuration de quasi co-localisation (qcl) pour des transmissions par multidiffusion
WO2018021812A1 (fr) * 2016-07-26 2018-02-01 엘지전자 주식회사 Procédé et dispositif pour recevoir des informations de commande de services mbms par le biais d'un faisceau
US11178536B2 (en) * 2019-02-15 2021-11-16 Samsung Electronics Co., Ltd. Method and system for notifying resource capability of user equipment

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI107220B (fi) * 1998-11-06 2001-06-15 Nokia Networks Oy Menetelmä kantajien ominaisuuksien hallitsemiseksi
DE60042461D1 (de) * 2000-12-22 2009-08-06 Nokia Corp Verfahren und system für den aufbau einer multimedia verbindung durch austausch der übertragungskapazitäten in einem ausserband-signalisierungskanal
KR100678181B1 (ko) * 2002-07-31 2007-02-01 삼성전자주식회사 이동통신 시스템에서 멀티미디어 방송 멀티 캐스트 서비스 데이터를 제공하는 장치 및 방법
KR100958519B1 (ko) * 2002-08-14 2010-05-17 엘지전자 주식회사 이동통신 시스템에서의 멀티미디어 서비스 수신 및 전송 방법
KR100827137B1 (ko) * 2002-08-16 2008-05-02 삼성전자주식회사 이동통신시스템에서의 멀티캐스트 멀티미디어 방송 서비스 제공 방법
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
EP1566013B1 (fr) 2002-11-29 2008-08-06 Telefonaktiebolaget L M Ericsson Saut entre groupes et zappage entre canaux pendant la transmission d'applications multidiffusions
KR100703380B1 (ko) * 2003-05-14 2007-04-03 삼성전자주식회사 멀티미디어 브로드캐스트/멀티캐스트 서비스를 지원하기 위한 제어정보 송수신 장치 및 방법
US20050064821A1 (en) * 2003-09-22 2005-03-24 Telefonaktiebolaget Lm Ericsson (Publ) Alternative service management
KR100651408B1 (ko) * 2004-03-30 2006-11-29 삼성전자주식회사 음성 모드와 데이터 모드간 대체를 이용한 화상전화안내방송 방법
ES2317039T3 (es) * 2004-07-27 2009-04-16 Telecom Italia S.P.A. Transmision de contenidos multimedia a una pluralidad de usuarios moviles.
US8792852B2 (en) * 2004-12-23 2014-07-29 Telefonaktiebolaget Lm Ericsson (Publ) Method for informing multiple mobile terminals of an emergency event

Also Published As

Publication number Publication date
US7899391B2 (en) 2011-03-01
JP2012105290A (ja) 2012-05-31
DE602005027504D1 (de) 2011-05-26
EP2101521B1 (fr) 2011-04-13
ATE443413T1 (de) 2009-10-15
JP4914912B2 (ja) 2012-04-11
CN101120611A (zh) 2008-02-06
US20100302988A1 (en) 2010-12-02
US7801480B2 (en) 2010-09-21
WO2006087067A1 (fr) 2006-08-24
DE602005016735D1 (de) 2009-10-29
ATE505914T1 (de) 2011-04-15
CN102075870A (zh) 2011-05-25
CN101120611B (zh) 2011-05-18
EP1694086B1 (fr) 2008-04-16
JP4774060B2 (ja) 2011-09-14
EP1915021A1 (fr) 2008-04-23
JP2008530921A (ja) 2008-08-07
EP2101521A1 (fr) 2009-09-16
JP2010081625A (ja) 2010-04-08
JP5244957B2 (ja) 2013-07-24
US20080102749A1 (en) 2008-05-01
DE602005006095T2 (de) 2009-07-09
EP1694086A1 (fr) 2006-08-23
DE602005006095D1 (de) 2008-05-29
CN102075870B (zh) 2013-10-16
ATE392788T1 (de) 2008-05-15

Similar Documents

Publication Publication Date Title
EP1915021B1 (fr) Support de terminaux mobiles dans un service de multidiffusion ou de diffusion comprenant une pluralitée de porteuses
EP1610502B1 (fr) Architecture de qualité de service adaptative et échelonnable pour services de multidiffusion/radiodiffusion à support unique
US7957738B2 (en) Adaptive and scalable QoS architecture for multi-bearer multicast/broadcast services
EP1760933B1 (fr) Régulation par rétroaction pour des services multicast et broadcast
US20090213775A1 (en) Deterministic feedback control for multicast or broadcast services
CN101911737A (zh) 在通信网络中的多重多媒体数据流递送

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

AC Divisional application: reference to earlier application

Ref document number: 1694086

Country of ref document: EP

Kind code of ref document: P

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

17P Request for examination filed

Effective date: 20080711

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

Owner name: PANASONIC CORPORATION

AKX Designation fees paid

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/06 20090101AFI20090107BHEP

Ipc: H04L 12/18 20060101ALI20090107BHEP

RTI1 Title (correction)

Free format text: SUPPORT OF MOBILE TERMINALS IN A MULTICAST OR BROADCAST SERVICE COMPRISING A PLURALITY OF BEARERS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AC Divisional application: reference to earlier application

Ref document number: 1694086

Country of ref document: EP

Kind code of ref document: P

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: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602005016735

Country of ref document: DE

Date of ref document: 20091029

Kind code of ref document: P

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

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: 20090916

Ref country code: SE

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: 20090916

Ref country code: FI

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: 20090916

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20090916

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

Ref country code: NL

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: 20090916

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: 20090916

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: 20090916

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
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: 20090916

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

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: 20090916

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: 20090916

Ref country code: ES

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: 20091227

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: 20100116

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: 20100118

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: 20090916

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: 20090916

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: 20090916

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: 20090916

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

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

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: 20090916

26N No opposition filed

Effective date: 20100617

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: MC

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

Effective date: 20100301

Ref country code: LI

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

Effective date: 20100228

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: 20091217

Ref country code: CH

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

Effective date: 20100228

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: 20100216

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

Ref country code: IT

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: 20090916

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: 20090916

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

Effective date: 20100317

Ref country code: LU

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

Effective date: 20100216

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: 20090916

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20140612 AND 20140618

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005016735

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005016735

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

Effective date: 20140711

Ref country code: DE

Ref legal event code: R081

Ref document number: 602005016735

Country of ref document: DE

Owner name: PANASONIC INTELLECTUAL PROPERTY CORPORATION OF, US

Free format text: FORMER OWNER: PANASONIC CORPORATION, KADOMA-SHI, OSAKA, JP

Effective date: 20140711

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005016735

Country of ref document: DE

Representative=s name: GRUENECKER PATENT- UND RECHTSANWAELTE PARTG MB, DE

Effective date: 20140711

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: PANASONIC INTELLECTUAL PROPERTY CORPORATION OF, US

Effective date: 20140722

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: GB

Payment date: 20211223

Year of fee payment: 18

Ref country code: FR

Payment date: 20211217

Year of fee payment: 18

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

Ref country code: DE

Payment date: 20211222

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602005016735

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20230216

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

Ref country code: GB

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

Effective date: 20230216

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

Ref country code: GB

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

Effective date: 20230216

Ref country code: FR

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

Effective date: 20230228

Ref country code: DE

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

Effective date: 20230901