Modifying QOS flow rules

Abstract

Systems, methods, and instrumentalities may be configure for modifying quality of service (QoS) flow rules. A wireless transmit / receive unit (WTRU) may receive configuration information indicating a mapping of a quality of service (Qos) flow identifier (QFI) to a first data radio bearer (DRB). The WTRU may receive a deadline for data associated with the QFI. The WTRU may determine, based on a QoS profile of the first DRB and the data, a transmission time associated with the data. The WTRU may determine that the transmission time exceeds the deadline. Based on the determination, the WTRU may transmit, to a network node, an indication that indicates a request to remap the QFI to a second DRB. A QoS profile of the second DRB may allow for transmission of the data within the transmission time deadline. The WTRU may transmit the data via the second DRB.

Description

MODIFYING QOS FLOW RULESCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of Provisional U.S. Patent Application No. 63 / 421 ,814, filed November 2, 2022, the disclosure of which is incorporated herein by reference in its entirety.BACKGROUND

[0002] Mobile communications using wireless communication continue to evolve. A fifth generation may be referred to as 5G. A previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Systems, methods, and instrumentalities are provided that may be associated with modifying quality of service (QoS) flow rules. A wireless transmit / receive unit (WTRU) may receive configuration information that indicates a mapping of a quality of service (Qos) flow identifier (QFI) to a first data radio bearer (DRB). The WTRU may receive a transmission time deadline for data associated with the QFI. The WTRU may determine, based on a QoS profile of the first DRB and the data, a transmission time associated with the data. The WTRU may determine that the transmission time exceeds the transmission time deadline. Based on the determination that the transmission time exceeds the transmission time deadline, the WTRU may transmit, to a network node, an indication that indicates a request to remap the QFI to a second DRB. A QoS profile of the second DRB may allow for transmission of the data within the transmission time deadline. The WTRU may transmit the data via the second DRB.

[0004] The determination that the transmission time exceeds the transmission time deadline may be based on a QoS requirement of the first DRB being below a threshold. The QoS profile of the second DRB allowing for transmission of the data before the transmission time deadline may be based on a QoS requirement of the second DRB being above a threshold. The configuration information may indicate one or more conditions associated with when one or more QFIs are mapped to one or more DRBs. The configuration information may be received from an application client. The indication that indicates the request to remap the QFI to the second DRB may be included in a radio resource control (RRC) message. The RRC message may include a dedicated uplink RRC message. The WTRU may transmit a confirmationindication to the network node. The confirmation indication may indicate that the QFI was remapped to the second DRB. The data may become available for transmission after receiving the configuration information and / or the transmission time deadline.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0009] FIG. 2 illustrates an example of a service data adaptation protocol (SDAP) sublayer.

[0010] FIG. 3 illustrates an example of an SDAP functional overview.

[0011] FIG. 4 illustrates an example of an SDAP data (protocol data unit) PDU format without an SDAP header.

[0012] FIG. 5 illustrates an example of a downlink (DL) SDAP data PDU format with an SDAP header.

[0013] FIG. 6 illustrates an example of an uplink (UL) SDAP data PDU format with an SDAP header.

[0014] FIG. 7 illustrates an example of an end-marker control PDU.

[0015] FIG. 8 illustrates an example of a high-level federated learning (FL) interaction between participants and a central artificial intelligence (Al) server over a system.

[0016] FIG. 9 illustrates an example of an FL protocol over wireless communication systems.

[0017] FIG. 10 illustrates an example functional relation between multiple devices and multiple agents.

[0018] FIG. 11 illustrates an example where a WTRU may take actions to (e.g., proactively) mitigate potential disturbances.

[0019] FIG. 12 illustrates an example operation timeline of two WTRUs that may be configured to do FL model training.

[0020] FIG. 13 illustrates an example of a WTRU changing its QoS flow rule at the SDAP layer.

[0021] FIG. 14 illustrates an example of a WTRU increasing / decreasing the number of data radio bearers (DRBs) dynamically.

[0022] FIG. 15 illustrates an example associated with a WTRU mapping a QoS flow identifier (QFI) to a data radio bearer (DRB).DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0054] 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 communicationsdevices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] Features described herein may be associated with Quality-of-Service (QoS) flows and rules. QoS may be implemented using QoS Flows. Mapping levels may be used for QoS flows, which may include: (i) at the non-access stratum (NAS) level and (ii) at the Access Stratum (AS) level.

[0078] At the NAS level, QoS rules (e.g., packet filters) in the wireless transmit / receive unit (WTRU) and packet detection rules (PDRs) in a user plane function (UPF) may be used to map uplink (UL) and downlink (DL) packets to QoS flows, respectively. A core network may indicate how I P / Ethernet flows are mapped to QoS flows. The QoS indication (e.g., QFI and RQI) may be carried from the core network to the gNB for a Protocol Data Unit (PDU) session, for example, via the PDU Session User Plane Protocol (e.g., the N3 encapsulation layer), which may sit above the GTPv1 -U layer. From the gNB, the QoS indications (e.g., QFI and RQI) may be carried over to the WTRU over a Service Data Adaptation Protocol (SDAP) header (e.g., if the SDAP header is configured).

[0079] At the AS level, the QoS flow rules in the WTRU and gNB may map QoS flows (QFIs) to Data Radio Bearers (DRBs). Multiple QoS flows may be mapped into single or multiple DRBs. The level of QoS mapping may be associated with feature(s) described herein .

[0080] The SDAP layer may provide control over QoS flows between the WTRU and the gNB for the user plane (UP) traffic. The SDAP layer may map QoS flows (e.g., data packets) to DRBs for uplink and downlink directions. The SDAP layer may change the priority of a flow dynamically.

[0081] FIG. 2 illustrates an example of the SDAP sublayer. As illustrated in FIG. 2, the SDAP layer may include multiple SDAP entities, and a single SDAP entity may be used for a single PDU Session. If the WTRU has multiple PDU Sessions, multiple instances of the SDAP layer may be created. The RRC layer may control the initiation and release of an SDAP instance. A PDU Session may carry multiple (e.g., I P / Ethernet) flows and may configure rules for multiple QoS flows. A QoS flow may be mapped to aparticular DRB at the SDAP layer. A DRB may be mapped to a specific PDCP layer, which may translate to one or two Radio Link Control (RLC) entities depending on the RLC mode.

[0082] In the uplink, a QoS flow may be mapped to one DRB at a time. A PDU session may have a (e.g., at least one) DRB. There may be a (e.g., at most one) default DRB in a PDU session (e.g., a PDU session). When the uplink mapping rule is unavailable, the SDAP PDU may be sent to the default DRB.

[0083] FIG. 3 illustrates an example of the SDAP functional overview. The mapping between QoS flows at the SDAP layer may be configured by the RRC layer. The SDAP layer may be configured (e.g., by RRC signaling) for a (e.g., each) DRB separately within the “sdap-Config” internal element (IE), which may be under the “DRB-ToAddMod” parameter structure, which may be under “radioBearerConfig.” A (e.g., any) modification to an SDAP mapping of a DRB may be initiated by the RRC.

[0084] An SDAP data PDU may be sent to the PDCP layer in one or more of the following ways: (i) without an SDAP header for UL and DL; (ii) with an SDAP header for DL; or (iii) with the SDAP header for UL. An SDAP header may be configured for both UL and DL per DRB.

[0085] FIG. 4 illustrates an example of an SDAP data (protocol data unit) PDU format without an SDAP header. Flows that come into the SDAP layer, which RRC does not configure to map to a specific DRB, may be placed into the default DRB. An SDAP header may not be used when flows that come into the SDAP layer are placed into the default DRB.

[0086] FIG. 5 illustrates an example of a DL SDAP data PDU format with the SDAP header. This header may be different than the UL and may include a reflective QoS flow to DRB mapping indication (RDI), reflective QoS indicator (RQI), and QoS Flow ID (QFI) parameters.

[0087] FIG. 6 illustrates an example of a UL SDAP data PDU format with the SDAP header. A D / C being 1 may indicate a DATA PDU, and 0 may indicate a Control PDU (e.g., end-marker).

[0088] In the uplink, an SDAP header may become a Control PDU with the size of one byte (e.g., a header without a payload) by setting D / C field to zero. A control SDAP header may be sent to obsolete a mapping for a QoS flow to a DRB (e.g., an “End-Marker Control PDU”). The mapping may become obsolete when the RRC configures an (e.g., new) mapping for a flow.

[0089] FIG. 7 illustrates an example of an end-marker control PDU. When using Reflective QoS (RQI) in the DL SDAP header, the SDAP layer may use the DRB mapping of the downlink for the uplink, so that the SDAP layer follows what the core network has configured for the downlink. If the core network changes a QFI for a flow within a PDU Session, the WTRU may follow the same changes for the uplink direction (e.g., the UL and DL may use the same DRB for a QoS flow). When the Reflective QoS is not activated, the SDAP / RRC may follow a mapping (e.g., a different mapping) for the uplink and downlink for a flow within aPDU Session. The Reflective QoS function may not be applicable if DL SDAP PDUs do not have a header, as the reflective QoS function may be indicated via the DL header.

[0090] Features described herein may be associated with AI / ML services. WTRUs may interact with network functions (NFs) in the core network (e.g., AIMLF or FLF) and Application Server (AS)ZApplication Function (AF) through the user plane (e.g., via UPF) or control plane (e.g., via the NAS signaling). In examples including the user plane (UP) model, the WTRU may (e.g., may need to) interact with AS / AF over a DRB, which may be established between the WTRU and NG-RAN over the Uu air interface.

[0091] Features described herein may be associated with AI / ML metadata and operations. The metadata may include one or more of the following: model topology, model weights, training completion time window, and other AI / ML specific parameters such as loss function, entropy, prediction accuracy, etc. The AI / ML operations may be categorized as one or more of the following: (i) model distribution; (ii) model splitting between AI / ML endpoints; or (iii) federated learning).

[0092] In Federated Learning (FL) mode, the central Al server may train a global model by combining local models trained by a participant (e.g., a participant WTRU) based on a model averaging technique. The WTRU may perform its local model training within a training cycle based on a model downloaded from the centralized Al server using local data. The local model training may be completed, and the WTRU may deliver the training results (e.g., a gradient for the deep neural network (DNN)) to the centralized Al server via UL channels. The centralized Al server may aggregate the gradients (e.g., model weights) from the WTRUs and update the global model. The next training cycle may begin where the Al server may distribute the updated global model to WTRUs via DL channels.

[0093] FIG. 8 illustrates an example of a high-level FL interaction between participants and the central Al server over the system. The FL training over wireless communication may be different than the FL training in data centers, where participants (e.g., participant WTRUs) may have variable conditions in terms of available computational and network resources. The WTRUs may not be homogeneous, so the WTRUs may have different capabilities in terms of their compute and network resources or what ML framework they support. It may not be efficient for a centralized Al server to include (e.g., all) the WTRUs (e.g., participant WTRUs) in a training session, so a member selection mechanism may be used (e.g., needed) before a training cycle begins. If the conditions (e.g., device’s computation resource and / or wireless channel condition) are not changed, the WTRU re-selection and training re-configurations may not be used (e.g., not needed) for a training cycle. However, different WTRUs may be reselected over time to achieve global training with diverse datasets.

[0094] FIG. 9 highlights an FL scenario where a set of participants (e.g., Device A-E) may be involved in a distributed training session. End devices, for example, WTRUs (e.g., all WTRUs) may not be involved intraining cycles (e.g., all training cycles). In training cycles, WTRUs may be inactive. In sessions (e.g., other sessions), WTRUs may be busy training a local model. For example, Device A may be initially (e.g., during the N-th cycle) engaged in a training session, and after Device A reports its training resources, the centralized FL server may not select Device A for the next cycle (e.g.,, N+1-th cycle). The centralized FL server may select Device B, which may have been inactive during the N-th cycle. The WTRU or the FL server may be inactive between and during the training sessions.

[0095] FIG. 9 illustrates an example of an FL protocol over wireless communication systems. An FL training cycle may be categorized into operating stages (e.g., three operating stages). In a first operating stage (e.g., yellow-colored box in FIG. 9), the FL training server may select a set of training devices (e.g., WTRUs). During the first operating stage, the training devices may express their training resources to the FL training server. Once the FL server collects information (e.g., all information) from training devices, the FL server may select training devices, and the FL server may enter a second operating stage (e.g., model distribution and training configuration), where the FL server may distribute a global trained model and related configurations to (e.g., all) selected devices (e.g., WTRUs). Upon the model's arrival and configuration, the WTRUs may start local model training at a point in time (e.g., a different point in time). Once the local training is completed at a WTRU, the local training may be delivered to the FL server, where a third operating stage may begin. During the third stage, the FL server may aggregate training results (e.g., all training results) to form a global model and repeats the training workflow again.

[0096] An example of FL may be referred to as Synchronous Federated Learning (SFL). A characteristic of the SFL may be the latency budget where participants (e.g., all participants) may complete the training results uploading within a predefined time window. WTRUs (e.g., all WTRUs) participating in a training session may complete the training results uploading within a predefined latency budget. In examples, for uncompressed FL for image recognition, the UL transmission deadline may be between 1 -3 seconds, as illustrated in Table 1.Table 1 : Latency and user experienced UL / DL data rates for uncompressed FL

[0097] An example of FL may be referred to as Synchronous Federated Learning (SFL). A characteristic of the SFL may be the latency budget where participants (e.g., all participants) may complete the training results uploading within a predefined time window. WTRUs (e.g., all WTRUs) participating in a training session may complete (e.g., need to complete) the training results uploading within a predefined latency budget. In examples, for uncompressed FL for image recognition, the UL transmission deadline may be between 1-3 seconds, as illustrated in Table 1.

[0098] Features described herein may be associated with multi-agent multi-device ML operations. The use case may describe a case of multi-agent multi-device ML operations with data (e.g., heavy data) when there is a level of disturbance for data collection / transfer (e.g., a shortage of network and / or computational resources, temporary failure, etc.).

[0099] Fig. 10 illustrates an example of a functional relationship between multiple devices (e.g., collecting devices) (denoted with Mx) and multiple agents (denoted with Ax). The devices may perform ML operations (e.g., functional splitting may be possible between a device and one or more learning agents). An agent may interact with a set of WTRUs and other agents collaboratively. This behavior may be similar to the partition / aggregate workflow that is commonly used in data center networks.

[0100] FIG. 10 illustrates a functional relation between multiple devices (e.g., Mi, M2, ..., Mk in the form of a WTRU) and multiple agents (e.g., A1, A2, ..., An). If the expected “input data” of a device, which may be raw data or / and trained data is not delivered to the intended learning agent in time, the input data may not be used by the learning agent, wasting the resources of parties involved (e.g., all parties involved). There may be reasons for the input data to be disturbed, for example, lack of network resources (e.g., radio resources due to temporal degradation, higher noise / i nterference level, highly crowded situations, partial / total break-down, etc.).

[0101] FIG. 11 illustrates an example where the WTRU may take actions to proactively mitigate potential disturbances. The preferred deadline for input data transfer may be 1 sec (t = t0+1 ) with the amount of useful input data 3 bits, in which kinds of scheduling (e.g., two kinds of scheduling) may be given: (a) may be imperfect scheduling, and (b) may be satisfactory (e.g., good) scheduling. A bit of data to send may take one second. The transfer payload type may not be limited to input data for learning agent(s) and may be applied to learning model transfer. The transfer direction may be uplink (e.g., for input data transfer) or downlink (e.g., for model distribution / transfer). With imperfect scheduling, the input data may miss a transmission deadline (e.g., because the input data may be delivered to its destination at tO+2 due to not allocating a higher data rate to this UL data transmission), while with perfect scheduling, the input data may be delivered to its destination within the predefined transmission deadline of 1 sec. In examples, thenetwork resources may be assigned to WTRUs (e.g., other WTRUs) during (t0+1, tO+2), allowing for an use of radio resources (e.g., an efficient use of radio resources).

[0102] FIG. 11 illustrates an example of disturbance of input data transfer within a preferred deadline of 1 sec (e.g., t = t0+1) with the amount of useful input data 3 bits (e.g., as an example), (a) For the 3-bit input data amount (shaded trapezoid in (a)), it may take 2 sec with imperfect scheduling, (b) for the 3-bit input data amount (shaded rectangle in (b)), it may take 1 sec with good scheduling, where the network resources may be assigned to WTRUs (e.g., other WTRUs) during (t0+1 , tO+2).

[0103] WTRUs may interact with network functions (NFs) in the core network through the user plane (e.g., via UPF). The AI / ML metadata may be transported to AF / AS directly. The metadata may include neural network (NN) model topology, weights, datasets, etc. The AI / ML operations (e.g., related to Federated Learning (FL)) may have a deadline for their task completion, so that if the WTRU cannot train a new local model and deliver the local model to the AS / AF within a predefined time window, the results of the AI / ML operations may not be considered, e.g., wasting resources across WTRU, RAN and CN.

[0104] FIG. 12 illustrates an example operation timeline of two WTRUs that may be configured to do FL model training. The WTRUs may be configured to start doing the model training almost at the same time and the time indicated by the deadline. Due to the differences in processing capabilities of the WTRUs and current WTRU conditions (e.g., data activity, battery level, etc.), the two WTRUs may finish their model training at different times. WTRU 1 may be done with the model training before the deadline, so whatever data WTRU1 has to send to the network related to the training (e.g., AI / ML metadata), such sending may be done in a relaxed manner (e.g., via a DRB with low priority or / and low data rate). WTRU 2 may be done with the model training very close to the deadline. Data of WTRU 2 may be sent with a DRB of higher priority or / and high data rate if the deadline is to be made.

[0105] The network may not know when exactly the WTRUs will be done with their training and may not be able to configure a DRB that is suitable for sending the metadata. In examples, if the network has configured a low priority or / and low data rate bearer to both WTRUs, then WTRU 2’s data may not arrive on time. If the network has configured a high priority or / and high data rate bearer to both WTRUs, then though the data of both WTRUs may be received before the deadline, the QoS of other traffic (e.g., of WTRU 1 or other WTRUs) may be impacted due to the high (e.g., unnecessarily high) QoS of the bearer used for WTRU 1 for the purpose of sending the metadata.

[0106] In examples, time sensitive (e.g., AI / ML trained model, metadata, etc.) may have an associated priority, e.g., such that the time sensitive data may be delivered to the network before the time sensitive data becomes outdated / irrelevant / useless.

[0107] Even though features described above and in the examples below may be related to the AI / ML metadata (e.g., trained model) or AI / ML related dataset, the examples described may be applicable to other UL data / traffic that may have varying requirements and a varying / bursty nature (e.g., XR traffic, for example, traffic related to Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), where the size of the data unit (e.g., packets / frames / PDU sets / data burst) may vary from one data unit to another data unit etc.,), where the network may not be able to configure a proper bearer / LCID, etc., that may be used to transmit the data, without over-provisioning (e.g., configuring a bearer / LCID with the highest priority, highest data rate, lowest packet delay budget, etc.).

[0108] A WTRU may be configured to map a QFI to DRBs (e.g., different DRBs), e.g., depending on conditions, for example the WTRU may be configured to remap a QFI to a different DRB if one or more conditions are satisfied as described herein. The WTRU may be configured with (e.g., receive configuration information that indicates) a configuration that associates a QFI (e.g., a certain QFI) to more than one DRB, along with one or more conditions associated with when a QFI (e.g., one or more QFIs) is to be mapped to a DRB (e.g., one or more DRBs). The condition for mapping the QFI with a particular DRB may be based on time information. The time information may be a relative time (e.g., a delta time) from the reception of the configuration. For example, the WTRU may receive a configuration as follows: QFIx:{DRB1 :t1}, {DRB2:t2}, {DRB3 :t3}, etc, which may indicate to the WTRU one or more of the following: within t1 of the reception of the DRB configuration, QFIx may be mapped to DRB1 ; between t1 and t2, QFIx may be mapped to DRB2; or between t2 and t3, QFIx may be mapped to DRB3, etc.

[0109] The time information may be duration information. In examples, the WTRU may receive a configuration as follows: QFIx: {DRB1 :t1}, {DRB2:t2}, {DRB3 :t3}, etc., which may indicate to the WTRU one or more of the following: within t1 of the reception of the DRB configuration, QFIx may be mapped to DRB1 ; for the next t2 time duration after t1 , QFIx may be mapped to DRB2; or for the next t3 time duration after t2, QFIx may be mapped to DRB3, etc.

[0110] The time information may be absolute time information. In examples, the WTRU may receive a configuration as follows: QFIx: {DRB1 :t1}, {DRB2:t2}, {DRB3 :t3}, etc, which may indicate to the WTRU one or more of the following: before absolute time t1 , QFIx may be mapped to DRB1; between absolute times t1 and t2, QFIx may be mapped to DRB2; or between absolute times t2 and t3, QFIx may be mapped to DRB3, etc.

[0111] The time information may be a percentage time information, e.g., relative to a time duration. In examples, the WTRU may receive a configuration of the time duration (t) as well as the percentage of the time duration regarding the mapping, such as: QFIx: {DRB1 :p1 }, {DRB2:p2}, {DRB3 :p3}, etc., which may indicate to the WTRU one or more of the following: if UL data arrives during the first p1 *t1 absolute time t1 ,QFIx may be mapped to DRB1; for UL data arriving between absolute times t1 and t2, QFIx may be mapped to DRB2; or, for UL data arriving between absolute times t2 and t3, QFIx may be mapped to DRB3, etc.

[0112] A final time information (e.g., t_f) may indicates that data for the concerned QFIx may arrive after t_f is to be mapped to the DRB associated with the time information. Configuration examples are examples, and not limiting, and the configuration may be provided in a multitude of different ways. In one or more examples, at different times (e.g., that are related to the time the configuration may be received and / or the time the AI / ML model training may be finished or / and the deadline the metadata that may be expected to be sent to the network), the WTRU may map the QFI associated with the metadata to different DRBs, e.g., such that the metadata may be received at the network and with as little impact as possible to other UP or CP data (e.g., for the same WTRU or other WTRUs).

[0113] The WTRU may send a request to the network for a change of the mapping of a QFI to DRB. The WTRU may detect that remapping of QoS rule(s) may be needed (e.g., the WTRU may determine that a condition for remapping as described herein is satisfied), and the WTRU may ask the base station (gNB) to remap the QoS rule(s) of the base station where an existing QFI may be mapped to a DRB (e.g., a different DRB) for UL, or a QFI (e.g., new QFI) may be configured to route AI / ML traffic to a different DRB. For the former case: (i) the WTRU may not wish to change priority between the gNB and the UPF, e.g., given that scheduling over the Uu air interface may occur in both UL and DL transmissions; and (ii) remapping QFI to a particular DRB between WTRU and gNB may provide segregation (e.g., good segregation) between AI / ML traffic with a job delivery deadline (e.g., a strict job delivery deadline) and other WTRUs’ traffic. The WTRU may signal (e.g., to the gNB) a preference (e.g., a preference of the WTRU) to remap a QoS flow (e.g., associated with a QFI) to a different DRB, e.g., where the WTRU signaling may be via different messages such as a MAC CE, PDCP Control PDU, RRC message (e.g., WTRU Assistance information, a UL RRC message, etc.), or SDAP Control PDU. The messages may include cause / value indications associated with preference.

[0114] It may be determined (e.g., by the core network) that an Application Client (AC) running at the WTRU may include a (e.g., may need a) higher priority in its UL data transmission, e.g., starting at a certain estimated / predicted time. The WTRU may ask the core network to change a QoS flow priority (e.g., via a NAS message). An Application Server (AS)ZApplication Function (AF), may ask the core network whether the WTRU may be associated with (e.g., may need) a higher priority for its UL / DL data transmission in an estimated / predicted time. The core network may initiate a PDU session modification procedure with an activated Reflective QoS (RQI).

[0115] The WTRU may indicate to the network that the mapping of a QFI to DRB has been modified. In examples, the WTRU may, if updating the mapping from QFI to DRB based on examples described herein, send an indication to the network.

[0116] The indication may be an SDAP control PDU. The End marker control PDU may not be sufficient because the end marker may be used to indicate that the WTRU has stopped mapping the QFI to the previously associated DRB, and the network may not know the (e.g., new) associated DRB to the QFI (e.g., as the mapping change in legacy SDAP may be triggered via DRB reconfiguration). A Start Marker PDU may be introduced that indicates that the WTRU has started mapping the concerned QFI to the bearer (e.g., new bearer). An example format of this control PDU is shown below in Table 2.Table 2

[0117] The WTRU may send an end marker PDU before sending the Start marker PDU. The indication of the update of the mapping of the QFI to DRB may be a MAC CE. The indication of the update of the mapping of the QFI to DRB may be a PDCP control PDU. In examples, the PDCP control PDU may be as shown in Table 3.Table 3

[0118] The indication may be sent to indicate to the network that (e.g., from this moment onwards) the indicated QFI may be mapped to the DRB that is associated with the PDCP entity in which this control PDU was received on.

[0119] The indication of the update of the mapping of the QFI to DRB may be an RRC message. In examples, new information elements (lEs) may be introduced in existing UL RRC message(s), e.g., WTRU assistance information. A new UL RRC message may be specified that may be used to send the indication of the concerned QFI and the new DRB that it is mapped to.

[0120] In examples, one QFI to DRB mapping update may be performed at a time. Examples may be modified to support the multiple updates being performed (e.g., multiple updates being performed at once).In examples, the SDAP / PDCP control PDUs may be extended to several octets including information regarding a QFI that may have been impacted and the new DRB that is associated with the QFI.

[0121] The WTRU may receive an ACK / NACK regarding the QFI to DRB mapping being applied. The WTRU may receive an indication from the network to keep or revert the QFI to DRB mapping update that it has applied.

[0122] In examples, the WTRU may apply (e.g., keep applying) the mapping unless it receives a NACK indication. In examples, the WTRU may not apply the mapping unless it receives an ACK indication. The indication sent by the network may be a DL SDAP control PDU.

[0123] If one mapping change is applied at a time, the contents in Table 4 may be used by the network to indicate to ACK / NACK the preceding mapping update indication from the WTRU.Table 4

[0124] If the WTRU receives such an indication with a NACK, the WTRU may revert the mapping update (e.g., use the QFI to DRB mapping that was used before the update).

[0125] The contents of Table 5 may be used to indicate to the WTRU the NACK to the remapping that the WTRU may have indicated and to which DRB the QFI is remapped to.Table 5

[0126] For example, if the WTRU receives such an indication, the WTRU may change the QFI mapping to the indicated DRB.

[0127] The contents of Table 6 may be used by the network to (e.g., explicitly) indicate the QFI remapping that may be ACKed or NACKed and may be used in cases where more than one update is made by the WTRU at once.Table 6

[0128] The contents of Table 7 may be used by the network to indicate a NACK to the re-mapping that was indicated by the WTRU and specify the DRB that the concerned QFI may (e.g., should) be remapped to.Table 7

[0129] The ACK / NACK indication from the network may be a DL MAC CE (e.g., an ACK / NACK indication, an ACK / NACK indication that also indicates the concerned QFI, an ACK / NACK indication that includes a DRB identity that the concerned QFI should be remapped to, etc.).

[0130] The ACK / NACK indication from the network may be a DL PDCP control PDU (e.g., a ACK / NACK indication, an ACK / NACK indication that indicates the concerned QFI, an ACK / NACK indication that includes a DRB identity that the concerned QFI should be remapped to, etc.)

[0131] The ACK / NACK indication from the network may be an RRC reconfiguration message (e.g., a ACK / NACK indication, an ACK / NACK indication that indicates the concerned QFI, an ACK / NACK indication that includes a DRB identity that the concerned QFI should be remapped to, etc.).

[0132] A WTRU may indicate to the network that the WRTRU requires additional DRBs. The WTRU may check whether the provided PDU Session ID has multiple DRBs, and how QoS flows are remapped to those DRBs to meet AC’s constraints. The WTRU may decide to set up new DRBs between the WTRU and the base station over the Uu air interface. DRB(s) may be added, as a PDU Session may have multiple flows (e.g., one of which is the AI / ML flow), e.g., running over a single best effort DRB (e.g., default bearer). The AI / ML flow may compete with other flows for UL resources, and if the AI / ML flow is moved to another (e.g., dedicated) DRB, the AI / ML flow may get a higher priority (e.g., by the MAC scheduler).

[0133] The WTRU may initiate a PDU Session Modification procedure in the case of a single DRB, requesting the network to set up a DRB (e.g., new DRB) for the PDU Session in question. A PDU Session may have a default DRB with a best-effort priority. The WTRU may send an RRC message to the base station requesting to increase the number of DRBs associated with a PDU Session ID. To carry this signal, an IE (e.g., a new I El) may be introduced, for example, to an existing UL RRC message (e.g., such as WTRU Assistance Information), or a (e.g., a new) UL RRC message may be defined.

[0134] The WTRU may receive an (e.g., explicit) signal (e.g., configuration information) from an AC that indicates that a mapping (e.g., remapping) for a QoS flow is needed (e.g., the mapping may be associated with a QoS flow identifier (QFI) to a first data radio bearer (DRB)). The WTRU may determine whether theWTRU needs a (e.g., new) mapping in its QoS flow rules related to a PDU Session for the uplink at the SDAP layer. This determination may be made by receiving an (e.g., explicit) signal from the AC running AI / ML operations at the WTRU or via an (e.g., a new) ML-based component operating within the WTRU, which may be interacting with AC. For example, the AC may directly indicate to the WTRU that the UL data transmission is to be performed at a higher priority for a certain time window (e.g., in the near future). Such prioritization may be related to a scenario where a local model training by AC may be completed such that the model training results (e.g., neural network weights) may be delivered to AF / AS (e.g., a global FL model trainer) within a certain time window. The time window may be communicated to the WTRU by the network (e.g., by PCF of the core network).

[0135] The WTRU’s (e.g., newly) determined mapping may be different than the policy available on the network and / or WTRU. The network (e.g., gNB) or WTRU may be authorized before such modification may be performed at the WTRU, for example, by interacting with PCF / UDM network functions.

[0136] The WTRU may configure the SDAP layer at its own radio protocol when a remap for the QoS flow rule is required at the SDAP layer. In examples, the WTRU may not interact with the base station for performing such reconfigurations.

[0137] A WTRU may determine whether current QoS rules for the uplink are sufficient to meet requirement(s) of an AI / ML application client running at the WTRU. It may be determined whether a time constraint (e.g., a transmission time), e.g., in terms of AI / ML task completion, is satisfied (e.g., whether the transmission time exceeds a transmission time deadline). The WTRU may modify QoS flow rule(s) (e.g., remapping a QFI from a DRB to another DRB), which may be in the SDAP layer. The modification and / or remapping may accommodate the constraints / requirements of an AI / ML application. For example, the WTRU may determine that the transmission time exceeds transmission time deadline based on a QoS requirement of the first DRB being below a threshold and perform the modification and / or remapping (e.g., as shown in FIG. 15). The WTRU may request the network to remap a QoS flow to a DRB, where the request may be via a (e.g., via a new) UL RRC message. The QoS profile of the second DRB may allow for transmission of the data before the transmission time deadline based on a QoS requirement of the second DRB being above a threshold (e.g., as shown in FIG. 15). The WTRU may ask the network to add more DRBs in for a PDU Session (e.g., via an existing WTRU Assistance Information using an IE (e.g., a new IE). The WTRU may request the network to remove DRBs from a PDU session (e.g., via a (e.g., new) UL RRC message or WTRU Assistance Information with (e.g., new) IE, etc.).

[0138] FIG. 13 illustrates an example of a WTRU changing its QoS flow rule (e.g., associated with a QFI), e.g., at the SDAP layer used as an example herein. The WTRU may receive an indication (e.g., from the AI / ML application client) that uploading training results may require different treatment over the Uuinterface. The WTRU may determine how the QoS flow rules, e.g., particularly for the UL direction, may be remapped to support AI / ML operations. The WTRU may request the base station (e.g., via an RRC message with a (e.g., new) information element) to perform the remapping (e.g., desired remapping) of QoS flows to DRBs at the SDAP layer (e.g., remap a QFI from a DRB to another DRB, as shown in FIG. 15). The base station may populate a new mapping to the SDAP layer of the WTRU, e.g., via an RRC Reconfiguration Procedure (e.g., message).

[0139] At 1 , the WTRU may receive configuration information that provides an indication, e.g., from an application client (AC). The configuration information may indicate a mapping of a QFI to a first DRB. The WTRU may determine or receive an indication (e.g., via the AC) that uploading training results may require different treatment over the Uu air interface for the uplink direction from the WTRU side. Such a signal from the AC may include a PDU Session ID, a specific start time, and / or a time window (e.g., a transmission time deadline for data associated with the QFI for which the treatment applies, as shown in FIG. 15). The AC may interact with an ML-based technique running at the WTRU to predict when such treatment may be needed (e.g., determine that a condition has been met).

[0140] Once the WTRU receives such a signal, the WTRU may determine whether current QoS flow rules (e.g., a QoS profile of the first DRB / QFI mapping to a DRB) at the SDAP layer needs to be changed. The WTRU may determine that current QoS flow rule(s) at the SDAP layer need to be changed based on a condition being satisfied (e.g., the WTRU determining a transmission time associated with the data and the WTRU determining that the transmission time exceeds the transmission time deadline, as shown in FIG. 15). This may be performed by remapping a QFI (e.g., a particular QFI) to another DRB (e.g., to a second DRB). The second DRB may have its own PDCP and RLC entity with a different configuration.

[0141] At 2, the WTRU may, based on the determination that the transmission time exceeds the transmission time deadline, send a message (e.g., an indication that may be included in an RRC message) to the base station asking to remap a QFI to a second DRB (e.g., as shown in FIG. 15). The QoS profile of the second DRB may allow for transmission of the data within the transmission time deadline. The message may include an information element within an existing RRC message such as WTRU Assistant Information, or a dedicated uplink (UL) RRC message may be defined for the signaling.

[0142] When the base station receives a request from the WTRU regarding remapping a QoS flow to a second DRB (e.g., as shown in FIG. 15), the base station may determine whether the requested mapping is allowed. As part of this determination, the gNB may interact with the PCF / UDM. The interaction of the gNB with the PCF / UDM may not be known in the call flow.

[0143] At 3, the base station may send a message (e.g., an RRC Reconfiguration Procedure message) to the WTRU with (e.g., all) remapping configuration information (e.g., remapping indication as receivedfrom the WTRU or locally available at gNB). The RRC message may include an “sdap-Config” IE, which may be under the “DRB-ToAddMod” parameter structure, which may be under “radioBearerConfig.” The WTRU may remap the QFI to the second DRB.

[0144] At 4, the WTRU may send an RRC Reconfiguration Complete Procedure (e.g., message) to the base station indicating that the requested configurations have been completed. The WTRU may transmit the data via the second DRB (e.g., as shown in FIG. 15).

[0145] FIG. 14 illustrates an example associated with a WTRU increasing / decreasing a number of DRBs, for example, when PDU Session handling AI / ML application flows have a single DRB. In FIG. 14, the WTRU may determine how the QoS flow rules for the UL direction may be changed to support AI / ML operations. As part of the determination, the WTRU may check if the PDU session related to a QoS flow has multiple DRBs. If the PDU session related to the QoS flow does not have multiple DRBs, the WTRU may ask the network to increase the number of DRBs. The WTRU may ask the network to decrease the number of DRBs from a PDU Session if the DRBs are no longer needed (e.g., after completion of an AI / ML operation).

[0146] At 1 , the WTRU may determine whether a PDU Session handling QoS flows of an AI / ML application has multiple DRBs. The WTRU may determine to set up (e.g., additional) DRBs between the WTRU and base station over the Uu air interface. Adding DRB(s) may be needed where a PDU Session has multiple flows (e.g., one of which may be the AI / ML flow) running over a single best effort DRB. The AI / ML flow may compete with flows for UL resources, and if the AI / ML flow is moved to another DRB (e.g., dedicated DRB) as described herein, the AI / ML flow may get a higher priority by the MAC scheduler.

[0147] At 2, the WTRU may send a message (e.g., an RRC message) to the base station, requesting to increase the number of DRBs associated with a PDU Session ID. To carry the signal, an IE may be introduced, for example, to an existing UL RRC message such as, for example, WTRU Assistance Information, or a UL RRC message may be defined.

[0148] The WTRU may initiate a PDU Session Modification procedure to change the number of DRBs.

[0149] At 3-4, the base station may send an RRC Reconfiguration Procedure (e.g., message) to the WTRU to increase the number of DRBs. The WTRU may send an RRC Reconfiguration Complete Procedure (e.g., message) to the base station, indicating that the requested configurations have been completed.

[0150] At 5-8, the WTRU may determine to remove unused DRBs from a PDU Session to free radio protocol stack resources at the WTRU and the base station. The WTRU may follow examples as described at 2-4 (e.g., with a removal indication of DRBs).

[0151] FIG. 15 illustrates an example associated with a WTRU mapping a QFI to a DRB (e.g., first DRB). A network node (e.g., base station) may send configuration information (e.g., AIML related information) to a WTRU. For example, the configuration information may be associated with a DRB, and may include one or more of: mapping of QFI(s) to the DRB, or a DRB's QoS profile. The WTRU may receive a trigger related to an AI / ML action (e.g., training) and a deadline for transmitting results. The WTRU may perform an AI / ML activity. The AI / ML activity may conclude and results or data may become available. A decision may be made based on the QoS profile of the DRB and the data that is available (e.g., the data that is to be sent). If the QoS profile of the DRB is adequate (e.g., above a threshold) for transmission (e.g., if a transmission time would complete before a transmission deadline), the data may be sent using the DRB to the network. If the QoS profile of the DRB is inadequate (e.g., below a threshold) for transmission (e.g., if a transmission time would not complete before a transmission deadline), the WTRU may request the network to request or indicate a remapping the QFI to a second DRB. The WTRU may, e.g., based on a received message from the network to remap the QFI to another DRB (e.g., to the second DRB), remap the QFI from the first DRB to the second DRB. The WTRU may send the data using the second DRB.

[0152] Systems, methods, and instrumentalities are provided that may be associated with modifying quality of service (QoS) flow rules. A wireless transmit / receive unit (WTRU) may receive configuration information that indicates a mapping of a quality of service (Qos) flow identifier (QFI) to a first data radio bearer (DRB). The WTRU may receive a transmission time deadline for data associated with the QFI. The WTRU may determine, based on a QoS profile of the first DRB and the data, a transmission time associated with the data. The WTRU may determine that the transmission time exceeds the transmission time deadline. Based on the determination that the transmission time exceeds the transmission time deadline, the WTRU may transmit, to a network node, an indication that indicates a request to remap the QFI to a second DRB. A QoS profile of the second DRB may allow for transmission of the data within the transmission time deadline. The WTRU may transmit the data via the second DRB.

[0153] The determination that the transmission time exceeds the transmission time deadline may be based on a QoS requirement of the first DRB being below a threshold. The QoS profile of the second DRB allowing for transmission of the data before the transmission time deadline may be based on a QoS requirement of the second DRB being above a threshold. The configuration information may indicate one or more conditions associated with when one or more QFIs are mapped to one or more DRBs. The configuration information may be received from an application client. The indication that indicates the request to remap the QFI to the second DRB may be included in a radio resource control (RRC) message. The RRC message may include a dedicated uplink RRC message. The WTRU may transmit a confirmationindication to the network node. The confirmation indication may indicate that the QFI was remapped to the second DRB. The data may become available for transmission after receiving the configuration information and / or the transmission time deadline.

[0154] A WTRU may modify QoS flow rules. The WTRU may obtain an indication that indicates that one or more training results (e.g., or AI / ML data / metadata) require modified treatment. The WTRU may determine, based on the indication, to remap one or more quality of service (QoS) rules. The WTRU may send a first message to a network, and the first message may include a request to remap a QoS flow ID (QFI) associated with a QoS rule. The WTRU may receive a second message from the network, and the second message may include the one or more remapped QoS rules and required instructions to perform a remapping between QFIs to Data Radi Bearers (DRBs). The WTRU may send a third message to the network, and the third message may include an indication that the one or more QoS rules have been remapped.

[0155] The indication that one or more training results require modified treatment may be received from an application client. The QoS rules may be associated with a service data adaptation protocol (SDAP) layer.

[0156] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements.

[0157] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0158] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMSWhat is Claimed:1 . A wireless transmit / receive unit (WTRU) comprising: a processor that is configured to: receive configuration information that indicates a mapping of a quality of service (Qos) flow identifier (QFI) to a first data radio bearer (DRB); receive a transmission time deadline for data associated with the QFI; determine, based on a QoS profile of the first DRB and the data, a transmission time associated with the data; determine that the transmission time exceeds the transmission time deadline; based on the determination that the transmission time exceeds the transmission time deadline, transmit, to a network node, an indication that indicates a request to remap the QFI to a second DRB, wherein a QoS profile of the second DRB allows for transmission of the data within the transmission time deadline; and transmit the data via the second DRB.

2. The WTRU of claim 1 , wherein the determination that the transmission time exceeds the transmission time deadline is based on a QoS requirement of the first DRB being below a threshold.

3. The WTRU of claim 1 , wherein the QoS profile of the second DRB allowing for transmission of the data before the transmission time deadline is based on a QoS requirement of the second DRB being above a threshold.

4. The WTRU of claim 1 , wherein the configuration information indicates one or more conditions associated with when one or more QFIs are mapped to one or more DRBs.

5. The WTRU of claim 1 , wherein the configuration information is received from an application client.

6. The WTRU of claim 1 , wherein the indication that indicates the request to remap the QFI to the second DRB is included in a radio resource control (RRC) message.

7. The WTRU of claim 6, wherein the RRC message comprises a dedicated uplink RRC message.

8. The WTRU of claim 1 , wherein the processor is further configured to:transmit a confirmation indication to the network node, wherein the confirmation indication indicates that the QFI was remapped to the second DRB.

9. The WTRU of claim 1 , wherein the data becomes available for transmission after receiving the configuration information and the transmission time deadline.

10. A method for a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information that indicates a mapping of a quality of service (Qos) flow identifier (QFI) to a first data radio bearer (DRB); receiving a transmission time deadline for data associated with the QFI; determining, based on a QoS profile of the first DRB and the data, a transmission time associated with the data; determining that the transmission time exceeds the transmission time deadline; based on the determination that the transmission time exceeds the transmission time deadline, transmitting, to a network node, an indication that indicates a request to remap the QFI to a second DRB, wherein a QoS profile of the second DRB allows for transmission of the data within the transmission time deadline; and transmitting the data via the second DRB.11 . The method of claim 10, wherein the determination that the transmission time exceeds the transmission time deadline is based on a QoS requirement of the first DRB being below a threshold.

12. The method of claim 10, wherein the QoS profile of the second DRB allowing for transmission of the data before the transmission time deadline is based on a QoS requirement of the second DRB being above a threshold.

13. The method of claim 10, wherein the configuration information indicates one or more conditions associated with when one or more QFIs are mapped to one or more DRBs.

14. The method of claim 10, wherein the configuration information is received from an application client.

15. The method of claim 10, wherein the indication that indicates the request to remap the QFI to the second DRB is included in a radio resource control (RRC) message.

16. The method of claim 15, wherein the RRC message comprises a dedicated uplink RRC message.

17. The method of claim 10, wherein the method further comprises: transmitting a confirmation indication to the network node, wherein the confirmation indication indicates that the QFI was remapped to the second DRB.

18. The method of claim 10, wherein the data becomes available for transmission after receiving the configuration information and the transmission time deadline.

Images