Negotiation on sufficient battery power in an IoT

Abstract

A wireless transmit / receive unit (WTRU) may receive a first message that is broadcast by a network. The first message may indicate one or more challenge values, an estimated required energy level to perform a requested action, and / or an indication that the WTRU should respond with an indication of an amount of energy available to the WTRU. The WTRU may determine whether to respond to the first message based on an amount of energy available to the WTRU. The WTRU may send a second message to the network based on a determination to respond to the first message. The second message may indicate a challenge response value, the amount of energy available to the WTRU, and / or a device-specific network challenge value.

Description

NEGOTIATION ON SUFFICIENT BATTERY POWER IN AN IOTCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to United States Provisional Patent Application No. 63 / 526,756 filed on July 14, 2023, the entire contents of which are incorporated herein by reference.BACKGROUND

[0002] One or more procedures with respect to authentication may be performed. For example, one or more devices may be authenticated with a network based one or more authentication procedures. Authentication may include an authentication initiation messaging exchange and / or authentication challenge (e.g., which may use challenge values).SUMMARY

[0003] Systems, methods, and apparatuses with respect to one or more ambient internet of things (loT) devices (e.g., wireless transmit / receive units (WTRUs)) may be provided herein. Systems, methods, and / or apparatuses with respect to one or more energy harvesting devices (e.g., WTRUs) may be described herein. Systems, methods, and / or apparatuses with respect to triggering ambient loT may be provided herein.

[0004] A network may trigger an ambient loT device. For example, the network may trigger ambient loT devices (e.g., WTRUs) based on a request from an application function (AF). Mutual authentication may take place between the network and the WTRU. This procedure may include device authentication, network authentication, and / or negotiation of whether the device has enough power to perform the procedure to be integrated with the triggering device (e.g., WTRU). For example, the number of interactions between the device and network may be minimized. Additionally or alternatively, the network may consider the power level in the WTRU available to perform the request action, for example, in one or more devices with limited power availability.

[0005] A WTRU may receive a signal from a network node. The signal may include one or more device-specific information, an indication of a challenge value, and / or anindication of a location. The signal may include an indication of an estimated required energy value. The device-specific information may include a device type and / or an indication of a device identity. The WTRU may determine to respond to the received signal based on the device-specific information. For example, the WTRU may determine to respond to the received signal based on the estimated required energy value. For example, the WTRU may determine that a stored energy estimate value is greater than the estimated required energy value to determine to respond to the received signal. For example, the WTRU may determine to respond to the received signal if a type of the WTRU matches the indicated device type and / or that an identity associated with the WTRU matches the indicated device identity. The WTRU may send a response message to the network node. The response message may include an indication of a challenge response value. The WTRU may receive an action trigger message from the network node. The WTRU may send an action trigger response to the network node.

[0006] A WTRU may receive a first message. The first message may be a broadcast message (e.g., by a network). The first message may indicate one or more challenge values, an estimated required energy level to perform a requested action, and / or an indication that the WTRU should respond with an indication of an amount of energy available to the WTRU. The WTRU may determine whether to respond to the first message. For example, the WTRU may determine to respond to the first message based on an amount of energy available to the WTRU. The WTRU may send a second message to the network based on a determination to respond to the first message. The second message may indicate a challenge response value, the amount of energy available to the WTRU, and / or a device-specific network challenge value.

[0007] The WTRU may determine whether the amount of energy available to the WTRU is equal to and / or greater than the estimated required energy level indicated by the first message. The WTRU may determine to respond to the first message when the amount of energy available to the WTRU is equal to and / or greater than the indicated estimated required energy level. The WTRU may generate the device-specific network challenge value based on a randomly generated number. The WTRU may use the one or more challenge response values to calculate the challenge response value.

[0008] The first message may indicate one or more locations. Each location of the one or more locations (e.g., as indicated by the first message) may be associated with one or more challenge values. The first message may indicate a requested action associated with the WTRU. The requested action may include one or more of: that the WTRU is to register to the network node, that the WTRU is to send data to an application server (AS) and / or a network node, that the WTRU is to send data to one or more other WTRUs, that the WTRU is to send a message to indicate that the WTRU is to send a message to indicate that the WTRU is available and / or located within range of a base station of the network, and / or that the WTRU is to send a message to an AS to indicate that the WTRU is available to receive downlink (DL) data. The data that is sent to the AS may be an application specific payload. The application specific payload may include data one or more of the data, an identity of a destination for the data, and / or an identity of a source of the data.

[0009] The WTRU may generate the device-specific network challenge value. The WTRU may generate the challenge response value. For example, the WTRU may generate the challenge response value based on one or more of the device-specific network challenge values, an identity of the WTRU, a provisioned key, and / or a network identity.

[0010] The WTRU may receive a third message, for example, from the network. The third message may indicate a device-specific network challenge response value, a (e.g., first) application specific payload, an indication of an action being requested, and / or a second challenge value. On a condition that the device-specific network challenge response value is correct, the WTRU may send a fourth message, for example, to the network. The fourth message may indicate a second challenge response value and / or a (e.g., second) application specific payload. An (e.g., first and / or second) application specific payload may include one or more of: an identity of a destination for data to be sent to an AS, a network node, and / or one or more other WTRUs; an identity of a source of the data; and / or ambient internet of things (loT) data. For example, the ambient loT data may include sensor data (e.g., sensor reading data). The WTRU may use the one or more challenge values to calculate the challenge response value.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0015] FIG. 2 depicts an example flow chart diagram illustrating authentication initiation messaging.

[0016] FIG. 3 depicts an example flow chart diagram illustrating authentication response messaging with extensible authentication protocol-authentication and key agreement (EAP-AKA).

[0017] FIG. 4 depicts an example flow chart diagram illustrating authentication response messaging with 5G-AKA.

[0018] FIG. 5 depicts an example flow chart diagram illustrating wireless transmit / receive unit (WTRU) ambient internet of things (loT) triggering.DETAILED DESCRIPTION

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

[0020] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscriptionbased 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 headmounted 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 WTRU.

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

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

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

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

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

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

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

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

[0029] The base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 toestablish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. 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.

[0030] 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. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E- UTRA, or WiFi radio technology.

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

[0032] 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. 1 A 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.

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

[0034] 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. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

[0038] 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 lightemitting 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 notphysically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

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

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

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

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

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

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

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

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

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

[0050] The ON 106 may facilitate communications with other networks. For example, the ON 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 ON 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.

[0051] Although the WTRU is described in FIGS. 1 A-1 D 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.

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

[0053] 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 in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11 e DLS or an 802.11 z 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.

[0054] When using the 802.11ac 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 by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in 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.

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

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

[0057] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11 ah relative to those used in 802.11 n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, 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).

[0058] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example 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 otherSTAs 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.

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

[0060] FIG. 1 D 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.

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

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

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

[0064] 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 Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. Asshown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

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

[0067] 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 WTRU 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.

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

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

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

[0071] 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 wirelesscommunication 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.

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

[0073] Systems, methods, and / or apparatuses with respect to network-triggered registration may be provided herein. A WTRU may receive a message. For example, the WTRU may receive a broadcast message from the network. The broadcast message may include one or more challenge value(s) (e.g., a first challenge value), one or more geographical locations where the WTRU maybe located, where the one or more challenge values may be used, an estimated required energy level to perform a requested action, and / or an indication that the device may respond with an indication of how much energy the device has available to perform an operation (e g., an amount of energy available to the WTRU). As used herein, the terms “device” and “wireless transmit receive unit” or “WTRU” may be used interchangeably.

[0074] The WTRU may use the content of the received broadcast message to determine to perform one or more of the following. The WTRU may send a response message, for example if the available power for the device is greater than or equal to the amount of energy that is indicated by an Estimated Required Energy value. For example, the WTRU may determine whether to respond to the broadcast message based on an amount of energy available to the WTRU. The WTRU may send a response message that indicates that the device does not have enough energy stored to perform the operation. If the device determines to send a response message, for example, the device may determine a challenge response value. The challenge response value maybe determined based on a calculation, which may have one or more calculation inputs. The one or more calculation inputs may include the challenge value and at least a device identity and / or a secret key. For example, both the device and secret key may be inputs to the calculation. If the device determines to send a response message, the response message may include the challenge response value, a device Stored Energy Estimate value (e.g., the amount of energy available to the WTRU), and / or a devicespecific network challenge value.

[0075] The WTRU may receive a trigger message. The trigger message may include a network challenge response value, an application specific payload, an indication of what action is requested, and / or a second challenge value.

[0076] The WTRU may determine to send a trigger response, for example, based on the network challenge response value being correct. The trigger response message may include a second challenge response value and / or an application specific payload.

[0077] An access and mobility function (AMF) may determine a value that represents an estimate of the amount of energy that one or more (e.g., each) device(s) may need to perform the request action. The AMF may send an action request towards an Access Network (AN). The action request may include one or more of the following. The action request may include the one or more challenge values, the one or more locations where one or more (e.g., each) challenge values may be used, an indication that the device may respond with an indication of how much energy the device has available, and / or an Estimated Required Energy for the request action.

[0078] The AMF may interact with the authentication server function (AUSF) to obtain a network challenge response value. The AMF may send, to the AUSF, the devicespecific network challenge value and / or the received device identity. The AUSF may respond with the network challenge response value. The AUSF may have been provisioned with the key of the device, and may use the (e.g., provisioned) key to determine the network challenge response value.

[0079] The AMF may compare the Stored Energy Estimate value that was received from the WTRU and compare it against the amount of energy that is required to perform the requested action. For example, the AMF may know the amount of energy that is required to perform the requested operation based on information that was receivedfrom the unified data management (UDM) / unified data repository (UDR). For example, the AMF may know the amount of energy that is required to perform the requested operation based on information that was provided by the application function (AF) (e.g., information that was received from the AF via the network exposure function (NEF)).

[0080] If the Stored Energy Estimate value is less than the amount of energy that is required to perform the requested action, the AMF may perform one or more of the following. The AMF may repeat one or more procedures (e.g., as described herein) so that the device can harvest more energy from the broadcasted signal. For example, the AMF may send a (e.g., an action) request to one or more AN Nodes that includes an indication that the device may (e.g., should) respond with an indication of how much energy the device has available to perform an operation. The AMF may initiate a different procedure so a signal is transmitted, and the device can use the signal for energy harvesting.

[0081] If the Stored Energy Estimate value is larger (e.g., greater) than the amount of energy that is required to perform the requested action, the AMF may send an action request toward the AN. The action request may include the network challenge response value, the application specific container, and / or another (e.g., new) challenge value.

[0082] The network may choose to send an application specific container to the WTRU. The application specific container may be encrypted. For example, the application specific container may be encrypted with a key that was received from the AUSF and / or may be specific to a device.

[0083] The AMF may determine to send (e.g., forward) the application specific payload to the AF and / or NEF, for example, if authentication is successful.

[0084] One or more mobile networks may include authentication. Authentication may be divided into one or more (e.g., two) procedures. For example, authentication may include authentication initiation messaging exchange. For example, authentication may include one or more authentication challenges.

[0085] FIG. 2 depicts an example flowchart illustrating authentication initiation messaging 200.

[0086] A WTRU authentication process may include a WTRU 202 sending (e.g., via an N1 message) a subscription concealed identifier (SUCI) and / or a 5G globally uniquetemporary identifier (5G GlITI) to the AMF and / or security anchor function (SEAF). For example, at 204, the WTRU 202 may send a SUCI and / or 5G-GUTI (e.g., via an N1 message) to an AMF 206a and / or SEAF 206b.

[0087] At 208, the SEAF 206b may send a request message to the ALISF 210 (e.g., Nausf_UEAuthentication_Authenticate Request). For example, the message 208 from the SEAF 206b to the AUSF 210 may include the SUCI and / or the serving network name (e.g., SN-name). Upon receiving the message 208 in the AUSF 210, the AUSF 210 may check the WTRU serving network name and / or may compare the WTRU serving network name with the expected serving network name. If the WTRU serving network name does not match the expected serving network name, the AUSF 210 may send a response that indicates the serving network is not authorized.

[0088] At 212, if the WTRU serving network name does match the expected serving network name, the request message 212 may be sent (e.g., via a Nudm_UEAuthentication_Get Request) from the AUSF 210 to the UDM 214 (e.g., and / or authentication credential repository (ARPF) and / or subscription identifier deconcealing function (SIDF)). For example, the AUSF 210 may send a request message 212 to the UDM 214 if the WTRU serving network name does match the expected serving network name. The message (e.g., request message) 214 may include: the WTRU SUCI and / or subscription permanent identifier (SUPI) and / or the serving network name (e.g., SN name).

[0089] At 216, upon reception, the UDM 214 may invoke the SIDF if SUCI is received, in order to gain the SUPI before replying to the request. Based on the SUPI value, the UDM 214 may determine (e.g., decide) the authentication mechanism. The SUPI may be sent (e.g., directly sent) from the WTRU 202 (e.g., instead of the SUCI). The authentication may start, for example, based on (e.g., after) this procedure.At 218, the WTRU 202 and UDM / ARPF / SIDF 214 may exchange one or more extensible authentication protocol (EAP) authentication messages. One or more authentication challenges may be provided herein. EAP-authentication and key agreement (EAP-AKA) may be provided herein. 5G-authentication and key agreement (5G-AKA) may be provided herein. EAP-AKA may be a method in EAP framework that uses AKA to share and / or distribute one or more keys.

[0090] FIG. 3 depicts an example flow chart of authentication response messaging 300. Generating an authentication vector may include calculating one or more values that may be used in an authentication procedure. At 304, the UDM 302 may generate authentication vector(s) (e.g., Random Number (RAND), Authentication Token (AUTN), Expected Response (XRES), Cipher Key (CK’), Integrity Key (IK’)) with an authentication management field separation bit equal to a first value (e.g., 1 ) and / or may send it (e.g., at 306) to the AUSF 308 (e.g., via a Nudm_UEAuthentication_Get Response, which may include an EAP-AKA’, AV, and / or SUPI). At 310, the AUSF 308 may send the EAP-Request / AKA’-Challenge message to the SEAF 314, for example, in a response message 310 (e.g., Nausf_UEAuthentication_Authenticate Response).Upon receiving the message from the AUSF 308, the SEAF 314 may send (e.g., at 316) the EAP-Request / AKA’-Challenge message to the WTRU 318 in a non-access stratum (NAS) message authentication request message. The SEAF 313 may include the 5G key set identifier (ngKSI) and / or the 5G anti-bidding down between architectures (ABBA) parameter in one or more (e.g., all) EAP-Authentication request messages to the WTRU 318. At 320, the WTRU 318 may calculate the authentication response. For example, the WTRU 318 may calculate the anchor key (KSEAF) in the same way as the AUSF 308 and / or may send the response to the AMF. The AMF may identify the partial native security context that is created if the authentication is successful and / or may set the ABBA parameter. At 322, the WTRU 318 may send an authentication response message (e.g., EAP Response / AKA’-Challenge) to the SEAF 314. At 324, the SEAF 314 may send the EAP Response / AKA’-Challenge to the AUSF (e.g., via Nausf_UEAuthentication_Authenticate Request). At 326, the AUSF 308 may verify the response. At 328, the AUSF 308 and the WTRU 318 may exchange (e.g., further exchange) EAP messages. At 330, the AUSF 308 may send a message to the SEAF 314 (e.g. Nausf_UEAuthentication_Authenitcate Response). For example, the message 314 may include an EAP success anchor key and / or SUPI. At 332, the SEAF 314 may send a message (e.g., N1 message) to the WTRU 318. For example, the message 332 may include EAP success, ngKSI, and / or ABBA.

[0091] 5G-AKA may be an enhancement of EAP-AKA where the home network receives confirmation of the WTRU successful authentication.

[0092] FIG. 4 depicts an example flowchart of authentication response messaging with 5G-AKA. As shown in FIG. 4, the UDM / ARPF 402 may calculate the KAusFfrom CK, IK, and / or SNN and / or may generate the 5G Home Environment AV (5G HE AV). For example, at 404, the UDM / ARPF may generate AV. The 5G HE AV may include the SUPI, Authentication and Key Management for Application (AKMA) indication, RAND, AUTN, XRES*, and / or root session key (KAUSF), and / or may be sent (e.g., at 406) to the AUSF 408 (e.g., via a Nudm_UEAuthentication_Get Response message). For example, in comparison to XRES, XRES* may be used in one or more other (e.g., similar) algorithms (e.g., in 4G).

[0093] At 410, the AUSF 408 may (e.g., temporarily) store (e.g., both) SUCI / SUPI and / or XRES* At 410, the AUSF 408 may generate a 5G AV from the received 5G HE AV. For example, the AUSF 408 may calculate an expected response token (HXRES*). At 412, the AUSF 408 may send (e.g., via a Nausf_UEAuthentication_Authenticate Response message) the 5G Serving Environment (5G SE AV) to the SEAF 414. The 5G SE AV may include RAND, AUTN, and / or HXRES* At 416, the SEAF 414 and / or AMF may send AUTN and / or RAND (e.g., transparently) to the WTRU 418 (e.g., via an authentication request). At 420, the WTRU 418 may calculate the authentication response RES and / or RES* (e.g., RES may be included for 4G AKA and / or RES* may be included for 5G AKA). At 422, the WTRU 418 may send the RES and / or RES* alongside CK and / or IK to the SEAF 414 (e.g., over an Authentication Response message). At 424, the SEAF 414 may calculate HRES* from HRES and / or may compare HRES* with HXRES, for example, to determine (e.g., check) whether HRES* matches HXRES. If HRES* matches HXRES, the SEAF 414 may consider the authentication successful and / or may send (e.g., at 426, via a Nausf_UEAuthentication_Authenticate Request message) RES*, alongside the one or more other content of the Authentication Response message, to the AUSF 408. At 428, the AUSF 408 may verify the response (e.g., RES* verification). For example, the AUSF 408 may determine if RES* matches the stored XRES*. If RES* matches XRES*, for example, the AUSF 408 may consider the authentication successful and / or may store KAUSF. At 430, the AUSF 408 may send an Authentication_Response message (e.g., an Nausf_UEAuthentication_Authenticate Response message, which may include Result,SUP I, and / or KSEAF) to the SEAF 414. The UDM 402 may be informed that the authentication is successful. For example, the ALISF 408 may send a message to the UDM 402 to indicate that the authentication is successful.

[0094] One or more ambient loT device types may be provided herein. For example, Type-A, Type-B, and / or Type-C ambient loT device types may be provided herein. The Type-A ambient loT device type may include one or more devices with no energy storage and no independent signal generation (e.g., backscattering transmission). The Type-B ambient loT device type may include one or more devices that have energy storage but do not have independent signal generation (e.g., backscattering transmission). Use of stored energy may include amplification for reflected signals. The Type-C ambient loT device type may include one or more devices that have energy storage and that have independent signal generation (e.g., active RF component for transmission).

[0095] Ambient loT devices may be limited in terms of their capability to generate signals and / or the amount of energy that is accessible to the device. Ambient loT devices may attempt to minimize the number and / or size of the messages that ambient loT devices exchange with the network. In order to minimize the number and size of the one or more messages that ambient loT devices exchange with the network, one or more procedures that integrate device triggering and mutual authentication (e.g., device and network authentication) may be used. One or more (e.g., any) procedure(s) may be designed to ensure that one or more devices are not triggered to perform one or more actions for which they do not have enough energy available to complete the one or more actions.

[0096] Systems, methods, and / or apparatuses are provided herein with respect to triggering ambient loT devices to perform action(s). A network may initiate an ambient broadcast towards the ambient device, for example, when it is required to perform one or more (e.g., certain) actions. When the network sends a broadcast message to one or more devices in an area to initiate the procedure, for example, the network may (e.g., also) include an authentication challenge value in the message. When one or more devices respond, for example, the one or more devices may include a challenge response value and / or a device-specific network challenge value. In this way, themessage that triggers interaction with the device(s) may be integrated with a procedure for authenticating the device(s) and the network.

[0097] The network may indicate to the device how much energy the device may need to execute the desired procedure. The device may respond to the network with an indication of how much energy is available to the device. This information exchange about how much energy is needed to perform the procedure may help the device avoid starting a procedure that cannot be completed because the device does not have enough energy available to complete the procedure.

[0098] The overall procedure may include one or more (e.g., two) portions. For example, a first portion may include WTRLI authentication, and a second portion may include network authentication.

[0099] A (e.g., first) portion of the procedure may include one or more of the following. The network may send, and the device may receive, an indication of how much energy is needed to perform a procedure and / or a series of one or more procedures. The device may send, and the network may receive, information about how much energy is available in the device. The network may authenticate the device.

[0100] A (e.g., second) portion of the procedure may include one or more of the following. The network may send, and the device may receive, an application specific container. The device may authenticate the network. The device may perform an action that is indicated in the application specific container.

[0101] The device authentication, network authentication, and / or negotiation of whether the device has enough power to perform the procedure may be integrated with device triggering. The number of interactions between the device and network may be minimized.

[0102] The network may trigger one or more (e.g., ambient loT) devices in an area to perform an action. The procedure may be triggered by an Application Function. For example, the procedure may be triggered when the application function wants to send data to one or more devices in the area, when the application function wants to receive data from one or more devices in the area, and / or when the application function wants to collect the identities of devices that are in the area.

[0103] FIG. 5 depicts an example flow chart diagram of WTRLI ambient loT triggering.

[0104] At 502, a WTRU 501 may be provisioned with a device identity and / or a key that is associated with the identity.

[0105] At 504, an AF 506 may send an action request to an NEF 508 (e.g., ambient_action_request). The request may include one or more of the following information: what types of device(s) may (e.g., should) perform the requested action; the identity of the device(s) that may (e.g., should) perform the requested action; location information; application types that may (e.g., should) perform the requested action; and / or an application specific container to be sent to the device(s) once authenticated.

[0106] The AF request sent at 504 to the NEF 508 may indicate what type(s) may (e.g., should) perform the requested action. For example, the device type may be Type-A, Type-B, or Type-C, as described herein. For example, a device may be stationary or mobile.

[0107] The AF request sent at 504 to the NEF 508 may identify the devices(s) that may (e.g., should) perform the requested action. Examples of identities may be a device subscription identity, such as a GPSI, that is formatted as an external identifier (e.g., FQDN), a device subscription identity such as a GPSI that is formatted as an IMSI, and / or a user identifier. The request (e.g., also) may include a group identifier such as an external group identifier (e.g., FQDN) that is associated with more than one device subscription. When a group identifier is included in the request, for example, it may be an indication that one or more (e.g., all) devices in the group are requested to perform the action. Additionally or alternatively, the AF may provide a number that indicates how many devices from the group may (e.g., should) perform the requested action.

[0108] The AF request sent at 504 to the NEF 508 may include location information. Inclusion of location information in the request may indicate that (e.g., only) devices in the indicated location are requested to perform the action. The format of the location information may be a service area identifier(s), tracking area identifier(s), GPS coordinates, and / or cell identifier(s).

[0109] The AF request sent at 504 to the NEF 508 may indicate one or more application types that may (e.g., should) perform the requested action. Examples of applicationtypes may include one or more inventory applications and / or one or more sensory applications.

[0110] The AF request sent at 504 to the NEF 508 may include an application specific container that may (e.g., should) be sent to the one or more devices, for example, once they are authenticated. The application specific container may include one or more instructions on what application specific functions the device may (e.g., should) perform. For example, the application specific container may indicate that the device may (e.g., should) send a report to a server. The identity and / or address of the server may be included in the container. For example, the application specific container may indicate that the device may (e.g., should) perform an action. The identity of the action may be included in the container.

[0111] The combination of information in the request from the AF 506 may be used by the (e.g., 5G) system to determine which device(s) may (e.g., should) perform the requested action. For example, if the request includes both location information and application type information, the (e.g., 5G) system may determine that (e.g., only) devices that match both the location information and application type information are requested to perform the action.

[0112] The request 504 may indicate what action is requested of the one or more targeted devices. Examples of requested actions may include one or more of the following. The request may indicate that the requested action is that the device register to the network. The request may indicate that the requested action is that the device send data to an application server and / or a network function. The request may indicate that the requested action is that the device send data to one or more other devices. The request may indicate that the requested action is that the device contact an application server, and / or a network function, to demonstrate that the device is available and / or located within the reach of the one or more base stations of the network. The request may indicate that the requested action is that the device contact an application server, and / or a network function, to receive downlink data.

[0113] The NEF 508 may receive the message 504 from the AF 506. Reception of the message from the AF 506 may trigger the NEF 508 to perform a procedure to determine the one or more identities of the one or more devices that may (e.g., should) performthe requested action. For example, the NEF 508 may query a UDM / UDR 510 to determine the identities of the devices that meet the criteria that was indicated in the request from the AF 506. For example, the request 514 from the AF 506 may have included the external identifier of one or more (e.g., ten) devices and / or location information. The NEF 508 may query the UDM / UDR 510 to determine which of the one or more (e.g., ten) devices meet the criteria of being in the indicated location. The NEF 508 may (e.g., then) determine to continue the procedure and / or (e.g., only) target the subset of one or more devices that meet the indicated criteria. Additionally or alternatively, the NEF 508 may determine the one or more network functions (e.g., AMF 512) that are serving the one or more devices. For example, the UDM / UDR 510 may indicate the identity of the AMF 512 that serves one or more (e.g., each) device(s).

[0114] The NEF 508 (e.g., also) may determine a value that represents an estimate of the required amount of energy for one or more (e.g., each) device(s) to perform the requested action. The value (e.g., of energy) may be determined based on interaction with the UDM / UDR 510. For example, the UDM / UDR 510 may provide the NEF 508 with information about the one or more devices that the NEF 508 uses to determine the value. The value may be referred to as Estimated Required Energy.

[0115] At 514, the NEF 508 may (e.g., then) send an action request to one or more (e.g., each) of the AMFs 512 that serve the one or more devices. The action request 514 may include the identity of the one or more devices, (e.g., any) information included in the ambient_action_request (e.g., as described herein), and / or the Estimated Required Energy. The AMF 512 may perform one or more (e.g., all) of the processes described herein, for example if one or more AFs 506 are trusted (e.g., an AF 506 may be considered trusted if a mobile network operator permits the AF 506 to connect to network nodes such as the AMF 512 and / or AF 506).

[0116] The AMF 512 may receive the request 514 from the NEF 508. The AMF 512 may (e.g., then) determine which AN Node(s) (e.g., base station(s)) serve the one or more locations that are indicated in the request. The AMF 512 may (e.g., then) determine a challenge value. The challenge value may be determined based on interaction with a network function (e.g., such as AUSF 516). For example, the AMF 512 may send the AUSF 516 information (e.g., some, all) that was received in the request from the AUSF516 . The AUSF 516 may use this information to generate a challenge value. The AMF 512 may request that the AUSF 516 generate one or more (e.g., multiple) challenge values. For example, if the AMF 512 determined that the device action request will be sent to one or more (e.g., multiple) AN Nodes and / or one or more (e.g., multiple) cells, the AMF 512 may request a unique challenge value for one or more (e.g., each) AN Node(s) and / or cell(s). The AUSF 516 may respond to the AMF 512, for example, by providing one or more challenge values.

[0117] The AMF 512 may determine a value that represents an estimate of the amount of energy that one or more (e.g., each) device(s) need to perform the requested action. The value may be determined based on interaction with the UDM / UDR 510. For example, the UDM / UDR 510 may provide the NEF 508 with information about the one or more devices that the AMF 512 uses to determine the value. The value may be referred to as Estimated Required Energy.

[0118] At 518, the AMF 512 may (e.g., then) send an action request to one or more (e.g., each) of the AN Nodes 520 that serve the one or more devices. The action request 518 may include one or more of: the identities of the one or more devices; information (e.g., some, any, all) that was provided by the AF 506 and / or NEF 508, as described herein; the one or more challenge values; the one or more locations where one or more (e.g., each) of the challenge values may be used; and / or an indication that the device may respond with an indication of how much energy the device has available to perform an operation.

[0119] At 522, the AN 520 may send a message (e.g., broadcast signal request message) to the WTRU 501 . For example, upon receiving the action request from the AMF 512, the AN Node 520 may broadcast a signal message request toward the one or more ambient devices (e.g., such as the WTRU 501 ). The broadcast message signal may convey information to a group of ambient devices (e.g., that includes the WTRU 501). The signal may be a message that includes information (e.g., any information) that was received in the action request that was received from the AMF 512 (e.g., as described herein). The signal may be formatted in a way such that the one or more devices that receive the signal can reflect the signal in a way that conveys information back to the AN node 520. The signal may be formatted in a way that conveysinformation to the device. The format of the signal may convey (e.g., any of the) information that was received in the action request that was received from the AMF 512 (e.g., as described herein). For example, the format of the signal may indicate that one or more (e.g., certain) groups of devices may (e.g., should) reflect information back to the AN Node 520. For example, the first message may indicate one or more challenge values, an estimated required energy level to perform a requested action (e.g., by the AF 506), and / or an indication that the WTRU 501 should respond with an indication of an amount of energy available to the WTRU 501 . For example, the first message may (e.g., further) indicate one or more locations, where each location of the one or more locations is associated with one or more challenge values.

[0120] The first message (e.g., received at 522) may indicate a requested action associated with the WTRU 501 (e.g., as described herein). The requested action may include one or more of that the WTRU 501 is to register to the network, that the WTRU 501 is to send data to an AS and / or a network node, that the WTRU 501 is to send data to one or more other WTRUs, that the WTRU 501 is to send a message to indicate that the WTRU 501 is available and / or located within range of a base station of the network, and / or that the WTRU 501 is to send a message to an AS to indicate that the WTRU 501 is available to receive downlink data. The data that is sent to the AS may be an application specific payload. The application specific payload may include one or more of the data, an identity of a destination for the data, and / or an identity of a source of the data.

[0121] At 523, the WTRU 501 may determine whether to respond to the first message. For example, the WTRU 501 may determine whether to respond to the first message based on an amount of energy available to the WTRU 501. The WTRU 501 may determine whether the action is to be performed in response to the received signal, for example, based on (e.g., after) receiving the broadcast signal. The WTRU 501 may use information associated with the signal (e.g., the format of the signal and / or the content of the message) to determine whether to transmit a response to the AN Node 520. For example, the WTRU 501 may determine to respond (e.g., only) if the signal indicates the identity of the WTRU 501 , the identity of a group that the WTRU 501 is associated with, and / or a device type (e.g., as described herein) that the WTRU 501 is associatedwith. For example, the WTRU 501 may determine to respond (e.g., only) if the signal indicates a desire (e.g., need) for the WTRU 501 to report information (e.g., a sensor reading) and the WTRU 501 has information available to report. For example, the WTRU 501 may determine to respond (e.g., only) if the signal indicates an Estimated Required Energy value, and the amount of energy available to the WTRU 501 is greater than or equal to the amount of energy that is indicated by the Estimated Required Energy value. The WTRU 501 may determine whether the amount of energy available to the WTRU 501 is equal to or greater than the estimated required energy level indicated by the first message. The WTRU 501 may determine to respond to the first message when the amount of energy available to the WTRU 501 is equal to or greater than the indicated estimated required energy level. Additionally or alternatively, the WTRU 501 may determine to respond and / or indicate in the response that the WTRU 501 does not have enough energy stored to perform the operation (e.g., the amount of energy available to the device is less than the amount indicated in the received broadcast message).

[0122] If the WTRU 501 determines to send a response message, the device may determine a challenge response value. The challenge response value may be determined based on a calculation. The calculation input(s) may include the challenge value and / or (e.g., at least) the WTRU 501 identity and / or secret key. For example, both the WTRU 501 identity and secret key may be inputs to the calculation.

[0123] At 524, the WTRU 501 may send a second message (e.g., such as a broadcast signal response message) to the network (e.g., to the AN 520). For example the WTRU 501 may send the second message to the network based on a determination to respond to the first message. The WTRU 501 may send the second (e.g., response) message to the AN node 520. The second (e.g., response) message 524 may include the device identity, the challenge response, a device Stored Energy Estimate value, an application specific payload, and / or a device specific network challenge value. For example, the second message may indicate a challenge response value, the amount of energy available to the WTRU 501 , and / or a device-specific network challenge value.

[0124] The Stored Energy Estimate value may represent the amount of energy stored in combination of battery(s) and / or capacitor(s) of the WTRU 501 . The Stored EnergyEstimate value may represent the amount of the energy the WTRU 501 expects to have accessible to it in order to complete an operation with the network.

[0125] The (e.g., first and / or second) application specific payload may include information that is application specific (e.g., the identity of a destination for the data, and / or identity of the source of the data, and / or a data such as sensor reading). For example, the (e.g., first and / or second) application specific payload may include one or more of: an identity of a destination for data to be sent to an AS, a network node, and / or one or more other WTRUs; an identity of a source of the data; and / or ambient internet of things (loT) data (e.g., such as sensor reading data). If the first message (e.g., received at 522), indicated that the requested action is that the WTRU 501 send data to an AS and / or a network node, the WTRU 501 may include an application specific payload in the second message 524.

[0126] The device-specific network challenge value may be generated by the WTRU 501 in order to authenticate the network. When the WTRU 501 generates the network specific challenge value, for example, the WTRU 501 may (e.g., also) generate an expected network challenge response. The device-specific network challenge value may be a number that the device generates in a random fashion. For example, the device-specific network challenge value may be based on a randomly generated number. The expected network challenge response may be based on (e.g., the result of) a calculation. One or more inputs to the calculation may include the device-specific network challenge value and / or at least one of the device’s identity, the key that was provisioned (e.g., as described herein), and / or a network identity. For example, the WTRU may generate a device specific network challenge value. For example, the WTRU may generate a challenge response value based on one or more of the devicespecific network challenge values, an identity of the WTRU, a provisioned key, and / or a network identity. The network identity may have been received in the signal message request broadcast by the AN node 520 (e.g., as described herein), and / or in a separate broadcast message. The device may store the expected network challenge response value and / or may not transmit it.

[0127] The WTRU 501 may send the broadcast signal response message by reflecting the received device action request. The reflection may be performed such that it conveys the information listed herein (e.g., above).

[0128] At 526, the AN Node 520 may send (e.g., forward) the information that was received in the response from the device to the AMF 512.

[0129] At 528, the AUSF 516 may identify the WTRU 501 and / or check the challenge response. The AMF 512 may interact with the AUSF 516 to check the challenge response value. For example, the AMF 512 may send, to the AUSF 516, the challenge response value, the received device identity, the location that the device was located in when it sent the challenge response, and / or the challenge value that was sent in the location. The AUSF 516 may respond with an indication of whether or not the challenge response value is correct and / or if the device, and / or the device response, can be considered authenticated.

[0130] The AMF 512 may (e.g., also) interact with the AUSF 516 to obtain a network challenge response value. For example, the AMF 512 may send, to the AUSF 516 , the network challenge value and / or the received device identity. The AUSF 516 may respond with the network challenge response value. The AUSF 516 may have been provisioned with the key of the device (e.g., as described herein) and / or the AUSF 516 may use the (e.g., provisioned) key to determine the network challenge value. The AMF 512 may interact (e.g., as described herein) with the AUSF 516 to obtain another (e.g., new) challenge value. The other (e.g., new) challenge value may be sent to the AN Node 520 with the action trigger message.

[0131] At 530, if the AUSF 516 indicates that the response from the device has been authenticated, for example, the AMF 512 may check if the device has enough energy stored to perform the action that was requested by the AF 506 (e.g., as described herein). The AMF 512 may compare the Stored Energy Estimate value that was received from the WTRU 501 and / or may compare it against the amount of energy that is required to perform the requested action. The AMF 512 may know the amount of energy that is required to perform the requested operation based on information that was received from the UDM / UDR 510 and / or based on information that was provided by the AF 506 (e.g., information that was received from the AF 506 via the NEF 508).

[0132] If the device indicated an amount of stored energy that is less than the amount required to perform the requested action, for example, the AMF 512 may (e.g., then) repeat one or more procedures as described herein so that the device can harvest more energy from the broadcast signal. For example, the AMF 512 may send an action request to one or more AN Nodes 520 that includes an indication that the device may (e.g., should) respond with an indication of how much energy the device has available to perform an operation. The AMF 512 may initiate a different procedure so that a signal is transmitted that the device can use for energy harvesting.

[0133] Prior to sending the action trigger to the AN Node 520, and as the device has now been authenticated, the AMF 512 may determine to send the application specific container to the WTRU 501 . The application specific container may be encrypted with a key that was received from the ALISF 516. The key may be specific to a device.

[0134] At 532, the AMF 512 may send an action request toward the AN 520. The action request may include the network challenge response value, application specific container, and / or other (e.g., new) challenge value.

[0135] At 534, the AN Node 520 may broadcast the action request (e.g., as described herein). For example, the AN 520 may send (e.g., broadcast) a third message (e.g., Action_Trigger_message) to a WTRU 501 . The WTRU 501 may receive the third message from the network. The third message may indicate a device-specific network challenge response value, an (e.g., first) application specific payload, an indication of an action being requested, and / or a second challenge value. Additionally or alternatively, the action request may include the network challenge response value.

[0136] The WTRU 501 may receive the action trigger request 534. When the WTRU 501 receives the action trigger request 504, the device (e.g., WTRU 501 ) may check if the network challenge response value matches the expected network challenge response value that was calculated (e.g., as described herein). For example, the WTRU 501 may use the one or more challenge values to calculate the challenge response value. If the values match, the WTRU 501 may consider the network to be authenticated. If the values do not match, the WTRU 501 may consider the network to not be authenticated and / or may determine (e.g., decide) to skip the rest of the procedure. If the network isnot authenticated, the WTRU 501 may determine to not follow one or more instructions of the network.

[0137] The device (e.g., WTRU 501 ) may decrypt the application specific container and / or may use the content(s) to determine the content(s) of an application specific payload to send back to the network. The WTRU 501 may (e.g., then) respond to the device action trigger (e.g., as described herein). For example, at 536, the WTRU 501 may send a message (e.g., Action_Trigger_Message_Response) to the AN 520. For example, on a condition that the device-specific network challenge response value is correct, the WTRU 501 may send a fourth message 536 to the network. The fourth message 536 may indicate a second challenge response value and / or an application specific payload.

[0138] At 538, an authentication challenge check may be performed. The AN Node 520 may receive the response 536 and / or may send (e.g., forward) the response to the AMF 512 (e.g., as described herein). For example, the AN 520 may send the response 538 to the AMF 512. The AMF 512 may check the challenge response (e.g., as described herein).

[0139] At 540, if the challenge response is determined to be correct, for example, the AMF 512 may determine to send (e.g., forward) the application specific payload to the NEF 508 (e.g., in the case of untrusted AF 506). For example, at 540, the AMF 512 may send an ambient action response message to the NEF 508.

[0140] At 542, the NEF 508 may send (e.g., forward) the application specific payload to the AF 506. For example, the NEF 508 may send the ambient action response to the AF 506.

[0141] The processes and instrumentalities described herein may apply in any combination, may apply to other wireless technologies, and for other services.

[0142] A WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc. WTRU may refer to application-based identities, e.g., user names that may be used per application.

[0143] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but arenot limited to, electronic signals (transmitted over wired and / or wireless connections) and / or 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, but not limited to, internal hard disks and removable disks, magnetooptical media, and / or optical media such as CD-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMS:1 . A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving a first message that is broadcast by a network, the first message indicating one or more challenge values, an estimated required energy level to perform a requested action, and an indication that the WTRU should respond with an indication of an amount of energy available to the WTRU; determining whether to respond to the first message based on an amount of energy available to the WTRU; and sending a second message to the network based on a determination to respond to the first message, the second message indicating a challenge response value, the amount of energy available to the WTRU, and a device-specific network challenge value.

2. The method of claim 1 , further comprising determining whether the amount of energy available to the WTRU is equal to or greater than the estimated required energy level indicated by the first message.

3. The method of claim 1 , further comprising determining to respond to the first message when the amount of energy available to the WTRU is equal to or greater than the indicated estimated required energy level.

4. The method of claim 1 , further comprising generating the device-specific network challenge value based on a randomly generated number.

5. The method of claim 1 , wherein the first message further indicates one or more locations, wherein each location of the one or more locations is associated with one or more challenge values.

6. The method of claim 1 , wherein the first message further indicates a requested action associated with the WTRU, and wherein the requested action comprises one ormore of that the WTRU is to register to the network, that the WTRU is to send data to an application server (AS) or network node, that the WTRU is to send data to one or more other WTRUs, that the WTRU is to send a message to indicate that the WTRU is available and located within range of a base station of the network, or that the WTRU is to send a message to an AS to indicate that the WTRU is available to receive downlink data, wherein the data that is sent to the AS is an application specific payload, and wherein the application specific payload comprises one or more of the data, an identity of a destination for the data, or an identity of a source of the data.

7. The method of claim 1 , further comprising: generating the device-specific network challenge value; and generating the challenge response value based on one or more of the devicespecific network challenge values, an identity of the WTRU, a provisioned key, or a network identity.

8. The method of claim 1 , further comprising receiving a third message from the network, the third message indicating a device-specific network challenge response value, a first application specific payload, an indication of an action being requested, and a second challenge value, wherein, on a condition that the device-specific network challenge response value is correct, the method further comprising sending a fourth message to the network, the fourth message indicating a second challenge response value and a second application specific payload.

9. The method of claim 8, wherein the first application specific payload or the second application specific payload comprises one or more of: an identity of a destination for data to be sent to an application server (AS), a network node, or one or more other WTRUs; an identity of a source of the data; or ambient internet of things (loT) data, wherein the ambient loT data comprises sensor data.

10. The method of claim 1 , further comprising using the one or more challenge values to calculate the challenge response value.

11. A wireless transmit / receive unit (WTRU) comprising: a processor configured to: receive a first message that is broadcast by a network, the first message indicating one or more challenge values, an estimated required energy level to perform a requested action, and an indication that the WTRU should respond with an indication of an amount of energy available to the WTRU; determine whether to respond to the first message based on an amount of energy available to the WTRU; and send a second message to the network based on a determination to respond to the first message, the second message indicating a challenge response value, the amount of energy available to the WTRU, and a device-specific network challenge value.

12. The WTRU of claim 11 , wherein the processor is further configured to determine whether the amount of energy available to the WTRU is equal to or greater than the estimated required energy level indicated by the first message.

13. The WTRU of claim 11 , wherein the processor is further configured to determine to respond to the first message when the amount of energy available to the WTRU is equal to or greater than the indicated estimated required energy level.

14. The WTRU of claim 11 , wherein the processor is further configured to generate the device-specific network challenge value based on a randomly generated number.

15. The WTRU of claim 11 , wherein the first message further indicates one or more locations, wherein each location of the one or more locations is associated with one or more challenge values.

16. The WTRU of claim 11 , wherein the first message further indicates a requested action associated with the WTRU, and wherein the requested action comprises one or more of that the WTRU is to register to the network, that the WTRU is to send data to an application server (AS) or network node, that the WTRU is to send data to one or more other WTRUs, that the WTRU is to send a message to indicate that the WTRU is available and located with range of a base station of the network, or that the WTRU is to send a message to an AS to indicate that the WTRU is available to receive downlink data, wherein the data that is sent to the AS is an application specific payload, and wherein the application specific payload comprises data one or more of the data, an identity of a destination for the data, or an identity of a source of the data.

17. The WTRU of claim 11 , wherein the processor is further configured to: generate the device-specific network challenge value; and generate the challenge response value based on one or more of the devicespecific network challenge values, an identity of the WTRU, a provisioned key, or a network identity.

18. The WTRU of claim 11 , wherein the processor is further configured to receive a third message indicating a device-specific network challenge response value, a first application specific payload, an indication of an action being requested, and a second challenge value, wherein, on a condition that the device-specific network challenge response value is correct, the processor is further configured to send a fourth message to the network, the fourth message indicating a second challenge response value and a second application specific payload.

19. The WTRU of claim 21 , wherein the first application specific payload or the second application specific payload comprises one or more of: an identity of a destination for data to be sent an application server (AS), a network node, or one or more other WTRUs; an identity of a source of the data;ambient internet of things (loT) data, wherein the ambient loT data comprises sensor data.

20. The WTRLI of claim 11 , wherein the processor is further configured to use the one or more challenge values to calculate the challenge response value.

Images