WO2025019271A1 - Dash signaling for adaptive streaming of haptics media - Google Patents

Abstract

Some embodiments of a method may include encoding information describing a haptics experience, wherein the information describing the haptics experience includes one or more adaptation sets, wherein each of the one or more adaptation sets includes one or more representations corresponding to a haptics media track. Some embodiments of a method may include decoding information describing a haptics experience, wherein the information describing the haptics experience includes one or more adaptation sets, wherein each of the one or more adaptation sets includes one or more representations corresponding to a haptics media track.

Description

DASH SIGNALING FOR ADAPTIVE STREAMING OF HAPTICS MEDIA

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims benefit of U.S. Patent Application No. 63/526,954, entitled “DASH SIGNALING FOR ADAPTIVE STREAMING OF HAPTICS MEDIA” and filed July 14, 2023, which is hereby incorporated by reference in its entirety.

INCORPORATION BY REFERENCE

[0002] The present application incorporates by reference in its entirety the following application: U.S. Provisional Patent Application Serial No. 63/417,638, entitled “Carriage of Coded Haptics Data in Media Containers" and filed Oct. 19, 2022 (‘“638 application”).

BACKGROUND

[0003] A haptic sequence is a set of data encoded for a rendering based on the sense of touch and positioning in space, like a video sequence is a set of encoded data for a rendering using the sense of vision. A haptic sequence encodes temporal data, for example represented as tracks associated with haptic devices. Haptic devices may render different modalities of the sense of touch and positioning in space, like vibration, force, position, velocity, or temperature.

SUMMARY

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

[0005] An example method in accordance with some embodiments may include: encoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track. [0006] For some embodiments of the example method, each of the one or more representations corresponds to the same time period.

[0007] For some embodiments of the example method, encoding of the information encodes the information in a container file.

[0008] For some embodiments of the example method, the one or more adaptation sets may include a main haptics experience and a second haptic experience, wherein the second haptic experience corresponds to a first perception modality and a first channel.

[0009] For some embodiments of the example method, the adaptation set corresponding to the main haptics experience may include initialization data corresponding to a haptics decoder.

[0010] For some embodiments of the example method, the adaptation set corresponding to the second haptics experience may include one or more fragments of a corresponding haptic track.

[0011] For some embodiments of the example method, the adaptation set corresponding to the second haptics experience may include information identifying the one or more fragments of the corresponding haptic track.

[0012] For some embodiments of the example method, the first channel corresponds to a first frequency band.

[0013] For some embodiments of the example method, the information describing the haptics experience may further include information identifying the one or more adaptation sets.

[0014] For some embodiments of the example method, the information describing the haptics experience may further include: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, wherein the configuration information may include information describing one or more parallel haptics experience tracks.

[0015] For some embodiments of the example method, the information may further include information describing one or more haptics experience tracks, and the information describing the haptics experience track may further include: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

[0016] An example method/apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: encode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0017] An additional example method in accordance with some embodiments may include: decoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0018] For some embodiments of the additional example method, each of the one or more representations corresponds to the same time period.

[0019] For some embodiments of the additional example method, encoding of the information encodes the information in a container file.

[0020] For some embodiments of the additional example method, the one or more adaptation sets may include a main haptics experience and a second haptic experience, and the second haptic experience corresponds to a first perception modality and a first channel.

[0021] For some embodiments of the additional example method, the adaptation set corresponding to the main haptics experience may include initialization data corresponding to a haptics decoder.

[0022] For some embodiments of the additional example method, the adaptation set corresponding to the second haptics experience may include one or more fragments of a corresponding haptic track.

[0023] For some embodiments of the additional example method, the adaptation set corresponding to the second haptics experience may include information identifying the one or more fragments of the corresponding haptic track.

[0024] Some embodiments of the additional example method may further include concatenating the initialization data with, from one or more adaptation sets, the information identifying the one or more fragments to generate a bitstream.

[0025] Some embodiments of the additional example method may further include rendering the bitstream in a haptic experience environment.

[0026] For some embodiments of the additional example method, the first channel corresponds to a first frequency band. [0027] For some embodiments of the additional example method, the information describing the haptics experience may further include information identifying the one or more adaptation sets.

[0028] For some embodiments of the additional example method, the information describing the haptics experience may further include: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, and the configuration information may include information describing one or more parallel haptics experience tracks.

[0029] For some embodiments of the additional example method, the information may further include information describing one or more haptics experience tracks, and the information describing the haptics experience track may further include: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

[0030] For some embodiments of an example method, the information describing the haptics experience, and/or the encoded information describing the haptics experience, or is encoded in accordance with, the ISO Base Media File Format (ISOBMFF).

[0031] For some embodiments of an example method, the information describing the haptics experience and/or the encoded information describing the haptics experience, is included in and streamed in a media file such as an MPEG-DASH (MPEG Dynamic Adaptive Streaming Over HTTP) media presentation descriptor (MPD) file.

[0032] For some embodiments of an example method, the information describing the haptics experience, and/or the encoded information describing the haptics experience, uses, is part of, and/or is compliant with, one or more of the MPEG standards ISO/IEC 23090-32 and ISO/IEC 23090-31.

[0033] An example method/apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: decode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0034] An example apparatus in accordance with some embodiments may include at least one processor configured to perform any one of the methods listed above. [0035] An example apparatus in accordance with some embodiments may include a computer-readable medium storing instructions for causing one or more processors to perform any one of the methods listed above.

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

[0037] An example apparatus in accordance with some embodiments may include a computer-readable medium storing encoded information scene description file generated according to any one of the methods listed above.

[0038] An example signal in accordance with some embodiments may include a scene description file generated according to any one of the methods listed above.

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

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0042] 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. 1 A according to some embodiments. [0043] FIG. 1 C is a system diagram illustrating an example set of interfaces for a system according to some embodiments.

[0044] FIG. 2 is a system diagram illustrating an example set of interfaces for an MPEG-I node hierarchy supporting elements of scene interactivity according to some embodiments.

[0045] FIG. 3 is a system diagram illustrating an example set of interfaces for an MPEG haptic architecture according to some embodiments.

[0046] FIG. 4 is a system diagram illustrating example hierarchical data structure for two codec formats according to some embodiments.

[0047] FIG. 5 is a schematic illustration showing an example NAL unit structure in a haptics bitstream according to some embodiments.

[0048] FIG. 6 is a schematic illustration showing example NAL unit payload types according to some embodiments.

[0049] FIG. 7 is a code listing illustrating an example EditListBox class structure according to some embodiments.

[0050] FIG. 8 is schematic illustration showing an example MPD hierarchical data model according to some embodiments.

[0051] FIG. 9 is a system diagram illustrating an example DASH configuration for grouping adaptation sets according to some embodiments.

[0052] FIG. 10 is a code listing illustrating an example XML schema according to some embodiments. FIG. 9 shows example data types for various elements and attributes for an XML schema.

[0053] FIG. 11 is a code listing illustrating an example XML schema according to some embodiments.

[0054] FIG. 12 is a flowchart illustrating an example process for encoding haptic data according to some embodiments.

[0055] FIG. 13 is a flowchart illustrating an example process for decoding haptic data according to some embodiments.

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

DETAILED DESCRIPTION

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

[0058] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104, a ON 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and/or a “ST A”, 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.

[0059] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, 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.

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

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

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

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

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

[0065] 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 sentto/from multiple types of base stations (e.g. , a eNB and a gNB).

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

[0067] 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. 1 A, 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.

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

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

[0070] 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 cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0071] FIG. 1B 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.

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

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

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

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

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

[0078] 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 location-determination method while remaining consistent with an embodiment.

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

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

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

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

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

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

[0086] The embodiments described herein are not limited to being implemented on a WTRU. Such embodiments may be implemented using other systems, such as the system of FIG. 1 C.

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

[0088] The system 140 includes at least one processor 142 configured to execute instructions loaded therein for implementing, for example, the various aspects described in this document. Processor 142 may include embedded memory, input output interface, and various other circuitries as known in the art. The system 140 includes at least one memory 144 (e.g., a volatile memory device, and/or a non-volatile memory device). System 140 may include a storage device 148, 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 148 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.

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

[0090] Program code to be loaded onto processor 142 or encoder/decoder 146 to perform the various aspects described in this document can be stored in storage device 148 and subsequently loaded onto memory 144 for execution by processor 142. In accordance with various embodiments, one or more of processor 142, memory 144, storage device 148, and encoder/decoder module 146 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.

[0091] In some embodiments, memory inside of the processor 142 and/or the encoder/decoder module 146 is used to store instructions and to provide working memory for processing that is needed during encoding or decoding. In other embodiments, however, a memory external to the processing device (for example, the processing device can be either the processor 142 or the encoder/decoder module 142) is used for one or more of these functions. The external memory can be the memory 144 and/or the storage device 148, for example, a dynamic volatile memory and/or a non-volatile flash memory. In several embodiments, an external non-volatile flash memory is used to store the operating system of, for example, a television. In at least one embodiment, a fast external dynamic volatile memory such as a RAM is used as working memory for video coding and decoding operations, such as for MPEG-2 (MPEG refers to the Moving Picture Experts Group, MPEG-2 is also referred to as ISO/IEC 13818, and 13818-1 is also known as H.222, and 13818-2 is also known as H.262), HEVC (HEVC refers to High Efficiency Video Coding, also known as H.265 and MPEG-H Part 2), or WC (Versatile Video Coding, a new standard being developed by JVET, the Joint Video Experts Team). [0092] The input to the elements of system 140 can be provided through various input devices as indicated in block 162. 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. 1A, include composite video.

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

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

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

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

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

[0098] The system 140 can provide an output signal to various output devices, including a display 166, speakers 168, and other peripheral devices 170. The display 166 of various embodiments includes one or more of, for example, a touchscreen display, an organic light-emitting diode (OLED) display, a curved display, and/or a foldable display. The display 166 can be for a television, a tablet, a laptop, a cell phone (mobile phone), or other device. The display 166 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 170 include, in various examples of embodiments, one or more of a stand-alone digital video disc (or digital versatile disc) (DVR, for both terms), a disk player, a stereo system, and/or a lighting system. Various embodiments use one or more peripheral devices 170 that provide a function based on the output of the system 140. For example, a disk player performs the function of playing the output of the system 140.

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

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

[0101] The system 140 may include one or more sensor devices 160. Examples of sensor devices that may be used include one or more GPS sensors, gyroscopic sensors, accelerometers, light sensors, cameras, depth cameras, microphones, and/or magnetometers. Such sensors may be used to determine information such as user’s position and orientation. Where the system 140 is used as the control module for an extended reality display (such as control modules), the user’s position and orientation may be used in determining how to render image data such that the user perceives the correct portion of a virtual object or virtual scene from the correct point of view. In the case of head-mounted display devices, the position and orientation of the device itself may be used to determine the position and orientation of the user for the purpose of rendering virtual content. In the case of other display devices, such as a phone, a tablet, a computer monitor, or a television, other inputs may be used to determine the position and orientation of the user for the purpose of rendering content. For example, a user may select and/or adjust a desired viewpoint and/or viewing direction with the use of a touch screen, keypad or keyboard, trackball, joystick, or other input. Where the display device has sensors such as accelerometers and/or gyroscopes, the viewpoint and orientation used for the purpose of rendering content may be selected and/or adjusted based on motion of the display device. [0102] The embodiments can be carried out by computer software implemented by the processor 142 or by hardware, or by a combination of hardware and software. As a non-limiting example, the embodiments can be implemented by one or more integrated circuits. The memory 144 can be of any type appropriate to the technical environment and can be implemented using any appropriate data storage technology, such as optical memory devices, magnetic memory devices, semiconductor-based memory devices, fixed memory, and removable memory, as non-limiting examples. The processor 142 can be of any type appropriate to the technical environment, and can encompass one or more of microprocessors, general purpose computers, special purpose computers, and processors based on a multi-core architecture, as non-limiting examples.

Runtime Interactivity

[0103] FIG. 2 is a system diagram illustrating an example set of interfaces for an MPEG-I node hierarchy 200 supporting elements of scene interactivity according to some embodiments. According to the present principles, in addition to a node tree as described in relation to FIG. 3, behavior metadata items (herein called ‘behaviors’) are added to the scene description. In example embodiments, the time-evolving scene description is augmented by adding information identifying behaviors. These behaviors may be related to pre-defined virtual objects on which runtime interactivity is allowed for user specific XR experiences.

[0104] In some embodiments, these behaviors are time-evolving. In such embodiments, the behaviors may be updated through the already-existing scene description update mechanism.

[0105] In example embodiments, a behavior is characterized by one or more of the following properties:

• One or more triggers defining the conditions to be met for activation.

• A trigger control parameter defining the logical operations between the defined triggers.

• Actions to be implemented in response to the activation of the triggers.

• An action control parameter defining the order of execution of the defined actions.

• A priority number enabling the selection of the behavior of highest priority in the case of concurrence of several behaviors on the same virtual object at the same time.

• An optional interrupt action to specify how to terminate this behavior when the behavior is no longer defined in a newly received scene update. For instance, a behavior is no longer defined if the related object has been removed or if the behavior is no longer relevant for this current media (e.g. audio or video) sequence. [0106] With the addition of these behaviors, time-dependent user interactivity in immersive content for XR experiences may be defined.

[0107] When a second scene description is received, some of the behaviors of the first scene description may be “on-going”, that is they are triggered, and their actions are running. The second scene description may be provided as update metadata, that is metadata describing the differences between the first scene description and the second description. The second scene description includes a node tree describing objects that may be common or different than objects of the first scene descriptions. Objects of the node tree of the first scene description may be no longer present in the second description. If the objects related to the running actions of the on-going behaviors are missing in the second scene description, then, these on-going behaviors are no longer appliable. The same way, if an on-going behavior is not defined in the second description, the on-going behavior is no longer appliable. The interrupt action field describes how to correctly interrupt the running actions on the on-going behavior.

Encoding Haptics Data

[0108] FIG. 3 is a system diagram illustrating an example set of interfaces for an MPEG haptic architecture according to some embodiments. FIG. 3 shows an example haptics codec architecture 300. A new standard, WG07N00624, TextofISO/IEC DIS 23090-31 MPEG Haptics Coding Phase 1, MPEG 142 (April 2023) (“ISO/IEC 23090-31”), is currently under development by the Motion Picture Experts Group (MPEG). FIG. 3 illustrates the MPEG haptics codec architecture 300. See ISO/IEC 23090-31.

[0109] In this architecture 300, the coded representation of haptics data may be in one of two formats: an interchange format (. hjif) 302 or distribution format (.hmpg) 304. The interchange format is a JSON-based human readable description of the haptics data while the distribution format is a compressed binary representation of the data. The two formats have complementary purposes and a lossless or lossy one to one conversion may be performed to go between them. An example of this conversion is shown near the center of FIG. 3 and the “interchange format” terms.

[0110] A compressed binary bitstream in the distribution format is structured into a sequence of network abstraction layer (NAL) units referred to as "packets" to ease encapsulation by any network protocol or file format. This operation is shown with the binary compression box 306 and binary decompression box 308 and the intervening boxes. [0111] A haptics decoder 310 takes as input a binary “.hmpg” file or an “.hjif” file and outputs an “.hjif” file. Haptic data contained in the resulting “.hjif’ file may be rendered, for example, directly on haptic devices or using an intermediate synthesizer 312 generating pulse code modulation (PCM) data as shown on the right side of FIG. 3.

[0112] FIG. 4 is a system diagram illustrating example hierarchical data structure for two codec formats according to some embodiments. FIG. 4 shows an example haptics data hierarchy 400. The data structure of two haptic codec formats follows the hierarchical organization illustrated in FIG. 4.

[0113] The highest level of the structure describes the entire haptic experience defined in the file or stream. This highest level contains some high-level metadata information 402 and provides a list of avatars 404 and/or body representations that may be referenced to specify a desired location of haptic stimuli on the body. The haptic data itself is described through a list of perceptions 406. These perceptions 406 correspond to haptic signals associated with specific perception modalities (e.g., vibration, force, position, velocity, and temperature).

[0114] In addition to perception-specific metadata 408, a perception may include a list of channels (or tracks 410) in which the data is decomposed into frequency bands. Each band 412 defines part of the signal in a given frequency range. The bands 412 are described with a list of haptic effects 414, each including a list of keyframes 416. The haptic signal in a channel may be reconstructed by combining the data in the different bands (e.g., by adding high and low frequency bands).

[0115] FIG. 5 is a schematic illustration showing an example NAL unit structure in a haptics bitstream according to some embodiments. A NAL unit (NALu) structure 500 includes a header and a payload. The NALu header 502 is 32 bits that includes 4 bits for a nal_unit_type field, 2 bits for a level field, 10 bits reserved for future use, and 16 bits for a payload byte length value. The nal_unit_type field may indicate a Metadata Expe type (including nb perception, phase 1, 2a, or 2b, or avatar); a Metadata Perception type (including nb Track, type, library, or device); a Metadata Track type (including nb band), or a DataBand type (including a header band). The level field is the level of the band in which 0 is the baseline. The Metadata NALu Payload 504 is n bits of metadata, in which n is a variable amount. The DataBand NALu Payload 506 is a variable length field with a header of n*8 bits and n sets of sub-fields FX1 to FXn that are each n bits wide.

[0116] FIG. 6 is a schematic illustration showing example NAL unit payload types according to some embodiments. FIG. 6 shows an example structure 600 of how the NALu Header 602 and NALu Payload 604 structure may be implemented for several NAL unit types. The left side of FIG. 6 shows the 16-bit NALu header 602 with 4 bits indicating the NAL type, 2 bits indicating the level and 10 bits reserved for future use. An NAL type of bOOOO is shown as corresponding to Metadata Haptic Experience data 606. An NAL type of b0001 is shown as corresponding to Metadata Haptic Perception data 608. An NAL type of b0010 is shown as corresponding to Metadata Haptic Track data 610. An NAL type of b0011 is shown as corresponding to Metadata Haptic Band data 612. An NAL type of b0100 is shown as corresponding to Library of Effects data 614. An NAL type of b0101 is shown as corresponding to Databand data 616. An NAL type of b1100 is shown as corresponding to a Cyclic Redundancy Code (CRC) 618. An NAL type of b1101 is shown as corresponding to byte stuffing 620.

ISO Base Media File Format

[0117] FIG. 7 is a code listing illustrating an example EditListBox class structure according to some embodiments. FIG. 7 shows an example code listing 700. Within the ISO/IEC 14496 (MPEG-4) standard there are several parts that define file formats for the storage of time-based media. According to ISO/IEC 14496-12, Coding of Audio-Visual Objects, Part 12: ISO Base Media File Format, 2020 ‘ISO/IEC 14496-12"), these parts are all based on and derived from the ISO Base Media File Format (ISOBMFF), which is a structural, mediaindependent definition. ISOBMFF contains structural and media data information mainly for timed presentations of media data such as audio, video, etc. There is also support for un-timed data, such as meta-data at different levels within the file structure. The logical structure of the file is of a movie that in turn contains a set of timeparallel tracks. The time structure of the file is such that the tracks contain sequences of samples in time, and those sequences are mapped into the timeline of the overall movie. ISOBMFF is based on the concept of box- structured files. A box-structured file has a series of boxes (sometimes called atoms), which have a size and a type. The types are 32-bit values and usually chosen to be four printable characters, also known a four-character code (4CC). Un-timed data may be contained in a metadata box, at the file level, or attached to the movie box or one of the streams of timed data, called tracks, within the movie.

[0118] Among the top-level boxes within an ISOBMFF container is the Mo vi eBox (“moo v”), which contains metadata for the continuous media streams present in the file. These metadata are signaled within the hierarchy of boxes in the Movie box, e.g., within the Trac kBox (“trak“). A track represents a continuous media stream that is present in the file. The media stream itself is a sequence of samples, such as audio or video access units of an elementary media stream, and are enclosed within a Medi aDat aBox ( mdat“) that is present at the top-level of the container. The metadata for each track includes a list of sample description entries, each providing the coding or encapsulation format used in the track and the initialization data for processing that format. Each sample is associated with one of the sample description entries of the track. ISO/IEC 14496-12 provides a tool for defining an explicit timeline map for each track. This is known as an edit list and is signalled using an Edi tL i s tBox with the syntax shown in FIG. 7. Each entry defines part of the track time-line: by mapping part of the composition timeline, or by indicating “empty” time (portions of the presentation timeline that map to no media, an “empty” edit).

[0119] FIG. 7 shows an example class structure for such an EditListBox extension of a FullBox class. For the example in FIG. 7, a sequence of samples, which are numbered 1 to the value of entry_count, form a media stream. FIG. 7 shows support for “version 0” and “version 1”. Version 0 uses 32-bit integers for the sample’s duration (variable edit_duration) and time within the media stream (variable media_time), while version 1 uses 64-bit integer fields. Each sample also has media_rate_integer and media_rate_fraction values that correspond to a sampling rate for the sample.

Carriage of Haptics Data

[0120] MPEG is currently working on developing a new standard, WG03N00686, Text of ISO/IEC CD 23090- 32 Carriage of Haptics Data, MPEG 142, April 2023 (ISO/IEC 23090-32) that defines how haptics bitstreams generated by the ISO/IEC 23090-31 codec may be encapsulated in ISOBMFF media containers. The current version of ISO/IEC CD 23090-32 describes how to carry haptics data in a single track in the file.

[0121] The ‘638 application describes a more flexible and scalable design for carrying the haptics data using a multi-track approach. In the multi-track mode, a haptics experience is carried in multiple ISOBMFF tracks with one track being the main track for the experience and carrying general information that applies to the entire experience. The main track may be associated, through track references in the ISOBMFF file, with one or more haptics tracks that carry haptics band data units for one or more haptic channels. The samples of this track may carry either data for only one band of a perception channel or all the bands of a perception channel. If all the bands are carried in the samples of the Haptics Track, each sample may be composed of sub-samples, in which each sub-sample contains data for one of the bands.

[0122] While the bitstream format being developed in ISO/IEC 23090-31 enables describing a haptics experience in compact representation, that may be easily consumed by a haptics decoder, there is currently no well-defined or standardized method for streaming such coded haptics content. A method to store ISO/IEC 23090-31 coded haptics bitstream in ISOBMFF containers by demultiplexing the data belonging to different haptics channels into separate tracks in the file was presented in m61136, [Haptics] On Carriage of Haptics Data in ISOBMFF, MPEG 140, October 2022. While this design allows scalable access to the different haptics stream components in a local playback scenario, such as when all the data are stored and accessed locally, such a structure may not be directly usable for enabling remote access and adaptive streaming of haptics content stored on a remote server over the network.

[0123] This application presents methods for supporting adaptive streaming of haptics bitstreams generated by ISO/IEC 23090-31 and packaged in ISOBMFF containers as multiple tracks. This application describes, for some embodiments, methods and systems that enable flexible and scalable streaming of haptics media, which may be coded using the ISO/IEC 23090-31 codec developed by ISO/IEC SC29/WG03 (MPEG Systems).

[0124] For some embodiments, the ideas presented in this application may be applied to immersive media coding, encoding, storage, and streaming of coded haptics media content and decoding of haptics media data on devices or any services providing an immersive media experience.

Dynamic Streaming over HTTP (DASH)

[0125] MPEG Dynamic Adaptive Streaming over HTTP (MPEG-DASH) is a universal delivery format that provides end users with the best possible video experience by dynamically adapting to changing network conditions. Dynamic HTTP streaming requires various bitrate alternatives of the multimedia content to be available at the server. In addition, the multimedia content may consist of several media components (e.g., audio, video, text), each of which may have different characteristics. In MPEG-DASH, these characteristics are described by Media Presentation Description (MPD).

[0126] FIG. 8 is schematic illustration showing an example MPD hierarchical data model according to some embodiments. The example hierarchical data model 800 includes a series of hierarchical boxes. The MPD 802 describes the sequence of Periods 804, where a consistent set of encoded versions of the media content components does not change during a Period. Each Period has a starting time and duration and is composed of one or multiple adaptation sets (AdaptationSet).

[0127] An Adaptation Set 806 represents a set of encoded versions of one or several media content components sharing the identical properties such as the language, the media type, the picture aspect ratio, the role, the accessibility, and the rating property. For instance, an AdaptationSet may contain different bitrates of the video component of the same multimedia content. Another AdaptationSet may contain different bitrates of the audio component (e.g. lower quality stereo and higher quality surround sound) of the same multimedia content. Each AdaptationSet usually includes multiple Representations.

[0128] A Representation 808 describes a deliverable encoded version of one or several media components, varying from other representations by bitrate, resolution, number of channels or other characteristics. Each Representation consists of one or multiple segments. The attributes of Representation element such as @id, ©bandwidth, ©qualityRanking, and @dependencyld are used to specify the properties of the associated Representation. Representations may also include Sub-Representations, which is part of the Representation, to describe and extract partial information from a Representation. Sub-Representations may provide the ability for accessing a lower quality version of the Representation in which they are contained.

[0129] A Segment 810 is the largest unit of data that can be retrieved with a single HTTP request. Each segment has a URL, i.e. an addressable location on a server, which can be downloaded using HTTP GET or HTTP GET with byte ranges.

[0130] To use this data model, the DASH client parses the MPD XML document, selects a collection of AdaptationSets suitable for its environment based on information provided in each of the AdaptationSet elements. Within each AdaptationSet, the client selects one Representation, typically based on the value of ©bandwidth attribute, but also taking into account client decoding and rendering capabilities. The client downloads the initialization segment of the selected Representations and then accesses the content by requesting entire Segments or byte ranges of Segments. Once the presentation has started, the client continues consuming the media content by continuously requesting Media Segments or parts of Media Segments and playing content according to the media presentation timeline. The client may switch Representations taking into account updated information from its environment. The client should play the content continuously across Periods. Once the client is consuming media contained in the Segments towards the end of the announced media in the Representation, then the Media Presentation is terminated, a new Period is started, or the MPD may be re-fetched.

Descriptors in DASH

[0131] MPEG-DASH introduces the concept of descriptors to provide application-specific information about the media content. Descriptor elements are all structured in the same way, namely they contain a ©schemeldUri attribute that provides a URI to identify the scheme and an optional attribute ©value and an optional attribute @id. The semantics of the element are specific to the scheme employed. The URI identifying the scheme may be a URN or a URL. The MPD does not provide any specific information on how to use these elements. It is up to the application that employs DASH formats to instantiate the description elements with appropriate scheme information. DASH applications that use one of these elements must first define a Scheme Identifier in the form of a URI and must then define the value space for the element when that Scheme Identifier is used. If structured data is required, then any extension element or attribute may be defined in a separate namespace. Descriptors may appear at a number of levels within the MPD:

• The presence of an element at MPD level means that the element is a child of the MPD element.

• The presence of an element at adaptation set level refers to that the element is a child element of an AdaptationSet element.

• The presence of an element at representation level refers to that the element is a child element of a Representation element.

Preselections

[0132] In MPEG-DASH, a bundle is a set of media components which may be consumed jointly by a single decoder instance. Each bundle includes a main media component that contains the decoder specific information and bootstraps the decoder. A PreSelection defines a subset of media component in a bundle that are expected to be consumed jointly.

[0133] The AdaptationSet that contains the main media component is referred to as main AdaptationSet. The main media component is always included in any PreSelection that is associated to a bundle. In addition, each bundle may include one or multiple partial AdaptationSets. Partial AdaptationSets may only be processed in combination with the main AdaptationSet.

[0134] PreSelections may be defined through the PreSelection element as defined in Table 1. The selection of PreSelections is based on the contained attributes and elements in the PreSelection element. For Table 1 , attributes that are designated as mandatory are listed with a Use value of “M”, while attributes that are designated as optional are listed with a Use value of “0”. An entry of “OD” means that the attribute is optional with a default value listed. For elements, the Use value lists the minimum number of occurrences to the maximum number of occurrences. An entry of “N” means that the number of occurrences is unbounded. Elements are shown first in bold, while attributes precede in non-bold and begin with an

symbol.

Adaptation Sets for Haptics Media

[0135] FIG. 9 is a system diagram illustrating an example DASH configuration for grouping adaptation sets according to some embodiments. FIG. 9 illustrates an example of a DASH configuration 900 for grouping Adaptation Sets 904, 906, 908, 910 belonging to the same haptics experience 902 within an MPEG-DASH MPD file.

[0136] To signal the presence of a multi-track haptics media in the DASH media presentation descriptor (MPD), each track of the media, including the main track, may be represented by an Adaptationset element in the MPD. The main (haptics experience) track's adaptation set 904 is referred to as the Haptics Experience Adaptation Set and the adaptation sets 906, 908, 910 for the associated haptics tracks are referred to as Haptics Adaptation Sets.

[0137] A 4CC is a 4-character code that is used to identify the type of sample entry of a track in ISOBMFF, which in turn is based on the type of codec (e.g., ‘hev1 ’ is the 4CC for an HEVC codec with a certain configuration). The track is represented by an Adaptation Set in the DASH MPD. Usually the ©codecs attribute is set to the corresponding 4CC of the associated track. For some embodiments, the same 4CC may be used for both the Haptics Experience AS and the Haptics Data AS because they are using the same haptics codec.

[0138] For some embodiments, perceptions are part of the same haptics experience. A haptics experience incorporates a number of perceptions and each perceptions has a number of channels and each channel has a number or bands. The Haptics Data Adaptation Set represents a track that carries band data for one or more channels of a certain perception in the haptics experience.

[0139] The Haptics Experience Adaptation Set has the Codecs attribute set to “mihl”, while the @ codecs attribute is set to “mihb” for each of the Haptics Adaptation Sets (or the Representations of these Adaptation Sets) if the ^codecs attribute is not present in the Adaptationset element. The Gmime T ype attribute for all Adaptation Sets of a haptics experience is set to "hapt i c /mp 4", which is the registered MIME type for haptics media.

[0140] The Haptics Experience Adaptation Set contains a single Initialization Segment at the adaptation set level. The Initialization Segment shall contain all MPEG-I Haptic Stream (MIHS) units (packets) needed to initialize the haptics decoder. Media Segments for the Representations of a Haptics Adaptation Set contains one or more track fragments of the corresponding haptic track at the file format level. By concatenating the Initialization Segment with Media Segments from one or more Haptics Adaptation Sets, the resulting file contains a bitstream that is decodable by the haptics decoder.

[0141] Representations of the Haptics Adaptation Sets of a Haptics Experience Preselection shall have a @ dependencyi d attribute set to the id of a Representation in the corresponding Haptics Experience Adaptation Set.

[0142] If a Haptics Adaptation Set contains more than one Representation, the @b i t s t re amswi t ching attribute is present in the Adaptationset element of the Haptics Adaptation Set and set to “t rue” to indicate to the player support for seamless switching between the Representations in the Adaptation Set. Moreover, the duration of the Media Segments in each Representation must be identical. [0143] For example, if the segments are not identical, then if the player switches to a different representation, the player has to figure out where in the new media segment retrieved from the other representation the player should continue playback. The player also needs to calculate which segment the player needs from the last timestamp of the last segment the player played from the first representation. So, switching would not be seamless in this case. The segment indices would not be aligned in time. Thus, in accordance with some embodiments, the duration of the Media Segments in each Representation must be identical.

Haptics Experience Preselection

[0144] A Haptics Experience Preselection may be signaled in the MPD using either a Preselection element within a Period element or a Preselection descriptor at the Adaptation Set level. A Haptics Experience Preselection element is signaled as defined in ISO/IEC 23009-1 with the @pre s e i e ct i onComponent s attribute, whose assigned value is an id list including the id of the Haptics Experience Adaptation Set followed by the ids of the associated Haptics Adaptation Sets. The @ code c s attribute for the Preselection is set to “mihl", indicating that the media represented by the Preselection is coded haptics media.

[0145] For some embodiments, an adaptation set may include information identifying one or more fragments of a corresponding haptic track.

Haptics Experience Descriptor

[0146] Table 2 lists elements and attributes of a haptics descriptor, which may be contained in a separate file. For Table 2, attributes that are designated as mandatory are listed with a Use value of “M”, while attributes that are designated as optional are listed with a Use value of “O”. For elements, the Use value lists the minimum number of occurrences to the maximum number of occurrences. An entry of “N” means that the number of occurrences is unbounded. Elements are shown first in bold, while attributes precede in non-bold and begin with symbol.

[0147] To signal different perceptions in a haptics experience, a HapticsExperience descriptor is created for the Haptics Experience Adaptation Set. For some embodiments, the HapticsExperience descriptor is an EssentialProperty descriptor with the @ s cheme i dUr i attribute set to a unique Uniform Resource Identifier (URI) (e.g., "urn : mpe g : mpe g l : hapt i c s : 2 02 3 : percept ion"). The @va lue attribute Of the HapticsExperience descriptor shall not be present. The HapticsExperience descriptor includes elements and attributes that describe the haptics experience and associated perceptions. The Haptics descriptor includes at least one or more hapticsPerception elements, each including an @ id attribute set to the unique identifier of the perception in the haptics bitstream and a @type attribute to signal its modality.

Table 2

[0148] FIG. 10 is a code listing illustrating an example XML schema according to some embodiments. FIG. 10 shows an example code listing 1000 with example data types for various elements and attributes for an XML schema. For the example shown in FIG. 10, the 6^th line of the code listing sets the element name to “hapticsPerception” and the data type to “haptics: HapticsPerceptionType”. The 8^th line of the code listing sets the name, type, and use for the @id attribute. The 9^th line of the code listing sets the name, type, and use for the @type attribute.

[0149] For some embodiments, the HapticsExperiece descriptor is a SupplementalProperty descriptor with the S s cheme i dUri attribute set to a unique URI (e.g., "urn : mpeg : mpeg I : hapt i cs : 2 023 : percept ion").

Haptics Channel Descriptor

[0150] Table 3 lists elements and attributes of a haptics descriptor, which may be contained in a separate file. For Table 3, attributes that are designated as mandatory are listed with a Use value of “M”, while attributes that are designated as optional are listed with a Use value of “0”. For elements, the Use value lists the minimum number of occurrences to the maximum number of occurrences. An entry of “N” means that the number of occurrences is unbounded. Elements are shown first in bold, while attributes precede in non-bold and begin with symbol.

[0151] To identify the haptics channels present in a Haptics Adaptation Set, a Haptics descriptor is used. For some embodiments, the Haptics descriptor is an EssentialProperty descriptor with the @ s cheme i dur i set to a unique URI (e.g., "urn : mpe g : mpe g I : hapt i c s : 2 02 3 : channe l"). At the Adaptation Set level, a Haptics descriptor is signaled for each haptics channel that is present in the Representations of the Haptics Adaptation Set. Again, the @va lue attribute of the Haptics descriptor shall not be present. The Haptics descriptor is associated with a Haptics Data Adaptation Set and provides information on the channel(s) and band(s) carried in that Adaptation Set. A HapticsExperience descriptor provides higher-level metadata about the haptics experience itself. In this case, the list of available perceptions in the experience. In the Haptics descriptor the hapticChannel element refers to one of those perceptions.

Table 3

[0152] FIG. 11 is a code listing illustrating an example XML schema according to some embodiments. FIG. 11 shows an example code listing 1100. The data types for various elements and attributes are defined in an XML schema for the example shown in FIG. 10. For the example shown in FIG. 11 , the 6^th line of the code listing sets the element name to “hapticsChannel” and the data type to “haptics: HapticsChannelType”. The 8^th line of the code listing sets the name, type, and use for the @id attribute. The 9^th line of the code listing sets the name, type, and use for the ©perception^ attribute. The 10^th line of the code listing sets the name, type, and use for the @band_ids attribute.

[0153] FIG. 12 is a flowchart illustrating an example process for encoding haptic data according to some embodiments. For some embodiments, an example process 1200 may include encoding 1202 information describing a haptics experience. For some embodiments of the example process 1200, the information describing 1204 the haptics experience includes one or more adaptation sets. For some embodiments of the example process 1200, each of the one or more adaptation sets includes 1206 one or more representations corresponding to a haptics media track.

[0154] FIG. 13 is a flowchart illustrating an example process for decoding haptic data according to some embodiments. For some embodiments, an example process 1300 may include decoding 1302 information describing a haptics experience. For some embodiments of the example process 1300, the information describing 1304 the haptics experience includes one or more adaptation sets. For some embodiments of the example process 1300, each of the one or more adaptation sets includes 1306 one or more representations corresponding to a haptics media track.

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

[0156] An example method in accordance with some embodiments may include: encoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0157] For some embodiments of the example method, each of the one or more representations corresponds to the same time period.

[0158] For some embodiments of the example method, encoding of the information encodes the information in a container file.

[0159] For some embodiments of the example method, the one or more adaptation sets may include a main haptics experience and a second haptic experience, wherein the second haptic experience corresponds to a first perception modality and a first channel.

[0160] For some embodiments of the example method, the adaptation set corresponding to the main haptics experience may include initialization data corresponding to a haptics decoder.

[0161] For some embodiments of the example method, the adaptation set corresponding to the second haptics experience may include one or more fragments of a corresponding haptic track.

[0162] For some embodiments of the example method, the adaptation set corresponding to the second haptics experience may include information identifying the one or more fragments of the corresponding haptic track. [0163] For some embodiments of the example method, the first channel corresponds to a first frequency band.

[0164] For some embodiments of the example method, the information describing the haptics experience may further include information identifying the one or more adaptation sets.

[0165] For some embodiments of the example method, the information describing the haptics experience may further include: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, wherein the configuration information may include information describing one or more parallel haptics experience tracks.

[0166] For some embodiments of the example method, the information may further include information describing one or more haptics experience tracks, and the information describing the haptics experience track may further include: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

[0167] An example method/apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: encode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0168] An additional example method in accordance with some embodiments may include: decoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

[0169] For some embodiments of the additional example method, each of the one or more representations corresponds to the same time period.

[0170] For some embodiments of the additional example method, encoding of the information encodes the information in a container file.

[0171] For some embodiments of the additional example method, the one or more adaptation sets may include a main haptics experience and a second haptic experience, and the second haptic experience corresponds to a first perception modality and a first channel. [0172] For some embodiments of the additional example method, the adaptation set corresponding to the main haptics experience may include initialization data corresponding to a haptics decoder.

[0173] For some embodiments of the additional example method, the adaptation set corresponding to the second haptics experience may include one or more fragments of a corresponding haptic track.

[0174] For some embodiments of the additional example method, the adaptation set corresponding to the second haptics experience may include information identifying the one or more fragments of the corresponding haptic track.

[0175] Some embodiments of the additional example method may further include concatenating the initialization data with, from one or more adaptation sets, the information identifying the one or more fragments to generate a bitstream.

[0176] Some embodiments of the additional example method may further include rendering the bitstream in a haptic experience environment.

[0177] For some embodiments of the additional example method, the first channel corresponds to a first frequency band.

[0178] For some embodiments of the additional example method, the information describing the haptics experience may further include information identifying the one or more adaptation sets.

[0179] For some embodiments of the additional example method, the information describing the haptics experience may further include: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, and the configuration information may include information describing one or more parallel haptics experience tracks.

[0180] For some embodiments of the additional example method, the information may further include information describing one or more haptics experience tracks, and the information describing the haptics experience track may further include: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

[0181] For some embodiments of an example method, the information describing the haptics experience, and/or the encoded information describing the haptics experience, or is encoded in accordance with, the ISO Base Media File Format (ISOBMFF). [0182] For some embodiments of an example method, the information describing the haptics experience and/or the encoded information describing the haptics experience, is included in and streamed in a media file such as an MPEG-DASH (MPEG Dynamic Adaptive Streaming Over HTTP) media presentation descriptor (MPD) file.

[0183] For some embodiments of an example method, the information describing the haptics experience, and/or the encoded information describing the haptics experience, uses, is part of, and/or is compliant with, one or more of the MPEG standards ISO/IEC 23090-32 and ISO/IEC 23090-31.

[0184] An example method/apparatus in accordance with some embodiments may include: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: decode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

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

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

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

[0188] An example apparatus in accordance with some embodiments may include a computer-readable medium storing encoded information scene description file generated according to any one of the methods listed above.

[0189] An example signal in accordance with some embodiments may include a scene description file generated according to any one of the methods listed above.

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

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

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

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

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

[0195] Various numeric values may be used in the present disclosure, for example. The specific values are for example purposes and the aspects described are not limited to these specific values. [0196] Embodiments described herein may be carried out by computer software implemented by a processor or other hardware, or by a combination of hardware and software. As a non-limiting example, the embodiments can be implemented by one or more integrated circuits. The processor can be of any type appropriate to the technical environment and can encompass one or more of microprocessors, general purpose computers, special purpose computers, and processors based on a multi-core architecture, as non-limiting examples.

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

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

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

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

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

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

[0203] The implementations and aspects described herein can be implemented in, for example, a method or a process, an apparatus, a software program, a data stream, or a signal. Even if only discussed in the context of a single form of implementation (for example, discussed only as a method), the implementation of features discussed can also be implemented in other forms (for example, an apparatus or program). An apparatus can be implemented in, for example, appropriate hardware, software, and firmware. The methods can be implemented in, for example, a processor, which refers to processing devices in general, including, for example, a computer, a microprocessor, an integrated circuit, or a programmable logic device. Processors also include communication devices, such as, for example, computers, cell phones, portable/personal digital assistants (“PDAs”), and other devices that facilitate communication of information between end-users. [0204] Reference to “one embodiment” or “an embodiment” or “one implementation” or “an implementation”, as well as other variations thereof, means that a particular feature, structure, characteristic, and so forth described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase “in one embodiment” or “in an embodiment” or “in one implementation” or “in an implementation”, as well any other variations, appearing in various places throughout this disclosure are not necessarily all referring to the same embodiment.

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

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

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

[0208] It is to be appreciated that the use of any of the following ”, “and/or”, and “at least one of”, for example, in the cases of “A/B”, “A and/or B” and “at least one of A and B”, is intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of both options (A and B). As a further example, in the cases of “A, B, and/or C” and “at least one of A, B, and C”, such phrasing is intended to encompass the selection of the first listed option (A) only, or the selection of the second listed option (B) only, or the selection of the third listed option (C) only, or the selection of the first and the second listed options (A and B) only, or the selection of the first and third listed options (A and C) only, or the selection of the second and third listed options (B and C) only, or the selection of all three options (A and B and C). This may be extended for as many items as are listed. [0209] Also, as used herein, the word “signal” refers to, among other things, indicating something to a corresponding decoder. For example, in certain embodiments the encoder signals a particular one of a plurality of parameters for region-based filter parameter selection for de-artifact filtering. In this way, in an embodiment the same parameter is used at both the encoder side and the decoder side. Thus, for example, an encoder can transmit (explicit signaling) a particular parameter to the decoder so that the decoder can use the same particular parameter. Conversely, if the decoder already has the particular parameter as well as others, then signaling can be used without transmitting (implicit signaling) to simply allow the decoder to know and select the particular parameter. By avoiding transmission of any actual functions, a bit savings is realized in various embodiments. It is to be appreciated that signaling can be accomplished in a variety of ways. For example, one or more syntax elements, flags, and so forth are used to signal information to a corresponding decoder in various embodiments. While the preceding relates to the verb form of the word “signal”, the word “signal” can also be used herein as a noun.

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

[0211] We describe a number of embodiments. Features of these embodiments can be provided alone or in any combination, across various claim categories and types. Further, embodiments can include one or more of the following features, devices, or aspects, alone or in any combination, across various claim categories and types:

• A bitstream or signal that includes one or more of the described syntax elements, or variations thereof.

• A bitstream or signal that includes syntax conveying information generated according to any of the embodiments described.

• Creating and/or transmitting and/or receiving and/or decoding a bitstream or signal that includes one or more of the described syntax elements, or variations thereof. • Creating and/or transmiting and/or receiving and/or decoding according to any of the embodiments described.

• A method, process, apparatus, medium storing instructions, medium storing data, or signal according to any of the embodiments described.

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

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

Claims

1. A method comprising: encoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

2. The method of claim 1 , wherein each of the one or more representations corresponds to the same time period.

3. The method of any one of claims 1-2, wherein encoding of the information encodes the information in a container file.

4. The method of any one of claims 1-3, wherein the one or more adaptation sets comprise a main haptics experience and a second haptic experience, and wherein the second haptic experience corresponds to a first perception modality and a first channel.

5. The method of claim 4, wherein the adaptation set corresponding to the main haptics experience comprises initialization data corresponding to a haptics decoder.

6. The method of any one of claims 4-5, wherein the adaptation set corresponding to the second haptics experience comprises one or more fragments of a corresponding haptic track.

7. The method of claim 6, wherein the adaptation set corresponding to the second haptics experience comprises information identifying the one or more fragments of the corresponding haptic track.

8. The method of any one of claims 4-7, wherein the first channel corresponds to a first frequency band.

9. The method of any one of claims 1-8, wherein the information describing the haptics experience further comprises information identifying the one or more adaptation sets.

10. The method of any one of claims 1 -9, wherein the information describing the haptics experience further comprises: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, wherein the configuration information comprises information describing one or more parallel haptics experience tracks.

11 . The method of any one of claims 1 -9, wherein the information further comprises information describing one or more haptics experience tracks, and wherein the information describing the haptics experience track further comprises: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

12. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: encode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

13. A method comprising: decoding information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

14. The method of claim 13, wherein each of the one or more representations corresponds to the same time period.

15. The method of any one of claims 13-14, wherein encoding of the information encodes the information in a container file.

16. The method of any one of claims 13-15, wherein the one or more adaptation sets comprise a main haptics experience and a second haptic experience, and wherein the second haptic experience corresponds to a first perception modality and a first channel.

17. The method of claim 16, wherein the adaptation set corresponding to the main haptics experience comprises initialization data corresponding to a haptics decoder.

18. The method of claim 17, wherein the adaptation set corresponding to the second haptics experience comprises one or more fragments of a corresponding haptic track.

19. The method of claim 18, wherein the adaptation set corresponding to the second haptics experience comprises information identifying the one or more fragments of the corresponding haptic track.

20. The method of claim 19, further comprising: concatenating the initialization data with, from one or more adaptation sets, the information identifying the one or more fragments to generate a bitstream.

21 . The method of claim 20, further comprising rendering the bitstream in a haptic experience environment.

22. The method of any one of claims 16-21 , wherein the first channel corresponds to a first frequency band.

23. The method of any one of claims 13-22, wherein the information describing the haptics experience further comprises information identifying the one or more adaptation sets.

24. The method of any one of claims 13-23, wherein the information describing the haptics experience further comprises: information describing at least one available avatar for the haptics experience; and configuration information for at least one perception in the haptics experience, wherein the configuration information comprises information describing one or more parallel haptics experience tracks.

25. The method of any one of claims 13-23, wherein the information further comprises information describing one or more haptics experience tracks, and wherein the information describing the haptics experience track further comprises: information describing at least one available avatar for a haptics experience; and configuration information for at least one perception in the haptics experience.

26. The method of any one of claims 1-25, wherein the information describing the haptics experience, and/or the encoded information describing the haptics experience, or is encoded in accordance with, the ISO Base Media File Format (ISOBMFF).

.

27. The method of any one of claims 1 -25, wherein the information describing the haptics experience and/or the encoded information describing the haptics experience, is included in and streamed in a media file such as an MPEG-DASH (MPEG Dynamic Adaptive Streaming Over HTTP) media presentation descriptor (MPD) file.

28. The method of any one of claims 1-25, wherein the information describing the haptics experience, and/or the encoded information describing the haptics experience, uses, is part of, and/or is compliant with, one or more of the MPEG standards ISO/IEC 23090-32 and ISO/IEC 23090-31.

29. An apparatus comprising: a processor; and a non-transitory computer-readable medium storing instructions operative, when executed by the processor, to cause the apparatus to: decode information describing a haptics experience, wherein the information describing the haptics experience comprises one or more adaptation sets, and wherein each of the one or more adaptation sets comprises one or more representations corresponding to a haptics media track.

30. An apparatus comprising at least one processor configured to perform the method of any one of claims 1-

29.

31. An apparatus comprising a computer-readable medium storing instructions for causing one or more processors to perform the method of any one of claims 1-29.

32. An apparatus comprising at least one processor and at least one non-transitory computer-readable medium storing instructions for causing the at least one processor to perform the method of any one of claims 1-29.

33. A computer-readable medium storing encoded information scene description file generated according to any one of claims 16-29.

34. A signal including a scene description file generated according to any one of claims 1-29.