Registration management of individual Internet of Things network elements

By introducing PIN application server to the wireless communication system, the registration management signaling transmission and configuration update of PIN components is solved, and more flexible and efficient device management and policy control are achieved.

CN118947155APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093665.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-29
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing wireless communication systems lack effective registration and management mechanisms in personal Internet of Things (IoT) networks, resulting in low efficiency in component registration and configuration management, which cannot meet the needs of rapid expansion and flexible management.

Method used

A device and method for wireless communication is designed to transmit registration management signaling to PIN components (including PEGC and PEMC) through a PIN application server, realize the registration, cancellation, authentication and access authorization of components, and update the configuration file, supporting Periodic updates and policy parameter management.

Benefits of technology

It improves the registration management efficiency and flexibility of PIN components, ensures the accessibility of devices and the update of communication paths, and enhances the flexibility and policy control capabilities of network management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947155A_ABST
    Figure CN118947155A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a personal Internet of Things (IoT) network (PIN) application server may transmit, to one or more PIN elements, signaling associated with registration management of the one or more PIN elements, where the one or more PIN elements include one or more of a PIN element, a gateway capable PIN element (PEGC), or a management capable PIN element (PEMC). The PIN application server may update registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements. The PIN application server may store or update a profile for the one or more PIN elements based at least in part on the registration management of the one or more PIN elements. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless communications and techniques and apparatus for registration management of personal Internet of Things (IoT) network (PIN) elements. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] In some specific implementations, an apparatus of a personal Internet of Things (IoT) application server for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors being configured to: transmit signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PIN element with gateway capability (PEGC), or a PIN element with management capability (PEMC); update the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and store or update configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0006] In some specific implementations, an apparatus for PEMC for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: transmit signaling associated with registration management of the PEMC to a PIN application server; and transmit signaling associated with creation of a PIN to the PIN application server.

[0007] In some specific implementations, an apparatus for a PIN element for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: transmit signaling associated with registration management of the PIN element to a PIN application server; receive a request associated with the PIN element from a PEMC via the PIN application server, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the PIN element.

[0008] In some specific implementations, an apparatus for a PEGC for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors being configured to: transmit signaling associated with registration management of the PEGC to a PIN application server; receive a request associated with the PEGC from a PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive a supply of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC.

[0009] In some specific implementations, a method of wireless communication performed by a PIN application server includes: transmitting signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: PIN elements, PEGC, or PEMC; updating the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and storing or updating configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0010] In some implementations, a method of wireless communication performed by a PEMC includes: transmitting signaling associated with registration management of the PEMC to a PIN application server; and transmitting signaling associated with creation of a PIN to the PIN application server.

[0011] In some specific implementations, a method of wireless communication performed by a PIN element includes: transmitting signaling associated with registration management of the PIN element to a PIN application server; receiving a request associated with the PIN element from a PEMC via the PIN application server, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending an indication to the PEMC via the PIN application server that the request has been accepted; and receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the PIN element.

[0012] In some specific implementations, a method of wireless communication performed by a PEGC includes: transmitting signaling associated with registration management of the PEGC to a PIN application server; receiving a request associated with the PEGC from the PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; sending an indication to the PEMC via the PIN application server that the request has been accepted; and receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the PEGC.

[0013] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a PIN application server, cause the PIN application server to: transmit signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PEGC, or a PEMC; update the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and store or update configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0014] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of the PEMC, cause the PEMC to: transmit signaling associated with registration management of the PEMC to a PIN application server; and transmit signaling associated with creation of a PIN to the PIN application server.

[0015] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a PIN element, cause the PIN element to: transmit signaling associated with registration management of the PIN element to a PIN application server; receive a request associated with the PIN element from a PEMC via the PIN application server, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive a supply of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element.

[0016] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a PEGC, cause the PEGC to: transmit signaling associated with registration management of the PEGC to a PIN application server; receive a request associated with the PEGC from a PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive a supply of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC.

[0017] In some specific implementations, an apparatus for wireless communication includes a component for transmitting signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PEGC, or a PEMC; a component for updating the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and a component for storing or updating configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0018] In some implementations, an apparatus for wireless communications includes means for transmitting signaling associated with registration management of the apparatus to a PIN application server; and means for transmitting signaling associated with creation of a PIN to the PIN application server.

[0019] In some specific implementations, a device for wireless communication includes a component for transmitting signaling associated with registration management of the device to a PIN application server; and a component for receiving a request associated with the device from the PEMC via the PIN application server, wherein the request is to invite the device to the PIN or to evict the device from the PIN; a component for sending an indication to the PEMC via the PIN application server that the request has been accepted; and a component for receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the device.

[0020] In some specific implementations, a device for wireless communication includes a component for transmitting signaling associated with registration management of the device to a PIN application server; a component for receiving a request associated with the device from a PEMC via the PIN application server, wherein the request is to invite the device to a PIN or to evict the device from the PIN; a component for sending an indication to the PEMC via the PIN application server that the request has been accepted; and a component for receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the device.

[0021] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, PIN application servers, PEMCs, PIN elements, PEGCs, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and descriptions and as illustrated by the accompanying drawings and descriptions.

[0022] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0023] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, cars, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0025] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0026] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0027] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0028] Figure 4 is a diagram illustrating an example of a personal Internet of Things (IoT) network (PIN) architecture in a fifth generation system (5GS) according to the present disclosure.

[0029] Figure 5 is a diagram illustrating an example associated with registration management of a PIN element according to the present disclosure.

[0030] Figures 6 to 9 is a diagram illustrating an example process associated with registration management of a PIN element according to the present disclosure.

[0031] Figures 10 to 13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0035] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0036] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0037] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0038] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0039] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG. 1 , BS 110 d (eg, a relay base station) can communicate with BS 110 a (eg, a macro base station) and UE 120 d to facilitate communication between BS 110 a and UE 120 d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0040] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0041] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0042] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0043] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0044] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0046] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0047] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0048] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave" or the like, if used herein, can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0049] In some aspects, as described in more detail elsewhere herein, a personal IoT network (PIN) application server (e.g., PINAS 124) may transmit signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PIN element with gateway capabilities (PEGC), or a PIN element with management capabilities (PEMC); update registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and store or update configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements. Additionally or alternatively, the PIN application server may perform one or more other operations described herein.

[0050] In some aspects, as described in more detail elsewhere herein, the PEMC (e.g., PEMC 122) can transmit signaling associated with registration management of the PEMC to the PIN application server; and transmit signaling associated with creation of a PIN to the PIN application server. Additionally or alternatively, the PEMC can perform one or more other operations described herein.

[0051] In some aspects, as described in more detail elsewhere herein, a PIN element (e.g., PINE 123) may transmit signaling associated with registration management of the PIN element to a PIN application server; receive a request associated with the PIN element from the PEMC via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element. Additionally or alternatively, the PIN element may perform one or more other operations described herein.

[0052] In some aspects, as described in more detail elsewhere herein, a PEGC (e.g., PEGC 121) may transmit signaling associated with registration management of the PEGC to a PIN application server; receive a request associated with the PEGC from a PEMC via the PIN application server, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from a PIN; send an indication to the PEMC via the PIN application server that the request has been accepted; and receive provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC. Additionally or alternatively, the PEGC may perform one or more other operations described herein.

[0053] As indicated above, Figure 1Other examples can be found in the Figure 1 The examples described are different.

[0054] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0055] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0056] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0057] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0058] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0059] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 13 ) any aspects of any method described.

[0060] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 5 to 13 ) any aspects of any method described.

[0061] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the UE 120 may perform one or more techniques associated with registration management of PIN elements, as described in more detail elsewhere herein. In some aspects, the PIN elements PEGC and / or PEMC described herein are UE 120, included in UE 120, or include Figure 2 In some aspects, the PIN application server described herein is a base station 110, included in the base station 110, or includes Figure 2 One or more components of the base station 110 are shown. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 6 Process 600, Figure 7 Process 700, Figure 8 Process 800, Fig. 9 900 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The process of 700 Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0062] In some aspects, the PIN application server (e.g., PIN AS 124) includes means for transmitting signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: PIN elements, PEGC, or PEMC; means for updating registration of one or more PIN elements based at least in part on the registration management of one or more PIN elements; and / or means for storing or updating configuration files of one or more PIN elements based at least in part on the registration management of one or more PIN elements. In some aspects, the means for performing the operations described herein may include one or more of the following: for example, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0063] In some aspects, the PEMC (e.g., PEMC 122) includes means for transmitting signaling associated with registration management of the PEMC to a PIN application server; and / or means for transmitting signaling associated with creation of a PIN to a PIN application server. In some aspects, the means for performing the operations described herein may include, for example, one or more of the following: antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0064] In some aspects, a PIN element (e.g., PINE 123) includes means for transmitting signaling associated with registration management of the PIN element to a PIN application server; means for receiving a request associated with the PIN element from the PEMC via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; means for sending an indication to the PEMC via the PIN application server that the request has been accepted; and / or means for receiving a provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element. In some aspects, means for performing operations described herein may include, for example, one or more of the following: antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0065] In some aspects, the PEGC (e.g., PEGC 121) includes means for transmitting signaling associated with registration management of the PEGC to a PIN application server; means for receiving a request associated with the PEGC from the PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; means for sending an indication to the PEMC via the PIN application server that the request has been accepted; and / or means for receiving a provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement the behavior of the PEGC. In some aspects, the means for performing the operations described herein may include, for example, one or more of the following: antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0066] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0067] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.

[0068] Figure 3 is a diagram illustrating an example 300 of a disaggregated base station architecture according to the present disclosure.

[0069] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., base station 110) or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

[0070] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0071] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0072] Figure 3 The decomposed base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each of the units (e.g., CU 310, DU 330, RU 340), as well as the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, a unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0074] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to transmit signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0075] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to transmit signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0076] The lower layer functions may be implemented by one or more RUs 340. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0077] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0078] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0079] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0080] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.

[0081] Figure 4 is a diagram illustrating an example 400 of a PIN architecture in a fifth generation system (5GS) according to the present disclosure.

[0082] like Figure 4As shown, the PIN architecture may include one or more PIN elements (PINEs). The PIN element may be a UE or device without 3GPP capabilities, such as a smart watch or smart glasses. The PIN element may communicate with the PEGC. The PEGC may be a first UE. The PIN element may communicate with the PEGC via a P1 reference point between the PIN element and the PEGC. The P1 reference point may be based at least in part on a non-3GPP access (e.g., WiFi or Bluetooth). The PEGC may communicate with the PEMC. The PEMC may be a second UE. The PEGC may communicate with the PEMC via a P2 reference point between the PEGC and the PEMC. The P2 reference point may be based at least in part on a non-3GPP access (e.g., WiFi or Bluetooth) or a 5G ProSe directional communication (e.g., a side link communication). The PEGC may communicate with a next generation radio access network (NG RAN) via a Uu interface between the PEGC and the NG RAN. The PEMC may communicate with the NG RAN via a Uu interface between the PEMC and the NG RAN.

[0083] NG RAN can communicate with 5G core network (5GC). 5GC may include authentication server function (AUSF), unified data management (UDM), policy control function (PCF), network open function (NEF), network function (NF) repository function (NRF), unified data repository (UDR), access and mobility management function (AMF), session management function (SMF) and user plane function (UPF). NEF and UPF can communicate with PIN application server (PIN AS), which can be associated with data network. PEMC can communicate with PIN application server via P3 reference point between PEMC and PIN application server. P3 reference point can be based at least in part on direct user plane path to 5GS, relay path via PEGC or another communication path via Internet. PEGC can communicate with PIN application server via P4 reference point between PEGC and PIN application server. P4 reference point can be based at least in part on user plane path between PEGC and 5GS.

[0084] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.

[0085] The PIN architecture in 5GS may include one or more PIN elements, PEGC, PEMC and / or PIN application servers. However, a mechanism for managing PINs and one or more PIN elements may not be defined. Management of PINs may involve registering or deregistering one or more PIN elements. Further, a mechanism for authorizing PINs may not be defined. Authorization of PINs may involve adding one or more PIN elements to a PIN and / or removing one or more PIN elements from a PIN. Without definitions for management and authorization, the functionality of the PIN architecture may be limited.

[0086] In various aspects of the techniques and devices described herein, a PIN application server may perform management of PINs, management of PIN elements, and authorization of PINs. A PIN application server may perform registration of a PIN element (e.g., a PIN element, a PEGC, and / or a PEMC) to a PIN, which may involve authentication and authorization of the PIN element, assignment of a PIN element ID, and / or creation of a PIN profile. The PIN application server may communicate with the PIN element via the Internet. Upon successful registration, the PEMC may send a request to create a PIN to the PIN application server, and a PIN ID may be assigned to the PEMC by the PIN application server.

[0087] In some aspects, the PEMC may send a request (e.g., an invitation request) to the PEGC via a PIN application server, and the PEGC may send a response (e.g., an invitation acceptance) to the PEMC via the PIN application server. The PIN application server may update the stored data of the PIN profile and the PEGC context accordingly, and the PIN application server may supply PIN-specific application data to the 5GC (e.g., PCF or UDR) for policy control. The PIN application server may send policy and parameter information to the PEGC for configuring PIN communications. In some aspects, the PEMC may send a request (e.g., an invitation request) to the PIN element via the PIN application server, and the PIN element may send a response (e.g., an invitation acceptance) to the PEMC via the PIN application server. The PIN application server may update the stored data of the PIN profile and the PIN element context accordingly. The PIN application server may send policy and parameter information elements to the PIN element for configuring PIN communications.

[0088] In some aspects, when association with a PEGC and a PIN element is requested, the PIN application server may update context data associated with the PEGC and the PIN element, and the PIN application server may supply PIN-specific application data to the 5GC for policy control in the PEGC. The PIN application server may then send policy and parameter information to the associated PEGC and the PIN element for configuring PIN communications.

[0089] Figure 5 is a diagram illustrating an example 500 associated with registration management of PIN elements according to the present disclosure. Figure 5 As shown, example 500 includes communications between a PIN element (e.g., PINE 123), a PEGC (e.g., PEGC 121, which may be associated with UE 120a), a PEMC (e.g., PEMC 122, which may be associated with UE 120e), and a PIN application server (PIN AS 124). In some aspects, the PIN element, PEGC, PEMC, and PIN application server may be included in a wireless network such as wireless network 100.

[0090] As shown in reference numeral 502, the PIN application server may transmit signaling associated with registration management of the PEMC to the PEMC. The PEMC may transmit signaling associated with registration management of the PEMC to the PIN application server. The registration management may include registration of the PEMC or deregistration of the PEMC. The registration management of the PEMC may be based at least in part on the authentication of the PEMC and the access authorization of the PEMC.

[0091] As shown by reference numeral 504, the PIN application server may transmit signaling associated with registration management of the PEGC to the PEGC. The PEGC may transmit signaling associated with registration management of the PEGC to the PIN application server. The registration management may include registration of the PEGC or deregistration of the PEGC. The registration management of the PEGC may be based at least in part on authentication of the PEGC and access authorization of the PEGC.

[0092] As shown in reference numeral 506, the PIN application server may transmit signaling associated with registration management of the PIN element to the PIN element. The PIN element may transmit signaling associated with registration management of the PIN element to the PIN application server. The registration management may include registration of the PIN element or cancellation of the PIN element. The registration management of the PIN element may be based at least in part on the authentication of the PIN element and the access authorization of the PIN element. Further, the PIN element may be associated with the PIN, or the PIN element may be included in the PIN.

[0093] In some aspects, a PIN application may communicate with one or more PIN elements. As used herein, "one or more PIN elements" may refer to a PIN element, a PEGC, and / or a PEMC. In other words, "one or more PIN elements" may refer to a collection of PIN elements, which may include a PIN element, a PEGC, and / or a PEMC.

[0094] In some aspects, the PIN application server may transmit signaling associated with registration management of the one or more PIN elements to one or more PIN elements. The one or more PIN elements may include a PIN element, a PEGC, and / or a PEMC. In some aspects, the PIN application server may update registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0095] In some aspects, the PIN application server may store or update configuration files of one or more PIN elements based at least in part on the registration management of the one or more PIN elements. The configuration files of the one or more PIN elements may indicate a device identifier (ID), a device name, a MAC address, a Bluetooth ID, a universal public subscription identifier (GPSI) of the UE, security-related information, a device type, a device communication capability, and / or a device service capability.

[0096] In some aspects, the PIN application server may transmit signaling associated with the updated registration management to one or more PIN elements. The updated registration management may be making the one or more PIN elements accessible to the PIN application server in a periodic manner. The updated registration management may be updating the status of the one or more PIN elements. The updated registration management may be updating a communication path associated with the one or more PIN elements. The updated registration management may be updating capabilities or parameters of the one or more PIN elements.

[0097] In some aspects, the PIN application server can maintain device context data for one or more PIN elements based at least in part on the registration management. The device context data can indicate an associated PIN ID, an indication of an associated PIN element, a device state, an assigned Internet Protocol (IP) address, an authorized communication path, and / or authorized services.

[0098] In some aspects, registration management can be used to register or deregister PEMC, PEGC and / or PIN elements with a PIN application server and maintain user context in the network. The initial registration process can involve the execution of authentication and access authorization of the PEMC, PEGC and / or PIN elements, which can be based at least in part on the configuration of the owner of the PEMC, PEGC and / or PIN elements (e.g., the owner of the device). After registration and when applied, the PEMC, PEGC and / or PIN element can update its registration with the PIN application server. The registration of the PEMC, PEGC and / or PIN element can be periodically updated so that the PEMC, PEGC and / or PIN element remains accessible to the PIN application server. The registration of the PEMC, PEGC and / or PIN element can be updated so as to update the state of the PEMC, PEGC and / or PIN element. The registration of the PEMC, PEGC and / or PIN element can be updated so as to update the communication path of the PEMC, PEGC and / or PIN element. The registration of the PEMC, PEGC and / or PIN elements may be updated in order to update the capabilities and / or parameters of the PEMC, PEGC and / or PIN elements.

[0099] In some aspects, the configuration file of the PIN element, PEGC and / or PEMC can be stored or updated by the PIN application server after successful registration. The configuration file (e.g., device configuration file) of the PIN element, PEGC and / or PEMC can indicate the device ID, device name, MAC address, Bluetooth ID, GPSI of the UE, security-related information, device type (e.g., PIN element, PEMC or PEGC), device communication capabilities and / or device service capabilities. In some aspects, the device context data of the PIN element or the PEGC of the PIN can indicate the associated PIN ID, the associated PEGC or the associated PIN element, the device status, the assigned IP address (e.g., IP address version 6 (IPv6) prefix), the authorized communication path and / or the authorized service.

[0100] As shown in reference number 508, the PIN application server may transmit signaling associated with the creation of the PIN to the PEMC. The PEMC may transmit signaling associated with the creation of the PIN to the PIN application server. For example, the PIN application server may receive a request to create a PIN from the PEMC. The PIN application server may send an indication of a PIN ID to the PEMC and based at least in part on the request. In other words, the PEMC may send a request to create a PIN to the PIN application server, and the PEMC may receive an indication of a PIN ID from the PIN application server based at least in part on the request. The PIN ID may be assigned to the PEMC by the PIN application server, and the PEMC may be authorized to manage the PIN. In some aspects, the PIN application server may store a PIN profile associated with the PIN, and the PIN application server may synchronize the PIN profile with the PEMC. The PIN profile may indicate a PIN status, a list of service PEMCs, a list of service PEGCs, a list of PIN elements, and / or an expiration date and time validity of the PIN and PIN elements.

[0101] In some aspects, the PEMC may be registered by a PIN application server, and the PEMC may be authorized to manage PINs. A user of the PEMC may initiate a request to create a PIN, for example, via a P3 reference point with a PIN application server. The PIN ID may be assigned by the PIN application server. An optional PIN name may be assigned by a user of the PEMC. The PIN profile and contextual data of the PIN may be stored in the PIN application server and synchronized with the PEMC. The PIN profile may store contextual data such as PIN status (e.g., active or inactive), a list of service PEMCs, a list of service PEGCs, a list of PIN elements, and / or the validity period and time validity of PINs and PIN elements. For a specific PEMC, the list of service PEMCs may indicate the PEMC ID, PEMC status, and / or GPSI and public land mobile network (PLMN) ID. For a specific PEGC, the list of service PEGCs may indicate the PEGCID, PEGC status, and / or GPSI and PLMN ID. For a specific PIN element, the PIN element list may indicate the PIN element ID, PIN element status, MAC address, Bluetooth ID, GPSI and PLMN ID, and / or the association with the PEGC and other PIN elements.

[0102] As shown in reference numeral 510, the PIN application server may receive a request associated with a PEGC from the PEMC. The request may be to invite the PEGC to the PIN or to expel the PEGC from the PIN. As shown in reference numeral 512, the PIN may send the request to the PEGC. In other words, the PEMC may send a request associated with the PEGC to the PEGC via the PIN application server. The PEGC may receive a request associated with the PEGC from the PEMC via the PIN application server. As shown in reference numeral 514, the PIN application server may receive an indication from the PEGC that the request has been accepted. As shown in reference numeral 516, the PIN application server may send an indication to the PEMC that the request has been accepted. In other words, the PEMC may receive an indication from the PEGC via the PIN application server that the request has been accepted, wherein the request may be associated with the PEGC. The PEGC may send an indication to the PEMC via the PIN application server that the request has been accepted. As shown in reference numeral 518, the PIN application server may update a PIN profile associated with the PIN based at least in part on the acceptance of the request. Policies and parameters may be provisioned to the PEGC based at least in part on a reference point between the PIN application server and the PEGC. The PEGC may receive provisioning of policy and parameter information from the PIN application server and based at least in part on an indication that the request has been accepted to implement behavior of the PEGC.

[0103] In some aspects, the PEMC may invite or evict a PEGC in a PIN, and a PEGC may request to join or leave a PIN. Signaling between the PEMC and the PEGC (e.g., requests and acceptance of requests) may be routed to the PIN application server for authorization. Upon successful authorization, the PIN application server may update the PIN profile and modify the context data of the PEGC involved. Further, policies and parameters may be supplied to the PEGC via the P4 reference point between the PEGC and the PIN application server to implement the behavior of the PEGC.

[0104] As shown in reference numeral 520, the PIN application server may receive a request associated with a PIN element from the PEMC. The request may be to invite the PIN element to the PIN or to expel the PIN element from the PIN. As shown in reference numeral 522, the PIN application server may send the request to the PIN element. In other words, the PEMC may send a request associated with the PIN element to the PIN element via the PIN application server. The PIN element may receive a request associated with the PIN element from the PEMC via the PIN application server. As shown in reference numeral 524, the PIN application server may receive an indication from the PIN element that the request has been accepted. As shown in reference numeral 526, the PIN application server may send an indication to the PEMC that the request has been accepted. In other words, the PEMC may receive an indication from the PIN element via the PIN application server that the request has been accepted, wherein the request may be associated with the PIN element. The PIN element may send an indication to the PEMC that the request has been accepted via the PIN application server. As shown in reference numeral 528, the PIN application server may update a PIN profile associated with the PIN based at least in part on the request being accepted. Policies and parameters may be provisioned to the PIN element based at least in part on a reference point between the PIN application server and the PIN element.The PIN element may receive provisioning of policy and parameter information from the PIN application server and based at least in part on an indication that the request has been accepted to implement behavior of the PIN element.

[0105] In some aspects, the PEMC may invite or evict PIN elements in a PIN, and PIN elements may request to join or leave a PIN. Signaling between the PEMC and PIN elements (e.g., requests and acceptance of requests) may be routed to a PIN application server for authorization. Upon successful authorization, the PIN application server may update the PIN profile and modify the context data of the PIN elements involved. Further, policies and parameters may be supplied to the PIN elements via the P1 reference point between the PIN elements and the PEGC to implement the behavior of the PIN elements.

[0106] As shown by reference numeral 530, the PIN application server may supply PIN-related information to the 5GC for policy control or subscription management based at least in part on the mobile operator's policy. The PIN application server may send policy and parameter update information to the PEGC and / or PIN element based at least in part on supplying PIN-related information to the 5GC. In other words, according to the mobile operator's policy, the PIN application server may supply PIN-related information to the 5GC (e.g., NEF, PCF, UDR, or UDM) for policy control or subscription management.

[0107] In some aspects, the management of PINs and PIN elements and the authorization of PINs may affect certain nodes in the 5GC. The PCF may include functionality to supply certain parameters to the UE and SMF to support PIN communications. The UDR may perform storage of PIN service parameters. The NEF may support additional PIN service parameters that may be used by the PIN application function to provide service specific information to the 3GPP network.

[0108] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.

[0109] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a PIN application server in accordance with the present disclosure. The example process 600 is an example of a PIN application server (eg, PIN AS 124) performing operations associated with registration management of PIN elements.

[0110] like Figure 6 As shown, in some aspects, process 600 may include transmitting signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PEGC, or a PEMC (block 610). For example, as described above, a PIN application server (e.g., using Fig.10 The illustrated receiving component 1002 and / or sending component 1004) can transmit signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PEGC, or a PEMC.

[0111] like Figure 6 As further shown, in some aspects, process 600 may include updating the registration of one or more PIN elements based at least in part on the registration management of the one or more PIN elements (block 620). For example, as described above, a PIN application server (e.g., using Fig.10 Illustrated processing component 1008) can update registration of one or more PIN elements based at least in part on registration management of the one or more PIN elements.

[0112] like Figure 6 As further shown, in some aspects, process 600 may include storing or updating configuration files for one or more PIN elements based at least in part on the registration management of the one or more PIN elements (block 630). For example, as described above, a PIN application server (e.g., using Fig.10Illustrated processing component 1008) can store or update configuration files for one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0113] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0114] In a first aspect, registration management includes registration of one or more PIN elements or deregistration of one or more PIN elements.

[0115] In a second aspect, alone or in combination with the first aspect, registration management of the one or more PIN elements is based at least in part on authentication of the one or more PIN elements and access authorization of the one or more PIN elements.

[0116] In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes transmitting signaling associated with updated registration management to one or more PIN elements, wherein the updated registration management is to make the one or more PIN elements accessible to a PIN application server in a periodic manner, update the status of the one or more PIN elements, update the communication path associated with the one or more PIN elements, or update the capabilities or parameters of the one or more PIN elements.

[0117] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the configuration file of the one or more PIN elements indicates one or more of the following: device ID, device name, media access control address, Bluetooth ID, GPSI of UE, security-related information, device type, device communication capability or device service capability.

[0118] In a fifth aspect, either alone or in combination with one or more of aspects one to four, process 600 includes maintaining device context data for one or more PIN elements based at least in part on registration management, wherein the device context data indicates one or more of: an associated PIN identifier, an indication of an associated PIN element, a device state, an assigned IP address, an authorized communication path, or an authorized service.

[0119] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 600 includes transmitting signaling associated with creation of a PIN to a PEMC.

[0120] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 600 includes receiving a request from a PEMC to create a PIN and sending an indication of a PIN ID to the PEMC and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by a PIN application server and the PEMC is authorized to manage the PIN.

[0121] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, process 600 includes storing a PIN profile associated with the PIN, and synchronizing the PIN profile with the PEMC, wherein the PIN profile indicates one or more of: a PIN status, a list of service PEMCs, a list of service PEGCs, a list of PIN elements, or a validity period and time validity of the PIN and PIN elements.

[0122] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, process 600 includes receiving a request associated with a PEGC from a PEMC, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from a PIN; sending the request to the PEGC; receiving an indication from the PEGC that the request has been accepted; sending an indication to the PEMC that the request has been accepted; and updating a PIN profile associated with the PIN based at least in part on the request being accepted, wherein policies and parameters are supplied to the PEGC based at least in part on a reference point between a PIN application server and the PEGC.

[0123] In a tenth aspect, alone or in combination with one or more of aspects one to nine, process 600 comprises receiving a request associated with a PIN element from a PEMC, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from a PIN; sending the request to the PIN element; receiving an indication from the PIN element that the request has been accepted; sending an indication to the PEMC that the request has been accepted; and updating a PIN profile associated with the PIN based at least in part on the request being accepted, wherein policies and parameters are supplied to the PIN element based at least in part on a reference point between a PIN application server and the PIN element.

[0124] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 600 includes supplying PIN-related information to the 5GC for policy control or subscription management based at least in part on the mobile operator's policy; and sending policy and parameter update information to one or more of the PEGC or PIN elements based at least in part on supplying PIN-related information to the 5GC.

[0125] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more of the blocks in the process 600 may be performed in parallel.

[0126] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a PEMC in accordance with the present disclosure. The example process 700 is an example of a PEMC (eg, PEMC 122) performing operations associated with registration management of PIN elements.

[0127] like Figure 7 As shown, in some aspects, process 700 may include transmitting signaling associated with registration management of the PEMC to a PIN application server (block 710). For example, as described above, the PEMC (e.g., using Fig.11 The illustrated receiving component 1102 and / or sending component 1104) can transmit signaling associated with registration management of the PEMC to the PIN application server.

[0128] like Figure 7 As further shown, in some aspects, process 700 may include transmitting signaling associated with the creation of a PIN to a PIN application server (block 720). For example, as described above, the PEMC (e.g., using Fig.11 A receiving component 1102 and / or a sending component 1104) are shown that can transmit signaling associated with the creation of a PIN to a PIN application server.

[0129] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, process 700 includes sending a request associated with the PEGC to a PEGC via a PIN application server, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from a PIN; and receiving an indication from the PEGC via the PIN application server that the request has been accepted.

[0131] In a second aspect, alone or in combination with the first aspect, process 700 includes sending a request associated with a PIN element to a PIN element via a PIN application server, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from a PIN; and receiving an indication from the PIN element via the PIN application server that the request has been accepted.

[0132] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 700 includes sending a request to a PIN application server to create a PIN; and receiving an indication of a PIN ID from the PIN application server and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server and the PEMC is authorized to manage the PIN.

[0133] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of process 700 may be performed in parallel.

[0134] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a PIN element according to the present disclosure. Example process 800 is an example of a PIN element (eg, PINE 123) performing operations associated with registration management of the PIN element.

[0135] like Figure 8 As shown, in some aspects, process 800 may include transmitting signaling associated with registration management of a PIN element to a PIN application server (block 810). For example, as described above, a PIN element (e.g., using Fig.12 The illustrated receiving component 1202 and / or sending component 1204) can transmit signaling associated with registration management of the PIN element to the PIN application server.

[0136] like Figure 8 As further shown, in some aspects, process 800 may include receiving a request associated with a PIN element from the PEMC via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN (block 820). For example, as described above, the PIN element (e.g., using Fig.12 A receiving component 1202 and / or a sending component 1204 are shown to receive a request associated with a PIN element from the PEMC via a PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN.

[0137] like Figure 8 As further shown, in some aspects, process 800 may include sending an indication to the PEMC via the PIN application server that the request has been accepted (block 830). For example, as described above, a PIN element (e.g., using Fig.12 The illustrated receiving component 1202 and / or sending component 1204) can send an indication to the PEMC via the PIN application server that the request has been accepted.

[0138] like Figure 8 As further shown, in some aspects, process 800 may include receiving a provision of policy and parameter information from a PIN application server and based at least in part on an indication that the request has been accepted to implement behavior of a PIN element (block 840). For example, as described above, a PIN element (e.g., using Fig.12 Illustrated receiving component 1202 and / or sending component 1204) can receive from the PIN application server and based at least in part on the indication that the request has been accepted, a provision of policy and parameter information to implement behavior of the PIN element.

[0139] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0140] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0141] Fig. 9 9 is a diagram illustrating an example process 900 performed, for example, by a PEGC according to the present disclosure. Example process 900 is an example of a PEGC (eg, PEGC 121) performing operations associated with registration management of PIN elements.

[0142] like Fig. 9 As shown, in some aspects, process 900 may include transmitting signaling associated with registration management of a PEGC to a PIN application server (block 910). For example, as described above, a PEGC (e.g., using Fig.13 The illustrated receiving component 1302 and / or sending component 1304) can transmit instructions associated with registration management of the PEGC to the PIN application server.

[0143] like Fig. 9 As further shown, in some aspects, process 900 may include receiving a request associated with a PEGC from a PEMC via a PIN application server, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from a PIN (block 920). For example, as described above, a PEGC (e.g., using Fig.13 The illustrated receiving component 1302 and / or sending component 1304) can receive a request associated with a PEGC from the PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN.

[0144] like Fig. 9 As further shown, in some aspects, process 900 may include sending an indication to the PEMC via the PIN application server that the request has been accepted (block 930). For example, as described above, the PEGC (e.g., using Fig.13 The illustrated receiving component 1302 and / or sending component 1304) can send an indication to the PEMC via the PIN application server that the request has been accepted.

[0145] like Fig. 9 As further shown, in some aspects, process 900 may include receiving a provision of policy and parameter information from a PIN application server and based at least in part on an indication that the request has been accepted to implement behavior of the PEGC (block 940). For example, as described above, the PEGC (e.g., using Fig.13 Illustrated receiving component 1302 and / or sending component 1304) can receive from the PIN application server and based at least in part on the indication that the request has been accepted, a provision of policy and parameter information to implement behavior of the PEGC.

[0146] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0147] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0148] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a PIN application server, or a PIN application server may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a processing component 1008, among other things.

[0149] In some aspects, the apparatus 1000 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0150] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described PIN application servers.

[0151] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described PIN application processors. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0152] The receiving component 1002 and / or the sending component 1004 can transmit signaling associated with registration management of the one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PEGC, or a PEMC. The processing component 1008 can update the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements. The processing component 1008 can store or update configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0153] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component set (one or more components) shown may be described as being executable by Fig.10 Another set of components shown performs one or more functions.

[0154] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a PEMC, or a PEMC may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104.

[0155] In some aspects, the apparatus 1100 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 1100 and / or Fig.11 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0156] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the PEMC.

[0157] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the PEMC. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0158] The receiving component 1102 and / or the sending component 1104 can transmit signaling associated with registration management of the PEMC to the PIN application server.The receiving component 1102 and / or the sending component 1104 can transmit signaling associated with creation of a PIN to the PIN application server.

[0159] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another set of components shown performs one or more functions.

[0160] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a PIN element, or the PIN element may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204.

[0161] In some aspects, the apparatus 1200 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.12 The device 1200 and / or one or more components shown may include Figure 2 One or more components of the PIN element described in combination. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0162] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the PIN element.

[0163] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the PIN elements. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0164] The receiving component 1202 and / or the sending component can transmit signaling associated with registration management of the PIN element to the PIN application server. The receiving component 1202 can receive a request associated with the PIN element from the PEMC via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN. The sending component 1204 can send an indication to the PEMC via the PIN application server that the request has been accepted. The receiving component 1202 can receive a provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement the behavior of the PIN element.

[0165] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12 Another set of components shown performs one or more functions.

[0166] Fig.131 is a diagram of an example apparatus 1300 for wireless communication. Apparatus 1300 may be a PEGC or a PEGC may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304.

[0167] In some aspects, the apparatus 1300 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig. 9 In some aspects, the apparatus 1300 and / or Fig.13 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0168] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described PEGC.

[0169] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described PEGC. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0170] The receiving component 1302 and / or the sending component 1304 can transmit signaling associated with registration management of the PEGC to the PIN application server. The receiving component 1302 can receive a request associated with the PEGC from the PEMC via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN. The sending component 1304 can send an indication to the PEMC via the PIN application server that the request has been accepted. The receiving component 1302 can receive a provision of policy and parameter information from the PIN application server and based at least in part on the indication that the request has been accepted to implement the behavior of the PEGC.

[0171] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The component set (one or more components) shown may be described as being executable by Fig.13 Another set of components shown performs one or more functions.

[0172] The following provides an overview of some aspects of the disclosure:

[0173] Aspect 1: A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) application server, the method comprising: transmitting signaling associated with registration management of one or more PIN elements to one or more PIN elements, wherein the one or more PIN elements include one or more of the following: a PIN element, a PIN element with gateway capability (PEGC), or a PIN element with management capability (PEMC); updating the registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; and storing or updating configuration files of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

[0174] Aspect 2: The method according to aspect 1, wherein the registration management includes registration of the one or more PIN elements or deregistration of the one or more PIN elements.

[0175] Aspect 3: The method according to any one of aspects 1 to 2, wherein the registration management of the one or more PIN elements is based at least in part on authentication of the one or more PIN elements and access authorization of the one or more PIN elements.

[0176] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: transmitting signaling associated with updated registration management to the one or more PIN elements, wherein the updated registration management is: making the one or more PIN elements accessible to the PIN application server in a periodic manner, updating the status of the one or more PIN elements, updating the communication path associated with the one or more PIN elements, or updating the capabilities or parameters of the one or more PIN elements.

[0177] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the profile of the one or more PIN elements indicates one or more of the following: a device identifier (ID), a device name, a media access control address, a Bluetooth ID, a universal public subscription identifier of the user equipment, security-related information, a device type, a device communication capability, or a device service capability.

[0178] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method also includes: maintaining device context data of the one or more PIN elements based at least in part on the registration management, wherein the device context data indicates one or more of the following: an associated PIN identifier, an indication of an associated PIN element, a device status, an assigned Internet Protocol address, an authorized communication path, or an authorized service.

[0179] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: transmitting signaling associated with creation of a PIN to the PEMC.

[0180] Aspect 8: A method according to Aspect 7, wherein transmitting the signaling also includes: receiving a request to create the PIN from the PEMC; and sending an indication of a PIN identifier (ID) to the PEMC and at least partially based on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

[0181] Aspect 9: According to the method of Aspect 8, the method also includes: storing a PIN profile associated with the PIN, and synchronizing the PIN profile with the PEMC, wherein the PIN profile indicates one or more of the following: PIN status, a list of service PEMCs, a list of service PEGCs, a list of PIN elements, or the validity period and time validity of the PIN and the PIN element.

[0182] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: receiving a request associated with the PEGC from the PEMC, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; sending the request to the PEGC; receiving an indication from the PEGC that the request has been accepted; sending the indication that the request has been accepted to the PEMC; and updating a PIN profile associated with the PIN based at least in part on the acceptance of the request, wherein policies and parameters are supplied to the PEGC based at least in part on a reference point between the PIN application server and the PEGC.

[0183] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a request associated with the PIN element from the PEMC, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; sending the request to the PIN element; receiving an indication from the PIN element that the request has been accepted; sending the indication that the request has been accepted to the PEMC; and updating a PIN profile associated with the PIN based at least in part on the acceptance of the request, wherein policies and parameters are supplied to the PIN element based at least in part on a reference point between the PIN application server and the PIN element.

[0184] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: supplying PIN-related information to a fifth generation core network (5GC) for policy control or subscription management based at least in part on a mobile operator's policy; and sending policy and parameter update information to the PEGC or one or more of the PIN elements based at least in part on supplying the PIN-related information to the 5GC.

[0185] Aspect 13: A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) element (PEMC) with management capabilities, the method comprising: transmitting signaling associated with registration management of the PEMC to a PIN application server; and transmitting signaling associated with creation of a PIN to the PIN application server.

[0186] Aspect 14: According to the method of Aspect 13, the method also includes: sending a request associated with the PEGC to a PIN element with gateway capabilities (PEGC) via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; and receiving an indication from the PEGC via the PIN application server that the request has been accepted.

[0187] Aspect 15: According to the method described in any one of Aspects 13 to 14, the method further includes: sending a request associated with the PIN element to the PIN element via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; and receiving an indication from the PIN element via the PIN application server that the request has been accepted.

[0188] Aspect 16: A method according to any one of Aspects 13 to 15, wherein transmitting the signaling also includes: sending a request to the PIN application server to create the PIN; and receiving an indication of a PIN identifier (ID) from the PIN application server and at least partially based on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

[0189] Aspect 17: A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) element, the method comprising: transmitting signaling associated with registration management of the PIN element to a PIN application server; receiving a request associated with the PIN element from a PIN element with management capabilities (PEMC) via the PIN application server, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; sending an indication to the PEMC via the PIN application server that the request has been accepted; and receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the PIN element.

[0190] Aspect 18: A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) element (PEGC) with gateway capabilities, the method comprising: transmitting signaling associated with registration management of the PEGC to a PIN application server; receiving a request associated with the PEGC from a PIN element (PEMC) with management capabilities via the PIN application server, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; sending an indication to the PEMC via the PIN application server that the request has been accepted; and receiving a supply of policy and parameter information from the PIN application server and at least partially based on the indication that the request has been accepted to implement the behavior of the PEGC.

[0191] Aspect 19: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 18.

[0192] Aspect 20: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 18.

[0193] Aspect 21: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 1 to 18.

[0194] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 18.

[0195] Aspect 23: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 18.

[0196] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0197] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to a specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0198] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0199] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0200] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A device for a personal Internet of Things (IoT) network (PIN) application server for wireless communication, the device comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting, to one or more PIN elements, signaling associated with registration management of the one or more PIN elements, wherein the one or more PIN elements include one or more of: a PIN element, a PIN element with gateway capability (PEGC), or a PIN element with management capability (PEMC); updating a registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; as well as A configuration file for the one or more PIN elements is stored or updated based at least in part on the registration management of the one or more PIN elements. 2 . The apparatus according to claim 1 , wherein the registration management comprises registration of the one or more PIN elements or deregistration of the one or more PIN elements. 3 . The apparatus of claim 1 , wherein the registration management of the one or more PIN elements is based at least in part on authentication of the one or more PIN elements and access authorization of the one or more PIN elements.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to: and transmitting signaling associated with updated registration management to the one or more PIN elements, wherein the updated registration management is: making the one or more PIN elements accessible to the PIN application server in a periodic manner, updating the status of the one or more PIN elements, updating the communication path associated with the one or more PIN elements, or updating the capabilities or parameters of the one or more PIN elements.

5. An apparatus according to claim 1, wherein the profile of the one or more PIN elements indicates one or more of the following: a device identifier (ID), a device name, a media access control address, a Bluetooth ID, a universal public subscription identifier of a user equipment, security-related information, a device type, a device communication capability, or a device service capability.

6. The apparatus of claim 1, wherein the one or more processors are further configured to: Maintaining device context data for the one or more PIN elements based at least in part on the registration management, wherein the device context data indicates one or more of: an associated PIN identifier, an indication of an associated PIN element, a device state, an assigned Internet Protocol address, an authorized communication path, or an authorized service.

7. The apparatus of claim 1 , wherein the one or more processors are further configured to: Signaling associated with creation of a PIN is transmitted to the PEMC.

8. The apparatus of claim 7, wherein the one or more processors are configured to: receiving a request from the PEMC to create the PIN; and An indication of a PIN identifier (ID) is sent to the PEMC and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

9. The apparatus of claim 8, wherein the one or more processors are further configured to: A PIN profile associated with the PIN is stored and synchronized with the PEMC, wherein the PIN profile indicates one or more of: a PIN status, a list of serving PEMCs, a list of serving PEGCs, a list of PIN elements, or a validity period and time validity of the PIN and the PIN elements.

10. The apparatus of claim 1, wherein the one or more processors are further configured to: receiving a request associated with the PEGC from the PEMC, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from the PIN; Sending the request to the PEGC; receiving an indication from the PEGC that the request has been accepted; sending said indication to said PEMC that said request has been accepted; as well as A PIN profile associated with the PIN is updated based at least in part on the request being accepted, wherein policies and parameters are provisioned to the PEGC based at least in part on a reference point between the PIN application server and the PEGC.

11. The apparatus of claim 1 , wherein the one or more processors are further configured to: receiving a request associated with the PIN element from the PEMC, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending the request to the PIN element; receiving an indication from the PIN element that the request has been accepted; sending said indication to said PEMC that said request has been accepted; as well as A PIN profile associated with the PIN is updated based at least in part on the request being accepted, wherein policies and parameters are provisioned to the PIN element based at least in part on a reference point between the PIN application server and the PIN element.

12. The apparatus of claim 1, wherein the one or more processors are further configured to: Supplying PIN-related information to a fifth generation core network (5GC) for policy control or subscription management based at least in part on a mobile operator's policy; and Sending policy and parameter update information to one or more of the PEGC or the PIN elements based at least in part on supplying the PIN-related information to the 5GC.

13. An apparatus for a Personal Internet of Things (IoT) Network (PIN) Component (PEMC) with management capabilities for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting signaling associated with registration management of the PEMC to a PIN application server; as well as Signaling associated with the creation of a PIN is transmitted to the PIN application server.

14. The apparatus of claim 13, wherein the one or more processors are further configured to: sending, via the PIN application server, a request associated with a gateway-capable PIN element (PEGC), wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; and An indication is received from the PEGC via the PIN application server accepting the request associated with the PEGC.

15. The apparatus of claim 13, wherein the one or more processors are further configured to: sending, via the PIN application server, to a PIN element a request associated with the PIN element, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; and An indication is received from the PIN element via the PIN application server accepting the request associated with the PIN element.

16. The apparatus of claim 13, wherein the one or more processors, when transmitting the signaling, are further configured to: sending a request to the PIN application server to create the PIN; and An indication of a PIN identifier (ID) is received from the PIN application server and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

17. An apparatus for a personal Internet of Things (IoT) network (PIN) element for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting signaling associated with registration management of the PIN element to a PIN application server; receiving, via the PIN application server, a request associated with the PIN element from a PIN element with management capabilities (PEMC), wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element.

18. An apparatus for a gateway-capable personal Internet of Things (IoT) network (PIN) element (PEGC) for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting signaling associated with registration management of the PEGC to a PIN application server; receiving, via the PIN application server, a request associated with the PEGC from a PIN element with management capabilities (PEMC), wherein the request is to invite the PEGC to a PIN or to evict the PEGC from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC.

19. A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) application server, the method comprising: transmitting, to one or more PIN elements, signaling associated with registration management of the one or more PIN elements, wherein the one or more PIN elements include one or more of: a PIN element, a PIN element with gateway capability (PEGC), or a PIN element with management capability (PEMC); updating a registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; as well as A configuration file for the one or more PIN elements is stored or updated based at least in part on the registration management of the one or more PIN elements. 20 . The method according to claim 19 , wherein the registration management comprises registration of the one or more PIN elements or deregistration of the one or more PIN elements.

21. The method of claim 19, wherein the registration management of the one or more PIN elements is based at least in part on authentication of the one or more PIN elements and access authorization of the one or more PIN elements.

22. The method according to claim 19, further comprising: and transmitting signaling associated with updated registration management to the one or more PIN elements, wherein the updated registration management is: making the one or more PIN elements accessible to the PIN application server in a periodic manner, updating the status of the one or more PIN elements, updating the communication path associated with the one or more PIN elements, or updating the capabilities or parameters of the one or more PIN elements.

23. The method of claim 19, wherein the profile of the one or more PIN elements indicates one or more of: a device identifier (ID), a device name, a media access control address, a Bluetooth ID, a universal public subscription identifier of a user equipment, security-related information, a device type, a device communication capability, or a device service capability.

24. The method according to claim 19, further comprising: Maintaining device context data for the one or more PIN elements based at least in part on the registration management, wherein the device context data indicates one or more of: an associated PIN identifier, an indication of an associated PIN element, a device state, an assigned Internet Protocol address, an authorized communication path, or an authorized service.

25. The method of claim 19, further comprising: Signaling associated with creation of a PIN is transmitted to the PEMC.

26. The method of claim 25, wherein transmitting the signaling further comprises: receiving a request from the PEMC to create the PIN; as well as An indication of a PIN identifier (ID) is sent to the PEMC and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

27. The method according to claim 26, further comprising: A PIN profile associated with the PIN is stored and synchronized with the PEMC, wherein the PIN profile indicates one or more of: a PIN status, a list of serving PEMCs, a list of serving PEGCs, a list of PIN elements, or a validity period and time validity of the PIN and the PIN elements.

28. The method of claim 19, further comprising: receiving a request associated with the PEGC from the PEMC, wherein the request is to invite the PEGC to a PIN or to evict the PEGC from the PIN; Sending the request to the PEGC; receiving an indication from the PEGC that the request has been accepted; sending said indication to said PEMC that said request has been accepted; as well as A PIN profile associated with the PIN is updated based at least in part on the request being accepted, wherein policies and parameters are provisioned to the PEGC based at least in part on a reference point between the PIN application server and the PEGC.

29. The method according to claim 19, further comprising: receiving a request associated with the PIN element from the PEMC, wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending the request to the PIN element; receiving an indication from the PIN element that the request has been accepted; sending said indication to said PEMC that said request has been accepted; as well as A PIN profile associated with the PIN is updated based at least in part on the request being accepted, wherein policies and parameters are provisioned to the PIN element based at least in part on a reference point between the PIN application server and the PIN element.

30. The method of claim 19, further comprising: Supplying PIN-related information to a fifth generation core network (5GC) for policy control or subscription management based at least in part on a mobile operator's policy; as well as Sending policy and parameter update information to one or more of the PEGC or the PIN elements based at least in part on supplying the PIN-related information to the 5GC.

31. A method of wireless communication performed by a Personal Internet of Things (IoT) Network (PIN) Component (PEMC) with Management Capabilities, the method comprising: transmitting signaling associated with registration management of the PEMC to a PIN application server; as well as Signaling associated with the creation of a PIN is transmitted to the PIN application server.

32. The method according to claim 31, further comprising: sending, via the PIN application server, a request associated with the PEGC to a PIN element (PEGC) with gateway capabilities, wherein the request is to invite the PEGC to the PIN or to evict the PEGC from the PIN; as well as An indication is received from the PEGC via the PIN application server that the request has been accepted.

33. The method according to claim 31, further comprising: sending, via the PIN application server, to a PIN element a request associated with the PIN element, wherein the request is to invite the PIN element to the PIN or to evict the PIN element from the PIN; as well as An indication is received from the PIN element via the PIN application server that the request has been accepted.

34. The method of claim 31 , wherein transmitting the signaling further comprises: Sending a request to the PIN application server to create the PIN; as well as An indication of a PIN identifier (ID) is received from the PIN application server and based at least in part on the request, wherein the PIN ID is assigned to the PEMC by the PIN application server, and wherein the PEMC is authorized to manage the PIN.

35. A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) element, the method comprising: transmitting signaling associated with registration management of the PIN element to a PIN application server; receiving, via the PIN application server, a request associated with the PIN element from a PIN element with management capabilities (PEMC), wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element.

36. A method of wireless communication performed by a personal Internet of Things (IoT) network (PIN) element (PEGC) with gateway capabilities, the method comprising: transmitting signaling associated with registration management of the PEGC to a PIN application server; receiving, via the PIN application server, a request associated with the PEGC from a PIN element with management capabilities (PEMC), wherein the request is to invite the PEGC to a PIN or to evict the PEGC from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC.

37. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a personal Internet of Things (IoT) network (PIN) application server, cause the PIN application server to: transmitting, to one or more PIN elements, signaling associated with registration management of the one or more PIN elements, wherein the one or more PIN elements include one or more of: a PIN element, a PIN element with gateway capability (PEGC), or a PIN element with management capability (PEMC); updating a registration of the one or more PIN elements based at least in part on the registration management of the one or more PIN elements; as well as Configuration files for the one or more PIN elements are stored or updated based at least in part on the registration management of the one or more PIN elements.

38. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a personal internet of things (IoT) network (PIN) component (PEMC) with management capabilities, cause the PEMC to: transmitting signaling associated with registration management of the PEMC to a PIN application server; and Signaling associated with the creation of a PIN is transmitted to the PIN application server.

39. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a personal Internet of Things (IoT) network (PIN) element, cause the PIN element to: transmitting signaling associated with registration management of the PIN element to a PIN application server; receiving, via the PIN application server, a request associated with the PIN element from a PIN element with management capabilities (PEMC), wherein the request is to invite the PIN element to a PIN or to evict the PIN element from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PIN element.

40. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a personal Internet of Things (IoT) network (PIN) element (PEGC) with gateway capabilities, cause the PEGC to: transmitting signaling associated with registration management of the PEGC to a PIN application server; receiving, via the PIN application server, a request associated with the PEGC from a PIN element with management capabilities (PEMC), wherein the request is to invite the PEGC to a PIN or to evict the PEGC from the PIN; sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as A provision of policy and parameter information is received from the PIN application server and based at least in part on the indication that the request has been accepted to implement behavior of the PEGC.

41. An apparatus for wireless communication, the apparatus comprising: Means for transmitting, to one or more personal Internet of Things (IoT) network (PIN) elements, signaling associated with registration management of the one or more PIN elements, wherein the one or more PIN elements include one or more of: a PIN element, a PIN element with gateway capabilities (PEGC), or a PIN element with management capabilities (PEMC); means for updating a registration of one or more PIN elements based at least in part on the registration management of the one or more PIN elements; as well as Means for storing or updating a configuration file for the one or more PIN elements based at least in part on the registration management of the one or more PIN elements.

42. An apparatus for wireless communication, the apparatus comprising: means for transmitting signaling associated with registration management of the device to a personal Internet of Things (IoT) network (PIN) application server; as well as Means for transmitting signaling associated with creation of a PIN to the PIN application server.

43. An apparatus for wireless communication, the apparatus comprising: means for transmitting signaling associated with registration management of the device to a personal Internet of Things (IoT) network (PIN) application server; means for receiving, via the PIN application server, a request associated with the device from a PIN component with management capabilities (PEMC), wherein the request is to invite the device to a PIN or to eject the device from the PIN; means for sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as Means for receiving, from the PIN application server and based at least in part on the indication that the request has been accepted, a provision of policy and parameter information to implement behavior of the device.

44. An apparatus for wireless communication, the apparatus comprising: means for transmitting signaling associated with registration management of the device to a personal Internet of Things (IoT) network (PIN) application server; means for receiving, via the PIN application server, a request associated with the device from a PIN component with management capabilities (PEMC), wherein the request is to invite the device to a PIN or to eject the device from the PIN; means for sending, via the PIN application server, to the PEMC an indication that the request has been accepted; as well as Means for receiving, from the PIN application server and based at least in part on the indication that the request has been accepted, a provision of policy and parameter information to implement behavior of the device.