Method and apparatus for personal internet of things network (PIN) management

Abstract

To provide methods and apparatuses for Personal Internet of Things Network (PIN) management.SOLUTION: A first wireless transmit / receive unit (WTRU) may transmit, to a network node in a cellular network, a first non-access stratum (NAS) request indicating capability of the first WTRU as a PIN Element (PE) with Management Capability (PEMC) in a PIN. The WTRU may receive, from the network node, a first NAS response including authorization information, an authorized PIN type and validity duration of the PIN. The WTRU may receive, from a second WTRU, a connection request including PE information associated with the second WTRU. The PE information may include a PE type and a PE capability. The WTRU may transmit, to the second WTRU, based on the PE type and the PE capability being compatible with the authorized PIN type, a connection response indicating the second WTRU is authorized as a PE of the PIN.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 324,517, filed March 28, 2022, the contents of each of which are incorporated herein by reference. [Background technology]

[0002] When multiple Internet of Things (IoT) devices are deployed in a private environment, devices with IoT capabilities can be organized into a Personal IoT Network (PIN). A PIN can include PIN elements (PEs) such as security sensors, smart lights, smart plugs, printers, and mobile phones. Different PEs can have different capabilities. For example, a PE with gateway capability (PEGC) can provide connectivity between PEs and between PEs and cellular networks. A PE with management capability (PEMC) can configure and / or manage PINs. However, methods and apparatuses for creating, updating, authorizing / unauthorizing, activating / deactivating, and managing PINs are not defined. Summary of the Invention

[0003] Described herein are methods and apparatus for Personal Internet of Things Network (PIN) management. A first wireless transmit / receive unit (WTRU) may send a first Non-Access Stratum (NAS) Request message to a network node in a cellular network indicating the first WTRU's capability to act as a PIN Element (PE) (PE with Management Capability (PEMC)) for a PIN. The WTRU may receive a first NAS Response message from the network node in the cellular network including authorization information of the first WTRU to act as a PEMC for initiating the PIN, an authorized PIN type, and a PIN validity period. The WTRU may receive a Connection Request message from a second WTRU including PE information associated with the second WTRU. The PE information may include the second WTRU's PE type and the second WTRU's PE capabilities. The WTRU may send a Connection Response message to the second WTRU indicating that the second WTRU is authorized to act as a PE for the PIN based on the PE type and PE capabilities being compatible with the authorized PIN type. [Brief explanation of the drawings]

[0004] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements and in which: [Figure 1A] 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1C]1A is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 2] FIG. 1 illustrates an exemplary home automation Personal Internet of Things network (PIN). [Figure 3] FIG. 10 is a diagram illustrating an example of a wearable PIN. [Figure 4] FIG. 1 illustrates an exemplary network architecture for a PIN. [Figure 5] FIG. 1 illustrates an exemplary reference model for a 5G / NextGen network. [Figure 6] FIG. 10 is a diagram illustrating an example of PIN management. [Figure 7A] FIG. 10 illustrates an example WTRU-initiated PIN creation. [Figure 7B] This is a continuation of Figure 7A. [Figure 8] FIG. 10 illustrates an example of a PIN management procedure. [Figure 9] FIG. 10 illustrates an example WTRU-initiated PIN update. [Figure 10] FIG. 1 illustrates an exemplary WTUR-initiated PIN recreation. [Figure 11] FIG. 10 illustrates an example of PIN activation / deactivation by a validity timer. [Figure 12] FIG. 1 illustrates an exemplary network-initiated PIN creation. [Figure 13] FIG. 1 illustrates an exemplary network-initiated PIN update. DETAILED DESCRIPTION OF THE INVENTION

[0005] 1A is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. Communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may use 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 discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), etc.

[0006] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of 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 (STA), may be configured to transmit and / or receive wireless signals and may be implemented as a user equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smartphone, laptop, netbook, personal computer, wireless sensor, hotspot or Mi-Fi device, Internet of Things (IoT) device, Personal Internet of Things Network (PIN) Element (PE) with Management Capability (PEMC), PE with Gateway Capability (PEC), PIN Element (PE), wristwatch or other wearable, head-mounted display (HMD), or other wearable device. The WTRUs may include devices such as head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

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

[0008] The base station 114a may be part of the RAN 104, 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 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 a cell (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers per sector of the cell, for example, using beamforming to transmit and / or receive signals in desired spatial directions.

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

[0010] More specifically, as noted above, the communications system 100 may be a multiple-access system, but may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c of the RAN 104 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).

[0011] In one 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).

[0012] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.

[0013] In one 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 jointly implement LTE radio access and NR radio access, e.g., using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to and from multiple types of base stations (e.g., eNBs and gNBs).

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

[0015] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one 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 yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not need to access the Internet 110 through the CN 106.

[0016] The RAN 104 may communicate with the CN 106, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as different throughput, latency, error tolerance, reliability, data throughput, mobility, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid 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 understood that the RAN 104 and / or CN 106 may communicate directly or indirectly with other RANs that use the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

[0020] The 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), any other type of integrated circuit (IC), a state machine, etc. 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. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0022] 1B as a single element, 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 over the air interface 116.

[0023] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

[0024] The processor 118 of the WTRU 102 may be coupled to and may receive user-entered data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an 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. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The 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. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. 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 home computer (not shown).

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

[0026] 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) regarding 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) over the 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 appreciated that the WTRU 102 may obtain location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0027] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripherals 138 may include one or more sensors. The sensor 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, a humidity sensor, and the like.

[0028] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe on both the UL (e.g., for transmission) and DL (e.g., for reception)) may be simultaneous and / or together. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference through either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe on either the UL (e.g., for transmission) or DL (e.g., for reception)) may be simultaneous and / or together.

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

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

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

[0032] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are illustrated 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.

[0033] The MME 162 may be connected to each of the eNodeBs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. 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.

[0034] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNodeB handover, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

[0035] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0036] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

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

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

[0039] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. An AP may have access to or interface with a Distribution System (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic originating outside the BSS and destined for a STA may arrive through the AP and be sent to the STA. Traffic originating at a STA and destined for a destination outside the BSS may be sent to the AP to be sent to its respective destination. Traffic between STAs within a BSS may be sent through the AP, for example, where the source STA may send traffic to the AP, and the AP may send traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) a source STA and a destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad hoc" communication mode.

[0040] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically configured width. The primary channel may be the operating channel of the BSS, but may be used by 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 an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), 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 in a given BSS at any given time.

[0041] High Throughput (HT) STAs may use 40 MHz wide channels for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

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

[0043] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communications (MTC), such as MTC devices in macro coverage areas. MTC devices may have limited functionality, including certain features, for example, support for certain and / or limited bandwidths (e.g., only supporting these). An MTC device may include a battery with a battery life above a threshold (eg, to maintain a very long battery life).

[0044] 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 a 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 configured and / or limited by the STAs among all STAs operating in the BSS that support the minimum bandwidth operating mode. In an 802.11ah embodiment, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) the 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) configuration can depend on the status of the primary channel. For example, if a STA (that only supports 1 MHz mode of operation) transmitting to an AP has a busy primary channel, all of the available frequency bands may be considered busy even if most of the available frequency bands are idle.

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

[0046] FIG. 1D is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 104 may also communicate with the CN 106.

[0047] The RAN 104 may include gNBs 180a, 180b, and 180c, although it will be understood that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNB 180a, 180b may transmit signals to and / or receive signals from the gNBs 180a, 180b, and 180c using beamforming. Thus, the gNB 180a may transmit and / or receive wireless signals to and / or from the WTRU 102a using, for example, multiple antennas. In one 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 one embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or 180c).

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

[0049] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to gNBs 180a, 180b, 180c while also communicating with and connecting to another RAN, such as eNodeBs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0050] 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 for network slicing, DC, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D , the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0051] 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 the foregoing elements are illustrated 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.

[0052] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for user authentication of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The network slicing may be used by the AMF 182a, 182b to customize the CN support for the WTRUs 102a, 102b, 102c based on the type of service utilizing the 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, etc. The AMFs 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0053] The SMFs 183a and 183b may be connected to the AMFs 182a and 182b in the CN 106 via an N11 interface. The SMFs 183a and 183b may also be connected to the UPFs 184a and 184b in the CN 106 via an N4 interface. The SMFs 183a and 183b may select and control the UPFs 184a and 184b and configure the routing of traffic through the UPFs 184a and 184b. The SMFs 183a and 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0055] The CN 106 may facilitate communication with other networks. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local DNs 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

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

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

[0058] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0059] The following terms may be used throughout this disclosure.

[0060] [Table 1]

[0061] Internet of Things (IoT) functionality is designed for devices that communicate using traditional cellular networks. Devices with IoT functionality require better power consumption performance and improved network efficiency for bulk operations.

[0062] 2 illustrates an exemplary home automation Personal Internet of Things network (PIN) 200 that may be used in combination with any of the other embodiments described herein. When multiple IoT devices are deployed in a private environment, WTRUs with IoT capabilities can be organized into a Personal IoT Network (PIN). For example, as shown in FIG. 2 , in a home environment, a guest device (or guest PE) 202, a security sensor 204, a motion sensor 206, a smart lock 208, a smart key 210, a smart plug 212A, a smart light 212B, smart plugs 212C and 212D, a smartphone 214, a printer 218, etc. can be managed by a residential gateway 216 and communicate with each other. The smart plug 212A, the smart light 212B, the smart plugs 212C and 212D can function as relay nodes for the guest device (or guest PE) 202, the security sensor 204, the motion sensor 206, the smart lock 208, and the smart key 210. In this example, all devices 202-216 in the home may be equipped with a personal IoT network (PIN). Each of these may be referred to as a PIN Element (PE), and different PIN Element (PE) may have different functions. For example, the residential gateway 216 may be a PIN Element (PE) with gateway functionality (PEGC) that provides connectivity between the PIN Element (PE) 202-214, 218 and between the 5G network 220 and the PIN Element 202-214, 218. A PIN Element (PE) with manageability (PEMC) may be a PIN Element (PE) that provides a means for an authorized administrator to configure and manage PINs. In one example, the residential gateway 216 functioning as a PEGC may also support PIN management functionality and be a PIN Element (PE) with manageability (PEMC). In another example, the smartphone 214 may function as a PEMC that manages the PIN Element (PE) 202-212, 218 in the home automation PIN 200. The smartphone 214 (i.e., the PEMC) may communicate with the PEs 202-212, 218 directly or through a residential gateway 216 (i.e., the PEGC). In one embodiment, the PEMC and the PEGC may be logical functions located in a single entity / device / WTRU. In another embodiment, the PEMC and the PEGC may be logical functions located in different, separate entities / devices / WTRUs. The PEMC and the PEGC may include non-3GPP communication capabilities (e.g., Bluetooth, WiFi, Zigbee, Z-Wave, Bluetooth low energy, etc.) and 3GPP communication capabilities (e.g., LTE, 5G NR, etc.) to communicate with the 5G core network 220, including the PEs 202-218 and the smartphone 222 within the 5G core network 220. PEs 202-212 may include non-3GPP communication capabilities (e.g., Bluetooth, WiFi, Zigbee, Z-Wave, Bluetooth low energy, etc.) for communicating with a smartphone 214 (e.g., PEMC) and / or a residential gateway 216 (e.g., PEGC).The terms PIN Element (PE) with management capabilities, PE with management capabilities, PE management function, PE management function, PIN management, WTRU with management capabilities, and / or any combination thereof may be used interchangeably throughout this disclosure. The terms PIN Element (PE) with gateway capabilities, PE with gateway capabilities, PE gateway function, PE gateway function, PIN gateway, WTRU with gateway capabilities, and / or any combination thereof may be used interchangeably throughout this disclosure.

[0063] FIG. 3 illustrates an exemplary wearable PIN 300 that can be used in combination with any of the other embodiments described herein. As shown in FIG. 3 , wearable devices such as earphones 302, 312, smart glasses 304, 314, and smartwatches 306, 316 can include another type of PIN, where smartphones 308, 318 can function as gateway-capable PIN elements (PEs) (PEGCs) and management-capable PIN elements (PEs) (PEMCs). For example, a wearable PIN 330 can include earphones 302, smart glasses 304, smartwatch 306, and smartphone 308. Smartphone 308 can function as a PEMC and PEGC for earphones 302, smart glasses 304, and smartwatch 306, functioning as a PE in wearable PIN 330. Wearable PIN 330 can be connected to a 5GS 310 via smartphone 308. Similarly, another wearable PIN 335 can coexist with wearable PIN 330. The wearable PIN 335 may also include earphones 312, smart glasses 314, a smartwatch 316, and a smartphone 318. The smartphone 318 may function as a PEMC and PEGC for the earphones 312, smart glasses 314, and smartwatch 316, which act as PEs within the wearable PIN 335. The wearable PIN 335 may be connected to the 5GS 310 via the smartphone 318. In another example, the smartwatches 306, 316, virtual reality (VR) / augmented reality (AR) glasses 304, 314, earphones 302, 312, etc. may communicate with each other within the PIN 330, 335 (or with other WTRUs over a 5G network).

[0064] 4 illustrates an example architecture of a Personal Internet of Things network (PIN) 400 that may be used in combination with any of the other embodiments described herein. As shown in FIG. 4 , a PIN 420 may include, but is not limited to, PIN Elements (PEs) 402, 404, a PIN Management (PEMC) 406, and a PIN Gateway (PEGC) 408. The PIN Elements (PEs) 402, 404 may be WTRUs or non-3GPP devices capable of communicating within the PIN 420. The PIN Management Device (i.e., PEMC) 406 may be a WTRU or PIN Element (PE) capable of managing the PIN 420. The PEGC 408 may be a WTRU or PIN Element (PE) capable of providing connectivity between other PIN Elements (PEs) 402, 404 and a 3GPP network, such as a 5G core network 422. The 5G core network 422 may include the RAN 410, the AMF 412, the SMF 414, and the UDF 416. The UDF 416 may provide connectivity between the 5G network 422 and the data network 418.

[0065] 4, the PIN elements (PEs) 402, 404 can communicate with each other directly or via the PEGC 408. Alternatively or additionally, the PIN elements (PEs) 402, 404 may communicate with a 5G system to obtain 5G service or may communicate with the data network 418 via a 5G core network 422. The 5G core network 422 is an example of a wireless network. Wireless networks with which the PEMC 406 and / or the PEGC 408 may communicate may include, but are not limited to, GSM, CDMA, UMTS, LTE, and 5G.

[0066] As mentioned above, the PIN element (PE) with management capabilities (PEMC) 406 and the PIN element (PE) with gateway capabilities (PEGC) 408 may be WTRUs or UEs with 3GPP and non-3GPP RATs, and all other communications within the PIN 420 may be performed via non-3GPP communications (e.g., WiFi, Bluetooth, etc.) by the PEMC 406 and the PEGC 408.

[0067]

[0013] Figure 5 illustrates an example reference model for a 5G or NextGen network 500, which may be used in combination with any of the other embodiments described herein. As shown in Figure 5, the 5G network may include a WTRU 502, a Radio Access Network (RAN) 504, a User Plane Function (UPF) 506, a Data Network (DN) 508, an Access Control and Mobility Management Function (AMF) 510, a Session Management Function (SMF) 512, a Policy Control Function (PCF) 514, an Application Function (AF) 516, an Authentication Server Function (AUSF) 518, and a Unified Data Manager (UDM) 520.

[0068] Radio Access Network (RAN) 504 may refer to a radio access network based on 5G RAT or evolved E-UTRA that connects to a NextGen core network.

[0069] The Access Control and Mobility Management Function (AMF) 510 may include, but is not limited to, functions such as registration management, connection management, reachability management, and mobility management.

[0070] The Session Management Function (SMF) 512 may include, but is not limited to, the following functions: session management (including session establishment, modification, and release), WTRU IP address allocation, selection and control of UP functions, etc.

[0071] The WTRU or a PE with management capabilities (PEMC) may be responsible for creating and managing the PIN, while the WTRU or a PE with gateway capabilities (PEGC) may facilitate the connection of the PE and PEMC with the CN.

[0072] The PIN may include different PIN elements (PEs) with different characteristics such as wearable devices, home automation devices, vehicle mounted devices, office or smart industrial automation devices, which have different requirements and roles in terms of size, weight, power consumption, mission criticality, high bandwidth, etc. A user based on need can create a network (PIN) for all or a subset of these devices (i.e., PEs) which may be static or dynamic in nature.

[0073] How a PIN is created, the authorization / deauthorization of a PE, the authorization / deauthorization of a PEMC, the authorization / deauthorization of a PEGC, and the activation / deactivation of a PIN are unknown whether the PIN is in the network or the WTRU. Therefore, mechanisms are needed such as how a PIN is created, how a PE is authorized or deauthorized to communicate within a PIN, how the PEMC obtains authorization and deauthorization for PIN creation, how the PEGC obtains authorization and deauthorization for PIN creation, how a PIN is updated or recreated, how a PIN is activated or deactivated, and how to establish the time validity of a PIN and its elements.

[0074] Embodiments for PIN creation, PIN regeneration, PIN authorization and deauthorization, PIN activation and deactivation, and PIN validity periods are described herein. Figure 6 illustrates an example PIN management 600 that can be used in combination with any of the other embodiments described herein.

[0075] Embodiments for PIN creation are described herein. As shown in FIG. 6, PIN creation may include authorization of the PEMC 605, authorization of the PEGC 610, and / or authorization (or activation) of the PIN 615. WTRU-initiated PIN creation may mean that the PIN creation is initiated by the PEMC. The PEMC first requests and obtains authorization to act as the PEMC at 605. The PEGC may request and obtain authorization independently at 610, but may also be selected and added to the PIN by the PEMC. The PEMC and PEGC may establish a direct connection with each other via PC5 or indirectly via Uu. At 615, the PE may establish a connection with the PEMC and request authorization to be part of the PIN; the request for PIN creation may be forwarded by the PEMC to the CN and authorized by the CN or a third-party PIN server. It should be noted that the PEMC and PEGC may be logical entities within a WTRU or device with 3GPP communication capabilities and non-3GPP RAT capabilities, or may be separate entities with 3GPP communication capabilities and non-3GPP RAT capabilities.

[0076] NW-initiated PIN creation may mean that the PIN creation is initiated by the PIN server. The PIN server can request the CN to provide information on all available PEMCs, PEGCs, and PEs that meet certain criteria. The PIN server can create PINs for available PEs, PEMCs, and PEGCs based on a specific service or application.

[0077] Embodiments of PIN duration are described herein. At 620, the CN may provide one or more timers for the validity periods of the PEMC, PEGC, and / or PIN. The one or more timers for the PIN, PEMC, and / or PEGC may start as soon as the CN authorizes them. Alternatively or additionally, the PIN validity timer value may start after a PIN activation indication is sent from the PEMC to the CN. The PIN is active as long as the PIN timer, PEMC timer, and / or PEGC timer are valid. The PIN may be deactivated as soon as the period of one of the timers expires. Alternatively or additionally, the PIN may be deactivated based on an event or trigger by the WTRU (e.g., the PEMC) or the CN. The term timer may be referred to as a clock, counter, duration, time unit, or any other device / value configured to measure a period of time throughout this disclosure.

[0078] Embodiments for PIN updates are described herein. Once a PIN is created and communication is established, the PIN can be updated at 625 if one or more PEs are added, modified, or removed from the PIN. A change in PE does not change the PIN type or require reauthorization, but may result in different QoS requirements (e.g., requiring changes to existing PDU sessions or updates to QoS flows).

[0079] Similar to above, an existing PIN may be updated by the service provider (e.g., PIN server). This may be due to changes in service and operation that require adding, modifying, or removing any PEs. Thus, PIN updates may be initiated based on service requirements.

[0080] Embodiments for PIN re-creation are described herein. Similar to PIN updates, where a new PIN element (PE) can be bound to or unbound from the PIN, if the PE being bound or unbound belongs to a PE category that changes PIN type or belongs to a secure PIN type, the PE may not be authorized to bind to the PIN, but if the PE is authorized by the PEMC at 630, PIN re-creation may be required. PIN re-creation may mean that the PEMC and PEGC remain connected and do not require re-authorization by the network. However, binding or unbinding of a PE may cause the old PIN to be discarded and authorization of a new PIN to be initiated by the PEMC.

[0081] 7A and 7B illustrate an example WTRU-initiated PIN creation 700, which may be used in combination with any of the other embodiments described herein. WTRU-initiated PIN creation may include four stages: 1) capability negotiation and policy provisioning between the PEMC and the AMF / UDM / PCF; 2) authorization for PEMC and parameter exchange, which also requests PIN creation, PIN ID, and context, is generated during this stage; 3) PIN element authorization to bind to the PIN; and 4) PIN creation and activation instruction.

[0082] 7A, in step 714, for PIN authorization and creation, the CN, which includes the AMF 707 / PCF 708 / UDM 709 and PIN-NEF 710, may require certain parameters received as policy parameters from a third-party PIN server 712 via the PIN-NEF 710. These parameters may include, but are not limited to, pre-authorized PIN types and PE types for which the CN does not require authorization from the PIN server. Alternatively or additionally, these parameters may include, but are not limited to, PIN types and PE types for which authorization can only be performed by the PIN server.

[0083] In step 716, the WTRU (e.g., the PEMC 704) may send a NAS message (e.g., a registration request) to the AMF 707. The NAS message may include, but is not limited to, a PEMC capability (or PEMC function), a PEGC capability (or PEGC capability), applications or services supported by the PEMC, a PIN server address, a PIN type, and / or a PIN size. The PEMC capability may indicate that the WTRU (i.e., the PEMC 704) can provide management functionality and / or that the WTRU (i.e., the PEMC 704) has PE functionality. The PEGC capability may indicate that the WTRU (i.e., the PEGC 706) can provide gateway functionality and / or that the WTRU (i.e., the PEGC 706) may have PE functionality. The applications or services supported by the PEMC may indicate the types of applications and services that the PEMC 704 can provide to the PE 702 in the PIN. For example, the applications or services supported by the PEMC 704 may include IoT, streaming, healthcare, VR, and / or AR applications / services. The PIN type may indicate the type of PIN network that the PEMC 704 can provide. The PIN types may include, but are not limited to, IoT, streaming, healthcare, etc.

[0084] In step 718, the AMF 707 may receive the PEMC capabilities and confirm with the UDM 709 and / or PCF 708 whether the WTRU (i.e., the PEMC 704) is authorized to function as a PEMC. The UDM 709 may include subscription information of the WTRU in the network. The AMF 707 may also receive the PEGC capabilities.

[0085] In step 720, the AMF 707 may request authorization for the PEMC 704 / PEGC 706 from the PIN server 712 before responding to a NAS message (e.g., a registration request) from the WTRU (i.e., the PEMC 704). This operation may be based on some round-trip messaging between the AMF 707 and the PIN server 712 via the PIN-NEF 710. Specifically, the AMF 707 may send the WTRU user ID, PEMC capabilities, applications or services supported by the PEMC 704, PIN type, PIN size, etc. to the PIN server 712. The PIN server 712 may respond with authorized PIN types, PIN sizes, number of PEs per type, PIN ID settings, a list of PIN servers, validity period of the PEMC / PEGC authorization, etc. It should be noted that step 720 may be optional depending on the pre-authorization information the AMF 707 / PCF 708 / UDM 709 has from the PIN server 712 regarding the PEMC / PEGC capabilities.

[0086] In step 722, the AMF 707 may send a NAS message (e.g., a registration response) to the WTRU (i.e., the PEMC 704). The NAS message may include, but is not limited to, PEMC authorization, pre-authorization to initiate PIN creation with certain characteristics (e.g., PIN type, PIN size, number of PEs per type) that may indicate or specify for which PEs local authorization by the PEMC is sufficient or for which PEs network authorization (e.g., by the PIN server 712) is required. For example, if the AMF 707 already has pre-authorization information for the PEMC 704, the AMF 707 may send PEMC authorization to the WTRU (i.e., the PEMC 704) with an indication that the PEMC 704 is authorized to act as the PEMC 704 in the PIN. If the AMF 707 does not have pre-authorization information for the PEMC 704, the AMF 707 may send a request to the PIN server 712 as disclosed in step 720. The PIN type included in the NAS message may indicate the type of PIN that the PEMC 704 is authorized to create. The NAS message (e.g., registration response) may include multiple PIN types for multiple PINs. The PIN ID setting may include one or more PIN IDs that the PEMC 704 is authorized to create or use. The PIN size may indicate the total number of PEs allowed within the PIN. The maximum number of PEs per type may indicate the maximum number of PEs allowed per PIN type. For example, the maximum number of PEs per type may indicate that 20 IoT devices are allowed for an IoT PIN type, but only one streaming device is allowed for a streaming PIN type. The NAS message (e.g., registration response) may also include the PIN, PEMC, and / or PEGC validity period with timer values, the PIN ID setting, and the authorized application / service. The PIN, PEMC, and / or PEGC validity period may be in milliseconds, seconds, minutes, hours, days, months, etc.

[0087] At step 724, the WTRU (i.e., the PEMC 704) may receive one or more connection requests from the PE 702, for example, via WiFi or Bluetooth, which are outside the scope of 3GPP. The PEMC 704 may have received a device ID and a PE ID, which may be used to create a PIN. The connection requests received from the PE(s) 702 may include, but are not limited to, a device ID, a PE ID, a PE type, and / or PE capabilities. The PE type may indicate the device type of the PE, such as a sensor, a light, a plug, a printer, a mobile phone, a wearable device, an augmented reality (AR) device, a vehicle-mounted device, and a virtual reality (VR) device. The PE capabilities may indicate the radio access technologies that the PE 702 may support, such as Bluetooth, Wi-Fi, Bluetooth Low-Energy (BLE), Zigbee, and Z-Wave.

[0088] In step 726, when a WTRU (i.e., the PEMC 704) connects to an available PE, the WTRU (i.e., the PEMC 704) may first determine whether this particular PE is from a pre-authorized PE type that can be locally authorized by the PEMC 704. If the PE type can be locally authorized, the WTRU (i.e., the PEMC 704) may authorize the connection request from the PE 702. In one example, the PEMC 704 may authorize the connection request based on a PE type that is compatible with the pre-authorized PE type and / or a pre-authorized PIN type. The pre-authorized PE type or pre-authorized PIN type may be received from the AMF 707 (e.g., in the NAS response message in step 722). In another example, the PEMC 704 may authorize the connection request based on a PE type and / or PE capability that is compatible with the pre-authorized PIN type. For example, if the PE type is an IoT device and the pre-authorized PIN type is temperature sensing, the WTRU (i.e., the PEMC 704) may authorize the connection request from the PE 702. If the PE type is IoT device but the pre-authorized PIN type is streaming media, the WTRU (ie, PEMC 704) may not allow the connection request from the PE 702.

[0089] The WTRU (i.e., PEMC 704) can connect with all available PEs 702 that are desired and discoverable for a particular service. The PEMC 704 may have pre-authorized some PEs locally, but for the rest, the PEMC 704 may have to request authorization from the CN or third-party PIN server 712. If network authorization is required for a PE 702, in step 728 the WTRU (i.e., PEMC 704) can send a mobility registration request to the AMF 707 including the pre-authorized PIN type, PE information (e.g., PE ID, PE capabilities and / or PE type), application / service, and PIN server address, for example, selected from the list received in step 720.

[0090] Step 730 may be the same as steps 718 and 720, but with slightly different parameters. Authorization may additionally or alternatively occur as in the exemplary procedures described below.

[0091] In one example, the AMF 707 may itself authorize the PE 702, as described in step 718. However, the CN may additionally or alternatively provide a timer value for the PIN validity period.

[0092] In another example, if the PIN server 712 needs to authorize, the AMF 707 may send a request as described in step 720. Specifically, the AMF 707 may send the pre-authorized PIN type, PE information (e.g., PE ID, PE function, and / or PE type), and application / service to the PIN server address selected by the PEMC. The PIN server 712 may respond with a list of authorized PEs with PE IDs, a PIN validity period with a timer value.

[0093] In step 732, the AMF 707 sends a mobility registration response to the PEMC 704, which may include the authorized PIN type, PIN ID, PIN policy parameters if new, CN connectivity parameters, and PIN validity period with timer value. It may also include the S-NSSAI NSI ID or DNN. The CN connectivity parameters may include one or more allowed Quality of Service (QoS) requirements associated with the PE type of the PE 702.

[0094] In step 734, the WTRU (i.e., the PEMC 704) may establish a connection with the PEGC 706 for PIN connectivity. In this step, the PEMC 704 may perform PEGC selection and request PDU session establishment with the PEGC 706. In one example, a direct unicast communication link may be established between the PEMC 704 and the PEGC 706, assuming both the PEMC 704 and the PEGC 706 can communicate directly via PC5.

[0095] In step 736, a PIN may be created and a PIN activation indication may be sent to the CN and / or PIN server 712. The CN and / or PIN server 712 may start a PIN validity timer.

[0096] In one embodiment, once the WTRU (i.e., PEMC 704) is authorized by the network according to steps 716-722 of WTRU-initiated PIN creation 700, the PEMC 704 may establish a PDU session with the CN. The remaining procedures for PE authorization and PIN creation may then alternatively or additionally be performed over the user plane using the PDU session. This procedure can be described as follows:

[0097] First, the PEMC 704 and the PEGC 706 may be authorized (e.g., independently). Both the PEMC 704 and the PEGC 706 may discover each other, and a PDU connection between the PEMC 704 and the PIN server 712 may be established.

[0098] Second, the PEMC 704 may receive a connection request from the PE 702, for example, via WiFi or Bluetooth, which is outside the scope of 3GPP, however, the PEMC 704 may have received a device ID and PE ID that can be further used for PIN creation.

[0099] Third, the PEMC 704 can trigger secondary authorization, where an application in the PEMC 704 sends PE information, including, for example, PIN type, PE information (e.g., PE ID, PE type, and number of PEs), application / service, etc., to an application in the PIN server.

[0100] Finally, an application within the PEMC 704 can receive PIN authorization from the PIN server 712 .

[0101] In another embodiment, the WTRU may perform authorization to act as a PEGC 706 in the same manner as is done for the PEMC 704 in steps 716-722 of WTRU-initiated PIN creation 700. A pre-authorized PEMC 704 may discover and establish a connection with a suitable / available PEGC 706 and a connection with the network via the PEGC 706.

[0102] 8 illustrates an example PIN management procedure 800 that can be used in combination with any of the other embodiments described herein. At step 805, a first WTRU may send a first Non-Access Stratum (NAS) request message to a network node in a cellular network. The first NAS request message may indicate that the first WTRU can function as a PEMC in the PIN. The network node in the cellular network may be a base station (BS), an AMF, a PCF, a UDM, a NEF, or any other device / entity / function in a core network (CN) or RAN that can communicate with the WTRU for PIN creation / management. The cellular network may include, but is not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 5G New Radio (NR), and 6G. In response to the first NAS request message, at step 810, the WTRU may receive a first NAS response message from the network node in the cellular network. The first NAS response message may include, but is not limited to, authorization information of the first WTRU's request, an authorized PIN type, and one or more validity periods of the PIN / PEMC / PEGC. The authorization information may indicate that the WTRU is allowed to act as a PEMC in the PIN being created. The authorized PIN types may include, but are not limited to, home security, industrial security, home automation, industrial automation, healthcare monitoring, temperature sensing, motion detection, augmented reality (AR), virtual reality (VR), connected vehicles, and autonomous vehicles.

[0103] At step 815, the first WTRU may receive a connection request message from the second WTRU, the connection request message including PE information associated with the second WTRU. The PE information associated with the second WTRU may include, but is not limited to, the second WTRU's PE type and the second WTRU's PE capabilities. The PE type may include, but is not limited to, a sensor, a light, a plug, a printer, a mobile phone, a wearable device, an augmented reality (AR) device, a vehicle-mounted device, and a virtual reality (VR) device. The PE capabilities may indicate non-3GPP RATs that the PE may support. Such non-3GPP RATs may include, but are not limited to, Bluetooth, Wi-Fi, Bluetooth low energy (BLE), Zigbee, and Z-Wave. At step 820, if the PE type and PE capabilities are compatible with the authorized PIN type, the WTRU may send a connection response message to the second WTRU indicating that the second WTRU is authorized to act as or bind to a PIN element (PE) of the PIN. For example, if the PE type is plug, the PE function is Zigbee, and the pre-authorized PIN type is home automation, the first WTRU may authorize a connection request from the second WTRU. If the PE type is plug, the PE function is Zigbee, but the pre-authorized PIN type is streaming media, the first WTRU (i.e., PEMC 704) may not authorize a connection request from the second WTRU. In one embodiment, the first WTRU may use only the PE type and the authorized PIN type to determine compatibility. In another embodiment, the first WTRU may use only the PE type and the authorized PE type to determine combability. Once the second WTRU is authorized by the first WTRU, or after the first WTRU sends a connection response message to the second WTRU, the first WTRU may send a PIN activation indication to the CN or PIN server.

[0104] If the first WTRU determines in step 820 that the PE type and PE functions are not compatible with the authorized PIN type, then in step 830 the first WTRU may send a second NAS request message to a network node in the cellular network requesting a core network (CN) or PIN server for authorization of the second WTRU to act as a PE for the PIN. The second NAS request message may include PE information associated with the second WTRU, as described above. In step 835, the first WTRU may receive a second NAS response message from the network node in the cellular network indicating that the second WTRU has been authorized by the CN or PIN server to act as a PE for the PIN. The second NAS response message may include, but is not limited to, the authorized PIN type, a PIN ID, one or more CN connectivity parameters, and a PIN validity period. Once the second WTRU is authorized as a PE by the CN or PIN server, in step 840 the first WTRU may send another connection response message to the second WTRU indicating that the second WTRU has been authorized to act as a PE for the PIN. The one or more CN connectivity parameters may include, but are not limited to, one or more allowed Quality of Service (QoS) requirements associated with the second WTRU or the PE type of the second WTRU. Once the second WTRU is authorized by the CN or PIN server, or after the first WTRU has sent another connection response message to the second WTRU, the first WTRU may send a PIN activation indication to the CN or PIN server.

[0105] In one embodiment, when the received validity period of the PEMC / PEGC / PIN expires, the first WTRU may send a third NAS request message to a network node in the cellular network for re-authorization of the second PE. The third NAS request message may request a core network (CN) or a PIN server to re-authorize the second WTRU to function as a PE for the PIN. The third NAS request message may include PE information associated with the second WTRU, as described above.

[0106] After the PIN is created, the first WTRU may receive another connection request message from the third WTRU in step 845. The another connection request message may include PE information associated with the third WTRU. The PE information related to the third WTRU may include, but is not limited to, the third WTRU's PE type and the third WTRU's PE capabilities. If one or more QoS requirements associated with the third WTRU or the third WTRU's PE type differ from one or more allowed QoS requirements associated with the second WTRU or the second WTRU's PE type, the first WTRU may send a third NAS request message to a network node in the cellular network or a PIN server in step 850, requesting authorization for the third WTRU to act as a PE for the PIN. The third NAS request message may include PE information associated with the third WTRU, as described above.

[0107] It should be noted that the first WTRU may be capable of both 3GPP and non-3GPP RATs, and the second WTRU is capable of non-3GPP RATs. 3GPP RATs may include, but are not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 5G New Radio (NR), and 6G. Non-3GPP RATs may include, but are not limited to, Bluetooth, Wi-Fi, Bluetooth Low Energy (BLE), Zigbee, and Z-Wave. The PE capabilities of the second WTRU or third WTRU may indicate that the second WTRU or third WTRU can support a non-3GPP RAT.

[0108] Embodiments for PIN update and re-creation are described herein. In these embodiments, it can be assumed that a PIN is created and a connection between the PIN, the CN, and the PIN server is established. When one or more PEs bind or unbind to the PIN, they may or may not significantly affect the PIN. If the change is significant with respect to a change in QoS requirements or results in a change in PIN type, the PIN can be updated or re-created based on the embodiments described herein. Specifically, once a PIN is created and in an operational state, the following scenarios may occur: (1) a PE in the PIN may become unavailable; (2) a new PE becomes available to bind the PIN; (3) the desired or allowed QOS may change due to PE binding / unbinding or unavailability; and (4) the PIN type and characteristics may change, for example, especially for security- or emergency-related PINs.

[0109] An embodiment for a WTRU-initiated PIN update is described herein. In this embodiment, a scenario describes a PIN update that may be initiated by the WTRU (e.g., a PEMC or a PEGC). Figure 9 illustrates an example WTRU-initiated PIN update 900 that may be used in combination with any of the other embodiments described herein.

[0110] As discussed above, it is assumed that a PIN is established in step 914. In step 916, the PIN component 902 can be enabled or disabled. The PEMC 904 can recognize it. New PEs 902 can connect to the PEMC 904 to notify it about their availability. Existing PEs can go down and be detected by the PEMC 904. Existing PEs 902 can offer additional services and QOS requirements can change (e.g., aggregate QOS from PEGC 906 to 5GS). One or more new PEs 902 attempting to bind to a PIN, or one or more existing PEs 902 attempting to leave a PIN, can trigger a PIN update and / or PIN recreation / re-authorization.

[0111] In step 918, the PEMC 904 may determine whether the PIN update in step 916 has any impact on the type or QoS requirements. In step 920, if the PEMC 904 determines a change in the PIN type or QoS, the PEMC 904 may send a NAS message (e.g., a mobility registration request to the AMF in the CN 908), which may include parameters such as the old PIN ID, S-NSSAI, DNN, an indication of the PIN type / QoS change, and newly added / deleted PE information (e.g., PE ID and PE type). In step 922, the AMF may check with the CN 908 and / or PIN server 912 whether re-authorization is required. If re-authorization is not required, the QoS parameters may be updated. In step 924, the AMF may send new CN connectivity parameters to the PEMC 904 for PDU session modification or QoS flow update via NAS signaling, for example using a mobility registration response.

[0112] Steps 926-930 and step 932 illustrate two alternative or additional approaches. In the first scenario, in step 926, NAS signaling may occur between the CN 908 and the PEMC 904, but this is unknown to the PEGC 906. Therefore, the PEMC 904 may send an instruction to the PEGC 906 to notify the QoS requirement change and provide new CN connectivity parameters for the PDU session change and a PIN ID. In step 928a, the PEGC 906 may initiate the session change and send a PDU session change request to the SMF, including the new CN connectivity parameters, the PIN ID. In step 928b, the SMF may send a session change accept, which may include the PIN ID. In step 930, the PEGC 906 may send a PEGC indication to the PEMC 904, indicating that the connection for the updated PIN has been successfully established. The PEGC indication may include the PIN ID.

[0113] In a second scenario, a network-initiated PDU session change may be established in step 932, with the AMF notifying the SMF of the change in PIN QoS requirements after step 924. The SMF may notify the PEGC 906 that the PDU session has been modified. The PEGC 906 may notify the PEMC 904 of the modified PDU session, including the connectivity parameters of the PIN ID. In step 934, a PIN connection with the new PIN may be established.

[0114] Embodiments for WTRU initiated PIN recreation are described herein. This embodiment illustrates that PIN recreation can be initiated by the WTRU (e.g., PEMC or PEGC). By recreation, it may mean that the PEMC / PEGC is authorized and connected to the CN, but the PIN type changes due to a PE joining, leaving, or becoming unavailable without authorizing the PIN. Such an action may require first deregistering the PIN and requesting new authorization for PIN recreation with updated PE information.

[0115] 10 illustrates an exemplary WTUR-initiated PIN recreation 1000 that can be used in combination with any of the other embodiments described herein. It is assumed that a PIN is established in step 1014. Steps 1016-1022 are the same as those described in FIG. 9 and will not be described here for the sake of brevity.

[0116] In step 1024, if re-authorization is required because the new PE 1002 joining or leaving the PIN may have significantly different characteristics (e.g., the PE 1002 is safety or security critical), the AMF via NAS signaling (e.g., Mobility Registration Response) may send a PIN deregistration notification to the PEMC 1004, requesting re-authorization for PIN re-creation. In step 1026, the PDU session may be released. This may be initiated by the PEMC 1004 requesting the PEGC 1006 to initiate a PDU session release procedure. Alternatively or additionally, the PDU session release may be initiated by the CN 1008 (e.g., SMF) or by an application server (or PIN server 1012) requesting an application in the PEMC 1004. In step 1028, a new PIN may be created in the same manner as shown in FIG. 7 (e.g., steps 724-738). This PIN creation may be referred to as a PIN re-creation as the PEMC 1004, PEGC 1006 may remain the same, but the PIN is created for an updated PE.

[0117]

[0013] Embodiments for PIN activation and deactivation are described herein. PIN activation and deactivation may need to be handled for PIN management. Embodiments for PIN activation and deactivation may include, for example, the following three scenarios: (1) timer-based (i.e., the WTRU or network determines PIN activation and deactivation upon timer expiration based on a timer value); (2) also timer-based, but where the timer value is extended by the CN or PIN server; and (3) where the PIN may be deactivated by the network operator or an authorized third-party PIN server, which may be both immediate and event-based triggered.

[0118] FIG. 11 is a diagram illustrating an example of PIN activation / deactivation with a validity timer 1100, which may be used in combination with any of the other embodiments described herein. As described above, once the PIN is created, it may or may not be activated immediately, in step 1114. However, once the PIN is activated, an instruction specifying the activation of the PIN and a reference time value may be sent to the CN 1108 and / or the PIN server 1112.

[0119] In the first scenario (i.e., option 1 1116), the PIN validity period may expire and the PEMC 1104 may send a PIN deactivation indication to the CN 1108 and / or PIN server 1112, which may also trigger a PDU session release and PIN deregistration. The PIN timer may expire and the PIN may be released, but the PEMC 1104 and PEGC 1106 may still be authorized and connected to the CN 1108 for PIN recreation. Reauthorization may not need to be performed.

[0120] In the second scenario (i.e., option 2 1118), if there are no significant changes to the PIN in terms of type, size, etc. before the PIN validity period expires, the CN 1108 can simply extend the time or reset it. The updated parameters can be sent to the WTRU (e.g., PEMC 1104) via a UE Configuration Update (UCU) command.

[0121] The WTRU (e.g., PEMC 1104) may respond with a UCU completion message or indication. The UCU completion message may include, but is not limited to, a PIN active indication that synchronizes clocks on the WTRU (e.g., PEMC 1104) and the CN 1108 for a timer duration.

[0122] In a third scenario (i.e., option 3 1122), a PIN deactivation instruction may be initiated by the CN 1108 and / or the PIN server 1112 upon certain conditions that invalidate the PIN connection and automatically release the PDU session.

[0123] Embodiments for network-initiated PIN creation are described herein. Network-initiated PIN creation can be accomplished, for example, in two steps. The first step is the same as that shown in FIG. 7. This allows the network to have information about available PEMCs, PEGCs, and PEs. Assuming that is known, FIG. 11 illustrates an exemplary network-initiated PIN creation 1200, which can be used in combination with any of the other embodiments described herein. Network-initiated PIN creation 1200 may be initiated by a managed service provider. The service provider can select the desired PE 1202, PEMC 1206, and PEGC 1204 to provide service. Note that the network may refer to any 3GPP network, such as a 5G system (5GS), including a CN and a RAN. The network may include an AMF / SMF 1208 and a PIN-NEF 1210.

[0124] In step 1214, the service provider can query available PEs 1202 by providing an application / service name, location, and / or service area. The application / service name may be the service / application the service provider wants to offer. It may be a string identifying the service, such as "GAMING," "AR / VR," "SURVILLENCE," or "HEALTH." The network (e.g., 5GS) may assume it knows the service name as part of a business agreement. The location may be a Tracking Area Identity (TAI), EUTRA Cell Global Identifier (ECGI), etc. The service area may be a metropolitan area code, geographic location, etc. In step 1216, the network (e.g., 5GS) can find whether a PIN exists based on the "application name," "location," and "service area." If not, it can attempt to find available PEs 1202, PEMCs 1206, and PEGCs 1204 that can support the application based on that information. In step 1218, the network (e.g., 5GS) can provide an available list of PEs and PEMCs 1206, PEGCs 1204 available at the desired location to support the application. It can provide a list of information elements: list [{location, application-level PE ID}, {location, application-level PE ID}, ....] The application-level PE IDs are assumed to be PE IDs known to the service producer.

[0125] In step 1219, the service provider may select a subset of PEs 1202, PEMCs 1206, and PEGCs 1204 to provide the desired service. It may initiate PIN creation by sending a PIN creation message to the network (e.g., 5GS) in step 1220, which may include, but is not limited to, the application name (string); service location (TAI, CGI); and selected application-level PE IDs (PE ID list (1..n)). In step 1221, the selected PE IDs may include PEs 1202, PEMCs 1206, and / or PEGCs 1204. If PEs 1202, PEMCs 1206, and / or PEGCs 1204 are not available, the network (e.g., 5GS) may select another PE ID. In step 1222, the network (e.g., 5GS) may determine the devices (e.g., PEs 1202, PEMCs 1206, and PEGCs 1204) based on the application-level IDs and initiate PIN creation. Application-level PE IDs can be translated to network-level PE IDs. PIN IDs and PE IDs associated with PIN IDs can be created. Allowed QoS can be determined based on subscriptions and business agreements.

[0126] In step 1224, the network (e.g., 5GS) may send a PIN creation request to the PEMC 1206 using a WTRU Configuration Update message. The WTRU Configuration Update message may include, but is not limited to, a PIN ID, a PIN size, allowed QoS requirements, and a list of elements. PIN ID: integer or string; identifies the PIN to be created. PIN size may be an integer indicating the maximum number of allowed PEs. Allowed QoS requirements may be allowed or desired for the entire PIN. It may be an aggregation of the allowed QoS of individual PEs. The list of elements or list of PE elements may be a list of 1...N elements. Specifically, list_of_Pin_elements[] may include, but is not limited to: (1) PIN type: temperature sensor if AR / VR; (2) allowed QoS, optional: allowed QoS for the PIN type; (3) max number of allowed PIN types: integer indicating the maximum number of allowed PE types. (4) A list of {PE_ID, timer value}(1....n), where the timer value for each PE_ID indicates the validity period of the identified PIN element; and / or (5) the network (e.g., 5GS) may include other available PEMC1206 and PEGC1204 in the list List_of_Pin_elements[ ].

[0127] In steps 1226A,B, the PEGC 1204 may be configured as follows.

[0128] In the first scenario (i.e., option 1 1226A), the PEMC 1206 can send configuration information to the PEGC 1204 by sending a Configuration Update message. This message can include, but is not limited to: (1) PIN ID: an integer or string identifying the PIN to be created; (2) Aggregate QOS: the PE GW's expected QOS requirements for 5GS; (3) List_of_Pin_elements[]: a list of 1...N PIN elements. The list of 1...N PIN elements can include, but is not limited to: (1) PIN Type: if AR / VR, temperature sensor; (2) Allowed QoS, optional: the allowed QoS for the PIN type; and / or (3) a list (1...n) of {PE_ID, timer value}, where the timer value for each PE_ID indicates the validity period for the identified PE.

[0129] In the second scenario (i.e., Option 2 1226B), the network (e.g., 5GS) can configure the PEGC 1204 by sending a Configuration Update message. This message includes: (1) PIN ID: which may include, but is not limited to, an integer or string, identifying the PIN to be created; (2) Aggregate QOS: the expected QOS requirements of the PE GW towards 5GS; and / or (3) List_of_Pin_elements[]. The list of 1...N PIN elements can include: (1) PIN Type: if AR / VR, temperature sensor; (2) Allowed QoS, optional: the allowed QoS for the PIN type; and (3) a list (1...n) of {PE_ID, timer value}, where the timer value for each PE_ID indicates the validity period for the identified PE.

[0130] In step 1228, the PEMC 1206 may trigger the PE 1202 to bind to the PIN. In step 1230, the PE 1202 may connect to the PEGC 1204, and a connection may be set up to a network (e.g., 5GS) by the PE 1202 and / or the PEGC 1204 within the PE 1202.

[0131] Assuming the PIN was successfully set up as in step 1230, the PEMC 1206 may notify the network (e.g., 5GS) by sending a WTRU configuration update response in step 1232. The configuration update response may include, but is not limited to, (1) a PIN ID: an integer or string identifying the created PIN; (2) a list of PIN elements [PE_ID....]: the PIN element portion of the created PIN; and / or (3) a result: success or failure. In step 1234, the network (e.g., 5GS) may send the PIN creation response to the service provider. The PIN creation response includes: (1) a PIN ID, which may include, but is not limited to, an integer or string, identifying the created PIN; (2) a list of PIN elements [application-level PIN ID, ....], which are the PIN element portions of the created PIN; and / or (3) a result, which is success or failure.

[0132] An embodiment for NW-initiated PIN update is described herein. Figure 12 illustrates an example network-initiated PIN update that can be used in combination with any of the other embodiments described herein. In this embodiment, the scenario describes a PIN update managed by a service provider.

[0133] In step 1314, the PE 1302 may become available or unavailable. The PEMC 1306 may recognize this. A new PE 1302 may connect to the PEMC 1306 to notify it of its availability. An existing PE may be down and detected by the PEMC 1306. The existing PE may provide additional services, and QoS requirements may change (e.g., aggregated QoS from the PEGC 1304 to the network (e.g., 5GS)). For example, the existing PE may support multiple different PINs or services. When the existing PE leaves one of the multiple PINs, the event may trigger the existing PE to provide a different service associated with a different PE to which the existing PE is still associated. Note that the network may refer to any 3GPP network, such as a 5G system (5GS), including a CN and a RAN. The network may include an AMF / SMF 1308 and a PIN-NEF 1310.

[0134] In step 1316, the PEMC 1306 can notify the network (e.g., 5GS) of the change by sending a mobility registration request. The mobility registration request includes: (1) PIN ID: which may include, but is not limited to, an integer or string, identifying the PIN; (2) Change Instruction: Enum(newPE, peUnav, qosChange); (3) PE-ID: a string, identifying an available or unavailable PIN; (4) qosReq: a string, describing the new aggregate QOS requirements; (5) S-NSSAI: identifying the slice containing the PIN; and (6) DNN: for the updated PIN.

[0135] In step 1318, the network (e.g., 5GS) may notify the PIN service provider (e.g., PIN server 1312) of the change in PE availability or PIN QoS. The network (e.g., 5GS) may initially authorize the change with the service provider (e.g., PIN server 1312). In step 1320, the network (e.g., 5GS) may notify the PEMC 1306 that the change has been authorized by sending a mobility registration response. The mobility registration response may include, but is not limited to, allow / prohibit indications that may add a new PE or update the QoS.

[0136] In step 1322, the service provider (e.g., PIN server 1312) may decide to update the PIN, which may be one or more of the following actions: (1) Remove the PE-ID from the PIN, identified by the PIN ID, or (2) Add the PE-ID to the current PIN, identified by the PIN ID. (3) Update QOS for PIN. The service provider (e.g., PIN server 1312) can send an update PIN message to the network (e.g., 5GS). The PIN update message includes: (1) PIN ID: which may include, but is not limited to, an integer or a string. It identifies the PIN; (2) New Application-Level PE ID: a list (1...n) of PE IDs; this list includes the PEs for the PIN, taking into account the added or removed PEs; and (3) Authorized QOS: YES or NO. In step 1324, the network (e.g., 5GS) can identify the corresponding PEMC 1306 based on the PIN ID.

[0137] In step 1326, the network (e.g., 5GS) may send a WTRU Configuration Update message to the PEMC 1306. The WTRU Configuration Update message may include, but is not limited to, (1) PIN ID and (2) ListUpdate_action{1...n}. ListUpdate_action{1...n} may include, but is not limited to, (1) Action: Enum Add, Delete, Update_QOS; (2) PIN Type: Identifies whether AR / VR, temperature sensor; (3) {List of PE-ID(1...n): PE identifier; PIN_Duration(1.n): timer value}; (4) Updated_QOS: new QoS from the PEGC 1304 to the network (e.g., 5GS).

[0138] In steps 1328A,B, the PEGC 1304 may be configured as follows.

[0139] In the first scenario (i.e., option 1 1328A), the PEMC 1306 can send configuration information to the PEGC 1304 by sending a Configuration Update message. The Configuration Update message may include, but is not limited to: (1) PIN ID: an integer or string identifying the PIN to be updated; (2) a list of Update_Action{1...n}. The list of Update_Action{1...n} can include, but is not limited to: (1) Action: Enum ADD, DELETE, UPDATE_QOS; (2) List_of_Pin_elements[]: a list of 1...N PIN elements; and (3) Aggregate QoS: the PEGC 1304's updated QoS requirements for the network (e.g., 5GS). The list of 1...N PIN elements can include, but is not limited to: (1) PIN Type: if AR / VR, then temperature sensor. (2) Allowed QoS, optional: the allowed QoS for the PIN type; and (3) a list of {PE_ID, Timer value} (1....n), where the timer value for each PE_ID indicates the validity period of the identified PIN element.

[0140] In a second scenario (i.e., option 2 1328B), the network (e.g., 5GS) can configure the PEGC 1304 by sending a configuration update message. This configuration update message can include, but is not limited to: (1) PIN ID: integer or string; identifying the PIN to be updated; (2) a list of Update_Action{1...n}. The list of Update_Action{1...n} can include, but is not limited to: (1) Action: Enum ADD, DELETE, UPDATE_QOS; (2) List_of_Pin_elements[]: list of 1...N PIN elements; and (3) Aggregate QoS: the PEGC 1304's updated QoS requirements for the network (e.g., 5GS). The list of 1...N PIN elements can include, but is not limited to: (1) PIN Type: if AR / VR, then temperature sensor. (2) Allowed QoS, optional: the allowed QoS for the PIN type; and (3) a list of {PE_ID, Timer value} (1....n), where the timer value for each PE_ID indicates the validity period of the identified PIN element.

[0141] In step 1330, if a new PE 1302 is available, the PEMC 1306 can trigger the PE 1302 to bind to the PIN. In step 1332, the new PE 1302 can connect to the unavailable PEGC 1304 or PE. The PEGC 1304 can, for example, update the PE 1302 or the connection configuration between the PEs 1302 to the network (e.g., 5GS).

[0142] In step 1334, assuming the PIN was successfully set up, the PEMC 1306 may notify the network (e.g., 5GS) by sending a WTRU Configuration Update Response. The WTRU Configuration Update Response includes: (1) a PIN ID: which may include, but is not limited to, an integer or string, identifying the created PIN; (2) a list of PIN elements [PE_ID....] the PIN element portion of the created PIN; and (3) a result: success or failure.

[0143] In step 1336, the network (e.g., 5GS) can send an Update_PIN_Response to the service provider (e.g., PIN server 1312). The Update_PIN_Response may include, but is not limited to: (1) PIN ID: integer or string; identifying the created PIN; (2) a list of PIN elements [application-level PIN ID, ....]: the PIN element portion of the created PIN; and (3) a result: success or failure. In step 1338, the PIN is updated by the network.

[0144] While features and elements are described above in particular combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with the other features and elements. Additionally, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, 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.

Claims

1. 1. A method for use by a first wireless transmit / receive unit (WTRU), comprising: receiving, by a first WTRU authorized to act as a PIN Element (PE) with management capabilities (PEMC) in a PIN associated with a Personal Internet of Things Network (PIN) identity, from a second WTRU, a connection request message including PE information associated with the second WTRU; sending a connection response message to the second WTRU based on the PIN identification and the PE information, indicating that the second WTRU is authorized to act as a PIN Element (PE) for the PIN; A method comprising:

2. The method of claim 1 , wherein the PE information includes a device identification and a PE identification.

3. 3. The method of claim 2, wherein the device type of the second WTRU includes one or more of a sensor, a light, a plug, a printer, a cellular phone, a wearable device, an augmented reality (AR) device, an in-vehicle device, or a virtual reality (VR) device.

4. sending a registration request message to a network node, the PEMC information including an ability of the first WTRU to act as a PEMC for the PIN and a service provided by the first WTRU for the PIN; receiving a registration response message from the network node indicating that the first WTRU is authorized to act as the PEMC for the PIN and provide the service; The method of claim 1 further comprising:

5. The method of claim 4 , wherein the registration response message further includes the PIN identification of the PIN.

6. based on receiving the connection request message including the PE information, sending another connection request message including the PE information to a network node; receiving another connection response message from the network node indicating that the second WTRU is authorized to act as the PE for the PIN; The method of claim 1 further comprising:

7. 7. The method of claim 6, wherein the another connection response message is determined based on the PE information of the second WTRU associated with the PIN identification of the PIN.

8. 2. The method of claim 1, wherein the first WTRU is capable of both a 3rd Generation Partnership Project (3GPP) radio access technology (RAT) and a non-3GPP RAT, and the second WTRU is capable of the non-3GPP RAT.

9. 9. The method of claim 8, wherein the 3GPP RAT includes one or more of Global System for Mobile (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), or 5G New Radio (NR), and the non-3GPP RAT includes one or more of Bluetooth, Wi-Fi, Bluetooth Low Energy (BLE), Zigbee, or Z-Wave.

10. 10. The method of claim 8, wherein the PE capabilities of the second WTRU indicate that the second WTRU supports the non-3GPP RAT.

11. a first wireless transmit / receive unit (WTRU), a receiver configured to receive, by a first WTRU authorized to act as a PIN Element (PE) with management capabilities (PEMC) in a PIN associated with a Personal Internet of Things Network (PIN) identity, from a second WTRU, a connection request message including PE information associated with the second WTRU; a transmitter configured to transmit, based on the PIN identification and the PE information, to the second WTRU, a connection response message indicating that the second WTRU is authorized to act as a PIN Element (PE) for the PIN; A first WTRU comprising:

12. The first WTRU of claim 11 , wherein the PE information includes a device identification and a PE identification.

13. 13. The first WTRU of claim 12, wherein the device type of the second WTRU includes one or more of a sensor, a light, a plug, a printer, a cellular phone, a wearable device, an augmented reality (AR) device, an in-vehicle device, or a virtual reality (VR) device.

14. 12. The first WTRU of claim 11, wherein the transmitter is further configured to send a registration request message to a network node, the registration request message including PEMC information, the PEMC information including the first WTRU's ability to act as a PEMC for the PIN and services provided by the first WTRU for the PIN, and the receiver is further configured to receive a registration response message from the network node indicating that the first WTRU is authorized to act as the PEMC for the PIN and provide the services.

15. 15. The first WTRU of claim 14, wherein the registration response message further includes the PIN identification of the PIN.

16. 12. The first WTRU of claim 11, wherein the transmitter is further configured to, based on receiving the connection request message including the PE information, send another connection request message to a network node including the PE information, and the receiver is further configured to receive another connection response message from the network node indicating that the second WTRU is authorized to act as the PE for the PIN.

Images