Paging for environmental internet of things devices

Abstract

Network communications may be performed using a paging procedure. A wireless transmit / receive unit (WTRU) may initiate paging with an on-demand paging procedure. A WTRU may determine a first indication that a transmitting WTRU is ready to initiate an on-demand paging procedure. The WTRU may transmit a first indication to at least one network entity. The WTRU may receive a second indication from at least one network entity as to the presence of pending downlink data for the WTRU. In response to determining that downlink data for the WTRU is pending, the WTRU may listen for the paging channel. The WTRU may determine that a paging occasion is set for the WTRU. The WTRU may read the paging message. In response to determining that the paging message includes an identifier associated with the WTRU, the WTRU may perform a service request procedure to receive downlink data.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 465,778, filed May 11, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] Paging is a procedure that allows the network to reach a Wireless Transmitter / Receiver Unit (WTRU) when it is inactive or idle. Current paging technology may be insufficient for IoT devices in power-constrained environments. Furthermore, using current technology to page environmental IoT devices may waste network resources. Summary of the Invention

[0003] A Wireless Transmitter Receiver Unit (WTRU) can determine to initiate an on-demand paging procedure. The WTRU can send a first indication associated with initiating the on-demand paging procedure to at least one network entity. The first indication may include a request for a System Information Block (SIB). For example, the first indication may identify a specific SIB. The WTRU can receive the SIB from the at least one network entity. The SIB may indicate whether the WTRU should continue the on-demand paging procedure. For example, in response to the SIB indicating that the WTRU should continue the on-demand paging procedure, the WTRU can monitor the paging channel for a second indication during the paging period. The second indication may indicate whether the paging period has been set. The SIB may include bits indicating whether the WTRU should monitor the paging channel. For example, the bits may indicate the presence of pending downlink data for the WTRU. When the bits indicate the presence of pending downlink data for the WTRU, the SIB may indicate that the WTRU should continue the on-demand paging procedure. When the bits indicate the absence of pending downlink data for the WTRU, the SIB may indicate that the WTRU should return to a low-power state. The WTRU can receive paging messages via the paging channel.

[0004] In some examples, the WTRU may receive configuration information associated with the on-demand paging procedure. The configuration information may include one or more of the following: conditions associated with initiating the paging procedure, a timer value associated with initiating the paging procedure, an allowed location, and / or an indication of the system information block. Initiation of the on-demand paging procedure may be determined based on one or more of the following: the configuration information, the expiration of a timer, detection that the WTRU has sufficient power to execute the on-demand paging procedure, or detection that the WTRU is in an allowed location. The WTRU may execute a service request procedure to receive the downlink data based on a paging message including an identifier associated with the WTRU. The service request procedure may include the WTRU transitioning to a connected state and receiving the downlink data. Attached Figure Description

[0005] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments can be implemented.

[0006] Figure 1B The illustration shows a method according to one embodiment. Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0007] Figure 1C The illustration shows a method according to one embodiment. Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used in the communication system.

[0008] Figure 1D The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows yet another example RAN and yet another example CN used in the communication system.

[0009] Figure 2 This is an example of a paging program on a network.

[0010] Figure 3 This is an example of on-demand paging initiated by WTRU. Detailed Implementation

[0011] Figure 1AThis is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0012] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as WTRUs. Furthermore, any descriptions herein referring to UEs may equally apply to WTRUs (or vice versa). For example, the WTRU can be configured to execute any of the procedures or programs described herein that are to be executed by the UE (or vice versa).

[0013] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, eNode B, home node B, home eNode B, gNB, NR node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

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

[0015] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0016] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0017] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0018] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using a new radio (NR).

[0019] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0020] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0021] For example, Figure 1A Base station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0022] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0023] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0025] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0026] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0027] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be, for example, a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0029] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

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

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

[0032] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0033] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

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

[0035] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0036] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0037] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0038] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0039] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0040] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0041] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0042] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0043] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0044] In a representative embodiment, another network 112 may be a WLAN.

[0045] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as an "ad-hoc" communication mode.

[0046] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0047] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0048] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

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

[0050] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy, even if most of the available band remains idle and can be available.

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

[0052] Figure 1D This diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0053] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0054] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a variable number of OFDM symbols and / or a continuously variable absolute time).

[0055] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0056] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0057] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0058] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, and / or so on. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

[0059] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0060] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0062] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

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

[0064] One or more simulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to implement the testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0065] Environmental Internet of Things (IoT) devices (e.g., WTRUs) can be configured to use information to determine when to transmit a signal to a base station. This signal can identify which group the WTRU belongs to. The purpose of this signal can be to trigger the base station to begin broadcasting an indication. The purpose of this indication can be to allow the WTRU to read the indication to determine whether to perform a WTRU check if it is being paged. The advantage of this procedure is that if the signal indicates that the WTRU does not need to perform the WTRU check if it is being paged, the WTRU can enter a low-power state. Another advantage of this procedure is that if the WTRU does need to be paged, the network does not need to attempt to transmit a page until it receives a signal from the environmental IoT device.

[0066] The methods and embodiments described herein can be performed by Access and Mobility Functions (AMFs). These operations can be performed by any network function that provides mobility management functions in a network that provides communication services to IoT devices in the environment.

[0067] The methods and embodiments described herein can be performed by a Session Management Function (SMF). These operations can be performed by any network function that provides session management functionality in a network that provides communication services to IoT devices in the environment.

[0068] The methods and embodiments described herein can be performed by a radio access network (RAN) node, gNodeB, or base station. These operations can be performed by any base station communicating with IoT devices in the environment.

[0069] System information request messages can be used in paging procedures. A system information request message can be a type of message that can be sent from a WTRU to a base station. A system information request can request the base station to broadcast certain information. A system information request can indicate what information is requested to be broadcast. The information can be transmitted in a System Information Block (SIB). The SIB can include information broadcast by the base station. The same information proposed to be sent can also be sent in any message broadcast by the base station. The events described herein can trigger a service request. A service request can be a procedure used by a WTRU to request entry into a connected state to receive downlink data and / or to enter a connected state to send uplink data.

[0070] Non-Access Stratum (NAS) messages can be sent from the WTRU to the network and / or received by the WTRU from the network. These messages can be sent using other protocols used to send control information between the WTRU and the network (e.g., the core network). Radio Resource Control (RRC) messages can be sent from the WTRU to the RAN node and received by the WTRU from the RAN node. These messages can be sent using other protocols used to send control information between the WTRU and the base station. The terms base station, gNB, NG-RAN, RAN, and RAN node are used interchangeably.

[0071] Figure 2 This is an example of paging procedure 200 in a network. Paging is a procedure that allows the network to reach the WTRU when it is inactive or idle. While the WTRU is transitioning to idle mode, the last known gNB to which the WTRU is attached (e.g., the anchor gNB) can preserve the WTRU's core context information. Discontinuous reception (DRX) allows the WTRU to remain offline for a specific period before waking up and decoding the paging opportunity (PO) to check for any paging messages destined for the WTRU and / or in which / which resource blocks that message can be sent. Figure 2 As shown, when incoming data is present from the User Plane Function (UPF), the SMF can use the Namf_Communication_N1N2MessageTransfer request to notify the AMF of the arriving service. The AMF can trigger the gNB using the NG Application Protocol (NGAP) paging message. Considering DRX, the gNB can use the paging opportunity (PO) on the PDCCH channel to page the WTRU. The WTRU can decode the PDCCH service for any paging information in each cycle; if the WTRU has no data to receive, this may be a waste of resources.

[0072] Early paging indication can be implemented to reduce power consumption in the WTRU. In the example, an Early Paging Indicator (EPI) can be sent to the WTRU via downlink control information (DCI) or a reference signal, so the WTRU checks for the next Page Out (PO) for paging, instead of decoding every PO sent during the wake-up time. When the WTRU receives the EPI, it can be ready to decode the next received PO.

[0073] Because a wide range of WTRUs share the same PO or inactive WTRU groups share the same EPI, subgrouping can be implemented to reduce the false paging notification rate. This reduces power consumption within the WTRU. Subgroup information can be sent via DCI along with the EPI, where the WTRU group is divided into subgroups. This allows the WTRU to determine whether to decode the next PO.

[0074] While the described paging techniques can be effectively used for WTRUs that do not have certain power constraints (e.g., extreme power constraints), these techniques may be insufficient for environmental IoT devices that do have certain power constraints (e.g., extreme power constraints). Using these techniques to page environmental IoT devices may waste network resources. Some paging programs may have drawbacks when considered in conjunction with environmental IoT devices. WTRUs with extreme power constraints may have relatively small energy storage capacities compared to other WTRUs and / or WTRU energy storage components, which may include batteries or other energy storage devices that may be charged at unknown and / or infrequent times. Some IoT devices with extreme power constraints (e.g., WTRUs) may be batteryless and / or use capacitors for energy storage. Some IoT devices with extreme power constraints (e.g., WTRUs) may use energy harvesting techniques to store energy in components such as batteries or capacitors. When using some energy harvesting techniques (e.g., vibration energy harvesting or RF energy harvesting), IoT devices with extreme power constraints (e.g., WTRUs) can harvest as little as a few microwatts of energy. In typical energy harvesting scenarios for WTRUs with extreme power constraints, the amount of energy available may be significantly less than that available from other sources, such as telephone chargers. For example, charging some WTRUs may consume more than 10 watts. Furthermore, WTRUs using energy harvesting technologies may harvest energy at unpredictable times. For instance, a WTRU that harvests energy from vibration may harvest energy while the WTRU is vibrating (e.g., while the WTRU is moving).

[0075] When paging technology is implemented, the device can listen for paging indications at the assigned paging time. Ambient IoT devices may rely on harvesting power from the environment and may not store enough power to listen for paging indications at the assigned paging time.

[0076] When the WTRU does not respond to paging, the network can assume the WTRU's location has changed and expand the paging area (e.g., the number of cells transmitting paging messages over it). This approach may not work well for environmental IoT devices. A paging indication may have been transmitted in the correct location, but the environmental IoT device may not respond because it has indeed stored enough power to receive the paging message. Therefore, this approach can waste network resources (e.g., paging resources) when applied to environmental IoT devices. Therefore, a paging procedure can be implemented to address the unreliable power supply nature of environmental IoT devices and to efficiently manage network resources.

[0077] This document describes embodiments for paging IoT devices in a paging environment. When the WTRU has sufficient power and is triggered by certain conditions, the WTRU can initiate a paging request toward the network. The embodiments described herein can reduce signaling and / or power consumption in the WTRU and transmission resources and signaling in the network. The embodiments described herein can be a driving force in scenarios where there is a high density of devices attached to the network and a wide distribution of individuals.

[0078] Environmental IoT devices (e.g., WTRUs) can be configured with information that the WTRU can use to determine when to transmit a signal to the base station. This signal can identify the group to which the WTRU belongs. This signal can trigger the base station to begin broadcasting an indication. This indication can be provided so that the WTRU can read it to determine whether to execute the WTRU's procedure of checking if it is being paged.

[0079] If the signal indicates that the WTRU does not need to perform the procedure of checking whether it is being paged, the WTRU can enter a low-power state. If the WTRU does need to be paged, the network may not attempt to transmit a page until the network receives a signal from the ambient IoT device.

[0080] The WTRU can determine whether to initiate an on-demand paging procedure. This determination can be based on configuration information received in NAS or RRC messages. It can also be based on timer expiration and detection that the WTRU has sufficient power to perform the on-demand paging procedure. Finally, it can be based on detection that the WTRU is in a permitted location.

[0081] The WTRU can transmit a message requesting broadcast information to the network. The content of this message can be based on configuration information received in NAS or RRC messages. The message content may include a group identifier or a paging listener identifier. The message can also be a System Information On Demand Request message, where the System Information On Demand Request message identifies an SIB, and the identified SIB is based on configuration information.

[0082] The WTRU can receive messages broadcast by the network, at least a portion of which is used by the WTRU to determine whether to continue the on-demand paging procedure. The message content may be an SIB (System Identifier). The message content may include a group identifier associated with the WTRU. The message content includes bits indicating the group associated with the WTRU and / or indicating whether WTRUs in that group should be paged. The message content may include the WTRU's identifier.

[0083] Based on the content of the message broadcast by the network, the WTRU can determine to send a message to the network to continue the on-demand paging procedure and / or determine whether the WTRU is being paged.

[0084] A WTRU can initiate a paging procedure by sending an indication to the network that the WTRU has been awakened. This indication may or may not specifically identify the WTRU. The indication may identify the group or service to which the WTRU belongs. The network can determine whether it intends to page any WTRUs associated with that group, and if it does intend to page any WTRUs associated with that group, it can begin broadcasting an indication from at least one WTRU in that group that it needs to receive a paging message. This example procedure can be referred to as "on-demand paging" because paging messages can be sent from WTRUs on demand or upon request.

[0085] For environmental IoT devices, the network can queue data and / or send paging requests to the RAN. The RAN (e.g., RAN nodes) can queue paging requests until the WTRU sends a system information request. This can be a paging procedure initiated by the WTRU, as the WTRU can control the start of the paging process.

[0086] The SMF can receive downlink data notifications from the UPF. These notifications can trigger the SMF to notify the AMF that downlink data is available for the WTRU. A message from the SMF can indicate to the AMF that if the WTRU is in a CM-IDLE state, the WTRU, AMF, and RAN can perform an on-demand paging procedure. The SMF can determine the availability of on-demand paging based on PCC rules. Alternatively or additionally, the AMF can determine the availability of on-demand paging based on the WTRU's subscription information. If the WTRU is in a CM-IDLE state, the AMF can respond to the SMF with an indication that the WTRU is currently unreachable and that an on-demand paging procedure will be performed. The AMF can assume that the WTRU is unreachable because it is in a CM-IDLE state and, based on the determination of using on-demand paging, cannot be paged. The AMF can then send a paging request to the RAN node. The paging request can include the WTRU's identity and / or indicate to the RAN node that an on-demand paging procedure can be performed.

[0087] When the WTRU determines that it has stored sufficient power to receive and process data from the network and / or data triggered by certain conditions, the WTRU may decide to perform an on-demand paging procedure to the network. The WTRU may transmit a System Information On-Demand Request to the network, which requests the network to broadcast a Paging Group SIB. The Paging Group SIB may include group identifiers for one or more WTRUs to be paged, or each bit of the Paging Group SIB may represent a group of devices, and / or if the network wishes to page one or more WTRUs in that group, the network may set the corresponding bits in the SIB. If the WTRU reads the SIB and determines that the bits corresponding to its group are set, the WTRU may begin listening for paging channels. If the WTRU reads the SIB and does not find its group identifier or determines that the bits corresponding to its group are not set, the WTRU may return to sleep mode.

[0088] If the WTRU reads the paging channel and determines that its assigned paging timing is set, the WTRU can read the paging message. If the WTRU reads the paging channel and determines that its assigned paging timing is not set, the WTRU can return to sleep mode. If the WTRU reads the paging message and finds the identifier assigned to the WTRU in the paging message, the WTRU can determine to execute a service request procedure in order to receive mobile termination data. If the WTRU reads the paging message and does not find the identifier assigned to the WTRU in the paging message, the WTRU can return to sleep mode.

[0089] The WTRU can determine whether to expend energy attempting to read the paging indicator. This determination can be based on reading the SIB. The network can avoid setting the SIB until a system information on demand request is received. By waiting for the WTRU to set up its paging activity until a system information on demand request is received, the possibility of other WTRUs detecting erroneous paging is avoided.

[0090] Figure 3 A call flow diagram for on-demand paging 300 initiated by the WTRU is depicted. At 312, the UPF 310 can receive downlink data. At 314a, upon receiving downlink data, the UPF 310 can send a downlink data notification to the SMF 308. At 314b, the SMF 308 can acknowledge receipt of the notification and can notify the UPF 310 to store the downlink data because the WTRU 302 is using on-demand paging. For example, the UPF 310 can store downlink data (e.g., user data) until the UPF 310 receives notification from the SMF 308 that the WTRU 302 is ready to receive downlink data. At 316a, the SMF 308 can send a message to the AMF 306 to notify the AMF 306 that downlink data is available for the WTRU 302. For example, if WTRU 302 is in an idle state (e.g., CM-IDLE state), a message sent at 316a could instruct AMF 306 to perform an on-demand paging procedure. In the example, the message sent at 316a could be a Namf_communication_N1N2MessageTransfer request.

[0091] At 316b, in response to the message received at 316a, AMF 306 may send a response message to SMF 308. The response message sent to SMF 308 at 316b may indicate that WTRU 302 is in CM-IDLE state and / or that an on-demand paging procedure will be executed. At 318, AMF 306 may send a paging message to a RAN node (e.g., AN 304). The paging message may include an identifier for WTRU 302 and an indication that an on-demand paging procedure should be executed. The paging message may include a group ID. This group ID may be used by the RAN node (e.g., AN 304) to determine which SIB and / or which bit of the SIB can be used to indicate to WTRU 302 that mobile termination data is available for WTRU 302. Additionally or alternatively, the identifier of WTRU 302 can (e.g., by AN 304) be used to determine which SIB and / or which bit of the SIB can be used to indicate to WTRU 302 that mobile termination data is available for WTRU 302.

[0092] At 320, the RAN node (e.g., AN 304) can store the paging request and can wait for an indication from WTRU 302 that WTRU 302 is available to receive the paging.

[0093] WTRU 302 can determine to initiate an on-demand paging procedure. At 322, one or more events and / or conditions can trigger WTRU 302 to initiate an on-demand paging procedure. For example, the determination to initiate an on-demand paging procedure can be based on one or more of the following (e.g., triggered by one or more of the following): configuration information, timer expiration, detection that WTRU 302 has sufficient power to perform the on-demand paging procedure, and / or detection that WTRU 302 is in a permitted location. Configuration information can be associated with the on-demand paging procedure and may have been received from the network (e.g., AN 304). Configuration information may include conditions associated with initiating the paging procedure, timer values ​​associated with initiating the paging procedure, permitted locations, and / or indications of system information blocks. WTRU 302 can send a system information on-demand request to at least one network entity (e.g., AN 304) at 322. This request may include indications associated with the on-demand paging procedure. For example, a system information on-demand request may indicate a request to broadcast a specific SIB to a RAN node (e.g., AN 304). The request can identify an SIB. For example, a request from WTRU 302 can identify an SIB that includes bits indicating to WTRU 302 whether there is pending downlink data for WTRU 302. For example, this bit can indicate whether WTRU 302 should monitor the paging channel. This document describes the events and / or conditions that trigger WTRU 302 to send a System Information On Demand Request to the network (e.g., AN 304). The RAN node (e.g., AN 304) can receive the System Information On Demand Request from WTRU 302 at 322. Based on the receipt of the System Information On Demand Request and based on the notification from AMF 306 regarding the existence of pending downlink data for WTRU 302, the RAN node (e.g., AN 304) can set a paging indicator associated with WTRU 302.

[0094] Based on a received system information on demand request, a RAN node (e.g., AN 304) can begin broadcasting an SIB at 326 instructing WTRU 302 whether it should continue the on-demand paging procedure. For example, the SIB may include a bit indicating to WTRU 302 whether there is pending downlink data for WTRU 302 (e.g., whether the WTRU should continue the on-demand paging procedure (e.g., monitoring the paging channel)). When this bit indicates the presence of pending downlink data for WTRU 302, the SIB can instruct WTRU 302 to continue the on-demand paging procedure.

[0095] At 326, WTRU 302 can receive an SIB indicating whether WTRU 302 should continue the on-demand paging procedure, and can detect the status of the bit indicating to WTRU whether there is pending downlink data for WTRU 302. For example, AN 304 can send a System Information On-Demand Response message to WTRU 302 at 326. If the status of this bit indicates that there is no pending downlink data for WTRU 302, WTRU 302 can return to a sleep or low-power state (e.g., CM-IDLE state). If the status of this bit indicates that there is pending downlink data for WTRU 302, WTRU 302 can continue the on-demand paging procedure and can listen to the paging channel at 328. For example, in response to the SIB indicating that WTRU 302 should continue the on-demand paging procedure, WTRU 302 can monitor the paging channel for a second indication during the paging timing. The second indication can indicate whether a paging timing has been set.

[0096] If WTRU 302 reads the paging channel and determines that its assigned paging timing is set, WTRU 302 can receive a paging message from AN 304 at 330. If WTRU 302 reads the paging channel and determines that its assigned paging timing is not set, WTRU 302 can return to sleep mode. At 330, WTRU 302 can read the paging message. WTRU 302 can execute a service request procedure at 332 to receive downlink data based on the paging message including an identifier associated with WTRU 302. The service request procedure may include WTRU 302 transitioning to a connected state and / or WTRU 302 receiving downlink data. For example, WTRU 302 can determine whether the paging message includes an identifier associated with WTRU 302. If WTRU 302 determines that the paging message includes an identifier associated with WTRU 302, WTRU 302 can execute a service request procedure with the network at 332 to transition to a connected state and / or begin receiving downlink data. For example, WTRU 302 can send a service request to AMF 306 at 332. If WTRU 302 determines that the paging message does not include the identifier associated with WTRU 302, WTRU 302 can return to a sleep state.

[0097] Several events and conditions exist that trigger the on-demand paging procedure for a WTRU. The WTRU can receive configuration information related to the on-demand paging procedure. This configuration information can be received from the AMF in the NAS message, the Policy Control Function (PCF) in the NAS message (e.g., carried in the NAS message), the base station in the RRC message, the user interface (e.g., a graphical user interface (GUI), button, or switch), and / or another WTRU (e.g., via a side link such as PC5).

[0098] The WTRU can receive configuration information from different network nodes. For example, configuration information from the AMF can indicate how often to perform on-demand paging when it is enabled, and configuration information from the base station can indicate whether on-demand paging is enabled. Configuration information may include information indicating what conditions need to be met for the WTRU to perform on-demand paging. Configuration information may include timer values. The WTRU can use time values ​​to configure timers. The WTRU can reset the timer whenever it is in connected mode or initiates an on-demand paging procedure. If the timer has expired, the WTRU can determine to perform the paging procedure. Therefore, time values ​​can be used to configure the WTRU to limit the number of on-demand paging procedures the WTRU attempts in the time domain.

[0099] Configuration information can include allowed or disallowed location information. When the WTRU determines that it is in a location corresponding to disallowed location information, the WTRU may decide not to initiate an on-demand paging procedure. When the WTRU determines that it is in a location corresponding to allowed location information, the WTRU may decide to initiate an on-demand paging procedure.

[0100] The configuration information can instruct the WTRU which SIB and / or which bit of the SIB to read when it checks whether it needs to be paged. When the WTRU determines that it has sufficient stored power to perform an on-demand paging procedure, it can determine to initiate the on-demand paging process by sending an appropriate system information on-demand request. The WTRU can receive downlink data and determine that the conditions indicated in the configuration information allow the on-demand paging procedure (e.g., allowable at the WTRU's current location or current time). When the WTRU determines that it has sufficient stored power to perform an on-demand paging procedure and / or to receive downlink data and / or to receive a trigger message from another WTRU via a side link (e.g., PC5), it can determine to initiate the on-demand paging procedure by sending an appropriate system information on-demand request.

[0101] Alternative methods exist for initiating on-demand paging procedures. The WTRU can initiate an on-demand paging procedure by transmitting a System On-Demand Request (SIR). Alternatively, the WTRU can initiate an on-demand paging procedure by transmitting different messages. For example, the WTRU can initiate an on-demand paging procedure by transmitting a message including a paging listener identifier. The identifier can be associated with the WTRU and also with other WTRUs (e.g., the identifier can be shared by a group of WTRUs). The paging listener identifier can be received by the WTRU in the configuration information related to the on-demand paging procedure. The RAN can determine which SIB to broadcast based on the paging listener identifier. An advantage of transmitting a paging listener identifier to initiate the procedure instead of transmitting a System On-Demand Request (SIR) might be that a spoofed or malicious base station would not know the SIB number broadcast in response to the WTRU's paging listener identifier transmission.

[0102] Alternative deployment models exist. The examples described in this paper illustrate how an environmental IoT device can communicate with a base station to determine whether the environmental IoT device wants to receive data from the network. The same procedure can be applied to scenarios where the environmental IoT device interacts with a WTRU, such as a handheld device, which is used to collect data from and send data back to the environmental IoT device. For example, as an alternative, Figure 3 The interaction described in the text occurs between the WTRU and the base station via the PC5 interface between the environmental IoT device and the WTRU. Additionally or alternatively, the interaction between the environmental IoT device and the WTRU can be used by the environmental IoT device to determine if the WTRU is being paged. Once the environmental IoT device determines that it is being paged, it can initiate contact with the network by sending a service request to the network. In other words, Figure 3 Procedures 322 to 330 can occur between the environmental IoT device and the handheld device, while procedure 332 can occur between the environmental IoT device and the network.

Claims

1. A method implemented by a wireless transmit-receive unit (WTRU), the method comprising: Confirm the initiation of the on-demand paging procedure; Send a first instruction associated with initiating the on-demand paging procedure to at least one network entity, the first instruction including a request for a system information block; The system information block is received from the at least one network entity, the system information block indicating whether the WTRU should continue the on-demand paging procedure; In response to the system information block instructing the WTRU to continue the on-demand paging procedure, the paging channel is monitored in response to the second instruction during the paging timing; and Paging messages are received via the paging channel.

2. The method of claim 1, further comprising receiving configuration information associated with the on-demand paging program, wherein, The configuration information includes one or more of the following: conditions associated with initiating the paging procedure, timer values ​​associated with initiating the paging procedure, allowed locations, or indications of the system information block.

3. The method according to claim 2, wherein, The determination to initiate the on-demand paging procedure is based on one or more of the following: the configuration information, the expiration of the timer, detection that the WTRU has sufficient power to execute the on-demand paging procedure, or detection that the WTRU is in an authorized location.

4. The method according to claim 1, wherein, The system information block includes bits indicating whether the WTRU should monitor the paging channel, wherein the bits indicate whether there is pending downlink data for the WTRU.

5. The method according to claim 4, wherein, When the bit indicates the presence of pending downlink data for the WTRU, the system information block instructs the WTRU to continue the on-demand paging procedure.

6. The method according to claim 4, wherein, When the bit indicates that there is no pending downlink data for the WTRU, the system information block indicates that the WTRU should return to a low-power state.

7. The method according to claim 1, wherein, The first indication associated with initiating the on-demand paging procedure identifies a specific system information block.

8. The method according to claim 1, wherein, The second indication indicates whether the paging timing has been set.

9. The method of claim 1, further comprising executing a service request procedure to receive downlink data based on the paging message including an identifier associated with the WTRU.

10. The method according to claim 9, wherein, Executing the service request procedure includes transitioning to a connected state, and the method further includes receiving the downlink data.

11. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Confirm the initiation of the on-demand paging procedure; Send a first instruction associated with initiating the on-demand paging procedure to at least one network entity, the first instruction including a request for a system information block; The system information block is received from the at least one network entity, the system information block indicating whether the WTRU should continue the on-demand paging procedure; In response to the system information block instructing the WTRU to continue the on-demand paging procedure, the paging channel is monitored in response to the second instruction during the paging timing; and Paging messages are received via the paging channel.

12. The WTRU according to claim 11, wherein, The processor is further configured to receive configuration information associated with the on-demand paging procedure, wherein the configuration information includes one or more of the following: conditions associated with initiating the paging procedure, timer values ​​associated with initiating the paging procedure, allowed locations, or indications of the system information block.

13. The WTRU according to claim 12, wherein, The determination to initiate the on-demand paging procedure is based on one or more of the following: the configuration information, the expiration of the timer, detection that the WTRU has sufficient power to execute the on-demand paging procedure, or detection that the WTRU is in an authorized location.

14. The WTRU according to claim 11, wherein, The system information block includes bits indicating whether the WTRU should monitor the paging channel, wherein the bits indicate whether there is pending downlink data for the WTRU.

15. The WTRU according to claim 14, wherein, When the bit indicates the presence of pending downlink data for the WTRU, the system information block instructs the WTRU to continue the on-demand paging procedure.

16. The WTRU of claim 14, wherein, When the bit indicates that there is no pending downlink data for the WTRU, the system information block indicates that the WTRU should return to a low-power state.

17. The WTRU according to claim 11, wherein, The first indication associated with initiating the on-demand paging procedure identifies a specific system information block.

18. The WTRU according to claim 11, wherein, The second indication indicates whether the paging timing has been set.

19. The WTRU according to claim 11, wherein, The processor is further configured to execute a service request procedure to receive downlink data based on the paging message, which includes an identifier associated with the WTRU.

20. The WTRU of claim 19, wherein, Executing the service request procedure includes: the processor being configured to transition to a connected state, wherein the processor is further configured to receive the downlink data.

Images