Avatars with mixed textures in scene descriptions

Abstract

Systems, methods, and instrumentalities are disclosed for rendering an avatar grid. A device can include a processor that can be configured to determine attributes associated with an avatar. The attributes can include at least a list of avatar textures. An avatar texture of the list of avatar textures can include at least a list of avatar texture operators. An avatar texture operator of the list of avatar texture operators can include at least a purpose. The avatar texture operator can indicate information associated with the avatar texture operator in a texture mix. The processor can be further configured to update a texture associated with the avatar based on the purpose associated with the avatar texture operator.

Description

[0001] Cross-reference to related applications This application claims the benefit of European Patent Application No. 24305496.2, filed on 29 March 2024, the contents of which are incorporated herein by reference in their entirety. Background Technology

[0002] Video encoding and decoding systems can be used to compress digital video signals, for example, to reduce the storage and / or transmission bandwidth required for such signals. Video encoding and decoding systems can include, for example, block-based, wavelet-based, and / or object-based systems. Current mechanisms for avatar coding for 3D scene representation may be imperfect. Summary of the Invention

[0003] The device may include a processor that can be configured to determine attributes associated with an avatar. The attributes associated with an avatar may be a node with an MPEG node avatar extension.

[0004] Attributes may include at least a list of avatar textures. The avatar texture list may include at least a list of avatar texture operators. Avatar textures may indicate avatar texture definitions. The processor is also configured to resolve material and path attributes from the avatar. The processor may also be configured to determine that descriptive attributes can be associated with an avatar and to resolve descriptive attributes from the avatar.

[0005] The avatar texture operator list can include at least a purpose. Avatar texture operators can indicate information associated with texture operators in a texture blend. Avatar texture operators can be information associated with each texture operator in a texture blend. The processor can also be configured to determine if an avatar texture can define the purpose of a texture blend. The processor can also be configured to determine if an avatar texture can define the purpose of a static texture.

[0006] The processor can also be configured to update the texture associated with the avatar based on the usage associated with the avatar texture operator.

[0007] These examples can be executed by a device with a processor. The device can be an encoder or a decoder. These examples can be executed by a computer program product stored on a non-transitory computer-readable medium and including program code instructions. These examples can be executed by a computer program including program code instructions. These examples can be executed by a bitstream including information representing a template-matching prediction pattern.

[0008] The systems, methods, and means described herein may relate to a decoder. In some examples, the systems, methods, and means described herein may relate to an encoder. In some examples, the systems, methods, and means described herein may relate to a signal (e.g., from an encoder and / or received by a decoder). A computer-readable medium may include instructions for causing one or more processors to perform the methods described herein. A computer program product may include instructions that, when executed by one or more processors, cause one or more processors to perform the methods described herein. Attached Figure Description

[0009] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented.

[0010] Figure 1B To illustrate, according to an embodiment, it is possible to Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0011] Figure 1C To illustrate, according to an embodiment, it is possible to Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system.

[0012] Figure 1D To illustrate, according to an embodiment, it is possible to Figure 1A The diagram shows another example RAN and another example CN used in the communication system.

[0013] Figure 2 The illustration shows an example video encoder.

[0014] Figure 3 The illustration shows an example video decoder.

[0015] Figure 4 The illustration shows an example of a system that can implement various aspects and examples.

[0016] Figure 5 The diagram illustrates the node parsing flowchart with support for the "MPEG_node_avatar" extension.

[0017] Figure 6 The diagram illustrates the parsing flowchart for items in the "textures" list of "MPEG_node_avatar".

[0018] Figure 7 The diagram illustrates the parsing flowchart for the items in the "operators" list of "AvatarTexture". Detailed Implementation

[0019] A more detailed understanding can be obtained from the following description, which is given in illustrative form in conjunction with the accompanying drawings.

[0020] Figure 1A The diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 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 Spectrum OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0021] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, 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. For example, any of the WTRUs 102a, 102b, 102c, and 102d, which may be referred to as a “station” and / or “STA”, may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain scenarios), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0023] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In embodiments, 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 a desired spatial direction.

[0024] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. The air interface can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

[0025] More specifically, as noted above, communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b, 102c can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

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

[0027] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish air interface 116 using new radio (NR).

[0028] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for example, use the dual connectivity (DC) principle to implement both LTE and NR radio access together. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0029] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced GSM Evolution Data Rate (EDGE), GSM EDGE (GERAN), etc.

[0030] Figure 1A Base station 114b can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business premises, residence, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, it is not required that base station 114b access Internet 110 via CN 106 / 115.

[0031] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. Data can have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or implement advanced security features such as user authentication. Although not explicitly stated... Figure 1AAs shown, but will be understood, RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to connecting to RAN 104 / 113, which may be using NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0032] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs that may employ the same RAT as or a different RAT than RAN 104 / 113.

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

[0034] Figure 1B The following diagram illustrates the system of example WTRU 102. Figure 1B As shown, among other things, 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 supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138. It will be appreciated that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0035] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. As discussed above, processor 118 may include multiple processors. Processor 118 may perform signal encoding / decoding, data processing, power control, input / output processing, and / or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be understood that the processor 118 and transceiver 120 can be integrated together into an electronic package or chip.

[0036] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF signals and optical signals. It will be appreciated that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0038] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals to be received by transmitting / receiving element 122. As noted above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via various RATs such as NR and IEEE 802.11, for example.

[0039] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from these devices. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access information from any type of suitable memory and store the data in memory such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)) and store the data in that memory.

[0040] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for powering the WTRU 102. For example, the power supply 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 cell units, fuel cell units, etc.

[0041] 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 instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information using any suitable location determination method, while remaining consistent with the embodiments.

[0042] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0043] WTRU 102 may include a full-duplex radio, for which the transmission and reception of some or all signals (e.g., associated with a specific subframe of both 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 hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In embodiments, WTRU 102 may include a half-duplex radio, for which the transmission and reception of some or all signals (e.g., associated with a specific subframe of either UL (e.g., for transmission) or downlink (e.g., for reception) may be concurrent and / or simultaneous.

[0044] Figure 1C The diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As noted above, RAN 104 may employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 may also communicate with CN 106.

[0045] RAN 104 may include eNode-B 160a, 160b, 160c, but will be appreciated that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each of eNode-B 160a, 160b, 160c may include one or more transceivers for communicating with WTRU 102a, 102b, 102c via air interface 116. In one embodiment, eNode-B 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNode-B 160a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0046] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0047] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0048] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0049] The SGW 164 can connect to each eNode B 160a, 160b, or 160c in RAN 104 via the S1 interface. The SGW 164 can typically route user data packets to or forward user data packets from WTRUs 102a, 102b, or 102c. The SGW 164 can also perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, or 102c, and managing and storing the context of WTRUs 102a, 102b, or 102c.

[0050] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks such as Internet 110, facilitating communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0051] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks such as PSTN 108 to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0052] Despite WTRU in Figures 1A-1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0053] In a representative embodiment, the other network 112 may be a WLAN.

[0054] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that introduces and / or leads traffic into and / or out of the BSS. Traffic originating outside the BSS and destined for a STA can be delivered to the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to its respective destination. Traffic between STAs within the BSS can be sent, for example, through the AP, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0055] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA (e.g., every STA), including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can exit. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0056] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0057] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data is passed through a segmented parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped onto the two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0058] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah uses non-TVWS spectrum to support 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths. According to a representative embodiment, 802.11ah can support instrument-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

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

[0060] In the United States, the available frequency band for 802.11ah is 902 MHz to 928 MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah ranges from 6 MHz to 26 MHz.

[0061] Figure 1D The diagram illustrates a system diagram of RAN 113 and CN 115 according to an embodiment. As noted above, RAN 113 can use NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 can also communicate with CN 115.

[0062] RAN 113 may include gNBs 180a, 180b, and 180c; however, it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Thus, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In an embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be located on unlicensed spectrum, while the remaining component carriers may be located on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0063] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with Scalable Digital Numerology (SDN). For example, OFDM symbol spacing and / or OFDM subcarrier spacing can be varied for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes of various or scalable lengths or Transmission Time Intervals (TTIs) (e.g., containing different numbers of OFDM symbols and / or absolute times of varying durations).

[0064] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without also accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, and also with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate essentially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput to serve WTRUs 102a, 102b, and 102c.

[0065] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, and routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

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

[0067] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types being utilized by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and services for Machine Type Communication (MTC) access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0068] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of traffic through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0069] UPF 184a and 184b can connect to one or more of gNB 180a, 180b, and 180c in RAN 113 via the N3 interface. The N3 interface can provide WTRU 102a, 102b, and 102c with access to packet-switched networks such as Internet 110, facilitating communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0070] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0071] Given Figures 1A-1D as well as Figures 1A-1D The corresponding descriptions herein indicate that one or more of the functions described herein in relation to one or more of the following can be implemented by one or more emulation devices (not shown): WTRU102a-102d, base station 114a-114b, eNode-b 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0072] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more functions while being temporarily implemented / deployed as part of a wired or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can be used for testing via over-the-air wireless communication.

[0073] One or more simulation devices can perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices can be used in test scenarios within test laboratories and / or undeployed (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. One or more simulation devices can be test rigs. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0074] This application describes a wide variety of aspects, including tools, features, examples, models, methods, etc. Many of these aspects are described in a targeted manner and, at least to show individual characteristics, are generally described in a way that may sound restrictive. However, this is for clarity and does not limit the application or scope of those aspects. In fact, all the different aspects can be combined and interchanged to provide other aspects. Furthermore, these aspects can also be combined and interchanged with aspects described in earlier applications.

[0075] The aspects described and envisioned in this application can be implemented in many different forms. Figures 5-7 Some examples can be provided, but other examples are also envisioned. Figures 5-7 The discussion does not limit the breadth of implementations. At least one of these aspects generally relates to video encoding and decoding, and at least one other aspect generally relates to the transmission of the generated or encoded bitstream. These and other aspects can be implemented as methods, apparatus, computer-readable storage media having instructions thereon stored thereon for encoding or decoding video data according to any of the described methods, and / or computer-readable storage media having bitstreams generated according to any of the described methods stored thereon.

[0076] In this application, the terms “reconstruction” and “decoding” are used interchangeably, the terms “pixel” and “sample” are used interchangeably, and the terms “image”, “picture” and “frame” are used interchangeably.

[0077] Various methods are described herein, and each method includes one or more steps or actions to achieve the described method. Unless a specific order of steps or actions is required for the method to operate correctly, the order and / or use of specific steps and / or actions can be modified or combined. Furthermore, terms such as "first," "second," etc., may be used in various examples to modify elements, components, steps, operations, etc., such as "first decoding" and "second decoding," for example. Unless specifically required, the use of such terms does not imply a reordering of the modified operations. Therefore, in this example, the first decoding does not need to be performed before the second decoding and can occur, for example, before, during, or within a time period overlapping with the second decoding.

[0078] The various methods and other aspects described in this application can be used to modify modules (e.g., decoding modules) of the video encoder 200 and video decoder 300, such as... Figure 2 and Figure 3 As shown. Furthermore, the subject matter disclosed herein can be applied to, for example, any type, format, or version of video codecs, whether described in pre-existing or future-developed standards or recommendations, and any extensions to such standards and recommendations. Unless otherwise indicated or technically excluded, the aspects described in this application may be used alone or in combination.

[0079] The examples in this application use various numerical values, such as bits, bit depth, etc. These and other specific numerical values ​​are for illustrative purposes only, and the aspects described are not limited to these specific numerical values.

[0080] Figure 2 This is a diagram illustrating a video encoder. Variations of the example encoder 200 are envisioned, but for clarity, encoder 200 is described below without depicting all anticipated variations.

[0081] Before being encoded, the video sequence may undergo pre-coding (201), for example, by applying color transformations to the input color image (e.g., from RGB 4:4:4 to YCbCr 4:2:0) or by remapping the input image components to obtain a more resilient signal distribution to compression (e.g., using histogram equalization of one of the color components). Metadata may be associated with the pre-processing and attached to the bitstream.

[0082] In encoder 200, the image is encoded by encoder elements as described below. The image to be encoded is partitioned (202) and processed in units such as encoding / decoding units (CUs). Each unit is encoded using, for example, an intra-frame or inter-frame mode. When a unit is encoded intra-frame, intra-frame prediction (260) is performed. In inter-frame mode, motion estimation (275) and compensation (270) are performed. The encoder can decide (205) which of the intra-frame or inter-frame modes to use for the encoding unit, and indicates the intra-frame / inter-frame decision, for example, by a prediction mode flag. For example, the prediction residual is calculated by subtracting (210) the predicted block from the original image block.

[0083] The predicted residual is then transformed (225) and quantized (230). The quantized transform coefficients, along with the motion vector and other syntax elements, are entropy encoded / decoded (245) to output a bitstream. The encoder can skip the transform and apply quantization directly to the untransformed residual signal. The encoder can bypass both the transform and quantization, i.e., the residual is directly encoded / decoded without applying either the transform or quantization process.

[0084] The encoder decodes the coded block to provide a reference for further prediction. The quantized transform coefficients are dequantized (240) and inverse transformed (250) to decode the prediction residual. The decoded prediction residual and the prediction block are combined (255) to reconstruct the image block. An in-loop filter (265) is applied to the reconstructed image to perform, for example, deblocking / SAO (sample adaptive offset) filtering to reduce coding artifacts. The filtered image is stored in a reference image buffer (280).

[0085] Figure 3 This is a diagram illustrating an example video decoder. In the example decoder 300, as described below, the bitstream is decoded by decoder elements. The video decoder 300 typically implements... Figure 2 The encoder 200 is the inverse of the decoder pass described in the document. The encoder 200 typically also performs video decoding as part of the encoding of the video data.

[0086] Specifically, the input to the decoder includes a video bitstream, which can be generated by the video encoder 200. The bitstream is first entropy decoded (330) to obtain transform coefficients, motion vectors, and other encoding / decoding information. Picture partitioning information indicates how to partition the picture. Therefore, the decoder can partition the picture according to the decoded picture partitioning information (335). The transform coefficients are dequantized (340) and inverse transformed (350) to decode the prediction residuals. The decoded prediction residuals and prediction blocks are combined (355) to reconstruct the image blocks. Prediction blocks can be obtained (370) from intra-frame prediction (360) or motion-compensated prediction (375) (i.e., inter-frame prediction). An in-loop filter (365) is applied to the reconstructed image. The filtered image is stored in a reference picture buffer (380).

[0087] The decoded image can also undergo post-decoding processing (385), such as inverse color transformation (e.g., from YCbCr 4:2:0 to RGB 4:4:4) or inverse remapping (the inverse of the remapping process performed in the pre-encoding process (201)). Post-decoding processing can use metadata derived in the pre-encoding process and signaled in the bitstream. In the example, the decoded image (e.g., after applying the in-loop filter (365) and / or after post-decoding processing (385) if post-decoding processing is used) can be sent to a display device for rendering to the user.

[0088] Figure 4 The diagram illustrates an example of a system in which the various aspects and examples described herein may be implemented. System 400 may be embodied as a device including the various components described below and configured to implement one or more aspects described in this document. Examples of such devices include, but are not limited to, various electronic devices such as personal computers, laptops, smartphones, tablets, digital multimedia set-top boxes, digital television receivers, personal video recording systems, connected home appliances, and servers. Elements of system 400 may be embodied individually or in combination in a single integrated circuit (IC), multiple ICs, and / or discrete components. For example, in at least one example, the processing and encoder / decoder elements of system 400 are distributed across multiple ICs and / or discrete components. In various examples, system 400 is communicatively coupled to one or more other systems or other electronic devices via, for example, a communication bus or through dedicated input and / or output ports. In various examples, system 400 is configured to implement one or more aspects described in this document.

[0089] System 400 includes at least one processor 410 configured to execute instructions loaded thereon to implement various aspects, such as those described in this document. Processor 410 may include embedded memory, input / output interfaces, and various other circuitry known in the art. System 400 includes at least one memory 420 (e.g., a volatile memory device and / or a non-volatile memory device). System 400 includes a storage device 440, which may 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 memory, disk drives, and / or optical disk drives. As a non-limiting example, storage device 440 may include internal storage devices, attached storage devices (including removable and non-removable storage devices), and / or network-accessible storage devices.

[0090] System 400 includes an encoder / decoder module 430 configured to, for example, process data to provide encoded or decoded video, and the encoder / decoder module 430 may include its own processor and memory. The encoder / decoder module 430 represents one or more modules that can be included in a device to perform encoding and / or decoding functions. It is well known that a device may include one or both of the encoding and decoding modules. Additionally, as those skilled in the art will appreciate, the encoder / decoder module 430 may be implemented as a separate element of system 400, or may be incorporated into processor 410 as a combination of hardware and software.

[0091] Program code to be loaded onto processor 410 or encoder / decoder 430 to implement the various aspects described in this document may be stored in storage device 440 and subsequently loaded onto memory 420 for execution by processor 410. According to various examples, one or more of processor 410, memory 420, storage device 440, and encoder / decoder module 430 may store one or more various items during the execution of the processes described in this document. Such stored items may include, but are not limited to, input video, decoded video or portions of decoded video, bitstreams, matrices, variables, and intermediate or final results from the processing of equations, formulas, operations, and operational logic.

[0092] In some examples, the memory within processor 410 and / or encoder / decoder module 430 is used to store instructions and provide working memory for processing required during encoding or decoding. However, in other examples, external memory (e.g., the processing device could be processor 410 or encoder / decoder module 430) is used for one or more of these functions. External memory could be memory 420 and / or storage device 440, such as volatile memory and / or non-volatile flash memory. In several examples, external non-volatile flash memory is used to store, for example, the operating system of a television. In at least one example, fast external volatile memory (such as RAM) is used as working memory for video encoding and decoding operations.

[0093] Inputs to the components of system 400 may be provided by various input devices as indicated in box 445. Such input devices include, but are not limited to: (i) a radio frequency (RF) section that receives, for example, RF signals transmitted 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. Figure 4 Other examples not shown include composite video.

[0094] In various examples, the input device of block 445 has associated corresponding input processing elements known in the art. For example, the RF section may be associated with elements suitable for: (i) selecting a desired frequency (also known as selecting a signal, or limiting a signal band to a certain band); (ii) down-converting the selected signal; (iii) band-limiting it again to a narrower band to select, for example, a signal band that may be referred to as a channel in some examples; (iv) demodulating the down-converted and band-limited signal; (v) performing error correction; and / or (vi) demultiplexing to select a desired data packet stream. The RF section of various examples includes one or more elements for performing these functions, such as frequency selectors, signal selectors, band limiters, channel selectors, filters, downconverters, demodulators, error correctors, and demultiplexers. The RF section may include tuners that perform various of these functions, including, for example, down-converting a received signal to a lower frequency (e.g., intermediate frequency or near-baseband frequency) or baseband. In one set-top box example, the RF section and its associated input processing elements receive RF signals transmitted via a wired (e.g., cable) medium and perform frequency selection by filtering, down-converting, and re-filtering to the desired frequency band. Various examples rearrange the order of the above (and other) components, remove some of these components, and / or add other components that perform similar or different functions. Adding components may include inserting components between existing components, such as, for example, inserting amplifiers and analog-to-digital converters. In various examples, the RF section includes an antenna.

[0095] USB and / or HDMI terminals may include corresponding interface processors for connecting system 400 to other electronic devices across USB and / or HDMI connections. It is to be understood that various aspects of input processing, such as Reed-Solomon error correction, may be implemented as needed, for example, within a separate input processing IC or within processor 410. Similarly, aspects of USB or HDMI interface processing may be implemented as needed within a separate interface IC or within processor 410. Demodulated, error-corrected, and demultiplexed streams are provided to various processing elements, including, for example, processor 410 and encoder / decoder 430 operating in conjunction with memory and storage elements, to process the data streams as needed for presentation on an output device.

[0096] Various components of system 400 can be provided within an integrated housing. Within the integrated housing, the various components can be interconnected using a suitable connection arrangement 425 and data can be transmitted therebetween, such as internal buses known in the art, including inter-IC (I2C) buses, wiring, and printed circuit boards.

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

[0098] In various examples, data is streamed or otherwise provided to system 400 using a wireless network such as Wi-Fi (e.g., IEEE 802.11 (IEEE refers to the Institute of Electrical and Electronics Engineers)). In these examples, the Wi-Fi signal is received via a communication channel 460 and a communication interface 450 suitable for Wi-Fi communication. The communication channel 460 in these examples is typically connected to an access point or router that provides access to external networks, including the Internet, to allow streaming applications and other over-the-top communications. Other examples use a set-top box to provide streaming data to system 400, delivering data via an HDMI connection in input box 445. Still other examples use an RF connection in input box 445 to provide streaming data to system 400. As indicated above, various examples provide data in a non-streaming manner. Additionally, various examples use wireless networks other than Wi-Fi, such as cellular networks or Bluetooth® networks.

[0099] System 400 can provide output signals to various output devices, including displays 475, speakers 485, and other peripheral devices 495. Displays 475 in various examples include one or more of, for example, touchscreen displays, organic light-emitting diode (OLED) displays, curved displays, and / or foldable displays. Displays 475 can be used in televisions, tablets, laptops, mobile phones, or other devices. Displays 475 can also be integrated with other components (e.g., in smartphones) or standalone (e.g., as an external monitor for a laptop). In various examples, other peripheral devices 495 include one or more of standalone digital video discs (or digital multifunction discs) (DVDs, for both terms), disc players, stereo systems, and / or lighting systems. Various examples use one or more peripheral devices 495 that provide functionality based on the output of system 400. For example, a disc player performs the function of playing the output of system 400.

[0100] In various examples, signaling such as AV links, Consumer Electronics Control (CEC), or other communication protocols that enable device-to-device control with or without user intervention is used to transmit control signals between system 400 and display 475, speaker 485, or other peripheral devices 495. Output devices can be communicatively coupled to system 400 via dedicated connections through their respective interfaces 470, 480, and 490. Alternatively, output devices can be connected to system 400 via communication interface 450 using communication channel 460. Display 475 and speaker 485 can be integrated into a single unit with other components of system 400 in electronic devices such as, for example, televisions. In various examples, display interface 470 includes display drivers, such as, for example, timing controller (TCon) chips.

[0101] Alternatively, the display 475 and speaker 485 can be separated from one or more other components, for example, if the RF section of input 445 is part of a separate set-top box. In various examples where the display 475 and speaker 485 are external components, the output signal can be provided via dedicated output connections, including, for example, HDMI ports, USB ports, or COMP outputs.

[0102] The example can be implemented by computer software implemented by processor 410, or by hardware, or by a combination of hardware and software. As a non-limiting example, the example can be implemented by one or more integrated circuits. Memory 420 can be of any type suitable for the technical environment and can be implemented using any suitable data storage technology, such as optical memory devices, magnetic memory devices, semiconductor-based memory devices, fixed memory, and removable memory, as non-limiting examples. Processor 410 can be of any type suitable for the technical environment and, as a non-limiting example, can encompass one or more of microprocessors, general-purpose computers, special-purpose computers, and processors based on multi-core architectures. Various implementations involve decoding. As used in this application, "decoding" can encompass all or part of a process, such as performing a received encoded sequence to produce a final output suitable for display. In various examples, such a process includes one or more processes typically performed by a decoder, such as entropy decoding, inverse quantization, inverse transform, and differential decoding. In various examples, such a process also includes, or alternatively may include, the process performed by a decoder of the various implementations described in this application, such as identifying a reference image (e.g., a reference frame) associated with a block (e.g., the current block), and the device may include a processor configured to determine attributes associated with the avatar. The attributes may include at least a list of avatar textures. The avatar textures in the avatar texture list may include at least a list of avatar texture operators. The avatar texture operators in the avatar texture operator list may include at least a purpose. The avatar texture operators may indicate information associated with texture operators in texture blending. The processor may be further configured to update the texture associated with the avatar based on the purpose associated with the avatar texture operator.

[0103] As further examples, in one example, "decoding" refers only to entropy decoding; in another example, "decoding" refers only to differential decoding; and in yet another example, "decoding" refers to a combination of entropy decoding and differential decoding. It will be clear, and those skilled in the art, whether the phrase "decoding processing" is intended to specifically refer to a subset of operations or generally to broader decoding processing, based on the specific context of the description.

[0104] Various implementations involve encoding. Similar to the discussion of “decoding” above, the term “encoding” as used in this application can encompass all or part of a process performed on an input video sequence to produce an encoded bitstream. In various examples, such a process includes one or more processes typically performed by an encoder, such as partitioning, differential coding, transform, quantization, and entropy coding. In various examples, such a process also includes, or alternatively includes, processes performed by encoders of the various implementations described in this application, for example, where the device may include a processor configured to determine attributes associated with an avatar. The attributes may include at least a list of avatar textures. The avatar textures in the avatar texture list may include at least a list of avatar texture operators. The avatar texture operators in the avatar texture operator list may include at least a purpose. The avatar texture operators may indicate information associated with texture operators in texture blending. The processor may be further configured to update the textures associated with the avatar based on the purposes associated with the avatar texture operators.

[0105] As further examples, in one example, "encoding" refers only to entropy encoding; in another, "encoding" refers only to differential encoding; and in yet another, "encoding" refers to a combination of differential and entropy encoding. It will be clear, and those skilled in the art, whether the phrase "encoding processing" is intended to specifically refer to a subset of operations or generally to broader encoding processing, based on the specific context of the description.

[0106] Note that the syntax elements used in this document, such as the codec syntax for template matching prediction, including but not limited to MPEG_node_avatar, isAvatar, mapping, type, operator, material, texture, range, weight, etc., are descriptive terms. Therefore, the use of other syntax element names is not excluded.

[0107] When a diagram is presented as a flowchart, it should be understood that it also provides a block diagram of the corresponding device. Similarly, when a diagram is presented as a block diagram, it should be understood that it also provides a flowchart of the corresponding method / process.

[0108] The implementations and aspects described herein can be implemented, for example, in methods or processes, apparatuses, software programs, data streams, or signals. Even if discussed only in the context of a single implementation (e.g., discussed only as a method), the features under discussion can be implemented in other forms (e.g., apparatuses or programs). Apparatuses can be implemented, for example, in appropriate hardware, software, and firmware. Methods can be implemented, for example, in a processor, which generally refers to a processing device, including, for example, a computer, microprocessor, integrated circuit, or programmable logic device. Processors also include communication devices, such as, for example, computers, mobile phones, portable / personal digital assistants (“PDAs”), and other devices that facilitate information communication between end users.

[0109] The reference to "an example" or "example" or "an implementation" or "implementation" and its variations means that the specific features, structures, characteristics, etc., described in connection with the example are included in at least one example. Therefore, the phrases "in an example" or "in the example" or "in an implementation" or "in the implementation" and any other variations appearing throughout this application do not necessarily all refer to the same example.

[0110] Additionally, this application may involve "determining" various pieces of information. Determining information may include, for example, one or more of estimated information, calculated information, predicted information, or information retrieved from memory. Obtaining may include receiving, retrieving, constructing, generating, and / or determining.

[0111] Furthermore, this application may involve "accessing" various information fragments. Accessing information may include, for example, receiving information, retrieving information (e.g., from memory), storing information, moving information, copying information, calculating information, determining information, predicting information, or estimating information, or one or more of these.

[0112] Additionally, this application may relate to "receiving" various pieces of information. Like "access," receiving is intended to be a broad term. Receiving information may include, for example, accessing information or retrieving information (e.g., from memory) from one or more sources. Furthermore, "receiving" typically relates in one or more ways during operations such as, for example, storing information, processing information, transmitting information, moving information, copying information, erasing information, calculating information, determining information, predicting information, or estimating information.

[0113] To be clear, for example, in the cases of “A / B,” “A and / or B,” and “at least one of A and B,” the use of any of the following “ / ,” “and / or,” and “at least one of…” is intended to cover selecting only the first listed option (A), or only the second listed option (B), or both options (A and B). As another example, in the cases of “A, B, and / or C” and “at least one of A, B, and C,” this wording is intended to cover selecting only the first listed option (A), or only the second listed option (B), or only the third listed option (C), or only the first and second listed options (A and B), or only the first and third listed options (A and C), or only the second and third listed options (B and C), or all three options (A, B, and C). As will be apparent to those skilled in the art and related fields, this can be extended to as many items as are listed.

[0114] Furthermore, as used herein, the term "signal" refers, among other things, to something indicated to the corresponding decoder. Encoder signals may include, for example, an encoding function that uses a precision factor to encode the input of a block. In this way, in the examples, the same parameters are used on both the encoder and decoder sides. Therefore, for example, the encoder may transmit (explicit signaling) a specific parameter to the decoder so that the decoder can use the same specific parameter. Conversely, if the decoder already has that specific parameter as well as other parameters, then signaling can then be used without transmission (implicit signaling) to simply allow the decoder to know and select that specific parameter. In various examples, bit savings are achieved by avoiding the transmission of any actual function. It should be understood that signaling can be done in a variety of ways. For example, in various examples, one or more syntax elements, flags, etc., are used to signal information to the corresponding decoder. While the foregoing refers to the verb form of the term "signal," the term "signal" may (e.g., also) be used as a noun herein.

[0115] It will be apparent to those skilled in the art that implementations can generate a wide variety of signals formatted to carry, for example, information that can be stored or transmitted. This information may include, for example, instructions for implementing a method or data generated by one of the described implementations. For example, a signal may be formatted to carry a bit stream as described in the example. Such a signal may be formatted, for example, as an electromagnetic wave (e.g., using the radio frequency portion of the spectrum) or a baseband signal. Formatting may include, for example, encoding a data stream and modulating a carrier wave with the encoded data stream. The information carried by the signal may be, for example, analog or digital information. It is well known that signals can be transmitted via a wide variety of wired or wireless links. Signals may be stored on, accessed from, or received from a processor-readable medium.

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

[0117] These examples can be executed by a device having at least one processor. The device can be an encoder or a decoder. These examples can be executed by a computer program product stored on a non-transitory computer-readable medium and including program code instructions. These examples can be executed by a computer program including program code instructions. These examples can be executed by a bitstream including information representing template matching prediction patterns.

[0118] In scene descriptions, texture blending encoding can be used on avatar 3D models. Blended textures can include non-linear combinations of textures, allowing for texture editing. Blended textures can be encoded into glTF files. Using the "MPEG_node_avatar" extension, one or more avatars can be defined in a glTF file.

[0119] For example, if additional information associated with texture blending is provided, an avatar containing blended textures within a glTF file can be used. For instance, an application can load a glTF file containing an avatar and blended textures. The system or user can define the texture blends to use and their intended purpose. In the example, texture blending can be performed to alter the avatar's facial appearance (e.g., tattoos, makeup, scars, etc.). Users can either know or guess these texture blends.

[0120] For example, in a heterogeneous environment, an avatar can be presented in a virtual store to try on clothes. The avatar can experiment with various combinations, such as clothing and / or makeup. Modification of the avatar's makeup with texture blending can be supported by a 3D rendering application. In this example, the exact texture blending associated with the makeup must be known to the application.

[0121] The list of textures can be associated with an avatar. The list of textures can be part of the MPEG_node_avatar extension, as shown in Table 1.

[0122] Table 1 - MPEG_node_avatar attributes with a new list of "textures".

[0123] Each item in the texture list can be used to define the texture for the avatar and how to use each texture in the texture list. The texture associated with the avatar can be indicated by the AvatarTexture property, as shown in Table 2.

[0124] Table 2 - AvatarTexture properties.

[0125] The "type" attribute indicates the type of texture. Various types are supported, including "main", "mix", and / or other types. If the "type" attribute is "main", then AvatarTexture indicates that the texture is a static texture. If the "type" attribute is "mix", then AvatarTexture indicates that the texture is a mixed texture. The "description" attribute describes the texture and its purpose. For example, the "description" attribute can be used in a user interface to help users understand the texture's intent. The "purpose" attribute can include a string. The string can identify the purpose of the texture. The string can follow a predefined set of values, which can be associated with an application or defined by a standard. The "purpose" attribute can include an enumeration type. The "material" attribute can be used to indicate the index of an existing material in the "materials" list under the root of the glTF file. The "path" attribute can be a string that points to the TextureInfo attribute in the material. If "type" is "mix", the TextureInfo it points to can include the "MPEG_texture_mix" extension.

[0126] The “operators” list of the AvatarTexture property can be used to indicate the properties of each operator in the texture blending of the TextureInfo indicated by the “material” and “path” properties. In the example, the size of the “operators” list can be equal to the number of operators in the texture blending of the TextureInfo indicated by the “material” and / or “path” properties. Each item in the “operators” list can indicate the properties of the corresponding texture operator (e.g., operators[0] can indicate the properties of the texture blending operator, the operators of the texture blending operator, etc.).

[0127] You can provide the AvatarTextureOperator property, as shown in Table 3.

[0128] Table 3 - AvatarTextureOperator properties.

[0129] As shown in Table 3, the "description" attribute can indicate the texture operator and its purpose. For example, the "description" attribute can be used in a user interface to help users understand the intent of the texture operator. The "purpose" attribute can include a string that identifies the purpose of the texture operator. The purpose attribute can follow a predefined value defined by the application or standard. The "purpose" attribute can include an enumeration type. For example, when weights exist (e.g., "INTERPOLATE"), the "range" attribute can define the minimum and maximum values ​​that the texture operator weights can obtain. When weights exist (e.g., the operator "INTERPOLATE"), the weight attribute can include one or more weights of the texture operator. The number of values ​​in "weight" can be the same as the number of values ​​in the "weight" attribute of the corresponding texture operator. If the corresponding texture operator has a weight attribute, the weight attribute can replace the weights of the corresponding texture operator.

[0130] The following example illustrates a possible part of a glTF file related to materials and nodes. There may be a scene with one (or more) meshes representing avatars.

[0131] In the example, the glTF file can encode the avatar, as shown below: .

[0132] In the example, the avatar head can be encoded with a skin texture that can be altered using texture blending. One or more textures can be used (e.g., three textures), including a base texture for albedo (skin tone), a texture with lip makeup, and a texture with eye makeup. The albedo texture can be used consistently. Two makeup textures can be used harmoniously.

[0133] In the example, the glTF parser can decode every attribute associated with the content except for the "MPEG_node_avatar" extension.

[0134] The gITF parser can decode the "MPEG_node_avatar" content found in the first node. The gITF parser can indicate that the node is an avatar (e.g., where "isAvatar" is true), the type is a standard type ("type" is "urn:mpeg:sd:2023:avatar"), and there is a part corresponding to the header ("mappings" attribute).

[0135] The "textures" attribute of "MPEG_node_avatar" can be parsed. A single "AvatarTexture" item may exist. The type of this avatar texture may be "mix" ("type" is "mix"). The "mix" type indicates that the texture defines texture blending properties. This texture can be described using the message "Makeup" ("description" is "Makeup"). This avatar texture can change the avatar's makeup (e.g., "purpose" could be "avatar:makeup"). The string "avatar:makeup" can be an example of the value of the "purpose" attribute and can be defined by the application or standard.

[0136] The avatar texture can use the "baseColorTexture" of "pbrMetallicRoughness" in the first material ("material" is 0 and "path" is "pbrMetallicRoughness / baseColorTexture"). This "TextureInfo" property can contain an "MPEG_texture_mix" extension, which can be consistent with the avatar texture of type "mix". The "operators" list of "AvatarTexture" can have three items, which is consistent with the number of operators in texture mixing (i.e., the "operators" in "MPEG_texture_mix" has three items).

[0137] The first item in the "operators" list for the avatar texture can be associated with the first texture operator. This first item can be indicated or described using the string "Lips makeup" ("description" is "Lips makeup"). Texture operators can be used to add makeup to the avatar's lips (in the "purpose" of "avatar:makeup:lips"). To achieve this effect, weight values ​​between 0.0 and 0.8 can be used ("range" is [0.0, 0.8]). In the example, the weights [1, 1, 1] can be replaced with texture operators having [0.0, 0.0, 0.0] ("weights" is [0.0,0.0,0.0]).

[0138] The second item in the list of "operators" that embody the texture can be associated with a second texture operator and can be described by the string "Eyes makeup" ("description" is "Eyes makeup"). This texture operator can add makeup to the eyes (i.e., with the "purpose" of "avatar:makeup:lips"). This effect can be achieved using weight values ​​between 0.0 and 0.7 (i.e., "range" is [0.0, 0.7]). The weights [1, 1, 1] in the texture operator can be replaced with [0.0, 0.0, 0.0] ("weights" is [0.0, 0.0, 0.0]).

[0139] The last item in the "operators" list that transforms into a texture can be ignored because its "purpose" value is set to "unused".

[0140] The choice of value for the “purpose” attribute may depend on the application or standard and may differ from the value in this example.

[0141] The processing model can assume the existence and support of the "MPEG_texture_mix" extension. Figure 5 The flowchart in the diagram illustrates the parsing of nodes with the support of the "MPEG_node_avatar" extension.

[0142] like Figure 5As illustrated in the diagram, at point 501, a node can be parsed each time it is processed in the glTF file. At point 502, the glTF loader can decode standard attributes and possible extensions. At point 503, it can determine whether "MPEG_node_avatar" exists. If "MPEG_node_avatar" exists, the loader can continue parsing the node. Otherwise, the parsing process can end. At point 504, the "isAvatar" attribute can be parsed. The "isAvatar" attribute can be mandatory. If the "isAvatar" attribute does not exist, an error may be generated (and / or displayed). At point 505, the "type" attribute can be parsed. The "type" attribute can be mandatory. If the "type" attribute does not exist, an error may be generated (and / or displayed). At point 506, the "mappings" attribute can be parsed. The "mappings" attribute can be mandatory. If the "mappings" attribute does not exist, an error may be generated (and / or displayed). At point 507, it can determine whether the "textures" attribute exists. At 508, if the "textures" attribute exists, each item in the texture list can be parsed. At 509, node parsing can end, and the results (if any) of the data found in the "MPEG_node_avatar" extension are stored in a dedicated structure. The data provided in MPEG_node_avatar (not just avatar textures) may be informative and may not change the scene described by glTF. Such data may not change the scene.

[0143] Figure 6 The flowchart in the document illustrates the parsing of items in the "textures" list within "MPEG_node_avatar".

[0144] like Figure 6As illustrated in the diagram, at 601, each time the "AvatarTexture" attribute in the glTF file is processed, the parsing of an item in the "textures" list of "MPEG_node_avatar" can occur. At 602, the "purpose" attribute can be parsed. The "purpose" attribute can be mandatory. If the "purpose" attribute does not exist, an error may be generated (and / or displayed). At 603, the "material" and "path" attributes can be parsed. The "material" and "path" attributes can be mandatory. If the "material" and "path" attributes do not exist, an error may be generated (and / or displayed). "Material" can index an existing material in the glTF. "Path" can indicate the "TextureInfo" attribute in that material. At 604, it can be determined whether the "description" attribute exists. At 605, the "description" attribute can be parsed. At 606, it can be determined whether the "type" attribute is classified as "main". If the "type" attribute is classified as "main", then the parsing of the node can then end at 610. At 607, it can be determined whether the "type" attribute is categorized as "mix". If the "type" attribute is categorized as "mix", then the "TextureInfo" indicated by the "material" and "path" attributes can have a mixed texture. At 608, each item in the "operators" list can be parsed. At 610, node parsing can end. If the "type" attribute is neither categorized as "main" nor "mix", then at 609, an error may be generated and / or reported.

[0145] Figure 7 The flowchart in the image illustrates the parsing of the items in the "operators" list within "AvatarTexture": like Figure 7As illustrated, at point 701, each time the "AvatarTextureOperator" attribute in the glTF file can be processed, the items in the "operators" list of the "AvatarTexture" can be parsed. At point 702, the "purpose" attribute can be parsed. The "purpose" attribute can be mandatory. If the "purpose" attribute does not exist, an error may be generated (and / or displayed). At point 703, the existence of the "description" attribute can be determined. At point 704, the "description" attribute can be parsed. At point 705, the existence of the "range" attribute can be determined. At point 706, the "range" attribute can be parsed. At point 707, the existence of the "weight" attribute can be determined. At point 708, the "weight" attribute can be parsed.

[0146] Virtual worlds can be controlled by various entities, such as companies, governments, or users. Users of such virtual worlds can import their avatars into these virtual worlds. These avatars can function according to the virtual world they inhabit. The operation of such virtual worlds can be standardized.

[0147] An avatar in the virtual world can support one or more functionalities. For example, the ability to change its texture(s). Textures can be changed for various reasons. For example, the texture associated with an avatar can be changed based on the situation the avatar can represent and / or the environment in which the avatar can exist. In one example, the avatar might be presenting well during an interview. In another example, the avatar might be attending a fun event with friends. In yet another example, the avatar might be showing signs of being affected by environmental conditions (e.g., cold, illness, etc.). Textures can be changed based on attributes provided by the user avatar file. In one example, the corresponding texture can be retrieved from the user avatar file. One or more uses can be defined. In one example, a use named "avatar:beautiful" can be defined. Such uses can be used to retrieve, generate, and / or display beautiful avatar textures. In one example, when the avatar is attending an interview, the application can use this use and set it to "avatar:beautiful". In one example, a use named "avatar:health:disease" can be defined to depict a sick avatar. For example, in games or virtual worlds, an application can use this purpose to present a sick avatar when the avatar needs to appear sick, or if the user triggers a "sick" emote. Texture changes can be binary. The default avatar texture can be replaced with another texture (e.g., the "main" avatar texture type). Texture changes can be composite. The default avatar texture can be replaced with a specific texture blend (e.g., the "mix" avatar texture type). The weighted portion of the blend can be enabled, disabled, and / or changed.

[0148] Virtual stores may be operated by different companies, governments, or users. Users can import their avatars into these virtual stores. These avatars can function correctly in each virtual store that adheres to the same standards.

[0149] It supports avatar customization in virtual stores within a virtual world. Users of the avatar can purchase clothing from these virtual stores. Avatars (e.g., user-controlled avatars) can be imported into virtual stores. Clothing can be tried on, provided the avatar has its body measurements. The avatar's textures can be updated, for example, to match clothing for specific occasions. For instance, avatar textures can model their sun exposure level (weighted, from low to high) to help them see how swimwear might suit different skin tones. Avatar textures can model everyday makeup to see how dresses might suit them. Avatar textures can model the amount of facial hair and indicate the suitability of accessories such as sunglasses.

[0150] Creating 3D assets can involve breaking the process down into multiple stages. Each stage can focus on a specific task, such as mesh modeling, texturing, animation, lighting, etc. These stages can be handled by various individuals or teams, or completed by the same person at different times. The results of each stage can be stored in a new file. Various glTF mechanisms can support storing the results of several tasks. This may not be the case for other tasks (such as avatar modeling). Editing avatar textures may not be possible.

[0151] An avatar's texture can be baked into a single texture, for example, using the glTF mechanism. During this process, all creation parameters may be lost. Therefore, if an artist receives an avatar with a baked texture, he or she may be unable to modify the avatar. The coding mechanism described in this paper allows artists to send avatars with blended textures. Other artists in subsequent stages can then correct the blended textures (e.g., enable or disable components, or change the weights associated with components) without interacting with artists involved in previous stages. Artists at a certain stage can describe and define the purpose of textures and texture parameters. Information about textures, how textures are used, and how to use textures can help artists who may be working on avatars and / or blended textures associated with avatars.

[0152] Although the features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented in computer programs, software, or firmware and embedded in computer-readable media for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and optical media (e.g., CD-ROMs and digital multifunction optical discs (DVDs)). The processor, used in conjunction with the software, can be used to implement a radio frequency transceiver, which can be used in a WTRU, UE, terminal, base station, RNC, or any host.

Claims

1. An apparatus comprising: The processor is configured to at least: Determine the attributes associated with the avatar, wherein the attributes include at least a list of avatar textures, wherein the avatar texture list includes at least a list of avatar texture operators, wherein the avatar texture operators in the list of avatar texture operators include at least a purpose, and wherein the avatar texture operators indicate information associated with texture operators in texture blending; and Update the texture associated with the avatar based on the usage associated with the avatar texture operator.

2. The device according to claim 1, wherein, The attribute associated with the avatar is a node with MPEG node avatar extensions.

3. The device according to claim 1, wherein, Avatar texture indicates the avatar texture definition.

4. The device according to claim 1, wherein, The processor is further configured as follows: Analyze the material and path properties derived from the avatar.

5. The device according to claim 1, wherein, The processor is further configured as follows: Determine the descriptive attributes associated with the avatar; and Parse the descriptive attributes from the avatar.

6. The device according to claim 1, wherein, The processor is further configured as follows: Defining the avatar texture defines the purpose of the static texture.

7. The device according to claim 1, wherein, The processor is further configured as follows: Defining the avatar texture defines the purpose of texture blending.

8. A method comprising: Determine the attributes associated with the avatar, wherein the attributes include at least a list of avatar textures, wherein the avatar texture list includes at least a list of avatar texture operators, wherein the avatar texture operators in the list of avatar texture operators include at least a purpose, and wherein the avatar texture operators indicate information associated with texture operators in texture blending; and Update the texture associated with the avatar based on the usage associated with the avatar texture operator.

9. The method according to claim 8, wherein, The attribute associated with the avatar is a node with MPEG node avatar extensions.

10. The method according to claim 8, wherein, Avatar texture indicates the avatar texture definition.

11. The method of claim 8, further comprising: Analyze the material and path properties derived from the avatar.

12. The method of claim 8, further comprising: Determine the descriptive attributes associated with the avatar; as well as Parse the descriptive attributes from the avatar.

13. The method of claim 8, further comprising: Defining the avatar texture defines the purpose of the static texture.

14. The method of claim 8, further comprising: Defining the avatar texture defines the purpose of texture blending.

Images