Individual Internet of Things network connectivity

By implementing policy transmission and connection management between the core network and the PIN device in the wireless transmitting/receiving unit (WTRU), the problems of low core network connectivity and traffic forwarding efficiency of IoT devices are solved, and the PIN GW and the core network are improved. connectivity and data transmission efficiency.

CN119014025APending Publication Date: 2024-11-22INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380024252.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-01-27
Filing Date
2023-01-27
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing technology is difficult to effectively manage the core network connectivity and traffic forwarding between personal Internet of Things (IoT) devices, resulting in low efficiency in PIN policy authorization, traffic parameter transmission and data transmission, and the connectivity management between PIN components and PIN GW. complex.

Method used

Provide a wireless transmitting/receiving unit (WTRU) that sends PIN manager capability requests to the core network through circuits, receives authorized PIN type policies, sends PIN gateway capability policies, receives traffic forwarding parameters and data network name information, based on these information Establish a connection to the core network and forward data through the connection.

Benefits of technology

It realizes efficient connectivity management and data transmission between PIN devices, simplifies the policy transmission and authorization process between PIN GW and the core network, and improves the efficiency and reliability of the IoT network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014025A_ABST
    Figure CN119014025A_ABST
Patent Text Reader

Abstract

Methods, devices, and systems are provided for personal internet of things (PIN) networking. A wireless transmit / receive unit (WTRU) is described, the wireless transmit / receive unit (WTRU) having circuitry to: send a PIN policy request indicating a PIN manager capability to a core network (CN); receiving, from the CN, a PIN policy indicating an authorized PIN type; transmitting a PIN connectivity policy indicating a PIN gateway (GW) capability of the WTRU; receiving, from the CN, PIN connectivity policy information indicating a traffic forwarding parameter, a data network name (DNN), and slice information; receiving a PIN connectivity establishment request from the PIN element; establishing a connection with the CN based on the DNN and the slice information; and forwarding data between the CN and the PIN element via the connection based on the traffic forwarding parameter.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 303,832, filed on January 27, 2022, the contents of which are incorporated herein by reference. Background Art

[0003] The Internet of Things (IoT) is a term that can be used to describe a network of devices embedded with sensors or other capabilities. IoT devices typically communicate data via wireless or wired communication networks. Summary of the invention

[0004] Methods, devices and systems for personal internet of things (PIN) networking are provided. A wireless transmit / receive unit (WTRU) is described, the wireless transmit / receive unit (WTRU) having circuitry for: sending a PIN policy request indicating PIN manager capabilities to a core network (CN); receiving a PIN policy indicating authorized PIN types from the CN; sending a PIN connectivity policy indicating PIN gateway (GW) capabilities of the WTRU; receiving PIN connectivity policy information indicating traffic forwarding parameters, a data network name (DNN) and slice information from the CN; receiving a PIN connectivity establishment request from a PIN element; establishing a connection with the CN based on the DNN and the slice information; and forwarding data between the CN and the PIN element via the connection based on the traffic forwarding parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

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

[0007] Figure 1B is an example of an embodiment in which Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0008] Figure 1C is an example of an embodiment in which Figure 1A a system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0009] Figure 1D is an example of an embodiment in which Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0010] Figure 2 is a system diagram illustrating an example personal IoT network (PIN);

[0011] Figure 3 is a system diagram illustrating another example PIN;

[0012] Figure 4 is a system diagram illustrating an example PIN architecture;

[0013] Figure 5 is a system diagram illustrating an example architecture for a 5G residential network;

[0014] Figure 6 is a flow chart illustrating an example method for PEMC to establish connectivity;

[0015] Figure 7 is a flow chart illustrating an example method for a PIN GW to establish connectivity;

[0016] Figure 8 is a sequence diagram illustrating example communications for PIN connectivity establishment;

[0017] Fig. 9 is a flow chart illustrating an example method for PEMC / GW to establish connectivity;

[0018] Fig.10 is a sequence diagram illustrating example communications for connectivity establishment;

[0019] Fig.11 is a sequence diagram illustrating example communications for local connectivity establishment; and

[0020] Fig.12 is a sequence diagram illustrating example communications for connectivity establishment. DETAILED DESCRIPTION

[0021] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0022] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

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

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

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

[0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0049] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

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

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

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

[0055] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, wherein the source STA may send traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

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

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

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

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

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

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

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

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

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

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

[0066] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0067] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

[0071] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.

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

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

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

[0075] Internet of Things (IoT) features have been designed for devices that communicate using traditional cellular networks. Devices with IoT features typically have better power consumption performance (e.g., compared to typical UEs) and improved network efficiency for bulk operations. IoT features may include, for example, control plane cellular IoT (CIoT) 5GS optimization, power saving enhancements, etc.

[0076] In some embodiments, for example, in the case where multiple IoT devices are deployed in a private environment, WTRUs with IoT capabilities may be organized as personal IoT networks (PINs). For example, in a home environment, security sensors, smart lights, smart plugs, printers, cellular phones, etc. may be managed by a residential gateway and may communicate with each other. In some embodiments, these home devices may form part of a PIN. Each device in a PIN may be referred to as a PIN element. Different PIN elements may have different capabilities. For example, a residential gateway or other device and / or application configured to provide a connection between PIN elements and a connection between a 5G network (or other network) and a PIN element may be referred to as a PIN element with gateway capabilities (PIN GW). In some embodiments, IoT devices (e.g., PIN elements) may communicate with other PIN elements directly or via a PIN GW or via another network (e.g., 5G or the Internet via 5G). In some embodiments, a PIN is a specific LAN controlled by a CN (e.g., a 5G system). In some embodiments, PIN management (e.g., PEMC) and PIN GW are WTRUs (e.g., UEs) that can access a CN (e.g., a 5G CN).

[0077] In some embodiments, the residential gateway may provide management functions for the PIN. A PIN element or other device and / or application that provides PIN management functions may be referred to as a PEMC, PIN management, or a PIN element with management capabilities (PEMC). Example management functions for a PIN include creating, modifying, or deleting a PIN, authorizing or deauthorizing a PIN element to access a PIN, authorizing or deauthorizing a PIN element to access another network (e.g., 5G CN) via a PIN GW, and the like. In some embodiments, the PIN GW may be collocated with the PEMC.

[0078] Figure 2 is a system diagram illustrating an example PIN 200. In this example, PIN 200 is a home automation PIN. In other embodiments, the PIN may be used for any suitable purpose. Figure 2The exemplary PIN 200 of includes a gateway 210 (which may be a residential gateway in an embodiment) acting as a PIN GW and various other PIN elements, such as a smart door 222, an alarm system 224, a smart light 242, smart power sockets 240, 244, 241, a smart lock 226, a visitor PIN element 230, etc. Some PIN elements may act as relays, for example, as shown by smart sockets 240, 244, 246 and smart light 242. In this example, the PIN GW includes PIN management functions (i.e., it is a PEMC). The PIN GW may be connected to a local Ethernet and to devices connected to the local Ethernet, such as a printer 212. A WTRU 250, which may be a mobile phone, may also be part of the PIN 200. The PIN may be connected to a core network 260, which may be a 5G CN.

[0079] Figure 3 is a system diagram illustrating another example PIN. Figure 3 An example of a wearable device PIN, namely PINa 310, is included. PINa includes a WTRU, which may be a cell phone 318 or a smart phone that functions as a PIN GW and PEMC, and various PIN elements, such as a smart watch 316, virtual reality (VR) and / or augmented reality (AR) glasses 314, and a wireless headset 312. In other embodiments, any suitable wearable (or non-wearable) PIN element may be included in the wearable device PIN. PIN elements (including cell phones or smart phones) communicate with each other within the PIN (or communicate with other devices such as WTRUs or UEs via a 5G network 330). In some embodiments, PINa may communicate with a similar PIN (PINb) 320 via a 5G network. PINb may include a WTRU, which may be a cell phone 328 or a smart phone that functions as a PIN GW and PEMC, and various PIN elements, such as a smart watch 324, virtual reality (VR) and / or augmented reality (AR) glasses 326, and a wireless headset 322. In some embodiments, PINa 310 and PINb 320 communicate via any suitable communication infrastructure and / or protocol, such as 5G, LTE, WiFi, TCP / IP, the Internet, etc.

[0080] Figure 4 is a system diagram illustrating an example PIN architecture. Figure 4In the example of FIG. 4 , PIN 410 includes PIN elements 416, 418, PEMC (PIN Mgmt 414 in the figure) and PIN gateway (PIN GW) 412. In this example, PIN elements 416, 418 are WTRUs (e.g., UEs) or non-3GPP devices that can communicate within the PIN. PIN Mgmt 414 is a PIN element with the ability to manage PINs. PIN GW 412 is a PIN element that can provide connectivity to and from a 5G core network 420 for other PIN elements. Example connectivity includes IP connectivity, Ethernet connectivity, etc. For example, such connectivity can be provided by creating a PDU session between PIN GW 412 and 5G network 420. 5G network 420 may include RAN 422, AMF 424 and SMF 426, and UPF 428. Connectivity may be established toward different 5G networks, different DNNs 430, different slices (e.g., Network Slice Selection Assistance Information (NSSAI) etc.).

[0081] In some embodiments, the PIN elements may communicate with each other via the PIN GW or directly. In some embodiments, the PIN elements may communicate with the 5G system to obtain 5G services and / or communicate with the data network via the 5G core network. For example, 5GC is used, however, in other embodiments, any suitable core network is available. The PIN elements may communicate with any other suitable system to obtain corresponding services and / or communicate with the data network via 5GC. In this example, the access and mobility management function (AMF) 424, session management function (SMF) 426 and user plane function (UPF) 428 of 5GC are shown, and other elements are omitted for ease of illustration.

[0082] In some embodiments, the existing 5G RG provides IP connectivity for local devices. In some embodiments, the PIN element may have specific connectivity requirements, for example, a specific DNN may be required. In some embodiments, the PIN is managed by the PEMC, but the connectivity is controlled by the PIN GW.

[0083] Figure 55G Residential Network 510 is a system diagram illustrating an example architecture for a 5G residential network 510. In this example, the 5G residential network includes a 5G residential gateway (RG) 516 and local devices 512, 514, which may include WTRUs or other devices that can communicate with the 5G RG 516 via the local network. In this example, the local network 510 is IP-based, however, in other embodiments, any suitable communication infrastructure may be used. Via the 5G RG 516, the local network 510 may provide connectivity between local devices and the 5G system to obtain 5G services and / or communicate with data networks via the 5G core network 520. The 5G network 520 may include a RAN 522, an AMF 524 and an SMF 526, and a UPF 528. Connectivity toward different 5G networks, different DNNs 530, different slices (e.g., network slice selection assistance information (NSSAI)), etc.) may be established.

[0084] exist Figure 5 In an exemplary 5G residential network of FIG. 5G RG 516, 5G RG 516 establishes a PDU session with 5GC to obtain an IP address and / or prefix. After obtaining the IP address and / or prefix, 5G RG assigns the IP address and / or prefix to the local device. After being assigned the IP address and / or prefix, the local device can communicate with other devices or data networks via IP traffic.

[0085] PIN can provide connectivity between PIN elements and 5G systems through mechanisms used in residential networks; for example, via PDU sessions established through residential gateways, however, various complex issues may still exist. For example, traditional systems may not provide CN connectivity management (e.g., management of connections between PIN GW and 5GC, or between PIN elements and 5GC via PINGW) and / or local connectivity management (e.g., management of connections between PIN elements and other PIN elements, and / or management of connections between PIN elements and PN GW).

[0086] Various PINs may include different types of PIN elements; for example, security sensors, Bluetooth headsets, game consoles, VR glasses, smart TVs, etc. Different PINs and PIN elements may have different connectivity requirements. For example, some PINs or PIN elements may need to access 5G services and / or external data networks, while some PINs or PIN elements may only utilize internal communications (i.e., within the PIN). In other words, some PINs and PIN elements require 5G services or access external networks via 5G, while other PIN elements only require internal communications within the PIN.

[0087] Thus, some embodiments facilitate authorization of PINs and / or PIN elements to use CN connectivity (e.g., communicating between a PIN GW and a 5GC, or communicating between a PIN element and a 5GC via a PIN GW). Some embodiments may facilitate distinguishing PINs and / or PIN elements to provide CN connectivity.

[0088] Various PIN elements may use local connectivity (e.g., between PIN elements and / or with a PIN GW) to communicate with other PIN elements or via other PIN elements or with the 5GC via a PIN GW. Thus, some embodiments may facilitate authorization of PIN and PIN element local connectivity (i.e., between PIN elements and / or with a PIN GW). For example, in addition to IP allocation as used in a residential network, the PIN GW may be configured to identify whether a PIN element is authorized to use local connectivity.

[0089] Various challenges may include authorization of PIN connectivity, provisioning of connectivity between the PIN and the core network, and provisioning of connectivity between the PIN elements and the PIN GW.

[0090] Thus, some embodiments may provide for PIN policy provisioning. In some embodiments, the PEMC receives the authorized PIN type and the corresponding connectivity type (e.g., local connectivity type or CN connectivity type), PIN size, and / or PIN duration. In some embodiments, the PIN GW receives the authorized PIN type and the corresponding connectivity type and the corresponding CN connectivity parameters (e.g., DNN, SSC mode, PDU session type).

[0091] Some embodiments may provide CN connectivity between the PIN GW and the CN. In some embodiments, the PEMC requests the PIN GW to establish connectivity to the CN for the PIN by indicating the PIN type. In some embodiments, the PIN GW retrieves the DNN, SSC mode, and NSSAI of the PIN type. In some embodiments, the PIN GW indicates the PINID during the PDU session establishment process.

[0092] Some embodiments provide local connectivity between PIN elements and PIN GW. In some embodiments, PINGW provides security parameters for connectivity to PEMC, which configures security parameters to PIN elements. In some embodiments, PIN elements provide their ID, data delivery type, and security parameters for connectivity establishment between PIN elements and PIN GW. In some embodiments, PIN GW reports PIN element ID, IP and RAT to CN, for example, for billing and QoS control. In some embodiments, PIN GW selects control plane (CP) or user plane (UP) delivery for PIN element traffic based on delivery type.

[0093] Some embodiments provide connectivity between a PIN and a core network. Some example PIN types include sensor PIN, VR PIN, gaming PIN, etc. Some example connectivity types include local connectivity or CN connectivity. In some embodiments, different PIN types are associated with different requirements for connection to the core network (e.g., SSC mode, slicing, DNN, CP data delivery, etc.). In some embodiments, the PEMC requests the PIN GW to establish a connection to the core network, for example by indicating the PIN type. In some embodiments, the indication may indicate a list of PIN elements and / or a corresponding connectivity type.

[0094] Some embodiments provide CN connectivity management. For example, in some embodiments, the PEMC and / or PIN GW receives a PIN connectivity policy including authorized PIN types from a 5G system (e.g., AMF or PCF, etc.). In some embodiments, the PIN connectivity policy received from the 5G system may include authorized PIN types, connectivity types for each PIN type, and / or CN connectivity parameters for each PIN type. In some embodiments, when the PEMC requests the PIN GW to establish or modify PIN connectivity for a PIN, the PEMC indicates the PIN type in the request. In some embodiments, after receiving the PIN type in a PIN connectivity establishment or modification request from the PIN management, the PIN GW retrieves the connectivity type and CN connectivity parameters of the PIN type based on the received PIN connectivity policy. In some embodiments, the PIN GW establishes or modifies CN connectivity with the 5G core network based on the retrieved CN connectivity parameters.

[0095] In some embodiments, the PIN type may indicate the type of the entire PIN. For example, the PIN type may include a sensor PIN, a VR PIN, a gaming PIN, etc. In some embodiments, the PIN GW establishes or modifies CN connectivity with the 5G core network for the entire PIN (e.g., based on the PIN type). Alternatively, in some embodiments, the PIN type may indicate the type of a PIN element (a portion of a PIN, or a type of a partial PIN). For example, the PIN type of a PIN element may include a motion sensor, VR glasses, a gaming console, etc. In some embodiments, when the PIN type indicates a PIN element type, the PIN GW may establish or modify CN connectivity with the 5G core network for a PIN element of that type (for a portion of a PIN, or a partial PIN).

[0096] In some embodiments, the connectivity type may indicate local connectivity (i.e., communication within a PIN), CN connectivity (i.e., communication via a 5G core network or other CN), offload connectivity (communication with another network offloaded via a PIN GW), etc., and / or any combination of these types of connectivity. In some embodiments, the PIN GW establishes or modifies CN connectivity with a 5G core network, wherein the received connectivity type indicates CN connectivity or both CN connectivity and another type of connectivity.

[0097] In some embodiments, the CN connectivity parameters may indicate a public land mobile network (PLMN) identification (ID), a data network name (DNN), a service and session continuity (SSC) mode, slice information, a packet data unit (PDU) session type, a data delivery mode (e.g., control plane and / or user plane) and / or a data transmission frequency, among others.

[0098] In some embodiments, the PEMC and / or PIN GW may receive a PIN connectivity policy from a 5G system (e.g., AMD, PCF, etc.), which may include local connectivity parameters. In some embodiments, the local connectivity parameters may indicate, for example, L2 / L3 relays, endpoint identifiers, and inter-RAT communication policies. The local connectivity parameters may be applied to the entire PIN, or to each PIN element, or to a group of PIN elements. Different policies may be used in the PIN for different PIN elements. In some embodiments, when a PIN connectivity establishment or modification request is received from the PEMC (e.g., as part of a request, or otherwise indicated by a request), the PIN GW retrieves the received local connectivity parameters for local connectivity.

[0099] In some embodiments, before the PIN GW establishes CN connectivity with the 5G core network, the PIN GW may select a PLMN for CN connectivity with the 5G core network. In some embodiments, the PIN GW may establish multiple CN connections with different PLMNs for different PIN types.

[0100] In some embodiments, the CN connection established by the PIN GW with the 5G core network may include a PDU session, a public data network (PDN) connection, a 5G local area network (5G-LAN) connection, a short message service (SMS) connection, etc.

[0101] In some embodiments, the PIN GW may indicate the PIN ID, PIN type, and / or the number of PIN elements in the PIN in a request to establish CN connectivity with the 5G core network. In some embodiments, the PIN GW may send a PIN connectivity response to the PEMC to indicate the result of the PIN connectivity establishment (e.g., whether the connection was successfully established or failed).

[0102] In some embodiments, the PEMC may receive an indication of the connectivity type for each PIN type in the PIN connectivity policy from the 5G system. In some embodiments, when the PEMC requests the PIN GW to establish or modify PIN connectivity for a PIN, the PEMC may indicate the connectivity type in the request. In some embodiments, the PIN GW may determine whether to establish or modify CN connectivity with the 5G core network based on the received connectivity type.

[0103] In some embodiments, the PEMC may receive another PIN policy; for example, indicating a PIN size and / or a PIN duration. In some embodiments, the PIN size indicates the maximum number of PIN elements in the PIN. In some embodiments, the PIN duration indicates the time during which the PIN is available (e.g., created or accessed by a PIN element).

[0104] In some embodiments, the PEMC may receive the PIN connectivity policy from the PIN GW instead of from the 5G system. In some such cases, the PIN GW may request the PIN connectivity policy for the PEMC and for the PIN GW itself from the 5G system.

[0105] Figure 6is a flow chart illustrating an example method for PEMC to establish connectivity. In this example, at 610, the PEMC sends a PIN connectivity policy request to the CN (e.g., to the AMF or policy control function (PCF) of the CN) or to the PIN GW, where the policy request indicates the PEMC capabilities. The capability indication may indicate, for example, whether the PIN supports PIN management, such as PIN creation, PIN modification, and / or PIN deletion, etc. At 612, the PEMC receives a PIN connectivity policy indicating authorized PIN types and a connectivity type for each PIN type from the CN or the PIN GW. At 614, the PEMC sends a PIN connectivity establishment or modification request indicating the authorized PIN types and a connectivity type for each PIN type to the PIN GW. At 616, the PEMC receives a PIN connectivity establishment or modification response from the PIN GW.

[0106] Figure 7 7 is a flow chart illustrating an example method for a PIN GW to establish connectivity. In this example, at 710, the PIN GW sends a PIN connectivity policy request to a CN (e.g., to an AMF or a policy control function (PCF) of the CN), wherein the policy request indicates the PIN GW capabilities. At 712, the PIN GW receives a PIN connectivity policy from the CN, which may indicate authorized PIN types, a connectivity type for each PIN type, and / or CN connectivity parameters for each PIN type. At 714, the PIN GW receives a PIN connectivity establishment / modification request from the PIN management, which may indicate authorized PIN types and / or a connectivity type for each PIN type. Under the condition (716) that the PIN GW decides to establish CN connectivity, at 718, the PIN GW retrieves a connectivity type for each PIN type and / or a CN connectivity parameter for each PIN type based on the received PIN type and the received PIN connectivity policy. The PIN GW determines the CN connectivity to be established for the PIN based on the connectivity type. The PIN GW selects the 5G core network (if applicable) based on the PLMN in the CN connectivity parameters of the PIN type. At 720, the PIN GW sends a CN connectivity establishment request to the 5G core network, which indicates the retrieved CN connectivity parameters, such as DNN, SSC mode and / or slice information, etc. Optionally, the PIN GW indicates the PIN type and / or PIN size in the CN connectivity establishment request to the 5G core network. At 722, the PIN GW receives a CN connectivity response from the CN. At 742, the PIN GW sends a PIN connectivity establishment or modification response to the PEMC. The response will also be sent if the result 716 of determining to establish CN connectivity is negative.

[0107] Figure 8 is a sequence diagram illustrating example communications between PIN element 810, PEMC 812, PIN GW 814, and CN 816 for PIN connectivity establishment.

[0108] At 820, PEMC 812 transmits a PIN connectivity policy request (eg, sends a message indicating the PIN connectivity policy request) to core network 816 (eg, to an AMF or policy control function (PCF) of the CN). The message may indicate PEMC capabilities.

[0109] At 822, the core network 816 communicates the PIN connectivity policy (eg, sends a message indicating the PIN connectivity policy) to the PEMC 812. The message may indicate the authorized PIN types.

[0110] At 824, the PIN GW 814 transmits a PIN connectivity policy request (eg, sends a message indicating the PIN connectivity policy request) to the core network 816 (eg, to the AMF or policy control function (PCF) of the CN). The message may indicate the PIN GW capabilities.

[0111] At 826, the core network provides the PIN connectivity policy to the PIN GW (e.g., sends a message indicating the PIN connectivity policy). The message may indicate the authorized PIN type, connectivity type, and / or CN connectivity parameters. In an embodiment, operations 824 and 826 may be independent of operations 820 and 822, and may be performed before, during, or between operations 820 and 822.

[0112] At 828, the PIN element 810 may establish a connection with the PEMC 812. The connection may be any suitable connection, such as, for example, a Bluetooth or WiFi connection. In some embodiments, operation 828 may be performed after operations 820 and 822. In some embodiments, operation 828 may be performed, for example, earlier or later than operation 830. Operation 828 is shown in the figure as optional. In some embodiments, other operations or elements may also be optional. For example, in some embodiments, the PEMC 812 may create a PIN context locally and request the PIN GW 814 to establish connectivity for the PIN, and then the PEMC 812 waits for the PIN element 810 to join. In another example, after the PIN element 810 joins the PIN, the PEMC 812 requests the PIN GW 814 to establish connectivity. It will be appreciated by those skilled in the art that various orders of these operations are contemplated, and Figure 8 The order in which the operations are presented is not intended to be limiting.

[0113] At 830, the PEMC 812 determines to create a PIN and determines the PIN type. The PEMC may verify whether the PIN type is allowed (e.g., according to a PIN connectivity policy), whether the number of PIN elements to be included in the PIN has reached a PIN size limit, whether the PIN duration has expired, etc. Creating the PIN may include determining and / or storing PIN context information (e.g., a PIN ID, a list of PIN elements, a PIN type, etc.).

[0114] At 832, PEMC 812 communicates a PIN connectivity establishment request to PIN GW 814 (e.g., sends a message indicating the PIN connectivity establishment request). The communication may indicate the PIN ID and PIN type of the PIN to be created. The communication may indicate the number of PIN elements, a list of PIN element IDs, and / or a PIN duration, etc.

[0115] At 834, the PIN GW 814 determines to establish or modify CN connectivity for the PIN according to the connectivity type of the PIN type indicated in the message of operation 832. The PIN GW 814 retrieves CN connectivity parameters of the PIN type according to the corresponding PIN connectivity policy.

[0116] At 836, PIN GW 814 communicates a CN connectivity establishment or modification request (e.g., sends a message indicating a CN connectivity establishment or modification request) to core network 816. The communication may indicate, for example, a PDU session establishment or modification request. The communication may indicate, for example, a PIN ID, a PIN type of the PIN, and / or a number of PIN elements.

[0117] At 838, the core network 816 communicates a CN connectivity establishment or modification response (eg, sends a message indicating the CN connectivity establishment or modification response) to the PIN GW 814. The communication may include, for example, a PDU session establishment and / or modification response.

[0118] At 840, PIN GW 814 communicates a PIN connectivity establishment response (eg, sends a message indicating the PIN connectivity establishment response) to PEMC 812. The communication may indicate a PIN connectivity establishment result; for example, CN connectivity is established.

[0119] In some embodiments, the PEMC 812 may be collocated with the PIN GW 814. The collocated PEMC and PIN GW may be referred to as PEMC / GW. The PEMC / GW may receive a PIN connectivity policy from the 5G system, which may include authorized PIN types, connectivity types for each PIN type, and / or CN connectivity parameters for each PIN type. In some embodiments, when the PEMC / GW decides to create a PIN, the PEMC / GW retrieves the connectivity type and CN connectivity parameters of the PIN type according to the received PIN connectivity policy. In some embodiments, the PEMC / GW establishes or modifies CN connectivity with the 5G core network based on the retrieved CN connectivity parameters.

[0120] In some embodiments, the PIN type may indicate the type of the entire PIN. For example, the PIN type may include a sensor PIN, a VR PIN, a gaming PIN, etc. In some embodiments, the PEMC / GW establishes or modifies CN connectivity with the 5G core network for the entire PIN (e.g., based on the PIN type). Alternatively, in some embodiments, the PIN type may indicate the type of a PIN element (a portion of a PIN, or a type of a partial PIN). For example, the PIN type of a PIN element may include a motion sensor, VR glasses, a gaming console, etc. In some embodiments, when the PIN type indicates a PIN element type, the PEMC / GW may establish or modify CN connectivity with the 5G core network for a PIN element of that type (for a portion of a PIN, or a partial PIN).

[0121] In some embodiments, the connectivity type may indicate local connectivity (i.e., communication within a PIN), CN connectivity (i.e., communication via a 5G core network or other CN), offload connectivity (communication with another network offloaded via a PIN GW), etc., and / or any combination of these types of connectivity. In some embodiments, the PEMC / GW establishes or modifies CN connectivity with a 5G core network, wherein the received connectivity type indicates CN connectivity or both CN connectivity and another type of connectivity.

[0122] In some embodiments, the CN connectivity parameters may indicate PLMN ID, DNN, SSC mode, slice information, PDU session type, data delivery mode (e.g., control plane and / or user plane) and / or data transmission frequency, etc.

[0123] In some embodiments, before the PEMC / GW establishes CN connectivity with the 5G core network, the PEMC / GW may select a PLMN for CN connectivity with the 5G core network. In some embodiments, the PEMC / GW may establish multiple CN connections with different PLMNs for different PIN types.

[0124] In some embodiments, the CN connectivity with the 5G core network established by the PEMC / GW may include PDU sessions, public data network (PDN) connections, 5G local area network (5G-LAN) connections, short message service (SMS) connections, etc.

[0125] In some embodiments, the PEMC / GW may indicate the PIN ID, PIN type and / or the number of PIN elements in the PIN in a request to establish CN connectivity with the 5G core network.

[0126] In some embodiments, the PEMC / GW may receive another PIN policy; for example, indicating a PIN size and / or a PIN duration. In some embodiments, the PIN size indicates the maximum number of PIN elements in the PIN. In some embodiments, the PIN duration indicates the time during which the PIN is available (e.g., created or accessed by a PIN element).

[0127] Fig. 9 is a flow chart illustrating an example method for PEMC / GW to establish connectivity. In this example, at 910, PEMC / GW sends a PIN connectivity policy request to CN (e.g., to the AMF or policy control function (PCF) of the CN) or to PEMC / GW, wherein the policy request indicates the PEMC / GW capabilities. The capability indication may indicate, for example, whether the PIN supports PIN management, such as PIN creation, PIN modification, and / or PIN deletion, etc. At 920, PEMC / GW receives a PIN connectivity policy from CN, which indicates the authorized PIN types, the connectivity type for each PIN type, and / or the CN connectivity parameters for each PIN type. At 930, PEMC / GW determines whether to establish connectivity with the CN for the PIN based on the connectivity type. At 932, PEMC / GW selects a 5G core network (if applicable) based on the PLMN indicated by the received CN connectivity parameters. Then, at 934, PEMC / GW sends a CN connectivity establishment request to the 5G core network. The request indicates the retrieved CN connectivity parameters 932 (eg, DNN, SSC mode, slice information, etc.). In some embodiments, the request indicates the PIN type.

[0128] Fig.10 is a sequence diagram illustrating example communications for connectivity establishment between PIN element 1010 , PIN management / GW (PEMC / GW) 1012 , and core network 1014 .

[0129] At 1020, PIN Management / GW 1012 transmits a PIN connectivity policy request (eg, sends a message indicating the PIN connectivity policy request) to the core network 1014 (eg, to the AMF or Policy Control Function (PCF) of the CN). The message may indicate the PEMC / GW capabilities.

[0130] At 1022, the core network 1014 transmits the PIN connectivity policy (eg, sends a message indicating the PIN connectivity policy) to the PEMC / GW 1012. The message may indicate the authorized PIN type, connectivity type, and / or CN connectivity parameters.

[0131] At 1024, PIN element 1010 establishes a connection with PEMC / GW 1012. The connection may be any suitable connection, such as a Bluetooth or WiFi connection. Operation 1024 may be optional in an embodiment.

[0132] At 1026, PEMC / GW 1012 determines to create a PIN and determines the PIN type. In an embodiment, PEMC / GW may verify whether the PIN type is allowed (e.g., by a PIN connectivity policy), whether the number of PIN elements to be included in the PIN has reached a PIN size limit, whether the PIN duration has expired, etc.

[0133] At 1028, the PEMC / GW 1012 determines to establish or modify CN connectivity for the PIN based on the connectivity type of the PIN type. The PIN management / GW retrieves the CN connectivity parameters of the PIN type based on the corresponding PIN connectivity policy.

[0134] At 1030, PEMC / GW 1012 transmits a CN connectivity establishment or modification request to core network 1014 (e.g., sends a message indicating a CN connectivity establishment or modification request). In an embodiment, the message may indicate, for example, a PDU session establishment or modification request. In another embodiment, the message may indicate, for example, a PIN ID, a PIN type of a PIN, and / or a number of PIN elements.

[0135] At 1032, the core network 1014 transmits a CN connectivity establishment or modification response (eg, sends a message indicating the CN connectivity establishment or modification response) to the PEMC / GW 1012. In an embodiment, the message may include, for example, a PDU session establishment and / or modification response.

[0136] Some embodiments may provide connectivity between the PIN and the PIN GW. Some embodiments may include security parameters, e.g., for connection establishment between the PIN element and the PIN GW; PIN GW ID, e.g., for PIN GW selection; data delivery type, e.g., indicating control plane delivery or user plane delivery; connectivity type, which may indicate local and / or CN connectivity, and / or IP, Ethernet, or unstructured, etc.; and / or PIN element RAT, e.g., used by the CN to decide QoS policy for traffic of the PIN element.

[0137] Some embodiments may provide local connectivity management. For example, in some embodiments, the PEMC provides a PINID, an ID of a PIN GW, a connectivity type, local connectivity parameters, and security parameters for local connectivity to a PIN element. In some embodiments, the PIN element sends a message indicating a local connectivity request to the PIN GW, the message including the PINID, the ID of the PIN element, the data delivery type, local connectivity parameters, and / or security parameters for local connectivity. In some embodiments, the PIN GW determines whether the requested local connectivity is available, for example, based on the security parameters for local connectivity. In some embodiments, if the PIN GW accepts the local connectivity request, the PIN GW may send a message indicating a local connectivity response to the PIN element. The message may indicate a connectivity status (e.g., whether CN connectivity is available for the local connectivity).

[0138] In some embodiments, the PEMC may obtain security parameters for local connectivity from the PIN GW. In some embodiments, the PEMC may obtain security parameters for local connectivity from the core network. In some embodiments, the PEMC may obtain local connectivity parameters from the PIN GW or the core network.

[0139] In some embodiments, the data delivery type indicated by the local connectivity request may indicate whether the data needs to be delivered by the control plane or the user plane in the CN connectivity between the PIN GW and the 5G core network. In some embodiments, the PINGW may report the ID of the PIN element, the IP address used by the PIN element, and the RAT of the PIN element (e.g., Wifi, Bluetooth, etc.) to the core network. In some embodiments, the connectivity state may additionally indicate IP connectivity, Ethernet connectivity, etc. In some embodiments, before sending a local connectivity request to the PIN GW, the PIN element may perform PINGW discovery and selection based on the received PIN GW ID. PIN GW discovery and selection may include, for example, proximity discovery. For example, the PIN GW may broadcast a notification message (e.g., including the PIN GW ID in the notification message) over a radio interface. PIN elements within a proximity range may receive the notification message. The PIN element may be considered to have discovered the PIN GW after having received the notification message. If the PIN element has discovered multiple PIN GWs, the PIN element may select a PIN GW to access.

[0140] In an example method for PEMC to establish connectivity, the PEMC may receive an indication of security parameters for local connectivity from a PIN GW and may send a PIN ID, an ID of a PIN GW, a connectivity type, and / or an indication of security parameters for local connectivity to a PIN element.

[0141] In an example method for a PIN element to establish connectivity, the PIN element may receive from the PEMC a PIN ID, an ID of a PIN GW, a connectivity type, and an indication of security parameters for local connectivity. The PIN element may discover and select a PIN GW based on the received ID of the PIN GW. The PIN element may send an indication of a local connectivity request to the PIN GW, which may include the PIN ID, the ID of the PIN element, and / or a data delivery type. The local connectivity request may be protected by the received security parameters for local connectivity. The PIN element may receive an indication of a connectivity state of the local connectivity.

[0142] In an example method for a PIN GW to establish connectivity, the PIN GW may send an ID of the PIN GW and an indication of security parameters for local connectivity to the PEMC. The PIN GW may receive a local connectivity request from a PIN element. The PIN GW may determine whether local connectivity corresponding to the local connectivity request is available based on the security parameters for local connectivity. The PIN GW may send an indication of the connectivity status of the local connectivity to the PIN element. The PIN GW may send an indication of the PIN ID, an ID of the PIN element, an IP address used by the PIN element, and / or a RAT of the PIN element to the core network. The PIN GW forwards traffic received from the PIN element to the 5G core network, for example, via a control plane or a user plane according to the data delivery type.

[0143] Fig.11 is a sequence diagram illustrating example communications for local connectivity establishment between PIN element 1110 , PIN management element (PEMC) 1112 , PIN GW 1114 , and core network 1116 .

[0144] At 1120, PEMC 1112 receives a PIN connectivity policy for PIN management (e.g., as described in Figure 8 820 and 822 in ). In some embodiments, provisioning occurs between PEMC 1112 and CN (e.g., 5G CN) 1116 without involving PIN GW 1114. In some embodiments, the PIN connectivity policy for PIN management may include the PIN type. In some embodiments, the PIN connectivity policy for PIN management does not include CN connectivity parameters.

[0145] At 1122, PIN GW 1114 receives a PIN connectivity policy for PIN GW from CN 1116 (e.g., as in Figure 8 In some embodiments, the PIN connectivity policy for the PIN GW may include a PIN type. In some embodiments, the PIN connectivity policy for the PIN GW may include a CN connectivity parameter.

[0146] At 1124, PIN GW 1114 communicates security parameters for local connectivity to PEMC 1112 (eg, sends a message indicating security parameters for local connectivity).

[0147] At 1126, PEMC 1112 communicates the availability of local connectivity to PIN element 1110 (e.g., sends a message indicating the availability of local connectivity). PEMC 112 may broadcast this information (e.g., to all PIN elements in the PIN). The communication may indicate, among other things, a PIN ID, PIN type, PIN GW ID, connectivity type, and / or security parameters for local connectivity.

[0148] At 1128 , the PIN element 1110 performs a discovery process according to the received ID of the PIN GW and selects a PIN GW.

[0149] At 1130, PIN element 1110 transmits a local connectivity request to PIN GW 1114 (e.g., sends a message indicating the local connectivity request). In some embodiments, the communication indicates the PIN ID, PIN type, ID of the PIN element, and / or data delivery type. In some embodiments, the local connectivity request may be protected by security parameters for local connectivity.

[0150] At 1132, PIN GW 1114 communicates a local connectivity response (eg, sends a message indicating the local connectivity response) to PIN element 1110. In some embodiments, the communication indicates a connectivity status (eg, available or unavailable) of the local connectivity.

[0151] At 1134, the PIN GW may communicate the PIN element report (eg, send a message indicating the PIN element report) to the core network 1116. The communication may indicate the PIN ID, the ID of the PIN element, the IP address used by the PIN element, and / or the RAT of the PIN element, among other things.

[0152] At 1136, upon receiving traffic 1135 from the PIN element, the PIN GW 1114 forwards the traffic 1137 (e.g., traffic for the CN), such as 5G traffic, to the CN 1116 via a control plane or a user plane, for example, based on the data delivery type.

[0153] Fig.12 is a sequence diagram illustrating example communications for connectivity establishment between the PIN element 1210 , the PIN management element (PEMC) 1212 , the PIN GW 1214 , and the core network 1216 .

[0154] At 1220, PEMC 1212 receives a PIN connectivity policy for PIN management (e.g., as in Figure 8820 and 822 in ). In some embodiments, provisioning occurs between PEMC 1212 and CN (e.g., 5G CN) 1216 without involving PIN GW 1214. In some embodiments, the PIN connectivity policy for PIN management may include the PIN type. In some embodiments, the PIN connectivity policy for PIN management does not include CN connectivity parameters.

[0155] At 1222, PIN GW 1214 receives a PIN connectivity policy for PIN GW from CN 1216 (e.g., as in Figure 8 In some embodiments, the PIN connectivity policy for the PIN GW 1214 may include a PIN type. In some embodiments, the PIN connectivity policy for the PIN GW includes a CN connectivity parameter.

[0156] At 1224, the PIN element 1210 may establish a connection with the PEMC 1212. The connection may be any suitable connection, such as a Bluetooth or WiFi connection. In some embodiments, operation 1224 is performed after operation 1220. In some embodiments, some operations or elements may be optional. For example, in some embodiments, the PEMC 1212 may create a PIN context locally and request the PIN GW to establish connectivity for the PIN, and then the PEMC waits for the PIN element to join. In another embodiment, after the PIN element joins the PIN, the PEMC 1212 requests the PIN GW 1214 to establish connectivity. Those skilled in the art will understand that various orders of these steps are contemplated.

[0157] In some embodiments, the PEMC 1212 determines to create a PIN and determines the PIN type. The PEMC 1212 may verify whether the PIN type is allowed (e.g., according to a PIN connectivity policy), whether the number of PIN elements to be included in the PIN has reached a PIN size limit, whether the PIN duration has expired, etc. Creating a PIN may include determining and / or storing PIN context information (e.g., a PIN ID, a list of PIN elements, a PIN type, etc.).

[0158] At 1226, PEMC 1212 communicates a PIN connectivity establishment request to PIN GW 1214 (e.g., sends a message indicating the PIN connectivity establishment request). The communication may indicate the PIN ID and PIN type of the PIN to be created. The communication may indicate the number of PIN elements, a list of PIN element IDs, and / or a PIN duration, etc.

[0159] At 1228, the PIN GW 1214 determines to establish or modify CN connectivity for the PIN based on the connectivity type of the PIN type indicated in the message of operation 1226. The PIN GW 1214 retrieves the CN connectivity parameters of the PIN type based on the corresponding PIN connectivity policy. In some embodiments, the PIN GW 1214 transmits a CN connectivity establishment or modification request to the core network (e.g., sends a message indicating the CN connectivity establishment or modification request). The communication may indicate, for example, a PDU session establishment or modification request. The communication may indicate, for example, a PIN ID, a PIN type of the PIN, and / or a number of PIN elements. In some embodiments, the core network transmits a CN connectivity establishment or modification response to the PIN GW (e.g., sends a message indicating the CN connectivity establishment or modification response). The communication may include, for example, a PDU session establishment and / or modification response.

[0160] At 1230, the PIN GW 1214 communicates security parameters for local connectivity to the PEMC 1212 (eg, sends a message indicating the security parameters for local connectivity).

[0161] At 1232, PEMC 1212 communicates the availability of local connectivity to PIN element 1210 (e.g., sends a message indicating the availability of local connectivity). PEMC 1212 may broadcast this information (e.g., to all PIN elements in the PIN). The communication may indicate, among other things, a PIN ID, PIN type, PIN GW ID, connectivity type, and / or security parameters for local connectivity.

[0162] At 1234, PIN element 1210 performs a discovery process and selects a PIN GW according to the received ID of the PIN GW. PIN GW discovery and selection may include, for example, proximity discovery. For example, PIN GW 1214 may broadcast a notification message (e.g., including the PIN GW ID in the notification message) over a radio interface. PIN elements within proximity may receive the notification message. The PIN element may be considered to have discovered the PIN GW after having received the notification message. If the PIN element has discovered multiple PIN GWs, the PIN element may select a PIN GW to access.

[0163] At 1236, PIN element 1210 communicates a local connectivity request to PIN GW 1214 (e.g., sends a message indicating a local connectivity request). In some embodiments, the communication indicates a PIN ID, a PIN type, an ID of a PIN element, and / or a data delivery type. In some embodiments, the local connectivity request may be protected by security parameters for local connectivity.

[0164] At 1238, PIN GW 1214 communicates a local connectivity response to the PIN element (eg, sends a message indicating the local connectivity response). In some embodiments, the communication indicates a connectivity status of the local connectivity (eg, available or unavailable).

[0165] At 1240, the PIN GW 1214 may communicate a PIN element report (eg, send a message indicating the PIN element report) to the core network 1216. The communication may indicate, among other things, a PIN ID, an ID of the PIN element, an IP address used by the PIN element, and / or a RAT of the PIN element.

[0166] At 1242, upon receiving traffic 1241 from the PIN element, the PIN GW 1214 forwards the traffic 1243 (eg, traffic for the CN, such as 5G traffic) to the CN via a control plane or a user plane, for example, based on the data delivery type.

[0167] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising a circuit, the circuit being configured to: Sending a personal internet of things (PIN) policy request to a core network (CN), wherein the PIN policy request indicates a PIN manager capability; receiving a PIN policy indicating authorized PIN types from the CN; sending a personal internet of things (PIN) connectivity policy request to the CN, wherein the PIN connectivity policy request indicates PIN gateway (GW) capabilities of the WTRU; receiving PIN connectivity policy information from the CN based on the PIN GW capability, wherein the PIN connectivity policy information indicates traffic forwarding parameters, a data network name (DNN), and slice information; receiving a PIN connectivity establishment request from a PIN element; Establishing a connection with the CN based on the DNN and the slice information; as well as Data is forwarded between the CN and the PIN element via the connection based on the traffic forwarding parameters.

2. The WTRU of claim 1, wherein the WTRU comprises a PIN GW.

3. The WTRU of claim 1 or 2, wherein the PIN connectivity policy information indicates at least one authorized PIN type, at least one connectivity type and / or at least one CN connectivity parameter.

4. The WTRU of claim 3, wherein the at least one CN connectivity parameter comprises at least one of: a public land mobile network (PLMN) identity (ID), a service and session continuity (SSC) mode, a packet data unit (PDU) session type, a data delivery mode, and a data transmission frequency.

5. The WTRU of any one of claims 1 to 4, wherein the PIN element comprises a PIN manager.

6. The WTRU of any one of claims 1 to 5, further comprising circuitry configured to receive local connectivity parameters for the PIN from the CN and send the local connectivity parameters to a PIN manager.

7. The WTRU of claim 6, wherein the local connectivity parameters indicate an L2 or L3 relay, an endpoint identifier, and / or an inter-radio access technology (RAT) communication strategy.

8. The WTRU of any one of claims 1 to 7, further comprising circuitry configured to receive security parameters for the PIN from the CN and send the security parameters to a PIN manager.

9. The WTRU of claim 8, wherein the security parameters include security parameters for local connectivity.

10. The WTRU of any one of claims 1 to 9, wherein the PIN policy further comprises a PIN size or a PIN duration.

11. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Sending a personal internet of things (PIN) policy request to a core network (CN), wherein the PIN policy request indicates a PIN manager capability; receiving a PIN policy indicating authorized PIN types from the CN; sending a personal internet of things (PIN) connectivity policy request to the CN, wherein the PIN connectivity policy request indicates PIN gateway (GW) capabilities of the WTRU; receiving PIN connectivity policy information from the CN based on the PIN GW capability, wherein the PIN connectivity policy information indicates traffic forwarding parameters, a data network name (DNN), and slice information; receiving a PIN connectivity establishment request from a PIN element; Establishing a connection with the CN based on the DNN and the slice information; as well as Data is forwarded between the CN and the PIN element via the connection based on the traffic forwarding parameters.

12. The method of claim 11, wherein the WTRU comprises a PIN GW.

13. The method according to claim 11 or 12, wherein the PIN connectivity policy information indicates at least one authorized PIN type, at least one connectivity type and / or at least one CN connectivity parameter.

14. The method of claim 13, wherein the at least one CN connectivity parameter comprises at least one of: a public land mobile network (PLMN) identity (ID), a service and session continuity (SSC) mode, a packet data unit (PDU) session type, a data delivery mode, and a data transmission frequency.

15. The method of any one of claims 11 to 14, wherein the PIN element comprises a PIN manager.

16. The method according to any one of claims 11 to 15, further comprising receiving local connectivity parameters for the PIN from the CN, and sending the local connectivity parameters to a PIN manager.

17. The method of claim 16, wherein the local connectivity parameters indicate an L2 or L3 relay, an endpoint identifier, and / or an inter-radio access technology (RAT) communication policy.

18. The method according to any one of claims 11 to 17, further comprising receiving security parameters for the PIN from the CN, and sending the security parameters to a PIN manager.

19. The method of claim 18, wherein the security parameters include security parameters for local connectivity.

20. The method of any one of claims 11 to 19, wherein the PIN policy further comprises a PIN size or a PIN duration.