Methods, architectures, apparatuses and systems for low power registration management

Abstract

Methods, architectures, apparatuses, and systems directed to low power methods for registration management are described herein. In an embodiment, a method implemented in a wireless transmit / receive unit (WTRU) may include sending a first registration request to a network element and receiving a first registration response from the network element. In various embodiments, the first registration response may comprise absolute time information. The method may include receiving an activation transmission and determining that a time value may satisfy a time condition associated with the absolute time information. The method may include sending a second registration request to the network element based on the time value satisfying the time condition associated with the absolute time information.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR EOW POWER REGISTRATION MANAGEMENTCROSS-REFERENCE TO REEATED APPLICATIONS

[0001] This application claims the benefit of US Patent Application No. 63 / 553,350 filed February 14, 2024, which is incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure is generally directed to the fields of communications, software and encoding, including methods, architectures, apparatuses, and systems directed to low power methods for registration management.BACKGROUND

[0003] An ambient internet of things (loT) device may be an loT device powered by energy harvesting, with limited energy storage capability. Ambient loT devices may be ultra-low complexity, power-constrained, cost-constrained, and resource-constrained. Embodiments described herein have been designed with the foregoing in mind.SUMMARY

[0004] Methods, architectures, apparatuses, and systems directed to low power methods for registration management are described herein. In an embodiment, a wireless transmit / receive unit (WTRU) is described. The WTRU may include circuitry including a transmitter, a receiver, a processor, and a memory. The WTRU may be configured to send a first registration request to a network element and to receive a first registration response from the network element. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. The WTRU may be configured to receive an activation transmission and to determine that a time value may satisfy a time condition associated with the (e.g., first absolute) time information. The WTRU may be configured to send a second registration request to the network element based on the time value satisfying the time condition associated with the (e.g., first absolute) time information.

[0005] In an embodiment, a network element is described. The network element may include circuitry including a transmitter, a receiver, a processor, and a memory. The network element may be configured to receive a first registration request from a WTRU. In various embodiments, the first registration request may indicate an intermediate network element. The network element may be configured to send a first registration response to the WTRU. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. The network element may be configured to send a trigger request to the intermediate network element based on the (e.g.,first absolute) time information and to receive a second registration request from the WTRU. In various embodiments, the second registration request may comprise mobile originated data.

[0006] In an embodiment, a first method implemented in a WTRU is described. The first method may include sending a first registration request to a network element and receiving a first registration response from the network element. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. The first method may include receiving an activation transmission and determining that a time value may satisfy a time condition associated with the (e.g., first absolute) time information. The first method may include sending a second registration request to the network element based on the time value satisfying the time condition associated with the (e.g., first absolute) time information.

[0007] In an embodiment, a second method implemented in a network element is described. The second method may include receiving a first registration request from a WTRU. In various embodiments, the first registration request may indicate an intermediate network element. The second method may include sending a first registration response to the WTRU. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. The second method may include sending a trigger request to the intermediate network element based on the (e.g., first absolute) time information and receiving a second registration request from the WTRU. In various embodiments, the second registration request may comprise mobile originated data.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] 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:

[0009] FIG. 1A is a system diagram illustrating an example communications system;

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

[0011] 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;

[0012] FIG. ID 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. 1 A;

[0013] FIG. 2 is a diagram illustrating an example method for a WTRU to determine when to perform a registration procedure;

[0014] FIG. 3 is a diagram illustrating an example of WTRU operations in a method for determining when to perform a registration procedure;

[0015] FIG. 4 is a diagram illustrating an example method for low power registration management, implemented in a WTRU; and

[0016] FIG. 5 is a diagram illustrating an example method for low power registration management, implemented in a network element.DETAILED DESCRIPTION

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

[0018] Example Communications System

[0019] The methods, 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.

[0020] FIG. 1A is a system 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 channelaccess 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 (ZT) unique-word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, fdter bank multicarrier (FBMC), and the like.

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

[0022] 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, e.g., to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a new radio (NR) Node-B (NR NB), 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.

[0023] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radionetwork controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an 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 or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0024] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

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

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

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

[0028] 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 WTRUs102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

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

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

[0032] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include 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 / 114 or a different RAT.

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

[0034] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / mi crophone 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 elements / 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.

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

[0036] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an 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 an 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.

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

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

[0039] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), readonly 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).

[0040] 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 source134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0041] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of 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 location-determination method while remaining consistent with an embodiment.

[0042] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., 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 elements / peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

[0044] 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, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0045] 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 an 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 receive wireless signals from, the WTRU 102a.

[0046] Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and / or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

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

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

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

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

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

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

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

[0054] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

[0055] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used bythe 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 in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

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

[0057] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0058] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.1 lah may support meter type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0059] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802. l ln, 802.11ac, 802.11af, and 802.11ah, 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 channelmay be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

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

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

[0062] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. 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).

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

[0064] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non- standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standal one 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.

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

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

[0067] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with differentrequirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized by 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 / or the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-APro, and / or non-3GPP access technologies such as WiFi.

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

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

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

[0071] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein, may be performed by one or more emulation elements / 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.

[0072] 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 may performing testing using over-the-air wireless communications.

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

[0074] Throughout embodiments described herein the terms "base station", "network", and "gNB", collectively "the network" may be used interchangeably to designate any network element such as e.g., a network element acting as a serving base station. Embodiments described herein are not limited to gNBs and are applicable to any other type of base stations.

[0075] For the sake of clarity, satisfying, failing to satisfy a condition, and configuring condition parameter(s) are described throughout embodiments described herein as relative to a threshold (e g., greater, or lower than) a (e.g., threshold) value, configuring the (e.g., threshold) value, etc. For example, satisfying a condition may be described as being above a (e.g., threshold) value, and failing to satisfy a condition may be described as being below a (e.g., threshold) value. Embodiments described herein are not limited to threshold-based conditions. Any kind of othercondition and parameter(s) (such as e.g., belonging or not belonging to a range of values) may be applicable to embodiments described herein.

[0076] Throughout embodiments described herein, (e.g., configuration) information may be described as received by a WTRU from the network, for example, through system information or via any kind of protocol message. Although not explicitly mentioned throughout embodiments described herein, the same (e.g., configuration) information may be pre-configured in the WTRU (e g., via any kind of pre-configuration methods such as e.g., via factory settings), such that this (e g., configuration) information may be used by the WTRU without being received from the network.

[0077] Throughout embodiments described herein, the expression "the WTRU may be configured with a set of parameters" is equivalent or may be used interchangeably with "the WTRU may receive configuration information (e.g., from another network element (e.g., gNB)) indicating a set of parameters". Throughout embodiments described herein, the expressions "the WTRU may report something", and "the WTRU may be configured to report something", is equivalent or may be used interchangeably with "the WTRU may transmit (e.g., reporting) information indicating something".

[0078] In embodiments described herein, "a" and "an" and similar phrases are to be interpreted as "one or more" and "at least one". Similarly, any term which ends with the suffix "(s)" is to be interpreted as "one or more" and "at least one". The term "may" is to be interpreted as "may, for example".

[0079] A symbol(e.g., forward slash) may be used herein to represent "and / or", where for example, "A / B" may imply "A and / or B".

[0080] In embodiments described herein, a network element may refer to any kind of device including computing resources and networking capabilities, that may be connected to a network. The terms network element and node may be used interchangeably. A network element may be any kind of network infrastructure device and or a WTRU. The architecture depicted at FIG. IB for a WTRU 102 may be applicable more generally to any kind of network element.

[0081] In embodiments described herein, the terms "application server (AS)", "application function (AF)", "network element comprising / running an AF" may be used interchangeably.

[0082] Embodiments are described herein with the example of a network element running an access and mobility function (AMF). Embodiments described herein are not limited to an AMF and may be applicable to any network element running any kind of (e.g., core) network function.

[0083] In embodiments described herein, the terms "signal" and "transmission" may be used interchangeably to refer to any transmission.

[0084] AMF action examples are described herein.

[0085] In an embodiment a network element, e.g. an AMF, may perform any of the following actions.

[0086] In an example, the AMF may receive a first registration request from a WTRU. The first registration request may include, for example, an identity (e.g., identifier) of an intermediate network element (which may be referred to herein as I-Node).

[0087] In an example, the AMF may send a first registration response to the WTRU. The first registration response may include, for example, any of (e g., time information indicating) a time value and an indication that mobile originated (MO) data (MO-data) may be requested in a subsequent (e.g., the next, second) registration request that the WTRU may initiate.

[0088] In an example, the AMF may send a trigger request to the I-Node.

[0089] In an example, the AMF may receive a second registration request from the WTRU. The second registration request may include, for example, MO-data.

[0090] In an example, the AMF may send the MO-data to an application server (AS).

[0091] Embodiments are described herein with the example of MO-data which. Any kind of data / signal / transmission to be sent by a WTRU may be applicable to embodiments described herein as MO-data.

[0092] WTRU action examples are described herein.

[0093] In an embodiment a WTRU (such as e.g., an ambient loT device) may perform any of the following actions.

[0094] In an example, the WTRU may send a first registration request to an AMF. The first registration request may include, for example, an identity (e.g., identifier) of an I-Node.

[0095] In an example, the WTRU may receive a first registration response from the AMF. The first registration response may include, for example, any of (e.g., time information indicating) a time value and an indication that MO-data may be requested in a subsequent (e.g., the next, second) registration request that the WTRU may initiate.

[0096] In an example, the WTRU may receive an activation signal (e.g. transmission).

[0097] In an example, the WTRU may determine a (e g., current) time value and may determine that the (e.g., current) time value may satisfy a time condition (e.g., may be greater than or equal to the time value that may have been received in the registration response). The (e g., current) time value may be determined by reading (e.g., broadcast) information that may be received from any of the base station and the I-Node.

[0098] In an example, the WTRU may send a second registration request. The second registration request may include, for example, MO-data.

[0099] An ambient loT device may be seen as an loT device powered by energy harvesting, with limited energy storage capability. Ambient loT devices may be any of ultra-low complexity, power-constrained, cost-constrained, and resource-constrained. Throughout embodiments described herein the terms "ambient loT device" and "WTRU" may be used interchangeably. Embodiments are described herein with the example of ambient loT devices. Embodiments described herein may be applicable to any kind of wireless devices (e.g., not limited to wireless devices powered by energy harvesting).

[0100] In one communication model for ambient loT devices, the ambient loT device originated traffic may be triggered by device terminated traffic and / or signaling.

[0101] An ambient loT device may communicate with the network by communicating (e.g., directly) with a base station (such as e.g., a RAN network element).

[0102] An ambient loT device may communicate with the network by using an intermediate network element (I-Node) to forward messages to the network and by receiving messages from the I-Node that may have been forwarded from the network.

[0103] A WTRU in the 5G system may be configured to initiate a registration procedure under one or more conditions. The WTRU may initiate a registration procedure by transmitting a registration request message. A registration request is a type of non-access stratum (NAS) message.

[0104] Expiration of a periodic registration timer may be one example condition that may trigger a WTRU to initiate a registration procedure. Detection of this condition may rely on the WTRU to maintain a timer.

[0105] Detecting that the WTRU may have left its registration area may be another example condition that may trigger a WTRU to initiate a registration procedure. Detection of this condition may rely on the WTRU to read system information (such as e.g., any of cell identities and tracking area identities) from nearby base stations so that the WTRU may detect that it may no longer be in a tracking area that may be part of the WTRU registration area.

[0106] Maintaining a timer and (e.g., frequently, regularly) reading system information may consume power from an energy storage device during a time when the WTRU may not (e.g., otherwise) be performing other functions. For example, if a WTRU is in idle state (such as e.g., connection management (CM) idle state, the WTRU may periodically read system information and may run the periodic registration timers.

[0107] Ambient loT devices may have limited energy storage capacity. For example, ambient loT devices might not be able to run a periodic registration timer and to (e.g., frequently, regularly) read system information when the ambient loT device may be in a low power state. Theconsequence for the ambient loT devices to run a periodic registration timer and (e.g., frequently, regularly) read system information may be that an ambient loT device may not have enough energy stored to perform data transmission and / or data reception at a (e.g., later) time e.g., when data transmission and / or data reception may be expected. Embodiments described herein enable an ambient loT in a low power state to detect when registration area update may be performed e.g., without running a timer and e.g., without frequently reading system information.

[0108] Embodiments described herein allow an ambient loT WTRU (referred to herein as WTRU) to determine whether to perform a registration update e.g., without maintaining (e.g., running) a timer in between registration events. In various embodiments, the WTRU may receive (e g., first time information indicating) a time value (such as e g. an absolute time value) indicating that the WTRU may be performing a registration update (e.g., sometime) after the time value. The WTRU may periodically receive triggers (e.g., information indicating) to check the (e.g., current) time and to compare it against the time value that may have been received during a last registration procedure (e.g., via first time information). Checking the (e g., current) time may be performed by reading system information that may be broadcasted by a base station and / or an intermediate network element. For example, the WTRU may not run any timers or may not keep track of time between registration events based on receiving a trigger to check the current time.

[0109] If the WTRU determines that the (e.g., current) time value is not after the time value (e.g., indicated by the first time information) that may have been received from the network during the (e g., last) registration procedure, the WTRU may determine to perform no registration procedure and return to a sleep state until receiving another trigger to check the (e.g., current) time and compare it against the time value (e.g., indicated by the first time information) that may have been received during its (e.g., last) registration procedure.

[0110] If the WTRU determines that the (e.g., current) time value is after the time value (e.g., indicated by the first time information) that may have been received from the network during the (e g., last) registration procedure, the WTRU may determine to perform a registration procedure, to receive a new time value (e.g., second time information) from the network during the second registration procedure and return to a sleep state until receiving another trigger (e.g., information indicating) to check the (e.g., current) time and compare it against the time value (e.g., indicated by the second) time information) that may have been received during its (e.g., last) registration procedure (e.g., the second registration procedure).

[0111] Embodiments described herein allow the ambient loT device to not maintain a timer, to not keep track of time, and to read system information (e.g., only) when triggered. Embodiments described herein enable the network (e.g., any entity), and / or event, that may trigger the ambientloT device to perform the registration procedure to have a measure of control over when, and how often, the ambient loT device may perform the registration procedure.

[0112] FIG. 2 is a diagram illustrating an example method for a WTRU to determine when to perform a registration procedure. An ambient loT device may be a WTRU. In FIG. 2, the WTRU represents the ambient loT device. An intermediate network element (referred to as I-Node) may be a WTRU. For example, an I-Node may be a smart phone or a WTRU that may be part of a vehicle. The RAN network element shown in FIG. 2 may be any of a base station and an access point.

[0113] In an example, the WTRU may send a first registration request 21 to the 5G core (5GC). The first registration request 21 may be (e.g., included in) a NAS message that may be sent to an AMF. The first registration request 21 may include an identity (e.g., identifier) of the WTRU. The first registration request 21 may include an indication that the WTRU may be associated with an I-Node. The first registration request 21 may include identities (e.g., identifiers) of one or more I- Nodes that the WTRU may be associated with.

[0114] A WTRU being associated with an I-Node may mean (e.g., may be equivalent to) that the WTRU may be able to communicate with the I-Node. For example, WTRU associated with an I- Node may have (e.g., recently, in a time shorter than a value) received any of a message from the I-Node, an excitation signal (e.g., transmission) from the I-Node, and / or may be authorized to communicate with the I-Node.

[0115] In an example, the 5GC may respond to the first registration request 21 by sending a first registration response 22.

[0116] The first registration response 22 may include (e.g., first time information indicating) a time value. Inclusion of the time value (e.g., first time information) in the response may indicate to the WTRU that the 5GC may request that the WTRU to initiate another registration procedure sometime after the time value.

[0117] In an example, the first registration response 22 may include (e.g., first time information indicating) a time window value. Inclusion of the time window (e.g., first time information) in the response may indicate to the WTRU that the 5GC may request that the WTRU may initiate another registration procedure sometime within the time window. If the WTRU does not initiate the registration before the end of the time window, the network and WTRU may assume (e.g., consider) that the WTRU may have been (e.g., explicitly) de-registered.

[0118] The first registration response 22 may include an indication that the WTRU may be requested to include MO-data in the next (e.g., second) registration request that the WTRU may send. The 5GC (e.g., the AMF) may (e.g., know to) request MO-data based on a policy that maybe part of subscription information of the WTRU For example, the policy may indicate that the WTRU may (e.g., be expected to) report MO-data at least twice a day. The 5GC (e.g., the AMF) may (e.g., know to) request MO-data based on receiving a request to collect MO-data from an AS. The request from the AS may not have been received directly from the AS. For example, the AS may have sent the request to the unified data management (UDM) network element and / or the unified data repository (UDR) network element via the network exposure function (NEF). For example, the UDM / UDR network element may have stored the request for MO data in subscription information of the WTRU. For example, the AMF may have received subscription information of the WTRU from the UDM / UDR network element.

[0119] MO-data may comprise, for example, application data. For example, the WTRU may be (e g., may include) a sensor and the application data may be (e g., may include) a sensor reading. For example, the WTRU may be (e.g., may include) an asset tracking device and the application data may be (e.g., may include) an application layer identity (e.g., identifier) of the WTRU and / or the location of the WTRU.

[0120] In an example, the AMF may store the time at which the WTRU may perform the first registration procedure (e.g., based on the first registration request 21 and the first registration response 22). In another example the AMF may start a timer to keep track of how much time may have passed since the WTRU may have performed the first registration procedure.

[0121] In an example, the AMF may send a trigger request 23 to the I-Node. The AMF may determine to send the trigger request 23 based on, for example, the AMF detecting that the (e.g., current) time may be greater than or equal to the time value that may have been sent to the WTRU in the first registration response 22. In another example, the AMF may determine to send the trigger request 23 based on the (e.g., current) time being within the time window that may have been sent to the WTRU in the first registration response 22. The trigger request 23 may include (e g., indicate) any of the identity (e.g., identifier) of the WTRU to be triggered, the (e.g., current) time value, and an indication of whether or not the WTRU to be triggered may be requested to send MO-data.

[0122] In an example, the I-Node may respond to the trigger request 23 by sending a trigger response 24. The trigger response 24 may indicate if the I-Node may (e.g., will) attempt to trigger the WTRU or may indicate that the WTRU may no longer be associated with the I-Node. The I- Node may indicate that it may forward the trigger request 23 to the (e.g., new) I-Node the WTRU may (e.g., currently) be associating with. The I-Node may indicate that the WTRU may (e.g., currently) have limited power availability and that the WTRU may not be able to perform the registration at this stage. In such a case, (e.g., case of limited power availability in the WTRU),1the I-Node may check whether the network may (e g., still) expect the WTRU to perform registration.

[0123] In an example, based on receiving the trigger request 23, the I-Node may initiate (e.g., transmit) an activation signal 25 to the WTRU. The activation signal 25 may indicate any of (i) the identity (e.g., identifier) of the WTRU that may be to be activated, (ii) that the WTRU may be requested to send MO-data, and (iii) the (e.g., current) time.

[0124] The activation signal 25 may be a general signal and the format of the signal may indicate that (e.g., all) WTRUs that may receive the signal may be activated. In an example, WTRUs receiving the activation signal 25, may not imply the WTRUs performing a transmission. For example, receiving an activation signal may trigger the WTRUs to determine whether they may transmit (e.g., it may trigger the WTRUs to check the time).

[0125] The format of the activation signal 25 may (e.g., also) indicate that a WTRU may transmit MO-data if the WTRU checks the (e.g., current) time and determines that MO-data may be transmitted.

[0126] If the activation signal 25 comprises a message that may carry information elements, the activation signal 25 may indicate the (e.g., current) time. Including the (e.g., current) time in the activation signal 25 may allow the WTRU to skip (e.g., not perform) reading the SIB, based on the (e.g., current) time value being received in the activation signal 25.

[0127] In an example, the "activation" signal may not be signal that may be received from the I- Node or any communication network node. For example, the WTRU may consider itself activated anytime the amount of energy stored in a battery and / or capacitor of the WTRU satisfies an energy condition (e.g., is above a threshold). For example, the WTRU may consider (e.g., determine) itself activated if the WTRU stored enough energy from the environment (e.g. from any of light and vibration) to determine the (e.g., current) time value.

[0128] In an example, the reception of the activation signal 25 may trigger the WTRU to read a time value that may be broadcasted by (e.g., received from) the RAN network element in e.g., a system information block (SIB) 26. For example, reception of the activation signal 25 may charge a capacitor in the WTRU. After the capacitor may be charged, the capacitor may begin discharging. As the capacitor may discharge, circuitry in the WTRU may (e.g., begin to) execute a function. One function may be reading a time value that may be broadcasted by (e.g., received from) the RAN network element, e g., in the SIB 26.

[0129] In an example, the I-Node may begin broadcasting the time value when (e.g., after) it may send the activation signal 25. The I-Node broadcasting the time value may be e.g., less powerintensive for the WTRU to receive a time value from the I-Node based on the I-Node being expected to be closer to the WTRU than the RAN network element.

[0130] In an example, the I-Node may begin broadcasting (e.g., information indicating) the identity (e.g., identifier) of the (e.g., specific) WTRU, or group of WTRUs, that may (e.g., be expected to) transmit to the RAN network element.

[0131] The WTRU may compare the received time value against the time value that may have been received in the first registration response 22. If the received time value is earlier than the time value that may have been received in the first registration response 22, the WTRU may determine to return to a sleep state and may not transmit a subsequent (e.g., second) registration request 27. If the received time value is equal to or greater than the time value that may have been received in the first registration response 22, the WTRU may determine to transmit a second registration request 27 as described herein.

[0132] In an example, the WTRU may compare the received time value against the time window value that may have been received in the first registration response 22. If the received time value is not within the time window value that may have been received in the first registration response 22, the WTRU may determine to return to a sleep state and to not transmit a second registration request 27. If the received time value is within the time window value that may have been received in the first registration response 22, the WTRU may determine to transmit a second registration request 27 as described herein.

[0133] In an example, based on evaluating the time e.g., received in the SIB 26, the WTRU may send a second registration request 27 to the network. The second registration request 27 may include an identity (e.g., identifier) of the WTRU. The second registration request 27 may include an indication that the WTRU may be associated with an I-Node. The second registration request 27 may include identities (e.g., identifiers) of one or more I-Nodes that the WTRU may be associated with.

[0134] A registration request may announce (e.g., indicate) the availability and / or presence of a WTRU to the 5GC (e.g., AMF).

[0135] If any of the first registration response 22 and the activation signal 25 indicated that the WTRU may be requested to send MO-data, the WTRU may include MO-data in the second registration request 27. The MO-data may comprise an application layer payload (e.g., message) and may carry (e.g., include) any of a sensor reading, status information, location information, and an application layer identity (e.g., identifier).

[0136] A WTRU being associated with an I-Node may mean (e.g., may be equivalent to) that the WTRU may be able to communicate with the I-Node. For example, the WTRU may have recentlyreceived a message from the I-Node and / or an excitation (e g , activation) signal from the I-Node, and / or may be authorized to communicate with the I-Node.

[0137] In an example, the 5GC may respond to the second registration request 27 by sending a second registration response 28.

[0138] The 5GC may include (e.g., second time information indicating) a new time value which may override and / or overwrite, the time value that may have been received in the first registration response 22.

[0139] The 5GC may include a new time window value which may override and / or overwrite, the time window value that may have been received in the first registration response 22.

[0140] The second registration response 28 may include a new MO-data request indication which may override and / or overwrite the MO-data request indication that may have been received in the first registration response 22.

[0141] The WTRU may enter a state where the WTRU may wait for a (e.g., new, subsequent) activation signal, and may perform the processing described herein after reception of the activation signal 25.

[0142] In an example, the 5GC (e g., AMF) may send a message including the MO-data 29 to the AS. The MO-data 29 may be sent to the AS via an NEF. The AMF may know which AS to send the MO-data based on, for example, receiving an AS identity (e.g., identifier) from the UDM / UDR network element in the WTRU's subscription. In another example, the AMF may send the MO-data to the UDM / UDR network element which may store the data in the WTRU's subscription information. The UDM / UDR network element may notify the AS about the updated MO-data. The UDM / UDR network element may send the notification to the AS via an NEF.

[0143] FIG. 3 is a diagram illustrating an example of WTRU operations in a method for determining when to perform a registration procedure.

[0144] In an example, as shown at 31, the WTRU may perform a first registration procedure.

[0145] In an example, as shown at 32, the WTRU may wait for an activation signal.

[0146] In an example, as shown at 33, the WTRU may receive the activation signal.

[0147] In an example, as shown at 34, the WTRU may determine whether it may be time to perform a second registration procedure. If the WTRU determines that it may not be time to perform a second registration procedure, the WTRU may return to a state where the WTRU may wait for an activation signal. If the WTRU determines that it may be time to perform a second registration procedure, the WTRU may perform a second registration procedure.

[0148] In an example, as shown at 35, the WTRU may perform a second registration procedure and may return to a state where the WTRU may wait for an activation signal.

[0149] FIG. 4 is a diagram illustrating an example method 400 for low power registration management, implemented in a WTRU. The WTRU may include circuitry including a transmitter, a receiver, a processor, and a memory. The circuitry may be configured to carry out the method 400. As shown at 410, the method 400 may include sending a first registration request to a network element. As shown at 420, the method 400 may include receiving a first registration response from the network element. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. As shown at 430, the method 400 may include receiving an activation transmission. As shown at 440, the method 400 may include determining that a time value may satisfy a time condition associated with the (e.g., first absolute) time information. As shown at 450, the method 400 may include sending a second registration request to the network element based on the time value satisfying the time condition associated with the (e.g., first absolute) time information.

[0150] In various embodiments, the first registration request may indicate (e.g., an identifier of) an intermediate network element.

[0151] In various embodiments, the activation transmission may be received from the intermediate network element.

[0152] In various embodiments, the (e.g., first absolute) time information may indicate a (e.g., first absolute) time value, and the time condition may be satisfied if the time value is determined to be after the (e.g., first absolute) time value.

[0153] In various embodiments, the (e.g., first absolute) time information may indicate a time window, and the time condition may be satisfied if the time value is determined to be within the time window.

[0154] In various embodiments, determining that the time value may satisfy the time condition may be triggered by reception of the activation transmission.

[0155] In various embodiments, the method 400 may further comprise receiving broadcast information indicating the time value.

[0156] In various embodiments, the broadcast information indicating the time value may be received from any of the intermediate network element and a base station.

[0157] In various embodiments, the first registration request may include any of an identifier of the WTRU and an indication that the WTRU may be associated with the intermediate network element.

[0158] In various embodiments, any of the first registration response and the activation transmission may indicate a request to include mobile originated data in a subsequent registration request to be sent to the network element.

[0159] In various embodiments, the second registration request may include the mobile originated data.

[0160] In various embodiments, the method 400 may further comprise receiving a second registration response from the network element. In various embodiments, the second registration response may comprise second time information.

[0161] In various embodiments, the second time information may indicate a second time value to be used for determining whether to send a subsequent registration request.

[0162] In various embodiments, the second time information may indicate a second time window to be used for determining whether to send a subsequent registration request.

[0163] In various embodiments, the network element may comprise an access and mobility function.

[0164] FIG. 5 is a diagram illustrating an example method 500 for low power registration management, implemented in a network element. The network element may include circuitry including a transmitter, a receiver, a processor, and a memory. The circuitry may be configured to carry out the method 500. As shown at 510, the method 500 may include receiving a first registration request from a WTRU. In various embodiments, the first registration request may indicate an intermediate network element. As shown at 520, the method 500 may include sending a first registration response to the WTRU. In various embodiments, the first registration response may comprise (e.g., first absolute) time information. As shown at 530, the method 500 may include sending a trigger request to the intermediate network element based on the (e.g., first absolute) time information. As shown at 540, the method 500 may include receiving a second registration request from the WTRU. In various embodiments, the second registration request may comprise mobile originated data.

[0165] In various embodiments, the first registration response may indicate a request to include the mobile originated data in a subsequent registration request.

[0166] In various embodiments, the method 500 may further include sending the mobile originated data to an application server.

[0167] In various embodiments, the (e.g., first absolute) time information may indicate a (e.g., first absolute) time value to be used for determining whether to send the second registration request.

[0168] In various embodiments, the (e.g., first absolute) time information may indicate a time window to be used for determining whether to send the second registration request.

[0169] In various embodiments, the method 500 may further comprise receiving a trigger response from the intermediate network element. In various embodiments, the trigger response may comprise information associated with the WTRU.

[0170] In various embodiments, the method 500 may further comprise sending a second registration response to the WTRU. In various embodiments, the second registration response may comprise second time information to be used for determining whether to send a subsequent registration request.

[0171] In various embodiments, the second time information may indicate a second time value to be used for determining whether to send a subsequent registration request.

[0172] In various embodiments, the second time information may indicate a second time window to be used for determining whether to send a subsequent registration request.

[0173] In various embodiments, the network element may comprise an access and mobility function.

[0174] While not explicitly described, embodiments described herein may be employed in any combination or sub-combination. For example, the present principles are not limited to the described variants, and any arrangement of variants and embodiments can be used.

[0175] Besides, any characteristic, variant or embodiment described for a method is compatible with an apparatus device comprising means for processing the disclosed method, with a device comprising circuitry, including any of a transmitter, a receiver, a processor, and a memory, the circuitry being operable (e.g., configured) to process the disclosed method, with a computer program product comprising program code instructions and with a non-transitory computer- readable storage medium storing program instructions. Besides, any characteristic, variant or embodiment described for a WTRU is compatible with an (e.g., infrastructure) network element of the cellular network.

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

[0177] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0178] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and / or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0179] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. 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, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0180] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0181] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0182] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0183] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0184] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. Thecomputer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0185] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systems and / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0186] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, acomputer memory, etc., and a transmission type medium such as a digital and / or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0187] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and / or control systems including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0188] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0189] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to theplural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0190] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will beunderstood to include the possibilities of "A" or "B" or "A and B " Further, the terms "any of followed by a listing of a plurality of items and / or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and / or "any combination of multiples of the items and / or the categories of items, individually or in conjunction with other items and / or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0191] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0192] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0193] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, U 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMSWhat is claimed is:

1. A wireless transmit / receive unit (WTRU) comprising circuitry, including a transmitter, a receiver, a processor, and a memory, configured to: send a first registration request to a network element; receive a first registration response from the network element, wherein the first registration response comprises absolute time information; receive an activation transmission; determine that a time value satisfies a time condition associated with the absolute time information; and send a second registration request to the network element based on the time value satisfying the time condition associated with the absolute time information.

2. The WTRU of claim 1, wherein the first registration request indicates an intermediate network element.

3. The WTRU of claim 2, wherein the activation transmission is received from the intermediate network element.

4. The WTRU of any of claims 1 to 3, wherein the absolute time information indicates an absolute time value, and wherein the time condition is satisfied if the time value is determined to be after the absolute time value.

5. The WTRU of any of claims 1 to 3, wherein the absolute time information indicates a time window, and wherein the time condition is satisfied if the time value is determined to be within the time window.

6. The WTRU of any of claims 1 to 5, wherein determination that the time value satisfies the time condition is triggered by reception of the activation transmission.

7. The WTRU of any of claims 1 to 6, wherein the WTRU is configured to receive broadcast information indicating the time value.

8. The WTRU of claims 2 and 7, wherein the broadcast information indicating the time value is received from any of the intermediate network element and a base station.

9. The WTRU of any of claims 2 to 8, wherein the first registration request includes any of an identifier of the WTRU and an indication that the WTRU is associated with the intermediate network element.

10. The WTRU of any of claims 1 to 9, wherein any of the first registration response and the activation transmission indicate a request to include mobile originated data in a subsequent registration request to be sent to the network element.

11. The WTRU of claim 10, wherein the second registration request includes the mobile originated data.

12. A network element comprising circuitry, including a transmitter, a receiver, a processor, and a memory, configured to: receive a first registration request from a wireless transmit / receive unit (WTRU), wherein the first registration request indicates an intermediate network element; send a first registration response to the WTRU, wherein the first registration response comprises absolute time information; send a trigger request to the intermediate network element based on the absolute time information; and receive a second registration request from the WTRU, wherein the second registration request comprises mobile originated data.

13. The network element of claim 12, wherein the first registration response indicates a request to include the mobile originated data in a subsequent registration request.

14. The network element of any of claims 12 to 13, configured to send the mobile originated data to an application server.

15. The network element of any of claims 12 to 14, wherein the absolute time information indicates an absolute time value to be used for determining whether to send the second registration request.

16. The network element of any of claims 12 to 14, wherein the absolute time information indicates a time window to be used for determining whether to send the second registration request.

17. The network element of any of claims 12 to 16, configured to receive a trigger response from the intermediate network element, wherein the trigger response comprises information associated with the WTRU.

18. The network element of any of claims 12 to 17, configured to send a second registration response to the WTRU, wherein the second registration response comprises second time information to be used for determining whether to send a subsequent registration request.

19. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: sending a first registration request to a network element; receiving a first registration response from the network element, wherein the first registration response comprises absolute time information; receiving an activation transmission; determining that a time value satisfies a time condition associated with the absolute time information; and sending a second registration request to the network element based the time value satisfying the time condition associated with the absolute time information.

20. A method implemented in a network element, the method comprising: receiving a first registration request from a wireless transmit / receive unit (WTRU), wherein the first registration request indicates an intermediate network element; sending a first registration response to the WTRU, wherein the first registration response comprises absolute time information; sending a trigger request to the intermediate network element based on the absolute time information; and receiving a second registration request from the WTRU, wherein the second registration request comprises mobile originated data.

Images