JP6400755B2 - Method and system for transitioning reception of broadcast DASH service between unicast and broadcast - Google Patents

Description

CROSS REFERENCE TO RELATED APPLICATIONS This patent application claims priority to the following provisional application, which is assigned to the assignee of the present specification, the entire contents of which are expressly incorporated herein by reference: “METHOD No. 61 / 587,103, “METHOD AND SYSTEM FOR TRANSITIONS OF BROADCAST DASH SERVICE RECEPTIONS BETWEEN UNICAST AND BROADCAST”, filed on January 16, 2012 No. 61 / 623,965, filed April 13, 2012, filed May 14, 2012, entitled “METHOD AND SYSTEM FOR TRANSITIONS OF BROADCAST DASH SERVICE RECEPTIONS BETWEEN UNICAST AND BROADCAST” 61 / 646,873 and “METHOD AND SYSTEM FOR TRANSITIONS OF BROADCAST DASH SERVICE RECEPTIONS BETWEEN UNICAST AND BROADCAST” No. 61 / 719,936, filed on the 29th month.

  Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to management of dynamic adaptive streaming over HTTP (DASH) services.

  Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, and so on. These wireless networks can be multiple access networks that can support multiple users by sharing available network resources. Examples of such multiple access networks include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA ( SC-FDMA) network is included.

  A wireless communication network may include a number of base stations that can support communication for a number of user equipments (UEs), also referred to as mobile entities. The UE may communicate with the base station via the downlink and uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station. As used herein, “base station” means an eNode B (eNB), Node B, Home Node B, or similar network component of a wireless communication system.

  The 3rd Generation Partnership Project (3GPP (R)) Long Term Evolution (LTE (R)) is an evolution of the Global System for Mobile Communications (GSM (R)) and Universal Mobile Telecommunications System (UMTS) It represents a major advance in cellular technology. The LTE physical layer (PHY) provides a highly efficient way to transfer both data and control information between a base station such as an evolved Node B (eNB) and a mobile entity such as a UE. In conventional applications, the method for facilitating high bandwidth communication for multimedia has been single frequency network (SFN) operation. The SFN communicates with the subscriber UE using a radio transmitter such as eNB, for example. In unicast operation, each eNB is controlled to transmit a signal carrying information intended for one or more specific subscriber UEs. The uniqueness of unicast signaling enables person-to-person services such as voice calls, text messaging, or video calls.

  Dynamic Adaptive Streaming Over HTTP (DASH) enables a service that delivers continuous (streaming) media content via the Hypertext Transfer Protocol (HTTP), which is a unicast transport protocol. The handling of simultaneous unicast and broadcast distribution of DASH content and the transition between unicast and broadcast distribution and vice versa is not fully defined. Latency associated with broadcast delivery also poses additional challenges for such transitions. Information about broadcast availability adjustments (for example, availability delay or advance) depends on the deployment of the network and mobile to achieve a seamless transition between unicast and broadcast delivery. Should be made available to the entity. Information related to the delivery of a DASH segment via broadcast may need to be delivered to the DASH client, such as geographical constraints on the receipt of a unicast version of the content, which representation of the content ) Is available via broadcast in a given area, information that allows discovery of appropriate broadcast transport sessions carrying different representations of the same content, and offload unicast DASH Information that supports an on-demand DASH service to traffic may be included. Therefore, there is also a need for techniques for conveying parameters that support broadcast delivery without affecting DASH core unicast functionality.

  Exemplary embodiments of the present invention shown in the drawings are summarized below. These and other embodiments are described more fully in the Detailed Description section. It should be understood, however, that the intention is not to limit the invention to the form described in the summary or detailed description of the invention.

  Note that broadcast and multicast are synonymous herein. Note further that in some broadcast networks, broadcast streamed content may also be made available or accessed via unicast. Such alternative delivery of content provides a unicast fallback technique for accessing content for broadcast streaming services while not within broadcast coverage. One problem is that broadcast DASH services can deliver different versions of content (eg, different representations) at different locations. Various representations may be available only via broadcast, only available via unicast, or may be available via both unicast and broadcast.

  According to one or more aspects of the embodiments described herein, a method operable by a mobile entity in a wireless communication system is provided. The method can include receiving a media presentation description (MPD) that includes parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions. The method can include determining whether a broadcast transmission or a unicast transmission is suitable for receiving a data segment. The method can include selecting a given representation from among multiple representations of content based on mobile entity criteria. The method can include receiving a data segment for a given representation based at least in part on parameters for the determined one of broadcast transmission and unicast transmission. In a related aspect, an electronic device (eg, a mobile entity or component thereof) can be configured to perform the methods described above.

  According to one or more aspects of the embodiments described herein, another method operable by a mobile entity is provided. The method includes receiving system information including (a) DASH MPD and (b) parameters for receiving data segments for multiple representations of content via broadcast and unicast transmissions. be able to. The method may include selecting a given representation from among multiple representations of content based on parameters for broadcast transmission and mobile entity criteria. The method can include receiving a data segment for a given representation in a broadcast file delivery session. In related aspects, an electronic device (eg, a mobile entity or component thereof) may be configured to perform the methods described above.

  According to one or more aspects of the embodiments described herein, a method operable by a network entity is provided. The method can include transmitting an MPD that includes parameters for reception of a data segment for multiple representations of content via broadcast and unicast transmissions. The method can include receiving a request for a given representation of content. The method can include transmitting a data segment for a given representation in a file delivery session via broadcast transmission or unicast transmission based at least in part on the parameters. In related aspects, an electronic device (eg, a network entity or component thereof) may be configured to perform the methods described above.

  To the accomplishment of the above and related ends, one or more embodiments include the features fully described below and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative aspects of the one or more embodiments. However, these aspects are merely illustrative of the various ways in which the principles of the various embodiments may be used, and the described embodiments include all such aspects and their equivalents. Shall be.

1 is a block diagram conceptually illustrating an example of a telecommunications system. 1 is a block diagram conceptually illustrating an example of a downlink frame structure in a telecommunications system. FIG. 1 is a block diagram conceptually illustrating a design of a base station / eNB and a UE configured in accordance with one aspect of the present disclosure. FIG. FIG. 4 is a signaling frame illustrating an example of symbol assignment for unicast and multicast signals. The figure which shows the MBSFN area in a MBMS over single frequency network (MBSFN) service area. 1 is a block diagram illustrating components of a wireless communication system for providing or supporting MBSFN services. FIG. The figure which shows one Embodiment of DASH MPD. The figure which shows one Embodiment of BaseURL in DASH MPD. The figure which shows one Embodiment of the bundle description in eMBMS USD. FIG. 3 shows an embodiment of a USD for eMBMS. FIG. 4 shows another embodiment of USD for eMBMS. The figure which shows one Embodiment of the deliveryMethod description in eMBMS USD. The figure which shows one Embodiment of several BaseURL in a MPD level. The figure which shows one Embodiment of a DASH segment availability timeline. The figure which shows an example of the implicit consideration regarding a protection period. FIG. 4 shows an exemplary timeline for UC-BC transitions. FIG. 6 shows examples of various playback delays for a unicast retrieval segment. FIG. 4 shows examples of various playback delays for broadcast fetch segments. FIG. 4 shows an exemplary timeline for BC-UC transitions. FIG. 6 shows segment playback based on broadcast fetching segments vs. unicast fetching segments. FIG. 4 shows multiple broadcast transmissions for a single service. FIG. 4 shows conveying parameters via an XML string for multiple broadcast transmissions for a single service. FIG. 4 illustrates an example method that can be performed by a mobile entity. FIG. 22B shows a further aspect of the method of FIG. 22A. FIG. 22B shows a further aspect of the method of FIG. 22A. FIG. 22B shows a further aspect of the method of FIG. 22A. FIG. 22 shows an embodiment of an apparatus according to the method of FIGS. 22A-22D. FIG. 7 is another example method that can be performed by a mobile entity in a wireless system. FIG. 25 shows an embodiment of an apparatus according to the method of FIG. FIG. 4 illustrates an example method that can be performed by a network entity in a wireless system. FIG. 27 shows an embodiment of an apparatus according to the method of FIG.

Detailed description

  The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

  The techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000. UTRA includes Wideband CDMA (WCDMA®) and other variants of CDMA. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). The OFDMA network includes evolved UTRA (E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, flash OFDMA. Wireless technology such as can be implemented. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE Advanced (LTE-A) are newly released UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above, as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

  FIG. 1 shows a wireless communication network 100 that may be an LTE network. The wireless network 100 may include a number of eNBs 110 and other network entities. An eNB may be a station that communicates with the UE and may also be referred to as a base station, Node B, access point, or other terminology. Each eNB 110a, 110b, 110c may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of an eNB and / or an eNB subsystem serving this coverage area, depending on the context in which the term is used.

  An eNB may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. Macrocells can cover a relatively large geographic area (eg, a few kilometers in radius) and can allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femtocell can cover a relatively small geographic area (eg, a home) and has a UE associated with the femtocell (eg, a UE in a limited subscriber group (CSG), a UE for a user in the home, etc.) ) To allow limited access. An eNB for a macro cell may be referred to as a macro eNB. An eNB for a pico cell may be referred to as a pico eNB. An eNB for a femto cell may be referred to as a femto eNB or a home eNB (HNB). In the example shown in FIG. 1, eNBs 110a, 110b, and 110c may be macro eNBs for macro cells 102a, 102b, and 102c, respectively. eNB 110x may be a pico eNB for pico cell 102x serving UE 120x. eNBs 110y and 110z may be femto eNBs for femto cells 102y and 102z, respectively. An eNB may support one or multiple (eg, three) cells.

  The wireless network 100 may also include a relay station 110r. A relay station receives a transmission of data and / or other information from an upstream station (eg, eNB or UE) and sends a transmission of that data and / or other information to a downstream station (eg, UE or eNB) It is. A relay station may also be a UE that relays transmissions for other UEs. In the example shown in FIG. 1, relay station 110r may communicate with eNB 110a and UE 120r to facilitate communication between eNB 110a and UE 120r. A relay station may be called a relay eNB, a relay, or the like.

  The wireless network 100 may be a heterogeneous network including various types of eNBs, eg, macro eNB, pico eNB, femto eNB, relay, and the like. These different types of eNBs may have different effects on different transmit power levels, different coverage areas, and interference within the wireless network 100. For example, a macro eNB may have a high transmission power level (eg, 20 watts), while a pico eNB, femto eNB, and relay may have a lower transmission power level (eg, 1 watt).

  The wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, eNBs can have similar frame timing, and transmissions from different eNBs can be aligned approximately in time. For asynchronous operation, eNBs can have different frame timings, and transmissions from different eNBs may not be aligned in time. The techniques described herein can be used for both synchronous and asynchronous operations.

  Network controller 130 may couple to a set of eNBs and provide coordination and control for these eNBs. The network controller 130 can communicate with the eNB 110 via the backhaul. The eNBs 110 may also communicate with each other directly or indirectly via, for example, a wireless backhaul or a wired backhaul.

  UE 120 may be distributed throughout wireless network 100, and each UE may be fixed or mobile. A UE may also be called a terminal, a mobile station, a subscriber unit, a station, and so on. A UE may be a mobile phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, or other mobile entity. A UE may be able to communicate with macro eNBs, pico eNBs, femto eNBs, relays, or other network entities. In FIG. 1, a solid line with double arrows indicates a desired transmission between a UE and a serving eNB, which is an eNB designated to serve the UE, on the downlink and / or uplink. The dashed line with double arrows indicates interfering transmissions between the UE and the eNB.

  LTE utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed and the total number of subcarriers (K) may depend on the system bandwidth. For example, K may be equal to 128, 256, 512, 1024, or 2048, respectively, for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz). The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz, and 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively. There can be a band.

  FIG. 2 shows a downlink frame structure used in LTE. The downlink transmission timeline can be divided into units of radio frames. Each radio frame may have a predetermined duration (eg, 10 milliseconds (ms)) and may be divided into 10 subframes with indices 0-9. Each subframe can include two slots. Thus, each radio frame can include 20 slots with indices 0-19. Each slot has L symbol periods, eg, 7 symbol periods for a normal cyclic prefix (CP) as shown in FIG. 2, or 6 symbol periods for an extended cyclic prefix. Can be included. A normal CP and an extended CP may be referred to herein as different CP types. 2L symbol periods in each subframe can be assigned 0-2L-1 indices. The available time frequency resources can be divided into resource blocks. Each resource block may cover N subcarriers (eg, 12 subcarriers) in one slot.

  In LTE, the eNB can send a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for each cell in the eNB. The primary synchronization signal and the secondary synchronization signal are respectively in symbol periods 6 and 5 in each of subframes 0 and 5 of each radio frame having a normal cyclic prefix, as shown in FIG. Can send. The synchronization signal can be used by the UE for cell detection and acquisition. The eNB may send a physical broadcast channel (PBCH) in symbol periods 0 to 3 in slot 1 of subframe 0. The PBCH can carry certain system information.

  While the eNB is shown in the entire first symbol period of FIG. 2, it may send a physical control format indicator channel (PCFICH) in only a portion of the first symbol period of each subframe. it can. The PCFICH can carry several (M) symbol periods used for the control channel, where M can be equal to 1, 2 or 3, and can vary from subframe to subframe. is there. M can also be equal to 4 for small system bandwidths, eg, with less than 10 resource blocks. In the example shown in FIG. 2, M = 3. The eNB may send a physical HARQ indicator channel (PHICH) and a physical downlink control channel (PDCCH) in the first M symbol periods of each subframe (M = 3 in FIG. 2). The PHICH can carry information that supports hybrid automatic retransmission (HARQ). The PDCCH can carry information on resource allocation for the UE and control information for the downlink channel. Although not shown in the first symbol period of FIG. 2, it should be understood that PDCCH and PHICH are also included in the first symbol period. Similarly, PHICH and PDCCH are also in both the second and third symbol periods, but are not shown as such in FIG. The eNB may send a physical downlink shared channel (PDSCH) during the remaining symbol periods of each subframe. The PDSCH can carry data for UEs scheduled for data transmission on the downlink. Various signals and channels in LTE are described in the published 3GPP TS 36.211 entitled “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation”.

  The eNB may send PSS, SSS, and PBCH at the system bandwidth center 1.08 MHz used by the eNB. The eNB may send PCFICH and PHICH over the entire system bandwidth within each symbol period in which these channels are sent. An eNB may send a PDCCH to a group of UEs in some part of the system bandwidth. An eNB may send a PDSCH to a specific UE in a specific part of the system bandwidth. The eNB can send PSS, SSS, PBCH, PCFICH, and PHICH to all UEs in a broadcast manner, can send a PDCCH to a specific UE in a unicast manner, and can also send a specific UE The PDSCH can be sent to the unicast system.

  Several resource elements may be available in each symbol period. Each resource element can cover one subcarrier within one symbol period and can be used to send one modulation symbol, which can be real-valued or complex-valued. Resource elements that are not used for the reference signal within each symbol period may be placed in a resource element group (REG). Each REG can include four resource elements within one symbol period. The PCFICH can occupy four REGs that can be approximately equally spaced in frequency in symbol period 0. The PHICH can occupy three REGs that can be spread over frequency in one or more configurable symbol periods. For example, the three REGs for PHICH may all belong to symbol period 0 or may be spread in symbol periods 0, 1 and 2. The PDCCH may occupy 9, 18, 32, or 64 REGs that may be selected from the available REGs in the first M symbol periods. Only some combinations of REGs can be allowed for PDCCH.

  The UE can know the specific REG used for PHICH and PCFICH. The UE can search for various combinations of REGs for PDCCH. The number of combinations to search is usually less than the number of combinations allowed for the PDCCH. The eNB may send a PDCCH to the UE in any of the combinations that the UE will search.

  The UE may be in multiple eNB coverage. One of these eNBs can be selected to serve the UE. The serving eNB may be selected based on various criteria such as received power, path loss, signal to noise ratio (SNR).

  FIG. 3 shows a block diagram of a design of base station / eNB 110 and UE 120, which may be one of base stations / eNBs and one of UEs in FIG. For the restricted association scenario, the base station 110 may be the macro eNB 110c of FIG. 1 and the UE 120 may be the UE 120y. Base station 110 may also be some other type of base station. The base station 110 may include antennas 334a to 334t, and the UE 120 may include antennas 352a to 352r.

  At base station 110, transmit processor 320 can receive data from data source 312 and receive control information from controller / processor 340. The control information may be for PBCH, PCFICH, PHICH, PDCCH, etc. The data may be for PDSCH and the like. The processor 320 can process (eg, encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 320 may also generate reference symbols for PSS, SSS, and cell specific reference signals, for example. A transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (eg, precoding) on data symbols, control symbols, and / or reference symbols, if applicable, and output The symbol stream can be provided to modulators (MODs) 332a-332t. Each modulator 332 may process a respective output symbol stream (eg, for OFDM, etc.) to obtain an output sample stream. Each modulator 332 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 332a through 332t can be transmitted via antennas 334a through 334t, respectively.

  In UE 120, antennas 352a-352r can receive downlink signals from base station 110 and can provide received signals to demodulators (DEMODs) 354a-354r, respectively. Each demodulator 354 may adjust (eg, filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 354 may further process the input samples (eg, for OFDM, etc.) to obtain received symbols. MIMO detector 356 may obtain received symbols from all demodulators 354a-354r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. Receive processor 358 processes (eg, demodulates, deinterleaves, and decodes) the detected symbols, provides decoded data of UE 120 to data sink 360, and provides decoded control information to controller / processor 380. Can do.

  On the uplink, at UE 120, transmit processor 364 may receive and process data from data source 362 (eg, for PUSCH) and control information from controller / processor 380 (eg, for PUCCH). Can be received and processed. The processor 364 can also generate a reference symbol for the reference signal. Symbols from transmit processor 364 are precoded by TX MIMO processor 366, where applicable, and further processed by modulators 354a-354r (eg, for SC-FDM, etc.) for transmission to base station 110. Can do. At base station 110, the uplink signal from UE 120 is received by antenna 334, processed by demodulator 332, detected by MIMO detector 336 when applicable, and further processed by receive processor 338 to allow UE 120 to The decoded data and control information to be sent can be obtained. The processor 338 can provide the decoded data to the data sink 339 and provide the decoded control information to the controller / processor 340.

  Controllers / processors 340 and 380 may direct the operation at base station 110 and UE 120, respectively. Processor 340 and / or other processors and modules at base station 110 may perform or direct the execution of various processes for the techniques described herein (see FIG. 26). . A processor 380 and / or other processors and modules at UE 120 may perform or direct the execution of various processes for the techniques described herein (FIGS. 22A-22D and (See FIG. 24). Memories 342 and 382 may store data and program codes for base station 110 and UE 120, respectively. A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

EMBMS and unicast signaling in single frequency networks: One technique that facilitates high bandwidth communication for multimedia has been single frequency network (SFN) operation. Specifically, multimedia broadcast multicast, also known as evolved MBMS (eMBMS) (including, for example, what has recently become known as Multimedia Broadcast Single Frequency Network (MBSFN) in the LTE context) Service (MBMS) and MBMS for LTE can utilize such SFN operation. The SFN communicates with the subscriber UE using a radio transmitter such as eNB, for example. Since groups of eNBs can transmit information in a synchronous manner, the signals reinforce each other rather than interfering with each other. In the context of eMBMS, shared content is transmitted from multiple eNBs in the LTE network to multiple UEs. Thus, within a given eMBMS area, the UE can receive eMBMS signals from any eNB within radio range as part of the eMBMS service area and MBSFN area. However, in order to decode the eMBMS signal, each UE receives multicast control channel (MCCH) information from the serving eNB via a non-eMBMS channel. MCCH information changes with time, and notification of the change is provided through another non-eMBMS channel, PDCCH. Thus, to decode eMBMS signals within a particular eMBMS area, each UE is provided with MCCH and PDCCH signals by one of the eNBs in the area.

  According to aspects of the disclosed subject matter, a wireless network (eg, 3GPP network) having functionality related to single carrier optimization for eMBMS is provided. eMBMS provides an efficient way to transmit shared content from an LTE network to multiple mobile entities such as UEs.

  For eMBMS physical layer (PHY) for LTE Frequency Division Duplex (FDD), the channel structure comprises time division multiplexing (TDM) resources that divide eMBMS and unicast transmissions on a mixed carrier. In some cases, this allows flexible and dynamic spectrum usage. Currently, a subset of subframes (up to 60%), known as Multimedia Broadcast Single Frequency Network (MBSFN) subframes, can be reserved for eMBMS transmissions. Thus, current eMBMS designs allow up to 6 out of 10 subframes for eMBMS.

  An example of subframe allocation for eMBMS is shown in FIG. 4, which shows the existing allocation of MBSFN reference signals to MBSFN subframes in the case of single carrier. The components depicted in FIG. 4 correspond to the components shown in FIG. 2, which shows the individual subcarriers in each slot and resource block (RB). In 3GPP LTE, the RB spans 12 subcarriers over a 0.5 ms slot period, with each subcarrier having a bandwidth of 15 kHz and a total of 180 kHz per RB. Subframes may be allocated for unicast or eMBMS, for example, in a sequence of subframes labeled 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9. Subframes 0, 4, 5, and 9 may be excluded from eMBMS in FDD. Also, subframes 0, 1, 5, and 6 may be excluded from eMBMS in time division duplex (TDD). More specifically, subframes 0, 4, 5, and 9 can be used for PSS / SSS / PBCH / Paging / System Information Block (SIB) and unicast services. The remaining subframes in the column, eg, subframes 1, 2, 3, 6, 7, and 8, can be configured as eMBMS subframes.

  Continuing with reference to FIG. 4, within each eMBMS subframe, the first one or two symbols may be used for unicast reference symbols (RS) and control signaling. The CP length of the first one or two symbols may follow the CP length of subframe 0. If the CP lengths are different, a transmission gap may occur between the first one or two symbols and the eMBMS symbol. In a related aspect, utilization of the entire eMBMS bandwidth may be 42.5% considering RS overhead (eg, 6 eMBMS subframes and 2 control symbols in each eMBMS subframe). . Known techniques for providing MBSFN RSs and unicast RSs typically assign MBSFN RSs to MBSFN subframes (as shown in FIG. 4) and assign unicast RSs separately to non-MBSFN subframes. With that. More specifically, as FIG. 4 shows, the extended CP of the MBSFN subframe includes an MBSFN RS, but does not include a unicast RS. The present technology is not limited to the particular frame allocation scheme illustrated by FIGS. 2 and 4 presented by way of example and not limitation. As used herein, a multicast session or multicast broadcast can use any suitable frame allocation scheme.

eMBMS Service Area: FIG. 5 shows a system 500 that includes an MBMS service area 502 that includes multiple MBSFN areas 504, 506, and 508, which themselves include multiple cells or base stations 510. As used herein, “MBMS service area” refers to a group of wireless transmission cells in which a particular MBMS service is available. For example, certain sports programs or other programs may be broadcast by base stations in the MBMS service area at certain times. The area where a specific program is broadcast defines the MBMS service area. The MBMS service area may be composed of one or more “MBSFN areas” indicated at 504, 506 and 508. As used herein, an MBSFN area refers to a group of cells (eg, cell 510) that are currently broadcasting a particular program in a synchronous manner using the MBSFN protocol. The “MBSFN synchronization area” is interconnected and configured to operate in a synchronous manner and to broadcast a specific program using the MBSFN protocol, whether or not it is currently doing, Refers to a group of cells. Each eNB can belong to only one MBSFN synchronization area on a given frequency layer. It is worth noting that the MBMS service area 502 can include one or more MBSFN synchronization areas (not shown). Conversely, the MBSFN synchronization area can include one or more MBSFN areas or MBMS service areas. In general, an MBSFN area is composed of all or part of a single MBSFN synchronization area and is located within a single MBMS service area. Overlap between different MBSFN areas is supported, and a single eNB can belong to several different MBSFN areas. For example, up to 8 independent MCCHs can be configured in SIB-13 to support membership in different MBSFN areas. An MBSFN area reserved cell or base station is a cell / base station in the MBSFN area that does not contribute to MBSFN transmission, eg, a cell near the boundary of the MBSFN synchronization area, or a cell that is not required for MBSFN transmission because of its location.

eMBMS System Components and Functions: FIG. 6 shows functional entities of a wireless communication system 600 that provides or supports MBSFN services. For quality of service (QoS), system 600 uses guaranteed bit rate (GBR) type MBMS bearers, and the maximum bit rate (MBR) is equal to GBR. These components are illustrated and described by way of example and do not limit the inventive concept described herein, which is another architectural and functional for distributing and controlling multicast transmissions. The distribution can be adopted.

  System 600 may include an MBMS gateway (MBMS GW) 616. The MBMS GW 616 controls Internet Protocol (IP) multicast distribution of MBMS user plane data to the eNodeB 604 via the M1 interface, and one eNB 604 of many possible eNBs is shown. In addition, the MBMS GW controls IP multicast distribution of MBMS user plane data to the UTRAN radio network controller (RNC) 620 via the M1 interface, and one UTRAN RNC 620 of many possible RNCs is shown. . The M1 interface is associated with MBMS data (user plane) and uses IP for data packet delivery. The eNB 604 may provide MBMS content to the user equipment (UE) / mobile entity 602 via the E-UTRAN Uu interface. The RNC 620 may provide MBMS content to the UE mobile entity 622 via the Uu interface. The MBMS GW 616 may further perform MBMS session control signaling, eg, MBMS session start and session stop, via the mobility management entity (MME) 608 and the Sm interface. The MBMS GW 616 further provides an interface to the entity using the MBMS bearer through the SG-mb (user plane) reference point and provides an interface to the entity using the MBMS bearer through the SGi-mb (control plane) reference point. be able to. The SG-mb interface carries MBMS bearer service specific signaling. The SGi-mb interface is a user plane interface for MBMS data distribution. MBMS data distribution may be performed by IP unicast transmission, which may be the default mode, or by IP multicasting. The MBMS GW 616 can provide control plane functions to the MBMS over UTRAN via the Serving General Packet Radio Service Support Node (SGSN) 618 and the Sn / Iu interface.

  System 600 can further include a multicast coordination entity (MCE) 606. The MCE 606 may perform admission control functions for MBMS content and allocate time and frequency radio resources used by all eNBs in the MBSFN area for multi-cell MBMS transmission using MBSFN operations. The MCE 606 can determine the radio configuration for the MBSFN area, eg, modulation and coding scheme. The MCE 606 can manage multiplexing of eMBMS services by scheduling and controlling user plane transmission of MBMS content and determining which services should be multiplexed in which multicast channel (MCH). The MCE 606 can participate in MBMS session control signaling with the MME 608 through the M3 interface, and can provide the control plane interface M2 to the eNB 604.

  System 600 can further include a broadcast multicast service center (BM-SC) 612 in communication with content provider server 614. The BM-SC 616 may handle the ingestion of multicast content from one or more sources, such as content provider 614, and provide other higher level management functions as described below. These functions can include, for example, membership functions including authentication and initiation of MBMS services for identified UEs. The BM-SC 616 may further perform distribution including MBMS session and transmission functions, live broadcast scheduling, and MBMS and related distribution functions. The BM-SC 612 may further provide service advertisements and descriptions, such as advertising content available for multicast. A separate packet data protocol (PDP) context may be used to carry control messages between the UE and the BM-SC. The BM-SC further provides security functions such as key management, manages charging of content providers according to parameters such as data volume and QoS, and content synchronization for MBMS in UTRAN and in E-UTRAN in broadcast mode And provide header compression for MBSFN data in UTRAN. The BM-SC 612 can indicate session start, update, and stop to the MBMS-GW 616, including session attributes such as QoS and MBMS service areas.

  System 600 can further include a multicast management entity (MME) 608 in communication with MCE 606 and MBMS-GW 616. The MME 608 may provide a control plane function for MBMS via E-UTRAN. In addition, the MME may provide multicast related information defined by the MBMS-GW 616 to the eNBs 604, 620. The Sm interface between the MME 608 and the MBMS-GW 616 may be used to carry MBMS control signaling, eg, session start and session stop signals.

  System 600 may further include a packet data network (PDN) gateway (GW) 610 (sometimes abbreviated as P-GW). The P-GW 610 may provide an evolved packet system (EPS) bearer between the UE 602 and the BM-SC 612 for signaling and / or user data. Thus, the P-GW can receive uniform resource locator (URL) based requests originating from the UE associated with the IP address assigned to the UE. The BM-SC 612 may also be linked to one or more content providers via the P-GW 610, and the P-GW 610 may communicate with the BM-SC 612 via the IP interface.

  In accordance with one or more aspects of the embodiments described herein, via a serviceLocation attribute in a media presentation description (MPD) for dynamic adaptive streaming over HTTP (DASH) content, Techniques are provided for signaling the use of several URLs that support directing unicast dynamic adaptive streaming over HTTP (DASH) access to an on-demand broadcast version of the content. DASH enables a service that delivers continuous (streaming) media content via Hypertext Transfer Protocol (HTTP). The specification for DASH mainly defines two formats: MPD and segment format.

  FIG. 7 shows an embodiment 700 of a high level extensible markup language (XML) schema structure for MPD. FIG. 8 depicts a schema 800 for illustrating the structure for BaseURL that associates the serviceLocation and byteRange attributes with a base URL. The list of BaseURL elements can be described in MPD, at the MPD Period level, at the Adaptation Set level, and at the Representation level.

  In a related aspect, the BaseURL can serve as a Base Uniform Resource Identifier (URL). The URL at each level of the MPD can be resolved according to RFC 3986 for the BaseURL element specified at that level of the document (eg, MPD) or at a higher level. URL resolution applies to all URLs found in MPD documents, particularly for initialization and media segments that are of interest to the disclosure described herein. Multiple BaseURL elements can be provided to specify one or more common locations where the same segment can be accessed. In the absence of other criteria, the DASH client may use the first BaseURL element as the base URI.

  Referring to FIG. 8, the serviceLocation attribute for the BaseURL element is such that a BaseURL element with the same serviceLocation value may have their URL resolution for services at a common network location, such as a common content distribution network, for example. Specifies the relationship between BaseURLs. For example, a DASH client retrieves segments for a representation (eg, various versions of a given content such as resolution, language, etc.) but (the access wireless network cannot continue to support current representation requirements on bandwidth If it is decided to retrieve a segment from a different representation, it is possible to select a BaseURL for the new representation that has the same serviceLocation value as the previous representation. Use of this serviceLocation attribute indicates that retrieving a segment for a new representation will experience similar performance (eg, availability adjustment) as a segment retrieved from a previous representation via a BaseURL with the same serviceLocation value. , Acting as a hint to the device.

Problems with DASH broadcast over eMBMS: Continuous delivery of DASH media segments (eg, media files) constitutes a media streaming service that may include continuous transmission of media files or DASH media segments. Although streaming delivery of media using RTP is possible, the RTP transport is usually not suitable for DASH segments.

  In some broadcast networks, broadcast streamed content can also be made available and accessed via unicast, such as in the case of RTP streaming broadcasts within eMBMS, for example. This alternative distribution of content provides a unicast fallback technique for accessing content for broadcast streaming services while not in broadcast coverage. A fallback technique for accessing files of a broadcast file delivery service is usually not defined in a broadcast network.

  Broadcast delivery of DASH segments typically uses a transport protocol employed in broadcast file delivery services (eg, FLUTE), which requires an alternative unicast fallback to access the contents of the broadcast DASH service. Is done.

  There are several issues to consider regarding DASH broadcasts such as via eMBMS. One problem is that broadcast DASH services can deliver different versions of content (eg, different representations) at different locations. Various representations may be available only via broadcast, only available via unicast, or may be available via both unicast and broadcast. Therefore, a technique is needed to signal which representations of services are available for the current desired / available broadcast or unicast transport.

  Another issue is that DASH segment transport may lead to further broadcast availability adjustments from the time segment (eg, procrastination or advancement of availability) may be available for retrieval via unicast. And broadcast availability adjustment is the broadcast latency in such a scenario. The availability of a segment received via broadcast delivery may lead to further availability adjustments from the time that the segment can be received via unicast delivery, which means that from one mode delivery to another mode delivery. It can lead to problems when switching to delivery (eg, from broadcast to unicast). In order to allow seamless unicast-to-broadcast (UC-BC) and broadcast-to-unicast (BC-UC) transitions as devices enter and exit broadcast coverage, information on broadcast availability adjustments is provided to DASH clients. Should be communicated.

  Another problem is that representations available via unicast may only be accessible in some geographic areas. Such geographical constraints should be signaled to the DASH client. Yet another problem is that the broadcast DASH service can carry multiple representations through various FLUTE sessions, and thus a technique is needed to identify which FLUTE session allows the desired representation. The For example, multiple representations may be available via broadcast in a given area to provide alternative language or video resolution options. Choosing to receive only the expressions of interest improves the battery life of the mobile entity.

  In some situations, it may be desirable to create a broadcast DASH service on demand to reduce the load on system resources caused by multiple users retrieving DASH content via unicast. It may also be necessary to signal to the device that it is necessary to switch from unicast reception to broadcast reception using a different URL. Accordingly, solutions for addressing these issues are described below.

Carrying signaling information: To address the above-mentioned problems, several parameters can be signaled to the DASH client for support of the broadcast DASH segment. Such parameters can be signaled as separate new parameters in the MPD. However, it may be undesirable or unacceptable to further extend the MPD definition to add support for these additional parameters used only in some scenarios of broadcast DASH.

  Thus, the proposed solution described herein can signal these parameters as a uniform resource name (URN) under a registered Namespace Identifier (NID) —for example, 3GPP In this case, the NID is 3 gpp, and as a result, the URN under 3GPP control is in the form of urn: 3 gpp: {3 gpp-urn}. In addition, the URN namespace specific string (NSS) should be encoded as a colon-separated list of key = value pairs carried as a string in the BaseURL serviceLocation attribute etc. Embodiments are provided.

  A possible alternative approach may include using a comma-separated list of key = value pairs carried as a string in the serviceLocation attribute of BaseURL. Another alternative approach may include encoding these parameters in the XML structure for each XML schema and carrying that XML encoded data in the BaseURL serviceLocation attribute. Yet another approach is to add additional attributes or elements to the XML schema of the MPD to capture a list of parameters, comma-separated list carried in the URN, or XML code in the serviceLocation attribute Or adding to parameters.

  In embodiments where URL encoding is used to convey a list of key = value pairs, the following rules or requirements may apply: The first string in the URN's NSS may be sl (for serviceLocation). For example, for a 3GPP URN, all URNs used in the serviceLocation attribute begin with “urn: 3gpp: sl”. The second string (or first key = value pair) may be “: transport =” + value string. For example, possible value strings may be “broadcast”, “unicast”, “both”. Other key = value pairs may follow “: transport =” + value strings, or variations thereof.

Unicast Availability of Broadcast DASH Services: DASH provides a unicast streaming framework that allows each DASH client to retrieve media services via HTTP and in a sequence according to the timeline defined in the MPD. The DASH segment can also be delivered to devices including DASH clients via a broadcast transport where media segments are broadcast via FLUTE or the like.

  A broadcast system typically includes system information (SI) metadata that describes services available via the broadcast transport. In an eMBMS broadcast system, the SI may be referred to as a user service description (USD), and may include metadata describing a service bundle, as shown in FIG. Note that other examples of SI are OMA broadcast service guides and MediaFLO service definition metadata. Referring to FIG. 10A, a USD embodiment for eMBMS is shown, where each service may be described with parameters. Such parameters may include a reference to the deliveryMethod list (detailed in FIG. 11) and the MPD uniform resource identifier (mpdURI) associated with the service. The mpdURI can bind the MPD to the service. FIG. 10B shows another embodiment of a USD for eMBMS, described in further detail below.

  FIG. 11 shows that for an eMBMS broadcast system, the SI for the broadcast system can provide information related to where a unicast version of the broadcast service content can be found. For eMBMS broadcast services that use RTP streaming, the SI provides a pointer to a session description protocol (SDP) file that describes a unicast RTP streaming version for the same content via the unicastAccessURI in the service's deliveryMethod. be able to. The presence of such a URL can also serve to signal that a unicast version of the service is available, while its absence indicates that the service is only available via broadcast. Show. Note that the parameters can be used to indicate unicast availability and the like. In the case of a broadcast DASH service, the attribute may be used to signal that a unicast representation is also available for the broadcast DASH service.

  For broadcast DASH services, explicit signaling of unicast availability via a separate URL in SI is generally undesirable. In the case of a broadcast DASH service, such explicit signaling may provide a reference to additional MPDs that describe the delivery of DASH segments via unicast. Since the exchange of MPD during playback tends to be disruptive, the MPD for broadcasting (eg, signaled via mpdURI for eMBMS USD) and the signaling via unicastAccessURI (eg, eMBMS USD) Using another MPD for unicast) does not allow a seamless transition from broadcast delivery to unicast delivery and vice versa. Therefore, it is desirable to embed unicast availability signaling in a single DASH MPD and take advantage of segment availability MPD signaling from different locations via a BaseURL element of the type shown in FIG. A method is provided for signaling to a DASH client which URL is to be used for unicast versus broadcast reception. In this way, when performing unicast reception of the broadcast service, the DASH client acts as a normal DASH client and takes out a segment using a unicast HTTP URL in a single MPD.

  This approach allows a single MPD to describe how services can be received via broadcast and unicast. A single MPD for broadcast and unicast reception also enables efficient support for seamless UC-BC and BC-UC receive handoffs when DASH clients enter and exit broadcast coverage.

  With regard to identifying segment URLs for unicast and broadcast reception, FIG. 12 provides a simplification of FIG. 7 showing a list of BaseURLs available at the MPD level, while removing other attributes and elements from the MPD. In unicast transport, multiple BaseURLs are typically used to signal that the same segment is accessible at multiple locations. The serviceLocation attribute can be defined to specify the relationship between the BaseURLs so that BaseURL elements with the same serviceLocation value may have their URL resolution for services at a common network location. This allows the DASH client to use serviceLocation when deciding which base URL to use when changing the representation. For example, the DASH client can select a new representation that has a BaseURL with the same serviceLocation attribute as the BaseURL used for the old representation.

  Multiple BaseURLs for a given representation describe the various locations from which segments for the service are available for retrieval, so for a DASH service through a broadcast system, the format is defined in terms of a serviceLocation string. Can be done. The format is either a given broadcast DASH service or any combination of their representations available only via broadcast, only available via unicast, or both unicast and broadcast Additional information can be provided to signal whether it is available via More specifically, when using the URN format, the serviceLocation attribute may include a string that begins with “urn: 3gpp: sl”, as described above. Subsequent strings can be concatenated to the first string starting with “:”, followed by a string that provides a key = value pair. The second string (or first key = value pair) may be “: transport =” + value string. Possible value strings may be “broadcast”, “unicast”, “both”. Other values may be used. An example string for the serviceLocation attribute may be urn: 3gpp: sl: transport = broadcast, or urn: 3gpp: sl: transport = unicast.

  Depending on the setting of the particular value string, other restrictions may be imposed on the use of the URL. For example, when the value string is “broadcast”, the URL derived from the use of the associated BaseURL element may be used when the DASH client receives the service via broadcast. More specifically, if there is only one BaseURL with the value string set to “broadcast”, the service or corresponding expression is only available via broadcast. If there is no BaseURL with the value string set to “broadcast”, the service or corresponding representation is not available via broadcast. If there are multiple BaseURLs with a value string set to “broadcast”, multiple broadcast transport (eg, FLUTE) sessions can be defined for the service, or the services described by the MPD can vary. Includes various representations that can be broadcast in different geographic areas. It is also possible that different representations can be broadcast at different locations. For illustrative purposes only, the following description assumes that there is only one broadcast representation. For compatibility with DASH clients that do not support the encoding scheme described herein, a BaseURL with a value string set to “broadcast” may be placed at the end of the list of BaseURLs. A BaseURL with a value string set to “broadcast” can point the DASH client to a local (ie, on the device) HTTP server by pointing to local host http: // localhost / etc.

  When the value string is “unicast”, the URL on the associated BaseURL element can be used when the DASH client accesses the service via unicast. If there is a multiple BaseURL with the value string set to “unicast”, the DASH client can use various methods to select one of the BaseURLs when accessing the service via unicast. Can be used. For example, one approach is to use BaseURLs starting with the first BaseURL in the list.

  When the value string is “both”, the URL on the associated BaseURL element is used to access the service, either via unicast or while in broadcast coverage. Can be done. If there is a BaseURL with the value string set to “both”, there is an additional BaseURL for the expression with the value string set to “broadcast” (assuming there is only one broadcast expression). do not do. The BaseURL with the value string set to “both” points the DASH client to an external (ie, a server accessible from the network) HTTP server. Thus, when the DASH client is in broadcast coverage and this URL is used, the device supports a technique for redirecting HTTP access to the local host.

Sample DASH Client Behavior: Based on the broadcast or unicast availability of DASH segments signaled in MPD, DASH client implementations can use the BaseURL serviceLocation information as follows: For initial reception in broadcast coverage, a DASH client may begin receiving broadcast (eg, eMBMS) DASH services while in broadcast coverage. The DASH client discovers which representations are available via the broadcast (assuming one broadcast representation) and returns either the string “: transport = broadcast” or “: transport = both”. The segment retrieval can be performed according to the behavior of a normal DASH client that selects a BaseURL having a serviceLocation attribute to include and / or uses the selected BaseURL. Determining which broadcast representation is currently available while in a broadcast can be done by matching the file name of the media segment signaled via the FLUTE transport.

  With respect to transitioning from broadcast coverage while consuming content via broadcast (BC-UC), a DASH client that receives a broadcast (eg, eMBMS) DASH service via broadcast transitions from broadcast reception of the segment Unicast reception can be started. The transition from broadcast coverage carries its broadcast DASH service more directly by the absence of SIB-13 available in the SIB in the LTE transport (Temporary Mobile Group Identification Information (TMGI) of the service). Can be detected when the LTE bearer is not available. In a related aspect, a BaseURL for a representation with a serviceLocation attribute that can then be supported by the unicast bandwidth and that includes either the string “: transport = unicast” or “: transport = both”. DASH client can continue to receive the current representation. Otherwise, the DASH client can change to a different representation in which there is a BaseURL with a serviceLocation attribute that includes either the string “: transport = unicast” or “: transport = both”. If there are multiple such BaseURLs, the DASH client can select one. In a further related aspect, the DASH client can perform segment fetching according to normal DASH client behavior using the selected BaseURL.

  With respect to initial reception from broadcast coverage (eg, when SIB-13 is not in the System Information Block (SIB) in LTE transport), the DASH client is able to communicate via unicast while not in broadcast coverage. Unicast reception of available broadcast (eg, eMBMS) DASH services can be initiated. The DASH client retrieves the segment, determines the available bandwidth to select the expression to be played, and contains a string of either “: transport = unicast” or “: transport = both” Selecting a BaseURL with a serviceLocation attribute and / or performing segment retrieval according to the behavior of a normal DASH client using the selected BaseURL.

  With respect to transitioning to broadcast reception while consuming content via unicast (UC-BC), a DASH client currently receiving a broadcast (eg, eMBMS) DASH service via unicast transitions to broadcast coverage. Then, the segment reception via the broadcast can be started. In a related aspect, the DASH client can discover what representations are available in broadcast coverage, for example, via media file names described in the FLUTE transport. In a further related aspect, the DASH client can continue to receive the current representation if the representation being broadcast is the same as the representation being accessed via unicast. In this case, the DASH client can select a BaseURL having a serviceLocation attribute including a character string of “: transport = broadcast” or “: transport = both”. In a further related aspect, the DASH client can transition to a broadcast representation and select a BaseURL that has a serviceLocation attribute that includes a string of either “: transport = broadcast” or “: transport = both”. In a further related aspect, the DASH client can perform segment fetching according to normal DASH client behavior using the selected BaseURL.

Geographic constraints on unicast availability of broadcast DASH services : Contractual obligations or other restrictions that limit unicast availability of service content to some geographic areas, even when broadcast DASH services are available via unicast There may be requirements.

  Geographic constraints on unicast availability can be indicated in the BaseURL in the MPD for broadcast DASH services by adding another value string. For example, a BaseURL in the MPD for a broadcast DASH service that is associated with a serviceLocation attribute containing either the string “: transport = unicast” or “: transport = both” is also transported in the serviceLocation attribute. Through additional string formats, geographic availability constraints for unicast reception can be indicated. Specifically, the serviceLocation attribute can include a string starting with “urn: 3gpp: sl” when using the urn format, to indicate that the service is available via unicast, Either “: transport = unicast” or “: transport = both” can be included.

  The string “: uGeo3GppCellID =” + CellID string (in key = value pair format) may indicate the 3GPP cell ID through which the service can be consumed via unicast via the CellID string. An exemplary string for the serviceLocation attribute may be urn: 3gpp: sl: transport = unicast: uGeo3GppCellID = 345690.

  The string “: uGeo3Gpp2S + N + Z =” + SID_value + “+” + NID_value + “+” + PZID_value is a unicode service that connects the SID, NID, PZID, and “+” character strings. A 3GPP2 cell ID that may be consumed via a cast may be indicated. An exemplary string for the serviceLocation attribute may be urn: 3gpp: sl: transport = unicast: uGeo3Gpp2S + N + Z = 23 + 34 + 45. Thus, other strings can be defined to capture other geographic descriptors that may be available for the device.

  Based on the unicast availability of DASH segments signaled in the MPD and any geographical constraints regarding sample DASH client behavior, the DASH client implementation may use serviceLocation information on the BaseURL as follows: it can. For unicast reception without geographic constraints, the DASH client can begin receiving broadcast (eg, eMBMS) DASH service via unicast (ie, the device is not in broadcast coverage and “ : BaseTransport having a serviceLocation attribute including a character string of “: transport = unicast” or “: transport = both”. In a related aspect, the DASH client takes the segment and determines the available bandwidth to select the representation to be played, and either “: transport = unicast” or “: transport = both” string Selects a BaseURL with a serviceLocation attribute that includes, verifies that there is no BaseURL that includes a string whose serviceLocation begins with “: uGeo”, and / or segments according to the behavior of a normal DASH client using the selected BaseURL Retrieval can be performed.

  For unicast reception with geographic constraints while in a constrained area, the DASH client can begin receiving broadcast (eg, eMBMS) DASH services via unicast. In a related aspect, the DASH client takes the segment and determines the available bandwidth to select the representation to be played, and either ": transport = unicast" or ": transport = both" string Select a BaseURL that has a serviceLocation attribute containing, verify that there is a BaseURL containing a string where the serviceLocation starts with “: uGeo”, decide to understand the geographic information provided, and Segment retrieval can be performed according to the behavior of normal DASH clients that use the selected BaseURL while determining that they are inside and / or while in the described area.

  In situations where there is no unicast reception with geographical constraints while outside the constrained area, the DASH client cannot initiate reception of a broadcast (eg, eMBMS) DASH service via unicast. Service playback should stop. In a related aspect, the DASH client takes the segment and determines the available bandwidth to select the representation to be played, and either ": transport = unicast" or ": transport = both" string Select a BaseURL with a serviceLocation attribute that includes, verify that there is a BaseURL that includes a string whose serviceLocation starts with “: uGeo”, and determine that the UE (or DASH client) understands the provided geographic information And determines that the UE is not in the described area, determines that the provided geographic information cannot be understood, and / or selected BaseURL while not in the described area. Normal DASH using It is possible not to perform a segment extraction according to the behavior of Ianto.

Transport Availability Adjustment Considerations: As shown in FIG. 13, a timeline for DASH segment availability can be described in the MPD. In this specification, the MPD availabilityStartTime called MPD @ availabilityStartTime defines an absolute time from the time when the timeline is fixed. The start attribute in the first period of the MPD describes the duration from availabilityStartTime when the first segment becomes available for retrieval. The next segment for the same representation is spaced by the appropriate duration attribute in the MPD for that representation when the segment is the same duration (ie, each segment is spaced by the segment duration). FIG. 13 also shows that the broadcast transport and LTE bearer to the UE via FLUTE will later provide segment availability for FLUTE / LTE delivery than when described in the MPD timeline described above. Indicates that When the media file is delivered via FLUTE, the DASH client retrieves the segment from local storage as opposed to unicast retrieval from the remote server. The unicast availability timeline may be a timeline described by the MPD's availabilityStartTime and duration attributes.

  In a related aspect, the segment availability timeline in the broadcast distribution need not be later than the unicast distribution timeline, and may actually be before the segment availability via unicast distribution. In this case, the “advertised” unicast segment availability timeline is determined by the HTTP server / content delivery segment within the range of the MPD document, as given by the availabilityStartTime and duration attributes in the MPD. The “latest” time can be represented when it can be guaranteed to be available within the entity (for HTTP searches by DASH clients). a) reception of DASH segments at the BM-SC from the content source, b) transmission to the UE over the FLUTE across the LTE core network and RAN, and / or c) FLUTE reception, FEC decoding and segment recovery at the UE The availability time of a broadcast-delivered segment, including a combination of placement in a local HTTP cache for retrieval, can occur before the segment reaches a remote content delivery network (CDN) or HTTP server. Accordingly, the availability time of the broadcasted segment can be before, the same as, or after the unicast availability time. Note that MPD can be made available / provided to a large number of devices and can reference multiple access networks or CDNs from which the device owning the MPD can retrieve DASH segments. For example, the entity that created the MPD document and the DASH content delivery service provider can deliver the media presentation and individual representations as described by MPD.

  If the unicast segment availability time indication expressed by MPD @ availabilityStartTime is the latest available time across all HTTP servers governed by the MPD document, a separate unicast that can guarantee an earlier segment availability time. It is useful that the cast access network / CDN can signal the difference and allow the user to obtain and view DASH content sooner. In other words, MPD @ availabilityStartTime is the worst case of the unicast start time. There are different latencies for delivering content to different CDNs. This can be done by adjusting the availability timeline for the segment of the representation by the latency period defined for that representation. A parameter referred to herein as availabilityTimeAdjustment (shown as the protection period in FIG. 13) may be added under the BaseURL element to indicate adjustments from the MPD @ availabilityStartTime for a given access network / technology. it can. In other words, availabilityTimeAdjustment can generally be used to indicate the segment availability time over a given unicast or broadcast network compared to the worst case unicast availability time.

  In a related aspect, the availability adjustment for the entire Period can be a negative value with a sufficiently large absolute value, so that resources in the period are accessible before MPD @ availabilityStartTime, and earlier in the data segment Downloads can improve the user experience.

  Referring to FIG. 13, a fetchable timeline that can be used by a DASH client to fetch a segment via unicast is shown. The FLUTE availability timeline of FIG. 13 shows that there is an availability adjustment involved in, for example, broadcasting a segment via an eMBMS FLUTE session, which is FEC coding for segment packetization and transport , Due to broadcast of packets towards the UE, and FEC decoding and segment relocation on the device. For DASH clients accessing these broadcast segments, this availability adjustment will vary depending on whether the time availability for retrieving the segment is retrieved via unicast or via broadcast delivery. Can inform you that you should. A DASH client should take into account the protection period when requesting a segment via broadcast.

  The protection period indicates to the DASH client that the availability of the segment for retrieval via broadcast is delayed compared to the same segment retrieved via unicast.

Signaling of protection period for broadcast delivery of DASH segment: As mentioned above, BaseURL in MPD for broadcast DASH service with associated serviceLocation attribute is a letter indicating that the representation is available via broadcast The column “: transport = broadcast” or “: transport = both” may be included. To accommodate availability adjustments related to segment broadcast delivery, protection period information can also be conveyed using an additional string that is also transported in the serviceLocation attribute. For example, the serviceLocation attribute may include a string beginning with “urn: 3gpp: sl” when using the URN format, and the string “:” to indicate that the service is available via broadcast. transport = broadcast "or": transport = both ".

  The string “: pp =” + ppValue (in key = value pair format) signals the protection period via ppValue, for example in milliseconds or other time increments, and the DASH client via broadcast reception It can be adapted when a segment is requested. An exemplary string for the serviceLocation attribute may be urn: 3gpp: sl: transport = broadcast: pp = 50.

  Based on the broadcast availability and protection period information of the DASH segment signaled in the MPD with respect to the sample DASH client behavior, the DASH client implementation can use the serviceLocation information on the BaseURL as follows:

  For reception via broadcast delivery, the DASH client discovers which representations are available within the broadcast area and includes either the string “: transport = broadcast” or “: transport = both”. A Segment Availability Timeline in the MPD that selects a BaseURL having a serviceLocation attribute, determines a protection period indicated in a substring in the serviceLocation attribute starting with “: pp”, and / or uses the selected BaseURL Segment fetch can be performed according to, but adjust segment fetch by the additional ppValue milliseconds indicated in the string containing “: pp” (ie, postpone or To the teeth). This allows mobiles in a given geographic area to make requests for segments sooner than advertised, providing users with a lower latency experience or after being advertised Causes the mobile to retrieve the segment, thus avoiding an error condition when the segment is only available after it has been advertised in the MPD.

  For reception outside of broadcast coverage, the DASH client determines the available bandwidth to retrieve the segment and select an expression, and either ": transport = unicast" or ": transport = both" string If a BaseURL with a serviceLocation attribute containing is selected and / or segment fetching can be performed according to the exact segment availability timeline in the MPD using the selected BaseURL, no further segment fetching delay is performed.

Alternative to protection period signaling for broadcast distribution of DASH segments: An alternative to accommodate broadcast latency is shown in FIG. Rather than explicitly signaling and responding to protection periods while in broadcast coverage, the MPD for broadcast DASH services should support broadcast transport availability adjustment via existing MPD parameters. Can do. This is illustrated in FIG. 14 by adding a protection period to the MPD's availabilityStartTime attribute or by adding a protection period to the period attribute of the initial MPD period. The effect of adding a protection period to any of the parameters described above is that unicast retrieval is also delayed.

Seamless UC-BC Transition / BC-UC Transition: Buffering before receiving and playing back segments via unicast and broadcast when considering two alternatives to accommodate further availability adjustments in broadcast transport UC-BC transitions and BC-UC transitions should be considered. FIG. 15 shows a point in time when a transition from reception of a segment via unicast to reception via broadcast occurs when segment N is extracted via unicast.

One goal for seamless transition is to minimize interference during media playback when the DASH client transitions between unicast and broadcast reception. To accomplish this, the DASH client can accumulate more than one segment before playback begins. The number of segments that accumulate before starting playback can be signaled, such as via the minBufferTime attribute in the MPD. FIG. 16 shows (at time t _Avi ) playback of the segment retrieved via unicast is delayed by one segment (left timeline) and delayed by two segments (right timeline) Fig. 4 shows an embodiment with two playback scenarios delayed (at time t _Pbi ). This means that one or two segments, respectively, need to be accumulated before playback can begin. The example of FIG. 16 shows one segment for downloading one segment via unicast when the segments are the same size and the bandwidth is available to download the segment within the duration of one segment. A scenario that takes a long time. The embodiment of FIG. 16 is merely exemplary and similar numbers are used to describe other scenarios where the size of the segments is variable and the number of segments to buffer corresponds to such variability. Note that you can draw.

FIG. 17 shows a similar delayed segment playback scenario for a segment received via broadcast (at time t _FAvi ). These segments are delivered via broadcast and are available locally as shown earlier, so they can be immediately available to clients. The embodiment of FIG. 17 uses one segment to deliver one segment via broadcast when the segments are the same size and the broadcast bandwidth is sufficient to deliver the segment within the duration of one segment. Suggests that it will take a long time. The embodiment of FIG. 17 is merely exemplary and similar numbers are used to describe similar scenarios where the size of the segments is variable and the number of segments to buffer corresponds to such variability. Note that you can draw.

FIG. 17 also illustrates the use of the same minBufferTime requirement for one or two segments before playback. FIG. 17 also illustrates that retrieval is driven by broadcast segment availability (at time t _FAvi ) when the DASH client corresponds to a protection period, ie, a protection period later than unicast availability (at time t _Avi ). When done (see FIG. 15), the segments can be readily available locally and can be retrieved with minimal latency. The retrieved segment is ready for playback immediately after the first or second segment, respectively, when minBufferTime is one or two segments.

  Given the timelines of FIGS. 16-17, assuming that broadcast availability is detected while the DASH client retrieves segment N via unicast, the impact on the UC-BC transition may include: . First, segment N may not be successfully received via broadcast (symbols not sufficient for FEC decoding), so that a UC-BC transition may occur later. Second, successful reception of a DASH segment via broadcast may not be guaranteed until the first segment (N + 1) is received via broadcast. Thus, the DASH client can complete segment N retrieval via unicast and segment N + 1 via unicast. Third, the DASH client can delay the retrieval of the segment from segment N + 2 (stop unicast) and rely on the broadcast delivery of the segment. Fourth, considering FIGS. 16-17, a seamless transition can be achieved, and segment N + 2 can be available at the same time as retrieved via unicast. That is, playback can proceed seamlessly. Thus, a seamless UC-BC transition can be realized when playback is delayed by one segment (ie, with a minBufferTime set to one segment). Depending on the situation, a seamless transition may require a larger segment delay and may require a smaller segment delay.

  FIG. 18 shows the reverse BC-UC transition by highlighting when a BC-UC transition occurs while the receipt of segment N is being retrieved via broadcast. Segment N may not be successfully received via broadcast (a symbol that is not sufficient for FEC decoding) and may not be immediately determined. If it is determined that segment N has not been successfully received, the DASH client can begin retrieving segment N via unicast to ensure continuous playback. The DASH client may need to switch back to a lower data rate representation.

  Thus, a seamless BC-UC handoff may only be achievable if segment N can be retrieved via unicast in time for playback. As the timeline on the left of FIG. 19 shows, this is not feasible when minBufferTime etc. defines only one segment. If minBufferTime defines two segments (see the timeline on the right in FIG. 19), the DASH client has one segment of time to rewind and avoid playback disruption. Thus, for a seamless transition from broadcast to unicast, a DASH client should be instructed to accumulate more than two segments before playback to accommodate rewind download via unicast. is there.

  In a related aspect, when including a protection period on the MPD attribute, the DASH client may be instructed to accumulate more than two segments before playback. Thus, the drawback of including a protection period in the existing parameters in the MPD may be further segment availability adjustment.

Use of a session description protocol to signal broadcast delivery of a given representation of a streaming service and associated broadcast availability adjustments: In some situations, to indicate a unicast vs. broadcast delivery mode of a media segment of a representation, It is not desirable to use MPD directly (eg, via the serviceLocation attribute, etc.). For example, in some implementations, network-based generation of DASH segments and associated MPDs may be agnostic with respect to media content transport methods (unicast and / or broadcast). In such cases, it may be desirable for the unicast-to-broadcast delivery mode to be signaled using, for example, service announcement information (also referred to as system information or SI).

  In particular, for 3GPP MBMS, the SI or USD component may be a session description metadata fragment or the like. Such parameters and syntax may then be based on the SDP defined by RFC 4566 of IETF. The term “attribute” or “a =” is the main way to extend SDP and is defined at the session level (ie applicable to the media component of a FLUTE session) or at the individual media level within a session. Note that you can. In a related aspect, the attribute field can be, for example, two forms. In a related aspect, there is a “property” attribute of the form “a = <flag>”, where the presence of the attribute only indicates that the attribute is a session property. In a further related aspect, there is a “value” attribute of the form “a = <attribute>: <value>”, where the value of the named attribute is composed of an arbitrary octet string or the like.

  According to aspects of the embodiments described herein, a new session level attribute “a = <representation-transport-mode>” is provided to represent the transport mode of the associated session. The defined <value> subfield of this attribute specifies a text string "unicast", "broadcast" that specifies a unicast only, broadcast only, or both unicast and broadcast delivery mode for the corresponding segment such as Representation. Or “both”.

Furthermore, broadcast distribution of segments may be associated with an additional delay, also called “protection period”, compared to unicast distribution. Such parameters can be added to the above “representation-transport-mode” attribute, such as via a new subfield <protection-period>. For example, the full syntax of the “representation-transport-mode” attribute may be as follows:

  In a related aspect, <representation-id>, which is equivalent to the value of the “id” attribute of the Representation in the USD MPD fragment, identifies the DASH segment associated with the Representation to which the next delivery mode tag applies. be able to. If the transport mode is “broadcast” or “both”, the subfield <protection-period> can appear, representing the broadcast availability adjustment for that representation.

  In a further related aspect, it is anticipated that the service announcement client will use the above attribute information to inform the DASH client of the corresponding Representation delivery mode in the MPD as well as the protection period for the broadcast delivery mode.

Use of Session Description Protocol to Signal FLUTE Session Broadcast Availability Adjustment: An alternative to the technique described above for signaling broadcast availability adjustment is that the transport mode is declared using the serviceLocation attribute of the MPD In contrast, signaling the broadcast delay using a session description fragment. This approach has the benefit of separating availability adjustment or protection period information from DASH. In other words, in addition to FLUTE delivery of DASH content as a streaming service, other file delivery service applications where knowledge of broadcast availability adjustment is useful to allow the application to use the delivered content faster. May exist. Examples of such applications include dynamic news or stock ticker information broadcast for near real-time background display on mobile terminals. For such applications, files associated with FLUTE delivery can be protected by application layer FEC (eg, RaptorQ, etc.), which can improve time interleaving, which is important in the creation of encoded symbol blocks. . In general, broadcast availability adjustment / protection period announcements via session description fragments should allow the UE to take this delay into account when scheduling related content playback.

Techniques for signaling a protection period within SDP may be implemented, for example, according to the following:

  Service announcement clients (ie, broadcast-capable UE capabilities) are expected to inform other capabilities within the broadcast availability coordination UE to take this delay into account when scheduling related content delivery mode playback. Is done. For broadcast delivery of DASH content, such client functions can include DASH clients.

Determining the appropriate FLUTE session: For some broadcast DASH services, it may be desirable to broadcast two alternative representations of the service simultaneously. For example, the two representations may have different video resolutions. Each resolution can accommodate a different device type, one with a small screen size (eg, a smartphone) and the other with a large screen size (eg, a tablet). Since only one of these representations is typically consumed / utilized by a given device, each representation can be broadcast using a different transport session. For eMBMS broadcasts, the representation may be two FLUTE sessions transported in different eMBMS bearer channels as shown in the embodiment of FIG.

  With respect to associating a FLUTE session with a representation, a BaseURL in the MPD for a broadcast DASH service with an associated serviceLocation attribute indicates that the representation is available via broadcast: “: transport = broadcast” or “: transport = Both "can be included. To signal an appropriate broadcast transport session for representation (eg, a FLUTE session in eMBMS), an additional string format can be transported in the serviceLocation attribute as follows.

  In the first aspect, when using the URN format, the serviceLocation attribute for the BaseURL for the representation can include a string starting with “urn: 3gpp: sl” and the representation is available via broadcast. Either “: transport = broadcast” or “: transport = both” may be included to indicate that there is. In the second aspect, the string “: flute =” + sourceIPAddValue + “+” + tsiValue (in the format of key = value pair) and the source IP address that uniquely identifies the FLUTE session together via sourceIPAddValue and tsiValue TSI can be signaled. An exemplary string for the serviceLocation attribute may be urn: 3gpp: sl: transport = broadcast: flute = 198.152.39.10 + 4567.

  In a third aspect, the alternative string “: fluteSDP =” + sdpURLValue (in the format of key = value pair) identifies one of the FLUTE sessions defined for the broadcast service via sdpURLValue. The URL can be signaled. An exemplary string for the serviceLocation attribute is: urn: 3gpp: sl: transport = broadcast: fluteSDP = http: // example. com / serviceX / service. It can be sdp or the like. In the fourth aspect, other strings can be defined to describe a transport session that is different from the FLUTE session.

  Based on information about the sample DASH client behavior and the mapping of DASH segments signaled in the MPD to broadcast availability and representation of FLUTE sessions, the DASH client implementation can be configured for reception during broadcast coverage as follows: The serviceLocation information on BaseURL can be used. In the first aspect, the DASH client can select a desired representation based on the media description information (eg, screen resolution). In the second aspect, the DASH client broadcasts a multiple expression when, for example, the serviceLocation information of BaseURL for these expressions includes a character string of either “: transport = broadcast” or “: transport = both”. It is possible to detect that it is available via In a third aspect, when the DASH client detects that it is in broadcast coverage, it will send either the string “: transport = broadcast” or “: transport = both” associated with the selected expression. A BaseURL having a serviceLocation attribute to include can be selected. In a fourth aspect, the DASH client broadcasts via a FLUTE session (in the case of eMBMS) identified by a string containing “flute =” or “fluteSDP =” in the serviceLocation attribute of the selected BaseURL. The reception of the segment can be caused. In a fifth aspect, the DASH client can perform segment fetching according to a segment availability timeline in the MPD that uses the selected BaseURL.

UC-BC URL signaling for on-demand services: The broadcast system can be used as a way to reduce the use of system resources by multiple users accessing some DASH content via unicast reception. Demand definition can be supported. In some situations, it may be necessary to redirect user devices that consume unicast DASH content to a broadcast DASH service that transports the same content. This redirection process can use an HTTP redirection function to cause the user device to re-request a desired segment that uses a URL that is different from the URL used for the original request. Use of these redirected URLs can serve as a trigger for the user device to determine the availability of a new broadcast DASH service for the same content being retrieved via unicast.

  With respect to identifying the segment URL for receiving broadcasts from unicast, the BaseURL in MPD for broadcast DASH service associated with the serviceLocation attribute containing the string “: transport = unicast” is represented via unicast. Indicates that it is available. To further indicate that some unicast URLs were only intended to support the redirection approach, an additional string format was transported in the serviceLocation attribute to identify the URL used for redirection. You can also More specifically, the serviceLocation attribute can contain a string starting with “urn: 3gpp: sl” when using the urn format to indicate that the service is available via unicast. , The character string “: transport = unicast” can be included. Also, the string “: transition =” + transValue (in key = value pair format) is only intended for URLs to support redirection techniques if the transValue can be either UC-BC or BC-UC. Can be shown. An exemplary string for the serviceLocation attribute may be urn: 3gpp: sl: transport = unicast: transition = UC-BC, etc.

  With respect to sample DASH client behavior, when DASH content available via unicast is also made available via broadcast to offload unicast traffic, the associated MPD for the content is broadcast content availability. And unicast availability can be signaled. Information about the transition URL can also be present to identify the URL to be used for transition redirection. For transition redirection, DASH client implementations can include the use of BaseURL serviceLocation information as described below.

  In the first aspect, the DASH client (a) determines the available bandwidth to retrieve the segment, selects the expression to be played, and (b) the strings “: transport = unicast” and “: transition”. Except for BaseURL that includes = "," select a BaseURL that has a serviceLocation attribute that includes a string of either ": transport = unicast" or ": transport = both" and / or (c) select the selected BaseURL If used to perform segment fetching according to normal DASH client behavior, the DASH client can initiate unicast reception of DASH content.

  In the second aspect, there may be broadcast service availability signaling (ie, an indication of transition from unicast to broadcast) while consuming content via unicast. A DASH client that receives DASH content via unicast can obtain HTTP redirection to another URL. The DASH client then (a) if the corresponding serviceLocation attribute contains the strings “: transport = unicast” and “: transition = UC-BC”, the redirected URL matches the Base URL of the MPD for the same representation Continue to extract segments from the redirected URL until (b) if there is such a match, perform the transition, and / or (c) the availability of the broadcast version of the content can be determined .

Communication of parameters via comma-separated strings: The various parameters described herein are encoded using URN format for purposes of illustration and not limitation. Alternatively, a comma-delimited string can be used. In one embodiment, a comma-delimited string can be implemented as follows: The first string to be transported in the serviceLocation attribute of BaseURL may be “3gpp-sl” or the like. Subsequent strings are concatenated to the first string starting with “,”, followed by a string that provides a key = value pair, and so on.

  The second string (or first key = value pair) may be “, transport =” + value string or the like. Possible value strings may be “broadcast”, “unicast”, “both”. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = broadcast or 3gpp-sl, transport = unicast.

  In a related aspect, to signal the geographic availability of a broadcast DASH service via unicast, the string “, uGeo3GppCellID =” + CellID string (in the format of key = value pair) is passed via the CellID string. Thus, a 3GPP cell ID in which the service can be consumed via unicast can be indicated. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = unicast, uGeo3GppCellID = 345690, etc.

  The string “, uGeo3Gpp2S + N + Z =” + SID_value + “+” + NID_value + “+” + PZID_value (in the format of a key = value pair) is a service that is uni A 3GPP2 cell ID that may be consumed via a cast may be indicated. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = unicast, uGeo3Gpp2S + N + Z = 23 + 34 + 45, etc.

Other strings can be defined to capture other geographic descriptors that may be available for the device.

  In a further related aspect, the string “, pp =” + ppValue (in key = value pair format) signals the millisecond protection period via ppValue while the DASH client is in broadcast coverage. Corresponding when a segment is requested. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = broadcast, pp = 50, etc.

  In a further related aspect, the string “, flute =” + sourceIPAddValue + “+” + tsiValue (in key = value pair format) is passed via sourceIPAddValue and tsiValue to signal the appropriate broadcast transport session for the representation. Together, the source IP address and TSI that uniquely identify the FLUTE session can be signaled. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = broadcast, flute = 198.152.39.10 + 4567, etc.

  The alternative string “, fluteSDP =” + sdpURLValue (in key = value pair format) may signal a URL identifying one of the FLUTE sessions defined for the broadcast service via sdpURLValue. it can. An exemplary string for the serviceLocation attribute is 3 gpp-sl, transport = broadcast, fluteSDP = http: // example. com / serviceX / service. It can be sdp or the like.

Other strings can be defined to describe a transport session that is different from the FLUTE session.

  In a further related aspect, the string “, transition =” + transValue (in key = value pair format) supports a redirection technique if the transValue can be either UC-BC or BC-UC. Can only show that it was intended. An exemplary string for the serviceLocation attribute may be 3gpp-sl, transport = unicast, transition = UC-BC, etc.

Communication of parameters via XML string: Yet another way to encode the various parameters described so far for transport in the serviceLocation attribute of BaseURL is via an XML file. The XML structure for these parameters can be captured on the XML schema, as shown in the example of FIG. 21 showing multiple broadcast transmissions for a single service.

In one embodiment, to signal the type of transport, the serviceLocation attribute may be as follows: For the broadcast type, the serviceLocation attribute can be:

For the unicast type, the serviceLocation attribute can be:

  In another embodiment, the following applies to signaling the geographic availability of a broadcast DASH service via unicast.

Use 3GPP cell ID:

Use 3GPP2 cell ID:

In yet another embodiment, the following applies to signaling the protection period:

In yet another embodiment, the following applies to signaling the appropriate broadcast transport session for the representation:

In yet another embodiment, the following applies to signaling the URL used for on-demand DASH service:

Options for declaring broadcast transport modes and / or broadcast availability adjustments: According to aspects of the subject matter of this disclosure, using MPD, transport modes of DASH segments, and unicast delivery of those same segments In contrast, other options are provided for declaring availability adjustments in the availability of media segments delivered via broadcast. One approach described above involves using the serviceLocation attribute to transport such metadata for transport mode and broadcast availability adjustment information. Another approach described above includes providing transport mode and delivery availability adjustment information using a session description of MBMS service announcement information, such as via an SDP file.

  Alternatively or additionally, transport mode and broadcast availability adjustment information may be signaled in a new MPD element with a name such as TransportDescription. For example, TransportDescription represents the type of generic descriptor element (eg, defined by the MPEG DASH (ISO / IEC 2309-1) standard or the 3GP-DASH (3GPP TS26.247) standard) and represented in the MPD. Can serve as a container for transmission and access related information. Examples of such transmission and access information include i) transmission topology (unicast, broadcast, or both), ii) certain types of broadcast techniques (eg, cellular MBMS over GERAN, UTRAN, or LTE), terrestrial broadcasts TV system (eg, ATSC, ISDB-T, T-DMB, CMMB, or DVB-T), or satellite TV broadcasting technology (eg, DVB-S or S-DMB), iii) services related to information specific to the access technology References to announcements / discoveries, and iV) Segment availability broadcast delivery specific availability adjustments to unicast delivery segment availability may be included. Broadcast specific availability adjustments can increase MPD @ availabilityStartTime by providing a time delay value to be added to the unicast segment availability time. The obtained value (unicast segment availability time + broadcast delay value) represents the broadcast segment availability time.

  Alternatively or additionally, the transport mode and broadcast availability adjustment information can be signaled by a new extension parameter under the BaseURL element in the MPD. New extension parameters can include child elements or child attributes broadcastDeliveries that indicate MBMS delivery and also announce broadcast availability adjustments. New extension parameters can appear under the BaseURL child elements, such as the Representation element. This approach should provide an indication of whether individual presentations of media presentations are available for broadcast delivery, and should also provide any variety of latency indications.

  Note that TransportDescription can only be defined to provide an entry point to service announcement information. The availability adjustment parameter can be moved to the BaseURL element of the MPD. In a related aspect, when the TransportDescription element is used to represent the access-specific parameters indicated in the broadcast transport case, the transmission and access related information may be technology (eg, cellular, terrestrial TV, satellite TV etc.) can be explicitly identified. Broadcast technology can be identified by extending the BaseURL element to transport access-specific parameters and the like. In a further related aspect, the Transport descriptor can be placed, for example, under various hierarchical levels of the MPD, such as a top MPD element level, or a child element of the MPD (eg, Period, AdaptationSet, Representation, etc.) . Note that the TransportDescription element can be a BaseURL peer element or a SegmentBase peer element.

  In a related aspect, since each segment can be delivered over a different network, a Transport descriptor (ie, a TransportDescription element) may be able to deal with individual segments declared in the MPD. In a further related aspect, the Transport descriptor can be defined at the representation level. For example, a Transport descriptor can be added to the following elements so that it can be added at the Period level, AdaptationSet level, and / or Representation level: (a) A BaseURL element that can then be used flexibly, and And / or (b) a SegmentBase element (eg, when there is no BaseURL).

  In a related aspect, the Transport descriptor access scheme, represented by the Transport descriptor attribute schemeIdUri, is interpreted by the DASH client, device middleware, or other UE function, and the network stack supports this transport scheme. It can be constructed so that it can be determined whether or not. The associated value in the Transport descriptor can provide a unique entry point for transport to the service announcement. For example, the associated value can be a serviceID or URL to a service announcement document.

  In a related aspect, for MBMS, the value of the Transport descriptor may be a URL to a user service bundle document / fragment that also includes a serviceID (eg, encoded as a fragment in the URL). The value of the Transport descriptor can include specific information about the FLUTE session to be joined. Alternatively or in addition, URLs to service and access discovery information can be made available on web pages, such as via HTTP. In this case, a content type that identifies a document linked by a URL as a user service bundle description document for a broadcast / multicast link can be defined.

Representation broadcast and / or unicast availability signaling: According to one or more aspects of the embodiments described herein, broadcast availability and / or unicast of representations of media data segments in a broadcast wireless system. Techniques for signaling availability are provided. Referring to FIG. 10B, an exemplary USD including system information for eMBMS service is shown. USD has been extended to describe the availability of representations via broadcast, unicast, or both.

  As FIG. 10B shows, the presence of the updated media-Presentation-Description-2 element indicates that if the mpdURI element provides a link to identify the MPD associated with the DASH service, the service described by the USD is a DASH eMBMS. Indicates a service.

  The updated media-Presentation-Description-2 element also provides a list of broadcast-Representation and unicast-Representation elements that identify broadcast and unicast expressions. The expressions identified in both lists are available via unicast and broadcast.

  A representation in either list is a reference to the respective value identified in the MPD by a period via the periodId attribute, by a matching set via the adaptationSetId attribute, and / or by a representation via the representationId attribute. Can be identified as Broadcast representations can also be associated with serviceArea information that allows the broadcast component to determine which representations are available within a given broadcast area.

  A broadcast service can also include multiple transport streams, so a broadcast DASH service can have various representations being transported over separate transport streams. This may be done to provide different resolutions targeting different device capabilities, or different languages targeting different user preferences.

  The exemplary broadcast client behavior is based on the broadcast and / or unicast availability of the DASH representation signaled in the USD for eMBMS DASH service, and the broadcast eMBMS client determines when the device enters and exits broadcast coverage. And / or according to system information (eg, USD in eMBMS) as shown in FIG. 10B, which of the DASH representations in the MPD is available via the broadcast service and which is unicast It may be possible to know what is available via In a related aspect, depending on the broadcast coverage state, the broadcast client signals the client to select one of the available broadcast representations when the device enters broadcast coverage, and / or the device is in broadcast coverage. Upon exiting, the DASH client can be signaled to select one of the available unicast representations. In a further related aspect, in response to the DASH client's selection of the broadcast representation, the broadcast client can activate reception of a FLUTE session that transports the selected representation.

  The attribute availabilityTimeAdjustment, if present, is declared in the MPD fragment (ie, MPD @ availabilityStartTime) and specifies the broadcast reception adjustment of the segment availability start time, which can be either a positive or negative value. A positive (negative) value means that the available time of the Representation segment is later (before) the available time of any Representation of the media presentation delivered via unicast, if applicable. To do. The serviceArea element and the sessionDescription element, when present, respectively represent a service area in which the Representation via it can be used and a FLUTE session that transports the Representation. The unicastRepresentation element, if present, identifies each Representation supplied via unicast for fallback delivery. A unicast delivered Representation can be the same representation delivered via an MBMS bearer, or it can be a Representation delivered via a unicast bearer only.

  In view of the exemplary systems shown and described herein, methods that can be implemented in accordance with the disclosed subject matter will be better understood with reference to various flowcharts. For ease of explanation, the methods are illustrated and described as a series of acts / blocks, although some blocks may be in a different order than depicted and described herein and / or other It should be understood and understood that claimed subject matter is not limited by the number or order of blocks, as they can be performed substantially simultaneously with the blocks. Moreover, not all illustrated blocks may be required to implement the methods described herein. It should be understood that the functionality associated with the blocks may be implemented by software, hardware, combinations thereof, or any other suitable means (eg, device, system, process, or component). In addition, it should be further appreciated that the methods disclosed throughout this specification can be stored in products that facilitate transport and transfer of such methods to various devices. Those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as a state diagram.

  In accordance with one or more aspects of the embodiments described herein, referring to FIG. 22A, illustrated is a method 2200 operable by a mobile entity (eg, a UE, etc.). Method 2200 can include receiving an MPD at 2210, where the MPD can represent multiple representations of content via broadcast and unicast transmissions (eg, in response to activation of a file delivery session). With parameters for reception of the data segment. Note that in the case of unicast, the data can reside in an HTTP server or “in the cloud”, whereas in the case of broadcast, the data can reside locally in the UE's HTTP cache. The method 2200 may include, at 2220, determining whether a broadcast transmission or a unicast transmission is suitable for receiving the data segment. The method 2200 may include, at 2230, selecting a given representation from among multiple representations of content based on mobile entity criteria. Method 2200 may include, at 2240, receiving a data segment for a given representation based at least in part on parameters for a determined one of broadcast transmission and unicast transmission.

  With reference to FIGS. 22B-22D, additional operations or aspects of a method 2200 that are optional and may be performed by a mobile entity or the like are illustrated. If the method 2200 includes at least one block of FIG. 22B or FIG. 22C, the method 2200 may end after the at least one block without necessarily including the subsequent downstream block shown. It is further noted that block reference numbers do not imply a particular order in which the blocks may be performed according to method 2200. For example, a mobile entity can operate on a broadcast mobile system, a broadcast DASH service can be defined via system information metadata including MPD, and a method can be used for alternative delivery of a broadcast DASH service. Determining whether it is available via unicast transmission can be included from parameters in the MPD (block 2250).

  The method 2200 may determine the availability of broadcast transmissions at the mobile entity's current location (block 2252) and, if there is no broadcast transmission availability, determine the availability of unicast transmissions as an alternative to broadcast transmissions (block 2254). ).

  The criteria include at least one of display resolution capabilities, language capabilities, mobile entity wireless network compatibility, or wireless channel availability to support bandwidth requirements for representation. (Block 2256). Information about the broadcast file delivery session associated with the given representation is used to activate the broadcast file delivery session for receipt of the media segment (block 2258).

  Method 2200 may include selecting a representation for broadcast reception by selecting from among the available broadcast representations that may be received within the current broadcast service area (block 2260).

  Method 2200 includes selecting a representation for unicast reception by selecting from among unicast representations available for alternative delivery that may be received within the current unicast service area (block 2262). Can do.

  Referring to FIG. 22C, receiving (block 2240) may include adjusting an availability timeline for the data segment of the representation (block 2264) by a latency adjustment period for the given representation.

  Receiving (block 2240) takes into account the difference in availability timelines for the representations defined by their respective latency adjustment periods (block 2266) and broadcast transmissions and unicasts that affect access to the data segment. Data segment buffer to consider the characteristics of the cast transmission (block 2268) and to achieve a seamless transition between reception via unicast transmission and reception via broadcast transmission for each representation of the content Adjusting the ring (block 2270).

  The adjustment of the latency period may indicate a time delay or time advance in data segment availability for a given representation via broadcast transmission relative to unicast transmission (block 2272). . For example, the parameter may indicate an availability adjustment for broadcast delivery of a data segment relative to unicast delivery of the data segment. For example, the parameter may indicate an expected time delay in the availability of broadcast-delivered data segments relative to their availability via unicast delivery. Alternatively, the parameters can indicate the expected time advance in the availability of broadcast-delivered data segments relative to their availability via unicast delivery.

  The parameter may indicate (a) unicast only, (b) broadcast only, or (c) both unicast and broadcast availability of the data segment (block 2274). At least one of the parameters relates to (b) broadcast only or (c) both unicast and broadcast availability of the data segment and identifies a broadcast distribution technique (block 2276). For example, the at least one broadcast distribution technology may correspond to an IP-based broadcast system such as, for example, a) a cellular broadcast technology, b) a terrestrial broadcast TV system, or c) a satellite TV broadcast technology.

  Referring to FIG. 22D, the parameters include information regarding the availability of broadcast representations within a number of identified broadcast service areas (block 2278).

  The data segment may be a DASH media segment or the like (block 2280), and the method 2200 may play the media segment seamlessly in response to receiving a media segment that changes from a broadcast transmission to a unicast transmission or vice versa. It may further include accumulating media segments to achieve the back (block 2282). The parameter may be encoded in one or more instances, such as an extension element TransportDescription in the MPD (block 2284). The parameters may include a FLUTE session identifier or the like for a specific representation of the broadcast content (block 2286).

  In a related aspect, determining (block 2220) may include determining that the unicast fetch is suitable for receiving a data segment. The parameter can indicate the geographic availability of the data segment for unicast retrieval. In a further related aspect, the parameters can comprise information for indicating unicast DASH access to an on-demand broadcast version of the content via a serviceLocation attribute in the MPD for the content.

  In a further related aspect, the parameters can be encoded within the Base URL of the MPD. The parameter may comprise a URN under the registered NID. The parameter may comprise a URN namespace specific string (NSS) containing a colon-separated list of key = value pairs transported as a string in the serviceLocation attribute in the BaseURL. The parameter can relate to a DASH expression that provides an alternative for a given data stream.

  In a further related aspect, the parameters can be encoded in one or more instances of the extension element TransportDescription under MPD. The extension element TransportDescription under MPD can be present in one or more of the following various hierarchical levels of the MPD data structure: MPD element, Period element, AdaptationSet element, and Representation element. The TransportDescription can be a type of generic descriptor element and can include transmission and access related information for the representation described in the MPD. The transmission and access related information transported within each instance of TransportDescription can indicate at least one transmission topology: a) unicast, b) broadcast, or c) both unicast and broadcast.

  When the transmission topology is indicated as broadcast, or both broadcast and unicast, the relevant information on transmission and access can be a specific type of a) cellular broadcast technology, b) terrestrial TV system, or c) satellite TV broadcast technology. One of them can be shown. The transmission and access related information may indicate entry point information for accessing service announcement / discovery information about the broadcast technology. In addition to entry point information to access service announcement / discovery information about broadcast technology, related information on transmission and access is expected of broadcasted data segments for their availability via unicast delivery. Can indicate availability adjustment. The available time through unicast delivery of a data segment can be represented by or derived from the value of MPD @ availabilityStartTime.

  In a related aspect, the parameters can be encoded in one or more extended parameters under at least one instance of the BaseURL element in the MPD. The parameter in each of the one or more instances of the BaseURL element can indicate a unicast or broadcast transport mode. When the transport mode is indicated as broadcast, the relevant parameters are explicit for one of the broadcast distribution technologies of a) a cellular broadcast technology, b) a terrestrial TV system, or c) a specific type of satellite TV broadcast technology. Identification can be made possible. The parameter may indicate an expected availability adjustment of the broadcasted data segment relative to their availability via unicast delivery. The parameter can indicate whether a separate representation of the media presentation is available for broadcast delivery. If the transport mode is indicated as unicast, the associated parameters may allow explicit identification of one unicast access network of the content delivery network (CDN) type. The parameter can indicate the expected availability adjustment of the data segment for retrieval on this unicast access network or CDN to their availability via unicast delivery.

  In accordance with one or more aspects of the embodiments described herein, devices and apparatus are provided for performing the methods described above with respect to FIGS. 22A-22D. With reference to FIG. 23, an example apparatus 2300 is provided that may be configured as a mobile entity or as a processor or similar device / component for use therein. Apparatus 2300 can include functional blocks that can represent functions implemented by a processor, software, or combination thereof (eg, firmware). For example, apparatus 2300 can include an electrical component or module 2312 for receiving MPD, which can receive data segments for multiple representations of content via broadcast and unicast transmissions. With parameters for Apparatus 2300 can include a component 2314 for determining whether a broadcast transmission or a unicast transmission is suitable for receiving a data segment. Apparatus 2300 can include a component 2316 for selecting a given representation among multiple representations of content based on mobile entity criteria. Apparatus 2300 can include a component 2318 for receiving a data segment for a given representation based at least in part on parameters for a determined one of broadcast transmission and unicast transmission. .

  In a related aspect, for device 2300 configured as a mobile entity rather than as a processor, device 2300 can optionally include a processor / controller component 2350 having at least one processor. In such cases, processor 2350 can operatively communicate with components 2312-2318, such as via bus 2352. The processor 2350 can implement activation and scheduling of processes or functions executed by the components 2312 to 2318.

  In a further related aspect, apparatus 2300 can include a radio frequency (RF) transceiver component 2354. Stand-alone receivers and / or stand-alone transmitters may be used instead of or in conjunction with transceiver 2354. Apparatus 2300 can optionally include a component for storing information, such as, for example, memory device / component 2356. Computer readable media or memory component 2356 may be operatively coupled to other components of device 2300, such as via bus 2352. Memory component 2356 stores the processes and behavior of components 2312-2318 and their subcomponents, or processor 2350, or computer-readable instructions and data for implementing the methods described above with reference to FIGS. 22A-22D. Can be adapted to do. Memory component 2356 can retain instructions for executing functions associated with components 2312-2318. Although shown as being external to memory 2356, it should be understood that components 2312-2318 may reside within memory 2356. It is further noted that the components in FIG. 23 may comprise processors, electronics devices, hardware devices, electrical subcomponents, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof.

  In accordance with one or more aspects of the embodiments described herein, FIG. 24 illustrates another example method 2400 operable by a mobile entity or the like. The method 2400 receives 2410 system information including (a) DASH MPD and (b) parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions. Can be included. The method 2400 may include, at 2415, determining whether a broadcast transmission or a unicast transmission is suitable for receiving the data segment. The method 2400 may include, at 2420, selecting a given representation from among multiple representations of content based on mobile entity parameters and criteria. Method 2400 can include, at 2430, receiving a data segment for a given representation.

  In accordance with one or more aspects of the embodiments described herein, FIG. 25 illustrates an apparatus 2500 (eg, a mobile entity or component thereof) for performing the method 2400 described above with reference to FIG. ) Design. For example, apparatus 2500 receives system information including (a) DASH MPD and (b) parameters for receiving data segments for multiple representations of content via broadcast and unicast transmissions. Of electrical components or modules 2512. Apparatus 2500 can include a component 2513 for determining whether a broadcast transmission or a unicast transmission is suitable for receiving a data segment. Apparatus 2500 can include a component 2514 for selecting a given representation from among multiple representations of content based on mobile entity parameters and criteria. Apparatus 2500 can include a component 2516 for receiving a data segment for a given representation. For the sake of brevity, the remainder of the details regarding device 2500 will not be further elaborated, although many of the features and aspects of device 2500 are substantially similar to those described above with respect to device 2300 of FIG. I want you to understand.

  In accordance with one or more aspects of the embodiments described herein, referring to FIG. 26, illustrated is a methodology 2600 operable by a network entity (eg, eNB, etc.). Method 2600 may include sending an MPD at 2610, wherein the MPD comprises parameters for reception of a data segment for multiple representations of content via broadcast and unicast transmissions. The method 2600 may include, at 2620, receiving a request for a given representation of content. Method 2600 can include, at 2630, sending a data segment for a given representation via a broadcast or unicast transmission based at least in part on the parameters. The method may optionally include signaling (block 2640) which representations of services are available for broadcast or unicast transmission. For example, sending a data segment (block 2630) may send a data segment for a given representation via a unicast transmission and concurrently for at least one different representation via a broadcast transmission. Sending a data segment (block 2650).

  In accordance with one or more aspects of the embodiments described herein, FIG. 27 illustrates an apparatus 2700 (eg, a network entity or component thereof) for performing the method 2600 described above with reference to FIG. ) Design. For example, apparatus 2700 can include an electrical component or module 2712 for sending MPD, where MPD is for receiving data segments for multiple representations of content via broadcast and unicast transmissions. With parameters. Apparatus 2700 can include a component 2714 for receiving a request for a given representation of content. Apparatus 2700 can include a component 2716 for sending a data segment for a given representation via broadcast or unicast transmission based at least in part on the parameters. For the sake of brevity, the remainder of the details regarding apparatus 2700 are not further elaborated, but it should be understood that many of the features and aspects of apparatus 2700 are similar to those described above with respect to apparatus 2300 of FIG. . However, it should be noted that the apparatus 2700 may be a network entity such as an eNB. Thus, the apparatus can include network interface components (eg, network interface cards or network interface controllers), as well as other components typically found in base stations used in wireless communication systems.

  Note that the network side describes the MPD and the parameters to the mobile device / entity to choose between broadcast and / or unicast representations. The network sends a broadcast representation, creating a unicast representation that the mobile device can use to retrieve the segment. In a related aspect, apparatus 2700 sends a representation of a mobile entity selection of a media data segment, such as via unicast HTTP, in response to the mobile entity selecting a unicast mode for receiving the media data segment. Can further be included.

  Those of skill in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any of them Can be represented by a combination.

  Those skilled in the art further appreciate that the various exemplary logic blocks, modules, circuits, and process steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. Let's be done. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in a variety of ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the present disclosure. Absent.

  Various exemplary logic blocks, modules, and circuits described in connection with the disclosure herein include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays ( FPGA or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein can do. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, eg, a DSP and microprocessor combination, a plurality of microprocessors, one or more microprocessors associated with a DSP core, or any other such configuration. it can.

  The method or process steps described in connection with the disclosure herein may be implemented directly in hardware, implemented in software modules executed by a processor, or a combination of the two. . The software module may be RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM, or any other form of storage known in the art. Can reside on media. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in the user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

  In one or more exemplary designs, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and computer communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer readable media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or instructions or data structures in the desired form Or any other medium that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Any connection is also properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or non-transient wireless technology, the coaxial cable Fiber optic cable, twisted pair, DSL, or non-transitory wireless technologies are included in the media definition. As used herein, a disk and a disc are a compact disc (CD), a laser disc (registered trademark) (disc), an optical disc (disc), a digital versatile disc (DVD). ), Floppy disk and Blu-ray disk, the disk normally reproduces data magnetically, and the disk drives the data with a laser. Reproduce optically. Combinations of the above should also be included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Accordingly, the present disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The invention described in the scope of claims at the beginning of the application will be appended.
[C1]
A method operable by a mobile entity for wireless communication, comprising:
Receiving a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions;
Determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment;
Selecting a given representation from among the multiple representations of the content based on criteria of the mobile entity;
Receiving the data segment for the given representation based at least in part on the parameters for the determined one of the broadcast transmission and the unicast transmission.
[C2]
The mobile entity operates on a broadcast mobile system, a broadcast DASH service is defined via system information metadata including the MPD, and the method includes an alternative delivery of the broadcast DASH service for the unicast transmission. The method of C1, further comprising determining from the parameter in the MPD whether it is available through the MPD.
[C3]
Judging
Determining the availability of the broadcast transmission at the current location of the mobile entity;
The method of C1, further comprising: determining availability of the unicast transmission as an alternative to the broadcast transmission if the availability of the broadcast transmission does not exist.
[C4]
The C1 above, wherein the criteria includes at least one of display resolution capability, language capability, wireless network compatibility of the mobile entity, or wireless channel availability to support the bandwidth requirements of the representation. Method.
[C5]
The method of C4, wherein information about a broadcast file delivery session associated with the given representation is used to activate the broadcast file delivery session for the reception of a media segment.
[C6]
The method of C1, further comprising selecting a representation for broadcast reception by selecting among available broadcast representations that may be received within the current broadcast service area.
[C7]
The method of C1, further comprising selecting a representation for unicast reception by selecting from among unicast representations available for alternative delivery that may be received within the current unicast service area.
[C8]
Receiving the data segment for the given representation further comprises adjusting an availability timeline for the data segment of the representation by a latency adjustment period for the given representation. The method according to C1 above.
[C9]
Receiving the data segment for the given representation;
Taking into account the difference in availability timelines for the representation defined by their respective latency adjustment periods;
Considering the characteristics of the broadcast transmission and the unicast transmission that affect access to the data segment;
Adjusting buffering of data segments to achieve a seamless transition between the reception via the unicast transmission and the reception via the broadcast transmission for each representation of the content; The method according to C1, further comprising:
[C10]
The method of C8, wherein the latency adjustment period indicates a time delay or time advance in the availability of the data segment for the given representation over the broadcast transmission relative to the unicast transmission.
[C11]
The parameter indicates (a) unicast only, (b) broadcast only, or (c) both unicast and broadcast availability of the data segment;
At least one of the parameters relating to (b) broadcast only or (c) both unicast and broadcast availability of the data segment identifies a broadcast distribution technique;
The method according to C1 above.
[C12]
The method of C1, wherein the parameters include information regarding availability of broadcast representations within a number of identified broadcast service areas.
[C13]
The data segment comprises a dynamic adaptive streaming over HTTP (DASH) media segment;
The method accumulates the media segments to achieve seamless playback of the media segments in response to the reception of the media segments changing from the broadcast transmission to the unicast transmission or vice versa. Further comprising
The method according to C1 above.
[C14]
The parameters are encoded in one or more instances of the extension element TransportDescription in the MPD;
The parameter includes a file delivery over unidirectional transport (FLUTE) session identifier for a particular representation of the broadcast content;
The method according to C1 above.
[C15]
A device,
Means for receiving a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions;
Means for determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment;
Means for selecting a given representation from among the multiple representations of the content based on mobile entity criteria;
Means for receiving the data segment for the given representation based at least in part on the parameter for the determined one of the broadcast transmission and the unicast transmission; apparatus.
[C16]
The device operates on a broadcast mobile system, a broadcast DASH service is defined via system information metadata including the MPD, and the device provides an alternative delivery of the broadcast DASH service via the unicast transmission. The apparatus of C15, further comprising means for determining from the parameter in the MPD whether or not it is available.
[C17]
Means for determining the availability of the broadcast transmission at the current location of the mobile entity;
The apparatus of C15, further comprising means for determining availability of the unicast transmission as an alternative to the broadcast transmission when the availability of the broadcast transmission does not exist.
[C18]
A device,
A radio frequency (RF) transceiver configured to receive a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions; ,
Configured to determine whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment, and to select a given representation from among the multiple representations of the content based on mobile entity criteria And at least one processor,
A memory coupled to the at least one processor for storing data;
The RF transceiver receives the data segment for the given representation based at least in part on the parameters for the determined one of the broadcast transmission and the unicast transmission;
apparatus.
[C19]
A computer program product,
Receiving a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions;
Selecting a given representation from among the multiple representations of the content based on mobile entity criteria;
Determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment for the given representation;
Receiving the data segment for the given representation based at least in part on the parameters for the determined one of the broadcast transmission and the unicast transmission. A computer program product comprising a non-transitory computer-readable medium comprising code for.
[C20]
A method operable by a mobile entity in a wireless system comprising:
(A) Dynamic Adaptive Streaming Over HTTP (DASH) Media Presentation Description (MPD) and (b) Parameters for the reception of data segments for multiple representations of content via broadcast and unicast transmissions Receiving system information including:
Determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment;
Selecting a given representation from among the multiple representations of the content based on the parameters and criteria of the mobile entity;
Receiving a data segment for the given representation.
[C21]
Determining the availability of the broadcast transmission at the current location of the mobile entity;
The method of C20, further comprising: determining availability of the unicast transmission as an alternative to the broadcast transmission if the availability of the broadcast transmission does not exist.
[C22]
A device,
(A) Dynamic Adaptive Streaming Over HTTP (DASH) Media Presentation Description (MPD) and (b) Parameters for the reception of data segments for multiple representations of content via broadcast and unicast transmissions Means for receiving system information including:
Means for determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment;
Means for selecting a given representation among the multiple representations of the content based on the parameters and criteria of the mobile entity;
Means for receiving a data segment for the given representation.
[C23]
A device,
(A) Dynamic Adaptive Streaming Over HTTP (DASH) Media Presentation Description (MPD) and (b) Parameters for the reception of data segments for multiple representations of content via broadcast and unicast transmissions A radio frequency (RF) transceiver configured to receive system information including:
Determine whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment, and based on the parameters and the criteria of the mobile entity, give a given representation among the multiple representations of the content At least one processor configured to select;
A memory coupled to the at least one processor for storing data;
The RF transceiver receives a data segment for the given representation;
apparatus.
[C24]
A computer program product,
(A) Dynamic Adaptive Streaming Over HTTP (DASH) Media Presentation Description (MPD); and (b) Parameters for receiving data segments for multiple representations of content via broadcast and unicast transmissions; Receiving system information including:
Determining whether the broadcast transmission or the unicast transmission is suitable for receiving the data segment;
Selecting a given representation from among the multiple representations of the content based on the parameters and criteria of the mobile entity;
A computer program product comprising a non-transitory computer readable medium comprising code for causing a computer to receive a data segment for the given representation.
[C25]
A method operable by a network entity for wireless communication, comprising:
Sending a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions;
Receiving a request for a given representation of the content;
Transmitting the data segment for the given representation via the broadcast transmission or the unicast transmission based at least in part on the parameter.
[C26]
The method of C25, further comprising signaling which representations of services are available for the broadcast transmission or the unicast transmission.
[C27]
Transmitting the data segment for transmitting at least one different representation via the broadcast transmission in parallel with transmitting the data segment for the given representation via the unicast transmission. Transmitting the data segment of C25.
[C28]
A device,
Means for transmitting a media presentation description (MPD) comprising parameters for reception of data segments for multiple representations of content via broadcast transmission and unicast transmission;
Means for receiving a request for a given representation of the content;
Means for transmitting the data segment for the given representation via the broadcast transmission or the unicast transmission based at least in part on the parameter.
[C29]
A device,
A radio frequency (RF) transceiver;
(A) instructing the RF transceiver to transmit a media presentation description (MPD) comprising parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions; (B) in response to receiving a request for a given representation of the content, for the given representation via the broadcast transmission or the unicast transmission based at least in part on the parameter At least one processor configured to instruct the RF transceiver to transmit the data segment of:
And a memory coupled to the at least one processor for storing data.
[C30]
A computer program product,
Sending a media presentation description (MPD) comprising parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions;
Receiving a request for a given representation of the content;
Non-temporary comprising code for causing a computer to transmit the data segment for the given representation via the broadcast transmission or the unicast transmission based at least in part on the parameter Computer program product comprising a computer readable medium.

Claims (5)

A method operable by a network entity for wireless communication, comprising:
Sending a media presentation description (MPD) including parameters for reception of data segments for multiple representations of content via broadcast transmission and unicast transmission , wherein said parameters are registered Signaled as Uniform Resource Name (URN) under Namespace Identifier (NID),
Receiving a request for a given representation of the content;
And Zui least also based on the parameter, and a transmitting a data segment through the broadcast transmission or the unicast transmission method.   The method of claim 1, further comprising signaling which representations of services are available for the broadcast transmission or the unicast transmission. A device,
Means for transmitting a media presentation description (MPD) comprising parameters for reception of data segments for multiple representations of content via broadcast transmission and unicast transmission , wherein said parameters are registered Signaled as a Uniform Resource Name (URN) under a Named Namespace Identifier (NID),
Means for receiving a request for a given representation of the content;
And Zui least also based on the parameter, and means for transmitting the data segments through the broadcast transmission or the unicast transmission apparatus. A device,
A radio frequency (RF) transceiver;
(A) instructing the RF transceiver to transmit a media presentation description (MPD) comprising parameters for reception of data segments for multiple representations of content via broadcast and unicast transmissions; (b) in response to receiving a request for a given representation of the content, and Zui least also based on the parameter, to transmit a data segment through the broadcast transmission or the unicast transmission At least one processor configured to instruct the RF transceiver , wherein the parameter is signaled as a uniform resource name (URN) under a registered namespace identifier (NID);
And a memory coupled to the at least one processor for storing data. A computer-readable storage medium,
Sending a media presentation description (MPD) with parameters for reception of data segments for multiple representations of content via broadcast transmission and unicast transmission , wherein said parameters are registered Signaled as Uniform Resource Name (URN) under Namespace Identifier (NID),
Receiving a request for a given representation of the content;
And Zui least also based on the parameter, storing code for causing and transmitting data segments via the broadcast transmission or the unicast transmission to the computer, the computer readable storage medium.