EP4710714A1 - Methods and apparatus for asynchronous federated learning using indirect network connection - Google Patents

Abstract

Methods and apparatuses directed to a network exposure function to assist in performing a selection procedure targeting asynchronous federated learning (FL) eligible devices with indirect communication capabilities are provided. For example, a network device is configured to receive a member selection request including information indicating filtering criteria; determine one or more SMFs serving DNN/S-NSSAI; send, to each respective SMF of the one or more SMFs, a subscription request requesting QoS monitoring information and ProSe type information for a set of ProSe devices managed by the respective SMF; receive, from the respective SMF, a message comprising the QoS monitoring information and the ProSe type information; generate, based on the filtering criteria and the received message, a list of candidate devices for FL; and transmit the list of candidates for FL to the AF.

Description

METHODS AND APPARATUS FOR ASYNCHRONOUS FEDERATED LEARNING USING INDIRECT NETWORK CONNECTION CROSS-REFERENCE TO RELATED APPLICATION(S) [001] This application claims priority to and the benefit of U.S. Provisional Application No. 63/465,722 filed in the U.S. Patent and Trademark Office on May 11, 2023, the entire contents of which being incorporated herein by reference as if fully set forth below in their entirety and for all applicable purposes. SUMMARY [002] This disclosure pertains to procedures, methods, architectures, apparatus, systems, devices, and computer program products for, and/or directed to a network exposure function to assist in performing a WTRU member selection procedure targeting asynchronous federated learning eligible WTRUs with indirect communication capabilities. [003] In one embodiment, a method of assisting in selecting wireless transmit/receive units (WTRUs) as members of a federated learning (FL) group is provided. The method includes receiving, from an application function (AF), a member selection request including information indicating filtering criteria; determining one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); and sending, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF. The method also includes receiving, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generating, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmitting, to the AF, the list of candidate WTRUs for FL. [004] In one embodiment, a network device comprises circuity, including a processor, a transmitter, a receiver, and/or memory is provided. The network device is configured to assist in selecting wireless transmit/receive units (WTRUs) as members of a federated learning (FL) group. The network device is configured to receive, from an application function (AF), a member selection request including information indicating filtering criteria; determine one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); send, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF; receive, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generate, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmit, to the AF, the list of candidate WTRUs for FL. BRIEF DESCRIPTION OF THE DRAWINGS [005] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with the drawings appended hereto. Figures in such drawings, like the detailed description, are exemplary. As such, the Figures and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the Figures ("FIGs.") indicate like elements, and wherein: [006] FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented; [007] FIG.1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [008] FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A, according to an embodiment; [009] FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A, according to an embodiment; [010] FIG.2 is a signal flow diagram illustrating a WTRU Member selection assistance process with exposure of indirect network connection capabilities, in accordance with embodiments; [011] FIG.3 is a signal flow diagram illustrating a U2N Relay communication procedure with application specific (e.g. Async-FL) access/session control, in accordance with embodiments; [012] FIG.4 is a signal flow diagram illustrating a U2N Relay communication procedure with Application specific (e.g. Async-FL) session control, in accordance with embodiments; [013] FIG.5 is a flowchart illustrating a WTRU member selection assistance procedure targeting Async-FL eligible WTRUs with indirect communication capabilities, in accordance with embodiments; and [014] FIG.6 is a flowchart illustrating an indirect network connection with application specific control, in accordance with embodiments. DETAILED DESCRIPTION INTRODUCTION [015] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed, or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. EXAMPLE COMMUNICATION SYSTEMS [016] FIG.1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like. [017] As shown in FIG.1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and/or a “STA”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE. [018] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements. [019] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [020] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT). [021] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA). [022] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro). [023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR). [024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB). [025] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. [026] The base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115. [027] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG.1A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing a NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. [028] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT. [029] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology. [030] FIG.1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non- removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. [031] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG.1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip. [032] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals. [033] Although the transmit/receive element 122 is depicted in FIG.1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116. [034] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. [035] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown). [036] The processor 118 may receive power from the power source 134 and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel- cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like. [037] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment. [038] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor. [039] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)). [040] FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. [041] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. [042] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [043] The CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [044] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA. [045] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like. [046] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. [047] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. [048] Although the WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [049] In representative embodiments, the other network 112 may be a WLAN. [050] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication. [051] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS. [052] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel. [053] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). [054] Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac.802.11af supports 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 Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). [055] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available. [056] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code. [057] FIG.1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115. [058] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c). [059] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time). [060] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c. [061] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface. [062] The CN 115 shown in FIG.1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [063] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF a82a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. [064] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like. [065] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like. [066] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b. [067] In view of Figs.1A-1D, and the corresponding description of Figs.1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. [068] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications. [069] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be a test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. Federated Learning Async-FL Use Case [070] A use case for Asynchronous Federated Learning (Async-FL) using both direct and indirect connection is discussed herein. Compared to Synchronous Federated Learning (Sync-FL), Async FL requires higher computation workload because the WTRU gets a new model (e.g., downlink) from the Parameter Server (e.g., Application Function) after it uploads its training results (uplink) without waiting for other WTRUs’ training results. Also compared to Sync-FL, Async-FL has less stringent timing communication requirements as the WTRU can report its results whenever it is ready. [071] Given the relaxed timing requirement for the WTRUs to communicate their training results, indirect network communication can be used for Async-FL. WTRU member selection assistance [072] WTRU member selection assistance capabilities at a Network Exposure Function (NEF) for an Application Function (AF) for the selection of WTRUs for Artificial Intelligence/Machine Learning (AIML) operations (e.g., based on Quality of Service (QoS), Radio Access Technology (RAT) type, WTRU location) is defined in Rel-18. The NEF retrieves a list of candidate WTRUs that match the AF-provided filtering criteria and by interacting with Network Functions (NFs) within the 5GC (5G Core Network). 5G ProSe U2N Relay discovery and communication [073] U2N (UE (or WTRU)-to-Network) Relay discovery and communication are defined in Rel-17. Relay discovery and connection via PC5 link by a Remote WTRU uses a provisioned Relay Service Code (RSC) associated with Data Network Name/Single- Network Slice Selection Assistance Information (DNN/S-NSSAI). The Relay provides a Packet Data Unit (PDU) Session for the connected Remote WTRU. Security for communication via U2N Relay also is defined, whereby the U2N Relay uses network assistance to authenticate and authorize the Remote WTRU and establish the security for the unicast communication link. WTRU Member selection for the support of Async-FL [074] Current WTRU Member selection assistance functionality does not support filtering criteria based on whether a WTRU is a ProSe capable WTRU i.e., whether it can act as a Remote WTRU or as a U2N Relay. Current Access or RAT type criteria does not provide such granularity. [075] This type of filter is desirable to allow the AF (FL Application Server) to select WTRUs that can participate in Async-FL, including as Remote WTRUs (e.g., while out of coverage) or as a Relay by using indirect network connection. [076] Furthermore, the AF should be able to select optimal sets of Remote WTRUs and U2N Relay WTRU members such as to achieve performant Async-FL (e.g., with efficient/fast model accuracy convergence). U2N Relay communication for the support of Async-FL [077] In current U2N Relay communication procedures when the U2N WTRU encounters a congestion situation (e.g., cause value #13), the Remote WTRU may either back off or initiate a U2N relay re-selection procedure. This raises several issues. [078] First, the Remote WTRU may not find a suitable U2N relay in proximity that can provide connectivity for Async-FL (e.g., with appropriate RSC, QoS). [079] Second, the non-connected Remote WTRUs may hold valuable datasets that may lead to sub-optimal Async FL model performance (e.g., overfitting, longer time to get accurate model) because the Async-FL does not have access to those valuable datasets. [080] Access and usage of U2N Relay connectivity by Remote WTRUs is currently based on a “First come – first served” principle. This may lead to situations where connected Remote WTRUs may hog the Relay resources for their Async-FL traffic (e.g., for an undetermined period of time), thereby preventing other potential Remote WTRUs in proximity from participating in the Async-FL using the Relay. [081] Thus, it would be beneficial to enhance U2N Relay discovery and communication procedures for the support of Async-FL using indirect network connection, while enabling fair access for an application session (e.g., FL) using the Relay service and ensuring diversity of enrolled Remote WTRUs (e.g., for Async-FL). Representative Embodiments [082] Embodiments are described below wherein the 5GC provides exposure for WTRU Member selection with awareness of indirect network communication capabilities. The mechanism allows the 5GC to include WTRUs that would otherwise not be selectable as Remote WTRU (i.e., out of coverage and connected via a Relay's PDU Session) and allows the AF (FL server) to extend the selection to all potential eligible WTRUs that would be capable of participating in the FL session (e.g., Async-FL). The embodiments allow clustering/grouping of WTRUs (Relay+connected Remote WTRU(s)) selection by the AF ad- hoc (without the need for additional grouping information pre-configuration) and independent of the Public Land Mobile Network (PLMN) to which the involved WTRUs belong. [083] Embodiments are described below wherein the Relay enforces application specific (e.g., Async-FL) session access control for Remote WTRUs during connection and communication procedures. The embodiments allow the Relay to provide fair and optimal access for Remote WTRUs participating in a FL session according to the AF requirements. The AF is provided with fine grained control of which Remote WTRUs access a particular session based on factors like Remote WTRU identity, PLMN, location, time, etc. using an AF provisioned session access control policy that is applied on top of the conventional Relay service access authorization. [084] Representative procedure of WTRU Member Selection Assistance with Indirect Network Connection Support [085] FIG.2 is a signal flow diagram illustrating a WTRU Member selection assistance process with exposure of indirect network connection capabilities. [086] In step 1, the NEF 203 receives from an AF 201 a Nnef_UEMemberSelectionAssistance_subscribe request including Application Identity or S- NSSAI/DNN, initial UE list, Area of Interest (AoI), ProSe capable WTRU selection indication (e.g., ProSe Remote WTRU/Relay type), required aggregated QoS for Relay, min- max number of Remote WTRU per Relay, and/or required QoS per Remote WTRU. [087] In step 2, the NEF locates Session Management Functions (SMFs) serving the S- NSSAI/DNN in the Area of Interest (AoI) by querying the Unified Data Management/Network Routing Function (UDM/NRF). [088] In step 3 (3a, 3b), for each target SMF, e.g., SMFs 205 and 207, the NEF sends an Nsmf_EventExposure_Subscribe request (Event: 'QoS monitoring', target WTRUs, Application ID or Flow Description(s), S-NSSAI, DNN, WTRU type indication) to request the specific WTRU type information (i.e., ProSe Remote WTRU/Relay type/Direct) in the SMF QoS report. [089] In step 4 (4a, 4b), the SMF 205, 207 may interact with a User Plane Function (UPF) to request QoS monitoring for certain flows within each identified PDU Session (e.g., using S-NSSAI/DNN). Based on inclusion of the WTRU type indication, for each identified PDU Session, the SMF collects Relay and associated Remote WTRU(s) information from the Session Management (SM) context of the Relay associated with the PDU Session. [090] In step 5 (5a, 5b), the SMF sends an Nsmf_EventExposure_Notify request including an Event Exposure notification with WTRU type information (Remote or Relay or Direct) and, if WTRU type is Relay, a list of connected Remote WTRUs. [091] In step 6, the NEF 203 consolidates the results from the various SMFs to derive the list of candidate WTRUs. Specifically, for Relay type WTRUs, the NEF verifies that the reported QoS fulfills the required aggregated QoS and the Relay serves an acceptable number of Remote WTRUs (e.g., based on the min parameter mentioned above in step 1). For example, if too few Remote WTRU participate in the FL session at the Relay, they may not provide a meaningful dataset to the FL server. For Remote type WTRUs, the NEF verifies that it is connected to an eligible Relay (above) and fits the max number of Remote WTRUs limit per given Relay. If the list includes a number of WTRUs over the max limit, the list may be shortened by picking in priority the "m" Remote WTRUs in the list having the best QoS, where m is the maximum number. [092] In step 7, the NEF 203 sends to the AF 201a Nnef_ UEMemberSelectionAssistance_Notify including the list(s) of candidate WTRU(s) and additional information, such as, for each WTRU, its WTRU type (Relay, Remote) and the WTRUs association/grouping information (Relay and associated connected Remote WTRUs). [093] The NEF 203 may provide further notification to the AF 201 (not shown in FIG.2) when Remote or Relay WTRU QoS changes occur and/or WTRU grouping information changes occur (e.g., Remote WTRU disconnection/new connection). [094] Representative Procedure of Indirect Network Connection with Application Specific Control [095] FIG.3 is a signal flow diagram illustrating a U2N Relay communication procedure with application specific (e.g. Async-FL) access/session control. [096] At step 0, the Relay WTRU 303 is provisioned by the AF 311 (e.g., FL server)/PCF with parameters for Application specific Remote WTRU session access control such as: session max time limit (per Remote WTRU), max number of UL/DL transactions or data volume (e.g., sending parameters to the FL server, receiving model from FL server), traffic inactivity timer, max number of connected Remote WTRUs, a Remote WTRU Session Access Control Policy (USACP). [097] The USACP provides rules for the Relay WTRU 303 to determine whether to allow access to an application session for a particular Remote WTRU 301, for example, based on Remote WTRU User information (e.g., Application layer ID) and/or the PLMN of the Remote WTRU. In another example, an admission rule may be based on measured signal strength/range of the Remote WTRU 301 (e.g., against a threshold). Rules may apply on a per PLMN basis, based on time of day, and/or current Relay location. The USACP may be used to determine a priority level for the PC5 link/Remote WTRU. The session access priority level may be used by the Relay to prioritize one Remote WTRU over another at connection time or when the Relay needs to disconnect a Remote WTRU to allow another Remote WTRU in proximity to reconnect. [098] The Remote WTRU 301 may be configured similarly by the AF with some of these session control parameters (e.g., session time limit, traffic inactivity timer, max number of transactions) via its own serving PLMN (not shown in the figure). [099] In step 1, the Relay WTRU 303 receives a connection request message from a Remote WTRU 301. [0100] In step 2, the Relay WTRU 303 initiates and performs a security procedure with the network 309 and Remote WTRU 301 for the authorization of the Remote WTRU 301 to access the Relay service associated with the RSC. The Relay obtains a security key from the network (e.g., from an Access and Mobility Function (AMF) or a ProSe Key Management Function (PKMF)) used to check whether the Remote WTRU is authorized to use the relay service associated with the RSC and to secure communication with the Remote WTRU 301. [0101] In step 3, the Relay WTRU 303 applies the USACP and checks whether the max number of connected Remote WTRUs is reached to determine whether to allow the Remote WTRU to setup a session using the Relay service. The Relay may assign a priority level to the PC5 link/Remote WTRU based on USACP rules. [0102] In step 4, the Relay WTRU 303 establishes a PDU session with the network 309 (or modifies an existing PDU session) for relaying associated with the RSC. [0103] In step 5, the Relay WTRU 303 starts a session duration timer and traffic inactivity timer if the connection is accepted. [0104] As seen in step 5a, if the connection is accepted, the Relay WTRU 303 sends a response message to the Remote WTRU 301 with acceptance including session control parameters (e.g., session duration timer, max number of transactions). [0105] If, on the other hand, the connection is rejected, as shown in step 5b, the Relay WTRU 303 instead sends to the Remote WTRU 301 a next session slot availability timer (e.g., based on the remaining session time of the connected Remote WTRUs, shortest remaining session time). The Relay WTRU 303 starts the next session slot availability timer associated with the Remote WTRU 301 (e.g., Remote WTRU user info) to keep track of Remote WTRU as pending for next available session slot. [0106] Representative Procedure of Indirect Network Communication with Application a a with Application specific (e.g. Async-FL) session control. This procedure would normally occur after the indirect network connection procedure described above in connection with FIG.3. [0108] As shown at step 0, the Relay WTRU 401 provisioned with Application specific Remote WTRU session access control parameters is connected with one or more Remote WTRUs, e.g., via a unicast link. [0109] In step 1, the Relay WTRU 403 detects that a session limit event has occurred for one or more Remote WTRUs, e.g., any of one of session max time limit timer has expired, traffic inactivity timer has expired, max number of UL/DL transactions has been reached, or data volume limit has been reached. [0110] The Relay WTRU 403 determines whether to maintain or release the link for the Remote WTRU based on any one or more of: the current number of connected Remote WTRUs (e.g., exceeds a maximum threshold); USACP rules (e.g., link may be maintained/released based on assigned session access priority level, e.g., higher priority level links may be maintained while lower priority links may be released); and presence of Remote WTRUs pending for an available session slot. [0111] If the Relay WTRU 403 decides to release the link, then, in step 2, it sends a Link Release request message indicating a session limit cause value (e.g., maximum time, inactivity, transaction volume). The message may include a next session slot availability timer (e.g., based on session max time limit parameter). [0112] As shown in step 3, the Relay WTRU 403 may start the next session slot availability timer associated with the Remote WTRU (e.g., Remote WTRU user info) to ensure the Remote WTRU next reconnection attempt is in accordance with the prescribed next available session slot. [0113] In step 4, the Remote WTRU 401 sends a disconnect response message back to the Relay WTRU 403. [0114] Exemplary Procedures [0115] WTRU Member selection assistance with indirect network connection support [0116] FIG.5 is a flowchart illustrating a procedure for WTRU member selection assistance with indirect network connection support as seen from the perspective of the NEF. [0117] In step 501, the NEF receives from an AF a WTRU Member selection request including filtering. The filtering may include any of the following filtering criteria: App Id or S-NSSAI/DNN, initial WTRU list, Area of Interest (AoI), ProSe capable WTRU selection indication (e.g., ProSe Remote WTRU/Relay type or Direct), required aggregated QoS for Relay, min-max number of Remote WTRU per Relay and/or required QoS per Remote WTRU. [0118] In step 503, the NEF locates SMFs serving the S-NSSAI/DNN in the AoI by querying UDM/NRF. [0119] In step 505, the NEF subscribes to each SMF requesting QoS monitoring information along with ProSe WTRU type indication (i.e., ProSe Remote WTRU/U2N Relay type). [0120] In step 507, the NEF receives from each SMF a notification message including WTRU information, such as ProSe WTRU type (Remote or Relay), list of connected Remote WTRUs for a Relay. [0121] In step 509, the NEF consolidates results from the various SMFs to derive the list of candidate WTRUs. For instance, for Relay type WTRUs, the NEF may determine if the WTRU has a QoS fulfilling the aggregated QoS and/or a sufficient number of connected Remote WTRUs (e.g., above a minimum). For Remote type WTRUs, the NEF may determine if the WTRU is connected to an eligible Relay WTRU (above) and/or is within the max number of Remote limit per given Relay WTRU. [0122] In step 511, the NEF sends to the AF the list of candidate WTRUs including additional information such as each WTRU type (Relay, Remote) and WTRU association/grouping (Relay and associated connected Remote WTRUs). [0123] In step 513, the NEF may provide further notification(s) to the AF when Remote or Relay QoS or WTRU grouping information changes occur (e.g., Remote WTRU disconnection/new connection). [0124] In one embodiment, a method of assisting in selecting WTRUs as members of a federated learning (FL) group is provided. The method includes receiving, from an application function (AF), a member selection request including information indicating filtering criteria; determining one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); and sending, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF. The method also includes receiving, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generating, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmitting, to the AF, the list of candidate WTRUs for FL. [0125] In one embodiment, a network device comprises circuity, including a processor, a transmitter, a receiver, and/or memory is provided. The network device is configured to assist in selecting wireless transmit/receive units (WTRUs) as members of a federated learning (FL) group. The network device is configured to receive, from an application function (AF), a member selection request including information indicating filtering criteria; determine one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); send, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF; receive, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generate, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmit, to the AF, the list of candidate WTRUs for FL. [0126] In an example, the message comprises information indicating a list of remote WTRUs connected to a WTRU managed by the respective SMF having a relay ProSe WTRU type. [0127] In an example, the filtering criteria comprises any of: an application identifier (ID), a DNN/S-NSSAI, an initial WTRU list, an area of interest (AoI), a ProSe capable WTRU selection indication, a required aggregated QoS for a Relay WTRU, a minimum number of remote WTRUs per Relay WTRU, a maximum number of Remote WTRUs for a Relay WTRU, or a required QoS per Remote WTRU. [0128] In an example, the FL group is an asynchronous FL group. [0129] In an example, the list of candidate WTRUs for FL transmitted to the AF further includes at least one of: the type of each candidate WTRU, or WTRU grouping information. [0130] In an example, the type of each candidate WTRU indicates whether the candidate WTRU is a Relay WTRU or a Remote WTRU. [0131] In an example, the WTRU grouping information comprises an indication of each Relay WTRU and its connected Remote WTRUs. [0132] In an example, one or more methods discussed herein are performed by a network exposure function (NEF). [0133] In an example, the network device is further configured to determine a change in QoS corresponding to a WTRU in the list or a change in the WTRU grouping information; and transmit, to the AF, information associated with the change. [0134] In an example, the network device comprises a network exposure function (NEF). [0135] Indirect Network Communication with application specific control [0136] FIG.6 is a flowchart illustrating indirect network connection with application specific control from the perspective of a Relay WTRU. [0137] In step 601, the Relay WTRU is provisioned by the AF (e.g., FL server)/PCF with Application specific Remote WTRU session access control parameters, such as: session max time limit (per Remote WTRU), max number of UL/DL transactions or data volume (e.g., sending params, receiving model), traffic inactivity timer, max number of connected Remote WTRU, a Remote WTRU Session Access Control Policy (USACP) (e.g., rules based on User Info/PLMN of Remote WTRU, signal strength/range, current location). [0138] In step 603, the Relay WTRU receives a connection request message from a Remote WTRU. [0139] In response, in step 605, the Relay WTRU applies the USACP (e.g., determine a priority level for the PC5 link/Remote WTRU) for the Remote WTRU and checks whether the maximum number of connected Remote WTRU has been reached to determine whether the Remote WTRU is allowed to establish a session using the relay service. The Relay may assign a relative priority level to the PC5 link/Remote WTRU based on USACP rules. [0140] If the connection is accepted, flow instead proceeds to step 609, in which the Relay WTRU starts a session duration timer and traffic inactivity timer. [0141] Furthermore, if the connection is accepted, in step 611, the Relay WTRU establishes (or modifies an existing) PDU session for relaying and sends a response message with acceptance including session control parameters (e.g., session duration timer, max number of transactions) to the Remote WTRU. [0142] If, on the other hand, the Relay WTRU determines that connection is not allowed, then, flow instead proceeds from step 605 to step 607 in which the Relay WTRU optionally may stop broadcasting the RSC if the max number is reached to prevent further connection and resume broadcasting the RSC when one or more Remote WTRUs disconnects at a later time. [0143] Furthermore, if the connection was rejected in step 605, then, in step 613, the Relay WTRU sends the Remote WTRU a response message including next session slot availability timer (e.g., based on the remaining session time of the connected Remote WTRUs, shortest remaining session time). The Relay may keep track of the Remote WTRU as pending for next available session slot. [0144] In one embodiment, a method, implemented in a WTRU acting as a Relay WTRU in a network for at least one Remote WTRU, for enforcing application specific session access control for Remote WTRUs, the method includes receiving from a network provisioning information including application specific Remote WTRU session access control parameters including a Remote WTRU Session Access Control Policy (USACP); receiving a connection request from a Remote WTRU; and determining whether to accept the request based on the USACP. If the WTRU determines to accept the request, the method may include starting a session duration timer and starting traffic inactivity timer. If the WTRU determines to accept the request based on the USACP, the method may include transmitting to the Remote WTRU a response to the connection request including at least one of the session control parameters. CONCLUSION [0145] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems. [0146] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves. [0147] It is also to 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 “imagery” may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms “user equipment” and its abbreviation “UE”, the term “remote” and/or the terms “head mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired- capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs.1A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience. [0148] In addition, the methods provided herein may 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 over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto- optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, MME, EPC, AMF, or any host computer. [0149] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage. [0150] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit (“CPU”) and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being “executed”, “computer executed” or “CPU executed”. [0151] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU’s operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods. [0152] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods. [0153] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device. [0154] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. [0155] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may 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, in whole or in part, may be equivalently implemented 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 as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.). [0156] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non- volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems. [0157] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components. [0158] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity. [0159] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.) and/or “permissive” terms (e.g., the term “is” and/or the term “are” may be interpreted as “may” and/or “might”, the terms ”"refer(s)" may be interpreted as "may refer" and/or "might refer", the terms "receive(s)" may be interpreted as "may receive" and/or "might receive", the terms "support(s)" may be interpreted as "may support" and/or "might support", the terms "interface(s)" may be interpreted as "may interface" and/or "might interface", the terms "transmit(s)" may be interpreted as "may interface" and/or "might interface", "may transmit" and/or "might transmit", the terms "send(s)" may be interpreted as "may send" and/or "might send", the terms "does not refer" (and/or the like) may be interpreted as "may not refer" and/or "might not refer", the terms "does not receive" (and/or the like) may be interpreted as "may not receive" and/or "might not receive", the terms "does not support" (and/or the like) may be interpreted as "may not support" and/or "might not support", the terms "does not interface" (and/or the like) may be interpreted as "may not interface" and/or "might not interface", the terms "does not transmit" (and/or the like) may be interpreted as "may not transmit" and/or "might not transmit", the terms "does not send" (and/or the like) may be interpreted as "may not send" and/or "might not send", etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have 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 those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have 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.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, 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." Further, the terms "any of" followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of" the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, 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 "multiple", as used herein, is intended to be synonymous with "a plurality". [0160] 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. [0161] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth. [0162] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, ¶ 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended. [0163] Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs); Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine. [0164] The WTRU may be used in conjunction with modules, implemented in hardware and/or software including a Software Defined Radio (SDR), and other components such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a Near Field Communication (NFC) Module, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any Wireless Local Area Network (WLAN) or Ultra Wide Band (UWB) module. [0165] Although the various embodiments have been described in terms of communication systems, it is contemplated that the systems may be implemented in software on microprocessors/general purpose computers (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software that controls a general-purpose computer. [0166] In addition, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications may be made in the details within the scope and range of equivalents of the claims and without departing from the invention.

Claims

CLAIMS What is claimed is: 1. A method of assisting in selecting wireless transmit/receive units (WTRUs) as members of a federated learning (FL) group, the method comprising: receiving, from an application function (AF), a member selection request including information indicating filtering criteria; determining one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); sending, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF; receiving, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generating, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmitting, to the AF, the list of candidate WTRUs for FL.

2. The method of claim 1, wherein the message comprises information indicating a list of remote WTRUs connected to a WTRU managed by the respective SMF having a relay ProSe WTRU type.

3. The method of any one of claims 1-2, wherein the filtering criteria comprises any of: an application identifier (ID), a DNN/S-NSSAI, an initial WTRU list, an area of interest (AoI), a ProSe capable WTRU selection indication, a required aggregated QoS for a Relay WTRU, a minimum number of remote WTRUs per Relay WTRU, a maximum number of Remote WTRUs for a Relay WTRU, or a required QoS per Remote WTRU.

4. The method of any one of claims 1-3, wherein the FL group is an asynchronous FL group.

5. The method of any one of claims 1-4, wherein the list of candidate WTRUs for FL transmitted to the AF further includes at least one of: the type of each candidate WTRU, or WTRU grouping information.

6. The method of claim 5, wherein the type of each candidate WTRU indicates whether the candidate WTRU is a Relay WTRU or a Remote WTRU.

7. The method of claim 5, wherein the WTRU grouping information comprises an indication of each Relay WTRU and its connected Remote WTRUs.

8. The method of claim 5, further comprising: determining a change in QoS corresponding to a WTRU in the list or a change in the WTRU grouping information; and transmitting, to the AF, information associated with the change.

9. The method of any one of claims 1-8, wherein the method is performed by a network exposure function (NEF).

10. A network device for assisting in selecting wireless transmit/receive units (WTRUs) as members of a federated learning (FL) group, comprising one or more of a processor, a transmitter, a receiver, and memory, the network device configured to: receive, from an application function (AF), a member selection request including information indicating filtering criteria; determine one or more session management functions (SMFs) serving data network name/single- network slice selection assistance Information (DNN/S-NSSAI); send, to each respective SMF of the one or more SMFs, a subscription request requesting 1) Quality of Service (QoS) monitoring information and 2) ProSe WTRU type information for a set of ProSe WTRU managed by the respective SMF; receive, from the respective SMF, a message comprising the QoS monitoring information and the ProSe WTRU type information; generate, based on the filtering criteria and the received message, a list of candidate WTRUs for FL; and transmit, to the AF, the list of candidate WTRUs for FL.

11. The network device of claim 10, wherein the message comprises information indicating a list of remote WTRUs connected to a WTRU managed by the respective SMF having a relay ProSe WTRU type.

12. The network device of any one of claims 10-11, wherein the filtering criteria comprises any of: an application identifier (ID), a DNN/S-NSSAI, an initial WTRU list, an area of interest (AoI), a ProSe capable WTRU selection indication, a required aggregated QoS for a Relay WTRU, a minimum number of remote WTRUs per Relay WTRU, a maximum number of Remote WTRUs for a Relay WTRU, or a required QoS per Remote WTRU.

13. The network device of any one of claims 10-12, wherein the FL group is an asynchronous FL group.

14. The network device of any one of claims 10-13, wherein the list of candidate WTRUs for FL transmitted to the AF further includes at least one of: the type of each candidate WTRU, or WTRU grouping information.

15. The network device of claim 14, wherein the type of each candidate WTRU indicates whether the candidate WTRU is a Relay WTRU or a Remote WTRU.

16. The network device of claim 14, wherein the WTRU grouping information comprises an indication of each Relay WTRU and its connected Remote WTRUs.

17. The network device of any one of claims 10-16, wherein the network device is further configured to: determine a change in QoS corresponding to a WTRU in the list or a change in the WTRU grouping information; and transmit, to the AF, information associated with the change.

18. The network device of any one of claims 10-17, wherein the network device comprises a network exposure function (NEF).