CN117837179A

CN117837179A - Discovery of internet of things network

Info

Publication number: CN117837179A
Application number: CN202280051964.1A
Authority: CN
Inventors: 时晓岩; T·阿巴斯; T·科加兰; 萨阿德·艾哈迈德; A·塞蒂; M·斯达斯尼克; 阿莱克·布鲁西洛夫斯基; 迪巴舍希·帕卡亚斯塔
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2021-06-25
Filing date: 2022-06-23
Publication date: 2024-04-05

Abstract

Systems, methods, and instrumentalities may be provided to discover a personal internet of things (IoT) network (PIN). Discovery policy configuration information associated with the PIN may be determined. The discovery policy configuration information may include a PIN Identification (ID) and may indicate that discovery for the PIN may be enabled. If discovery for the PIN is enabled, a first message may be sent to a second WTRU. The first message may be based on the discovery policy configuration information and may indicate the PIN ID. A second message may be received from the second WTRU. The second message may indicate the PIN ID and may indicate a request for information associated with the PIN. A third message may be sent to the second WTRU. The third message may indicate a PIN ID and may indicate the requested information that may be associated with the PIN.

Description

Discovery of internet of things network

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional application number 63/215,162 filed on 25 th 6 th 2021, U.S. provisional application number 63/276,236 filed on 5 th 11 th 2021, and U.S. provisional application number 63/338,780 filed on 5 th 2022, the contents of which are hereby incorporated by reference in their entirety.

Background

Devices that communicate using a traditional cellular network may be designed such that they have internet of things (Internet of Things, ioT) features and/or capabilities. For example, for bulk operation, these devices (e.g., ioT capable) may improve power consumption and/or may increase network efficiency.

Disclosure of Invention

Systems, methods, and instrumentalities associated with discovery of a personal internet of things (IoT) network (PIN) are described herein. In an example, a PIN element (PIN) may discover PIN information by sending a solicitation request and/or receiving a solicitation response. In an example, the PINE may be a wireless transmit/receive unit (WTRU). In an example, the PIN element may send an assist discovery request message to the PIN gateway, a PIN element with PIN management capabilities, and/or other PIN elements. In an example, the PIN element may discover other PIN group members based on a group discovery policy. The PIN gateway may discover the PIN group information and/or may provide the PIN group information to other PIN elements. The PIN element may be configured with one or more discovery limit levels. If the PIN information matches a discovery limit level configured for other PIN elements, the PIN element may provide the PIN information to the other PIN elements. In an example, a PIN element may broadcast its reachability status, which may indicate that the PIN element may be accessed directly or via a PIN Gateway (GW) or PIN relay.

The format of the pin element (pin) identity (identity) and credential information to be configured in the pin may be provided. A system (e.g., a 5G system) may be enhanced such that a PINE (PEMC) with management capabilities may authenticate and/or authorize a PINE that has been provisioned with identities and credentials. A system (e.g., 5 GC) may be able to assist in authentication and authorization procedures performed between PEMCs and pins.

When a PIN is authenticated and/or authorized by the PEMC, the PIN is able to communicate with a gateway-capable PIN (PEGC) of the PIN. The PEMC may assist the PEGC in authenticating and/or authorizing the PINE.

Systems, methods, and instrumentalities associated with discovery of a personal internet of things (IoT) network (PIN) are described herein. Discovery policy configuration information associated with a personal internet of things (IoT) network (PIN) may be determined. The discovery policy configuration information may include a PIN Identification (ID). The discovery policy configuration information may indicate that discovery for the PIN is enabled. The first message may be sent to a WTRU (e.g., another WTRU). For example, if discovery for the PIN has been enabled, a first message may be sent to the WTRU. The first message may be based on the discovery policy configuration information. The first message may indicate the PIN ID. A second message may be received from the WTRU. The second message may indicate the PIN ID and may indicate a request for information associated with the PIN. A third message may be sent to the WTRU. The third message may indicate the PIN ID and may indicate the requested information associated with the PIN.

Systems, methods, and instrumentalities associated with discovery of a personal internet of things (IoT) network (PIN) are described herein. A solicitation request message may be received from a WTRU (e.g., another WTRU). The solicitation request message may indicate a personal internet of things (PIN) Identification (ID) associated with the PIN. The solicitation request message indicates a request for information associated with the PIN. A solicitation response message may be sent to the WTRU. The solicitation-response message may indicate the PIN ID. The solicitation-response message may indicate the requested information associated with the PIN. A request message may be received from the WTRU. The second message may be based on the requested information. The request message may indicate the PIN ID. The request message may indicate a WTRU ID associated with the WTRU. The request message may indicate a request to join the PIN. For example, a response message may be received from the WTRU when the WTRU ID has been authenticated. The response message may indicate that the WTRU is authorized to join the PIN. The response message may indicate authorization information.

Drawings

Fig. 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented.

Fig. 1B is a system diagram illustrating an exemplary wireless transmit/receive unit (WTRU) that may be used within the communication system shown in fig. 1A, in accordance with an embodiment.

Fig. 1C is a system diagram illustrating an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that may be used within the communication system shown in fig. 1A, according to an embodiment.

Fig. 1D is a system diagram illustrating another exemplary RAN and another exemplary CN that may be used in the communication system shown in fig. 1A, according to an embodiment.

Fig. 2 is a diagram illustrating an exemplary home PIN.

Fig. 3 is a diagram illustrating an exemplary PIN including a wearable device.

Fig. 4 is a diagram illustrating an example of ProSe direct discovery using a first discovery model (e.g., discovery model a described herein).

Fig. 5 is a diagram illustrating an example of ProSe direct discovery using a second discovery model (e.g., discovery model B described herein).

Fig. 6 is a diagram showing an example of PIN discovery.

Fig. 7 is a diagram showing an example of PIN discovery.

Fig. 8 is a diagram showing an example of PIN element group discovery.

Fig. 9 is a diagram showing another example of PIN element group discovery.

Fig. 10 is a diagram showing an example of restricted PIN discovery.

Fig. 11 shows an exemplary procedure for Pin (PEMC) authentication and authorization with management capabilities for a pin element (pin).

Detailed Description

Fig. 1A is a diagram illustrating an exemplary 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, messages, broadcasts, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter Bank Multicarrier (FBMC), and the like.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, RANs 104/113, CNs 106/115, public Switched Telephone Networks (PSTN) 108, the internet 110, and other networks 112, although it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. As an example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a "station" and/or a "STA") may be configured to transmit and/or receive wireless signals and may include User Equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular telephones, personal Digital Assistants (PDAs), smartphones, laptop computers, netbooks, personal computers, wireless sensors, hot spot or Mi-Fi devices, internet of things (IoT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronic devices, devices operating on commercial and/or industrial wireless networks, and the like. Any one of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the internet 110, and/or the other network 112. As an example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node bs, evolved node bs (enbs), home node bs, home evolved node bs, next generation node bs (gnbs), NR node bs, site controllers, access Points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

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

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, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).

More specifically, as noted above, communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. For example, a base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interfaces 115/116/117.WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or evolved HSPA (hspa+). HSPA may include high speed Downlink (DL) packet access (HSDPA) and/or High Speed UL Packet Access (HSUPA).

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and/or LTE-advanced (LTE-a) and/or LTE-advanced Pro (LTE-a Pro) to establish the air interface 116.

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 use a new air interface (NR) to establish the air interface 116.

In embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using a Dual Connectivity (DC) principle. 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/from multiple types of base stations (e.g., enbs and gnbs).

In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., wireless fidelity (WiFi)), IEEE 802.16 (i.e., worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000 1X, CDMA EV-DO, tentative standard 2000 (IS-2000), tentative standard 95 (IS-95), tentative standard 856 (IS-856), global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN), and the like.

The base station 114B in fig. 1A may be, for example, a wireless router, home node B, home evolved node B, or access point, and may utilize any suitable RAT to facilitate wireless connections in local areas such as business, home, vehicle, campus, industrial facility, air corridor (e.g., for use by drones), road, etc. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 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 pico cell or femto cell. As shown in fig. 1A, the base station 114b may have a direct connection with the internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106/115.

The RANs 104/113 may communicate with the CNs 106/115, 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, 102 d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location based services, prepaid calls, internet connections, video distribution, etc., and/or perform advanced security functions such as user authentication. Although not shown in fig. 1A, it should be appreciated that the RANs 104/113 and/or CNs 106/115 may communicate directly or indirectly with other RANs that employ the same RAT as the RANs 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113 that may utilize NR radio technology, the CN 106/115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA, wiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.PSTN 108 may include circuit-switched telephone networks that provide Plain Old Telephone Services (POTS). The internet 110 may include a global system for interconnecting computer networks and devices using common communication protocols, such as Transmission Control Protocol (TCP), user Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP internet protocol suite. Network 112 may include wired and/or wireless communication networks owned and/or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RANs 104/113 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 radio technology, and with a base station 114b, which may employ an IEEE 802 radio technology.

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

The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) circuits, any other type of Integrated Circuit (IC), a state machine, or the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit/receive element 122. Although fig. 1B depicts the processor 118 and the transceiver 120 as separate components, it should be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

The transmit/receive element 122 may be configured to transmit signals to and receive signals from a base station (e.g., base station 114 a) 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 emit and/or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive RF and optical signals. It should be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

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

The transceiver 120 may be configured to modulate signals to be 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. For example, therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (such as NR and IEEE 802.11).

The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128, such as 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. Further, the processor 118 may access information from and store data in any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include Random Access Memory (RAM), read Only Memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 may never physically locate memory access information on the WTRU 102, such as on a server or home computer (not shown), and store the data in that memory.

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

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 in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114 b) 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 should be appreciated that the WTRU 102 may obtain location information by any suitable location determination method while remaining consistent with an embodiment.

The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software modules and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, the number of the cells to be processed, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photographs and/or video), universal Serial Bus (USB) ports, vibrating devices, television transceivers, hands-free headsets, wireless communications devices, and the like,Modules, frequency Modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and/or augmented reality (VR/AR) devices, activity trackers, and the like. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; a geographic position sensor; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and/or humidity sensors.

WTRU 102 may include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and/or simultaneous. The full duplex radio station may include an interference management unit for reducing and/or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) or downlink (e.g., for reception)).

Fig. 1C is a system diagram illustrating a RAN 104 and a CN 106, according to one embodiment. As noted above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using an E-UTRA radio technology. RAN 104 may also communicate with CN 106.

RAN 104 may include enode bs 160a, 160B, 160c, but it should be understood that RAN 104 may include any number of enode bs while remaining consistent with an embodiment. The enode bs 160a, 160B, 160c may each include one or more transceivers to communicate with the WTRUs 102a, 102B, 102c over the air interface 116. In an embodiment, the evolved node bs 160a, 160B, 160c may implement MIMO technology. Thus, the enode B160 a may use multiple antennas to transmit wireless signals to the WTRU 102a and/or to receive wireless signals from the WTRU 102a, for example.

Each of the evolved node bs 160a, 160B, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and/or DL, and the like. As shown in fig. 1C, the enode bs 160a, 160B, 160C may communicate with each other over an X2 interface.

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

The MME 162 may be connected to each of the evolved node bs 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 the user of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, and the like. MME 162 may provide control plane functionality for switching between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and/or WCDMA.

SGW 164 may connect to each of the evolved node bs 160a, 160B, 160c in RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102 c. The SGW 164 may perform other functions such as anchoring user planes during inter-enode B handover, triggering paging when DL data is available to the WTRUs 102a, 102B, 102c, managing and storing the contexts of the WTRUs 102a, 102B, 102c, etc.

The SGW 164 may be connected to a PGW 166 that may provide the WTRUs 102a, 102b, 102c with access to a packet switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network (such as the PSTN 108) to facilitate communications between the WTRUs 102a, 102b, 102c and legacy landline communication devices. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers.

Although the WTRU is depicted in fig. 1A-1D as a wireless terminal, it is contemplated that in some representative embodiments such a terminal may use a wired communication interface with a communication network (e.g., temporarily or permanently).

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

A WLAN in an infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic to and/or from the BSS. Traffic originating outside the BSS and directed to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the respective destination. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may pass the traffic to the destination STA. Traffic between STAs within a BSS may be considered and/or referred to as point-to-point traffic. Point-to-point traffic may be sent between (e.g., directly between) the source and destination STAs using Direct Link Setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunnel DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure mode of operation or similar modes of operation, the AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20MHz wide bandwidth) or a width dynamically set by signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access/collision avoidance (CSMA/CA) may be implemented, for example, in an 802.11 system. For CSMA/CA, STAs (e.g., each STA), including the AP, may listen to the primary channel. If the primary channel is listened to/detected by a particular STA and/or determined to be busy, the particular STA may backoff. One STA (e.g., only one station) may transmit at any given time in a given BSS.

High Throughput (HT) STAs may communicate using 40MHz wide channels, for example, via a combination of a primary 20MHz channel with an adjacent or non-adjacent 20MHz channel to form a 40MHz wide channel.

Very High Throughput (VHT) STAs may support channels that are 20MHz, 40MHz, 80MHz, and/or 160MHz wide. 40MHz and/or 80MHz channels may be formed by combining consecutive 20MHz channels. The 160MHz channel may be formed by combining 8 consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels (this may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data may pass through a segment parser that may split the data into two streams. An Inverse Fast Fourier Transform (IFFT) process and a time domain process may be performed on each stream separately. These streams may be mapped to two 80MHz channels and 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 a Medium Access Control (MAC).

The 802.11af and 802.11ah support modes of operation below 1 GHz. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11 ac. The 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the television white space (TVWS) spectrum, and the 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter type control/machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., supporting only) certain bandwidths and/or limited bandwidths. MTC devices may include batteries with battery lives above a threshold (e.g., to maintain very long battery lives).

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

The available frequency band for 802.11ah in the united states is 902MHz to 928MHz. In 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.

Fig. 1D is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As noted above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, 102c over an air interface 116. RAN 113 may also communicate with CN 115.

RAN 113 may include gnbs 180a, 180b, 180c, but it should be understood that RAN 113 may include any number of gnbs while remaining consistent with an embodiment. Each of the gnbs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gnbs 180a, 180b, 180c may implement MIMO technology. For example, gnbs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from gnbs 180a, 180b, 180 c. Thus, the gNB 180a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example. In an embodiment, the gnbs 180a, 180b, 180c may implement carrier aggregation techniques. 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 the unlicensed spectrum while the remaining component carriers may be on the licensed spectrum. In embodiments, the gnbs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180 c).

The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using transmissions associated with the scalable parameter sets. For example, the OFDM symbol interval and/or OFDM subcarrier interval may vary from one transmission to another, from one cell to another, and/or from one portion of the wireless transmission spectrum to another. The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using various or scalable length subframes or Transmission Time Intervals (TTIs) (e.g., including different numbers of OFDM symbols and/or continuously varying absolute time lengths).

The gnbs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in an independent configuration and/or in a non-independent configuration. In a standalone configuration, the WTRUs 102a, 102B, 102c may communicate with the gnbs 180a, 180B, 180c while also not accessing other RANs (e.g., such as the enode bs 160a, 160B, 160 c). In an independent configuration, the WTRUs 102a, 102b, 102c may use one or more of the gnbs 180a, 180b, 180c as mobility anchor points. In an independent configuration, the WTRUs 102a, 102b, 102c may use signals in unlicensed frequency bands to communicate with the gnbs 180a, 180b, 180 c. In a non-standalone configuration, the WTRUs 102a, 102B, 102c may communicate or connect with the gnbs 180a, 180B, 180c, while also communicating or connecting with other RANs (such as the enode bs 160a, 160B, 160 c). 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 enode bs 160a, 160B, 160c may serve 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, 102 c.

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 UL and/or DL, support of network slices, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and so on. As shown in fig. 1D, gnbs 180a, 180b, 180c may communicate with each other through an Xn interface.

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

AMFs 182a, 182b may be connected to one or more of gNB 180a, 180b, 180c in RAN 113 via an N2 interface and may function as a control node. For example, the AMFs 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slices (e.g., handling of different PDU sessions with different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMFs 182a, 182b may use network slices to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102 c. For example, different network slices may be established for different use cases, such as services relying on ultra high reliability low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for Machine Type Communication (MTC) access, and so on. AMF 162 may provide control plane functionality for switching between RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-a Pro, and/or non-3 GPP access technologies, such as WiFi.

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

UPFs 184a, 184b may be connected to one or more of the gnbs 180a, 180b, 180c in the RAN 113 via an N3 interface that may provide the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-host PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to 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 connect to the local Data Networks (DNs) 185a, 185b through the UPFs 184a, 184b through an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

In view of fig. 1A-1D and the corresponding descriptions of fig. 1A-1D, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more emulation devices (not shown): the WTRUs 102a-d, base stations 114a-B, evolved node bs 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMFs 182a-B, UPFs 184a-B, SMFs 183a-B, DN 185a-B, and/or any other devices described herein. The emulated device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation device may be used to test other devices and/or analog network and/or WTRU functions.

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

The one or more emulation devices can perform one or more (including all) functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the simulation device may be used in a test laboratory and/or a test scenario in a non-deployed (e.g., test) wired and/or wireless communication network in order to enable testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and/or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation device to transmit and/or receive data.

The format of the pin element (pin) identity and credential information to be configured in the pin may be provided. A system (e.g., a 5G system) may be enhanced such that a PINE (PEMC) with management capabilities may authenticate and/or authorize a PINE that has been provisioned with identities and credentials. A system (e.g., 5 GC) may be able to assist in authentication and authorization procedures performed between PEMCs and pins.

Systems, methods, and instrumentalities associated with discovery of a personal internet of things (IoT) network (PIN) are described herein. Discovery policy configuration information associated with a personal internet of things (IoT) network (PIN) may be determined. The discovery policy configuration information may include a PIN Identification (ID). The discovery policy configuration information may indicate that discovery for the PIN is enabled. The first message may be sent to a second WTRU. For example, if discovery for the PIN is enabled, a first message may be sent to the second WTRU. The first message may be based on the discovery policy configuration information. The first message may indicate the PIN ID. A second message may be received from the second WTRU. The second message may indicate the PIN ID and may indicate a request for information associated with the PIN. A third message may be sent to the second WTRU. The third message may indicate the PIN ID and may indicate the requested information associated with the PIN.

In an example, the discovery policy configuration information may include at least one of a discovery mode, PIN information, and/or the PIN ID.

In an example, the requested information may include at least one of a list of one or more devices associated with the PIN, PIN capabilities, PIN availability, PIN reachability, and/or services associated with the PIN.

In an example, the discovery policy configuration information that may be associated with the PIN may be determined by receiving a fourth message from a third WTRU. The third WTRU may be at least one of a PIN gateway, a PIN element with management capabilities (PEMC), and/or a PIN element with gateway capabilities (PEGC).

In an example, a fifth message may be sent to the second WTRU. The fifth message may indicate a request to establish a connection between the first WTRU and the second WTRU.

Systems, methods, and instrumentalities associated with discovery of a personal internet of things (IoT) network (PIN) are described herein. In an example, a first WTRU may be provided. The first WTRU may include a processor. The processor may be configured to perform one or more methods. A solicitation request message may be received from a second WTRU. The solicitation request message may indicate a personal internet of things (PIN) Identification (ID) that may be associated with the PIN. The solicitation request message indicates a request for information that may be associated with the PIN. A solicitation response message may be sent to the second WTRU. The solicitation-response message may indicate the PIN ID. The solicitation-response message may indicate the requested information that may be associated with the PIN. A request message may be received from the second WTRU. The second message may be based on the requested information. The request message may indicate the PIN ID. The request message may indicate a WTRU ID that may be associated with the second WTRU. The request message may indicate a request to join the PIN. For example, a response message may be received from the second WTRU when the WTRU ID has been authenticated. The response message may indicate that the second WTRU is authorized to join the PIN. The response message may indicate authorization information.

In an example, an announcement message may be sent to the second WTRU. The announcement message may indicate a PIN that may be associated with the PIN.

In an example, a connection request message may be received. The connection request message may indicate a request to establish a connection to the PIN based on the authorization information.

In an example, the WTRU ID may be authenticated. In an example, the WTRU ID may be authenticated using the authentication information.

In an example, it may be determined that the second WTRU may be allowed to access the service.

PIN element and PIN may be used interchangeably herein. The PIN may be a device connected to a Personal IoT Network (PIN). PIN GW and PEGC may be used interchangeably herein. PEGC can be a PINE that can be used as a gateway in a PIN. PIN management and PEMC may be used interchangeably herein. The PEMC may be a PIN that can be used as a management function in a PIN. PEGC and PIN GW may be used interchangeably herein. For example, functions that may be performed by the PEGC may be performed by the PEMC. As another example, the functions that may be performed by the PEMC may be performed by the PEGC. The device may be both PEGC and PEMC (e.g., may include features of both PEGC and PEMC as described herein). For example, the PIN GW may be PEGC and/or PEMC. As another example, the WTRU may be a PIN GW, PEGC, PEMC, combinations thereof, or the like. Devices such as a normal pin element (PINE), a gateway-capable PINE (PEGC), and/or a management-capable PINE (PEMC) may be linked to the WTRU subscription. Linking a device to a WTRU's subscription may mean that the WTRU's subscription is updated to indicate that a normal PIN may be associated with the WTRU within a PIN. For example, if the WTRU is a PEMC or PEGC, the link may indicate that the device (e.g., PIN) may operate within a PIN serviced by the PEMC or PEGC.

As described herein, a PINE may represent a normal PINE (e.g., a PINE that may not be PEGC or PEMC). As disclosed herein, a wireless transmit/receive unit (WTRU) may be and/or may include PINE, PEGC, PEMC, combinations thereof, and the like.

Multiple IoT devices (e.g., ioT capable WTRUs) may be deployed in an environment such as a private environment. IoT capable WTRUs may be organized as PINs. For example, in a home environment, security sensors, smart lights, smart plugs, printers, cellular telephones, etc. may be managed by a residential gateway and may communicate with each other. One or more of these devices (e.g., all of these devices) may constitute a PIN. Devices (e.g., each device, such as a WTRU) may be referred to as PIN elements, and different PIN elements may have different capabilities. For example, the residential gateway may be a gateway-capable PIN element (PIN GW) associated with providing a connection between PIN elements and/or a connection between a network (e.g., a 5G network) and PIN elements. The residential gateway may support (e.g., be configured to perform) one or more PIN management functions. Fig. 2 illustrates an exemplary home PIN (e.g., home automation PIN).

One or more wearable devices (e.g., portable and/or attachable devices) may form a PIN. In an example, the wearable device may be a WTRU. In such a PIN, a WTRU (e.g., another WTRU, which may be a cellular phone) may be used as a gateway-capable PIN element and/or a management-capable PIN element. One or more PIN elements, such as a smart watch, virtual Reality (VR)/Augmented Reality (AR) device (e.g., VR/AR goggles or glasses), air ds, WTRUs, etc., may communicate with each other in the PIN (e.g., and/or with other WTRUs via a 5G network). Fig. 3 shows two exemplary PINs comprising wearable devices that communicate with each other via a 5G network.

The proximity services (Proximity service, proSe) may be provided by 3GPP systems (e.g., 5G networks) based on WTRUs being in proximity to each other. The first WTRU may be configured to discover other WTRUs that may be in the vicinity of the first WTRU, for example, through a ProSe discovery procedure. There may be multiple ProSe discovery modes (e.g., two ProSe discovery modes), such as model a and model B. In model a, a WTRU (e.g., a notification WTRU) may broadcast a notification message, e.g., with a ProSe code. Such ProSe codes may be associated with, for example, an identifier informing the WTRU and/or a service provided by the informing WTRU. Other WTRUs (e.g., monitoring WTRUs) receiving the notification message may be aware that the notification WTRU is in their vicinity. In model B, a WTRU (e.g., a discoverer WTRU) may broadcast a solicitation request message, e.g., with a ProSe query code. Such ProSe query codes may be associated with an identifier of the WTRU to be discovered and/or ProSe service to be discovered. Other WTRUs, such as discoveree (WTRU), that receive the solicitation request message may respond to the request, for example, with a ProSe response code. Such ProSe response codes may be associated with identifiers of the discoveree WTRUs and/or ProSe services provided by the discoveree WTRUs. The discoverer WTRU may be aware that one or more discoveree WTRUs are in its vicinity, e.g., through features described herein.

One or more discovery modes (e.g., all discovery modes) described herein may be used to perform group discovery (e.g., discover WTRUs belonging to a particular group), WTRU-to-network relay discovery (e.g., discover WTRU-to-network relays that provide connectivity to a 5G network), and so forth. In an example (e.g., for group discovery), a discovery message (e.g., a notification message, solicitation request/response, etc.) may include a group ID. In an example (e.g., for WTRU-to-network relay discovery), a discovery message (e.g., a notification message, solicitation request/response, etc.) may use a relay service code (e.g., in place of the ProSe code described herein) to indicate WTRU-to-network relay service.

Fig. 4 illustrates an example of 5G ProSe discovery (e.g., direct discovery) using discovery pattern a described herein. Fig. 5 illustrates an example of 5G ProSe discovery (e.g., direct discovery) using discovery pattern B described herein.

The systems, methods, and instrumentalities described herein may be used to facilitate PIN discovery and/or PIN element discovery. In an example (e.g., for a home automation PIN), a visitor (guest) to home, possibly with an IoT device (e.g., a guest PIN element), and/or a guest may temporarily join the home PIN (e.g., the home automation PIN), e.g., to play a video game using the visitor's own gaming device (e.g., the guest PIN element). Prior to joining the PIN, the guest PIN element may discover the home PIN and/or one or more PIN elements in the home PIN. Proximity service discovery (e.g., based on discovery model a and/or mode B described herein) may be used to discover peer nodes. In one or more PIN environments (such as the home PIN described herein), the guest PIN element may be configured to discover available PIN information and/or PIN element information. The PIN information may include, for example, a PIN Identifier (ID), PIN topology, and/or status of the PIN (e.g., number of PIN elements in the PIN), while the PIN element information may include, for example, PIN element ID, PIN element capabilities (e.g., whether the PIN element is a gateway, administration, or relay entity), status of the PIN element (e.g., whether the PIN element is on or off), and the like.

One or more techniques described herein may be used to determine what types of PIN information and/or PIN element information to discover and/or enable discovery of such PIN and/or PIN element information.

The systems, methods, and instrumentalities described herein may be used to facilitate PIN element group discovery. In an example (e.g., to perform in-PIN communications associated with home automation and/or stream data such as voice, video, and/or game data), a PIN element may be configured to communicate with one or more other PIN elements (e.g., simultaneously), and/or may be configured to discover the other PIN elements as a single element or as a group of PIN elements prior to commencing communication. The PIN element groups may be formed relative to the applications, for example, based on the application group ID. Such application layer group IDs may be provided by an application server and/or may be preconfigured or provisioned (e.g., by a network). In an example (e.g., where a PIN is involved), the group size and/or member ID may be known (e.g., obtained) via the PIN GW. Such information may be used for multicast (groupcast) control.

Proximity-based group member discovery techniques may be used for PIN element group discovery. In an example (e.g., where a PIN environment is involved), the PIN elements may be configured to discover available PIN group information, such as PIN application group IDs, PIN group sizes (e.g., number of PIN elements in a group), PIN group IDs, and the like. For example, one or more techniques described herein may enable the discovery of PIN element group information when the PIN GW does not allow the PIN group members to directly discover each other, or when the PIN GW allows the PIN group members to directly discover each other.

Privacy issues associated with PIN discovery, PIN element discovery, and/or PIN element group discovery may be addressed. These privacy concerns may occur, for example, when a customer PIN element performs a discovery procedure with a PIN. Privacy issues may include ensuring that PIN information and/or PIN element information is not discoverable by unauthorized guest PIN elements, that security sensors are not discoverable by guest PIN elements (e.g., even if guest PIN elements are authorized to discover printers in a PIN), and so forth. One or more techniques described herein may be used to control the performance of PIN discovery and/or PIN element discovery based on privacy policies (e.g., allowing different discovery operations to be performed with respect to PIN information and/or PIN element information based on different privacy policies).

Discovery of availability and/or reachability of PIN elements may be provided. In an example, if the guest PIN element performs a discovery procedure to discover the PIN element, the guest PIN may be interested in availability and/or accessibility of the PIN element. For example, a customer PIN may be interested in a window of time that a PIN element may be accessed, and/or may be interested in a data path that a PIN element may be accessed. A provision may be made to enable the guest PIN element to discover the availability and/or reachability of the PIN element.

Authentication and authorization of the PINE may be provided. The PINE may be preconfigured and/or logged in (on-board) with credentials and/or identities (e.g., PINE ID). The credentials and/or pin ID may be provisioned on a server, network function, and/or repository controlled by a Mobile Network Operator (MNO). The PIN may be placed near the PEMC that manages the PIN. The PINE may be turned on and PEMC may be discovered and a PINE authentication and authorization procedure may be initiated. The PEMC may determine whether the PIN is authenticated and/or whether the PIN is authorized to join the PIN. Once the PIN joins the PIN, the PIN may establish communication with the PEGC and may communicate with other devices within the PIN.

The PEMC and PEGC may be one or more WTRUs. For communication between PINE and PEMC or PEGC, PC5 may be used. In an example, other interfaces between PINE and PEMC, PEGC and/or PIN GW may be used. Communication between the PINE and PEMC, PEGC and/or PIN GW may be carried by protocols such as bluetooth or WiFi (e.g., non-3 GPP protocols). In an example, security may be provided by the PIN application layer and may not be provided by bluetooth and/or WiFi (e.g., confidentiality, integrity, and/or replay protection).

The format of the PINA identity and/or credential information to be configured (e.g., may need to be configured) in the PINA may be provided. The system (e.g., a 5G system) may be enhanced such that the PEMC may authenticate and/or authorize a pin that has been provisioned with an identity and/or credential. A system (e.g., 5 GC) may be able to assist in authentication and/or authorization procedures performed between PEMCs and pins.

If the PEMC authenticates the PEMC authentication and authorization, the PINE is able to communicate with the PEGC of the PIN. The PEMC may assist the PEGC in authenticating and/or authorizing the PINE.

Examples described herein may be used in a customer premises network (customer premises network). The PIN GW (which may be PEMC and/or PEGC) may be replaced by an evolved residential gateway, and the customer PIN element/PIN element may be replaced by the WTRU.

In an example, a PIN element (e.g., a PIN GW or a PIN element with management capabilities) may send (e.g., broadcast) a notification message, which may include an identifier of the PIN. The guest PIN element may discover the PIN in response to receiving the notification message. The guest PIN element may decide to discover information about the PIN (e.g., additional information) and may send a request (e.g., solicit request) to one or more other PIN elements in the PIN. The request may include information such as a PIN identifier and/or other PIN information to be discovered. Such PIN information may indicate, for example, one or more PIN elements with capabilities (e.g., particular capabilities), PIN topology, one or more PIN services, and so forth. The PIN element matching the PIN information included in the request may send a response (e.g., solicit a response) with the PIN information requested by the guest PIN element, for example. For example, if the guest PIN element decides to discover a PIN element with relay capability, the guest PIN element may include a relay capability indication in the PIN information to be discovered. In an example, if the guest PIN element decides to discover a PIN element that provides a PIN service (e.g., a particular PIN service), the guest PIN element may include a PIN service description and/or service ID in the PIN information to be discovered.

The PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may configure one or more PIN discovery policies for other PIN elements. The one or more PIN discovery policies may include an indication of whether discovery is enabled or disabled, an indication of a discovery mode, an indication of a PIN identifier, and the like. The PIN element may perform a discovery procedure based on one or more PIN discovery policies. Different PIN elements may be configured with different PIN discovery policies.

The notification messages described herein may be broadcast by one or more PIN elements (e.g., all PIN elements) of the PIN, or may be broadcast by the PIN GW or PIN elements with administrative capabilities based on a discovery policy.

The notification, solicitation request, and/or solicitation response messages described herein may include a PIN element identifier and/or a guest PIN element identifier.

The guest PIN element may be configured with one or more of the following actions. The guest PIN element may receive a notification message, which may include a PIN identifier. The guest PIN element may decide to discover PIN information for the PIN based on a local policy. The guest PIN element may send a solicitation request that may include a PIN identifier and/or PIN information to be discovered. The guest PIN element may receive a solicitation response that may include a PIN identifier and/or PIN information to be discovered.

The PIN element may be configured with one or more of the following actions. The PIN element may receive discovery policy configuration information that may indicate whether discovery is enabled or disabled, a discovery mode to be used, a PIN identifier to be used (e.g., in a discovery message), and so on. The PIN element may broadcast a notification message, for example, based on a discovery policy. The PIN element may receive the solicitation request and/or may determine whether the PIN element matches the PIN information included in the solicitation request. The PIN element may send a solicitation response with the PIN information requested by the solicitation request message.

The PIN GW (e.g., PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) may be configured with one or more of the following actions. The PIN GW may send discovery policy configuration information that may indicate whether discovery is enabled or disabled, a discovery mode to be used, a PIN identifier to be used (e.g., in a discovery message), and so on. The PIN GW may broadcast a notification message, e.g., based on the discovery policy. The PIN GW may receive the solicitation request and/or may determine whether the PIN element matches PIN information to be discovered (e.g., the PIN information included in the solicitation request). The PIN GW may transmit a solicitation response with the PIN information requested by the solicitation request message.

Fig. 6 illustrates an exemplary PIN discovery procedure. At 1, a PIN GW (e.g., or PIN elements with PIN management capabilities) may send discovery policy configuration information to one or more PIN elements (e.g., different PIN elements may be configured with different discovery policies). The configuration information may indicate whether discovery is enabled or disabled, a discovery mode to be used, a PIN identifier to be used (e.g., in a discovery message), and so on. At 2, the PIN GW may broadcast a notification message, which may include a PIN identifier. At 3 (e.g., after the PIN is found), the guest PIN element may decide to find PIN information associated with the PIN. At 4, the customer PIN element may send a solicitation request, which may include a PIN identifier and/or PIN information to be discovered. At 5, the PIN element that matches the PIN information to be discovered may send a solicitation response, e.g., with the PIN information requested by the guest PIN element.

In an example, discovery model a described herein (e.g., discovery model a alone) may be used for PIN discovery. The PIN element may broadcast a notification message that may include a PIN identifier and/or other PIN information, such as the capabilities of the PIN element, PIN topology, PIN services provided by the PIN element, and the like. The guest PIN element may monitor for notification messages. A PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may configure PIN discovery policies for one or more of the PIN elements (e.g., different PIN elements may be configured with different discovery policies). The notification message may be broadcast by one or more of the PIN elements (e.g., all PIN elements) or by the PIN GW (e.g., PIN elements with administrative capabilities, PEMC, PEGC, and/or combinations thereof), e.g., based on a discovery policy. In an example, the notification message may include a PIN element identifier. In an example, the PIN element may be configured with one or more of the following actions. The PIN elements may receive discovery policy configuration information (e.g., different PIN elements may be configured with different discovery policies) that may indicate whether discovery is enabled or disabled, a discovery mode to be used, a PIN identifier to be used (e.g., in a discovery message), and so forth. The PIN element may broadcast a notification message based on the discovery policy. The notification message may include PIN information.

In an example, discovery model B described herein (e.g., discovery model B alone) may be used for PIN discovery. The guest PIN element may send a solicitation request that may include a PIN identifier. The PIN element receiving the solicitation request may send a solicitation response, which may include a PIN identifier and/or other PIN information. A PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may configure PIN discovery policies for one or more of the PIN elements (e.g., different PIN elements may be configured with different discovery policies). The PIN element may decide to respond to the solicitation request based on the discovery policy. The solicitation request and/or response message may include a PIN element identifier and/or a guest PIN element identifier. The PIN element may be configured with one or more of the following actions. The PIN element may receive discovery policy configuration information (e.g., different PIN elements may receive different discovery policy configuration information) that may indicate whether discovery is enabled or disabled, a discovery mode to be used, a PIN identifier to be used in a discovery message, and so on. The PIN element may receive a solicitation request (e.g., which may include PIN information to be discovered) and may determine whether the PIN element matches the PIN information to be discovered. The PIN element may send a solicitation response with PIN information.

In an example, a PIN element (e.g., a PIN GW, a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may broadcast a notification message that may include an ID and/or information of the PIN that the PIN element is not discoverable without authorization or is discoverable via the PIN GW (e.g., discoverable via communication with the PIN GW). The customer PIN element may discover the PIN GW, for example, after receiving the notification message. The guest PIN element may be allowed (e.g., may be allowed only) to communicate with the PIN GW. Other PIN elements may be configured with a discovery policy by the PIN GW such that they are disabled from being discovered directly via the guest PIN element. The customer PIN element may send a solicitation request to the PIN GW, which may include, for example, a PIN ID of the PIN GW and/or PIN information to be discovered (e.g., PIN element with specific capabilities, PIN topology, PIN service, etc.).

The PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may collect the requested PIN information, e.g., via communication with the PIN element within the PIN (e.g., via solicitation request/response). In an example, if the PIN GW has collected information, it may send a solicitation response back to the guest PIN element. The PIN GW may enable discovery of the corresponding PIN element so that it may be discovered by the guest PIN.

The behavior of the guest PIN element may include one or more of the following: receiving a notification message including a PIN ID; determining PIN information for discovering the PIN based on the local policy; transmitting a solicitation request, wherein the solicitation request comprises a PIN ID and/or PIN information to be discovered; or receiving a solicitation response comprising the PIN ID and/or PIN information to be found.

The behavior of the PIN element may include one or more of the following: receiving a discovery policy configuration including enabling or disabling discovery, discovery mode, PIN ID used in discovery messages, and the like; receiving a solicitation request and determining whether the PIN element matches PIN information and/or PIN ID to be found; or send a solicitation response with the PIN information requested by the solicitation request message.

The PIN GW behavior (which may be a PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) may include one or more of the following behaviors: transmitting a discovery policy configuration including enabling or disabling discovery, discovery mode, PIN ID used in discovery message, etc.; broadcasting a notification message based on the discovery policy; receiving a solicitation request and determining whether the PIN element matches PIN information to be discovered; or send a solicitation response with PIN information.

Fig. 7 is a diagram showing an example of PIN discovery. The PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) may send a discovery policy configuration to the PIN element, e.g., the discovery policy configuration may disable discovery of the PIN element by the guest PIN element. The PIN GW may broadcast a notification message that may include the PIN ID of the PIN GW and an indication that PIN discovery is not allowed without authorization or via PIN GW discovery only. After the PIN GW is discovered, the customer PIN element may decide to discover PIN information. The guest PIN element may send a solicitation request that may include the PIN ID and/or PIN information to be discovered. The PIN GW may discover the requested PIN information from the customer PINs within the PIN via solicitation requests and/or responses. The PIN GW may respond to the customer PIN with the PIN ID of the target PIN element and PIN information. The PIN GW may enable discovery of the target PIN element, e.g., so that it may be discovered by the guest PIN. The guest PIN may have information (e.g., all required information) for discovering the target PIN element, and may follow a discovery procedure (e.g., as described herein).

The PIN elements may be configured to discover PIN element groups. Such a PIN element group may be formed by an application (e.g., an application layer of one or more PIN elements) and/or may be preconfigured or provisioned by a network. In the latter case, the group size and/or the members of the group (e.g., member IDs) may be known (e.g., configured by the network). The PIN element may be configured to perform group discovery in a variety of ways (e.g., two ways). For example, the PIN element may send an assistance request to the PIN GW to discover one or more group members, e.g., if the PIN GW does not allow (e.g., based on a configured policy) the PIN element to discover other group members directly, whether they are nearby or remote. For example, if the direct discovery of group members is not limited by the PIN GW, the PIN element may send a group member discovery solicitation message.

Fig. 8 shows an example of the PIN element group being found when direct discovery of the PIN element is not allowed. As shown, a set of 4 PIN elements may be associated with a PIN GW (e.g., PIN elements with administrative capabilities, PEMC, PEGC, and/or combinations thereof). One of the PIN elements may be interested in discovering other group members for multicast communications. The PIN GW may not allow (e.g., based on configured policies) PIN group members to directly discover each other. In such cases, the PIN element may be configured with one or more of the following actions. The PIN element may receive a group discovery policy configuration that may indicate whether direct (e.g., or indirect) group discovery is enabled or disabled, discovery mode to be used, PIN identifier, PIN group identifier, PIN application identifier (e.g., application ID associated with PIN group), group size, etc. In an example (e.g., for indirect discovery), the PIN element may send an assist discovery request message to a PIN GW (e.g., a PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) to discover group members, e.g., based on a group discovery policy. The PIN element may receive a solicitation request including PIN group information (e.g., to be discovered) and may determine whether the PIN element matches the PIN group information to be discovered. The PIN element may send a solicitation response, which may include PIN group information. The PIN element may receive a group discovery notification message, which may include PIN group information. In an example (e.g., for indirect discovery), the PIN element may receive an assisted discovery response message with group information from a PIN GW (e.g., or a PIN element with management capabilities).

The PIN GW may be configured with one or more of the following actions. The PIN GW may send group discovery policy configuration information that may indicate whether direct (e.g., or indirect) group discovery is enabled or disabled, discovery mode to be used, PIN identifier to be used, PIN group identifier to be used, PIN application identifier (e.g., application ID associated with PIN group), group size, etc. The PIN GW may send a group discovery solicitation request and/or may determine whether the PIN element matches PIN group information to be discovered. The PIN GW may receive a group discovery solicitation response, which may include PIN group information. The PIN GW may receive a group member discovery assistance request message from the PIN element, which may include PIN group information. The PIN GW may send an assistance response message to the PIN element and may include PIN group information and/or group member ID in the response.

As shown in fig. 7, at 1, the PIN GW may send group discovery policy configuration information to one or more PIN elements (e.g., all PIN elements). The configuration information may include an indication of whether the discovery member is enabled or disabled, a discovery mode to be used, a PIN identifier, a PIN group identifier, a PIN application identifier (e.g., an application ID associated with the PIN group), a group size, etc., directly (e.g., or indirectly) discovered. At 2, PIN element 1, which may be interested in discovering other group members, may send an assistance message to the PIN GW. The assistance message may include, for example, PIN group information (e.g., PIN group information being discovered). At 3 (e.g., after receiving the assistance request), the PIN GW may broadcast a discovery solicitation request message. At 4, one or more PIN elements may receive a discovery solicitation message, which may include PIN group information. A PIN element attempting to find matching PIN group information may send a solicitation response to the PIN GW, which may include matching PIN group information. At 5, the PIN GW may send a discovery assistance response to PIN element 1 confirming the presence of PIN group members.

Fig. 9 shows an example of a PIN element group being discovered when it is permissible to directly discover PIN elements. As shown, a set of 4 PIN elements may be associated with a PIN GW (e.g., PIN elements with administrative capabilities, PEMC, PEGC, and/or combinations thereof). One or more of the PIN elements may be of interest to discover other group members, e.g., for multicast communications. For example, if the PIN group members may be close enough to send discovery messages to each other or receive discovery messages from each other, policies may be preconfigured to allow the PIN group members to discover each other. The PIN GW may assist in this discovery if a group member (e.g., any of the group members) is not directly reachable.

The PIN element may be configured with one or more of the following actions. The PIN element may receive group discovery policy configuration information, which may include an indication of whether direct (e.g., or indirect) group discovery is enabled or disabled, a discovery mode to be used, a PIN identifier, a PIN group identifier, a PIN application identifier (e.g., an application ID associated with a PIN group), a group size, and the like. In an example (e.g., for direct discovery), the PIN element may broadcast a group discovery solicitation message based on a group discovery policy. The PIN element may send and/or receive a solicitation request, which may include PIN group information (e.g., PIN group information being discovered) and may determine whether the PIN element matches the PIN information being discovered. The PIN element may send and/or receive a solicitation response with PIN group information. The PIN element may receive a group discovery notification message with PIN group information. The PIN element may receive an assist discovery response message, for example, from the PIN GW. The auxiliary discovery response message may include PIN group information and/or group members that may or may not be directly discovered by the discoverer PIN element.

The PIN GW may be configured with one or more of the following actions. The PIN GW may send group discovery policy configuration information that may include an indication of whether direct (e.g., or indirect) group discovery is enabled or disabled, a discovery mode, a PIN identifier, a PIN group identifier, a PIN application ID (e.g., an application ID associated with a PIN group), a group size, and the like. The PIN GW may broadcast a group discovery notification message, e.g., based on a discovery policy. The PIN GW may receive the solicitation request and may determine whether the PIN element matches the PIN group information being discovered. The PIN GW may send a solicitation response, which may include PIN group information. The PIN GW may receive an assistance request message from the PIN element, which may include PIN group information. The PIN GW may send an assistance response message with PIN group information and/or group member identifier to the PIN element.

As shown in fig. 9, at 1, a PIN GW (e.g., a PIN element with management capabilities, PEMC, PEGC, and/or a combination thereof) may send group discovery policy configuration information to one or more PIN elements (e.g., all PIN elements). The configuration information may include an indication of whether group discovery is enabled or disabled, a discovery mode to be used, a PIN identifier, a PIN group identifier, a PIN application identifier (e.g., an application ID associated with a PIN group), a group size, and the like. At 2, a PIN element (e.g., a finder PIN element) that is interested in finding a PIN element group (e.g., providing a particular service or having a particular group ID) may broadcast a group discovery solicitation message. The request message may include a group ID and/or an application ID (e.g., an application ID associated with the PIN group). At 3 (e.g., after receiving a solicitation request from the discoverer PIN element), the discoveree PIN elements belonging to the group may respond with a solicitation response. The response may include information associated with the PIN group. At 4, the finder PIN element (e.g., PIN element 1) may decide that it did not receive a response from one or more group members (e.g., all group members) of the PIN group. In response, the discoverer PIN element may send a member discovery assistance message to the PIN GW at 5. The assistance message may include, for example, PIN group information and/or the number of missing members. At 6, the PIN GW may broadcast a discovery notification message. At 7, one or more of the PIN elements that were not earlier responsive to the solicitation request message from PIN element 1 may send a discovery solicitation request message to the PIN GW. At 8, the PIN GW may respond to the solicitation request message with detailed PIN group information. At 9, the PIN GW may send a discovery assistance response to the discoverer PIN element (e.g., PIN element 1 in this case), confirming the presence of the PIN group members.

Restrictions may be imposed on PIN discovery and/or PIN element discovery. In an example, one or more PIN elements (e.g., all PIN elements) may be configured with a discovery policy, which may specify one or more discovery limit levels. The customer PIN element that decides to discover PIN information may, for example, retrieve the discovery policy of the PIN from the PIN GW (e.g., or other PIN element with PIN management capabilities). The guest PIN element may send a solicitation request that may include a PIN identifier and/or a discovery limit level. The PIN element receiving the solicitation request may determine (e.g., check) whether the guest PIN element is authorized to discover PIN information based on the discovery limit level and/or one or more corresponding security parameters. The PIN element may send a solicitation response with a PIN identifier and/or other PIN information.

The discovery limit level may be configured with a set (e.g., corresponding set) of security parameters. The token may be generated based on one or more security parameters associated with the security level and/or may be sent with the discovery limit level. The token and/or the receiver of the discovery limit level may check whether the discovery limit level is misused in the discovery message, for example, by checking the token based on the corresponding security parameters.

In an example, instead of sending a solicitation response after receiving a solicitation request, the PIN element may broadcast a notification message, which may include a discovery limit level.

The customer PIN element may establish a secure connection with a PIN GW (e.g., a PIN element with administrative capabilities, PEMC, PEGC, and/or combinations thereof) and then receive discovery policy configuration information from the PIN GW.

The discovery limit level may be defined as low, medium, or high, and/or as client level, regular level, full access level, etc. The discovery limit level may include a time window for indicating when the discovery limit level is available.

The discovery limit level may be configured by a PIN element. For example, PIN element a may be configured with a high discovery limit level and PIN element B may be configured with a low discovery limit level.

The discovery limit level may be configured with PIN information. For example, PIN element a may be configured with a high discovery limit level associated with the status of PIN element a and a low discovery limit level associated with the ID of PIN element a. The discovery limit level may be configured as a PIN service. A high discovery limit level may be configured for a first service and a low discovery limit level may be configured for a second service.

The guest PIN element configured with the discovery limit level may discover (e.g., discover only) PIN information corresponding to the configured discovery limit level. For example, a PIN element configured with a high discovery limit level may not respond to solicitation requests from a guest PIN element configured with a low discovery limit level. If the corresponding solicitation request is from a customer PIN element configured with a low discovery limit level, the PIN element may include (e.g., include only) PIN information associated with the low discovery limit level in the solicitation response.

The guest PIN element may be configured with one or more of the following actions. The guest PIN element may receive discovery policy configuration information that may include one or more discovery limit levels and/or security parameters corresponding to the discovery limit levels. The guest PIN element may decide to discover PIN information for the PIN based on a local policy. The guest PIN element may send a solicitation request that may include one or more discovery limit levels and/or tokens generated based on security parameters associated with the discovery limit levels. The solicitation request may include a PIN identifier and/or PIN information to be discovered. The guest PIN element may receive a solicitation response that may include the discovered PIN identifier and/or PIN information.

The PIN element may be configured with one or more of the following actions. The PIN element may receive discovery policy configuration information that may include one or more discovery limit levels and/or security parameters associated with the discovery limit levels. The PIN element may receive the solicitation request and determine a discovery limit level for the guest PIN element. The PIN element may determine whether the guest PIN element is authorized for its discovery limit level, for example, by examining a token associated with the discovery limit level (e.g., a security parameter associated with the limit level). The PIN element may send a solicitation response that may include PIN information that matches the discovery limit level of the guest PIN element.

The PIN GW (e.g., PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) may be configured with one or more of the following actions. The PIN GW may send discovery policy configuration information to one or more PIN elements. The discovery policy configuration information may include one or more discovery limit levels and/or security parameters associated with the limit levels. The PIN GW may receive a solicitation request, for example, from a guest PIN element, and may determine a discovery limit level for the guest PIN element. The PIN GW may determine whether the guest PIN element is authorized for its discovery limit level, for example, by examining a token associated with the discovery limit level (e.g., a security parameter associated with the limit level). The PIN GW element may send a solicitation response that may include PIN information that matches the discovery limit level of the guest PIN element.

Fig. 10 shows an example of restricted PIN discovery. At 1, a PIN GW (e.g., a PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) may send discovery policy configuration information to one or more PIN elements. The discovery policy configuration information may include one or more discovery limit levels and/or security parameters associated with the discovery limit levels. At 2, PIN discovery may be performed, for example, in accordance with one or more examples described herein. At 3, the customer PIN element may establish a secure connection with the PIN GW (e.g., the customer PIN element may join a PIN associated with the PIN GW). At 4, the PIN GW may send discovery policy configuration information to the customer PIN element. The discovery policy configuration information may include one or more discovery limit levels and/or security parameters associated with the discovery limit levels. At 5, the guest PIN element may send a solicitation request that may include one or more discovery limit levels configured for the guest PIN element and/or a token generated based on security parameters associated with the discovery limit levels. The solicitation request may include a PIN identifier and/or other PIN information to be discovered. At 6, the PIN element may determine those discovery limit levels of the guest PIN element and/or whether the guest PIN element is authorized for its discovery limit level, for example, by examining a token associated with the discovery limit level. At 7, the PIN element may send a solicitation response with PIN information matching the discovery limit level of the guest PIN element.

Discovery of availability and/or reachability of PIN elements may be provided. Examples described herein may show how a guest PIN element is enabled to discover the availability and/or reachability of the PIN element.

In an example, a PIN element (e.g., a PIN element with management capabilities, PEMC, PEGC, and/or a combination thereof) may broadcast, multicast, or multicast a notification message, which may include reachability status. The PIN element reachability status may indicate whether the PIN element may be directly accessed, e.g., via a PIN GW or PIN relay, or via a core network.

In an example, instead of broadcasting, multicasting or multicasting a notification message, the PIN element may send a solicitation response with reachability status after receiving a solicitation request from the client PIN element.

Reachability status may include QoS information and/or security information when the PIN element is accessed directly, e.g., via a PIN GW or PIN relay, or via a core network.

When the PIN element is accessible via the PIN GW (e.g., via PIN relay) or via the core network, the reachability status may include the ID of the PIN GW, the ID of the PIN relay, or the PLMN ID.

Reachability status may include IP address, MAC address, and/or Protocol Data Unit (PDU) session ID, which may be used for access via PIN GW, PIN relay, or via the core network.

If the reachability status is available for a service (e.g., a particular service), such as a printer service accessible via a PIN GW, the reachability status may include a service ID.

In an example, if the client WTRU is acting as a PIN GW, the client WTRU may indicate whether a connection with the core network is available.

After discovering the reachability status of the PIN element, the client WTRU may select a communication path to communicate with the PIN element, e.g., via a PIN GW, PIN relay, or via a core network.

In an example, when a client WTRU communicates with a PIN element, the client WTRU may communicate using an IP address, MAC address, or PDU session ID in the reachability status of the PIN element.

The behavior of the guest PIN element may include one or more of the following: sending a solicitation request; receiving a reachability status of the PIN element in the solicitation response; based on the reachability status, a communication path is selected, e.g., via a PIN GW, via PIN relay, or via a core network; establishing a communication path based on the received ID of the PIN GW, the ID of the PIN relay, or the PLMN ID; or communicate with the PIN element by using an IP address, MAC address, or PDU session ID based on the received reachability status.

The behavior of the PIN element may include one or more of the following: a solicitation request is received or its reachability status is broadcast via a solicitation response.

Availability discovery may be provided. Examples described herein may show how a guest PIN element is enabled to discover the availability and/or reachability of the PIN element.

In an example, a PIN element (e.g., a PIN GW, a PIN element with management capabilities, PEMC, PEGC, and/or combinations thereof) may broadcast a notification message, which may include availability status. The PIN element availability status may indicate in which time window the PIN element is accessible.

The PIN element may send a solicitation response with an availability status after receiving a solicitation request from the guest PIN element. The availability status may include a service ID. The availability status may include location information that may indicate in which region the PIN element is available for access.

The behavior of the guest PIN element may include one or more of the following: sending a solicitation request; receiving availability status of the PIN element in the solicitation response; determining whether the PIN element is available in the current time window and the current location; or communicate with the PIN element.

The behavior of the PIN element may include one or more of the following: a solicitation request is received or its availability status is broadcast in a solicitation response.

Authentication and/or authorization of the PINE may be provided. Procedures may be provided as to how the WTRU may discover devices in the PIN (such as PIN GW, PEMC, and/or PEGC), connect to these devices, and/or perform authentication and/or authorization procedures with these devices. The program may use the boot identifier and/or alias to enable information exchange (e.g., secure exchange) and/or to allow authentication and/or authorization procedures to be performed.

A pin identity format may be provided. The pin ID format may include a plurality of fields. The first field in the PINE ID may be a value that can be parsed into an MNO ID. The format of this field may be a Mobile Country Code (MCC) and/or a Mobile Network Code (MNC). The second field in the PINE ID may be a value that may be parsed into a network function that may be contacted to perform authentication and/or authorization procedures with the PINE. For example, the network function may be an authentication, authorization and accounting (AAA) server, an AAA proxy, an authentication server function (AUSF), or a Unified Data Management (UDM). In an example, the first field may be used to determine a network function that may be contacted to perform authentication and/or authorization procedures for the PINE. In an example, this field may be parsed into network functions that may be queried to obtain a PIN ID and/or a PINID. The third field in the PINE ID may be a value that may be parsed into a subscription identifier linked to the PINE. The subscription may identify a PEMC or PINE having gateway capabilities (e.g., PIN elements having administrative capabilities, PEMC, PEGC, and/or combinations thereof). The fourth field in the pin ID may be a value that may be parsed into a device identifier. The fifth field in the PINE ID may be a value that can be parsed into a service provider ID.

The use of routing information in an identity may present a situation based on privacy and/or unlinkability considerations. For example, from a security and/or privacy perspective (e.g., perspective), the pin ID pseudonym and/or alias may be features.

The pin ID may be associated with a pin ID alias. The pin ID alias may be an indistinguishable ID that may be resolved into a pin ID. If the PINE ID is supplied in PINE, PEMC or PEGC, the PINE ID alias can be supplied. The PINE ID may be used in message exchanges and/or broadcast messages to avoid broadcasting or making visible the PINE ID and/or information included therein. Such PINE ID pseudonyms and/or aliases may have to be changed frequently in order to avoid linkable.

PIN guide information may be provided. In addition to the PIN ID and the PIN ID alias, the PIN may be configured with PIN guide information.

The PIN guide information may include one or more credentials. The credentials (e.g., each credential) may be a value associated with the pin ID and used to authenticate the pin and/or an authentication and/or non-authentication token (e.g., ticket). The credentials (e.g., each credential) may be associated with a PIN ID, PEMC ID, and/or PEGC ID. If the credential is associated with a PIN ID, PEMC ID, or PEGC ID, the PINE can be aware of using the credential to communicate, authenticate, and/or authorize (e.g., for communication, authentication, and/or authorization only) with PEMC or PEGC (a particular PEMC or PEGC) within the PIN. The credentials may be keys, identities, and/or certificates.

The PIN guide information may include a PIN ID alias. The PIN ID alias may be a value used by PINE to discover PIN, PEMC, and/or PEGC. For example, the PIN ID alias may be a value broadcast by the PIN, PEMC, and/or PEGC to allow the PIN to discover other PINs, PEMCs, and/or PEGCs. The PIN ID alias may allow other PINs, PEMCs, and/or PEGCs to avoid broadcasting PIN IDs. The pin ID alias may be a Uniform Resource Identifier (URI) that may be parsed into a real pin ID, or may be a URI ID (e.g., an index) that points to a URI that may be parsed into a real pin ID.

PIN guide information for PINs may be used for procedures (e.g., discovery, authentication, and/or authorization) between PINs and PEMCs or PEGCs, and PEMCs or PEGCs may obtain (e.g., need to obtain) PIN guide information for PINs, or at least a subset of PIN guide information for PINs. The PEMC or PEGC may obtain PIN guide information of the PIN before or during performing an authentication procedure with the PIN. PIN guide information for the PIN may be obtained from the AAA server via NAS signaling from a system (e.g., 5 GC) or via user plane interactions. The obtained PIN guide information may be used to authenticate and/or authorize the PIN. The AAA server described herein may be a PIN server.

In an example, the PEMC may be used as a log-in PEMC that may provide connectivity for the PIN and assist in provisioning PIN guidance information from a system (e.g., 5 GC) via NAS signaling (e.g., control plane) or from an application server via user plane interactions. The PEMC may broadcast a generic discovery code and/or a routable address (e.g., IP address). The PINE may listen to a broadcast message with a generic discovery code. When the PEMC is found, the PIN may connect with the PEMC for logging in and/or provisioning PIN guide information. After the PIN guide information has been provisioned (e.g., successfully provisioned), the PIN may be disconnected from the logged PEMC and the provisioned PIN guide information used for subsequent procedures (e.g., discovery, authentication, and/or authorization) between the PIN and the PEMC or PEGC.

PEMC authorization and/or authentication of PINE may be provided.

Fig. 11 shows an exemplary procedure for PEMC authentication and authorization of PINE. The PIN may be provisioned, guided and/or configured with PIN guide information. The PINE may receive one or more of the following from the server: PIN ID, PIN ID alias, or PIN guide information. For example, an application on the PINE, such as an application client or a PIN enabler (enabler) client, may receive PIN guidance information from a PIN enabler server. The PIN may be configured with PIN guide information during the manufacturing process via a user interface such as a Graphical User Interface (GUI). If the PIN is a WTRU, the PIN may receive PIN guide information from the system (e.g., 5 GC) via NAS messages during authentication and authorization procedures with the system (e.g., 5 GC). If the PIN is a WTRU, the PIN may derive the PIN ID, PIN ID alias, and/or credential using PIN guide information received from the system (e.g., 5 GC) via NAS messages during authentication and/or authorization procedures with the system (e.g., 5 GC). For example, the PIN may use a key that may have been included in the PIN guide information to derive the PIN ID, PIN alias, and/or credential. A pin as a WTRU may use access authentication to direct its application credentials using one or more of the following: generic Bootstrapping Architecture (GBA), authentication and Key Management of Applications (AKMA) or 5G GBA.

The PEMC may receive information about the PIN that is allowed to join the PIN. The information may include PIN guide information, PIN ID alias, and/or a subset of PIN guide information for the PIN. The PEMC may receive PIN guide information of the PIN via a NAS message such as a WTRU configuration update message. When the subscription of the PEMC is updated to indicate that the PIN may join a PIN managed by the PEMC, the network may determine to send a WTRU configuration update message to the WTRU (e.g., the PEMC). When the pin links to the PEMC's subscription, a WTRU configuration update message may be sent to the PEMC. The PEMC may receive PIN guide information of the PIN via a NAS message such as a PDU session establishment accept message or a PDU session modify command. The network may determine to send a PDU session establishment accept message or PDU session modification command to the WTRU (e.g., PEMC) when the subscription of the PEMC is updated to indicate that the PEB may join a PEMC-managed PIN, or when the subscription of the WTRU is updated to indicate that traffic from the PEB may be routed to or from a DNN/S-NNSAI combination used by the PDU session. When a PDU links to session management information associated with a DNN/S-NSSAI combination in a subscription of a PEMC, a PDU session establishment acceptance message or PDU session modification command may be sent to the PEMC. PIN guide information for the PIN may be received by a PIN enabler client hosted on the WTRU. The PIN enabler user side may receive PIN guidance information of the PIN from the PIN enabler server in the form of an HTTP message (e.g., user plane). For example, the PIN enabler server may store PIN guidance information of the PIN, and may determine to transmit the information to the PIN enabler user side when the PIN is linked to a subscription of the PEMC or when the PIN enabler server receives a notification of the PIN linked to the subscription of the PEMC.

PINE can discover PEMC or PIN and can determine to join a PIN managed by PEMC. PIN and PEMC may use PIN guide information of PIN in a discovery procedure. For example, PIN guidance information for PIN may include discovery values that may be broadcast by PEMC. The PEMC may broadcast a message that includes the discovery value and/or a routable address (e.g., IP address). When the PIN receives the broadcast message, the PIN may check whether the discovery value is associated with PIN guidance information stored in the PIN. For example, the PINE may check whether the discovery value is in PIN guide information or whether the result of calculation performed on the discovery value matches information stored in PIN guide information of the PINE. For example, the PINE may perform a hash operation on the received discovery value and the identifier of the PINE and check whether it matches the value in the PIN guide information. If the PINE determines that a discovery value is associated with PINE's PIN guidance information, the PINE can consider that PEMC has been discovered and proceed with the techniques described herein.

As described herein, the PIN may use PIN ID aliases to discover PINs. For example, the PINE may discover and select the PEMC that is broadcasting the PIN ID alias, or the PINE may broadcast a request for the PEMC to broadcast the PIN ID alias. The discovery value may be a PIN ID alias.

The PIN may use the received routable address (e.g., as described herein) to send a join request to the PEMC to join the PIN and begin an authentication and/or authorization procedure. The join request (e.g., all or part of the join request) may use security material as part of the PINE guide information for confidentiality, integrity, and/or replay protection. The join request may include a PINE ID or a PINE ID alias. The join request may include an unencrypted portion. The unencrypted portion may include a discovery value (e.g., an observed discovery value) that is received by the PINE and triggers the PINE to send a join request. For example, the discovery of values may be specific to one or more pins, and the PEMC may use the received discovery values to determine what pin bootstrapping information is available to decrypt the join request. The PEMC may use the received discovery value to determine what pin sent the request.

The receipt of the join request by the PEMC may trigger the PEMC to obtain information (e.g., necessary information) to authenticate and/or authorize the pin. The PEMC may have no information (e.g., necessary information) to authenticate and/or authorize the pin. For example, it may be that the PEMC has not received or obtained the pin guidance information of the pin that sent the join request. In such cases, receipt of the join request may trigger exception handling, which may include a request to an MNO to obtain pin guide information for the pin. The request to obtain the pin guide information for the pin may be transmitted via a NAS message, and may include a value received in the join request. For example, the join request may already include the PINE ID and/or observed discovery value. The AMF may use the PINE ID and/or observed discovery value to determine an NF, AAA server, or AAA-P associated with the PINE and obtain PINE guide information for the PINE from the NF, AAA server, or AAA-P. The obtained pin guidance information may be transmitted to the PEMC via a NAS message. The PEMC may use the pin guide information to authenticate and/or authorize the WTRU. When a request to obtain the pin guide information for the pin is transmitted via the NAS message, the PEMC may include the pin ID included in the join request via the NAS message. When the AMF receives the NAS message, the AMF may use the pin ID to determine where to forward the request for pin guide information. For example, the AMF may perform a Domain Name System (DNS) lookup on the pin ID. The AMF may perform a DNS lookup on a field (e.g., a single field) of the pin (e.g., a second field of the pin ID). The AMF may have been configured with a mapping between an MNO ID (e.g., or a service provider ID) and a server identifier so that the AMF may determine which server to contact based on the MNO ID (e.g., or the service provider ID) as part of the pin ID. If the join request includes a PINE ID alias, the AMF may resolve (e.g., first resolve) the PINE ID alias to a PINE ID. The request to obtain the pin guide information for the pin may be transmitted to the server via a data plane message (e.g., an HTTP message), and may include a value received in the join request. For example, the join request may already include the PINE ID and/or observed discovery value. The server may use the PINE ID and/or observed discovery value to obtain the PINE guide information for the PINE. The obtained pin guide information may be transmitted to the PEMC via a response message. The PEMC may use the pin guide information to authenticate and/or authorize the WTRU. When a request to obtain the pin guide information for the pin is transmitted to the server via a data plane message (e.g., HTTP message), the PEMC may use the pin ID (e.g., all or part of the pin ID) included in the join request to determine to which server to transmit the join request. For example, the PEMC may perform a DNS lookup on the pin ID. The PEMC may perform a DNS lookup on a field (e.g., a single field) of the pin (e.g., a second field of the pin ID). The PEMC may have been configured with a mapping between an MNO ID (e.g., or a service provider ID) and a server identifier, such that the PEMC may determine which server to contact based on the MNO ID (e.g., or the service provider ID) as part of the pin ID. If the join request includes a PINE ID alias, it may be that the PEMC may resolve (e.g., resolve only) the PINE ID alias to a server identity (e.g., the identity of a server that knows the PINE ID associated with the PINE ID alias).

When the PEMC obtains the pin guide information, the PEMC may perform an authentication and/or authorization procedure with the pin.

The PEMC may send a message to the pin to indicate that the authentication and/or authorization procedure is complete.

The PEMC may send a request to the system (e.g., 5 GC) to verify that the credentials provided by the pin are authentic. For example, when the PEMC performs an authentication and/or authorization procedure with PINE, the PEMC may not have access to the system (e.g., 5 GC), and the PEMC may wish to check that the provided credentials are up-to-date.

The PEMC and the PIN may execute a PIN bootstrap program in which the PEMC configures the PIN with credentials that may be used by the PIN to communicate with other devices within the PIN. For example, the PEMC may determine what PEGC the pin may communicate with, and may configure the pin with the PEGC ID, a routable PEGC address (e.g., IP address), and a value (e.g., key ID and/or key index) that may be used to derive and/or obtain a key that may be used to communicate (e.g., securely communicate) with the PEGC.

The PEMC may configure other devices with information that may be used to authenticate and/or authorize the pin. For example, the PEMC may configure the PEGC with a pin ID, a pin ID alias, and/or a value that may be used to derive a key that may be used to communicate with the pin. In examples where there are multiple PEMCs in the PIN, the PEMCs may utilize this information to configure other PEMCs.

PEGC authorization and/or authentication of PINE may be provided. The PINE may contact the PEGC and perform a mutual authentication and/or authorization procedure with the PEGC using credentials provided by the PEMC. For example, the join request, credential response, authentication and/or authorization, join completion, credential check request, credential check response, and/or bootstrapping the PINE credentials described herein may be performed between the PINE and PEGC with the credentials provided by the PEMC. In an example, the PEGC may use the PEMC to help authenticate and/or authorize the PINE.

Although the above features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements.

While the implementations described herein may consider 3GPP specific protocols, it should be appreciated that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein consider LTE, LTE-a, new air interface (NR), or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario, and are applicable to other wireless systems as well.

The processes described above may be implemented in computer programs, software and/or firmware incorporated in a computer readable medium for execution by a computer and/or processor. Examples of computer readable media include, but are not limited to, electronic signals (transmitted over a wired or wireless connection) and/or 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, but not limited to, internal hard disks and removable disks), magneto-optical media, and optical media (such as Compact Disks (CD) -ROM disks, and/or Digital Versatile Disks (DVD)). A processor associated with the software may be used to implement a radio frequency transceiver for the WTRU, the terminal, the base station, the RNC, and/or any host computer.

Claims

1. A first wireless transmit/receive unit (WTRU), the first WTRU comprising:

a processor configured to:

determining discovery policy configuration information associated with a personal internet of things (IoT) network (PIN), wherein the discovery policy configuration information includes a PIN Identification (ID), and wherein the discovery policy configuration information indicates that discovery for the PIN is enabled;

If discovery for the PIN is enabled, sending a first message to a second WTRU, wherein the first message is based on the discovery policy configuration information, and wherein the first message indicates the PIN ID;

receiving a second message from the second WTRU, wherein the second message indicates the PIN ID and indicates a request for information associated with the PIN; and is also provided with

A third message is sent to the second WTRU, wherein the third message indicates the PIN ID and indicates the requested information associated with the PIN.

2. The first WTRU of claim 1, wherein the discovery policy configuration information includes at least one of a discovery mode, PIN information, or PIN ID.

3. The first WTRU of any of claims 1 or 2, wherein the requested information includes at least one of a list of one or more devices associated with the PIN, PIN capabilities, PIN availability, PIN reachability, or services associated with the PIN.

4. The first WTRU of any of claims 1-3, wherein the processor is configured to determine the discovery policy configuration information associated with the PIN by receiving a fourth message from a third WTRU, wherein the third WTRU is at least one of a PIN gateway, a management-capable PIN Element (PEMC), or a gateway-capable PIN Element (PEGC).

5. The first WTRU of any of claims 1-4, wherein the processor is further configured to send a fifth message to the second WTRU, wherein the fifth message indicates a request to establish a connection between the first WTRU and the second WTRU.

6. A method performed by a first wireless transmit/receive unit (WTRU) for discovering a personal internet of things (IoT) network (PIN), the method comprising:

determining discovery policy configuration information associated with a PIN, wherein the discovery policy configuration information includes a PIN Identification (ID), and wherein the discovery policy configuration information indicates that discovery for the PIN is enabled;

receiving a second message from the second WTRU, wherein the second message indicates the PIN ID and indicates a request for information associated with the PIN; and

7. The method of claim 6, wherein the discovery policy configuration information comprises at least one of a discovery pattern, PIN information, or PIN ID.

8. The method of any of claims 6 or 7, wherein the requested information comprises at least one of a list of one or more devices associated with the PIN, PIN capabilities, PIN availability, PIN reachability, or services associated with the PIN.

9. The method of any of claims 6-8, wherein the determining the discovery policy information associated with the PIN comprises receiving a fourth message from a third WTRU, wherein the third WTRU is at least one of a PIN gateway, a management-capable PIN Element (PEMC), or a gateway-capable PIN Element (PEGC).

10. The method of any of claims 6-9, wherein the method further comprises sending a fifth message to the second WTRU, wherein the fifth message indicates a request to establish a connection between the first WTRU and the second WTRU.

11. A first wireless transmit/receive unit (WTRU), the first WTRU comprising:

a processor configured to:

receiving a solicitation request message from a second WTRU, wherein the solicitation request message indicates a personal internet of things (PIN) Identification (ID) associated with a PIN and indicates a request for information associated with the PIN;

Transmitting a solicitation response message to the second WTRU, wherein the solicitation response message indicates the PIN ID and indicates the requested information associated with the PIN;

receiving a request message from the second WTRU based on the requested information, wherein the request message indicates the PIN ID, indicates a WTRU ID associated with the second WTRU, and indicates a request to join the PIN; and is also provided with

When the WTRU ID has been authenticated, a response message is sent to the second WTRU, wherein the response message indicates that the second WTRU is authorized to join the PIN, and wherein the response message indicates authorization information.

12. The first WTRU of claim 10, wherein the processor is further configured to send an announcement message to the second WTRU, wherein the announcement message indicates the PIN ID associated with the PIN.

13. The first WTRU of any of claims 10-11, wherein the processor is further configured to receive a connection request message, wherein the connection request message indicates a request to establish a connection to the PIN based on the authorization information.

14. The first WTRU of any of claims 10-12, wherein the processor is further configured to authenticate the WTRU ID.

15. The first WTRU of any of claims 10-13, wherein the processor is further configured to authenticate the WTRU ID by sending an authentication request to a network node, wherein the authentication request is a request for authentication information to be used to authenticate the WTRU ID.

16. The first WTRU of any of claims 10-14, wherein the processor is further configured to authenticate the WTRU ID by authenticating the WTRU using the authentication information.

17. The first WTRU of any of claims 10-15, wherein the processor is further configured to determine services that the second WTRU is allowed to access.

18. The first WTRU of any of claims 10-16, wherein the response message further indicates the service to which the second WTRU is allowed to access.