PIN configuration, management and application service discovery

Abstract

A WTRU may receive a first message, the first message including one or more criteria associated with an application server. If one or more local application servers satisfy the one or more criteria, the WTRU may transmit a second message to the local client device. The second message may include information for accessing the one or more local application servers in the local network. If no local application server in the local network satisfies the one or more criteria, the WTRU may transmit a third message to a central application management server, the third message including the one or more criteria. The WTRU may receive a fourth message from the central application management server, the fourth message indicating one or more non-native application servers that satisfy the one or more criteria. The WTRU may transmit a fifth message to the local client device, the fifth message having information for accessing the one or more non-local application servers.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 324,493 filed in the United States on March 28, 2022, each of which is incorporated herein by reference in its entirety. Background Art

[0003] The Internet is a global system of interconnected computers and computer networks that communicate with each other using a standard suite of Internet protocols, such as the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet of Things (IoT) is based on the concept that in addition to computers and computer networks, everyday objects can be readable, identifiable, locatable, addressable, and controllable via IoT communication networks.

[0004] The development of IoT devices is driven by multiple market trends. For example, strategic government investments in smart grids and support for future consumption (such as electric vehicles and public charging stations) are driven by increasing energy costs. The development of remote / connected healthcare and fitness services is driven by increasing healthcare costs and an aging population. The development of new "smart" services (including consolidation by service providers marketing multi-service integration ("N" play) (e.g., data, voice, video, security, energy management, etc.) and extended home networks) is driven by technological changes in the home. In order to reduce the operating costs of corporate facilities, buildings are becoming more intelligent and convenient.

[0005] IoT plays a key role in many applications. For example, in the field of smart grid and energy management, utility companies can optimize energy delivery to homes and businesses, while customers can better monitor energy use. In the field of home and building automation, smart homes and buildings can centrally control almost any device or system in the home or office, from appliances to plug-in electric vehicle (PEV) safety systems. In the field of asset tracking, businesses, hospitals, factories and other large organizations can accurately track the location of high-value equipment, patients, vehicles, etc. Finally, in the field of health and wellness, people can track the progress of their fitness programs, and doctors can remotely monitor the health of patients. Summary of the invention

[0006] The WTRU may receive a first message from a local client device in a local network. The local network may include a personal Internet of Things (IoT) network (PIN). The first message may include one or more criteria associated with an application server. The first message may include information associated with a registration request. The information associated with the registration request may include one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS) name, a uniform resource locator (URL), a PIN element identifier (PE-ID), or capability information. The one or more criteria may include one or more of a PIN application server (PAS) name, a PIN element identifier (PE-ID), location information, provider information, or capability information. The WTRU may determine whether any local application server in the local network meets the one or more criteria. If one or more local application servers meet the one or more criteria, the WTRU may transmit a second message to the local client device. The one or more local application servers may include a PIN application server (PAS) in the PIN. The second message may include information for accessing the one or more local application servers in the local network. If no local application server in the local network meets the one or more criteria, the WTRU may transmit a third message to a central application management server. The third message may include the one or more criteria.

[0007] If no local application server in the local network satisfies the one or more criteria, the WTRU may receive a fourth message from the central application management server indicating one or more non-local application servers that satisfy the one or more criteria. The one or more non-local application servers may be located outside the PIN. The WTRU may be configured as a local PIN application manager (LPAM) for the PIN. If no local application server in the local network satisfies the one or more criteria, the WTRU may transmit a fifth message to the local client device. The fifth message to the local client device may include information for accessing the one or more non-local application servers.

[0008] The WTRU may accept the registration request. The WTRU may transmit an update message to the central application management server. The update message may include the information associated with the registration request. The WTRU may transmit a registration acceptance message to the local client device in response to the acceptance of the registration request. The WTRU may update the network in response to the acceptance of the registration request. The update may indicate one or more domain name system (DNS) rules or classifier information associated with routing traffic to the one or more local application servers. The information for accessing the one or more local application servers or the one or more non-local application servers may include one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS), a uniform resource locator (URL), or a PAS capability.

[0009] The WTRU may transmit a message to a personal Internet of Things (IoT) network (PIN) configuration server (PCS), the message including information associated with creating a PIN. The PIN may be associated with the one or more local application servers. The WTRU may receive a message from the PCS, the message including a PIN identifier (PIN ID) and / or a PIN element identifier (PE-ID). The WTRU may transmit a message to a PIN configuration manager (PCM), the message requesting the creation of a PIN. The message to the PCM may include one or more of a PIN ID, a PE-ID, a PIN type, and authorization information. The WTRU may receive a message in response to a message transmitted by the WTRU requesting the PCS to provide an available PIN, the message including a PIN ID and one or more supported application services. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0011] Figure 1B is an example of a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system.

[0012] Figure 1C is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of an example Radio Access Network (RAN) and an example Core Network (CN) for use within the illustrated communication system.

[0013] Figure 1D is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of yet another example RAN and yet another example CN for use within the illustrated communication system.

[0014] Figure 2is a system diagram illustrating an example of a personal Internet of Things (IoT) network (PIN) in a home automation environment.

[0015] Figure 3 is a system diagram illustrating an example of a personal Internet of Things (IoT) network (PIN) in an environment of one or more wearable devices.

[0016] Figure 4 is an architectural diagram illustrating an example of a PIN architecture.

[0017] Figure 5 is a process diagram illustrating an example discovery mode for providing proximity services (ProSe) discovery.

[0018] Figure 6 is a process diagram illustrating an example discovery mode for providing proximity services (ProSe) discovery.

[0019] Figure 7 is a diagram illustrating an example of a PIN application function.

[0020] Figure 8 is a flow chart illustrating an example process for creating a PIN.

[0021] Fig. 9 is a flow chart illustrating an example process for PIN discovery.

[0022] Fig.10 is a flow chart illustrating an example process for adding a PIN.

[0023] Fig.11 is a flow chart illustrating an example process for enabling a PIN.

[0024] Fig.12 is a diagram illustrating an example PIN application client (PAC) and an example PIN application server (PAS).

[0025] Fig.13 is an exemplary diagram illustrating a PIN element with management capabilities (PEMC), a PIN application client (PAC), a PIN application server (PAS), a PIN configuration manager (PCM), a local PIN application manager (LPAM), a PIN client (PC) and a central PIN application manager (CPAM).

[0026] Fig.14 is a diagram illustrating an example PAS registry and an example discovery procedure.

[0027] Fig.15 is a diagram illustrating an example architecture of a PIN application framework. DETAILED DESCRIPTION

[0028] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may 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 multi-carrier (FBMC), etc.

[0029] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but 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. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

[0030] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is 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 other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0031] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send 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 spectrums. A cell may provide coverage of wireless services to a specific 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 the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0032] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0033] More specifically, as noted above, the 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, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 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).

[0034] 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

[0035] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0036] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

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

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

[0039] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

[0041] 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 via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

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

[0043] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

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

[0048] 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 cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0049] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0050] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

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

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

[0054] 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, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0055] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being 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.

[0056] 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 serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

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

[0060] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

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

[0062] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (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 within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0063] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA 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, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0064] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0065] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

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

[0067] 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 a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing 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 a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

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

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

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

[0071] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0072] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0073] 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 slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0074] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is 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.

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

[0076] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0078] 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 acts 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 networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0079] Given that Figures 1A to 1D as well as Figures 1A to 1D , one or more or all of the functions described herein for one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182ab, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0081] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0082] Internet of Things (IoT) features have been designed for devices that use traditional cellular networks for communication. IoT-enabled devices may require enhanced power performance and improved network efficiency for bulk operations.

[0083] Figure 2 2 is an example diagram of a personal Internet of Things (IoT) network (PIN) 200 in a home automation environment. When multiple IoT devices 210 are deployed in a private environment, a WTRU 220 with IoT capabilities may be organized in a personal IoT network (PIN). For example, in a home environment, security sensors, smart lights, smart plugs, printers, mobile phones, etc. are managed by a residential gateway and communicate with each other. One or more devices 210 in a home may constitute a PIN. Each device in the device 210 is referred to as a PIN element or a PIN device. In one example, different PIN elements may have different capabilities. For example, a residential gateway may be a PIN element (PINGW) 230 with gateway capabilities that provides connections between PIN elements and connections between a 5G network and a PIN element. A PIN element with management capabilities (PIN Mgmt) may be a PIN element that provides components for configuring and managing PINs for authorized administrators. For example, a residential gateway acting as a PIN GW 230 may support PIN management functions and / or may also act as a PIN Mgmt. One or more PIN devices or PIN elements may be implemented in a WTRU. The terms PIN device, PIN element, WTRU, PIN client, etc. may be used interchangeably herein.

[0084] Figure 3 300a or 300b. A wearable device may constitute a type of PIN, for example, a wearable PINa 300a or a wearable PINb 300b. For example, a smartphone may act as a PIN GW as well as a PIN Mgmt. A smartwatch 330a or 330b, VR / AR glasses 320a or 320b, and / or a wireless headset 310a or 310b may communicate with each other in a PIN and / or with other WTRUs 340a or 340b via a 5G network 350, for example.

[0085] Figure 4 An example PIN network architecture 400 is shown. A PIN may include one or more of a PIN element (PE) 410, a PIN management (PIN Mgmt) 420, and / or a PIN gateway (PIN GW) 430. A PIN element may be a WTRU or any of a number of different non-3GPP devices capable of communicating within a PIN. A PIN management device may be a PIN element with the ability to manage a PIN. A PIN GW may be a PIN element capable of providing connectivity to and from a 5G network for one or more other PIN elements.

[0086] The PIN elements 410 may communicate with each other by a variety of methods, such as through the PIN GW 430. The PIN elements may also communicate directly with each other. In addition, the PIN elements may communicate with the 5G system to obtain 5G services. The PIN elements may also communicate with the data network 450 via the 5G core network 440. One or more PIN elements with management capabilities may be WTRUs. One or more PIN elements with gateway capabilities may be WTRUs. Communications within the PIN may be performed using one or more of a variety of non-3GPP communications (such as WiFi, Bluetooth, etc.).

[0087] According to one exemplary aspect, the present disclosure is directed to a wireless transmit / receive unit (WTRU) that includes a processor and a memory and is configured to join, manage, or otherwise support a personal IoT network (PIN). A PIN may be a network of devices that communicate to utilize one or more shared services or applications. For example, a PIN may be formed in a home environment to support smart home type applications and may include various devices such as security systems, smart lights, smart plugs, home assistants, mobile phones, etc. The PIN devices may receive connectivity through one or more common gateways.

[0088] In one example, one or more PIN devices may be implemented in a WTRU. The WTRU may be configured to send identification information to a personal Internet of Things network (PIN) configuration server (PCS). In one exemplary aspect, the WTRU receives configuration information and authorization information from the PCS and sends information to a PIN configuration manager (PCM) based on the identification information, the configuration information, and / or the authorization information.

[0089] In one example of the present disclosure, the WTRU receives personal Internet of Things network (PIN) information from the PCM and initiates a PIN-related control procedure based on configuration information, authorization information and / or PIN information.

[0090] One or more devices may participate in and / or provide support for PIN management functions for client devices. For example, the PCS may communicate with a PIN client (PC) located at the WTRU. A PIN gateway manager (PGM) may provide connectivity to one or more application servers that provide services and applications to support PIN operations. For example, a PC (e.g., at a WTRU) may obtain configuration and authorization information from the PCS to create a PIN or join a PIN. The PC may collaborate with the PCM to initiate, join, create, or otherwise manage a PIN.

[0091] One or more devices in the PIN may be configured to facilitate application server discovery for the PIN. For example, a local registry may be maintained by a PIN device, such as a local PIN application manager (LPAM). The LPAM may be implanted at the PCS and / or the PCS may communicate with a device that implements the LPAM. The PIN device may communicate with a device external to the PIN to receive information related to a global registry (e.g., a larger and / or more robust list) of PIN applications. The global registry may be maintained by a central PIN application manager. In one example, a PC (e.g., at a WTRU) may obtain information maintained by the LPAM from the PCS. For example, registration and query messages that may be triggered by a user may be transmitted by the PC to the LPAM. If the LPAM / PCS cannot obtain the information required to respond to the registration and query messages, the LPAM / PCS may query the CPAM to obtain the information and provide it to the PC.

[0092] Figure 55 is a diagram of an example proximity services (ProSe) direct discovery mode 500. ProSe may include services that may be provided based on the relative location of one WTRU 510 and one or more other WTRUs 520a, 520b, 520c, 520d, etc. (e.g., by a 3GPP system). To provide ProSe, the WTRU may perform a ProSe discovery procedure to discover one or more other WTRUs (e.g., such as WTRUs 520a, 520b, 520c, and / or 520d) in its proximity. The WTRU 510 (e.g., an advertiser WTRU) may broadcast one or more announcement messages 530 with a ProSe code. The ProSe code may be associated with an ID of the advertiser WTRU and / or associated with a service provided by the advertiser WTRU 510. One or more other WTRUs (eg, such as WTRUs 520a , 520b , 520c , 520d ) (eg, monitoring WTRUs) that receive the announcement message may determine that they are within a particular proximity of the announcing WTRU 510 .

[0093] Figure 6 6 is a diagram of an example ProSe direct discovery mode 600. A WTRU 610 (e.g., a discoverer WTRU) may broadcast one or more solicitation request messages 630 using a ProSe query code, which may be associated with an ID of the WTRU 610. For example, the ID of the WTRU may be discovered or associated with a ProSe service to be discovered. One or more other WTRUs (e.g., discoverer WTRUs 620a, 620b, 620c, 620d, etc.) that receive the solicitation request message may respond to the request with a ProSe response code. For example, one or more of the discoverer WTRUs 620a, 620b, 620c, 620d may transmit a response message 640 with a ProSe response code in response to the one or more solicitation request messages 630. The ProSe response code may be associated with the ID of the discoverer WTRU and / or associated with a ProSe service. The ProSe service may be provided by a discoverer WTRU (e.g., such as the discoverer WTRU 620a, 620b, 620c, or 620d). The discoverer WTRU 610 may determine that it is within a certain proximity of a discoverer WTRU (e.g., such as the discoverer WTRU 620a, 620b, 620c, or 620d).

[0094] The discovery mode may be used to perform group discovery. An example of group discovery is discovery of one or more WTRUs that may belong to a group. The discovery mode may be used to perform WTRU to network relay discovery. An example of WTRU to network relay discovery is discovery of a WTRU to network relay that may provide connectivity to a 5G network.

[0095] For group discovery, a discovery message (e.g., such as an announce message, solicitation request message 630 and / or response message 640, 650) may include a group ID. For WTRU to network relay discovery, a discovery message may use a relay service code instead of a ProSe code to indicate a WTRU to network relay service.

[0096] The PIN network may be managed by an MNO (Mobile Network Operator) to support application services (eg, gaming, telehealth, etc.) provided by one or more hosting service providers. Users (eg, at home, business, or any location) may establish a PIN to operate the application service.

[0097] The application service provider may supply one or more PIN elements, which the user may purchase directly. Each PIN element may be a 3GPP device or a non-3GPP device. In one example, the PIN element may receive configuration information through an application-level information exchange mechanism before becoming part of the PIN and / or being managed by the MNO. The PIN element may be a non-3GPP device, which may use, for example, BT, WiFi technology and / or other similar technologies.

[0098] PIN can support various application services. An example of a PIN supporting various application services is that various application clients and / or application servers run on one or more PIN elements. PIN can have a distributed and diverse environment, and can rely entirely on or not entirely on network-level methods to discover and connect to application servers. PE may need to determine application-level configurations that can be used for PIN management functions (such as, for example, creating, discovering, joining and / or starting PINs). For example, when PE wants to create a PIN in a location where a PIN does not exist, it may be necessary to determine an application-level configuration for creation. For example, when PE wants to discover whether a PIN already exists in a location and what application services it provides, it may be necessary to determine an application-level configuration for discovery. For example, when PE wants to join an existing PIN, it may be necessary to determine an application-level configuration for joining. For example, when a PIN is to be started, it may be necessary to determine an application-level configuration for startup, which may occur when, for example, a PIN has been created but may not yet be operational. PE may, for example, choose to make the PIN operational at a specific time. In certain circumstances (such as, for example, registering an application server or inputting a query for an application server), it may be desirable to determine a component that facilitates application server discovery using an application-level mechanism. It may also be desirable to determine the architectural requirements of the application framework to support PIN activities, such as, for example, activities related to PIN management, application server discovery, and the like. A solution for PIN management may employ application functions PCS (PIN configuration server), PC (PIN client), PCM (PIN configuration management), and / or PGM (PIN gateway manager). A solution for PIN management may be that the PC obtains configuration and authorization information from the PCS to create and join a PIN. A solution for PIN management may be that the PC collaborates with the PCM to initiate, join, or create a PIN. A solution for PIN application server discovery may be that a local registry LPAM (local PIN application manager) and a global registry CPAM (central PIN application manager) are proposed. A solution for PIN application server discovery may be that the PC obtains LPAM information from the PCS. A solution for PIN application server discovery may be that user-triggered registration and query messages may be transmitted by the PC to the LPAM. A solution for PIN application server discovery may be that if the information is not found in the LPAM, the information may be obtained from the CPAM.

[0099] Figure 7is an exemplary diagram illustrating an example of a PIN application function. For example, a PIN configuration server (PCS) 710 may be an application function that facilitates a PIN management program. PCS 710 may be a central entity that may have knowledge about one or more PINs in a network. PIN client (PC) 720 may be an example of an application function that facilitates a PIN management program. PC 720 may be a client in a PIN element that may obtain information from the PCS to enable PIN management operations. PIN configuration manager (PCM) 730 may be an example of an application function that facilitates a PIN management program. PCM 730 may be an application function associated with a PIN element with management capabilities. PCM 730 may locally track PIN management for a PIN. PIN gateway manager (PGM) 740 may be an example of an application function that facilitates a PIN management program. PGM 740 may be an application function in a PE with gateway capabilities. PCS 710 may, for example, maintain information about one or more PINs across an MNO network. PCS 710 may maintain information including, for example, information about authorization and policy-related information for PEs, such as whether the PE is allowed to create a PIN, allowed to join a PIN, allowed to use a specific application service, and the like. PCS 710 may maintain information about IDs assigned to PEs and / or may authorize PEs to join PINs. PCS 710 may maintain information about available PINs, their PIN IDs in specific locations, and / or allowed application services. PCS 710 may maintain information about the PCM 730 for each PIN and how to reach the PCM 730 for a specific PIN ID. PC 720 may be a function in a PE and may be provided with PCS 710 information. PC 720 may provide a function of obtaining information about available PINs, PIN IDs, available services, and / or PCM 730 information for PINs from PCS 710. PC 720 may provide a function of obtaining an application-level PE-ID from PCS 710 in order to join or create a PIN. In addition, PC 720 may provide a function to assist PEs in executing and / or creating PINs and / or joining PINs using PCS 710 and PCM 730. PCM 730 may be a local PIN management function and may be part of the PEMC. PCM 730 may maintain local PIN information such as PIN ID, available PEs and PE-IDs, PEs joining PINs, authorization information, policy information, and the like. PCM 730 may also verify, update, and / or synchronize information about local PINs with the PCS. PGM 740 may be a function that may be used with a PE having gateway capabilities. PGM 740 may obtain and implement gateway configuration from PCM 730 and / or PCS 710. The PIN may not be present in a location where a user may want to initiate a PIN for a particular application service.In an example scenario, a user may own a PE and want to use the PE to create a PIN. The PE owned by the user may be a WTRU with PEMC capabilities (e.g., a 3GPP WTRU). The PE owned by the user may also be a non-3GPP device that does not have PEMC capabilities.

[0100] Figure 8 800 is a diagram illustrating an example process for creating a PIN creation, which causes the creation of a PIN. At 810, a PIN client (PC) may indicate to the PCS the intention and / or ability to create a PIN by, for example, providing information such as a user ID, a device ID, location information, whether the PE has PEMC capabilities, desired application services on the PIN, and / or other types of similar or related information. At 812, the PCS may authenticate and authorize the user and may create a PIN ID and / or PE-ID. The PCS may determine the appropriate PCM function based on the capabilities of the PE. At 814, the PCS may respond by providing the PIN-ID and / or PE-ID of the device. The PCS may also include PCM information in its response. At 816, after obtaining information from the PCS, the PC may transmit a creation request with information such as, for example, PIN ID, PE-ID, PIN type, and / or authorization information to the PCM. At 818, the PCM may verify the newly created PIN ID with the PCS. The PCM may obtain information from the PCS about what PE may be needed to support application services. The PCM may transmit a query message to the PCS at 818, which may include a PIN ID. The PCS may return one or more PE-IDs that may be used to create a PIN and support the desired service. At 820, the PCM may determine whether the required PE is available and whether it is allowed to join. For example, if the PCM determines at 820 that the required PE is available and allowed to join, the PCM may determine that a PIN can be created and notify the PC about the successful creation of the PIN. For example, if the PCM determines at 820 that the PE is not available and / or is not allowed to join, the PCM may transmit an indication such as, for example, ERROR or PIN creation FAIL. The PCM may also update the PCS about one or more PE-IDs that are available to join or have joined. At 822, the PCM may transmit a configuration update message to the PGM, which may include information such as, for example, a PIN ID, one or more PE-IDs, and / or one or more allowed QOS. At 824, the PCM may update the PIN creation details to the 3GPP network.

[0101] Fig. 99 is a diagram illustrating an example process 900 for PIN discovery. For example, a user with a PE may join a PIN in order to use an application service. The user may discover whether a PIN is available at a specific location that provides the desired application service. The PE may be a 3GPP or non-3GPP device. The PE may or may not perform network-level discovery. Application-level service discovery may allow a unified discovery method for 3GPP and / or non-3GPP PEs. The PC 910 may query the PCS 920 for available PINs via location information and / or PLMN information. For example, the PC 910 may transmit a query message to the PCS 920 at 912. The query message may indicate location information and / or PLMN information. The PCS 920 may check its database to determine available PINs at a specific location. The PCS 920 may respond to the PC 910 with a list of available PINs in a specific location at 922, for example by transmitting a PIN ID and supported application services. The PC 910 may select which PIN it wants to join to use a specific application service.

[0102] Fig.10is a diagram illustrating an example of steps 1000 involved in PIN joining. After the PE discovers the PIN, the next step may be to join the PIN. After the PE determines the PIN it will join, the PE may obtain authorization from the PCS to join the PIN. For example, at 1010, the PC may transmit a join request by transmitting information including the PIN ID, user ID, and / or PIN type of the PIN it wants to join. At 1012, the PCS may authenticate and / or authorize the join request transmitted by the PC based on the user ID and / or PIN type. If the PCS determines that the join request is allowed, the PCS may respond by transmitting a message (such as, for example, OK) to the PC at 1012, which may include information such as the PE-ID assigned to the PE by the PCS, PCM information, a local PCM for PIN management, and / or authorization information for the local PIN. At 1014, the PC may contact the PCM and notify the PCM of its intention to join the PIN. For example, the PC may transmit specific information to the PCM at 1014, such as a PIN ID that may have been previously discovered and authorized by the PCS, its own PE-ID, PIN type, and / or authorization information. The PCM may verify whether the joining of the PE can be supported, and may do so by considering conditions including the current state of the application service, the available QOS, and / or other available PEs. The PCM may also contact the PCS to verify the PE ID and / or verify whether the PE is allowed to join. At 1016, if the PE is allowed to join and can be supported, the PCM may respond by transmitting an approval indication to the PC and an indication of the result of the request. Examples of indications of the result of the request may be ALLOWED, BARRED, NOT SUPPORTED, or another result. At 1018, the PCM may update the PCS with updated PIN information, thereby indicating a new PE that has joined the PIN. At 1020, the PCM may transmit a configuration update message to the PGM, which may include information such as the PIN ID, one or more PE-IDs, and / or one or more allowed QOS. The PCM may update the PIN join details to the 3GPP network at 1022. The PIN join details may include, for example, re-creation, update operations, and / or other information.

[0103] Fig.111100 is a flow chart illustrating an example process 1100 for starting a PIN. After creating or joining a PIN, the user may then start the PIN. PIN creation or joining may utilize one or more available PEs, PEMCs, and / or PEGWs to set the PIN. In one example, PIN start may cause the PIN to enter an operational state in which one or more time-based PEs are running and available. The user may start the PIN by transmitting a trigger to the PC. In 1110, a PE with or without PEMC capability may trigger the PIN start. The start trigger may originate from the PC and be transmitted to the PCM. The PC may transmit a start trigger indicating the PIN ID at 1110 and set the START indication to TRUE. At 1112, the PCM may transmit the PIN ID and / or one or more PE-IDs of the PEs that have joined the PIN together with the START request to the PCS. At 1114, the PCS verifies the PIN ID, one or more PE-IDs, and / or the timer value. The PCS may transmit an OK indication to the PCM at 1114. At 1116, the PCM may transmit a configuration update to the PGM function and may set the state from START to TRUE. At 1118, the PCM may transmit an OK indication to the PC requesting START. The PCM may also trigger other PEs to enter the START state by transmitting an OK indication (e.g., 200 OK (START == TRUE)) to one or more other PEs. At 1120 and 1122, the PCS may transmit a START indication to the 3GPP network to start the PIN. The PCM may, for example, transmit a START indication to the 3GPP network at 1122. The PCS may, for example, transmit a START indication to the 3GPP network at 1120.

[0104] Fig.12 12 is a diagram illustrating an example PIN application client (PAC) 1210 and an example PIN application server (PAS) 1220. A PE 1230 or 1260 may provide services through a PIN application server (PAS) 1220. A PAC 1210 may consume one or more services from one or more other PASs (e.g., such as PAS 1250). A PAC 1210 may discover and / or connect to other PASs 1250 to consume one or more services. A PAS 1220 may register and enable the PAC 1210 to be discovered by one or more other PACs (e.g., such as PAC 1240). The discovery and consumption of PASs 1220, 1250 may occur locally within a PIN. The discovery and consumption of PASs 1220, 1250 may occur outside of a PIN, such as in another PIN, in an EDN, within a 5GS, in the Internet, or in any other location.

[0105] Fig.13 1300 is an exemplary diagram illustrating a PIN element with management capabilities (PEMC) 1310, a PIN application client (PAC) 1320, a PIN application server (PAS) 1330, a PIN configuration manager (PCM) 1340, a local PIN application manager (LPAM) 1350, a PIN client (PC) 1360, and a central PIN application manager (CPAM) 1370. A service registry function may be provided in the context of a local PIN to facilitate PAS 1330 discoverability. A global PAS 1330 registry may be used for discovery across PINs and in EDNs. PIN local level service registry and management functions (e.g., LPAM 1350) may occur in PEMC 1310. A local PIN application server may register services with LPAM 1350. LPAM 1350 may be hosted in PEMC 1310. CPAM 1370 may serve as a global registry for a PAS (e.g., such as PAS 1330). CPAM 1370 may be deployed in a core network (e.g., 5G CN), such as, for example, in an EDN.

[0106] Fig.141400 is a diagram depicting an example of a procedure 1400 involved in PIN application server (PAS) registration and discovery. A PIN client (PC) 1420 in a PE may obtain local PIN application manager (LPAM) 1440 information from a PIN configuration server (PCS) 1450 by transmitting a Get_lpam_info message to the PCS 1450 at 1412. The PCS 1450 may respond to the PC 1420 with the LPAM 1440 information at 1414. In an example PAS registration procedure, the PAS 1410 may transmit a registration request to the PC 1420 at 1416. With the registration request, the PAS 1410 may transmit an application server name and detailed information on how to reach the PAS 1410 at 1416. The PC 1420 may transmit a registration request to the LPAM 1440 at 1418. The registration request transmitted at 1418 may include information such as a PAS name, URL, PE-ID, and / or PE-ID capabilities. LPAM 1440 may accept the registration request, may update the local service registry, and may transmit an OK message to PC 1420 at 1422. PC 1420 may transmit an OK message to PAS 1410 at 1424. LPAM 1440 may also update CPAM at 1426 with information including PAS name, URL, PE-ID, and / or capabilities. LPAM 1440 and CPAM 1320 may update 3GPP network at 1428 with information including Domain Name System (DNS) rules, classifier information for proper routing or traffic direction toward application servers. In an example query procedure, the query procedure may be initiated by PAC 1410 at 1432. PAC 1410 may transmit a query message to PC 1420 at 1432, which may include the PAS name and / or one or more selection criteria. The query message to PC 1420 may include information such as PE-ID, location, provider, and / or capabilities of the PAS. The PC 1420 may transmit a query message with detailed information (such as, for example, PAS name, PE-ID, and / or other selection criteria that may include location, capabilities, and / or provider) to the LPAM 1440 at 1434. The LPAM 1440 may search its registry to find out whether the PAS information is available. If not, the LPAM 1440 may query the CPAM 1320 for the same information at 1436. After the LPAM 1440 finds the PAS information, the LPAM may respond to the PC 1420 with PAS information such as a PAS URL, capabilities, and / or other PAS information at 1438. The PC 1420 may transmit the PAS information to the PAC 1410 at 1442. The PAS information may include, for example, a PAS URL and / or PAS capabilities.

[0107] Fig.15 is an example diagram of a PIN application framework architecture 1500. The example application framework is described based on the management and application server discovery program requirements previously described. In an example set of interactions for PIN management, PIN 1 can connect application client / server (PAS / PAC) (ACS) 1510 and PC 1520. PIN 1 can be a trigger for creating, launching and / or discovering a PIN: user application, application client initiates PIN creation, PIN discovery and / or PIN launch. PIN 2 can connect PC 1520 and PCS 1530. PIN 2 can perform creation and / or launch: PC 1520 pre-configured with PCS information can contact PCS 1530 to create or launch a PIN, during which PCS 1530 can assign a PEID and / or PIN ID. PCS 1530 can also provide PCM information to PC 1520. PIN 2 can also perform discovery, during which the PC can obtain a PIN ID and / or PCM information. PIN 3 can connect PC 1520 and PCM 1550. For PIN 3, after obtaining the PIN ID and PE ID from the PCS, PC 1520 may initiate a create, join, and / or start procedure with PCM 1550, during which a create PIN, join PIN, and / or start PIN are performed. PIN 5 may connect PCM 1550 and PCS 1530, which may allow PCM 1550 to update information to PCS 1530. PIN 5 may perform a process of starting a PIN and / or obtaining PIN policy information. PIN 7 may connect PCM 1550 and PGM 1560, which may allow PCM 1550 to transmit configuration information to PGM 1560, for example, to establish one or more PIN paths. PIN 7 may also update the PIN ID and / or PE-ID. In an example set of interactions related to PIN application service management, PIN 1 may connect ACS 1510 and PC 1520. PIN 1 may perform registration and queries initiated by user applications to the PC. PIN 1 may perform service registration, which involves registration of an application server in the PE. PIN 1 may also perform a query, which may be initiated by an application client in the PE. PIN 2 may connect PC 1520 and PCS 1530. PIN 2 may perform an action to obtain LPAM information, during which the PC may obtain LPAM (local registry) information. PIN 4 may connect PC 1520 and LPAM 1570. PIN 4 may perform registration services and query actions for services. PIN 6 may connect LPAM 1570 and CPAM 1540. PIN 6 may perform update registration and query actions for services not found in LPAM 1570.

Claims

1. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising a processor and a memory, the processor being configured to: receiving a first message from a local client device in a local network, the first message including one or more criteria associated with an application server; determining whether any local application server in the local network satisfies the one or more criteria; transmitting, conditional upon one or more local application servers satisfying the one or more criteria, a second message to the local client device, the second message comprising information for accessing the one or more local application servers in the local network; as well as On the condition that no local application server in the local network satisfies the one or more criteria: transmitting a third message to the central application management server, the third message including the one or more criteria, receiving a fourth message from the central application management server indicating one or more non-local application servers that satisfy the one or more criteria, and A fifth message is transmitted to the local client device, wherein the fifth message includes information for accessing the one or more non-local application servers.

2. The WTRU of claim 1 , wherein the local network comprises a personal Internet of Things (IoT) network (PIN), the one or more local application servers comprise a PIN application server (PAS) in the PIN, the one or more non-local application servers are located outside the PIN, and the WTRU is configured as a local PIN application manager (LPAM) for the PIN.

3. A WTRU according to claim 1 or 2, wherein the one or more criteria include one or more of a PIN application server (PAS) name, a PIN element identifier (PE-ID), location information, provider information or capability information.

4. The WTRU of any one of claims 1 to 3, wherein the first message includes information associated with a registration request.

5. The WTRU of claim 4, wherein the information associated with the registration request comprises one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS) name, a uniform resource locator (URL), a PIN element identifier (PE-ID), or capability information.

6. The WTRU of claim 4 or 5, wherein the processor is further configured to: accepting the registration request; and An update message is transmitted to the central application management server, the update message including the information associated with the registration request.

7. The WTRU of claim 6, wherein the processor is further configured to transmit a registration accept message to the local client device in response to the acceptance of the registration request.

8. A WTRU according to claim 6 or 7, wherein the processor is further configured to: update the network in response to acceptance of the registration request, and the update indicates one or more Domain Name System (DNS) rules or classifier information associated with routing the service to the one or more local application servers.

9. The WTRU according to any one of claims 1 to 8, wherein the information used to access the one or more local application servers or the one or more non-local application servers includes one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS), a uniform resource locator (URL), or PAS capabilities.

10. The WTRU of claim 1 , wherein the processor is further configured to: transmitting a sixth message to a personal Internet of Things (IoT) network (PIN) configuration server (PCS), the sixth message including information associated with creating a PIN, wherein the PIN is associated with the one or more local application servers; receiving a seventh message from the PCS, the seventh message including a PIN identifier (PINID) and a PIN element identifier (PE-ID); transmitting an eighth message to a PIN configuration manager (PCM), the eighth message requesting creation of a PIN, wherein the eighth message to the PCM includes one or more of a PIN ID, a PE-ID, a PIN type, and authorization information; and A ninth message is received in response to the eighth message, the ninth message including a PINID and supported application services.

11. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving a first message from a local client device in a local network, the first message including one or more criteria associated with an application server; determining whether any local application server in the local network satisfies the one or more criteria; transmitting, conditional upon one or more local application servers satisfying the one or more criteria, a second message to the local client device, the second message comprising information for accessing the one or more local application servers in the local network; as well as On the condition that no local application server in the local network satisfies the one or more criteria: transmitting a third message to the central application management server, the third message including the one or more criteria, receiving a fourth message from the central application management server indicating one or more non-local application servers that satisfy the one or more criteria, and A fifth message is transmitted to the local client device, wherein the fifth message includes information for accessing the one or more non-local application servers.

12. The method of claim 11, wherein the local network comprises a personal Internet of Things (IoT) network (PIN), the one or more local application servers comprise a PIN application server (PAS) in the PIN, the one or more non-local application servers are located outside the PIN, and the WTRU is configured as a local PIN application manager (LPAM) for the PIN.

13. The method of claim 11 or 12, wherein the one or more criteria include one or more of a PIN application server (PAS) name, a PIN element identifier (PE-ID), location information, provider information, or capability information.

14. The method according to any one of claims 11 to 13, wherein the first message comprises information associated with a registration request.

15. The method of claim 14, wherein the information associated with the registration request comprises one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS) name, a uniform resource locator (URL), a PIN element identifier (PE-ID), or capability information.

16. The method according to claim 14 or 15, further comprising: accepting said registration request; as well as An update message is transmitted to the central application management server, the update message including the information associated with the registration request.

17. The method according to claim 16, further comprising: A registration accept message is transmitted to the local client device in response to the acceptance of the registration request.

18. The method according to claim 16 or 17, further comprising: The network is updated in response to accepting the registration request, wherein updating the network includes indicating one or more Domain Name System (DNS) rules or classifier information associated with routing traffic to the one or more local application servers.

19. The method of any one of claims 11 to 18, wherein the information for accessing the one or more local application servers or the one or more non-local application servers comprises one or more of a personal Internet of Things (IoT) network (PIN) application server (PAS), a uniform resource locator (URL), or PAS capabilities.

20. The method according to claim 11, further comprising: transmitting a sixth message to a personal Internet of Things (IoT) network (PIN) configuration server (PCS), the sixth message including information associated with creating a PIN, wherein the PIN is associated with the one or more local application servers; receiving a seventh message from the PCS, the seventh message including a PIN identifier (PINID) and a PIN element identifier (PE-ID); transmitting an eighth message to a PIN configuration manager (PCM), the eighth message requesting creation of a PIN, wherein the eighth message to the PCM includes one or more of a PIN ID, a PE-ID, a PIN type, and authorization information; and A ninth message is received in response to the eighth message, the ninth message including a PINID and supported application services.

Images