Supporting real-time avatar-based communication in 5g services

Abstract

Systems, methods, and instrumentalities are disclosed for an approach for avatar-based real-time communication service in 5G systems. The device may include sending a request for configuration information associated with a real-time communication (RTC) session to a network. The device may receive the configuration information from the network. The device may obtain WebRTC signaling function information. The device may use the WebRTC signaling function information to send signaling information associated with a WebRTC session to establish the WebRTC session with a second WTRU. The device may use the WebRTC session to negotiate avatar-related capabilities associated with an avatar.

Description

PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENTSUPPORTING REAL-TIME AVATAR-BASED COMMUNICATION IN 5G SERVICESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The application claims the benefit of U.S. Patent Application Number 63 / 682,186, filed August 12, 2024, the contents of which are incorporated by reference in their entirety herein.BACKGROUND

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

[0003] Systems, methods, and instrumentalities are disclosed for an approach for avatar-based real-time communication service in 5G systems. The method may include obtaining a base avatar. The method may include sending the base avatar to a first WTRU using a first data channel. The method may include sending the base avatar to a second WTRU using a second data channel. The method may include sending avatar animation data at least to the second WTRU. The method may include generating, using the avatar animation data, an animated avatar stream. The method may include sending the animated avatar stream for rendering to the first WTRU or the second WTRU.

[0004] In examples, the method being configured to receive the configuration information from the network comprises an RTC media session handler (MSH) being configured to receive the configuration information from an RTC application function (AF). The method may obtain the signaling function information comprises an avatar application being configured to obtain the signaling function information from an RTC media session handler (MSH).

[0005] In examples, the method may establish the WebRTC session and negotiate the avatar-related capabilities associated with the avatar using an SDP message exchange. The method may include establishing the WebRTC session with the second WTRU may include the processor being configured to establish the WebRTC session with the second WTRU via a media function (MF).

[0006] In examples, the avatar-related capabilities may include at least one of an avatar representation format or animation data format. In examples, the method may use the established WebRTC session toPCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT send avatar source data to the network. In examples, the method may include receiving a base avatar from the network.

[0007] In examples, the method may generate an avatar animation data stream. The method may include sending the avatar animation data stream to the second WTRU via a media function (MF) using a media channel or a data channel. In examples, the method may include animating the base avatar using the avatar animation data stream. The method may include sending the avatar animation data stream to the second WTRU using a media channel. The method may include rendering the animated base avatar.

[0008] A method associated with a first wireless transmit / receive unit (WTRU) may include establishing a WebRTC session with a second WTRU via a media function (MF) associated with a real time communication (RTC) application server (AS) of a network. The method may include using the WebRTC session to send captured data to the RTC AS, wherein the captured data is needed to generate a base avatar. The method may include receiving the base avatar from the RTC AS. The method may include obtaining source animation data and using the source animation data to generate an animation data stream. The method may include sending the animation data stream to the second WTRU.

[0009] In examples, the method may include sending the source animation data using a media channel or a data channel. The source animation data comprises one or more of a sensor data, an audio data, a video data, or a text data associated with the avatar. The sending the animation data stream may include sending the animation data stream to the second WTRU using a media channel or a data channel. The sending the animation data stream to the second WTRU may include sending the animation data stream to the second WTRU via the MF. The method may include using the animation data stream to animate the base avatar and generate an animated avatar stream. The method may include sending the animated avatar stream to the second WTRU using a media channel. The method may include rendering the animated base avatar. The method may include negotiating avatar-related capabilities associated with an avatar. The method may include negotiating the avatar-related capabilities associated with the avatar using an SDP message exchange. The avatar-related capabilities may include at least one of an avatar representation format or animation data format.

[0010] A method associated with a real time communication (RTC) application server (AS) may establishing a WebRTC session with a first wireless transmit / receive unit (WTRU) and a second WTRU. The method may include using the WebRTC session to receive captured data associated with an avatar. The method may include obtaining a base avatar. The method may include sending the base avatar to each of the first WTRU and the second WTRU. The method may include receiving source animation data from the first WTRU and use the source animation data to generate an animation data stream. The method may include sending the animation data stream to the second WTRU.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT

[0011] In examples, the obtaining the base avatar may include using the captured data to generate the base avatar. The obtaining the base avatar may include receiving the base avatar from an avatar storage based on a negotiation between the first WTRU and a media function (MF) of the RTC AS. The method may include establishing a first data channel with the first WTRU and a second data channel with the second WTRU. The method may include send the base avatar or the animation data stream to the first WTRU using the first data channel, or the second WTRU using the second data channel. The method may include using the animation data stream to animate the base avatar and generate an animated avatar stream. The method may include sending the animated avatar stream to at least one of the first WTRU using the first data channel or the second WTRU using the second data channel. The method may include retrieving and sending a scene description associated with the avatar to the first WTRU or the second WTRU. The method may include generating and sending a scene update trigger to the first WTRU or the second WTRU. The establishing the WebRTC session with the first WTRU and the second WTRU may include negotiating avatar-related capabilities associated with the avatar with the first WTRU or the second WTRU. The method may include negotiating the avatar-related capabilities associated with the avatar using an SDP message exchange. The avatar-related capabilities may include at least one of an avatar representation format or animation data format.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The following detailed description will be better understood when read in conjunction with the appended drawings, in which there are shown examples of one or more of the multiple embodiments of the present disclosure. It should be understood, however, that the embodiments described herein are not limited to the precise arrangements and instrumentalities shown in the drawings.

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

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

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

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

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

[0018] FIG. 3 illustrates an example video decoder.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT

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

[0020] FIG. 5 shows an example of a media delivery architecture.

[0021] FIG. 6 shows an example of a real-time communication (RTC) architecture.

[0022] FIG. 7 shows reference architecture for avatars.

[0023] FIG. 8 shows an example of an RTC architecture for avatar-based communication.

[0024] FIG. 9 shows an example of a call flow for call setup and capability negotiation.

[0025] FIG. 10 shows an example of a call flow for avatar media and metadata exchange.DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0078] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

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

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

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

[0082] The aspects described and contemplated in this application may be implemented in many different forms. FIGS. 5-10 described herein may provide some examples, but other examples are contemplated. The discussion of FIGS. 5-10 does not limit the breadth of the implementations. At least one of the aspects generally relates to video encoding and decoding, and at least one other aspect generally relates to transmitting a bitstream generated or encoded. These and other aspects may be implemented as a method, an apparatus, a computer readable storage medium having stored thereon instructions for encoding or decoding video data according to any of the methods described, and / or a computer readable storage medium having stored thereon a bitstream generated according to any of the methods described.

[0083]

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

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

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

[0086] Various numeric values are used in examples described the present application. These and other specific values are for purposes of describing examples and the aspects described are not limited to these specific values.

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

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

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

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

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

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

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

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

[0095] FIG. 4 is a diagram showing an example of a system in which various aspects and examples described herein may be implemented. System 400 may be embodied as a device including the various components described below and is configured to perform one or more of the aspects described in this document. Examples of such devices, include, but are not limited to, various electronic devices such as personal computers, laptop computers, smartphones, tablet computers, digital multimedia set top boxes, digital television receivers, personal video recording systems, connected home appliances, and servers. Elements of system 400, singly or in combination, may be embodied in a single integrated circuit (IC), multiple ICs, and / or discrete components. For example, in at least one example, the processing and encoder / decoder elements of system 400 are distributed across multiple ICs and / or discrete components. In various examples, the system 400 is communicatively coupled to one or more other systems, or otherPCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT electronic devices, via, for example, a communications bus or through dedicated input and / or output ports. In various examples, the system 400 is configured to implement one or more of the aspects described in this document.

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

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

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

[0099] In some examples, memory inside of the processor 410 and / or the encoder / decoder module 430 is used to store instructions and to provide working memory for processing that is needed during encoding or decoding. In other examples, however, a memory external to the processing device (for example, the processing device may be either the processor 410 or the encoder / decoder module 430) is used for one or more of these functions. The external memory may be the memory 420 and / or the storage device 440, forPCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT example, a dynamic volatile memory and / or a non-volatile flash memory. In several examples, an external non-volatile flash memory is used to store the operating system of, for example, a television. In at least one example, a fast external dynamic volatile memory such as a RAM is used as working memory for video encoding and decoding operations.

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

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

[0102] The USB and / or HDMI terminals can include respective interface processors for connecting system 400 to other electronic devices across USB and / or HDMI connections. It is to be understood that various aspects of input processing, for example, Reed-Solomon error correction, may be implemented, for example, within a separate input processing IC or within processor 410 as necessary. Similarly, aspects of USB or HDMI interface processing may be implemented within separate interface ICs or within processorPCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT410 as necessary. The demodulated, error corrected, and demultiplexed stream is provided to various processing elements, including, for example, processor 410, and encoder / decoder 430 operating in combination with the memory and storage elements to process the datastream as necessary for presentation on an output device.

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

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

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

[0106] The system 400 can provide an output signal to various output devices, including a display 475, speakers 485, and other peripheral devices 495. The display 475 of various examples includes one or more of, for example, a touchscreen display, an organic light-emitting diode (OLED) display, a curved display, and / or a foldable display. The display 475 may be for a television, a tablet, a laptop, a cell phone (mobile phone), or other device. The display 475 can also be integrated with other components (for example, as in a smart phone), or separate (for example, an external monitor for a laptop). The other peripheral devices 495 include, in various examples, one or more of a stand-alone digital video disc (or digital versatile disc) (DVD, for both terms), a disk player, a stereo system, and / or a lighting system. Various examples use one or more peripheral devices 495 that provide a function based on the output of the system 400. For example, a disk player performs the function of playing the output of the system 400.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT

[0107] In various examples, control signals are communicated between the system 400 and the display 475, speakers 485, or other peripheral devices 495 using signaling such as AV. Link, Consumer Electronics Control (CEC), or other communications protocols that enable device-to-device control with or without user intervention. The output devices may be communicatively coupled to system 400 via dedicated connections through respective interfaces 470, 480, and 490. Alternatively, the output devices may be connected to system 400 using the communications channel 460 via the communications interface 450. The display 475 and speakers 485 may be integrated in a single unit with the other components of system 400 in an electronic device such as, for example, a television. In various examples, the display interface 470 includes a display driver, such as, for example, a timing controller (T Con) chip.

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

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

[0110] As further examples, in one example “decoding” refers only to entropy decoding, in another example “decoding” refers only to differential decoding, and in another example “decoding” refers to a combination of entropy decoding and differential decoding. Whether the phrase “decoding process” is intended to refer specifically to a subset of operations or generally to the broader decoding process will be clear based on the context of the specific descriptions and is believed to be well understood by those skilled in the art.

[0111] As further examples, in one example “encoding” refers only to entropy encoding, in another example “encoding” refers only to differential encoding, and in another example “encoding” refers to a combination of differential encoding and entropy encoding. Whether the phrase “encoding process” is intended to refer specifically to a subset of operations or generally to the broader encoding process will bePCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT clear based on the context of the specific descriptions and is believed to be well understood by those skilled in the art.

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

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

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

[0115] Additionally, this application may refer to “determining” various pieces of information.Determining the information can include one or more of, for example, estimating the information, calculating the information, predicting the information, or retrieving the information from memory. Obtaining may include receiving, retrieving, constructing, generating, and / or determining.

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

[0117] Additionally, this application may refer to “receiving” various pieces of information. Receiving is, as with “accessing”, intended to be a broad term. Receiving the information can include one or more of, for example, accessing the information, or retrieving the information (for example, from memory). Further,PCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT“receiving” is typically involved, in one way or another, during operations such as, for example, storing the information, processing the information, transmitting the information, moving the information, copying the information, erasing the information, calculating the information, determining the information, predicting the information, or estimating the information.

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

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

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

[0121] Real-time communication services may provide immersive experiences to the end user, for example, by teleporting them into new worlds and allowing them to interact with other participants in richer and more realistic ways. Immersive real-time communication may have the potential to disrupt the way people communicate. Immersive real-time communication may be a (e.g., perceived as a) core aspect of the metaverse.

[0122] Avatars may be digital representations of users in the metaverse. The metaverse may be a set of virtual worlds where people may interact with each other in real-time. These avatars may take on many forms, from realistic human-like figures to synthetic characters. Avatars may allow users to express themselves, create a unique digital identity within the metaverse, and / or provide a sense of presence and connection with other users. The integration, animation, and representation of avatars in real-time communication services may enable (e.g., be essential to enable) these immersive experiences.

[0123] Real-time communication in 5G systems may be provided. Real-time communication (RTC) over a 5G system may be used for delivery of delay-sensitive media from one peer device to another via a 5G network. AR conversational service may be a typical use case for RTC. The RTC may enable end-users to directly communicate real-time media including AR / MR media content.

[0124] RTC architecture may be an instantiation of a media delivery architecture that utilzes5G media streaming and real-time communication (RTC) applications and services. FIG. 5 illustrates an example generalized media delivery architecture. FIG. 5. Various entities shown in FIG. 5 may provide various entities, mechanisms, and reference points that enable media delivery.

[0125] Network functions and WTRU entities a media delivery architecture may be provided including at least a media application function (AF). A media AF may be an AF dedicated to media delivery. Network functions and WTRU entities in this architecture may be provided including a media application server (AS). A media AS may be dedicated to media delivery. Network functions and WTRU entities in this architecture may be provided including at least a media client. A media client may include a WTRU internal function dedicated to media delivery. The media client may include a media session handler. The media session handler may be an entity on the WTRU that communicates with the Media AF (e.g., via a reference point M5) to establish, control and support the delivery of a media session.

[0126] A media client may include a media access function. The media access function may be an entity on a WTRU that may communicate with the media AS to access and / or deliver media content. In examples,PCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT the media access function may be further sub-divided into content delivery protocols, codecs, media types and / or metadata representation.

[0127] A media client may include a media-aware application. The media-aware application may be an application entity on the WTRU that may use application programing interfaces (APIs) to invoke the media session handler and / or the media access function to support media delivery.

[0128] FIG. 6 illustrates an example of an RTC general architecture over a 5G system. Table 1 illustrates mapping of RTC functions in the RTC general architecture in FIG. 6 to the generalized media delivery architecture in FIG. 5. Subfunctions inside the RTC AF, RTC AS and the RTC endpoint may be defined and the reference points shown in FIG. 6 may be defined.Table 1

[0129] An avatar reference architecture may be provided. FIG. 7 may illustrate an example of a reference architecture for avatars. The architecture for avatars as illustrated in FIG. 7 may be utilized for identifying and addressing the key technology challenges and recommend solutions for the support of avatars in 5G RTC services.

[0130] The identified Avatar functions may include avatar storage. Avatar storage may be an entity that offers storage of base avatars. This entity may be offered by the 5G System, a 3rd party entity, or a local storage of the user’s device(s). The avatar storage may enable access to the base avatar and any related data, for example, including authorization of the avatar usage rights, etc. an authentication functionality may be able to map and identify the ownership of an avatar.

[0131] The identified Avatar functions may include avatar animation. Depending on the avatar representation format, avatar animation may be utilized to retrieve the base avatar. Avatar animation may receive representation format-specific animation data stream(s),and may perform the avatar animation to produce the animated avatar that may be used in the rendering process.

[0132] The identified Avatar functions may include scene management. Scene management may include creating and composing the shared 3D scene for participants (e.g., all participants). Scene management may integrate a description of a user’s avatar and may update its position and / or orientation based on the user’s pose. The updated scene may be shared with participants (e.g., all participants).PCT / US25 / 41653 12 August 2025 (12.O8.2O25)IVOW_2024P00591WO PATENT

[0133] The identified Avatar functions may include animation data generation. Animation data generation may include generating animation data from raw signals. The raw signals may be obtained from camera(s), microphone(s), specialized motion capturing device(s), and the like. In examples, through the current functional element, the video captured by the camera may be converted into facial feature points. The audio captured by the microphone may be converted into text, and the like.

[0134] The identified Avatar functions may include base avatar generation. A base avatar may be generated from inputs such as captured video from a camera and / or other sensors information, for example, in conjunction with a reference avatar. Base avatar generation may be performed online or offline.

[0135] An RTC service based on the general RTC architecture may support (e.g., only support) classic media types such as audio and video. In some examples, such an RTC service based on the general RTC service may not allow for more immersive media types and interactions such as avatar media.

[0136] An instantiation of the general RTC architecture may be provided that takes into consideration the unique characteristics of this type of media (e.g., avatar media). The reference architecture for avatars may enable real-time avatar-based communication in 5G services.

[0137] An instantiation may be identified to provide a description of how to set up a call or sessions for exchanging avatar media and exchange avatar media.

[0138] An RTC Architecture for avatar-based communication services may be provided. FIG. 8 illustrates an RTC architecture for avatar-based communication that may be an instantiation of the general RTC architecture with a mapping of the network functions described in the avatar reference architecture. In this RTC architecture, an application for avatar-based communication may interact with an RTC client to establish RTC session(s) (e.g., a webRTC-based RTC session(s)) with avatar support.

[0139] Call flow for call setup and capability negotiation may be provided.

[0140] FIG. 9 illustrates an example of a call flow diagram for call setup and capability negotiation between an avatar application (e.g., an avatar application running on a WTRU ( WTRU1 )), the MF, and a remote endpoint (e.g., WTRU2).

[0141] As illustrated in FIG. 9, at 1 , service provisioning and announcement of an RTC service may be provided on the network side, for example, between the Media AF and the Media application provider (AP).

[0142] As illustrated in FIG. 9, at 2, the RTC MSH (e.g., as part of the WTRU1) may request configuration information from the RTC AF relating to one or more RTC sessions.

[0143] As illustrated in FIG. 9, at 3, the RTC AF may provide the requested configuration information to the RTC MSH of the WTRU1.

[0144] As illustrated in FIG. 9, at 4, the application (e.g., an avatar application) may query the RTC MSH, e.g., via the WebRTC Framework for the WebRTC signaling function information to retrieve thisPCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT information. In some examples, where the signaling is handled by WebRTC framework, the RTC Framework may query the RTC MSH for this information.

[0145] As illustrated in FIG. 9, at 5 and / or 6, two or more WebRTC endpoints(e.g., WTRU1 and WTRU2) may exchange signaling information related to the WebRTC session, for example, a WebRTC session between interactive connectivity establishment (ICE) candidates and session description protocol (SDP) offer / answer message using the trusted WebRTC signaling function. The SDP offer / answer messages may be used to negotiate avatar-related capabilities such as an avatar representation format or an animation data format as well as support for data channels.

[0146] Avatar media and metadata exchange may be provided. FIG. 10 illustrates a call flow diagram for the exchange of avatar media and associated metadata between relevant entities in the RTC architecture for avatar-based communication after call setup has been complete and a WebRTC session has been established between the MF, avatar application running on WTRU1, and the remote endpoint (e.g., WTRU2).

[0147] A scene description retrieval may be provided. An MF and the participating WTRUs may retrieve scene descriptions. The scene description may be shared by the MF with the WTRUs. The WTRUs may have their own scene descriptions. A scene description update may be provided. A scene update trigger may occur, for example, if an object is added to or removed from a scene or if spatial information is updated. The update trigger may originate from the MF itself or the WTRUs. The WTRUs may update their scene descriptions independently or the MF may generate an updated scene description and share it with the WTRUs.

[0148] As illustrated in FIG. 10, avatar acquisition may be provided (e.g., at D.1). The RTC application on WTRU1 may send (e.g., at D.1 a.1) captured data needed to generate the base avatar to the Media Function in the RTC AS through one or more real-time transport protocols (RTP) streams over the WebRTC session (e.g., the established WebRTC session). The MF may use (e.g., at D.1 a.2) the captured data sent by WTRU1 to generate the base avatar for the user. When the base avatar is generated in the network by the MF, the generated base avatar may be stored in the avatar storage for future loading. The MF may load (e.g., at D.1 b.1 ) the base avatar for WTRU1 , identified by the negotiation step, from the Avatar Storage.

[0149] As illustrated in FIG. 10, avatar delivery may be provided (e.g., at D.2). The MF may create (e.g., at D.2.1) a reliable data channel for the delivery of the base avatar to WTRU2. The MF may create (e.g., at D.2.2) a reliable data channel for the delivery of the base avatar to WTRU1 . The MF may deliver the base avatar to WTRU1 and WTRU2 using the respective data channels.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT

[0150] Animation Data Generation may be provided (e.g., at D.3). As illustrated in FIG. 10, WTRU1 may send (e.g., at D.3a.1) source animation data (e.g., sensor data, audio, video, text) to the MF through media or data channels. The MF may process (e.g., at D.3a.2) the received source data to generate an animation data stream for the session. The MF may deliver (e.g., at D.3a.3) the generated animation data through a media or data channel to WTRU2. In network-centric avatar animation data generation, the animation data generated by the MF may be delivered to WTRU1 . WTRU1 may use (e.g., at D.3b.1 ) data captured by its sensors to generate an animation data stream. WTRU1 may send (e.g., at D.3b.2) the generated animation data stream to WTRU2 through the MF over a media or data channel.

[0151] Avatar Animation may be provided. As illustrated in FIG. 10, the MF may use (e.g., at D.4a.1) the animation data (generated by the MF itself in step D.3a.2 or received from WTRU1 in step D.3b.2) to animate the base avatar. The MF may send (e.g., at D.4a.2) an animated avatar stream to WTRU1 and WTRU2. WTRU1 may animate (e.g., at D.4b.1 ) the base avatar using the animation data stream generated (e.g., at D.3b.1 ). The WTRU1 may send (e.g., at D.4b.2) an animated avatar stream to (e.g., directly to) WTRU2 through a media channel.

[0152] As illustrated in FIG. 10, avatar rendering and display (e.g., at D.5) may be provided. The WTRU2 may render the animated avatar based on the target viewport and pose.

[0153] One or more embodiments provide a computer program comprising instructions which when executed by one or more processors cause such processors to perform the encoding and / or decoding methods according to any of the embodiments described above. One or more embodiments also provide a computer readable storage medium having stored thereon instructions for encoding or decoding video data according to the methods described above.

[0154] One or more embodiments provide a computer readable storage medium having stored thereon video data generated according to the methods described above. One or more embodiments also provide a method and apparatus for transmitting or receiving video data generated according to the methods described above.

Claims

PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENTCLAIMSWhat is claimed is:1 . A first wireless transmit / receive unit (WTRU) comprising a processor configured to at least: send a request for configuration information associated with a real-time communication (RTC) session to a network; receive the configuration information from the network; obtain WebRTC signaling function information; use the WebRTC signaling function information to send signaling information associated with a WebRTC session to establish the WebRTC session with a second WTRU; and use the WebRTC session to negotiate avatar-related capabilities associated with an avatar.

2. The first WTRU of claim 1 , wherein the processor being configured to receive the configuration information from the network comprises an RTC media session handler (MSH) being configured to receive the configuration information from an RTC application function (AF).

3. The first WTRU of claim 1 , wherein the processor being configured to obtain the WebRTC signaling function information comprises an avatar application being configured to obtain the WebRTC signaling function information from an RTC media session handler (MSH).

4. The first WTRU of claim 1 , wherein the processor is further configured to establish the WebRTC session and negotiate the avatar-related capabilities associated with the avatar using an SDP message exchange.

5. The first WTRU of claim 1 , wherein the processor being configured to establish the WebRTC session with the second WTRU comprises the processor being configured to establish the WebRTC session with the second WTRU via a media function (MF).

6. The first WTRU of claim 1 , wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT7. The first WTRU of claim 1 , wherein the processor is further configured to use the established WebRTC session to send avatar source data to the network.

8. The first WTRU of claim 1 , wherein the processor is further configured to receive a base avatar from the network.

9. The first WTRU of claim 8, wherein the processor is further configured to: generate an avatar animation data stream; and send the avatar animation data stream to the second WTRU via a media function (MF) using a media channel or a data channel.

10. The first WTRU of claim 9, wherein the processor is further configured to: animate the base avatar using the avatar animation data stream; and send the avatar animation data stream to the second WTRU using a media channel.11 . The first WTRU of claim 10, wherein the processor is further configured to render the animated base avatar.

12. A first wireless transmit / receive unit (WTRU) comprising a processor configured to at least: establish a WebRTC session with a second WTRU via a media function (MF) associated with a real time communication (RTC) application server (AS) of a network; use the WebRTC session to send captured data to the RTC AS, wherein the captured data is needed to generate a base avatar; receive the base avatar from the RTC AS; obtain source animation data and use the source animation data to generate an animation data stream; and send the animation data stream to the second WTRU.

13. The first WTRU of claim 12, wherein the processor is configured to send the source animation data using a media channel or a data channel.

14. The WTRU of claim 12, wherein the source animation data comprises one or more of a sensor data, an audio data, a video data, or a text data associated with an avatar.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT15. The WTRU of claim 12, wherein the processor being configured to send the animation data stream comprises the processor being configured to send the animation data stream to the second WTRU using a media channel or a data channel.

16. The WTRU of claim 15, wherein the processor being configured to send the animation data stream to the second WTRU comprises the processor being configured to send the animation data stream to the second WTRU via the MF.

17. The WTRU of claim 12, wherein the processor is further configured to: use the animation data stream to animate the base avatar and generate an animated avatar stream; and send the animated avatar stream to the second WTRU using a media channel.

18. The WTRU of claim 17, wherein the processor is further configured to render the animated base avatar.

19. The WTRU of claim 12, wherein the processor is further configured to negotiate avatar-related capabilities associated with an avatar.

20. The WTRU of claim 19, wherein the processor is configured to negotiate the avatar-related capabilities associated with the avatar using an SDP message exchange.21 . The WTRU of claim 19, wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.

22. A real time communication (RTC) application server (AS) comprising a processor configured to at least: establish WebRTC session with a first wireless transmit / receive unit (WTRU) and a second WTRU; use the WebRTC session to receive captured data associated with an avatar; obtain a base avatar; send the base avatar to each of the first WTRU and the second WTRU; receive source animation data from the first WTRU and use the source animation data to generate an animation data stream; and send the animation data stream to the second WTRU.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT23. The RTC AS of claim 22, wherein the processor being configured to obtain the base avatar comprises the processor being configured to use the captured data to generate the base avatar.

24. The RTC AS of claim 22, wherein the processor being configured to obtain the base avatar comprises the processor being configured to receive the base avatar from an avatar storage based on a negotiation between the first WTRU and a media function (MF) of the RTC AS.

25. The RTC AS of claim 22, wherein the processor is configured to establish a first data channel with the first WTRU and a second data channel with the second WTRU.

26. The RTC AS of claim 25, wherein the processor is configured to send the base avatar or the animation data stream to the first WTRU using the first data channel, or the second WTRU using the second data channel.

27. The RTC AS of claim 25, wherein the processor is configured to use the animation data stream to animate the base avatar and generate an animated avatar stream.

28. The RTC AS of claim 27, wherein the processor is configured to send the animated avatar stream to at least one of the first WTRU using the first data channel or the second WTRU using the second data channel.

29. The RTC AS of claim 22, wherein the processor is further configured to retrieve and send a scene description associated with the avatar to the first WTRU or the second WTRU.

30. The RTC AS of claim 22, wherein the processor is further configured to generate and send a scene update trigger to the first WTRU or the second WTRU.31 . The RTC AS of claim 22, wherein the processor is being configured to establish the WebRTC session with the first WTRU and the second WTRU comprises the processor being configured to negotiate avatar-related capabilities associated with the avatar with the first WTRU or the second WTRU.

32. The RTC AS of claim 31 , wherein the processor is further configured to negotiate the avatar- related capabilities associated with the avatar using an SDP message exchange.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT33. The RTC AS of claim 31 , wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.

34. A method associated with a first wireless transmit / receive unit (WTRU) comprising: sending a request for configuration information associated with a real-time communication (RTC) session to a network; receiving the configuration information from the network; obtaining WebRTC signaling function information; using the WebRTC signaling function information to send signaling information associated with a WebRTC session to establish the WebRTC session with a second WTRU; and using the WebRTC session to negotiate avatar-related capabilities associated with an avatar.

35. The method of claim 34, wherein receiving the configuration information from the network comprises an RTC media session handler (MSH) being configured to receive the configuration information from an RTC application function (AF).

36. The method of claim 34, wherein obtaining the WebRTC signaling function information comprises an avatar application being configured to obtain the WebRTC signaling function information from an RTC media session handler (MSH).

37. The method of claim 34, further comprising establishing the WebRTC session and negotiating the avatar-related capabilities associated with the avatar using an SDP message exchange.

38. The method of claim 34, wherein establishing the WebRTC session with the second WTRU further comprises establishing the WebRTC session with the second WTRU via a media function (MF).

39. The method of claim 34, wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.

40. The method of claim 34, further comprising use the established WebRTC session to send avatar source data to the network.41 . The method of claim 34, further comprising receiving a base avatar from the network.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT42. The method of claim 41 , further comprising: generating an avatar animation data stream; and sending the avatar animation data stream to the second WTRU via a media function (MF) using a media channel or a data channel.

43. The method of claim 42, further comprising: animating the base avatar using the avatar animation data stream; and sending the avatar animation data stream to the second WTRU using a media channel.

44. The method of claim 43, further comprising rendering the animated base avatar.

45. A method associated with a first wireless transmit / receive unit (WTRU) comprising: establishing a WebRTC session with a second WTRU via a media function (MF) associated with a real time communication (RTC) application server (AS) of a network; using the WebRTC session to send captured data to the RTC AS, wherein the captured data is needed to generate a base avatar; receiving the base avatar from the RTC AS; obtaining source animation data and use the source animation data to generate an animation data stream; and sending the animation data stream to the second WTRU.

46. The method of claim 45, further comprising sending the source animation data using a media channel or a data channel.

47. The method of claim 45, wherein the source animation data comprises one or more of a sensor data, an audio data, a video data, or a text data associated with an avatar.

48. The method of claim 45, wherein sending the animation data stream further comprises sending the animation data stream to the second WTRU using a media channel or a data channel.

49. The method of claim 48, wherein sending the animation data stream to the second WTRU further comprises sending the animation data stream to the second WTRU via the MF.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT50. The method of claim 45, further comprising: using the animation data stream to animate the base avatar and generate an animated avatar stream; and sending the animated avatar stream to the second WTRU using a media channel.51 . The method of claim 50, further comprising rendering the animated base avatar.

52. The method of claim 48, further comprising negotiating avatar-related capabilities associated with an avatar.

53. The method of claim 52, further comprising negotiating the avatar-related capabilities associated with the avatar using an SDP message exchange.

54. The method of claim 52, wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.

55. A method associated with a real time communication (RTC) application server (AS) comprising: establishing WebRTC session with a first wireless transmit / receive unit (WTRU) and a secondWTRU; using the WebRTC session to receive captured data associated with an avatar; obtaining a base avatar; sending the base avatar to each of the first WTRU and the second WTRU; receiving source animation data from the first WTRU and use the source animation data to generate an animation data stream; and sending the animation data stream to the second WTRU.

56. The method of claim 55, wherein obtaining the base avatar further comprises using the captured data to generate the base avatar.

57. The method of claim 55, wherein obtaining the base avatar further comprises receiving the base avatar from an avatar storage based on a negotiation between the first WTRU and a media function (MF) of the RTC AS.PCT / US25 / 41653 12 August 2025 (12.08.2025)IVOW_2024P00591WO PATENT58. The method of claim 55, further comprising establishing a first data channel with the first WTRU and a second data channel with the second WTRU.

59. The method of claim 58, further comprising sending the base avatar or the animation data stream to the first WTRU using the first data channel, or the second WTRU using the second data channel.

60. The method of claim 58, further comprising using the animation data stream to animate the base avatar and generate an animated avatar stream.61 . The method of claim 60, further comprising sending the animated avatar stream to at least one of the first WTRU using the first data channel or the second WTRU using the second data channel.

62. The method of claim 55, further comprising retrieving and sending a scene description associated with the avatar to the first WTRU or the second WTRU.

63. The method of claim 55, further comprising generating and sending a scene update trigger to the first WTRU or the second WTRU.

64. The method of claim 55, wherein establishing the WebRTC session with the first WTRU and the second WTRU further comprises negotiating avatar-related capabilities associated with the avatar with the first WTRU or the second WTRU.

65. The method of claim 64, further comprising negotiating the avatar-related capabilities associated with the avatar using an SDP message exchange.

66. The method of claim 64, wherein the avatar-related capabilities comprise at least one of an avatar representation format or animation data format.

Images