Methods and apparatus to manage indirect communication via gateways in personal internet of things (IOT) networks

Abstract

A first PINE may receive, from a second PINE, a first request to establish communication between the first PINE and a third PINE. The request may include an indication of indirect communication through PEGC, an identity of the third PINE, a type of the third PINE, and QoS being requested. The first PINE may send, to a network, a second request to establish the service through PEGC. The second request may be sent in a NAS or in an application layer message. The first PINE may receive, from the network, routing information associated with the communication between the first PINE and the third PINE. The first PINE may send, to the second PINE, an indication of the successful establishment of the communication. The first PINE may be a PEGC. The first PINE may be a PEMC configuring a PEGC, wherein the PEGC may be identified in the routing information.

Description

METHODS AND APPARATUS TO MANAGE INDIRECT COMMUNICATION VIA GATEWAYS IN PERSONAL INTERNET OF THINGS (IOT) NETWORKSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 542,001 , filed October 2, 2023, the contents of which are incorporated herein by reference.BACKGROUND

[0002] Internet of things (loT) devices may be deployed in a private network environment, such as security sensor, smart lights, smart plugs, printers, and smartphones in a home or office environment. The loT devices may be managed by other devices in the network that implement management capabilities. The loT devices may communicate with each other directly or via other devices in the network that implement gateway capabilities.

[0003] A private network environment may be modelled as a personal loT network (PIN) comprising PIN elements (PINEs). In one example, PINEs may communicate with each other with the support of a cellular network, such as a 5G system (5GS). While many PINEs may not be able to communicate with the cellular network due to their limited capabilities, a sub-set of the PINEs in the PIN may be WTRUs (e.g , UEs) communicating with the cellular network (e.g., 5GS). These PINEs (e.g., UEs) may provide management and gateway capabilities for the other PINEs in the PIN.

[0004] A residential gateway may be a PINE with gateway capability (PEGC). A PEGC may enable the communication between two PINEs and the communication between a PINE and the network (e.g., an application server in the network). The communication within a PIN may be a direct connection between PINEs, or a connection via a PEGC or via a PEGC and the 5GS The communication outside a PIN with an application server outside the PIN, may be via a PEGC and the 5GC A PINE with management capability (PEMC) may provide a means for an authorized administrator to configure and manage the PIN. A residential gateway acting as a PEGC may also implement management functions and operate as a PEMC.SUMMARY

[0005] In a PIN, PEGC and PEMC functionalities may be implemented in WTRUs (UEs). PEGCs and PEMCs may support communication with the 5G core network using 5G-NR radio interface. PEGCs and PEMCs may also communicate with each other using ProSe direct communication over a sidelink channel. As PEGCs may not have information on traffic rules and routing for PINEs in a PIN, a need was identified to define mechanisms to establish indirect PINE-to-PINE communication and PINE-to-network communication. The procedures may be initiated by a PINE or by the network. The procedures include mechanisms for the network to configure PEGCs, for PEMC to configure PEGCs, and for PEGCs to configure PINEs. The mechanisms may be based on user plane communication or control plane signaling. User plane mechanisms may involveapplication layer messages between entities, such as between an application server and a PEGC application client. Control plane mechanisms may involve control plane messages such as NAS messages.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0007] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0008] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0009] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0010] FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0011] FIG. 2 shows a simplified diagram of a personal loT network (PIN);

[0012] FIG. 3 illustrates an example of a direct communication between PINEs;

[0013] FIG. 4 illustrates an example of an indirect communication between PINEs via one or morePEGCs;

[0014] FIG. 5 illustrates an example of an indirect communication between PINEs via a PEGC and including a 5GS;

[0015] FIG. 6 depicts an example of a 3GPP PIN application (PINAPP) architecture;

[0016] FIG. 7 illustrates an example call flow of a PINE-initiated user plane procedure via PEGC for establishment of inter-PINE indirect communication;

[0017] FIG. 8A illustrates an example call flow of a PINE-initiated user plane procedure via PEMC for establishment of inter-PINE indirect communication;

[0018] FIG. 8B illustrates two examples of a PIN server configuring an inter-PINE indirect communication in a PIN over the user plane;

[0019] FIG. 9 illustrates an example call flow of a PINE-initiated control plane procedure via PEGC for establishment of inter-PINE indirect communication;

[0020] FIG. 10A illustrates an example call flow of a PINE-initiated control plane procedure via PEMC for establishment of inter-PINE indirect communication;

[0021] FIG. 10B illustrates an example of a PIN server configuring an inter-PINE indirect communication in a PEGG and a PEMC over the control plane;

[0022] FIG. 11 A illustrates an example call flow of a network-initiated user plane procedure where an AF initiates the procedure;

[0023] FIG. 11 B illustrates two examples of an AF configuring an inter-PINE indirect communication in a PIN over the user plane;

[0024] FIG. 12A illustrates an example call flow of a network-initiated control plane procedure where the AF initiates the procedure;

[0025] FIG. 12B illustrates two examples of an AF configuring an inter-PINE indirect communication in a PIN over the control plane;

[0026] FIG. 13 depicts an example of a flow-chart of the PEMC process during PINE-initiated user plane procedure for establishment of inter-PINE indirect communication; and

[0027] FIG. 14 depicts an example of a flow-chart of the PEGG process during PINE-initiated control plane procedure for establishment of inter-PINE indirect communication.DETAILED DESCRIPTION

[0028] The following acronyms may be used in this specification:5GC 5G Core network5GS 5G SystemAC Application ClientAF Application FunctionAMF Access and Mobility FunctionAS Application ServerCAPIF Common API Framework for 3GPP northbound APIs loT Internet of ThingsMM Mobility ManagementN3QAI Non-3GPP QOS Assistance InformationNAS Non-Access StratumNEF Network Exposure FunctionNLSP Network local switch for PINP2N PINE-to-NetworkP2P PINE-to-PINEPDB Packet Delay BudgetPEGC PIN Elements with Gateway CapabilityPEMC PIN Elements with Management CapabilityPIN Personal loT NetworksPINE PIN ElementRAN Radio Access NetworkRRC Radio Resource ControlSM Session ManagementSMF Session Management FunctionUDM User Data ManagementUDR User Data RepositoryUE User EquipmentUPF User Plane Function

[0029] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 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), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0030] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill be appreciated 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 a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in anindustrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0031] The communications systems 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 the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, 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.

[0032] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. 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 licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one 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 desired spatial directions.

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

[0034] More specifically, as noted above, the communications 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, and the like. 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), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

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

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

[0037] 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 implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by 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 , an eNB and a gNB).

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

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

[0040] 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 varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communicationwith 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 be utilizing a NR radio technology, the ON 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0041] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide 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), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications 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.

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

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

[0044] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0046] Although the transmit / receive element 122 is depicted in FIG. 1 B 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.

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

[0048] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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 the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0049] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the 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, and the like.

[0050] 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 over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated thatthe WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment

[0051] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a handsfree headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.

[0052] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e g., associated with particular subframes for both the 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 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).

[0053] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to 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.

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

[0055] Each of the eNode-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 the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

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

[0057] The MME 162 may be connected to each of the eNode-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, and the like. 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

[0058] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0059] 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.

[0060] 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 communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

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

[0062] In representative embodiments, the other network 112 may be a WI XN.

[0063] A WL XN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example,where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0064] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, 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., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in 802.11 systems. For CSMA / CA, the STAs (e.g., every 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.

[0065] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0066] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0067] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g , only support for) certain and / or limitedbandwidths The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0068] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest 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, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0069] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

[0070] FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an 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.

[0071] 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, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may 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 unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

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

[0073] 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 the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0074] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

[0076] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like The AMF 182a, 182b may provide a control plane function forswitching 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.

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

[0078] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The 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, and the like.

[0079] 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 serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0080] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0081] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, 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. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network The emulation device maybe directly coupled to another device for purposes of testing and / or performing testing using over-the-air wireless communications.

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

[0083] Below are listed the terms and definitions that are used herein.

[0084] Personal loT Network (PIN): A configured and managed group of PIN Elements (PINEs) those are able to communicate with each other directly or via PIN Elements with Gateway Capability (PEGC), communicate with 5G network via at least one PEGC, and managed by at least one PIN Element with Management Capability (PEMC)

[0085] PIN Element (PINE): A UE or non-3GPP device that can communicate within a PIN (via PIN direct connection, via PEGC, or via PEGC and 5GC), or outside the PIN via a PEGC and 5GC.

[0086] PIN Element with Gateway Capability (PEGC): A PIN Element (PINE) with the ability to provide connectivity to and from the 5G network for other PIN Elements, or to provide relay for the communication between PIN Elements

[0087] PIN Element with Management Capability (PEMC): A PIN Element (PINE) with capability to manage the PIN.

[0088] PI NE-to-PI NE communication: communication between two PINEs which may use PI N E-to-PI N E direct communication or PINE-to-PINE indirect connection

[0089] PINE-to-PINE direct connection: the connection between two PIN Elements without PEGC, any 3GPP RAN or core network entity in the middle.

[0090] PINE-to-PINE indirect connection: the connection between two PIN Elements via PEGC or via UPF.

[0091] PINE-to-PINE routing: the traffic is routed by a PEGC between two PINEs, the two PINEs direct connect with the PEGC via non-3GPP access.

[0092] PINE-to-Network routing: the traffic is routed by a PEGC between PINE and 5GS, the PINE connects directly with the PEGC via non-3GPP access separately.

[0093] N3QAI : Non 3GPP QOS Assistance Information

[0094] A personal loT network (PIN) may consist of devices known as PIN elements (PINE) wherein one or more PINEs may provide gateway and / or routing functionality, known as the PIN element with gatewaycapability (PEGC); and one or more devices that may provide PIN management functionality, known as the PIN element with management capability (PEMC). A PINE may or may not support 5G communications, and it may or may not be a UE.

[0095] FIG. 2 shows a simplified diagram of a personal loT network (PIN).

[0096] A PIN 2001 comprises a group of PIN elements (PINEs) 2002 A PINE 2002 may be a 3GPP device (e g., UE) or a non-3GPP device. PINEs 2002 may be able to communicate with each other either directly 2003 or via PIN elements with gateway capability (PEGC) 2004, 2005. PINEs 2002 may be able to communicate with a 5G system (5GS) 2006 via at least one PEGC 2005, 2007. PINEs 2002 and may be managed by at least one PIN element with management capability (PEMC) 2008.

[0097] PEGCs 2005 and PEMC 2008 are PINEs (e.g , UEs) that implement extra functionality. A PEGC 2005 is a PINE (e.g., UE) with the ability to provide relay functionality for the communication between PINEs 2004 and / or connectivity to and from the 5GS 2005 to PINEs 2004, 2007. A PEMC 2008 is a PINE (e.g., UE) with capability to manage a PIN and its PINEs.

[0098] A PI NE-to-PINE communication refers to the communication between two PINEs. As illustrated in FIG. 2, a PINE-to-PINE communication may be a direct PINE-to-PINE communication In this case, the communication between two PINEs is enabled using a direct connection 2003, 2009, i.e., a connection without another PINE and / or network in the middle. The PIN elements may use non-3GPP access (e g., WIFI, Bluetooth) for direct communication 2003. The PEMC and PEGC may use 5G ProSe direct communication (e g. sidelink channels) for direct communication with each other 2009.

[0099] An indirect PINE to PINE communication involves another PINE, e.g., a PEGC 2005, or another PINE (e.g., PEGC) 2005 and a network, e.g., 5GS 2006 The communication may traverse a radio access network (RAN) entity, such as a gNB, or a RAN entity and a CN entity, such as a UPF. PEGCs may also enable the communication between a PINE and a network, e.g., PINEs communicate to PEGCs and PEGCs routes the information to the network (5GS). A communication between a PINE and a network (e.g., 5GS) is referred to an indirect connection through a PEGC. In one example the indirect connection may be facilitated by a WiFi access point (AP) connected to a 5G core (5GC) network.

[0100] A PINE-to-PINE routing refers to a routing performed by a PEGC between two PINEs, with each PINE directly connecting to the PEGC via non-3GPP access. A PINE-to-network routing refers to a routing performed by a PEGC between a PINE and a 5GS, with the PINE directly connecting to the PEGC via non- 3GPP access

[0101] The indirect communication via a PEGC may be managed within the PIN by the PEMC. In one example, there may be one or more PEGCs and one or more PEMCs in a PIN. In one example where there are a plurality of PEMCs in a PIN and one of the PEMCs may control the PIN. In one example, a PEGC and a PEMC in the same PIN may subscribe to the same PLMN or (S)NPN. In one example, a single PEGC may support more than one PIN at a time.

[0102] Different use cases may be applicable in different PINs, or a PIN may support more than one use case.

[0103] FIG. 3 illustrates an example of a direct communication between PINEs. In this example, PINE-1 3001 and PINE-2 3002 communicate with each other directly, i e., without connecting via a PEGG 3003.

[0104] FIG. 4 illustrates an example of an indirect communication between PINEs via one or more PEGCs.

[0105] In example (a) in FIG. 4, 4001, PINE-1 4002 and PINE-2 4003 may not able to reach each other directly. In this case a PEGC 4004 may relay the communication between the PINEs. In example (b) in FIG. 4, 4005, PINE-1 4006 and PINE-2 4007 may not able to reach each other directly and may not be able to reach the same PEGC directly. In this case, PINE-1 4006 may communicate to PEGC-1 4008 and PINE-2 4007 may communicate directly with PEGC- 2 4009. PEGC-1 4008 and PEGC-2 4009 communicate directly with one another to relay the information of PINE-1 4006 and PINE-2 4007.

[0106] FIG. 5 illustrates an example of an indirect communication between PINEs via a PEGC and including a 5GS.

[0107] In example (a) in FIG. 5, 5001, PINE-1 5002 and PINE-2 5003 may communicate with each other via one PEGC 5004, and the data traverses the 5GC 5005 . In example (b) in FIG. 5, 5006, PINE-1 5007 and PINE-2 5008 may not able to reach each other directly and may not be able to reach the same PEGC directly. In this case, PINE-1 5007 may communicate to PEGC-1 5009 and PINE-2 5008 may communicate directly with PEGC- 2 5010. In this case, PEGC-1 5009 and PEGC-2 5010 may not able to reach each other directly and may communicate with one another indirectly via the 5GC 5011 another to relay the information of PINE- 1 5007 and PINE-2 5008.

[0108] As exemplified above, PINEs may interact with each other through one or more PEGCs. Routing PINE communication through PEGCs may be beneficial; however, PEGCs in a PIN may not have any information about traffic handling rules during communication between two PINEs, e.g., PINE-1 and PINE-2. One example of traffic handling rules if routing information necessary to configure a path between two PINEs. The traffic handling rules for communication within the same PIN may be different from the traffic handling rules for communication across different PINs. Moreover, different PEGCs may be served by different PLNMs and thus may have different rules. Finally, aspects such as configuration of traffic handling rules, authorization and control in a PIN still need to be specified.

[0109] A PIN may also have a PIN application server (AS) that may comprise an application function (AF). The AF may be deployed by a mobile operator or by an authorized third party. When the AF is deployed by a third party, the interworking with the 5GS may be performed via the network exposure function (NEF).

[0110] A need was identified to define mechanisms to establish indirect PI NE-to-PINE communication and indirect PINE-to-network communication. Solutions for PINE-initiated and network-initiated are described. In one example, an AF may interact with a network exposure function (NEF) to trigger the procedure. The solutions described include mechanisms to configure PEGCs and mechanisms for PEGCs to configure PINEs.The mechanisms to configure PEGCs may be classified as user plane or control plane mechanisms. User plane mechanisms may involve application layer messages between entities and control plane mechanisms may involve control plane messages, such as NAS messages. A PINAPP architecture is used herein to provide examples that facilitate the description of the main concepts of the invention. The PINAAP architecture is as defined by the 3GPP standards bodies. A 5G system (5GS) is assumed, with a 5G-NR radio interface and a 5GC network.

[0111] FIG. 6 depicts an example of a 3GPP PIN application (PINAPP) architecture.

[0112] PINE A 6001 , PINE B 6002, and PINE C may be operating in a PIN 6004. Each PINE 6001, 6002, 6003, may comprise a PIN client 6005, 6006, 6007 and support a PIN application (PINAPP) via an application client 6008, 6009, 6010.

[0113] Also operating in the PIN 6004, are a PEGG 6011 comprising a PIN gateway (PEGG) client 6012, and a PEMC 6013 comprising a PIN management client 6014. A PIN server 6015 and an application server (AS) 6016 are located in a Data Network (DN) 6017. The elements of the PIN 6004 communicate with the DN 6017 via a 3GPP core network 6018, e.g., 5GC. These elements may enable a desired functionality in a PIN.

[0114] Procedures for configuration of the traffic handling rules may be initiated by a PINE or by an application function (AF) in the AS PEGC and PEMC may be implemented in a UE. The PIN gateway client 6012 in the PEGC 6011 and the PIN management client 6014 in the PEMC 6013, may be involved in the configuration of traffic rules.

[0115] Procedures may be executed via the control plane or the user plane. For control plane procedures, the Uu interface 6019 may be used by the PEGC client 6012 to communicate with the 5GS, more specifically, the 5GC network 6018. The communication maybe done using NAS signaling 6020 towards the AMF 6021 . An AF in the data network may communicate with the 5GC 6018 via the NEF 6022. For user plane procedures, the PIN-7 interface 6023 may be used by the PEGC client 6012 to communicate with the PIN server 6015. This communication may be realized through the UPF 6024.

[0116] In PINE-initiated procedures, after receiving a request from a PINE, the PEGC client may contact the PIN server to request traffic handling rules information.

[0117] In case a user plane procedure is used, the PEGC client may send a PIN Indirect Communication Setup Request message over the PIN-7 interface 6019. The PIN server may then send a response on Communication Setup Information message to the PEGC client This may be realized using an application layer mechanism, i.e., over the user plane.

[0118] In case a control plane procedure is used, the traffic handling rules may be directly configured by the 5GS in the PEGC. In one example, a trigger may be configured at the PEGC MT / UE to request to the 5GS, over the control plane (e g., NAS signaling), for the traffic handling rules. On the uplink direction (PEGC -> NW), the PEGC client may send a PIN Indirect Communication Setup Request message to the network. The request may comprise, e.g., New request type, End Point IDs / PINE IDs, PINE types, QoS Requirements, andList of Configured PEGCs and Connected PINEs. On reception of these parameters, the PEGC MT may provide the information to the PEGC client to perform the configuration.

[0119] The same procedures may apply to a PEMC application client: The PEMC application layer may contact the PIN server for traffic handling rules by sending a PIN Indirect Communication Setup Request message. The PIN server may send the Communication Setup Information message to the PEMC client using an application layer mechanism, i.e., over the user plane. In one example, a trigger at the PEMC MT may be configured to request the 5GS, over the control plane, e.g., via NAS signaling, for the traffic handling rules. Traffic handling rules may be delivered via control plane, e.g., NAS signaling to the PEMC by the 5GC In this case, the PEMC may further configure the PEGC(s) in the PIN. For instance, upon reception of the parameters, the PEMC client may provide the information to the PEGC client for configuration.

[0120] In a network-initiated procedure, an AF may initiate the configuration procedure. The AF may request, via NEF, for the 5GC to provide traffic handling rules for the PIN. The 5GC may provide the information, e.g., in a PIN Indirect Communication Configuration Request / Response message to the AF, via NEF. The AF may then configure the PEMC / PEGC.

[0121] FIG. 7 illustrates an example call flow of a PINE-initiated user plane procedure via PEGC for establishment of inter-PINE indirect communication.

[0122] In step 1 , 7001 , a PIN client in a PINE may decide to communicate with another PINE. If authorized, the PIN client may send a request to a PEGC client for the establishment of indirect communication with another PINE, by sending the Inter PINE Communication Setup Request message. The PIN client may indicate that indirect communication through the PEGC is requested by setting the request type field to Indirect Communication. Optionally, if the request type field is not specified, the PEGC may decide, e.g., based on policy configuration, what type of communication setup may be allowed for the PINE. The message may indicate the destination PINE, identified by PINE ID and IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message may indicate the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may include the requested QoS by the origination PINE, such as the desired bandwidth, delay, and jitter. The requested QoS may influence the PEGC’s decision about the type of communication path between two PINEs, e.g., indirect or via 5GS.

[0123] In step 2, 7002, after receiving the Inter PINE Communication Setup Request message, the PEGC client may check the request type field If the request type is present and set to indirect communication, the PEGC may verify if the PINE is allowed to establish an indirect communication with the destination PINE. If the request type is not present, the PEGC may decide to establish an indirect communication between the two PINEs based on PINE policy and requested QoS In order to establish an indirect communication between two PINEs, the PEGC may request traffic handling rules such as path configuration and routing information from the 5GS by sending a PIN Indirect Communication Setup Request message to the PIN server, using an application layer mechanism, i.e., over the use plane.

[0124] In the PIN Indirect Communication Setup Request message, the PEGC may include: 1) request type as “Indirect through PEGC”; 2) origination and destination PINE IDs; 3) origination and destination PINE types such as sensor, video, audio etc.; 4) requested QoS between the PINEs e.g , bandwidth, delay, jitter, etc.; 5) list of PEGCs available PEGCs (which may be selected by the PEGC); and 6) list of connected PINEs in the PIN

[0125] In step 3, 7003, the 5GS / PIN server receives the PIN Indirect Communication Setup Request message and may validate the request by verifying against the PIN policy and PINE subscription, which will identify if the PINE is allowed to communicate with the destination PINE using indirect communication. If allowed, the PIN server may determine a routing information to establish the inter PINE indirect communication. It is possible that inter PINE communication may be setup through one or more PEGC. The PIN server may provide traffic handling rules such as path configuration and routing information to one or more PEGCs to establish the end to end path between two PINEs.

[0126] Step 4, 7004, may be executed when the origination PINE and destination PINE are owned by a different providers, are in different domains, and are managed by different PIN servers If the destination PINE is in a different domain from the origination PINE, then the PIN server of the origination PINE may contact the PIN server of the destination PINE to obtain valid routing information between PINE-1 and PINE-2, through one or more PEGC.

[0127] In step 5, 7005, the PIN server may respond to the PIN Indirect Communication Setup Request message sent by the PEGC by sending PIN Indirect Communication Setup Response message using an application layer mechanism, i.e., over the user plane This message may comprise traffic handling rules, routing, forwarding, and path setup information from the origination PINE to the destination PINE, through one or more PEGCs. The message may also include a set of traffic handling rules, such as the IP address and port number where the traffic should be routed. For example, assuming PINE-1 may communicate with PINE-2 through PEGC-1 , PEGC-2 and PEGC-3, then the information may be: If origination PINE == PINE-1 and destination PINE == PINE-2; PEGC-1 : Route to IP addressl , port#; PEGC-2: Route to IP address2, port#; and PEGC-3: Route to destination port#. The rule may be provided to one or more PEGCs, and in this example the routing rule may be sent to PEGC-1 , PEGC-2 and PEGC-3.

[0128] In step 6, 7006, the PEGC client may respond to the Inter PINE Communication Setup Request message by sending an Inter PINE Communication Setup Response message indicating success or failure to the PINE

[0129] FIG. 8A illustrates an example call flow of a PINE-initiated user plane procedure via PEMC for establishment of inter-PINE indirect communication.

[0130] In step 1 , 8001, the PIN client in a PINE, decides to communicate with another PINE If authorized, the PIN client may request the PEMC client to establish inter PINE communication, by sending the Inter PINE Communication Setup Request message. The PIN client may indicate that indirect communication through aPEGC is requested by setting the request type to “Indirect through PEGC”. Optionally, if the request type is not specified, the PEMC client may decide what type of communication setup is allowed for the PINE, based on policy configuration. The message may indicate the destination PINE, identified by PINE ID and IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message may also indicate the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may also include the requested QoS by the origination PINE, such as the desired bandwidth, delay, and jitter. The requested QoS may influence PEMC’s decision regarding the type of communication path between two PINEs, e.g., “Indirect through PEGC” or “through 5GS.”

[0131] In step 2, 8002, after receiving the inter PINE communication request from a PINE, the PEMC client may check the request type field. If the request type is present and set to “Indirect through PEGC”, the PEMC may verify if the PINE is allowed to establish an indirect communication with the destination PINE. If the request type is not set, the PEMC may decide to establish an indirect communication between the two PINEs based on PINE policy and requested QoS. The PEMC client may select available PEGCs in the PIN which may support indirect communication between the PINEs.

[0132] In step 3, 8003, to establish an indirect communication between two PINEs, the PEMC client may request the traffic handling rules such as path configuration and routing information from the PIN server / 5GS. The PEMC client may send PIN Indirect Communication Setup Request message to the PIN server using an application layer mechanism. The PEMC client indicates 1) request type as “Indirect through PEGC”, 2) origination and destination PINE IDs; 3) origination and destination PINE types such as sensor, video, audio, etc.; 4) requested QoS between the PINEs e.g., bandwidth, delay, and jitter; and optionally: 5) a list of PEGCs in the PINE which are available and maybe selected by the PEGC and 6) a list of connected PINEs in the PIN

[0133] In step 4, 8004, the PIN server / 5GS receives the PIN Indirect Communication Setup Request message and may validate the request by verifying against PIN policy and PINE subscription whether the PINE may be allowed to communicate with the destination PINE using indirect communication. If allowed, the PIN server determines routing information from 5GS to establish inter PINE indirect communication between the indicated origination and destination PINEs, identified by PINE ID and PINE type. The PIN server may also specify the agreed QoS to the 5GS, and the 5GS may select the route which may support the requested QoS. The PIN server may select a list of PEGCs provided by the PEMC that may support indirect communication, based on policy. The selected list may also be provided to the 5GS as the preferred PEGCs for indirect communication. The 5GS may decide if indirect communication may be supported through the PEGCs or if a different PEGC should be selected

[0134] The PIN server considers the list of connected PINEs and may select possible PEGCs and the QoS that may be supported for indirect communication. It is possible that inter PINE communication may be established through one or more PEGC. The 5GS may provide the PIN server with a list of PEGCs and the traffic handling rules such as path configuration and routing information to establish the indirect communication. The PIN server may provide the traffic handling rules such as path configuration and routing information to oneor more PEGCs to establish the end to end path between two PINEs. These message happen using an application layer mechanism and application layer protocols.

[0135] Step 5, 8005, may be executed when the origination PINE and the destination PINE may be owned by different providers, are in different domains, and may be managed by different PIN servers. The PIN server may identify, based on the PINE ID and PINE Type, that the origination PINE and the destination PINE are in different domains. The PIN server of the origination PINE may identify the destination PIN server of the destination PINE. The origination PIN server may contact the destination PIN server to obtain valid traffic handling rules such as path configuration and routing information between PINE-1 and PINE-2, through one or more PEGCs.

[0136] FIG. 8B illustrates two examples of a PIN server configuring an inter-PINE indirect communication in a PIN over the user plane.

[0137] In one example (example 1 in FIG. 8B), the PIN server responds with a PIN Indirect Communication Setup Response message to the PEMC client, in step 6-1, 8006-1. This message may include traffic handling rules such as routing, forwarding, and path setup information from the origination PINE to destination PINE, through one or more PEGCs. The message may also include a set of rules, such as the IP address and port number where the traffic should be routed. For example, assuming PINE-1 may communicate with PINE-2 through PEGC-1 , PEGC-2 and PEGC-3, then the information may be: If origination PINE == PINE-1 and destination PINE == PINE-2; PEGC-1 : Route to IP addressl , port #X; PEGC-2: Route to IP address2, port#; and PEGC-3: Route to destination port#. The rule set may be provided to one or more PEGCs, in this example the routing rule may be sent to PEGC-1 , PEGC-2 and PEGC-3

[0138] The PEMC client may store the traffic handling rules such as path configuration and routing information. The PEMC may identify the PEGC in the list. The listed PEGCs may be verified by the PEMC and then checked whether they PEGC are still available to route the traffic. The PEMC may start preparing to inform the PEGCs about the routing rule.

[0139] In step 7-1 , 8007-1, the PEMC client may send Configure PEGC Request message, which may include the routing rule to each identified PEGC client from step 6a (e.g., PEGC-1 , PEGC-2, PEGC-3). The routing rule may indicate the origination and the destination PINE ID, IP address, port#, and related traffic handling rules such as path configuration and routing information. The PEGC may configure the traffic handling rules such as path configuration and routing information for the origination and destination PINE.

[0140] In step 8-1 , 8008-1, if the PEGC can successfully configure the traffic handling rules such as path configuration and routing information for the origination and the destination PINE, it responds by sending a Configure PEGC Response message to the PEMC client, indicating success or failure of the configuration procedure.

[0141] In step 9-1 , 8009-1, the PEMC client responds to the Inter PINE Communication Setup Request message to the PINE, by sending a message Inter PINE Communication Setup Response message indicating success or failure of the inter PINE communication setup procedure.

[0142] In another example (example 2 in FIG. 8B), as an alternative, the PN server may create a traffic handling rules such as path configuration and routing information for indirect communication between PINE-1 and PINE-2, in step 6-2, 8006-2. The PIN server may identify each involved PEGC and may directly send a Configure PEGC Request message to the identified PEGCs. The message may include the routing rule, which may include the origination and the destination PINE ID, IP address, port#, and related traffic handling rules such as path configuration and routing information for that PEGC. The PEGC may configure the traffic handling rules such as path configuration and routing information for the origination and the destination PINE.

[0143] In step 7-2, 8007-2, if the PEGC can successfully configure the traffic handling rules such as path configuration and routing information for the origination and the destination PINE, it may respond by sending a Configure PEGC Response message to the PIN server, indicating success or failure of the configuration procedure.

[0144] In step 8-2, 8008-2, the PIN server may send a PIN Indirect Communication Setup Response message to the PEMC client, which may indicate success or failure of the indirect communication setup procedure.

[0145] In step 9-2, 8009-2, the PEMC client may respond to the Inter PINE Communication Setup Request message by sending a response Inter PINE Communication Setup Response message to the PINE, indicating success or failure of the inter PINE communication setup procedure.

[0146] In another exemplary method, traffic handling for indirect PINE communication may be obtained using a combination of application layer mechanism and network signaling. Preferably, a PINE may request for communication setup using application layer mechanism or PEGC / PEMC obtains the information using network signaling.

[0147] FIG. 9 illustrates an example call flow of a PINE-initiated control plane procedure via PEGC for establishment of inter-PINE indirect communication.

[0148] In step 1 , 9001, the PIN client in a PINE may decide to communicate with another PINE. If authorized, the PIN client may request the PEGC client (TE part of PEGC) to establish inter PINE communication, by sending the Inter PINE Communication Setup Request message. The PIN client may indicate that indirect communication through PEGC is requested by setting the request type to “Indirect through PEGC’’. Optionally, if request type is not specified, the PEGC client may decide, based on policy configuration, what type of communication setup may be allowed for the PINE The message may indicate the destination PINE, identified by PINE ID and the IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message may also indicate the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may include a requested QoS by the origination PINE, such asthe desired bandwidth, delay, and jitter. The requested QoS may influence the selection of the communication path, e.g., for indirect communication through PEGG, the selection of which PEGC may support the requested QoS or if the requested QoS cannot be supported using indirect communication, if the PINE may use the 5GS instead.

[0149] In step 2, 9002, the PEGC client, after receiving the Inter PINE Communication Request message from a PINE, may check the request type field. If the request type is present and set to “Indirect through PEGC”, the PEGC client may verify if the PINE is allowed to establish an indirect communication with the destination PINE. If the request type is not set, the PEGC client may establish an indirect communication between the two PINEs based on the PINE policy and requested QoS. The PEGC client (TE) may send a request to the PEGC MT to obtain information about setting up Inter PINE communication from the 5GS. The PEGC client sends Get Inter PINE Communication Setup Information (IPCSI) message and may indicate the PIN ID, which includes the PINE and PEGC, the origination and destination PINE IDs to identify the PINE, the end point identifier of the origination and destination PINE such as IP address, GPSI, and MAC address, the requested QoS by PINE, and possibly a list of PEGCs, identified by PEGC ID, UE ID, authorized and available to support PINE indirect communication.

[0150] In step 3, 9003, the PEGC MT sends the Inter PINE Communication Setup Information IPCSI message to the 5GS via control plane, e.g., using UL NAS signaling message. The PEGC MT may send to the AMF the Inter PINE Communication Setup Information message via the UL NAS signaling, providing PIN ID, PINE ID, PIN end point identifiers, requested QoS, list of available and authorized PEGCs along with the new flag i.e , PIN Indirect Communication Setup Request.

[0151] In step 4, 9004, the AMF may retrieve the Inter PINE communication setup information, including the identification of the origination and destination PINEs which may be identified by the PINE IDs, the end point identifiers, such as IP address, port#, GPSI, and the PIN where they are located, which may be identified by PIN ID. The AMF may retrieve updated User Equipment Route Selection Policy (URSP) from the UDM / UDR / PCF / PIN Server, as per the requested PIN ID, PINE ID, authorized PEGCs as per the provided UE ID (SUPI / GPSI) and generate the Inter PINE Communication Setup Information (IPCSI) message to be provided to the relevant PEGC MTs.

[0152] The Indirect PINE Communication Setup Information message may include information regarding setting up side link communication between PEGCs. E.g., the sidelink setup information may be sent as part of the updated URSP. PEGC may use this information to establish sidelink communication with another PEGC. If the PINEs are in different PIN, the PIN server serving the different PIN may be identified based on PIN ID and PINE ID. Then the destination PIN server may be requested to provide additional information on how to reach the destination PINE.

[0153] In step 5, 9005, the 5GS / AMF / PCF may send Inter PINE Communication Setup Information (IPCSI) message to the requesting PEGC MT TheAMF / PCF, upon reception of the new / updated IPCSI message, maypass on this information via the control plane, e.g., DL NAS transport message, to the PEGG MTs listed in the IPCSI message. The UDM may pass the IPCSI information to the AMF via constructing / updating the UPU as per the received IPCSI message, which may be transparently forwarded by the AMF to the PEGG MT. The PCF may construct new URSPs as per the received IPCSI information from the UDM / UDR and provide those to the PEGG MT as UE policies via AMF as DL NAS transport message The AMF might construct an entirely new information element to transport the IPCSI message to the PEGC MT. The information flow from the AMF to the PEGC MT may be carried over other control plane NAS signaling messages as well. If the IPCSI message contains more than one PEGC, then the AMF / PCF, upon reception of the new / updated IPCSI message, may pass on this information via the DL NAS signaling (e.g., DL NAS transport message) to all the PEGC MTs listed in the IPCSI message.

[0154] In step 6, 9006, the PEGC MT may pass on IPCSI message to the PEGC client (TE). The PEGC client may configure forwarding rules based on the information received from PEGC MT.

[0155] In step 7, 9007, the PEGC client responds to the Inter PINE Communication Setup Request message to the PINE, by sending the Inter PINE Communication Setup Response message, indicating success orfailure of the inter PINE communication setup procedure.

[0156] FIG. 10A illustrates an example call flow of a PINE-initiated control plane procedure via PEMC for establishment of inter-PINE indirect communication.

[0157] In this example, a combination of user plane and control plane may be used, i.e., application layer mechanism and NAS signaling. Preferably, a PIN client in a PINE requests indirect communication setup with another PINE to the PEMC client. The PINE request the PEMC client for inter PINE communication setup information, and the PEMC is assumed to be responsible for obtaining the information and configuring PEGC.

[0158] In step 1 , 1001, the PIN client in a PINE may decide to communicate with another PINE. If authorized, the PIN client requests the PEMC client (TE part of the PEMC) to establish inter PINE communication, by sending the Inter PINE Communication Setup Request message. The PIN client may indicate that indirect communication through PEGC is requested by setting the request type to “Indirect through PEGC”. Optionally, if the request type is not specified, the PEMC client may decide, based on policy configuration, what type of communication setup is allowed for the PINE. The message may also indicate the destination PINE, identified by PINE ID and IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message may indicate the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may also include the requested QoS by the origination PINE, such as the desired bandwidth, delay, and jitter. The requested QoS, may influence selection of communication path, e.g., which PEGC may be selected to support the requested QoS or if the requested QoS cannot be supported using indirect communication, if the 5GS may be used.

[0159] In step 2, 1002, the PEMC client, after receiving the inter PINE communication request from a PINE, may check the request type field. If the request type is present and set to indirect communication, the PEMCclient may verify if the PINE is allowed to establish an indirect communication with the destination PINE. If the field request type is not set, the PEMC client may decide to establish an indirect communication between the two PINEs based on PINE policy and requested QoS. The PEMC client (TE) may send a request to the PEMC MT to obtain information regarding setting up inter PINE communication via 5GS. The PEMC client may send Get Inter PINE Communication Setup Information (IPCSI) message and indicate the PIN ID, which includes the PINE and PEGC, the origination and destination PINE ID, to identify the PINE, the end point identifier of the origination and destination PINE such as IP address, GPSI, and MAC address. The message may also include the requested QoS by the PINE, and possibly a list of PEGCs, identified by PEGC ID, UE ID, authorized and available to support PINE indirect communication.

[0160] In step 3, 1003, the PEMC MT may send a request Inter PINE Communication Setup Request message to the 5GS using UL NAS signaling message. The PEMC MT may send to the AMF a Inter PINE Communication Setup Information message, via the UL NAS signaling, providing PIN ID, PINE ID, PIN end point identifiers, requested QoS, list of available and authorized PEGCs along with the new flag i.e., PIN Indirect Communication Setup Request.

[0161] In step 4, 1004, the AMF may retrieve the inter PINE communication setup information between the two PINEs, identified by PINE ID, and end point identifiers such as IP address, GPSI, and the PIN where they are located, which is identified by PIN ID. The AMF may retrieve updated URSP’s from the UDM / UDR / PCF / PIN server, as per the requested PIN ID, PINE ID, and authorized PEGCs as per the provided UE ID (SUPI / GPSI) and generate the Inter PINE Communication Setup Information (IPCSI) message for configuring the relevant PEGCs. The IPCSI message for indirect communication between PINE-1 and PINE-2 may include the traffic handling rules such as path configuration and routing information. For example, if the origination PINE == PINE-1 and the destination PINE == PINE-2; PEGC-1 , and assuming PINE-1 may communicate with PINE-2 through PEGC-1 , PEGC-2 and PEGC-3, it may include Route to IP addressl, port #X; PEGC-2: Route to IP address2, port#; and PEGC-3: Route to destination port#. The rule set may be provided to one or more PEGCs, in this example the routing rule may be sent to PEGC-1, PEGC-2 and PEGC-3. If the PINEs are in different PINs, the PIN server serving the different PINEs may be identified based on PIN ID and PINE ID. Then the destination PIN server may be requested to provide additional information on how to reach the destination PINE.

[0162] In one example, in step 5-1, 1005-1 , the 5GS / AMF / PCF may send Inter PINE Communication Setup Information (IPCSI) message back to the requesting PEMC MT. The AMF / PCF, upon reception of the new / updated IPCSI message, may pass on this information via the DL NAS signaling (e.g., DL NAS transport message) to the PEMC MT The UDM may pass the IPCSI information to the AMF via constructing / updating UPU as per the received IPCSI message, which may be transparently forwarded by the AMF to the PEMC MT. The AMF may construct an entirely new information element to transport the IPCSI message to the PEMC MT. The information flow from the AMF to the PEMC MT may be carried over other control plane NAS signaling messages as well.

[0163] The Indirect PINE Communication Setup Information message may include information about setting up a sidelink communication between PEGCs. E.g., the sidelink setup information may be sent as part of the updated URSP. The IPCSI information includes the traffic handling rules such as path configuration and routing information from origination PINE to destination PINE, through one or more PEGCs.

[0164] In step 6-1 , 1006-1, the PEMC MT may send the IPCSI information to the PEMC client (TE), by sending the PIN Indirect Communication Setup Response message, which may include the IPCSI information and the set of routing rules as above.

[0165] In step 7-1 , 1007-1 , the PEMC client may store the traffic handling rules such as path configuration and routing information The PEMC may identify the PEGC in the list. The listed PEGCs may be verified by the PEMC and checked whether they are still available. The PEMC may start preparing to inform the PEGCs regarding the traffic handling rules such as path configuration and routing information. The PEMC client may send a Configure PEGC Request message, which may include the traffic handling rules such as path configuration and routing information, to each identified PEGC clients (e.g., PEGC-1, PEGC-2, PEGC-3). The routing rules may indicate the origination and the destination PINE ID, IP address, port#, and related traffic handling rules such as path configuration and routing information. The PEGC may configure the traffic handling rules such as path configuration and routing information for origination and destination PINE.

[0166] In step 8-1 , 1008-1, if the PEGC can successfully configure the traffic handling rules such as path configuration and routing information from the origination to the destination PINE, it may respond by sending a Configure PEGC Response message to the PEMC client, indicating success or failure of the configuration procedure.

[0167] In step 9-1 , 1009-1, the PEMC client responds may send a Inter PINE Communication Setup Response message to the PINE, indicating success orfailure of the inter PINE communication setup procedure.

[0168] FIG. 10B illustrates an example of a PIN server configuring an inter-PINE indirect communication in a PEGC and a PEMC over the control plane.

[0169] In another example, as shown in FIG. 10B, in step 5-2, 1005-2, the 5GS / AMF / PCF may send Inter PINE Communication Setup Information (IPCSI) message to the PEGC, which are identified to support Inter PINE communication. The AMF / PCF, upon reception of the new / updated IPCSI message, may pass on this information via the control plane, e.g., DL NAS transport message, to one or more PEGC MT. The UDM may pass the IPCSI information to the AMF via constructing / updating UPU as per the received IPCSI message, which is transparently forwarded by the AMF to the PEGC MT. The AMF may construct an entirely new information element to transport the IPCSI message to the PEGC MT. The information flow from the AMF to PEGC MT may be carried over other control plane NAS signaling messages as well

[0170] The Indirect PINE Communication Setup Information message may include information regarding setting up sidelink communication between PEGCs E.g , the sidelink setup information may be sent as part of the updated URSP. The IPCSI message includes the traffic handling rules such as path configuration androuting information from the origination PINE to the destination PINE, through one or more PEGCs. The message may include a set of traffic handling rules such as path configuration and routing information.

[0171] In step 6-2, 1006-2, the 5GS / AMF / PCF may inform the PEMC MT about the result of the inter PINE communication setup by sending Inter PINE Communication Setup message through control plane, e.g., DL NAS transport message, which may indicate success or failure

[0172] In step 7, 1007-2, the PEMC MT may send the Inter PINE Communication Information message to the PEMC client, which may also indicate the success or failure of the indirect PINE communication setup procedure.

[0173] In step 8-2, 1008-2, the PEMC client responds to the Inter PINE Communication Setup Request message to the PINE by sending a response in a Inter PINE Communication Setup Response message indicating success or failure of the inter PINE communication setup procedure.

[0174] FIG. 11 A illustrates an example call flow of a network-initiated user plane procedure where an AF initiates the procedure.

[0175] In one example, the application function (AF) or the PIN server initiates the PINE indirect communication setup process In this example, the PINE indirect communication may be setup over the user plane.

[0176] In step 1 , 1101 , the PIN AF may decide to establish indirect inter PINE communication between two PINEs. The setup may happen during PIN creation or PIN reconfiguration. In order to establish indirect communication between the two PINEs, the AF may obtain the traffic handling rules such as path configuration and routing information from 5GS.

[0177] In step 2, 1102, the AF sends the PIN Indirect Communication Setup Request message to the 5GS, e.g., via NEF or common API framework for 3GPP northbound APIs (CAPIF). The AF may indicate that indirect communication through PEGC is requested by setting the request type to “Indirect through PEGC”. The message may indicate the destination PINE, identified by PINE ID and IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message indicates the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may also include the requested QoS by the origination PINE, such as the desired bandwidth, delay, and jitter The requested QoS may influence the 5GS / PIN server’s decision regarding the best type of communication path, e.g., “Indirect through PEGC’’ or “through 5GS” to establish between two PINEs.

[0178] In step 3, 1103, the 5GS / PIN server, after receiving the inter PINE communication request from PIN AF, may check the request type field. If the request type is present and set to indirect communication, the 5GS may verify if the PINE is allowed / capable to setup an indirect communication with the destination PINE. If the request type is not set, the 5GS may decide to setup an indirect communication between the two PINEs based on PINE policy and requested QoS. The PIN AF may inform available PEGCs in the PIN which can support indirect communication between the PINEs. The PIN server / 5GS may validate the request and verify againstPIN policy and PINE subscription whether the PINE may be allowed to communicate with the destination PINE using indirect communication. If allowed, the PIN server may obtain the traffic handling rules such as path configuration and routing information from the 5GS to establish inter PINE indirect communication between the indicated origination and destination PINEs identified by PINE ID and PINE type. The PIN server may also specify the agreed QoS to the 5GS, while identify the traffic handling rules such as path configuration and routing information, so that the 5GS may select the route which may support the requested QoS.

[0179] The PIN server may select a list of PEGCs provided by PEMC, based on policy, which may support indirect communication The selected list may also be provided to the 5GS as the preferred PEGCs for indirect communication. The 5GS may decide if indirect communication may be supported through the PEGCs or different PEGC should be selected. The PIN server may consider the list of connected PINEs and may determine the possible PEGCs and what QoS may be supported for indirect communication. Additional processing may be involved, when the origination PINE and destination PINE are owned by different providers, are in different domains, and are managed by different PIN servers. The PIN server may identify, based on PINE ID and PINE type, that the origination PINE and the destination PINE are in different domains. The origination PIN server of the origination PINE may identify the destination PIN server of the destination PINE. The origination PIN server may contact the destination PIN server to obtain valid routing information between PINE-1 and PINE-2, through one or more PEGCs.

[0180] In step 4, 1104, the 5GS / PIN server responds to the PIN Indirect Communication Setup Request message sent by the PIN AF by sending a PIN Indirect Communication Setup Response message to the PIN AF, which may include the traffic handling rules such as path configuration and routing information from the origination PINE to destination the PINE, through one or more PEGCs. The message may also include a set of rules, such as the IP address and port number where the traffic should be routed.

[0181] FIG. 11 B illustrates two examples of an AF configuring an inter-PINE indirect communication in a PIN over the user plane.

[0182] In one example (example 1 in FIG. 11 B), in step 5-1 , 1105-1 , the PIN AF sends to the PEMC client a PIN Indirect Communication Configuration Setup Request message indicating that indirect communication may be setup between PINE-1 and PINE-2. The PIN AF provides to the PEMC client the traffic handling rules such as path configuration and routing information from the origination PINE to the destination PINE, through one or more PEGCs. The message may include a set of routing rules such as the ones described above. The PEMC client may store the traffic handling rules such as path configuration and routing information. The PEMC may identify the PEGC in the list. The listed PEGCs may be verified by the PEMC and checked if the PEGCs are still available. The PEMC starts preparing to inform the PEGCs about the routing rule.

[0183] In step 6-1 , 1106-1 , the PEMC client informs the PIN AF if the PEGC could be configured properly, by sending a PIN Indirect Communication Configuration Setup Response message, indicating success or failure.

[0184] In step 7-1 , 1107-1 , the PEMC client may send a Configure PEGG Request message, which may include the traffic handling rules such as path configuration and routing information to each identified PEGG client from step 5. Each PEGC may configure the traffic handling rules such as path configuration and routing information for origination and destination PINE.

[0185] In step 8-1 , 1108-1, if the PEGC can successfully configure the traffic handling rules such as path configuration and routing information for the origination and the destination PINEs, it may respond by sending a Configure PEGC Response message to the PEMC client, indicating success or failure of the configuration procedure.

[0186] In another example (example 2 in FIG. 11 B) , in step 5-2, 1105-2, the PIN AF has obtained the routing rule for indirect communication between PINE-1 and PINE-2. The PIN AF may identify each involved PEGC and may directly send a Configure PEGC Request message to the identified PEGCs. The message may include the traffic handling rules such as path configuration and routing information, which includes the origination and destination PINE ID, IP address, port#, and related traffic handling rules such as path configuration and routing information for that PEGC. The PEGC may configure the traffic handling rules such as path configuration and routing information for origination and destination PINE.

[0187] In step 6-2, 1106-2, if the PEGC can successfully configure the traffic handling rules such as path configuration and routing information for origination and destination PINE, it may respond by sending a Configure PEGC Response message to the PIN server, indicating success or failure of the configuration procedure.

[0188] In one example, communication with the NEF and NAS signaling may be used. As an example, the AF or the PIN server may initiate the PINE indirect communication setup process using NAS signaling with PEMC / PEGCs.

[0189] FIG. 12A illustrates an example call flow of a network-initiated control plane procedure where the AF initiates the procedure.

[0190] In step 1 , 1201 , the PIN AF, during PIN creation or PIN reconfiguration, may decide to establish the indirect inter PINE communication between two PINEs. The AF may obtain the traffic handling rules such as path configuration and routing information from the 5GS.

[0191] In step 2, 1202, the AF may send a PIN Indirect Communication Setup Request message to the 5GS, e.g., via NEF or CAPIF. The AF may indicate that indirect communication through PEGC is requested by setting the request type to “Indirect through PEGC”. The message may indicate the destination PINE, identified by PINE ID and IP address, and other end point identifiers such as MAC address, port number, and PINE name. The message may indicate the PINE type of the destination PINE, such as sensor, video equipment, etc. The message may also include the requested QoS by the origination PINE, such as the desired bandwidth, delay, and jitter. The requested QoS may influence the 5GS / PIN server decision regarding the type of communication path to be used, e.g., “Indirect through PEGC” or “through 5GS”.

[0192] In step 3, 1203, the 5GS / PIN server, after receiving the inter PINE communication request from the PIN AF, may check the request type field. If the request type is present and set to indirect communication, the 5GS may verify if the PINE is allowed / capable to establish an indirect communication with the target PINE. If the request type is not set, the 5GS may decide to establish an indirect communication between the two PINEs based on PINE policy and requested QoS. The PIN AF may inform which available PEGCs in the PIN can support indirect communication between the PINEs.

[0193] The PIN server / 5GS may validate the request, and it may verify against PIN policy and PINE subscription if the PINE is allowed to communicate with the destination PINE using indirect communication. If allowed, the PIN server may determine routing information from the 5GS to establish inter PINE indirect communication between the indicated origination PINE and destination PINE identified by PINE ID and PINE type. The PIN server may also specify the agreed QoS to the 5GS, while determining routing information, so the 5GS may select the route which can support the requested QoS. The PIN server may select a list of PEGCs provided by the PEMC, based on policy, which can support indirect communication. The selected list may also be provided to the 5GS as the preferred PEGCs for indirect communication. The 5GS may determine whether indirect communication may be supported through the PEGCs or if a different PEGC may be selected.

[0194] The PIN server may consider the list of connected PINEs and determine possible PEGCs and what QoS can be supported for indirect communication. Additional processing may be involved, when the origination PINE and destination PINE are owned by different providers, are in different domains, and are managed by different PIN servers. The PIN server may identify, based on PINE ID and PINE type, that the origination PINE and destination PINE are in different domains. The origination PIN server of the origination PINE may identify the destination PIN server of the destination PINE. The origination PIN server may contact the destination PIN server to obtain valid routing information between origination PINE and destination PINE, through one or more PEGCs.

[0195] In step 4, 1204, the 5GS / PIN server may respond to the PIN AF, by sending a PIN Indirect Communication Setup Response message. The response may indicate if the request was accepted or not accepted. The 5GS may accept the request if the indirect path setup is allowed and possible to establish by 5GS.

[0196] FIG. 12B illustrates two examples of an AF configuring an inter-PINE indirect communication in a PIN over the control plane.

[0197] In one example (example 1 in FIG. 12B), in step 5-1, 1205-1, the 5GS / AMF / PCF may send an Inter PINE Communication Setup Information (IPCSI) message to the PEGC MT identified in the IPCSI message. The AMF / PCF, upon reception of the new / updated IPCSI message, may pass on this information via the control plane (e.g., DL NAS transport message) to the PEGC MTs listed in the IPCSI message. The UDM may pass the IPCSI information to the AMF via constructing / updating UPU as per the received IPCSI message, which may be transparently forwarded by the AMF to the PEGC MT. The PCF may construct new URSPs as per thereceived IPCSI message from the UDM / UDR and provide those to the PEGC MT as UE policies via the AMP as DL NAS transport message. The AMF may construct an entirely new information element to transport the IPCSI message to the PEGC MT. The information flow from the AMF to the PEGC MT may be carried over other control plane NAS signaling messages as well.

[0198] The Indirect PINE Communication Setup Information message may include information about setting up sidelink communication between PEGCs. E.g. , the sidelink setup information can be sent as part of the updated URSP. The PEGC may use this information to establish sidelink communication with another PEGC. If the IPCSI message includes more than one PEGC, then the AMF / PCF, upon reception of the new / updated IPCSI message, may pass this information via the control plane (e.g., DL NAS transport message) to all the PEGC MTs listed in the IPCSI message.

[0199] In step 6-1 , 1206-1, the PEGC MT may pass the IPCSI message to the PEGC client (TE). The PEGC client may configure the traffic handling rules such as path configuration and routing information based on the information received from PEGC MT.

[0200] In another example (example 2 in FIG. 12B), in step 5-2, 1205-2, the 5GS / AMF / PCF may send Inter PINE Communication Setup Information (IPCSI) message to the PEMC MT in the PIN. The AMF / PCF, upon reception of the new / updated IPCSI message, may pass this information via the control plane (e g., DL NAS transport message) to the PEMC MT. The UDM may pass the IPCSI information to the AMF via constructing / updating UPU as per the received IPCSI message, which may be transparently forwarded by the AMF to the PEMC MT. The AMF might construct an entirely new information element to transport the IPCSI message to the PEMC MT. The information flow from the AMF to the PEMC MT could be carried over the control plane NAS signaling messages as well. The Indirect PINE Communication Setup Information (IPCSI) message may include information about setting up sidelink communication between PEGCs. E.g., the sidelink setup information can be sent as part of the updated URSP. The IPCSI message may include the traffic handling rules such as path configuration and routing information from the origination PINE to the destination PINE, through one or more PEGCs.

[0201] In step 6-2, 1206-2, the PEMC client may store the traffic handling rules such as path configuration and routing information The PEMC may identify the PEGC in the list. The listed PEGCs may be verified by the PEMC and checked if the PEGC are still available. The PEMC may start preparing to inform the PEGCs about the routing rule. The PEMC client sends a Configure PEGC Request message, which may include the routing rules for each identified PEGC client. The routing rules may indicate the origination and the destination PINE ID, IP address, port#, and related traffic handling rules such as path configuration and routing information. The PEGC configures the traffic handling rules such as path configuration and routing information for origination and destination PINE.

[0202] FIG. 13 depicts an example of a flow-chart of the PEMC process during PINE-initiated user plane procedure for establishment of inter-PINE indirect communication.

[0203] A PEMC client 1301 may receive a request from PINE-1 to setup an indirect communication with PINE-2 1302. The request may contain PINE-2 identification, the PINE-2 type and the requested QoS. The PEMC client may determine the associated PIN server, the available PEGCs in the PIN, and the other connected PINEs in the PIN 1303. The PEMC client may send a request to the PIN server to setup an indirect communication between PINE-1 and PINE-2 1304. The PEMC client may then receive a response from the PIN server, which may include the path information, including information about one or more PEGCs in the path, and associated routing information 1305. The PEMC client may use that information to configure the indirect communication between PINE 1 and PINE 2 in the PEGCs participating in the path 1306. The PEMC client may receive an indication from the participating PEGCs whether the indirect communication path setup was successful or it failed 1307. The PEMC may finally respond to PINE-1 , indicating if the indirect communication setup request was successful or it failed 1308.

[0204] As it was discussed is previous paragraphs, a similar procedure may apply without the PEMC, i.e., the application layer request may be sent directly to the PEGC, as it is illustrated in FIG. 7. Optionally, a PINE- initiated procedure for establishment of inter-PINE indirect communication over the control plane may be used, e.g., using NAS layer communication / NAS signaling.

[0205] FIG. 14 depicts an example of a flow-chart of the PEGC process during PINE-initiated control plane procedure for establishment of inter-PINE indirect communication.

[0206] A PEGC may receive, from a first PINE, a first request to establish a service with a third PINE. The request may comprise an indication of indirect communication through PEGC, an identity of the third PINE, a type of the third PINE, and QoS of the service being requested 1401.

[0207] The PEGC may send, to a network, a first NAS message including the request to establish the service using an indirect communication between the first PINE and the second PINE 1402. Optionally, the request may be sent in a first PINAPP message over the user plane.

[0208] The PEGC may receive, from the network, a second NAS message including an indication of successful establishment of the service using the indirect communication between the first PINE and the third PINE, and information associated with the indirect communication path including routing information 1403. Optionally, the information from the network may be received in a second PINAPP message over the user plane.

[0209] The PEGC may send, to the first PINE, based on successful establishment of the service using the indirect communication between the first PINE and the second PINE, a response to the first request, wherein the response indicates the successful establishment of the service 1404

[0210] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the 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 over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMSWhat is Claimed:

1. A method performed by a first wireless transmit and receive unit (WTRU) operating in a personal internet of things (loT) network (PIN) as a first PIN element (PINE), the method comprising: receiving, from a second WTRU operating in the PIN as a second PINE, a first request to establish communication between the second WTRU and a third WTRU operating in the PIN as a third PINE, wherein the first request includes identification of the third WTRU; sending, to a core network (CN), a second request to establish the communication between the second WTRU and the third WTRU, wherein the second request includes an indication that the communication being requested is indirect communication through PINE with gateway capability (PEGC); receiving, from the CN, a first response, wherein the first response includes information associated with the indirect communication through PEGC; and sending, to the second WTRU, based on the information associated with the indirect communication through PEGC, a second response, wherein the second response indicates successful establishment of the communication between the second WTRU and the third WTRU.

2. The method of claim 1, wherein the first WTRU comprises a user equipment (UE) configured to operate in the PIN as a PEGC.

3. The method of claim 1 , wherein the first WTRU comprises a user equipment (UE) configured to operate in the PIN as a PINE with management capability (PEMC).

4. The method of any one of claims 1-3, wherein the second request is sent to an access and mobility function (AMF) using a non access stratum (NAS) message.

5. The method of any one of claims 1-4, wherein the second request is sent to a PIN server via a user plane function (UPF).

6. The method of any one of claims 1-5, wherein the first request further comprises at least one of: a type of the third WTRU, or a QoS requirement to support the indirect communication through PEGC.

7. The method of any one of claims 1-6, wherein the information associated with the indirect communication through PEGC includes updated user equipment route selection policy (URSP) rules.

8. The method of any one of claims 1-7, wherein the information associated with the indirect communication through PEGC includes information on a route to be used for communication between the second WTRU and the third WTRU, and wherein the information on a route includes identification of one or more PEGCs in the route.

9. The method of claim 8, further comprising:sending, to the one or more PEGCs in the route, the information associated with the indirect communication through PEGC.

10. The method of claim 8 or claim 9, wherein the information associated with the indirect communication through PEGC is sent to the one or more PEGCs identified using proximity services (ProSe) direct communication over a sidelink channel.

11. A wireless transmit / receive unit (WTRU) operating in a personal internet of things (loT) network (PIN) as a first PIN element (PINE), the WTRU comprising at least one processor and a transceiver, wherein: the least one processor and a transceiver are configured to receive, from a second WTRU operating in the PIN as a second PINE, a first request to establish communication between the second WTRU and a third WTRU operating in the PIN as a third PINE, wherein the first request includes identification of the third WTRU; the least one processor and a transceiver are configured to send, to a core network (CN), a second request to establish the communication between the second WTRU and the third WTRU, wherein the second request includes an indication that the communication being requested is indirect communication through PINE with gateway capability (PEGC); the least one processor and a transceiver are configured to receive, from the CN, a first response, wherein the first response includes information associated with the indirect communication through PEGC; and the least one processor and a transceiver are configured to send, to the second WTRU, based on the information associated with the indirect communication through PEGC, a second response, wherein the second response indicates successful establishment of the communication between the second WTRU and the third WTRU.

12. The WTRU of claim 11 , wherein the first WTRU comprises a user equipment (UE) configured to operate in the PIN as a PEGC.

13. The WTRU of claim 11 , wherein the first WTRU comprises a user equipment (UE) configured to operate in the PIN as a PINE with management capability (PEMC).

14. The WTRU of any one of claims 11-13, wherein the second request is sent to an access and mobility function (AMP) using a non access stratum (NAS) message.

15. The WTRU of any one of claims 11-14, wherein the second request is sent to a PIN server via a user plane function (UPF).

16. The WTRU of any one of claims 11-15, wherein the first request further comprises at least one of: a type of the third WTRU, or a QoS requirement to support the indirect communication through PEGC.

17. The WTRU of any one of claims 11-16, wherein the information associated with the indirect communication through PEGC includes updated user equipment route selection policy (URSP) rules.

18. The WTRU of any one of claims 11-17, wherein the information associated with the indirect communication through PEGC includes information on a route to be used for communication between the second WTRU and the third WTRU, and wherein the information on a route includes identification of one or more PEGCs in the route.

19. The WTRU of claim 18, wherein: the least one processor and a transceiver are further configured to send, to the one or more PEGCs in the route, the information associated with the indirect communication through PEGC.

20. The WTRU of claim 18 or claim 19, wherein the information associated with the indirect communication through PEGC is sent to the one or more PEGCs identified using proximity services (ProSe) direct communication over a sidelink channel.

Images