Method and apparatus for performing uplink (UL) data prediction and reporting predicted UL buffer status

Abstract

A wireless transmit / receive unit (WTRU) may receive predictive buffer status report (BSR) configuration information. The predictive BSR configuration information may include information indicating an associated time frame and at least one trigger condition. The WTRU may predict an uplink (UL) traffic amount corresponding to the associated time frame. The WTRU may predict BSR configuration information. The WTRU may determine that at least one trigger condition has been satisfied. The WTRU may transmit a predictive BSR that includes an indication of the predicted amount of UL traffic.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 388,055 filed on July 11, 2022 and U.S. Provisional Patent Application No. 63 / 410,924 filed on September 28, 2022. U.S. Provisional Patent Application No. 63 / 388,055 is incorporated herein by reference in its entirety. U.S. Provisional Patent Application No. 63 / 410,924 is incorporated herein by reference in its entirety. Background Art

[0003] Current New Radio (NR) uplink (UL) scheduling mechanisms may rely primarily on UL buffer status reports (BSRs) transmitted by user equipment (UE). UEs may also be referred to herein as wireless transmit / receive units (WTRUs). Typically, a WTRU may transmit a BSR after data has arrived at the WTRU, and may not start UL transmission of the data until the WTRU is granted permission. Scheduling based on such request and / or grant patterns may result in high latency and a large amount of UL signaling, which may make it challenging to provide services that are delay-intolerant such as URLLC (Ultra-Reliable Low Latency Communication) services. Summary of the invention

[0004] Wireless communications between one or more user equipments (UEs) and a network are contemplated herein. A UE may also be referred to as a wireless transmit / receive unit (WTRU). The terms "UE" and "WTRU" are used interchangeably herein.

[0005] Methods and apparatus for completing uplink (UL) scheduling are described herein. In an example, a WTRU may facilitate scheduling by providing its UL data prediction capability. The WTRU may be configured to utilize artificial intelligence (AI) and / or machine learning (ML) to complete UL data prediction. The WTRU may be configured to receive an AI and / or ML (AI / ML) model for UL data prediction. The WTRU may receive an indication and / or information about the AI / ML model, capability and / or configuration configured for UL data prediction and / or generating a predictive buffer status report (BSR). The WTRU may receive a configuration about information to be included in a predictive BSR from the network. The WTRU may receive a configuration about a trigger condition for the predictive BSR from the network. The WTRU may receive an indication from the network to activate, start and / or resume and / or deactivate, stop and / or suspend UL data prediction and / or associated predictive buffer status report. The WTRU may perform UL data prediction. When the BSR trigger condition is met, the WTRU may transmit a predictive BSR. When UL resources are not available, the WTRU may be configured to store a predictive BSR. The WTRU may transmit a predictive BSR when resources become available (eg, if resources become available within a certain duration of time, etc.).

[0006] In an example, a WTRU may transmit an indication of its UL data prediction capability to a network. The WTRU may be in connected mode. The WTRU may receive an indication and / or configuration from the network regarding the UL data prediction model / capability to be used. The WTRU may receive a configuration regarding a predictive BSR configuration from the network (e.g., information to be included in the BSR, trigger conditions for the BSR, such as a buffer level threshold, an expected time range, and / or an expected confidence level, etc.). The WTRU may perform UL data prediction and / or monitor the predictive BSR trigger condition. As used herein, UL data prediction refers to a prediction of the amount of data that the WTRU will have ready to transmit in its buffer. The WTRU may also perform UL traffic prediction, wherein the UL traffic prediction may include predictions regarding data rate and / or rate of change of data rate, etc. Upon determining that the trigger condition is met, the WTRU may construct a predictive BSR (e.g., MAC CE) and may transmit the predictive BSR to the network.

[0007] In an example, a WTRU may include a processor and a transceiver configured to facilitate the following operations. The WTRU may be configured to transmit an indication of its UL data prediction capability to a network via the transceiver. The WTRU may be in connected mode. The WTRU may be configured to receive an indication and / or configuration of a UL data prediction model and / or capability to be used from the network via the transceiver. The WTRU may receive a configuration of a predictive BSR configuration from the network via the transceiver (e.g., information to be included in the BSR, trigger conditions for the BSR, such as a buffer level threshold, an expected time range, and / or an expected confidence level, etc.). The WTRU may be configured to perform UL data prediction and monitor the predictive BSR trigger condition. Upon determining that the trigger condition is met, the WTRU may be configured to construct a predictive BSR (e.g., a medium access control control element (MAC CE)) and / or may transmit the predictive BSR to the network.

[0008] In an example, the UL data prediction capability may include an error tolerance, a time range, an indication of accuracy, a confidence level, an interval, etc., or any suitable combination thereof.

[0009] Different logical channel groups (LCGs) may indicate separate prediction capabilities. Different entries in the same LCG may indicate separate prediction capabilities. The error tolerance value and / or percentage may be the same for each type of prediction within the same prediction time range. The accuracy and / or confidence level of the lower tolerance and / or upper tolerance of the error may be separated. The WTRU may be configured to transmit a predictive BSR including an indication of accuracy, confidence level and / or error tolerance. A WTRU and a method performed by the WTRU are described herein. In an example method for performing UL data prediction and reporting a predicted UL buffer status, a WTRU may receive predictive BSR configuration information. The predictive BSR configuration information may indicate an associated time frame and at least one trigger condition. The WTRU may predict the UL traffic corresponding to the associated time frame. The WTRU may determine that at least one of the at least one trigger condition has been met.

[0010] The WTRU may transmit a predictive BSR, wherein the predictive BSR may include an indication of predicted UL traffic. The predictive BSR may be transmitted via a MAC CE.

[0011] The WTRU may transmit an indication of the UL traffic prediction capability of the WTRU.The predictive BSR configuration may include information for predicting the UL traffic volume.

[0012] The predictive BSR configuration information may include at least one of artificial intelligence (AI) related information, machine learning (ML) related information, or a combination thereof. The AI ​​related information may include an AI model, and the ML related information may include an ML model. The AI ​​related information may include information about the identity of the AI ​​model, and the ML related information may include information about the identity of the ML model.

[0013] The associated time frame may include at least one of a time length for which the UL traffic is predicted and / or a time frame for which the UL traffic is predicted. The UL traffic may be predicted for a traffic type. The WTRU may predict the UL traffic based on at least one of historical traffic volume information, historical transmission time information, historical arrival rate information, historical WTRU location information, and / or historical WTRU trajectory information. The at least one trigger condition may include a UL traffic prediction confidence level, a UL traffic transmission time, and / or a UL traffic volume. The UL traffic corresponding to the associated time frame may be based on at least one of an artificial intelligence (AI) algorithm and / or a machine learning (ML) algorithm.

[0014] An example WTRU for performing UL data prediction and reporting predicted UL buffer status may include a processor and a transceiver. The processor may be configured to receive predictive BSR configuration information via the transceiver. The predictive BSR configuration information may indicate an associated time frame and at least one trigger condition.

[0015] The processor may be configured to predict the UL traffic volume corresponding to the associated time frame. The processor may be configured to determine that at least one of the at least one trigger condition has been satisfied. The processor may be configured to transmit a predictive BSR via the transceiver, wherein the predictive BSR may include an indication of the predicted UL traffic volume. The predictive BSR may be transmitted via a MAC CE. The processor may be configured to transmit an indication of the UL traffic prediction capability of the WTRU via the transceiver. The predictive BSR configuration may include information for predicting the UL traffic volume.

[0016] The predictive BSR configuration information may include at least one of artificial intelligence (AI) related information, machine learning (ML) related information, or a combination thereof. The AI ​​related information may include an AI model, and the ML related information may include an ML model. The AI ​​related information may include information about the identity of the AI ​​model, and the ML related information may include information about the identity of the ML model.

[0017] The associated time frame may include at least one of a time length for which the UL traffic is predicted and / or a time frame for which the UL traffic is predicted. The UL traffic may be predicted for a traffic type. The processor may be configured to predict the UL traffic based on at least one of historical traffic volume information, historical transmission time information, historical arrival rate information, historical WTRU location information, and / or historical WTRU trajectory information.

[0018] The at least one trigger condition may include a UL traffic prediction confidence level, a UL traffic transmission time, and / or a UL traffic volume. The UL traffic corresponding to the associated time frame may be based on at least one of an artificial intelligence (AI) algorithm and / or a machine learning (ML) algorithm. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are examples. Therefore, the drawings and specific embodiments should not be considered limiting, and other equally effective examples are possible and intended. The same reference numerals represent the same elements in the drawings.

[0020] Figure 1A is an example system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0021] Figure 1B is an example of a method that can be performed according to an embodiment of the present invention. Figure 1A An example system diagram of an example wireless transmit / receive unit (WTRU) for use within an example communication system.

[0022] Figure 1C is an example of a method that can be performed according to an embodiment of the present invention. Figure 1A An example system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) for use within an illustrated communication system.

[0023] Figure 1D is an example of a method that can be performed according to an embodiment of the present invention. Figure 1A An example system diagram of another example RAN and another example CN used within the illustrated communication system.

[0024] Figure 2 Example buffer status report (BSR) medium access control element (MAC CE), extended short BSR, and long BSR MAC CE formats are illustrated.

[0025] Figure 3 A table depicting example BSR buffer size levels in bytes for a 5-bit buffer size field.

[0026] Figure 4 A table depicting example BSR buffer size levels in bytes for an 8-bit buffer size field.

[0027] Figure 5 is an example illustration of communication between a wireless transmit / receive unit (WTRU) and a network.

[0028] Figure 6 is a flow chart depicting an example enhanced uplink (UL) scheduling mechanism.

[0029] Figure 7 is a flow diagram depicting an example uplink scheduling system. DETAILED DESCRIPTION

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

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

[0032] The communication system 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 that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0033] 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), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver 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 send and / or receive signals in a desired spatial direction.

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

[0035] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base stations 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. 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).

[0036] 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 Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

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

[0038] 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 together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0039] 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, CDMA2000EV-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), and GSM EDGE (GERAN).

[0040] Figure 1AThe base station 114b in may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial locations, homes, vehicles, campuses, industrial facilities, sky corridors (e.g., for use by drones), and roads. 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 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 a femtocell. As Figure 1A As shown, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0041] 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Figure 1A Although not shown in the figure, 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 utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0042] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication 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.

[0043] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.

[0044] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, 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. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0045] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC) and state machine, etc. The processor 118 may perform signal decoding, 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0046] The send / receive element 122 can be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station by air interface 116. For example, in one embodiment, the send / receive element 122 can be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 can be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 can be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 can be configured to send and / or receive any combination of wireless signals.

[0047] Although the transmit / receive element 122 Figure 1B Although depicted as a single element in the figure, 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.

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

[0049] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a 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, and a secure digital (SD) memory card, among others. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0050] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control 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, etc.

[0051] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0052] The processor 118 may be further coupled to other peripherals 138, which may include one or more software modules 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 electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, and an activity tracker, etc. The peripheral device 138 may include one or more sensors, which may be one or more of the following: 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.

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

[0054] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with 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.

[0055] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0056] Each of the evolved Node 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, and scheduling of users in the UL and / or DL, among other things. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0057] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0058] The MME 162 may be connected to each of the evolved Node-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 and / or deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. 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.

[0059] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an 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 the user plane during an inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

[0061] 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 be in communication with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0062] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

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

[0064] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries the service to and / or out of the BSS. Services to STAs from outside the BSS may be reached by the AP and may be delivered to the STAs. Services to destinations outside the BSS from STAs may be transmitted to the AP to be delivered to the respective destinations. Services between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit services to the AP, and the AP may deliver services to the destination STA. Services between STAs within the BSS may be considered and / or referred to as point-to-point services. Point-to-point services may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0065] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can send beacons on a fixed channel (such as a primary channel). The primary channel can be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel can be an operating channel of the BSS and can be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) can listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a specific STA, the specific STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0066] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0067] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be individually processed by inverse fast Fourier transform (IFFT) and time domain processing. These streams can be mapped to two 80MHz channels, and the data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0068] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0069] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum 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 (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only 1MHz operating mode) is sending to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

[0070] In the United States, the available frequency bands for 802.11ah are 902MHz to 928MHz. In South Korea, the available frequency bands are 917.5MHz to 923.5MHz. In Japan, the available frequency bands are 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0071] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 in accordance with an embodiment. As noted above, the RAN 113 may employ 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.

[0072] 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 being 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, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send 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 an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and the gNB 180b (and / or the gNB 180c).

[0073] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, 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 the gNBs 180a, 180b, 180c using subframes or transmit time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths).

[0074] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as an evolved Node-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0075] 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 UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b and routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0076] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0077] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling and mobility management, etc. The AMF 182a, 182b may use network slicing in order to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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 mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. 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.

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

[0079] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the 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, and providing mobility anchoring, etc.

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

[0081] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with respect to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0082] The simulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices can perform one or more functions 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. One or more simulation devices can perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to another device for testing purposes and / or can use over-the-air wireless communications to perform testing.

[0083] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication performed via an RF circuit system (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0084] Methods and apparatus for performing communications between a WTRU and / or a network are described herein. These communications may provide uplink (UL) scheduling for a WTRU that includes UL data prediction capabilities. Thus, the WTRU may communicate expected UL traffic to the network via a predictive buffer status report (BSR). The network may use this information for UL scheduling. The network may utilize information about predicted traffic as input to a network artificial intelligence / machine learning (AI / ML) model for processing mobility optimization, load balancing, and / or generally any SON (self-organizing network) function.

[0085] As described herein, the term AI / ML is used to describe any model and / or associated learning algorithm used, for example, by a WTRU and / or a network to predict future behavior (e.g., behavior at the WTRU and / or arrival of data to be transmitted to the network). The model and / or associated learning algorithm may utilize a large data set collected by the WTRU and / or the network. The terms "anticipate," "expect," "estimate," "predictive," and / or "predict" (and / or their adverbial variations) may be used interchangeably. The term "time frame" may be used to refer to the time at which the predicted UL data is expected to arrive (e.g., be ready to be transmitted by the WTRU) after the predicted BSR is received. The term "normal BSR" may be used to describe a BSR report that is triggered based on UL data arriving at the WTRU (e.g., a regular BSR, a filler BSR, and / or a periodic BSR, etc.).

[0086] The process of scheduling in New Radio (NR) may involve a base station (e.g., a next generation Node B (gNB), etc.). Scheduling may involve a medium access control (MAC) entity of the gNB. The gNB may be responsible for scheduling both UL physical resources and downlink (DL) physical resources in NR. In order to achieve resource efficient usage of the radio resources of the network and / or to achieve resource efficient usage fairly among different WTRUs served by the gNB, the gNB may utilize various types of information.

[0087] For example, the gNB may utilize buffer status associated with the WTRU (e.g., pending data to be sent at the gNB in ​​the WTRU's DL or UL buffer status reported by the WTRU, etc., or any suitable combination thereof, etc.). The gNB may utilize QoS requirements for each WTRU and associated radio bearers. Radio conditions at the WTRU (e.g., identified by measurements made at the gNB and / or reported by the WTRU). The gNB may utilize power headroom at the WTRU, which may include the difference between the WTRU's maximum transmit power and the estimated power for UL transmissions (e.g., as indicated in a power headroom report from the WTRU).

[0088] The gNB may use this information when making scheduling decisions in the UL and / or DL ​​(e.g., which WTRU(s) get which UL / DL resources to transmit and / or receive). The gNB may accomplish scheduling in a dynamic manner (e.g., the scheduled WTRUs and / or the resources assigned to these WTRUs may change from one radio slot and / or frame to another). Additionally or alternatively, the gNB may accomplish scheduling in a persistent manner (e.g., allocating a certain set of radio resources to a WTRU or a group of WTRUs in the UL and / or DL ​​for a given time). In NR, persistent scheduling in the UL may be referred to as configured grant, and persistent scheduling in the DL may be referred to as semi-persistent scheduling (SPS).

[0089] The gNB may dynamically allocate resources to the WTRU via the Cell Radio Network Temporary Identifier (C-RNTI) on the Physical Downlink Control Channel (PDCCH). The WTRU may monitor the PDCCH for possible grants for UL transmissions. When carrier aggregation (CA) is configured, the same C-RNTI may apply to all serving cells.

[0090] The gNB may cancel a Physical Uplink Control Channel (PUSCH) transmission and / or a repetition of a PUSCH transmission or a Sounding Reference Signal (SRS) transmission of the WTRU for another WTRU having a latency critical transmission. The gNB may configure the WTRU to monitor for the cancelled transmission indication using the CI-RNTI on the PDCCH.

[0091] Alternatively or additionally, with configured grants, the gNB may allocate UL resources to the WTRU for initial hybrid automatic repeat request (HARQ) transmissions and HARQ retransmissions.

[0092] In an example configuration, the WTRU may be configured with up to 12 active configured UL grants for a given bandwidth part (BWP) of a serving cell. When more than one UL grant is configured, the network may decide which of these configured uplink ULs is active at a time. One or more or all uplink grants may be active at a time. Each configured UL grant may be of type 1 or type 2.

[0093] For Type 2, activation and / or deactivation of configured UL grants may be independent among serving cells. When more than one Type 2 configured grant is configured, each configured grant may be activated individually using a downlink control information (DCI) command. Deactivation of a Type 2 configured grant may be accomplished using a DCI command. The DCI command may deactivate a single configured grant configuration or deactivate multiple configured grant configurations jointly.

[0094] The UL BSR may be used to provide support for QoS-aware packet scheduling. In NR, the BSR may be reported at a logical channel group (LCG) granularity. In an example configuration, the WTRU may be configured with up to 32 logical channel IDs (LCIDs) which may be grouped into up to 8 LCGs. In various example configurations, the WTRU may be configured with more than 32 LCIDs and more than 8 LCGs (e.g., a mobile terminal (MT) of an integrated access and / or backhaul (IAB) node may be configured with up to 65,855 LCIDs and / or 256 LCGs).

[0095] The BSR may be transmitted in any combination of formats, including: a short BSR format for reporting data for only one LCG and / or a long BSR format for reporting data from several LCGs.

[0096] The MAC CE may send a BSR. When a BSR is triggered (eg, when new data arrives at the WTRU's transmit buffer), and when the WTRU does not have any available UL grant to transmit the BSR, the WTRU may send a Scheduling Request (SR) to request UL resources to transmit the BSR.

[0097] Figure 2Example BSR formats for a short buffer status report (BSR) medium access control element (MAC CE) 202, an extended short BSR 204, and a long BSR MAC CE 206 are illustrated. There are several variations of the short BSR 202 and long BSR 206 (e.g., for the case of IAB MT), a subset of which are described in Figure 2 The identifier octet 1, octet 2, octet 3, ... octet m+1 represents the number of octets.

[0098] To reduce signaling overhead in the BSR, a buffer level index is used instead of the actual buffer size, where the buffer level index corresponds to a range of buffer sizes. The buffer size included in the BSR report can be based on Figure 3 300 depicted in (eg, the WTRU may include an index corresponding to the buffer size of the corresponding LCG). Figure 3 Table 300 depicts example BSR buffer size levels in bytes for a 5-bit buffer size field.

[0099] Similarly, Figure 4 Depicted is a table 400 illustrating buffer size levels (in bytes) for an 8-bit buffer size field.

[0100] RRC may configure the following parameters to control BSR: periodicBSR-Timer; retxBSR-Timer; logicalChannelSR-DelayTimerApplied; logicalChannelSR-DelayTimer; logicalChannelSR-Mask; and / or logicalChannelGroup.

[0101] The MAC entity may determine the amount of UL data available for a logical channel based on data volume calculation procedures performed at the Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP). When performing the data volume calculation, the RLC may include RLC data protocol data units (PDUs) pending for transmission or retransmission, RLC service data units (SDUs) (or segments of RLC SDUs not yet included in an RLC data PDU), and / or any pending RLC status PDUs. The data volume calculation at the PDCP may take into account PDCP SDUs for which PDCP data PDUs have not yet been constructed, PDCP data PDUs that have not yet been sent to lower layers, any PDCP control PDUs, and / or any PDPC SDUs and / or PDUs to be retransmitted due to PDCP reestablishment or PDCP data recovery.

[0102] The WTRU may trigger a BSR if any combination of events occurs. One such event may include when UL data for a logical channel belonging to an LCG becomes available to the MAC entity. The UL data may belong to a logical channel with a higher priority than any logical channel containing available UL data belonging to any LCG, and / or any logical channel belonging to the LCG does not contain any available UL data. In either case, the BSR is referred to as a "regular BSR";

[0103] In an example, another such event may occur when UL resources are allocated and the number of padding bits is equal to or greater than the size of the BSR MAC CE plus its subheader. In this instance, the BSR is referred to as a "padding BSR".

[0104] In an example, another such event may occur when the retxBSR-Timer expires and / or at least one of the logical channels belonging to the LCG contains UL data. In this instance, the BSR is also referred to as a "regular BSR".

[0105] In the example, another such event may occur when the periodicBSR-Timer expires. In this example, the BSR is also referred to as a "periodic BSR".

[0106] When a regular BSR triggering event occurs simultaneously for multiple logical channels, each logical channel may trigger a separate regular BSR.

[0107] Figure 5 is an example illustration of communication between a wireless transmit / receive unit (WTRU) and a network. Figure 5 As depicted, in NR, at 502, the WTRU may receive a UECapabilityEnquiry message from the network. Then, at 504, the WTRU may compile and / or communicate its WTRU capability information (e.g., supported frequencies, supported radio access technologies and / or processing capabilities, etc.) upon receiving the UECapabilityEnquiry message from the network by transmitting a UECapabilityInformation message.

[0108] When the network requires (e.g., additional) WTRU radio access capability information, the network may initiate a procedure to the WTRU in RRC_CONNECTED mode. In an example, the network may retrieve WTRU capabilities after AS security activation, and the network may not forward WTRU capabilities retrieved before AS security activation to the core network (CN).

[0109] The WTRU capabilities may be requested for a radio access technology (RAT) type (e.g., NR, Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (EUTRA), etc.). Additional filters may also be included in the capability request to limit the UL signaling, since the size of all WTRU capability information may be quite large. Additionally, the network may already have some of the capability information in the WTRU capability information (e.g., an earlier capability transfer from the WTRU and / or an earlier capability transfer from the CN, etc.).

[0110] As discussed herein, the NR UL scheduling mechanism may rely on receiving a UL BSR from the WTRU. The WTRU may transmit the UL BSR after data has arrived at the WTRU and is waiting to be transmitted. Scheduling based on such a request and / or grant mode of operation may result in high latency and / or a large amount of UL signaling, which may impact delay intolerant services. The network may provide configured grants that may be available over a longer duration to mitigate latency issues with request and / or grant based scheduling. However, inconsistent UL data rates may result in inefficient use of UL resources.

[0111] Figure 6 is a flow chart 600 depicting an example enhanced uplink (UL) scheduling mechanism. Figure 6 Methods and apparatus are illustrated for enhancing UL scheduling mechanisms that may benefit from WTRU information regarding expected and / or desired UL data traffic.

[0112] The WTRU may communicate the expected UL traffic to the network via a predictive BSR. The network may use the information in the predictive BSR to facilitate UL scheduling. In an example, the network may use any information about the predicted traffic as input to the network AI / ML model for handling mobility optimization, load balancing, and / or generally any SON (self-organizing network) functions.

[0113] Figure 7700 is a flowchart depicting another example uplink scheduling system. At 702, the WTRU notifies the network of UL data prediction capabilities. At 704, the WTRU may receive a configuration related to a predictive BSR from the network. At 706, the WTRU may perform UL data arrival protection. At 708, the WTRU may determine whether the conditions for transmitting a predictive BSR are met. The information that the WTRU may consider when making the determination may include, for example, reporting periodicity, whether the predictive BSR may be reported together with a regular BSR, a periodic BSR, or a filler BSR and / or reported separately. The information that the WTRU may consider when making the determination may include priority ranking compared to normal BSRs. If there is a predictive BSR for an LCID / LCG with a higher priority compared to a normal BSR for an LCID / LCG with a lower priority, and / or the WTRU has an UL grant available to transmit only a normal BSR and / or a predictive BSR, the WTRU may prioritize the predictive BSR. The information that the WTRU may consider when making the determination may include timeline settings, for example, how far in the future the prediction may occur. The configuration may include thresholds for reporting, such as only if the buffer size is expected to be above or below a certain threshold or range of values.The information that the WTRU may consider in making the determination may include an indication of the required prediction confidence level.

[0114] At 710, the WTRU may transmit a predicted BSR to the network (e.g., periodically and / or when a trigger threshold is met, etc.). The predicted BSR may contain one or more sets of the following information: data volume (average, minimum, maximum, range, etc.); estimated arrival time (e.g., precise timestamp, delta time, precise / delta time range, etc.); and / or prediction confidence level (e.g., probability value or value range). At 712, the WTRU receives an UL resource grant.

[0115] The WTRU may indicate to the network its ability to perform UL data prediction. For example, the WTRU may indicate to the network its ability based on a WTRU capability transfer (e.g., the network transmits UECapabilityEnquiry 502 and the WTRU responds with UECapabilityInformation 504, such as Figure 5). An information filtering capability related to UL data prediction for the WTRU may be introduced in the UECapabilityEnquiry 502 message. The capability information may be as simple as a binary "yes / no". A response of "no" may indicate that the WTRU is not capable of UL data prediction (e.g., predicting how much data will be in the WTRU's buffer before transmitting the data). Therefore, the WTRU may not need to be configured to generate a predictive BSR. A response of "yes" may indicate that the WTRU is capable of UL data prediction (e.g., predicting how much data will be in the WTRU's buffer before transmitting the data). The "yes" response indicates to the network that the network may transmit to the WTRU a configuration specifying the transmission of a predictive BSR (e.g., when to trigger a predictive BSR and / or what information to include in the predictive BSR, etc.). A response of "yes" may also contain details about the type of predictions that the WTRU may make.

[0116] The response may be more detailed and include, for example, the following information, including the prediction time range (e.g., the WTRU may predict UL data up to xms in advance). In an example, the WTRU may indicate the capability based on the prediction time window length (e.g., data is expected to arrive at the earliest xms and at the latest yms). The response may include a confidence level in the prediction (e.g., the WTRU is 95% confident in the prediction). The response may include the time duration for which the prediction applies (e.g., the WTRU may be able to provide accurate predictions only during certain times of the day, such as 7:30am and 8:00am). The response may include the location for which the prediction applies (e.g., a range of Global Navigation Satellite System (GNSS) / GPS coordinates, a set of cell IDs, etc.).

[0117] The response may include the predicted granularity. The predicted granularity may contain information including an increment (plus or minus) to be applied to determine the range of expected data (e.g., an increment of d indicates that the network should consider expected data rates between rd and r+d, where r is the reported expected data rate from the WTRU). In an example, the WTRU may report a range of values ​​without communicating the increment. The information may include the level of granularity, such as whether the level of granularity is at the LCG level, at a finer granularity at the LCID level, at a coarser granularity at the total UE buffer level, and / or somewhere in between.

[0118] The WTRU may indicate multiple UL data prediction capabilities to the network. For example, a first capability (e.g., capability 1) may include prediction up to x1ms ahead, confidence level c1, time duration t1, location l1, and / or granularity of total UL buffer level. In an example, a second capability (e.g., capability 2) may include prediction up to x2ms ahead, confidence level c2, time duration t2, location l2, and / or granularity of LCG.

[0119] The WTRU may indicate to the network whether the WTRU can perform prediction based on only one prediction capability at a given time. Alternatively or additionally, the WTRU may perform multiple predictions at a time. For example, the WTRU may indicate that it is able to perform UL data prediction at a given time based on any combination of conditions. These conditions may include only one of the indicated capabilities, a subset of the indicated capabilities (e.g., capability 1 and capability 2, capability 1 and capability 3, capability 2, capability 4 and capability 5, etc.), all indicated capabilities when some capabilities are not adopted together (e.g., capability 1 and capability 3 cannot be used at the same time), and / or all indicated capabilities. If the WTRU is unable to perform prediction based on all of its capabilities at once, the WTRU may indicate to the network the preferred levels of different capabilities and / or capability sets that can be adopted together.

[0120] The network may indicate to the WTRU the UL data prediction capability(s) to be adopted. For example, once the network has received an indication that the WTRU supports a certain number of UL data prediction capabilities, the network may configure the WTRU to operate UL data prediction. The network may indicate to the WTRU to perform UL data prediction (simultaneously) according to more than one UL prediction capabilities. The network may indicate to the WTRU to perform UL data prediction according to more than one UL prediction capabilities. The WTRU may indicate (one or more) selected capabilities in a response message. For example, the network may indicate to the WTRU to predict UL traffic according to capability 1 or capability 2. The WTRU may select an appropriate capability (e.g., capability 1 or capability 2) and transmit a message indicating the selected prediction capability to the network. The network may indicate to the WTRU to perform UL data prediction according to more than one UL prediction capability. The network may include further constraints on when the WTRU should perform UL prediction according to the indicated capabilities. For example, the network may indicate to the WTRU that it has capability 1 for use during a specific time period (e.g., between 8am and 8:30am) and / or specific locations (e.g., range of GNSS locations, cell identities, being served by certain RATs and / or frequencies simultaneously, etc.). Additionally or alternatively to absolute time and / or location constraints, the network may indicate relative constraints (e.g., delta time and / or location from the current time and / or location).

[0121] A combination of the above two examples may be configured (eg, the network may implement constraints on when / where predictions are performed and / or reported, such as, for example, time and / or location). The WTRU may decide which prediction capability to employ.

[0122] The RRC message may indicate to the WTRU the configuration of the capability(s) to be used for UL data prediction. The MAC CE may indicate to the WTRU the configuration of the capability(s) to be used for UL data prediction. The DCI may indicate to the WTRU the configuration of the capability(s) to be used for UL data prediction.

[0123] The network may configure the WTRU with an AI / ML model for UL data prediction. In addition to the UL data prediction model, the network may also configure the WTRU with conditions for when to transmit a predicted BSR. These conditions may be based on inferences from the model (such as, for example, immediately), as soon as a trigger condition is met, after the WTRU has completed training the model for some specified duration, after the WTRU has compared the predicted UL data values ​​with the actual values ​​and / or has determined that the accuracy and / or confidence level is above a configured threshold, etc.

[0124] The WTRU may be configured with an AI / ML model for UL data prediction, wherein specific inputs to the AI / ML model are preconfigured. For example, the WTRU may be configured to input historical data volume, timestamp, data arrival rate, etc. for a preconfigured LCID and / or LCG (see, e.g. Figure 6 In step 626 of FIG. 1 , the WTRU may be configured with an AI / ML model dedicated to an LCG. For example, the WTRU may be configured with multiple AI / ML models. The WTRU may apply different AI / ML models to different LCGs.

[0125] The WTRU may consider selecting capability(s) to be used by the network for UL prediction. The WTRU may make this consideration to start UL data prediction and / or reporting based on the selected and / or indicated capability(s). In an example, if constraints (e.g., time and / or location, etc.) are configured for the prediction described herein, the WTRU may perform prediction and / or reporting only under those constraints.

[0126] The WTRU may wait to receive an additional explicit activation message and / or indication to start UL data prediction reporting. If more than one capability is selected and / or configured, the capability(s) for UL data prediction and / or reporting may be included in the activation message and / or indication. If more than one capability is selected and / or configured, the network may indicate to the WTRU with an explicit flag to employ all capabilities at once, rather than including all selected capabilities individually.

[0127] The WTRU may receive a deactivation message and / or indication to stop performing and / or reporting UL data prediction. If more than one capability is activated, the capability(s) that are deactivated for UL data prediction and / or reporting may be included in the deactivation message and / or indication. If more than one capability is activated and the network wants to stop all UL prediction and / or reporting, the network may indicate this stopping of all UL prediction and / or reporting using an explicit flag instead of individually including all prediction capabilities to be deactivated. In an example, the WTRU may perform activation and / or deactivation and / or reporting of UL prediction upon receiving such a message.

[0128] Additional information may be included in the activation and / or deactivation message to indicate when the message should take effect. For example, a delta time may be included in the deactivation message and the WTRU may wait until the indicated delta time has passed after receiving the deactivation message before deactivating UL data prediction and / or reporting (according to the indicated capabilities or all UL data prediction (if indicated)). Activation and / or deactivation signaling may be performed via RRC. MAC CE may be used for activation and / or deactivation signaling. DCI may be used for activation and / or deactivation signaling.

[0129] The logical channel groupings used for a predicted BSR may be the same as those used for a normal BSR. Different logical channel groupings may be used for a predicted BSR than for a normal BSR. For example, in addition to the traditional logicalChannelGroup IE, a new information element (IE) may be introduced in the logical channel group configuration indicating the LCG ID for a given logical channel. The UL buffer level index may include any appropriate buffer level index, such as, for example, a current buffer level index, a new buffer level index, and / or any combination thereof. A new UL buffer level index may be used for a predictive BSR (e.g., having less or more granularity and / or size limit than that of a normal BSR).

[0130] The WTRU may be configured to transmit a predicted UL buffer status report periodically. The periodicity for the predicted UL buffer status may be configured as the same periodicity of a normal BSR. The periodicity may be implicitly assumed (e.g., the WTRU implicitly assumes the periodicity of the normal BSR to report the predicted BSR). The periodicity may be explicitly indicated to the WTRU (e.g., a flag in the predicted UL buffer status report configuration indicates that the WTRU uses the same periodicity as the normal BSR). The periodicity for the predicted UL buffer status may be configured to be different from the normal BSR. The WTRU may be configured to apply similar behavior as in a regular BSR for a normal BSR, for example, when new data is expected to arrive in the UL buffer, the new data has a higher priority than the data already waiting in the buffer. The WTRU may be configured to transmit a predicted BSR report when new data is expected to arrive in the UL buffer. The data may have the same or even lower priority than the data already waiting in the buffer, depending on the expected buffer size of the new data (e.g., whether the data exceeds a certain configured threshold).

[0131] The WTRU may be configured to transmit a predicted BSR report when new data is expected to arrive in the UL buffer, with the same or even lower priority than the data already waiting in the buffer, depending on the difference between the expected buffer size of the new data and the data already waiting in the buffer for high priority data (e.g., if the difference is above some configured threshold). The buffer level threshold for triggering a predicted BSR may be configured to be the same for all LCGs, or different for each LCG. The buffer level threshold for triggering a predicted BSR for a certain LCG may be configured as the predicted UL buffer for that LCG plus the current UL buffer level for that LCG. The buffer level threshold for triggering a predicted BSR may be configured as the total predicted UL buffer (e.g., over all LCGs). The buffer level threshold for triggering a predicted BSR may be configured as the total predicted UL buffer (e.g., over all LCGs) plus the current total UL buffer level.

[0132] The triggering of the predicted BSR may be configured to be controlled by the desired confidence level of the prediction. For example, the network may authorize the WTRU to make predictions based on any capability. The network may configure the WTRU to report only when the confidence level exceeds a certain desired threshold. The triggering of the predicted BSR may be configured to be controlled by the desired time range of the prediction. For example, the network may allow the WTRU to be authorized to make predictions based on any capability. The network may configure the WTRU to report predictions within the configured time range of the prediction report (e.g., only transmit predictions about the next xms, only transmit predictions about the time period between xms and yms, and / or only transmit predictions about the time period after yms, etc.).

[0133] The predicted UL buffer status report may include only the buffer level index. The network may find information about the confidence level and / or time range, etc. implicitly from the capability indication from the WTRU. The network may also discover information from the corresponding configuration transmitted by the network to the WTRU and / or any further indication received from the WTRU, as discussed herein. The predicted UL buffer status report may include an indication of the UL prediction capability corresponding to the report in question (e.g., a prediction capability ID). The network may use the indication to determine the confidence level and / or time range, etc. from the capability information previously indicated from the WTRU. The predicted UL buffer status report may include an indication of the time range for UL prediction, the confidence level for UL prediction, and / or a range of prediction values, rather than an indication of a given value and / or buffer index level (e.g., between level 1 and level 2). The predicted UL buffer status report may include several values ​​and / or value ranges for a given LCG (e.g., with different time ranges, confidence levels, and / or value ranges). One of the LCID values ​​reserved in the MAC specification (eg, an LCID between 35 and 44) ​​may indicate that the BSR is a predictive BSR.

[0134] In an example, if there are available UL resources (e.g., no SR is triggered for transmitting a predicted BSR), the WTRU may transmit a predicted BSR. The WTRU may transmit the predicted BSR as a filler BSR. Upon determining that there are no resources to transmit the predicted BSR, the WTRU may discard the predicted BSR. Upon determining that there are no resources to transmit the predicted BSR, the WTRU may store the predicted BSR and / or transmit the predicted BSR when UL resources become available. When a predicted BSR is triggered and another predicted BSR is to be transmitted, the WTRU may discard the old predicted BSR and / or store the new predicted BSR for transmission when UL resources become available. When a predicted BSR is triggered and another predicted BSR is to be transmitted, the WTRU may discard the new predicted BSR and / or keep the old predicted BSR for transmission when UL resources become available.

[0135] When a predicted BSR is triggered and another predicted BSR is to be transmitted, the WTRU may compare the two BSRs and / or decide to keep one BSR. For example, the WTRU may keep the BSR that is triggered due to a higher priority LCID and / or LCG, the BSR that includes information about the higher priority LCID and / or LCG, and / or the BSR that indicates a higher buffer threshold, etc.

[0136] When a predicted BSR is triggered and another predicted BSR is to be transmitted, the WTRU may combine the two BSRs. For example, if the two BSRs are separate (e.g., the two BSRs do not involve the same LCG), the WTRU may append the two BSRs together in a long BSR format if the two BSRs have a common portion (e.g., one or more LCGs included in the two BSRs are the same). In the case where the two BSRs have a common portion (e.g., one or more LCGs included in the two BSRs are the same), the WTRU may include the two BSRs in a new BSR format that includes multiple entries for the same LCG but with different time ranges. In the case where the two BSRs have a common portion (e.g., one or more LCGs included in the two BSRs are the same), the WTRU may reserve one entry for the combined BSR with a buffer value corresponding to the first BSR (e.g., an earlier time range). The WTRU may reserve one entry for the combined BSR with a buffer value corresponding to the BSR indicating a higher confidence level.

[0137] The WTRU may be configured with a threshold time duration (e.g., a storage timer) that a predicted BSR may be kept pending. When a predicted BSR is triggered, the timer may be started. If the timer expires before the predicted BSR is transmitted, the WTRU may discard the predicted BSR. The threshold time duration for keeping a pending BSR may be related to the predicted time range (e.g., equal to the time range and / or a specified portion of the time range, etc.). The threshold time duration for keeping a pending BSR may not be related to the predicted time range and / or may be configured separately.

[0138] A WTRU configured to store a predictive BSR for a certain duration and / or until UL resources are available as disclosed herein may be configured to include information that the BSR has been delayed (when the BSR is transmitted later). For example, the WTRU may include information in the MAC CE header describing how long the BSR has been waiting to be transmitted. If time range information is included in the BSR, the WTRU may update the time range information. The WTRU may update the time range information to reflect the time when the data indicated in the BSR is expected.

[0139] Upon determining that there are no available UL resources, the storage of predicted BSRs may be subject to configured conditions. These configured conditions may include, for example, the buffer level in the BSR in question (e.g., only BSRs indicating a buffer level above a configured threshold, below a configured threshold, and / or within a configured threshold are stored); the predicted time range; the explicit time window (e.g., the WTRU is configured to only store predictive BSRs made between time 1 and time 2, where these times refer to absolute times); the LCG and / or LCID that triggered the BSR (e.g., only store the BSR if the BSR was triggered due to certain LCGs and / or LCIDs and / or sets of LCGs and / or LCIDs); the LCGs and / or LCIDs included in the BSR (e.g., only store the BSR if the BSR contains information about certain LCGs and / or LCIDs and / or sets of LCGs and / or LCIDs); and the amount of pending BSRs that have been stored and / or are yet to be transmitted (e.g., only store a newly triggered BSR if the size of the stored pending BSRs is below a certain threshold).

[0140] The WTRU may be configured to keep the predictive BSRs even after the storage timer has expired, but not transmit these predictive BSRs immediately when UL resources become available. Instead, the WTRU may transmit an indication to the network that the WTRU has stored the predictive BSRs (e.g., including information such as the number of stored BSRs, the time when these BSRs were generated, and / or the size of the BSRs). The WTRU may be configured to keep the predictive BSRs even after the storage timer has expired, but not transmit these predictive BSRs immediately when UL resources become available. Instead, the WTRU may wait for an explicit request from the network to transmit the stored BSRs.

[0141] Starting a timer (e.g., delay and / or prohibit timer) whenever a predictive BSR is transmitted may prevent frequent predictive BSRs from being transmitted. The WTRU may be configured with one timer value for all predictive BSRs regardless of the LCG and / or LCID that triggered the BSR. The WTRU may start the timer whenever any predictive BSR is transmitted and / or avoid transmitting another predictive BSR before the currently running timer expires. The WTRU may be configured with separate timer values ​​for predictive BSRs triggered for each LCID and / or LCG. The WTRU may start a timer with a value corresponding to the timer associated with the LCID and / or LCG that triggered the predictive BSR. The WTRU may start the timer whenever any predictive BSR is transmitted and may avoid transmitting another predictive BSR before the currently running timer expires.

[0142] The WTRU may be configured with one timer value for all predictive BSRs regardless of the LCG and / or LCID that triggered the BSR. The WTRU may start this timer whenever any predictive BSR is transmitted. While this timer is running, the WTRU may avoid transmitting another predictive BSR that is also triggered due to the same LCID and / or LCG as the last transmitted predictive BSR. If a new predictive BSR is triggered due to a different LCID and / or LCG than the one that triggered the last transmitted predictive BSR, the WTRU may start the currently running timer and / or transmit the BSR.

[0143] The WTRU may be configured with a separate timer value for a predictive BSR triggered for each LCID and / or LCG. Whenever any predictive BSR is transmitted, the WTRU may start a timer with a value corresponding to the timer associated with the LCID and / or LCG that triggered the predictive BSR. While the timer is running, the WTRU may avoid transmitting another predictive BSR that is also triggered due to the same LCID and / or LCG as the last transmitted predictive BSR. If a new predictive BSR is triggered due to a different LCID and / or LCG than the LCID and / or LCG that triggered the last transmitted predictive BSR, the WTRU may stop the currently running timer and / or transmit the BSR. The WTRU may restart the timer with the value corresponding to the LCID and / or LCG involved.

[0144] The WTRU may be configured with a timer value for predictive BSRs triggered due to some specific LCIDs and / or LCGs. The inhibit timer may not be used for the remaining LCIDs and / or LCGs. The WTRU may start the timer whenever a triggered predictive BSR is associated with a delay timer. The WTRU may avoid transmitting another predictive BSR triggered by the LCID and / or LCG associated with the delay timer until the currently running delay timer expires. Predictive BSRs triggered by LCIDs and / or LCGs that are not associated with the timer may not be affected by the timer (e.g., the predictive BSR will be transmitted regardless of whether the delay timer is running), and / or the WTRU may stop the inhibit timer (if running) when transmitting the BSR.

[0145] The WTRU may be configured with a timer value for predictive BSRs triggered due to some specific LCIDs and / or LCGs, while the prohibit timer may not be used for the remaining LCIDs and / or LCGs. Whenever a predictive BSR associated with a delay timer is triggered, the WTRU may start the timer. Before the currently running delay timer expires, the WTRU may avoid transmitting another triggered predictive BSR through the same LCID and / or LCG as the last predictive BSR. Regardless of whether the LCID and / or LCG has an associated timer, predictive BSRs that are not triggered due to LCIDs and / or LCGs that are different from the last LCID and / or LCG that triggered the BSR may not be affected. For example, a predictive BSR may be transmitted regardless of whether the delay timer is running. When transmitting a predictive BSR triggered due to an LCID and / or LCG that does not have an associated timer, the WTRU may stop running the prohibit timer. If the LCID and / or LCG has an associated delay timer, the WTRU may restart the timer with a value corresponding to the delay timer associated with the LCID and / or LCG.

[0146] The WTRU may be configured with separate timer values ​​for predictive BSRs triggered due to some specific LCIDs and / or LCGs, while the inhibit timer may not be used for the remaining LCIDs and / or LCGs. The WTRU may apply behavior similar to that described herein for the case of one timer value. However, whenever the timer is started, the value of the timer associated with the LCID and / or LCG that triggered the predictive BSR may be used.

[0147] The delay timer value used may not be the delay timer value associated with the LCG and / or LCID that triggered the predictive BSR. The delay timer may be the maximum delay timer value among all delay timer values ​​configured for other LCIDs and / or LCGs included in the predictive BSR to be transmitted.

[0148] The delay timer value used may not be the delay timer value associated with the LCG and / or LCID that triggered the predictive BSR. The delay timer may be the minimum delay timer value among all delay timer values ​​configured for other LCIDs and / or LCGs included in the predictive BSR to be transmitted.

[0149] The delay timer value used may not be the delay timer value associated with the LCG and / or LCID that triggered the predictive BSR. The delay timer may be the average delay timer value of all delay timer values ​​configured for other LCIDs and / or LCGs included in the predictive BSR to be transmitted. The timer value may be specified for a normal BSR and / or a predictive BSR.

[0150] When the running BSR delay timer is started due to a normal BSR, the WTRU may avoid transmitting a normal BSR. The WTRU may still transmit a newly triggered predictive BSR when such timer is running. The WTRU may avoid transmitting only a predictive BSR when the running BSR delay timer is started due to a predictive BSR. The WTRU may still transmit a newly triggered normal BSR when such timer is running. Whenever the running BSR delay timer is started due to the transmission of a normal BSR, the WTRU may avoid transmitting any BSR (e.g., a normal BSR and / or a predictive BSR). Whenever the running BSR delay timer is started due to the transmission of a predictive BSR, the WTRU may avoid transmitting any BSR (e.g., a normal BSR and / or a predictive BSR). Whenever the BSR delay timer is running (e.g., whether the previous BSR transmitted was a normal BSR and / or a predictive BSR), the WTRU may avoid transmitting any BSR (e.g., a normal BSR and / or a predictive BSR).

[0151] If a normal BSR and / or a predicted BSR are triggered simultaneously, the WTRU may delete the predicted BSR and attempt to transmit only the normal BSR; the WTRU may delete the normal BSR and attempt to transmit only the predicted BSR; and / or the WTRU may prioritize transmitting the normal BSR. For example, the predictive BSR may not be transmitted at all and / or may be transmitted only if UL resources are still available after the transmission of the normal BSR. For example, the normal BSR may be transmitted first and / or wait to transmit the predictive BSR until additional UL resources become available. If UL resources are not available to transmit even a normal BSR, an SR indicating the availability of the normal BSR may be transmitted. If UL resources are not available to transmit even a normal BSR, an SR indicating the availability of both the normal BSR and / or the predictive BSR may be transmitted.

[0152] If a normal BSR and / or a predicted BSR are triggered at the same time, the WTRU may decide which BSR to prioritize. If a normal BSR and / or a predicted BSR are triggered at the same time, the WTRU may prioritize the BSR triggered due to the LCID and / or LCG with a higher priority. If a normal BSR and / or a predicted BSR are triggered at the same time, the WTRU may combine the BSR reports from both the normal BSR and / or the predicted BSR. The WTRU may include the buffer size in the BSR report based on the LCID and / or LCG priority, regardless of whether the size is predicted and / or actual using some indication of the BSR type. In the case where a normal BSR and / or a predicted BSR belong to the same LCID and / or LCG, the WTRU may only include the normal BSR for such LCID and / or LCG. If a normal BSR and / or a predicted BSR are triggered at the same time, the WTRU may prioritize the predictive BSR if the indicated buffer level (for a given LCID and / or LCG or the total buffer level) exceeds a certain configured threshold. If a normal BSR and / or a predicted BSR are triggered simultaneously, the WTRU may prioritize the predictive BSR if the indicated buffer level (e.g., for a given LCID and / or LCG and / or total buffer level) exceeds a certain configured threshold compared to the buffer level in the regular BSR.

[0153] The traffic prediction capability of the WTRU (e.g., at different prediction time horizons and / or different traffic and / or bearer types, etc.) may be estimated to have an accuracy and / or confidence level of x%. However, the traffic prediction capability of the WTRU may vary depending on several factors, including, for example, the behavior of the end-user, the dynamic nature of the data traffic, particularly interactive and / or real-time traffic, etc. The traffic prediction capability of the WTRU may have difficulty having a specific accuracy and / or confidence level for prediction. The traffic prediction capability of the WTRU may have difficulty having a specific value for prediction.

[0154] The WTRU may indicate to the network the WTRU's prediction capability for each traffic type (e.g., all traffic types) or certain traffic types (e.g., a specific prediction time range, etc.) with a confidence interval between two values ​​(e.g., between 75% and 85%). When transmitting a predictive BSR (e.g., when the accuracy and / or confidence are explicitly communicated according to any of the embodiments described herein), the WTRU may indicate the range of the accuracy and / or confidence interval. Within a given predictive BSR report, there may be several entries with different prediction accuracy and / or confidence levels or ranges. Several entries with different prediction accuracy and / or confidence levels or ranges may conform to a given predictive BSR report. For example, a predictive BSR may indicate different prediction accuracy and / or confidence levels and / or ranges for different LCGs. For example, LCG A may have a predicted traffic level of X bytes, a time range of t1, and / or a confidence level of 75% to 90%. LCG B may have a predicted traffic level of Y bytes, a time horizon of t2, and a confidence level of 85% to 90%.

[0155] The WTRU may indicate to the network the WTRU prediction capability for each traffic type (e.g., all traffic types) and / or certain traffic types (e.g., a specific prediction time range, etc.). These traffic types may have associated error tolerances with certain confidence intervals. For example, the capability may indicate that the WTRU can perform UL data traffic prediction with 85% confidence and / or that the predicted value may fall within the predicted value (e.g., a lower tolerance and / or the predicted value plus an upper tolerance). When transmitting a predictive BSR (e.g., when the accuracy and / or confidence level is explicitly communicated as described herein), the WTRU may indicate the error tolerance. For example, the predictive BSR may indicate different prediction accuracy and / or confidence levels and / or ranges for different LCGs. In an example, LCG A may have a predicted traffic level of X bytes, a time range of t1, a confidence of 75% to 90%, a lower tolerance of x1 bytes, and / or an upper tolerance of x2 bytes. LCG B may have a predicted traffic level of Y bytes, a time range of t2, a confidence level of 85% to 90%, a lower tolerance of y1 bytes, and / or an upper tolerance of y2 bytes. When the network obtains such a BSR, the expected traffic for LCG A may be expected to fall between X-x1 bytes and X+x2 bytes, with a confidence level of 75% to 90%.

[0156] Example indications for inclusion in a BSR are described below. However, each of the examples described below may be applicable at the WTRU capability level. For example, a WTRU may indicate its capabilities in a similar manner, but indicate confidence levels and / or error tolerances in a different manner. The network may select specific capabilities and / or indicate to the WTRU to transmit a predictive BSR that meets a certain confidence level and / or error tolerance, etc.

[0157] The WTRU may provide an error tolerance and the network may assign a default confidence level. For example, LCG A may have a predicted traffic level of X bytes, a time range of t1, a lower tolerance of x1 bytes, and / or an upper tolerance of x2 bytes. For example, when the network obtains such a BSR, the expected traffic for LCG A may be expected to fall between X-x1 bytes and X+x2 bytes, with a default confidence level, such as 100%.

[0158] The forecast capability may directly indicate the forecasted traffic range, rather than separately communicating lower and / or upper tolerances. For example, LCG A may have a forecasted traffic level of [X1-X2] bytes, a time range of t1, and a confidence level of 75% to 90%.

[0159] Even for the same traffic type (and / or traffic group), several entries may indicate different confidence levels, error tolerances, and / or time ranges, etc. For example, LCG A may have a predicted traffic level of [A1-A2] bytes, a time range of t1, and a confidence level of 75% to 90%. LCG A may have another predicted traffic level of [B1-B2] bytes, a time range of t1, and a confidence level of 85% to 95%. LCG A may have another predicted traffic level of [C1-C2] bytes, a time range of t2, and a confidence level of 75% to 90%.

[0160] The lower error tolerance and / or upper error tolerance may be indicated as a percentage rather than an absolute value. For example, LCG A may have a predicted traffic level of X bytes, a time range of t1, a confidence level of 75% to 90%, a lower tolerance of x1%, and / or an upper tolerance of x2%. When the network obtains such a BSR, the network may infer that the expected traffic of LCG A may be expected to fall between (1-x1)*X bytes and (1+x2)*X bytes, with a confidence level of 75% to 90%.

[0161] The error tolerance value and / or percentage may be the same for each type of forecast (eg, all types of forecasts) having the same forecast time horizon.

[0162] There may be separate accuracy and / or confidence levels for the lower and / or upper error tolerances. For example, LCG A may have a predicted traffic level of X bytes, a time range of t1, a lower tolerance of x1%, an upper tolerance of x2%, a lower confidence level of 75% to 80%, and / or an upper confidence level of 90% to 95%.

[0163] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in the present application, which are intended to be illustrative of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be obvious to those skilled in the art. Unless explicitly provided as such, any element, action or description used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, within the scope of the present disclosure, functionally equivalent methods, devices and products will be obvious to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0164] Although the foregoing embodiments may be discussed with respect to specific terminology and structures (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.) for simplicity, the embodiments discussed are not limited thereto and may be applied to other systems using, for example, other forms of electromagnetic waves or non-electromagnetic waves such as sound waves.

[0165] It should also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, a single image, and / or multiple images displayed on a time basis, or any suitable combination thereof. For example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a plurality of embodiments of the WTRU; (iii) a wireless and / or wired (e.g., tetherable) device configured with (in particular) some or all of the structure and functionality of the WTRU; (iii) a wireless and / or wired device configured with less than all of the structure and functionality of the WTRU; or (iv), etc. References herein Figures 1A to 1D Details of an example WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than head mounted displays may be utilized and that some or all of the embodiments of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0166] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Unlike signals, examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0167] Variations of the methods, devices, articles, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be utilized with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0168] In addition, in the embodiments provided herein, processing platforms, computing systems, controllers and other devices comprising processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, reference to the symbolic representation of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as "executed", "computer executed" or "CPU executed".

[0169] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bits is a physical location that has specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0170] The data bits may also be maintained on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by the CPU. The computer-readable medium may include cooperating or interconnected computer-readable media that exist solely on a processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the provided methods.

[0171] In an exemplary embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0172] The above specific embodiments have been listed various embodiments of devices and / or processes by using block diagrams, flow charts and / or examples. In the case where such block diagrams, flow charts and / or examples contain one or more functions and / or operations, it should be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or almost any combination thereof. In example embodiments, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. Those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be implemented in whole or in part in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware or almost any combination thereof, and according to the present disclosure, designing circuit systems and / or writing codes for software and / or firmware will be within the technical scope of those skilled in the art. Those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in various forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually implement the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0173] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit housing; a video display device; a memory, such as a volatile memory and a non-volatile memory; a processor, such as a microprocessor and a digital signal processor; a computing entity, such as an operating system, a driver, a graphical user interface, and an application; one or more interactive devices, such as a touch pad or a screen; and / or a control system, including a feedback loop and a control motor (e.g., a feedback for sensing position and / or velocity, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0174] The subject matter described herein sometimes illustrates different components contained in or connected to different other components. It should be understood that such depicted architectures are merely examples, and in fact many other architectures that achieve the same functionality can be implemented. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively "associated" so that the desired functionality can be achieved. Therefore, any two components that are combined to achieve a specific functionality in this article can be considered to be "associated" with each other so that the desired functionality is achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operably coupled" to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or wirelessly interact and / or components that can logically interact and / or components that can logically interact.

[0175] With respect to substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate, depending on the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.

[0176] It will be understood by those skilled in the art that, in general, the terms used herein, especially in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation object is intended, such intent will be explicitly stated in the claim, and in the absence of such a recitation object, there is no such intent. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitation objects. However, the use of such phrases should not be understood to imply that any particular claim containing such introduced claim recitation object is limited to an embodiment containing only one such recitation object by the indefinite article "a" or "an" to introduce the claim recitation object. This is true even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "a kind" (e.g., "a" and / or "a kind" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the stated number (e.g., a bare recitation of "two recitations" without other modifiers means at least two recitations or two or more recitations). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and / or A, B, and C simultaneously, etc.). In those instances where a convention similar to “at least one of A, B, or C, etc.” is used, generally speaking, the meaning of such construction is that a person skilled in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include, but is not limited to, a system having A alone, B alone, C alone, A and B at the same time, A and C at the same time, B and C at the same time, and / or A, B, and C at the same time, etc.).It will also be understood by those skilled in the art that, in fact, any separate words and / or phrases presenting two or more alternative terms, whether in the specification, claims or drawings, should be understood to contemplate the possibility of including one of the terms, any of the terms or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". In addition, as used herein, the term "any of..." followed by a listing of multiple items and / or multiple item categories is intended to include "any of", "any combination", "any multiples" and / or "any combination of multiples" of items and / or item categories, either alone or in combination with other items and / or other item categories. In addition, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any number, including zero. And, as used herein, the term "multiple" is intended to be synonymous with "multiple".

[0177] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.

[0178] As will be understood by those skilled in the art, for any and all purposes (such as in terms of providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, one-third, one-quarter, one-fifth, one-tenth, etc. As a non-limiting example, each range discussed herein can be easily divided into lower third, middle third, and upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "up to", "at least", "greater than", and "less than", etc. include the cited numbers and refer to the ranges that can be subsequently divided into subranges as described above. Finally, as will be understood by those skilled in the art, the range includes each individual number. Therefore, for example, a group with 1 to 3 units refers to a group with 1, 2, or 3 units. Similarly, a group with 1 to 5 units refers to a group with 1, 2, 3, 4, or 5 units, etc.

Claims

1. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: receiving predictive buffer status reporting (BSR) configuration information, the predictive BSR configuration information comprising information indicating an associated time frame and at least one triggering condition; predicting uplink (UL) traffic corresponding to the associated time frame; determining that at least one of the at least one triggering condition has been satisfied; and A predictive BSR is transmitted, the predictive BSR including an indication of predicted UL traffic volume.

2. The method of claim 1, wherein the predictive BSR is transmitted via a medium access control (MAC) control element (CE).

3. The method of claim 1 , further comprising transmitting an indication of the UL traffic prediction capability of the WTRU. 4 . The method according to claim 1 , wherein the predictive BSR configuration information includes information for predicting the UL traffic.

5. The method of claim 4, wherein the predictive BSR configuration information comprises at least one of artificial intelligence (AI) related information, machine learning (ML) related information, or a combination thereof.

6. The method of claim 5, wherein the AI-related information comprises information about an identity of an AI model, and the ML-related information comprises information about an identity of an ML model.

7. The method of claim 1, wherein the associated time frame comprises at least one of a length of time for which the UL traffic is predicted, a time frame for which the UL traffic is predicted, or a combination thereof.

8. The method of claim 1 , further comprising predicting the UL traffic based on at least one of historical traffic volume information, historical transmission time information, historical arrival rate information, historical WTRU location information, historical WTRU trajectory information, or a combination thereof.

9. The method of claim 1, wherein the at least one trigger condition comprises at least one of a UL traffic prediction confidence level, a UL traffic transmission time, a UL traffic volume amount, or a combination thereof.

10. The method of claim 1, further comprising predicting the UL traffic corresponding to the associated time frame based on at least one of an artificial intelligence (AI) algorithm, a machine learning (ML) algorithm, or a combination thereof.

11. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising a processor and a transceiver, the processor being configured to: receiving, via the transceiver, predictive buffer status reporting (BSR) configuration information, the predictive BSR configuration information comprising information indicating an associated time frame and at least one triggering condition; predicting uplink (UL) traffic corresponding to the associated time frame; determining that at least one of the at least one triggering condition has been satisfied; and A predictive BSR is transmitted via the transceiver, the predictive BSR including an indication of predicted UL traffic volume.

12. The WTRU of claim 11, wherein the predictive BSR is transmitted via a medium access control (MAC) control element (CE).

13. The WTRU of claim 11, the processor further configured to transmit, via the transceiver, an indication of a UL traffic prediction capability of the WTRU.

14. The WTRU of claim 11, wherein the predictive BSR configuration information includes information for predicting the UL traffic volume.

15. The WTRU of claim 11, wherein the predictive BSR configuration information comprises at least one of artificial intelligence (AI) related information, machine learning (ML) related information, or a combination thereof.

16. The WTRU of claim 15, wherein the AI-related information comprises information about an identity of an AI model, and the ML-related information comprises information about an identity of an ML model.

17. The WTRU of claim 11, wherein the associated time frame comprises at least one of a length of time for which the UL traffic is predicted, a time frame for which the UL traffic is predicted, or a combination thereof.

18. The WTRU of claim 11, wherein the processor is further configured to predict the UL traffic based on at least one of historical traffic volume information, historical transmission time information, historical arrival rate information, historical WTRU location information, historical WTRU trajectory information, or a combination thereof.

19. The WTRU of claim 11, wherein the at least one trigger condition comprises at least one of a UL traffic prediction confidence level, a UL traffic transmission time, a UL traffic volume amount, or a combination thereof.

20. The WTRU of claim 11, wherein the processor is further configured to predict the UL traffic corresponding to the associated time frame based on at least one of an artificial intelligence (AI) algorithm, a machine learning (ML) algorithm, or a combination thereof.

Images