Systems and methods for personal internet of things network local routing policy control

Abstract

Systems and methods for personal internet of things (loT) network (PIN) local routing policy control are discussed herein. In some cases, an application function (AF) interacts with a core network (CN) of a wireless communication system via network exposure function (NEF) Trafficinfluence service to request local routing through the CN for PIN elements (PINEs) of a PIN (e.g., for PIN elements with gateway capability (PEGCs) of the PIN). In some cases, subscription information for one or a group of UEs of the PIN (e.g., PEGC(s) of the PIN) may be provided that can be used to configure and control local routing through the CN as between those PINEs of the PIN. The local routing through the CN makes the transport of the data within the PIN and across the CN as between two PINEs (e.g., PINEs connected to the CN through different PEGCs of the PIN) transparent to those PINEs.

Description

SYSTEMS AND METHODS FOR PERSONAL INTERNET OF THINGS NETWORKLOCAL ROUTING POLICY CONTROLTECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including local routing policy control for local routing through a CN for personal internet of things networks.

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi*).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example. Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN). Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE). and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G CN (5GC).BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act. the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0008] FIG. 1 A illustrates a diagram showing the arrangement of a PIN that is in communication with an AF of a DN via an NG-RAN and a segment of a 5G CN, according to embodiments herein.

[0009] FIG. IB illustrates a diagram showing the arrangement of a PIN that is in communication with an AF of a DN via an NG-RAN and a segment of a 5G CN, according to embodiments herein.

[0010] FIG. 2 illustrates a table illustrating examples of information elements that maybe contained in a service request from an AF to a PCF for establishing local routing through a CN for a PIN, according to some embodiments discussed herein.

[0011] FIG. 3 illustrates a method of a UDM entity of a CN, according to embodiments discussed herein.

[0012] FIG. 4 illustrates a method of a UDM entity of a CN, according to embodiments discussed herein.

[0013] FIG. 5 illustrates a method of a PCF of a CN, according to embodiments discussed herein.

[0014] FIG. 6 illustrates a method of an SMF of a CN, according to embodiments discussed herein.

[0015] FIG. 7 illustrates a method of a PCF of a CN, according to embodiments discussed herein.

[0016] FIG. 8 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0017] FIG. 9 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION

[0018] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0019] FIG. 1 A illustrates a diagram 100 showing the arrangement of a personal internet of things (loT) network (PIN) 102 that is in communication with an application function (AF) 104 of a data network (DN) 106 via an NG- RAN 108 and a segment of a 5G CN 110, according to embodiments herein.

[0020] Data traffic transport between a PIN 102 and an AF 104, which is present on a DN 106 (that represents, for example, Internet services) that is accessible to the PIN 102 through the NG-RAN 108 and the 5G CN 110, as illustrated, may be desirable. It may be understood that a PIN element (PINE) of the PIN 102 (described below) may access an application server of the AF 104 through this route. In this manner, data can be transported into the PIN 102 from external services associated with the AF 104 and / or transported out of the PIN 102 to the external service(s) associated with the AF 104. Further, it is contemplated that in some cases, the AF 104 can influence the traffic of / for the PIN 102.

[0021] A PIN 102 may be a configured and managed group of PINEs. PINEs illustrated in FIG. 1 A include the PINE 112, the PIN element with gateway capability (PEGC) 114, and the PIN element with management capability (PEMC) 116. Note that the PINE 112 is referred to in the generic because it does not perform the functions of a more particular type of PINE such as those of a PEGC 114 and / or of a PEMC 116 as described herein.

[0022] Each of the PINEs of the PIN 102 (e.g., the PINE 112, the PEGC 114, and / or the PEMC 116) may be able to communicate with each other either directly or via the PEGC 114. This managed group of PINEs may further communicate with the 5G CN 110 acrossthe NG-RAN 108 via at least the PEGC 114 and may be managed by at least the PEMC 116. The number and arrangement of the PINEs 112, 114, and 116 within the PIN 102 in FIG. 1A is given by way of example and not by way of limitation.

[0023] A PINE (e.g., as in the PINE 112) may be a UE or some other (e.g., non-3GPP) device that can communicate with other PINE(s) within the PIN 102. This communication can be made through a number of ways, including PIN direct connection, through the PEGC 114, or through the PEGC 114 and the 5G CN 110. A PINE may also communicate outside the PIN through the PEGC 114 and the 5G CN 110.

[0024] The PEGC 114 may further have the ability to provide connectivity to and from the 5G CN 110 through the NG-RAN 108 for other PINEs in the PIN 102. The PEGC 114 may also provide relay for the communication between PINEs in the PIN 102.

[0025] The PEMC 116 may further have the capability to manage the PIN 102.

[0026] Note that a PINE could alternatively have the features of both the PEGC 114 and the PEMC 116, as these are described herein.

[0027] While the embodiment of FIG. 1A illustrates a single grouping of PINEs 112, 114, and 116 using a PEGC 114 of the PIN 102, it is contemplated that the PIN 102 could include other elements that use another PEGC. For example, FIG. IB illustrates that the PIN 102 also includes (in addition to the PINEs 112, 114, 116 previously discussed, which connect back to the AF 104 through the PEGC 114) a second set of PINEs, a PINE 138 (which may have analogous functions as the PINE 112) and a PEGC 140 (which may have analogous functions as the PEGC 114) that connect back to the AF 104 through the PEGC 140. Note that in such cases, data traffic of the PIN 102 flowing as between two PINEs behind different PEGCs (e.g., data traffic 142 from one of the PINEs 112, 114, or 116 to one of the PINEs 138 and 140, as illustrated) accordingly flows through the PEGC 114 and the PEGC 140 and across the NG-RAN 108 and / or the 5G CN 110. (Note that in FIG. IB. the details of the 5G CN 110 as these are presented in FIG. 1A have been removed only for illustrative purposes).

[0028] Returning to FIG. 1A, it is noted that while FIG. 1A illustrates the use of an NG-RAN 108 in the context of a 5G / NR assumption, and further that the 5G CN 110 illustrates various CN elements in the context of the same 5G / NR system assumption. However, it should be understood that similar and / or analogous RANs / CNs / CN elements could be provided / used within other system context assumptions (e.g., LTE, 6G systems context assumptions). Accordingly, discussion of particularly an NG-RAN 108, the 5GCN 110, and / or particular elements of the 5G CN 110 as based on a 5G / NR assumption should be understood here as given by way of example and not by way of limitation.

[0029] A PINE-to-PINE communication is a communication between two PINEs which may use PINE-to-PINE direct connection or PINE-to-PINE indirect connection. A PINE- to-PINE direct connection is a connection between two PINEs without the use of a PEGC 114, any NG-RAN 108, or any 5G CN 110 in the middle. A PINE-to-PINE indirect connection is a connection between two PINEs via a PEGC 114 and / or via a PEGC 114 and a user plane function (UPF) (e.g., UPF 136).

[0030] PINE-to-PINE routing routes traffic between two PINEs through a PEGC 114, where the two PINEs directly connect with the PEGC 114 via non-3GPP access (e.g., WiFi, Bluetooth).

[0031] PINE-to-Network routing routes traffic between PINEs through a PEGC 114 and a 5G CN 110. The PINE directly connects with the PEGC 114 via non-3GPP access (e.g., WiFi, Bluetooth) separately.

[0032] A network local switch for PIN routes traffic by UPFs 136 between two PINEs, where the two PINEs use two different PEGCs (e.g., the PEGC 114 for a first PINE in the PIN 102 and a second PEGC of the PIN 102 that separately accesses the NG-RAN 108 and / or the 5G CN 110) via non-3GPP access (e.g. WiFi. Bluetooth) separately.

[0033] A PI reference point 118 operates between a PINE 112 and the PEMC 116. This reference point is based on non-3GPP access (e.g., WiFi, Bluetooth, etc.) and may be used to provide data as between the PINE 112 and the PEMC 116.

[0034] A P2 reference point 120 operates between the PINE 112 and the PEGC 114. This reference point can be based on non-3GPP access (e.g., WiFi, Bluetooth, etc.), the direct user plane path to the 5G CN 110, a relay path via the PEGC 114, or other communication path (e.g., via Internet).

[0035] A P3 reference point 122 operates between the PEMC 116 and the PEGC 114. This reference point is based on non-3GPP access (e.g., WiFi, Bluetooth) or via sidelink (e.g.. 5G ProSe Direct Communication).

[0036] The PEMC 116 may be configured to perform a number of functions. First functions of the PEMC 116 may relate to the management of associated PINs. The scope of management may include the ability to further manage, modify, or delete a PIN (e.g.. such as the PIN 102).

[0037] In addition to PIN-level operations, the PEMC 116 may also perform functions relating to the management of PINEs. With this functionality, the PEMC 116 may add and remove desired PINEs into / out of the PIN 102. Along with managing PINEs, the PEMC 116 may also add and remove desired PEGCs (e.g., such as the PEGC 114 and / or the PEGC 140).

[0038] Another function of the PEMC 116 may be to allocate a PINE identifier (ID) for an associated PINE.

[0039] Further functions of the PEMC 116 may include operations pertaining to the storage of different types of PIN profile data. PIN profile data (e.g., for the PIN 102) may be a type of data managed by the PEMC 116. The PEMC 116 may store a variety of information about PIN profiles, which may include, but is not limited to, PIN IDs, PIN names, validity times, and more.

[0040] Further functions of the PEMC 116 may include operations pertaining to the storage of different types of PINE profile data. The PEMC 116 may store a variety of information about PINE profiles, which may include, but is not limited to PINE IDs. PINE types, PINE capabilities, validity time, and more.

[0041] Another function of the PEMC 116 may be to support the discovery7of PINEs and / or PINs.

[0042] The PEGC 114 may be configured to perform a number of functions. In some cases, the PEGC 114 supports the relaying of traffic between a PINE of the PIN 102 and the 5G CN 110.

[0043] Additional functionalities of the PEGC 114 may include, but are not limited to, supporting the traffic relaying between PINEs, supporting PIN discovery, and accessing control and traffic enforcement for PINEs.

[0044] Note that the PEGC 140 may be configured to perform analogous functions to those described in relation to PEGC 114.

[0045] The PINE 112 may be configured to perform a number of functions. In at least one example, some of the functions of the PINE 112 can include discovery and communication with the PEGC 114. Another function of the PINE 112 can be communication with other PINEs directly, via the 5G CN 110. or via the PEGC 114.

[0046] Note that the PINE 138 may be configured to perform analogous functions to those described in relation to the PINE 112.

[0047] Elements illustrated as part of the 5G CN 110 are now discussed. In at least one example, the PIN architecture can also include further functionality utilizing the unified data management (UDM) 124 functionality. The addition of UDM 124 may be advantageous to the PIN architecture in that it may allocate PIN IDs associated with PEMC 116 IDs.

[0048] The UDM 124 further supports generation of 3GPP Authentication and Key Management (AKA) Authentication Credentials, User Identification Handling (e.g., storage and management of Subscription Permanent Identifier (SUPI) for each subscriber in the 5G system), de-concealment of a privacy-protected Subscription Concealed Identifier (SUCI). access authorization based on subscription data (e.g.. roaming restrictions), UE's Serving network function (NF) Registration Management (e g., storing serving access and mobility management function (AMF) 130 for UE, storing serving session management function (SMF) 132 for UE's protocol data unit (PDU) session), service / session continuity (e.g., by keeping SMF / data network name (DNN) assignment of ongoing sessions, mobile terminating short message service (MT-SMS) delivery, Lawful Intercept (LI) Functionality (especially in outbound roaming cases where a UDM 124 is the only point of contact for LI), subscription management, short message service (SMS) management, 5GLAN group management handling, and / or external parameter provisioning (Expected UE Behavior parameters or Network Configuration parameters). To provide such functionality, the UDM 124 uses subscription data (including authentication data) that may be stored in a unified data repository' (UDR) 128, in which case a UDM 124 implements the application logic and may not require an internal user data storage and several different UDMs 124 may serve the same user in different transactions. The UDM 124 may be located in the home public land mobile network (HPLMN) of the subscribers it serves and may access the information of the UDR 128 located in the same public land mobile network (PLMN).

[0049] The policy control function (PCF) 126 supports a unified policy framework to govern network behavior. The PCF 126 provides policy rules to control plane function(s) to enforce them. The PCF 126 accesses subscription information relevant for policydecisions in a UDR. The PCF 126 may access the UDR located in the same PLMN as the PCF.

[0050] The AMF 130 supports termination of RAN control plane (CP) interface (N2), termination of non-access stratum (NAS) (Nl) for NAS ciphering and integrityprotection, registration management, connection management, reachability management, Mobility Management, lawful intercept (for AMF 130 events and interface to LI System), transport for session management (SM) messages between UE and SMF 132, transparent proxy for routing SM messages, Access Authentication, Access Authorization, transport for SMS messages between UE and short message service function (SMSF), security anchor function (SEAF), Location Services management for regulatory services, transport for Location Services messages between UE and location management function (LMF) as well as between RAN and LMF, evolved packet system (EPS) Bearer ID allocation for interworking with EPS, UE mobility7event notification, Control Plane cellular loT (CIoT) 5GS Optimization, User Plane CIoT 5GS Optimization, provisioning of external parameters (Expected UE Behavior parameters or Network Configuration parameters), and / or Network Slice-Specific Authentication and Authorization. Some or all of the AMF 130 functionalities may be supported in a single instance of the AMF 130. Regardless of the number of Network functions, in certain embodiments there is only one NAS interface instance per access network between the UE and the CN. terminated at one of the Network functions that implements at least NAS security and Mobility Management. The AMF 130 may also include policy related functionalities.

[0051] In addition to the functionalities described above, the AMF 130 may include the following functionality to support non-3GPP access networks: support of N2 interface with N3IWF / TNGF, over which some information (e.g., 3GPP Cell Identification) and procedures (e.g., Handover related) defined over 3GPP access may not apply, and non- 3GPP access specific information may be applied that do not apply to 3GPP accesses; support of NAS signaling with a UE over N3IWF / TNGF, wherein some procedures supported by NAS signaling over 3 GPP access may be not applicable to untrusted non- 3GPP (e.g., Paging) access; support of authentication of UEs connected over N3IWF / TNGF; management of mobility, authentication, and separate security context state(s) of a UE connected via a non-3GPP access or connected via a 3GPP access and a non-3GPP access simultaneously; support a coordinated registration management (RM) management context valid over a 3GPP access and a Non 3GPP access; and / or support dedicated configuration management (CM) management contexts for the UE for connectivity over non-3GPP access. Not all of the above functionalities may be required to be supported in an instance of a Network Slice.

[0052] The session management function (SMF) 132 supports Session Management (e.g.. Session Establishment, modify and release, including tunnel maintain between UPF 136 and access network (AN) node), UE internet protocol (IP) address allocation & management (including optional Authorization) wherein the UE IP address may be received from a UPF 136 or from an external data network, DHCPv4 (server and client) and DHCPv6 (server and client) functions, functionality to respond to Address Resolution Protocol requests and / or IPv6 Neighbor Solicitation requests based on local cache information for the Ethernet PDUs (e g., the SMF 132 responds to the address resolution protocol (ARP) and / or the IPv6 Neighbor Solicitation Request by providing the medium access control (MAC) address corresponding to the IP address sent in the request), selection and control of User Plane functions including controlling the UPF 136 to proxy ARP or IPv6 Neighbor Discovery or to forward all ARP / IPv6 Neighbor Solicitation traffic to the SMF 132 for Ethernet PDU Sessions, traffic steering configuration at the UPF 136 to route traffic to proper destinations, 5G virtual network (VN) group management (e.g., maintain the topology of the involved PDU session anchor (PSA) UPFs, establish and release the N19 tunnels between PSA UPFs 136, configure traffic forw arding at UPF 136 to apply local switching, and / or N6-based forwarding or N19-based forwarding), termination of interfaces towards Policy control functions, lawful intercept (for SM events and interface to LI System), charging data collection and support of charging interfaces, control and coordination of charging data collection at the UPF 136, termination of SM parts of NAS messages, Downlink Data Notification, Initiator of AN specific SM information sent via AMF 130 over N2 to AN, determination of session and service continuity (SSC) mode of a session, Control Plane CIoT 5GS Optimization, header compression, acting as I-SMF in deployments where I- SMF can be inserted / removed / relocated, provisioning of external parameters (Expected UE Behavior parameters or Network Configuration parameters), proxy call session control function (P-CSCF) discovery for IP multimedia subsystem (IMS) services, roaming functionality (e.g.. handle local enforcement to apply QoS service level agreements (SLAs) (virtual public land mobile network (VPLMN)). charging data collection and charging interface (VPLMN), and / or lawful intercept (in VPLMN for SM events and interface to LI System), interaction with external DN for transport of signaling for PDU Session authentication / authorization by external DN, and / or instructing UPF 136 and NG-RAN to perform redundant transmission on N3 / N9 interfaces. Some or all of the SMF 132 functionalities may be supported in a singleinstance of an SMF 132. However, in certain embodiments, not all of the functionalities are required to be supported in an instance of a Network Slice. In addition to these functionalities, the SMF 132 may include policy related functionalities.

[0053] The network exposure function (NEF) 134 supports exposure of capabilities and events. NF capabilities and events may be securely exposed by the NEF 134 (e.g., for 3rd party, Application Functions, and / or Edge Computing). The NEF 134 may store / retrieve information as structured data using a standardized interface (Nudr) to a Unified Data Repository (UDR 128). The NEF 134 may also secure provision of information from an external application to 3GPP network and may provide for the Application Functions to securely provide information to the 3GPP network (e.g., expected UE behavior, 5GLAN group information, and service specific information), wherein the NEF 134 may authenticate and authorize and assist in throttling the Application Functions (AFs). The NEF 134 may provide translation of internal-external information by translating between information exchanged with an AF and information exchanged with the internal network function. For example, the NEF 134 translates between an AF-Service-Identifier and internal 5G Core information such as DNN and single-network slice selection assistance information (S-NSSAI). The NEF 134 mayhandle masking of network and user sensitive information to external AF's according to the network policy. The NEF 134 may receive information from other network functions (based on exposed capabilities of other network functions) and stores the received information as structured data using a standardized interface to a UDR 128. The stored information can be accessed and re-exposed by the NEF 134 to other network functions and Application Functions and used for other purposes such as analytics. For external exposure of services related to specific UE(s), the NEF 134 may reside in the HPLMN. Depending on operator agreements, the NEF 134 in the HPLMN may have interface(s) with NF(s) in the Visited (VPLMN). When a UE is capable of switching between EPC and 5GC, a service capability exposure function (SCEF) + NEF may be used for service exposure.

[0054] The user plane function (UPF) 136 may act as an anchor point for intra- RAT and inter- RAT mobility, an external PDU session point of interconnect to the DN 106. and a branching point to support multi-homed PDU session. The UPF 136 may also perform packet routing and forwarding, perform packet inspection, enforce user plane part of policy rules, lawfully intercept packets, perform traffic usage reporting, performQoS handling for user plane (e g., packet filtering, gating, UL / DL rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), perform transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 136 may include an uplink classifier to support routing traffic flows to a data network.

[0055] The DN 106 may represent various network operator services, Internet access, or third party services. The DN 106 may include, for example, an application server.

[0056] A PIN may include one or more PINEs (which are members of the PIN), one or more PEGCs, and / or one or more PEMCs. In some embodiments, it may be that only the PEGC(s) of a PIN are visible to a CN as UE(s). Consistent with disclosure herein, a PEGC may have specific subscription data that allows it to function as a PIN gateway in order to relay traffic between PINEs (when the PINEs are connected to the same PEGC) or over a CN and to another PEGC (when the PINEs are connected to different PEGCs) or over the CN to external data network (DN) (e g., an application server).

[0057] A PIN may support / function using local routing of data traffic for the PIN through the CN. Such a local routing through the CN may permit any PINE of a PIN to communicate with any other PINE of the PIN without the PINE performing an express packetization for handling transport through the CN (even in cases where the two PINEs of the PIN are connected to the CN through different PEGCs). In other words, the enablement of local routing of data traffic for the PIN over the CN causes that the transport of PIN data traffic through the CN is transparent to the PINEs of the PIN. Further, such local routing is not dependent on an AF or on a router for the routing of data traffic in the PIN as between two different PEGCs.

[0058] In some cases, this local routing is realized within the CN when an SMF configures a UPF with a set of one or more packet detection rules (PDRs) and one or more forwarding action rules (FARs). These PDRs and FARs act using IP filtering, detecting IP packets based on a PDR and then forwarding them based on attributes of a corresponding FAR.

[0059] In regard to local routing over the CN, multiple options are possible. In the context of a 5G wireless communication system, one option may be to use existing procedures for 5G virtual networks (VNs). Another option may be to make modifications to 5G VN procedures to adapt these for use in the PIN context.

[0060] Another option may be to define procedures not linked to 5G VN parameter provisioning (e.g., using a network exposure function (NEF) Trafficinfluence application programming interface (API)).

[0061] In some wireless communication systems, an NEF Trafficinfluence service allows an application function (AF) to specify traffic routing preferences for a UE or a group of UEs. See, e.g., 3GPP Technical Specification (TS) 23.502, version 18.1.1 (April 2023), section 5.2.6.7.

[0062] However, a prior intention of the Trafficinfluence API was to allow local access to a DN. In this context, the Trafficinfluence service allows the AF to specify, for identified traffic (e.g., using internet protocol (IP) 5tuple or Application Identifier), a DN access identifier (DNAI) that allows local access depending on the UE's location. This information may then be taken into account by the SMF while selecting a UPF or inserting an uplink classifier (UL CL) / branching point for a target UE's PDU session.

[0063] When considering the use of the Trafficinfluence service in the PIN context, it has been determined that the Trafficinfluence service may be configured to allow an AF to request that identifies traffic from the target set of UEs be allowed local routing within the wireless communication system (e g., through the CN).

[0064] Accordingly, various enhancements to an NEF Trafficinfluence service and corresponding policy and charging control (PCC) rules are discussed herein. In some embodiments, an NEF Trafficinfluence service is enhanced to allow an AF to send a request to a PCF for local routing of identified traffic through the CN. The AF may provide an indication of local routing along with the target UEs for which the request applies (where such target UEs that are indicated may be, for example, PEGCs of the PIN for which local routing through the CN is desired).

[0065] The request for local routing may include a Boolean flag (indicating that local routing is wanted) along with an identifier(s) corresponding to the target set of UEs (e.g., the PEGCs) of the PIN for which local routing is wanted.

[0066] The identifier(s) corresponding to the PEGCs may be one or more of: IP addresses of the target set of UEs, general public subscription identifiers (GPSIs) for the target set of UEs, a PIN ID for a PIN of the target set of UEs, an external group identifier for the target set of UEs, and / or a specific combination of data DNN / S-NSSAI that is assigned to the PIN of the target set of UEs. Note that an AF may include / identify multiple such groups of target UEs in a service request.

[0067] FIG. 2 illustrates a table 200 illustrating examples of information elements that may be contained in a service request from an AF to a PCF for establishing local routing through a CN for a PIN, according to some embodiments discussed herein. As illustrated, in some embodiments, a traffic local routing indication information element 202 may be use in a service request for local routing for a PIN by an AF. The presence of this field may indicate that local routing with a CN is wanted. It may be that, as illustrated, if the traffic local routing indication information element 202 is included in the service request, the service request does not include a list of DNAIs.

[0068] As illustrated, in some embodiments, an indication of traffic correlation information element 204 and a traffic correlation ID information element 206 may be used in a service request for local routing for a PIN by an AF. In cases where the traffic correlation ID information element 206 corresponds to a PIN, the indication of traffic correlation information element 204 may be used (e.g., instead of / in addition to the traffic local routing indication information element 202) to indicate that local routing for the indicated PIN is wanted.

[0069] The traffic correlation ID information element 206 may be understood to correspond to / identify a set of PEGCs of the PIN in such cases.

[0070] For some 5G communication systems, the information in the table 200 may be considered in addition to that found in 3GPP TS 23.501, version 18.1.0 (March 2023), table 5.6.7-1 (describing information elements that may be contained in an AF request). For example, it may be that the traffic local routing indication information element 202 is a new information element for such contexts, while the indication of traffic correlation information element 204 and the traffic correlation ID information element 206 are understood as new uses / understandings / applications of existing information elements under that system.

[0071] However it is made, the indication of local routing information is used by PCF to establish a PCC rule that causes local routing through a CN for the data traffic between the target set of UEs (e.g., the PEGCs of the PIN). Such an application may fall under a definition in the wireless communication system for AF-influenced traffic steering enforcement control with respect to such PCC rules.

[0072] In some embodiments, local routing through the CN for the PIN may also be indicated as part of subscription information that is applicable to one or more UEs of the PIN (e.g., the PEGCs of the PIN). For example, in such circumstances, it may be thatPEGCs of PINs that use local routing have a special field indicating the permission to have local routing in the CN.

[0073] For example, in some cases, PIN subscription data for a UE may be incorporated as a UE subscription data ty pe within the wireless communication systems. In such cases, one or more PIN IDs may be provided as PIN subscription data for a UE, and for each PIN ID a field (e.g., a '‘Traffic Local routing enabled” field) may indicate whether or not local routing through the CN should be enabled for the UE with respect to that PIN. Definitions for this behavior for some 5G wireless communication systems may be added to, for example, 3GPP TS 23.502, version 18.1.1 (April 2023), Table 5.2.3.3.1-1.

[0074] As a further example, in some cases, such subscription data with respect to a UE may be identifiable based on group subscription data for a group of UEs that includes the UE, where that group subscription data incorporates PIN aspects. In the case of PIN information / a PIN context, it may be that the group subscription data for the group of UEs includes information regarding whether local routing through the CN is applicable for that group of UEs. Definitions for this behavior for some 5G wireless communication systems may be added to, for example, 3GPP TS 23.502, version 18.1.1 (April 2023), Table 5.2.3.3. 1-2.

[0075] The subscription information as discussed herein may be provided by a UDM of the CN and be consumed by other CN NFs (e.g., by a PCF and / or an SMF). The subscription information may be so provided in response to a request for the same from the other CN NF.

[0076] In the case where a PIN is configured for local routing through the CN, that PIN may be determined to be restricted to a unique PDU session (where no other PIN is allowed to use the same protocol data unit PDU session). This in turn implies that a unique UE route selection policy (URSP) rule is needed for the UEs understood to be part of this PIN. Accordingly, in such cases, it may be that the PCF uses the subscription information to install a first URSP rule to the UEs of the PIN which causes these UE(s) to use the unique PDU session for the PIN. The PCF may further ensure that no other PIN ID traffic descriptor for other URSP rule(s) refers to a same route selection descriptor (RSD) as is used in this first URSP rule.

[0077] Further, the SMF may use such subscription information to prevent a PEGC from using the unique PDU session for traffic from multiple PINs. In this regard, the SMF may reject any PDU session modification from a UE that indicates a PIN ID that isdifferent from / does not correspond to the PIN that has been assigned to the applicable DNN / S-NSSAI.

[0078] Note finally that in some embodiments, it may be that the wireless communication system is configured for both the use of the AF requests through an NEF Trafficinfluence service to control local routing through the CN for the PIN and the use of subscription information to control local routing through the CN for the PIN. In cases where both mechanisms are implemented, then it may be that the subscription information takes precedence over any AF requests through the NEF Trafficinfluence service.

[0079] FIG. 3 illustrates a method 300 of a UDM entity7of a CN, according to embodiments discussed herein. The method 300 includes receiving 302, from an NF consumer of the CN, a request for group subscription data for a group of UEs. The method 300 further includes providing 304. to the NF consumer, the group subscription data for the group of UEs in response to the request; wherein the group subscription data for the group of UEs comprises a PIN identifier for the group of UEs and an indication of whether a PIN identified by the PIN identifier uses local routs through the CN.

[0080] In some embodiments of the method 300, each UE in the group of UEs is a PEGC of the PIN.

[0081] In some embodiments of the method 300, the NF consumer is a PCF.

[0082] In some embodiments of the method 300, the NF consumer is an SMF.

[0083] FIG. 4 illustrates a method 400 of a UDM entity of a CN, according to embodiments discussed herein. The method 400 includes receiving 402, from an NF consumer of the CN, a request for PIN subscription data for a UE. The method 400 further includes providing 404. to the NF consumer, the PIN subscription data for the UE in response to the request; wherein the PIN subscription data for the UE comprises a PIN identifier for the UE and an indication of whether a PIN identified by the PIN identifier is allowed to use local routs through the CN.

[0084] In some embodiments of the method 400, the UE is a PEGC of the PIN.

[0085] In some embodiments of the method 400, the NF consumer is a PCF.

[0086] In some embodiments of the method 400, the NF consumer is an SMF.

[0087] FIG. 5 illustrates a method 500 of a PCF of a CN, according to embodiments discussed herein. The method 500 includes receiving 502, from a UDM entity, anindication of a PIN that uses local routing through the CN. The method 500 further includes installing 504, in a UE of the PIN that is in communication with the CN, a URSP rule that causes the UE to use a unique PDU session for the PIN.

[0088] In some embodiments of the method 500, the URSP rule is an only URSP rule of a set of all URSP rules of the PCF that is associated with an RSD that corresponds to the PIN.

[0089] In some embodiments of the method 500, the UE is a PEGC of the PIN.

[0090] FIG. 6 illustrates a method 600 of an SMF of a CN, according to embodiments discussed herein. The method 600 includes receiving 602, from a UDM entity, an indication of a first PIN that uses local routing through the CN. The method 600 further includes receiving 604, from a UE of the first PIN, a PDU session modification requesting to use a PDU session for the first PIN for traffic from of a second PIN. The method 600 further includes rejecting 606 the PDU session modification request.

[0091] In some embodiments of the method 600, the UE is a PIN element with gateway PEGC of the first PIN.

[0092] FIG. 7 illustrates a method 700 of a PCF of a CN, according to embodiments discussed herein. The method 700 includes receiving 702, from an AF, a request for local routing through the CN for data traffic between a target set of UEs identified by the request, wherein the target set of UEs are associated with a PIN. The method 700 further includes establishing 704, in response to the request from the AF, a PCC rule that causes local routing through the CN for the data traffic between the target set of UEs.

[0093] In some embodiments of the method 700, the request is an NEF traffic influence request.

[0094] In some embodiments of the method 700, the target set of UEs are PEGCs of the PIN.

[0095] In some embodiments of the method 700, the target set of UEs is identified in the request using IP addresses of the target set of UEs.

[0096] In some embodiments of the method 700, the target set of UEs is identified in the request using GPSIs of the target set of UEs.

[0097] In some embodiments of the method 700, the target set of UEs is identified in the request using a PIN identifier for the PIN of the target set of UEs.

[0098] In some embodiments of the method 700, the target set of UEs is identified in the request using an external group identifier for the target set of UEs.

[0099] In some embodiments of the method 700, the target set of UEs is identified in the request using a combination of a DNN and an S-NSSAI that is assigned to the PIN of the target set of UEs.

[0100] In some embodiments of the method 700, the request includes a field that indicates for local routing through the CN for the data traffic between the target set of UEs.

[0101] FIG. 8 illustrates an example architecture of a wireless communication system 800, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 800 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0102] As shown by FIG. 8. the wireless communication system 800 includes UE 802 and UE 804 (although any number of UEs may be used). In this example, the UE 802 and the UE 804 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0103] The UE 802 and UE 804 may be configured to communicatively couple with a RAN 806. In embodiments, the RAN 806 may be NG-RAN, E-UTRAN, etc. The UE 802 and UE 804 utilize connections (or channels) (shown as connection 808 and connection 810, respectively) with the RAN 806, each of which comprises a physical communications interface. The RAN 806 can include one or more base stations (such as base station 812 and base station 814) that enable the connection 808 and connection 810.

[0104] In this example, the connection 808 and connection 810 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 806, such as, for example, an LTE and / or NR.

[0105] In some embodiments, the UE 802 and UE 804 may also directly exchange communication data via a sidelink interface 816. The UE 804 is shown to be configured to access an access point (shown as AP 818) via connection 820. By way of example, the connection 820 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 818 may comprise a Wi-Fi® router. Inthis example, the AP 818 may be connected to another network (for example, the Internet) without going through a CN 824.

[0106] In embodiments, the UE 802 and UE 804 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 812 and / or the base station 814 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0107] In some embodiments, all or parts of the base station 812 or base station 814 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 812 or base station 814 may be configured to communicate with one another via interface 822. In embodiments where the wireless communication system 800 is an LTE system (e.g., when the CN 824 is an EPC), the interface 822 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 800 is an NR system (e.g., when CN 824 is a 5GC), the interface 822 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 812 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g.. CN 824).

[0108] The RAN 806 is shown to be communicatively coupled to the CN 824. The CN 824 may comprise one or more network elements 826, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 802 and UE 804) who are connected to the CN 824 via the RAN 806. The components of the CN 824 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0109] In embodiments, the CN 824 may be an EPC, and the RAN 806 may be connected with the CN 824 via an SI interface 828. In embodiments, the SI interface 828 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 812 or base station 814 and a serving gateway (S-GW), and the SI -MME interface, which is a signaling interface between the base station 812 or base station 814 and mobility management entities (MMEs).

[0110] In embodiments, the CN 824 may be a 5GC, and the RAN 806 may be connected with the CN 824 via an NG interface 828. In embodiments, the NG interface 828 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 812 or base station 814 and a user plane function (UPF). and the SI control plane (NG-C) interface, which is a signaling interface between the base station 812 or base station 814 and access and mobility management functions (AMFs).

[0111] Generally, an application server 830 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 824 (e.g., packet switched data services). The application server 830 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 802 and UE 804 via the CN 824. The application server 830 may communicate with the CN 824 through an IP communications interface 832.

[0112] FIG. 9 illustrates a system 900 for performing signaling 930 between a wireless device 902 and a network device 916, according to embodiments disclosed herein. The system 900 may be a portion of a wireless communications system as herein described. The wireless device 902 may be, for example, a UE of a wireless communication system. The network device 916 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0113] The wireless device 902 may include one or more processor(s) 904. The processor(s) 904 may execute instructions such that various operations of the wireless device 902 are performed, as described herein. The processor(s) 904 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0114] The wireless device 902 may include a memory 906. The memory 906 may be a non-transitory computer-readable storage medium that stores instructions 908 (which may include, for example, the instructions being executed by the processor(s) 904). The instructions 908 may also be referred to as program code or a computer program. The memory' 906 may also store data used by, and results computed by, the processor(s) 904.

[0115] The wireless device 902 may include one or more transceiver(s) 910 that may include radio frequency (RF) transmitter circuitry' and / or receiver circuitry that use the antenna(s) 912 of the wireless device 902 to facilitate signaling (e.g., the signaling 930) to and / or from the wireless device 902 with other devices (e.g., the network device 916) according to corresponding RATs.

[0116] The wireless device 902 may include one or more antenna(s) 912 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 912, the wireless device 902 may leverage the spatial diversity of such multiple antenna(s) 912 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 902 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 902 that multiplexes the data streams across the antenna(s) 912 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU- MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0117] In certain embodiments having multiple antennas, the wireless device 902 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 912 are relatively adjusted such that the (joint) transmission of the antenna(s) 912 can be directed (this is sometimes referred to as beam steering).

[0118] The wireless device 902 may include one or more interface(s) 914. The interface(s) 914 may be used to provide input to or output from the wireless device 902. For example, a wireless device 902 that is a UE may include interface(s) 914 such asmicrophones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 910 / antenna(s) 912 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0119] The network device 916 may include one or more processor(s) 918. The processor(s) 918 may execute instructions such that various operations of the network device 916 are performed, as described herein. The processor(s) 918 may include one or more baseband processors implemented using, for example, a CPU. a DSP. an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0120] The network device 916 may include a memory 920. The memory 920 may be a non-transitory computer-readable storage medium that stores instructions 922 (which may include, for example, the instructions being executed by the processor(s) 918). The instructions 922 may also be referred to as program code or a computer program. The memory 920 may also store data used by, and results computed by, the processor(s) 918.

[0121] The network device 916 may include one or more transceiver(s) 924 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna(s) 926 of the network device 916 to facilitate signaling (e.g.. the signaling 930) to and / or from the network device 916 with other devices (e.g., the wireless device 902) according to corresponding RATs.

[0122] The network device 916 may include one or more antenna(s) 926 (e.g., one. two, four, or more). In embodiments having multiple antenna(s) 926, the network device 916 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0123] The network device 916 may include one or more interface(s) 928. The interface(s) 928 may be used to provide input to or output from the network device 916. For example, a network device 916 that is a base station may include interface(s) 928 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 924 / antenna(s) 926 already described) that enables the base station to communicate with other equipment in a CN, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations,administration, and maintenance of the base station or other equipment operably connected thereto.

[0124] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 300, the method 400, the method 500, the method 600, and / or the method 700. This apparatus may be, for example, an apparatus of a CN (such as a 5G CN 110 or a CN 824, as described herein).

[0125] Embodiments contemplated herein include one or more non -transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the method 300, the method 400, the method 500, the method 600, and / or the method 700. This non-transitory computer-readable media may be. for example, a memory of a CN (such as a 5G CN 110 or a CN 824, as described herein).

[0126] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 300. the method 400. the method 500. the method 600. and / or the method 700. This apparatus may be, for example, an apparatus of a CN (such as a 5G CN 110 or a CN 824, as described herein).

[0127] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 300, the method 400, the method 500, the method 600, and / or the method 700. This apparatus may be, for example, an apparatus of a CN (such as a 5G CN 110 or a CN 824, as described herein).

[0128] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 300, the method 400, the method 500, the method 600, and / or the method 700.

[0129] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the method 300, the method 400, the method 500, the method 600, and / or the method 700. The processor may be a processor of a CN (such as a processor of a 5G CN 110 or a CN 824, as described herein). These instructions may be. for example, locatedin the processor and / or on a memory of the CN (such as a memory of a 5G CN 110 or a CN 824, as described herein).

[0130] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0131] Any of the above-described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0132] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0133] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0134] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0135] Although the foregoing has been described in some detail for purposes of clarity7, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

CLAIMS1. A method of a unified data management (UDM) entity of a core network (CN), comprising: receiving, from a network function (NF) consumer of the CN, a request for group subscription data for a group of user equipments (UEs); and providing, to the NF consumer, the group subscription data for the group of UEs in response to the request; wherein the group subscription data for the group of UEs comprises a personal internet of things network (PIN) identifier for the group of UEs and an indication of whether a PIN identified by the PIN identifier is allowed to use local routing through the CN.

2. The method of claim 1, each UE in the group of UEs is a PIN element with gateway capability (PEGC) of the PIN.

3. The method of claim 1, wherein the NF consumer is a policy control function (PCF).

4. The method of claim 1, wherein the NF consumer is a session management function (SMF).

5. A method of a unified data management (UDM) entity of a core network (CN), comprising: receiving, from a network function (NF) consumer of the CN, a request for personal internet of things network (PIN) subscription data for a user equipment (UE); and providing, to the NF consumer, the PIN subscription data for the UE in response to the request; wherein the PIN subscription data for the UE comprises a PIN identifier for the UE and an indication of whether a PIN identified by the PIN identifier is allowed to use local routing through the CN.

6. The method of claim 5, wherein the UE is a PIN element with gateway capability (PEGC) of the PIN.

7. The method of claim 5, wherein the NF consumer is a policy control function (PCF).

8. The method of claim 5, wherein the NF consumer is a session management function (SMF).

9. A method of a policy control function (PCF) of a core network (CN), comprising: receiving, from a unified data management (UDM) entity, an indication of a personal internet of things network (PIN) that uses local routing through the CN; and installing, in a user equipment (UE) of the PIN that is in communication with the CN, a UE route selection policy (URSP) rule that causes the UE to use a unique protocol data unit (PDU) session for the PIN.

10. The method of claim 9. wherein the URSP rule is an only URSP rule of a set of all URSP rules of the PCF that is associated with a route selection descriptor (RSD) that corresponds to the PIN.

11. The method of claim 9. wherein the UE is a PIN element with gateway capability (PEGC) of the PIN.

12. A method of a session management function (SMF) of a core network (CN), comprising: receiving, from a unified data management (UDM) entity, an indication of a first personal internet of things network (PIN) that uses local routing through the CN; receiving, from a user equipment (UE) of the first PIN, a protocol data unit (PDU) session modification requesting to use a PDU session for the first PIN for traffic from of a second PIN; and rejecting the PDU session modification request.

13. The method of claim 12, wherein the UE is a PIN element with gateway capability (PEGC) of the first PIN.

14. A method of a policy control function (PCF) of a core network (CN), comprising: receiving, from an application function (AF), a request for local routing through the CN for data traffic between a target set of user equipments (UEs) identified by the request, wherein the target set of UEs are associated with a personal internet of things network (PIN); andestablishing, in response to the request from the AF, a policy and charging control (PCC) rule that causes local routing through the CN for the data traffic between the target set of UEs.

15. The method of claim 14, wherein the request is a network exposure function (NEF) traffic influence request.

16. The method of claim 14, wherein the target set of UEs are PIN elements with gateway capability (PEGCs) of the PIN.

17. The method of claim 14, wherein the target set of UEs is identified in the request using internet protocol (IP) addresses of the target set of UEs.

18. The method of claim 14, wherein the target set of UEs is identified in the request using generic public subscription identifiers (GPSIs) of the target set of UEs.

19. The method of claim 14, wherein the target set of UEs is identified in the request using a PIN identifier for the PIN of the target set of UEs.

20. The method of claim 14, wherein the target set of UEs is identified in the request using an external group identifier for the target set of UEs.

21. The method of claim 14, wherein the target set of UEs is identified in the request using a combination of a data network name (DNN) and a single-network slice selection assistance information (S-NSSAI) that is assigned to the PIN of the target set of UEs.

22. The method of claim 14, wherein the request includes a field that indicates for local routing through the CN for the data traffic between the target set of UEs.

23. An apparatus comprising means to perform the method of any of claim 1 to claim 22.

24. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 22.

25. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 22.

Images