Interactive signaling for energy saving

Abstract

Disclosed herein are systems, methods, and instrumentalities associated with energy saving for video coding. A video decoding device may be configured to send, to a video encoding device, a first request that may indicate one or more operational changes associated with energy saving. The video decoding device may receive, from the video encoding device, a first response that may indicate whether or to what extent the video encoding device may accept the first request, and the video decoding device may perform an operation based on the first response.

Description

INTERACTIVE SIGNALING FOR ENERGY SAVINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of European Patent Application No. 23306716.4, filed October 5, 2023, and European Patent Application No.23306761.0, filed October 10, 2023, the disclosures of which are incorporated herein by reference in their entirety.BACKGROUND

[0002] Video coding systems may be used to compress digital video signals, e.g., to reduce the storage and / or transmission bandwidth needed for such signals. Video coding systems may include, for example, block-based, wavelet-based, and / or object-based systems.SUMMARY

[0003] Disclosed herein are systems, methods, and instrumentalities associated with energy saving for video coding. According to embodiments of the present disclosure, a video decoding device may be configured to send, to a video encoding device, a first request that may indicate one or more operational changes associated with energy saving. The video decoding device may receive, from the video encoding device, a first response that may indicate whether or to what extent the video encoding device may accept the first request, and the video decoding device may perform an operation based on the first response.

[0004] In examples, the video decoding device being configured to perform the operation based on the first response may comprise the video decoding device being configured to decode a video block based on the first response or send a second request associated with energy saving to the video encoding device. The second request may, for example, indicate a modification of the first request.

[0005] In examples, the first response may indicate that only a subset of the operational changes indicated by the first request has been accepted. In examples, the first request may indicate multiple types of operational changes, and the first response may indicate which one or more types of operational indicated by the first request are accepted.

[0006] In examples, the first response may indicate that a parameter associated with video encoding or video decoding may have been adjusted, that a tool associated with video encoding or video decoding may have been disabled, that an image resolution associated with a video may have been adjusted, or that a bitrate associated with the video may have been adjusted.

[0007] In examples, the video decoding device may be further configured to send a second request to the video encoder to cancel the first request at least partially, and the video decoding device may receive asecond response that indicates that the first request has been cancelled at least partially. In examples, the second response may indicate that all previous requests associated with energy saving sent by the video decoding device have been cancelled.

[0008] According to embodiments of the disclosure, a video encoding device may be configured to receive, from a video decoding device, a first request that may indicate one or more operational changes associated with energy saving. The video encoding device may determine whether or to what extent to implement the one or more operational changes indicated by the first request. The video encoding device may send a first response to the video decoding device, wherein the first response may indicate whether or to what extent the video encoding device may have decided to implement the one or more operational changes.

[0009] In examples, the video encoding device being configured to determine whether or to what extent to implement the one or more operational changes indicated by the first request may comprise the video encoding device being configured to determine whetherto adjust a parameter associated with video encoding or video decoding, whether to disable a tool associated with video encoding or video decoding, whether to adjust an image resolution associated with a video, or whether to adjust a bitrate associated with the video.

[0010] In examples, the video encoding device may be further configured to receive a second request from the video decoding device, wherein the second request may indicate a modification of the first request or a cancellation of the first request. In examples, the first response may indicate that the video encoding device may implement only a subset of the operational changes indicated by the first request.

[0011] A computer program product stored on a non-transitory computer readable medium may comprise program code instructions for implementing (e.g., when executed by a processor) the operations described for the video decoding device or the video encoding device. Further, data comprising information representative of the first request sent by the video decoding device, or the first response sent by the video encoding device may be transmitted.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0013] 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 an embodiment.

[0014] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0015] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0016] FIG. 2 illustrates an example video encoder.

[0017] FIG. 3 illustrates an example video decoder.

[0018] FIG. 4 illustrates an example of a system in which various aspects and examples may be implemented.

[0019] FIG. 5 illustrates an example of using interactive signaling between a decoder (e.g., in a receiver) and a transmitter (e.g., including an encoder) to exchange metadata on how to reduce the energy consumed at the decoder side by adapting the coding process at the encoder side.

[0020] FIG. 6 illustrates an example of decoding operation reduction request / response interactive signaling.

[0021] FIG. 7 illustrates an example of a process at the encoder side in case of a cancellation request.

[0022] FIG. 8 illustrates an example of a process at the encoder side in case of a cancellation request that may be partially accepted by the encoder.

[0023] FIG. 9 illustrates an example of a process at the encoder side in case of a DOR-Req.

[0024] FIG. 10 illustrates an example of a process at the encoder side in case of a DOR-Req partially followed.

[0025] FIG. 11 illustrates an example of a process at the encoder side in case of a DOR-Req, where the encoder may select additional and / or alternative coding parameters.

[0026] FIG. 12 illustrates an example of a process at the decoder side.DETAILED DESCRIPTION

[0027] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings.

[0028] 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.

[0029] As shown in FIG. 1 A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, 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.

[0030] 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 / 115, 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, a Home 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.

[0031] The base station 114a may be part of the RAN 104 / 113, 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 mayutilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0032] 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).

[0033] 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 / 113 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 115 / 116 / 117 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).

[0034] 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).

[0035] 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).

[0036] 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).

[0037] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.1 1 (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.

[0038] 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 / 115.

[0039] The RAN 104 / 113 may be in communication with the CN 106 / 115, 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 / 115 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. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0040] The CN 106 / 115 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 / 113 or a different RAT.

[0041] 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.

[0042] 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.

[0043] 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 coupled to 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.

[0044] 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.

[0045] 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 / receiveelements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0046] 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.

[0047] 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).

[0048] 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.

[0049] 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.

[0050] 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, asatellite 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.

[0051] 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 1 18). 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)).

[0052] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0053] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0054] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0055] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0056] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0057] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0058] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0059] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0060] Although the WTRU is described in FIGS. 1 A-1 D 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.

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

[0062] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0063] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0064] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0065] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0066] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0067] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0068] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0069] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0070] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In anembodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0071] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0072] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0073] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0074] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0075] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0076] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0077] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0078] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0079] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode- B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a- b, and / or any other device(s) 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.

[0080] 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 perform testing using over-the-air wireless communications.

[0081] 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.

[0082] This application describes a variety of aspects, including tools, features, examples, 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 application or scope of those aspects. Indeed, all of the different aspects may be combined and interchanged to provide further aspects. Moreover, the aspects may be combined and interchanged with aspects described in earlier filings as well.

[0083] The aspects described and contemplated in this application may be implemented in many different forms. FIGS. 5-12 described herein may provide some examples, but other examples are contemplated. The discussion of FIGS. 5-12 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 may 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.

[0084] In the present application, the terms “reconstructed” and “decoded” may be used interchangeably, the terms “pixel” and “sample” may be used interchangeably, the terms “image,” “picture” and “frame” may be used interchangeably.

[0085] 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 examples 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.

[0086] Various methods and other aspects described in this application may be used to modify modules, for example, decoding modules, of a video encoder 200 and decoder 300 as shown in FIG. 2 and FIG. 3. Moreover, the subject matter disclosed herein may be applied, for example, to any type, format or version of video coding, whether described in a standard or a recommendation, whether pre-existing or future- developed, and extensions of any such standards and recommendations. Unless indicated otherwise, or technically precluded, the aspects described in this application may be used individually or in combination.

[0087] Various numeric values are used in examples described the present application, such as request type values, mode values, bit positions, bit values, parameter / flag values, operation labels, descriptor ID labels, percentage of change values, value ranges, multiplier values, etc. These and other specific values are for purposes of describing examples and the aspects described are not limited to these specific values.

[0088] FIG. 2 is a diagram showing an example video encoder. Variations of example encoder 200 are contemplated, but the encoder 200 is described below for purposes of clarity without describing all expected variations.

[0089] Before being encoded, the video sequence may go through pre-encoding processing (201), for example, applying a color transform to the input color picture (e.g., conversion from RGB 4:4:4 to YCbCr 4:2:0), or performing a remapping of the input picture components in order to get a signal distribution more resilient to compression (for instance using a histogram equalization of one of the color components). Metadata may be associated with the pre-processing, and attached to the bitstream.

[0090] In the encoder 200, a picture is encoded by the encoder elements as described below. The picture to be encoded is partitioned (202) and processed in units of, for example, coding units (CUs). Each unit is encoded using, for example, either an intra or inter mode. When a unit is encoded in an intra mode, it performs intra prediction (260). In an inter mode, motion estimation (275) and compensation (270) are performed. The encoder decides (205) which one of the intra mode or inter mode to use for encoding the unit, and indicates the intra / inter decision by, for example, a prediction mode flag. Prediction residuals are calculated, for example, by subtracting (210) the predicted block from the original image block.

[0091] The prediction residuals are then transformed (225) and quantized (230). The quantized transform coefficients, as well as motion vectors and other syntax elements, such as picture partitioning information, are entropy coded (245) to output a bitstream. The encoder can skip the transform and apply quantization directly to the non-transformed residual signal. The encoder can bypass both transform and quantization, i.e., the residual is coded directly without the application of the transform or quantization processes.

[0092] The encoder decodes an encoded block to provide a reference for further predictions. The quantized transform coefficients are de-quantized (240) and inverse transformed (250) to decode prediction residuals. Combining (255) the decoded prediction residuals and the predicted block, an image block is reconstructed. In-loop filters (265) are applied to the reconstructed picture to perform, for example, deblocking / SAO (Sample Adaptive Offset) / ALF (Adaptive Loop Filtering) filtering to reduce encoding artifacts. The filtered image is stored at a reference picture buffer (280).

[0093] FIG. 3 is a diagram showing an example of a video decoder. In example decoder 300, a bitstream is decoded by the decoder elements as described below. Video decoder 300 generally performs a decoding pass reciprocal to the encoding pass as described in FIG. 2. The encoder 200 also generally performs video decoding as part of encoding video data.

[0094] In particular, the input of the decoder includes a video bitstream, which may be generated by video encoder 200. The bitstream is first entropy decoded (330) to obtain transform coefficients, prediction modes, motion vectors, and other coded information. The picture partition information indicates how the picture is partitioned. The decoder may therefore divide (335) the picture according to the decoded picture partitioning information. The transform coefficients are de-quantized (340) and inverse transformed (350) to decode the prediction residuals. Combining (355) the decoded prediction residuals and the predicted block, an image block is reconstructed. The predicted block may be obtained (370) from intra prediction (360) or motion- compensated prediction (i.e., inter prediction) (375). In-loop filters (365) are applied to the reconstructed image. The filtered image is stored at a reference picture buffer (380). In some examples (e.g., for a given picture) the contents of the reference picture buffer 380 on the decoder 300 side may be identical to the contents of the reference picture buffer 280 on the encoder 200 side (e.g., for the same picture).

[0095] The decoded picture can further go through post-decoding processing (385), for example, an inverse color transform (e.g. conversion from YCbCr 4:2:0 to RGB 4:4:4) or an inverse remapping performing the inverse of the remapping process performed in the pre-encoding processing (201). The post-decoding processing can use metadata derived in the pre-encoding processing and signaled in the bitstream. In an example, the decoded images (e.g., after application of the in-loop filters (365) and / or after post-decoding processing (385), if post-decoding processing is used) may be sent to a display device for rendering to a user.

[0096] FIG. 4 is a diagram showing an example of a system in which various aspects and examples described herein may be implemented. System 400 may 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 400, singly or in combination, may be embodied in a single integrated circuit (IC), multiple ICs, and / or discrete components. For example, in at least one example, the processing and encoder / decoder elements of system 400 are distributed across multiple ICs and / or discrete components. In various examples, the system 400 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 examples, the system 400 is configured to implement one or more of the aspects described in this document.

[0097] The system 400 includes at least one processor 410 configured to execute instructions loaded therein for implementing, for example, the various aspects described in this document. Processor 410 can include embedded memory, input output interface, and various other circuitries as known in the art. The system 400 includes at least one memory 420 (e.g., a volatile memory device, and / or a non-volatile memory device). System 400 includes a storage device 440, 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 440 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 400 includes an encoder / decoder module 430 configured, for example, to process data to provide an encoded video or decoded video, and the encoder / decoder module 430 can include its own processor and memory. The encoder / decoder module 430 represents module(s) that may be included in adevice 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 430 may be implemented as a separate element of system 400 or may be incorporated within processor 410 as a combination of hardware and software as known to those skilled in the art.

[0099] Program code to be loaded onto processor 410 or encoder / decoder 430 to perform the various aspects described in this document may be stored in storage device 440 and subsequently loaded onto memory 420 for execution by processor 410. In accordance with various examples, one or more of processor 410, memory 420, storage device 440, and encoder / decoder module 430 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 examples, memory inside of the processor 410 and / or the encoder / decoder module 430 is used to store instructions and to provide working memory for processing that is needed during encoding or decoding. In other examples, however, a memory external to the processing device (for example, the processing device may be either the processor 410 or the encoder / decoder module 430) is used for one or more of these functions. The external memory may be the memory 420 and / or the storage device 440, for example, a dynamic volatile memory and / or a non-volatile flash memory. In several examples, an external non-volatile flash memory is used to store the operating system of, for example, a television. In at least one example, a fast external dynamic volatile memory such as a RAM is used as working memory for video encoding and decoding operations.

[0101] The input to the elements of system 400 may be provided through various input devices as indicated in block 445. 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. 4, include composite video.

[0102] In various examples, the input devices of block 445 have associated respective input processing elements as known in the art. For example, the RF portion may 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 may be referred to as a channel in certain examples, (iv) demodulating the downconverted and band-limited signal, (v) performing error correction,and / or (vi) demultiplexing to select the desired stream of data packets. The RF portion of various examples 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 nearbaseband frequency) or to baseband. In one set-top box example, 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 desired frequency band. Various examples 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 examples, the RF portion includes an antenna.

[0103] The USB and / or HDMI terminals can include respective interface processors for connecting system 400 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, may be implemented, for example, within a separate input processing IC or within processor 410 as necessary. Similarly, aspects of USB or HDMI interface processing may be implemented within separate interface ICs or within processor 410 as necessary. The demodulated, error corrected, and demultiplexed stream is provided to various processing elements, including, for example, processor 410, and encoder / decoder 430 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 400 may be provided within an integrated housing, Within the integrated housing, the various elements may be interconnected and transmit data therebetween using suitable connection arrangement 425, for example, an internal bus as known in the art, including the Inter- IC (I2C) bus, wiring, and printed circuit boards.

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

[0106] Data is streamed, or otherwise provided, to the system 400, in various examples, 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 examples is received over the communications channel460 and the communications interface 450 which are adapted for Wi-Fi communications. The communications channel 460 of these examples 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 examples provide streamed data to the system 400 using a set-top box that delivers the data over the HDMI connection of the input block 445. Still other examples provide streamed data to the system 400 using the RF connection of the input block 445. As indicated above, various examples provide data in a non-streaming manner. Additionally, various examples use wireless networks other than Wi-Fi, for example a cellular network or a Bluetooth® network.

[0107] The system 400 can provide an output signal to various output devices, including a display 475, speakers 485, and other peripheral devices 495. The display 475 of various examples 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 475 may be for a television, a tablet, a laptop, a cell phone (mobile phone), or other device. The display 475 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 495 include, in various examples, one or more of a stand-alone digital video disc (or digital versatile disc) (DVD, for both terms), a disk player, a stereo system, and / or a lighting system. Various examples use one or more peripheral devices 495 that provide a function based on the output of the system 400. For example, a disk player performs the function of playing the output of the system 400.

[0108] In various examples, control signals are communicated between the system 400 and the display 475, speakers 485, or other peripheral devices 495 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 may be communicatively coupled to system 400 via dedicated connections through respective interfaces 470, 480, and 490. Alternatively, the output devices may be connected to system 400 using the communications channel 460 via the communications interface 450. The display 475 and speakers 485 may be integrated in a single unit with the other components of system 400 in an electronic device such as, for example, a television. In various examples, the display interface 470 includes a display driver, such as, for example, a timing controller (T Con) chip.

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

[0110] The examples may be carried out by computer software implemented by the processor 410 or by hardware, or by a combination of hardware and software. As a non-limiting example, the examples may beimplemented by one or more integrated circuits. The memory 420 may be of any type appropriate to the technical environment and may 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 410 may 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.

[0111] Various implementations involve decoding. “Decoding”, as used in this application, 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 examples, 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 examples, such processes also, or alternatively, include processes performed by a decoder of various implementations described in this application, for example, sending, to a video encoding device, a decoding operation reduction request (DOR-Req) that indicates a DOR-Req type associated with an energy saving feature; receiving, from the video encoding device, a decoding operation reduction response (DOR-Resp) comprising a DOR-Resp indication indicating whether or to what extent the encoder accepts the DOR-Req; decoding a current block using decoding parameters corresponding to the DOR-Resp indication; determining whether the DOR-Resp corresponds to the DOR- Req; determining whether an alternative or additional energy saving feature other than the energy saving feature associated with the DOR-Req is applicable if the DOR-Resp does not correspond with the DOR-Req; decoding the current block using decoding parameters corresponding to the alternative or additional energy saving feature if the alternative or additional energy saving feature is applicable; sending, to the video encoding device, a second DOR-Req that indicates a DOR-Req type associated with the alternative or additional energy saving feature; etc.

[0112] As further examples, in one example “decoding” refers only to entropy decoding, in another example “decoding” refers only to differential decoding, and in another example “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 and is believed to be well understood by those skilled in the art.

[0113] Various implementations involve encoding. In an analogous way to the above discussion about “decoding”, “encoding” as used in this application 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 examples, 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 examples, such processes also, or alternatively, include processes performed by an encoder of various implementations described in this application, for example, receiving, from a video decoding device, a decoding operation reduction request (DOR-Req) that indicates a DOR-Req type associated with an energy saving feature; sending, to the video decoding device, a decoding operation reduction response (DOR-Resp) comprising a DOR-Resp indication indicating whether or to what extent the DOR-Req is accepted; encoding a current block using encoding parameters corresponding to the DOR-Resp indication; determining energy savings corresponding to the DOR-Req; determining at least one coding parameter, coding tool, picture resolution, or video frame rate different from coding parameters, coding tools, picture resolution, or video frame corresponding to the DOR-Req that provides the determined energy savings; encoding the current block using the determined at least one coding parameter, coding tool, picture resolution, or video frame rate different from coding parameters, coding tools, picture resolution, or video frame corresponding to the DOR- Req that provides the determined energy savings; etc.

[0114] As further examples, in one example “encoding” refers only to entropy encoding, in another example “encoding” refers only to differential encoding, and in another example “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 and is believed to be well understood by those skilled in the art.

[0115] Note that syntax elements as used herein, such as syntax elements shown in and described with reference to Tables 1 -6, are descriptive terms. As such, they do not preclude the use of other syntax element names.

[0116] 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.

[0117] The implementations and aspects described herein may 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 may be implemented in, for example, appropriate hardware, software, and firmware. The methods may 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.

[0118] Reference to “one example” or “an example” 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 example is included in at least one example. Thus, the appearances of the phrase “in one example” or “in an example” or “in one implementation” or “in an implementation”, as well any other variations, appearing in various places throughout this application are not necessarily all referring to the same example.

[0119] Additionally, this application 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. Obtaining may include receiving, retrieving, constructing, generating, and / or determining.

[0120] Further, this application 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.

[0121] Additionally, this application 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.

[0122] It is to be appreciated that the use of any of the following 7”, “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, as is clear to one of ordinary skill in this and related arts, for as many items as are listed.

[0123] Also, as used herein, the word “signal” refers to, among other things, indicating something to a corresponding decoder. Encoder signals may include, for example, a decoding operation reduction response (DOR-Resp) message, etc. In this way, in an example 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 may 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 examples. It is to be appreciated that signaling may 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 examples. While the preceding relates to the verb form of the word “signal”, the word “signal” can also be used herein as a noun.

[0124] As will be evident to one of ordinary skill in the art, implementations may produce a variety of signals formatted to carry information that may 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 may be formatted to carry the bitstream of a described example. Such a signal may be formatted, for example, as an electromagnetic wave (for example, using a radio frequency portion of spectrum) or as a baseband signal. The formatting may include, for example, encoding a data stream and modulating a carrier with the encoded data stream. The information that the signal carries may be, for example, analog or digital information. The signal may be transmitted over a variety of different wired or wireless links, as is known. The signal may be stored on, or accessed or received from, a processor- readable medium.

[0125] Many examples are described herein. Features of examples may be provided alone or in any combination, across various claim categories and types. Further, examples may include one or more of the features, devices, or aspects described herein, alone or in any combination, across various claim categories and types. For example, features described herein may be implemented in a bitstream or signal that includes information generated as described herein. The information may allow a decoder to decode a bitstream, the encoder, bitstream, and / or decoder according to any of the embodiments described. For example, features described herein may be implemented by creating and / or transmitting and / or receiving and / or decoding a bitstream or signal. For example, features described herein may be implemented a method, process, apparatus, medium storing instructions, medium storing data, or signal. For example, features described herein may be implemented by a TV, set-top box, cell phone, tablet, or other electronic device that performs decoding. The TV, set-top box, cell phone, tablet, or other electronic device may display (e.g. using a monitor, screen, or other type of display) a resulting image (e.g., an image from residual reconstruction ofthe video bitstream). The TV, set-top box, cell phone, tablet, or other electronic device may receive a signal including an encoded image and perform decoding.

[0126] Interactive signaling for a decoding operation reduction request and / or response for energy saving may provide signaling mechanisms to enable a decoder to control its energy usage.

[0127] Reducing the energy consumption of electronic devices may reduce their environmental impact and / or contribute to the emergence of a sustainable display industry.

[0128] Videos represent more than 80% of data consumed by end users. Decoders in end user devices may process received videos, which may be transmitted over networks. Energy consumed while decoding the videos may be reduced.

[0129] Feature(s) described herein may be implemented at an encoder and / or decoder. Feature(s) described herein may be implemented at a power optimization module on a transmitter and / or receiver side of the video streaming end-to-end chain.

[0130] FIG. 5 illustrates an example of using interactive signaling between a decoder (e.g., in a receiver) and a transmitter (e.g., including an encoder) to exchange metadata on how to reduce the energy consumed at the decoder side by adapting the coding process at the encoder side.

[0131] A decoder may send a request for decoding operation reduction to a transmitter. A capability may be implemented for the transmitter to send a decoding operation reduction response, for example, to acknowledge reception of the request message and / or to inform the decoder of what the encoder may accept as changes in its coding process.

[0132] Metadata (e.g., Green Metadata) may facilitate the reduction of energy usage at the decoder, for example, through (e.g., the definition of) a decoding operation reduction request (DOR-Req) sent by a decoder to a transmitter to request changes in the coding process. One or more (e.g., three) types of requests may be defined. For example, a remote encoder (e.g., in a first mode, where dec_pow_reduction_type may be equal to 0) may be requested to adjust its encoding parameters so that (e.g., when the local decoder decodes the bitstream) the power saving of the local decoder may match the (e.g., requested) power saving, which may be implied by the DOR-Req message. A remote encoder (e.g., in a second mode, where dec_pow_reduction_type may be equal to 1) may be requested to disable coding tools so that (e.g., when the local decoder decodes the bitstream) the power consumption of the local decoder may be decreased. A remote encoder (e.g., in a third mode, where dec_pow_reduction_type may be equal to 2) may be requested to adjust the picture resolution and / or video frame rate so that (e.g., when the local decoder decodes the bitstream) the power consumption of the local decoder may be decreased. An example dec_pow_reduction_type may correspond to requesting the cancellation of prior requests.

[0133] Metadata may be sent to request one or more (e.g., specific) coding parameters, for example, depending on the mode.

[0134] There may be a response message on the transmitter side, for example, for the transmitter to acknowledge that it received a request from the decoder and / or to indicate (e.g., give information on) what the transmitter accepts (e.g., determined) to change in its coding process based on the received request. For example, a response message may indicate whether changes in the coding process match the received request.

[0135] A receiver may respond to a decoder, for example, if / when a request for decoding operation reduction is received. This response may allow the receiver to acknowledge reception of the request and / or to indicate how the receiver may change its coding process to respond to the requested changes from the decoder. A Decoding Operation Reduction mechanism may support an interactive signaling framework for a response message.

[0136] Energy-Efficient Media Consumption (e.g., Green Metadata) may include metadata signaling information for decoding operation reduction, which may reduce the energy consumption at the decoder side. A mechanism for interactive signaling may enable a decoder to request one or more (e.g., specific) decoding operation reductions. Examples of metadata syntax are shown in Table 1 .Table 1 - Example of syntax for interactive signaling for remote decoder-power reduction

[0137] A transmitter in a (e.g., each) device may send a decoding operation reduction request (DOR-Req) message to the attention of the remote encoder. A DOR-Req message (e.g., in a first mode, where dec_pow_reduction_type may be equal to 0) may request the remote encoder to adjust its encoding parameters so that (e.g., when the local decoder decodes the bitstream) the power saving of the local decoder may match the power saving implied by the DOR-Req message. A DOR-Req message (e.g., in a second mode, where dec_pow_reduction_type may be equal to 1) may request the remote encoder disable coding tools so that (e.g., when the local decoder decodes the bitstream) the power consumption of the local decoder may be decreased. A DOR-Req message (e.g., in a third mode, where dec_pow_reduction_type may be equal to 2) may request the remote encoder adjust the picture resolution and / or video frame rate so that (e.g., when the local decoder decodes the bitstream) the power consumption of the local decoder may be decreased.

[0138] Metadata may be sent to complement a request for a (e.g., each) dec_pow_reduction_type type. Metadata (e.g., additional metadata) may include (e.g., additional) information on how to perform the request for the type of request, which may be indicated by dec_pow_reduction_type.

[0139] A transmitter may (e.g., first) acknowledge reception of a decoding operation reduction request. A transmitter may (e.g., then) inform the decoder of what the transmitter actually accepts to produce as reduction operations. A decoding operation reduction response may be implemented, for example, through (e.g., definition of) syntax and / or semantics of a response message used by the transmitter, which may be consistent / compatible with one or more codecs (e.g., AVC, HEVC and VVC).

[0140] Energy-Efficient Media Consumption (Green Metadata) may provide a capability for a decoder (e.g., in a point-to-point communication) to request a decoding operation reduction (DOR-Req), which may be indicated and / or implemented through, for example, changes in encoder coding parameters, disabling of one or more filters of the encoder, and / or changes in the image resolution and frame rate.

[0141] A corresponding decoding operation reduction response (DOR-Resp) may allow the transmitter to acknowledge that it received the request issued by the decoder and / or notify the decoder with an indication of the decoding operation reduction the transmitter accepts to produce / implement. The decoder may receive the response from the transmitter. The decoder may adapt further its operating process (e.g., by reducing other parts of its processing) and / or may request (e.g., further) decoding operation reductions, for example, in response to the indication(s) in the transmitter response, which may match the decoder’s request. Syntax and signaling of a message response may be described herein.

[0142] Interactive signaling for a decoding operation reduction response for energy saving may relate to one or more operations by an encoder and / or decoder and / or by a power optimization module on the transmitter and / or receiver side of a video streaming end-to-end chain.

[0143] A receiver and / or decoder may make requests for decoding operation reduction. A request may ask a transmitter and / or encoder to modify its encoded bitstream so that the modification enables the decoder to reduce its energy consumption. The transmitter and / or the encoder may send a response to acknowledge the request and / or to inform or indicate what modifications (e.g., if any) are accepted in the encoding process.

[0144] A decoding operation reduction response may be provided in the form of a message, which may be carried at a transport level between an encoder and decoder. Syntax and semantics examples are described herein.

[0145] A decoding operation reduction response may be implemented, for example, using signaling in a point-to-point communication between a receiver and a transmitter. A decoding operation reduction response (DOR-Resp) may be provided from a transmitter to a receiver, for example, in response to a decoding operation reduction request (DOR-Req) from the decoder to the receiver. A DOR-Resp may allow a transmitter to acknowledge reception of the DOR-Req from the decoder and / or to inform the decoder how the transmitter accepts none or more (e.g., all) aspects of the request, for example, by indicating new values of related metadata the transmitter may have changed in its coding process. The decoder may be informed by the response that its request was received and / or to which extent the request was accepted. The response may indicate, for example, that the request was not accepted or was partially accepted. The decoder may use the indication, for example, to adapt by modifying one or more (e.g., other) parts of its process for reducing its energy consumption, and / or to (re-)send the same or different request (e.g., another request) with the same or different dec_pow_reduction_type that might be additionally and / or alternatively accepted by the encoder, e.g., in whole or in part.

[0146] FIG. 6 describes an example of a process of interactive signaling between a transmitter and a receiver in the context of decoding operation reduction in which a DOR-Resp response message is provided from the transmitter to the receiver.

[0147] FIG. 6 illustrates an example of decoding operation reduction request / response interactive signaling.

[0148] As shown in FIG. 6, at 1 , the transmitter may announce a service (e.g., service#!) as a “green” profile service.

[0149] At 2, the user may select service#! from a service list. An Energy aware application request for the service may be generated. At 3, the reception of the video data may begin / start.

[0150] At 4, for example, a low battery level may be raised. The receiver may decide to initiate a process of decoding operation reduction, e.g., to reduce its energy consumption.

[0151] At 5, a Decoding Operation Reduction Request may be sent from the receiver to the transmitter, for example, with a new or updated resolution value and / or with request to disable one or more encodingfilters. The transmitter may acknowledge reception of the request and / or may inform the decoder how the transmitter may change its coding parameters, for example, by sending a Decoding Operation Reduction Response. The transmitter may (e.g., then) change its coding parameters. At 6, the transmitter may start encoding the video data according to the new coding parameters.

[0152] At 7, an event of high level of battery may be raised.

[0153] At 8, the decoder may decide to stop the Decoding Operation Reduction process. The decoder may send a Decoding Operation Reduction Request of cancellation. The transmitter may send a Decoding Operation Reduction Response, for example, to acknowledge reception of the request and / or to indicate if and / or to what extent the transmitter accepts the request.

[0154] An example of syntax that may be used for a remote Decoding Operation Reduction Response (DOR-Resp) message, which may be sent by the transmitter, is described in Table 42.

[0155] A DOR-Resp message may allow a transmitter to acknowledge that it received a Decoding Operation Reduction Request (DOR-Req) and / or to indicate what the transmitter has accepted / determined to change in its coding process, which may depend on the type of DOR-Req received by the transmitter.

[0156] In some examples, a message may be used to acknowledge a request of cancellation, e.g., with a list of requested types. A DOR-Resp message may include a list of dec_pow_reduction_requested types of requests that the transmitter has accepted / determined to perform. In some examples, the last request(s) (e.g., most recent request(s)) of one or more types corresponding to the list of requested types may be cancelled. An example of syntax for a DOR-Resp is shown in Table 2.Table 2 - Example of syntax for interactive signaling from the transmitter to acknowledge remote decoderpower reduction

[0157] A message may be used to acknowledge a (e.g., global) cancellation of one or more (e.g., all) previous decoding operation reduction requests, for example, if / when nb_dec_pow_reduction_type_resp equals 0. In some examples, information including image resolution and / or frame rate may be sent to the decoder. In some examples, the image resolution and / or frame rate may not be sent.

[0158] In some examples (e.g., with the same previous syntax), one or more (e.g., all) requests of types corresponding to the requested list of types may be cancelled.

[0159] In some examples, an empty message may acknowledge or indicate a (e.g., global) cancellation of (e.g., all) previous decoding operation reduction requests.

[0160] In some examples, an empty message may acknowledge the last received request from the decoder.

[0161] In some examples, one or more syntax elements may be used to acknowledge remote decoderpower reduction. Table 3 below shows an example of a message including such syntax elements. Table 1 - Example syntax for interactive signaling from a transmitter to acknowledge remote decoder-power reduction

[0162] In the example syntax shown in Table 3, a message may include a dec_pow_reduction_type_resp syntax element (e.g., a flag) with a value of 3 (or another suitable value) to acknowledge the reception of one or more extended decoding operation reduction types. For example, in a first extended decoding operation reduction type, an encoder (e.g., a remote encoder) may acknowledge the types of decoding operation reduction requests that the encoder has accepted to cancel.

[0163] In the example syntax shown in Table 3, variables named with a suffix “_resp” may indicate the same information (e.g., have the same meaning) as similarly named variables described herein without the suffix.

[0164] In some examples, a message that may be used to acknowledge a request of (e.g., global) cancellation may include (e.g., only) the dec_pow_reduction_type flag, for example, with a value of three (3). An example of the syntax is described in Table 4.Table 4 - Example syntax for interactive signaling from the transmitter to acknowledge remote decoderpower reduction

[0165] In some examples, a message including (e.g., only) the dec_pow_reduction_type flag (e.g., with a value of three (3)), may (e.g., be used to) acknowledge a request of cancellation of the last request.

[0166] In some examples, a message including the dec_pow_reduction_type flag (e.g., with a value of three (3)) may (e.g., be used to) acknowledge a request of cancellation of the last request of a given type signaled in the message. Metadata (e.g., additional metadata), such as dec_pow_reduction_type_id, may be included, for example, to indicate the type of the last request that has been canceled. In some examples(e.g., with the same semantics), the metadata may indicate that (e.g., all) previous requests of type dec_pow_reduction_type_id have been cancelled. An example of the syntax is described in Table 5.Table 5 - Example of syntax for interactive signaling from the transmitter to acknowledge remote decoder- power reduction

[0167] In some examples, a message including the dec_pow_reduction_type flag (e.g., with a value of three (3)) may (e.g., be used to) acknowledge a request of cancellation of a request for a given identifier signaled in the message. Metadata (e.g., additional metadata), such as dec_pow_reduction_id, may be included to indicate the identifier of the request that has been cancelled. An example of the syntax is described in Table 6.

[0168] In some examples, a list of request identifiers may be provided to acknowledge their cancellation. For example, the syntax may be similar to the example syntax shown in Table 2. Table 6 - Example of syntax for interactive signaling from the transmitter to acknowledge remote decoderpower reduction

[0169] In some examples, a message that may (e.g., be used to) acknowledge a request of cancellation of one or more requests may (e.g., also) include information on related metadata, e.g., per type. The information may be conveyed, for example, through the use of a bit field, which may allow the information to be more accurate about the acknowledged cancellation. An example of the syntax is described in Table 7.Table 7 - Example of syntax for interactive signaling from the transmitter to acknowledge remote decoderpower reduction

[0170] In some examples, (e.g., all) requests of a type (e.g., dec_pow_reduction_type equal to 0) may be cancelled if the cancellation request from the decoder concerns decoding operation reduction of the type (e.g., dec_pow_reduction_type equal to 0). All requests of the type may be cancelled, for example, if the cancellation is (e.g., indicated to be) global. The requested percentage change of local decoding operationsin the encoder (e.g., PoecopsReductionReq)maY be set to zero (0), for example, if the transmitter accepts the global cancellation. The corresponding requested percentage change of local decoding operations in the encoder, memorized in the decoder, may (e.g., also) be set to zero (0), for example, if the decoder (e.g., also) keeps some memory of the percentage change, e.g., upon response from the encoder.

[0171] A decoder may request one or more types of decoding operation reduction. An encoder may determine and / or signal one or more additional and / or alternative (e.g., other) types of decoding operation reduction that the encoder may accept to set in place, e.g., in response to the decoder request. An encoder may (e.g., in this mode) evaluate the amount of (e.g., indicated and / or determined) energy savings that could be achieved by the requests from the decoder. An encoder may (e.g., further) determine, propose and / or set in place one or more other and different (e.g., additional and / or alternative) decoding operation reductions, which may correspond to the same or similar amount of (e.g., indicated and / or determined) energy savings.

[0172] Signaling may be implemented between an encoder and decoder. An encoder (e.g., a remote encoder) may send a decoding operation reduction response (DOR-Resp) message to a decoder (e.g., a remote decoder), for example, in response to a decoding operation reduction request (DOR-Req). An encoder (e.g., in a first mode, where dec_pow_reduction_type may be equal to 0) may acknowledge (e.g., in a DOR-Resp message) that the encoder may proceed or has proceeded to an adjustment of its encoding parameters to save power for the decoder while decoding. An encoder (e.g., in a second mode, where dec_pow_reduction_type may be equal to 1) may acknowledge (e.g., in a DOR-Resp) message that the encoder may disable or has disabled one or more coding tools. The list of coding tools the encoder has accepted to disable may be sent or indicated in the message. An encoder (e.g., in a third mode) may acknowledge (e.g., in a DOR-Resp) message that the encoder may adjust or has adjusted the picture resolution and / or video frame rate. An encoder (e.g., in a fourth mode) may acknowledge (e.g., in a DOR- Resp message) the list of types of decoding operation reduction requests the encoder may accept or has accepted to cancel.

[0173] An empty message may indicate that the encoder may accept or has accepted to perform a (e.g., global) cancellation of (e.g., all) previous decoding operation reduction requests.

[0174] As shown in Table 3, the signaling may be modified. For example, in response to a decoding operation reduction request (DOR-Req), an encoder (e.g., a remote encoder) may send a decoding operation reduction response (DOR-Resp) message to a decoder (e.g., a remote decoder). The message may indicate a first mode (e.g., when dec_pow_reduction_type_resp is equal to 0), with which the encoder may acknowledge that it has made an adjustment of its encoding parameters to save power while decoding. The message may indicate a second mode (e.g., when dec_pow_reduction_type_resp is equal to 1), with whichthe encoder may acknowledge that it has disabled one or more coding tools (e.g., the list of coding tools disabled may also be indicated in the message). The message may indicate a third mode (e.g., when dec_pow_reduction_type_resp is equal to 2), with which the encoder may acknowledge that it has adjusted a picture resolution and / or a video frame rate. The message may indicate a fourth mode (e.g., when dec_pow_reduction_type_resp is equal to 3), which may indicate that one or more extended decoding operation reduction types are acknowledged. For instance, with a first extended decoding operation reduction type, the encoder may acknowledge the types of decoding operation reduction requests that the encoder has accepted to cancel.

[0175] The type of the decoder power reduction method (e.g., dec_pow_reduction_type) may indicate that the encoder acknowledges to have received a request and / or accepts to apply the request, e.g., in whole or in part. The type may be indicated, for example, by an unsigned integer. Examples of types of power reduction are shown in Table 8.Table 8 - Example definition of dec_pow_reduction_types

[0176] In examples, the definition shown in Table 8 may be modified (e.g., to correspond to the syntax shown in Table 3), as shown in Table 9.Table 2 - Example definition of dec_pow_reduction_type_resp

[0177] A decoder operations reduction response (e.g., dec_ops_reduction_resp) may indicate the variation of local decoding operations relative to the local decoding operations, for example, since the last dec_ops_reduction_req was sent to the transmitter, or since the start of the video session (e.g., if an earlier dec_ops_reduction_req was not sent) that the encoder may accept to set in place. The signaled parameter dec_ops_reduction_resp may be, for example, an integer in the interval [-31, 32], The parameter dec_ops_reduction_resp may be set equal to zero (0), for example, if / when absent, which may indicate that the requested variation of local decoding operations requested by the decoder was accepted by the encoder.

[0178] The value of PoecopsReductionReq may be derived, for example, by or based on dec_ops_reduction_resp. The value may indicate the requested percentage change of local decoding operations. The value of PoecopsReductionReq may be determined, for example, in accordance with Eq. (1):where dreqmay be set equal to dec_ops_reduction_resp.

[0179] A negative percentage may indicate a decrease of decoding operations. PoecopsReductionReq may be, for example, an integer, e.g., in the interval [-62, 64] in steps of two.

[0180] A disabled _loop_filters value (e.g., equal to one (1)) may indicate that loop filters were disabled. A disabled _loop_filters value (e.g., equal to zero (0)) may specify that the encoder does not agree / accept to disable loop filters. Loop filters may include (e.g., upon availability), a deblocking filter, sample Adaptive offset, and / or an adaptive loop filter. The absence of a disabled_loop_filters parameter may indicate that the requested disabling or enabling of loop filters was accepted by the encoder.

[0181] A disabled_bi_prediction value (e.g., equal to one (1)) may indicate bi-prediction is disabled in B slices. A disabled_bi_prediction value (e.g., equal to zero (0)) may indicate that the encoder does not agree / accept to disable bi-prediction in B slices. The absence of a disabled_bi_prediction parameter may indicate that the requested disabling or enabling of biprediction in B slices was accepted by the encoder.

[0182] A disabled Jntra_in_B value (e.g., equal to one (1)) may indicate intra prediction is disabled in B slices. A disable_intra_in_B value (e.g., equal to 0) may indicate that the encoder does not agree / accept to disable intra prediction in B slices. The absence of a disabled Jntra_in_B parameter may indicate that the requested disabling or enabling of intra prediction in B slices was accepted by the encoder.

[0183] A disabled_fracpel_filtering value (e.g., equal to one (1)) may indicate fractional pel filtering is disabled in P slices or B slices. A disabled_fracpel_filtering value (e.g., equal to zero (0)) may indicate that the encoder does not agree / accept to disable fractional pel filtering in P slices or B slices. The absence of adisabled_fracpel_filtering parameter may indicate that the requested disabling or enabling of fractional pel filtering in P slides or B slides was accepted by the encoder.

[0184] A user_defined_resp parameter may indicate whether or not the encoder agrees / accepts to enable or disable user-defined coding tools. The absence of a user_defined_req parameter may indicate that the requested disabling or enabling of user defined coding tools was accepted by the encoder.

[0185] A pic_width_in_luma_samples parameter may indicate the picture width in the units of luma samples that the encoder may accept to encode. The absence of a pic_width J n _luma_samples parameter may indicate the picture width in the units of luma samples requested by the decoder was accepted by the encoder.

[0186] A pic_height_in_luma_samples parameter may indicate the picture height in the units of luma samples that the encoder may accept to encode. The absence of a pic_height_in_luma_samples parameter may indicate the picture height in the units of luma samples requested by the decoder was accepted by the encoder.

[0187] A frames_per_second parameter may indicate the frame rate samples that the encoder accepts to produce. The absence of a frames_per_second parameter may indicate the frame rate samples requested by the decoder were accepted by the encoder.

[0188] A dec_pow_reduction_extension_type_resp parameter may indicate extended types of requests for decoding operation reduction acknowledged by the encoder. If dec_pow_reduction_extension_type_resp equals 0 (or another suitable value), it may indicate that a global or partial cancellation of one or more previous decoding operation reduction requests of a specific type as accepted at the transmitter side. In this case, the encoder may stop the corresponding changes previously enabled in a coding process. If a global cancellation was accepted, the transmitter may go back to a mode in which no change in local decoding operations compared to the start of a video session may be applied.

[0189] An nb_dec_pow_reduction_type_resp parameter may indicate the number of requested types of request the encoder accepts to cancel. A value of nb_dec_pow_reduction_type_resp (e.g., equal to zero (0)) may indicate that a (e.g., global) cancellation of (e.g., all) previous decoding operation reductions was accepted by the encoder. The absence of an nb_dec_pow_reduction_type_resp parameter may indicate a (e.g., global) cancellation of (e.g., all) types of previous decoding operation reduction requests.

[0190] A dec_pow_reduction_type_resp Jd[i] parameter may indicate that the encoder agrees / accepts to cancel the last request of a corresponding type.

[0191] A dec_pow_reduction_type_resp_id parameter may indicate that the encoder agrees / accepts to cancel the last request of corresponding type.

[0192] A dec_pow_reduction_resp_id parameter may indicate that the encoder agrees / accepts to cancel the request corresponding to the identified dec_pow_reduction_resp_id.

[0193] A dorm_flags parameter may indicate (e.g., in the form of a bit field) which decoding operation reduction methods the encoder agrees / accepts to cancel. An example representation / indication of dorm_flags may include, for example, one or more of the following: one or more bits (e.g., bit 0) may represent a Global_cancel_flag, which may indicate whether a global decoder power reduction cancel is accepted; one or more bits (e.g., bit 1 ) may represent a Dor_cancel_flag, which may indicate that the cancellation of a method including reducing the number of decoding operations may be accepted; one or more bits (e.g., bit 2) may represent an lf_cancel_flag, which may indicate that the cancellation of a method including disabling a loop filter tool may be accepted; one or more bits (e.g., bit 3) may represent a bp_cancel_flag, which may indicate that the cancellation of a method including disabling bi-prediction in a B slices tool may be accepted; one or more bits (e.g., bit 4) may represent an ib_cancel_flag, which may indicate that the cancellation of a method including disabling intra prediction in a B slices tool may be accepted; one or more bits (e.g., bit 5) may represent an fp_cancel_flag, which may indicate that the cancellation of a method including disabling fractional pel filtering in a P slices or B slices tool is accepted; one or more bits (e.g., bit 6) may represent a prls_cancel_flag, which may indicate that the cancellation of a method including changing the picture resolution in luma samples may be accepted; one or more bits (e.g., bit 7) may represent an fr_cancel_flag, which may indicates that the cancellation of a method including changing the picture frame rate may be accepted; and / or one or more bits (e.g., bits 8-10) may representone or more other flags or may be reserved.

[0194] A Decoding Operation Reduction response may be generated by the encoder.

[0195] FIG. 7 depicts a block diagram showing an example of coding parameters and generation of a DOR-Resp in response to a DOR-Req of type cancellation from a decoder.

[0196] As shown in FIG. 7, at 7001 , the request of cancellation from the decoder may be received. The coding parameters may be set back to normal mode. Normal mode may correspond to a state without (e.g., decoder-requested) energy savings (e.g., where no request of energy savings was sent from the decoder). At 7002, the picture may be encoded with the coding parameters in normal mode. At 7003, the DOR-Resp message may be generated. At 7004, the DOR-Resp message may be sent to the decoder.

[0197] FIG. 7 illustrates an example of a process at the encoder side in case of a cancellation request.

[0198] FIG. 8 depicts a block diagram showing an example of coding parameters and generation of a DOR-Resp in response to a DOR-Req of type cancellation from a decoder. As shown in FIG. 8, the encoder may partially follow the request from the decoder.

[0199] As shown in FIG. 8, at 8001 , the request of cancellation from the decoder may be received. The encoder may partially set its coding parameters back to normal mode. Normal mode may correspond to astate without (e.g., decoder-requested) energy savings (e.g., where no request of energy savings was sent from the decoder). At 8002, the picture may be encoded with the coding parameters as set in 8001 . At 8003, the DOR-Resp message may be generated, for example, with information on which coding parameters were set to normal mode and / or which coding parameters were not changed. At 8004, the DOR-Resp message may be sent to the decoder.

[0200] FIG. 8 illustrates an example of a process at the encoder side in case of a cancellation request that may be partially accepted by the encoder.

[0201] FIG. 9 depicts a block diagram of coding parameters and generation of a DOR-Resp in response to a DOR-Req from a decoder.

[0202] As shown in FIG. 9, at 9001 , a request of decoding operation reduction from a decoder may be received. The encoder may set its coding parameters according to the received request. At 9002, the picture may be encoded with the coding parameters as set in 9001. At 9003, the DOR-Resp message may be generated, for example, with information indicating how the coding parameters were set. At 9004, the DOR- Resp message may be sent to the decoder.

[0203] FIG. 9 illustrates an example of a process at the encoder side in case of a DOR-Req.

[0204] FIG. 10 depicts a block diagram showing an example of coding parameters and generation of a DOR-Resp in response to a DOR-Req from a decoder. As shown in FIG. 10, the encoder may partially follow the request of decoding operation reduction.

[0205] As shown in FIG. 10, at 1001 , a request of decoding operation reduction from a decoder may be received. The encoder may partially set its coding parameters according to the received request. At 1002, the picture may be encoded with the coding parameters as set in 1001. At 1003, the DOR-Resp message may be generated, for example, with information indicating how the coding parameters were set. At 1004, the DOR-Resp message may be sent to the decoder.

[0206] FIG. 10 illustrates an example of a process at the encoder side in case of a DOR-Req partially followed.

[0207] In the examples shown in FIGS. 7-10, the ordering of operations may be changed. For example, 7001 and 7002 may be exchanged with 7003 and 7004, 8001 and 8002 may be exchanged with 8003 and 8004, 9001 and 9002 may be exchanged with 9003 and 9004, 1001 and 1002 may be exchanged with 1003 and 1004.

[0208] FIG. 11 depicts a block diagram of coding parameters and generation of a DOR-Resp in response to a DOR-Req from a decoder. As shown in FIG. 11 , the encoder may (e.g., first) compute the energy savings implied by the request. The encoder may (e.g., partially) choose coding parameters other than, e.g.,in addition or alternative to, coding parameters indicated in the request. The selected coding parameters may result in the same or similar amount of energy savings as the coding parameters indicated in the request.

[0209] As shown in FIG. 11 , at 1101 , the request of decoding operation reduction from the decoder may be received. The encoder may compute the potential energy savings resulting from the requested encoding changes. At 1102, the encoder may (e.g., partially) choose another set of coding parameters, which may result in the same or similar amount of energy savings. At 1103, the encoder may set the coding parameters, according to the choice in 1 102. At 1104, the picture may be encoded with the coding parameters as set in 1103. At 1005, the DOR-Resp message may be generated, for example, with information indicating how the coding parameters were set. At 1006, the DOR-Resp message may be sent to the decoder. The ordering of steps shown in FIG. 11 may be changed.

[0210] FIG. 11 illustrates an example of a process at the encoder side in case of a DOR-Req, where the encoder may select additional and / or alternative coding parameters.

[0211] A decoder may implement a decoding process. FIG. 12 depicts a block diagram of an example of a process at the decoder side. As shown in FIG. 12, at 1201 , a low level battery event may be detected. The decoder may generate a decoding operation reduction request (DOR-req) at 1201 , e.g., in response to the low level battery event. At 1202, the decoder may send the DOR-Req to the transmitter. At 1203, the decoder may receive a picture, which may correspond to the coding parameters requested in the DOR-Req. At 1204, the decoder may (e.g., also) receive a decoding operation reduction response (DOR-Resp) from the transmitter, which may indicate how the transmitter has agreed / accepted to change its coding parameters according to the DOR-Req. At 1205, the decoder may check how the DOR-Resp corresponds to its DOR- Req. At 1206, the decoder may decode the picture, for example, if the DOR-Req and DOR-Resp correspond. At 1207, the decoder may check if it can set in place one or more other energy savings processes, for example, if the request and the response do not correspond. At 1208, the decoder may set in place one or more other energy savings processes, for example, if the decoder determined that it can set in place one or more other energy savings processes, e.g., before decoding the picture at 1210. At 1209, the decoder may decode the picture without setting other energy savings in place, which may occur at the expense of further reducing the low level of the battery detected at 1201 , for example, if the decoder determined that it cannot set in place one or more other energy savings processes.

[0212] FIG. 12 illustrates an example of a process at the decoder side.

[0213] Performing video coding using interactive signaling for a decoding operation reduction response for energy saving may provide one or more advantages. A signaling mechanism may enable the transmitter to acknowledge reception of a request from a receiver for coding modification(s) to provide decoder energysavings. A signaling mechanism may enable the transmitter to inform the receiver about which decoding operation reductions the transmitter accepts to set in place in response to the request.

[0214] 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 media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. 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 video decoding device, comprising: a processor configured to: send, to a video encoding device, a first request that indicates one or more operational changes associated with energy saving; receive, from the video encoding device, a first response that indicates whether or to what extent the video encoding device accepts the first request; and perform an operation based on the first response.

2. The video decoding device of claim 1 , wherein the processor being configured to perform the operation based on the first response comprises the processor being configured to decode a video block based on the first response or send a second request associated with energy saving to the video encoding device.

3. The video decoding device of claim 2, wherein the second request indicates a modification of the first request.

4. The video decoding device of any of claims 1-3, wherein the first response indicates that only a subset of the operational changes indicated by the first request has been accepted.

5. The video decoding device of claim 4, wherein the first request indicates multiple types of operational changes, and wherein the first response indicates which one or more types of operational indicated by the first request are accepted.

6. The video decoding device of any of claims 1 -5, wherein the first response indicates that a parameter associated with video encoding or video decoding has been adjusted, that a tool associated with video encoding or video decoding has been disabled, that an image resolution associated with a video has been adjusted, or that a bitrate associated with the video has been adjusted.

7. The video decoding device of any of claims 1-6, wherein the processor is further configured to send a second request to the video encoding device to cancel the first request at least partially.

8. The video decoding device of claim 7, wherein the processor is further configured to receive a second response that indicates that the first request has been cancelled at least partially.

9. The video decoding device of claim 8, wherein the second response indicates that all previous requests associated with energy saving sent by the video decoding device have been cancelled.

10. A method implemented by a video decoding device, the method comprising: sending, to a video encoding device, a first request that indicates one or more operational changes associated with energy saving; receiving, from the video encoding device, a first response that indicates whether or to what extent the video encoding device accepts the first request; and performing an operation based on the first response.

11. The method of claim 10, wherein performing the operation based on the first response comprises decoding a video block based on the first response or sending a second request associated with energy saving to the video encoding device.

12. The method of claim 10, wherein the second request indicates a modification of the first request.

13. The method of any of claims 10-12, wherein the first response indicates that only a subset of the operational changes indicated by the first request has been accepted.

14. The method of claim 13, wherein the first request indicates multiple types of operational changes, and wherein the first response indicates which one or more types of operational indicated by the first request are accepted.

15. The method of any of claims 10-14, wherein the first response indicates that a parameter associated with video encoding or video decoding has been adjusted, that a tool associated with video encoding or video decoding has been disabled, that an image resolution associated with a video has been adjusted, or that a bitrate associated with the video has been adjusted.

16. The method of any of claims 10-15, further comprising sending a second request to the video encoding device to cancel the first request at least partially.

17. The method of claim 16, further comprising receiving a second response that indicates that the first request has been cancelled at least partially.

18. The method of claim 17, wherein the second response indicates that all previous requests associated with energy saving sent by the video decoding device have been cancelled.

19. A video encoding device, comprising: a processor configured to: receive, from a video decoding device, a first request that indicates one or more operational changes associated with energy saving; determine whether or to what extent to implement the one or more operational changes indicated by the first request; and send a first response to the video decoding device, wherein the first response indicates whether or to what extent the video encoding device has decided to implement the one or more operational changes.

20. The video encoding device of claim 19, wherein the processor being configured to determine whether or to what extent to implement the one or more operational changes indicated by the first request comprises the processor being configured to determine whether to adjust a parameter associated with video encoding or video decoding, whether to disable a tool associated with video encoding or video decoding, whether to adjust an image resolution associated with a video, or whether to adjust a bitrate associated with the video.

21. The video encoding device of claim 19 or 20, wherein the processor is further configured to receive a second request from the video decoding device, the second request indicating a modification of the first request or a cancellation of the first request.

22. The video encoding device of any of claims 19-21, wherein the first response indicates that the video encoding device is to implement only a subset of the operational changes indicated by the first request.

23. A method implemented by a video encoding device, the method comprising: receiving, from a video decoding device, a first request that indicates one or more operational changes associated with energy saving; determining whether or to what extent to implement the one or more operational changes indicated by the first request; and sending a first response to the video decoding device, wherein the first response indicates whether or to what extent the video encoding device has decided to implement the one or more operational changes.

24. The method of claim 23, wherein determining whether or to what extent to implement the one or more operational changes indicated by the first request comprises determining whether to adjust a parameter associated with video encoding or video decoding, whether to disable a tool associated with video encoding or video decoding, whether to adjust an image resolution associated with a video, or whether to adjust a bitrate associated with the video.

25. The method of claim 23 or 24, further comprising receiving a second request from the video decoding device, wherein the second request indicates a modification of the first request or a cancellation of the first request.

26. The method of any of claims 23-25, wherein the first response indicates that the video encoding device is to implement only a subset of the operational changes indicated by the first request.

27. A computer program product stored on a non-transitory computer readable medium and comprising program code instructions for implementing the steps of a method according to any one of claims 10-18 or claims 23-26 when executed by a processor.

28. Data comprising information representative of the first request sent by the video decoding device of claims 1 -9 or the first response sent by the video encoding device of claims 19-22.

Images