WTRU-initiated withdrawal from federated learning operations

Abstract

Methods and apparatus for initiating withdrawal from federated learning operations are provided herein. A method implemented in a wireless transmit-receive unit may include: receiving a routing policy including a background data transmission (BDT) policy; and determining that the WTRU cannot meet the requirements of the BDT policy and indicating that the WTRU cannot meet the requirements of the BDT policy. The indication may be by sending a status report; transmitting a mobility registration, the mobility registration not including network slice selection assistance information for an application associated with the BDT policy; releasing a protocol data unit session associated with the BDT policy; or signaling, by the application layer, an application function associated with the BDT policy.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 396,488, filed on August 9, 2022, the contents of which are incorporated herein by reference. Background Art

[0003] A WTRU operating in a fifth generation (5G) communication system may participate in federated learning operations. The WTRU may operate in a communication system having a radio access network (RAN) with a 5G radio access technology (RAT) or an evolved universal mobile telecommunications system (UMTS) terrestrial radio access (E-UTRA), and it is connected to a NextGen core network (CN). The access control and mobility management function (AMF) may provide the following functionality to the system: registration management, connection management, reachability management, and / or mobility management. The session management function (SMF) may provide the following functionality to the system: session management (including session establishment, modification, and release), WTRU IP address allocation, and / or UP function selection and control. The user plane function (UPF) may provide the following functionality to the system: packet routing and forwarding, packet inspection, and / or traffic usage reporting. Summary of the invention

[0004] A method and apparatus for initiating a withdrawal from a federated learning operation is provided herein. A method implemented in a WTRU may include: receiving a routing policy including a background data transfer (BDT) policy; determining that the WTRU cannot meet the requirements of the BDT policy; indicating that the WTRU cannot meet the requirements of the BDT policy by one of the following: sending a status report; sending a mobility registration that does not include network slice selection assistance information for an application associated with the BDT policy; releasing a protocol data unit session associated with the BDT policy; or signaling, by an application layer, an application function associated with the BDT policy.

[0005] In yet another aspect, the requirement of the BDT policy is a requirement to provide data within a time frame set by the BDT policy. In yet another aspect, the determination that the BDT policy requirement cannot be met is based on the detection of a change in the quality of service. In yet another aspect, the determination that the BDT policy requirement cannot be met is based on power consumption. In yet another aspect, the status report may include the reason why the WTRU cannot meet the requirement of the BDT policy. In yet another aspect, the reason may be related to a change in the service area of ​​the WTRU. In yet another aspect, the reason may be related to a user changing the configuration of the WTRU. In yet another aspect, the WTRU may receive an updated routing selection policy after indicating that the WTRU cannot meet the requirement of the BDT policy. In yet another aspect, a WTRU may be configured to perform any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0007] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0008] Figure 1B is an example of an embodiment in which Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within an illustrated communication system;

[0009] Figure 1C is an example of an embodiment in which Figure 1A A system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0010] Figure 1D is an example of an embodiment in which Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0011] Figure 2 is a signaling flow diagram illustrating an exemplary procedure for WTRU status reporting for URSP policy update.

[0012] Figure 3 is a signaling flow diagram illustrating an exemplary process for providing a WTRU status update based on URSP rules when requesting to establish or modify a PDU session;

[0013] Figure 4 is a signaling flow diagram illustrating an exemplary process for providing a status update of a WTRU for network slice availability;

[0014] Figure 5 is a signaling flow diagram illustrating exposure of an event of slice availability by the AMF to the WTRU;

[0015] Figure 6 is a signaling flow diagram illustrating an exemplary process for providing WTRU status updates via a PDU session;

[0016] Figure 7 is a signaling flow diagram illustrating an exemplary process for performing a WTRU status update via the application layer; and

[0017] Figure 8 is a signaling flow diagram illustrating an exemplary procedure for providing FL analysis assistance through WTRU status update reporting. DETAILED DESCRIPTION

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

[0019] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, 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 device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), consumer electronic devices, and devices operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0020] The communication system 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, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0021] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSC), radio network controllers (RNC), and relay nodes. Base station 114a and / or base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, 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 send and / or receive signals in a desired spatial direction.

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

[0023] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), that may use Wideband CDMA (WCDMA) to establish the air interface 116. 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 ​​Uplink (UL) Packet Access (HSUPA).

[0024] 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology (such as NR radio access) that may establish the air interface 116 using NR.

[0026] 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 together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

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

[0028] Figure 1A The base station 114b in may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial venues, homes, vehicles, campuses, industrial facilities, sky corridors (e.g., for use by drones), and roads. 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 a femtocell. As Figure 1A As shown, the base station 114 b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not need to access the Internet 110 via the CN 106.

[0029] The RAN 104 may be in communication with the CN 106, 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the specification, the CN 106 may be 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. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0030] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication 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 or a different RAT.

[0031] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.

[0032] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, 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. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0033] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), state machine, etc. The processor 118 may perform signal decoding, 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0035] Although the transmit / receive element 122 Figure 1B Although depicted as a single element in the figure, 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.

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

[0037] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a 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, and a secure digital (SD) memory card, among others. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0038] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control 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, etc.

[0039] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0040] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules 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 electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game player modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices and activity trackers, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and a humidity sensor, etc.

[0041] 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 specific subframes for both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0042] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ 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.

[0043] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0044] Each of the evolved Node 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, and scheduling of users in the UL and / or DL, among other things. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0045] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0046] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, and selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c. 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.

[0047] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an 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 the user plane during an inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

[0049] 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 be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0050] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0051] In a representative embodiment, the other network 112 may be a WLAN.

[0052] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and destined for the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and destined for a target outside the BSS may be transmitted to the AP to be delivered to the corresponding target. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the target STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the target STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0053] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each 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.

[0054] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels) to form a 40 MHz wide channel.

[0055] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and the data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0056] 802.11af and 802.11ah support operating modes below 1GHz. 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 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0057] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum 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 (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, all available bands may be considered busy even if most of the available bands remain idle.

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

[0059] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ NR 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.

[0060] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 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, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send 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, gNB 180a may transmit multiple component carriers to 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, 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).

[0061] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, 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 the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths over time).

[0062] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0063] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b and routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0064] Figure 1D The CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0065] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, and mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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, and services for MTC access. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 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.

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

[0067] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the 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 DL packets, and providing mobility anchoring, etc.

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

[0069] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0071] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0072] Table 1 is a list of acronyms that may be used in this article:

[0073]

[0074]

[0075]

[0076] Table 1: Abbreviations

[0077] Network slicing considerations are described herein. Restrictions may be imposed on simultaneous registrations of network slices. The WTRU may support subscription-based restrictions on simultaneous registrations of network slices. When the AMF provides the WTRU with the configured NSSAI and the WTRU indicates that it supports this feature, the AMF may provide the WTRU with NSSRG information related to the S-NSSAI of the Home Public Land Mobile Network (HPLMN), which may be included in the mapping information of the configured NSSAI. When the WTRU receives the NSSRG value in the network slice configuration information, the WTRU may include the S-NSSAI that shares the common NSSRG in the requested NSSAI based on the received information.

[0078] When the network changes the NSSRG information in the subscriber record, the network may update the WTRU with the new NSSRG information, thereby providing the WTRU with slice configuration information through the WTRU configuration update procedure. These updates may bring changes to the configured NSSAI and the allowed NSSAI.

[0079] Slice specific admission control is described herein. The Network Slice Admission Control (NSAC) feature may enable an operator to manage and control the number of registered WTRUs per network slice and / or the number of PDU sessions per network slice for network slices configured to support NSAC. The Network Slice Admission Control Function (NSACF) may be responsible for monitoring and controlling the WTRUs and PDU sessions admitted to a specific network slice.

[0080] As a WTRU moves across a network, and the network is configured to have multiple service areas handled by a particular NSACF, it may be possible that a WTRU that was previously admitted in a service area controlled by, for example, NSACF-A, may not be admitted in an adjacent service area where slice admission control is now handled by another NSACF (e.g., NSACF-B).

[0081] Network data analysis statistics and forecasts are described herein. The network data analysis feature may provide statistics and / or forecasts based on specific requests from entities consuming the information. Some examples of the types of information that this feature can provide include statistics and forecasts regarding network node status information, network node resource usage, communications in an area of ​​interest, and mobility performance. The targets of such analysis may include a single WTRU, a group of WTRUs, or any WTRU that may be in an area of ​​interest. In addition, network data analysis may be provided to characterize network function load and / or network slice load, as well as data analysis that may provide forecasts and statistics regarding WTRU mobility, expected WTRU behavior, and even observed service experience at multiple levels, including network slices, service experience for specific applications, or service experience for specific applications on specific access types (RAT types or frequencies).

[0082] Future background data transfers are described herein. The process for future background data transfers may enable negotiation between the AF (Application Function) and the network (i.e., PCF) regarding a transmission strategy for future background data transfers. The Application Service Provider (ASP) may negotiate with the network a time window and related conditions for future background data transfers (BDT), including information about the network regions where the BDT may occur, and optionally an aggregate bit rate. The ASP may accomplish this through the AF communicating directly via the PCF (Policy Control Function) or through the NEF (Network Exposure Function). This negotiation may occur before the WTRU establishes a PDU session.

[0083] When the AF wants to apply the BDT policy to future sessions, it may provide the background data transfer reference ID and the external identifier (i.e., GPSI) or external group to the network. The PCF servicing the WTRU for which the request is intended may retrieve the BDT policy or may receive notifications by subscribing to WTRU application data changes. The PCF then communicates the relevant BDT policy to the WTRU by creating a UE / WTRU Routing Policy (URSP) and communicating it to the WTRU.

[0084] When the PCF needs to update the URSP rules related to the BDT policy, the PCF may trigger the WTRU configuration update procedure.The WTRU may use routing validation criteria to determine whether a PDU session should be established.

[0085] When a PDU session is established, the PCF serving the PDU session may use the BDT reference ID in the WTRU's PDU session policy control subscription information to retrieve the corresponding BDT policy and related information from the UDR, and derive the policy charging and control (PCC) rules for BDT.

[0086] The PCF may subscribe to analysis of network performance from the NWDAF for regions of interest and time windows for BDT policies. For example, if the PCF realizes that network performance has degraded below some threshold, the PCF may attempt to renegotiate the affected BDT policies with an application function (AF) that accepts BDT policy renegotiation.

[0087] Various problems solved by the proposed embodiments are described herein. Various existing solutions suggest time-dependent configuration of traffic descriptors. These solutions may rely on network-driven configuration of URSP rules that the WTRU should follow. A problem with such solutions may be that there is no standardized way for the WTRU to determine whether the user wants to participate in a session configured by the network or to signal the network whether it can do so. In some cases, it may not be possible for the WTRU to participate in future scheduled data sessions, such as when background traffic is being transmitted or traffic with different QoS is being transmitted at different times.

[0088] Some of the issues addressed herein may relate to mobility across service areas or tracking areas (TAs) with NSSRG restrictions. For example, the network may update the NSSRG information when the WTRU changes service areas and this triggers a mobility registration. If this is the case, it may be possible that a network slice associated with, for example, an application federated learning operation is removed from the allowed NSSAI as it would conflict with other network slices indicated in the NSSRG information. This may prevent the WTRU from reporting any local training for an application FL operation where the network slice is running and should therefore be excluded from the FL membership.

[0089] Some of the issues addressed herein may relate to mobility across service areas with congested networks. For example, as a WTRU moves across service areas handled by different NSACFs, the network may update admission control information for network slices. Therefore, it is possible that a WTRU that was previously admitted in a service area controlled by NSACF-A may no longer be admitted when it moves to a service area that is now controlled by, for example, NSACF-B. In this case, it is possible that a network slice associated with, for example, an application federated learning operation cannot be used in the next service area. This may prevent the WTRU from reporting any local training for an application FL operation where the network slice is running and should therefore be excluded from FL membership.

[0090] It should be noted that similar issues may occur when the WTRU changes RA (Registration Area) and the new RA no longer supports the network slice on which the AIML operation is running. In addition, service area restrictions may also impose limitations.

[0091] Some of the issues addressed herein may relate to situations where a WTRU moves to a service area with less than optimal conditions. If the WTRU is moving towards a service area where performance may be degraded, network congestion may be experienced or the observed service experience may be less than optimal, and it may be disadvantageous to include the WTRU in FL operation while the WTRU remains in a service area with less than optimal conditions. The network may provide statistics and predictions about specific network conditions, however this information may not be available to the WTRU.

[0092] Some of the issues addressed herein may relate to resource utilization for AIML operations of a WTRU. In some cases, the network and the AIML AF may collaborate for better AIML operations, and the network may manage network resources to ensure proper AIML operations according to the AIML AF, and may also involve the WTRU by using URSP updates to potential members of the FL operations. When a WTRU cannot perform as expected, there may be no way to notify the network, however, which may result in a waste of reserved resources.

[0093] Some of the issues addressed herein may involve limitations on WTRU battery power. When there are limitations on WTRU battery power, the system may need to optimize battery life by shutting down certain services in the WTRU using some criteria (e.g., high power consumption applications, non-essential applications, low priority applications, etc.). This may result in the denial or withdrawal of certain services that the WTRU is involved in, and the release of any corresponding network resources.

[0094] Some of the issues addressed herein may involve user configuration changes. While using an application in a WTRU, a user may want to change the WTRU configuration based on the user's preferences, and this may result in shutting down or dropping the services involved and releasing any corresponding network resources.

[0095] Various solutions are provided herein to address at least the above-mentioned issues.

[0096] If the WTRU detects any of the situations generally described above, then based on the time window allocated by the AF for local model migration / training reporting, the WTRU may determine whether it wants / is able to report the interim training results within the allocated time window. In an embodiment, the WTRU may communicate its intention to the 5G network, for example, through a WTRU status report for a URSP policy, through a mobility registration that does not include an S-NSSAI that applies AIML operations running, by releasing AIML related PDU sessions, or by having the AF contact the network.

[0097] Figure 2 is a signaling flow diagram illustrating an exemplary procedure for WTRU status reporting for URSP policy update. Figure 2 AF 10, PCF 12, SMF 14, AMF 16, RAN 18 and WTRU 20 are shown. At 210 of the exemplary process, the policy settings for the application negotiated by the PCF 12 and AF 10 may be requested by the AF 10, based on the request of the AF. If necessary, the PCF 12 may also establish a BDT policy for future background data transmissions of the application and reserve resources to ensure appropriate communication services for the application requested by the AF with a set of WTRUs. For the BDT policy, the PCF 12 may update the URSP rules with verification criteria (e.g., time window and location) for each WTRU included as a candidate WTRU for each AF-requested policy setting.

[0098] At 212, after updating with the URSP rule, the WTRU 20 may determine that the WTRU may not continue future PDU sessions in the time window or position indicated by the validation criteria, or that the WTRU should be dropped from the service of the AF 10, for any reason including the above. At 214, after deciding that the WTRU cannot continue future PDU sessions, the WTRU may transmit a WTRU status report for WTRU policy to the AMF 16, which includes an indication that the WTRU cannot follow a certain URSP rule. The WTRU may include relevant URSP rule information (such as the URSP rule ID that the WTRU is indicated to be unable to follow) and relevant service information (such as an application identifier, traffic descriptor, or other information that may identify the service associated with the indicated URSP rule). The WTRU may include a reason for the indication, for example, it may be suboptimal for the reasons generally stated in the above paragraphs. Such an indication of the reason why the WTRU withdraws from following the URSP rule may assist the network in determining or inferring the reason and the best course of action to take. At 216, when the AMF 16 receives the status report of the WTRU 20 to the PCF, the AMF 16 may forward the status report of the WTRU to the PCF 12.

[0099] At 218, after receiving the status report of the WTRU, the PCF 12 may identify relevant policies, such as BDT policies, session management related policies, from the included relevant service information. The PCF 12 may directly notify the AF 10 when the AF is trusted, or the PCF 12 may notify the AF 10 via the NEF when the AF is not trusted because it is outside the 5G network, regarding applications that the WTRU should be dropped from the service traffic. For example, in FL service, the WTRU may be dropped from the WTRU candidate list for FL service. Alternatively or additionally, the AF may require modification of the BDT policy, such as modification of the validation rules.

[0100] At 220, if the SMF 14 is configured for session management information (e.g., QoS rule related information) related to the WTRU's application, the PCF 12 may update the SM policy to release the QoS rules related to the WTRU's application. Alternatively or additionally, if the PCF 12 receives a modification of the BDT policy, the PCF 12 may update the SM policy according to the received modification request.

[0101] At 222, based on the WTRU's status report, the PCF 12 may update the URSP rules for the WTRU, such as removing the URSP rules for the application, updating the URSP rules for the application, such as modifying the validation rules such as the time condition and the location condition. The PCF 12 may transmit the WTRU policy update to the WTRU 20 via the AMF 16.

[0102] This document describes a solution involving updating URSP rules with optimal operating conditions. Additionally or alternatively, the 5G CN may provide the URSP with updated conditions for optimal operation of the WTRU.

[0103] The updated conditions for optimal operation may be recommended values ​​for providing optimal operation to the WTRU. This may include recommended WTRU battery levels, channel conditions such as minimum SINR, minimum CINR or other values, recommended locations and timing (i.e., to avoid traffic under overload or poor traffic conditions), etc.

[0104] When the WTRU determines that the WTRU's environment does not meet the optimal operating conditions for the WTRU policy, the WTRU may transmit a WTRU status report for the WTRU policy according to one or more of the above steps.

[0105] The 5GCN may manage the session management policy with the best operating condition in association with the URSP with the updated best operating condition. When the 5GCN receives the PDU session establishment of the WTRU, the 5GCN may check whether the session management policy has the best operating condition.

[0106] When the requested PDU session does not meet the optimal operating conditions of the relevant session management policy, the 5GCN may reject the PDU session request that serves other PDU sessions with priority or better conditions. The decision from the 5GCN may depend on various circumstances.

[0107] This document describes a solution involving updates to the URSP that are triggered based on a policy control request.

[0108] Figure 3 is a signaling flow diagram illustrating an exemplary process for providing WTRU status updates based on URSP rules when requesting to establish or modify a PDU session. At 310, based on the request of the AF 10, the PCF 12 and the AF 10 may have negotiated policy settings for the application requested by the AF 10. If necessary, the PCF 12 may establish policies that apply within a time window, such as future application-specific traffic that requires reserving resources to guarantee appropriate communication services for the application requested by the AF 10 with a set of WTRUs.

[0109] At 312, after the WTRU has been updated with the URSP rules, and based on one or more conditions specified herein, the WTRU 20 may determine to trigger the establishment of a new PDU session or a PDU session modification request, indicating that for certain policies and at a specific time window, location, or AN type, the WTRU may not meet certain WTRU (session or mobility management) policies, and therefore the WTRU may not be suitable for services managed at the AF 10. At 314, after deciding what policies cannot be met during a specific time window, time, or AN type, the WTRU 10 may include a status report in the PDU session establishment or modification request to the SMF. At 316, if the policy control trigger is met, the SMF 14 may initiate a policy association modification procedure. In this case, the WTRU notification that certain URSP rules cannot be met may be a condition for satisfying the policy control request trigger. At 318, the PCF 12 may report the policy change based on the AF 10 subscription to such events. At 320, based on the SMF input, the PCF 12 may provide the SMF with updated policy information. At 322, the SMF may include the new policy information in a PDU Session Setup Accept / Modify Command message.

[0110] This document describes a solution involving WTRU mobility registration updates with a network slicing configuration.

[0111] Figure 4 is a signaling flow diagram illustrating an exemplary process for providing a status update of a WTRU for network slice availability. At 410, based on the request of the AF 10, the 5G network may have negotiated with the AF relevant policy settings and network slice configuration for the application requested by the AF 10. For example, when the WTRU 20 is registered in FL operation, the WTRU may be configured on a network slice for exchanging traffic for FL operation.

[0112] At 412, depending on WTRU mobility or other environmental changes, the WTRU 20 may detect that the WTRU will be available or unavailable to use the network slice for the AF 10, which may be configured as a result of the previous steps described above. For example, when the WTRU 20 is configured with a network slice for FL operation and other network slices belonging to a different NSSRG, the WTRU 20 may move to another RA where a network slice belonging to a different NSSRG from FL operation is available. For example, the WTRU 20 may newly enter an area where the SNSSAI for FL operation becomes unavailable.

[0113] At 414, after detecting the update to the availability of FL operation, the WTRU 20 may transmit a mobility registration request with the expected S-NSSAI to the AMF 16. For example, when FL operation is not available within the WTRU, the WTRU may transmit an S-NSSAI that does not include the NSSAI for FL operation as the requested S-NSSAI.

[0114] At 416, after receiving the mobility registration request, when the AMF 16 detects that the FL operation has become available or unavailable at the WTRU due to an update of the network slice unavailability, the AMF 16 may notify the NWDAF 22, PCF (not shown), NEF (not shown), or other NFs (not shown) that were previously subscribed to the notification of the WTRU's state change at the AMF 16 that the WTRU's network slice environment has changed and the network slice for FL operation has become available or unavailable. For example, on behalf of AF10, the NEF may request a notification service about the WTRU's slice availability from the AMF. In this case, after receiving the mobility registration, the AMF may notify the NEF of the update of the WTRU's slice availability, and the NEF may notify the AF, for example, as follows.

[0115] At 418, when the NWDAF 22 or other NF receives a report of a WTRU status change or a slice availability update of the WTRU, for FL operation, it may notify the AF 10 directly when the AF is trusted, or notify the AF 10 via the NEF when the AF is not trusted because it is outside the 5G network that the WTRU becomes available or unavailable for FL operation.

[0116] This document describes solutions related to event exposure of AMF for slice usage of WTRU.

[0117] When a WTRU requests a change of allowed network slice or a change to a different NSSRG, the AMF may notify the AF or other NFs that are subscribed to notifications about slice availability for the WTRU, as part of the AMF's event exposure service.

[0118] The slice availability of the WTRU may be determined based on whether the allowed S-NSSAI of the WTRU has changed, whether specific S-NSSAI information is included or excluded in the allowed NSSAI of the WTRU, and / or information of the allowed NSSAI in the WTRU.

[0119] Figure 55 is a signaling flow diagram illustrating an event exposure of slice availability of the WTRU 20 by the AMF 16. In one step of the exemplary process, the NF1 or NEF 24 may transmit a request to the AMF 16 to subscribe 510 to a set of event IDs including event IDs for slice availability updates of the WTRU in the AMF. When subscribing to the notification service, the NF1 or NEF 24 may request to be notified when a specific S-NSSAI value or group of S-NSSAI values ​​becomes available or unavailable (i.e., when those values ​​are included or excluded in the allowed NSSAI of the WTRU). NFs other than NF1 / NEF (e.g., such as Figure 5 NF2 26) shown may be requested as a destination for the notification service in a subscription request from NF1 / NEF and may be used by the service provider NF (in Figure 5 At 512, the AMF may confirm the execution of the subscription. At 514, the WTRU 20 may change the requested NSSAI of the WTRU via the registration process, and the AMF 16 may allow those requested NSSAIs to the allowed NSSAIs taking into account the subscription of the WTRU, the availability of the NF supporting the requested NSSAI, and / or other parameters. At 516, when the AMF 16 detects that the slice availability of the WTRU has changed, the AMF may transmit an event report to the notification endpoint, which may include whether the allowed NSSAI of the WTRU has changed, whether specific S-NSSAI information is included or excluded in the allowed NSSAI of the WTRU, and / or information of the allowed NSSAI in the WTRU. When the notification endpoint is different from the subscribed NF (i.e., NF1 or NEF), as shown in 518, the AMF 16 may transmit an event report to NF2 26, which may include an indication of whether the WTRU's allowed NSSAI has changed, whether specific S-NSSAI information is included or excluded in the WTRU's allowed NSSAI, and / or information about the allowed NSSAI in the WTRU.

[0120] This article describes a solution related to the release of AIML related PDU sessions.

[0121] Figure 6610 is a signaling flow diagram illustrating an exemplary process for providing WTRU status updates via a PDU session. When the WTRU 20 is registered in a service for FL operation 610, the WTRU 20 may be configured with network slice information, DNN information, or other session-related subscription information for FL operation, and the WTRU may establish a PDU session for FL operation. At 612, for any reason, the WTRU 20 may not maintain the PDU session for FL operation, or the WTRU wants to drop from FL operation. For example, this may occur when the WTRU has moved in a service area with less than optimal conditions, or when the WTRU encounters battery problems and may need to drop services that consume a high degree of battery power. At 614, after detecting an environmental change, the WTRU 20 may transmit a PDU session release request or a PDU session modification request to the SMF 14 to release the QoS flow for FL operation. The WTRU may include a release cause in the PDU session release request. For example, the WTRU 20 may include "withdraw from FL operation" as a cause to notify that the WTRU has withdrawn from FL operation. For example, the WTRU may include an indication of the above situation as a cause for the PDU session release to indicate a change in the WTRU's environment. At 616, when the SMF 14 receives the PDU session release or the PDU session modification, the SMF 14 may contact the PCF 12 to update the SM policy association modification to discard the PDU session or QoS flow related to the FL operation. At 618, when an indication that the WTRU is unavailable for FL operation or withdrawn from FL operation is received as a cause for the PDU session release or based solely on receiving the PDU session release, the PCF 12 or NWDAF (not shown) notified by the PCF of the WTRU's unavailability may involve notifying the AF 10 directly of the FL operation when the AF is trusted, or notifying the AF 10 via the NEF when the AF is not trusted because it is outside the 5G network that the WTRU is no longer available or the WTRU wants to withdraw from the FL operation. At 620, the PCF 12 may respond to the SMF 14 with an SM policy association modification response. At 622, the SMF 14 may respond to the WTRU in response to the PDU session release response or the PDU session modification response and may include results regarding the PDU session or QoS flow for FL operation.

[0122] This document describes a solution involving providing notifications to AIML services via the application layer.

[0123] Figure 7is a signaling flow chart illustrating an exemplary process of performing a WTRU status update via the application layer. At 710, upon request by AF 10, PCF 12 and AF 10 may negotiate policy settings for applications requested by AF. If necessary, PCF may also establish a BDT policy for future background data transmissions of the application and reserve resources to ensure appropriate communication services between the application requested by AF 10 and the WTRU 20 group. For the BDT policy, the PCF may update URSP rules with validation criteria (e.g., time window and location) for each WTRU included as a candidate WTRU for each AF-requested policy setting. When the AF's service will be consumed at a network slice, the slice information will be configured at the WTRU during the registration or WTRU configuration update process. At 712, at some point, due to any reason including the circumstances described herein, WTRU 10 may determine that it cannot maintain service from AF 10 or that the WTRU may need to withdraw or suspend service. At 714, WTRU 20 may notify the WTRU of a status update of the WTRU served by AF 10 via application layer signaling. At 716, upon receiving a service status update for the WTRU, the AF 10 may negotiate directly with the PCF 12 or other NF in the 5GCN when the AF 10 is trusted, or negotiate with the PCF 12 or other NF in the 5GCN via the NEF when the AF is not trusted because it is outside the 5G network, to update the service policy configuration. For example, when a BDT policy has been established for the AF's service, the AF may update the WTRU list for the BDT policy so as to remove the WTRU from the list. For example, when a network slice is used for the AF's service, since the WTRU no longer uses the AF's service, the WTRU may be configured to remove the network slice for the AF's service. At 720, after receiving a request from the AF 10, the PCF 12 or other NF in the 5GCN may respond and update its policy or configuration with the SMF 14. At 722, based on the service policy configuration update, other NFs may be notified of the update. For example, when there is an ongoing PDU session for the AF's service, the SMF may be notified to release the PDU session. In some examples, the AMF 16, UDM and / or NSSF (not shown) may be notified of network slice information to be removed from the allowed NW slices and / or configured NW slices.

[0124] This document describes a solution involving providing federated learning analytics assistance through WTRU status updates.

[0125] Figure 8 is a signaling flow diagram illustrating an exemplary procedure for providing FL analysis assistance through WTRU status update reporting.

[0126] At 810, the AF 10 may request analysis information for potential FL members (e.g., a candidate WTRU list or WTRU group). The AF may request NWDAF specific analysis information for each WTRU 20, such as WTRU mobility, WTRU latency, or UL / DL data rate, etc., or the AF may directly request NWDAF 28 aggregate analysis information, such as aggregate bit rate, average latency of the group, etc., when the AF is trusted, or request NWDAF 28 aggregate analysis information via NEF when the AF is not trusted because it is outside the 5G network. Alternatively or additionally, the AF may communicate with a dedicated NF (e.g., an AI / ML assisting NF) to directly request assistance information for AI / ML operations of potential FL members when the AF is trusted, or request assistance information for AI / ML operations of potential FL members via NEF when the AF is not trusted because it is outside the 5G network. After receiving the request from the AF, the dedicated NF may request NWDAF analysis information or aggregate analysis information for each WTRU.

[0127] At 812, based on the request, the NWDAF 22 may communicate with a NF such as the UDM 17, PCF, AMF, SMF, or other NF to collect status information about the candidate WTRUs regarding the requested analysis information. For example, the NWDAF 28 may contact the UDM 17 (as shown) to check the WTRU 20 user consent settings regarding the analysis information or other information of the WTRU to the AF. For example, at 814, the NWDAF 28 may contact the PCF 12 to collect QoS or PDU session statistics about the candidate WTRUs. For example, the NWDAF may contact the AMF to check the reachability or other location or mobility related information of the WTRU. Based on the responses from each NF, the NWDAF may construct the analysis information of the FL members.

[0128] At 818, the NWDAF 28 may request a status report of the WTRU from the WTRU 20 via the AMF 16. The status report of the WTRU may include the slice availability of the WTRU (e.g., a list of allowed NSSAIs), the resource status of the WTRU (such as battery power consumption), and / or the performance data of the WTRU (such as data rate, error rate, latency, etc.). At 820, the WTRU may respond to the NWDAF 28 with the status report of the WTRU via the AMF 16. The NWDAF may compose analysis information of FL members based on the status report of the WTRU and the response data from each NF. Based on the status report of the WTRU, the NWDAF may determine whether the WTRU is available or is an appropriate entity for FL operation of the AF. At 822, after composing the analysis data of the FL members, the NWDAF 28 may respond to the AF 10 with the analysis data.

[0129] Alternatively or additionally (eg, as part of one or more of the above steps), the AF may subscribe to a notification service for any updates to analytical information for potential FL members.

[0130] Upon receiving the analysis information notification update request, the NWDAF may update the subscription notification service to each NF or the WTRU itself for the status of each WTRU that is a potential FL member. The subscription may be performed as the same process or an additional process during one or more steps generally described above.

[0131] After successfully subscribing to the notification service, when an update of the WTRU status is detected from the WTRU itself, the AMF, the SMF, the PCF, and / or other NFs to which the NWDAF subscribes notifications, each NF may notify the WTRU of the status update. For example, similar to one or more solutions described herein, at 828, the WTRU may report the WTRU's environmental change to the NWDAF 28 via the AMF 16. For example, similar to one or more solutions described herein, at 824, when the AMF receives a mobility registration for WTRU mobility or for a slice update, the AMF 16 may report the WTRU's status update to the NWDAF 28.

[0132] After receiving updated reports from the WTRU itself, AMF, PCF 12 (shown here at 826) and / or other NFs, at 830, the NWDAF 28 may notify the AF 10 of the status update of the WTRU 20 directly when the AF is trusted, or notify the AF 10 of the status update of the WTRU 20 via the NEF when the AF is not trusted because it is outside the 5G network.

[0133] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, WTRU, terminal, base station, RNC, or any host computer.

Claims

1. A method implemented in a wireless transmit receive unit (WTRU), the method comprising: receiving a routing policy including a background data transfer (BDT) policy; determining that the WTRU cannot satisfy requirements of the BDT policy; The WTRU is indicated as being unable to satisfy the requirement of the BDT policy by one of: Send status reports; sending a mobility registration that does not include network slice selection assistance information for an application associated with the BDT policy; Releasing the protocol data unit session associated with the BDT policy; or The application functionality associated with the BDT policy is signaled by the application layer. 2 . The method of claim 1 , wherein the requirement of the BDT policy is a requirement to provide data within a time frame set by the BDT policy.

3. The method of claim 1 or 2, wherein the determination that the BDT policy requirement cannot be met is based on the detection of a change in quality of service. The method of claim 1 , wherein the determination that the BDT policy requirement cannot be met is based on power consumption.

5. The method according to any one of claims 1 to 4, wherein the status report includes the reason why the WTRU cannot meet the requirements of the BDT policy.

6. The method of claim 5, wherein the cause is related to a change in a service area of ​​the WTRU.

7. The method of claim 5, wherein the reason is related to a user changing a configuration of the WTRU.

8. The method of any one of claims 1 to 7, further comprising receiving an updated routing policy after indicating that the WTRU cannot meet the requirements of the BDT policy.

9. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit configured to: receiving a routing policy including a background data transfer (BDT) policy; determining that the WTRU cannot satisfy requirements of the BDT policy; The WTRU is indicated as being unable to satisfy the requirement of the BDT policy by one of: Send status reports; sending a mobility registration that does not include network slice selection assistance information for an application associated with the BDT policy; Releasing the protocol data unit session associated with the BDT policy; or The application functionality associated with the BDT policy is signaled by the application layer.

10. The WTRU of claim 9, wherein the requirement of the BDT policy is a requirement to provide data within a time frame set by the BDT policy.

11. The WTRU of claim 9 or 10, wherein the determination that the BDT policy requirement cannot be met is based on detection of a change in quality of service.

12. The WTRU of claim 9 or 10, wherein the determination that the BDT policy requirement cannot be met is based on power consumption.

13. The WTRU of any one of claims 9 to 12, wherein the status report includes a reason why the WTRU cannot meet the requirement of the BDT policy.

14. The WTRU of claim 13, wherein the cause is related to a change in a service area of ​​the WTRU.

15. The WTRU of claim 13, wherein the reason is related to a user changing a configuration of the WTRU.

16. The WTRU of any one of claims 9 to 15, wherein the WTRU is further configured to receive an updated routing policy subsequent to an indication that the WTRU cannot meet the requirements of the BDT policy.

Images