WO2024097408A1 - Système et procédés pour améliorer les performances d'un apprentissage fédéré par l'intermédiaire de communications de liaison latérale - Google Patents

Système et procédés pour améliorer les performances d'un apprentissage fédéré par l'intermédiaire de communications de liaison latérale Download PDF

Info

Publication number
WO2024097408A1
WO2024097408A1 PCT/US2023/036792 US2023036792W WO2024097408A1 WO 2024097408 A1 WO2024097408 A1 WO 2024097408A1 US 2023036792 W US2023036792 W US 2023036792W WO 2024097408 A1 WO2024097408 A1 WO 2024097408A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
wtrus
request
capability
candidate
Prior art date
Application number
PCT/US2023/036792
Other languages
English (en)
Inventor
Morteza KHEIRKHAH
Ulises Olvera-Hernandez
Jung Je SON
Guanzhou Wang
Michelle Perras
Samir Ferdi
Zhibi Wang
Achref METHENNI
Original Assignee
Interdigital Patent Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Interdigital Patent Holdings, Inc. filed Critical Interdigital Patent Holdings, Inc.
Publication of WO2024097408A1 publication Critical patent/WO2024097408A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00—Machine learning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management

Definitions

  • a fifth generation of mobile communication radio access technology may be referred to as 5G new radio (NR).
  • NR 5G new radio
  • a previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE).
  • a wireless transmit/receive unit may receive, from a network node, a first message including a selection policy for federated learning (FL).
  • the WTRU may send to one or more candidate WTRUs, a second message.
  • the second message may indicate a request.
  • the request may be based on the selection policy for FL.
  • the WTRU may receive a third message from at least one candidate WTRU.
  • the at least one candidate WTRU may be from the one or more candidate WTRUs.
  • the third message may indicate an FL capability and a resource availability based on the request.
  • the WTRU may determine a target WTRU from the at least one candidate WTRU based on the FL capability and the resource availability.
  • the WTRU may execute an FL operation with the target WTRU.
  • the request may include a resource availability request.
  • the resource availability request may include at least one of a GPU capacity, a CPU capacity, a battery capacity, or a storage capacity.
  • the resource availability may indicate a characteristic of a resource associated with the at least one candidate WTRU.
  • the characteristic may include at least one of a GPU capacity, a CPU capacity, a battery level, a storage capacity, a memory capacity, or a queue delay of the at least one candidate WTRU.
  • the WTRU may determine that the characteristic satisfies a threshold associated with the resource availability request.
  • the request may include an FL capability request, and the FL capability request may include at least one of a model aggregation, a member selection, a number of training sessions, or a global model distribution.
  • the FL capability may include at least one of a model aggregation, a model transfer, a member selection, or a number of maximum training cycles.
  • the network node may include a policy control function (PCF).
  • PCF policy control function
  • the first message may be a Non- Access Stratum (NAS) message.
  • NAS Non- Access Stratum
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • RAN radio access network
  • ON core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example ON that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • FIG. 2 illustrates an interaction (e.g., a high-level interaction) between participants and an artificial intelligence (Al) server.
  • Al artificial intelligence
  • FIG. 3 illustrates an example method for Proximity Services (ProSe) direct discovery with an example Model A.
  • FIG. 4 illustrates an example method for ProSe direct discovery with an example Model B.
  • FIG. 5 illustrates an example method for Federated Learning (FL) with a decentralized averaging technique.
  • FIG. 6 illustrates an example of two WTRUs performing decentralized FL using a direct device connection during which a centralized FL server has no connection to the two WTRUs.
  • FIG. 7 illustrates an example discovery procedure (e.g., an example discovery procedure with Model B) for FL operations.
  • an example discovery procedure e.g., an example discovery procedure with Model B
  • 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.
  • 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 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.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • 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.
  • 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.
  • 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.
  • BSC base station controller
  • RNC radio network controller
  • 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.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • 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).
  • RAT radio access technology
  • 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.
  • the base station 114a in the RAN 104/1 13 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • 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).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • 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).
  • NR New Radio
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • 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.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • 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).
  • WLAN wireless local area network
  • 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).
  • 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.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • 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.
  • QoS quality of service
  • 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.
  • 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.
  • 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.
  • 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).
  • POTS plain old telephone service
  • 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.
  • 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.
  • 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).
  • 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.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • 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.
  • GPS global positioning system
  • 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. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • 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.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • 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.
  • 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.
  • 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.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • 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.
  • 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.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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.
  • 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.
  • 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.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.
  • 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.
  • 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.
  • FM frequency modulated
  • 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.
  • 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.
  • 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).
  • 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)).
  • 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)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • 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.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the
  • 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.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • 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.
  • 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.
  • 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.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • 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.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • 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).
  • the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • 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.
  • 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.
  • 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.
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting 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).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and
  • 802.11 ac 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine- Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as
  • 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • 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.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for
  • 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • 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.
  • 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.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • 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.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • 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).
  • TTIs subframe or transmission time intervals
  • 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.
  • 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).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • 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.
  • 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.
  • 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.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • 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.
  • 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.
  • 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.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.
  • 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,
  • 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.
  • the CN 115 may facilitate communications with other networks.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • DN local Data Network
  • 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.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • 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.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • 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.
  • 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.
  • RF circuitry e.g., which may include one or more antennas
  • Federated learning may be provided.
  • an Al server e.g., a central Al server
  • the WTRU may perform the local model training within a training cycle based on a model downloaded from the Artificial Intelligence server (e.g., centralized Artificial Intelligence (Al) server) (e.g., using local data).
  • the Artificial Intelligence server e.g., centralized Artificial Intelligence (Al) server
  • the WTRU may deliver the training results (e.g., gradient for the Deep Neural Network (DNN)) to the Al server (e.g., centralized Al server) via a channel (e.g., 5G UL channels).
  • the Al server e.g., centralized Al server
  • the Al server may aggregate the gradients (e.g., model weights) from the WTRUs and update the global model.
  • a training cycle (e.g., a subsequent training cycle) may begin where the Al server distributes the updated global model to WTRUs via a DL channel (e.g., 5G DL channels).
  • Fig. 2 illustrates an example interaction (e.g., high-level interaction) between participants and the Al server (e.g., central Al server) over a system, which may be a 5G system. Examples described herein may be associated with federal learning (FL) over a system, such as a 5G system.
  • the FL training over wireless communication may differ from the FL training in data centers (e.g., where participants (e.g., WTRUs) may have (e.g., variable) conditions in terms of available computational and network resources).
  • the WTRUs may not be homogeneous, and the WTRUs may have (e.g., different) capabilities in terms of computational and network resources or supported ML frameworks.
  • a member selection technique may be needed before a training cycle begins.
  • the conditions of a device may not change.
  • the WTRU re-selection and training re-configurations may not be needed for a training cycle.
  • WTRUs e.g., different WTRUs
  • WTRUs may be re-selected to achieve global training with diverse datasets.
  • Synchronous Federated Learning may be provided.
  • FL may be referred to as SFL.
  • participants may complete the training results uploading within a predefined time window (e.g., WTRUs participating in a training session may need to complete the training results uploading within a predefined latency budget).
  • the UL transmission deadline may be between 1-3 seconds, as illustrated in Table 1.
  • Proximity Services may be provided.
  • Proximity Services may be services that may be provided by a system (e.g., 3GPP system) based on WTRUs being in proximity (e.g., in proximity to one other).
  • WTRUs may perform ProSe, a discovery technique to discover WTRUs in proximity. Examples may include ProSe discovery modes: Model A and Model B.
  • Fig. 3 illustrates an example ProSe direct discovery with Model A.
  • a WTRU e.g., an announcing WTRU
  • the ProSe Query code may be associated with announcing an ID of the WTRU and/or with the service provided by the announcing WTRU.
  • WTRUs that receive the announcement message e.g., a monitoring WTRU
  • WTRUs that receive the announcement message may know (e.g., may be configured to know) that the announcing WTRU is in proximity (e.g., of the monitoring WTRU).
  • Fig. 4 illustrates ProSe direct discovery with Model B.
  • a WTRU may broadcast a solicitation request message with a ProSe Query code, a discovery message, and/or a security protection element.
  • the ProSe Query Code may be associated with an ID of the WTRU or a ProSe service to be discovered.
  • WTRUs that receive the solicitation request message e.g., a discoveree WTRU
  • the ProSe response code may be associated with the discoveree WTRU’s ID or any of a ProSe service provided by the discoveree WTRU, a type of discovery code, a security protection element, and/or metadata information.
  • the discoverer WTRU may know (e.g., may be configured to know) that the discoveree WTRU is in proximity.
  • a device may want to use Sidelink communication (e.g., device-to-device via a reference point) to be retained in the FL training session.
  • Sidelink communication e.g., device-to-device via a reference point
  • devices in an area may have cellular connectivity, and devices elsewhere (e.g., devices outside the area) may be without cellular connectivity but with a (e.g., a good) computational capability, network resource availability, and/or datasets.
  • the disconnected devices may want to engage in the FL model training if they are not already engaged in the FL model training.
  • the disconnected devices may communicate with devices (e.g., in proximity) to deliver local training results (e.g., of the disconnected devices) to the central (e.g., centralized) FL server.
  • FIG. 5 illustrates an example where device_b may interact with the centralized FL server at NG-RAN via device_a, which may have direct cellular connectivity with NG-RAN.
  • the device_b may send its training results to device_a.
  • device_a may send the training results to the FL server.
  • the WTRUs may determine whether WTRUs in a vicinity (e.g., of the WTRUs in the application group) may relay data to the application server.
  • the device_b may find nearby devices to invite the nearby devices to engage with the FL training. For example, the devices may not have cellular connectivity to the cellular network when device_b discovers the devices (e.g., or when the devices discovered device_b).
  • Figure 5 illustrates an example of applying a decentralized averaging technique to FL (e.g., FL with a decentralized averaging technique may outperform the original FL).
  • a set of devices may be part of a distributed FL training session.
  • Cellular connectivity e.g., of the set of devices
  • This set of devices may, for example, be on a train traveling to a destination.
  • the WTRUs may (e.g., may rapidly) have trouble delivering their local training data to an AS/AF (e.g., the centralized FL server due to poor cellular connectivity).
  • AS/AF e.g., the centralized FL server due to poor cellular connectivity
  • the WTRUs may want to change their mode of operation from directly interacting with the FL server (e.g., central FL server) to device-to-device communication to a WTRU nearby.
  • Participants may select a suitable device to act as a local FL server (e.g., to perform model aggregation and determine devices that may be in a training session in the next training cycle, etc.) without requiring interaction with the FL server.
  • a local FL server may select participants (e.g., more participants) without an FL server’s knowledge (e.g., the main FL server’s knowledge) when the server (e.g., the main server) has provided such authority to the local FL server.
  • the central FL server may select and configure the local FL server.
  • the local FL server may be referred to as the Master WTRU. If the Master WTRU has good connectivity with the central FL server (e.g., via the cellular network or other network types), the Master WTRU may deliver the latest global trained model to the central FL server for global model averaging, and the Master WTRU may receive an updated global model.
  • Fig. 6 illustrates two WTRUs performing decentralized FL using a Direct Device connection during which the centralized FL server may have no connection to both WTRUs (e.g., Alice and Bob).
  • Alice may discover Bob in proximity to Alice with the decentralized model averaging technique.
  • Alice may establish a connection with Bob.
  • Bob may aggregate Alice's training results with Bob's training results.
  • Bob may share the global model with Alice (e.g., for further training).
  • WTRUs may find one another for a particular application/service, which a ProSe layer may indicate via a ProSe Application Code or a ProSe Query Code.
  • a WTRU may obtain a ProSe Application Code to find WTRUs in proximity (e.g., of the WTRU) supporting such an application or service.
  • a WTRU may take on responsibilities based on the capabilities of the WTRU. For example, a WTRU may be eligible to take responsibility for heavy processing tasks in a distributed FL model training.
  • a WTRU with network capacity may be qualified to support WTRUs in its proximity (e.g., in proximity of the WTRU with network capacity) to act as a WTRU-to-WTRU or WTRU-to-Network relay.
  • a set of WTRUs with specific capabilities may take certain responsibilities within a service (e.g., which may be identified by ProSe App Code).
  • a discovery process one or more WTRUs of the set may not be available to provide such services to other WTRUs (e.g., within proximity).
  • Techniques may be associated with identifying whether WTRUs within a service or group may deliver on roles/capabilities assigned to the WTRUs.
  • An example may include events that may cause a WTRU to enter a ProSe discovery process for FL. Examples may include whether the WTRUs are initiated by a signal from the network, WTRU, or other entities. Examples may include what the triggering aspects are from the system perspective.
  • Examples may include how a WTRU modifies its discovery process so that WTRUs that meet its FL requirements are contacted during a ProSe discovery procedure.
  • Examples may include how the network or other entities may assist the WTRU in the discovery of other WTRUs nearby.
  • Examples may include criteria/rules for a WTRU to select another WTRU in its proximity in the context of FL. Examples may include which entity may provide such selection rules/policies to the WTRU.
  • Features described herein may be associated with a WTRU becoming a Master WTRU to recruit and/or assist nearby WTRUs in FL operations (e.g., their FL operations).
  • the central FL server may select a set of participants/devices/WTRUs with network and computational resources to discover other devices in proximity (e.g., of the central FL server) to participate in a distributed FL training session and/or to assist other WTRUs in FL operations (e.g., of the other WTRUs).
  • FL-capable devices/WTRUs may be referred to as Master devices/WTRUs.
  • the Master WTRU may discover peers’ proximity (e.g., of the Master WTRU) and inform the central FL server (e.g., AS/AF) about the computational and network availability of the peers, consent of the peers to engage in an FL training session, mobility pattern of the peers, and other predictions (e.g., if available, etc.).
  • the FL server e.g., central FL server
  • the selection result may be informed to the Master WTRUs (e.g., alongside a training configuration and global model).
  • the Master WTRU may share a (e.g., newly) received global model and training configurations with the selected peers (e.g., with a ProSe unicast, broadcast, or groupcast direct communication mode) so that the peers may begin their training.
  • the Master WTRU may act as a participant discoverer and entity that may relay messages between the central FL server and participants.
  • the central FL server may select a set of Master WTRUs in a training cycle (e.g., or another interval).
  • the Master WTRU may act as a central FL server (e.g., the Master WTRU may perform decentralized model averaging and peers’ selection in a training cycle without interacting with the FL server).
  • the FL server e.g., central FL server, which may be an AF/AS
  • the Master WTRU may act as a participant discoverer and a local FL server without relaying information back and forth to the centralized FL server.
  • peers of a Master WTRU may become a Master WTRU to expand FL training participants. Further devices may be discovered over a network of WTRUs to engage in an FL training session.
  • a WTRU e.g., every WTRU
  • becoming a Master WTRU may be performed voluntarily by the device/WTRU, and the centralized FL server or a parent Master WTRU in the chain may grant approval (e.g., approval may be needed).
  • a WTRU may become a Master WTRU and discover other devices via a discovery technique according to a policy that may be distributed to one or more participants (e.g., participant WTRUs).
  • the device may indicate in its discovery procedure that it is seeking to find other devices with specific resource availability and capabilities (e.g., X number of GPUs (e.g., a GPU capacity), Y amount of storage with SSD technology (e.g., a storage capacity), Z amount of flash memory (e.g., a memory capacity), low possibility of mobility/handover, high data rate for DL/UL, etc.) to support FL operations (e.g., decentralized model averaging).
  • the other device e.g., Bob
  • may participate in the FL training session e.g., the same FL training session).
  • the other device e.g., Bob
  • Alice and Bob may engage in multiple consecutive FL training sessions together, and Bob may act as a temporary FL server to Alice.
  • Alice and Bob may deliver trained results to the FL server (e.g., central FL server) and obtain a global model (e.g., a new global model) for further training.
  • the FL server e.g., central FL server
  • a global model e.g., a new global model
  • Bob e.g., the Master device
  • Bob may act as a decentralized model aggregator and an FL participant.
  • a device initiated to be a local FL server may form a local group (e.g., to be a local FL server).
  • the device may assign a Group ID and indicate it in the discovery messages when the device tries to find or recruit other devices.
  • the FL capabilities e.g., required FL capabilities
  • the model transfer among the group may be associated with the Group ID.
  • the local FL server may communicate with (e.g., other) members in a group (e.g., via groupcast mode of ProSe Direct Communication).
  • Unicast communication between a participant (e.g., participant WTRU) and the FL server (e.g., the central FL server) may be prevented, and an amount of network resources across RAN and CN may be saved.
  • the Master e.g., local FL server
  • the device that acts as the local FL server may be determined.
  • the device that initiates the process may become the local server/aggregator (e.g., by default).
  • the device may be selected and configured by the AS.
  • an election process may be performed among the group members.
  • a device may calculate an indicator value using the weighted sum of the FL- related capabilities of the device (e.g., decentralized model aggregation) and resource availability (e.g., memory (e.g., memory capacity), computing power (e.g., CPU capacity), etc.) and may exchange the value during the discovery and group forming process.
  • the device with the highest value (e.g., of resource availability) may become the local server/aggregator.
  • TA/AOI Tracking Area
  • a local FL server may indicate the possibility of accepting further participants; if the local FL server does not accept further participants, the participants may select other local FL servers.
  • Events may cause a WTRU to initiate a ProSe discovery procedure reported by the network.
  • the network may predict that a source WTRU or a group of WTRUs may enter a TA/AOI with poor cellular connectivity. The prediction may be signaled to the WTRU via the AMF (e.g., via NAS signaling).
  • the AMF may receive prediction information from an NWDAF instance of the core network (e.g., 5GC).
  • the network may predict that WTRU connectivity may be poor and/or lost in X ms due to a WTRU’s mobility.
  • a source WTRU may initiate a discovery procedure to find other WTRUs in the proximity of the source WTRU to change its mode of operation from directly connecting to the central FL server via cellular to connecting to a local FL server (i.e. , connecting to a Master WTRU).
  • the network may provide (e.g., may be able to provide) a list of WTRUs with registered capabilities (e.g., capable of GPU processing with a memory capacity, storage capacity, and network capacity/ability) to a source WTRU in a particular TA/AOI.
  • the network may be able to provide a Group ID associated with a group of WTRUs with certain capabilities.
  • the network may provide a Group ID for a set of WTRUs in a TA/AOI that may execute heavy processing tasks or a Group ID for a set of WTRUs in a TA/AOI that may be capable of transmitting data with a high data rate, e.g., to act as a relay (e.g., WTRU-to-WTRU or WTRU-to-Network relaying).
  • the network may be aware of WTRUs in the TA/AOI, which may or may not be able to assist a WTRU in FL operations.
  • the source WTRU may initiate a ProSe discovery procedure (e.g., with a ProSe App Code and a Group ID) to find a WTRU or a group of WTRUs in proximity (e.g., of the source WTRU) for assisting with FL operations.
  • a ProSe discovery procedure e.g., with a ProSe App Code and a Group ID
  • a source WTRU may ask the network (e.g., PCF) to provide a list of WTRUs or group I D(s) associated with a certain WTRU’s capabilities in a TA/AOI of the source WTRU.
  • a source WTRU may initiate a ProSe group member discovery procedure to find WTRUs restricted to the group(s) in proximity (e.g., of the source WTRU).
  • a WTRU may send multiple Group Member Discovery Announcement messages (e.g., Model A) if the WTRU belongs to more than one discovery group.
  • a group ID may be associated with a set of WTRUs.
  • Groupl may include a set of WTRUs with adequate network and computational resources. WTRUs in Groupl may help other WTRUs in proximity in model averaging and/or other functionalities (i.e., acting as a local FL server).
  • Group2 may include a set of WTRUs with adequate network resource capability. WTRUs in Group2 may help other WTRUs in relaying FL data to/from the network.
  • Group3 may include a set of WTRUs with adequate computational resources, such as the number of GPUs and CPUs. WTRUs in this group may help other WTRUs in processing tasks (e.g., of the other WTRUs).
  • Group4 may include a set of WTRUs with adequate network and computational capability that may be stationary.
  • Group5 may include a set of WTRUs with good network and computational capability, and they may be mobile.
  • GroupX may include one or more of the combinations described herein or other parameters.
  • Events may cause a WTRU to initiate a ProSe discovery procedure reported by the WTRU.
  • a WTRU may predict that the connectivity of the WTRU to a cellular network may be intermittent due to user mobility, interferences, etc.
  • the source WTRU may deliver training results to the central FL servers within a time window.
  • a WTRU may initiate a discovery procedure to find other WTRUs in proximity (e.g., of the WTRU) to act as a relay for transmitting the training results of the source to the AS.
  • a source WTRU may predict that the source WTRU may not complete an ongoing training session (e.g., due to a lack of battery power).
  • the WTRU may initiate a ProSe discovery technique to find another WTRU nearby to help the source WTRU to complete a training session and upload the training results to the central FL server.
  • the source WTRU may offload its FL-related data to the target WTRU (e.g., so that the target WTRU may finish the training).
  • a WTRU may detect that the WTRU does not have enough data records in a training dataset, and a model training may not reach a stable point.
  • the WTRU may initiate a ProSe discovery technique to find another WTRU in proximity to get a new dataset.
  • the target WTRU may be not in a source WTRU proximity, the source WTRU may interact with the target WTRU (e.g., via a WTRU-to-WTRU relay).
  • a WTRU may predict that the computational resources of the WTRU, such as GPU/CPU, may be less available in the next X ms, and the WTRU may not be able to allocate the required processing resources to the FL training to continue.
  • the WTRU may initiate a ProSe discovery procedure to find a WTRU in its proximity with computational availability to handover the training metadata (e.g., model construction, model configuration, model weights, dataset, etc.), and the target WTRU may continue the training and upload the training to the FL server (e.g., centralized FL server) after completion.
  • the WTRU may use a particular Group ID associated with devices with computational availability during a discovery procedure.
  • a WTRU may interact with the network to get the requested (e.g., required) list of WTRUs, Group IDs, ProSe App Code, ProSe Query Code, etc. for a particular TA/AOI before initiating a ProSe discovery.
  • the WTRU may find another WTRU or a set of capable WTRUs with less signaling overhead.
  • the AC/AS may notify the WTRU that the WTRU may initiate a ProSe discovery procedure to find other WTRUs in proximity for a reason (e.g., downloading a new dataset, offloading computations, etc.).
  • the AC/AS or the network may provide information regarding group IDs and/or a list of WTRUs, etc., to the WTRU, which may be used in a discovery procedure.
  • WTRUs may be configured to announce the availability of their resource to nearby WTRUs periodically (e.g., every X seconds) via a ProSe discovery technique (e.g., Model A).
  • WTRUs with a particular group I D(s) and/or ProSe App Code may be configured to announce their resource availability to nearby WTRUs according to a specific reporting configuration.
  • a WTRU may send resource availability (e.g., of the WTRU) to another WTRU upon request via a ProSe discovery procedure.
  • a source WTRU may have received resource information of other (e.g., target) WTRUs in the proximity of the source WTRU (e.g., or TA/AOl) from the network (e.g., if WTRUs are configured to report to the network the resource availability information), but the source WTRU may still initiate a ProSe discovery procedure to get the latest resource availability reporting from those target WTRUs).
  • Target WTRUs may be capable of performing specific operations (e.g., as indicated by the network, e.g., via a ProSe App Code), and at the time of discovery, the Target WTRUs may not have enough resources to perform FL operations. For example, WTRUs lacking resource availability may not respond to a discovery message. In examples, WTRUs with a lack of resource availability may respond with an indication to help the source WTRU, e.g., by indicating an absolute/relative time when the WTRUs with the lack of resource availability may have more resource availability or by providing a list of other WTRUs in proximity (e.g., the proximity of the WTRUs with the lack of resource availability) which are not in the proximity of the source WTRU, etc.
  • specific operations e.g., as indicated by the network, e.g., via a ProSe App Code
  • the Target WTRUs may not have enough resources to perform FL operations.
  • WTRUs lacking resource availability may not respond to a
  • a WTRU may be configured to initiate an announcement based on at least the following example configurations: periodically: may be based on a time interval (e.g., every 10 seconds); may be event-based; may be based on (e.g., a set of) predefined conditions (e.g., when WTRU is stationary, when battery power is full, when WTRU may be not active, etc.); may be policy-based (e.g., selection policy based); may be based on (e.g., a set of) rules ordered by precedence (e.g., an event may cause a WTRU to initiate a discovery procedure irrespective of the fact that the WTRU may have been configured to announce resource availability periodically).
  • a time interval e.g., every 10 seconds
  • event-based may be based on (e.g., a set of) predefined conditions (e.g., when WTRU is stationary, when battery power is full, when WTRU may be not active, etc.); may be policy-based (e
  • resource availability reporting may include information regarding a WTRU’s computational resources (e.g., the available battery power (e.g., battery capacity), the number of GPUs (e.g., GPU capacity), and CPUs (e.g., CPU capacity) with an indication of processing speed, memory size (e.g., memory capacity), and storage (e.g., storage capacity) with an indication of speed).
  • computational resources e.g., the available battery power (e.g., battery capacity), the number of GPUs (e.g., GPU capacity), and CPUs (e.g., CPU capacity) with an indication of processing speed, memory size (e.g., memory capacity), and storage (e.g., storage capacity) with an indication of speed).
  • resource availability reporting may include a WTRU’s network resources and conditions such as radio condition, available bandwidth in UL/DL, and PHY layer measurements (e.g., RSRP, SNIR, etc.).
  • WTRU network resources and conditions such as radio condition, available bandwidth in UL/DL, and PHY layer measurements (e.g., RSRP, SNIR, etc.).
  • Resource availability reporting may include the number of connections the WTRU may handle simultaneously.
  • a WTRU may be configured by a set of thresholds defined according to computational and network availability. For example, when a WTRU may have NX amount of network capacity, CX amount of computational resource (GPU/CPU), and PX amount of power (battery life), the WTRU may support an N number of participants.
  • the configuration may include a number of parameters.
  • resource availability reporting may include information regarding available access technologies at the WTRU.
  • resource availability reporting may include latency information between the source WTRU and other destinations (e.g., the AS). The latency information between a pair of WTRUs may be included in the resource availability reporting. Bidirectional interactions may be requested (e.g., required) between two WTRUs (e.g., with the ProSe discovery procedure Model B). In examples, the latency between a WTRU and the network (e.g., gNB or UPF) may be included. In examples, resource availability reporting may include information regarding a buffer status (e.g., queueing delay).
  • a buffer status e.g., queueing delay
  • a category of elements in the resource availability reporting may follow a scoring system or bit coding (e.g., a scoring system to indicate computational resources and/or a scoring system to indicate network resources, etc.).
  • the signaling overhead of the resource availability reporting message may be minimized during a discovery procedure.
  • resource availability reporting may include elements described herein (e.g., resource availability reporting may not be limited to the examples described herein).
  • the WTRU may receive resource availability reporting configuration.
  • the WTRU may be configured to receive the resource availability configuration from the network (e.g., PCF), e.g., via a NAS message.
  • the network may receive resource availability configuration from the AS/AF, which may be tailored for FL applications.
  • the AC running at the WTRU may provide resource availability configurations to the WTRU.
  • the AC may receive the resource availability configuration from the AS.
  • Resource availability reporting may be configured by the WTRU vendor and validated by the network or AC/AS.
  • the resource availability reporting configuration may be dynamically updated by the network or AC (e.g., via AS).
  • the WTRU may be configured to send FL capability reporting with an efficient encoding scheme.
  • FL capability may be reported during a ProSe discovery procedure as part of Application Layer information (metadata).
  • FL capability reporting may be encoded into a certain number of bitstreams or byte streams where a bit corresponds to a particular FL capability, which may be associated with the application metadata during a ProSe discovery or link establishment procedure.
  • Table 2 includes example bitstreams.
  • Multiple byte streams or bitstreams with different sizes may be configured at WTRUs to signal these application layer capabilities efferently during a ProSe discovery procedure, or during a ProSe direct link establishment procedure.
  • the WTRU may receive the WTRU selection configuration/policy for FL operations.
  • the WTRU may be configured to receive (e.g., in message, such as a first message) a selection policy for FL from the network (e.g., a network node, such as a PCF) via a message (e.g., a NAS message).
  • the network may receive the configuration from the AS/AF.
  • the AC running at the WTRU may provide the selection policies to the WTRU.
  • the selection policy may be configured by the WTRU vendor and validated by the network or AS.
  • a WTRU selection policy may be (e.g., dynamically) updated by the network or AC (e.g., via AS).
  • a policy may be or may comprise a selection policy.
  • Examples may include a modified ProSe direct discovery procedure to support FL operations.
  • Fig. 7 illustrates an example discovery procedure (e.g., an example discovery procedure with Model B) for FL operations.
  • the discoverer WTRU may send a second message, such as a solicitation message (e.g., to one or more discoveree WTRUs, such as a candidate WTRU).
  • a solicitation message e.g., to one or more discoveree WTRUs, such as a candidate WTRU.
  • the discoverer WTRU and the WTRU may be used interchangeably, and a discoveree WTRU and a candidate WTRU may be used interchangeably.
  • the solicitation message (e.g., a request message) may include a type of discovery message (e.g., FL Discovery Msg1 , ProSe query code, security protection element, Group ID, Resource Availability Request (e.g., a number of desired GPU and CPU (e.g., GPU and CPU capacity), desired battery level (e.g., battery capacity), desired storage capacity, etc.) and an FL Capability Request (e.g., application metadata) by a discoveree WTRU including model aggregation, member selection, number of training sessions requested (e.g., required), and/or global model distribution.
  • the solicitation message may be based on the selection configuration/policy for FL.
  • At 2 at least one discoveree WTRU from the one or more discoveree WTRUs that matches the solicitation message may respond to the discoverer WTRU with a third message, such as a response message (e.g., the WTRU may receive the third message from at least one candidate WTRU).
  • the third message may indicate an FL capability and a resource availability based on the request.
  • an FL Capability Report e.g., application metadata
  • the discoverer WTRU may determine a target WTRU from among the at least one candidate WTRU (e.g., the discoverer WTRU may select a target WTRU from the at least one candidate WTRU) according to a policy (e.g., the resource availability, such as the resource availability report, and the FL capability, such as the FL metadata report).
  • the policy may be a selection policy.
  • a WTRU may be configured with the policy by the network (e.g., PCF). Determining the target WTRU from the one or more candidate WTRUs based on the FL capability and the resource availability may include the WTRU determining that the FL capability satisfies a threshold associated with the FL capability request.
  • Determining the target WTRU from the one or more candidate WTRUs based on the FL capability and the resource availability may include determining that the characteristic satisfies a threshold associated with the resource availability request.
  • the discoverer WTRU may send to the target WTRU a direct communication request message to initiate a unicast layer-2 link establishment procedure (e.g., the discoverer WTRU may execute an FL operation with the target WTRU).
  • the direct communication request message may include source user information, target user information, ProSe service information, security information, etc.
  • a wireless transmit/receive unit may receive, from a network node, a first message including a selection policy for federated learning (FL).
  • the WTRU may send to one or more candidate WTRUs, a second message.
  • the second message may indicate a request.
  • the request may be based on the selection policy for FL.
  • the WTRU may receive a third message from at least one candidate WTRU.
  • the at least one candidate WTRU may be from the one or more candidate WTRUs.
  • the third message may indicate an FL capability and a resource availability based on the request.
  • the WTRU may determine a target WTRU from the at least one candidate WTRU based on the FL capability and the resource availability.
  • the WTRU may execute an FL operation with the target WTRU.
  • the request may include a resource availability request.
  • the resource availability request may include at least one of a GPU capacity, a CPU capacity, a battery capacity, or a storage capacity.
  • the resource availability may indicate a characteristic of a resource associated with the at least one candidate WTRU.
  • the characteristic may include at least one of a GPU capacity, a CPU capacity, a battery level, a storage capacity, a memory capacity, or a queue delay of the at least one candidate WTRU.
  • the WTRU may determine that the characteristic satisfies a threshold associated with the resource availability request.
  • the request may include an FL capability request, and the FL capability request may include at least one of a model aggregation, a member selection, a number of training sessions, or a global model distribution.
  • the FL capability may include at least one of a model aggregation, a model transfer, a member selection, or a number of maximum training cycles.
  • the WTRU may determine that the FL capability satisfies a threshold associated with the FL capability request.
  • the network node may include a policy control function (PCF).
  • the first message may be a Non- Access Stratum (NAS) message.
  • NAS Non- Access Stratum
  • a WTRU may improve the performance of federated learning via sidelink communications.
  • the WTRU may send a solicitation message to a plurality of relay WTRUs.
  • the solicitation message may include one or more of a resource availability request and a capability request.
  • the WTRU may receive a plurality of response messages from a (e.g., each relay) relay WTRU of the plurality of relay WTRUs.
  • a response message of the plurality of response messages may include at least one of a resource availability report associated with the resource availability request or a capability report associated with the capability request.
  • the WTRU may select a preferred relay WTRU from the plurality of relay WTRUs based on the plurality of response messages.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Artificial Intelligence (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des systèmes, des procédés et des instrumentalités peuvent être associés à la modification de la performance d'un apprentissage fédéré (FL) par l'intermédiaire de communications de liaison latérale (SL). Une unité d'émission/réception sans fil (WTRU) peut recevoir, en provenance d'un nœud de réseau, un premier message comprenant une politique de sélection pour un apprentissage fédéré (FL). La WTRU peut envoyer à une ou plusieurs WTRU candidates, un deuxième message. Le deuxième message peut indiquer une demande. La demande peut reposer sur la politique de sélection pour FL. La WTRU peut recevoir un troisième message provenant d'au moins une WTRU candidate. La ou les WTRU candidates peuvent provenir de la ou des WTRU candidates. Le troisième message peut indiquer une capacité FL et une disponibilité de ressource sur la base de la demande. La WTRU peut déterminer une WTRU cible à partir de la ou des WTRU candidates sur la base de la capacité FL et de la disponibilité de ressources. La WTRU peut exécuter une opération FL avec la WTRU cible.
PCT/US2023/036792 2022-11-03 2023-11-03 Système et procédés pour améliorer les performances d'un apprentissage fédéré par l'intermédiaire de communications de liaison latérale WO2024097408A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263422285P 2022-11-03 2022-11-03
US63/422,285 2022-11-03

Publications (1)

Publication Number Publication Date
WO2024097408A1 true WO2024097408A1 (fr) 2024-05-10

Family

ID=89119281

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/036792 WO2024097408A1 (fr) 2022-11-03 2023-11-03 Système et procédés pour améliorer les performances d'un apprentissage fédéré par l'intermédiaire de communications de liaison latérale

Country Status (1)

Country Link
WO (1) WO2024097408A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022060748A1 (fr) * 2020-09-18 2022-03-24 Google Llc Apprentissage fédéré d'ensemble de coordination d'équipement d'utilisateur pour réseaux neuronaux profonds
WO2022076863A1 (fr) * 2020-10-09 2022-04-14 Qualcomm Incorporated Rapport de capacité d'équipement utilisateur (ue) pour des applications d'apprentissage automatique
WO2022164599A1 (fr) * 2021-01-28 2022-08-04 Qualcomm Incorporated Apprentissage fédéré à support de liaison latérale pour l'apprentissage d'un composant d'apprentissage automatique

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022060748A1 (fr) * 2020-09-18 2022-03-24 Google Llc Apprentissage fédéré d'ensemble de coordination d'équipement d'utilisateur pour réseaux neuronaux profonds
WO2022076863A1 (fr) * 2020-10-09 2022-04-14 Qualcomm Incorporated Rapport de capacité d'équipement utilisateur (ue) pour des applications d'apprentissage automatique
WO2022164599A1 (fr) * 2021-01-28 2022-08-04 Qualcomm Incorporated Apprentissage fédéré à support de liaison latérale pour l'apprentissage d'un composant d'apprentissage automatique

Similar Documents

Publication Publication Date Title
US20230035965A1 (en) Methods and devices to determine the quality of service mechanisms for vehicle-to-everything mobile device communications
US11665730B2 (en) Relay for wireless communication system
EP4075871A1 (fr) Relocalisation de plan d'utilisateur
US20220150754A1 (en) Congestion control procedures for pc5 communications
EP3881509B1 (fr) Activation d'une communication de réseau non public
WO2020033562A1 (fr) Procédés et appareils de synchronisation dans un système sans fil
EP4038847A1 (fr) Procédés et appareils de transmission et de réception de données dans un nouveau système radio
US20220360967A1 (en) Method and apparatus for prose peer discovery
EP4154471A1 (fr) Procédé de commutation de mode de distribution de service de diffusion générale /diffusion groupée multimédia (mbms)
WO2024097408A1 (fr) Système et procédés pour améliorer les performances d'un apprentissage fédéré par l'intermédiaire de communications de liaison latérale
US20240196184A1 (en) Discovery and interoperation of constrained devices with mec platform deployed in mnos edge computing infrastructure
US20230308840A1 (en) Multicast-broadcast services support for network relay
WO2023192303A1 (fr) Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
WO2023147032A1 (fr) Surveillance et rapport de performance pour prendre en charge une opération aiml
WO2023192299A1 (fr) Procédés, appareil et systèmes pour fournir des informations à une wtru par l'intermédiaire d'un plan de commande ou d'un plan d'utilisateur
WO2022221321A1 (fr) Découverte et interfonctionnement de dispositifs contraints avec une plateforme mec déployée dans une infrastructure informatique de périphérie mnos
WO2023059888A1 (fr) Acheminement de trafic de diffusion/multidiffusion pour terminaux distribués
WO2022261098A1 (fr) Procédés d'exportation de services générés au niveau d'applications de calcul en périphérie à accès multiple contraint (cmec) à calcul en périphérie à accès multiple de périphérie (emec)
WO2024102975A1 (fr) Procédés de diffusion et de découverte d'aiml dans un réseau wlan
WO2024097983A1 (fr) Amélioration de découverte et de connexion pc5 pour ai/ml sur pc5
WO2024035797A1 (fr) Retrait initié par wtru à partir d'une opération d'apprentissage fédéré
WO2023086761A1 (fr) Procédés et appareils permettant d'activer une mise à l'échelle de calcul de périphérie reposant sur une unité d'émission/réception sans fil (wtru)
WO2024097324A1 (fr) Sélection de support radio dynamique associée à des opérations ai/ml
WO2024035629A1 (fr) Autorisation d'une fonction d'application pour gestion de politique
WO2024097333A1 (fr) Modification de règles de flux de qos