Paging strategy for ambient devices by using an intermediate node
The proposed paging strategy for ambient IoT devices uses intermediate node locations to optimize paging areas, reducing energy consumption and signaling, thereby enhancing efficiency and resource conservation.
Patent Information
- Application Number
- PCT/US2025/011031
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-11
- Filing Date
- 2025-01-10
- Publication Date
- 2025-07-17
AI Technical Summary
Existing paging strategies for ambient IoT devices are inefficient, leading to excessive energy consumption and unnecessary signaling due to frequent location updates and wide-area paging, which is detrimental to devices with limited energy storage and high mobility.
A paging strategy that utilizes the location information of intermediate nodes associated with ambient IoT devices to determine targeted paging areas, reducing the need for widespread broadcasting and conserving network resources.
This approach minimizes energy consumption and signaling overhead by efficiently reaching ambient IoT devices through intermediate nodes, ensuring timely data delivery while conserving network resources.
Smart Images

Figure US2025011031_17072025_PF_FP_ABST
Abstract
Description
PAGING STRATEGY FOR AMBIENT DEVICES BY USING AN INTERMEDIATE NODECROSS-REFERENCE TO RELATED APPLICATION
[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 619,930, filed January 11, 2024, the contents of which are incorporated herein by reference.BACKGROUND
[0002] Paging is a procedure that allows a mobile network to reach a wireless transmit / receive unit (WTRU) when the WTRU is in an inactive state or idle state. While the WTRU goes to the idle state or idle mode, the last known gNode B (gNB) or base station that the WTRU attached to (for example, an anchor gNB or anchor base station) saves the WTRU core context information.
[0003] Discontinuous Reception (DRX) has been introduced allowing the WTRU to shut down for a specific period of time before waking up and decoding the Paging Occasion (PC) to check if there is any paging message toward the WTRU and in which one or more Resource Blocks the message will be sent Network nodes may trigger a paging message.SUMMARY
[0004] A network node may receive a first indication indicating that a wireless transmit / receive unit (WTRU) is associated with an intermediate node. The network node may be or may include an access and mobility function (AMF). The first indication may be included in a message. Further, the message may include a first identity of the WTRU that is associated with the intermediate node. Also, the message may include a second indication of how long the WTRU and intermediate node are expected to be associated. Moreover, the AMF may receive information from a session management function (SMF) that indicates that there is downlink data available for the WTRU The A F may respond to the SMF and the response may indicate that the intermediate node is associated with the WTRU.
[0005] Additionally or alternatively, the procedure may involve receiving, from the UDM node, a second identity of an AMF that serves the intermediate node. In addition, the procedure may involve receiving, from the AMF that serves the intermediate node, first location information associated with the intermediate node. Moreover, the first location information associated with the intermediate node may be one or more RAN Node Identities, one or more cell identities, or one or more tracking area identities. In addition, the AMF may send a first paging message to a RAN Node that is associated with the first location information associated with the intermediate node The first paging message may include one or more of the cell identities or tracking area identities that are associated with the intermediate node, and includes a third identity that is associated with the WTRU and a fourth identity that is associated with the intermediate node.
[0006] Additionally or alternatively, the AMF may perform a procedure to determine second location information associated with the intermediate node. Further, the AMF may send a second paging message to aRAN Node that is associated with the second location information associated with the intermediate node. Additionally or alternatively, the procedure may involve receiving, from a unified data management (UDM) node or a UDM / unified data repository (UDR), third location information associated with the intermediate node. Moreover, the AMF may send a third paging message to a RAN Node that is associated with the third location information associated with the intermediate node.BRIEF DESCRIPTION OF THE DRAWINGS
[0007] 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, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein:
[0008] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;
[0009] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
[0010] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
[0011] FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
[0012] FIG. 2 is a signaling diagram illustrating an example of paging in Third Generation Partnership Project (3GPP) networks;
[0013] FIG. 3 is a signaling diagram illustrating an example of a registration update;
[0014] FIG. 4 is a system diagram illustrating an example of an ambient device and intermediate node scenario; and
[0015] FIG. 5 is a signaling diagram illustrating an example of intermediate node and ambient device associationDETAILED DESCRIPTION
[0016] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described,disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.
[0017] Example communications system, networks, and devices are provided The methods, procedures, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.
[0018] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
[0019] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill 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 (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 (for example, remote surgery), an industrial device and applications (for example, 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.
[0020] 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, 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 NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (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.
[0021] The base station 114a may be part of the RAN 104, 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, and the like. 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.
[0022] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (for example, radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0023] More specifically, as noted above, the 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 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 116 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 Uplink (UL) Packet Access (HSUPA).
[0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), 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).
[0025] 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 NR.
[0026] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may 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 (for example, an eNB and a gNB).
[0027] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e , Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
[0028] The base station 114b in FIG 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (for example, for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (for example, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.
[0029] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have 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 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 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0030] The CN 106 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 or a different RAT.
[0031] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (for example, 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. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0032] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0033] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0034] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (for example, 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.
[0035] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (for example, multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0036] 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.
[0037] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (for example, 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 nonremovable 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).
[0038] 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 (for example, nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium- ion (Li-ion), etc.), solar cells, fuel cells, and the like.
[0039] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (for example, 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 (for example, base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.
[0040] 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 satellitetransceiver, 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, a humidity sensor and the like.
[0041] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (for example, associated with particular subframes for both the U L (for example, for transmission) and DL (for example, for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (for example, a choke) or signal processing via a processor (for example, 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 (for example, associated with particular subframes for either the UL (for example, for transmission) or the DL (for example, for reception)).
[0042] 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 ON 106.
[0043] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.
[0044] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
[0045] The ON 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 (PGW) 166. While the foregoing elements are depicted as part of the ON 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0046] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gatewayduring an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA
[0047] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
[0048] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0049] The ON 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 (for example, 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.
[0050] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (for example, temporarily or permanently) wired communication interfaces with the communication network.
[0051] In representative embodiments, the other network 112 may be a WLAN.
[0052] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for 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 (for example, directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (for example, 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.
[0053] When using the 802.11 ac 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 (for example, 20 MHz wide bandwidth) or a dynamically set width. 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 (for example, 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 (for example, only one station) may transmit at any given time in a given BSS
[0054] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
[0055] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 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).
[0056] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (for example, only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (for example, to maintain a very long battery life).
[0057] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of802.11 ah, the primary channel may be 1 MHz wide for ST As (for example, MTC type devices) that support (for example, 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, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
[0058] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
[0059] FIG. 1 D 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 NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0060] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0061] 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 (for example, containing a varying number of OFDM symbols and / or lasting varying lengths of absolute time).
[0062] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (for example, such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102cmay 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.
[0063] 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, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
[0064] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While 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.
[0065] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 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 (for example, handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (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 MTC access, and the like The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non- Third Generation Partnership Project (3GPP) access technologies such as WiFi.
[0066] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IPaddress, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
[0067] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 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 DL packets, providing mobility anchoring, and the like.
[0068] The CN 106 may facilitate communications with other networks For example, the CN 106 may include, or may communicate with, an IP gateway (for example, 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. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local 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.
[0069] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, 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.
[0070] 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 order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network The emulation device may be directly coupled to another device for purposes of testing and / or performing testing using over-the-air wireless communications.
[0071] 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 (for example, 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 wirelesscommunications via RF circuitry (for example, which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.
[0072] Paging is a procedure that allows the mobile network to reach a WTRU when the WTRU is in an inactive state or idle state. While the WTRU goes to the idle state or idle mode, the last known gNB or base station that the WTRU attached to (for example, an anchor gNB or anchor base station) saves the WTRU core context information. Discontinuous Reception (DRX) has been introduced allowing the WTRU to shut down for a specific period of time before waking up and decoding the Paging Occasion (PO) to check if there is any paging message toward the WTRU and in which one or more Resource Blocks the message will be sent.
[0073] FIG. 2 is a signaling diagram illustrating an example of paging in 3GPP networks. As shown in an example in signaling diagram 200, when there is incoming data from a UPF 290, an SMF 283 notifies an AMF 282 about the arriving traffic utilizing a Namf_Communication_N1N2MessageTransfer Request. The AMF 282 triggers an access node (AN) 214, such as a base station or a gNB, with a next generation (NG) application protocol (NGAP) paging message. Considering the DRX, the AN 214 (or gNB) pages a WTRU 202 (or UE) using one of the Paging Occasions (PO) on the physical downlink control channel PDCCH. The WTRU 202 must decode the PDCCH traffic for any paging information every cycle, which can be resource wasteful if the WTRU 202 has no data to receive.
[0074] In an example, a WTRU can be triggered to initiate a registration update to update its location by one, but not limited to, of the following: the periodic Tracking Area (TA) update timer has expired; the radio resource control (RRC) connection was released with release cause “load re-balancing TAU required”; or the RRC layer in the WTRU informs the WTRU’s NAS layer that an RRC connection failure has occurred.
[0075] FIG. 3 a signaling diagram illustrating an example of a registration update. As shown in an example in signaling diagram 300, when triggered, a WTRU 302 sends a location update message to a new AMF 382 to start a registration update. In an example, the registration update request may be sent to the new AMF 382 by way of a base station 380, such as a gNB. The new AMF 382 retrieves the WTRU contexts from an old AMF 381. After retrieving the WTRU context, the new AMF 302 sends a PDU session update session management (SM) context request to an SMF 390 When the new AMF 382 receives the response from the SMF 390, the new AMF 382, sends a registration update confirmation to the WTRU 302. Additionally or alternatively, the registration update response may be sent to the WTRU 302 by way of the base station 380.
[0076] FIG. 4 is a system diagram illustrating an example of an ambient device and intermediate node scenario. In an example shown in system diagram 400, ambient loT devices may be behind an intermediate node. Further, FIG. 4 shows an example scenario where the network, such as core network 406, is using an intermediate node, such as intermediate node WTRUs 410a, 410b, to locate and page one or more ambient devices, such as WTRUs 402a, 402b, 403c, 402d, 402e, 402f. In an example, core network 406 may communicate with intermediate node WTRUs 410a via AN1 414a, and with intermediate node WTRUs 410b via AN 1 414b. The core network 406 might use the intermediate node WTRU 410a or intermediate node WTRU 410b to locate the ambient loT device due to the limited power availability in the ambient device, and thepossibility of the ambient device becoming deactivated when the ambient loT device runs out of power. When the ambient loT device becomes not pageable, the core network 406 can use the intermediate node WTRU location to locate the ambient device WTRU
[0077] A paging strategy may involve different use cases and objectives, and may include any one or any combination of the following. For example, a paging strategy may involve determining where, for example, what tracking areas or cells, to transmit a page for a WTRU. Further, a paging strategy may involve determining how many times to transmit a page for a WTRU before receiving a response This determination may be made before determining to transmit the page in other locations (for example, other tracking areas or cells). Additionally or alternatively, this may be made before determining that the WTRU is not reachable Forming efficient paging strategies involves important tradeoffs.
[0078] A network that initially transmits a page over a very wide area, for example, in a large number of cells or tracking areas, is very likely to receive a response from the WTRU if the WTRU is available. However, the network resources that were used to transmit the page in all the cells and tracking areas where the WTRU was not present would have been wasted. Furthermore, it is likely that many devices will experience false pages and process them, thus causing WTRUs that were not paged to perform more processing and as a result cause such devices to become less available, which may, in some examples, case a denial of service (DOS) attack.
[0079] Conversely, a network that initially transmits a page over a very small area, for example, in a small number of cells or tracking areas, is less likely to receive a response from a highly mobile WTRU if the WTRU is available. For example, the network may initially only transmit the page in a small area and then gradually increase the area where the page is transmitted until the WTRU responds. A network that gradually increases the paging area in this manner will waste fewer paging resources but will take a longer time to reach the WTRU.
[0080] In embodiments and examples provided herein, the term paging area may refer to the location where a page is transmitted. Also, the location may be described as a list of one or more cells or tracking areas, in embodiments and examples provided herein.
[0081] Embodiments and examples provided herein include low power modes or lower power states. A WTRU may operate in certain modes, or states, where the WTRU is expected to consume a relatively small amount of power compared to a mode, or state, where the WTRU, for example, transmits data.
[0082] The WTRU and network may coordinate the WTRU’s use of power modes or states. In other words, the network may be aware of when the WTRU is operating in a lower power mode or state.
[0083] A Fifth Generation (5G) WTRU may operate in a connection management (CM)-IDLE state where the WTRU periodically listens to the network for pages and otherwise does not transmit or receive any data.
[0084] A 5G WTRU may operate in a Mobile Initiated Connection Only (MICO) Mode. When the WTRU is in MICO mode, the WTRU does not listen for pages.
[0085] Embodiments and examples provided herein may assume that an Ambient loT device may sometimes operate in an Ambient loT Low Power State. When the WTRU is in the Ambient loT Low Power State, the WTRU will not listen to the network for a page.
[0086] Registration updates are used by WTRUs to update the network with the WTRU’s current location. For example, the procedure is used to indicate if the WTRU has left a registration area. The network will use the WTRU’s registration area to form a paging strategy for a WTRU if downlink data comes for the WTRU while the WTRU is in CM-IDLE mode. If this same approach to forming a paging strategy is applied to Ambient loT devices, it may be detrimental to the Ambient loT devices in terms of energy consumption and it may be detrimental to the network in terms of generating unnecessary signaling.
[0087] This approach may be detrimental to the Ambient loT devices in terms of energy consumption because performing the registration update procedure will consume energy that is stored by the Ambient loT device.
[0088] Further, this approach may be detrimental to the network in terms of generating unnecessary signaling because, given the large density of ambient loT devices, performing the registration update procedure will generate a significant amount of signaling in the network. Considering that there may be numerous Ambient loT devices in the network and that the network only needs to initiate contact with the devices infrequently, it may be that the information that is obtained by the network in the registration area update, for example, the WTRU’s location, is often not needed.
[0089] Embodiments and examples provided herein focus on Ambient loT devices that send and receive data very infrequently and will therefore spend a high percentage of time in an Ambient loT Low Power State. Further, embodiments and examples provided herein focus on Ambient loT devices that need to be reachable for mobile terminated data. Also, embodiments and examples provided herein focus on Ambient loT devices that do not reliably have enough energy stored to respond to paging messages; are highly mobile. Moreover, embodiments and examples provided herein focus on Ambient loT devices that can connect to the network via an intermediate node.
[0090] Embodiments and examples provided herein include addressing problems such as how, in the scenario described above, the network can determine a paging strategy for the Ambient loT device without requiring the Ambient loT device to frequently update the network with a device location, and without the network sending unnecessary paging messages and signaling toward the WTRU.
[0091] A WTRU may be an ambient loT device. This WTRU may go long periods of time without sending updated location information to the network. For example, due to limited energy storage capacity, the WTRU might not be able to periodically perform a registration area update with the network. When the network receives downlink data for this type of WTRU, the network may need to page the WTRU. Since a relatively long period of time may have passed since the WTRU last communicated with the network and the WTRU may be mobile, the network needs to form a strategy for paging the WTRU. Part of the paging strategy involves determining where to send the paging message, for example, where the WTRU is likely to be located.
[0092] Some WTRUs will communicate with the network via intermediate nodes.
[0093] Embodiments and examples presented herein include a solution for forming a paging strategy for WTRUs that sometimes communicate via intermediate nodes. The principle of the solution is that a network function (for example, an AMF) can form a paging area (by, for example, determining the parts of the network where a paging message needs to be sent) for the WTRU (for example, the Ambient lot Device) by using location information that is associated with the intermediate node. The paging message may also be sent to the intermediate node (instead of the WTRU) so that the intermediate node can trigger the WTRU to perform a service request. The paging message that is sent from the AMF to the Base Station may include the identity of the WTRU that needs to be paged and the identity of the intermediate node The paging message may indicate whether the WTRU should be triggered, by the intermediate node, to perform a Service Request or send data to the network.
[0094] An advantage of this procedure is that it reduces the area over which a paging message needs to be broadcasted. Thus, paging resources in the network are conserved.
[0095] Embodiments and examples provided herein include using the intermediate node location in a paging strategy for the Ambient loT WTRU, and include one or more AMF actions. In an example, an AMF may receive an indication that a WTRU is associated with an intermediate node. The indication may be included in a message Further, the message may include an identity that is associated with the intermediate node. Additionally or alternatively, the message may include an indication of how long the WTRU and intermediate node are expected to be associated.
[0096] Also, the AMF may receive a message from an SMF that indicates that there is downlink data available for the WTRU. The AMF may respond to the SMF and the response may indicate that there is an intermediate node associated with the WTRU.
[0097] Further, the AMF may perform a procedure to determine location information associated with the intermediate node The procedure may involve receiving, from the unified data management (UDM)Zunified data repository (UDR), location information associated with the intermediate node. Additionally or alternatively, the procedure may involve receiving, from the UDM / UDR, the identity of an AMF that serves the intermediate node. Additionally or alternatively, the procedure may involve receiving, from the AMF that serves the intermediate node, location information associated with the intermediate node Moreover, the location information associated with the intermediate node may be one or more RAN Node Identities. Additionally or alternatively, the location information associated with the intermediate node may be one or more cell identities. Additionally or alternatively, the location information associated with the intermediate node may be one or more tracking area identities.
[0098] In addition, the AMF may send a paging message to a RAN Node that is associated with the location information associated with the intermediate node. The paging message may include one or more of the cell identities or tracking area identities that are associated with the intermediate node. Also, the paging messagemay include an identity that is associated with the WTRU and an identity that is associated with the intermediate node.
[0099] Embodiments and examples provided herein include using the intermediate node location in a paging strategy for the Ambient loT WTRU, and include one or more intermediate node actions. In an example, the intermediate node may send a message to the network that indicates that the intermediate node is associated with a WTRU.
[0100] Further, the intermediate node may receive a paging message. The paging message may indicate that the cause of the page is to check if the intermediate node is associated with the WTRU.
[0101] Also, the intermediate node may respond to the paging message by establishing an RRC connection and indicating in the RRC message whether the WTRU is still associated with the intermediate node. Additionally or alternatively, the intermediate node may indicate that the WTRU is no longer associated with the intermediate node and may indicate how much time has passed since the intermediate node last communicated with the WTRU.
[0102] Embodiments and examples provided herein include using the intermediate node location in a paging strategy for the Ambient loT WTRU, and include one or more UDM actions In an example, a UDM may receive an association request from the WTRU through an AMF or any other network function (NF) to perform association with surrounding intermediate nodes. Additionally or alternatively, the UDM may check the WTRU and intermediate node subscription information. Additionally or alternatively, the UDM may receive the WTRU power level and coverage status from the WTRU or other NF such as the AMF. Additionally or alternatively, the UDM may check the WTRU power level and coverage status to evaluate the association request. Additionally or alternatively, the UDM may check the intermediate node power level and coverage status. For example, the UDM may check the signal quality and reachability of the intermediate node.
[0103] Further, a UDM may receive from the intermediate node an association request. Additionally or alternatively, the UDM may check the WTRU power level and coverage status to evaluate the association request. Additionally or alternatively, the UDM may receive the WTRU power level and coverage status from the intermediate node or another NF such as the AMF. Additionally or alternatively, the UDM may check the WTRU and intermediate node subscription information. Additionally or alternatively, the UDM may check the WTRU power level and coverage status to evaluate the association request Additionally or alternatively, the UDM may check the intermediate node power level and coverage status.
[0104] Also, the UDM may notify the AMF which serves the WTRU that the association between the WTRU and intermediate node has been confirmed. Moreover, the UDM may provide the intermediate node location information such as a RAN Node Identity, cell identities, tracking area, or identity of the AMF that serves the intermediate node.
[0105] FIG. 5 is a signaling diagram illustrating an example of intermediate node and ambient device association Signaling diagram 500 shows an example procedure where downlink data arrives for a WTRU 502, and the WTRU 502 is an Ambient loT device. Before downlink data arrives at the WTRU 502, the WTRU502 and / or an intermediate node 510 may inform the network that the WTRU 502 and the intermediate node 510 are associated. After downlink data arrives for the WTRU 502, the network uses the information about the association between the WTRU 502 and the intermediate node 510 to form a strategy for paging the WTRU 502.
[0106] In step 1.1 , the WTRU 502 and the intermediate node 510 may perform an association procedure. Further, the WTRU 502 and the intermediate node 510 may participate in a discovery procedure. After the discovery procedure, the WTRU and / or the intermediate node 510 may determine to begin an association procedure. The purpose of the association procedure is to inform the network that the WTRU 502 and the intermediate node 510 are located geographically close, and are expected to remain geographically close for some period of time.
[0107] Also, the WTRU 502 may trigger the association procedure based on receiving discovery information that is broadcasted from the intermediate node 510. For example, the intermediate node 510 may broadcast information stating that it is associated with a certain type of application, is a particular application, or is owned by a certain entity. Additionally or alternatively, the WTRU 502 may use the broadcasted information to determine whether and how to trigger the association procedure. Additionally or alternatively, the WTRU 502 may be triggered to perform the association based on the available power level, an assigned power saving policy, or the signal and coverage condition. For a power level trigger, the WTRU 502 may have only a small amount of power available, and limited accessibility to power source.
[0108] Additionally or alternatively, the intermediate node 510 may trigger the association procedure based on receiving information that is broadcasted from the WTRU 502. For example, the WTRU 502 might broadcast information stating that it is associated with a certain type of application, is a particular application, or is owned by a certain entity. The intermediate node 510 might use the broadcasted information to determine to trigger the association procedure.
[0109] During the association procedure, the WTRU 502 may receive the intermediate node Identity and the Association Time Period from the intermediate node 510. Also, during the association procedure, the intermediate node 510 may receive a WTRU Identity, an Application Type Identifier, and an Association Time Period from the WTRU 502.
[0110] The association time may be negotiated between the WTRU 502 and intermediate node 510, and may be based on the Application Type Identifier. For example, the Association Time Period may represent how long the WTRU 502 and intermediate node 510 may assume that the association is valid before requiring a new association procedure. When the association is valid, it may be assumed that the WTRU 502 and intermediate node 510 are located relatively close to each other.
[0111] In another step, which may be step 1.2, after performing the association procedure with the intermediate node 510, the WTRU 502 may send an association request message to an AMF, such as AMF 1 581, in a NAS Message. The association request message may include the intermediate node Identity, the Association Time Period, and the WTRU Power Level.
[0112] The purpose of this association request message may be for the WTRU 502 to check that the network authorizes the WTRU 502 to be associated with the intermediate node 510, and to inform the network of how long the WTRU 502 and intermediate node 510 expect to be associated. Additionally or alternatively, this association request message may be optional if the intermediate node 510 is configured and authorized to request the association authorization on behalf of the WTRU 502 (for example in step 1 6); when the intermediate node 510 requests association authorization on behalf of the WTRU 502, the WTRU 502 may receive an association confirmation notification, as in step 1.10 and step 1.11 explained further below, to confirm that the association is authorized by the network.
[0113] One of skill in the art will appreciate that the WTRU 502 may send a WTRU association request to the AMF 581 to renew an association with an intermediate node 510 before the association expires. Additionally or alternatively, the WTRU 502 may include the association identifier obtained in the initial association authorization response (for example, in 1 .5) to indicate that the request is for renewal (for example, not a new association). When an association is renewed, a UDM / UDR 570 may reuse the same association identifier in the response.
[0114] In step 1.3, the AMF 581 that serves the WTRU 502 will send a request to the UDM / UDR 570 that serves the WTRU 502. The UDR that serves the WTRU 502 is the UDR 570 where the subscription of the WTRU 502 is stored The request will indicate the identity of the WTRU 502, the identity of the intermediate node 510, the Association Time Period, and the WTRU Power Level.
[0115] In step 1 .4, the UDM / UDR 570 may respond to the AMF 581 and indicate whether the association between the WTRU 502 and intermediate node 510 is authorized. The UDM / UDR 570 may assign an association identifier to uniquely identify an association between a WTRU 502 and an intermediate node 510. Further, the association identifier may be returned to the WTRU 502 in the WTRU association authorization response and used by the WTRU 502 when performing operations related to the association The UDM / UDR 570 may determine if the association is authorized based on the subscription of the WTRU 502 and / or intermediate node 510. For example, the subscription information of the WTRU 502 and / or intermediate node 510 may indicate one or more of: that association between the WTRU 502 and intermediate node 510 is permitted, that the WTRU 502 and intermediate node 510 are part of the same group, that the WTRU 502 and intermediate node 510 are owned by the same entity, or that the WTRU 502 and intermediate node 510 subscriptions are associated with a common identifier. The response from the UDM / UDR 570 may also indicate whether the intermediate node 510 has also indicated that the WTRU 502 and intermediate node 510 are associated. In an example shown in FIG. 5, the UDM / UDR 570 may indicate that the intermediate node 510 has not yet indicated an association between the intermediate node 510 and WTRU 502
[0116] The AMF 581 may not consider the association authorized until the UDM / UDR 570 indicates that the intermediate node 510 has also indicated an association between the intermediate node 510 and WTRU 502. The UDM / UDR 570 may also check the available power level or signal information of the WTRU 502 to evaluate the need for the association. The network might decide not to permit the association in case theintermediate node power is under a certain threshold, the intermediate coverage is not stable, or other policy- driven power saving conditions.
[0117] Additionally or alternatively, in step 1 .5, the AMF 581 that serves the WTRU 502 may respond with an indication of whether or not the association is authorized, and an indication of whether or not the association is confirmed. The response, which may be a WTRU association response, may include an association identifier issued by the UDM / UDR570 in step 1.4 An authorized association may mean that the network has determined that association between the WTRU 502 and intermediate node 510 may be permitted. A confirmed association may mean that both, the WTRU 502 and intermediate node 510 have indicated that the association was established A confirmed association must have been authorized. An authorized association may or may not have been confirmed.
[0118] In an example shown in FIG. 5, the WTRU association response message in step 1.5 indicates that the association is not yet confirmed. This step can be optional if the following messages to the WTRU 502 deliver to the WTRU 502 any form of authorization or confirmation for the association between the WTRU 502 and intermediate node 510, and / or Step 1 2 did not take place.
[0119] In step 1 .6, after performing the association procedure with the WTRU 502, the intermediate node 510 sends an association request to an AMF 2 582 in a NAS Message. The association request, which may be a WTRU association request, may include the intermediate node Identity, the Association Time Period, the associated WTRU identity, and the associated WTRU Power Level.
[0120] The purpose of this WTRU association request message is for the intermediate node 510 to check that the network authorizes the WTRU 502 to be associated with the intermediate node 510, and to inform the network of how long the WTRU 502 and intermediate node 510 expect to be associated. In an example, the AMF that serves the WTRU 502 and intermediate node 510 may be different. For example, AMF 1 581 may serve the WTRU 502, and AMF 2 582 may serve the intermediate node 510. Additionally or alternatively, AMF 1 581 may serve the intermediate node 510, and AMF 2 582 may serve the WTRU 502. Additionally or alternatively, the AMF that serves the WTRU 502 and intermediate node 510 may be the same. For example, AMF 1 581 may serve the WTRU 502 and the intermediate node 510. Additionally or alternatively, AMF 2 582 may serve the WTRU 502 and the intermediate node 510.
[0121] In step 1.7, the AMF, such as AMF 2 582, that serves the intermediate node 510, will send a request to the UDM / UDR 570 that serves the WTRU 502. The UDR that serves the WTRU is the UDR 570 where the subscription of the WTRU 502 is stored. The request will indicate the identity of the WTRU 502, the identity of the intermediate node 510, the Association Time Period, and the WTRU Power Level.
[0122] In step 1.8, the UDM / UDR 570 will respond to the AMF, such as AMF 2 582, and indicate if the association between the WTRU 502 and intermediate node 510 is authorized. The UDM / UDR 570 may assign an association identifier to uniquely identify an association between a WTRU and an intermediate node, such as between the WTRU 502 and intermediate node 510. Further, the association identifier may be the same asthe one issued in step 1.4. Additionally or alternatively, the association identifier may be returned to the intermediate node 510 in a WTRU association authorization response message, such as in step 1.9 below.
[0123] Additionally or alternatively, the intermediate node 510 may use the association identifier when performing operations related to the association. The UDM / UDR 570 may determine if the association is authorized based on the subscription of the WTRU 502 and / or intermediate node 510. For example, the subscription information of the WTRU 502 and / or intermediate node 510 may indicate one or more of: that association between the WTRU 502 and intermediate node 510 is permitted, that the WTRU 502 and intermediate node 510 are part of the same group, that the WTRU 502 and intermediate node 510 are owned by the same entity, or that the WTRU 502 and intermediate node 510 subscriptions are associated with a common identifier. The response from the UDM / UDR 570 may also indicate whether the WTRU 502 has also indicated that the WTRU 502 and intermediate node 510 are associated
[0124] In an example shown in FIG. 5, the UDM / UDR 570 may indicate that the intermediate node 510 has already indicated an association between the intermediate node 510 and WTRU 502. The UDM\UDR 570 may also check the available power level or the information signaled by the WTRU 502 to evaluate the need for the association The network might decide to not permit the association in case the intermediate node power is under a certain threshold or the intermediate coverage is not stable.
[0125] One of skill in the art will appreciate that the intermediate node 510 may send a WTRU association request to the AMF 582 to renew an association with a WTRU 502 before the association expires. Further the intermediate node 510 may include the association identifier obtained in the initial association authorization response (for example, in step 1.9) to indicate that the request is for renewal (for example, not a new association). When an association is renewed, the UDM / UDR 570 may reuse the same association identifier in the response.
[0126] In step 1 .9, the AMF 582 that serves the intermediate node 510 may respond with an indication of whether or not the association is authorized and an indication of whether or not the association is confirmed. The response, which may be a WTRU association response message, may include an association identifier issued by the UDM / UDR 570 in step 1.8. In an example shown in FIG. 5, the message in this step indicates that the association has been confirmed. The message may also indicate that an association time duration is approved by the UDM / UDR 570.
[0127] In step 1.10, the UDM / UDR 570 may notify the AMF 581 that serves the WTRU 502 that the association between the WTRU 502 and intermediate node 510 is authorized. The notification, which may be a WTRU association authorization notification, may also indicate that an association time duration that was previously approved by the UDM / UDR 570 has expired, or that an authorized association has been revoked. The message includes the identity that is associated with the WTRU 502, the second identity that is associated with the intermediate node 510, and the status related to the authorized association. The notification may include the association identifier issued by the UDM / UDR 570 in step 1 .3.
[0128] In step 1.11 , the AMF 581 that serves the WTRU 502 may notify the WTRU 502 that the association between the WTRU 502 and intermediate node 510 has been confirmed. The notification, which may be a WTRU association confirmation notification, may include an association identifier issued by the UDM / UDR 570 in step 1.3. The notification may also indicate that the association time duration was approved by the UDM / UDR 570. This step can be optional if previous or following messages to the WTRU 502 deliver to the WTRU 502 any form of authorization or confirmation for the association between the WTRU 502 and intermediate node 510.
[0129] Although not necessarily shown in FIG. 5, one of skill in the art will appreciate that the notification related to the association may be sent to the intermediate node 510 or both the WTRU 502 and the intermediate node 510. Additionally or alternatively, one of skill in the art will appreciate that the notification may include the association identifier issued by the UDM / UDR 570 in step 1.3 or step 1 .8.
[0130] In Step 2.1 , downlink data for the WTRU 502 is received by a UPF, such as UPF 590. In Step 2.2a, upon receiving the downlink data, the UPF 590 sends a downlink data notification to an SMF, such as SMF 583. The SMF 583 acknowledges receiving the downlink data notification and requests that the UPF 590 store the downlink data in Step 2.2b.
[0131] In Step 2.3a, the SMF 583 sends a message to the AMF 581 to notify the AMF 581 that there is downlink data available for the WTRU 502. In an example, the message may be a Namf_Communications_N1 N2MessageTransfer message
[0132] In step 2.3b, the AMF 581 responds to the SMF 583 a message, which may be a Namf_Communications_N1 N2MessageResponse message, and informs the SMF 583 that the WTRU 502 is in an Ambient loT Low Power State and that the AMF 581 will attempt to page the WTRU 502. If the AMF 581 determines that there is an intermediate node associated with the WTRU, such as intermediate node 510, the AMF 581 may also inform the SMF 583 that it will attempt to reach the WTRU 502 via an intermediate node. Additionally or alternatively, indication information in the message may be used by the SMF 583 to determine whether and how to configure a buffer for the downlink data in the SMF 583 or the UPF 590.
[0133] In step 2.4, the AMF 581 may determine a paging strategy for the WTRU 502 based on the notification in the message received from the SMF 583 that downlink data needs to be sent to the WTRU 502. Additionally or alternatively, the AMF 581 may be triggered to determine a paging strategy for the WTRU 502 when the AMF 581 determines that a NAS Message needs to be sent to the WTRU 502. Additionally or alternatively, the AMF 581 may determine that a NAS message needs to be sent to the WTRU 502 when the AMF 581 receives a request to send information to the WTRU 502 from the policy control function (PCF), short message service function (SMSF), or UDM / UDR 570.
[0134] The AMF 581 may have context information stored for the WTRU 502. Based on the association confirmation that was received from the UDM / UDR 570, the context information may indicate that the WTRU 502 is associated with the intermediate node 510. The context information may also indicate how long the WTRU 502 and intermediate node 510 are expected to be associated
[0135] Based on the current time being within the time period where the WTRU 502 and intermediate node 510 are expected to be associated, the AMF 581 may query (2.4a) the UDM / UDR 570 that serves the intermediate node 510 to obtain information about the intermediate node’s location. In an example, the query may be an intermediate node information request. The UDM / UDR 570 that serves the intermediate node 510 is the UDM / UDR where the intermediate node’s subscription information is stored.
[0136] Further, the UDM / UDR 570 may reply (2.4b) to the query with information about the intermediate node’s location, with the identity of the AMF that serves the intermediate node 510 (for example, the identity of AMF 2 582), or with both. In an example, the reply from the UDM / UDR 570 may be an intermediate node information response. The information about the intermediate node’s location may be a RAN Node Identity, a Cell Identity, or a tracking area.
[0137] In step 2.5, if the identity of the AMF 582 that serves the intermediate node 510 was obtained from the UDM / UDR 570, the AMF 581 that serves the WTRU 502 may query (2.5a) the AMF 582 that serves the intermediate node 510 to obtain (25b) the information about the intermediate node’s location. In an example, the query from the AMF 1 581 to the AMF 2582 may be an intermediate node location request message, and the response from the AMF 2582 to the AMF 1 581 may be an intermediate node location response message.
[0138] In step 2.6, the AMF 1 581 may send a paging message request to the one or more RAN Nodes that are associated with the intermediate node 510, with the cell identities associated with the intermediate node 510, or with the tracking area that is associated with the intermediate node 510. In an example, the paging message may be an NGAP paging message. Additionally or alternatively, a RAN Node may be AN 514. The paging message may include the identity of the WTRU 502 that needs to be paged and the identity of the intermediate node 510. The paging message may indicate whether the WTRU 502 should be triggered, by the intermediate node 510, to perform a Service Request or send data to the network
[0139] In step 2.7, the RAN Node, such as AN 514, may perform a WTRU paging procedure. The paging procedure may involve the RAN Node 514 first paging the WTRU 502. If the WTRU 502 does not respond to the page by establishing an RRC connection with the RAN Node 514, the RAN Node 514 may then page the intermediate node 510. If the WTRU 502 is in an Ambient loT Low Power State, the AMF 581 may determine to directly page the intermediate node 510. When paging the intermediate node 510, the paging message may indicate that the cause of the page is to check if the intermediate node 510 is associated with the WTRU 502. The paging message may indicate the identity of the WTRU 502.
[0140] The intermediate node 510 may respond to paging message by establishing an RRC connection and indicating in an RRC message whether the WTRU 502 is still associated with the intermediate node 510 or indicating how much time has passed since the intermediate node 510 last communicated with the WTRU 502. The paging message may indicate that the cause of the page is to trigger the WTRU 502 to perform a service request. Additionally or alternatively, the paging message may indicate that the cause of the page is to request that the intermediate node 510 trigger the WTRU 502 to perform a service request. If this paging message indicates that the cause of the page is to request that the intermediate node 510 to trigger the WTRU502 to perform a service request, then the intermediate node 510 may send a message to the WTRU 502 to request that the WTRU 502 perform a service request or send data to the network.
[0141] In Step 2.8, if the WTRU 502 has not established an RRC Connection, the RAN Node 514 may send a paging failure notification to the AMF 581. In an example, the notification may be an NGAP paging failure notification. The notification may indicate that the intermediate node 510 is no longer associated with the WTRU 502, and may indicate how much time has passed since the intermediate node 510 last communicated with the WTRU 502. The information about how much time has passed since the intermediate node 510 last communicated with the WTRU 502 may be used by the AMF 581 to determine whether to attempt to page the WTRU 502 via other RAN Nodes. The other RAN Nodes may be, for example, RAN Nodes that are located geographically close to the intermediate node 510.
[0142] In step 2.9, the AMF 581 sends a Namf_Communications_N1 N2MessageTransfer Failure Notification to the SMF 583 and indicates that the WTRU 502 did not respond to paging.
[0143] In an example, a network node may receive a first indication indicating that a WTRU is associated with an intermediate node. The network node may be or may include an AMF. Also, the network node may be a first network node, and may include a first AMF. The first indication may be included in a message. Further, the message may include a first identity of the WTRU that is associated with the intermediate node. Also, the message may include a second indication of how long the WTRU and intermediate node are expected to be associated. Moreover, the AMF may receive a information from an SMF that indicates that there is downlink data available for the WTRU. The AMF may respond to the SMF and the response may indicate that the intermediate node is associated with the WTRU.
[0144] Additionally or alternatively, the procedure may involve receiving, from the UDM node, a second identity of a second network node that serves the intermediate node The second network node may be or may include a second AMF. Further, the second AMF may serve the intermediate node. In addition, the procedure may involve receiving, from the AMF that serves the intermediate node, first location information associated with the intermediate node. Moreover, the first location information associated with the intermediate node may be one or more RAN Node Identities, one or more cell identities, or one or more tracking area identities. In addition, the first AMF may send a first paging message to a RAN Node that is associated with the first location information associated with the intermediate node. The first paging message may include one or more of the cell identities or tracking area identities that are associated with the intermediate node, and includes a third identity that is associated with the WTRU and a fourth identity that is associated with the intermediate node
[0145] Additionally or alternatively, the AMF may perform a procedure to determine second location information associated with the intermediate node. Further, the AMF may send a second paging message to a RAN Node that is associated with the second location information associated with the intermediate node. Additionally or alternatively, the procedure may involve receiving, from a UDM node or a UDM / UDR, third location information associated with the intermediate node. Moreover, the AMF may send a third pagingmessage to a RAN Node that is associated with the third location information associated with the intermediate node.
[0146] Additionally or alternatively, the first AM F may serve the WTRU. Additionally or alternatively, the first AMF may receive, from the intermediate node, an RRC message including information regarding whether the WTRU is still associated with the intermediate node. Additionally or alternatively, the RAN node has a RAN node identity included in the location information associated with the intermediate node. The location information may include as well a cell identity, a tracking area, or both, additionally or alternatively. Additionally or alternatively, the WTRU is an Ambient loT device.
[0147] In another example, an intermediate node may send a message to the network that indicates that the intermediate node is associated with a WTRU. Further, the intermediate node may receive a paging message, wherein the paging message indicates that the cause of the page is to check if the intermediate node is associated with the WTRU. Also, the intermediate node may respond to the paging message by establishing an RRC connection. Moreover, the intermediate node may send an RRC message including information indicating whether the WTRU is still associated with the intermediate node.
[0148] Although features and elements are described 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. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical 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, an integrated access and backhaul node, or any host computer.
Claims
CLAIMSWhat is claimed:
1. A method for use in a first network node, the method comprising: receiving a first indication indicating that a wireless transmit / receive unit (WTRU) is associated with an intermediate node, wherein the first indication is received in a message, wherein the message includes a first identity of the WTRU that is associated with the intermediate node, and a second indication of how long the WTRU and the intermediate node are expected to be associated; receiving, rom a session management function (SMF), information indicating that there is downlink data available for the WTRU; sending, to the SMF, a response indicating that the intermediate node is associated with the WTRU; receiving, from a unified data management (UDM) node, a second identity of a second network node; receiving, from the second network node, first location information associated with the intermediate node, wherein the first location information associated with the intermediate node includes one or more radio access network (RAN) node identities, one or more cell identities, or one or more tracking area identities; and sending a first paging message to a RAN node that is associated with the first location information associated with the intermediate node, wherein the first paging message includes one or more of the cell identities or tracking area identities that are associated with the intermediate node, and includes a third identity that is associated with the WTRU and a fourth identity that is associated with the intermediate node.
2. The method of claim 1 , wherein the first network node includes a first access and mobility function (AMF), and the second network node includes a second AMF.
3. The method of claim 2, wherein the first AMF serves the WTRU, and the second AMF serves the intermediate node.
4. The method of claim 1, further comprising: performing a procedure to determine second location information associated with the intermediate node, wherein a second paging message is sent to a RAN node that is associated with the second location information associated with the intermediate node.
5. The method of claim 1 , further comprising: receiving, from the UDM node, third location information associated with the intermediate node, wherein a third paging message is sent to a RAN node that is associated with the third location information associated with the intermediate node.
6. The method of claim 1 , further comprising: receiving, from the intermediate node, a radio resource control (RRC) message including information regarding whether the WTRU is still associated with the intermediate node.
7. The method of claim 6, wherein the RRC message includes information indicating that the WTRU is no longer associated with the intermediate node, and information indicating how much time has passed since the intermediate node last communicated with the WTRU.
8. The method of claim 1, wherein the RAN node that is associated with the first location information associated with the intermediate node has a RAN node identity included in the first location information associated with the intermediate node.
9. The method of claim 1, wherein the WTRU is an Ambient Internet of Things (loT) device.
10. A first network node comprising: a transceiver; and a processor operatively coupled to the transceiver; wherein: the transceiver is configured to receive a first indication indicating that a wireless transmit / receive unit (WTRU) is associated with an intermediate node, wherein the first indication is received in a message, wherein the message includes a first identity that is associated with the intermediate node, and a second indication of how long the WTRU and the intermediate node are expected to be associated; the transceiver is configured to receive, from a session management function (SMF), information indicating that indicates that there is downlink data available for the WTRU; the transceiver and the processor are configured to send, to the SMF, a response indicating that the intermediate node is associated with the WTRU; the transceiver is configured to receive, from a unified data management (UDM) node, a second identity of a second network node; the transceiver is configured to receive, from the second network node, first location information associated with the intermediate node, wherein the first location information associated with the intermediate node includes one or more radio access network (RAN) node identities, one or more cell identities, or one or more tracking area identities; and the transceiver and the processor are configured to send a first paging message to a RAN node that is associated with the first location information associated with the intermediate node, wherein the first paging message includes one or more of the cell identities or tracking area identities that are associated with the intermediate node, and includes a third identity that is associated with the WTRU and a fourth identity that is associated with the intermediate node.
11. The first network node of claim 10, wherein the first network node includes a first access and mobility function (AMF), and the second network node includes a second AMF.
12. The first network node of claim 11 , wherein the first AMF serves the WTRU, and the second AMF serves the intermediate node.
13. The first network node of claim 10, wherein the transceiver and the processor are further configured to perform a procedure to determine second location information associated with the intermediate node, wherein a second paging message is sent to a RAN node that is associated with the second location information associated with the intermediate node.
14. The first network node of claim 10, wherein the transceiver is further configured to receive, from the UDM node, third location information associated with the intermediate node, wherein a third pagingmessage is sent to a RAN node that is associated with the third location information associated with the intermediate node.
15. The first network node of claim 10, wherein the transceiver is further configured to receive, from the intermediate node, a radio resource control (RRC) message including information regarding whether the WTRU is still associated with the intermediate node.
16. The first network node of claim 15, wherein the RRC message includes information indicating that the WTRU is no longer associated with the intermediate node, and information indicating how much time has passed since the intermediate node last communicated with the WTRU.
17. The first network node of claim 10, wherein the RAN node that is associated with the first location information associated with the intermediate node has a RAN node identity included in the first location information associated with the intermediate node.
18. The first network node of claim 10, wherein the WTRU is an Ambient Internet of Things (loT) device.
19. An intermediate node comprising: a transceiver; and a processor operatively coupled to the transceiver; wherein: the transceiver and the processor are configured to send a message to a network that indicates that the intermediate node is associated with a wireless transmit / receive unit (WTRU); the transceiver is configured to receive a paging message, wherein the paging message indicates that a cause of the paging message is to check if the intermediate node is associated with the WTRU; the transceiver and the processor are configured to respond to the paging message by establishing a radio resource control (RRC) connection; and the transceiver and the processor are configured to send an RRC message including information indicating whether the WTRU is still associated with the intermediate node.
20. The intermediate node of claim 19, wherein the RRC message includes information indicating that the WTRU is no longer associated with the intermediate node, and information indicating how much time has passed since the intermediate node last communicated with the WTRU; and wherein the WTRU is an Ambient Internet of Things (loT) device.