Isobmff carriage of attenuation map information for energy-aware images in a dash context

Abstract

Some embodiments of a method may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation and information related to a set of attenuation map representations for the visual content; obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

Description

ISOBMFF CARRIAGE OF ATTENUATION MAP INFORMATION FOR ENERGY-AWARE IMAGES IN A DASH CONTEXTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims benefit of: European Patent Application No. EP23306784, entitled "ISOBMFF CARRIAGE OF ATTENUATION MAP INFORMATION FOR ENERGY-AWARE IMAGES IN A DASH CONTEXT” and filed October 13, 2023; and European Patent Application No. EP23306227, entitled "ISOBMFF CARRIAGE OF ATTENUATION MAP INFORMATION FOR ENERGY-AWARE IMAGES IN A DASH CONTEXT” and filed July 17, 2023, which are each hereby incorporated by reference in their entirety.INCORPORATION BY REFERENCE

[0002] The present application incorporates by reference in its entirety, and is related to, the following application: European Patent Application Serial No. 22306227.2 and filed July 17, 2023 ("‘227 application”). The present application incorporates by reference in their entirety the following applications: European Patent Application Serial No. 22306719.0 and filed November 22, 2022 ("719 application”); European Provisional Patent Application Serial No. 23305185.3 and filed February 10, 2023 ("‘185 application”); European Patent Application Serial No. 23305479.0 and filed April 3, 2023 ("‘479 application”); European Provisional Patent Application Serial No. 23305958.3 and filed June 16, 2023 ("‘958 application”); European Patent Application Serial No. 22306908.9 and filed December 10, 2022 ("‘908 application”); European Provisional Patent Application Serial No. 23305521.9 and filed April 7, 2023 ("‘521 application”); European Patent Application Serial No. 23306066.4 and filed June 29, 2023 ("‘066 application”); European Provisional Patent Application Serial No. 23305566.4 and filed April 14, 2023 ("‘566 application”); and European Provisional Patent Application Serial No. 23306068.0 and filed June 29, 2023 ("‘068 application”).BACKGROUND

[0003] Reducing energy consumption of electronic devices has become a requirement not only for electronic devices manufacturers but also to limit, as much as possible, the environmental impact and to contribute to the emergence of a sustainable display industry. The increase in display resolution from SD to HD to 4K and soon to 8K and beyond, as well as the introduction of high dynamic range imaging, has brought about a corresponding increase in energy requirements of display devices. Conversely, there is a globalneed to reduce energy consumption. Indeed, displays are a source of energy consumption, whether for battery-powered devices (e.g., smartphones) or in the global video distribution chain.SUMMARY

[0004] Embodiments described herein include methods that are used in video encoding and decoding (collectively "coding”).

[0005] A first example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, and information related to a set of attenuation map representations for the visual content; obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0006] For some embodiments of the first example method, the manifest file includes an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI).

[0007] For some embodiments of the first example method, the manifest file includes an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AMU).

[0008] For some embodiments of the first example method, the identifier field is accessible with an external class.

[0009] Some embodiments of the first example method may further include: responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to the attenuation map representation selected.

[0010] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to quality of the picture, and selecting the attenuation map from the list is based on the information corresponding to quality of the picture.

[0011] Some embodiments of the first example method may further include rendering the attenuated picture.

[0012] For some embodiments of the first example method, the information related to the attenuation map representations further includes information representative of a type of interpolation.

[0013] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to scaling of pixels of the picture.

[0014] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to backlighting of the picture.

[0015] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to quality of the picture.

[0016] For some embodiments of the first example method, the manifest file and the segments are based on MPEG-DASH.

[0017] For some embodiments of the first example method, obtaining segments of the attenuation map representation is performed using an adaptation set with an identifier field corresponding to a Green Video type.

[0018] A first example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0019] A second example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, and information related to a set of attenuation map representations for the visual content; responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to an attenuation map representation selected from the set of attenuation map representations, obtaining segments of the video representation; obtaining segments of the selected attenuation map representation; decoding apicture from the obtained segments of the video representation; decoding the selected attenuation map representation from the obtained segments of the selected attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture.

[0020] A second example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0021] A third example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, information related to a set of attenuation map representations for the visual content, and anadaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AM II); obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0022] A third example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0023] A fourth example method in accordance with some embodiments may include: creating a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, and information related to a set of attenuation map representations for the visual content; and sending to a client the manifest file corresponding to visual content.

[0024] Some embodiments of the fourth example method may further include: receiving a request for segments of the video representation; receiving a request for segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; sending to the client the segments of the video representation; and sending to the client the segments of the attenuation map representation selected from the set of attenuation map representations based on the selected energy reduction rate.

[0025] Some embodiments of the fourth example method may further include: encoding a picture as the segments of the video representation; and encoding the selected attenuation map representation as the segments of the selected attenuation map representation.

[0026] A fourth example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0027] An example server apparatus in accordance with some embodiments may include: one or more processors, the one or more processors configured to generate a manifest file, the manifest file comprising information configured to and available to be used by a client to reduce energy consumption of video representations at a client display in a pixel-wise manner, wherein the one or more processors are further configured to generate the manifest file in part by deriving the information from attenuation map information obtained by the server.

[0028] For some embodiments of the example server apparatus, the server is a DASH server.

[0029] For some embodiments of the example server apparatus, the manifest file is a DASH MPD file.

[0030] An example client apparatus in accordance with some embodiments may include one or more processors and in communication with a display, the one or more processors configured to obtain a manifest file, the manifest file comprising information configured to and available to be used by the client to reduce energy consumption of video representations at a display in a pixel-wise manner, wherein the information is derived from attenuation map information, wherein the one or more processors are further configured to update the display in accordance with the manifest file.

[0031] For some embodiments of the example client apparatus, the client includes the display.

[0032] For some embodiments of the example client apparatus, the client is a DASH client.

[0033] For some embodiments of the example client apparatus, the manifest file is a DASH MPD file.

[0034] For some embodiments of the example client apparatus, the client selects the information derived from the attenuation map information from the server.

[0035] For some embodiments of the example client apparatus, the server is a DASH server.

[0036] A fifth example apparatus in accordance with some embodiments may include at least one processor configured to perform any one of the methods listed above.

[0037] A sixth example apparatus in accordance with some embodiments may include a computer- readable medium storing instructions for causing one or more processors to perform any one of the methods listed above.

[0038] A seventh example apparatus in accordance with some embodiments may include at least one processor and at least one non-transitory computer-readable medium storing instructions for causing the at least one processor to perform any one of the methods listed above.

[0039] A computer-readable medium in accordance with some embodiments may include a computer- readable medium storing a bitstream generated according to any one of the methods listed above.

[0040] A signal in accordance with some embodiments may include a bitstream generated according to any one of the methods listed above.

[0041] In additional embodiments, encoder and decoder apparatus are provided to perform the methods described herein. An encoder or decoder apparatus may include a processor configured to perform the methods described herein. The apparatus may include a computer-readable medium (e.g. a non-transitory medium) storing instructions for performing the methods described herein. In some embodiments, acomputer-readable medium (e.g. a non-transitory medium) stores a video encoded using any of the methods described herein.

[0042] One or more of the present embodiments also provide a computer readable storage medium having stored thereon instructions for performing bi-directional optical flow, encoding or decoding video data according to any of the methods described above. The present embodiments also provide a computer readable storage medium having stored thereon a bitstream generated according to the methods described above. The present embodiments also provide a method and apparatus for transmitting the bitstream generated according to the methods described above. The present embodiments also provide a computer program product including instructions for performing any of the methods described.BRIEF DESCRIPTION OF THE DRAWINGS

[0043] FIG. 1A is a system diagram illustrating an example communications system according to some embodiments.

[0044] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to some embodiments.

[0045] FIG. 1C is a system diagram illustrating an example set of interfaces for a system according to some embodiments.

[0046] FIG. 2 is a schematic illustration showing an example DASH system architecture according to some embodiments.

[0047] FIG. 3 is a schematic illustration showing an example hierarchy for an MPD XML manifest file according to some embodiments.

[0048] FIG. 4 is a code listing for an example green video information structure according to some embodiments.

[0049] FIG. 5 is a schematic illustration showing an example Video and attenuation map representation preparation at the Dash server side according to some embodiments.

[0050] FIG. 6 is a schematic illustration showing example DASH client interfaces according to some embodiments.

[0051] FIGs. 7A-7B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0052] FIGs. 8A-8B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0053] FIGs. 9A-9B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0054] FIGs. 10A-10B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0055] FIGs. 11A-11 B form a code listing for an example MPD manifest file according to some embodiments.

[0056] FIGs. 12A-11 B form a code listing for an example MPD manifest file according to some embodiments.

[0057] FIG. 13A is a flowchart illustrating an example DASH server-side application process according to some embodiments.

[0058] FIG. 13B is a flowchart illustrating an example DASH server-side application process according to some embodiments.

[0059] FIG. 14 is a flowchart illustrating an example DASH client-side process according to some embodiments.

[0060] FIG. 15 is a schematic illustration showing an example DASH client-side process according to some embodiments.

[0061] FIG. 16 is a flowchart illustrating an example process for generating an attenuation image for display according to some embodiments.

[0062] FIG. 17 is a flowchart illustrating an example process for generating an attenuation image for display according to some embodiments.

[0063] FIGs. 18A-18B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0064] FIGs. 19A-19B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0065] FIGs. 20A-20B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments.

[0066] The entities, connections, arrangements, and the like that are depicted in— and described in connection with— the various figures are presented by way of example and not by way of limitation. As such, any and all statements or other indications as to what a particular figure "depicts,” what a particular element or entity in a particular figure "is” or "has,” and any and all similar statements— that may in isolation and outof context be read as absolute and therefore limiting— may only properly be read as being constructively preceded by a clause such as "In at least one embodiment, ... " For brevity and clarity of presentation, this implied leading clause is not repeated ad nauseum in the detailed description.DETAILED DESCRIPTION

[0067] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0068] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104, a ON 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station” and / or a "STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0069] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, aHome eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0070] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0071] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0072] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0073] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0074] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).

[0075] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., a eNB and a gNB).

[0076] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0077] The base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0078] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Althoughnot shown in FIG. 1 A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0079] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0080] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0081] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0082] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupledto the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0083] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0084] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0085] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.

[0086] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0087] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium- ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0088] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

[0089] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0090] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0091] Although the WTRU is described in FIGs. 1 A-1 B as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0092] In representative embodiments, the other network 112 may be a WLAN.

[0093] In view of FIGs. 1 A-1 B, and the corresponding description , one or more, or all, of the functions described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0094] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0095] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0096] The embodiments described herein are not limited to being implemented on a WTRU. Such embodiments may be implemented using other systems, such as the system of FIG. 1 C. FIG. 1 C is a system diagram illustrating an example set of interfaces for a system according to some embodiments. An extended reality display device, together with its control electronics, may be implemented using a system such as the system of FIG. 1 C. System 150 can be embodied as a device including the various components described below and is configured to perform one or more of the aspects described in this document. Examples of such devices, include, but are not limited to, various electronic devices such as personal computers, laptop computers, smartphones, tablet computers, digital multimedia set top boxes, digital television receivers, personal video recording systems, connected home appliances, and servers. Elements of system 150, singlyor in combination, can be embodied in a single integrated circuit (IC), multiple ICs, and / or discrete components. For example, in at least one embodiment, the processing and encoder / decoder elements of system 150 are distributed across multiple ICs and / or discrete components. In various embodiments, the system 150 is communicatively coupled to one or more other systems, or other electronic devices, via, for example, a communications bus or through dedicated input and / or output ports. In various embodiments, the system 1000 is configured to implement one or more of the aspects described in this document.

[0097] The system 150 includes at least one processor 152 configured to execute instructions loaded therein for implementing, for example, the various aspects described in this document. Processor 152 may include embedded memory, input output interface, and various other circuitries as known in the art. The system 150 includes at least one memory 154 (e.g., a volatile memory device, and / or a non-volatile memory device). System 150 may include a storage device 158, which can include non-volatile memory and / or volatile memory, including, but not limited to, Electrically Erasable Programmable Read-Only Memory (EEPROM), Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), flash, magnetic disk drive, and / or optical disk drive. The storage device 158 can include an internal storage device, an attached storage device (including detachable and non-detachable storage devices), and / or a network accessible storage device, as non-limiting examples.

[0098] System 150 includes an encoder / decoder module 156 configured, for example, to process data to provide an encoded video or decoded video, and the encoder / decoder module 156 can include its own processor and memory. The encoder / decoder module 156 represents module(s) that can be included in a device to perform the encoding and / or decoding functions. As is known, a device can include one or both of the encoding and decoding modules. Additionally, encoder / decoder module 156 can be implemented as a separate element of system 150 or can be incorporated within processor 152 as a combination of hardware and software as known to those skilled in the art.

[0099] Program code to be loaded onto processor 152 or encoder / decoder 156 to perform the various aspects described in this document can be stored in storage device 158 and subsequently loaded onto memory 154 for execution by processor 152. In accordance with various embodiments, one or more of processor 152, memory 154, storage device 158, and encoder / decoder module 156 can store one or more of various items during the performance of the processes described in this document. Such stored items can include, but are not limited to, the input video, the decoded video or portions of the decoded video, the bitstream, matrices, variables, and intermediate or final results from the processing of equations, formulas, operations, and operational logic.

[0100] In some embodiments, memory inside of the processor 152 and / or the encoder / decoder module 156 is used to store instructions and to provide working memory for processing that is needed during encoding or decoding. In other embodiments, however, a memory external to the processing device (for example, the processing device can be either the processor 152 or the encoder / decoder module 152) is used for one or more of these functions. The external memory can be the memory 154 and / or the storage device 158, for example, a dynamic volatile memory and / or a non-volatile flash memory. In several embodiments, an external non-volatile flash memory is used to store the operating system of, for example, a television. In at least one embodiment, a fast external dynamic volatile memory such as a RAM is used as working memory for video coding and decoding operations, such as for MPEG-2 (MPEG refers to the Moving Picture Experts Group, MPEG-2 is also referred to as ISO / IEC 13818, and 13818-1 is also known as H.222, and 13818-2 is also known as H.262), HEVC (HEVC refers to High Efficiency Video Coding, also known as H.265 and MPEG-H Part 2), or WC (Versatile Video Coding, a new standard being developed by JVET, the Joint Video Experts Team).

[0101] The input to the elements of system 150 can be provided through various input devices as indicated in block 172. Such input devices include, but are not limited to, (i) a radio frequency (RF) portion that receives an RF signal transmitted, for example, over the air by a broadcaster, (ii) a Component (COMP) input terminal (or a set of COMP input terminals), (iii) a Universal Serial Bus (USB) input terminal, and / or (iv) a High Definition Multimedia Interface (HDMI) input terminal. Other examples, not shown in FIG. 1 C, include composite video.

[0102] In various embodiments, the input devices of block 172 have associated respective input processing elements as known in the art. For example, the RF portion can be associated with elements suitable for (i) selecting a desired frequency (also referred to as selecting a signal, or band-limiting a signal to a band of frequencies), (ii) downconverting the selected signal, (iii) band-limiting again to a narrower band of frequencies to select (for example) a signal frequency band which can be referred to as a channel in certain embodiments, (iv) demodulating the downconverted and band-limited signal, (v) performing error correction, and (vi) demultiplexing to select the desired stream of data packets. The RF portion of various embodiments includes one or more elements to perform these functions, for example, frequency selectors, signal selectors, band-limiters, channel selectors, filters, downconverters, demodulators, error correctors, and demultiplexers. The RF portion can include a tuner that performs various of these functions, including, for example, downconverting the received signal to a lower frequency (for example, an intermediate frequency or a near-baseband frequency) or to baseband. In one set-top box embodiment, the RF portion and its associated input processing element receives an RF signal transmitted over a wired (for example, cable) medium, and performs frequency selection by filtering, downconverting, and filtering again to a desiredfrequency band. Various embodiments rearrange the order of the above-described (and other) elements, remove some of these elements, and / or add other elements performing similar or different functions. Adding elements can include inserting elements in between existing elements, such as, for example, inserting amplifiers and an analog-to-digital converter. In various embodiments, the RF portion includes an antenna.

[0103] Additionally, the USB and / or HDMI terminals can include respective interface processors for connecting system 150 to other electronic devices across USB and / or HDMI connections. It is to be understood that various aspects of input processing, for example, Reed-Solomon error correction, can be implemented, for example, within a separate input processing IC or within processor 152 as necessary. Similarly, aspects of USB or HDMI interface processing can be implemented within separate interface ICs or within processor 152 as necessary. The demodulated, error corrected, and demultiplexed stream is provided to various processing elements, including, for example, processor 152, and encoder / decoder 156 operating in combination with the memory and storage elements to process the datastream as necessary for presentation on an output device.

[0104] Various elements of system 150 can be provided within an integrated housing, Within the integrated housing, the various elements can be interconnected and transmit data therebetween using suitable connection arrangement 174, for example, an internal bus as known in the art, including the Inter- IC (I2C) bus, wiring, and printed circuit boards.

[0105] The system 150 includes communication interface 160 that enables communication with other devices via communication channel 162. The communication interface 160 can include, but is not limited to, a transceiver configured to transmit and to receive data over communication channel 162. The communication interface 160 can include, but is not limited to, a modem or network card and the communication channel 162 can be implemented, for example, within a wired and / or a wireless medium.

[0106] Data is streamed, or otherwise provided, to the system 150, in various embodiments, using a wireless network such as a Wi-Fi network, for example IEEE 802.11 (IEEE refers to the Institute of Electrical and Electronics Engineers). The Wi-Fi signal of these embodiments is received over the communications channel 162 and the communications interface 160 which are adapted for Wi-Fi communications. The communications channel 162 of these embodiments is typically connected to an access point or router that provides access to external networks including the Internet for allowing streaming applications and other over-the-top communications. Other embodiments provide streamed data to the system 150 using a set-top box that delivers the data over the HDMI connection of the input block 172. Still other embodiments provide streamed data to the system 150 using the RF connection of the input block 172. As indicated above, various embodiments provide data in a non-streaming manner. Additionally, various embodiments use wireless networks other than Wi-Fi, for example a cellular network or a Bluetooth network.

[0107] The system 150 can provide an output signal to various output devices, including a display 176, speakers 178, and other peripheral devices 180. The display 176 of various embodiments includes one or more of, for example, a touchscreen display, an organic light-emitting diode (OLED) display, a curved display, and / or a foldable display. The display 176 can be for a television, a tablet, a laptop, a cell phone (mobile phone), or other device. The display 176 can also be integrated with other components (for example, as in a smart phone), or separate (for example, an external monitor for a laptop). The other peripheral devices 180 include, in various examples of embodiments, one or more of a stand-alone digital video disc (or digital versatile disc) (DVR, for both terms), a disk player, a stereo system, and / or a lighting system. Various embodiments use one or more peripheral devices 180 that provide a function based on the output of the system 150. For example, a disk player performs the function of playing the output of the system 150.

[0108] In various embodiments, control signals are communicated between the system 150 and the display 176, speakers 178, or other peripheral devices 180 using signaling such as AV. Link, Consumer Electronics Control (CEC), or other communications protocols that enable device-to-device control with or without user intervention. The output devices can be communicatively coupled to system 1000 via dedicated connections through respective interfaces 164, 166, and 168. Alternatively, the output devices can be connected to system 150 using the communications channel 162 via the communications interface 160. The display 176 and speakers 178 can be integrated in a single unit with the other components of system 150 in an electronic device such as, for example, a television. In various embodiments, the display interface 164 includes a display driver, such as, for example, a timing controller (T Con) chip.

[0109] The display 176 and speaker 178 can alternatively be separate from one or more of the other components, for example, if the RF portion of input 172 is part of a separate set-top box. In various embodiments in which the display 176 and speakers 178 are external components, the output signal can be provided via dedicated output connections, including, for example, HDMI ports, USB ports, or COMP outputs.

[0110] The system 150 may include one or more sensor devices 168. Examples of sensor devices that may be used include one or more GPS sensors, gyroscopic sensors, accelerometers, light sensors, cameras, depth cameras, microphones, and / or magnetometers. Such sensors may be used to determine information such as user's position and orientation. Where the system 150 is used as the control module for an extended reality display (such as control modules 124, 132), the user's position and orientation may be used in determining how to render image data such that the user perceives the correct portion of a virtual object or virtual scene from the correct point of view. In the case of head-mounted display devices, the position and orientation of the device itself may be used to determine the position and orientation of the user for the purpose of rendering virtual content. In the case of other display devices, such as a phone, a tablet, a computer monitor, or a television, other inputs may be used to determine the position and orientation of theuser for the purpose of rendering content. For example, a user may select and / or adjust a desired viewpoint and / or viewing direction with the use of a touch screen, keypad or keyboard, trackball, joystick, or other input. Where the display device has sensors such as accelerometers and / or gyroscopes, the viewpoint and orientation used for the purpose of rendering content may be selected and / or adjusted based on motion of the display device.

[0111] The embodiments can be carried out by computer software implemented by the processor 152 or by hardware, or by a combination of hardware and software. As a non-limiting example, the embodiments can be implemented by one or more integrated circuits. The memory 154 can be of any type appropriate to the technical environment and can be implemented using any appropriate data storage technology, such as optical memory devices, magnetic memory devices, semiconductor-based memory devices, fixed memory, and removable memory, as non-limiting examples. The processor 152 can be of any type appropriate to the technical environment, and can encompass one or more of microprocessors, general purpose computers, special purpose computers, and processors based on a multi-core architecture, as non-limiting examples.

[0112] This application relates to the field of communications systems for video streaming aiming at providing a signaling mechanisms to enable a display to control its energy usage and rendered video quality in the context of a DASH delivery, specified in ISO / IEC 23001-10] ISO / IEC 23009-1 , Dynamic Adaptive Streaming over HTTP (DASH) — Part 1: Media Presentation Description and Segment Formats ‘ISO / IEC 23009-1")', and ISO / IEC 23009-3, Dynamic Adaptive Streaming over HTTP (DASH) — Part 3 Implementation Guidelines (‘ISO / IEC 23009-3") on the screen of a desktop or laptop computer, a Smartphone, a tablet, a set-top box, a television connected to the internet.

[0113] Reducing energy consumption of electronic devices has become a requirement not only for electronic devices manufacturers but also to limit, as much as possible, the environmental impact and to contribute to the emergence of a sustainable display industry. The increase in display resolution from SD to HD to 4K and soon to 8K and beyond, as well as the introduction of high dynamic range imaging, has brought about a corresponding increase in energy requirements of display devices. Conversely, there is a global need to reduce energy consumption. Indeed, displays are a source of energy consumption, whether for battery-powered devices (e.g., smartphones) or in the global video distribution chain.

[0114] Organic Light Emitting Diode (OLED) displays are getting more and more popular because of numerous advantages compared to non-emissive displays such as Thin-Film Transistor Liquid Crystal Displays (TFT-LCDs). Rather than using a uniform backlight, OLED displays are composed of LEDs as image pixels. OLEDs power consumption is therefore highly correlated to the image content and can be readily estimated by considering the luminance level of the displayed image pixels. Although OLED displaysconsume energy in a more controllable and efficient manner, they are still the most important source of energy consumption in a video transmission chain.

[0115] It is therefore interesting to elaborate energy-aware images, i.e., that will need less energy when displayed on CE displays, notably OLED displays. An example of such an elaboration is discussed in the ‘518 application, which discusses a technique to build energy-aware images, based on the learning of a dimming map with good properties such as a smoothness property and a scalable property.

[0116] When in a video coding chain, the question is raised of where such a processing of building energy- aware images should be applied, and several stages might be envisioned: at the encoder, at the decoder, or at the display side.

[0117] The ‘518 and ‘066 applications discuss a method of signaling to transmit the dimming maps and make them available for use at the display side of the chain. In this solution, a new SEI message is created, and the dimming maps are transmitted as auxiliary data up to the receiver side.

[0118] The ‘958 application discusses a method of signaling to transmit the dimming maps and make them available for use at the display side of the chain via an interactive streaming application. In this application, new tracks are created for dimming maps and are associated with the rendered video for which the receiver expects a reduction of the energy consumption. This application discusses new attributes for the @AdaptationSet and Representation elements of the DASH MPD manifest file.

[0119] The present application aims at proposing an alternative of the new @AdaptationSet and ©Representation attributes by using at least one metadata track carrying the Attenuation Map Information in respect with the storage format for timed metadata within the ISO Base Media File Format (ISO / IEC 14496- 12 and ISO / IEC 15444-12).

[0120] FIG. 2 is a schematic illustration showing an example DASH system architecture according to some embodiments. This new timed metadata tracks carrying Attenuation Map Information are signaled in the MPD Manifest file specified for the dynamic adaptative streaming over HTTP (i.e., DASH) that enable delivery of continuous media content from standard HTTP servers to HTTP clients and enable caching of content by standard HTTP caches.

[0121] FIG. 2 illustrates an example of adaptive streaming system 200 based on DASH. The system 200 includes a DASH server 206 and a DASH client 210. The server 206 is for example implemented through a content provider server, and a DASH client is for example implemented using a display device. When a DASH client 210 wishes to play multimedia content in adaptive streaming, it first gets a Media Presentation Description (MPD), a.k.a. a manifest, describing how this multimedia content might be obtained. This is generally done by getting the manifest from an URL (Uniform Resource Locator), for example through HTTPprotocol as represented by the HTTP Cache 208 or by other means (e.g., broadcast, broadband service description, and so on). The manifest is generated in advance by the DASH media presentation preparation / description 202. The manifest may be static or may be updated dynamically. The manifest lists the available representations, also called instances or versions, of the multimedia content, with variations in terms of coding bitrate, image resolution, and other properties. A representation may be associated with a given quality level expressed as a bitrate. The data stream of each representation is provided by the DASH Segment delivery function 204 and is divided into segments (also called chunks) of equal duration (e.g., a few seconds), accessible by a separate URL. The plurality of segments is prepared by the DASH Media Presentation Preparation. Different versions of each segment are prepared, ready to be provided to the clients. When playing multimedia content, a DASH client may smoothly switch from one quality level to another between two segments, to dynamically adapt to network conditions. When low bandwidth is available, a client requests low bitrate chunks and they may request higher bitrate chunks when higher bandwidth becomes available. As a result, the video quality may vary while playing but rarely suffers from interruptions (also called freezes).

[0122] At the client side, the segments may be selected based on a measure of the available bandwidth of the transmission path. A DASH client usually requests the representation of a segment corresponding to a bitrate encoding and thus a quality compliant with the measured bandwidth.

[0123] FIG. 3 is a schematic illustration showing an example hierarchy for an MPD XML manifest file according to some embodiments. FIG. 3 illustrates an example structure 300 of a Media Presentation Description 302 based on DASH. The Media Presentation Description 302 includes period elements 304, 312 (regular periods, early available periods, etc.) of equal length (60 seconds in the example), each of the period being identified by a Period ID, a start value representing the start time with respect to the first frame of the multimedia content of the period and a duration. Each period includes one or more adaptation sets 306, 314 which contain(s) alternate representations 308, 316 of the multimedia components considered to be perceptually equivalent. Adaptation set and the contained representations shall be prepared and contain sufficient information such that seamless switching across different representations in one adaptation set is possible. Multimedia content components being video, audio, teletext, subtitle, etc. Each representation 308, 316 includes a segment info 310, 318 that itself includes different sub-segments 320 having relative start time with respect to the current segment. From one period to another, adaptation sets and the contained representations may be different.

[0124] For some embodiments, a mechanism for transmitting a pixel-wise attenuation map in an adaptive video streaming environment enables a receiver device to control its energy reduction rate when displaying the video. Some embodiments of an adaptation set for DASH may have an identifier (@id) attributethat includes a string "ami”, which stands for "Attenuation Map Information", for example, or that includes another string representing the notion of attenuation map signaling (e.g., "dm” for dimming map, "dpr” for display power reduction). This string is known by the DASH server and the DASH client . This identifier indicates that the adaptation set includes attenuation map information. Such an adaptation set enables a DASH MPD to list pixel-wise attenuation map representations available on the DASH server as different representations. Such an adaptation set also enables a DASH client to select one of the representations to control its energy reduction rate when displaying the video. Instead of using the identifier @id=”ami” to identify the new type of Adaptation Set Element, the attribute @contentType of an adaptation set may be set to, for example, "Attenuation Map" or "am" or other strings to indicate the adaptation set element signals attenuation map representations. In the rest of this application, the term @id="ami" will be used for simplification.

[0125] A DASH client may also select multiple "ami” adaptation sets, for example identified by @id="amiX", with X in the range 0..n, in the MPD manifest file, and therefore allow a selection of an appropriate attenuation map corresponding to a chosen energy reduction in which the adaptation sets have different values for the energy reduction. The same principle applies to the other parameters of the adaptation set. According to its energy consumption strategy, a DASH client may ignore the "ami” adaptation set. In this case, no pixel-wise attenuation map representation is requested by the DASH client, and the video is displayed without any modification. As a result, the DASH client may not benefit from energy reduction.

[0126] For some embodiments, the "ami” adaptation set provides information on how to use the pixel-wise attenuation map representation, the type of displays on which to apply the attenuation map representation, the type of post-processing to further use the attenuation map representation, the type of downsampling and its subsequent upsampling if any to apply as a preprocessing before using the attenuation map representation on an image, and some indicative metrics of the expected energy reduction and on the expected quality impact of the use of such an attenuation map representation.

[0127] For some embodiments, the "ami” adaptation set is dynamically updated within the DASH MPD per period and the granularity of the update may be based on time (per period / duration of the video content), on temporal layers (per temporal layer), on slice type (per intra and inter slices) or on parts of the picture (Slices, Tiles, Sub-pictures). An MPD that includes an adaptation set with @id=”ami” is hereafter named AM I- MPD. Such an MPD is generated at the DASH server, based on information provided by a processing block that handles the generation and encoding of the attenuation map from an input image. The AMI-MPD is parsed by a DASH client. In response, a pixel-wise attenuation map representation, for example corresponding to a target reduction rate, is selected and requested by the DASH server. When received, theinformation from the adaptation set and the representations are provided to the media engine and to the post-processing module if required, to apply the selected attenuation map representation to the video component representation. This operation results in a reduced energy consumption of the DASH client because the image displayed uses less energy than the original image.

[0128] For some embodiments, multiple attenuation map representations are requested and are combined together. This operation allows a new attenuation map to be produced with an intermediate reduction rate, not directly available in the list of attenuation map representations. The new attenuation may be generated by interpolating two attenuation map representations according to a weighting corresponding to the respective attenuation rates. In such an enhanced ecosystem, the DASH server and client are energy- aware devices in the sense that an energy-aware DASH server prepares data that are needed to allow an energy- aware DASH client to control its energy consumption through the selection, reception, and application of a pixel-wise dimming map.

[0129] The additional signaling enables a dash player to select a video media representation, one or several complementary attenuation maps (or dimming map), and one or several timed metadata representation(s) to modify the video and reduce the energy consumption while displaying the video on the screen of the receiver device or the screen connected to the receiver. A timed metadata representation may be associated with one or several attenuation map representation(s).

[0130] Currently, as understood, the control of the energy impact of displaying a video is rather limited, and not linked to pixel-wise information announced as a collection of resource identifiers within the DASH Media Presentation Description (MPD) manifest file. The standard ISO / IEC 23001-11 , Energy-Efficient Media Consumption (Green Metadata), (‘ISO / IEC 23001-11") specifies metadata (Green Metadata) that facilitates reduction of energy usage during media consumption (decoding and display operation), and specifically for reducing display power consumption.

[0131] The metadata for display adaptation are defined in section "Display power reduction using display adaptation” of the standard ISO / IEC 23001-11. They are particularly well tailored to non-emissive pixels display technology embedding backlight illumination such as LCD. They are designed to attain display energy reductions by using display adaptation techniques that generate dynamically, on the emitter side, some RGB- component statistics and quality indicators metrics about the consumed video content. They may be used to perform RGB picture components rescaling to set the best compromise between backlight / voltage reduction and picture quality, reducing voltage, and therefore allowing to reduce the energy consumption. However, these metadata convey global information and, in no case, they are understood to not convey any information that would help the use of a pixel-wise attenuation map, since such a map is of no use for non-emissive pixel types of displays.

[0132] The document ISO / IEC 23001-11 (Annex B.3) specifies how to convey these display green metadata in adaptative streaming as a DASH timed metadata representation with a ©codecs attribute = “dipi” which may be retrieved and used by the decoder to perform post-processing to all the available media representations and reduce energy consumption.

[0133] While the ‘566 and ‘068 applications describe user data SEI messages registered by ITU-T Recommendation T.35, the genericity of such messages makes their use inefficient for some of the current use cases. The ‘908 application describes a new SEI message, which is conveyed within the codec signaling and is aimed at guiding the use of a pixel-wise attenuation map.

[0134] The problem to be solved is how to provide, within a DASH MPD manifest, information derived from a dimming or attenuation map and, related to its further use, that will serve for the elaboration of energy aware images at the receiver side (e.g., OTT ecosystem). The information carried by a green video timed metadata representation is relative to the attenuation map representation which is associated with a video representation.

[0135] This information adds the capability for a service provider to use the methods described herein instead of using SEI messages and auxiliary data within the codec bitstream as described in the 719 and ‘185 applications. As understood, there are no such mechanisms and signaling for providing information within the DASH MPD that aims at reducing the energy consumption of video representations at display in a pixel-wise manner.

[0136] FIG. 4 is a code listing for an example green video information structure according to some embodiments. FIG. 4 shows an example code listing 400. The standard ISO / IEC 23001-11 specifies metadata aiming at signaling information for display adaptation. These metadata may include RGB- component statistics and quality indicators of the video content. The statistics are used to set display controls in the presentation subsystem so that desired quality levels and corresponding display power reductions are attained. In Dynamic Adaptative Streaming, the metadata (see chapter "Display power reduction using display adaptation” of the ISO / IEC 23001-11 document) are sent in a dedicated "green video” adaptation set with multiple representations associated with different representations of the "video” adaptation set:

[0137] An adaptation set with id=”green_video” conveys metadata for reduction of the energy consumed by displays, each association conveys global information on statistics derived from the input content of each representation (such as vO, v1 , v2, ...). This kind of adaptation set does not allow the DASH client to be informed of the availability of a (or several) pixel-wise attenuation map(s) on the content DASH server, but once used on the dash client, this kind of adaptation set allows for a more precise control both on the energy reduction and the quality of experience, and allows for a reduced bitrate overhead because only the attenuation maps selected by the DASH client are transmitted from the dash server. FIG. 4 shows an exampleof such an adaptation set with an id=”green_video”. Different ©codecs values allow selection of either "display information " already specified in ISO / IEC 23001-11 or "attenuation map information". This permits not downloading data that will not be used by the receiver.

[0138] The application uses an adaptation set with id=”ami” (Attenuation Map Information) in the DASH MPD to list the available pixel-wise attenuations maps on the DASH server and to allow the DASH client to select one or several of them or none and control its energy reduction rate when displaying the video on its display.

[0139] The selection and use of the attenuation map(s) by the receiver is performed by parsing for an adaptation set id=”green video” with a ©codecs attribute value of "amii”(Attenuation Map Information Indication). This adaptation set element contains the list of the timed metadata representations associated with the attenuation map(s) with the attribute @associationType=”cdsc”.

[0140] The timed metadata representation track carries the Attenuation Map Information Indication (AM 11) metadata type (which is “amii”) in an ISO Base Media File Format (ISOBMFF) (ISO / IEC 14496-12 and ISO / IEC 15444-12). The corresponding storage format for the Attenuation Map Information metadata in the ISOBMFF is identified by a unique sample entry code.

[0141] For some embodiments, the Attenuation Map Information (AMI) metadata provides:• How to use the pixel-wise attenuation map,• The type of displays to apply the attenuation map,• The type of processing to further use the attenuation map,• The type of downsampling and its subsequent upsampling if any to apply as a preprocessing before using the attenuation map on an image,• Some indicative metrics of the expected energy reduction and on the expected quality impact of the use of such an attenuation map

[0142] The DASH client may decide whether or not to use an adaptation set with id=”ami” and / or an adaptation set id=”green video” with @codecs=”amii” depending on its energy consumption strategy. For some embodiments, if the client decides "no”, no green video metadata with @codecs=”amii” and pixel-wise attenuation map representations are requested by the DASH client, and the video is displayed without any modification. For some embodiments, if the client decides "yes”, the green video metadata with @codecs=”amii” and the associated pixel-wise attenuation map are requested, retrieved, and the attenuation map is applied to the video thanks to the information of the green video metadata by the dash client to reduce the energy consumption at the display side.

[0143] The adaptation sets for id=”ami” and for id=”green_video” with ©codecs-' amii” are dynamically updated within the DASH MPD per period and the granularity of the update may be based on:Time: per period / duration of the video• Temporal layers: per temporal layer• Slice type: per intra and inter slices• Parts of the picture: slices, tiles, sub-pictures

[0144] For some embodiments, the MPD and the adaptation sets id=”ami” and id=”green video” with @codecs=”amii” are generated at the DASH server, from information provided by the processing block responsible for the elaboration of the attenuation map.

[0145] For some embodiments, operation may occur as described here. The adaptation sets id=”ami” and id=”green video” with ©codecs-’ amii” are parsed by the DASH client from the MPD. One or several pixelwise attenuation map(s) is / are requested from the DASH server and received. The information within the adaptation set and representations are sent to the decoder and a post-processing block to apply the attenuation map to the video component.

[0146] For some embodiments, a system may include an encoder, an origin server packager, and a decoder. The encoder is asked to create signal energy-related metadata into the bitstream. The decoder is asked to decode these metadata.

[0147] Metadata syntax and semantics are provided in the shape of the Attenuation Map Information metadata type ("amii”) in an ISO Base Media File Format (ISOBMFF) (ISO / IEC 14496-12 and ISO / IEC 15444-12). The codec blocks that are affected are not depicted in the figures because they relate to high- level syntax carried in an SEI message.

[0148] The application describes a new adaptation set id for a DASH MPD to signal attenuation map(s) and thereby reduce energy consumption by a display, which may be at the client or associated with the client. For some embodiments, such an adaptation set has an id=”ami” in the DASH MPD. Such an adaptation set relates to one or more attenuation map representation(s) (which may be available on the DASH server side) in addition to multiple representations of a video media component. The information relative to these attenuation maps may be carried in timed metadata representation with an id=”green video” and @codecs=”amii” for the attribute value. The application may be implemented on the DASH server and client sides for the delivery of media.DASH Server

[0149] FIG. 5 is a schematic illustration showing an example Video and attenuation map representation preparation at the Dash server side according to some embodiments. In FIG. 5, the Input Video 502 is provisioned to the dash system 500 at the server side. The entity may handle the presentation preparation initiates and manage the following items:• The encoding 504 of the different video component representations without any modification of the state of the art. As understood, other systems may provide functionality to encode and signal different video representations.• The computing and the encoding of the attenuation maps 514, 516, 518, 520, 522, 524 with different energy reduction rates in the Map Computing and Encoding 506 entity.• The creation of the Attenuation Map Information timed metadata of type—’amii” and storage in an ISO Base Media File Format (i.e. ISOBMFF) (ISO / IEC 14496-12 and ISO / IEC 15444-12).• The insertion in the MPD manifest file of the new kind of Adaptation Set id=”ami” and the attenuation map representations associated to the video representations.• The insertion in the MPD manifest file of the Adaptation Set id=”green video” and the Attenuation Map Information timed metadata Representations associated to the attenuation map representations.

[0150] The output(s) of the Encoding and Attenuation Map Computing block(s) 514, 516, 518, 520, 522, 524 is / are transmitted to the DASH delivery block 508, which may create the following segments of a media component:• The segments of the different video representations (different bitrate, spatial resolution, frame rate,• The segments of the attenuation maps representations,• The segments of the Attenuation Map Information timed metadata representations

[0151] The MPD manifest file is transmitted to the MPD delivery function 526 to respond to any request from the DASH Client 512.

[0152] Segment formats may be based on ISOBMFF with fragmented movie files. (Sub)Segments are encoded as movie fragments containing a track fragment as defined in ISO / IEC 14496-12 with the constraints of being independently decodable.

[0153] The segments may be cached in an HTTP cache 510 for performance reasons. As for the segments of the multiple video representations, only the segments of the requested attenuation map representations and associated Attenuation Map Information timed metadata representations are available in the cache for some embodiments. The dash client requests the attenuation map representation depending on its energy reduction strategy from the information of the MPD manifest file (Attenuation Map Information timed metadata Representations).

[0154] FIG. 5 illustrates an example of architecture for an energy-aware DASH server according to an embodiment. This architecture is for example implemented by a content provider server. The original input video is provisioned to the dash system to an encoding block that prepares and encodes the input video as described in relation with FIGs. 2 and 3, i.e., splitting the video into segments and encoding the segments for the different video representations with for example different bitrates, different spatial resolutions, and / or different frame rates. The Map Generation module determines, from decoded images of these different video representations, a set of corresponding attenuation maps, one attenuation map per decoded image. Thesemaps are then conventionally encoded in so-called attenuation map representations using the same principle as for video segments. Multiple attenuation map representations may be used, for example with different energy reduction rates, as illustrated in the figure (one representation with 10% reduction, and a second representation with 20%). The DASH media presentation preparation module handles the preparation of the data used within the system by driving the Encoding module and the Map Generation module, for example establishing the set of different bitrates, different spatial resolutions, and / or different frame rates for the different video representations as well as listing the reduction rates for which attenuation maps should be generated. The DASH media presentation preparation module 528 then generates the MPD manifest file, that includes an "ami” adaptation set and the attenuation map representations, from metadata obtained from the Encoding module and the Map Generation module. The metadata provides information for the element attributes of the adaptation set and representations (for example: energy reduction rate, usage of the attenuation map). The MPD manifest file is provided to the MPD delivery function to respond to requests from the DASH Client. The data generated by the Encoding module and the Map Generation module are combined together by the DASH Segment delivery function to create the segments of the different video representations and the segments of the attenuation maps representations. These segments, including the video related segments and the corresponding attenuation map representations (i.e., 10% or 20% in the example of the figure), will then be retrieved by a DASH client according to the information of the MPD manifest file and to a selected energy reduction strategy. As described below with respect to FIG. 6, the DASH client will then apply the attenuation to the video to generate an energy-aware image 480 that will require less energy when being displayed on a screen than the original image.

[0155] The segments are cached in an HTTP cache for performance reasons. This cache is handled so that only the relevant segments of a selected video representation amongst the multiple video representations and only the segments of the selected attenuation map representations are available in the cache, thus ensuring a minimal load on the distribution network. Segment formats are based on ISO BMFF with fragmented movie files, i.e. (Sub)Segments are encoded as movie fragments containing a track fragment as defined in ISO / IEC 14496-12 with the constraints of being independently decodable.DASH Client

[0156] FIG. 6 is a schematic illustration showing example DASH client interfaces according to some embodiments. FIG. 6 shows an example DASH client architecture 600 with an ability to generate an attenuation map adaptation set. For some embodiments, video media and timed AMI metadata and AM HTTP requests / segments may be exchanged between a DASH server 602 and a DASH access engine 606 via an HTTP cache 604.

[0157] FIG. 6 illustrates an example of architecture 600 for an energy-aware DASH client according to an embodiment. This architecture is for example implemented by a display device. FIG. 6 illustrates the logical components of a DASH client 608 and the relation to other components in a media streaming application. The DASH client 608 is operated under control of a Media Streaming Application 610. The DASH access engine 606 requests and receives from the server the Media Presentation Description (MPD) containing information related to both Video Media component representations and the "ami” adaptation set with a list of attenuation map representations associated to the video media component representation. For some embodiments, the DASH access engine 606 may also request Attenuation Map Information timed metadata representations with the Adaptation Sets id=”green video” and @codecs=”amii”. The energy reduction metadata are provided to the Selection Logic module. The energy reduction metadata includes information about the attenuation map representations, how to use them to reduce the energy consumption when the video component is presented on the display, the expected reduction rate and the associated quality or experience metric. The Selection Logic module 612 may use the energy reduction metadata to select the media components of the service, requested by the Media Streaming application, through interactions with the energy consumption module. This module receives from the Media Streaming application 610 the energy profile determined by the energy reduction strategy of the device itself or the End-user and provides the requested reduction rates to the Selection Logic module 612. Upon a selection of the representations, the Media Streaming application 610 configures the Decoding module 614 (e.g., codec, number of attenuation map representations, ...), the attenuation map post-processing 616, the video and attenuation map application module 618 and the rendering module 620. Thus, the DASH access engine requests and receives the video media segments and the attenuation map representation segments corresponding to the selected representation. The attenuation map and the Video component representations are decoded by the decoding module. The attenuation map representations are optionally post-processed when needed (for example for up-scaling). The attenuation map representations are combined with the video by the application module and the resulting video is rendered on the display by a video rendering module.

[0158] FIG. 6 illustrates the logical components of a conceptual DASH Client model and the relation to other components in a media streaming application. In this figure, the DASH access engine requests and receives the Media Presentation Description (MPD) containing both Video Media component representations, the new attenuation map adaptation sets id=”ami” with a list of attenuation map representations associated (@associationType=”amit”) to the video component representation and the green video adaptation sets with ©codecs-’ amii” with the list of the Attenuation Map Information timed metadata representations associated (@associationType=”cdsc”) to the attenuation map representations, constructs and issues requests in relation with its energy reduction strategy and receives segments or parts of segments.

[0159] The DASH client may use the Attenuation Map Information timed metadata, retrieved from one or several representations of the green video adaptation sets with @codecs=”amii” associated to one or several attenuation map(s)(@associationType=”cdsc”), for the selection of the attenuation maps by communication with the media streaming application and the knowledge of the energy reduction strategy of the device itself or the End-user. The new Information relative to the current application may be provided and may include information about the attenuation maps and how to use them to reduce the energy consumption when the video component is presented on the display.

[0160] For some embodiments, the DASH access engine performs the following actions:• Requests the Attenuation Map Information timed metadata representation segments,• Retrieves the information relative to one or several attenuation maps,• Decides whether the relative attenuation map(s) match(es) with the energy reduction strategy of the device or the end-user,• Selects the attenuation map(s) and the video component(s)• Outputs media and the maps in MPEG container formats or parts thereof, together with timing information that maps the internal timing of the continuous media to the timeline of the Media Presentation.

[0161] The attenuation map and video component representations are decoded, the attenuation map is applied, and the resulting video is rendered on the display.Attenuation Map Information Timed Metadata

[0162] The Attenuation Map Information timed metadata is retrieved from the timed metadata representation of the green video adaptation sets with @codecs=”amii” and associated with one or several attenuation map(s) (@associationType=”cdsc”).

[0163] The information may be carried in an ISOBMFF file as sample entries with a unique value for the ©codecs equal to “amii”. Such a sample entry is standardized in the ISO / IEC 23001-10 specification.Attenuation Map Information Sample Entry DefinitionSample Entry Type: ‘amii’Container: Sample Description Box (‘stsd’)Mandatory: NoQuantity: 0 or n

[0164] The sample entry is stored in the sample description box ("stsd”).Attenuation Map Information Sample Entry Syntax

[0165] Sample Attenuation Map Information metadata is as follows:c las s AttenuationMapInf ormat ionlndicat ionMetaDataSampleEntry ( ) extends MetaDataS ampleEntry ( ' amii ' ) {}

[0166] The examples shown in FIGs. 7A-9B are examples that build on this sample attenuation map information indication (AMII) class structure.

[0167] FIGs. 7A-7B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. FIGs. 7A and 7B show example code listings 700, 750. Each representation of the green video adaptation sets with ©codecs-’ amii” carries the information of only one attenuation map.

[0168] FIGs. 8A-8B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. FIGs. 8A and 8B show example code listings 800, 850. Each representation of the green video adaptation sets with @codecs=”amii” carries the information of several attenuation maps in separate sample entries. The am ID data field is added to identify the attenuation map (e.g., the amID variable may be the track ID of the attenuation map in which information is associated) and to retrieve relative attenuation map information.

[0169] FIGs. 9A-9B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. FIGs. 9A and 9B show example code listings 900, 950. Each representation of the green video adaptation sets with @codecs=”amii” carries the information of several attenuation maps in a unique sample entry. Compared to FIG. 7B, the amID data field is added in FIG. 9B to identify the attenuation map and to retrieve relative attenuation map information. An amiAmNumber field stores the quantity of attenuation maps with associated attenuation map information. An index value i, which goes from 0 to (amiAmNumber-1), is an index used with attenuation map information arrays and function calls in the class AttenuationMapInformationlndicationMetaDataSample.

[0170] FIGs. 10A-10B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. FIGs. 10A and 10B show example code listings 1000, 1050. Each representation of the green video adaptation sets with ©codecs-’ amii” carries the information of several attenuation maps in a unique sample entry. For some embodiments, as shown in the example of FIG. 10B, the amID data field is removed compared to FIG. 9B.

[0171] An amiAmNumber field stores the quantity of attenuation maps with associated attenuation map information. This associated attenuation map information is referenced by an additional box class TrackReferenceBox in a track box carrying attenuation map information. This class TrackReferenceBox uses an array TrackReferenceTypeBox[] for such referencing. An index value i, which goes from 0 to (amiAmNumber-1), is an index used with attenuation map information arrays and function calls in the class AttenuationMapInformationlndicationMetaDataSample and corresponds to the track_IDs[] array of theTrackReferenceTypeBox box of reference type "damt” (which is an acronym for Display Attenuation Map Type). For some embodiments, the field amiAmNumber may be, for example, 1 or 2, without the use of the amID field within the AttenuationMapInformationlndicationMetaDataSample class.

[0172] Table 1 describes each of these new attributes.Table 1Attenuation Map Information Sample Entry Semantic

[0173] Setting amiCancelFlag equal to 1 indicates that the sample cancels the persistence of any previous attenuation map Information Indication sample in output order. Setting amiCancelFlag equal to 0 indicates that attenuation map Information parameters follow. This flag is used in the example code shown in FIGs. 7B, 8B, and 9B, and a value of 0 for the amiCancelFlag (or "ami_cancel_flag” as used in the sample code) allows the rest of the class to be created and used. Some embodiments may use an amiCancelFlag attribute, while some embodiments may not use the amiCancelFlag attribute.

[0174] In Table 2, the amiDisplayModel attribute is a bit field mask indicating on which display models the attenuation map may be used. The example of amiDisplayModel = 3 means the attenuation map may be used for both Non emissive and Emissive display modelsTable 2

[0175] The attribute amiMapApproximationModel as shown in Table 3 shows the model used to extrapolate the attenuation map sample values(s) from a set of attenuation maps with individual energy reduction rate(s) to another set of attenuation map sample values with a different energy reduction rate.

[0176] Setting amiMapApproximationModel equal to 0 indicates that a linear scaling of the attenuation map sample values of the current attenuation map given its respective amiEnergyReductionRate should be considered to obtain corresponding attenuation map sample values for another energy reduction rate.

[0177] Setting amiMapApproximationModel equal to 1 indicates that an interpolation of type Lanczos between the attenuation map sample values of the current attenuation map given their respective amiEnergyReductionRate should be considered to obtain corresponding attenuation map sample values for another energy reduction rate.

[0178] Setting amiMapApproximationModel equal to 2 indicates that an interpolation of type bicubic between the attenuation map sample values of the current attenuation map given their respective amiEnergyReductionRate should be considered to obtain corresponding attenuation map sample values for another energy reduction rate.

[0179] Setting amiMapApproximationModel equal to 3 indicates that a proprietary user defined process may be used to infer corresponding attenuation map sample values for another energy reduction rate from the attenuation map sample values given their respective amiEnergyReductionRate.Table 3

[0180] The approximation model is applicable to all the attenuation map representation within the current Adaptation Set.

[0181] amiBoxXstart, amiBoxYstart, amiBoxWidth, amiBoxHeight defined respectively the x coordinate, y coordinate, width and height of the bounding box defining the region of the decoded picture to apply the attenuation map. The size of the attenuation map is defined accordingly.

[0182] Table 4 shows the amlAttenuationUseldc attribute to indicate how to use the attenuation map.

[0183] Setting attribute ami Attenuation Useldc equal to 0 specifies that the attenuation map sample should be added to the samples of the associated video component representation before displayed on screen.

[0184] Setting attribute ami Attenuation Useldc equal to 1 specifies that the attenuation map sample should be subtracted to the samples of the associated video component representation before displayed on screen.

[0185] Setting attribute ami Attenuation Useldc equal to 2 specifies that the attenuation map sample should be multiplied to the samples of the associated video component representation before displayed on screen.

[0186] Setting attribute ami Attenuation Useldc equal to 3 specifies that the attenuation map sample should be used according to a proprietary user defined process to the samples of the associated video component representation before displayed on screen.Table 4

[0187] Table 5 shows how the attribute amiAttenuationCompldc may be specified to indicate on which component(s) of the associated video component representation the attenuation map may be applied usingthe process defined by @amiAttenuationUseldc. The attribute amiAttenuationCompldc may also specifies how many components the attenuation map should contain.

[0188] Setting attribute amiAttenuationCompldc equal to 0 specifies that the attenuation map contains only one component and that this component should be applied to the luma component of the associated video component representation.

[0189] Setting attribute amiAttenuationCompldc equal to 1 specifies that the attenuation map contains two components and that the first component should be applied to the luma component of the associated video component representation, and the second component should be applied to both chroma components of the associated video component representation.

[0190] Setting attribute amiAttenuationCompldc equal to 2 specifies that the attenuation map contains only one component and that this component should be applied to the luma component and the chroma components of the associated video component representation.

[0191] Setting attribute amiAttenuationCompldc equal to 3 specifies that the attenuation map contains only one component and that this component should be applied to the RGB components (after YUV to RGB conversion) of the associated video component representation.

[0192] Setting attribute amiAttenuationCompldc equal to 4 specifies that the attenuation map contains three components and that these components should be applied respectively to the luma and chroma components of the associated video component representation.

[0193] Setting attribute amiAttenuationCompldc equal to 5 specifies that the attenuation map contains three components and that these components should be applied respectively to the RGB components (after YUV to RGB conversion) of the associated video component representation.

[0194] Setting attribute amiAttenuationCompldc equal to 6 specifies that the mapping between the components of the associated video component representation and the components of which to apply the attenuation map corresponds to some proprietary user-defined process.Table 5

[0195] Table 6 shows how the attribute amiPreprocessingFlag may be used to indicate the use of preupsampling on the attenuation map samples before applying it on the associated video component representation

[0196] The attribute amiPreprocessingTypeldc, if present, specifies the recommended type of the interpolation (e.g., bicubic) used to pre-upsample the attenuation map sample values.

[0197] Setting amiPreprocessingFlag equal to 0 specifies that an interpolation of type bicubic between the attenuation map sample values should be considered to obtain the attenuation map sample values to apply to the sample values of the associated video component representation.

[0198] Setting amiPreprocessingFlag equal to 1 specifies that an interpolation of type Lanczos between the attenuation map sample values should be considered to obtain the attenuation map sample values to apply to the sample values of the associated video component representation.

[0199] Setting amiPreprocessingFlag equal to 2 specifies that a proprietary user defined process should be used to pre-upsample the attenuation map sample values to apply to the sample values of the associated video component representation .Table 6

[0200] Table 7 shows how the attribute amiPreprocessingScale may be used to indicate which scaling should be applied to the attenuation map to obtain the attenuation map sample values before applying it on the associated video component representation.

[0201] Setting attribute amiPreprocessingScale equal to 0 indicates that a scaling of 1 / 255 should be applied to the attenuation map. This is the preferred embodiment.

[0202] Setting attribute amiPreprocessingScale equal to 1 indicates that a proprietary user defined scaling should be applied to the attenuation map.Table 7

[0203] Table 8 shows how the attribute ami BacklightFlag may be used to indicate the use of the process to compute the scaling factor of the backlight of transmissive pixel displays, derived from the attenuation map sample values.

[0204] Attribute amiBacklightScalingldc indicates the process to compute the scaling factor of the backlight of transmissive pixel displays, derived from the attenuation map sample values.

[0205] Setting attribute amiBacklightFlag equal to 0 indicates that the scaling to apply to the backlight of the display is computed as a ratio between the maximal values of the associated video component representation after and before applying the attenuation map sample values. The associated video component representation sample(s) on which the attenuation map sample values are applied are further rescaled to their maximal value before the application of the attenuation map sample values.

[0206] Setting attribute amiBacklightFlag equal to 1 indicates that the scaling to apply to the backlight of the display is determined according to a proprietary user defined process derived from the attenuation map sample values of the decoded auxiliary picture of index i. This is summarized in table 9 below.Table 8

[0207] Attribute amiMaxValue indicates the maximum value of the attenuation map. Such a maximal value can be optionally used to further adjust the dynamic of the encoded attenuation map in the scaling process.

[0208] Attribute amiEnergyReductionRate indicates the expected energy saving rate when the associated video component representation is displayed after applying the attenuation map sample values of the current attenuation map. An example unit for the ©amiEnergyReductionRate is a percentage or a value in Watt.

[0209] Attribute amiVideoQualityReduction indicates the quality of the displayed video after applying the attenuation map sample values of the current attenuation map. Examples of metrics that can be stored in @amiVideoQuality are PSNR, V-MAF or SSIM values for the modified picture after applying the attenuation map.

[0210] Such quality metrics may be computed by the decoder but, for the sake of reducing the energy consumption, they could also be inferred at the encoder side. In this case, they could correspond to values of expected minimal quality.

[0211] Table 9 shows how the attribute amiVideoQualityMetric may be used to indicate the quality metric to use for computing the video quality reduction when the attenuation map is applied to get the energy reduction rate.Table 9

[0212] The following example XML manifest files provide examples of MPD manifest file with information for energy reduction:

[0213] FIGs. 11A-11 B form a code listing for an example MPD manifest file according to some embodiments. FIGs. 11A and 11 B show example code listings 1100, 1150.

[0214] FIGs. 11A-11 B show an adaptation set with id=ami and mimetype=video / mp4 corresponding to the type of attenuation maps and an adaptation set with id=green_video and codecs=amii corresponding to the type of Attenuation Map Information timed metadata. The representation element of this Adaptation Set carries the information about the attenuation map listed below.

[0215] FIGs., 11A-11 B also show an attenuation map representation of id=”ami0” associated with the Video Component representation id=”v0”, which may be used with emissive and non-emissive displays,allowing a reduction in energy consumption of 20%. An approximation model may be provided to generate other attenuation maps with different reduction rates on the DASH client side.

[0216] FIGs. 11A-11 B represent a first example MPD manifest file including the information allowing to reduce the energy consumption when displaying a video according to an embodiment. This example uses one Adaptation Set of @id=ami and mimetype=video / mp4 corresponding to the type of the attenuation map representations, one attenuation map representation of @id=”ami0” associated with the associated type-'amit” to the Video Component representation @id=”v0”, which can be used for emissive and non- emissive displays (amiDisplayModel=”3”) allowing to reduce the energy consumption of 20% (amiEnergyReductionRate=”20”) with a reduction of the PSNR Quality Video metric value of 5% and with a linear approximation model (amiMapApproximationModel=”0”).

[0217] In the example of FIGs. 11 A-11 B, the attributes ©association Id and @associationType are carried by the attenuation map representation element. In another implementation, the attributes @associ ation Id and @associationType are common attributes to all attenuation map representations and are carried directly by the Adaptation Set Element.

[0218] FIGs. 12A-12B form a code listing for an example MPD manifest file according to some embodiments. FIGs. 12A and 12B show example code listings 1200, 1250.

[0219] FIGs., 12A-12B show an adaptation set with id=ami and mimetype=video / mp4 corresponding to the type of the attenuation maps. FIGs., 12A-12B also show an adaptation set with id=green video and codecs=amii corresponding to the type of the Attenuation Map Information timed metadata. The representation element of this Adaptation Set carries the information about the two attenuation maps listed below.

[0220] FIGs., 12A-12B show two attenuation map representations with id=”ami0” and id=”ami1” associated with the Video Component representation id=”v0”. FIGs., 12A-12B show both attenuation Maps can be used for emissive and non-emissive displays. FIGs., 12A-12B show one attenuation Map allowing to reduce the energy consumption of 20% and another of 40%. FIGs., 12A-12B show an approximation model provided to generate other attenuation maps with different reduction rates on the DASH client side

[0221] FIGs. 12A-12B represent a second example MPD manifest file that includes information enabling reduction of energy consumption when displaying a video according to an embodiment. This second example uses one Adaptation Set of @id =ami and mimetype=video / mp4 corresponding to the type of the attenuation maps, Two attenuation map representations of @id=”ami0” and @id=”ami1” associated to the Video Component representation @id=” vO”, both attenuation Maps being used for emissive and non-emissivedisplays, one attenuation Map allowing to reduce the energy consumption by 20% and another by 40%, and both maps using a Lanczos approximation model (amiMapApproximationModel-T)..

[0222] FIG. 13A is a flowchart illustrating an example DASH server-side application process according to some embodiments. FIG. 13B is a flowchart illustrating an example DASH server-side application process according to some embodiments. These two example processes 1300, 1350 are very similar to each other. In FIG. 13A, energy reduction rates 1322 are an input into the block computing and encoding an attenuation map (AM) 1306. In FIG. 13B, a list of energy reduction rates 1372 is used as an input, and for each energy reduction rate on the list, a looping process 1374 may be performed. For some embodiments, an input video 1324, 1376 is used to encode 1302, 1352 a video frame. The output of the encoding may be processed via a default decoding block 1304, 1354 for each of these respective example processes 1300, 1350.

[0223] The attenuation map metadata 1308, 1358 used to create the new kind of Adaptation Set id=”ami” (At least, the prefix "ami” should be used in the id to identify the type of the Adaptation Set Element) with a new association type(@associationType) for the representations are generated 1310, 1360 while the attenuation map(s) is (are) computed 1306, 1356 by the Map Computing entity at the encoder side.

[0224] FIGs. 13A and 13B depict block diagrams of the generation processes 1300, 1350 of the MPD manifest file with the new Adaptation Set id=”ami” and attenuation map representations, according to an embodiment, performed during the encoding (by the Computing and Encoding entity within the encoder and using the internal decoded video).

[0225] In this embodiment, the new Adaptation Set id=”ami” is inserted 1312, 1362 for a given period. The encoding of the picture by the Encoding entity is performed and results in a set of bitstreams with different characteristics (i.e., bitrate, resolution, ...). The bitstreams are decoded internally and the attenuation map corresponding to the picture is computed and encoded by the attenuation map Computing entity. Data about its use, its expected energy reduction and the corresponding expected quality are collected. These Information are gathered in the attenuation map Information timed metadata and inserted 1314, 1364 in the attenuation map Information sample entry and signaled in the Adaptation Set id=”green video” with codecs-’amii” of the MPD manifest file. The representations of this Adaptation Set are associated (associationType-’cdsc”) to the attenuation map representations. The new Adaptation Set id=”ami” with the attenuation map representations and the Adaptation Set id=”green video” with codecs-’amii” are inserted 1316, 1366 in the MPD which is published 1318, 1368 by the MPD delivery function. Segments of the video component, the green video and attenuation map representations are transmitted 1320, 1370 to the DASH segment delivery function after being requested by the DASH client.

[0226] In another embodiment, multiple Adaptation Sets signaling attenuation maps can be present in the MPD manifest file with id=”amiX”, with X=0..n. This allows, for example, to group the attenuation maps associated to a video representation in a same Adaptation Set Element.

[0227] In another embodiment, instead of using the id=”ami” or id=”amiX” for the new Adaptation Set Element, the attribute @contentType of this element can be set to attenuation map. In that case, the id of the Adaptation Set can be different from "ami” or "amiX”.

[0228] At least one of the two possibilities shall be used to inform the client that the Adaptation Set Element signals attenuation map representations.

[0229] In another embodiment, the attribute @associationType can be an attribute of the Adaptation Set Element instead of being an attribute per representation element when all the attenuation maps of the Adaptation Set are associated to the same video representations.

[0230] In another embodiment, the computation of the attenuation map and the collection of the associated metadata is realized outside of the encoder. The input Video used to compute the attenuation map is the original video and not the output video from the internal decoder of the encoder. The associated metadata are transmitted to the DASH Media Presentation preparation entity to create the new Adaptation Set id=”ami” and the Adaptation Set id=”green video” with codecs-' amii” and insert them in the MPD manifest file, attenuation map corresponding to the picture is computed and encoded by the Attenuation Map Computing entity. The original video is encoded by the encoder and the synchronized bitstream outputs of the two processes are transmitted to the Dash segment delivery function.

[0231] In another embodiment, the Adaptation Set id=”green video” with codecs-’amii” of the MPD manifest has one Attenuation Map Information timed metadata representation carrying information in a sample entry for only one attenuation map.

[0232] In another embodiment, the Adaptation Set id=”green video” with codecs-’amii” of the MPD manifest has one Attenuation Map Information timed metadata representation carrying information in several sample entries, one per attenuation map.

[0233] In another embodiment, the Adaptation Set id=”green video” with codecs-’amii” of the MPD manifest has one Attenuation Map Information timed metadata representation carrying information in a sample entry for several attenuation maps.

[0234] In another embodiment, the amiDisplayModel information is present in the Attenuation Map Information timed metadata in order to indicate to the DASH client that the associated attenuation map representations can only be used for a given Display type. Then the client can perform the appropriate request to the DASH server and not request the attenuation maps that it can't use with the Display to whichit is connected. This embodiment allows to reduce the transmission of data between the DASH server and the client.

[0235] In another embodiment, several attenuation maps with different reduction rates can be computed and the new Adaptation Set id=”ami” element contains several attenuation map representations for the same Video component representation.

[0236] In another embodiment, some attenuation maps are computed with different reduction rates and the amiMapApproximationModel is added in the Attenuation Map Information timed metadata in order to allow the DASH Client to generate new attenuation map representation from the ones it has received from the DASH Server. This embodiment allows to reduce the use of the network bandwidth.

[0237] For example, two attenuation maps with energy reduction rates R and R2are computed. This will allow at the decoder side to interpolate for any other reduction rate RCisuch as R < RCi< R2.

[0238] In another embodiment, amiBoxXstart, amiBoxYstart, amiBoxWidth, amiBoxHeight are added in in the Attenuation Map Information timed metadata to indicate the part of the picture on which the attenuation map should be applied. Instead of transmitting an attenuation map with the same size of the Video representation, only the area of the picture which allows a significative display energy consumption reduction is given. This can also be seen as a representation alternative selection for the DASH client between a partial or a full attenuation map. In that case, the DASH server can create the two kind of Attenuation Map Information timed metadata, one with amiBoxXstart, amiBoxYstart, amiBoxWidth, amiBoxHeight and one without.

[0239] As the attenuation map representation(s) may be at different levels of the video media component, the following granularities may be used:• Granularity 1 - Picture• Granularity 2 - Parts of picture: slices, tiles, sub-pictures,• Granularity 3 - GOP or scenes

[0240] In conjunction with the adaptation set id=”ami”, the adaptation set id=”green video” with codecs-' amii” and the attached attenuation map representation of AssociationType-'amit” elements may be updated to reflect changes in the presentation over time.

[0241] In an embodiment, the update can be performed by, in case of MPD@type = static, the definition of different ©period in the MPD with different kinds of Adaptation Set id=”ami”, Adaptation Set id=”green video” with codecs-' amii” and attached attenuation map representations of AssociationType-'amit” or in case of MPD@type=”dynamic”, an update of one unique new kind of Adaptation Set id=”ami”.

[0242] FIG. 14 is a flowchart illustrating an example DASH client-side process according to some embodiments.

[0243] FIG. 14 illustrates an example process for using an attenuation map representations according to an embodiment. Such a process 1400 may be implemented by an energy-aware DASH client such as a display device. This process is for example implemented by a processor of such device. This process is for example initiated by the user that request streaming of a multimedia content.

[0244] Prior to this process, a target reduction rate has been selected. This selection may be done using different techniques. In an embodiment, the target reduction rate may be selected though a manual user operation by setting a numeric value for the target. For example, a slider may be displayed on the screen and controlled by the user to adjust a numerical value representing the target reduction rate. A numeric value may also be entered directly using digit keys on a keyboard.

[0245] In an embodiment, a list of potential target reduction rates may be displayed on the screen to allow the user to select one of the rates to become the target reduction rate. The list of rates is for example restricted to the list of @amiEnergyReductionRate parameters in the MDP manifest file of the selected multimedia content.

[0246] In an embodiment, the target reduction rate is selected though a configuration setting of the display device and obtained from the display device without requiring user intervention before displaying a multimedia content. Such configuration setting should preferably be under control of the user, for example through a dedicated user interface.

[0247] In an embodiment, the target reduction rate is selected according to the category of multimedia content and based on a user configuration. The category may correspond to a classification, for example allowing to differentiate movies, news, advertisements, talk shows, music shows, etc. A user would be able to select using a dedicated user interface the target reduction rate for each category.

[0248] The DASH client requests 1402 an MPD manifest file. After obtaining the MPD Manifest file, this file is processed 1404 to extract the necessary data to select the video component representation, the attenuation map representation(s), the parameters to configure the Decoding module, the attenuation maps post-processing module and the rendering modules. A request may be sent 1406 and a response received for green video timed metadata. The DASH client checks 1408 if the display model corresponding to the screen that will display the multimedia content is in the list of display models of the MPD. This is done by comparing the display model (or type) information of the screen to the @amiDisplayModel parameter in the MPD.

[0249] In an example, the @amiDisplayModel parameter in the MPD is set to 1 to indicate that the attenuation map representation should be used on an emissive display. If there is no match, for example for a first DASH client with a non-emissive display, the first DASH client requests 1410 and receives representation segments for the video, decodes 1412 the pictures of the video and provides the picture to the screen for being displayed. The expected energy reduction will not be available for this first DASH client.

[0250] When there is a match, for example for a second DASH client with a non- emissive display and @amiDisplayModel set to 1 , then the second DASH client will be able to benefit from an energy reduction allowed by the embodiments and will display an energy-reduced version of the multimedia content therefore lowering its energy consumption. In this case, the second DASH client requests 1414 the attenuation map representation segment that corresponds to the selected target reduction rate, and receives it. The attenuation map representation is then decoded 1416 and optionally preprocessed 1418 and applied 1420 to the decoded picture, according to the parameters of the "ami” Adaptation Set. For example, the attenuation map representation will be subsampled to reduce the quantity of data to be encoded. In this case, an upscaling is performed on the attenuation so that its resolution corresponds to the resolution of the image to be displayed. Independently (i.e., possibly at the same time or sequentially), the second DASH client requests 1422 the video component representation segment, and receives it. The picture of the video component representation segment is then decoded 1424. When both the attenuation map representation and corresponding picture have been decoded, the second DASH client sends 1426 the reduced picture to be displayed. Compared to the display of the corresponding non-attenuated picture, the device will lower its energy consumption since the device displays an energy-reduced version of the picture.

[0251] Additionally, in the example where none of the available Attenuation Map representations proposes the target energy reduction rate selected by the user, the device will select one of the available attenuation map representations and perform an interpolation of the attenuation map representation values to obtain the selected target energy reduction rate. The selection is done by choosing for example the attenuation with closest reduction rate with regards to the selected target reduction rate. In the case where the selected target energy reduction rate is between two available target energy reduction rates, then request, receive, and decode the attenuation map representations corresponding to these two reduction rates to be able to perform an interpolation between their values. For example, when the user selected a 30% reduction rate and the available attenuation map representations have reduction rates of 20% and 40%, then these two maps will be interpolated by simply taking the average values.

[0252] In an embodiment, the DASH client is not in an energy consumption reduction mode and therefore does not consider the "ami” Adaptation Set and the attached attenuation map representations. Only the video component representation segments are requested.

[0253] In an embodiment, the DASH client only requests the attenuation map representations with @amiAttenuationUseldc attribute it can deal with, i.e., it has not the capability to execute the process to apply the attenuation map representation to the decoded video. In an embodiment, the DASH client only requests the attenuation map representations with @amiPreprocessingTypeldc attribute it can deal with, i.e., it has not the capability to execute the preprocessing method before applying the attenuation map representation to the decoded video. In an embodiment, the DASH client only requests the attenuation maps with an acceptable value (i.e., content provider expectation) of the @amiVideoQuality attribute. In an embodiment, the DASH client prioritizes attenuation map representations with attributes @amiBoxXstart, @amiBoxYstart, @amiBoxWidth, @amiBoxHeight instead of selecting the attenuation Map representation of the same size of the Video representation. The selection of these representations allows to reduce the use of the network bandwidth to transmit the attenuation map representation by using partial attenuation map representations and thus to reduce the display energy consumption.

[0254] Several embodiments may be envisioned for the use of the attenuation map and its accompanying metadata. FIG. 14 depicts a block diagram of the MPD usage by an end device, containing a display compatible with amiDisplayModel, according to an embodiment to apply a green strategy by using the attenuation maps.

[0255] In another embodiment, the end user device can decide to not consider the new kind of Adaptation Set id=”ami” and the attached attenuation map representations and doesn't request any attenuation map because the Display Model is not aligned with the amiDisplayModel field retrieved in the Attenuation Map Information timed metadata.

[0256] In another embodiment, the end user device can decide to not consider the new kind of Adaptation Set id=”ami” and the attached attenuation map representations and doesn't request any attenuation map because it is not in an energy consumption reduction mode. Only the video component representation segments are requested.

[0257] In another embodiment, the end user device can decide to request some attenuation maps with different reduction rates when it is able to use the amiMapApproximationModel of the Attenuation Map Information timed metadata to generate new attenuation map representation with different reduction rates. This embodiment allows to reduce the use of the network bandwidth.

[0258] For example, two attenuation maps with energy reduction rates R and R2are computed. This will allow at the decoder side to interpolate for any other reduction rate R such as R < R < R2.

[0259] In another embodiment, the end user device can decide to only request the attenuation maps with amiAttenuationUseldc of the Attenuation Map Information timed metadata attribute it can deal with, i.e., it has not the capability to execute the process to apply the attenuation map to the decoded video.

[0260] In another embodiment, the end user device can decide to only request the attenuation maps with an amiPreprocessingTypeldc of the Attenuation Map Information timed metadata it can deal with, i.e., it has not the capability to execute the preprocessing method before applying the attenuation map to the decoded video.

[0261] In another embodiment, the end user device can decide to only request the attenuation maps with an acceptable value (i.e., content provider expectation) of the amiVideoQualityReduction of the Attenuation Map Information timed metadata.

[0262] In another embodiment, the end user device can decide to select the attenuation map representation with the amiBoxXstart, amiBoxYstart, ami BoxWidth, amiBoxHeight present in the Attenuation Map Information timed metadata instead of selecting the attenuation map representation of the same size of the Video representation. This allows to reduce the use of the network bandwidth to transmit the attenuation map and, with a least significative value, to reduce the display energy consumption.

[0263] FIG. 15 is a schematic illustration showing an example DASH client-side process according to some embodiments. For some embodiments of such a process 1500, an MPD file 1508 is received as well as data 1510 for multiple segments by a DASH access engine 1504. A selection is made. The DASH access engine1504 may send MPD selection metadata 1512, which may include a new adaptation set, to a selection logic process 1502. The selection process 1502 may send 1514 an indication back to the DASH access engine indicating the selected representations for AMI time metadata, video, and attenuation maps. The DASH access engine 1504 may send 1516 MPEG format video media, attenuation maps, and timing information to a media engine 1506. The media engine 1506 may use this received data to generate and / or display reduced energy video media.

[0264] The application impacts the DASH server and player. The presence of attenuation maps in the DASH Media Presentation Description (MPD) manifest file may be checked at the DASH adaptative streaming player side when: (1) the request of the MPD is performed and the new Adaptation Sets to access the attenuation maps segments are available, (2) the request of the MPD is performed and the Adaptation Sets id=”green video” with ©codecs-’ amii” are available, (3) an HTTP request to receive one or several Attenuation Map Information timed metadata is performed and the segments transporting the Attenuation Map Information timed metadata are transmitted from the server to the player, (4) an HTTP request to receive one or several attenuation maps is performed and the segments transporting the attenuation map are transmitted from the server to the player.

[0265] A check may be done to determine whether, for different display types, the consumed energy is reduced or not in correlation with the selected adaptation set in the MPD. In the case where there are different adaptation sets in the MPD for different energy reduction rates, a check may be done to determine if the energy consumed by the modified video is in accordance with one of the energy reduction rates provided in one of the adaptation sets of the MPD of the current period. .

[0266] FIG. 16 is a flowchart illustrating an example process for generating an attenuation image for display according to some embodiments. For some embodiments, an example process 1600 may include obtaining 1602 a manifest file corresponding to visual content. For some embodiments of the example process 1600, the manifest file includes: information related to a video representation and information related to a set of attenuation map representations for the visual content. For some embodiments, the example process 1600 may further include obtaining 1604 segments of the video representation. For some embodiments, the example process 1600 may further include obtaining 1606 segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate. For some embodiments, the example process 1600 may further include decoding 1608 a picture from theobtained segments of the video representation. For some embodiments, the example process 1600 may further include decoding 1610 the attenuation map representation from the obtained segments of the attenuation map representation. For some embodiments, the example process 1600 may further include applying 1612 the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0267] FIG. 17 is a flowchart illustrating an example process for generating an attenuation image for display according to some embodiments. For some embodiments, an example process 1700 may include obtaining 1702 a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, information related to a set of attenuation map representations for the visual content, and an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AMII). For some embodiments, the example process 1700 may further include obtaining 1704 segments of the video representation. For some embodiments, the example process 1700 may further include obtaining 1706 segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate. For some embodiments, the example process 1700 may further include decoding 1708 a picture from theobtained segments of the video representation. For some embodiments, the example process may further include decoding 1710 the attenuation map representation from the obtained segments of the attenuation map representation. For some embodiments, the example process 1700 may further includeapplying 1712 the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0268] FIGs. 18A-18B form a code listing for an example attenuation map information indication (AM 11) sample process according to some embodiments. Each representation of the green video adaptation sets with ©codecs-’ amii” carries the information of only one attenuation map. FIGs. 18A-18B are corollaries to FIGs. 7A-7B with FIGs. 18A-18B showing the use of the amiCancelFlag attribute for some embodiments.

[0269] FIGs. 19A-19B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. Each representation of the green video adaptation sets with ©codecs-' amii” carries the information of several attenuation maps in separate sample entries. The amID data field is added to identify the attenuation map and to retrieve the relative information to use the attenuation map. FIGs. 19A-19B are corollaries to FIGs. 8A-8B with FIGs. 19A-19B showing the use of the amiCancelFlag attribute for some embodiments.

[0270] FIGs. 20A-20B form a code listing for an example attenuation map information indication (AMII) sample process according to some embodiments. Each representation of the green video adaptation sets with @codecs=”amii” carries the information of several attenuation maps in a unique sample entry. The amID data field is added to identify the attenuation map and to retrieve the relative information to use the attenuation map. FIGs. 20A-20B are corollaries to FIGs. 9A-9B with FIGs. 20A-20B showing the use of the amiCancelFlag attribute for some embodiments.

[0271] While the methods and systems in accordance with some embodiments are generally discussed in context of extended reality (XR), some embodiments may be applied to any XR contexts such as, e.g., virtual reality (VR) / mixed reality (MR) / augmented reality (AR) contexts. Also, although the term "head mounted display (HMD)” is used herein in accordance with some embodiments, some embodiments may be applied to a wearable device (which may or may not be attached to the head) capable of, e.g., XR, VR, AR, and / or MR for some embodiments.

[0272] A first example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, and information related to a set of attenuation map representations for the visual content; obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0273] For some embodiments of the first example method, the manifest file includes an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI).

[0274] For some embodiments of the first example method, the manifest file includes an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AMU).

[0275] For some embodiments of the first example method, the identifier field is accessible with an external class.

[0276] Some embodiments of the first example method may further include: responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to the attenuation map representation selected.

[0277] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to quality of the picture, and selecting the attenuation map from the list is based on the information corresponding to quality of the picture.

[0278] Some embodiments of the first example method may further include rendering the attenuated picture.

[0279] For some embodiments of the first example method, the information related to the attenuation map representations further includes information representative of a type of interpolation.

[0280] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to scaling of pixels of the picture.

[0281] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to backlighting of the picture.

[0282] For some embodiments of the first example method, the information related to the attenuation map representations further includes information corresponding to quality of the picture.

[0283] For some embodiments of the first example method, the manifest file and the segments are based on MPEG-DASH.

[0284] For some embodiments of the first example method, obtaining segments of the attenuation map representation is performed using an adaptation set with an identifier field corresponding to a Green Video type.

[0285] A first example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0286] A second example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, and information related to a set of attenuation map representations for the visual content; responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to an attenuation map representation selected from the set of attenuation map representations, obtaining segments of the video representation; obtaining segments of the selected attenuation map representation; decoding apicture from the obtained segments of the video representation; decoding the selected attenuation map representation from the obtained segments of the selected attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture.

[0287] A second example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0288] A third example method in accordance with some embodiments may include: obtaining a manifest file corresponding to visual content, wherein the manifest file includes: information related to a video representation, information related to a set of attenuation map representations for the visual content, and an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AM II); obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

[0289] A third example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0290] A fourth example method in accordance with some embodiments may include: creating a manifest file corresponding to visual content, wherein the manifest file includes: information related to a videorepresentation, and information related to a set of attenuation map representations for the visual content; and sending to a client the manifest file corresponding to visual content.

[0291] Some embodiments of the fourth example method may further include: receiving a request for segments of the video representation; receiving a request for segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; sending to the client the segments of the video representation; and sending to the client the segments of the attenuation map representation selected from the set of attenuation map representations based on the selected energy reduction rate.

[0292] Some embodiments of the fourth example method may further include: encoding a picture as the segments of the video representation; and encoding the selected attenuation map representation as the segments of the selected attenuation map representation.

[0293] A fourth example apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform any one of the methods listed above.

[0294] An example server apparatus in accordance with some embodiments may include: one or more processors, the one or more processors configured to generate a manifest file, the manifest file comprising information configured to and available to be used by a client to reduce energy consumption of video representations at a client display in a pixel-wise manner, wherein the one or more processors are further configured to generate the manifest file in part by deriving the information from attenuation map information obtained by the server.

[0295] For some embodiments of the example server apparatus, the server is a DASH server.

[0296] For some embodiments of the example server apparatus, the manifest file is a DASH MPD file.

[0297] An example client apparatus in accordance with some embodiments may include one or more processors and in communication with a display, the one or more processors configured to obtain a manifest file, the manifest file comprising information configured to and available to be used by the client to reduce energy consumption of video representations at a display in a pixel-wise manner, wherein the information is derived from attenuation map information, wherein the one or more processors are further configured to update the display in accordance with the manifest file.

[0298] For some embodiments of the example client apparatus, the client includes the display.

[0299] For some embodiments of the example client apparatus, the client is a DASH client.

[0300] For some embodiments of the example client apparatus, the manifest file is a DASH MPD file.

[0301] For some embodiments of the example client apparatus, the client selects the information derived from the attenuation map information from the server.

[0302] For some embodiments of the example client apparatus, the server is a DASH server.

[0303] A fifth example apparatus in accordance with some embodiments may include at least one processor configured to perform any one of the methods listed above.

[0304] A sixth example apparatus in accordance with some embodiments may include a computer- readable medium storing instructions for causing one or more processors to perform any one of the methods listed above.

[0305] A seventh example apparatus in accordance with some embodiments may include at least one processor and at least one non-transitory computer-readable medium storing instructions for causing the at least one processor to perform any one of the methods listed above.

[0306] A computer-readable medium in accordance with some embodiments may include a computer- readable medium storing a bitstream generated according to any one of the methods listed above.

[0307] A signal in accordance with some embodiments may include a bitstream generated according to any one of the methods listed above.

[0308] This disclosure describes a variety of aspects, including tools, features, embodiments, models, approaches, etc. Many of these aspects are described with specificity and, at least to show the individual characteristics, are often described in a manner that may sound limiting. However, this is for purposes of clarity in description, and does not limit the disclosure or scope of those aspects. Indeed, all of the different aspects can be combined and interchanged to provide further aspects. Moreover, the aspects can be combined and interchanged with aspects described in earlier filings as well.

[0309] The aspects described and contemplated in this disclosure can be implemented in many different forms. While some embodiments are illustrated specifically, other embodiments are contemplated, and the discussion of particular embodiments does not limit the breadth of the implementations. At least one of the aspects generally relates to video encoding and decoding, and at least one other aspect generally relates to transmitting a bitstream generated or encoded. These and other aspects can be implemented as a method, an apparatus, a computer readable storage medium having stored thereon instructions for encoding or decoding video data according to any of the methods described, and / or a computer readable storage medium having stored thereon a bitstream generated according to any of the methods described.

[0310] In the present disclosure, the terms "reconstructed” and "decoded” may be used interchangeably, the terms "pixel” and "sample” may be used interchangeably, the terms "image,” "picture” and "frame” maybe used interchangeably. Usually, but not necessarily, the term "reconstructed” is used at the encoder side while "decoded” is used at the decoder side.

[0311] The terms HDR (high dynamic range) and SDR (standard dynamic range) often convey specific values of dynamic range to those of ordinary skill in the art. However, additional embodiments are also intended in which a reference to HDR is understood to mean "higher dynamic range” and a reference to SDR is understood to mean "lower dynamic range.” Such additional embodiments are not constrained by any specific values of dynamic range that might often be associated with the terms "high dynamic range” and "standard dynamic range.”

[0312] Various methods are described herein, and each of the methods comprises one or more steps or actions for achieving the described method. Unless a specific order of steps or actions is required for proper operation of the method, the order and / or use of specific steps and / or actions may be modified or combined. Additionally, terms such as "first”, "second”, etc. may be used in various embodiments to modify an element, component, step, operation, etc., such as, for example, a "first decoding” and a "second decoding”. Use of such terms does not imply an ordering to the modified operations unless specifically required. So, in this example, the first decoding need not be performed before the second decoding, and may occur, for example, before, during, or in an overlapping time period with the second decoding.

[0313] Various numeric values may be used in the present disclosure, for example. The specific values are for example purposes and the aspects described are not limited to these specific values.

[0314] Embodiments described herein may be carried out by computer software implemented by a processor or other hardware, or by a combination of hardware and software. As a non-limiting example, the embodiments can be implemented by one or more integrated circuits. The processor can be of any type appropriate to the technical environment and can encompass one or more of microprocessors, general purpose computers, special purpose computers, and processors based on a multi-core architecture, as nonlimiting examples.

[0315] Various implementations involve decoding. "Decoding”, as used in this disclosure, can encompass all or part of the processes performed, for example, on a received encoded sequence in order to produce a final output suitable for display. In various embodiments, such processes include one or more of the processes typically performed by a decoder, for example, entropy decoding, inverse quantization, inverse transformation, and differential decoding. In various embodiments, such processes also, or alternatively, include processes performed by a decoder of various implementations described in this disclosure, for example, extracting a picture from a tiled (packed) picture, determining an upsampling filter to use and then upsampling a picture, and flipping a picture back to its intended orientation.

[0316] As further examples, in one embodiment "decoding” refers only to entropy decoding, in another embodiment "decoding” refers only to differential decoding, and in another embodiment "decoding” refers to a combination of entropy decoding and differential decoding. Whether the phrase "decoding process” is intended to refer specifically to a subset of operations or generally to the broader decoding process will be clear based on the context of the specific descriptions.

[0317] Various implementations involve encoding. In an analogous way to the above discussion about "decoding”, "encoding” as used in this disclosure can encompass all or part of the processes performed, for example, on an input video sequence in order to produce an encoded bitstream. In various embodiments, such processes include one or more of the processes typically performed by an encoder, for example, partitioning, differential encoding, transformation, quantization, and entropy encoding. In various embodiments, such processes also, or alternatively, include processes performed by an encoder of various implementations described in this disclosure.

[0318] As further examples, in one embodiment "encoding” refers only to entropy encoding, in another embodiment "encoding” refers only to differential encoding, and in another embodiment "encoding” refers to a combination of differential encoding and entropy encoding. Whether the phrase "encoding process” is intended to refer specifically to a subset of operations or generally to the broader encoding process will be clear based on the context of the specific descriptions.

[0319] Various embodiments refer to rate distortion optimization. In particular, during the encoding process, the balance or trade-off between the rate and distortion is usually considered, often given the constraints of computational complexity. The rate distortion optimization is usually formulated as minimizing a rate distortion function, which is a weighted sum of the rate and of the distortion. There are different approaches to solve the rate distortion optimization problem. For example, the approaches may be based on an extensive testing of all encoding options, including all considered modes or coding parameters values, with a complete evaluation of their coding cost and related distortion of the reconstructed signal after coding and decoding. Faster approaches may also be used, to save encoding complexity, in particular with computation of an approximated distortion based on the prediction or the prediction residual signal, not the reconstructed one. A mix of these two approaches can also be used, such as by using an approximated distortion for only some of the possible encoding options, and a complete distortion for other encoding options. Other approaches only evaluate a subset of the possible encoding options. More generally, many approaches employ any of a variety of techniques to perform the optimization, but the optimization is not necessarily a complete evaluation of both the coding cost and related distortion.

[0320] When a figure is presented as a flow diagram, it should be understood that it also provides a block diagram of a corresponding apparatus. Similarly, when a figure is presented as a block diagram, it should be understood that it also provides a flow diagram of a corresponding method / process.

[0321] The implementations and aspects described herein can be implemented in, for example, a method or a process, an apparatus, a software program, a data stream, or a signal. Even if only discussed in the context of a single form of implementation (for example, discussed only as a method), the implementation of features discussed can also be implemented in other forms (for example, an apparatus or program). An apparatus can be implemented in, for example, appropriate hardware, software, and firmware. The methods can be implemented in, for example, a processor, which refers to processing devices in general, including, for example, a computer, a microprocessor, an integrated circuit, or a programmable logic device. Processors also include communication devices, such as, for example, computers, cell phones, portable / personal digital assistants ("PDAs”), and other devices that facilitate communication of information between end-users.

[0322] Reference to "one embodiment” or "an embodiment” or "one implementation” or "an implementation”, as well as other variations thereof, means that a particular feature, structure, characteristic, and so forth described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase "in one embodiment” or "in an embodiment” or "in one implementation” or "in an implementation”, as well any other variations, appearing in various places throughout this disclosure are not necessarily all referring to the same embodiment.

[0323] Additionally, this disclosure may refer to "determining” various pieces of information. Determining the information can include one or more of, for example, estimating the information, calculating the information, predicting the information, or retrieving the information from memory.

[0324] Further, this disclosure may refer to "accessing” various pieces of information. Accessing the information can include one or more of, for example, receiving the information, retrieving the information (for example, from memory), storing the information, moving the information, copying the information, calculating the information, determining the information, predicting the information, or estimating the information.

[0325] Additionally, this disclosure may refer to "receiving” various pieces of information. Receiving is, as with "accessing”, intended to be a broad term. Receiving the information can include one or more of, for example, accessing the information, or retrieving the information (for example, from memory). Further, "receiving” is typically involved, in one way or another, during operations such as, for example, storing the information, processing the information, transmitting the information, moving the information, copying the information, erasing the information, calculating the information, determining the information, predicting the information, or estimating the information.

[0326] It is to be appreciated that the use of any of the following “ / ”, "and / or”, and "at least one of, for example, in the cases of “A / B”, "A and / or B” and "at least one of A and B”, is intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of both options (A and B). As a further example, in the cases of "A, B, and / or C” and "at least one of A, B, and C”, such phrasing is intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of the third listed option (C) only, or the selection of the first and the second listed options (A and B) only, or the selection of the first and third listed options (A and C) only, or the selection of the second and third listed options (B and C) only, or the selection of all three options (A and B and C). This may be extended for as many items as are listed.

[0327] Also, as used herein, the word "signal” refers to, among other things, indicating something to a corresponding decoder. For example, in certain embodiments the encoder signals a particular one of a plurality of parameters for region-based filter parameter selection for de-artifact filtering. In this way, in an embodiment the same parameter is used at both the encoder side and the decoder side. Thus, for example, an encoder can transmit (explicit signaling) a particular parameter to the decoder so that the decoder can use the same particular parameter. Conversely, if the decoder already has the particular parameter as well as others, then signaling can be used without transmitting (implicit signaling) to simply allow the decoder to know and select the particular parameter. By avoiding transmission of any actual functions, a bit savings is realized in various embodiments. It is to be appreciated that signaling can be accomplished in a variety of ways. For example, one or more syntax elements, flags, and so forth are used to signal information to a corresponding decoder in various embodiments. While the preceding relates to the verb form of the word "signal”, the word "signal” can also be used herein as a noun.

[0328] Implementations can produce a variety of signals formatted to carry information that can be, for example, stored or transmitted. The information can include, for example, instructions for performing a method, or data produced by one of the described implementations. For example, a signal can be formatted to carry the bitstream of a described embodiment. Such a signal can be formatted, for example, as an electromagnetic wave (for example, using a radio frequency portion of spectrum) or as a baseband signal. The formatting can include, for example, encoding a data stream and modulating a carrier with the encoded data stream. The information that the signal carries can be, for example, analog or digital information. The signal can be transmitted over a variety of different wired or wireless links, as is known. The signal can be stored on a processor-readable medium.

[0329] We describe a number of embodiments. Features of these embodiments can be provided alone or in any combination, across various claim categories and types. Further, embodiments can include one ormore of the following features, devices, or aspects, alone or in any combination, across various claim categories and types:• A bitstream or signal that includes one or more of the described syntax elements, or variations thereof.• A bitstream or signal that includes syntax conveying information generated according to any of the embodiments described.• Creating and / or transmitting and / or receiving and / or decoding a bitstream or signal that includes one or more of the described syntax elements, or variations thereof.• Creating and / or transmitting and / or receiving and / or decoding according to any of the embodiments described.• A method, process, apparatus, medium storing instructions, medium storing data, or signal according to any of the embodiments described.

[0330] Note that various hardware elements of one or more of the described embodiments are referred to as "modules” that carry out (i.e., perform, execute, and the like) various functions that are described herein in connection with the respective modules. As used herein, a module includes hardware (e.g., one or more processors, one or more microprocessors, one or more microcontrollers, one or more microchips, one or more application-specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), one or more memory devices) deemed suitable by those of skill in the relevant art for a given implementation. Each described module may also include instructions executable for carrying out the one or more functions described as being carried out by the respective module, and it is noted that those instructions could take the form of or include hardware (i.e., hardwired) instructions, firmware instructions, software instructions, and / or the like, and may be stored in any suitable non-transitory computer-readable medium or media, such as commonly referred to as RAM, ROM, etc.

[0331] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMS1. A method comprising: obtaining a manifest file corresponding to visual content, wherein the manifest file comprises: information related to a video representation, and information related to a set of attenuation map representations for the visual content; obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

2. The method of claim 1 , wherein the manifest file comprises an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI).

3. The method of claim 1 , wherein the manifest file comprises an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AMU).

4. The method of any one of claims 1-3, wherein the identifier field is accessible with an external class.

5. The method of any one of claims 1-4, further comprising: responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to the attenuation map representation selected.

6. The method of claim 5, wherein the information related to the attenuation map representations further comprises information corresponding to quality of the picture, and wherein selecting the attenuation map from the list is based on the information corresponding to quality of the picture.

7. The method of any one of claims 1-6, further comprising rendering the attenuated picture.

8. The method of any one of claims 1-7, wherein the information related to the attenuation map representations further comprises information representative of a type of interpolation.

9. The method of any one of claims 1-8, wherein the information related to the attenuation map representations further comprises information corresponding to scaling of pixels of the picture.

10. The method of any one of claims 1-9, wherein the information related to the attenuation map representations further comprises information corresponding to backlighting of the picture.

11. The method of any one of claims 1-10, wherein the information related to the attenuation map representations further comprises information corresponding to quality of the picture.

12. The method of anyofclaims 1-11 , wherein the manifest file and the segments are based on MPEG-DASH.

13. The method of any of claims 1-12, wherein obtaining segments of the attenuation map representation is performed using an adaptation set with an identifier field corresponding to a Green Video type.

14. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform the method of any one of claims 1 through 13.

15. A method comprising: obtaining a manifest file corresponding to visual content, wherein the manifest file comprises: information related to a video representation, and information related to a set of attenuation map representations for the visual content; responsive to finding, in the manifest file, an adaptation set with an identifier field corresponding to Attenuation Map Information (AMI), retrieving a list of one or more available pixel-wise attenuation maps; and selecting an attenuation map from the list, wherein the selected attenuation map corresponds to an attenuation map representation selected from the set of attenuation map representations; obtaining segments of the video representation; obtaining segments of the selected attenuation map representation;decoding a picture from the obtained segments of the video representation; decoding the selected attenuation map representation from the obtained segments of the selected attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture.

16. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform the method of claim 15.

17. A method comprising: obtaining a manifest file corresponding to visual content, wherein the manifest file comprises: information related to a video representation, information related to a set of attenuation map representations for the visual content, and an adaptation set with an identifier field corresponding to Green Video and a codec attribute with a value corresponding to Attenuation Map Information Indication (AM 11); obtaining segments of the video representation; obtaining segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; decoding a picture from the obtained segments of the video representation; decoding the attenuation map representation from the obtained segments of the attenuation map representation; and applying the decoded attenuation map representation to the decoded picture to generate an attenuated picture for display.

18. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform the method of claim 17.

19. A method comprising: creating a manifest file corresponding to visual content, wherein the manifest file comprises: information related to a video representation, andinformation related to a set of attenuation map representations for the visual content; and sending to a client the manifest file corresponding to visual content.

20. The method according to claim 19, further comprising: receiving a request for segments of the video representation; receiving a request for segments of an attenuation map representation selected from the set of attenuation map representations based on a selected energy reduction rate; sending to the client the segments of the video representation; and sending to the client the segments of the attenuation map representation selected from the set of attenuation map representations based on the selected energy reduction rate;21 . The method according to claim 20, further comprising: encoding a picture as the segments of the video representation; and encoding the selected attenuation map representation as the segments of the selected attenuation map representation.

22. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to perform the method of any one of claims 19 through 21 .

23. A server apparatus comprising one or more processors, the one or more processors configured to generate a manifest file, the manifest file comprising information configured to and available to be used by a client to reduce energy consumption of video representations at a client display in a pixel-wise manner, wherein the one or more processors are further configured to generate the manifest file in part by deriving the information from attenuation map information obtained by the server.

24. The server apparatus of claim 23, wherein the server is a DASH server.

25. The server apparatus of claim 23, wherein the manifest file is a DASH MPD file.

26. A client apparatus comprising one or more processors and in communication with a display, the one or more processors configured to obtain a manifest file, the manifest file comprising information configured to and available to be used by the client to reduce energy consumption of video representations at a display in a pixel-wise manner, wherein the information is derived from attenuation map information, wherein the one or more processors are further configured to update the display in accordance with the manifest file.

27. The client apparatus of claim 26, wherein the client comprises the display.

28. The client apparatus of claim 26, wherein the client is a DASH client.

29. The client apparatus of claim 26, wherein the manifest file is a DASH MPD file.

30. The client apparatus of claim 26, wherein the client selects the information derived from the attenuation map information from the server.31 . The client apparatus of claim 30, wherein the server is a DASH server.

32. An apparatus comprising at least one processor configured to perform the method of any one of claims1-13, 15, 17, and 19-21.

33. An apparatus comprising a computer-readable medium storing instructions for causing one or more processors to perform the method of any one of claims 1-13, 15, 17, and 19-21.

34. An apparatus comprising at least one processor and at least one non-transitory computer-readable medium storing instructions for causing the at least one processor to perform the method of any one of claims 1-13, 15, 17, and 19-21.

35. A computer-readable medium storing a bitstream generated according to any one of claims 1-13, 15, 17, and 19-21.

36. A signal including a bitstream generated according to any one of claims 1-13, 15, 17, and 19-21.

Images