Wireless transmit / receive unit assisted communications for ambient internet of things (AIOT) devices

Abstract

A WTRU may be configured to function as an AIoT assistant WTRU. The AIoT assistant WTRU may act as an intermediary between AIoT devices and a network. The AIoT assistant WTRU may handle paging on behalf of one or more AIoT devices using a virtual temporary identifier. The VTMSI may be assigned by the network and may be associated with the one or more AIoT devices. The AIoT assistant WTRU may initiate procedures to perform the exchange of data between the network and the AIoT devices.

Description

WIRELESS TRANSMIT / RECEIVE UNIT ASSISTED COMMUNICATIONS FOR AMBIENT INTERNET OF THINGS (AIoT) DEVICESCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Number 63 / 553,386, filed February 14, 2024, which is hereby incorporated herein by reference in its entirety.BACKGROUND

[0002] An ambient power-enabled internet of things (AIoT) device can harvest energy from the environment, such as wireless radio waves, motion, vibration, piezoelectricity, solar energy, wind power, etc. An AIoT device may not comprise a battery (battery-less). An AIoT device may possess limited energy storage capability via, for example, a capacitor or the like. AIoT devices may be used in Industrial Wireless Senor Networks where the environment is harsh (e.g., extremely high or low temperature) and may require devices to be battery-less, maintenance-free, and have a long service life. AIoT devices may play a role in Smart Logistics and Smart Warehousing. The low-cost, small-form, battery-lessness, and durability make AIoT devices suitable to be attached to wide variety of goods and facilitate more efficient goods identifying, sorting, tracking, and inventory. An example AIoT use case may involve very small size data transmission / reception, such as sending device identifications, product information, sensor data, or receiving actuator commands, triggering messages, etc. An AIoT device may be a device that is a wearable, a tracking device, a tag, a sensor, or the like.SUMMARY

[0003] Described herein are mechanisms for configuring and utilizing a wireless transmit / receive unit (WTRU) also referred to as a user equipment (UE) to handle paging and communications on behalf of one or more AIoT devices. The WTRU, also referred to herein as an AIoT assistant WTRU, may utilize an AIoT temporary identifier, referred to herein as a VTMSI (Virtual Temporary Mobile Subscriber Identity), or the like. The VTMSI may beassigned by a network. The AIoT assistant WTRU may utilize a PDU (Protocol Data Unit) session that may be associated with an AIoT service and / or device. The PDU session may be dedicated to the AIoT device. The AIoT assistant WTRU may monitor paging opportunities using the VTMSI and may receive downlink transmissions intended for AIoT devices using the PDU Session. The AIoT devices may be within a proximity of the AIoT assistant WTRU. The AIoT assistant WTRU may transmit the data received from the downlink transmission to the intended AIoT device or devices. The AIoT assistant WTRU may transmit data to an intended AIoT device(s) via a D2D (device-to device) communication channel.

[0004] An example method performed by a WTRU, may comprise sending a registration request message, wherein the registration request message may comprise receiving configuration information, wherein the configuration information may comprise an authorization for assistance with AIoT (ambient internet of things) paging associated with an AIoT device. The method may comprise receiving a registration response message, wherein the registration response message comprises a temporary identifier (e.g., VTMSI) associated with the AIoT device. The method may comprise monitoring paging opportunities based on the temporary identifier. The method may comprise receiving data intended for the AIoT device. And the method may comprise sending the received data to the AIoT device. The registration request message may comprise a request for assistance with a plurality of AIoT devices and the registration response message may comprise a temporary identifier associated with each of the plurality of AIoT devices. The registration request message may comprise an indication of an AIoT paging period. The monitoring of paging opportunities may occur during the AIoT paging period. The request message may comprise an AIoT service identifier (ID). The request message may comprise an AIoT group identifier (ID).

[0005] An example WTRU may comprise a transceiver and a processor. The processor may be configured to send, via the transceiver, a registration request message, wherein the registration request message may comprise receiving configuration information, wherein the configuration information may comprise a request for assistance with AIoT (ambient internet of things) paging associated with an AIoT device. The processor may be configured to receive, via the transceiver, a registration response message, wherein the registration response message comprises a temporary identifier associated with the AIoT device. The processor may be configured to monitor, via the transceiver, paging opportunities based on the temporary identifier. Theprocessor may be configured to receive, via the transceiver, data intended for the AIoT device. And the processor may be configured to send, via the transceiver, the received data to the AIoT device. The registration request message may comprise a request for assistance with a plurality of AIoT devices and the registration response message may comprise a temporary identifier associated with each of the plurality of AIoT devices. The registration request message may comprise an indication of an AIoT paging period. The monitoring of paging opportunities may occur during the AIoT paging period. The request message may comprise an AIoT service identifier (ID). The request message may comprise an AIoT group identifier (ID).

[0006] An example computer-readable storage medium may have executable instructions stored thereon for configuring at least one processor to send a registration request message, wherein the registration request message may comprise receiving configuration information, wherein the configuration information may comprise a request for assistance with AIoT (ambient internet of things) paging associated with an AIoT device. The executable instructions may configure the processor to receive a registration response message, wherein the registration response message comprises a temporary identifier associated with the AIoT device. The executable instructions may configure the processor to monitor paging opportunities based on the temporary identifier. The executable instructions may configure the processor to receive data intended for the AIoT device. And the executable instructions may configure the processor to send the received data to the AIoT device. The registration request message may comprise a request for assistance with a plurality of AIoT devices and the registration response message may comprise a temporary identifier associated with each of the plurality of AIoT devices. The registration request message may comprise an indication of an AIoT paging period. The monitoring of paging opportunities may occur during the AIoT paging period. The request message may comprise an AIoT service identifier (ID). The request message may comprise an AIoT group identifier (ID).

[0007] An example WTRU configured to perform WTRU-assisted communications for AIoT devices may comprise a transceiver and a processor. The processor may be configured to receive, via the transceiver, an ambient internet of things (AIoT) authorization policy. The processor may be configured to send, via the transceiver, based on the received AIoT authorization policy, a registration request message, wherein the registration request message comprises an indication for AIoT paging assistance. The processor may be configured to receive, via the transceiver, aregistration response message, wherein the registration response message comprises an indication of an AIoT paging period and one or more virtual temporary identifiers associated with at least one or more AIoT devices. The processor may be configured to receive, via the transceiver, a paging message comprising an indication of a virtual temporary identifier of the one or more virtual temporary identifiers. The processor may be configured to determine to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message. The processor may be configured to receive, via the transceiver, the downlink data intended for the AIoT device. The processor may be configured to send, via the transceiver, the received downlink data to the AIoT device. The received downlink data may be sent to the AIoT device via one of a unicast, a broadcast, or a device-to-device communication. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise a respective virtual temporary identifier associated with each of the one or more AIoT devices. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise an AIoT group identifier associated with the one or more AIoT devices. The one of more virtual temporary identifiers may comprise one or more virtual temporary mobile subscriber identifiers, one or more AIoT service identifiers, or a combination thereof. The processor may be configured to send, via the transceiver, a service request comprising an indication of a protocol data unit (PDU) session identifier associated with the one or more virtual temporary identifiers. The processor may be configured to monitor, via the transceiver, for paging occasions associated with the WTRU. The processor may be configured to monitor, via the transceiver, for paging occasions associated with at least one of the one or more AIoT devices. The processor may be configured to, upon expiration of a paging period associated with the AIoT device of the one or more AIoT devices, receive, via the transceiver, an updated virtual temporary identifier associated with the AIoT device of the one or more AIoT devices.

[0008] An example method for AIoT device WTRU-assisted communications may be performed by a WTRU. The method may comprise receiving an ambient internet of things (AIoT) authorization policy. The method may comprise sending, based on the received AIoT authorization policy, a registration request message, wherein the registration request message comprises an indication for AIoT paging assistance. The method may comprise receiving a registration response message, wherein the registration response message comprises anindication of an AIoT paging period and one or more virtual temporary identifiers associated with at least one or more AIoT devices. The method may comprise receiving a paging message comprising an indication of a virtual temporary identifier of the one or more virtual temporary identifiers. The method may comprise determining to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message. The method may comprise receiving the downlink data intended for the AIoT device. The method may comprise sending the received downlink data to the AIoT device. The received downlink data may be sent to the AIoT device via one of a unicast, a broadcast, or a device-to- device communication. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise a respective virtual temporary identifier associated with each of the one or more AIoT devices. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise an AIoT group identifier associated with the one or more AIoT devices. The one of more virtual temporary identifiers may comprise one or more virtual temporary mobile subscriber identifiers, one or more AIoT service identifiers, or a combination thereof. The method may comprise sending a service request comprising an indication of a protocol data unit (PDU) session identifier associated with the one or more virtual temporary identifiers. The method may comprise monitoring for paging occasions associated with the WTRU. The method may comprise monitoring for paging occasions associated with at least one of the one or more AIoT devices. The method may comprise, upon expiration of a paging period associated with the AIoT device of the one or more AIoT devices, receiving an updated virtual temporary identifier associated with the AIoT device of the one or more AIoT devices.

[0009] An example computer-readable storage medium for AIoT device WTRU-assisted communications may comprise executable instructions, wherein the computer-readable storage medium in not a transitory signal. The executable instructions, when executed, may configure at least one processor to receive an ambient internet of things (AIoT) authorization policy. The executable instructions, when executed, may configure at least one processor to send, based on the received AIoT authorization policy, a registration request message, wherein the registration request message comprises an indication for AIoT paging assistance. The executable instructions, when executed, may configure at least one processor to receive a registration response message, wherein the registration response message comprises an indication of an AIoTpaging period and one or more virtual temporary identifiers associated with at least one or more AIoT devices. The executable instructions, when executed, may configure at least one processor to receive a paging message comprising an indication of a virtual temporary identifier of the one or more virtual temporary identifiers. The executable instructions, when executed, may configure at least one processor to determine to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message. The executable instructions, when executed, may configure at least one processor to receive the downlink data intended for the AIoT device. The executable instructions, when executed, may configure at least one processor to send the received downlink data to the AIoT device. The received downlink data may be sent to the AIoT device via one of a unicast, a broadcast, or a device-to-device communication. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise a respective virtual temporary identifier associated with each of the one or more AIoT devices. The one or more virtual temporary identifiers associated with the at least one or more AIoT devices may comprise an AIoT group identifier associated with the one or more AIoT devices. The one of more virtual temporary identifiers may comprise one or more virtual temporary mobile subscriber identifiers, one or more AIoT service identifiers, or a combination thereof. The executable instructions, when executed, may configure at least one processor to send a service request comprising an indication of a protocol data unit (PDU) session identifier associated with the one or more virtual temporary identifiers. The executable instructions, when executed, may configure at least one processor to monitor for paging occasions associated with the WTRU. The executable instructions, when executed, may configure at least one processor to monitor for paging occasions associated with at least one of the one or more AIoT devices. The executable instructions, when executed, may configure at least one processor to, upon expiration of a paging period associated with the AIoT device of the one or more AIoT devices, receive an updated virtual temporary identifier associated with the AIoT device of the one or more AIoT devices.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, likethe detailed description, are examples. As such, the Figures and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Like reference numerals (“ref.” or “refs.”) in the Figures indicate like elements.

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

[0012] FIG. IB is an example system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0013] FIG. 1C is an example system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0014] FIG. ID is an example system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0015] FIG. 2 depicts an example ambient power-enabled internet of things (AIoT) assistant wireless transmit / receive unit (WTRU) registration and protocol data unit (PDU) session establishment procedure.

[0016] FIG. 3 depicts an example network triggered service request for an AIoT assistant WTRU.EXAMPLE NETWORKS FOR IMPLEMENTATION OF THE INVENTION

[0017] FIG. 1 A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-fdtered OFDM, fdter bank multicarrier (FBMC), and the like.

[0018] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0019] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

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

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

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

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

[0026] 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 IX, 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.

[0027] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. 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 cellularbased RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0028] The RAN 104 / 113 may be in communication with the CN 106 / 1 15, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0029] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0031] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a di splay / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0032] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0034] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 mayinclude two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

[0036] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / mi crophone 124, the keypad 126, and / or the di splay / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0037] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0038] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e g., base stations 114a, 114b) and / or determine its location based on the timing of thesignals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0039] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

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

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

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

[0044] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0045] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an SI 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 attachment of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

[0048] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0049] Although the WTRU is described in FIGS. 1 A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

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

[0051] 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 or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.1 le DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0052] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set widthvia signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0053] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0054] Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0055] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.1 lah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802. Hah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.1 lah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limitedbandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0056] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802.1 lac, 802.1 laf, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0057] In the United States, the available frequency bands, which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.

[0058] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

[0060] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0061] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non- standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

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

[0063] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP (third generation partnership project) access technologies such as WiFi.

[0065] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an Ni l interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183 a, 183b may performother functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP -based, non-IP based, Ethernet-based, and the like.

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

[0067] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0068] In view of Figs. 1A-1D, and the corresponding description of Figs. 1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0069] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in orderto test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may perform testing using over-the-air wireless communications.

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

[0071] Described herein are methods and apparatuses for configuring and utilizing a WTRU, referred to herein as an AIoT assistant WTRU, to handle paging and communications on behalf of one or more AIoT devices. An AIoT device may not be able to perform periodic or mobility registration procedures or contact the network directly because of its limited capabilities (e.g., limited or lack of signaling capabilities, inability to maintain registration timers, RRC - radio resource control- state). Current paging procedures require device signaling to locate the device or enable the device to establish connection for receiving data (e.g., Registration, Service Request). The lack of proper signaling support by the AIoT device may result in the network being unable to determine the AIoT device location and / or to alert the AIoT device of incoming data (e.g., for application function -AT- to send downlink commands). The ability to contact AIoT devices securely and reliably provides support for AIoT use cases (e.g., command). Described herein are mechanisms by which a 5GS (5G system) may provide means to support a secure and reliable paging mechanism for AIoT devices.

[0072] Described herein are mechanisms by which the NR (new radio) paging procedure may be enhanced so that a WTRU (e g., AIoT assistant WTRU) may handle paging on behalf of one or more AIoT devices using the concept of a virtual temporary identifier (referred to herein as a VTMSI). The VTMSI may be assigned by the network (e.g., AMF) to a WTRU authorized as anassistant WTRU (e.g., AIoT assistant WTRU) and associated with one or more AIoT devices based on WTRU subscription, configuration, and operator policy. The VTMSI may be updated frequently by the network for the WTRU (e.g., after each paging) to preserve the privacy of the WTRU or the associated AIoT devices. An AIoT assistant WTRU may receive an updated virtual temporary identifier associated with the AIoT device upon expiration of a paging period associated with an AIoT device. After being paged, the AIoT assistant WTRU may initiate procedures (e.g., service request) to perform the exchange of data (e.g., commands from an AIoT application function -AF) between the network and the AIoT devices.

[0073] The herein described mechanisms may enable scalable deployments of AIoT devices with limited capabilities. Limited capabilities may include a lack of a USIM (universal subscriber identity module), no 3GPP signaling / communication capabilities, limited energy storage, or the like, or any appropriate combination thereof. The herein described mechanisms may provide a cost effective AIoT service solution when coupled with assistant WTRUs. The herein described mechanisms may provide additional potential optimization opportunities for radio signaling resources usage (e.g., paging channel, Non Access Stratum -NAS / RRC messaging), when compared to an equivalent solution using conventional WTRUs and / or devices capable of direct network connectivity. In various examples, an AIoT assistant WTRU may be configured to be any combination of a wearable, a tracking device (e.g., tag), a sensor, or the like.

[0074] Utilization of an identifier for AIoT services, such as a VTMSI for example, may provide means to handle paging messages for an AIoT service that may require downlink data transmission that may be much less frequent than for other types of services. Such frequency may depend on AIoT AF requirements, the expected availability / reachability and / or capability of the AIoT devices. VTMSI based paging may allow the network to facilitate the paging procedure and other related signaling adapted for support of an AIoT service without impacting (or reducing the impact on) other types of services (e g., reduced usage of resources and power on the WTRU and network).

[0075] An AIoT assistant WTRU may utilize an AIoT temporary identifier, referred to herein as a VTMSI. The VTMSI may be assigned by a network. The AIoT assistant WTRU may utilize a PDU session that may be associated with an AIoT device. The PDU session may be dedicatedto the AIoT device. The AIoT assistant WTRU may monitor paging opportunities using the VTMSI and may receive downlink transmissions intended for AIoT devices using the PDU Session. The AIoT devices may be within a proximity of the AIoT assistant WTRU. The AIoT assistant WTRU may transmit the data received from the downlink transmission to the intended AIoT device or devices. The AIoT assistant WTRU my transmit data to an intended AIoT device(s) via a D2D (device-to device) communication channel.

[0076] For example, an AIoT assistant WTRU may handle paging on behalf of one or more AIoT devices and may send a wake up signal to the one or more AIoT devices. The AIoT assistant WTRU may send an AIoT payload to the one or more AIoT devices. The one or more AIoT devices may be within a proximity of the AIoT assistant WTRU. The AIoT assistant WTRU may communicate with the one or more AIoT devices via unicast, groupcast, broadcast, D2D communications, or the like, or any appropriate combination thereof. An AIoT assistant WTRU may be provisioned with an AIoT paging assistance authorization policy by a PCF (policy control function) and / or an AF (application function). For example, the AIoT assistant WTRU may be provisioned with an indication of the AIoT device or devices, a group ID associated with the AIoT device(s), an AIoT service ID, information associated with MT (mobile termination) data, information associated with MO (mobile origination) data, authorized PLMN (public land mobile network) areas, or the like, or any appropriate combination thereof.

[0077] An AIoT assistant WTRU may handle AIoT assisted paging based on an AIoT authorization policy. The AIoT assistant WTRU may initiate procedures upon an occurrence of a mobility event and / or upon an AIoT application layer trigger such as, for example AF (application function) messaging or AIoT device pairing / unpairing. An AIoT assistant WTRU may send a registration request message. The registration request message may include an indication for AIoT paging assistance (e.g., to add and / or remove a device) and one or more identifiers associated with one or more AIoT devices, a requested AIoT paging period, an AIoT service ID, an AIoT group ID, a list of AIoT device IDs, or the like, or any appropriate combination thereof. The AIoT assistant WTRU may receive a registration response message in response to the registration request message. The registration response message may include, for example, an indication of an AIoT paging period and one or more virtual temporary identifiers associated with an AIoT devices, or devices. The registration response message may include an acceptance of any, all, or none of the items requested in the registration request message. Forexample, the registration response message may include an acceptance of AToT paging assistance and one or more temporary identifiers (e.g., VTMSI) associated with the one or more AIoT devices, and the AIoT paging period. A VTMSI may be associated with a AIoT service ID. A network node, such as an AMF (access and mobility management function) may store mapping information associated with the VTMSI / AIoT service ID in an AIoT assistant WTRU context.

[0078] To establish an AIoT assistant WTRU session, an AIoT assistant WTRU may send a PDU Session establishment request message. The session establishment request message may include an AIoT service ID. The AIoT assistant WTRU may receive a PDU Session establishment accept message. The AIoT assistant WTRU may associate the PDU Session ID with the VTMSI which is associated with AIoT service ID. The AMF may maintain mapping PDU Session ID / VTMSI / AIoT service ID in an AIoT assistant WTRU context.

[0079] Regarding AIoT assistant WTRU paging, the AIoT assistant WTRU may monitor a PO (paging occasion) for one or more AIoT devices based on the VTMSI and allowed paging period. The AIoT assistant WTRU may start monitoring following registration or PDU Session establishment. The AIoT assistant WTRU may detect paging message(s) including VTMSI. The AMF may determine which VTMSI to page based on PDU Session ID / AIoT service ID from the AIoT assistant WTRU context. The AIoT assistant WTRU may send a service request including the PDU Session ID associated with the VTMSI in the allowed PDU Sessions. The network may reestablish network resources for AIoT communications. The AIoT assistant WTRU may receive downlink data and may forward it to AIoT devices.

[0080] Paging and Service Request may be the mechanisms by which the network alerts an AIoT assistant WTRU of incoming downlink data and for the AIoT assistant WTRU to reactivate the uplink connection to receive the downlink data. The AIoT assistant WTRU may be paged by the network (e.g., AMF) based on its intermediate temporary identifier 5G-GUTI (5G - Globally Unique Temporary Identity) using its shortened form 5G-S-TMSI (5G -Serving - Temporary Mobile Subscriber Identity). The temporary identifier may be uniquely assigned to the AIoT assistant WTRU by the AMF and may serve to page the AIoT assistant WTRU for all the PDU sessions the AIoT assistant WTRU has. The AIoT assistant WTRU may provide all the PDU sessions whose connection can be reactivated in the Service Request message in responseto the paging message. The network (e.g., SMF - session management function) may reestablish the uplink connection for the PDU session in the list of PDU sessions for which pending downlink data triggered the paging.

[0081] FIG. 2 depicts an example AIoT WTRU registration and PDU session establishment procedure. FIG. 2 depicts examples of Registration and PDU Session establishment procedures which may be enhanced to enable communications with AIoT devices using an assistant WTRU (aka intermediate node or AIoT assistant WTRU). The Assistant WTRU may perform a Registration procedure to inform the network that it wishes to handle communication on behalf of AIoT devices. The AIoT assistant WTRU may obtain from the network a temporary identifier (VTMSI) assigned specifically for the AIoT devices and used by the network to locate the AIoT devices and alert them of incoming data via the AIoT assistant WTRU. The AIoT assistant WTRU may establish a PDU Session dedicated for the purpose of transporting data sent to and received from the AIoT devices. The PDU Session may be associated with the VTMSI in the AIoT assistant WTRU and the network. This association may allow the network and AIoT assistant WTRU to determine whether incoming download traffic is intended for (intended destination) the AIoT devices.

[0082] The AIoT assistant WTRU (204) may receive an AIoT authorization policy. At step 0a, the AIoT assistant WTRU (204) may be authorized in the network (UDM-unified data management / UDR-unified data repository 212) to act as an Assistant WTRU for an AIoT service and / or individual AIoT device(s) (202). The authorization information included in the subscription data may include one or more AIoT service IDs and / or one or more AIoT devices (202). The information may indicate whether Mobile Originated (MO) and / or Mobile Terminated (MT) data for AIoT devices is authorized, e.g., devices that are DT (Device Terminated) or DO-DTT (Device -originated - device-terminated triggered), or DO-A (Deviceoriginated - autonomous). Parameters associated with this information may be set by an operator and / or provisioned by an AF (Application Function) (214) using external parameter provisioning procedure (e.g., using Nnef_ParameterProvision_Create function). At step 0b, the AIoT assistant WTRU (204) may perform an initial Registration procedure providing its AIoT assistance capabilities. During the procedure the AIoT assistant WTRU may be provisioned by a PCF (210), for example, with an AIoT paging and communication assistance authorization policy. The policy may include the AIoT service ID and / or device ID supported, the type ofservice / d evices supported (e.g., DO-DTT or DT). The AIoT assistant WTRU (204) may be provisioned with a URSP (user equipment routing selection policy) rule that AIoT assistant WTRU (204) may use to determine a DNN (data network name) / S-NSSAI (single-network slice selection assistance information) combination that is associated with the AIoT Service ID. The WTRU (204) may provide the DNN / S-NSSAI combination to the network during the PDU Session Establishment procedure (described below). At step 0c, the AIoT assistant WTRU (204) may be paired with one or more AIoT devices (202) (e.g., using low power Bluetooth communications). The AIoT devices (202) may be associated with a AIoT service.

[0083] The AIoT assistant WTRU (204) may send, based on the AIoT authorization policy, a registration request message, wherein the registration request message may comprise an indication for AIoT paging assistance. At step 1, based on the pairing and AIoT authorization policy the AIoT assistant WTRU (204) may initiate a registration procedure (send a registration request) to provide paging and communication assistance to the paired devices. The AIoT assistant WTRU (204) may indicate, in the registration request, the AIoT Service ID that is associated with the device(s) (202) that the AIoT assistant WTRU (204) is paired with. The AIoT assistant WTRU (204) may indicate one or more AIoT device ID(s) associated with the paired device(s) (202).

[0084] At step 2a, the AMF (206) may check that the AIoT assistant WTRU (204) is authorized as AIoT Assistant WTRU based on subscription information. The AMF (206) may check the AIoT assistant WTRU provided AIoT Service ID (or device ID(s)) against the one or more AIoT Service ID(s) (or device ID(s)) authorized in the subscription data. If the AIoT assistant WTRU (204) did not provide any AIoT service (or device ID) the AMF (206) may decide to authorize a default AIoT service ID (or one or more device IDs) based on subscription information and local operator policy.

[0085] At step 2b, the AMF (206) may check whether the AIoT assistant WTRU (204) is authorized for MT and / or MO service. If the device (204) is authorized for MT service (e.g., to receive paging for AIoT devices) the AMF (206) may allocate a secondary temporary ID or virtual TMSI (VTMSI). The AMF (206) may store the secondary temporary ID or the VTMSI in the WTRU Context along the associated AIoT service ID (device ID).

[0086] The AIoT assistant WTRU (204) may receive a registration response message, which may comprise an indication of an AIoT paging period and one or more virtual temporary identifiers associated with at least one AIoT device (202). At step 3, the AIoT assistant WTRU (204) may receive a Registration Response message (e.g., registration accept message), which may include a VTMSI. The Registration Response message may include an AIoT Service ID the VTMSI is associated with (e.g., if not provided in the Registration Request). The VTMSI may be associated with the AIoT Service ID provided by the AIoT assistant WTRU (204) in the Registration Request (e.g., at step 1). The Registration Response message may include a paging period, or periods, for monitoring for paging occasions.

[0087] At step 4, the AIoT assistant WTRU (204) may store the VTMSI along with any AIoT service / device ID received from AMF (206) or already configured. The AIoT assistant WTRU (204) may monitor for paging occasions associated with the AIoT assistant WTRU (204). The AIoT assistant WTRU (204) may monitor for paging occasions associated with an AIoT device, or devices (202). The AIoT assistant WTRU (204) may start monitoring for AIoT service / device paging using the VTMSI. The AIoT assistant WTRU (204) may perform conventional monitoring for its own paging using its own S-TMSI (serving temporary mobile subscriber identity), e.g., for its own, non-IoT data services.

[0088] At step 5, the AIoT assistant WTRU (204) may establish a PDU Session so that the AIoT assistant WTRU (204) may send and receive data to an AS (application server) that is associated with the AIoT Service ID. The AIoT assistant WTRU (204) may provide a DNN / S- NSSAI combination used for the AIoT service or send the VTMSI to the AMF (206) in the NAS message to the AMF (206) that carries the PDU Session Establishment Request. The AMF (206) may determine a DNN / S-NSSAI combination based on the VTMSI and provide the DNN / S- NSSAI combination to the SMF (208) when the PDU Session Establishment Request is sent to the SMF (208).

[0089] At step 6a, The AMF (206) may associate the VTMSI with the PDU Session ID (SM Context). At step 6b, the SMF (208) may receive the AIoT service ID in the PDU Session Establishment request. The SMF (208) may store the AIoT service ID in the WTRU SM context.

[0090] At step 7, the AIoT assistant WTRU (204) may receive a PDU Session Establishment Accept message confirming that AIoT assistant WTRU (204) is authorized send and receive datato / from the AIoT AS. At step 8, the AIoT assistant WTRU (204) may associate the PDU Session ID with the AIoT service ID (or AIoT device IDs).

[0091] The AIoT WTRU (204) may receive a paging message comprising an indication of a virtual temporary identifier of a virtual temporary identifier, or identifiers. The AIoT WTRU (204) may determine to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message. The AIoT WTRU (204) may receive the downlink data intended for the AIoT device, or devices. And, the AIoT WTRU (204) may provide the received downlink data to the AIoT device, or devices.

[0092] An AIoT application in the AIoT assistant WTRU may establish communication with the AS. For example the AIoT assistant WTRU may send a message to inform the AS of its availability as an AIoT assistant WTRU and its proximity / connection with one or more AIoT devices. The AIoT assistant WTRU may provide the identifiers of the Ambient loT Devices (e.g., which last time contacted if not currently connected) and an Identifier of the WTRU (e.g., an External ID). Alternatively, the AS may subscribe via an NEF (network exposure function) for events related to the AIoT assistant WTRU (e g., from step 0 in FIG. 2). For example the AS may be notified by an NEF of the PDU Session being established by the AIoT assistant WTRU and of the AIoT assistant WTRU IP Address / Prefix. The AS also may be notified of the AIoT assistant WTRU location. With this mechanism the AS may determine whether an AIoT device is reachable and its (last known) location. For example the AS may provide a “Find me” service to locate tracking tag.

[0093] The PDU Session establishment procedure may be enhanced to enable communications with AIoT devices using an AIoT assistant WTRU. The AIoT assistant WTRU may establish a PDU Session dedicated for the purpose of transporting data sent to and from the AIoT devices. The AIoT assistant WTRU may obtain the VTMSI from the network in an NAS message (e.g., WTRU Configuration Update command, NAS transport) during or following the PDU Session establishment procedure. The AMF may detect that a VTMSI is to be allocated based on combination of DNN / S-NSSAI in the PDU Session or based on a message from SMF (e.g., Nsmf_PDUSession_CreateSMContext Response).

[0094] The same AIoT service may be provided by multiple AIoT assistant WTRUs, each with its PDU session established (as described above). The AIoT assistant WTRUs may be served bythe same AMF which may assign to each AIoT assistant WTRU a unique VTMSI. An AS may then contact multiple sets (clusters) of AIoT devices using one or more AIoT assistant WTRUs. For example, an AS may collect data from a high number of sensors widely spread (e.g., in a field) using only a few AIoT assistant WTRUs.

[0095] FIG. 3 depicts an example network triggered paging / service request for an AIoT assistant WTRU (304) . FIG. 3 depicts an example of network triggered Service Request procedure which may be enhanced to alert AIoT devices (302) using an AIoT assistant WTRU (304). The network (e.g., AMF) (308) may determine that an AIoT assistant WTRU (304) is to be paged using a VTMSI based on the determination that the downlink data is for a PDU Session for AIoT service that is associated with the VTMSI. When paged the AIoT assistant WTRU (304) may include the AIoT PDU Session ID in the list of PDU Sessions sent to the network in the Service Request message. The AIoT assistant WTRU (403) may obtain from the network during a WTRU Configuration update procedure a new temporary identifier (VTMSI) that may be used to replace the old VTMSI and associated with the PDU Session in the AIoT assistant WTRU (304) and network. The update of VTMSI allocation after alerting the AIoT assistant WTRU (304) for AIoT incoming data may allow for the privacy protection of AIoT devices (302) (e.g., prevent unauthorized tracking).

[0096] At step 0, the AIoT assistant WTRU (304) has been authorized by the network to act as an Assistant WTRU for an AIoT service and / or individual AIoT device(s) (302). The AIoT assistant WTRU (304) has established a PDU Session for the AIoT service communication. The AIoT application on the AIoT assistant WTRU (304) may have established communication with the AIoT AS (314) and / or the AS (314) may have learned about the connectivity of the AIoT assistant WTRU (304) via the network as described above.

[0097] At step 1, the AS (314) may send downlink data to the AIoT assistant WTRU (304) intended for (intended destination) the AIoT devices (302). At step 2, the UPF (312) may detect and may notify the SMF (310) of the arrival of a downlink packet destined for the PDU Session of the AIoT assistant WTRU (304). At step 3, the SMF (310) may request from AMF (308) transfer of a downlink message to AIoT assistant WTRU (304) / RAN (308). The message may include the PDU Session ID and may include an AIoT service ID. At step 4, the AMF (308) maydetermine, based on the AIoT service ID, that the paging is for an AIoT assistant WTRU (304) and locate the associated VTMSI based on PDU Session ID / AIoT service ID.

[0098] At step 5, the AMF (308) may send a paging message to the RAN (306) to page the AIoT assistant WTRU (304) identified by VTMSI. The RAN (306) may send a paging message to the AIoT assistant WTRU (304) including the VTMSI using the corresponding paging opportunity. At step 6, the AIoT assistant WTRU (304) may detect the paging for its VTMSI and determine that the AIoT assistant WTRU (304) is to receive incoming downlink data for the AIoT devices (302) on the PDU Session setup for the associated AIoT service. Based on the determination that AIoT devices (302) associated with the AIoT service are to be alerted, the AIoT assistant WTRU (304) may trigger actions proactively with the AIoT devices (302) (e.g., prior or during next step, before receiving downlink). For example, the AIoT assistant WTRU (304) may attempt to wake up or set up communications with the devices (302) and / or assess whether the devices (302) are reachable. At a later step (step 9), the AIoT assistant WTRU (304) may forward more rapidly downlink data to devices (302) that have been connected and / or provide close to real time status back to the AS (314) if the device cannot be reached. The AIoT assistant WTRU (304) may send device data reception ack / response or device reachability status information to the AS (314) more rapidly, which may allow for quicker release of uplink resources in the network. At step 7, the AIoT assistant WTRU (304) may send a service request message and include (e.g., only) the PDU Session ID for the AIoT service in the list of PDU Sessions to request the reestablishment of RAN / CN communications resources. At step 8 / 8a, following the completion of the service request, the AMF (308) may send a WTRU Configuration Command message including a new VTMSI to be used for a future paging. At step 8b, the PDU Session ID may be associated with the new VTMSI which replaces the old VTMSI in the AIoT assistant WTRU (304) and the network. At step 9, the AIoT assistant WTRU (304) may receive the downlink data for the AIoT devices (302). The AIoT assistant WTRU (304) may transmit the data to the devices (302) by means based on the AIoT communication technology used (e.g., low power RAT-radio access technology- such as Bluetooth, or the like).

[0099] The AIoT assistant WTRU (304) may buffer the data sufficiently to allow for an AIoT device (302) unavailable / offline to come online (e.g., recharged with sufficient energy harvested). The application on the AIoT assistant WTRU (304) may send acknowledgement ofdata received to the AS (314) on behalf of the AIoT devices (302). The application on the AIoT assistant WTRU (304) may request new data if previous data (e.g., command) could not be transmitted in time (e.g., if with expiry).

[0100] Considerations for the support of multiple AIoT services by the same AIoT assistant WTRU are provided herein. The AIoT assistant WTRU may support multiple AIoT services concurrently. In some scenarios, the AIoT assistant WTRU may establish a PDU Session per AIoT service and therefore may be paged for a specific AIoT service using the associated VTMSI / PDU Session as described above. In other scenarios a PDU Session may be reused by the AIoT assistant WTRU for multiple AIoT services (e.g., using same DNN / S-NSSAI). The network may be able to distinguish the service data flow based on information such as the respective application ID, AS / application addressing info (source / destination IP Address / port). The AIoT assistant WTRU may be paged with the same VTMSI for all AIoT services associated with the PDU Session. Then, the application on the AIoT assistant WTRU may determine the target AIoT service based on the downlink data packet information (destination IP address / port).

[0101] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods, apparatuses, and articles of manufacture, within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims.

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

[0103] Any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable storage medium. The computer- readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

Claims

CLAIMSWhat is claimed is:

1. A wireless transmit / receive unit (WTRU) comprising: a transceiver and; a processor configured to: receive, via the transceiver, an ambient internet of things (AIoT) authorization policy; send, via the transceiver, based on the received AIoT authorization policy, a registration request message, wherein the registration request message comprises an indication for AIoT paging assistance; receive, via the transceiver, a registration response message, wherein the registration response message comprises an indication of an AIoT paging period and one or more virtual temporary identifiers associated with at least one or more AIoT devices; receive, via the transceiver, a paging message comprising an indication of a virtual temporary identifier of the one or more virtual temporary identifiers; determine to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message; and receive, via the transceiver, the downlink data intended for the AIoT device.

2. The WTRU of claim 1 , the processor further configured to send, via the transceiver, the received downlink data to the AIoT device.

3. The WTRU of claim 2, wherein the received downlink data is sent to the AIoT device via one of a unicast, a broadcast, or a device-to-device communication.

4. The WTRU of claim 1, wherein the one or more virtual temporary identifiers associated with the at least one or more AIoT devices comprises a respective virtual temporary identifier associated with each of the one or more AIoT devices.

5. The WTRU of claim 1, wherein the one or more virtual temporary identifiers associated with the at least one or more AIoT devices comprises an AIoT group identifier associated with the one or more AIoT devices.

6. The WTRU of claim 1, wherein the one of more virtual temporary identifiers comprises one or more virtual temporary mobile subscriber identifiers, one or more AIoT service identifiers, or a combination thereof.

7. The WTRU of claim 1, the processor further configured to send, via the transceiver, a service request comprising an indication of a protocol data unit (PDU) session identifier associated with the one or more virtual temporary identifiers.

8. The WTRU of claim 1, the processor further configured to monitor, via the transceiver, for paging occasions associated with the WTRU.

9. The WTRU of claim 1, the processor further configured to monitor, via the transceiver, for paging occasions associated with at least one of the one or more AIoT devices.

10. The WTRU of claim 1, the processor further configured to, upon expiration of a paging period associated with the AIoT device of the one or more AIoT devices, receive, via the transceiver, an updated virtual temporary identifier associated with the AIoT device of the one or more AIoT devices.

11. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: receiving an ambient internet of things (AIoT) authorization policy; sending, based on the received AIoT authorization policy, a registration request message, wherein the registration request message comprises an indication for AIoT paging assistance; receiving a registration response message, wherein the registration response message comprises an indication of an AIoT paging period and one or more virtual temporary identifiers associated with at least one or more AIoT devices; receiving a paging message comprising an indication of a virtual temporary identifier of the one or more virtual temporary identifiers; determining to receive downlink data intended for an AIoT device associated with the virtual temporary identifier identified in the paging message; andreceiving the downlink data intended for the AIoT device.

12. The method of claim 11, further comprising sending the received downlink data to the AIoT device.

13. The method of claim 12, wherein the received downlink data is sent to the AIoT device via one of a unicast, a broadcast, or a device-to-device communication.

14. The method of claim 11, wherein the one or more virtual temporary identifiers associated with the at least one or more AIoT devices comprises a respective virtual temporary identifier associated with each of the one or more AIoT devices.

15. The method of claim 11, wherein the one or more virtual temporary identifiers associated with the at least one or more AIoT devices comprises an AIoT group identifier associated with the one or more AIoT devices.

16. The method of claim 11, wherein the one of more virtual temporary identifiers comprises one or more virtual temporary mobile subscriber identifiers, one or more AIoT service identifiers, or a combination thereof.

17. The method of claim 11, further comprising sending a service request comprising an indication of a protocol data unit (PDU) session identifier associated with the one or more virtual temporary identifiers.

18. The method of claim 11, further comprising monitoring for paging occasions associated with the WTRU.

19. The method of claim 11, further comprising monitoring for paging occasions associated with at least one of the one or more AIoT devices.

20. The method of claim 1 1, further comprising, upon expiration of a paging period associated with the AIoT device of the one or more AIoT devices, receiving an updated virtual temporary identifier associated with the AIoT device of the one or more AIoT devices.

Images