Pdu session establishment enabling cascaded relay networks

Abstract

Systems, methods, devices, and instrumentalities are described herein that are related to enabling cascaded relay networks during FDD U session establishment. A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor configured to perform one or more actions. The device may send a session request message to a network node. The session request message may indicate a request for a session, a request for a service, information associated with an application, and / or a federated learning (FL) capability of the WTRU. The FL capability may be associated with the service. The service may be associated with the application. The device may receive an authorization message from the network node. The authorization message may indicate that the requested service is authorized based on the FL capability and the application information. The device may receive a session establishment message from the network.

Description

PDU SESSION ESTABLISHMENT ENABLING CASCADED RELAY NETWORKS CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 528,490, filed July 24, 2023, the contents of which are hereby incorporated by reference herein. BACKGROUND

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

[0003] Systems, methods, devices, and instrumentalities related to enabling cascaded relay networks during PDU session establishment are described herein.

[0004] A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor configured to perform one or more actions. The device may send a protocol data unit (PDU) session request. The PDU session request may indicate a vertical federated learning (VFL) capability of the device and may indicate a requested service that is associated with the VFL capability. The device may receive an authorization message. The authorization message may indicate that the requested service may be authorized.

[0005] The device may detect a trigger associated with an application. The PDU session request may be sent in response to the trigger. The trigger may be one or more of the application starting, a first WTRU joining the application, or a change in configuration to the application (e.g., a second WTRU joining the application). The application may be one or more of a federated learning (FL) application or a machine learning (ML) application. The requested service may be further associated with the application.

[0006] The VFL capability may be associated with at least one of a machine learning (ML) capability or a cascading relay capability.

[0007] The authorization message may include a value indicating a duration of time during which the WTRU may be authorized to use the requested service.

[0008] A device (e.g., a session management function (SMF)) may include a processor configured to perform one or more actions. The device may receive a protocol data unit (PDU) session request. The PDU session request may indicate a vertical federated learning (VFL) capability of a WTRU and may indicate a requested service that is associated with the VFL capability. The device may select a user plane function (UPF) configured to support traffic associated with the requested service and the VFL capability. The device may send a PDU session response, wherein the PDU session response includes a parameter associated with the requested service and the UPF.

[0009] The device may select a policy control function (PCF) configured to support policy provisioning associated with the requested service.

[0010] The requested service may be associated with at least one of federated learning (FL), cascading relay, or machine learning (ML) capabilities, for example.

[0011] Systems, methods, devices, and instrumentalities are described herein related to WTRU-initiated discovery and selection of WTRU(s) for processing and cascading relay nodes over ProSe communication (e.g., device-to-device communication).

[0012] A device (e.g., a WTRU) may include a processor configured to perform one or more actions. The device may send a registration message. The registration message may indicate a capability associated with the WTRU. The device may receive a discovery message. The discovery message may include a request for the WTRU to participate in a task associated with the capability. The device may authorize the use of the capability. The device may send a discovery response. The discovery response may indicate that the WTRU may participate in the task.

[0013] The capability may be a capability to become at least one of an intermediate WTRU or a cascading relay node for a federated learning (FL) application.

[0014] A device (e.g., a WTRU) may include a processor configured to perform one or more actions. The device may receive a topology of a direct device network associated with the first WTRU. The device may send a discovery message to a second WTRU. The discovery message may include a request for a service not provided by the direct device network. The device may receive a discovery response from the second WTRU. The discovery response may include an indication that the second WTRU is authorized to provide the service. The device may verify that the second WTRU is authorized to provide the service. The device may send a notification message to the direct device network. The notification message may indicate that the first WTRU may be associated with the direct device network and the service.

[0015] The topology may include the second WTRU. The second WTRU may be configured to support federated learning (FL) and direct communication, for example.

[0016] The topology may include a third WTRU and an indication of a capability of the third WTRU.

[0017] Systems, methods, and / or instrumentalities disclosed herein may provide PDU session establishment enabling cascaded relay networks. In examples, a WTRU may include a processor that may be configured to perform a method. A session request message may be sent to a network node. For example, the session request message may have been sent by a WTRU. The session request message may indicate a request for a session, a request for a service, information associated with an application, and / or a federated learning (FL) capability of the WTRU. The FL capability may be associated with the service, and / or the service may be associated with the application. An authorization message may be received from the network node. For example, the WTRU may receive the authorization message from the network. The authorization message may indicate that the requested service is authorized based on the FL capability and / or the application information. A session establishment message may be received from the network. For example, the WTRU may receive the session establishment message from the network. The session establishment message may indicate a duration. The duration may be associated with the requested service.

[0018] In examples, the session request message may be sent responsive to a trigger. For example, the WTRU may be further configured to determine a trigger associated with the application. The trigger may be at least one of a start of the application, an indication that another WTRU may be associated with the application, a change in a configuration of the application, or an update of a model. The application may be at least one of an FL application or a machine learning (ML) application. The FL capability of the WTRU may be associated with at least one of a machine learning (ML) capability or a cascading relay capability. Information associated with a machine learning (ML) capability or a cascading relay capability may be derived. For example, a WTRU may be further configured to, based on the authorization message associated with the PDU session request, derive information associated with a machine learning (ML) capability or a cascading relay capability. The session establishment message may indicate a duration of time during which the WTRU may be authorized to use the service. The information may include at least one of an identifier, a Quality of Service (QoS) parameter, a session modification parameter, a processing node type, a cascading relay capability, an application capability provided by the WTRU, a hardware capability provided by the WTRU, an indication of available data, an indication of another application, or a density of devices within a vicinity.

[0019] Systems, methods, and / or instrumentalities disclosed herein may provide PDU session establishment enabling cascaded relay networks. In examples, a method may be performed by a first network node. The first network node may include a processor. A session request message may be received from a WTRU. For example, the first network node may be configured to receive a session request message from a WTRU. The session request message may indicate a requested service and / or afederated learning (FL) capability associated with the requested service. A second network node may be selected. The second network node may be configured to support traffic associated with the requested service and / or FL capability. For example, the first network node may select a second network node that may be configured to support traffic associated with the requested service and / or the FL capability. The second network may be associated with a user plane function (UPF). A session response message may be sent to the WTRU. For example, the first network node may send a session response message to the WTRU. The session response message may include an identifier associated with the second network node and / or a parameter associated with the requested service.

[0020] In examples, the session request message may further indicate information associated with an application. An authorization message may be sent to the WTRU. For example, the first network node may be further configured to send an authorization message to the WTRU. The authorization message may indicate that the requested service may be authorized based on the FL capability and / or the application information. The session request message may be received in response to a trigger. The trigger may be at least one of a start of the application, an indication that another WTRU may be associated with the application, a change in a configuration of the application, or an update of a model. The application may be at least one of an FL application or a machine learning (ML) application. A network node the FL capability may be associated with at least one of a machine learning (ML) capability or a cascading relay capability. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] 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 example.

[0023] 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 example.

[0024] 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 example.

[0025] FIG.2 depicts an example FL operation comparison between original FL and collaborative FL.

[0026] FIG.3 depicts an example of the three categories of federated-learning.

[0027] FIG.4 depicts an example comparison of one or more features of horizontal federated learning (HFL), vertical federated learning (VFL), and federated transfer learning (FTL).

[0028] FIG.5A depicts an example structure of a vertically partitioned FL model.

[0029] FIG.5B depicts an example structure of a vertically partitioned FL model.

[0030] FIG.6 depicts an example multi-tier direct device network enabled by cascading relays.

[0031] FIG.7 depicts an example protocol data unit (PDU) session establishment enabling cascading direct networks.

[0032] FIG.8A depicts an example method for WTRU and intermediate WTRU discovery.

[0033] FIG.8B depicts an example method for WTRU and intermediate WTRU discovery. DETAILED DESCRIPTION

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

[0035] 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), aconsumer 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0062] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c 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.

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

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

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

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

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

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

[0069] 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 theAP. 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.

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

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

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

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

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

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

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

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

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

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

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

[0081] 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 182a, 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.

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

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

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

[0085] In view of Figures 1A-1D, and the corresponding description of Figures 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.

[0086] 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 devicesmay 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.

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

[0088] Systems, methods, devices, and instrumentalities related to enabling cascaded relay networks during PDU session establishment are described herein.

[0089] A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor configured to perform one or more actions. The device may send a protocol data unit (PDU) session request. The PDU session request may indicate a vertical federated learning (VFL) capability of the device and may indicate a requested service that is associated with the VFL capability. The device may receive an authorization message. The authorization message may indicate that the requested service is authorized.

[0090] The device may detect a trigger associated with an application. The PDU session request may be sent in response to the trigger. The trigger may be one or more of the application starting, a first WTRU joining the application, or a change in configuration to the application. The application may be one or more of a federated learning (FL) application or a machine learning (ML) application. The requested service may be, for example, associated with the application.

[0091] The VFL capability may be associated with at least one of a machine learning (ML) capability or a cascading relay capability.

[0092] The authorization message may include a value indicating a duration of time during which the WTRU is authorized to use the requested service.

[0093] A device (e.g., a session management function (SMF)) may include a processor configured to perform one or more actions. The device may receive a protocol data unit (PDU) session request. The PDU session request may indicate a vertical federated learning (VFL) capability of a WTRU and / or may indicate a requested service that is associated with the VFL capability. The device may select a user plane function(UPF) configured to support traffic associated with the requested service and / or the VFL capability. The device may send a PDU session response, wherein the PDU session response includes a parameter associated with the requested service and / or the UPF.

[0094] The device may select a policy control function (PCF) configured to support policy provisioning that may be associated with the requested service.

[0095] The requested service may be associated with at least one of a federated learning (FL), a cascading relay, or a machine learning (ML) capability.

[0096] Systems, methods, devices, and instrumentalities described herein may be related to WTRU- Initiated discovery and selection of WTRU(s) for processing and / or cascading relay nodes over ProSe communication (e.g., device-to-device communication).

[0097] A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor configured to perform one or more actions. The device may send a registration message. The registration message may indicate a capability associated with the WTRU. The device may receive a discovery message. The discovery message may include a request for the WTRU to participate in a task associated with the capability. The device may authorize the use of the capability. The device may send a discovery response. The discovery response may indicate the WTRU may participate in the task.

[0098] The capability may be a capability to become at least one of an intermediate WTRU or a cascading relay node for a federated learning (FL) application.

[0099] A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor configured to perform one or more actions. The device may receive a topology of a direct device network associated with the first WTRU. The device may send a discovery message to a second WTRU. The discovery message may include a request for a service not provided by the direct device network. The device may receive a discovery response from the second WTRU. The discovery response may include an indication that the second WTRU is authorized to provide the service. The device may verify that the second WTRU is authorized to provide the service. The device may send a notification message to the direct device network. The notification message may indicate the first WTRU is associated with the direct device network and / or the service.

[0100] The topology may include the second WTRU. The second WTRU may be configured to support federated learning (FL) and / or direct communication.

[0101] The topology may include a third WTRU and / or an indication of a capability of the third WTRU.

[0102] Systems, methods, and / or instrumentalities disclosed herein may provide PDU session establishment enabling cascaded relay networks. In examples, a WTRU may include a processor that maybe configured to perform a method. A session request message may be sent to a network node. For example, the session request message may have been sent by a WTRU. The session request message may indicate a request for a session, a request for a service, information associated with an application, and / or a federated learning (FL) capability of the WTRU. The FL capability may be associated with the service, and / or the service may be associated with the application. An authorization message may be received from the network node. For example, the WTRU may receive the authorization message from the network. The authorization message may indicate that the requested service is authorized based on the FL capability and / or the application information. A session establishment message may be received from the network. For example, the WTRU may receive the session establishment message from the network. The session establishment message may indicate a duration. The duration may be associated with the requested service.

[0103] In examples, the session request message may be sent responsive to a trigger. For example, the WTRU may be further configured to determine a trigger associated with the application. The trigger may be at least one of a start of the application, an indication that another WTRU may be associated with the application, a change in a configuration of the application, or an update of a model. The application may be at least one of an FL application or a machine learning (ML) application. The FL capability of the WTRU may be associated with at least one of a machine learning (ML) capability or a cascading relay capability. Information associated with a machine learning (ML) capability or a cascading relay capability may be derived. For example, a WTRU may be further configured to, based on the authorization message associated with the PDU session request, derive information associated with a machine learning (ML) capability or a cascading relay capability. The session establishment message may indicate a duration of time during which the WTRU may be authorized to use the service. The information may include at least one of an identifier, a Quality of Service (QoS) parameter, a session modification parameter, a processing node type, a cascading relay capability, an application capability provided by the WTRU, a hardware capability provided by the WTRU, an indication of available data, an indication of another application, or a density of devices within a vicinity.

[0104] Systems, methods, and / or instrumentalities disclosed herein may provide PDU session establishment enabling cascaded relay networks. In examples, a method may be performed by a first network node. The first network node may include a processor. A session request message may be received from a WTRU. For example, the first network node may be configured to receive a session request message from a WTRU. The session request message may indicate a requested service and / or a federated learning (FL) capability associated with the requested service. A second network node may be selected. The second network node may be configured to support traffic associated with the requestedservice and / or FL capability. For example, the first network node may select a second network node that may be configured to support traffic associated with the requested service and / or the FL capability. The second network may be associated with a user plane function (UPF). A session response message may be sent to the WTRU. For example, the first network node may send a session response message to the WTRU. The session response message may include an identifier associated with the second network node and / or a parameter associated with the requested service.

[0105] In examples, the session request message may further indicate information associated with an application. An authorization message may be sent to the WTRU. For example, the first network node may be further configured to send an authorization message to the WTRU. The authorization message may indicate that the requested service may be authorized based on the FL capability and / or the application information. The session request message may be received in response to a trigger. The trigger may be at least one of a start of the application, an indication that another WTRU may be associated with the application, a change in a configuration of the application, or an update of a model. The application may be at least one of an FL application or a machine learning (ML) application. A network node the FL capability may be associated with at least one of a machine learning (ML) capability or a cascading relay capability.

[0106] Feature(s) associated with enabling cascaded relay networks through protocol data unit (PDU) session establishment are provided herein.

[0107] A WTRU may send a PDU session request (e.g., for PDU session establishment or PDU session modification). The PDU session request may include indications of vertical federated learning (VFL) processing or cascading capabilities. The PDU session request may include artificial intelligence (AI) or machine learning (ML) information (e.g., supported artificial intelligence / machine learning (AI / ML) features, such as model components and / or other AI / ML capabilities of the WTRU).

[0108] The WTRU may receive a message authorizing services it requests (e.g., requires) for federated learning (FL), cascading relay, or AI / ML processing WTRU capabilities. Services the WTRU requests may include one or more services that the WTRU provides to other nodes (e.g., traffic relaying and / or forwarding services, AI / ML processing services, caching services, and / or the like). The WTRU may receive authorization for the addition, joining, and / or acceptance of new WTRUs and / or nodes to the network (e.g., if / when the WTRU is a cascading relay).

[0109] The WTRU may receive a PDU session response (e.g., PDU session establishment acceptance or PDU session modification acceptance) with information related to the approved WTRU capabilities the WTRU may take. The PDU session response may include a duration for which the WTRU capabilities (e.g., the rules) may be used.

[0110] An SMF may receive (e.g., from a WTRU) a PDU session request (e.g., for PDU session establishment). The PDU session request may include AI / ML related information (e.g., supported AI / ML features, such as model components, and / or other AI / ML capabilities of the requesting WTRU).

[0111] The SMF may select the policy control function (PCF) that may support policy provisioning (e.g., FL policy provisioning for the requesting WTRU).

[0112] The SMF may select a user plane function (UPF) to support the traffic (e.g., AI / ML and / or FL traffic).

[0113] The SMF may send (e.g., via AMF) a PDU session accept message to the requesting WTRU. The PDU session accept message may include AL / ML information and / or FL parameters.

[0114] WTRU-initiated discovery and selection of WTRU(s) for processing and / or cascading relay nodes over ProSe communication may be performed.

[0115] In examples, one or more of the following operations may be performed.

[0116] A WTRU may receive a message. The message may include one or more of AI / ML service(s), WTRU(s) that support FL and direct communication, intermediate WTRU(s) and their capabilities, the topology of the direct device network, and / or the like.

[0117] A WTRU may send a registration message to a network (e.g., to register or update / amend an existing registration). The registration message may indicate the AI / ML and / or FL capabilities of the respective WTRU.

[0118] A WTRU may receive information associated with intermediate WTRU(s) (e.g., newly assigned intermediate WTRU(s)). The WTRU may receive a topological structure (e.g., the topological structure resulting from newly assigned WTRU(s)). The topological structure may include the AI / ML model and / or the existing WTRU communication network (e.g., if any). The WTRU may receive information associated with (e.g., related to) the sidelink communication (e.g., allocated resources for sidelink communication). The WTRU may receive information related to sidelink / ProSe communication with intermediate WTRU(s).

[0119] A WTRU may send and / or receive a ProSe discovery message. The ProSe discovery message may include one or more of the WTRU’s AI / ML capabilities, services being offered / provided, AI / ML features supported, data types, labels supported, and the like.

[0120] The WTRU may authorize the requested AI / ML WTRU capabilities and / or type (e.g., intermediate node).

[0121] The WTRU may send / receive a ProSe discovery response. The ProSe discovery response may confirm the WTRU’s participation in the AI / ML application and / or AI / ML task.

[0122] The WTRU may send / receive an acknowledgment message. The acknowledgment message may confirm the discovery and device association to the network, the application, and / or the task.

[0123] The WTRU may notify the application and / or the network of the newly joined WTRU.

[0124] Sidelink and ProSe communication may be performed.

[0125] Device-to-Device (D2D) direct communication protocol may enable devices (e.g., two WTRUs) to communicate directly (e.g., with or without the aid of the network). Different examples (e.g., scenarios) may exist for D2D communication depending on whether the devices (e.g., WTRUs) involved are within the coverage of a cellular network. Sidelink (SL) may enable proximate devices to directly communicate without packets going through a network. Targeted applications (e.g., for SL) may include higher priority services, V2X services, and / or industrial Internet of Things (IIoT). D2D communication may provide ultra- low latency links. D2D communication may support applications such as augmented reality (AR), virtual reality (VR), and extended reality (XR) applications.

[0126] D2D communication may support technologies, including proximity services (ProSe) and / or group communication. ProSe services may allow devices to communicate with each other if the devices are within proximity to each other (e.g., are nearby each other). ProSe services may be enabled by D2D discovery and D2D direct communication procedures. Discovery mechanisms may allow a WTRU to discover another WTRU in its proximity (e.g., which may be performed directly by the WTRU or through a network). Group communication mechanisms may allow one-to-many communication among WTRUs (e.g., in a highly resource-efficient manner). Group communication mechanisms may allow messages to be disseminated to a large group of devices (e.g., WTRUs) over a downlink stream (e.g., common downlink stream).

[0127] For unicast communication, communicating entities may use a Layer-2 ID to identify the WTRU(s) (e.g., each WTRU). An application layer ID may be associated with V2X application(s) within a WTRU (e.g., the same WTRU). In examples, a WTRU may have more than one application layer ID. An application layer ID (e.g., each application layer ID) of a WTRU (e.g., the same WTRU) may be treated (e.g., seen) as a different WTRU. The WTRU may maintain the application layer ID and / or the Layer-2 ID(s) used for unicast links. Applications may use an application layer ID (e.g., may not use the Layer-2 ID(s)). In examples, applications using an application layer ID may allow changes to the Layer-2 ID(s) without requesting (e.g., requiring) an update of the applications (e.g., V2X applications). ).

[0128] User IDs (e.g., EPC ProSe User ID) may identify a WTRU registered for ProSe. An application layer group ID may identify an application layer group to which a WTRU belongs, a user (e.g., within the context of an application), or a group of users (e.g., within the context of an application).

[0129] Feature(s) associated with device-to-device federated learning (FL) are provided herein.

[0130] FIG.2 depicts an example FL operation comparison between an FL (e.g., an original FL) and a collaborative FL (e.g., through D2D communication). The FL may be a first FL and the collaborative FL may be a second FL.

[0131] An application server may have a transmission delay parameter (e.g., requirement) for an FL member (e.g., an FL member running in a WTRU). FL performance may decrease if WTRU(s) that are far away from the network (e.g., a gNB) do not fulfill a transmission delay parameter (e.g., requirement) imposed by the FL application (e.g., while holding a valuable dataset). A performance decrease (e.g., constraint) may be alleviated by using D2D communications. D2D communications may allow FL members to send their local AI / ML parameters to nearby devices. As illustrated in FIG.2, the nearby devices may use an AI / ML model received from other devices to train a local model.

[0132] FIG.2 depicts an example FL operation comparison between an original FL and a collaborative FL. As depicted in FIG.2, six participating WTRUs may use D2D communications to outperform a first FL mechanism (e.g.,an original FL mechanism). The first FL mechanism, which may be an original FL mechanism, may use (e.g., only four) WTRUs (e.g., directly connect to the eNB). Enabling D2D communication may allow for the use of WTRUs that otherwise may not meet transmission latency requirements. Enabling D2D communication may reduce energy consumption (e.g., since ML model parameters may be transmitted to other WTRUs instead of to a network node (e.g., a gNB), which may be farther away).

[0133] FIG.3 depicts an example of the three categories of federated learning.

[0134] Vertically partitioned federated learning may be performed. Federated learning (FL) may be an ML paradigm where multiple parties collaboratively execute machine learning models without having to centralize their data. There may be three categories of FL: horizontal federated learning (HFL), vertical federated learning (VFL), and / or federated transfer learning (FTL).

[0135] HFL may be used if / when the participants (e.g., WTRUs) share a feature space while holding different data.

[0136] VFL may be used if / when a party (e.g., each party) keeps its data and / or a model locally, and exchanges intermediate computed results.

[0137] FTL may be used if / when datasets differ in features and / or sample spaces with limited overlaps. For example, EEG data from one or more subjects with heterogeneous distributions may collaboratively build BCI models using FTL.

[0138] HFL and / or VFL may adopt different training protocols (e.g., due to differences in data partitions).

[0139] In HFL, a party (e.g., each party) may train a local model and / or may exchange model updates (e.g., parameters or gradients) with a server, which may aggregate the updates and / or may send the aggregating result back to a party (e.g., each party). The output of an HFL training procedure may be a global model shared among one or more parties (e.g., all parties). A party (e.g., each party) in HFL may use the global model to make inferences separately.

[0140] In VFL, a party (e.g., each party) may exchange intermediate computed results while keeping its data and model local. The output of a VFL training procedure may be a local model (e.g., a separate model) for a party (e.g., each party). Parties in VFL may collaborate to make inferences.

[0141] FL may be categorized into cross-device and / or cross-silo settings. The cross-device FL may involve a vast number of mobile or edge devices (e.g., WTRUs) as the participating parties. The cross-silo FL may involve a limited number of organizations as the participating parties. HFL may be cross-device or cross-silo FL. VFL may, for example, belong to the cross-silo FL.

[0142] FIG.4 depicts an example comparison of one or more features of HFL, VFL, and FTL.

[0143] In VFL, a party may have a disjoint subset of features. VFL may be used if / when privacy may be a priority (e.g., such as in military, finance, healthcare settings, and / or the like).

[0144] For example, a bank and / or an e-commerce company may operate in the same city. User sets for both the bank and / or the e-commerce company may include many of the residents of an area, and / or the intersection of their user space may be large. The bank may record the user’s revenue, expenditure behavior, and / or credit rating while the e-commerce company may retain the user’s browsing and / or purchasing history, resulting in distinct feature spaces. If both parties want a prediction model for product purchase based on user product information, backpropagation algorithms may be used.

[0145] FIGS.5A-5B depict example structures of exemplary vertically partitioned FL models.

[0146] Feature(s) associated with ProSe discovery procedures supporting the discovery of nodes in a distributed topology are provided herein.

[0147] VFL may request (e.g., require) intermediate results to be shared among participating FL nodes (e.g., which enables large FL tasks to be broken down into sub-tasks). VFL may allow FL tasks and / or sub- tasks to be trained and / or executed independently (e.g., a divide-and-conquer approach). VFL may establish a multi-hop topology of FL logical tasks. VFL may request (e.g., require) participating FL nodes to collaborate for inference.

[0148] Cooperative federated learning over direct device connectivity may assume the connectivity of a collection of devices inhabiting a star topology for executing FL tasks. In examples, traffic may go through asingle relay and / or master device, or a relay that may be directly connected to the network through a Uu reference point.

[0149] The increased complexity of AI / ML tasks, distributed availability of AI / ML features to be used for the models (e.g., features needed for a single model being available in different locations), privacy concerns with distribution of sensitive data, resource scarcity of WTRUs, and / or the volatile nature of resource availability in direct device connections may indicate (e.g., require) an expanded workload distribution across WTRUs (e.g., WTRUs in one-hop distance, resembling a star topology).

[0150] A distributed approach may be executed (e.g., taken) in which the device connectivity inhabits a tree topology (e.g., introducing cascading direct device connectivity paths and / or relay nodes) and / or a mesh topology (e.g., where one device may be connected to more than one device for completing tasks).

[0151] Feature(s) associated with expanding ProSe discovery procedures to support the discovery of nodes in more distributed topologies (e.g., multi-hop relays) to support collaborative networks (e.g., VFL) are provided herein.

[0152] Feature(s) associated with expanding PDU session and / or modification procedures to allow collaborative applications (e.g., VFL applications) to convey information related to device (e.g., WTRU) capabilities and / or to allow devices (e.g., WTRUs) to collaborate for inference (VFL inference) are provided herein.

[0153] FIG.6 depicts an example multi-tier direct device network enabled by cascading relays.

[0154] FL workload distribution to WTRUs may (e.g., only) consider WTRUs in a hop distance (e.g., such as a one-hop distance resembling a star topology). Procedures that may enable tree topologies (e.g., introducing cascading and / or multi-hop direct device connectivity paths and / or relay nodes) or mesh topology (e.g., where one device may be connected to more than one device for completing tasks) may be introduced (e.g., to more efficiently distribute FL workload).

[0155] Collaborative WTRU networks or collaborative relay networks may be D2D networks that have more than one degree and / or level of worker and / or collaborative nodes (e.g., as depicted in FIG.6). Collaborative WTRU networks or collaborative relay networks (e.g., D2D networks) may be treated as (e.g., seen as) a collection of multi-hop D2D networks.

[0156] WTRUs that act as FL worker nodes may be referred to as collaborative WTRUs. Collaborative WTRUs may be capable of one or more of the following: hosting FL worker node(s), WTRU-to-WTRU relaying, WTRU-to-network relaying, or acting as a multi-hop relay.

[0157] A collaborative WTRU may host a primary, coordinator, and / or collaborator FL node. The results of the FL execution may be received at the primary, coordinator, and / or collaborator FL node.

[0158] A collaborative WTRU may be connected to a parent collaborative WTRU in a leg (e.g., hosting its parent FL node). A parent collaborative WTRU may have one or more worker, sub-tree, child, sibling, branch, and / or leaf WTRUs (e.g., where FL worker nodes are hosted). A worker, sub-tree, child, sibling, branch, and / or leaf WTRU’s own AI / ML learning or inference may depend on the results of its worker, sub- tree, child, sibling, branch, and / or leaf node(s).

[0159] A collaborative WTRU may (e.g., be capable of) collect intermediate data from sub-tree, child, sibling, branch, and / or leaf nodes (e.g., if any). A collaborative WTRU may (e.g., be capable of) combine and / or update models. A collaborative WTRU may act as an FL server where the global model is stored and updated. A collaborative WTRU may have one or more of the following capabilities intermediate result data processing, data relaying, collaborative node coordination, and collaborative task coordination.

[0160] Feature(s) associated with communicating WTRU capabilities are provided herein.

[0161] The capabilities of WTRUs to serve as processing nodes or cascading relay nodes may be dynamically changed (e.g., removed) or assigned to the WTRU. Capabilities may be realized as WTRU types or WTRU roles that the corresponding WTRU may take on (e.g., for a period of time). WTRU types or roles may be known to WTRUs and / or a network. Capabilities, WTRU types, or WTRU roles may be (pre)configured on the WTRUs.

[0162] An index number may be used to refer to particular capabilities, WTRU types, or WTRU roles (e.g., during communication). The index number may be understood by the communicating entities.

[0163] Features may refer to AI / ML features or model components of a global AI / ML computation.

[0164] Feature(s) associated with QoS handling for collaborative WTRUs are provided herein.

[0165] A WTRU (e.g., each WTRU) may maintain different QoS contexts and / or QoS rule(s) for a QoS flow (e.g., each QoS flow). The QoS flow may be identified by a QoS flow identifier (PFI) per destination node (e.g., collaborative relay) which may be identified by destination Layer-2 ID. QoS metrics (e.g., QoS contexts and / or QoS rule(s) for a QoS flow) and identifiers may be related to PC5 connectivity. A collaborative WTRU may maintain one or more (e.g., at least two) kinds of flows (e.g., PC5 flows): control flow and / or results flow.

[0166] Control flow may be used to share control information and / or metadata related to the formed VFL collaborative network and / or WTRU group.

[0167] Results flow may be used to exchange results (e.g., intermediate or complete results).

[0168] Feature(s) associated with a packet filter set are provided herein.

[0169] The packet filter set may support packet filters based on one or more of the following: FL packet type (e.g., control packet, result packet, or model packet); packet direction; collaborative node capabilities(e.g., intermediate result data processing, data relaying, FL node coordination, and / or FL task coordination); the hop, layer, or degree the WTRU may be at in the overall topology; and whether the source and / or destination may be a collaborative node.

[0170] A packet direction (e.g., which may be a first packet direction and / or a second packet direction) may be differentiated as traffic goes from a collaborative node to a child collaborative node. A second packet direction may be differentiated as traffic goes from a child collaborative node to a parent collaborative node.

[0171] If / when the WTRU assigns a new PFI, the WTRU may associate the new PFI with the collaborative node capabilities of the destination WTRU.

[0172] A collaborative WTRU may (e.g., always) prioritize the collaborative WTRU’s own results over the collaborative WTRU’s worker node’s results if / when results are forwarded and / or routed upstream towards the primary WTRU (e.g., where the final results are generated). Prioritization may be because the collaborative WTRU’s own results are computed using the worker node’s results. In examples, the collaborative WTRU’s results may include the worker node’s results or a processed version of the worker node’s results.

[0173] Feature(s) associated with enabling cascaded relay networks during PDU session establishment are provided herein.

[0174] A WTRU may provide device capabilities (e.g., AI / ML capabilities, cascading relay capabilities) to a network at the PDU session establishment stage. Device capabilities may be used for authorizing (e.g., by the network) the AI / ML and / or cascading relay WTRU capabilities that the WTRU may take on.

[0175] FIG.7 depicts an example of PDU session establishment enabling cascading direct networks.

[0176] In examples, one or more of the following operations (e.g., as represented in FIG.7) may be performed.

[0177] At 1, an FL application event may trigger the WTRU to establish and / or modify a PDU session with the network. The FL application event may be one or more of the following: starting of the application; updating of the model and / or a new iteration of training (e.g., updating the model due to the availability of new features and / or collaborative nodes); a new WTRU joining the application through SL and / or ProSe or Uu reference points; and / or a change to the configuration of the application (e.g., updated features).

[0178] At 2, the WTRU may send a PDU session request (e.g., a PDU establishment request or a PDU modification request) to the network. The PDU session request may include information related to an AI / ML application (e.g., an FL application that may have triggered the WTRU at 1). In examples, the information included in the PDU session request may include a user ID (e.g., GPSI, SUPI), PC5 QoS-relatedparameters, Uu QoS-related parameters (e.g., PDU modification), the type of processing node or cascading relay WTRU capabilities that the WTRU may be capable of taking on, AI / ML capabilities the WTRU may provide, hardware capabilities (e.g., GPU, Neural Processor, sensors), and / or data and software capabilities (e.g., available features, data types and / or labels).

[0179] In examples, if the WTRU is aware of an existing FL application or a group that the WTRU may like to join, the information included in the PDU session request may include the corresponding AI / ML application IDs and / or group IDs (e.g., of the target desired group communications). In examples, the information included in the PDU session may include traffic related parameter(s) (e.g., requirements) information (e.g., UL / DL foreseeable traffic size and type), a time or time window (e.g., if the WTRU is capable of producing a time or time window) at which the WTRU may determine to (e.g., wants to) engage in the communications, WTRU IDs that the registering WTRU may know in advance that the registering WTRU may communicate directly with (e.g., collaborative relays, processing nodes with features and / or data of interest to the WTRU), information of supported services, and / or density of devices within the vicinity (e.g., cell).

[0180] The PDU session request may include application IDs and / or group IDs of requested group communications. The PDU session request may include information regarding a new FL application grouping (e.g., if the WTRU creates a new FL application grouping, the WTRU may include information). The Information may be provided to the network so that the information may be conveyed to the corresponding application function (AF) / application server (AS).

[0181] The PDU session request may include information on supported services. For example, information on supported services may include a vector of services, a record including (e.g., each record containing) information of a service (e.g., a service ID, service parameters, service requirements, supported multimodal flows, and / or the like).

[0182] The PDU session request may include a density of devices (e.g., WTRUs) within the vicinity (e.g., cell). The density of devices may be specified as a number (e.g., a number of devices) or as an indication (e.g., low, medium, high). The WTRUs may be configured to interpret information conveyed in the density of devices within a vicinity parameter (e.g., information). The density of devices within a vicinity may be used for adjusting protocol and / or procedural parameters (e.g., determining the broadcast message frequency).

[0183] At 3, the AMF may select the SMF configured to support AI / ML or FL sessions.

[0184] At 3A, the AMF may send the PDU session request (e.g., PDU session establishment request) to the SMF.

[0185] At 4, the network (e.g., a 5G system) may authorize (e.g., authenticate) a WTRU, the requested services for FL, cascading relay, and / or processing WTRU capabilities. Information related to WTRU capabilities may be used for authorizing WTRU capabilities for the WTRU (e.g., authorizing the WTRU to become a cascading relay WTRU). The authorization message may specify if the WTRU is able to authorize the addition and / or joining of new WTRUs and / or nodes to the network (e.g., if / when the WTRU may be a cascading relay).

[0186] At 5, the SMF may select the PCF that may support the FL policy provisioning. The SMF may establish a WTRU policy association with the PCF (e.g., for WTRU policy and / or parameter provisioning).

[0187] If there are multiple PCFs used by WTRU(s) associated with the collaborative application, the PCFs may communicate with one or more other PCFs (e.g., each other) to decide (e.g., determine) whether to generate PCC rules jointly. If PCC rules are generated jointly, the corresponding PCFs may communicate with each other for coordinating the PCC rules generated for the AI / ML and / or FL services (e.g., provided by the WTRUs served by each PCF). If there is an update in the performance and / or resources related to a WTRU served by a PCF (e.g., during the application execution), the PCF may report the update in the performance and / or resources to the other PCF. Reporting may be helpful in generating coherent PCC rules and / or aligning the policies for the involved WTRUs.

[0188] At 6, the SMF may select the UPF that supports AI / ML and / or FL traffic. In examples, the PCF may proceed with the authorization of the AI / ML and / or FL WTRU capabilities (e.g., through AUSF, if it is the first time). The PCF may (e.g., otherwise) check the UDM for stored authorization information.

[0189] At 7, the WTRU may receive a PDU session accept message from the network (e.g., a 5G system). The PDU session accept message may include information related to the approved WTRU capabilities the WTRU may use and / or the duration the rules may be valid (e.g., taken). If the duration of a WTRU capability expires, the WTRU may request authorization for the WTRU capability again (e.g., to be able to operate with the requested WTRU capability). A request for authorization may be made through WTRU registration procedures or PDU session establishment and / or modification procedures.

[0190] Feature(s) associated with WTRU-initiated discovery and selection of WTRU(s) for processing and cascading relay nodes over ProSe communication are provided herein.

[0191] A WTRU may discover an existing multi-tier and / or cascading network. The WTRU may discover existing multi-tier relay networks for AI / ML applications and / or may join at a level and / or tier of the D2D network. The level and / or tier of the D2D network that the WTRU may join may depend on the features and / or data available at a node.

[0192] A node (e.g., a WTRU) in an existing network may discover other suitable nodes (e.g., WTRUs) to join the network (e.g., branching out from the discoverer’s node).

[0193] FIGs.8A-8B depict example methods for WTRU and / or intermediate WTRU discovery.

[0194] In examples, one or more of the following operations (e.g., as represented in FIGS.8A-8B) may be performed.

[0195] At 0, the WTRU and the network components (e.g., SMF, PCF, NWDAF) may be initialized or provisioned with information (e.g., initial information) related to AI / ML and / or FL applications. Initial information may include one or more of the following: known AI / ML services, known WTRUs that support FL and direct communication, known intermediate WTRUs and the WTRU capabilities the intermediate WTRUs hold, and / or known topology of the direct device network. The WTRU may receive a partial topology (e.g., that may be associated with the WTRU’s location).

[0196] At 1, the WTRU may register with the network or may update and / or amend an existing registration with the network. The WTRU may indicate the WTRU’s capability to become an intermediate WTRU or a cascading relay node for FL application(s).

[0197] At 2, the WTRU may receive a configuration message with the information of newly assigned intermediate WTRU(s) and / or the resulting topological structure (e.g., of both the AI / ML model and the existing WTRU communication network, if any). The WTRU may receive information related to sidelink communication (e.g., allocated resources for sidelink communication with newly assigned WTRU(s)). The information of the intermediate WTRU(s) may be received by the network (e.g., AMF, SMF, PCF) and / or application layer components (e.g., an AF / AS in the network and / or an application running on the WTRU). Information of intermediate WTRU(s) may be transferred using MBS. Information of intermediate WTRU(s) may be provisioned using configuration update procedures.

[0198] At 3, AI / ML WTRU and / or node discovery may be triggered (e.g., by various trigger events). Trigger events may include one or more of an application layer notification (e.g., from an application running on the WTRU or AF / AS in the network) to establish device-to-device connectivity, intermediate WTRU registration with the network (e.g., 5G system), and / or based on a (pre)configured time. In examples, AI / ML WTRU and / or node discovery may be executed periodically (e.g., periodically consider announcement messages being received). The triggering may vary based on one or more examples (e.g., on two examples (e.g., scenarios).

[0199] In a first example (e.g., Example 1 depicted at 800 in FIG.8A), an intermediate node may discover a WTRU. The WTRU(s) participating in a multi-tier D2D network may send discovery announcement messages (e.g., over PC5 reference point) to announce one or more of the WTRU’s AI / ML capabilities, services being offered, AI / ML features supported, and / or data types and / or labels supported (e.g., over the PC5 interface). The information included in the discovery announcement may be used by other SL WTRU(s) and / or intermediate WTRU(s) (e.g., received through monitoring) to identify suitableWTRUs in proximity. The announcement messages may be broadcast. The announcement messages may be received by another WTRU or may target one or more WTRU(s) (e.g., via restricted discovery procedures).

[0200] In a second example (e.g., Example 2 depicted at 810 in FIG.8B), a- WTRU may discover an intermediate node. An intermediate WTRU may advertise its capabilities and information regarding AI / ML operations, applications, and / or the resources being allocated. The WTRUs that are part of the node (e.g., branching off from the node in the topology) may receive the services, AI / ML features, data types, and / or labels supported by the intermediate WTRU. The announcement messages may be broadcast (e.g., through broadcast or multicast). The announcement messages may be received by another WTRU or may be announced targeting one or more WTRUs (e.g., via restricted discovery procedures).

[0201] At 4, the WTRUs and / or intermediate WTRUs may receive AI / ML node discovery messages. Node discovery message(s) may include one or more of the following AI / ML features supported by the WTRU, data types and / or labels supported by the WTRU, AI / ML features requested (e.g., required) by the WTRU, FL or AI / ML models supported, AI / ML and / or FL services that are provided by the WTRU, AI / ML and / or FL services that are requested (e.g., required) by the WTRU, and / or parameters.

[0202] The AI / ML and / or FL services provided by the WTRU may be the AI / ML and / or FL services provided by the WTRU to other WTRUs (e.g., the AI / ML and / or FL services part of the message may be used as an advertisement of available capabilities). For example, the WTRU may provide FL processing capabilities to other WTRUs.

[0203] AI / ML and / or FL services that are requested (e.g., required) by the WTRU may be services and / or capabilities requested (e.g., required) by the WTRU. For example, the WTRU may discover intermediate node(s) that have certain features.

[0204] The node discovery message may include one or more of the following parameters: application code / ID; time duration and / or resources (e.g., any combination of a time window, a start time, end time, at the level of application execution, or at the level of individual sidelink links); traffic-related parameters (e.g., requirements), such as UL / DL foreseeable traffic size and / or type; a time window (e.g., if the WTRU is capable of producing a time or time window) for which the WTRU may determine to (e.g., wants to) engage in communications; WTRU IDs (e.g., a set and / or subset of WTRU IDs) that the WTRU may anticipate direct communication with or WTRU aggregations associated with the WTRU IDs; and / or information of FL services and / or FL models (e.g., features required by a WTRU).

[0205] The node discovery message may include information on the AI / ML services and the intermediate nodes that are supported by the PLMN, cell, base station, or WTRUs. The node discoverymessage may include information related to accessing AI / ML services, WTRUs (e.g., link IDs, IP addresses), and / or FL groups.

[0206] If / when the FL application-related information (e.g., only the FL application-related information) is received, the WTRU may derive (e.g., further) information from the AI / ML application and / or the cascading network. The WTRU may derive (e.g., further) information by looking the information up (e.g., querying information) in a database (e.g., that may be hosted locally or in the network) or by querying an application layer service (e.g., an AF / AS).

[0207] In examples, one or more parameters may be omitted in the node discovery message for security reasons. In examples, sensitive information may (e.g., instead) be sent at 5 or at 6 (e.g., after the WTRU has been authorized). Depending on the example (e.g., scenario), the node discovery message may be used to advertise available capabilities or as a request to discover available services, WTRUs, and / or WTRU aggregations.

[0208] At 4A, the intermediate WTRU and / or the network may authorize the services, WTRUs, and / or intermediate WTRUs that are being discovered. The authorization may ensure that the services, WTRUs, and / or intermediate WTRUs are used for the AI / ML application within a segment of the network or the geographical location (e.g., within the cell, PLMN).

[0209] The intermediate WTRU may communicate with the network to authorize the discovered WTRUs and / or AI / ML services for the given network segment or geographical location.

[0210] There may be privileged intermediate WTRU(s). Privileged intermediate WTRU(s) may perform the authorization on behalf of the network (e.g., using the information received from the network).

[0211] Authorization for the services, WTRUs, and / or intermediate WTRUs that are being discovered may be integrated with existing ProSe authorization procedures or may be used in addition to the existing ProSe authorization procedures (e.g., for authorizing FL procedures).

[0212] At 5, the intermediate WTRU may receive a discovery response message from the participating WTRUs (e.g., in Example 2 of FIG.8B) or from the intermediate WTRU (e.g., in Example 1 of FIG.8A). The discovery response message may confirm the discovery. The discovery response message may confirm the intermediate WTRU’s participation in the AI / ML application and / or AI / ML task (e.g., for providing services (in case the WTRU provides FL services) for consuming services, for relaying messages (e.g., acting as a U2N or U2U relay), or any combination as described herein).

[0213] The discovery response message may include one or more of the following: ProSe application code / ID; time duration and / or resources (e.g., any combination of a time window, a start time, and / or an end time at the level of application or at the level of individual sidelink links); traffic-related parameter information (e.g., UL / DL foreseeable traffic size and / or type); a time window (e.g., if the WTRU is able toprovide a time window) for which the WTRU may determine to (e.g., wants to) engage in communications; information of neighboring WTRUs (e.g., WTRU IDs); session information; the degree, layer, level, and / or tier the WTRU may be assigned to (e.g., if a degree, layer, level, and / or tier of the multi-tiered network corresponds to the initial request); or information of the intermediate WTRUs, services, and / or AI / ML applications that are supported by the public land mobile network (PLMN), cell, base station, other WTRUs, and / or the like. Information related to how to access services and / or WTRUs may be included in the discovery response message.

[0214] At 6, the member WTRUs and / or the intermediate WTRUs may (e.g., optionally) receive an acknowledgment message confirming the discovery and device association. The acknowledgment message may have a high priority (e.g., in Example 2 of FIG.8B, where the acknowledgment message may include the information regarding whether the authorization (e.g., from 4A) was successful or not, and / or the reason). An acknowledgment message may include one or more of the parameters included at 5.

[0215] At 7, ProSe and / or sidelink connectivity may be established to the chosen known and / or unknown devices. Communication may be established by the member and / or participating WTRU or by the intermediate WTRU (e.g., by specifying a time value such as a time window or by sending a trigger message at the time the intermediate WTRU expects the WTRUs to establish connectivity).

[0216] WTRUs and / or intermediate WTRUs may exchange information including one or more of the following: information related to the direct communication, IP communication-related information (e.g., IP address configuration, local IP address, IP address allocation mechanism, such as whether the WTRU and / or intermediate WTRU is acting as an IP router or not), and / or QoS information including information about the QoS flows (e.g., specifying the WTRUs and / or intermediate WTRUs PFI, PQI and / or associated services) to be added to the direct communication link (e.g., PC5, ProSe, and / or Sidelink) and / or the WTRUs and / or intermediate WTRUs corresponding QoS parameters. WTRUs and / or the intermediate WTRUs may store peer WTRU’s layer-2 ID for future communication.

[0217] At 7, WTRU participation in the AI / ML application and / or AI / ML task may be confirmed. The WTRU may be confirmed for one or more of the following: for providing services (e.g., in case the WTRU provides FL services), for consuming services, or for relaying messages.

[0218] At 8, the application (e.g., hosted on a mobile device or an AF / AS) may be notified of the newly joined WTRU (e.g., so that the AI / ML application may be able to make a change, such as, model updates). For example, an initial aggregation may include at least two WTRUs (e.g., may only contain two WTRUs. For example, at least two WTRUs may be a display and / or a gaming controller.

[0219] The discovered WTRU or the intermediate WTRU may report the information of the newly added nodes, WTRUs, and / or intermediate WTRUs to the network (e.g., to UDM, AMF, SMF, PCF) and / or to the AF / AS. Information may be used to monitor the status of the D2D network.

[0220] In examples where a WTRU is discovering existing cascading and / or multi-tier D2D networks, an intermediate WTRU (e.g., the closest intermediate WTRU) may become the primary contact point of the AI / ML and / or FL network (e.g., the closest intermediate WTRU to the WTRU).

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

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

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

Claims

CLAIMS What is claimed is:

1. A wireless transmit / receive unit (WTRU) comprising: a processor configured to: send a session request message to a network node, wherein the session request message indicates a request for a session, a request for a service, information associated with an application, and a federated learning (FL) capability of the WTRU, wherein the FL capability is associated with the service, and wherein the service is associated with the application; receive an authorization message from the network node, wherein the authorization message indicates that the requested service is authorized based on the FL capability and the application information; and receive a session establishment message from the network, wherein the session establishment message indicates a duration, wherein the duration is associated with the requested service.

2. The WTRU of claim 1, wherein the session request message is sent responsive to a trigger, and wherein the processor is further configured to determine a trigger associated with the application.

3. The WTRU of claim 2, wherein the trigger is at least one of a start of the application, an indication that another WTRU is associated with the application, a change in a configuration of the application, or an update of a model.

4. The WTRU of any one of claims 1-3, wherein the application is at least one of an FL application or a machine learning (ML) application.

5. The WTRU of any one of claims 1-4, wherein the FL capability of the WTRU is associated with at least one of a machine learning (ML) capability or a cascading relay capability.

6. The WTRU of any one of claims 1-5, wherein the processor is further configured to: based on the authorization message associated with the PDU session request, derive information associated with a machine learning (ML) capability or a cascading relay capability.

7. The WTRU of claim 1-5, wherein the information comprises at least one of an identifier, a Quality of Service (QoS) parameter, a session modification parameter, a processing node type, a cascadingrelay capability, an application capability provided by the WTRU, a hardware capability provided by the WTRU, an indication of available data, an indication of another application, or a density of devices within a vicinity.

8. The WTRU of any one of claims 1-7, wherein the session establishment message indicates a duration of time during which the WTRU is authorized to use the service.

9. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: sending a session request message to a network node, wherein the session request message indicates a request for a session, a request for a service, information associated with an application, and a federated learning (FL) capability of the WTRU, wherein the FL capability is associated with the service, and wherein the service is associated with the application; receiving an authorization message from the network node, wherein the authorization message indicates that the requested service is authorized based on the FL capability and the application information; and receiving a session establishment message from the network, wherein the session establishment message indicates a duration, wherein the duration is associated with the requested service.

10. The method claim 9, wherein the session request message is sent responsive to a trigger, and wherein the method further comprises determining a trigger associated with the application.

11. The method of claim 10, wherein the trigger is at least one of a start of the application, an indication that another WTRU is associated with the application, a change in a configuration of the application, or an update of a model.

12. The method of any one of claims 9-11, wherein the application is at least one of an FL application or a machine learning (ML) application.

13. The method of any one of claims 9-12, wherein the FL capability of the WTRU is associated with at least one of a machine learning (ML) capability or a cascading relay capability.

14. The method of any one of claims 9-13, wherein the method further comprises: based on the authorization message associated with the PDU session request, deriving information associated with a machine learning (ML) capability or a cascading relay capability.

15. The method of claim 9-13, wherein the information comprises at least one of an identifier, a Quality of Service (QoS) parameter, a session modification parameter, a processing node type, a cascading relay capability, an application capability provided by the WTRU, a hardware capability provided by the WTRU, an indication of available data, an indication of another application, or a density of devices within a vicinity.

16. A first network node for providing a session management function (SMF), the network node comprising: a processor configured to: receive a session request message, from a wireless transmit / receive unit (WTRU), wherein the session request message indicates a requested service and a federated learning (FL) capability associated with the requested service; select a second network node that is configured to support traffic associated with the requested service and the FL capability, wherein the second network is associated with a user plane function (UPF); and send a session response message to the WTRU, wherein the session response message comprises an identifier associated with the second network node and a parameter associated with the requested service.

17. The network node of claim 16, wherein the session request message further indicates information associated with an application, and wherein the processor is further configured to: send an authorization message to the WTRU, wherein the authorization message indicates that the requested service is authorized based on the FL capability and the application information.

18. The network node of any one of claims 16-17, wherein the session request message is received in response to a trigger, and wherein the trigger is at least one of a start of the application, an indication that another WTRU is associated with the application, a change in a configuration of the application, or an update of a model.

19. The network node of any one of claims 16-18, wherein the application is at least one of an FL application or a machine learning (ML) application.

20. The network node of any one of claims 16-19, wherein the FL capability is associated with at leastone of a machine learning (ML) capability or a cascading relay capability.

Images