RU2654130C1 - Methods for improved multicast content - Google Patents

Abstract

FIELD: network communication technology.

SUBSTANCE: invention relates to network communication technologies. User’s equipment contains: memory; and logic, at least part of which is implemented in the circuit connected to the memory, wherein the logic is for: identifying a multicast content stream packet containing multicast content streams based on the matching section contained in the received multicast transmission, wherein each of the multicast content streams corresponds to one of a plurality of versions of content transmitted via the Multimedia Broadcast Multicast Service (MBMS), and selecting one of the multicast streams for processing based on the characteristics identified in the description section contained in the received multicast transmission.

EFFECT: technical result consists in increasing of data transmission rate.

25 cl, 11 dwg

Description

State of the art

Computing systems are commonly used by users to receive and use various types of multimedia content, such as video, audio, and images. There are numerous technologies and standards used in various contexts when downloading and consuming multimedia content. Some of these technologies and standards relate to unicast transmission of multimedia content, comprising transmitting multimedia content from a single source to a single destination. Other such technologies and standards relate to multicast multimedia content, comprising transmitting multimedia content from a single source to multiple destinations. Multicast can offer increased transmission efficiency and / or beneficial reduction in bandwidth usage.

Due to the wide variety of capabilities of various computing systems used to use multimedia content, and variations in the quality and capabilities of communication channels used to transfer multimedia content from content providers to content consumers, multimedia content providers can make multiple versions of multimedia content available for consumption. Different versions of a particular element of multimedia content may correspond, for example, to different base bit rates, different resolutions, different quality levels and / or other characteristics. Each version of multimedia content may be suitable for a plurality of consumers of multimedia content. In order to take advantage of the benefits of multicasting when providing multiple versions of multimedia content, methods for improved multicast transmission may be required.

Brief Description of the Drawings

FIG. 1 is one embodiment of a device and one embodiment of a system.

FIG. 2 is one embodiment of a first gear.

FIG. 3A is a first embodiment of a conformance segment.

FIG. 3B is a second embodiment of a conformance segment.

FIG. 3C is a third embodiment of a conformance segment.

FIG. 3D is the fourth embodiment of the matching segment.

FIG. 4 is one embodiment of a logical flow.

FIG. 5 is one embodiment of a second gear.

FIG. 6 is one embodiment of a storage medium.

FIG. 7 is one embodiment of a computer architecture.

FIG. 8 is one embodiment of a communication system.

Detailed description

Various embodiments are generally aimed at improving methods for transmitting content. In some embodiments, for example, the device may comprise a processor circuit, a communication component controlled by a processor circuit to receive a data transfer comprising a description segment and a correspondence segment, a correspondence processing component controlled by a processor circuit to determine a plurality of multicast content streams representing different versions multimedia content based on a matching segment and a selection component controlled by a processor circuit to select and receive one or more of the plurality of multicast streams of content, based on the characteristics identified in the segment description. In various such embodiments, an apparatus may comprise an adaptation component controlled by a processor circuit to adaptively switch across multiple streams of multicast content for receiving and processing based on characteristics identified in the description segment. Other embodiments are described and claimed in the claims.

The methods disclosed herein may comprise transmitting content over one or more wireless connections using one or more broadband wireless mobile technologies. Examples of broadband wireless mobile technologies may include, in particular, any of such standards as the Institute of Electronics and Radio Engineering (IEEE) 802.16m and 802.16p, European Institute for Telecommunication Standardization (ETSI) Long Term Evolution (LTE) and LTE- Advanced (LTE ADV) 3rd Generation Partnership Development Project (3GPP) and International Mobile Telecommunications Advanced (IMT-ADV) standards, including their versions, subsequent versions and options. Other relevant examples may include, but not limited to, Global System for Mobile Communications (GSM) technologies / Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications technologies System (UMTS) / High Speed Packet Access (HSPA), World Wide Interoperability for Microwave Access (WiMAX) or the WiMAX II, Code Section Multiple Access System Technologies (CDMA) 2000 (e.g., CDMA2000 IxRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), high-performance urban computer network technologies, High Performance Radio Metropolitan Area Network (HTPERMAN), as defined by broadband radio access network technologies , Broadband Radio Access Networks (BRAN), Wireless Broadband (WiBro), GSM technology with General Packet Radio Service, GSM with General Packet Radio Service (GPRS) (GSM / GPRS), High Speed Downlink Packet Access Technology communication channel, High Speed Downlink Packet Access (HSDPA), high-speed packet access technology For Orthogonal Frequency Division Multiplexing, High Speed Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA), High Speed Uplink Packet Access (HSUPA) Ed. 8 and 9 3GPP LTE / System Architecture Evolution, System Architecture Evolution (SAB), etc. Embodiments are not limited in this context.

By way of example, but not limitation, various embodiments may be described with specific reference to various 3GPP LIE and LTE ADV standards, such as 3GPP LTE Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Universal Terrestrial Radio Access (E- UTRA) and LTE ADV Radio Technology 36 Series of Technical Specifications (collectively the “3GPP LTE Specifications”), and IEEE 802.16 standards, such as the IEEE 802.16-2009 standard and the current third version of IEEE 802.16, referred to as “802.16Rcv3,” combining 802.16-2009, 802.16h-2010 and 802.16m-2011 standards, and draft IEEE 802.16p standards, including IEEE P802.16.lb/D2 of January 2012, entitled "Draft Amendments to IEEE Standard for WirelessMAN-Advanced Air Interface for Broadband Wireless Access Systems, Enhancements to Support Machine-to-Machine Applications "(collectively," IEEE 802.16 Standards "), and any projects, versions or variations of 3GPP LTE technical specifications and IEEE 802.16 standards . Although some embodiments may be described as 3GPP LTE Specifications or the IEEE 802.16 Standards System for example, but not to limit, it should be understood that other types of communication systems may be implemented as various other types of mobile broadband communication systems and standards. Embodiments are not limited in this context.

In addition to, or alternatively, transmitting through one or more wireless connections, the methods disclosed herein may comprise transmitting content via one or more wired connections in one or more wired communication environments. Examples of wired communications include wire, cable, metal conductors, printed circuit board (PCB), motherboard, multi-input switching system, semiconductor material, twisted-pair wire, coaxial cable, fiber optic, etc. Embodiments are not limited in this context.

Here, reference is made to the drawings in which similar reference numbers are used to refer to similar elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in a manner that provides a comprehensive understanding. It may be apparent, however, that new embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate their description. The goal is to cover all modifications, equivalents and alternatives compatible with the stated nature of the subject.

In FIG. 1 is a block diagram of a device 100. Although the device 100 in FIG. 1 has a limited number of elements in a particular topology, it should be understood that the device 100 may contain more or less elements in an alternative topology, as may be required for this implementation.

The device 100 may include a computer-implemented device 100 having a processor circuit 120 configured to execute one or more software components 122-a. It should be noted that “a” and “b” and “c” and similar pointers, as used here, are intended to be variables representing any positive integer. Thus, for example, if the implementation sets the value for a = 5, then the full set of software components 122-a may contain nodes 122-1, 122-2, 122-3, 122-4 and 122-5. Embodiments are not limited in this context.

In various embodiments, device 100 may be implemented in a stationary device. A stationary device is usually called an electronic device designed to be in a fixed, stationary, constant or other position or place without movement, which does not change in time. For example, a stationary device can be installed using devices, fixtures and a bed to prevent movement, including using wired power lines, transmission lines, etc. It should be understood that although the fixed device is generally stationary, some fixed devices can be disconnected from their existing equipment in a first fixed location, moved to a second fixed location, and connected to equipment in a second fixed location. In some other embodiments, device 100 may be implemented as a mobile device. A mobile device is designed to be mobile enough to often move between different places in time. In various embodiments, device 100 may be implemented in any fixed or mobile electronic device or equipment that has wireless and / or wired capabilities and is compatible with one or more wired and / or wireless standards. For example, in one embodiment, a device may comprise a mobile communications device compatible with one or more 3GPP LTE or IEEE 802.16 standards. Embodiments are not limited in this context.

The device 100 may include a processor circuit 120. The processor circuit 120 may typically be configured to execute one or more software components 122-a. The processor circuit 120 may be any of various commercially available processors, including but not limited to AMD® Athlon®, Duron®, and Opteron® processors; ARM® processors with loaded and secure applications; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony © Cell processors; Intel® Celeron®, Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon®, and XScale® processors; and similar processors. Dual microprocessors, multicore processors, and other multiprocessor architectures may also be used as processor unit 120.

The device 100 may include a communication component 122-1. In some embodiments, communication component 122-1 may be configured to be used by processor circuitry 120 to receive transmission 110 via a wired or wireless connection. In various embodiments, transmission 110 may comprise a multicast transmission. A multicast transmission may comprise any transmission transmitted to a group of destinations, essentially simultaneously, through one single transmission from a source. In some embodiments, transmission 110 may be performed using the Multimedia Broadcast / Multicast Service (MBMS) protocol, such as 3GPP TS 26.346, version 10.3.0, revision 10, released in March 2012. In these various embodiments, transmission 110 may comprise a description transmission Services for User (USD) MBMS, which provides application-level information about the available MBMS services, including related transportation options, session description, content characteristics, broadcast schedules, and file correction procedures. In various embodiments, transmission 110 may comprise transmitting metadata. Embodiments are not limited in this context.

In some embodiments, the device 100 may have multiple versions of the content of a particular content item available via one or more wired and / or wireless connections. The term “plurality,” as used herein, is used to mean two or more quantities of something. Examples of such a specific content item may be video files, audio files, images, and other types of media content. Each of the multiple versions of the content may contain a particular version of a particular content item that is different from other versions of the content item based on one or more characteristics. Examples of characteristics on the basis of which versions may differ can be a basic bit rate, frame rate, resolution, codec type, audio language, subtitle language and other characteristics. In various embodiments, each of the multiple versions of the content may be available to the device 100 through an appropriate multicast service. In some such embodiments, each multicast service may comprise a corresponding content stream. In various embodiments, multiple content streams may comprise various transmissions and / or transmission streams. In other embodiments, multiple content streams may comprise different segments within one or more shared transmissions and / or transmission streams. In some embodiments, the implementation of multiple content streams may contain multicast streams of content. In various embodiments, each plurality of versions of the content may be available to the device 100 through a content stream in a corresponding MBMS service. Embodiments are not limited in this context.

In various embodiments, each plurality of versions of the content may be transmitted in one or more bitstreams using scalable video coding (SVC) methods, such as those compliant with Appendix G of ITU-T H.264, published April 4, 2012. SVC methods can generally , contain the formation of one or more bit streams containing the base level and one or more advanced levels. In some embodiments, each version of the content may correspond or be associated with a different SVC level, each MBMS service may correspond or be associated with a different version of the content, and thus, each multicast content stream and associated MBMS services may correspond or be associated with a different level SVC. In various embodiments of this kind, one of the plurality of MBMS services may correspond to or be associated with a base SVC layer, and all other MBMS services from among the plurality of MBMS services may correspond to or be associated with one of the plurality of enhanced SVC layers. Embodiments are not limited in this context.

In some embodiments, each of the multiple versions of the content may be transmitted in one or more bitstreams using multi-projection video coding (MVC) technologies, such as those compliant with Appendix H of ITU-T H.264, published April 4, 2012. MVC methods may, in generally, comprise combining a plurality of time-synchronized video streams representing various projections of three-dimensional (3D) video content in one or more coded bit streams. In various embodiments, a plurality of versions of the content may comprise representing a single 3D scene obtained from different perspectives. One particularly important case of MVC is stereoscopic 3D video coding, in which case two projections are encoded, one for the left eye and one for the right eye. MVC introduces inter-projection prediction between projections to increase compression efficiency, as well as support conventional temporal and spatial prediction. MVC is capable of compressing stereoscopic video in a backward compatible manner without compromising projection resolution. In some embodiments, a single encoded bitstream may be generated by encoding a plurality of time-synchronized bitstreams based on inter-projection predictions. Embodiments are not limited in this context.

In some embodiments, transmission 110 may comprise a segment or description section 111 and a correspondence segment or section 113. The description segment 111 may comprise information, data, or description characteristics of the logic of multiple versions of the content. In various embodiments, the description segment 111 may comprise a plurality of description parts 112b. Each description part 112-b may comprise metadata information description characteristics of a specific version of the content that is available for reception by device 100. Embodiments are not limited in this context.

In some embodiments, the matching segment 113 may contain information, data or logic identifying, for each version of the content described in the description segment 111, a corresponding description of the multicast services through which this version of the content is available for reception by the device 100. In various embodiments, the segment 113 compliance may contain parts 114-c compliance. Each correspondence part 114-c may comprise information identifying a version of the content described by description part 112-b and information identifying a multicast service through which the version of content described by description part 112-b is available for reception by device 100. In some embodiments the implementation of multiple content streams may correspond to or be associated with multiple multicast services, and the segment 113 of the correspondence may contain information, data, or logic identifying for each version ontenta described in the description of the segment 111 corresponding to the content stream and a multicast service, which is available through this version of the content. Embodiments are not limited in this context.

As described herein, multicast services and / or content streams may or may not correspond, or be associated with different physical locations, different network addresses, identifications and / or locations, or different transmissions. For example, in some embodiments, two different multicast services and / or content streams may correspond to or be associated with two different content source devices (eg, multicast servers) in two different places. In other embodiments, two different multicast services and / or content streams may correspond or be associated with two different source devices (eg, multicast servers) in the same place. In other embodiments, two different multicast services and / or content streams may correspond to or be associated with two different transmissions and / or transmission streams from a single device (eg, a multicast server). In other embodiments, two different multicast services and / or content streams may correspond or be associated with different parts of a single transmission and / or transmission stream from one device (eg, a multicast server). Embodiments are not limited in this context.

In various embodiments, the description segment 111 may comprise a media presentation description (MPD) description metadata file received during the transfer of USD MBMS, and each description part 112-b may describe characteristics of a version of the content available for receiving by the device 100 through the MBMS service. In some such embodiments, the correspondence segment 113 may comprise a plurality of correspondence portions 114-c, each of which identifies an MBMS service through which a corresponding version of the content described by the description part 112-b can be received by the device 100. In various embodiments, multiple versions of the content may be available to device 100 as multiple MBMS services. In an example of such an embodiment, the first MBMS service may correspond or be associated with a high-resolution content version, and the second MBMS service may correspond or be associated with a low-resolution content version, and the description segment 111 may comprise a description part 112-1, describing a high resolution content version, and a description part 112-2 describing a low resolution content version. In such an example, the correspondence segment 113 may comprise a correspondence part 114-1 identifying a high resolution content version and indicating that it is available through the first MBMS service, and may include a correspondence part 114-2 identifying a low resolution content version and indicating that it is available through the second MBMS service. In another example of such an embodiment, the first MBMS service may correspond or be associated with a base level content version (left projection) and the second MBMS service may correspond or be associated with an enhanced level content version (right projection) encoded based on SVC (MVC) , and the description segment 111 may include a description part 112-1 describing a base level content version (left projection), a content version and a description part 112-2 describing an enhanced level content version (right projection). In such an example, the correspondence segment 113 may comprise a correspondence part 114-1 identifying the base level content version (left view) and indicating that it is available through the first MBMS service, and may include a correspondence part 114-2 identifying the enhanced level content version (right projection) and indicating that it is available through the second MBMS service. Embodiments are not limited in this context.

In some embodiments, multiple versions of the content may be available to device 100 as various MBMS services within a single MBMS package. In an example of such an embodiment, the MBMS package may comprise a first MBMS service corresponding to a high-resolution content version and a second MBMS service corresponding to a low-resolution content version, and a description segment 111 may comprise a description part 112-1 describing a content version with high resolution, and a description section 112-2 describing a low resolution version of content. In such an example, the correspondence segment 113 may comprise a correspondence part 114-1 identifying a high resolution content version and indicating that it is available through the first MBMS service in the MBMS package, and may include a correspondence part 114-2 identifying a low resolution content version ability and indicating that it is available through the second MBMS service in the MBMS package. Embodiments are not limited in this context.

In various other embodiments, multiple versions of the content may be available to device 100 as various MBMS services within various MBMS packages. In an example of such an embodiment, the MBMS package may comprise a first MBMS service corresponding to a high-resolution content version and a second MBMS service corresponding to a low-resolution content version, and a description segment 111 may comprise a description part 112-1 describing a content version with high resolution, and a description section 112-2 describing a low resolution version of content. In such an example, the correspondence segment 113 may comprise a correspondence part 114-1 identifying a high resolution content version and indicating that it is available through the first MBMS service in the MBMS package, and may include a correspondence part 114-2 identifying a low resolution content version ability and indicating that it is available through the second MBMS service in the MBMS package. Embodiments are not limited in this context.

The device 100 may comprise a compliance processing component 122-2. The correspondence processing component 122-2 may be adapted to be executed by the transmission processing processor circuit 120. In some embodiments, the correspondence processing component 122-2 may control the transmission process 110 to identify multiple content versions, identify characteristics of each of the multiple content versions, and identify a plurality of multicast services through which versions of the content are available to the device 100. In various embodiments, each of the plurality of services is multicast unicast transmission may correspond to or be associated with one of the plurality of content streams. In one example embodiment, the compliance processing component 122-2 can identify the high resolution content version and the low resolution content version and decide that the high resolution content version is available through the first MBMS service and the low resolution content version available through the second MBMS service. Embodiments are not limited to this example.

The device 100 may comprise a connection measurement component 122-3. The connection measurement component 122-3 may be configured to perform a circuit 120 of a measurement and / or analysis of signal path characteristics between the device 100 and each of a plurality of multicast services and / or content streams. In some embodiments, the connection measurement component 122-3 may control the measurement of channel quality and / or effective transmission rate associated with transmission through each multicast service and / or content stream. In embodiments where the compliance processing component 122-2 has identified a plurality of multicast services containing MBMS services, the connection measurement component 122-3 may be controlled to measure channel quality, effective transmission rate and / or other characteristics associated with transmission through each service MBMS In embodiments in which multiple versions of the content are available across multiple MBMS services within the MBMS package, the connection measurement component 122-3 may be controlled to measure channel quality, effective transmission rate and / or other characteristics of the MBMS package, as well as MBMS services within package. In embodiments in which each of the multiple versions of the content is accessible through multiple MBMS services within the multiple MBMS packets, the connection measurement component 122-3 may be controlled to measure channel quality, effective transmission rate and / or other characteristics of each of the MBMS packets, so same as each of the MBMS services within the packages. Embodiments are not limited in this context.

The device 100 may include a selection component 122-4. The selection component 122-4 may be configured to execute the selection processor circuit 120 and receive one or more of a plurality of content versions and / or corresponding multicast services. The selection of one or more of the multiple versions of the content and / or the corresponding multicast services may comprise selecting and receiving one or more of the multiple content streams for processing, including rendering and playback, based on the characteristics identified in the description segment 111. For example, the description segment 111 may include a description part 112-1 identifying the first multicast service and / or the first content stream as corresponding to the first content version, and the selection component 122-4 may select and receive the first content stream for processing based on this first correspondence version of the content.

In various embodiments, the selection component 122-4 may be controlled to select and receive one or more versions of content and / or content streams based on channel quality, effective transmission rate, and / or other characteristics associated with transmission through each of the multiple multicast services and / or content flows measured by the connection dimension component 122-3. In an exemplary embodiment, the connection measurement component 122-3 may be controlled to measure the first effective transmission rate associated with transmitting the first version of the content through the first content stream, and may be controlled to measure the second effective transmission rate associated with the transmission of the second version of the content through the second content stream.

Continuing the above example, the selection component 122-4 may be controlled to compare the first effective transmission rate with the second effective transmission rate and select and receive either the first version of the content and / or the first content stream or the second version of the content and / or the second content stream based whether the first effective transmission rate or the second effective transmission rate is the maximum possible transmission rate supported for multicast communication with a client. Embodiments are not limited to this example. As noted above, multiple content streams may comprise multicast content streams. In some such embodiments, the selection component 122-4 may be controlled to select and receive for processing a multicast content stream available through the MBMS service. Embodiments are not limited in this context.

In various embodiments, when the selection component 122-4 has selected and received a multicast service and / or content stream, the communication component 122-1 may be controlled to obtain a version of the content and / or content stream from the corresponding multicast service. In some embodiments, communication component 122-1 may receive one or more content transmissions containing a content version and / or content stream over a particular channel or frequency assigned to the content version and / or content stream as part of a multicast service. In various embodiments, multiple versions of the content and / or streams may be available through the same channel or on the same frequency, and the communication component 122-1 may be controlled to identify and process portions of the content transmissions on this channel or on this frequency that match or that are associated with the selected version of the content and / or the content stream. In some other embodiments, each version of the content and / or streams may be available through a different channel or at a different frequency as part of a multicast service, and the communication component 122-1 may be controlled to identify the channel (s) or frequency (s) with the selected available version of the content and / or the stream of content and process the parts of the content transfers on this channel (s) or on this frequency (s) that correspond or are associated with the selected version (s) of the content and / or stream (s) ) content. Embodiments are not limited in this context.

The device 100 may comprise an adaptation component 122-5. The adaptation component 122-5 may be adapted to allow the adaptive switching processor circuit 120 across multiple streams of multicast content to receive and process based on the characteristics identified in the description segment. In some embodiments, the adaptation component 122-5 may adaptively switch across multiple streams of multicast content, also based on measurements of channel quality and / or effective transmission rate performed by the connection measurement component 122-3. In an exemplary embodiment, after the selection component 122-4 has selected and received a multicast service and / or content stream, the adaptation component 122-5 can adaptively switch to another multicast service and / or content stream based on the channel quality measurement performed by the component 122-4 selection, which indicates that rendering and playback by another multicast service and / or content stream may provide an improved experience for the user. Embodiments are not limited in this context.

In various embodiments, the MBMS service may comprise selected content version (s) and / or content stream (s) and communication component 122-1 may be controlled to receive content transfers for MBMS and retrieve selected version (s) of content and / or content stream (s) of these content transfers. In some such embodiments, the selected version (s) of content and / or the content stream (s) may correspond to or be associated with the MBMS service contained within the MBMS service package, and the communication component 122-1 may be controlled to receive content transmissions for a package of MBMS services and extract the selected version (s) of content and / or stream (s) of content from the parts of the transmissions of the package of MBMS services corresponding to or associated with the MBMS service to which the selected version (s) of content and / or stream ( i) content. Embodiments are not limited in this context.

In various embodiments, the communication component 122-1 may be controlled to receive content transmissions containing MBMS services and / or service packages in accordance with a File Delivery Over Unidirectional Transport (FLUTE) file transfer protocol. In some such embodiments, the communication component 122-1 may be controlled to organize a FLUTE session for the MBMS service corresponding to the selected content version and / or content stream, receive MBMS content transfers for the MBMS service in the FLUTE session, and retrieve the selected version of the content and / or a stream of content from content transmissions received in a FLUTE session. In various embodiments, communication component 122-1 may be controlled to establish multiple FLUTE sessions corresponding to multiple MBMS services, identify FLUTE session (s) corresponding to MBMS service (s) containing the selected versionito content (s) and / or stream (s) of content, and extract the selected version (s) of content and / or stream (s) of content from the content transfers received through the identified FLUTE session (s). In some such embodiments, multiple MBMS services may be contained in a single MBMS service package. Embodiments are not limited in this context.

In an exemplary embodiment, two versions of the video may be available through the MBMS package: a high-resolution version and a low-resolution version. The MBMS service package may comprise a first MBMS corresponding to the high resolution version and a second MBMS corresponding to the low resolution version. Communication component 122-1 may receive transmission 110. Transmission 110 may comprise a description segment 111 describing a high resolution version and a low resolution version. Transmission 110 may also include a matching segment 113. The compliance processing component 122-2 may process the compliance segment 113 to identify the MBMS package and the first and second MBMS and determine that the high-resolution version corresponds to the first MBMS and the low-resolution version corresponds to the second MBMS. The connection measurement component 122-3 may then measure the channel quality associated with the transmission of the MBMS packet. Based on the measured channel quality, the selection component 122-4 may select and accept a high-resolution version for processing. Based on the determination made by the correspondence processing component 122-2 that the high-resolution version corresponds to the first MBMS, the communication component 122-1 may receive MBMS packet transmissions and extract a content stream corresponding to the first MBMS from the MBMS packet transmissions. Embodiments are not limited to this example.

In another exemplary embodiment, two versions of the video may be available through the MBMS package: a base level version (left projection) and an enhanced level version (right projection) encoded via SVC (MVC). The MBMS service package may comprise a first MBMS service corresponding to a base level version (left projection) and a second MBMS service corresponding to an enhanced level version (right projection). Communication component 122-1 may receive transmission 110. Transmission 110 may comprise a description segment 111 describing a base level version (left projection) and an enhanced level version (right projection). Transmission 110 may also include a matching segment 113. The compliance processing component 122-2 may process the compliance segment 113 to identify the MBMS package and the first and second MBMS and determine that the base level version (left projection) corresponds to the first MBMS service and the enhanced level version (right projection) corresponds to the second service MBMS The connection measurement component 122-3 can then measure the channel quality associated with the transmission of the MBMS packet. Based on the determination that the measured channel quality is high enough to accept both the base level and the improved level (left and right projections), the selection component 122-4 can select and accept both versions of the base level (left projection) and the improved level (right projection) for processing. Based on the determination made by the correspondence processing component 122-2 that the base level version (left projection) corresponds to the first MBMS service, and that the enhanced level version (left projection) corresponds to the second MBMS service, the communication component 122-1 may receive MBMS service packet transmissions and extract from the transmissions of the MBMS service package a content stream corresponding to both the first and second MBMS services. Embodiments are not limited to this example.

In FIG. 1, one embodiment of the system 140 can also be seen. System 140 may include a device 100 and an audio device 142. The audio device 142 may include any device capable of generating tones, music, speech, pronunciation, sound effects, background noise, or other sounds based on the received audio data. Examples of the audio device 142, among other examples, may include a speaker, a multi-speaker system, a home entertainment system, a television, a home appliance, a computer system, a mobile device, and a portable electronic media device. Embodiments are not limited in this context.

In various embodiments, audio device 142 may be configured to generate tones, music, speech, pronunciation, sound effects, background noise, or other sounds based on audio data 141 received from device 100. In some embodiments, audio data 141 may be generated by circuit 120 a processor in combination with reproducing one or more content streams received by the communication component 122-1. Embodiments are not limited in this context.

In FIG. 2, one embodiment of transmission 200 can be seen, which may be the same or similar to transmission 110 in FIG. 1. As shown in FIG. 2, transmission 200 comprises a description segment 211 and a correspondence segment 213. In the example shown in FIG. 2, the description segment 211 comprises description parts 212-1, 212-2 and 212-3. Part 212-1 of the description indicates two characteristics of version A of the content. Namely, the description part 212-1 indicates that the content version A has a resolution of 1920 × 1080 and a transmission speed of 4 MB / s. Similarly, the description part 212-2 indicates that the content version B has a resolution of 1600x900 and a transmission speed of 2 MB / s, and the description part 212-3 indicates that the content version C has a resolution of 1280 × 720 and a transmission speed of 1 MB / from. In addition, in the example shown in FIG. 2, conformity segment 213 comprises conformance parts 214-1, 214-2 and 214-3. Compliance part 214-1 indicates a multicast service corresponding to version A of the content. Namely, the correspondence part 214-1 indicates that the content version A is available through the multicast service 1. Similarly, the correspondence part 214-2 indicates that the content version B is available through the multicast service 2 and the correspondence part 214-3 indicates that the version C content is available through the multicast service 3. It should be noted that although the description parts 212-6 and the correspondence parts 214-c are shown in FIG. 2 in a tabular format, in some embodiments, transmission 200 may contain information of description parts 212-b and correspondence parts 214-c in any format and does not need to contain tables. Embodiments are not limited in this context.

In FIG. 3A presents a first embodiment of a matching segment 300, which may be contained within transmission 200 shown in FIG. 2. FIG. 3A contains an example of a matching segment that may be associated with embodiments in which multiple versions of content are available as multiple MBMS services. As shown in FIG. 3A, conformity segment 300 comprises conformity parts 314-1, 314-2 and 314-3. In the example shown in FIG. 3A, compliance part 314-1 indicates that content version A is available through MBMS service 1, compliance part 314-2 indicates that content version B is available through MBMS service 2, and compliance part 314-3 indicates that content version C is available through 3 MBMS service. Embodiments are not limited to this example.

In FIG. 3B, a second embodiment of a correspondence segment 300 may be seen, which may be present within the transmission 200 shown in FIG. 2. In FIG. 3B presents an example of a conformance segment that may be associated with embodiments in which multiple versions of the content are available as multiple MBMS services within a single MBMS service package. As shown in FIG. 3B, conformity segment 300 comprises conformance parts 314-1, 314-2 and 314-3. In the example of FIG. 3B, compliance part 314-1 indicates that content version A is available through MBMS package 1, service 1, compliance part 314-2 indicates that content version B is available through MBMS package 1, service 2, and compliance part 314-3, indicates that version C of the content is available through MBMS package 1, service 3. Embodiments are not limited to this example.

In FIG. 3C shows a third embodiment of a matching segment 300, such as may be present within the transmission 200 shown in FIG. 2. In FIG. 3C shows an example of a correspondence segment that may be associated with embodiments in which multiple versions of the content are available, since there are many MBMS services within a plurality of MBMS service packages. As shown in FIG. 3C, conformity segment 300 comprises conformance parts 314-1, 314-2 and 314-3. In the example of FIG. 3C, correspondence part 314-1 indicates that content version A is available through MBMS package 1, service 1, correspondence part 314-2 indicates that content version B is available through MBMS package 2, service 1, and correspondence part 314-3, indicates that version C of the content is available through MBMS package 3, service 1. Embodiments are not limited to this example.

In various embodiments, communication component 122-1 may be controlled to establish one or more File Delivery over Unidirectional Transport (FLUTE) sessions with one or more multicast service broadcast centers (BMSCs). In some embodiments, each FLUTE session may correspond to an MBMS service or an MBMS service package, so that content transfers associated with a particular MBMS service are received through a FLUTE session corresponding to that MBMS service or an MBMS service package to which the MBMS service belongs.

In FIG. 3D presents a fourth embodiment of a correspondence segment 300, which may be present within the transmission 200 shown in FIG. 2, and which may be suitable for use in embodiments in which MBMS services and / or MBMS service packets are received through FLUTE sessions. As shown in FIG. 3D., Conformity segment 300 comprises conformance parts 314-1, 314-2 and 314-3. In the example shown in FIG. 3D, correspondence part 314-1 indicates that content version A is available in MBMS service 1 through a FLUTE session 1, correspondence part 314-1 indicates that content version B is available in MBMS service 2 through a FLUTE session 2, and correspondence part 314-3 indicates that version C of the content is available in MBMS 3 through a 3 FLUTE session. Embodiments are not limited to this example.

In FIG. 4 illustrates one embodiment of a content transfer 400. In the example of FIG. 4, content transfer 400 may be an example of various embodiments in which multiple multicast services correspond to different parts of the same transmission or series of transmissions that may occur simultaneously. As shown in FIG. 4, content transfer 400 may comprise content parts 402-1 and 402-2. Part 402-1 content contains segments 403-1, 403-2 and 403-3 content and part 402-2 content contains segments 403-4, 403-5 and 403-6 content. As shown on the time axis in FIG. 4, various segments of content within a particular piece of content can be transmitted sequentially in time. As shown on the axis of the multicast services in FIG. 4, various pieces of content may be transmitted through a change in multicast services. In some embodiments, the content portion 402-1 may correspond to a first version of the content and the content portion 402-2 may correspond to a second version of the content. In such various embodiments, the selection component 122-4 may select and receive the first version of the content and / or the second version of the content, and the communication component 122-2 may extract segments of the content from the piece (s) of content corresponding to the selected version (s) of the content. In an exemplary embodiment, the selection component 122-4 may select and receive a first version of the content, and the communication component 122-2 may retrieve content segments 403-1, 403-2, and 403-3 from the content portion 402-1 corresponding to the first content version. Embodiments are not limited to this example.

In some embodiments, the content transfer 400 may correspond to the content transfer of the MBMS package. In various such embodiments, each piece of content within the content transfer 400 may correspond to different MBMS services within the MBMS service package. For example, the content part 402-1 may correspond to the first MBMS service within the MBMS service package, and the content part 402-2 may correspond to the second MBMS service within the MBMS service package. In some such embodiments, the selection component 122-4 may select and receive a version of the content corresponding to the first MBMS service and / or the second MBMS service, and the communication component 122-2 may retrieve content segments from the content part (s) corresponding to the selected service ( s) MBMS. In an exemplary embodiment, the selection component 122-4 may select and receive a version of the content corresponding to the content part 402-1 and the first MBMS service, and the component 122-2 may extract content segments 403-1, 403-2 and 403-3 from the part 402 -1 content that correspond to the first MBMS service and, thus, the first version of the content. Embodiments are not limited in this context.

It contains a set of logical flows that represent approximate methodologies for implementing new variants of the disclosed architecture. Although, in order to simplify the explanation, one or more of the methodologies shown here is presented and described as a sequence of actions, those skilled in the art should understand that methodologies are not limited to the order of actions. Some actions in accordance with this may occur in a different order and / or simultaneously with other actions shown and described here. For example, those skilled in the art should understand that a methodology can alternatively be represented as a sequence of interrelated states or events, such as shown in a state diagram. In addition, not all activities shown in the methodology may be required for a new implementation.

The logical stream may be implemented in software, firmware, and / or hardware. In embodiments of software and firmware, the logical stream may be implemented by a computer capable of executing instructions stored on non-transferable computer readable media or computer readable media such as optical, magnetic or semiconductor memory. Embodiments are not limited in this context.

In FIG. 5 shows an embodiment of a logical stream 500. The logical stream 500 may be represented by several or all of the operations performed by one or more of the embodiments described here, such as device 100. In more detail, the logical stream 500 may be implemented by communication component 122-1, component 122 -2 conformance processing, connection dimension component 122-3, selection component 122-4 and / or adaptation component 122-5.

As shown in FIG. 5 of the embodiment, the logical flow 500 in step 502 may receive a transmission containing a description segment and a correspondence segment. For example, the device 100 shown in FIG. 1, may receive a transmission 110 comprising a description segment 111 and a correspondence segment 113 through a communication component 122-1. In some embodiments, a description segment may identify characteristics of multiple versions of content. For example, the description segment 111 shown in FIG. 1 may include portions 112-6 of the description that may identify characteristics of multiple versions of content. In various embodiments, the compliance segment may identify multiple streams of multicast content corresponding to multiple versions of the content. For example, the correspondence segment 113 shown in FIG. 1 may comprise correspondence portions 114c, which can identify multiple streams of multicast content corresponding to the multiple versions of the content described by description portions 112-6. Logical stream 500, at 504, can determine multiple streams of multicast content based on the matching segment. For example, the compliance processing component 122-2 shown in FIG. 1 may process correspondence portions 114c to identify multiple streams of multicast content. Logical stream 500, at 506, can select and receive one or more of a plurality of multicast content streams for processing based on information contained in a description segment. For example, the selection component 122-4 shown in FIG. 1 may select one or more of a plurality of multicast content streams defined by the correspondence processing component 122-2 based on the characteristics identified in parts 111-b of the description. Logical stream 500 may adaptively switch across multiple streams of multicast content for reception and processing based on the characteristics identified at block 508 in the description segment. For example, adaptation component 122-5 of FIG. 1 may adaptively switch across multiple streams of multicast content defined by the correspondence processing component 122-2 based on the characteristics identified in parts 111-b of the description. Embodiments are not limited to these examples.

In FIG. 6 illustrates an embodiment of a storage medium 600. Storage medium 600 may comprise product data. In one embodiment, the storage medium 600 may include any non-transferable computer-readable medium or computer-readable medium, such as optical, magnetic or semiconductor memory. Storage media may store various types of computer-executable instructions, such as instructions for implementing logical flow 500. Examples of computer-readable or computer-readable media may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable storage device, writable or rewritable memory, etc. Examples of “computer-executable instructions” may be any appropriate type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, etc. The implementation options are not limited to this context.

In FIG. 7 illustrates an embodiment of an apparatus 700 for use in a broadband wireless access network. Device 700 may implement, for example, device 100, storage medium 600 and / or logic 730. Logic 730 may include physical circuits for performing the operations described for device 100. As shown in FIG. 7, device 700 may include a radio interface 710, a baseband circuit 720, and a computer platform 730, although embodiments are not limited to this configuration.

The device 700 may implement some or all of the structures and / or operations for the device 100, the medium 600 and / or the logic circuit 730 in a single computer entity, such that is entirely located within a single device. Alternatively, device 700 may distribute portions of the structure and / or operations to device 100, medium 600 and / or logic 730 through multiple computer objects using distributed system architectures such as client-service architecture, 3-tier architecture, N-tier architecture reliably coupled or clustered architecture, peer-to-peer network architecture, master-slave architecture, shared database architecture, and other types of distributed systems. Embodiments are not limited in this context.

In one embodiment, the radio interface 710 may comprise a component or combination of components adapted to transmit and / or receive an unmodulated carrier or multi-carrier modulated signals (e.g., such as CCK modulation (CCK) and / or orthogonal frequency division multiplexing (OFDM) symbols, although embodiments are not limited to any particular radio interface or modulation scheme. The radio interface 710 may comprise, for example, a receiver 712, a transmitter 716, and / or a frequency synthesizer 714. The radio interface 710 may include bias controls, a crystal oscillator, and / or one or more antennas 718-f. In another embodiment, the air interface 710 may use external voltage controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and / or radio frequency (RF) filters, as needed. Due to the variety of potential designs of the radio interfaces, their extended description is not given.

The baseband circuit 720 may communicate with a radio interface 710 to process the received and / or transmitted signals, and may include, for example, an analog-to-digital converter 722 for converting the received signals downward in frequency, a digital-to-analog converter 724 for converting the signals for transmission. Additionally, the baseband circuitry 720 may comprise a baseband or physical (PHY) layer processing circuitry 756 for processing the PHY link level of the respective received / transmitted signals. The baseband operation 720 may comprise, for example, a processing circuitry 728 for processing with respect to medium access control (MAC) / data link layer. The baseband circuit 720 may include a memory controller 732 for communicating with the processing circuitry 728 and / or the computer platform 730, for example, through one or more interfaces 734.

In some embodiments, the PHY processing circuitry 726 may include a frame construction and / or detection module in combination with an additional circuitry such as buffer memory to collect and / or parse communication frames, such as packet 600. Alternatively or additionally, the processing circuitry 728 The MAC may jointly process some of these functions or perform these processes independently of the PHY processing circuit 726. In some embodiments, MAC and PHY processing can be integrated into a single scheme.

Computer platform 730 may provide the computing functionality of device 700. As shown, computer platform 730 may comprise a processing component 740. In addition to or alternatively to the baseband operation 720, device 700 may perform processing operations or logic operations for device 100, data recording medium 600, and logic 730 using processing component 730. Processing component 730 (and / or 726 for PHY and / or 728 for MAC) may contain various hardware elements, software elements, or a combination of both. Examples of software may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits (e.g., processor circuit 120), circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, specialized integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), programmable logic integrated circuits (FPGA), memory blocks, logic arrays, registers, semiconductor devices, micros hemes, microcrystals, chipsets, etc. Examples of software elements can be software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, program modules, typical programs, routines, functions, methods, procedures, software interfaces, application programming interfaces (APIs), set s commands, computational code, machine code, code segments, machine code segments, words, values, characters, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and / or software elements may vary according to any number of factors, such as the required computing level, power levels, heat tolerances, processing cycle budget, input data rate, output rate data, memory resources, data bus speed, and other design or performance constraints required for a given implementation.

Computer platform 730 may further comprise other platform components 750. Other components of the 750 platform contain conventional computer elements such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, generators, synchronization devices, video cards, sound cards, multimedia input-output components (I / O) (e.g. digital displays), power supplies, etc. Examples of memory blocks can be, in particular, various types of computer-readable and computer-readable media in the form of one or more high-speed memory blocks, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), dual-speed DRAM data communications (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory, such as ferroelectric polymer memory, memory l on Ovshinsky elements, phase-change memory or memory on ferroelectrics, silicon-oxide-nitride-silicon-silicon (SONOS) memory, magnetic or optical cards, a device matrix such as a disk array (RAID), solid-state memory devices ( for example, USB memory, solid state drives (SSDs), and any other type of storage medium suitable for storing information.

The device 700 may be, for example, an ultramobile device, a mobile device, a stationary device, a machine-to-machine device (M2M), a personal digital assistant (PDA), a mobile computer device, a smartphone, a telephone, a digital telephone, a cellular telephone, user equipment, e-book reader, telephone headset, one-way pager, two-way pager, messaging device, computer, personal computer (PC), desktop computer, laptop, laptop computer, netbook, handheld computer, tablet computer, server, server matrix or group of servers, web server, network server, internet server, workstation, minicomputer, central computer, supercomputer, network device, web device, distributed computing system , multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, gaming devices, television, digital television, television rate, access point, base station, Node B, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or a combination thereof. Accordingly, the functions and / or specific configurations of the device 700 described herein may be introduced or excluded in various embodiments of the device 700 as necessary. In some embodiments, device 700 may be configured to be compatible with protocols and frequencies associated with one or more 3GPP LTE specifications and / or IEEE 802.16 WMAN standards and / or other broadband wireless networks listed here, although embodiments are not limited in this regard.

Embodiments of device 700 may be implemented using single-input and single-output (SISO) architectures. However, some implementations may include multiple antennas (for example, antennas 718-f) for transmission and / or reception, using adaptive methods, beamforming techniques or spatial division multiple access (SDMA) and / or using MIMO communication methods.

The components and features of device 700 may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic arrays, and / or single-chip architectures. Additionally, the features of device 700 may be implemented using microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the above, where appropriate. It should be noted that hardware, firmware, and / or software elements, collectively or individually, may be referred to here as “logic” or “circuitry”.

It should be understood that the exemplary device 700 shown in the block diagram of FIG. 7 may represent one functionally descriptive example from a variety of potential implementations. Accordingly, the division, exclusion, or introduction of the functions of the blocks shown in the accompanying drawings does not imply that hardware components, circuits, software, and / or elements for implementing these functions must necessarily be shared, excluded, or introduced into embodiments.

In FIG. 8 illustrates an embodiment of a broadband wireless access system 800. As shown in FIG. 8, the broadband wireless access system 800 may be an Internet Protocol (IP) type network, comprising an Internet type 810 network and the like, capable of supporting mobile wireless access and / or fixed wireless Internet access 810. In one or more embodiments of implementation, the broadband wireless access system 800 may comprise any type of orthogonal frequency division multiple access (OFDMA) wireless network, such as a system compatible with one or more of the technical requirements 3GPP LTE and / or IEEE 802.16 standards, and the scope of the claimed subject matter is not limited in these respects.

In an exemplary broadband wireless access system 800, access service networks (ASNs) 814 are capable of communicating with base stations (BSs) 814, 820 (or eNodeB), respectively, to provide wireless communication between one or more fixed devices 816 and the Internet 110 or one or more mobile devices 822 and the Internet 110. One example of a fixed device 816 and a mobile device 822 is a device 700 with a fixed device 816 containing a stationary version of the device 700, and a mobile device 822, with holding a mobile version of device 700. ASN 812 may implement profiles capable of determining the mapping of network functions to one or more physical entities on broadband wireless access system 800. Base stations 814, 820 (or eNodeB) may include radio equipment for providing radio frequency communications with a fixed device 816 and a mobile device 822, such as described with respect to device 700, and may include, for example, PHY and MAC layer equipment in accordance with 3GPP specifications LTE or IEEE 802.16 standard. Base stations 814, 820 (or eNodeB) may further comprise an IP motherboard for communicating with the Internet 810 via ASN 812, 818, respectively, although the scope of the claimed entity is not limited in these respects.

Broadband wireless access system 800 may further comprise a visited communications service network (CSN) 824 capable of providing one or more network functions, including, but not limited to, proxy and / or relay type functions, for example, authentication, authorization, and accounting (AAA ), Dynamic Host Configuration Protocol (DHCP) functions, or domain name service controls, etc., domain gateways such as Public Switched Network Gateways (PSTNs) or Internet Protocol Telephony Gateways (VoIP), and / or functions server type Internet Protocol (IP), etc. However, this is just an example of the types of functions that can be provided by the visited CSN 824 or home CSN 826, and the scope of the claimed subject matter is not limited in these respects. A visited CSN 824 may be referred to as a visited CSN in a case where the visited CSN 824 is not part of the regular service provider of the fixed device 816 or mobile device 822, for example, when the fixed 816 or mobile device 822 is roaming away from their corresponding home CSN 826 or when broadband wireless access system 800 is part of a service provider of a fixed device 816 or mobile device 822, but where broadband wireless access system 800 may be located in a different location or condition that is not the primary or original location of the fixed device 816 or mobile device 822.

The fixed device 816 may be located anywhere within the range of one or both of the base stations 814, 820, such as inside or near the home or business, to provide the client at home or on the premises of the business with broadband Internet access 810 through the base stations 814, 820 and ASN 812, 818, respectively, and home CSN 826. It should be noted that although the stationary device 816 is usually located in a stationary location, it can be moved to various places as necessary. Mobile device 822 may be used in one or more places if the mobile device 822, for example, is within the range of one or both base stations 814, 820.

In accordance with one or more embodiments, an operation support system (OSS) 828 may be part of a broadband wireless access system 800 to provide management functions for the broadband wireless access system 800 and the interfaces between the functional entities of the broadband wireless access system 800. The broadband wireless access system 800 shown in FIG. 8 is simply one type of wireless network containing a number of components of a broadband wireless access system 800, and the context of the claimed subject matter is not limited in these respects.

The following examples relate to further embodiments:

The method may comprise receiving, on a computer device comprising a processor circuit, data transmission comprising a description segment and a correspondence segment identifying a plurality of multicast content streams representing various versions of multimedia content based on a matching segment and selecting one or more of the plurality of streams using a processor circuit multicast content to be processed based on the characteristics identified in the description segment.

Such a method may comprise receiving one or more of a plurality of multicast content streams from a multicast server.

Such a method may comprise rendering multimedia content from a selected one or more streams of multicast content on an output device.

Such a method may comprise adaptively switching a processor circuit to multiple streams of multicast content for receiving and processing based on characteristics identified in the description segment.

According to such a method, each of the plurality of multicast content streams may comprise one service from a plurality of multimedia broadcast multicast services (MBMS).

According to such a method, a plurality of MBMS services may be contained in an MBMS service package.

According to such a method, the computing device may comprise dynamic adaptive streaming to a client using the Hypertext Transfer Protocol (DASH).

According to such a method, the data transfer may comprise transmitting a service description for a user (USD) representing a matching segment.

In accordance with such a method, the description segment may comprise a media presentation description (MPD) metadata file as part of the USD transfer.

Such a method may comprise establishing multiple sessions using a unidirectional transport file transfer protocol (FLUTE), each of the plurality of FLUTE sessions corresponding to one of a plurality of multicast content streams.

According to such a method, the correspondence segment may comprise information identifying, for each of the plurality of multicast content streams and corresponding MBMS, the corresponding one of the plurality of FLUTE sessions.

Such a method may comprise defining one or more FLUTE sessions corresponding to MBMS services containing the selected multicast content streams.

Such a method may comprise receiving selected multicast content streams in MBMS services corresponding to certain FLUTE sessions.

Such a method may comprise selecting and receiving one or more of a plurality of multicast content streams, based on a format or a base rate of a content version that corresponds to one or more of a plurality of multicast content streams.

Such a method may comprise selecting and receiving one or more of a plurality of multicast content streams based on channel quality or an effective transmission rate associated with transmitting one or more of a plurality of multicast content streams.

According to such a method, each of the plurality of multicast content streams and MBMS services can correspond to one of the plurality of layers in a scalable video coding (SVC) bitstream.

According to such a method, each of a plurality of multicast content streams and MBMS services may correspond to one of a plurality of projections in a multi-projection video coding (MVC) bitstream.

The device may include a processor circuit, a communication component configured to perform a multicast reception processor circuit comprising a description section and a correspondence section, correspondence processing component configured to implement a processor circuit to identify a multicast content stream containing a plurality of multicast content streams, based on the correspondence section, each of the multiple streams of multicast content corresponding to one of the multiple ver This content and the selection component are configured to execute at least one of the plurality of multicast content streams for processing by the processor circuit based on the characteristics identified in the description section.

With respect to such a device, the selection component may be adapted to allow the processor circuitry to receive at least one of the plurality of multicast content streams from the device of the multicast source source.

With respect to such a device, the processing may comprise rendering and reproducing multimedia content.

Such a device may comprise an adaptation component adapted to allow the processor circuit to adaptively switch across multiple streams of multicast content for reception and processing based on the characteristics identified in the description section.

With respect to such a device, each of the plurality of multicast content streams may comprise one of a plurality of multimedia broadcast multicast service (MBMS) services.

With respect to such a device, the multicast content stream packet may comprise an MBMS service packet.

Such a device may comprise dynamic adaptive streaming through a Hypertext Transfer Protocol (DASH) client.

With respect to such a device, a multicast may comprise transmitting a service description for a user (USD) representing a correspondence section.

With respect to such a device, the description section may comprise a media presentation description (MPD) metadata file within the USD transfer.

With respect to such a device, the communication component may be arranged by the processor circuit to organize multiple sessions using the Unidirectional Transport File Transfer Protocol (FLUTE), each of the plurality of FLUTE sessions corresponding to one of the plurality of multicast content streams, and the correspondence section contains identification information , for each of a plurality of multicast content streams and corresponding MBMS services corresponding to a plurality of FLUTE sessions.

With respect to such an apparatus, the correspondence processing component may be adapted to be implemented by a processor circuit to determine one or more FLUTE sessions corresponding to MBMS services containing selected multicast content streams.

With respect to such a device, the communication component may be configured by a processor circuit to receive selected multicast streams in MBMS services corresponding to certain FLUTE sessions.

With respect to such a device, the selection component may be adapted to be implemented by a processor circuit to select and receive at least one of a plurality of multicast content streams based on a format or a base rate of a content version corresponding to at least one of the plurality of multicast streams content, or based on the quality of the channel or the effective transmission rate associated with the transmission of at least one of the multiple streams of multicast content.

With respect to such a device, each of a plurality of multicast content streams and MBMS services may correspond to one of a plurality of layers in a scalable video coding (SVC) bitstream.

With respect to such a device, each of a plurality of multicast content streams and MBMS services may correspond to one of a plurality of projections in a multi-projection video coding (MVC) bitstream.

At least one machine-readable medium may comprise a plurality of instructions that, in response to their execution on a computer device, cause the computer device to receive a service description for the user (USD) containing a description section and a correspondence section, and select at least one content stream from multiple content streams identified using the matching section, each of the multiple content streams containing multicast streams associated with a different version of the multicast ontenta accessible via the corresponding service of multimedia broadcast multicast service (MBMS), and at least one content stream is selected according to the properties identified in the description section.

Such at least one machine-readable medium may contain instructions that, in response to their execution on a computer device, cause the computer device to organize one or more sessions using the unidirectional transport file transfer protocol (FLUTE) corresponding to at least one content stream.

Such at least one machine-readable medium may comprise instructions that, in response to their execution on a computer device, cause the computer device to receive the selected at least one content stream using one or more FLUTE sessions.

With respect to such at least one computer-readable medium, each of a plurality of content streams may be associated with one of a plurality of layers in a scalable video coding (SVC) stream.

With respect to such at least one machine-readable medium, each of a plurality of content streams may be associated with one of a plurality of projections in a multi-projection video coding (SVC) stream.

With respect to such at least one machine-readable medium, a plurality of content streams may comprise a plurality of MBMS services within an MBMS package.

Such at least one machine-readable medium may comprise instructions that, in response to their execution on a computer device, cause the computer device to receive the selected at least one content stream from the MBMS server.

Such at least one computer-readable medium may comprise instructions that, in response to their execution on a computer device, cause the computer device to provide a multicast version of the content corresponding to the selected at least one content stream.

The system may include a processor, an audio device connected by means of communication with the processor, a communication component configured to implement a data transmission receiving processor comprising a description section and a correspondence section, a correspondence processing component for identifying a plurality of multimedia streams of broadcast multicast service content (MBMS) by the processor, based on the correspondence section, each of the plurality of MBMS content streams corresponding to one of the plurality of content versions, and a selection component, configured to allow the processor to select at least one of the multiple MBMS content streams for processing based on the characteristics identified in the description section.

With respect to such a system, the selection component may be arranged for the processor to select and receive at least one of the plurality of MBMS content streams, based on the format or base rate of the content version to which at least one of the plurality of MBMS content streams corresponds, or based on channel quality or effective transmission rate associated with the transmission of at least one of the multiple MBMS content streams.

Such a system may comprise an adaptation component adapted to allow the processor to adaptively switch across multiple MBMS content streams for reception and processing based on the characteristics identified in the description section.

With respect to such a system, the communication component can be configured by the processor to organize multiple sessions using the Unidirectional Transport File Transfer Protocol (FLUTE), each of the multiple FLUTE sessions corresponding to one of the multiple MBMS content streams and the correspondence section contains identification information identifying for each of a plurality of MBMS content streams corresponding to one of a plurality of FLUTE sessions.

With respect to such a system, the communication component may be arranged for the processor to receive the selected at least one MBMS content stream in one or more MBMS services corresponding to certain FLUTE sessions.

With respect to such a system, a plurality of MBMS content flows may be contained within an MBMS service package.

With respect to such a system, the description section may comprise a media presentation description file (MPD) within a user service description (USD) transmission.

Such a system may comprise dynamic adaptive streaming through a Hypertext Transfer Protocol (DASH) client.

With respect to such a system, each of a plurality of MBMS content streams may correspond to one of a plurality of layers in a scalable video coding (SVC) bitstream.

With respect to such a system, each of a plurality of MBMS content streams may correspond to one of a plurality of projections in a multi-projection video coding (MVC) bitstream.

Some embodiments may be described using the expression “one embodiment” or “embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with an embodiment is contained in at least one embodiment. The appearance of the expression “in one embodiment” at various places in the description does not necessarily always refer to the same embodiment.

In addition, in the following description and / or claims, the terms “coupled” and / or “connected” along with their derivatives can be used. Specific connected embodiments may be used to indicate that two or more elements are in direct physical and / or electrical contact with each other. “Connected” may mean that two or more elements are in direct physical and / or electrical contact. However? “coupled” may also mean that two or more elements may not be in direct contact with each other, but may still act in conjunction and / or interact with each other. For example, “coupled” may mean that two or more elements are not in contact with each other, but are indirectly combined through another element or intermediate elements.

In addition, the term “and / or” can mean “and”, can mean “or”, can mean “exclusive or”, can mean “one”, can mean “several but not all”, can mean “not a single "and / or this may mean" both ", although the scope of the claimed subject matter is not limited in this regard. In the following description and / or claims, the terms “comprises” and “includes” may be used synonymously with their derivatives.

We emphasize that the section "Abstract" is intended to allow the reader to quickly establish the nature of the technical disclosure. It is proposed with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the previous “Detailed Description” section, it can be seen that various features are grouped in a single embodiment in order to optimize the disclosure. This disclosure method should not be interpreted as a reflection of the intention that the claimed embodiments require more features than is expressly expressed in each claim. Rather, as the following claims reflect, the essence of the subject invention is less than in all the features of a single disclosed embodiment. Thus, the following claims are hereby included in the “Detailed Description” with each claim standing independently as a separate embodiment. In the appended claims, the terms “comprising” and “in which” are used as purely English equivalents of the respective terms, “comprising” and “where”, respectively. In addition, the terms “first”, “second”, “third”, etc. they are used simply as marks and are not intended to impose numerical requirements on their objects.

What has been described above contains examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and / or methodologies, but one skilled in the art may recognize that many additional combinations and permutations are possible. Accordingly, the new architecture is intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims.

Claims (25)

1. User equipment (UE), comprising: memory; and logic, at least a portion of which is implemented in a circuit connected to the memory, the logic being for: identifying a packet of multicast content streams containing multicast content streams based on a correspondence section contained in the received multicast transmission, each of the multicast streams corresponds to one of a plurality of versions of content transmitted through a multimedia broadcast multicast service (MBMS), and selecting one of the multicast streams for operations based on the characteristics identified in the description section contained in the received multicast. 2. The UE according to claim 1, wherein the logic is designed to organize one or more sessions using the unidirectional transport file transfer protocol (FLUTE), each of the plurality of FLUTE sessions corresponding to one of the multicast content streams and the correspondence section contains information identifying for each of multicast content streams and the corresponding MBMS corresponding FLUTE session. 3. The UE of claim 2, wherein the logic is for determining a FLUTE session corresponding to an MBMS service containing a selected multicast content stream. 4. The UE of claim 3, wherein the logic is for receiving a selected multicast content stream in an MBMS corresponding to a specific FLUTE session. 5. UE according to any one of paragraphs. 1-4, wherein the logic is for selecting a multicast content stream based on a format or a base rate of a version of the content to which a multicast content stream corresponds, or based on a channel quality or an effective transmission rate associated with transmitting a multicast content stream. 6. UE according to any one of paragraphs. 1-4, in which each multicast content stream and MBMS service correspond to a level in a scalable video coding (SVC) bitstream. 7. UE according to any one of paragraphs. 1-4, in which each multicast content stream and the MBMS service correspond to a projection in a multi-projection video coding (MVC) bitstream. 8. At least one computer-readable storage medium containing a set of instructions that, when executed by a user equipment (UE), causes the UE to: identify one or more multimedia broadcast multicast content service (MBMS) service streams based on the correspondence section contained in the received wireless data transmission, each of the MBMS content streams corresponding to one of the multiple versions of the content, and select at least one of the MBMS content streams for processing based on ve description section contained in the received wireless data transmission. 9. At least one computer-readable storage medium according to claim 8, containing a set of instructions that, when executed by a user equipment (UE), prompts the UE to select at least one of the MBMS content streams based on the format or the base rate of the content version which corresponds to at least one of the MBMS content streams, or based on channel quality or effective transmission rate associated with the transmission of at least one of the MBMS content streams. 10. At least one computer-readable storage medium according to claim 8, containing a set of instructions that, when executed by a user equipment (UE), causes the UE to adaptively switch over MBMS content streams to receive and process based on the characteristics identified in section descriptions. 11. At least one computer-readable storage medium according to claim 8, containing a set of instructions which, when executed by a user equipment (UE), prompts the UE to organize multiple file transfer sessions using the unidirectional transport file transfer protocol (FLUTE), each of which is a FLUTE session corresponds to one of the MBMS content flows and the correspondence section contains information identifying for each of the MBMS content flows the corresponding one of the FLUTE sessions. 12. At least one computer-readable storage medium according to claim 8, containing a set of instructions that, when executed by a user equipment (UE), causes the UE to receive at least one MBMS content stream in one or more MBMS services corresponding to certain FLUTE sessions. 13. At least one computer-readable storage medium according to claim 8, wherein the MBMS content streams are contained within the limit of the MBMS service packet. 14. At least one computer-readable storage medium according to any one of paragraphs. 8-13, in which the description section contains a description of the media presentation file (MPD) as part of the transfer of user service descriptions (USD). 15. At least one computer-readable storage medium according to any one of paragraphs. 8-13, comprising dynamic adaptive streaming through a client using the Hypertext Transfer Protocol (DASH). 16. At least one computer-readable storage medium according to any one of paragraphs. 8-13, in which each of the MBMS content streams corresponds to a level in a scalable video coding (SVC) bitstream or projection in a multi-projection video coding (MVC) bitstream. 17. A device for processing streams of multicast content, comprising: means for receiving a multicast transmission containing a description of services for a user (USD) over a multimedia broadcast / multicast service protocol (MBMS), the multicast transmission comprising a description section and a correspondence section; means for identifying a packet of multicast content streams containing multicast content streams based on a correspondence section, each of the plurality of multicast content streams corresponding to one of the plurality of content versions; and means for selecting one of the multicast content streams for processing based on the characteristics identified in the description section. 18. The device according to p. 17, containing means for rendering and reproducing multimedia content from one of the streams of multicast content. 19. The device according to claim 17, comprising means for adaptively switching over a series of multicast content streams to receive and process one of the multicast content streams based on the characteristics identified in the description section. 20. The device according to p. 17, in which each of the streams of multicast content contains the content of the multimedia broadcast multicast service (MBMS). 21. The device according to claim 20, in which the packet of multicast streams of content contains a package of MBMS services. 22. The device according to p. 17, containing means for performing dynamic adaptive streaming through a client using the Hypertext Transfer Protocol (DASH). 23. The device of claim 17, wherein the multicast comprises transmitting a service description for a user (USD) to represent a conformance section. 24. The device according to claim 23, wherein the description section contains a media presentation description (MPD) metadata file within the USD transmission. 25. The device according to any one of paragraphs. 17-24, wherein each of the MBMS content streams corresponds to a level in a scalable video coding (SVC) bitstream or projection in a multi-projection video coding (MVC) bitstream.

Images