Access control of network relays related to ai / ML services by wtru

Abstract

Systems, methods, and instrumentalities are provided for access control of a wireless transmit / receive unit (WTRU) to network relays related to artificial intelligence / machine learning (AI / ML) services. The first WTRU may receive a first message including a service authorization from a first network node. The service authorization may include a first priority value associated with the first WTRU. The first WTRU may receive a second message from a second network node. The second message may include a supported service indication and a second priority value associated with the second WTRU. The first WTRU may determine a second WTRU based on the supported service indication and a second priority value. Based on the determination, the first WTRU may establish a direct connection with the second WTRU.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 444,395, filed February 9, 2023, the contents of which are incorporated herein by reference. Background Art

[0003] Mobile communications using wireless communications continue to evolve. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G New Radio (NR). The previous generation (legacy) mobile communications RAT may be, for example, fourth generation (4G) long term evolution (LTE). Wireless communication devices may establish communications with other devices and data networks, for example, via an access network such as a radio access network (RAN). Summary of the Invention

[0004] Systems, methods, and means are provided for controlling access of a wireless transmit / receive unit (WTRU) to a network relay associated with an artificial intelligence / machine learning (AI / ML) service. A first WTRU may receive a first message from a first network node including a service authorization. The service authorization may include a first priority value associated with the first WTRU. The first WTRU may receive a second message from a second network node. The second message may include a supported service indication and a second priority value associated with the second WTRU. The first WTRU may determine that the second priority value is lower than the first priority value. The first WTRU may determine, based on the supported service indication and the determination that the second priority value is lower than the first priority value, that the second WTRU supports the authorized service associated with the service authorization. Based on the determination, the first WTRU may establish a direct connection with the second WTRU.

[0005] The first WTRU may establish a radio resource control (RRC) connection with the second network node. The first WTRU may send a third message including a NAS message to the third network node. The first WTRU may send a fourth message to the fourth network node. The fourth message may indicate a session establishment procedure.

[0006] The first network node may include a policy control function (PCF). The second network node may be associated with a next generation radio access network (NG-RAN). The third network node may include an access management function (AMF) associated with the first WTRU. The fourth network node may include a user plane function (UPF) associated with the first WTRU.

[0007] The first message may include a relay service code (RSC) associated with the service. The first priority value may be associated with the RSC. The second priority value may be associated with the active role of the second WTRU. The first WTRU may include a remote WTRU. The second WTRU may include a relay WTRU. The first network node may include a policy control function (PCF). BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Furthermore, like reference numerals designate like elements throughout the drawings, and wherein:

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

[0010] Figure 1B is a diagram according to one embodiment that can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system as shown in FIG.

[0011] Figure 1C is a diagram according to one embodiment that can be Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) for use within a communication system as shown in FIG.

[0012] Figure 1D is a diagram according to one embodiment that can be Figure 1A A system diagram of an additional example RAN and an additional example CN used within the communication system shown in FIG;

[0013] Figure 2 An example network is illustrated.

[0014] Figure 3 An example connection setup (eg, including a Layer 2 WTRU to NW relay with a priority value) is illustrated.

[0015] Figure 4 An example connection setup (eg, including a Layer 3 WTRU to NW relay with a priority value) is illustrated. DETAILED DESCRIPTION

[0016] Figure 1A1 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 by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), and the like.

[0017] like Figure 1A As shown in FIG, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit 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 smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

[0018] 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 / 115, 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 eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, 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.

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

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

[0021] More specifically, as described 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, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High Speed ​​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).

[0022] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0023] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0024] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement both LTE radio access and NR radio access, e.g., using dual connectivity (DC) principles. Thus, the air interface utilized by the 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., eNBs and gNBs).

[0025] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology 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.

[0026] Figure 1A The base station 114b in may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (LAN) (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. Figure 1A As shown in FIG, base station 114b may be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

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

[0028] 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 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) from the TCP / IP internet protocol suite. The networks 112 may include wired 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 / 113 or a different RAT.

[0029] 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 WTRU 102c shown in FIG. 1 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.

[0030] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B , 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 supply 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0031] 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) circuit, 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. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

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

[0033] Despite Figure 1B 102 as a single element, the WTRU 102 may include any number of TX / RX elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more TX / RX elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0034] 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 described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0035] 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. Furthermore, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as a server or a home computer (not shown).

[0036] 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, and the like.

[0037] 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 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 obtain location information by any suitable location-determination method while remaining consistent with an embodiment.

[0038] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an 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, electronic game player modules, internet browsers, virtual reality / augmented reality / extended reality (VR / AR / XR) devices, activity trackers, and the like. Peripheral devices 138 may include one or more sensors, which 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 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.

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

[0040] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As mentioned above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

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

[0042] 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, user scheduling in the UL and / or DL, and the like. Figure 1C As shown in FIG, eNode-Bs 160a, 160b, and 160c can communicate with each other via an X2 interface.

[0043] Figure 1C The CN 106 shown in FIG may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is 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.

[0044] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for translating between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0045] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

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

[0047] 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 serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0048] Even though the WTRU Figure 1A-Figure 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may (eg, temporarily or permanently) employ a wired communication interface with a communication network.

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

[0050] 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 access to or be connected to a distributed system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS destined for a STA may reach the AP and may be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. For example, traffic between STAs within a BSS may be sent through the AP, where the source STA may send traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between a source STA and a destination STA (e.g., directly between the source STA and the destination STA) using 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 (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode is sometimes referred to herein as an "ad hoc" communication mode.

[0051] When using 802.11ac infrastructure operation mode or similar operation mode, the AP can transmit beacons on a fixed channel (such as the primary channel). The primary channel can be a fixed width (e.g., a wide bandwidth of 20 MHz) or a width dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, such as in an 802.11 system, carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented. For CSMA / CA, STAs (e.g., each STA), including the AP, can sense the primary channel. If the primary channel is sensed / detected by a specific STA and / or is determined to be busy, the specific STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0052] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0053] Very High Throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining adjacent 20MHz channels. A 160MHz channel can be formed by combining 8 adjacent 20MHz channels, or by combining two non-adjacent 80MHz channels - this can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can separate the data into two streams. Each stream can be subjected to inverse fast Fourier transform (IFFT) processing and time domain processing separately. These streams can be mapped onto two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the media access control (MAC).

[0054] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carriers in 802.11af and 802.11ah are reduced relative to the operating modes used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support metered type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities (e.g., limited capabilities), including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0055] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as a primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for a STA that supports (e.g., only supports) a 1 MHz mode (e.g., an MTC-type device), the primary channel can be 1 MHz wide, 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 can depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which only supports the 1 MHz operating mode) transmitting to the AP, the entire available frequency band can be considered busy, even if most of the frequency band remains idle and can be used.

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

[0057] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As described above, the RAN 113 may employ 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.

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

[0059] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different 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 a different number of OFDM symbols and / or lasting for a different length of absolute time).

[0060] 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 without also accessing another RAN (e.g., such as the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed frequency 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 DC principles 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 serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for the serving WTRUs 102a, 102b, 102c.

[0061] 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, user scheduling in UL and / or DL, network slicing support, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to a user plane function (UPF) 184a, 184b, routing of control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown in , gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0062] Figure 1DThe CN 115 shown in FIG may include at least one AMF 182 a, 182 b, at least one UPF 184 a, 184 b, at least one session management function (SMF) 183 a, 183 b, and possibly a data network (DN) 185 a, 185 b. While each of the aforementioned elements is 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.

[0063] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, and the like. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service being 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, services for machine type communication (MTC) access, and the like. The AMF 162 may provide a control plane function for translating between the RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

[0065] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

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

[0067] Given that Figure 1A-Figure 1D and Figure 1A-Figure 1D As described herein, one or more or all of the functionality described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other 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 functionality described herein. For example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functionality.

[0068] Emulated devices can be designed to perform one or more tests on other devices in a lab environment and / or in a carrier network environment. For example, one or more emulated devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulated devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulated device can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communications.

[0069] One or more emulated devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulated devices can be used in test scenarios in a test lab and / or in a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. The one or more emulated devices can be test devices. The emulated devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas).

[0070] As used herein, the term "rule" may be used interchangeably with the term "packet detection rule (PDR)." The identifier may be associated with one or more of a Quality of Service (QoS) Flow Identifier (QFI) or a Service Set Identifier (SSID). A WTRU-to-NW relay may be associated with a relay WTRU.

[0071] Features described herein may be associated with access control for WTRUs (e.g., remote WTRU to a network relay (e.g., AI / ML related) (e.g., relay WTRU)). WTRU to NW relay discovery and connection setup procedures may be described herein. WTRU capability update and protocol data unit (PDU) session establishment procedures may be described herein.

[0072] As described herein, WTRU to NW may be referred to as UE to NW, and vice versa. For example, a UE to NW WTRU may be a WTRU to NW WTRU, a UE to NW relay WTRU may be a WTRU to NW relay WTRU, etc.

[0073] As described herein, an example WTRU-to-NW relay may include a computational resource of a relay WTRU (which may be referred to as a WTRU-to-NW relay) and a priority of each Relay Service Code (RSC) in a WTRU-to-NW Relay Discovery message (which may be referred to as a WTRU-to-NW Relay). A remote WTRU may be assigned a priority value of the RSC to which it is authorized to access. Based on the priority value, the WTRU-to-NW Relay may perform admission control for the remote WTRU for each RSC and may perform load balancing. When performing a connection setup procedure, the core network (e.g., 5GC) and the WTRU-to-NW Relay (e.g., UE-to-NW Relay) may verify the priority value of the remote WTRU.

[0074] Figure 2 An example reference model of a network (e.g., 5G / next generation network) is illustrated.

[0075] The radio access network (RAN) may be based on a RAT (e.g., 5G RAT) or evolved E-UTRA connected to a core network (e.g., a next generation core network).

[0076] The access control and mobility management function (AMF) may include one or more of the following functions: registration management, connection management, reachability management, mobility management, etc.

[0077] The session management function (SMF) may include one or more of the following functions: session management (including session establishment, modification, and release), WTRU IP address allocation, selection and control of UP functions, etc.

[0078] The User Plane Function (UPF) may include one or more of the following functions: packet routing and forwarding, packet inspection, service usage reporting, etc.

[0079] Features described herein may be associated with AI / ML. Support for AI / ML operations may be observed (e.g., how to support AI / ML split operations). The performance of AI / ML applications (including split calculations and model transfer examples) may be modified when an estimate of network conditions may be provided to the AI / ML application before / during operation. Examples may relate to how performance data and / or performance analysis data may be monitored between the WTRU and the core network and how the results may be exposed to the WTRU or AF so that the WTRU or AF can initiate AI / ML split operations.

[0080] For example, when the uplink end-to-end (E2E) latency is below 2ms and the data rate exceeds 1.08Gbps, the AI / ML image recognition work can be split and this information can be provided to the WTRU or AF to initiate the operation.

[0081] In an example, a determination may be made as to how to enhance AI / ML operations using device-to-device (D2D) connectivity. For example, a decision may be made to split (e.g., decide to split) AI / ML operations between a WTRU or an application server (AS) such that, for example, a WTRU (e.g., WTRU-A) is responsible for computations for layers 1-15, and an AS is responsible for computations for layers 16-24. When PC5 connectivity is above a threshold (e.g., PC5 connectivity is good and / or sufficiently good), the WTRU (e.g., WTRU-A) may offload AI / ML operations to another nearby WTRU (e.g., WTRU-B). In an example, WTRU-B may be responsible for computations for layers 5-15, and WTRU-A may be responsible for computations for layers 1-4. This may be desirable and beneficial for WTRU-A because it may utilize less power in WTRU-A and provide better AI / ML services, such as reduced latency. AI / ML operations using multiple WTRUs in conjunction with PC5 connectivity may be referred to as PC5-based AI / ML operations. AI / ML operations using application servers in a network may be referred to as server-based AI / ML operations.

[0082] Federated Learning (FL) may be a machine learning service. Synchronous FL (sync-FL) may use (e.g., is associated with) the (e.g., strict) communication quality of the WTRU in order to deliver (e.g., all) intermediate results to the FL server in a timely manner. Sync-FL may be susceptible to unpredictable radio conditions and WTRU capability differences. Asynchronous FL (async-FL) may be used (e.g., to address limitations of sync-FL). Async-FL may allow the WTRU to report its results when it is ready (e.g., without strict time constraints), and the FL server may refresh the model without waiting for (e.g., all) intermediate results to be collected. Sync-FL and asynchronous-FL may each have advantages and disadvantages, as depicted in Table 1.

[0083] Table 1: Comparison of synchronous-FL and asynchronous-FL

[0084]

[0085]

[0086] When the remote WTRU is outside the direct coverage of the serving NG-RAN, WTRU-to-NW relay may be involved for delivery of AI / ML services.

[0087] Based on the service requirements and characteristics of the AI / ML service, the relay's operations may provide (e.g., optimized) resource management.

[0088] In an example, for synchronous FL, the WTRUs involved in the FL may be requested to report their results in a pre-allocated time slot. This condition (e.g., pre-allocated time slot) may impose (e.g., strict) QoS requirements to support it. The WTRU-to-NW relay may attempt to provide a connection that meets the QoS requirements.

[0089] In an example, for asynchronous FL, the WTRUs may not (e.g., not every WTRU) report results simultaneously. When the WTRU is available, it may report results and download the updated model. For model download, the WTRU may establish a connection with high bandwidth for model download. High computational power supported by the relay may be used (e.g., required).

[0090] From the perspective of the remote WTRU, the serving remote WTRU may select a WTRU-to-NW relay that can provide services that reflect the characteristics of the service while meeting the QoS requirements. The relay may support multiple services (e.g., asynchronous FL and synchronous FL), and its QoS characteristics may change temporarily.

[0091] In case of multiple relays, support for multiple services with (e.g., different) QoS capabilities may be available, and the remote WTRU may select a (e.g., appropriate) relay for AI / ML operations.

[0092] With multiple relay services for AI / ML available (e.g., relay service for synchronous FL and relay service for asynchronous FL), the relay and core networks can control access and resource utilization for optimal QoS and throughput.

[0093] The features described herein may be associated with access control operations between a WTRU to a NW relay and a remote WTRU (eg, by enforcing a priority value for each relay service). The priority value may be verified during connection setup between a relay WTRU and a remote WTRU via the core network.

[0094] WTRU-to-network (e.g., UE-to-network) relay discovery may be based on the capabilities of the relay. For example, for Proximity Services (ProSe) WTRU-to-network relay discovery, the WTRU-to-network relay may broadcast an announcement including a Relay Service Code (RSC) to indicate the connectivity services provided by the ProSe WTRU-to-network relay to the core network.

[0095] To use the discovery method, a remote WTRU may send a WTRU-to-network relay discovery request message including the expected RSC. Upon receiving the discovery request message, a WTRU-to-network relay that supports RSC may send a WTRU-to-network delayed discovery response message including the RSC and relay information.

[0096] When the WTRU-to-network relay supports relay services for carrying traffic related to AI / ML operations (e.g., synchronous FL and asynchronous FL), an RSC may be assigned to the WTRU-to-network relay to indicate support for AI / ML operations. (e.g., different) RSCs may be assigned for AI / ML services (e.g., an RSC for synchronous FL and an RSC for asynchronous FL may be assigned).

[0097] A WTRU-to-network relay may be assigned an RSC indicating whether the WTRU-to-network relay is capable of supporting specific capabilities, e.g., whether the WTRU-to-network relay is capable of meeting QoS and latency (e.g., latency requirements), without indicating its support for (e.g., specific) application services.

[0098] The remote WTRU may select a WTRU to a NW relay WTRU based on the signal quality between the remote WTRU and the relay WTRU.Good (eg, better) link quality may provide good (eg, better) communication performance.

[0099] For AI / ML services, the selection of a relay WTRU at a remote WTRU may take into account factors other than the link quality between the relay WTRU and the remote WTRU. For example, for asynchronous FL, once the WTRU reports its results, the data (e.g., a large amount of data) of the AI / ML model may be downloaded, and the performance of downloading the data may depend on the computing power and available resources of the relay WTRU.

[0100] To improve relay services for AI / ML, information (e.g., additional information) indicating the capabilities of the WTRU to relay to the network (e.g., available memory and / or computing power) may be delivered to the remote WTRU during discovery (e.g., as examples described herein).

[0101] For example, a relay's capability class may be defined and / or preconfigured. A relay's class value (e.g., a preconfigured class value) may be included in a notification message. For example, a class based on relay capabilities may represent a combination of capabilities (e.g., battery level, available memory, and / or computing power).

[0102] In an example, category one may include the following: battery charge > 80%, available memory > 16 GB, computing power > 8 cores * 1 GHz.

[0103] In an example, category two may include the following: battery charge > 80%, available memory > 12 GB, computing power > 4 cores * 1 GHz. Category three: battery charge > 80%, available memory > 8 GB, computing power > 4 cores * 1 GHz.

[0104] When a remote WTRU discovers and selects a WTRU-to-network relay based on an application, the remote WTRU may select a WTRU-to-network relay based on the capability category of the relay. For example, the remote WTRU may select a relay for asynchronous FL service, and the remote WTRU may select a relay based on the available memory and computing capabilities of the relay rather than based on the signal quality of the link between the relay and the remote WTRU.

[0105] Admission control of the WTRU to the network relay may be based on the WTRU's priority value.

[0106] Unified access control can assign priority values ​​per device category, for example, MPS public safety devices can have a higher priority (e.g., per application or network slice, per access type (e.g., access for mobile originated signaling)) or access for mobile terminated signaling, access for voice calls, or access for delay tolerant services.

[0107] In ProSe, the WTRU-to-NW relay can support multiple relay services, and the remote WTRU can be authorized to access multiple relay services. An access control mechanism that supports multiple services simultaneously can be considered.

[0108] For relay services, supported applications can request (e.g., require) state-based resource control (e.g., state-based differential resource control). Controlling application priority based on their state can improve efficiency. For example, for synchronous FL, there can be a specified time interval to collect model update results. Resources may not be requested (e.g., may not be required) beyond the required time interval.

[0109] As admission control to the WTRU to the network relay, the remote WTRU may be assigned a priority value for each RSC. When the remote WTRU is authorized for multiple relay services, the remote WTRU may be assigned (eg, different) priority values ​​for the RSCs.

[0110] The priority value of a remote WTRU may be assigned by the core network during registration or by the AF and may be updated during operation. Different priority values ​​may be assigned to remote WTRUs based on the application or the role of the remote WTRU at the application. For example, when a relay service is used for AI / ML operations, a volunteer WTRU for AI / ML model distribution may be responsible for forwarding the AI / ML model to WTRUs (e.g., other WTRUs) and may be assigned a higher priority value than other WTRUs.

[0111] During discovery, the WTRU-to-network relay may report allowed priority values ​​based on the RSC. When a remote WTRU attempts to access the WTRU-to-network relay for a given RSC, the remote WTRU may select a WTRU-to-network relay that reports a lower priority value than the one assigned to the remote WTRU as an allowed priority value.

[0112] When a WTRU-to-network relay (e.g., UE-to-network relay) WTRU registers with the core network, the relay WTRU may be authorized to operate as a WTRU-to-network relay. The supported RSCs and allowed priority values ​​may be provided to the relay. When authorized as a WTRU-to-network relay, a (e.g., different) RSC may be configured based on the capabilities of the relay WTRU. For example, when the relay WTRU's computational resources or the relay's capability category is high, the relay WTRU may be assigned an RSC with high computational resources (e.g., an RSC for asynchronous FL).

[0113] Based on the request of the application function or the control of the core network, the allowed priority value of each RSC of each WTRU to network relay can be changed. For example, on asynchronous FL service, training results can be collected and the allowed priority value of the RSC of asynchronous FL can be set to high to reduce service traffic.

[0114] By adjusting the allowed priority value of each RSC, admission control or resource control between relay services can be achieved. For example, if more user traffic from the asynchronous FL is expected within a certain period (e.g., a certain duration), the allowed priority value of the synchronous FL can be lowered, or a higher priority value can be assigned to the relay WTRU of the RSC of the synchronous FL.

[0115] The relay may dynamically adjust the priority level of the RSC (e.g., increase the priority value when busy to limit lower priority remote WTRUs, or decrease the priority value when less busy). If the priority of the remote WTRU does not meet the priority level, the relay may notify the (e.g., current) adjusted priority value during discovery or direct communication rejection so that the remote WTRU can retry (e.g., later). Within the remote WTRUs allowed at the WTRU-to-network relay (e.g., in overload situations), overload control or congestion control in the WTRU-to-network relay may be performed based on the priority value of the WTRU. For example, a connection of a remote WTRU with a lower priority value than another remote WTRU connection may be dropped first.

[0116] If the priority value is reported per RSC during discovery of the relay WTRU to network relay, the remote WTRU's priority value may be included in the connection setup request. The remote WTRU's priority value may be validated by the WTRU to network relay and the core network (e.g., if the remote WTRU's priority value is not a value authorized by the core network or AF). If the remote WTRU's priority value is lower than the allowed priority value of the RSC at the WTRU to network relay, the remote WTRU connection request may be rejected and the remote WTRU's PDU session setup may be rejected.

[0117] Figure 3 A connection setup (eg, with a Layer 2 WTRU to NW relay with a priority value) is illustrated.

[0118] At 1, a ProSe Layer 2 remote WTRU (e.g., a first WTRU, such as a remote WTRU) and a ProSe Layer 2 WTRU to network relay (e.g., a second WTRU, such as a relay WTRU) may independently receive service authorization for ProSe Layer 2 WTRU to network relay operation from the network.

[0119] When a WTRU is authorized as a WTRU-to-NW relay, it may be provided with parameters such as a Relay Service Code (RSC) associated with the service and a priority value for each RSC (e.g., a priority value may be associated with the RSC to control access to the relay (e.g., the parameters may be received in a first message). When the RSC and priority value are provided, a Policy Control Function (PCF) (e.g., a first network node) may provide a default priority value (e.g., a first priority value associated with the remote WTRU) for the RSC (e.g., service authorization) (e.g., in a first message to the remote WTRU) and / or may provide a (e.g., different) priority value for the RSC based on input from the AF. Pre-configured priority values ​​may be used.

[0120] When a WTRU is authorized as a remote WTRU, parameters such as an RSC (Relay Service Code) and a priority value for each RSC may be provided to the WTRU. When the RSC and priority values ​​are provided, the PCF may provide a default priority value for (e.g., different) RSCs, or may provide a priority value for (e.g., each) RSC based on the role of the authorized WTRU in the service or based on input from the AF. Pre-configured priority values ​​may be used.

[0121] If a WTRU is accessing a relay service for a joint AI / ML service, the WTRU may be authorized as a volunteer WTRU for distributing AI / ML models. Based on the WTRU's role as a volunteer WTRU, a higher priority value may be assigned to the relay service supporting the joint AI / ML service.

[0122] When a WTRU is authorized for multiple roles per application, a (e.g., different) priority value may be assigned to (e.g., each) authorized role. When selecting and accessing a WTRU to a NW relay, a priority value (e.g., a second priority value) associated with the (e.g., currently) active role may be used. Whether the WTRU is using the correct priority value may be verified during the connection setup with the WTRU to the NW relay (e.g., PC5).

[0123] At 2, the ProSe Layer 2 remote WTRU and the ProSe Layer 2 WTRU-to-network relay may perform ProSe WTRU-to-network relay discovery and selection.

[0124] When the remote WTRU is informed (e.g., received by the remote WTRU in a second message from the NG-RAN) of the relay's priority value(s) (e.g., the second priority value) and supported service indication during the WTRU-to-NW relay discovery phase (e.g., the remote WTRU may select the WTRU-to-NW relay (e.g., the second WTRU) (e.g., based on the supported service indication and the second priority value associated with the second WTRU). The remote WTRU may determine that the second priority value is lower than the first priority value. The remote WTRU may determine that the second WTRU is the one to which the relay WTRU indicates a lower priority value than the priority value assigned to the WTRU for the RSC of interest (e.g., the second priority value is lower than the first priority value).

[0125] At 3 , the ProSe Layer 2 remote WTRU (eg, the first WTRU) may initiate a one-to-one communication connection (eg, a direct connection) with the selected ProSe Layer 2 WTRU to network relay (eg, the second WTRU) through PC5 .

[0126] During the connection setup procedure, the remote WTRU may be authenticated and authorized by the relay WTRU and the core network.

[0127] The RSC and the remote WTRU's priority value of the RSC may be included in the direct communication request for the WTRU to the NW relay.

[0128] When the remote WTRU's indicated priority value is greater than the relay WTRU's priority value of the RSC, the remote WTRU's request for PC5 connection setup may be allowed.

[0129] The relay WTRU may forward the priority value of the remote WTRU to verify its validity. The NF in the core network (e.g., PCF, UDM or AMF) may verify the validity of the priority value of the remote WTRU.

[0130] During authorization, the relay WTRU may obtain the remote WTRU's priority value from the AMF when CP-based security is used, or from the PKMF when UP-based security is used. Based on the received priority value, the relay WTRU may verify whether the remote WTRU is allowed to access the relay WTRU for RSC.

[0131] When the priority value of the remote WTRU cannot be successfully verified, the relay WTRU may reject the connection setup request from the remote WTRU.

[0132] At 4, the remote WTRU may establish an RRC connection with the same RAN (eg, NG-RAN, such as a second network node) serving the selected ProSe Layer 2 WTRU to network relay.

[0133] To verify the priority of the remote WTRU, the remote WTRU and / or the relay may provide the remote WTRU's priority value to the RAN.

[0134] At 5, the remote WTRU may send a non-access stratum (NAS) message to a serving third network node (e.g., an access management function (AMF)) (e.g., in a third message). The NAS message may be encapsulated in a Uu RRC message sent to the relay via PC5, and the relay may forward the Uu RRC message to the RAN. The RAN may select a serving AMF for the ProSe Layer 2 remote WTRU and forward the NAS message to the WTRU-to-network relay's AMF. To verify the remote WTRU's priority value, the remote WTRU and / or the relay WTRU may provide the remote WTRU's priority value to the AMF.

[0135] At 6, the ProSe Layer 2 remote WTRU may trigger (eg, by sending in a fourth message) a session establishment procedure (eg, a PDU session establishment procedure).

[0136] At 7, data may be transferred between the remote WTRU and a fourth network node (eg, UPF) via the relay and the NG-RAN.

[0137] Figure 4 A connection setup (eg, layer 3 WTRU to NW relay with priority value) is illustrated.

[0138] At 0, a ProSe Layer 3 WTRU to Network Relay may be authorized and provided with parameters for acting as an L3 WTRU to NW Relay. The provided parameters may include an RSC with a priority value. When an RSC and a priority value are provided, the RSC may be provided with (e.g., different) priority values ​​based on input from the AF, and a default priority value may be provided for other RSCs that are not assigned a separate priority value. Pre-configured priority values ​​may be used.

[0139] At 1, a ProSe Layer 3 remote WTRU may be authorized and provided with parameters for acting as a remote WTRU, which may include an RSC with a priority value. When providing the RSC and priority value, a (e.g., different) priority value may be provided for (e.g., each) RSC based on the role of the authorized WTRU in the service or based on input from the AF. A default priority value may be provided for an RSC that is not assigned an individual priority value. Pre-configured priority values ​​may be used.

[0140] When a WTRU is authorized for multiple roles of an application, (e.g., different) priority values ​​may be assigned to (e.g., different) authorized roles. When selecting and accessing a WTRU to a NW relay, the priority value associated with the currently active role may be used. Whether the WTRU is using the correct priority value may be verified during the PC5 connection setup with the WTRU to the NW relay.

[0141] At 2, the ProSe Layer 3 WTRU to network relay may establish a PDU session for the relay. In an example (eg, for IPv6), the ProSe Layer 3 WTRU to network relay may obtain a prefix from the network via a prefix delegation function, which may be an IPv6 prefix.

[0142] At 3, the ProSe Layer 3 remote WTRU may perform discovery of the ProSe Layer 3 WTRU to the network relay.

[0143] When notified of the priority value of a relay during the discovery phase of a WTRU-to-NW relay, a remote WTRU may select a WTRU-to-NW relay that indicates a lower priority value than the assigned priority value of the WTRU of the RSC of interest.

[0144] At 4, the ProSe Layer 3 remote WTRU may select a ProSe Layer 3 WTRU-to-Network Relay and establish a connection for unicast mode communication.

[0145] During the unicast connection setup procedure, the remote WTRU may be authenticated and authorized by the relay WTRU and the core network.

[0146] The RSC and the remote WTRU's priority value of the RSC may be included in the WTRU's direct communication request to the NW relay for verification. When the remote WTRU's indicated priority value is greater than the relay WTRU's priority value of the RSC, the remote WTRU's request for PC5 connection setup may be allowed.

[0147] The relay WTRU may forward the priority value of the remote WTRU to verify the validity. The NF in the core network (e.g., PCF, UDM or AMF) may verify the validity of the priority value of the remote WTRU.

[0148] During authorization, the relay WTRU may obtain the remote WTRU's priority value from the AMF when CP-based security is used, or from the PKMF when UP-based security is used. Based on the received priority value, the relay WTRU may verify whether the remote WTRU is allowed to access the relay WTRU for RSC.

[0149] When the priority value of the remote WTRU cannot be successfully verified, the relay WTRU may reject the connection setup request from the remote WTRU.

[0150] If there is no PDU session associated with the relay service code, or if there is a new PDU session for relaying, the ProSe Layer 3 WTRU to network relay may initiate a (e.g., new) PDU session establishment procedure for relaying before completing the PC5 connection establishment.

[0151] At 5, for IP PDU session type and IP traffic over PC5 reference point, the ProSe Layer 3 remote WTRU may be allocated a (eg, IPv6) prefix or a (eg, IPv4) address.

[0152] The ProSe Layer 3 remote WTRU may provide PC5 QoS information and PC5 QoS rule(s) to the ProSe Layer 3 WTRU-to-network relay using a Layer 2 Link Modification procedure at 6. Based on this input, the relay WTRU may perform the WTRU-requested PDU session modification to set up a new QoS flow or bind traffic to an existing QoS flow.

[0153] At 7, the ProSe Layer 3 WTRU to Network Relay may send a Remote WTRU Report (e.g., Remote User Identifier (ID), Remote WTRU Information) message to the SMF for the PDU session associated with the relay.

[0154] At 8, the remote WTRU may exchange user traffic through the relay WTRU.

[0155] Systems, methods, and means are provided for controlling access of a wireless transmit / receive unit (WTRU) to a network relay associated with an artificial intelligence / machine learning (AI / ML) service. A first WTRU may receive a first message from a first network node including a service authorization. The service authorization may include a first priority value associated with the first WTRU. The first WTRU may receive a second message from a second network node. The second message may include a supported service indication and a second priority value associated with the second WTRU. The first WTRU may determine a second WTRU based on the supported service indication and the second priority value. Based on the determination, the first WTRU may establish a direct connection with the second WTRU.

[0156] The first WTRU may determine that the second priority value is lower than the first priority value. If the second priority value is lower than the first priority value, the first WTRU may determine that the second WTRU is connected. The first WTRU may establish a radio resource control (RRC) connection with the second network node. The first WTRU may send a third message including a NAS message to the third network node. The first WTRU may send a fourth message to the fourth network node. The fourth message may indicate a session establishment procedure.

[0157] The first network node may include a policy control function (PCF). The second network node may be associated with a next generation radio access network (NG-RAN). The third network node may include an access management function (AMF) associated with the first WTRU. The fourth network node may include a user plane function (UPF) associated with the first WTRU.

[0158] The first message may include a relay service code (RSC) associated with the service. The first priority value may be associated with the RSC. The second priority value may be associated with the active role of the second WTRU. The first WTRU may include a remote WTRU. The second WTRU may include a relay WTRU. The first network node may include a policy control function (PCF).

[0159] Systems, methods, and means may be provided for controlling access of a wireless transmit / receive unit (WTRU) to a network relay associated with an artificial intelligence / machine learning (AI / ML) service. A first WTRU may receive a first message from a first network node, and the first message may include a service authorization. The first WTRU may send a second message to a second network node. The second message may include a discovery indication indicating that the WTRU is discovering and selecting a second WTRU. The first WTRU may discover the second WTRU. The first WTRU may select the second WTRU. The first WTRU may establish a connection with the second WTRU. The first WTRU may establish a radio resource control (RRC) connection with the second network node. The first WTRU may send a third message to the second network node. The first WTRU may send a fourth message to a fourth network node. The fourth message may indicate a session establishment process.

[0160] Although the above features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiment, or in various combinations with or without the other features and elements.

[0161] Although the implementations described herein may consider 3GPP specific protocols, it will be understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it will be understood that the solutions described herein are not limited to this scenario and may be applicable to other wireless systems. For example, although the system has been described with reference to 3GPP, 5G and / or NR network layers, the envisioned embodiments extend beyond implementations using specific network layer technologies. Likewise, potential implementations extend to all types of service layer architectures, systems and embodiments. The techniques described herein may be applied independently and / or in combination with other resource configuration techniques.

[0162] The processes described herein may be implemented in a computer program, software, and / or firmware that is incorporated into a computer-readable medium for execution by a computer and / or a processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via a wired and / or wireless connection) and / or 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, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver for use in a WTRU, a terminal, a base station, an RNC, and / or any host computer.

[0163] It should be understood that the entities that perform the processes described herein can be logical entities implemented in the form of software (e.g., computer-executable instructions) stored in the memory of a mobile device, network node, or computer system and executed on a processor of the mobile device, network node, or computer system. That is, these processes can be implemented in the form of software (e.g., computer-executable instructions) stored in the memory of a mobile device and / or network node (such as a node or computer system), which, when executed by the processor of the node, performs the processes in question. It should also be understood that any transmission and reception processes illustrated in the accompanying drawings can be performed by the communication circuitry of the node under the control of the processor of the node and the computer-executable instructions (e.g., software) executed by it.

[0164] The various techniques described herein can be implemented in combination with hardware or software, or in combination with a combination of the two in appropriate circumstances. Therefore, the implementation and device of the subject matter described herein or some aspects or parts thereof can take the form of program code (e.g., instructions) embodied in a tangible medium including any other machine-readable storage medium, wherein, when the program code is loaded into a machine such as a computer and executed by a machine such as a computer, the machine becomes a device for practicing the subject matter described herein. In the case where the program code is stored on a medium, it may be the following: the program code in question is stored on one or more media that jointly perform the action in question, that is, one or more media together contain the code for performing the action, but - in the case where there is more than one single medium - it is not required that any particular part of the code is stored on any particular medium. In the case where the program code is executed on a programmable device, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage element), at least one input device and at least one output device. One or more processes can be implemented or utilized in conjunction with the process described in the subject matter described herein, for example, by using an API, a reusable control, or the like. Such a program is preferably implemented in a high-level process or object-oriented programming language to communicate with a computer system. However, if desired, the program(s) may be implemented in assembly language or machine language. In any case, the language may be a compiled or interpreted language, and combined with hardware implementation.

[0165] Although example embodiments may involve utilizing aspects of the subject matter described herein in the context of one or more stand-alone computing systems, the subject matter described herein is not limited thereto and may be implemented in conjunction with any computing environment, such as a network or distributed computing environment. Further, aspects of the subject matter described herein may be implemented in or across multiple processing chips or devices, and storage may similarly be implemented across multiple devices. Such devices may include personal computers, network servers, handheld devices, supercomputers, or computers integrated into other systems, such as automobiles and aircraft.

[0166] In describing preferred embodiments of the disclosed subject matter, as illustrated in the accompanying drawings, specific terminology is employed for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose.

Claims

1. A first wireless transmit / receive unit (WTRU), comprising: A processor configured to: receiving a first message including a service authorization from a first network node, wherein the service authorization includes a first priority value associated with a first WTRU; receiving a second message from a second network node, the second message including a supported services indication and a second priority value associated with a second WTRU; determining that the second priority value is lower than the first priority value; determining, based on the supported services indication and a determination that the second priority value is lower than the first priority value, that the second WTRU supports the authorized service associated with the service authorization; as well as Based on the determination, a direct connection is established with the second WTRU.

2. The WTRU of claim 1 , wherein the processor is further configured to: establishing a radio resource control (RRC) connection with the second network node; sending a third message including a NAS message to a third network node; and A fourth message is sent to a fourth network node, wherein the fourth message indicates a session establishment procedure.

3. The WTRU of claim 2 , wherein the first network node comprises a policy control function (PCF), wherein the second network node is associated with a next generation radio access network (NG-RAN), wherein the third network node comprises an access management function (AMF) associated with the first WTRU, and wherein the fourth network node comprises a user plane function (UPF) associated with the first WTRU.

4. The WTRU of claim 1 , wherein the first message further comprises a relay service code (RSC) associated with a service, and wherein the first priority value is associated with the RSC.

5. The first WTRU of claim 1 , wherein the second priority value is associated with an active role of the second WTRU.

6. The first WTRU of claim 1 , wherein the first WTRU comprises a remote WTRU, the second WTRU comprises a relay WTRU, and the first network node comprises a policy control function.

7. A method for a first wireless transmit / receive unit (WTRU), comprising: receiving a first message including a service authorization from a first network node, wherein the service authorization includes a first priority value associated with a first WTRU; receiving a second message from a second network node, the second message including a supported services indication and a second priority value associated with a second WTRU; determining that the second priority value is lower than the first priority value; determining, based on the supported services indication and a determination that the second priority value is lower than the first priority value, that the second WTRU supports the authorized service associated with the service authorization; as well as Based on the determination, a direct connection is established with the second WTRU.

8. The method according to claim 7, wherein the method further comprises: establishing a radio resource control (RRC) connection with the second network node; sending a third message including a NAS message to a third network node; and A fourth message is sent to a fourth network node, wherein the fourth message indicates a session establishment procedure.

9. The method of claim 8, wherein the first network node comprises a policy control function (PCF), wherein the second network node is associated with a next generation radio access network (NG-RAN), wherein the third network node comprises an access management function (AMF) associated with the first WTRU, and wherein the fourth network node comprises a user plane function (UPF) associated with the first WTRU.

10. The method of claim 7, wherein the first message further comprises a Relay Service Code (RSC) associated with a service, and wherein the first priority value is associated with the RSC.

11. The method of claim 7, wherein the second priority value is associated with an active role of the second WTRU.

12. The method of claim 7, wherein the first WTRU comprises a remote WTRU, the second WTRU comprises a relay WTRU, and the first network node comprises a policy control function.

Images