Discovery and use of intermediate nodes for environmental devices

Abstract

An intermediate node WTRU may receive an intermediate node policy from a network. The intermediate node may identify one or more destinations to which the WTRU may forward data and / or information about conditions in which the WTRU may be triggered to operate as an intermediate node. The WTRU may determine to operate as an intermediate node. The WTRU may send a broadcast message to indicate that it is operating as an intermediate node. A low power device may receive a broadcast message from a WTRU and may send a message to the WTRU. The WTRU may receive a message from a low power device. The message may include data. The WTRU may send the data to the network using an address associated with the destination. Lightweight authentication procedures (e.g., transmission keys and group keys, random numbers) may be used between the low-power device and the intermediate node.

Description

Cross-references to related applications concerning the discovery and use of intermediate nodes for environmental devices.

[0001] This application claims priority to U.S. Provisional Patent Application 63 / 588,101, filed October 5, 2023, the contents of which are incorporated herein by reference as if fully set forth. Background Technology

[0002] Intermediate nodes can be entities capable of forwarding data to a specific destination endpoint. A Wireless Transmit / Receive Unit (WTRU) is an example of an intermediate node. Ambient Internet of Things (IoT) devices are examples of low-power devices. The destination endpoint can be a node that should receive data from the device, such as a Network Function (NF) or Application Function (AF). Information transmission between low-power devices and the network can take into account the limited available and usable power within the low-power device.

[0003] Due to limited power availability, devices may be unable to communicate directly with the network. This could include low-power devices, such as environmental IoT devices and / or devices operating at low power levels due to abnormal conditions. Low-power devices can discover intermediate nodes capable of sending uplink data to the network and forwarding that uplink data to a specific destination. This can trigger the device to use the intermediate node to send data to the destination endpoint. A lightweight authentication process can be used between the low-power device and the intermediate node. Summary of the Invention

[0004] Methods and systems for discovering and using intermediate nodes for environmental devices are disclosed. WTRUs can discover and / or use intermediate nodes to forward data to desired destinations.

[0005] The intermediate node WTRU can receive intermediate node policy information from the network. This policy information can identify one or more destinations to which the WTRU can forward data and / or information about one or more conditions that can trigger the WTRU to act as an intermediate node. The policy may include one or more addresses associated with each of the one or more destinations. For example, the address may be an Internet Protocol (IP) address or a combination of Data Network Name (DNN) / Single Network Slice Selection Auxiliary Information (S-NSSAI). This policy can be received in Non-Access Stratum (NAS) messages. Information about the conditions that can trigger the WTRU to act as an intermediate node may be related to the time of day and / or location. The policy may indicate which types of low-power devices are allowed to send data via the WTRU.

[0006] WTRU can determine whether to operate as an intermediate node. This can be based on detecting conditions indicated in a policy (e.g., location information or time of day). Determining to act as an intermediate node can also be based on receiving a trigger message. Alternatively, it can be based on both receiving a trigger message and / or detecting conditions indicated in a policy.

[0007] A WTRU can send broadcast messages to indicate that it is operating as an intermediate node. The broadcast message can indicate the destination identifier (ID) of one or more destinations to which the WTRU can forward data. The broadcast message may also include the destination-ID-Code of one or more destinations. A WTRU can receive messages from low-power devices. These messages may include data. The received messages may also include the destination ID or destination-ID-Code. The WTRU can use the address associated with the destination to send data to the network. The low-power device's identification can be sent along with the data.

[0008] Low-power devices can be configured with identifiers of destinations to which they can send data. A low-power device can receive broadcast messages from a WTRU indicating that the WTRU is operating as an intermediate node. The broadcast message can indicate a destination ID. The broadcast message can also include a destination ID code. A low-power device can send a message to the intermediate node. This message can include data. The low-power device can determine which data to send based on the destination ID received from the WTRU. The sent message can also include the destination ID and / or a destination ID code. As explained more fully below, the WTRU can send data to a destination associated with a destination ID or a destination ID code.

[0009] WTRUs can use secure communication between intermediate nodes and low-power devices. The intermediate node WTRU can receive intermediate node policy information from the network. This policy information may include one or more of the following: destination ID, device ID of the WTRU and / or the authorized low-power device, transmission key (TK), and / or destination address. The intermediate node WTRU can send broadcast messages to indicate that it is operating as an intermediate node. Broadcast messages may include a hidden version of the destination ID and / or a random number. The random number can be generated by the WTRU. The hidden version of the destination ID can be calculated using the random number, TK, and destination ID. The intermediate node WTRU can receive messages from low-power devices. These messages may include data, a hidden version of the low-power device ID, and / or a third random value. The WTRU can use the TK, the hidden version of the low-power device ID, and / or the third random value to calculate or determine the low-power device ID. The intermediate node WTRU can send data to the network using the address associated with the destination. The low-power device's identifier can be sent along with the data. The intermediate node WTRU can send reports to the network to provide information about the data transmission. The report may include the low-power device ID and the destination ID.

[0010] A low-power device can be configured with an identifier of the destination to which it can send data, a low-power device ID, and a time limit (TK). The low-power device can receive broadcast messages from the WTRU indicating that the WTRU is operating as an intermediate node. This message may include a hidden version of the destination ID and / or a random number. The low-power device can determine the destination ID using the TK, the random number, and / or the hidden version of the destination ID. The low-power device can detect that the determined destination ID is associated with a destination to which it can send data. The low-power device can send a message to the WTRU. This message may include data, a hidden version of the low-power device ID, and / or a third random value. The third random value can be generated by the low-power device. The hidden version of the low-power device ID can be determined based on the third random number, the TK, and the low-power device ID. Attached Figure Description

[0011] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more of the disclosed embodiments may be implemented.

[0012] Figure 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that can be used within the communication system shown in Figure 1A according to an embodiment.

[0013] Figure 1C is a system diagram illustrating an exemplary radio access network (RAN) and an exemplary core network (CN) that can be used within the communication system shown in Figure 1A according to an embodiment.

[0014] Figure 1D is a system diagram illustrating yet another exemplary RAN and yet another exemplary CN that can be used within the communication system shown in Figure 1A according to an embodiment.

[0015] Figure 2 is a diagram depicting an exemplary transmission of uplink data via intermediate nodes. Detailed Implementation

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

[0017] As shown in Figure 1A, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as WTRUs.

[0018] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b can be base transceiver stations (BTS), Node-B, eNode B, home Node B, main eNode B, gNB, NR Node B, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

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

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

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

[0022] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish air interface 116.

[0023] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional terrestrial line communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108, or can communicate with it. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0048] Although the WTRU is depicted as a wireless terminal in Figures 1A through 1D, it is conceivable that in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0049] In a representative embodiment, the other network 112 may be a WLAN.

[0050] A WLAN in Infrastructure Basic Services 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 access or interface with a Distribution System (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between a source STA and a destination STA using a Direct Link Setup (DLS) (e.g., directly between them). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this article.

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

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

[0053] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. In the 80+80 configuration, data, after channel coding, can be passed through a fragment resolver that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped onto the two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

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

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

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

[0057] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

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

[0059] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with a scalable set of parameters. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can be varied for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various lengths or scalable lengths (e.g., including different numbers of OFDM symbols and / or absolute times of varying durations).

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

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

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

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

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

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

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

[0067] Based on the corresponding descriptions in Figures 1A-1D, one or more emulation devices (not shown) can perform one or more or all of the functions described herein with respect to one or more of the following: WTRU 102a-102d, base stations 114a-114b, eNode-B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182ab, UPF 184a-184b, SMF 183a-183b, DN 185a-185b, and / or any other devices described herein. An emulation device can be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

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

[0069] One or more simulation devices may perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, a simulation device may be used to test scenarios in a laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to perform testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via an RF circuit system (e.g., which may include one or more antennas).

[0070] WTRU can discover and use intermediate nodes to forward data to the desired destination.

[0071] Figure 2 is a diagram depicting the transmission of uplink data via intermediate nodes. The intermediate node WTRU can receive intermediate node policy information from the network. This policy information can identify one or more destinations to which the WTRU can forward data and / or information about conditions that can trigger the WTRU to act as an intermediate node. The policy information may include one or more addresses associated with each of the one or more destinations. For example, the address may be an Internet Protocol (IP) address or a combination of Data Network Name (DNN) / Single Network Slice Selection Auxiliary Information (S-NSSAI).

[0072] Policy information can be received in Non-Access Stratum (NAS) messages. Information about the conditions that can trigger WTRU operation as an intermediate node may be related to the time of day and / or location. Policy information can indicate which types of low-power devices are allowed to transmit data via the WTRU.

[0073] WTRU can determine whether to act as an intermediate node. Determining to act as an intermediate node can be based on detecting conditions indicated in a policy (e.g., location information and / or time of day). Determining to act as an intermediate node can also be based on receiving a trigger message. Alternatively, it can be based on both receiving a trigger message and / or detecting conditions indicated in a policy.

[0074] A WTRU can send broadcast messages to indicate that it is operating as an intermediate node. A broadcast message can indicate the destination identifier (ID) of one or more destinations to which the WTRU can forward data. The broadcast message may also include the destination ID codes of one or more destinations.

[0075] A WTRU can receive messages from a low-power device. The low-power device can be a WTRU (e.g., a low-power WTRU). The message can include data. The received message may also include a destination ID or a destination ID code.

[0076] WTRU can use an address associated with the destination to send data to the network. An indication of the low-power device sending the data can be sent along with the data.

[0077] Low-power devices can be configured with identifiers of destinations to which they can send data. Low-power devices can receive broadcast messages from the WTRU indicating that the WTRU is operating as an intermediate node. The broadcast message can indicate the destination ID. The broadcast message can also include the destination ID code.

[0078] Low-power devices can send messages to intermediate nodes. These messages may include data. The low-power device may determine which data to send based on the destination ID received from the WTRU. The sent message may also include the destination ID and / or a destination ID code.

[0079] WTRU can enable secure communication between intermediate nodes and low-power devices.

[0080] Intermediate WTRUs can be configured for authentication and security. An intermediate WTRU can receive intermediate node policy information from the network. This policy information may include one or more of the following: destination ID, WTRU device ID, transport key (TK), destination address, and / or an indication of which low-power devices the WTRU can communicate with and which data destinations data from low-power devices can be sent to.

[0081] Intermediate node WTRU can send broadcast messages to indicate that it is operating as an intermediate node. Broadcast messages may include a hidden version of the destination ID and / or a random number. The random number can be generated by the WTRU. The random number, TK, and destination ID can be used to calculate the hidden version of the destination ID.

[0082] The intermediate node WTRU can receive messages from the low-power device. These messages may include one or more of the following: data, a hidden version of the low-power device ID, and / or a third random value. The WTRU can use the TK, the hidden version of the low-power device ID, and / or the third random value to calculate and / or determine the low-power device ID.

[0083] Intermediate WTRUs can use an address associated with the destination to send data to the network. An indication of the identifier of a low-power device sending data to an intermediate WTRU can be sent along with the data.

[0084] The intermediate node WTRU can send reports to the network, such as providing information about data transmission. This report may include the low-power device ID and the destination ID.

[0085] Low-power devices can be configured with an identifier of the destination to which the low-power device can send data, a low-power device ID, and / or a TK.

[0086] Low-power devices can receive broadcast messages from the WTRU indicating that the WTRU is operating as an intermediate node. This message may include a hidden version of the destination ID and / or a random number.

[0087] Low-power devices can use a TK, a random number, and / or a hidden version of the destination ID to determine the destination ID. The low-power device can detect that the determined destination ID is associated with a destination to which the low-power device can send data.

[0088] Low-power devices can send messages to WTRUs. These messages may include data, a hidden version of the low-power device ID, and / or a third random value. The third random value can be generated by the low-power device. The hidden version of the low-power device ID can be determined based on the third random number, TK, and the low-power device ID.

[0089] The term "intermediate node" can refer to an entity that can forward data to a specific destination endpoint. WTRU can be an example of an intermediate node.

[0090] The term "device" can refer to a low-power device. "Device" and "low-power device" are used interchangeably. An environmental Internet of Things (IoT) device can be an example of a low-power device.

[0091] A destination endpoint can refer to a node that can receive data from a device, such as a network function (NF) or application function (AF). An application function can refer to a function performed by a server. An application function can also be called an application server.

[0092] It can transmit information between low-power devices and networks.

[0093] Environmental IoT devices can be referred to as Type A devices. Type A devices may not have energy storage and may not generate independent signals (for example, they can transmit signals by using backscatter transmission).

[0094] Environmental IoT devices can be referred to as Type B devices. Type B devices may have energy storage, but may not have the ability to perform independent signal generation (e.g., it can transmit by using backscatter transmission) (e.g., using stored energy can include amplification of reflected signals).

[0095] Environmental IoT devices can be referred to as Type C devices. Type C devices may have energy storage and the ability to perform independent signal generation (e.g., the device may have active RF components for transmission).

[0096] Low-power devices (e.g., environmental IoT devices or low-power smartphones) may have a limited ability to send data to the network due to limited available power. Sending data to the network may require power that the WTRU does not have or cannot obtain. The device may have sufficient power to send data to nearby devices that require less power for transmission and communication. The system can be designed so that some low-power devices can (e.g., can only) send data to the network via intermediate nodes such as WTRUs. Low-power devices can use intermediate nodes to communicate with the network. Low-power devices can discover intermediate nodes that can forward data to the destination endpoint where the data should be received.

[0097] The system can support low-power devices in discovering intermediate nodes capable of sending data to a specific destination. One or more lightweight authentication processes can be provided, enabling low-power devices to authenticate intermediate nodes and vice versa. In this paper, "lightweight" means that the computational overhead is low when executed by the low-power device.

[0098] Due to limited power availability, devices may be unable to communicate directly with the network. This could include low-power devices, such as environmental IoT devices and / or devices operating at low power levels due to abnormal conditions. Low-power devices may discover intermediate nodes capable of sending uplink data to the network and forwarding that uplink data to a specific destination, for example, when a low-power device needs to send data to a specific destination server.

[0099] A WTRU can be triggered to act as an intermediate node. For example, a WTRU can act as an intermediate node due to a direct request from the network (e.g., a trigger message) or by using information from a policy to detect conditions. A device can be triggered to use an intermediate node to send data to the destination endpoint. A lightweight authentication process can be used between low-power devices and intermediate nodes.

[0100] Figure 2 illustrates an exemplary process for triggering a device to send data to a specific destination using an intermediate node WTRU. This exemplary process lists exemplary conditions that may trigger a low-power device to send data via an intermediate node WTRU.

[0101] In this exemplary process, the intermediate node WTRU can receive policy information. The policy information may include information related to which low-power devices the WTRU can communicate with and to which data destinations data from low-power devices can be sent. The WTRU can receive policy information from the Policy Control Function (PCF) in a WTRU Configuration Update message. The PCF can derive policies based on the WTRU's subscription information or service parameters and / or based on information received from the Application Function (AF). For example, the WTRU's subscription information may indicate which destination IDs the WTRU can serve, and / or service parameters from the AF may indicate which destination IDs the WTRU can serve.

[0102] When a WTRU is triggered by a condition (e.g., one of the conditions disclosed herein), the WTRU can broadcast a message to notify one or more of the surrounding low-power devices of its ability to act as an intermediate node.

[0103] Figure 2 is a diagram depicting an exemplary transmission of uplink data via an intermediate node at point 200. At point 201, the low-power device may be pre-configured with a destination ID of the destination endpoint to which the low-power device should send data. The destination ID can be sent to the low-power device in a NAS message (such as a register NAS message). Alternatively or alternatively, this information can be sent using other types of NAS messages (e.g., downlink (DL) NAS delivery messages). The low-power device may be configured with information about conditions that trigger the device to use the intermediate node to send data to the network. In the example, these conditions may include: detecting that a measurement of power stored in the low-power device exceeds a threshold; receiving a message from the network or intermediate node indicating that the low-power device can send data; detecting that a specific time of day has been reached; and / or detecting that the low-power device is located in a specific location.

[0104] At position 202, the WTRU can receive policy messages from NFs (such as PCFs) in the core network (CN). This message may include intermediate node policy information. The policy information may include a list of destination IDs to which the WTRU can send data. The policy information may include information about the conditions that should trigger the WTRU to act as an intermediate node. For example, the policy information may indicate that the WTRU should act as an intermediate node when it is in a specific location or at a specific time of day. For example, the policy information may indicate that the WTRU should act as an intermediate node (e.g., only as an intermediate node) when it receives a trigger message from a low-power device or network.

[0105] Policy information may include information indicating which types of low-power devices are allowed to send data via the WTRU. The WTRU can use this information when determining whether to accept data from low-power devices.

[0106] The policy information received by the WTRU can be tailored to each destination ID. For example, the WTRU can receive a first policy with a first set of information applied to a first destination ID, and the WTRU can receive a second policy with a second set of information applied to a second destination ID.

[0107] At points 203 to 205, the WTRU can be triggered to act as an intermediate node. This can be triggered based on a message received from the network at point 203. This instruction can be received in a NAS message. The network function may have already requested the Access and Mobility Function (AMF) to send this instruction to the WTRU in a NAS message. Alternatively, the network function may have already requested the AMF to send this instruction to the WTRU in a NAS message based on detected WTRU location or a request received from the AF.

[0108] The WTRU can be triggered to act as an intermediate node 204 based on the conditions that trigger it to act as an intermediate node, which are detected using information from the policy. For example, the WTRU can detect that it is located at the position provided in the policy information.

[0109] The WTRU can be triggered to act as an intermediate node based on a request received from the low-power device 205. For example, the WTRU can be triggered to act as an intermediate node based on a discovery request received from the low-power device indicating that the low-power device wants to discover an intermediate node. For example, the WTRU can be triggered to act as an intermediate node based on an indication received from the low-power device that the low-power device has data to send to its destination.

[0110] The WTRU can be triggered to act as an intermediate node based on a combination of conditions. For example, if the received policy information indicates that the WTRU is permitted to act as an intermediate node at its current location, the WTRU can allow (e.g., only allow) messages from low-power devices to trigger the WTRU to act as an intermediate node.

[0111] At 206, the WTRU can send a broadcast message to announce its potential role as an intermediate node for a specific destination endpoint. The WTRU may determine to send the broadcast message based on the fact that it has been triggered to act as an intermediate node. The broadcast message may include a destination ID and / or a destination ID code. The destination ID can be N bits long. The destination ID code can be M bits long. M can be less than N. The destination ID code can be a part of the destination ID or a value independent of the destination ID. At 207, a low-power device can receive and decrypt the broadcast message from the WTRU.

[0112] If an intermediate node can send data to the destination endpoint, then at 208, the low-power device can send a message to the intermediate node. This message may include the data to be sent to the destination and / or an identifier of the destination. Alternatively, the message may include, for example, a destination ID code instead of the destination identifier. The destination ID code may be smaller and therefore requires less power to transmit than the destination ID.

[0113] At position 209, the WTRU can forward data to the destination. The message sent by the WTRU to the destination may include the low-power device identifier, the WTRU identifier, the destination ID, and / or payload data.

[0114] At 210, the WTRU can receive an acknowledgment message from the destination endpoint. The acknowledgment message can indicate one or more of the following: data has been successfully received; data is corrupted or erroneous and the device needs to perform a retransmission; and / or the device identifier is not recognized by the endpoint station. At 211, the WTRU can forward the acknowledgment message to the low-power device.

[0115] The processing power of low-power devices may be limited. Therefore, it may be desirable to design processes that enable secure information exchange between low-power devices and WTRUs without requiring the low-power devices to perform computationally expensive or power-intensive operations.

[0116] It can enhance the transmission of uplink data via intermediate nodes, making information exchange between low-power devices and WTRUs secure.

[0117] Low-power devices can be configured with a low-power device ID, a transport key (TK), and / or one or more identifiers (e.g., destination IDs) of the destinations to which the device can forward data. Low-power devices can be configured with a unique low-power device ID and a unique TK for each destination to which the low-power device is permitted to send data. Low-power devices can be configured with one or more device group IDs and / or one or more associated device group keys (GKs) (e.g., shared by a group or class of devices). A group of low-power devices can use the group ID and GK to receive security information from an intermediate WTRU (e.g., during broadcasts).

[0118] Low-power devices can receive broadcast messages from the WTRU. The low-power device can detect the broadcast message as an indication that the WTRU can forward information to the destination to which the low-power device needs to send data. For example, the broadcast message may include a destination ID. Alternatively or additionally, the broadcast message may include a hidden version of the destination ID and / or a random number. The hidden version of the destination ID can be a value that can be used to derive the associated destination ID. Derivation may require performing calculations or mathematical operations. The random number, the hidden version of the destination ID, and / or the TK can be inputs to the calculations or mathematical operations. For example, the broadcast message may include a device group ID. A GK can be used to hide the device group ID.

[0119] Low-power devices can unhide a hidden version of a received destination ID (e.g., and / or a device group ID). The unhiding operation may involve performing computations or mathematical operations. A random number, the hidden version of the destination ID, and / or the TK can be inputs to the computation or mathematical operation. The result of the unhiding operation may include the destination ID. The low-power device can check if the destination ID is the destination to which it wants to send data. Since the low-power device has successfully unhidden the destination ID, it can assume that the WTRU is authenticated and authorized to send data to the destination. Broadcast messages may include an indication of the availability of a group of low-power devices. Low-power devices may use a GK (e.g., instead of a single TK) to unhide the hidden identifier.

[0120] After a low-power device determines that it wants to send data to the destination identified in a broadcast message, the low-power device can transmit a message to the WTRU. This message may include the data to be sent to the destination, a second hidden destination ID, and / or a second random value. The low-power device may randomly generate the second random value. The low-power device may calculate the second hidden destination ID. The inputs to the calculation may include the destination ID and the first and second random values. Alternatively or additionally, the low-power device may encrypt the data to be sent to the destination using a TK or GK and one or more random values. This message may include a hidden low-power device ID and / or a second random value. The hidden low-power device ID may be a hidden version of the low-power device's identifier. The hidden low-power device ID may be the result of a calculation performed by the low-power device. The TK, the random value, and / or the low-power device's identifier may be the inputs to the calculation. In scenarios where a broadcast message addresses a group of devices, the low-power device may use a GK to hide identifiers (e.g., device ID and / or destination ID).

[0121] The WTRU can receive one or more intermediate node policies from the network. For example, policies can be received from the PCF. Each policy can be associated with a data destination. Each policy may include information including one or more of the following: destination ID, WTRU device ID, TK, and / or destination address. Additionally or alternatively, each policy may include a group ID and an associated group key. Security materials (e.g., TK, GK, and other key materials) can be configured by a key management function (e.g., Public Key Management Function (PKMF)).

[0122] The WTRU's device ID can be an identifier that the WTRU can use when it is performing operations related to communicating with low-power devices and sending data to destinations covered by a policy. The group ID can be an identifier that the WTRU can use when it is performing operations related to communicating with a group of low-power devices (e.g., securely broadcasting availability to a group of devices).

[0123] The destination address can be an address associated with a destination ID. The destination address can include a combination of IP address and port number to which the WTRU should forward data when data is received from a low-power device. For example, the destination address can include the address of the server to which the data is sent. Alternatively or concurrently, the destination address can include a combination of DNN and S-NSSAI, which the WTRU can use to determine or select a non-IP packet data unit (PDU) session on which to send destination-related data.

[0124] The policy may include identifiers of low-power devices permitted to send data to the destination. Each low-power device can be associated with its own TK, and each device's TK can be included in the policy. Including device-specific TKs has the advantage of reducing the risk of TK leakage and spoofing among low-power devices. Alternatively, the WTRU may be configured with information that can be used to derive low-power device-specific TKs. The advantage of enabling the WTRU to derive low-power device-specific TKs is that the WTRU may not need to be configured with identifiers of every low-power device that can be connected to the WTRU, while minimizing the risk of TK leakage. For example, the TK can be derived in part based on the WTRU's identifier (e.g., device ID). The TK can be derived using a master key (MK) configured to the WTRU by the PKMF. The MK can be associated with a group of low-power devices (e.g., group ID).

[0125] WTRUs can send broadcast messages. Broadcast messages may include a destination ID. Alternatively or concurrently, broadcast messages may include a hidden version of the destination ID and a first random number. The random number may be randomly generated by the WTRU. The hidden version of the destination ID may be based on a calculation performed by the WTRU. The TK, destination ID, and / or random number may be inputs to the calculation. The output of the calculation may include a hidden version of the destination ID. Broadcast messages may include an indication of WTRU availability for a group of low-power devices. In this scenario, an intermediate WTRU may use a GK (e.g., instead of a TK) to hide identifiers (e.g., destination or group ID).

[0126] The WTRU can receive data, a hidden version of the low-power device ID, a hidden version of the destination ID, and a second random value. The WTRU can use the TK, the hidden version of the low-power device ID, and the random value to calculate or determine the low-power device ID. The WTRU can also use the TK or GK, the hidden version of the destination ID, and / or the random value to calculate or determine the destination ID. The WTRU can use the TK to create a decrypted version of the data.

[0127] Based on the successful de-hiding of the low-power device ID and destination ID by WTRU, WTRU can determine that the low-power device is authenticated and authorized to send data to a given destination.

[0128] WTRU can use the previously exported destination ID and previously received policy information to determine the address and PDU session used to send the decrypted version of the data to the destination server.

[0129] The WTRU can periodically report to the network (e.g., Session Management Function (SMF)) information about which traffic it forwards to the destination. For example, a policy received by the WTRU can instruct it to send periodic reports to the network. This policy might instruct that reports be sent after a certain time period and / or after forwarding a specific number of packets. Reports can be sent for one or more devices that have already transmitted data. Reports from the WTRU can be sent in UL NASTRANSPORT and / or another type of NAS message. The report may include indicative information about each packet forwarded to the destination (e.g., low-power device ID, transmission time, and destination ID). The information included in the report can be used by the mobile network operator for billing purposes.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: A processor and a memory, wherein the processor and the memory are configured to: receive policy information associated with operation as an intermediate node, wherein the policy information includes one or more destinations and one or more conditions that trigger the WTRU to operate as an intermediate node, the WTRU being capable of forwarding data to the one or more destinations; determine to operate as an intermediate node for one or more low-power devices; send a broadcast message indicating that the WTRU is operating as an intermediate node, the broadcast message indicating the one or more destinations; receive a message from a low-power device, wherein the message includes data, and wherein the message includes a destination identifier (ID) or destination ID code associated with a destination among the one or more destinations indicated in the broadcast message; and send the data to the destination associated with the destination ID or destination ID code in the received message.

2. The WTRU according to claim 1, wherein, The processor and the memory are configured to determine operation as intermediate nodes based on trigger messages received from the low-power device or from the network.

3. The WTRU according to claim 1 or 2, wherein, The processor and the memory are configured to determine whether to operate as an intermediate node based on detecting one or more conditions indicated in the policy information.

4. The WTRU according to claim 3, wherein, The one or more conditions indicated in the strategy information are associated with a geographic location or a time of day.

5. The WTRU according to any one of claims 1 to 4, wherein, The broadcast message indicates the destination ID or the destination ID code for each of the one or more destinations.

6. The WTRU according to any one of claims 1 to 5, wherein, The policy information includes indications of one or more types of low-power devices capable of sending data to the WTRU.

7. The WTRU according to any one of claims 1 to 6, wherein, The policy information includes a transmission key (TK), wherein the processor and the memory are configured to determine a random value associated with the TK, wherein the broadcast message includes the random value, and wherein the one or more destinations indicated in the broadcast message are hidden, the hiding being based at least on the random value and the TK.

8. The WTRU according to any one of claims 1 to 7, wherein, The message received from the low-power device includes a second random value and a hidden identifier of the low-power device, wherein the processor and the memory are further configured to identify the low-power device based at least on the second random value and the hidden identifier of the low-power device; wherein the data is sent to the destination based on the identification of the low-power device; and wherein an indication of the identifier of the low-power device is sent to the destination along with the data.

9. The WTRU according to claim 8, wherein, The policy information also includes instructions for one or more low-power devices authorized to send data to the one or more destinations.

10. The WTRU according to claim 9, wherein, An authorized low-power device among the one or more low-power devices authorized to send data to the one or more destinations is authorized to send data to a subset of the one or more destinations.

11. A method to be performed by a wireless transmit / receive unit (WTRU), the method comprising: The system receives policy information associated with operation as an intermediate node, wherein the policy information includes one or more destinations and one or more conditions that trigger the WTRU to operate as an intermediate node, the WTRU being able to forward data to the one or more destinations; determines to operate as an intermediate node for one or more low-power devices; sends a broadcast message indicating that the WTRU is operating as an intermediate node, the broadcast message indicating the one or more destinations; receives a message from a low-power device, wherein the message includes data, and wherein the message includes a destination identifier (ID) or destination ID code associated with a destination among the one or more destinations indicated in the broadcast message; and sends the data to the destination associated with the destination ID or destination ID code in the received message.

12. The method according to claim 11, wherein, The operation as an intermediate node is determined based on the trigger message received from the low-power device or from the network.

13. The method according to claim 11 or 12, wherein, Based on the detection of one or more conditions indicated in the policy information, an operation is determined as an intermediate node.

14. The method according to claim 13, wherein, The one or more conditions indicated in the strategy information are associated with a geographic location or a time of day.

15. The method according to any one of claims 11 to 14, wherein, The broadcast message indicates the destination ID or destination ID code for each of the one or more destinations.

16. The method according to any one of claims 11 to 15, wherein, The policy information includes indications of one or more types of low-power devices capable of sending data to the WTRU.

17. The method according to any one of claims 11 to 16, wherein, The policy information includes a transmission key (TK), wherein the method further includes determining a random value associated with the TK, wherein the broadcast message includes the random value, and wherein the one or more destinations indicated in the broadcast message are hidden, the hiding being based at least on the random value and the TK.

18. The method according to claim 11, wherein, The message received from the low-power device includes a random value and a hidden identifier of the low-power device, wherein the method further includes identifying the low-power device based at least on the random value and the hidden identifier of the low-power device; wherein the data is sent to the destination based on the identification of the low-power device; and wherein an indication of the identifier of the low-power device is sent to the destination along with the data.

19. The method according to claim 18, wherein, The policy information also includes instructions for one or more low-power devices authorized to send data to the one or more destinations.

20. The method according to claim 19, wherein, An authorized low-power device among the one or more low-power devices authorized to send data to the one or more destinations is authorized to send data to a subset of the one or more destinations.

Images