Method, architecture, apparatus and system for radio resource control state optimization for federated learning

Abstract

Processes, methods, architectures, apparatuses, systems, devices, and computer program products for federated learning are provided. In some embodiments, a wireless transmit / receive unit (WTRU) may receive information that configures resource availability reports, as it relates to WTRU resources available for service and / or federated learning. The WTRU may receive information configuring timing information regarding when the WTRU may send a resource availability report. In some embodiments, the WTRU may send a resource availability report immediately when configured for the resource availability report. In some embodiments, when the WTRU is in a low power state, a resource availability report (e.g., a resource availability indication) may be sent. In some embodiments, the WTRU may transition to a connected state prior to sending the resource availability report.

Description

[0001] Cross - Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 421,615, filed on November 2, 2022, which is incorporated herein by reference. Field of the Invention

[0002] The present disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, devices, and systems related to radio resource control (RRC) state transitions and to control and / or user plane uplink and / or downlink transmissions. Background Art

[0003] In an example of federated learning (FL), a central artificial intelligence (AI) server trains a global model by combining local models trained by each participant (such as a wireless transmit / receive unit (WTRU)) based on model averaging techniques. In the context of FL training in wireless communications, it is necessary to coordinate FL training among WTRUs by considering the radio resource control (RRC) state of the WTRUs. Summary of the Invention

[0004] In certain representative embodiments, a process may be implemented by a WTRU and / or other network entities to configure the WTRU to report (e.g., periodically report) resource availability (e.g., associated with services and / or one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions), such as resources available for (e.g., at the WTRU) federated learning operations.

[0005] In certain representative embodiments, a process may be implemented by a WTRU to report resource availability based on one or more triggers, conditions, and / or relationships.

[0006] In certain representative embodiments, a process may be implemented by a wireless transmit / receive unit (WTRU) to report resource availability once and / or immediately.

[0007] In certain representative embodiments, a process may be implemented by a WTRU to report resource availability when in certain states such as RRC_INACTIVE (RRC inactive) and / or RRC_IDLE (RRC idle).

[0008] In certain representative embodiments, a process may be implemented by a WTRU to report resource availability when transitioning to or after transitioning to certain states such as RRC_CONNECTED (RRC connected).

[0009] In certain representative embodiments, a process may be implemented by a WTRU to report resource availability using one or more small data transmissions (SDT). BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. The figures in these drawings are examples, as in the detailed description. Similarly, the drawings (FIG.) and the detailed description should not be considered restrictive, and other equally valid examples are possible. In addition, the same reference numerals (ref.) in the drawings denote the same elements, where:

[0011] Figure 1A is a system diagram showing an example communication system;

[0012] Figure 1B is a system diagram showing an example wireless transmit / receive unit (WTRU) that can be used within the communication system shown in Figure 1A is a system diagram showing an example radio access network (RAN) and an example core network (CN) that can be used within the communication system shown in

[0013] Figure 1C is a system diagram showing an example radio access network (RAN) and an example core network (CN) that can be used within the communication system shown in Figure 1A is a system diagram showing an example radio access network (RAN) and an example core network (CN) that can be used within the communication system shown in

[0014] Figure 1D is a system diagram showing an example of federated learning interaction between various participants and a central server; Figure 1A is a system diagram showing an example of federated learning interaction between various participants and an FL training server;

[0015] Figure 2 is a system diagram showing an example of federated learning interaction between various participants and a central server;

[0016] Figure 3 is a system diagram showing an example of federated learning interaction between various participants and an FL training server;

[0017] Figure 4 is a timing diagram showing an example of a 4-step random access (RA) process;

[0018] Figure 5 is a timing diagram showing an example of a two-step RA process;

[0019] Figure 6 is a timing diagram showing an example of an RRC connection establishment / setup process;

[0020] Figure 7 is a timing diagram showing an example of an RRC connection recovery process;

[0021] Figure 8 is a state diagram showing an example of a transition between different RRC states;

[0022] Figure 9 is a syntax diagram showing an example of establishment and recovery reasons;

[0023] Figure 10 is a timing diagram showing an example of a 4-step RA process using small data transfer (SDT);

[0024] Figure 11 is a timing diagram showing an example of a 2-step RA process using SDT;

[0025] Figure 12 is a timing diagram showing an example of a configuration grant (CG) process using SDT;

[0026] Figure 13 is a process diagram showing an example process for reporting the availability of federated learning resources;

[0027] Figure 14 is a process diagram showing an example process for reporting the availability of federated learning resources using paging information; and

[0028] Figure 15 is a process diagram showing another example process for reporting the availability of federated learning resources. Detailed Description

[0029] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the following description. Additionally, embodiments and examples not specifically described herein may be practiced in lieu of or in combination with the embodiments and other examples explicitly, implicitly, and / or inherently described, disclosed, or provided (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which a device, system, apparatus, etc. and / or any of its elements perform an operation, process, algorithm, function, etc. and / or any part thereof, it should be understood that any embodiment described and / or claimed herein assumes that any device, system, apparatus, etc. and / or any of its elements is configured to perform any operation, process, algorithm, function, etc. and / or any part thereof.

[0030] Example communication system.

[0031] The methods, apparatuses, and systems provided herein are well-suited for communication involving both wired and wireless networks. Referring to Figures 1A - 1D provides an overview of various types of wireless devices and infrastructure, where various elements of the network can be utilized, execute, be arranged in accordance with, and / or be adapted and / or configured for the methods, apparatuses, and systems provided herein.

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

[0033] As Figure 1A shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop computer, a netbook, a personal computer, a wireless sensor, a hot spot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless devices operating in an industrial and / or automation processing chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0034] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, 102d, for example to facilitate access to one or more communication networks such as CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, base stations 114a, 114b may be base transceiver stations (BTSs), Node Bs (NBs), eNode-Bs (eNBs), home Node Bs (HNBs), home eNode-Bs (HeNBs), gNode-Bs (gNBs), NR Node-Bs (NR NBs), site controllers, access points (APs), wireless routers, etc. Although base stations 114a, 114b are each depicted as a single element, it should be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

[0036] Base stations 114a, 114b may communicate with one or more of WTRUs 102a, 102b, 102c, 102d via air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) may be used to establish air interface 116.

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

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

[0039] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish the air interface 116.

[0040] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base stations 114a and the WTRUs 102a, 102b, 102c can implement LTE radio access and NR radio access together, for example using the Dual Connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0041] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., 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 Rate for GSM Evolution (EDGE), GSM EDGE (GERAN), and so on.

[0042] For example, Figure 1A the base station 114b in may be a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a commercial venue, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for drones), a road, etc. 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 one 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 any one of a small cell, a picocell, or a femtocell. As Figure 1A shown, the base station 114b may have a direct connection to the Internet 110. Thus, it may not be required for the base station 114b to access the Internet 110 via the CN 106 / 115.

[0043] RAN 104 / 113 can communicate with CN 106 / 115, and CN 106 / 115 can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, 102d. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location-based services, prepaid calling, internet connectivity, video distribution, etc. and / or perform advanced security functions, such as user authentication. Although not shown in Figure 1A , it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs using the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113 which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using any one of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

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

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

[0046] Figure 1B is a system diagram showing an exemplary WTRU 102. As Figure 1B shown, among other things, the WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138. It should be understood that the WTRU 102 can include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

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

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

[0049] Although the transmit / receive element 122 is shown in Figure 1Bis depicted as a single element, but the WTRU 102 can include any number of transmit / receive elements 122. For example, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0050] The transceiver 120 can be configured to modulate signals to be transmitted by the transmit / receive elements 122 and to demodulate signals received by the transmit / receive elements 122. As described above, the WTRU 102 can have multi-mode capabilities. Thus, for example, the transceiver 120 can include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (such as NR and IEEE 802.11).

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

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

[0053] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via an air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may obtain location information by any suitable location determination method while remaining consistent with the embodiments.

[0054] The processor 118 may be further coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, (Bluetooth) module, a frequency modulation (FM) radio unit, a digital music player, a media player, an electronic game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The elements / peripherals 138 may include one or more sensors, which 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 geographical location sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, an attitude sensor, a biometric sensor, and / or a humidity sensor.

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

[0056] Figure 1CFIG. 0 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, and 102c via the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

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

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

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

[0060] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the S1 interface and may act 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 the initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide control plane functions for handover between the RAN 104 and other RANs (not shown) using other radio technologies such as GSM and / or WCDMA.

[0061] The SGW 164 can be connected via the S1 interface to each of the eNode Bs 160a, 160b, 160c in the RAN 104. The SGW 164 can typically route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions such as anchoring the user plane during handovers between eNode Bs, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a, 102b, 102c, etc.

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

[0063] The CN 106 can facilitate communication with other networks. For example, the CN 106 can provide the WTRUs 102a, 102b, 102c with access to a circuit switched network such as the PSTN 108 to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, the CN 106 can include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 can provide the WTRUs 102a, 102b, 102c with access to other networks 112, which can include other wired and / or wireless networks owned and / or operated by other service providers.

[0064] Although the WTRU is described as a wireless terminal in Figures 1A - 1D it is contemplated that in some representative embodiments, such a terminal can use (e.g., temporarily or permanently) a wired communication interface to the communication network.

[0065] In a representative embodiment, the other network 112 can be a WLAN.

[0066] Infrastructure Basic Service Set (BSS) mode WLANs can have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP can have access or an interface to a Distribution System (DS) or another type of wired / wireless network that conveys traffic to and / or from the BSS. Traffic destined for an STA from outside the BSS can reach the STA through the AP and can be delivered to the STA. Traffic originating from an STA to a destination outside the BSS can be sent to the AP to be delivered to the corresponding destination. For example, traffic between STAs within the BSS can be sent through the AP, where the source STA can send the traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer traffic. Peer traffic can be sent between the source and destination STAs (e.g., directly between them) using Direct Link Setup (DLS). In some representative embodiments, DLS can use 802.11e DLS or 802.11z Tunnel DLS (TDLS). WLANs using Independent BSS (IBSS) mode may not have an AP, and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as the "ad-hoc" communication mode.

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

[0068] High Throughput (HT) STAs can communicate using 40 MHz wide channels, e.g., by combining the primary 20 MHz channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[0069] A very high throughput (VHT) STA may support channels that are 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide. 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 eight 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, after channel coding, data may pass through a segment parser that may divide the data into two streams. Inverse fast Fourier transform (IFFT) processing and time - domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations of the above 80 + 80 configuration may be reversed, and the combined data may be sent to the media access control (MAC) layer, entity, etc.

[0070] 802.11af and 802.11ah support operation modes below 1 GHz. The channel operation bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non - TVWS spectrum. According to a representative embodiment, 802.11ah may support metering type control / machine type communication (MTC), such as MTC devices in a macro - coverage area. MTC devices may have certain capabilities, for example, limited capabilities, including supporting (e.g., only supporting) certain and / or limited bandwidths. MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0071] A WLAN system that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) includes a channel that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or restricted by an STA among all STAs operating in the BSS that supports the minimum bandwidth operation mode. In the example of 802.11ah, for an STA that supports (e.g., only supports) the 1MHz mode (e.g., an MTC-type device), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, e.g., due to an STA (that only supports the 1MHz operation mode) transmitting to the AP, the entire available frequency band can be considered busy, even if most of the frequency band remains idle and may be available.

[0072] In the United States, the available frequency band that 802.11ah can use is from 902MHz to 928MHz. In Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is from 6MHz to 26MHz, depending on the country code.

[0073] Figure 1D FIG. is a system diagram showing RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

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

[0075] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol interval and / or the OFDM subcarrier interval may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and / or an absolute time of continuously varying length).

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

[0077] Each of gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slice support, dual connectivity, interworking between NR and E-UTRA, routing user plane data to user plane functions (UPFs) 184a, 184b, routing control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As Figure 1D shown, gNBs 180a, 180b, 180c can communicate with each other via the Xn interface.

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

[0079] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing the registration area, terminating NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing, for example, to customize the CN support for the WTRUs 102a, 102b, 102c based on the type of service utilized by the 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, etc. The AMF 162 may provide control plane functions for handover between the RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as Wi-Fi.

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

[0081] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide access to a packet switched network (e.g., the Internet 110) to the WTRUs 102a, 102b, 102c, for example to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

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

[0083] In view of Figures 1A - 1D and Figures 1A - 1D In view of the corresponding descriptions of, one or more or all of the functions described herein for any one of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b and / or any other element / devices described herein can be performed by one or more emulation elements / devices (not shown). The emulation devices can be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices can be used to test other devices and / or simulate network and / or WTRU functions.

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

[0085] One or more simulation devices can perform one or more functions, including all functions, without being implemented / deployed as part of a wired and / or wireless communication network. For example, a simulation device can be used to test test scenarios in a laboratory and / or a non-deployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test devices. A simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication via an RF circuit (e.g., which can include one or more antennas).

[0086] Introduction

[0087] The following abbreviations and acronyms may be used herein:

[0088] 5GC 5G Core

[0089] AI Artificial Intelligence

[0090] AC Application Client

[0091] AMF Access and Mobility Management Function

[0092] AS Application Server

[0093] AF Application Function

[0094] AN Access Network

[0095] CN Core Network

[0096] CP Control Plane

[0097] ML Machine Learning

[0098] NAS Non-Access Stratum

[0099] NF Network Function

[0100] PCF Policy Control Function.

[0101] PDCP Packet Data Convergence Protocol

[0102] RAN Radio Access Network

[0103] RLC Radio Link Control

[0104] RRC Radio Resource Control

[0105] SMF Session Management Function

[0106] SDAP Service Data Adaptation Protocol

[0107] UE User Equipment

[0108] UP User Plane

[0109] UPF User Plane Function

[0110] Overview

[0111] AI / ML Services in the System

[0112] In certain representative embodiments, one or more WTRUs may interact with network functions (NFs) in a 5G core network. For example, WTRU 102 may interact with any one of an AI / ML function (AIMLF), a federated learning function (FLF), an application server (AS), and / or an application function (AF) via the user plane (e.g., via UPF) and / or the control plane (e.g., via NAS signaling). In the case of UP interaction, WTRU 102 may need to interact with at least the AS and / or AF via a data radio bearer (DRB) that is established between WTRU 102 and the NG-RAN over the Uu air interface.

[0113] AI / ML Metadata and Operations

[0114] In certain representative embodiments, metadata may include any one of model topology, model weights, training completion time window, and / or other AI / ML specific parameters. For example, AI / ML parameters may include, but are not limited to, any one of loss function, entropy, prediction accuracy, etc. In certain representative embodiments, AI / ML operations may be classified as: (i) model distribution; (ii) model splitting between AI / ML endpoints; and (iii) federated learning.

[0115] Federated Learning

[0116] In some representative embodiments, a (e.g., central) AI server or functionality can operate in a federated learning (FL) mode. The central AI server can train a global (or central) model, such as by a director combining a set of local models trained by various participants (e.g., WTRUs) based on model averaging. A WTRU can perform local model training (e.g., within each training cycle) using local data (e.g., obtained by the WTRU) based on a model downloaded from a (e.g., centralized) AI server. This training can use a set of resources at the WTRU 102. For example, the training may require a set of resources available at the WTRU 102 (e.g., within a particular time period). For example, the set of resources can include any one of the battery power (e.g., level) of the WTRU 102, the amount of memory of the WTRU 102, and / or the processor capacity of the WTRU 102. Once the local model training is complete, the WTRU 102 can deliver the training results (e.g., gradients of a deep neural network - DNN) to the centralized AI server, such as via an UL channel. Next, the (e.g., centralized) AI server can aggregate the gradients (e.g., model weights) from the WTRUs and update the global (or central) model. For example, the next training cycle can begin, where the AI server distributes the updated global model to one or more WTRUs, such as via a DL channel.

[0117] Figure 2 FIG. is a system diagram showing an example of a federated learning system having various participants 202 and a central server 204 (such as a 5G or 6G cloud).

[0118] In some representative embodiments, FL training over wireless communication, where participants (e.g., WTRU 102) may have highly variable conditions in terms of available computing (e.g., memory and / or processing capabilities) and network resources, may (e.g., slightly) differ from FL training in a data center. In some representative embodiments, WTRU 102 may not be homogeneous, and thus WTRU 102 may have different capabilities in terms of corresponding computing and network-related resources and / or even what AI and / or ML frameworks (e.g., functions and / or models) they support. For example, it may not be efficient for a centralized AI server to include all participants 202 (e.g., WTRU 102) in a training session, and thus some kind of member selection mechanism may be needed before the start of each training cycle. For example, it may be considered that, given constant conditions (e.g., device computing resources and / or wireless channel conditions), WTRU may not need to be (re)-selected and training reconfigured for each training cycle. In some examples, it may be beneficial (e.g., crucial) to (re)-select different WTRU 102 over time to achieve global training with different datasets. For example, computing resources may include any one of battery power (e.g., percentage of total battery power), memory (e.g., in megabytes), and / or processing (e.g., percentage of total CPU and / or GPU) capabilities.

[0119] Figure 3 is a system diagram showing an example of federated learning interaction between various participants 202 (e.g., devices A-E, such as WTRU 102) and an FL training server 302.

[0120] In Figure 3 , the FL scenario may include a set of participants 202 (e.g., devices A-E) involved in a distributed training session. For example, not all devices (e.g., WTRU 102) participate in all training cycles. In some training cycles, some WTRU 102 may be inactive, while in other sessions, WTRU 102 may be configured to perform local model training. For example, device A may initially (e.g., during the Nth cycle) participate in a training session, but after device A reports its training resources, the centralized FL server 302 may not (re)-select device A for the next cycle (e.g., the N+1th cycle). For example, the FL server 302 may instead select device B (e.g., which was inactive during the Nth cycle). In some representative embodiments, there may be periods and / or cycles during which WTRU 102 or the FL server 302 may be inactive between and / or during training sessions.

[0121] In certain representative embodiments, one (e.g., each) FL training cycle can be classified into three operational phases. In the first operational phase, the FL training server 302 can select a set of devices (e.g., WTRU 102) for training. During this phase, the training devices (e.g., WTRU 102) can first notify the FL training server 302 of their training resources. Once the FL server 302 has collected the resource information from the training devices, the FL training server 302 can select some WTRU102 (e.g., a set of WTRU 102). The FL server 302 can then move to the next operational phase of model distribution and training configuration. Here, the FL server 302 can distribute the globally trained model and associated configuration to all selected devices (e.g., WTRU 102). After receiving the globally trained model and associated configuration, the selected devices can start local model training, such as at one or more different time points. Once local training is completed at the device, the locally trained model and / or associated training information can be delivered to the FL server 302. After receiving the locally trained model and / or associated training information, a third operational phase can begin. During this phase, the FL server 302 can aggregate any (e.g., all) training results to form (e.g., an updated) global model. Thereafter, the entire training workflow can be repeated one or more times.

[0122] 2-step and 4-step random access procedures

[0123] For example, random access can be performed in a contention-based manner (e.g., contention-based random access (CBRA)) or a contention-free manner (e.g., contention-free random access (CFRA)). Two types of random access supported in NR are 4-step RA and 2-step RA. For example, the 4-step RACH procedure can be performed together with the RRC resume / setup procedure. For example, in cases where latency is important, the 2-step RACH procedure may be useful because the signaling exchange required to complete the random access procedure is reduced.

[0124] Figure 4 is a timing diagram showing an example of a 4-step random access procedure. In Figure 4In [this process], it can start at 402, where the WTRU 102 sends Msg1 containing a preamble on the PRACH to the gNB 180. After the MSG1 transmission, at 404, the WTRU 102 can monitor for a random access response (e.g., RAR / Msg2) from the network within a configured window. After receiving an RAR containing a UL grant and a timing advance command, the WTRU 102 can apply the timing advance command and send Msg3 at 406 using the UL grant provided in the RAR. After the Msg3 transmission, at 408, the WTRU 102 can monitor for a network response (e.g., Msg4) containing contention resolution information.

[0125] For example, in the case of successful contention resolution, random access is completed, and the WTRU 102 starts connecting to the gNB 180. In the case of failed contention resolution, the WTRU 102 can restart the random access process via the transmission of (e.g., another) Msg1.

[0126] Figure 5 is a timing diagram showing an example of a two-step random access process. In Figure 5 In [this process], the two-step random access can start with the transmission of MsgA to the gNB at 502, where MsgA includes a preamble on the PRACH and a payload on the PUSCH. After the MsgA transmission, at 504, the WTRU 102 can monitor for a response (e.g., MsgB) from the gNB within a configured window containing information about contention resolution.

[0127] For example, in the case of successful contention resolution, the WTRU 102 can terminate the random access process. In the case of failed contention resolution and a fallback indication provided in MsgB, the WTRU 102 can perform a Msg3 transmission using the UL grant contained in the MsgB fallback indication and start monitoring for contention resolution. In the case of failed contention resolution again after the Msg3 transmission, the WTRU 102 can revert to the MsgA transmission. If the MsgA transmission fails a configured number of times, the WTRU 102 can revert to a four-step random access.

[0128] The type of random access process to use can be selected when initiating the random access process, such as based on network configuration. When contention-free random access resources are configured, depending on whether the random access resources correspond to two-step or four-step, the WTRU 102 can perform four-step or two-step random access. If no contention-free random access resources are provided, the WTRU 102 can choose between four-step and two-step random access, such as based on an RSRP threshold.

[0129] RRC State and State Transitions

[0130] In NR, the WTRU 102 can be in one of the following three RRC states: (i) RRC_CONNECTED (also referred to herein as the connected mode / status); (ii) RRC_INACTIVE (also referred to herein as the inactive mode / status); and (iii) RRC_IDLE (also referred to herein as the idle mode / status).

[0131] In RRC_CONNECTED, the WTRU 102 is actively connected to the network, establishes signaling and data radio bearers (e.g., SRBs and DRBs), and is capable of receiving downlink (DL) data from the network in unicast and also sending uplink (UL) data to the network. The network can control the mobility of the WTRU 102 from one cell and / or node to another cell and / or node. The network can configure the WTRU 102 to send measurement reports periodically or when certain conditions are met (e.g., an adjacent cell becomes better than the serving cell by more than a certain threshold), and based on these reports, can send a handover command to the WTRU 102 to move the WTRU 102 to another cell and / or node. The network can also configure conditional handover CHO, where (e.g., instead of sending measurement reports), when certain conditions are met, the WTRU 102 can execute a pre-configured handover command. The network can also send a HO command to the WTRU 102 without receiving any measurement reports (e.g., based on an implementation, such as the determination of the current location).

[0132] For example, keeping the WTRU 102 in the connected mode can be power-intensive for the WTRU 102 (e.g., the WTRU 102 needs to continuously monitor the PDCCH of the serving cell, such as for determining the arrival of DL data, for UL data scheduling, etc.), and a certain cell and / or gNB may (e.g., only) be able to accommodate a certain number of WTRUs in the connected mode (e.g., due to resource limitations). When there is no activity in the UL and / or DL for a certain duration (e.g., based on an inactivity timer saved in the network), the network can send the WTRU 102 to the RRC_INACTIVE or RRC_IDLE state.

[0133] For example, in the case where the network expects the WTRU 102 to be active for a long duration, the network may send the WTRU 102 to the RRC_IDLE state. When in RRC_IDLE, the WTRU 102 may camp on a cell (e.g., the cell with the best signal level at the highest priority RAT and the highest priority frequency within that RAT), which will assist the WTRU 102 in establishing a connection via that cell if there is a need for the WTRU 102 to transition back to the connected state. More details of the cell reselection process that ensures the WTRU 102 always camps on the best cell will be described later. The WTRU 102 may also monitor the downlink paging channel to detect the arrival of DL data. The WTRU 102 may initiate a connection setup / establishment process, such as in the case where the WTRU 102 detects paging information indicating the arrival of DL data from the network, or in the case where the WTRU 102 needs to send UL data. The following figure shows the RRC connection establishment / setup and connection re-establishment processes.

[0134] Figure 6It is a timing diagram showing an example of the RRC connection establishment / setup process. At 602, the WTRU 102 can be in RRC_IDLE and CM-IDLE. At 604, the WTRU can send an RRCSetupRequest (RRC setup request) message to the gNB 180. At 608, the WTRU 102 can receive an RRCSetup (RRC setup) message from the gNB 180. At 610, the WTRU 102 can be in RRC_CONNECTED and CM-IDLE. At 612, the WTRU 102 can send an RRCSetupComplete (RRC setup complete) message to the gNB 180. At 614, the gNB 180 can send an initial UE message to the AMF 182. At 616, the WTRU can be in RRC_CONNECTED and CM-CONNECTED. At 618, the AMF 182 can send a DL NAS transport message to the gNB 180. At 620, the WTRU 102 can receive DL information from the gNB 180. At 622, the WTRU 102 can send UL information to the gNB 180. At 624, the AMF 182 can receive a ULNAS transport message. At 626, the AMF can send an initial context setup request message to the gNB 180. At 628, the WTRU 102 can receive a security mode command from the gNB 180. At 630, the WTRU 102 can reply to the gNB 180 with the security mode command. At 632, the WTRU 102 can receive an RRCReconfiguration (RRC reconfiguration) message from the gNB 180. At 634, the WTRU 102 can send an RRCReconfigurationComplete (RRC reconfiguration complete) message to the gNB 180. At 636, the AMF 182 can receive an initial context setup response from the gNB 180.

[0135] It can be seen from Figure 6 that the RRC connection setup process is a lengthy process that requires several round-trip times (RTT) to complete and it involves the core network (CN) 115. This is because when the WTRU 102 enters the IDLE mode, the RRC context of the WTRU is released and the WTRU 102 is unknown at the RAN level and the RAN 113 has to obtain the WTRU102 context from the CN 115. In addition, security has to be re-established afterwards and the WTRU 102 is reconfigured with DRBs and SRBs before UL / DL data transmission / reception can take place.

[0136] This lengthy setup process may not be compatible with low latency services, so 5G NR has introduced an intermediate state between the CONNECTED and IDLE states, called the INACTIVE state. The INACTIVE state has most of the power saving advantages of the IDLE state (e.g., the WTRU 102 does not need to continuously monitor the PDCCH, which is one of the most power consuming processes in the CONNECTED state), but at the same time, the RAN maintains the RRC / security context of the WTRU. When it is necessary to transition the WTRU 102 to the CONNECTED mode (e.g., due to the arrival of UL data or the reception of a paging indicating the arrival of DL data), the connection can be restored very quickly without involving the CN 115, re - establishing the security context of the WTRU, and re - configuring the bearers.

[0137] Figure 7 is a timing diagram showing an example of the RRC connection restoration process. At 702, the WTRU is in the RRC_INACTIVE and CM - CONNECTED states. At 704, the WTRU 102 can send an RRC Resume Request message to the gNB 180 - 1. At 706, the gNB 180 - 1 can send a UE context request to the last serving gNB 180 - 2. At 708, the gNB 180 - 2 can send a UE context response to the gNB 180 - 1. At 710, the gNB 180 - 1 can send an RRC Resume message to the WTRU 102. At 712, the WTRU is in the RRC_CONNECTED and CM - CONNECTED states. At 714, the WTRU can send an RRC Resume Complete message to the gNB 180 - 1. At 716, the gNB 180 - 1 can send an Xn - U address indication to the gNB 180 - 2. At 718, the gNB 180 - 1 can send a path switch request to the AMF 182. At 720, the AMF 182 can send a path switch request response to the gNB 180 - 1. At 722, the gNB 180 - 1 can send a UE context release to the gNB 180 - 2.

[0138] Figure 8 is a state diagram showing an example of the transitions between different 5G NR RRC states. At Figure 8In this context, a resume request can be used to transition the WTRU 102 from RRC_INACTIVE 802 to RRC_CONNECTED 804. A release request with a pending release can be used to transition from RRC_CONNECTED 804 to RRC_INACTIVE 802. A release request can be used to transition from RRC_INACTIVE 802 (or RRC_CONNECTED 804) to RRC_IDLE 806. A setup request with a pending setup can be used to transition from RRC_IDLE 806 to RRC_CONNECTED 804. When the WTRU 102 performs a connection setup / establishment or resume procedure, the WTRU 102 can include (e.g., in an RRCSetupRequest (RRC setup request) or an RRCResumeRequest (RRC resume request)) setup or resume cause information.

[0139] Figure 9 is a syntax diagram showing examples of setup and resume causes. For example, the setup cause information 902 can be indicated as various values that can be associated with (e.g., predefined) causes, such as Figure 9 shown. For example, the resume cause information 904 can be indicated as various values that can be associated with (e.g., predefined) causes, such as Figure 9 shown.

[0140] In some representative embodiments, the connection can be set up and / or resumed due to a voice call and / or a video call originating from the WTRU 102. For example, the WTRU 102 can set up the setup or resume cause to indicate a "mo-voice call" (e.g., a mobile-originated voice call) or a "mo-video call" (e.g., a mobile-originated video call). As another example, the connection can be established and / or resumed due to receiving a downlink paging indicating DL data (e.g., for the WTRU 102). The WTRU 102 can set the setup or resume cause to indicate one of "mt-access" (mobile-terminated access), "high-priority access", "mps-priority access", or "mcs-priority access". The specific cause may depend on the access category of the WTRU 102.

[0141] In some representative embodiments, the WTRU 102 can be sent to the inactive state, and the network can include a suspendConfig (suspend configuration) information element in an RRCRelease (RRC release) message. For example, the suspendConfig (suspend configuration) can include information indicating any of the following: resumeIdentity (resume identity), RAN paging area, and / or nextHopChaining (next-hop chaining) count.

[0142] For example, the WTRU 102 may use resumeIdentity (e.g., short identity / short I-RNTI and / or long identity / full I-RNTI) in RRC_INACTIVE. The WTRU 102 may determine which identity to use based on the system information broadcast in the target cell (e.g., use the long identity if useFullResumeID is indicated in the SIB, otherwise use the short identity).

[0143] For example, the RAN paging area may indicate a list of cells or otherwise be associated with a list of cells. The list of cells may be a RAN area where the WTRU 102 may be paged at the RAN level. The WTRU 102 may perform cell reselection to a cell outside the RAN area, and the WTRU 102 may perform a RAN area update procedure. The WTRU 102 may send a resume request with a cause value indicating the reason for the RAN area update, and the network may respond with a release message. This release message may configure the WTRU 102 with a new RAN area. This process may be referred to as a two-step resume process.

[0144] For example, the nextHopChaining count may be used to derive a security context (e.g., encryption / integrity protection keys) when resuming a connection.

[0145] In some embodiments, there may be a one-to-one mapping between RRC and CM (e.g., with one exception). For example, the RRC state may be in the CONNECTED mode, and the CM state may also be in the CONNECTED mode. For example, when the RRC state is in the IDLE mode, then the CM state may be in the idle mode. As an example of an exception to the one-to-one mapping, the WTRU 102 may be in the CM_CONNECTED mode, and the RRC state may be in the INACTIVE mode.

[0146] SDT in 5G systems

[0147] In 5G NR Release 15, a WTRU 102 in RRC inactive may (e.g., always have to) resume the RRC connection for any UL / DL data transmission / reception. From the perspective of WTRU power consumption, it is very inefficient to resume the connection even for some small infrequent small payload data (e.g., for periodic and / or event-triggered information reporting).

[0148] In 5G NR Release 17, Small Data Transfer (SDT) enables a WTRU 102 in RRC Inactive state to perform data transfer, such as without RRC state transition. For example, in Release 17, various SDT procedures have been standardized. Discussions on how to enhance SDT for DL transmission have emerged in Release 18.

[0149] Random Access Channel (RACH) SDT

[0150] In some representative embodiments, a 4-step RA procedure may include SDT.

[0151] Figure 10 is a timing diagram showing an example of a 4-step RA procedure with SDT. In Figure 10 , at 1002, the WTRU 102 may be in RRC Inactive. At 1004, a new UL payload (e.g., waiting to be transmitted) may be provided in the buffer of the WTRU 102. At 1006, the WTRU 102 may send Msg1 (e.g., PRACH preamble) to the gNB 180. At 1008, the WTRU 102 may receive Msg2 (e.g., RA response) from the gNB 180. At 1010, the WTRU 102 may send Msg3 (e.g., RRC resume request). For example, Msg3 may carry (e.g., include) the UL payload as SDT information. At 1012, the WTRU 102 may receive Msg4 from the gNB180. For example, at 1014, Msg4 may be an RRC release with a suspend indication from the gNB to keep the WTRU 102 in RRC_INACTIVE.

[0152] In some representative embodiments, a two-step RA procedure may include SDT.

[0153] Figure 11 is a timing diagram showing an example of a two-step RA procedure with SDT. In Figure 11 , at 1102, the WTRU 102 may be in RRC Inactive. At 1104, a new UL payload (e.g., waiting to be transmitted) may be provided in the buffer of the WTRU 102. At 1106, the WTRU 102 may send MsgA to the gNB. For example, MsgA may include a PRACH preamble and a PUSCH transmission, which carry (e.g., include) an RRC resume request and / or a UL payload (e.g., which was buffered at 1104) as SDT information. At 1108, the WTRU 102 may receive MsgB from the gNB 180. For example, MsgB may be an RRC release with a suspend indication from the gNB 180 to keep the WTRU 102 in RRC_INACTIVE.

[0154] For example, UL payload transmission occurs in MsgA of the two-step RA procedure. The UL payload transmission can use the PUSCH resources pre-configured by the gNB 180 and broadcast in the system information, such as the associated physical transmission parameters (e.g., the number and / or location of physical resource blocks (PRBs), modulation and coding scheme (MCS)). Receiving a successful random access response (RAR) message including an RRC release with a pending indication at 1108 can indicate that the WTRU 102 remains in RRC_Inactive.

[0155] For example, SDT based on two-step RA can reduce packet delay and associated signaling overhead (e.g., compared to four-step RASDT). However, the two-step RA delay may increase if a collision occurs when multiple WTRU 102 compete for the same shared PUSCH resource while transmitting MsgA separately.

[0156] Configured grant (CG) transmission.

[0157] Figure 12 is a timing diagram showing an example of a configured grant (CG) procedure with SDT.

[0158] In some representative embodiments, the WTRU 102 can perform SDT based on CG. For example, the UL payload can be sent on pre-configured PUSCH resources, such as when the WTRU 102 has a valid timing advance (TA). For example, the SDT can be a CG-type1 transmission.

[0159] In Figure 12In [the figure], at 1202, the WTRU 102 may be in an RRC connection. At 1204, the WTRU 102 may send a CG request and / or UE assistance information to the gNB 180. At 1206, the WTRU 102 may receive an RRCRelease (RRC release) message with a suspension indication. For example, the message may include one or more CG configurations and / or TA timers (e.g., timer values). At 1208, the WTRU is in RRC inactivity. At 1210, a new UL payload (e.g., waiting to be transmitted) may be provided in the buffer of the WTRU 102, and the WTRU 102 may determine that the TA with the gNB 180 is valid. At 1212, the WTRU 102 may send a CG-based PUSCH transmission that carries an RRCResumeRequest (RRC resume request) message and the UL payload (e.g., which was buffered at 1210). At 1214, the WTRU 102 may receive an RRCRelease (RRC release) message with a suspension indication from the gNB 180. At 1216, the WTRU 102 may remain in RRC inactivity (e.g., not transition to an RRC connection).

[0160] In some representative embodiments, when in an RRC connected state, the WTRU 102 may request one or more CG configurations (e.g., based on a data traffic pattern). For example, the CG configuration may be received as part of an RRC release with a suspension indication. The CG configuration may be WTRU-specific. Among other information, the received CG configuration may include PUSCH resource allocation and periodicity.

[0161] As can be seen from Figure 3 it, the WTRU may wish to notify the network (e.g., an FL training entity) about the availability of training. Based on the notified availability and training requirements, the network may select a subset of devices to perform training and send training results (e.g., updated metadata) when ready (e.g., when the training converges according to convergence criteria).

[0162] For example, requiring the WTRU to be in a connected state for all phases of Figure 3 (e.g., training resource availability reporting, receiving model updates, training, sending training results, etc.) may be (e.g., very) inefficient for the power consumption of the WTRU 102 unless the WTRU 102 also has active UL / DL user plane data at the same time.

[0163] In some representative embodiments, the WTRU 102 may perform one or more procedures such that the WTRU 102 is connected to a PLMN via an access point (e.g., a gNB) and has thus performed a registration procedure.

[0164] In certain representative embodiments, the WTRU 102 may support the RRC_INACTIVE state. The network may check it using UE capability information.

[0165] In certain representative embodiments, the RAN (e.g., 5G RAN) may support data and analytics exposure to the AS / AF via the core network (e.g., 5GC). For example, the AS / AF may subscribe to or request data and / or analytics from the core network and the RAN.

[0166] In certain representative embodiments, the core network may employ a dedicated network function to handle AIML workflows, such as FL.

[0167] In certain representative embodiments, the WTRU 102 may operate in a low-power state. As used herein, a low-power state, a low-power operating mode, and / or a lower-power state may refer to any state other than the RRC_CONNECTED state (e.g., a higher-power operating mode). For example, the (relatively) low-power state may refer to RRC_INACTIVE. In another example, the (relatively) low-power state may refer to RRC_IDLE. In another example, it may refer to a state between the RRC_CONNECTED state and the RRC_INACTIVE state, where the DCI monitoring level of the WTRU 102 is between the (e.g., typical) levels of the RRC_CONNECTED state and the RRC_INACTIVE state.

[0168] Configuration for reporting resource availability of federated learning

[0169] In certain representative embodiments, the WTRU 102 may receive information indicating one or more configurations, including information associated with reporting resource availability of federated learning.

[0170] In certain representative embodiments, the WTRU 102 may be configured by the network to report its resource availability for federated learning.

[0171] In certain representative embodiments, the WTRU 102 may be configured by the network to stop reporting its resource availability for federated learning.

[0172] In certain representative embodiments, the WTRU 102 may be configured to send information indicating resource availability in a periodic manner (e.g., every X seconds).

[0173] In certain representative embodiments, the WTRU 102 may be configured with start and / or stop times (e.g., absolute time, relative time from receipt of configuration, etc.) for providing resource availability. For example, the WTRU 102 may be configured with a periodic report of X seconds and a stop time of t_stop. The WTRU 102 may send resource availability information to the network every X seconds until the specified stop time has elapsed.

[0174] In certain representative embodiments, the WTRU 102 may be configured with the number of resource availability reports (e.g., requested) to be sent to the network. For example, the WTRU 102 may be configured with a periodic report of X seconds and a report number of N. The WTRU 102 may send N resource availability reports to the network, each spaced X seconds apart. In another example, the WTRU 102 may be configured with N = 1 and t_start. The WTRU 102 may send (e.g., only) one resource availability report at the specified t_start.

[0175] In certain representative embodiments, the WTRU 102 may be configured to report resource availability associated with AI / ML RAN functions. For example, the reported resource availability may be configured to be associated with the name of the function (e.g., radio resource management, beam management, positioning, etc.). For example, the reported resource availability may be configured to be associated with the identification (e.g., ID) of the model of the AI / ML RAN function.

[0176] In certain representative embodiments, the WTRU 102 may be configured to report the resource availability of multiple AI / ML RAN functions and / or AI / ML models at once. For example, the WTRU 102 may provide a report with information indicating different resource availabilities associated with different AI / ML functions and / or models at their respective configured reporting times.

[0177] In certain representative embodiments, the WTRU 102 may be configured to report the resource availability of any (e.g., all) AI / ML RAN functions and / or models (e.g., supported by the WTRU 102).

[0178] In certain representative embodiments, when in the CONNECTED mode, the WTRU 102 may receive configuration information for resource availability reporting via (e.g., dedicated) signaling (e.g., RRC reconfiguration message, NAS message, etc.).

[0179] In some representative embodiments, the WTRU 102 may receive configuration information for resource availability reporting when transitioning to a lower power state. For example, the WTRU 102 may receive the configuration information (e.g., via an RRC release message) during any transition to INACTIVE or IDLE.

[0180] In some representative embodiments, the WTRU 102 may receive configuration information for resource availability reporting when transitioning to the CONNECTED state (e.g., an RRC resume message, an RRC setup message).

[0181] In some representative embodiments, the WTRU 102 may receive configuration information for resource availability reporting via broadcast signaling. For example, one or more of any (e.g., new) information elements in system information (e.g., SIB1, SIB2, etc.) and / or in a (e.g., new) SIBx for AI / ML-related configuration may be used to receive the configuration information.

[0182] In some representative embodiments, when in the CONNECTED state, the WTRU 102 may have received a resource availability reporting configuration. For example, the WTRU may maintain the reporting configuration when transitioning to a lower power state (e.g., INACTIVE or IDLE state).

[0183] In some representative embodiments, when the WTRU 102 determines that a (e.g., new or updated) resource availability reporting configuration is available via broadcast signaling, such as via dedicated signaling, it may release any (e.g., previous) resource availability reporting configuration that it may have received earlier and may apply the broadcast configuration.

[0184] In some representative embodiments, when the WTRU 102 determines that it has received a (e.g., previous) resource availability reporting configuration via dedicated signaling (e.g., RRC reconfiguration, RRC release, RRC resume, RRC setup, etc.), it may ignore (e.g., discard) the resource availability reporting configuration available via broadcast signaling.

[0185] In some representative embodiments, the WTRU 102 may receive configuration information for resource availability reporting via a paging message (e.g., RAN paging or CN paging). For example, the paging message may be an individual WTRU paging or a group paging message. For example, a group paging identifier may be assigned for resource availability reporting (e.g., for any reporting, for reporting on a specific AI / ML function, for reporting on a specific AI / ML model, etc.). Any (e.g., each) WTRU 102 starts resource availability reporting (e.g., conditional on the WTRU 102 being assigned the paging identifier) when detecting a paging indication associated with the paging identifier.

[0186] In certain representative embodiments, the WTRU 102 may be configured with a reporting configuration according to any of the above embodiments. The WTRU 102 may wait to receive information (e.g., a configuration and / or signal from the network) indicating activation of the reporting configuration. For example, any one of a dedicated RRC message (e.g., RRC reconfiguration, RRC release, RRC resume, RRC setup), a broadcast RRC message (e.g., SIB signaling), a MAC CE, a DCI, and / or a paging message (e.g., an indication therein) may be used to activate the reporting configuration.

[0187] In certain representative embodiments, according to any of the above solutions, the WTRU 102 may be configured to stop and / or deactivate a previously configured reporting configuration. For example, any one of a dedicated RRC message (e.g., RRC reconfiguration, RRC release, RRC resume, RRC setup), a broadcast RRC message (e.g., SIB signaling), a MAC CE, a DCI, and / or a paging message (e.g., an indication therein) may be used to deactivate the reporting configuration.

[0188] In one solution, if the WTRU 102 has received a reporting configuration regarding a number of AI / ML functions or / and models, the activation or deactivation signal may include an identification of the relevant function or / and model(s) (or an indication to activate / deactivate all functions or / and models).

[0189] Resource availability report

[0190] In certain representative embodiments, the WTRU 102 may send a resource availability report that includes a (e.g., binary) indication of whether there are (e.g., sufficient) resources available at the WTRU 102 (e.g., whether the WTRU 102 is able to perform training).

[0191] In certain representative embodiments, the resource availability report may include timing information (e.g., when the WTRU 102 can start training, how long the WTRU 102 can perform training, etc.).

[0192] In certain representative embodiments, the resource availability report may include the cost of training for the respective WTRU 102 (e.g., how much battery power the training will use, such as in percentage, how long the training is expected to take, etc.).

[0193] In some representative embodiments, the WTRU 102 may be configured with a reporting configuration for a number of AI / ML functions / models. The WTRU 102 may send a resource availability report that includes a bitmap. For example, each bit of the bitmap may indicate the availability or unavailability of resources for a given function and / or model. For example, the WTRU 102 may be configured to report the resource availability related to 8 AI / ML models. The WTRU 102 may send an octet bitmap, where each bit is associated with a specific one of the 8 AI / ML models. For example, 0 may indicate that the resources are unavailable, and 1 may indicate that the resources are available, and vice versa. The order of the bits may be according to the model ID, for example, in ascending or descending order, or according to some pre-configured association of the bitmap and different models.

[0194] In some representative embodiments, the WTRU 102 may be configured with a reporting configuration for a number of AI / ML functions and / or models, and the resource availability report may be multiple bitmaps. For example, any (e.g., each) bitmap may indicate the resource availability for performing the training of a corresponding combination of different functions and / or models. For example, the WTRU 102 may be configured to report the resource availability of AI / ML models 0 to 7, and the WTRU 102 may send the following bitmaps: (i) 11100000; (ii) 10110000; (iii) 00111000; and (iv) 00010010.

[0195] For example, the first bitmap (i) may indicate that the WTRU 102 may perform the training of models 7, 6, and 5 together. The second bitmap (ii) may indicate the training of models 7, 5, and 4 together. The third bitmap may indicate the training of models 5, 4, 3 together. The fourth bitmap may indicate the training of models or models 4 and 1 together.

[0196] In some representative embodiments, the WTRU 102 may include (e.g., additional) timing and / or cost-related information, such as the above bitmap-based examples.

[0197] Resource availability report

[0198] In some representative embodiments, the WTRU 102 in the CONNECTED state may send a resource availability report to the network in a NAS message.

[0199] In certain representative embodiments, the WTRU 102 in the CONNECTED state may send a resource availability report to the network in an RRC message. For example, an existing message may be used to send a resource availability report, such as a UE assistance information message or a measurement report. For example, a new RRC message may be defined to send a resource availability report.

[0200] In certain representative embodiments, the WTRU 102 in the CONNECTED state may send a resource availability report in a MAC CE to the network.

[0201] In certain representative embodiments, the WTRU 102 in the CONNECTED state may send a resource availability report to the network using uplink control information (UCI). For example, the UCI may be a scheduling request (SR) that implicitly indicates resource availability or unavailability.

[0202] In certain representative embodiments, a WTRU 102 in a low power state (e.g., IDLE or INACTIVE state) may use a preconfigured RACH preamble to send a resource availability report (e.g., indication), such as during a 2-step and / or 4-step RACH procedure. For example, the WTRU 102 may be configured with a RACH preamble to indicate that resources are available for training of a corresponding AI / ML model and / or function, and another RACH preamble to indicate that resources are not available for training of a corresponding AI / ML model and / or function. For example, the WTRU 102 may be configured with a set of different RACH preambles, each preamble indicating resource availability for corresponding training of one or more RAN functions.

[0203] In certain representative embodiments, a WTRU 102 in a low power state (e.g., IDLE or INACTIVE state) may trigger an RRC connection recovery and / or connection setup to send a resource availability report (e.g., indication). For example, the WTRU 102 may send an RRCResumeRequest (RRC recovery request) or RRCSetupRequest (RRC setup request) message with a (e.g., new) cause value (e.g., ai_ml_report_available).

[0204] In certain representative embodiments, the WTRU 102 may be configured to use different WTRU identities (e.g., a recovery identity, an initial WTRU identity, etc.) in connection recovery and / or connection setup messages. For example, each identity may be associated with an indication of the availability or unavailability of resources for performing training of a corresponding AI / ML function / model or set of AI / ML functions or models.

[0205] In certain representative embodiments, in response to an RRC Resume Request or an RRC Setup Request, the WTRU 102 may receive an RRC Resume or an RRC Setup message. The WTRU 102 may transition to the CONNECTED state and may use any of the examples described herein (e.g., NAS, RRC, MAC CE, UCI, etc.) for a CONNECTED UE to send a resource availability report.

[0206] In certain representative embodiments, the WTRU 102 may use SDT to send a resource availability report (e.g., without transitioning to the CONNECTED state). For example, during a 4-step RACH SDT, the resource availability report may be sent with Msg 3. For example, during a 2-step RACH SDT, the resource availability report may be sent with Msg A. For example, the resource availability report may be sent with a resume request via a configured grant.

[0207] In certain representative embodiments, the WTRU 102 may receive an RRC Release message in response to an RRC Resume Request and / or an RRC Setup Request that it has sent (e.g., if resource availability reporting is implicitly / explicitly indicated in the resume / setup request, if resource availability reporting is explicitly indicated with SDT, etc.).

[0208] In certain representative embodiments, the WTRU 102 may have indicated a first (e.g., implicit or short) resource availability report and the network may decide to transition the WTRU 102 to the CONNECTED state. After transitioning to the CONNECTED state, the WTRU 102 may send a second (e.g., explicit or long) resource availability report. For example, the network may include an indication of the required detailed report in an RRC resume or RRC setup message. As another example, the network may send an RRC reconfiguration message (e.g., UE assistance information) to the WTRU 102 with such an indication.

[0209] In certain representative embodiments, the WTRU 102 may receive information (e.g., an indication) as to whether the WTRU 102 may perform a resource availability report in a low power state (e.g., IDLE and / or INACTIVE) or the WTRU 102 must transition to the CONNECTED state. For example, this information may be received in a resource availability report configuration, such as according to any of the examples described herein. In another example, this information may be received in the activation of a resource availability report, such as according to any of the examples described herein.

[0210] In certain representative embodiments, the WTRU 102 may be configured with one or more buffer level thresholds that determine the procedure for sending a resource availability report. For example, the WTRU 102 may be configured to use SDT-based reporting (e.g., only) if the size of the resource availability report is below a threshold. For example, it may be configured to transition to the CONNECTED state and send a resource availability report in the CONNECTED state (e.g., using an RRC message such as UE assistance information) (e.g., only) if the size of the report is above the threshold.

[0211] One-time and immediate reporting

[0212] In certain representative embodiments, it may be assumed that the WTRU 102 uses a previously received configuration to send a resource availability report, such as periodically or when certain conditions are met (e.g., sufficient resources become available, etc.).

[0213] In certain representative embodiments, the WTRU 102 in the CONNECTED state may receive an explicit (e.g., one-time) request from the network to send an AI / ML resource availability report (e.g., an NAS message, an existing RRC message such as a UE information request, a new RRC message defined for requesting a report, a MAC CE, DCI, etc.). For example, the request may include details such as the relevant AI / ML RAN function(s) or model(s).

[0214] In certain representative embodiments, a WTRU 102 in a low power state (e.g., IDLE or INACTIVE state) may receive paging information from the network (e.g., a CN paging indication for when the WTRU 102 is in IDLE, or a RAN paging indication for when the WTRU 102 is in INACTIVE) to send an AI / ML resource availability report. For example, the paging information may be associated with a specific WTRU identity or group identity associated (e.g., pre-configured) with the WTRU. For example, the paging information may include implicit (e.g., based on a paging identity) or explicit (e.g., additional information in the paging message) information about the relevant AI / ML function(s) or model(s) that the WTRU should report. For example, the WTRU 102 may respond to the paging (e.g., using an RRC resume request or RRC setup request message), such as (e.g., only) if the WTRU 102 has available resources (e.g., for the indicated AI / ML function / model).

[0215] In certain representative embodiments, a WTRU 102 in any of the IDLE, INACTIVE, and / or CONNECTED states may receive a broadcast signal (e.g., any system information block) that indicates for the WTRU 102 to send a one-time AI / ML resource availability report (e.g., an indication). The broadcast signal may include information about the relevant AI / ML function(s) or model(s) that the WTRU 102 should report. For example, the WTRU 102 may respond to the indication (e.g., only) if resources are available (e.g., for the indicated AI / ML function / model). The WTRU 102 may use any of the processes described herein (e.g., SDT, two-step resume, RACH preamble, reporting via an RRC message when in the CONNECTED state or after transitioning to the CONNECTED state, etc.) to send the resource availability report, which may be used to send the one-time report.

[0216] In certain representative embodiments, the WTRU 102 may receive additional information (e.g., an indication) in a one-time request about whether to perform the resource availability report in the RRC_CONNECTED state or in a low power state (e.g., IDLE and / or INACTIVE).

[0217] Figure 13 is a process diagram showing an example process for reporting resource availability for a service. The WTRU 102 may be configured to perform (e.g., implemented as a method) Figure 13The process shown. At 1302, when operating in a first operating mode, the WTRU 102 may receive configuration information associated with a report of the availability of resources for a service (e.g., at the WTRU 102). For example, the configuration information may include information indicating one or more conditions for the WTRU to trigger a report of resource availability (e.g., the available resources required for the service at the WTRU 102). For example, the configuration information may include information indicating the content (e.g., one or more types) to be provided by the WTRU when reporting resource availability. At 1304, the WTRU 102 may transition to a second operating mode. At 1306, when operating in the second operating mode, the WTRU 102 may monitor one or more conditions of the WTRU 102 to trigger a resource availability report. At 1308, the WTRU 102 may send (e.g., report) information indicating the availability of resources for the service based on meeting one or more conditions.

[0218] For example, the service may be associated with federated learning using one or more AI / ML models and / or functions. As an example, the AI and / or ML models and / or functions (e.g., at the WTRU 102) may be associated with the service.

[0219] For example, the availability of resources for the service may indicate the availability of federated learning resources at the WTRU 102.

[0220] For example, at 1308, any of the techniques described herein may be used to send a resource availability indication. As an example, the information indicating the availability of resources for the service (e.g., the indication) may include the use of (e.g., pre-configured) RACH resources. As an example, the information indicating resource availability (e.g., the indication) may include the use of a (e.g., configured) recovery identity, such as an I-RNTI. As an example, the Msg3 UL payload (such as at 1010) may include information indicating resource availability (e.g., the indication). As an example, the MsgAUL payload (such as at 1106) may include information indicating resource availability (e.g., the indication). As an example, CG-based transmission may include information indicating resource availability (e.g., an indication as part of the UL payload at 1212).

[0221] In some representative embodiments, the WTRU 102 may (e.g., further) receive configuration information that includes information indicating a set of resources required (e.g., available) for services at the WTRU 102. For example, the set of resources may include (i) the required battery power level of the WTRU 102, (ii) the required amount of memory of the WTRU 102, (iii) the required processor capacity of the WTRU 102, and / or (iv) any one of one or more AI and / or ML models and / or functions required at the WTRU 102.

[0222] In some representative embodiments, one or more conditions may include any of the following: (i) a set of resources required for services at the WTRU 102, (ii) the periodicity of the resource availability report (e.g., reporting timing), (iii) one or more AI and / or ML models and / or functions that need to be available at the WTRU 102, and / or (iv) an explicit request to receive the resource availability for sending services.

[0223] In some representative embodiments, the first operating mode may be a full-power operating mode.

[0224] In some representative embodiments, the second operating mode may be a reduced-power operating mode.

[0225] In some representative embodiments, the WTRU 102 may (e.g., further) receive an RRC message associated with transitioning to the second operating mode.

[0226] In some representative embodiments, the information indicating resource availability (such as at 1308) may include (e.g., be sent as) any one of a random access channel preamble, a WTRU identifier, or an explicit indication.

[0227] In some representative embodiments, any one of non-access stratum (NAS) signaling, radio resource control (RRC) signaling, media access control (MAC) control element (CE), or uplink control information (UCI) may be used to send the information indicating resource availability, such as at 1308.

[0228] In some representative embodiments, when operating in the second operating mode, the information indicating resource availability may be sent, such as at 1308.

[0229] In some representative embodiments, the WTRU 102 may (e.g., further) transition to a first operating mode; and when operating in the first operating mode, send (e.g., after 1308) additional information indicating resource availability. For example, at 1308, the WTRU 102 may indicate (e.g., to the network) that a set of required resources is available at the WTRU 102. This additional information may indicate (e.g., to a greater extent) which resources (e.g., battery power level, free memory, and / or processing capacity) are available at the WTRU 102 in addition to the set of required resources. As an example, a battery level of at least X1% and / or an amount of free memory of Y1 megabytes may be required at the WTRU 102, and the additional information may indicate that a battery level of X2% and / or an amount of free memory of Y2 megabytes is available at the WTRU 102 (e.g., where X2 > X1 and Y2 > Y1). This may be beneficial in allowing the network to (e.g., only) select certain WTRUs that have relatively more available resources in addition to the set of required resources.

[0230] Figure 14 is a process diagram illustrating an example process of using paging information to report service resource availability. The WTRU 102 may be configured to perform (e.g., implemented as a method) Figure 14 the process shown. At 1402, when operating in the first operating mode, the WTRU 102 may receive an RRC message associated with transitioning to a second operating mode. At 1404, the WTRU 102 may transition to the second operating mode. At 1406, when operating in the second operating mode, the WTRU 102 may receive paging information associated with the WTRU 102. At 1408, the WTRU 102 may monitor one or more conditions of the WTRU 102 based on the paging information to trigger reporting of service resource availability. At 1410, the WTRU 102 may send (e.g., report) information indicating service resource availability based on meeting one or more conditions.

[0231] For example, the service may be associated with federated learning using one or more AI / ML models and / or functions. As an example, AI and / or ML models and / or functions (e.g., at the WTRU 102) may be associated with the service.

[0232] For example, the resource availability of the service may indicate the federated learning resource availability at the WTRU 102.

[0233] For example, at 1410, any of the techniques described herein can be used to send a resource availability indication. As an example, the information indicating resource availability (e.g., the indication) can include the use of (e.g., pre-configured) RACH resources. As an example, the information indicating resource availability (e.g., the indication) can include the use of (e.g., configured) recovery identities, such as I-RNTI. As an example, the Msg3 UL payload (such as, at 1010) can include the information indicating resource availability (e.g., the indication). As an example, the MsgA UL payload (such as, at 1106) can include the information indicating resource availability (e.g., the indication). As an example, CG-based transmission can include the information indicating the availability of federated learning resources (e.g., an indication as part of the UL payload at 1212).

[0234] In certain representative embodiments, when operating in a first operating mode, the WTRU 102 can (e.g., further) receive configuration information associated with a report of the availability of resources for the service. For example, the configuration information can include information indicating one or more conditions for the WTRU 102 to trigger a report of resource availability.

[0235] In certain representative embodiments, the WTRU 102 can (e.g., further) receive a signal indicating activation of the configuration information. For example, the signal can include any one of paging information, an RRC message, a MAC CE, and / or DCI.

[0236] In certain representative embodiments, the paging information can be associated with a report of resource availability. For example, the paging information can include information indicating one or more conditions for the WTRU 102 to trigger a report of resource availability.

[0237] In certain representative embodiments, the WTRU 102 can (e.g., further) receive configuration information indicating a set of resources required (e.g., available) for the service at the WTRU 102. For example, the set of resources can include any one of the following: (i) the required battery level of the WTRU 102, (ii) the required memory amount of the WTRU 102, (iii) the required processor capacity of the WTRU 102, and / or (iv) one or more AI and / or ML models and / or functions required at the WTRU 102.

[0238] In certain representative embodiments, one or more conditions include any one of the following: (i) a set of resources required for the service at the WTRU 102, (ii) the periodicity of the resource availability report, (iii) one or more AI and / or ML models and / or functions that need to be available at the WTRU 102; and / or (iv) receiving an explicit request to send the availability of resources for the service.

[0239] In certain representative embodiments, the first operating mode may be a full power operating mode.

[0240] In certain representative embodiments, the second operating mode may be a reduced power operating mode.

[0241] In certain representative embodiments, the information indicating resource availability (such as at 1410) may include any one of a random access channel preamble, a WTRU identifier, or an explicit indication.

[0242] In certain representative embodiments, any one of NAS signaling, RRC signaling, MAC CE, and / or UCI may be used to send the information indicating resource availability, such as at 1410.

[0243] In certain representative embodiments, when operating in the second operating mode, the information indicating resource availability (e.g., at 1410) may be sent.

[0244] In certain representative embodiments, the WTRU 102 may (e.g., further) transition to the first operating mode (e.g., after 1410). When operating in the first operating mode, the WTRU 102 may send additional information indicating resource availability. For example, at 1410, the WTRU 102 may indicate (e.g., to the network) that the required set of resources is available at the WTRU 102. This additional information may indicate (e.g., to a greater extent) which resources (e.g., battery power level, free memory, and / or processing capacity) are available at the WTRU 102 in addition to the required set of resources. As an example, at least X1% of the processing capacity and / or Y1 megabytes of free memory may be required at the WTRU 102, and the additional information may indicate that X2% of the processing capacity and / or Y2 megabytes of free memory are available at the WTRU 102 (e.g., where X2 > X1 and Y2 > Y1). This may be beneficial in allowing the network (e.g., only) to select certain WTRUs that have relatively more available resources outside of the required set of resources.

[0245] In certain representative embodiments, paging information such as at 1406 may indicate a group associated with the WTRU.

[0246] Figure 15 is a process diagram showing another example process for reporting resource availability (e.g., for a service). The WTRU 102 may be configured to perform (e.g., implemented as a method) Figure 15The process shown. At 1502, the WTRU 102 may receive configuration information associated with a report of resource availability. For example, the configuration information may include information indicating one or more conditions for the WTRU 102 to trigger a report of resource availability. At 1504, the WTRU 102 may monitor one or more conditions of the WTRU 102 to trigger a report of resource availability. At 1506, the WTRU 102 may send (e.g., report) information indicating resource availability based on meeting one or more conditions.

[0247] For example, a service may be associated with federated learning using one or more AI / ML models and / or functions. As an example, AI and / or ML models and / or functions (e.g., at the WTRU 102) may be associated with a service.

[0248] For example, the resource availability of a service may indicate the federated learning resource availability at the WTRU 102.

[0249] For example, at 1506, any of the techniques described herein may be used to send a resource availability indication. As an example, the information indicating resource availability (e.g., indication) may include the use of (e.g., preconfigured) RACH resources. As an example, the information indicating resource availability (e.g., indication) may include the use of (e.g., configured) recovery identities, such as I-RNTI. As an example, the Msg3 UL payload (such as, at 1010) may include information indicating resource availability (e.g., indication). As an example, the MsgA UL payload (such as, at 1106) may include information indicating resource availability (e.g., indication). For example, CG-based transmission may include information indicating resource availability (e.g., indication as part of the UL payload at 1212).

[0250] In certain representative embodiments, the WTRU 102 may be configured to perform a process (e.g., implemented as a method) that includes receiving (e.g., from a network entity) first information indicating a resource availability report configuration associated with training one or more AI and / or ML functions and / or models. The WTRU 102 may send (e.g., to the network entity) second information indicating that one or more resources are available for (e.g., at the WTRU) training one or more AI and / or ML functions and / or models based on (e.g., in accordance with) the received first information.

[0251] For example, the first information may be received in any one of broadcast signaling, dedicated signaling, RRC messages (e.g., associated with a transition from a first state to a second state), MAC CE, DCI, and / or paging information.

[0252] In certain representative embodiments, the WTRU 102 may transmit a (SDT) that includes second information.

[0253] In certain representative embodiments, the WTRU 102 may perform a two-step RACH procedure that includes transmitting a first message that includes a UL payload. The UL payload may include second information.

[0254] For example, the two-step RACH procedure may include receiving a second message that includes information indicating the I-RNTI of the WTRU 102.

[0255] In certain representative embodiments, the WTRU 102 may perform a four-step RACH procedure that includes transmitting a first message, receiving a second message, and transmitting a third message that includes a UL payload. The UL payload may include second information.

[0256] For example, the four-step RACH procedure may include receiving a fourth message that includes information indicating the I-RNTI of the WTRU 102.

[0257] In certain representative embodiments, the WTRU 102 may receive information indicating the CG configuration and the I-RNTI of the WTRU 102. The WTRU 102 may use the CG configuration to transmit a UL payload. The UL payload may include second information.

[0258] For example, after transmitting a UL payload using the CG configuration, the WTRU 102 may receive information indicating the I-RNTI of the WTRU 102.

[0259] In certain representative embodiments, the second information may be or include a RACH preamble.

[0260] In certain representative embodiments, the second information may be or include one or more bitmaps that indicate corresponding combinations of one or more resources available for training AI and / or ML models and / or functions.

[0261] In certain representative embodiments, the WTRU 102 may receive information indicating one or more AI / ML models and / or functions. After reporting the second information, the WTRU 102 may perform training of one or more AI / ML models and / or functions. The WTRU 102 may transmit information associated with the results of the training of one or more AI / ML models and / or functions.

[0262] In certain representative embodiments, the WTRU 102 may send (e.g., to a network entity) third information based on (e.g., according to) the received first information, where the third information indicates that one or more resources are available for training one or more AI and / or ML functions and / or models. The third information may be associated with a higher reporting level (e.g., more detailed) than the second information.

[0263] Conclusion

[0264] Although the features and elements are provided above in particular combinations, those of ordinary skill in the art will appreciate that each feature or element can be used separately or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this application, which are intended to be illustrative of various aspects. Many modifications and variations can be made without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. Any element, act, or instruction used in the description of this application should not be construed as critical or essential to the invention unless expressly so provided. From the foregoing description, functional equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art in addition to the methods and apparatuses enumerated herein. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the full scope of equivalents to such claims. It will be understood that the present disclosure is not limited to a particular method or system.

[0265] For simplicity, the foregoing embodiments are discussed in terms of the terminology and structure of a device having wireless communication capabilities (i.e., a radio wave transmitter and receiver). However, the embodiments discussed are not limited to these systems, but can be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

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

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

[0268] Variations of the methods, apparatuses, and systems provided above are possible without departing from the scope of the present invention. Given the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered as limiting the scope of the appended claims. For example, the embodiments provided herein include a handheld device that can include or be used in conjunction with any suitable voltage source such as a battery that provides any suitable voltage.

[0269] In addition, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include a processor are indicated. These devices can include at least one central processing unit (“CPU”) and memory. In accordance with the practice of those skilled in the art of computer programming, references to acts and symbolic representations of operations or instructions can be performed by the various CPUs and memories. Such acts and operations or instructions can be referred to as “executed,” “computer-executed,” or “CPU-executed.”

[0270] Those of ordinary skill in the art will appreciate that the operations or instructions of the acts and symbolic representations include manipulation of electrical signals by a CPU. The electrical system represents data bits, which may cause a final conversion or reduction of the electrical signals and maintain the data bits at a memory location in the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and other processing of the signals. The memory location maintaining the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs mentioned above, and other platforms and CPUs may support the provided methods.

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

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

[0273] There is little difference between the hardware and software implementations of the various aspects of the system. The use of hardware or software is generally (but not always, and in some situations, the choice between hardware and software may become important) a design choice representing a cost-versus-efficiency tradeoff. There may be various means by which the processes and / or systems and / or other technologies described herein (e.g., hardware, software, and / or firmware) may be implemented, and the preferred means may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are of utmost importance, the implementer may choose means that are primarily hardware and / or firmware. If flexibility is of utmost importance, the implementer may choose means that are primarily software implementations. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0274] The foregoing detailed description has set forth various embodiments of devices and / or processes via the use of block diagrams, flowcharts, and / or examples. As within such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or jointly by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented, in whole or in part, in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or virtually any combination thereof, and designing the circuitry and / or writing code for the software and / or firmware would be well within the skill of those in the art in light of this disclosure. Additionally, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a variety of program products, and the illustrative embodiments of the subject matter described herein apply regardless of the particular type of signal bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, etc., and transmission type media such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0275] Those skilled in the art will recognize that within the art, it is common to describe devices and / or processes in the manner set forth herein and then use engineering practice to integrate the devices and / or processes so described into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally can include one or more system unit enclosures, a video display device, memories such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computing entities such as operating systems, drivers, graphical user interfaces, and application programs, one or more interaction devices such as touchpads or screens, and / or a control system including feedback loops and control motors (e.g., for listening for feedback of position and / or speed, control motors for moving and / or adjusting components and / or amounts). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0276] The subject matter described herein sometimes illustrates different components included within or connected to different other components. It will be understood that such depicted architectures are merely examples, and in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components that achieves the same functionality is effectively "associated" such that the desired functionality can be achieved. Thus, any two components that are combined herein to achieve a particular functionality can be regarded as being "associated" with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be regarded as being "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be regarded as being "operably coupled" to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, components that physically mate and / or physically interact and / or wirelessly interact and / or wirelessly communicate and / or logically interact and / or are logically communicable.

[0277] Regarding the use of substantially any plural and / or singular terms herein, those skilled in the art can appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be set forth herein explicitly.

[0278] Those skilled in the art will understand that, in general, the terms used herein and especially in the appended claims (e.g., the body of the appended claims) are generally intended to be "open" terms (e.g., the term "comprising" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "including" should be interpreted as "including but not limited to", etc.). Those skilled in the art will further understand that if an intention to introduce a specific number of claim recitations is present, such an intention will be expressly recited in the claims, and if no such recitation is present, there is no such intention. For example, in cases where only one item is intended, the term "single" or similar language may be used. To assist understanding, the appended claims and / or the description herein below may include the use of introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that a claim recitation introduced by the indefinite article "a" or "an" limits any particular claim that includes such introduced claim recitation to only one embodiment including such recitation, even when the same claim includes the introductory phrase "one or more" or "at least one" as well as an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). This also applies to the use of definite articles used to introduce claim recitations. Further, even if the specific number of introduced claim recitations is expressly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., a simple recitation of "two recitations" without any other modifiers means at least two recitations, or two or more recitations). Additionally, in cases similar to those using conventions such as "at least one of A, B, and C, etc.", generally, such a construction is intended in the following sense: to enable those skilled in the art to understand the convention (e.g., "a system having at least one of A, B, and C" will include but not be limited to systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In cases similar to those using conventions such as "at least one of A, B, or C, etc.", generally, such a construction is intended in the following sense: to enable those skilled in the art to understand the convention (e.g., "a system having at least one of A, B, or C" will include but not be limited to systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Those skilled in the art will further understand that any disjunctive word and / or phrase that actually represents two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibilities of including one term, the other term, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B".Furthermore, as used herein, the term "any" followed by a listing of multiple items and / or multiple categories of items is intended to include "any one," "any combination," "any multiple," and / or "any combination of multiples" of the items and / or categories of items, either alone or in combination with other items and / or other categories of items. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "plurality," as used herein, is intended to be synonymous with "multiple."

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

[0280] As will be understood by those skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also include any and all possible sub-ranges and combinations of sub-ranges thereof.Any listed range can be easily considered to fully describe and enable the same range to be decomposed into at least equal half, one-third, one-quarter, one-fifth, one-tenth, etc. As a non-limiting example, each range discussed herein can be easily decomposed into lower third, middle third, and upper third, etc. As will be understood by those skilled in the art, all languages such as "up to", "at least", "greater than", "less than", etc. include the listed numbers, and refer to the ranges that can be subsequently decomposed into sub-ranges as discussed above. Finally, as will be understood by those skilled in the art, ranges include each individual member.Therefore, for example, a group with 1-3 units refers to a group with 1, 2 or 3 units. Similarly, a group with 1-5 units refers to a group with 1, 2, 3, 4 or 5 units, etc.

[0281] Furthermore, the claims should not be read as limited to the order or elements provided unless so stated. Furthermore, the use of the term "means for..." in any claim is intended to refer to 35 U.S.C. §112, or means-plus-function claim format, and any claim without the term "means for..." is not so intended.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: When operating in a first operation mode, receiving configuration information associated with a report of service resource availability, wherein the configuration information includes information indicating one or more conditions for the WTRU to trigger a report of resource availability; Switching to a second operation mode; When operating in the second operation mode, monitoring one or more conditions of the WTRU to trigger a report of the resource availability of the service; And Based on the one or more conditions being met, sending information indicating the resource availability of the service.

2. The method according to claim 1, wherein the service is associated with federated learning using one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions.

3. The method according to any one of claims 1-2, Among them, The configuration information includes information indicating a set of resources required for the service at the WTRU, and wherein the set of resources includes the required battery power level of the WTRU, the required memory amount of the WTRU, the required processor capacity, and / or any one of one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions required by the WTRU.

4. The method according to any one of claims 1-2, wherein, The one or more conditions include any one of the following: (i) the availability of a set of resources required for the service at the WTRU, (ii) the periodicity of the resource availability report, (iii) one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions that need to be available at the WTRU for federated learning, and / or (iv) receiving an explicit request to send the resource availability of the service.

5. The method according to any one of claims 1-4, wherein The first operation mode is a full power operation mode.

6. The method according to any one of claims 1-5, wherein, The second operation mode is a reduced power operation mode.

7. The method according to any one of claims 1-6, further comprising: Receiving a radio resource control (RRC) message associated with switching to the second operation mode.

8. The method according to any one of claims 1-7, wherein, The information indicating the resource availability of the service includes any one of a random access channel preamble, a WTRU identifier, or an explicit indication.

9. The method according to any one of claims 1-8, wherein, Using any one of non-access stratum (NAS) signaling, radio resource control (RRC) signaling, media access control (MAC) control element (CE), or uplink control information (UCI) to send information indicating the resource availability of the service.

10. The method according to any one of claims 1-9, wherein the information indicating the resource availability of the service is sent when operating in the second operation mode.

11. The method according to any one of claims 1-10, further comprising: Switching to the first operation mode; And When operating in the first operation mode, sending additional information indicating the resource availability of the service.

12. A wireless transmit / receive unit (WTRU) comprising: A processor, a memory, and a transceiver, which are configured to: When operating in a first operating mode, receive configuration information associated with a report of resource availability of a service, where the configuration information includes information indicating one or more conditions for triggering a report of resource availability of the service by the WTRU; Transition to a second operating mode; When operating in the second operating mode, monitor one or more conditions of the WTRU to trigger a report of resource availability of the service; And Based on the one or more conditions being met, send information indicating the resource availability of the service.

13. The WTRU according to claim 12, wherein the service is associated with federated learning using one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions.

14. The WTRU according to any one of claims 12-13, Among them, The configuration information includes information indicating a set of resources required for the service at the WTRU, and wherein the set of resources includes any one of a required battery power level of the WTRU, a required memory amount of the WTRU, a required processor capacity of the WTRU, and / or one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions required by the WTRU.

15. The WTRU according to any one of claims 12 - 13, wherein, The one or more conditions include any one of the following: (i) availability of a set of resources required for the service at the WTRU, (ii) periodicity of the resource availability report, (iii) one or more artificial intelligence (AI) and / or machine learning (ML) models and / or functions that need to be available at the WTRU for federated learning, and / or (iv) receipt of an explicit request to send the resource availability of the service.

16. The WTRU according to any one of claims 12 - 15, wherein The first operating mode is a full power operating mode.

17. The WTRU according to any one of claims 12 - 16, wherein, The second operating mode is a reduced power operating mode.

18. The WTRU according to any one of claims 12-17, wherein, The processor, the memory, and the transceiver are further configured to: Receive a radio resource control (RRC) message associated with the transition to the second operating mode.

19. The WTRU according to any one of claims 12 - 18, wherein, The information indicating the resource availability of the service includes any one of a random access channel preamble, a WTRU identifier, or an explicit indication.

20. The WTRU according to any one of claims 12 - 19, wherein Use any one of non-access stratum (NAS) signaling, radio resource control (RRC) signaling, media access control (MAC) control element (CE), or uplink control information (UCI) to send the information indicating the resource availability of the service.

21. The WTRU according to any one of claims 12 - 20, wherein, The information indicating the resource availability of the service is sent when operating in the second operating mode.

22. The WTRU according to any one of claims 12 - 21, wherein, The processor, the memory, and the transceiver are further configured to: Transition to the first operating mode, and When operating in the first operating mode, send additional information indicating the resource availability of the service.

Images