Techniques for local routing of individual Internet of Things network communications

Abstract

The application relates to devices and components including apparatuses, systems, and methods for internal routing of individual Internet of Things network communications.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 338,819, filed on May 5, 2022, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present application relates to the field of network communications, and in particular to a technology for local routing of personal Internet of Things communications. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) define standards for New Radio (NR) wireless networks. One area of ​​research in the development of these TSs is enhancing the fifth generation (5G) system to support communications for Personal Internet of Things (PIN) networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A network environment according to some embodiments is illustrated.

[0006] Figure 2 Flowcharts according to some embodiments are illustrated.

[0007] Figure 3 A user plane function (UPF) according to some embodiments is illustrated.

[0008] Figure 4 An operational flow / algorithm structure according to some embodiments is illustrated.

[0009] Figure 5 Another operational flow / algorithm structure according to some embodiments is illustrated.

[0010] Figure 6 Another operational flow / algorithm structure according to some embodiments is illustrated.

[0011] Figure 7 PIN elements according to some embodiments are illustrated.

[0012] Figure 8 A network node according to some embodiments is illustrated. DETAILED DESCRIPTION

[0013] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces and technologies are described to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purpose of this document, phrases "A / B" and "A or B" refer to (A), (B) or (A and B).

[0014] The following is a glossary of terms that may be used in this disclosure.

[0015] The term "circuit" as used herein refers to a part of or including a hardware component configured to provide the described function. The hardware component may include an electronic circuit, a logic circuit, a processor (shared, dedicated or group) or a memory (shared, dedicated or group), an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC or a programmable system on chip (SoC)) or a digital signal processor (DSP). In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for executing the function of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a circuit of a specific type.

[0016] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0017] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and a network interface card.

[0018] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities that can allow a user to access network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with the following and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment or reconfigurable mobile device. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0019] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0020] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database, and an application or a unit of workload. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or network resources provided by a virtualized infrastructure to an application, device, or system. The term "network resources" or "communication resources" may refer to resources that can be accessed by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0021] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection between two devices for sending and receiving information.

[0022] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0023] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0024] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, or virtualized network function.

[0025] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0026] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include various components of a core network (CN) (e.g., a 5G core network (5GC) 104), a radio access network (RAN) (e.g., a next generation RAN (NG-RAN) 108), and a PIN 112. In some embodiments, the 5GC 104 and the NG-RAN 108 may be referred to as a 5G system (5GS). In other embodiments, the network environment 100 may additionally / alternatively be compatible with other network generations, including, for example, fourth generation (4G) or sixth generation (6G) networks.

[0027] The 5GC 104 may have a variety of network functions to provide services such as storing subscription information, authenticating user equipment (UE) / network components, registering and tracking UEs, managing quality of service (QoS) aspects, controlling data sessions, and forwarding uplink / downlink traffic.

[0028] The 5GC 104 may have a network exposure function (NEF) 116 to provide information about the capabilities of the network functions of the 5GC 104 to external network functions (such as, for example, the PIN AF 120). The PIN AF 120 (which may be referred to as a PIN management function (MF)) may provide support for services associated with communications related to a PIN (e.g., the PIN 112). The PIN AF 120 may be provided by an application server (AS) in an external data network. Alternatively, the PIN AF 120 may provide control plane signaling for control signaling, while the PIN AS provides user plane signaling for application data. In some embodiments, the PIN AF 120 may not have direct access to other network functions of the 5GC 104, and therefore may be coupled to the NEF 116. In other embodiments, the PIN AF 120 may have direct access and may be coupled to a policy control function (PCF) of the 5GC 104 via an N5 reference point. A "reference point" may refer to a point-to-point interface that may be associated with a set of specified signaling procedures between coupled functions. In this disclosure, "reference point" may be used interchangeably with "interface."

[0029] 5GC 104 may also have a session management function (SMF) 124. SMF 124 may configure traffic steering, QoS control, and policy-related functions at one or more user plane functions (UPFs), such as UPFs 128 and 132, perform protocol data unit (PDU) session management, Internet Protocol (IP) address allocation, general packet radio service tunneling protocol-user plane (GTP-U) tunnel management, UPF selection and control, and downlink notification management. SMF 124 may be coupled to UPFs 128 and 132 via an N4 interface.

[0030] UPF 128 / 132 may handle a user plane path of a PDU session to facilitate routing traffic to and from external data networks and within network environment 100, as described herein.

[0031] The 5GC 104 may have a number of additional network functions (NFs) 136 not specifically shown or described. These NFs may include, but are not limited to, PCF, unified data manager (UDM), and access and mobility management function (AMF).

[0032] The NG-RAN 108 may include base stations (e.g., base stations 140 and 148) that provide radio access cells (e.g., new radio (NR) cells) through which user equipment (UE) can access services of the network environment 100. The UE and base stations 140 / 148 may communicate over an air interface compatible with 5G NR system standards as provided by 3GPP technical specifications.

[0033] PIN 112 may be a collection of PIN elements (PINEs) (e.g., IoT elements and UEs) that can be directly coupled to each other. PIN 112 may be established with the help of components of 5GC 104. PIN 112 may be a smart home network, a wearable personal area network, etc.

[0034] The elements of PIN 112 may communicate with each other using short-range communication protocols such as, for example, 3GPP PC5 sidelink, wireless local area network (WLAN) protocols, and wireless personal area network (WPAN) protocols.

[0035] The PIN 112 may include certain types of elements configured to provide specific functions to the PIN 112. For example, the PIN 112 may include a PIN element with management capabilities (PEMC) 152 and one or more PIN elements with gateway capabilities (PEGC) (e.g., PEGC#1 156 and PEGC#2 160). The PEMC 152, PEGC#1 156, and PEGC#2 160 may be UEs capable of accessing the NG-RAN 108 and the 5GC 104. The PIN 112 may also include a plurality of other PIN elements 164.

[0036] PEMC 152 may manage the establishment and operation of PIN 112 with the help of components of 5GC 104. PEGC may operate as an interface between PIN 112 and NG-RAN 108. PEGC 156 / 160 may be enabled with an independent connection toward 5GC 104. If PEGC#2 160 is within range of other elements of PIN 112, it may connect to 5GC 104 using its own connection options or through PEGC#1 156. In some embodiments, one UE may act as both PEMC and PEGC.

[0037] When the communication elements are in close proximity to each other, short-range communication protocols for communication between the elements of PIN 112 may be useful. However, in the case where PIN 112 includes more than one PEGC and one of the PEGCs is not close to the other elements of PIN 112, the communication paths may pass through other networks. In many cases it may be necessary to protect the communication paths as they pass through other networks.

[0038] For example, consider the first scenario where the user of a smartphone may wish to access a camera when the smartphone is out of direct communication range with the camera. In a conventional system, both the smartphone and the camera would utilize a connection to an application server (from the manufacturer or IOT network provider) within a data network external to the 5GS. The 5GS would route data between the UPF and the external data network over the N6 interface. The application server of the external data network would then provide the required connection establishment.

[0039] Another scenario may involve a PIN with a voice-activated smart home assistant. Such a smart home assistant may have a distributed architecture, where different processing operations are performed in different PIN elements. If a smart home assistant instance in a smartphone needs to access a smart home assistant instance in a PIN element that is not communicating directly with the smartphone, the connection may need to traverse an external network similar to that described above.

[0040] Translating the above situation into network environment 100, when an element of the first part of PIN 112 (e.g., the first element of PIN element 164) and an element of the second part of PIN 112 (e.g., PEGC #2160) are not within direct communication range of each other (or another PIN element that can act as a repeater), these elements may need to communicate with each other.

[0041] The embodiment describes a network environment 100 that is configured to provide internal routing between PDU sessions used by PEGCs (e.g., PEGC#1 156 and PEGC#2 160) of the same PIN (e.g., PIN 112). Through internal routing, the communication path between PEGC#1 156 and PEGC#2 160 can stay within the secure 5GS and does not need to traverse the N6 interface to the external data network. Various embodiments describe establishing and using communication paths between elements of PIN 112 via 5GS.

[0042] When PIN 112 is established within network environment 100, provision may be made for routing PIN communications within the security domain provided by 5GS without having to route communications via an external data network. Routing PIN communications within 5GS to an external data network without using the N6 interface may be referred to herein as local routing.

[0043] In some embodiments, PEGC#1 156 and PEGC#2 160 may have PDU sessions terminated in a common UPF. In these embodiments, the communication path within PIN 112 via 5GS may be implemented using 5GC procedures for local switching within the UPF. In other embodiments, PEGC#1 156 and PEGC#2 160 may have PDU sessions anchored by different UPFs (e.g., Figure 1 128 and 132). In these embodiments, the communication path within PIN 112 via 5GS may be implemented using the N19 interface between UPFs 128 and 132. Thus, various embodiments may use a PEGC connected to the same UPF or use an N19 interface between multiple UPFs to authorize PIN 112 for local routing. In some embodiments, local routing may be limited to PEGCs connected to UPFs that are within the same SMF service area (e.g., the UPFs are coupled to the same SMF).

[0044] In some embodiments, PIN 112 may be configured for local routing within a particular geographic area. For example, when PEGC#1 156 and PEGC#2 160 are connected to 5GC 104 through a particular NG-RAN (e.g., NG-RAN 108) or base station, PIN 112 may be configured for local routing.

[0045] In some embodiments, PIN 112 may be configured for local routing within a specific time period. For example, PIN 112 may be configured for local routing within a time period that is considered more critical for secure intra-5GC routing.

[0046] Granular identification of PDUs for local routing can be performed by configuring a set of packet filters. For example, a set of packet filters can be identified by using an IP 5-tuple. The IP 5-tuple can include a source IP address, a source port, a destination IP address, a destination port, and a transport protocol. In some cases, this can be used to provide privileges for local routing services to certain PIN elements. For example, PIN 112 can be configured in a manner that enables some PIN elements to utilize local routing, while other PIN elements may not utilize local routing. This can be used to provide a safer local routing option to a first PIN element that sends / receives more sensitive information (e.g., a video), while providing a standard routing option involving an external data network to a second PIN element that sends / receives less sensitive information (e.g., a sensed temperature setting).

[0047] Embodiments may be applicable to PINs 112 having more than one PEGC that is authorized to communicate with 5GC 104. Although embodiments describe local routing of communications between two PEGCs of PIN 112; other embodiments may be applicable to local routing of communications between more than two PEGCs of PIN 112.

[0048] PIN AF 120 may use an external parameter provisioning interface to provide local switching or 5GS routing configuration for PIN traffic. In some embodiments, PIN AF 120 may provide the following configuration parameters to facilitate local routing of PIN traffic.

[0049] The configuration parameters may include a data network name (DNN) identifying a data network including an external PIN application server that services PIN 112 .

[0050] The configuration parameters may additionally / alternatively include single network slice selection assistance information (S-NSSAI) to identify the network slice providing service to PIN112.

[0051] The configuration parameters may additionally / alternatively include a PIN identifier identifying the PIN 112 .

[0052] The configuration parameters may additionally / alternatively include a PIN element identifier for which local routing support is to be provided. The PIN element identifier may be an IP address or a universal public subscription identifier (GPSI) that identifies an element of PIN 112. If the PEGC of PIN 112 provides network address translation (NAT) for the PIN element, the PIN AF 120 may configure only the IP address of the PEGC. In some embodiments, the PIN element identifier may include an identifier associated with a PIN element behind a PEGC (e.g., a PIN element 164 behind PEGC#1 156) that uses framed routing in a PDU session. Framed routing can support an IP network behind a UE in a manner that allows access to a range of IPv4 addresses or IPv6 prefixes in a single PDU session. Therefore, a PDU session may be associated with multiple framed routes. Framed routing may be similar to the framed routing described in clause 5.6.14 of TS23.501v17.4.0 (2022-03-23).

[0053] In some embodiments, PIN AF 120 may authorize only a subset of PEGCs of PIN 112 for local routing. For example, consider that PIN 112 includes a third PEGC (PEGC #3). PIN AF 120 may authorize PEGC #1 156 and PEGC #2 for local routing by including the corresponding PIN element identifiers in the configuration parameters. If the PIN element identifier of PEGC #3 is not included, then the PEGC may not be authorized for local routing.

[0054] The configuration parameters may additionally / alternatively include any restrictions for local routing. For example, in some embodiments, local routing may be restricted to specific geographic locations in the PIN AF 120, which may provide indications of these locations where the PEGC may select for local routing. The geographic restrictions may be associated with network equipment that provides connectivity services to the PEGC. For example, some geographic restrictions may be applied by indicating a set of base stations / NG-RANs that may be used to support local routing. In another example, geographic restrictions may be applied by indicating a UPF or a set of specific UPFs that may be used to support local routing (if N19-based routing is allowed). In some embodiments, local routing may be subject to time restrictions.

[0055] The configuration parameters may additionally / alternatively include traffic characteristics for local routing. The traffic characteristics may include a set of packet filters that may be used by the UPF 128 / 132 to identify traffic to be locally routed. The set of packet filters may include, for example, IP 5-tuples, which allow granular routing of traffic.

[0056] PIN AF 120 may provide configuration parameters to SMF 124 via NEF 116. SMF 124 may use the configuration parameters to identify the associated PDU sessions to be configured to support local routing. When all PEGCs have PDU sessions in a common UPF, local switching within the UPF may be used. If a PEGC has PDU sessions established with different UPFs, such as Figure 1 As shown, the SMF 124 may create a group-level N4 session. For example, the SMF 124 may configure the UPF 128 (which anchors PDU Session #1 for PEGC #1 156) and the UPF 132 (which anchors PDU Session #2 for PEGC #2 160) with group-level N4 rules based on the configuration parameters. The group-level N4 rules may use the PIN identifier as a network instance. The UPF 128 / 132 may use the group-level N4 rules to establish a PIN-specific tunnel on the N19 interface for local routing.

[0057] In some embodiments, local routing can be supported only when all USFs are in the same SMF service area. This ensures that one SMF can create / manage group-level N4 sessions.

[0058] When establishing or modifying a PDU session for a PEGC configured for a PIN for local routing, SMF 124 may evaluate whether the conditions for installing UPF rules for local routing are met. If these conditions are met, SMF 124 may configure UPF using routing rules as described below.

[0059] Figure 2is a flow chart 200 illustrating configuration of local routing for PEGC#1 156 and PEGC#2 160 of PIN 112 according to some embodiments.

[0060] Flowchart 200 may include an operation 0 (Op 0) at 204 in which a PIN 112 is created. PIN 112 may be provided with one or more PEGCs. Figure 1 As shown, PIN 112 may be supplied with two PEGCs - PEGC #1 156 and PEGC #2 160. However, in other embodiments, PIN 112 may be supplied with more than two PEGCs. Operation 0 may additionally include supplying PEMC 152 to PIN 112. The supply of PEGC / PEMC may also include authorizing PIN elements to operate in their respective roles.

[0061] In some embodiments, the provisioning of PEGC / PEMC may include multiple operations related to the discovery, selection, authentication and registration of PIN elements. Some of these operations may be completed locally, such as between devices based on PIN 112, while other operations may include communication with PIN AF 120 or PIN application server in an external data network.

[0062] Flowchart 200 may also include operation 1a (Op 1a) at 208 in which PEGC#1 156 establishes or modifies PDU Session #1 for PIN 112. Operation 1a may include signaling between PEGC#1 156, SMF 124, and UPF 128.

[0063] Flowchart 200 may also include operation 1b (Op 1b) at 212, in which PEGC#2 160 establishes or modifies PDU Session #2 for PIN 112. Operation 1b may include signaling between PEGC#2 160, SMF 124, and UPF 132.

[0064] Flowchart 200 may also include operation 2 (Op 2) at 216, in which PEMC 152 provides PEMC configuration to PIN AF 120. Operation 2 may include application layer signaling of the PEMC configuration. The PMC configuration may include the IP addresses of PEGC#1 156 and PEGC#2 160. If framed routing is used, a PINE identifier that may use local routing may also be provided to PIN AF 120.

[0065] Flowchart 200 may also include an operation 3a (Op 3a) at 220, in which the PIN AF 120 configures parameters for local routing. The configuration parameters for local routing may be similar to those discussed above and elsewhere herein. In some embodiments, additional configuration parameters for PIN communications may also be configured. For example, the additional configuration parameters may include information about whether some PIN elements are allowed / not allowed to access the Internet, specific Internet services, or other PIN elements.

[0066] Flowchart 200 may also include operation 3b (Op 3b) at 224, in which PIN AF 120 provides configuration parameters in an association request to NEF 116. At 224, the message may be a create, update, or delete association request message. NEF 116 may proceed to authorize the request.

[0067] Flowchart 200 may also include operation 4 (Op 4) at 228, in which NEF 116 may create a NEF-SMF association for PIN management upon authorization of the request received in operation 3b. In some embodiments, the NEF-SMF association may be established in a manner similar to that described in clause 6.12.2.1 of 3GPP Technical Report (TR) 23.700-88 v.0.2.0 (2022-04). In some cases, a "NEF ID for PIN" may be used to establish the NEF-SMF association, as described in clause 6.12.2.1 of TR 23.700-88. In other cases, a separate ID may be used instead, such as a "NEF ID for local routing of PIN". When establishing the NEF-SMF association, NEF 116 may also provide configuration parameters received from PIN AF 120 to SMF 124 to allow SMF 124 to create N4 rules for local routing.

[0068] The flowchart 200 may also include an operation 5 (Op 5) at 232, in which the SMF 124 identifies the restrictions within the configuration parameters and obtains relevant information. For example, where the restrictions include geographical restrictions based on a set of one or more NG-RANs authorized for local routing, the SMF 124 may obtain an NG-RAN identifier for the relevant NG-RAN.

[0069] Flowchart 200 may also include operation 6 (Op 6) at 236, in which the SMF 124 uses the PIN ID to establish a group-level N4 session. To establish the group-level N4 session, the SMF 124 may create N4 rules based on the configuration parameters (and any relevant information obtained in operation 5). Unless otherwise described herein and as follows, the N4 rules can be created in a manner similar to that described in clause 5.8.2.13 of 3GPP TS 23.501.

[0070] Figure 3 Illustrated is a UPF 300 configured for local routing of PIN communications according to some embodiments. UPF 300 may be similar to UPF 128 or UPF 132, and may be substantially interchangeable therewith.

[0071] The UPF 300 may be configured with local routing rules (e.g., N4 rules 304) via a configuration interface 306 coupled to an N4 reference point. The N4 rules may include packet detection rules (PDRs) 308 and forwarding action rules (FARs) 312. The UPF 300 may use these rules to identify and forward traffic between multiple interfaces. These interfaces may include an access interface 316 coupled to an N3 reference point or an N9 reference point and multiple CN interfaces 318. The CN interface 318 may include a peer interface 320 coupled to an N19 reference point and a data network (DN) interface coupled to an N6 reference point.

[0072] The N4 rules 304 may include the following detection and forwarding rules that are configured to handle packets arriving from a PEGC with a PDU session anchored at the UPF 300. To detect traffic, the N4 rules 304 may include a PDR that contains a source interface and CN tunnel information, the source interface is set to "access side" and the CN tunnel information is set to the PDU session tunnel header associated with the PDU session anchored at the UPF 300 (e.g., N3 or N9 General Packet Radio Service Tunneling Protocol-User (GTP-U) Fully Qualified Tunnel Identifier (F-TEID)). To forward traffic, the N4 rules may include a FAR that contains a destination interface that is set to "5G PIN Internal" + PIN identifier. "5G PIN Internal" may be used herein to identify an internal PIN interface. In other embodiments, other names may be used to identify such interfaces. Local routing may then be applied to traffic received from the PEGC that includes packets that match the PDR / FAR.

[0073] The N4 rules 304 may include the following detection and forwarding rules configured to handle packets heading to a PEGC with a PDU session anchored at the UPF 300. To detect traffic, the N4 rules 304 may include a PDR containing a source interface set to "5G PIN inside" + PIN identifier and a destination address set to the IP address of the PEGC / PIN element (if framed routing is used, the IP address is configured for the framed routing). To forward traffic, the N4 rules 304 may include a FAR containing an outer header creation indicating N3 / N9 tunnel information and a destination interface set to "access side".

[0074] If N19 based forwarding is to be used, the SMF 124 may configure a group level N4 session for each N19 tunnel by providing N4 rules 304 as follows.

[0075] To process packets received from the N19 tunnel, the N4 rules 304 may include the following detection and forwarding rules. To detect traffic, the N4 rules 304 may include a PDR containing a source interface set to "core side" and CN tunnel information set to the N19 tunnel header (e.g., N19 GTP-U F-TEID). To forward traffic, the N4 rules may include a FAR containing a destination interface set to "5G PIN internal" + PIN identifier.

[0076] To handle packets towards a 5G PIN gateway / element anchored at another UPF, the N4 rules 304 may include the following detection and forwarding rules. To detect traffic, the N4 rules 304 may include a PDR containing a source interface and a destination address, the source interface is set to "5G PIN internal" + PIN identifier, and the destination address is set to the IP address of the PEGC / PIN element at the peer UPF anchored at the N19 tunnel. To forward traffic to a 5G PIN gateway / element anchored at another UPF via an N19 tunnel, the N4 rules may include a FAR containing an outer header creation and a destination interface, the outer header creation indicates the N19 tunnel information, and the destination interface is set to "core side".

[0077] In some embodiments, the SMF 124 can also configure N4 rules 304 for group-level N4 sessions in a manner that allows the UPF 300 to handle packets with unknown destination addresses as follows. To detect traffic, the N4 rule 304 may include a PDR that includes a source interface set to "5G PIN internal" + PIN identifier, a full match packet filter, and a priority set to the lowest priority value. To process traffic, the N4 rule 304 may include a FAR that includes a destination interface set to "core side" to route traffic via N6 by default, or in the event that local SMF configuration for N6-based forwarding is not applied, the N4 rule includes a FAR that instructs the UPF to drop the traffic.

[0078] Figure 4 is an operational flow / algorithm structure 400 according to some embodiments. The operational flow / algorithm structure 400 may be Figure 8 The PIN AF 120 or the network node 800 or a component thereof (such as the processor 804) is implemented.

[0079] The operational flow / algorithm structure 400 may include obtaining configuration information at 404, the configuration information including IP addresses of multiple PEGCs for the PIN. The configuration information may be received from the PEMC of the PIN via application layer signaling. In some embodiments, the generated configuration information also includes addresses of one or more PIN elements in addition to the PEGC.

[0080] The operational flow / algorithm structure 400 may also include configuring parameters for local routing of PIN traffic between the first PEGC and the second PEGC at 408. These parameters may include DNN or S-NSSAI. In some embodiments, the parameters may include a PDU session type that may be associated with a PDU session of multiple PEGCs.

[0081] The configuration parameters may also include a PIN identifier and a PIN element identifier, the PIN identifier being used to identify the PIN for which local routing is to be configured, the PIN element identifier being associated with a PIN element that may participate in local routing. The PIN element identifier may be an IP address or a GPSI.

[0082] In some embodiments, the configuration parameters may include restrictions that may be imposed on the local routing of the PIN. These restrictions may include geographic-based restrictions or time-based restrictions.

[0083] The operational flow / algorithm structure 400 may also include sending the parameters to the NEF in an association request at 412. The association request may be a create, update, or delete association request.

[0084] Figure 5is an operational flow / algorithm structure 500 according to some embodiments. The operational flow / algorithm structure 500 may be Figure 8 The SMF 124 or network node or a component thereof (such as processor 804) is implemented.

[0085] The operational flow / algorithm structure 500 may include receiving configuration information from the PIN AF at 504. As part of establishing a NEF-SMF association for the PIN, configuration parameters may be received via the NEF. These configuration parameters may be similar to those described above with respect to Figure 4 or those configuration parameters described elsewhere in this document.

[0086] The operational flow / algorithm structure 500 may also include generating a rule for local routing of PIN traffic at 508. The rule may be a UPF rule, which may also be referred to as an N4 rule, which may be used to detect and forward traffic through an appropriate local routing communication path. The rule may be used to establish a group-level N4 session using a PIN identifier.

[0087] The operational flow / algorithm structure 500 may also include sending the rule to one or more UPFs at 512 .

[0088] Figure 6 is an operational flow / algorithm structure 600 according to some embodiments. The operational flow / algorithm structure 600 may be Figure 8 The UPF 128, UPF 132, UPF 300 or a network node or a component thereof (such as processor 804) is implemented.

[0089] The operational flow / algorithm structure 600 may include receiving a rule for local routing of PIN traffic at 604. The rule may be a UPF / N4 rule similar to that described above with respect to Figure 5 Or those rules discussed elsewhere in this article. The rules may include PDR and FAR.

[0090] The operational flow / algorithm structure 600 may also include identifying traffic based on the rule-based PDRs at 608. Some specific PDRs are discussed below.

[0091] If the UPF anchors a PDU session for the first PEGC from which it receives PIN traffic for local routing, the PDR may have a source interface and core network tunnel information, where the source interface is set to the access side and the core network tunnel information is set to the PDU session tunnel header associated with the PDU session.

[0092] If the UPF anchors the PDU session for a first PEGC and traffic for local routing is directed to the first PEGC, the PDR may have a source interface and a destination address, where the source interface is set to the value of "5GPIN internal" plus the PIN identifier and the destination address is set to the IP address of the first PEGC or a PIN element associated with the first PEGC.

[0093] If the UPF is coupled with another UPF via an N19 tunnel and traffic for local routing comes from the N19 tunnel, the PDR may have a source interface and core network tunnel information, the source interface being set to the core side, and the core network tunnel information being set to the header of the N19 tunnel.

[0094] If the UPF is coupled to another UPF via an N19 tunnel and traffic for local routing is directed to a first PEGC anchored by the other UPF, the PDR may have a source interface and a destination address, where the source interface is set to the PIN internal value plus the PIN identifier, and the destination address is set to the IP address of the first PEGC or a PIN element associated with the first PEGC.

[0095] The operational flow / algorithm structure 600 may also include forwarding traffic based on the rule's FAR at 612. Some specific FARs are discussed below.

[0096] If the UPF anchors the PDU session for the first PEGC from which it receives PIN traffic for local routing, the FAR may have a destination interface set to the PIN internal value plus the PIN identifier.

[0097] If the UPF anchors the PDU session for the first PEGC and traffic for local routing is directed to the first PEGC, the FAR may have an outer header creation indicating tunnel information and a destination interface set to the access side.

[0098] If the UPF is coupled to another UPF via an N19 tunnel and the traffic for local routing comes from the N19 tunnel, the FAR may have a destination interface set to the PIN internal value plus the PIN identifier.

[0099] If the UPF is coupled with another UPF via an N19 tunnel and traffic for local routing is directed to a first PEGC anchored by another UPF, the FAR may have an outer header creation and a destination interface, the outer header creation indicating tunnel information of the N19 tunnel, the destination interface being set to the core side.

[0100] Figure 7An exemplary PIN element 700 according to some embodiments is illustrated. The PIN element 700 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device (e.g., a smart watch), a loose IoT device. In some embodiments, the PIN element 700 can be a RedCap UE or a NR-Light UE.

[0101] PIN element 700 may include processor 704, RF interface circuit 708, memory / storage 712, user interface circuit 716, sensor circuit 720, driver circuit 722, power management integrated circuit (PMIC) 724, antenna structure 726, and battery 728. The components of PIN element 700 may be implemented as an integrated circuit (IC), part of an integrated circuit, discrete electronic device or other module, logic component, hardware, software, firmware, or a combination thereof. Figure 7 The block diagram of PIN element 700 is intended to show a high-level view of some of the components of PIN element 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0102] The components of PIN element 700 can be coupled to various other components via one or more interconnects 732, which can represent any type of interface, input / output, bus (local, system or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0103] Processor 704 may include processor circuits such as baseband processor circuit (BB) 704A, central processor unit circuit (CPU) 704B, and graphics processor unit circuit (GPU) 704C. Processor 704 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 712) to cause PIN element 700 to perform operations as described herein.

[0104] In some embodiments, the baseband processor circuit 704A can access the communication protocol stack 736 in the memory / storage device 712 to communicate through a 3GPP compatible network. In general, the baseband processor circuit 704A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 708.

[0105] The baseband processor circuit 704A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0106] The memory / storage 712 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 736) that may be executed by one or more of the processors 704 to cause the PIN element 700 to perform various operations described herein. The memory / storage 712 includes any type of volatile or non-volatile memory that may be distributed throughout the PIN element 700. In some embodiments, some of the memory / storage 712 may be located on the processor 704 itself (e.g., L1 cache and L2 cache), while other memory / storage 712 is located external to the processor 704 but can be accessed via a memory interface. The memory / storage 712 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0107] The RF interface circuit 708 may include a transceiver circuit and a radio frequency front end module (RFEM) that allows the PIN element 700 to communicate with other devices through a radio access network. The RF interface circuit 708 may include various components arranged in a transmission path or a reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0108] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 726 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 704.

[0109] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the signal through a power amplifier before the RF signal is radiated across the air interface via the antenna structure 726.

[0110] In various embodiments, the RF interface circuit 708 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0111] The antenna structure 726 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. The antenna structure 726 may have antenna panels that are omnidirectional, directional, or a combination thereof to achieve beamforming and multiple-input / multiple-output communications. The antenna structure 726 may include microstrip antennas, printed antennas manufactured on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna structure 726 may have one or more panels that are designed for specific frequency bands including bands in FR1 or FR2.

[0112] The user interface circuit 716 includes various input / output (I / O) devices designed to enable the user to interact with the PIN element 700. The user interface circuit 716 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, and in particular includes one or more physical or virtual buttons (e.g., reset buttons), physical keyboards, keypads, mice, touch pads, touch screens, microphones, scanners, headphones, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs) or more complex outputs (such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.)), wherein the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the PIN element 700.

[0113] Sensor circuitry 720 may include a device, module, or subsystem whose purpose is to detect events or changes in its environment and to communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0114] The driver circuit 722 may include software and hardware elements for controlling a specific device embedded in, attached to, or otherwise communicatively coupled to the PIN element 700. The driver circuit 722 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the PIN element 700. For example, the driver circuit 722 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 720 and controlling and allowing access to the sensor circuit 720, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, or an audio driver for controlling and allowing access to one or more audio devices.

[0115] The PMIC 724 may manage the power provided to the various components of the PIN element 700. Specifically, with respect to the processor 704, the PMIC 724 may control power supply selection, voltage scaling, battery charging, or DC-DC conversion.

[0116] In some embodiments, the PMIC 724 may control or otherwise become part of various power saving mechanisms of the PIN element 700. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the PIN element 700 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the PIN element 700 may transition to the RRC_Idle state, in which it is disconnected from the network and no operations (such as channel quality feedback, handover, etc.) are performed. The PIN element 700 enters an extremely low power state and performs paging, in which it wakes up again periodically to listen to the network and then powers off again. The PIN element 700 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for a time exceeding the paging interval (from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will incur significant latency, and it is assumed that latency is acceptable.

[0117] The battery 728 can power the PIN element 700, but in some examples, the PIN element 700 can be mounted in a fixed location and can have a power source coupled to the power grid. The battery 728 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 728 can be a typical lead-acid automotive battery.

[0118] Figure 8 Illustrated is a network node 800 according to some embodiments. The network node 800 may include a processor 804, a CN interface circuit 812, a memory / storage circuit 816, and an antenna structure 826.

[0119] Components of network node 800 may be coupled to various other components via one or more interconnects 828 .

[0120] The processor 804, memory / storage circuitry 816 (including the communication protocol stack 810), and interconnect 828 may be similar to those described with respect to Figure 7 Like named elements are shown and described.

[0121] The CN interface circuit 812 may provide a connection to a device implementing the functionality of a core network (e.g., 5GC 104) using a 5GC-compatible network interface protocol, such as a carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the network node 800 via optical fiber or wireless backhaul. The CN interface circuit 812 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 812 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0122] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0123] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuit associated with the UE, base station, or network element described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0124] Example

[0125] In the following sections, additional exemplary embodiments are provided.

[0126] Embodiment 1 includes a method of operating a personal Internet of Things network (PIN) application function (AF), the method comprising: obtaining configuration information from a PIN element with management capabilities (PEMC), the configuration information comprising Internet Protocol (IP) addresses for a first PIN element with gateway capabilities (PEGC) and a second PEGC; configuring parameters for local routing of PIN traffic between the first PEGC and the second PEGC; and sending the parameters to a network exposure function (NEF) in an association request.

[0127] Embodiment 2 includes a method according to embodiment 1 or some other embodiments herein, wherein the parameters include: data network name (DNN); single network slice selection assistance information (S-NSSAI); or protocol data unit (PDU) session type.

[0128] Embodiment 3 includes a method according to embodiment 1 or some other embodiments herein, wherein the parameter includes a PIN identifier.

[0129] Embodiment 4 includes a method according to embodiment 1 or some other embodiments herein, wherein the parameter includes a PIN element identifier associated with a PIN element to be provided with local routing support, the PIN element identifier including an IP address or a universal public subscription identifier (GPSI) of the PIN element.

[0130] Embodiment 5 includes the method of embodiment 4 or some other embodiments herein, wherein the PIN element is or is in direct communication with the first PEGC.

[0131] Embodiment 6 includes the method of embodiment 1 or some other embodiments herein, wherein the parameter includes an indication of a geographic location that supports local routing for the first PEGC and the second PEGC.

[0132] Embodiment 7 includes the method of embodiment 1 or some other embodiments herein, wherein the parameter includes an indication of timing constraints applicable to local routing of the first PEGC and the second PEGC.

[0133] Embodiment 8 includes the method of embodiment 1 or some other embodiments herein, wherein the parameter comprises a set of packet filters for identifying traffic for local routing associated with the first PEGC and the second PEGC.

[0134] Embodiment 9 includes a method of operating a session management function (SMF), the method comprising: receiving configuration parameters from a personal Internet of Things network (PIN) application function (AF) from a network exposure function (NEF); generating rules for local routing of traffic between a first PIN element (PEGC) with gateway capability and a second PEGC based on the AF configuration; and sending the rules to one or more user plane functions (UPF).

[0135] Embodiment 10 includes the method of embodiment 9 or some other embodiments herein, wherein the configuration parameters include: including a PIN identifier.

[0136] Embodiment 11 includes the method according to embodiment 10 or some other embodiments herein, the method further comprising: sending the rule to one or more UPFs to establish a group level N4 session using the PIN identifier.

[0137] Embodiment 12 includes a method according to embodiment 9 or some other embodiments herein, wherein the configuration parameters include a PIN element identifier associated with a PIN element to be provided with local routing support, the PIN element identifier including an IP address or a universal public subscription identifier (GPSI) of the PIN element.

[0138] Embodiment 13 includes the method of embodiment 9 or some other embodiments herein, wherein the PIN element is or is in direct communication with the first PEGC.

[0139] Embodiment 14 includes the method of embodiment 9 or some other embodiments herein, wherein the configuration parameters include an indication of a geographic location that supports local routing for the first PEGC and the second PEGC.

[0140] Embodiment 15 includes the method of embodiment 9 or some other embodiments herein, wherein the parameter includes an indication of a timing constraint applicable to local routing of the first PEGC and the second PEGC.

[0141] Embodiment 16 includes a method of operating a user plane function (UPF), the method comprising: receiving rules for local routing of traffic between a first personal internet of things network (PIN) element (PEGC) with gateway capability and a second PEGC of the PIN from a session management function (SMF), wherein the rules include packet detection rules (PDRs) and forwarding action rules (FARs); identifying the traffic based on the PDRs; and forwarding the traffic based on the FARs.

[0142] Embodiment 17 includes a method according to embodiment 16 or some other embodiments herein, wherein: the UPF anchors a protocol data unit (PDU) session for the first PEGC; the traffic comes from the first PEGC; the PDR has a source interface and core network tunnel information, the source interface is set to the access side, the core network tunnel information is set to the protocol data unit (PDU) session tunnel header associated with the PDU session; and the FAR has a destination interface, the destination interface is set to the PIN internal value plus an identifier associated with the PIN.

[0143] Embodiment 18 includes a method according to embodiment 16 or some other embodiments herein, wherein: the UPF anchors a protocol data unit (PDU) session for the first PEGC; the traffic is directed toward the first PEGC; the PDR has a source interface and a destination address, the source interface is set to the value of the internal PIN interface plus an identifier associated with the PIN, and the destination address is set to the IP address of the first PEGC or the PIN element associated with the first PEGC; and the FAR has an outer header creation and a destination interface, the outer header creation is used to indicate tunnel information, and the destination interface is set to the access side.

[0144] Embodiment 19 includes a method according to embodiment 17 or some other embodiments herein, wherein: the UPF is a first UPF; the first UPF is coupled to a second UPF via an N19 tunnel; the traffic comes from the N19 tunnel; the PDR has a source interface and core network tunnel information, the source interface is set to the core side, the core network tunnel information is set to the N19 tunnel header associated with the N19 tunnel; and the FAR has a destination interface, the destination interface is set to the value of the internal PIN interface plus an identifier associated with the PIN.

[0145] Embodiment 20 includes the method according to embodiment 16 or some other embodiments herein, the method further comprising: the UPF is a first UPF; the first UPF is coupled to a second UPF via an N19 tunnel; the traffic is directed toward the first PEGC, and the first PEGC is anchored by the second UPF; the PDR has a source interface and a destination address, the source interface is set to the value of the internal PIN interface plus an identifier associated with the PIN, and the destination address is set to the IP address of the first PEGC or the PIN element associated with the first PEGC; and the FAR has an external header creation and a destination interface, the external header creation indicates tunnel information of the N19 tunnel, and the destination interface is set to the core side.

[0146] Example 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1 to 20, or any other method or process described herein.

[0147] Embodiment 22 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Embodiments 1 to 20 or any other method or process described herein.

[0148] Embodiment 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0149] Embodiment 24 may include methods, techniques or processes described or related to any one of Embodiments 1 to 20, or parts or components thereof.

[0150] Embodiment 25 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0151] Embodiment 26 may include a signal as described or related to any one of Embodiments 1 to 20, or a portion or component thereof.

[0152] Embodiment 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of Embodiments 1 to 20, or otherwise described in the present disclosure.

[0153] Embodiment 28 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in this disclosure.

[0154] Embodiment 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0155] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 20.

[0156] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0157] Embodiment 32 may include signals in a wireless network as shown and described herein.

[0158] Embodiment 33 may include a method of communicating in a wireless network as shown and described herein.

[0159] Embodiment 34 may include a system for providing wireless communications as shown and described herein.

[0160] Embodiment 35 may include an apparatus for providing wireless communications as shown and described herein.

[0161] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0162] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method for operating a personal Internet of Things network (PIN) application function (AF), the method comprising: obtaining configuration information from a PIN element with management capabilities (PEMC), the configuration information including Internet Protocol (IP) addresses for a first PIN element with gateway capabilities (PEGC) and a second PEGC; configuring parameters for local routing of PIN traffic between the first PEGC and the second PEGC; as well as The parameters are sent to the Network Exposure Function (NEF) in an association request.

2. The method according to claim 1, wherein the parameters include: Data Network Name (DNN); Single Network Slice Selection Auxiliary Information (S-NSSAI); or protocol data unit (PDU) session type. The method of claim 1 , wherein the parameter comprises a PIN identifier.

4. The method of claim 1, wherein the parameter comprises a PIN element identifier associated with a PIN element to be provided with local routing support, the PIN element identifier comprising an IP address or a General Public Subscription Identifier (GPSI) of the PIN element.

5. The method of claim 4, wherein the PIN element is the first PEGC or is in direct communication with the first PEGC.

6. The method of claim 1, wherein the parameter comprises an indication of a geographic location for which local routing is supported for the first PEGC and the second PEGC.

7. The method of claim 1, wherein the parameters include an indication of timing constraints applicable to local routing of the first PEGC and the second PEGC.

8. The method of claim 1, wherein the parameters include a set of packet filters for identifying traffic for local routing associated with the first PEGC and the second PEGC.

9. One or more computer-readable media having instructions that, when executed, cause a session management function (SMF): receiving configuration parameters from the Personal IoT Network (PIN) Application Function (AF) from the Network Exposure Function (NEF); generating rules for local routing of traffic between a first PIN element (PEGC) with gateway capability and a second PEGC based on the configuration parameters; and The rules are sent to one or more User Plane Functions (UPFs).

10. One or more computer-readable media according to claim 9, wherein the configuration parameters include: Includes a PIN identifier.

11. The one or more computer-readable media of claim 10, wherein the instructions, when executed, further cause the SMF to: The rules are sent to one or more UPFs to establish a group level N4 session using the PIN identifier.

12. One or more computer-readable media according to claim 9, wherein the configuration parameters include a PIN element identifier associated with a PIN element to be provided with local routing support, the PIN element identifier including an IP address or a universal public subscription identifier (GPSI) of the PIN element.

13. The one or more computer-readable media of claim 9, wherein the PIN element is or is in direct communication with the first PEGC.

14. The one or more computer-readable media of claim 9, wherein the configuration parameters include an indication of a geographic location for which local routing is supported for the first PEGC and the second PEGC.

15. The one or more computer-readable media of claim 9, wherein the configuration parameters include an indication of timing constraints applicable to local routing of the first PEGC and the second PEGC.

16. A user plane function (UPF), the user plane function (UPF) comprising: Interface circuit; as well as A processing circuit, the processing circuit is coupled to the interface circuit, and the processing circuit is used to: receiving from a session management function (SMF) rules for local routing of traffic between a first personal internet of things network (PIN) element (PEGC) having gateway capabilities and a second PEGC of the PIN, wherein the rules include a packet detection rule (PDR) and a forwarding action rule (FAR); identifying the traffic based on the PDR; as well as The traffic is forwarded based on the FAR.

17. The UPF of claim 16, wherein: The UPF anchors a protocol data unit (PDU) session for the first PEGC; The traffic is from the first PEGC; The PDR has a source interface and core network tunnel information, the source interface is set to the access side, and the core network tunnel information is set to a PDU session tunnel header associated with the PDU session; as well as The FAR has a destination interface which is set to the PIN internal value plus an identifier associated with the PIN.

18. The UPF of claim 16, wherein: The UPF anchors a protocol data unit (PDU) session for the first PEGC; The traffic is toward the first PEGC; the PDR having a source interface and a destination address, the source interface being set to the value of the internal PIN interface plus an identifier associated with the PIN, the destination address being set to an Internet Protocol (IP) address of the first PEGC or a PIN element associated with the first PEGC; as well as The FAR has an outer header creation for indicating tunnel information and a destination interface which is set to an access side.

19. The UPF of claim 16, wherein: The UPF is a first UPF; The first UPF is coupled to the second UPF via an N19 tunnel; The traffic comes from the N19 tunnel; The PDR has a source interface and core network tunnel information, the source interface is set to the core side, and the core network tunnel information is set to the N19 tunnel header associated with the N19 tunnel; as well as The FAR has a destination interface which is set to the value of the internal PIN interface plus an identifier associated with the PIN.

20. The UPF of claim 16, wherein: The UPF is a first UPF; The first UPF is coupled to the second UPF via an N19 tunnel; The flow is toward the first PEGC, and the first PEGC is anchored by the second UPF; the PDR having a source interface and a destination address, the source interface being set to the value of the internal PIN interface plus an identifier associated with the PIN, the destination address being set to the IP address of the first PEGC or a PIN element associated with the first PEGC; as well as The FAR has an outer header creation indicating tunnel information of the N19 tunnel and a destination interface set to a core side.

Images