Methods, architectures, apparatuses and systems for ambient-powered internet of things device authentication and identification management

Abstract

A method, implemented in a wireless transmit receive unit (WTRU) is described herein. The method may include (i) sending a first message to a first network element of a cellular network, the first message indicating an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU, (ii) receiving a second message from the first network element of the cellular network, the second message indicating one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers, (iii) determining that a pseudo identifier of the one or more pseudo identifiers may be valid based on the valid time period, and (iv) sending a request message to a second network element of the cellular network indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR AMBIENT- POWERED INTERNET OF THINGS DEVICE AUTHENTICATION AND IDENTIFICATION MANAGEMENTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of US Patent Application No. 63 / 540,982 filed September 28, 2023, which is incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure is generally directed to the fields of communications, software and encoding, including methods, architectures, apparatuses, and systems directed to ambient-powered internet of things (loT) device authentication and identification management.BACKGROUND

[0003] An ambient power enabled loT device may be seen as a kind of loT device that may harvest energy from the environment, such as e.g., any of wireless radio waves, motion, vibration, piezoelectricity, solar and wind power, etc. Embodiments described herein have been designed with the foregoing in mind.BRIEF SUMMARY

[0004] Methods, architectures, apparatuses, and systems directed to ambient-powered loT device authentication (e.g., authorization) and identification management are described herein. In an embodiment, a wireless transmit / receive unit (WTRU) is described. The WTRU may include circuitry including any of transmitter, a receiver, a processor, and a memory. The WTRU may be configured to send a first message to a first network element of a cellular network. In various embodiments, the first message may indicate an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU. In various embodiments, the network access identifier may be to be forwarded to an EAP server. The WTRU may be configured to receive a second message from the first network element of the cellular network. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. The WTRU may be configured to determine that a pseudo identifier of the one or more pseudo identifiers may be valid based on the valid time period. The WTRU may be configured to send a request message to a second network element of the cellular network indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

[0005] In an embodiment, a method implemented in a wireless transmit / receive unit (WTRU) is described. The method may include sending a first message to a first network element of a cellular network. In various embodiments, the first message may indicate an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU. In variousembodiments, the network access identifier may be to be forwarded to an EAP server. The method may include receiving a second message from the first network element of the cellular network. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. The method may include determining that a pseudo identifier of the one or more pseudo identifiers may be valid based on the valid time period. The method may include sending a request message to a second network element of the cellular network indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

[0006] In an embodiment, a network element of a cellular network is described. The network element may include circuitry including any of transmitter, a receiver, a processor, and a memory. The network element may be configured to receive a first message from a wireless transmit / receive unit (WTRU). In various embodiments, the first message may indicate an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU. The network element may be configured to send an EAP message to an EAP server. In various embodiments, the EAP message may indicate the network access identifier of the WTRU. The netw ork element may be configured to send a second message to the WTRU. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. The network element may be configured to receive a request message from the WTRU. In various embodiments, the request message may indicate a pseudo identifier of the one or more pseudo identifiers as a WTRU identifier.

[0007] In an embodiment, a method implemented in a network element of a cellular network is described. The method may include receiving a first message from a wireless transmit / receive unit (WTRU). In various embodiments, the first message may indicate an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU. The method may include sending an EAP message to an EAP server. In various embodiments, the EAP message may indicate the network access identifier of the WTRU. The method may include sending a second message to the WTRU. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. The method may include receiving a request message from the WTRU. In various embodiments, the request message may indicate a pseudo identifier of the one or more pseudo identifiers as a WTRU identifier.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction w ith drawings appended hereto. Figures in such drawings, like thedetailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref") in the FIGs. indicate like elements, and wherein:

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

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

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

[0012] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0013] FIG. 2 is a diagram illustrating an example method for cellular network authentication and authorization;

[0014] FIG. 3 is a diagram illustrating an example of extensible authentication protocol (EAP) bootstrapping through an intermediate network element;

[0015] FIG. 4 is a diagram illustrating an example of EAP bootstrapping through the control plane of a cellular network;

[0016] FIG. 5 is a diagram illustrating an example of EAP bootstrapping through the control plane of a cellular network;

[0017] FIG. 6 is a diagram illustrating an example of pseudonym and session key insertion in a cellular network;

[0018] FIG. 7 is a diagram illustrating an example of network access authorization and uplink data transmission using device pseudonym;

[0019] FIG. 8 is a diagram illustrating an example method for ambient-powered loT device authentication and identification management;

[0020] FIG. 9 is a diagram illustrating an example method for ambient-powered loT device authentication and identification management, implemented in a WTRU; and

[0021] FIG. 10 is a diagram illustrating an example method for ambient-powered loT device authentication and identification management, implemented in a network element.DETAILED DESCRIPTION

[0022] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, componentsand circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.Example Communications System

[0023] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.

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

[0025] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other netw orks 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 wirelesssignals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

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

[0027] 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 an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

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

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

[0031] 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 1 16 using New Radio (NR).

[0032] 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 ty pes of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

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

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

[0035] 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 an NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

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

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

[0038] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 1 18, a transceiver 120, atransmit / 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 elements / peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0039] 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 ty pe of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

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

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

[0042] 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 thetransmit / 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.

[0043] The processor 1 18 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 cry stal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any ty pe 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 ty pe of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory' that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

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

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

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

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

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

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

[0052] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S I 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.

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

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

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

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

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

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

[0059] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary' channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used 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.

[0060] 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 adj acent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

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

[0062] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and earners, are reduced in 802. 1 laf and 802. 1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TVwhite space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support meter type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (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).

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

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

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

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

[0067] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b. 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or 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., including a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

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

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

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

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

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

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

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

[0075] In view of FIGs. 1A-1D, and the corresponding description of FIGs. 1A-1D, one or more, or all. of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein, may be performed by one or more emulation elements / devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

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

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

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

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

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

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

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

[0083] A symbol 7’ (e.g., forward slash) may be used herein to represent ‘and / or’, where for example, ‘A / B’ may imply ‘A and / or B’.Overview

[0084] An ultra-low complexity device such as e.g., an ambient-powered loT (A IoT) device may initiate an extensible authentication protocol (EAP) bootstrapping procedure with an EAPserver using lightweight EAP procedures. The A_IoT device may obtain a pseudonym and / or session key through the bootstrapping procedure. Any of the obtained pseudonym and session key may be inserted in a cellular network by the EAP server and may be associated with any real identifier of the A_IoT device. When the A_IoT device accesses the cellular network, the A_IoT device may identify itself using (e.g., based on) the pseudonym. The network may grant the access if the received pseudonym exists (e.g., matches an existing record) in the network database.

[0085] Throughout embodiments described herein the terms "ambient-powered loT device”, "ambient power-enabled loT device” and “A IoT device” may be used interchangeably to refer to a low complexity device that may be powered based on ambient power. Embodiments are described herein with an A IoT device as an example of device. Embodiments described herein are not limited to A IoT devices and may be applicable to any kind of WTRUs.

[0086] Throughout embodiments described herein the terms “pseudonym” and “pseudoidentifier” may be used interchangeably to refer to any kind of identifier that may be used to identify a (e.g., A_IoT) device.

[0087] Throughout embodiments described herein the term “real identifier(s), “device identifier” e.g., of the A_IoT device may be used interchangeably with “any of first (e.g., physical) identifier and second (e.g., logical) identifier (e.g., of the A_IoT device)”.

[0088] For the sake of simplicity, embodiments are described herein for A IoT authentication or authorization. Embodiments described herein may be applicable to any of A IoT authentication, A IoT authorization, and A IoT authentication and authorization.Ambient Powered Enabled loT (A IoT) Device

[0089] An ambient power enabled loT device may be seen as a kind of loT device that may harvest energy from the environment, such as e.g.. any of wireless radio waves, motion, vibration, piezoelectricity, solar and wind power, etc. A_IoT devices may be battery -less or may have limited energy storage (e.g., using a capacitor). Ambient power-enabled loT devices may be used in industrial wireless sensor networks where the environment may be harsh (e.g., extremely high or low temperature) and for which battery-less, maintenance-free and long service life may be appropriate. A_IoT devices may be present in smart logistics and / or smart warehousing. The low- cost, small-form, battery-lessness and durability may make them suitable to be attached to large amounts of goods and may facilitate more efficient goods identifying, sorting, tracking and inventory.

[0090] A study item has been started by the third-generation partnership proj ect (3GPP) to study the potential sendee requirement to support ambient power-enabled loT device in 3GPP wireless networks. The study item is described in 3GPP Work Item Description SP-220085, “Study onAmbient power-enabled Internet of Things and in 3GPP Technical Report TR 22.840, “Study on Ambient power-enabled Internet of Things (Release 19)”, V2.0.0, 2023-09.

[0091] Three categories of A_IoT devices (e.g.. which may be referred to herein as device A, device B and device C) may be identified in 3GPP TR 38.848, “Study on Ambient loT (Internet of Things) in RAN”, VI.0.0, 2023-09.

[0092] Device A may have no energy' storage, no independent signal generation and / or amplification, e.g., backscattering transmission.

[0093] Device B may include energy storage, no independent signal generation, e.g., backscattering transmission. The stored energy may be used, for example, for amplification of reflected signals.

[0094] Device C may include energy storage, may have independent signal generation capabilities, such as e.g.. active RF component(s) for transmission.

[0095] Ultra-low complexity A IoT devices may not support 3GPP authentication and key agreement (AKA), universal integrated circuit card (UICC), or embedded subscriber identification module (eSIM) functionality. A_IoT devices may not have a cellular network subscription. Such devices may not have any of the 3GPP identities such as any of a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), an international mobile station equipment identity (IMEI), a mobile station international subscriber directory number (MSISDN), etc. An A_IoT device may not support primary authentication and authorization procedures (such as e.g., 5G-AKA, EAP-AKA, etc.) used in cellular networks. For serving A_IoT devices, a cellular network may implement one or more reduced-complexity authentication & authorization (A&A) mechanisms that may be supported by the A IoT devices.

[0096] Reduced-complexity authentication and authorization (A&A) mechanisms may not be able to generate security keys that can be used to protect (e.g., encrypt) any of transmitted data, received data, and the device identity. Related to primary A&A. embodiments described herein may alloyv the A_IoT devices to securely transmit / receive data and protect their identities if they cannot rely on the security keys generated from the primary authentication procedures.

[0097] Some procedures, such as paging, may be based on 3GPP identifiers. For example, a 5G serving temporary mobile subscriber identity7(5G S-TMSI) may be used in paging occasion calculation and may be included in paging records. Embodiments described herein describe whether and how 3GPP identifiers may be assigned, hoyv 3GPP identifiers may be associated with the (e.g., own) identifiers of the A IoT device, and hoyv 3GPP identifiers may be used in one or more service procedures.

[0098] Embodiments described herein describe how ultra-low complexity A IoT devices may be authenticated and authorized by a cellular network, if 3GPP standard primary A&A procedures are not supported.

[0099] Embodiments described herein describe mechanisms to protect application data and device identity in A IoT device communication.

[0100] Embodiments described herein describe mechanisms to assign and manage identifiers to enable cellular network procedures (such as e.g., any of paging, device triggering, data transmission / receiving. etc.).

[0101] In embodiments described herein, an A_IoT device may have its (e.g., own) device identifiers (e.g., which may be different from 3GPP identifiers). For example, an A IoT device may have a first (e.g., physical) identifier associated with its hardware (e.g., a serial number) and a second (e.g., logical) identifier that may denote (e.g., be associated with) any of an application name, a product name, a piece of software, etc. (e.g., electronic product code).Cellular Network Access Authorization Based on EAP Bootstrapping

[0102] In an embodiment, cellular network access authorization may be based on EAP bootstrapping. An A_IoT device may initiate an EAP bootstrapping procedure with any of an authentication, authorization and accounting (AAA) server or an extensible authentication protocol (EAP) server, through any of the control plane and the user plane of a cellular network. The A IoT device may obtain a session key and / or one or more temporary identifiers through the EAP bootstrapping. The obtained session key and / or one or more temporary identifiers may be communicated (e.g., transmitted) to the cellular network by the EAP (e.g., AAA) server. The A_IoT device and the cellular network may use the session key and / or the one or more temporary identifiers to any of perform reduced-complexity A&A and secure the data transmission.

[0103] The cellular network access authorization may include (1) a lightweight EAP bootstrapping through any of the control plane and the user plane of the cellular network, (2) an insertion of the identifiers and the session key generated by the bootstrapping procedure in the cellular network; and (3), a use of the identifiers and the session key in network A&A and various service procedures.

[0104] FIG. 2 is a diagram illustrating an example method for cellular network authentication and authorization.

[0105] As shown at 21, an A IoT device may perform a lightweighted EAP bootstrapping to obtain any of a session key and one or more identifiers, which may be stored in the A_loT device. As shown at 22, the 5G network may insert any of the generated identifiers and the session key.As show n at 23, the A_IoT device may use any of the session key and the identifiers for any of A&A and one or more service procedure.Example of EAP Bootstrapping

[0106] An A IoT device may initiate EAP bootstrapping procedure with an EAP server before the A IoT device may access the cellular network (e.g., including any of public and non-public networks) for services. The EAP bootstrapping procedure may aim at generating any of a pseudo identifier, a session key and a certificate, in the A_IoT device and the network, that may be used later for any of network A&A and other procedures. The A IoT device may support (e.g., may be capable of performing) one or more EAP methods (e.g., extensible authentication protocol transport layer security (EAP-TLS), etc.) and may include the credentials (e.g.. any of pre-shared key, certificate, etc.) associated with the supported EAP method.

[0107] The A_IoT device may perform the EAP bootstrapping procedure according to any of the three example methods described herein.

[0108] In a first example method, the EAP bootstrapping procedure may be performed through an intermediate network element or entity (such as e.g., any of a WTRU and a RAN network element). The intermediate network element may serve as the EAP authenticator and may forward the EAP messages between the A_IoT device and the EAP server.

[0109] FIG. 3 is a diagram illustrating an example of EAP bootstrapping through an intermediate network element.

[0110] As shown at 31 , the A IoT device may negotiate the EAP method used for bootstrapping. The inner EAP method may be, for example, pre-provisioned and online negotiation may not be performed. For example, if the intermediate netw ork element is a WTRU, the WTRU may transmit broadcast information indicating its support for EAP bootstrapping (e.g., over PC5 broadcast channel). The A_IoT device and the WTRU may exchange (e.g., information indicating) supported EAP methods over PC5 unicast link and may select an EAP method to be used for bootstrapping. If the intermediate node is a RAN network element (e.g., gNB), the negotiation may be performed over the radio resource control (RRC) link. The RAN network element may transmit broadcast information indicating its support for EAP bootstrapping, for example, in a system information broadcast (SIB) transmission.[01U] As shown at 32, the A_IoT device may initiate EAP bootstrapping by sending (e.g., a first message indicating) an EAP bootstrapping request, for example, over any of PC5 and RRC link to the intermediate netw ork element. The A_IoT device may provide (e.g.. include) any of its device identifier and an application identifier in the bootstrapping request. The device identifier may include any of a first (e.g., physical) identifier and a second (e.g., logical) identifier of the A_IoTdevice. The application identifier may be any identifier identifying any of an application and a service. An application identifier may be shared by more than one A_IoT devices. The A_IoT device may provide (e.g., include information indicating) an EAP server address e.g., if preconfigured in the A IoT device. In another example, the intermediate network element may have been configured with an EAP server address (e.g., any of an IP address and uniform resource identifier (URI)). The intermediate network element may have been configured with a WTRU route selection policy (URSP) rule. The traffic descriptor of the URSP Rule may indicate that the URSP Rule may be associated with any of (e.g., all) EAP traffic and (e.g.. all) ambient loT traffic. In an example, the intermediate network element may use this URSP rule to determine what PDU session may be used to transmit the EAP message 34. In another example, the intermediate netw ork element may use this URSP rule to determine the characteristics of a PDU session to establish such that the PDU session may be used to transmit the EAP message 34.

[0112] As shown at 33, the intermediate network element may construct the network access identifier (NAI) using the received device identifier and the cellular network identifier that that intermediate network element may be connected to, e.g., in the form of “device- identifier@network-idT In embodiments described herein a NAI may be referred to as a device identifier associated with a network identifier. The selected network-id may be any of the home network of the intermediate netw ork element and the identity of the network that the intermediate netw ork element may be currently registered to. In another example, the selected network-id may be derived from the received A_IoT device identifier. For example, part of the A_IoT device identifier may represent (e.g., be associated with) the owner of the A IoT device. The intermediate network element may be configured with a rule that may be used to map part of the A IoT device identifier to any of a network-id and realm value. Any of the network-id and realm may be used by the netw ork to determine the identity of a AAA server that the A_IoT device may perform authentication and authorization with.

[0113] As shown at 34, the intermediate network element may locate the EAP server (e.g., by any of using the received EAP server address, and querying a domain name system (DNS) server) and may send the EAP message 34 to the EAP server via the cellular network (over any of the control plane and the user plane). The EAP message 34 may include the constructed NAI.

[0114] As shown at 35. the intermediate network element may relay the EAP message exchanges between the A IoT device and the EAP server. The details of the EAP exchanges may depend on the selected EAP method. If the EAP authentication is successful, the intermediate network element may receive an EAP server-generated pseudonym and / or a session key, and other parameters such as e.g., any of the timestamp and information indicating the valid time period of the pseudonym and session key, the encryption algorithm to used, etc. In embodiments describedherein, a timestamp may refer to a time of a successful authentication of the WTRU. A valid time period may indicate a period of time during which any of the associated information (pseudonym, session key etc.) may be valid. The intermediate network element may forward information received from the EAP server to the A_IoT device, e.g., in a second message. The format of the generated pseudonym may be closed to that of a 3GPP identifier such as any of a SUPI and a subscription concealed identifier (SUCI). The pseudonym received by the A_IoT device may comprise a list (e g., set) of multiple pseudonyms. The list may be later used by the A_IoT device with the network. When (e.g., each time) the A_IoT device contacts the network e.g., during the service request procedure as described herein, the A_IoT may use a different pseudo-identifier from the list of pseudo-identifiers.

[0115] As shown at 36, the A_IoT device may store any of the received pseudo-identifier, session key and other parameters.

[0116] In a second example method, the EAP bootstrapping procedure may be performed through the control plane of a cellular network. The A IoT device may establish a non-access stratum (NAS) link with the network. A network function (such as e.g., the access and mobility' function (AMF)) may serve as the EAP authenticator and may forward EAP messages between the device and the EAP server.

[0117] FIG. 4 is a diagram illustrating an example of EAP bootstrapping through the control plane of a cellular network.

[0118] As shown at 41, The A_IoT device may establish a NAS link with the (e.g., selected) cellular network by sending a (e.g., first message indicating a) NAS request (such as e.g.. any of a registration request and a service request) to the cellular network (e.g., AMF). The A_IoT device may include a bootstrapping request indication in the NAS request and may provide (e.g., include) its NAI (e.g., “device-identifier@network-id”). The usual primary' A&A may be skipped for this NAS request.

[0119] As shown at 42, the AMF network element may locate the EAP server (e.g., by any of (i) directly receiving the address from the A_IoT device, and (ii) deriving the address from any of the device identifier and the application identifier). The AMF network element may initiate the bootstrapping procedure and may send an EAP message 42 with (e.g., including information indicating) the NAI to the EAP server.

[0120] As shown at 43, the AMF network element may relay the EAP message exchanges betyveen the A IoT device and the EAP server. The details of the EAP exchanges may depend on the selected EAP method. If the EAP authentication is successful, the AMF network element may receive any of an EAP server-generated pseudonym, session key, and other parameters such as any of the timestamp (e.g., of a successful authentication of the WTRU) and information indicatingthe valid time period of any of the pseudonym and the session key, which may be forwarded to the A_IoT device over the NAS link, e.g., in a second message. The pseudonym received by the A_IoT device may be a list (e.g., set) of multiple pseudonyms. This list may be later used by the A_IoT device itself with the network. When (e.g., each time) the A_IoT device contacts the network e.g., during the sendee request procedure as described in herein, the A_IoT may use a different (e.g., pseudo-) identifier from the list.

[0121] As shown at 44, the A_IoT device may store any of the received pseudo-identifier, session key and other parameters.

[0122] In a third example method, the EAP bootstrapping procedure may be performed through the user plane of a cellular network. The A IoT device may establish a PDU session in the network for the bootstrapping purpose and may exchange the EAP messages with the EAP server over user plane. A network function (such as e.g., a session management function (SMF)) may serve as the EAP authenticator.

[0123] FIG. 5 is a diagram illustrating an example of EAP bootstrapping through the user plane of a cellular network.

[0124] As shown at 51, the A IoT device may request PDU session from SMF. The A IoT device may send a first message the SMF network element indicating a request for a PDU session. The first message may comprise, for example, a PDU session establishment request. The first message may indicate any of a (e.g., EAP) bootstrapping request and one or more identifiers of the A_IoT device, such as e.g., its NAI (e.g.,£idevice-identifier@network-id’').

[0125] As shown at 52, 53, and 54, SMF, UPF. and EAP Server may engage in EAP protocol exchange.

[0126] As shown at 55, the SMF network element may communicate the EAP success message (e.g., in a second message) including information indicating any of the assigned pseudonym, session key(s) and other parameters such as e.g., any of the timestamp (e.g., of a successful authentication of the WTRU) and information indicating the valid time period of any of the pseudonym and the session key to the A_IoT device.

[0127] The pseudonym received by the A_IoT device may be a list (e.g., set) of multiple pseudonyms. This list may be later used by the A_IoT device itself with the network. When (e.g., each time) the device contacts the network e.g., during the service request procedure as described herein, the A_IoT device may use a different (e.g., pseudo-) identifier from the list.

[0128] As shown at 56, the A_IoT device may store any of the assigned pseudonym, session key(s) and other parameters.

[0129] In the three bootstrapping example methods described herein, though any of an intermediate network element, an AMF network element, and an SMF network element, mayperform the role of EAP authenticator and may receive any of the assigned pseudonym and session key(s) generated from the bootstrapping procedure, they may not store the information and may not use them to authorize the network access for the A_IoT device at a later point in time (e.g.. in the future). As described herein, any of the pseudonym and session key(s) generated from the bootstrapping process may be inserted in a central network element (such as e.g., unified data management (UDM)) in the cellular network and may be retrieved by other network functions (such as e.g., AMF) for network access A&A.

[0130] After the A IoT device may have successfully completed EAP bootstrapping procedures, the A IoT device may initiate new EAP procedures to refresh any of its pseudonyms and keys based on one or more rules. For example, the A_IoT device may initiate new bootstrapping procedures when the (e.g., indicated) valid period of time of any of current active pseudonyms and keys may have expired. In another example, the A IoT device may periodically initiate bootstrapping procedures, etc.Example of Insertion of Pseudonym and Session Key in Cellular Network

[0131] The A_IoT-device-may initiate an EAP bootstrapping procedure, which may successfully complete. The EAP server may initiate a request to the cellular network to insert any of the generated pseudonym and session key in the network. The EAP may send (e.g., information indicating) the request (e.g., to a network element of the cellular network) via any of the network exposure service of the cellular network and other application programming interfaces (APIs) that the cellular network may provide. As described herein, if the pseudonym comprises a list (e.g., set) of pseudonyms, the list may be sent by the EAP server to the core network functions as show n in FIG. 6.

[0132] FIG. 6 is a diagram illustrating an example of pseudonym and session key insertion in cellular network.

[0133] As shown at 61, the A IoT device may perform a device-initiated EAP bootstrap procedure. As shown at 62, the EAP server may send information to a network exposure function (NEF) network element, indicating a data insertion request. The information may indicate any of a device identifier, a pseudonym, a session key and other parameters (such as e.g., any of a timestamp and a valid time period). As shown at 63, the NEF network element may verily (e.g., determine) that the requesting server is trusted. As show n at 64, a data insertion request message may be sent by the NEF network element to an UDM network element.

[0134] The data insertion request (e.g.. that may be sent by the EAP server) may indicate any of (i) whether the A_IoT device may have been successfully authenticated, (ii) the timestamp of the successful authentication (e.g., a time value indicating when the authentication succeeded), (iii)the generated pseudonym and / or session key, (iv) the timestamp and / or valid period of time of the pseudonym and session key, (v) the A_IoT device identifier (physical identifier and / or logical identifier) associated with the pseudonym and session key. (vi) the application or service identifier that the A_IoT device may be associated with, (vii) the address (e.g., any of and IP address and a fully qualified domain name (FQDN)) of the application server, and (viii) the valid area (e.g. geographical area) from where the A_IoT device may be allowed to access the network.

[0135] The cellular network may store the received information in a (e.g., centralized) database such as any of a UDM and a unified data repository (UDR). Other network functions (such as e.g., any of AMF, SMF) that may handle the A_IoT device’s network access in the future may query the (e.g., centralized) database for the information and may check whether the A_IoT device may be legitimate as described herein.Example of Use of Pseudonym and / or Session Key in Network Access Authorization

[0136] An example of using any of a pseudonym and a session key in any of network access authorization and other procedures is described herein.

[0137] The A IoT device may successfully complete the EAP bootstrapping procedure and may have obtained the pseudonym and / or session key (e.g., in a second message). The A_IoT device may initiate the access to the cellular network for (e.g., accessing, receiving) services by sending a request message, which may comprise (e.g., indicate) a NAS request. For example, an A_IoT device may initiate the establishment of a (e.g., NAS) connection by sending a (e.g., NAS) request such as any of a registration request and a service request (e.g., in the request message). The request message may indicate a type of A_IoT device (e.g., indicating that the A_IoT device may be of a (e.g., specific) type (such as e.g., any of ultra-low complexity and low power loT device). The type may indicate that the A IoT device may not support (e.g.. normal primary) A&A, such that any of minimal, and reduced security protection may apply. The request message may indicate that the A IoT device may have been successfully authenticated by EAP bootstrapping procedure. The request message may indicate any of an identifier (e.g., FQDN) and an address of the EAP server that may have authenticated the A_IoT device. The request message may indicate the time (e.g., timestamp) of the (e.g., previous) successful EAP authentication.

[0138] In an example, the pseudonym generated from the EAP bootstrapping procedure may be available and e.g., valid (e.g., based on valid period of time indication if available). The A_IoT device may include the pseudonym in the request message as main identifier of the A_IoT device. If a list (e.g., set) of more than one pseudonym is available (e.g., has been received from the EAP server), the A_IoT device may determine one of the pseudonyms based on one or more rules to be used for the current (e.g., NAS) request (e.g., message). In an example, the A_IoT device mayrandomly determine one pseudonym from the list (e.g., set). In another example, the A_IoT device may determine (e.g., select) one (e.g., any) pseudonym different from the pseudonym that may have been indicated in the preceding (e.g., NAS) request (e.g., message), etc.

[0139] The request message may indicate any of an application identifier and a service identifier associated with the A_IoT device. Any of the application identifier and the service identifier may be used by the network to determine (i) the destination of the application data if included in the request message, and / or (ii) the format of the application data packet. The network may use the format information to perform deep packet inspection of the data and to replace one or more fields, for example.

[0140] The request message may indicate an application data container (e.g., inserted by the A IoT device). The application data container may include any of the pseudonym as the A IoT device identifier and other application information. In an example, the format of the application data container (e.g., the location of the device pseudonym) may be known to the network. In an example, the A_IoT device may encrypt its (e.g., real) identifier using the session key (if available) and may include the encrypted identifier in the application data container.

[0141] The request message may indicate whether A_IoT device may request a response confirmation of the request. If the A_IoT device is power constrained, the A_IoT device may go to dormant state after sending the request and the data e.g., without waiting for any response from the network.

[0142] In an example, the cellular network may receive the (e.g., NAS) request (e.g., message) from the A IoT device, and may determine that the A IoT device may be a (e.g.. specific) type using reduced (e.g., minimal) security protection. The network may skip the usual primary A&A procedure based on the determination that the A_IoT device may use reduced security protection and may perform any of the following examples of actions:

[0143] In a first example of action, the cellular network function that may handle the NAS request (e.g., AMF) may query the UDM network element if the received pseudonym is valid. If the received pseudonym is available in any of UDM and UDR data base and if the received pseudonym is within the valid period of time associated with the pseudonym, the received pseudonym may be determined to be valid and the A IoT device may be granted network access. The network function may retrieve other information associated with the pseudonym from the UDM network element, including any of (i) the (e.g., real) device identifier (e.g., including physical identifier and / or logical identifier), (ii) the session key, (iii) the valid period of time of the pseudonym, (iv) the application identifier, and (v) the service identifier etc. The network function may store the information, for example, as device context until the valid period of time may have expired. The network function (e.g., AMF) may report the location information (e.g., indicating any of thecell / gNB ID from which the (e.g., NAS) request (e.g., message) may have been received, the AMF identifier, etc.) in the query' request, and the UDM may store the location information associated with the A IoT device.

[0144] In a second example of action, the cellular network (e.g., AMF) may assign a network slice dedicated for reduced-security devices for the A_IoT device. This dedicated network slice may be securely separated from other network resources such that any security compromise within the dedicated network slice may not impact the other network resources.

[0145] In a third example of action, an application data container may be included in the request, the network function (e.g., AMF) may inspect the data and may take any of the following actions. If the A IoT device identifier in the data container is encr pted, the network function may use the session key to decrypt the identifier and may replace the original encrypted identifier with the decrypted identifier. If the pseudonym is used as the A IoT device identifier in the data container, the network function may replace the pseudonym with the real identifier of the A_IoT device. After replacing the identifier, the network function may locate the destination address (e.g., based on any of the application identifier and the local network configuration) and may send the application data towards the destination (e.g., send the data as unstructured data via NEF network element).

[0146] In a fourth example of action, e.g., if the device has not indicated it may not expect any response, the network function may send a confirmation message to the requesting A_IoT device. The confirmation message may indicate that the application data may have been successfully sent to the destination. The confirmation message may include information indicating the (e.g., assigned) network slice e.g., to the A_IoT device.

[0147] FIG. 7 is a diagram illustrating an example of network access authorization and uplink data transmission using the A_IoT device pseudonym.

[0148] As shown at 70, the A IoT device may successfully complete the EAP bootstrapping procedure with an EAP server and may obtain information indicating any of a pseudonym, a session key and other parameters.

[0149] As shown at 71 , the A_IoT device may send a request message such as e.g., aNAS request message (e.g., a service request) for sending application data. The request message may indicate that the A IoT device may be of a (e.g., specific) type using reduced (e.g.. minimum) security protection. The A_IoT device may use (e.g., insert) its pseudonym as the device identifier in the (e.g., NAS) request message.

[0150] As shown at 72, the AMF netw ork element may query' the UDM for the A_IoT device identified by the pseudonym. The AMF network element may report information indicating the A_IoT device’s location to the UDM.

[0151] As shown at 73, the UDM network element may store the received information indicating the A_IoT device’s location.

[0152] As shown at 74, the UDM network element may respond with (e.g., transmit information to the AMF network element indicating) whether there is information associated with the pseudonym (e.g., in the database), and if yes, may transmit the information associated with the pseudony m of the A IoT device to the AMF. The information may include any of the A IoT device's real identifiers, session key, valid period of time, negotiated security algorithm, etc.

[0153] As shown at 75, the AMF network element may check the query result. If information associated the pseudonym is available, the AMF network element may determine that the A_IoT device may be legitimate and may store the A_IoT device information.

[0154] As shown at 76, if the (e.g., NAS) request (e.g.. message) includes an application data container, the AMF network element may inspect the data container and may replace any of the encrypted device identifier and pseudonym with unencrypted real device identifier. The AMF network element may locate the destination address for the application data.

[0155] As shown at 77 and 78. the AMF network element may send the application data to its destination address through the NEF.

[0156] In the downlink, the pseudonym may (e.g., also) be used for any of A IoT device triggering and data transmission. The cellular network may receive a device triggering request from the application server and the A_IoT device’s real identifier may be included in the device triggering request. The cellular network may query its database (e.g., any of UDM and UDR) for information associated with the A IoT device, such as any of the location of the A IoT device, the pseudonym, etc. The cellular network may replace the real device identifier with the pseudonym and may send the device triggering request through the entity (such as e.g., any of a backscattering device, a gNB and a WTRU) that may communicate with the A_IoT device.Example Method for A IoT Device Authentication / Authorization and Identification Management

[0157] FIG. 8 is a diagram illustrating an example method 800 for A IoT device authentication and identification management. The method 800 may be implemented in an A_IoT device (such as e.g., a WTRU). As shown at 810, the WTRU may send a first message to an extensible authentication protocol (EAP) serv er indicating an EAP bootstrap request. As shown at 820, the WTRU may receive a second message indicating any of one or more pseudo identifiers, a session key and a certificate. As shown at 830, the WTRU may send a request message to a first network element of a cellular netw ork indicating a pseudo identifier of the one or more pseudo identifiers as a WTRU identifier in the request message.

[0158] In various embodiments, the first message may be sent to an intermediate network element for being forwarded to the EAP server.

[0159] In various embodiments, the intermediate network element may comprise any of another WTRU and a base station of the cellular network.

[0160] In various embodiments, the first message may be sent to the first network element of the cellular network for being forw arded to the EAP server.

[0161] In various embodiments, the first message may be sent to a second network element of the cellular network for being forw arded to the EAP server.

[0162] In various embodiments, the first message may indicate any of a first identifier of the WTRU and a second identifier of the WTRU.

[0163] In various embodiments, the first identifier may comprise a phy sical identifier of the WTRU, and the second identifier may comprise a logical identifier of the WTRU.

[0164] In various embodiments, the second message may indicate any of a timestamp and a valid time period associated with any of the one or more pseudo identifiers, the session key and the certificate.

[0165] In various embodiments, the second message may indicate more than one pseudo identifiers.

[0166] In various embodiments, the WTRU may send a subsequent request message to the first network element of the cellular network, after sending the request message. The request message and the subsequent request message may indicate different pseudo identifiers of the more than one pseudo identifiers.

[0167] In various embodiments, the first network element may comprise an access and mobility function of the cellular network.

[0168] In various embodiments, the second network element may comprise a session management function of the cellular network.

[0169] In various embodiments, the request message may comprise a non-access stratum request message.

[0170] In various embodiments, the WTRU may comprise an ambient powered internet of things device.

[0171] In an embodiment, a WTRU may comprise circuitry, including any of a transmitter, a receiver, a processor, and a memory. The circuitry may be configured to cany7out the method 800 according to any of the various embodiments.

[0172] FIG. 9 is a diagram illustrating an example method 900 for A_IoT device authentication and identification management. The method 900 may be implemented in a WTRU (such as an A_IoT device). As shown at 910, the method may include sending a first message to a first networkelement of a cellular network. In various embodiments, the first message may indicate an EAP bootstrap request and a network access identifier of the WTRU. In various embodiments, the network access identifier may be to be forwarded to an EAP server. As shown at 920, the method may include receiving a second message from the first network element of the cellular network. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. As shown at 930, the method may include determining that a pseudo identifier of the one or more pseudo identifiers may be valid based on the valid time period. As shown at 940, the method may include sending a request message to a second network element of the cellular netw ork indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

[0173] In various embodiments, the first network element and the second network element may be a same network element of the cellular network.

[0174] In various embodiments, the first network element and the second network element may be different netw ork elements of the cellular netw ork.

[0175] In various embodiments, the second message may indicate a timestamp of a successful authentication of the WTRU.

[0176] In various embodiments, the second message may indicate more than one pseudo identifier.

[0177] In various embodiments, the method 900 may further include sending a subsequent request message to the first network element of the cellular network, after sending the request message. In various embodiments, the request message and the subsequent request message may indicate different pseudo identifiers of the more than one pseudo identifier.

[0178] In various embodiments, the first network element may comprise an AMF of the cellular network.

[0179] In various embodiments, the second network element may comprise an SMF of the cellular network.

[0180] In various embodiments, the request message may comprise a non-access stratum (NAS) request message.

[0181] In various embodiments, the WTRU may comprise an ambient powered internet of things device.

[0182] FIG. 10 is a diagram illustrating an example method 1000 for A IoT device authentication and identification management. The method 1000 may be implemented in a (e.g., infrastructure) netw ork element of a cellular network. As shown at 1010, the method may include receiving a first message from a WTRU. In various embodiments, the first message may indicate an EAP bootstrap request and a network access identifier of the WTRU. As shown at 1020, themethod may include sending an EAP message to an EAP server. In various embodiments, the EAP message may indicate the network access identifier of the WTRU. In various embodiments, sending the EAP message to the EAP server may include forwarding the network access identifier of the WTRU to the EAP server. As shown at 1030, the method may include sending a second message to the WTRU. In various embodiments, the second message may indicate one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers. As shown at 1040, the method may include receiving a request message from the WTRU. In various embodiments, the request message may indicate a pseudo identifier of the one or more pseudo identifiers as a WTRU identifier.

[0183] In various embodiments, the network element of the cellular network may comprise an AMF

[0184] In various embodiments, the network element of the cellular network may comprise an SMF.

[0185] In various embodiments, the second message may indicate a timestamp of a successful authentication of the WTRU.

[0186] In various embodiments, the second message may indicate more than one pseudo identifier.

[0187] In various embodiments, the method 1000 may further comprise receiving a subsequent request message from the WTRU, after receiving the request message. In various embodiments, the request message and the subsequent request message may indicate different pseudo identifiers of the more than one pseudo identifier.

[0188] In various embodiments, the request message may comprise a non-access stratum request message.

[0189] In various embodiments, the WTRU may comprise an ambient powered internet of things device.

[0190] In various embodiments, the method 1000 may further comprise sending a query request to a unified data management network element. In various embodiments, the query request may indicate any of the pseudo identifier identifying the WTRU and location information associated with the WTRU.

[0191] In various embodiments, the method 1000 may further comprise receiving a query response from the unified data management network element. In various embodiments, the query response may comprise information associated with the pseudo identifier of the WTRU.

[0192] In various embodiments, the information associated with the pseudo identifier of the WTRU may comprise any of a device identifier, a session key, a valid period of time, and a negotiated security algorithm.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

CLAIMSWhat is claimed is:

1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: sending a first message to a first network element of a cellular network, wherein the first message indicates an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU, and wherein the network access identifier is to be forwarded to an EAP server; receiving a second message from the first network element of the cellular network, wherein the second message indicates one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers; determining that a pseudo identifier of the one or more pseudo identifiers is valid based on the valid time period; and sending a request message to a second network element of the cellular network indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

2. The method of claim 1, wherein the first netw ork element and the second network element are a same network element of the cellular network.

3. The method of claim 1, wherein the first network element and the second network element are different network elements of the cellular network.

4. The method of any of claims 1 to 3, wherein the second message indicates a timestamp of a successful authentication of the WTRU.

5. The method of any of claims 1 to 4, wherein the second message indicates more than one pseudo identifier.

6. The method of claim 5, comprising sending a subsequent request message to the first network element of the cellular network, after sending the request message, wherein the request message and the subsequent request message indicate different pseudo identifiers of the more than one pseudo identifier.

7. The method of claim 1, wherein the first network element comprises an access and mobility function of the cellular network.

8. The method of claim 1, wherein the second network element comprises a session management function of the cellular network.

9. The method of any of claims 1 to 8, wherein the request message comprises anon-access stratum request message.

10. The method of any of claims 1 to 9, wherein the WTRU comprises an ambient powered internet of things device.

11. A wireless transmit / receive unit (WTRU) comprising circuitry, including any of a transmitter, a receiver, a processor, and a memory, wherein the WTRU is configured to: send a first message to a first network element of a cellular network, wherein the first message indicates an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU, and wherein the network access identifier is to be forwarded to an EAP server; receive a second message from the first network element of the cellular network, wherein the second message indicates one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers; determine that a pseudo identifier of the one or more pseudo identifiers is valid based on the valid time period; and send a request message to a second network element of the cellular netw ork indicating the pseudo identifier as a WTRU identifier in the request message based on the pseudo identifier being valid.

12. The WTRU of claim 11, wherein the first network element and the second network element are a same netw ork element of the cellular network.

13. The WTRU of claim 11, wherein the first network element and the second network element are different network elements of the cellular network.

14. The WTRU of any of claims 11 to 13, wherein the second message indicates a timestamp of a successful authentication of the WTRU.

15. The WTRU of any of claims 11 to 14, wherein the second message indicates more than one pseudo identifier.

16. The WTRU of claim 15, further configured to send a subsequent request message to the first network element of the cellular network, after sending the request message, wherein the request message and the subsequent request message indicate different pseudo identifiers of the more than one pseudo identifier.

17. The WTRU of claim 11, wherein the first network element comprises an access and mobility function of the cellular network.

18. The WTRU of claim 11, w herein the second netw ork element comprises a session management function of the cellular network.

19. The WTRU of any of claims 11 to 18, wherein the WTRU comprises an ambient powered internet of things device.

20. A method implemented in a netw ork element of a cellular network, the method comprising: receiving a first message from a wireless transmit / receive unit (WTRU), wherein the first message indicates an extensible authentication protocol (EAP) bootstrap request and a network access identifier of the WTRU; sending an EAP message to an EAP server, wherein the EAP message indicates the network access identifier of the WTRU; sending a second message to the WTRU, wherein the second message indicates one or more pseudo identifiers and a valid time period associated with the one or more pseudo identifiers; and receiving a request message from the WTRU. wherein the request message indicates a pseudo identifier of the one or more pseudo identifiers as a WTRU identifier.

Images