Quality of service control for devices in wireless communication systems

Abstract

Various aspects of the present disclosure relate to a Session Management Function (SMF) for wireless communication. The SMF may be configured to, capable of, or operable to receive a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a Policy Control Function (PCF) the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a User Plane Function (UPF), the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

Description

QUALITY OF SERVICE CONTROL FOR DEVICES IN WIRELESS COMMUNICATION SYSTEMSTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including managing (e.g., controlling, providing) Quality of Service (QoS) for devices in a wireless communication system.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C orAB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] It should be understood that a UE as described herein may be a 5G Residential Gateway (5G-RG). A 5G-RG may be configured or operable as a UE in supporting (e.g., establishing, managing, providing) a tethered connection to other devices when connectivity to a core network (e.g., a 5G core (5GC) network) is via fixed broadband access or cable access.

[0005] A Session Management Function (SMF) for wireless communication is described. The SMF may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the SMF may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the SMF to: receive a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a Policy Control Function (PCF) the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a User Plane Function (UPF), the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

[0006] A method performed or performable by the SMF is described herein. The method may comprise: receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; sending a policy association request to a PCF the policy association request including the Device Identifier; receiving a policy association response from the PCF, the policyassociation response comprising a policy control request trigger; in response to receiving the policy association response, sending a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receiving a notification of the source user plane address from the UPF; determining whether the source user plane address needs to be reported to the PCF.

[0007] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a PCF the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

[0008] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: establish a tethering connection with a first device; receive a request from the first device for a first data connection; send a first request to an Access & Mobility Management Function (AMF) the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0009] A method performed or performable by a UE is described. The method comprising: establishing a tethering connection with a first device; receiving a request from the first device for a first data connection; and sending a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0010] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: establish a tethering connection with a first device; receive a request from the first device for a first data connection; send a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0012] Figures 2 through 6 illustrate examples of process flows in accordance with aspects of the present disclosure.

[0013] Figure 7 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0014] Figure 8 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0015] Figure 9 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0016] Figure 10 illustrates a flowchart of a method performed by an NE in accordance with aspects of the present disclosure.

[0017] Figure 11 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0018] A wireless communication network, including one or more network entities (e.g., base stations, network functions, and the like) may identify (e.g., discover) a wireless communication device based at least in part on an identity module of the wirelesscommunication device. The identity module or components thereof may be implemented in hardware (e.g., a processor), software executed by a processor, firmware, or any combination thereof. For example, the identity module may be subscriber identity module (SIM), an embedded SIM (eSIM), etc. The wireless communication device includes the identity module. The wireless communication network may determine (e.g., map to, associate with) a user subscription for the identity module and provide one or more services based at least in part on the user subscription. In some implementations, the wireless communication network may provide the one or more services according to a dedicated QoS based on the user subscription, where the user subscription linked to the wireless communication device is identified from the identity module. Wireless communication devices, such as tethered devices with or without an identity module might be unable to utilize dedicated QoS.

[0019] Various aspects of the present disclosure enable (e.g., allow) a network entity, such as a PCF to identify (e.g., discover) a first device and allocate one or more Policy and Charging Control (PCC) rules for data traffic associated with the first device (e.g., transmitted from and / or received at the first device). Additionally, aspects of the present disclosure enable the network entity to apply one or more QoS rules to the data traffic. The allocation of PCC rules and / or applicability of QoS rules for data traffic may be beneficial to the first device, for example, when the first device is a tethered device.

[0020] A 3 GPP device is a device that conforms (e.g., configured) to one or more of theThird Generation Partnership Project (3 GPP) standards. A tethered device might not be a 3 GPP device and may therefore be referred to as a non-3GPP device. The tethered device may be connected to the wireless communication network via a wireless communication device, such as a UE or a 5G-RG. In this case, the wireless communication network can identify the device (e.g., the UE, the 5G-RG), but may not have access to an identity (e.g., identifier) of the first device. The wireless communication network is able to identify devices connected thereto, such as UE’s or 5G-RGs. However, the UE or 5G-RG may not disclose the identity of a tethered device to the wireless communication network. As used herein, including in the claims, it should be understood that a UE may be a 5G-RG. A 5G- RG may operate (e.g., function) as a UE providing a tethered connection to other devices,for example, when a connectivity to a core network (e.g., a 5G core network, or core networks supporting technologies beyond 5G) is via a fixed broadband access or cable access.

[0021] Aspects of the present disclosure are described in the context of a wireless communications system.

[0022] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0023] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0024] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0025] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0026] A UE 104 may be able to support wireless communication directly with otherUEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0027] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, suchas an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0028] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an AMF) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a UPF). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0029] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0030] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a singleframe structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0031] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0032] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0033] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively.Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0034] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0035] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0036] Wireless communication devices such as a UE include an identity module such as a Universal Subscriber Identity Module (USIM) or an electronic Subscriber Identity Module (eSIM). When a wireless communication device connects to a wireless communication network, the wireless communication network identifies a subscription associated with the USIM or eSIM in the wireless communication device. The wireless communication network is configured to offer services to the wireless communication device based on the provisioned data in the identified subscription. This creates a one-to- one mapping between subscriptions and provided services. If a user of the wireless communication device wants to experience different services, e.g. reliable access to corporate applications (for business use) and inexpensive access to social media (for personal use), the user is typically required to buy different subscriptions, each one tailored to providing a different experience and satisfying the needs of a certain use case.

[0037] A tethered device may connect to the wireless communication network via the wireless communication device. The tethered device may connect to the wireless communication device via a tethering connection. The tethered device may be a non-3GPP device. The tethering connection may be made using Wi-Fi, for example. The wireless communication device may be a UE. In the case of fixed wireless, the wireless communication device may be a 5G-RG.

[0038] The first device may be a tethered device and may have a Device Identifier, which identifies the tethered device. As part of the Release 19 work in 3 GPP SA2, it was agreed that the UE (or 5G-RG) is to include the Device Identifier when the UE establishes or modifies a PDU session. The Device Identifier corresponds to the tethered device. The tethered device may be a non-3GPP device connected behind the UE / 5G-RG. The tethered device may be a non-3GPP device tethered to the UE / 5G-RG. The non-3GPP device may be a device not supporting NAS (e.g. a laptop, a TV etc). The Device Identifier is used by the 5GC to offer enhanced QoS services for the non-3GPP device connected via the UE. The enhanced QoS services that are offered are determined based on QoS information associated with a Device Identifier stored in the Unified Data Repository (UDR). The UDR stores the Device Identifier and QoS information. The UDR may store a mapping of the Device Identifier to the QoS information.

[0039] The PCF allocates Policy and Charging Control (PCC) rules dependent upon the Device Identifier. For the PCF to allocate a PCC rule corresponding to the non-3GPP device, the PCF needs to be made aware of the full address of the non-3GPP device. The solution presented here in addresses each of the following three cases.• Case 1 : When the PDU session uses an Ethernet address, the PCF needs to be made aware of the MAC address of the non-3GPP device linked to the provided Device Identifier.• Case 2: When the PDU session uses an IPv4 address the PCF needs to be aware of the full IPv4 address used by the UE / 5G-RG to forward traffic of the non-3GPP device and its association to the provided Device Identifier.• Case 3: When the PDU session uses an IPv6 address the PCF needs to be aware of the full IPv6 address (prefix + interface) used by the UE / 5G-RG to forward traffic of the non-3GPP device and its association to the provided Device Identifier.

[0040] As part of the SAI study in TR 22.904 vl 8.0.1 (April 2024) and the corresponding normative requirements in 3GPP TS 22.101 vl9.0.0 (June 2024). The following has been defined as part of a User Profile.• The 3GPP system shall be able to store and update a User Profile for a user.• The User Profile shall include a User Identifier.• The User Profile may include one or more pieces of the following information: o Additional User Identifiers of the user's User Identities and potentially linked 3 GPP subscriptions, o used UEs (identified by their subscription and Device Identifiers), o capabilities the used UEs support for authentication, o information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices.o User Identity specific service settings and parameters. [These shall include network parameters (e.g. QoS parameters), IP Multimedia Subsystem (IMS) service (e.g. MultiMedia Telephony (MMTEL) supplementary services) and operator deployed service chain settings.] o User Identity specific network resources (e.g., network slice).• Subject to operator policy the 3GPP system shall be able to update User Profile related to a User Identifier, according to the information shared by a trusted third party.

[0041] This new model of operation may specify (a) how a new "profile" (called User Profile) can be created and linked with a mobile subscription and (b) how a mobile data connection (i.e. PDU Session) can be associated with a User Profile, and be configured to operate based on the service settings in this User Profile as shown in Figure 2.

[0042] Figure 2 illustrates an example of a process flow 200 in accordance with aspects of the present disclosure. The process flow 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 200 may include a device 210 (e.g., a UE or a non-5G capable UE), a UDR 215, a Unified Data Management (UDM) 220, a Network Exposure Function (NEF) 225, an Internet 240, a User Identity Management Function (UIMF) 252, and a Third-Party Application Server (AS) 260, which may be one or more examples of devices described herein with reference to Figure 1. The device 210 may be connected via a tethered connection to a UE (not shown). The device 210 may include a Mobile Network Operator (MNO) Application 212.

[0043] In the following description of the process flow 200, one or more operations or signaling performed by one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third-Party AS 260 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signaling performed by one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third-Party AS 260 may be performed or signalled (e.g., transmitted, received) in different orders or at different times.

[0044] In the example of Figure 2, at 271a through 27 Ih, one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third-Party AS 260 may perform one or more operations or signaling to generate (e.g., create) a user profile in accordance with an app-layer procedure. The user profile may be associated with (e.g., linked) with a third-party account.

[0045] At 271a, one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third-Party AS 260 may perform one or more operations for security establishment. For example, the security establishment may be between the device 210 and the UIMF 252. At 271b, one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third- Party AS 260 may perform one or more operations for authentication. For example, one or more of the device 210, the UDR 215, the UDM 220, the NEF 225, the Internet 240, the UIMF 252, and the Third-Party AS 260 may perform one or more operations for authentication between the device 210 and the UIMF 252. At 271c, the device 210 may transmit, and the UIMF 252 may receive, a request message to create user profile.

[0046] At 271 d, the UIMF 252 and the Third-Party AS 260 may perform one or more operations for OAuth 2.0. For example, the UIMF 252 and the Third-Party AS 260 may perform one or more operations associated with OAuth 2.0 to grant an authorization code grant according to RFC 6749. At 271e, the UIMF 252 and the Third-Party AS 260 may receive a token (e.g., an access token), which may be used to retrieve user information associated with the device 210. The user information may include, for example: a username (user23@third-party.com), a subscription type, one or more preferences, etc.

[0047] At 27 If, the UIMF 252 may generate (e.g., create, establish) a user profile including one or more of service settings, user identifier(s), user credentials, authentication types, allowed devices, etc. For example, the UIMF 252 may create the user profile based at least in part on the retrieved user information. At 271g, the UIMF 252 may transmit, and the device 210 may receive, for example over the Internet 240 user profile data. The user profile may include one or more of a Generic Public Subscription Identifier (GPSI), one or more user identifier(s), user credentials, and associated App-ID of the MNO application212. At 27 Ih, the UIMF 252 may transmit the user profile data to all other devices connected and associated with the GPSI and allowed to use the user profile.

[0048] At 272, the UIMF 252 may transmit, and the NEF 225 may receive, a network message, for example, a Nnef UserProfile Create Request message. The message may include a GPSI and a user profile. At 273 a, the NEF 225 may transmit, and the UDM 220 may receive, a network message, such as a Nudm_SDM_Get message that includes the GPSI and an identifier translation. At 273b, the UDM 220 may transmit, and the NEF 225 may receive, a network message (e.g., a response message) that acknowledges the received request for the user profile (e.g., the Nnef UserProfile Create Request message). For example, the UDM 200 may transmit, and the NEF 225 may receive, a 200 OK message that includes a Subscription Permanent Identifier (SUPI). At 274a, the NEF 225 may transmit, and the UDR 215 may receive, a network message, for example, a Nudr_DM_Update Request message. The Nudr_DM_Update Req message may include (e.g., indicate) the SUPI, subscription data, and / or user profile. At 274b, the UDR 215 may transmit, and NEF 225 may receive, a network message, for example, a Nudr_DM_Update Response message. At 275, the NEF 225 may transmit, and the UIMF 252 may receive, a network message, for example, a Nnef UserProfile Create Response message.

[0049] With reference to Figure 1, as described herein, a UE 104 may detect (e.g., discover) a non-3GPP device and include a user identifier associated with (e.g., linked to) the non-3GPP device when a PDU session is established. A network entity, such as an AMF of CN 106 may identify a user profile based at least in part on a user profile identifier (ID) associated with the user profile (e.g., user) and provide (e.g., transmit, forward) the identified user profile (or indication of the identified user profile) to another network entity, such a SMF and / or a PCF of the CN 106. The SMF and / or the PCF may retrieve user profile information associated with the identified user profile and / or the user profile ID, and apply one or more corresponding policies.

[0050] Various solutions are described herein. According to one solution, a device (e.g., a UE, a 5G-RG) may include, during a PDU session establishment, a device identifier of a connected non-3GPP device and a MAC address irrespective of a PDU session type. The device identifier may be sent by the UE in a message as part of the PDU sessionestablishment. The PDU session type may include at least one of an Ethernet, IPv4 or Ethernet, IPv6. A network entity, such as an SMF may output (e.g., transmit, forward) information (e.g., the device identifier, the MAC address) to another network entity, such as a PCF, which may store a mapping of the device identifier to the MAC address.

[0051] Alternatively, or additionally, the SMF or another network entity, such as a UPF may be configured (e.g., by the PCF) to report a user plane address of the non-3GPP device associated with (e.g., linked to) the device identifier. The user plane address (e.g., a MAC address or IP address depending on the PDU session type) may be used by the device for the non-3GPP device. Alternatively, the SMF or the UPF may be configured to report both the MAC address of uplink traffic together with one or more of an IPv4 address or an IPv6 address, when available. For IPv4 and IPv6 addresses, the SMF or the UPF may interface with the device (e.g., the UE, the 5G-RG) to provide the MAC address corresponding to the IP address of uplink traffic transmitted from the device.

[0052] Alternatively, or additionally, the SMF may notify the PCF of the user plane address associated with (e.g., linked to) the device identifier. The SMF may notify the PCF about the device identifier, MAC address, and / or IP address information. The SMF may notify the PCF about device identifier and user plane address associated with the PDU session type (e.g., if a PDU session type is Ethernet, the SMF may provide the MAC address, if the PDU session type is an IP, the SMF may provide IPv4 and / or IPv6 addresses). The PCF may use the information to associate (e.g., link, map) a device identifier to a user plane address based on the received MAC address and provide corresponding PCC rules to the device.

[0053] Figure 3 illustrates an example of a process flow 300 in accordance with aspects of the present disclosure. The process flow 300 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 300 may include a device 310 (e.g., a UE, a 5G-RG), a non-3GPP device 314, an AMF 330, an SMF 333, a PCF 336, a UPF 339, and an Access Network 342, which may be one or more examples of devices described herein with reference to Figure 1. The process flow 300 may be referred to as a procedure, including one or more operations performed by one or more of the non-3GPP device 314, the UE 310, the AMF 330, the SMF 333, the PCF 336,the UPF 339, and the Access Network 342. In the example of Figure 3, the process flow 300 may include a PDU session with a PDU session type of Ethernet. Additionally, the process flow 300 may include a device identifier associated with (e.g., linked, mapped to) a MAC address based at least in part on that the PDU session type is Ethernet.

[0054] In the following description of the process flow 300, the operations or signalling performed between one or more of the non-3GPP device 314, the UE 310, the AMF 330, the SMF 333, the PCF 336, the UPF 339, and the Access Network 342 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the non-3GPP device 314, the UE 310, the AMF 330, the SMF 333, the PCF 336, the UPF 339, and the Access Network 342 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 300. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0055] At 370a, the device 310 (e.g., the UE, the 5G-RG) may perform a registration procedure. For example, the device 310 (e.g., the UE, the 5G-RG) may perform a 5G registration with a network via the AMF 330.

[0056] At 371a, the device 310 (e.g., the UE, the 5G-RG) may perform an association with the non-3GPP device 314. For example, the device 310 (e.g., the UE, the 5G-RG) may perform an association (e.g., tethering) with the non-3GPP device 314. At 371b, the device 310 (e.g., the UE, the 5G-RG) may determine (or identify) a device identifier and a MAC address of the non-3GPP device 314.

[0057] At 372, the device 310 (e.g., the UE, the 5G-RG) may transmit, and the AMF 330 may receive, a NAS message, for example, an uplink NAS transport message. The NAS message may indicate a PDU session establishment request and include the device identifier and the MAC address of the non-3GPP device 314. In some cases, the device 310 (e.g., the UE, the 5G-RG) may transmit the PDU session establishment request based at least in part on (or in response to) the non-3GPP device 314 being associated with the device 310 (e.g., the UE, the 5G-RG). In some cases, the device 310 (e.g., the UE, the 5G-RG) may transmit the PDU session establishment request may be based at least in part on (or in response to) the non-3GPP device 314 establishing a tethering connection to the device 310 (e.g., the UE, the 5G-RG). In some examples, the PDU session establishment request may include one or more of: a PDU Session ID, a Single-Network Slice Selection Assistance Information (S-NSSAI), a Data Network Name (DNN), a Request Type, a Payload Container Type = N1 Session Management (SM) Information, a Payload: PDU Session Establishment Request, a device identifier, and a user plane address (e.g., such as a MAC address). The device identifier and the user plane address may be included within the PDU session establishment request. The device identifier and the user plane address may be exchanged outside the PDU session establishment request within N1 SM information.

[0058] At 373, in accordance with one or more PDU session establishment procedures, the AMF 330 may identify an SME For example, the AMF 330 may one or more of identify, determine, or select the SMF 333 based at least in part on the received uplink NAS transport message (e.g., PDU session establishment request, etc.).

[0059] At 374, in accordance with one or more PDU session establishment procedures, the AMF 330 may transmit, and the SMF 333 may receive, a create SM context request message. The create SM context request message may include one or more of: a SUPI, a PDU Session ID, an S-NSSAI, a DNN, an AMF-ID, a Globally Unique AMF ID (GUAM!), a Request Type, an Access Type, a Radio Access Technology (RAT) Type, or a PDU Session Establishment Request.

[0060] At 375, in accordance with one or more PDU session establishment procedures, the SMF 333 may select a PCF, such as the PCF 336. At 376, the SMF 333 may transmit (e.g., forward), and the PCF 336 may receive, an SM Policy Control Create Request message (e.g., a policy association request). The SM Policy Control Create Request message may include one or more of the device identifier or the MAC address. For example, the SMF 333 may transmit (e.g., forward), and the PCF 336 may receive, one or more of the device identifier or the MAC address within a policy association request. Additionally, the SM Policy Control Create Request message may include one or more of a SUPI, a PDU Session ID, a DNN, an S-NSSAI, an Access Type, a location, a device identifier, or a user plane address (e.g., the MAC address).

[0061] At 377, the PCF 336 may receive (e.g., obtain), from the UDR (not shown) the device identifier (e.g., a device profile identifier). In some examples, the PCF 336 may identify or determine one or more QoS requirements based at least in part on the received device identifier. Additionally, or alternatively, the PCF 336 may store the device identifier and associated MAC address (e.g., an association (or mapping) of the device identifier to MAC address).

[0062] At 378, the PCF 336 may trigger (e.g., according to a PCC rule) the SMF 333 to report a MAC address associated with uplink traffic from the UE 310. In some examples, the PCF 336 may trigger the SMF 333 to report each MAC addresses associated with (e.g., transmitted) uplink traffic from a corresponding device, including the device 310 or report MAC addresses for specific device identifiers. For example, the trigger to the SMF 333 to report MAC address may be based on a specific policy control request trigger. In other examples, the PCF 336 may include one or more PCC rules for the device identifier and the MAC address reported at 377.

[0063] At 379, in accordance with one or more PDU session establishment procedures, the PCF 336 may transmit (e.g., output), and the SMF 333 may receive (e.g., obtain), an SM Policy Control Create Response message, which may include one or more PCC rules. At 380, in accordance with one or more PDU session establishment procedures, the SMF 333 may select the UPF 339, for example, based at least in part on the SM Policy Control Create Response message. In some examples, the SM Policy Control Create Response message may include an SM Policy Decision.

[0064] At 381, the SMF 333 may transmit (e.g., output), and the UPF 339 may receive (e.g., obtain), one or more N4 rules, which may include an indication to report a MAC address associated with uplink traffic from the device 310. In some examples, the SMF 333 may request for the UPF 339 to report a specific MAC address (e.g., linked to a specific device identifier) or report MAC addresses associated with uplink traffic of a device, including the device 310, for example. At 382, the UPF 339 may transmit (e.g., output), and the SMF 333 may receive (e.g., obtain), an acknowledgment of the one or more N4 rules.

[0065] At 383, 384, 385, the PDU session establishment continues and UE / 5G-RG 310 receives the PDU session establishment accept message. At 383 the SMF 333 may transmit (e.g., output), and the AMF 330 may receive (e.g., obtain), an N1N2 message transfer request. Message 383 may comprise at least one of UE Context, PDU Session ID, N2 Info Container, 5QI, Allocation and Retention Priority (ARP), PPI, and PDU Session Est. Accept. At 383 the AMF 330 may transmit (e.g., output), and the Access Network 342 may receive (e.g., obtain), a message. At 385 the Access Network 342 may transmit (e.g., output), and device 310 may receive (e.g., obtain), an RRC PDU Session Establishment Accept.

[0066] At this point the non-3GPP device 314 starts sending uplink traffic and the UE / 5G-RG 310 forwards uplink traffic to the UPF 339. The uplink traffic comprises the MAC address of the non-3gpp device 314. The UE / 5G-RG 310 includes in the ethernet frames the MAC address of the non-3GPP device 314 as source address.

[0067] At 386, the UPF 339 identifies the MAC address from UL traffic.

[0068] At 387 the UPF 339 may transmit (e.g., output), and the SMF333 may receive(e.g., obtain), a report of the MAC address via the N4 protocol.

[0069] At 388 the SMF 333 may transmit (e.g., output), and the PCF 336 may receive(e.g., obtain), the MAC address information. The SMF 333 may include Device Identifier associated to the MAC address.

[0070] At 389, the PCF 336 links MAC address to Device Identifier and derives PCC rules.

[0071] At 380, PCC rules are sent to the UE 310 and the core network as per existing procedures. In this way appropriate PCC rules are used within the network for traffic from the non-3GPP device 314.

[0072] Figure 4 illustrates an example of a process flow 400 in accordance with aspects of the present disclosure. The process flow 400 may implement or be implemented by aspects of the wireless communication system 400. For example, the process flow 400 may include a non-3GPP UE 414, a UE 410, an AMF 430, an SMF 433, a PCF 436, a UPF 439,and an Access Network 442, which may be one or more examples of devices described herein with reference to Figure 1.

[0073] The process flow 400 may be referred to as a procedure, including one or more operations performed by one or more of the non-3GPP UE 414, the UE 410, the AMF 430, the SMF 433, the PCF 436, the UPF 439, and the Access Network 442. In the example of Figure 4, the process flow 400 may include, when the PDU session is IPv4 or IPv6 type for a first alternative where SMF derives MAC address. Here, the Device Identifier is linked to the IP address for PDU session type IPv4 / IPv6. The process flow 400 is performed by a non-3GPP UE 414, a UE 410, an AMF 430, an SMF 433, a PCF 436, a UPF 439, and an Access Network 442. The non-3GPP UE 414 may be a tethered device. The UE 410 may comprise a 5G-RG.

[0074] In the following description of the process flow 400, the operations or signalling performed between one or more of the non-3GPP UE 414, the UE 410, the AMF 430, the SMF 433, the PCF 436, the UPF 439, and the Access Network 442may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the non-3GPP UE 414, the UE 410, the AMF 430, the SMF 433, the PCF 436, the UPF 439, and the Access Network 442 may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 400. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0075] The process flow 400 begins at 470, when the UE / 5G-RG 410 registers with the network.

[0076] At 471, a non-3GPP device 414 is associated with the UE / 5G-RG 410 and the UE / 5G-RG 410 determines the Device Identifier and the MAC address of the non-3GPP device 414.

[0077] At 472, the UE / 5G-RG 410 sends a PDU session establishment request, e.g., when a non-3GPP device 414 is associated or tethered with the UE / 5G-RG 410 andincludes the Device Identifier and MAC address of a non-3GPP device 414 with the PDU session establishment request. The PDU session establishment request may comprise a UL NAS Transport. The PDU session establishment request may comprise: PDU Session ID, S-NSSAI, DNN, Request Type, Payload Container Type = N1 SM Info, Payload: PDU Session Establishment Request, Device Identifier, and the user plane address such as a MAC address. The Device Identifier and user plane address may be included within the PDU Session Establishment request. The Device Identifier and user plane address may be exchanged outside the PDU session establishment request within N1 SM info.

[0078] At 473, 474, 475, a per PDU session establishment procedures the PDU session establishment request is received at the SMF 433 and the SMF 433 selects a PCF 436. The create session management context request at 474 may comprise at least one of: SUPI, PDU Session ID, S-NSSAI, DNN, AMF-ID, GUAM!, Request Type, Access Type, RAT Type, and PDU Session Establishment Req.(...)

[0079] At 476, the SMF 433 forwards the Device Identifier and MAC address to the PCF 436 within the Policy Association request. The message at 476 may comprise a SM Policy Control Create Request. The message at 476 may comprise at least one of SUPI, PDU Session ID, DNN, S-NSSAI, Access Type, Location, Device Identifier and the user plane address such as a MAC address. The SMF 433 also allocates an interface identifier to the UE 410 for the UE 410 to build its link-local address.

[0080] At 477, the PCF 436 obtains the Device Identifier from the UDR (not shown) and identifies its QoS requirements. The PCF 436 also stores the association of Device Identifier to MAC address.

[0081] At 478, the PCF 436 may trigger (within a PCC rule) the SMF 433 to report full IP address of uplink traffic from UE / 5G-RG 410 associated to the Device Identifier. For example, the trigger to the SMF 433 to report IP address is based on a specific Policy Control Request Trigger.

[0082] At 479,480, as per PDU session establishment procedures the PCC rule is received at SMF 433 and SMF 433 selects a UPF 439. At this point the SMF 433 mayassign an IPv4 address or an IPv6 prefix plus an interface identifier for link-local address of the UE / 5G-RG 410.

[0083] At 481, 482, the N4 rule sent to the UPF 439 may include an indication to report IP address of uplink traffic from UE.

[0084] At 483, 484, 485, the PDU session establishment continues and UE / 5G-RG 410 receives the PDU session establishment accept message. At 483 an N1N2 message transfer request is sent from the SMF 433 to the AMF 430. Message 483 may comprise at least one of UE Context, PDU Session ID, N2 Info Container, 5QI, Allocation and Retention Priority (ARP), PPI, and PDU Session Est. Accept.

[0085] At 486, the UE / 5G-RG 410 may request IPv4 or IPv6 address by sending a Router Solicitation message. The request is received to the SMF 433 via the UPF 439.

[0086] At 487, as an alternative to step 480 the SMF 433 may assign an IPv4 address or an IPv6 prefix plus an interface identifier for link-local address of the UE / 5G-RG 410 and provides the IP address to the UE / 5G-RG 410 via a Router Advertisement message. Each Router Advertisement message 487a and 487b may comprise either an IPv4 address or IPv6 prefix + interface identifier for link-local address.

[0087] At 488, the non-3GPP device 414 starts sending uplink traffic and the UE / 5G- RG 410 derives IPv4 or IPv6 address for the non-3GPP device 414. For IPv4 the UE / 5G- RG 410 assigns a port number for each non-3GPP device 414. For IPv6 the UE / 5G-RG 410 assigns an interface identifier for each non-3GPP device 414. The UE / 5G-RG 410 forwards uplink traffic based on the allocated IP4 / port number or IPv6 prefix + interface identifier.

[0088] At 489, the UPF 439 receives uplink traffic and may notify the IP address via N4 to the SMF 433. The uplink traffic may comprise either IPv4 address / port number or IPv6 prefix + interface identifier allocated by UE for non-3GPP device.

[0089] At 490, the SMF 433 queries the UE to provide the MAC address. This may be carried out using Address Resolution Protocol (ARP) or Neighbour Discovery Protocol (NDP) messages. The messages may be sent via IP to the UE / 5G-RG 410 or via N4 toUPF 439 and IP from UPF 439 to the UE / 5G-RG 410. The SMF 433 may query the UE to provide the MAC address corresponding to an IP address received at 489 or may query the UE to provide the IP address corresponding to the MAC address received at 475. The SMF 433 may also query the UE to provide list of all assigned IP addresses for each non-3GPP device connected to the UE. It should be noted that any Address Resolution Protocol (ARP) or NDP messages and / or queries between the UE and SMF may be carried out either via IP signalling or via NAS signalling.

[0090] At 491, the SMF 433 forwards the IP address information and Device Identifier to the PCF 436 via an existing policy association (created in step 476). In another embodiment the SMF 433 forwards the Device Identifier, IP address and MAC address associated to the non-3GPP device 414.

[0091] At 492, the PCF 436 associates the received MAC address to the Device Identifier (based on the mapping stored in step 477), retrieves QoS information for the Device Identifier from the UDR (not shown) and derives PCC rules for the UE / 5G-RG 410 using the IP address associated to the MAC address received in step 491.

[0092] At 493, PCC rules are sent to the UE / 5G-RG 410 and the core network as per existing procedures.

[0093] In an alternative, the SMF 433 stores the association of Device Identifier to MAC address in step 475. The PCF 436 may trigger the SMF 433 to report Device Identifier to IP address association in step 479. The SMF 433 may derive the association of Device Identifier to IP address in step 490 by associating the received MAC address to the Device Identifier received in step 475 and reports Device Identifier to IP address association in step 491.

[0094] Figure 5 illustrates an example of a process flow 500 in accordance with aspects of the present disclosure. The process flow 500 may implement or be implemented by aspects of the wireless communication system 500. For example, the process flow 500 may include a non-3GPP UE 514, a UE 510, an AMF 530, an SMF 533, a PCF 536, a UPF 539, and an Access Network 542. The non-3GPP UE 514 may be a tethered device. The UE510 may comprise a 5G-RG, which may be one or more examples of devices described herein with reference to Figure 1.

[0095]

[0037] The process flow 500 may be referred to as a procedure, including one or more operations performed by one or more of the non-3GPP UE 514, the UE 510, the AMF 530, the SMF 533, the PCF 536, the UPF 539, and the Access Network 542. In the example of Figure 5, the process flow 500 may include, when PDU session is IPv4 or IPv6 type for a second alternative where UPF derives MAC address. Here, the Device Identifier is linked to the IP address for PDU session type IPv4 / IPv6.

[0096] In the following description of the process flow 500, the operations or signalling performed between one or more of the non-3GPP UE 514, the UE 510, the AMF 530, the SMF 533, the PCF 536, the UPF 539, and the Access Network 542 may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the non-3GPP UE 514, the UE 510, the AMF 530, the SMF 533, the PCF 536, the UPF 539, and the Access Network 542may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 500. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0097] At 570, the UE / 5G-RG 510 registers with the network.

[0098] At 571, a non-3GPP device 514 is associated with the UE / 5G-RG 510 and the UE / 5G-RG 510 determines the Device Identifier and the MAC address of the non-3GPP device 514.

[0099] At 572, UE / 5G-RG 510 sends a PDU session establishment request, e.g., when a non-3GPP device 514 is associated, and includes the Device Identifier and MAC address of a non-3GPP device 514 with the PDU session establishment request. The PDU session establishment request may comprise a UL NAS Transport. The PDU session establishment request may comprise: PDU Session ID, S-NSSAI, DNN, Request Type, Payload Container Type = N1 SM Info, Pay load: PDU Session Establishment Request, Device Identifier, andthe user plane address such as a MAC address. The Device Identifier and user plane address may be included within the PDU Session Establishment request. The Device Identifier and user plane address may be exchanged outside the PDU session establishment request within N1 SM info.

[0100] At 573, 574, 575, as per PDU session establishment procedures the PDU session establishment request is received at the SMF 533 and the SMF 533 selects a PCF 536. The create session management context request at 574 may comprise at least one of: SUPI, PDU Session ID, S-NSSAI, DNN, AMF-ID, GUAMI, Request Type, Access Type, RAT Type, and PDU Session Establishment Req.(...)

[0101] At 576, the SMF 533 forwards the Device Identifier and MAC address to the PCF 536 within the Policy Association request. The message at 576 may comprise a SM Policy Control Create Request. The message at 576 may comprise at least one of SUPI, PDU Session ID, DNN, S-NSSAI, Access Type, Location, Device Identifier and the user plane address such as a MAC address. The SMF 533 also allocates an interface identifier to the UE 510 for the UE 510 to build its link-local address.

[0102] At 577, the PCF 536 obtains the Device Identifier from the UDR (not shown) and identifies its QoS requirements. The PCF 536 also stores the association of Device Identifier to MAC address.

[0103] At 578, the PCF 536 may trigger (within a PCC rule) the SMF 533 to report full IP address of uplink traffic from UE / 5G-RG 510 associated to a Device Identifier. In one embodiment the trigger to the SMF 533 to report IP address is based on a specific Policy Control Request Trigger.

[0104] At 579, 580, a per PDU session establishment procedures the PCC rule is received at SMF 533 and SMF 533 selects a UPF 539. At this point the SMF 533 may assign an IPv4 address or an IPv6 prefix plus an interface identifier for link-local address of the UE / 5G-RG 510.

[0105] At 581, 582, the N4 rule sent to the UPF 539 includes an indication to report MAC address and IP address of uplink traffic from UE / 5G-RG 510.

[0106] At 583, 584, 585, the PDU session establishment continues and UE / 5G-RG 510 receives the PDU session establishment accept message. At 583 an N1N2 message transfer request is sent from the SMF 533 to the AMF 530. Message 583 may comprise at least one of UE Context, PDU Session ID, N2 Info Container, 5QI, ARP (Allocation and Retention Priority), PPI, and PDU Session Est. Accept.

[0107] At 586, if IP address is not allocated at step 10, the UE / 5G-RG 510 may request IPv4 or IPv6 address by sending a Router Solicitation message. The request is received to the SMF 533 via the UPF 539.

[0108] At 587, the SMF 533 assigns an IPv4 address or an IPv6 prefix plus an interface identifier for link-local of the UE / 5G-RG 510. Each Router Advertisement message 587a and 587b may comprise either an IPv4 address or IPv6 prefix + interface identifier for linklocal address.

[0109] At 588, At this point the non-3GPP device 514 starts sending uplink traffic and the UE / 5G-RG 510 derives IPv4 or IPv6 address for the non-3GPP device 514. For IPv4 the UE / 5G-RG 510 assigns a port number for each non-3GPP device 514. For IPv6 the UE / 5G-RG 510 assigns an interface identifier for each non-3GPP device 514. The UE / 5G- RG 510 forwards uplink traffic based on the allocated IP4 / port number or full IPv6 address (i.e. prefix and interface identifier).

[0110] At 589, the UPF 539 receives UL traffic identifies the MAC address from UL traffic. This may be carried out by the UPF 539 sending Address Resolution Protocol (ARP) messages for IPv4 / IPv6 addresses or NDP messages for IPv6 addresses to the UE / 5G-RG 510 to obtain the MAC address corresponding to the IP address. The uplink traffic may comprise either IPv4 address / port number or IPv6 prefix + interface identifier allocated by UE for non-3GPP device. It should be noted that any Address Resolution Protocol (ARP) or NDP messages and / or queries between the UE and SMF may be carried out either via IP signalling or via NAS signalling.

[0111] At 590, the UPF 539 notifies the MAC address and IP address via N4 to the SMF 533.

[0112] At 591, the SMF 533 forwards the IP address information and Device Identifier to the PCF via an existing policy association (created in step 576). In another embodiment the SMF 533 forwards the Device Identifier, IP address and MAC address associated to the non-3GPP device 514.

[0113] At 592, the PCF 536 associates the received MAC address to the Device Identifier (based on the mapping stored in step 577), retrieves QoS information for the Device Identifier from the UDR and derives PCC rules for the UE / 5G-RG 510 using the IP address associated to the MAC address received in step 591.

[0114] At 593, PCC rules are sent to the UE / 5G-RG 510 and the core network as per existing procedures.

[0115] Figure 6 illustrates an example of a process flow 600 in accordance with aspects of the present disclosure. The process flow 600 may implement or be implemented by aspects of the wireless communication system 600. For example, the process flow 600 may include a non-3GPP UE 614, a UE 610, an AMF 630, an SMF 633, a PCF 636, a UPF 639, and an Access Network 642, which may be one or more examples of devices described herein with reference to Figure 1.

[0116] The process flow 600 may be referred to as a procedure, including one or more operations performed by one or more of the non-3GPP UE 614, the UE 610, the AMF 630, the SMF 633, the PCF 636, the UPF 639, and the Access Network 642. In the example of Figure 6, the process flow 600 may include, when PDU session is IPv4 or IPv6 type for a third alternative using an SMF based solution. Process flow 600 may operate without using Address Resolution Protocol (ARP) or NDP messaging to the UE. Here, the Device Identifier is linked to the IP address for PDU session type IPv4 / IPv6.

[0117] In the following description of the process flow 600, the operations or signalling performed between one or more of the non-3GPP UE 614, the UE 610, the AMF 630, the SMF 633, the PCF 636, the UPF 639, and the Access Network 642may be performed or signalled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the non-3GPP UE 614, the UE 610, the AMF 630, the SMF 633, the PCF 636, the UPF 639, and the Access Network642may be performed or signalled (e.g., transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 600. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0118] At 670, the UE / 5G-RG 610 registers with the network.

[0119] At 671, a non-3GPP device 614 is associated with the UE / 5G-RG 610 and theUE / 5G-RG 610 determines the Device Identifier and the MAC address of the non-3GPP device 614.

[0120] At 672, the UE / 5G-RG 610 sends a PDU session establishment request, e.g., when a non-3GPP device 614 is associated, and includes the Device Identifier only of a non-3GPP device 614 with the PDU session establishment request. The PDU session establishment request may comprise a UE NAS Transport. The PDU session establishment request may comprise: PDU Session ID, S-NSSAI, DNN, Request Type, Payload Container Type = N1 SM Info, Pay load: PDU Session Establishment Request, and Device Identifier. The Device Identifier and user plane address may be included within the PDU Session Establishment request. The Device Identifier and user plane address may be exchanged outside the PDU session establishment request within N1 SM info.

[0121] At 673, 674, 675, as per PDU session establishment procedures the PDU session establishment request is received at the SMF 633 and the SMF 633 selects a PCF 636. The create session management context request at 674 may comprise at least one of: SUPI, PDU Session ID, S-NSSAI, DNN, AMF-ID, GUAM!, Request Type, Access Type, RAT Type, and PDU Session Establishment Req.(...)

[0122] At 676, the SMF 633 forwards the Device Identifier and MAC address to the PCF 636 within the Policy Association request. The message at 676 may comprise a SM Policy Control Create Request. The message at 676 may comprise at least one of SUPI, PDU Session ID, DNN, S-NSSAI, Access Type, Location, Device Identifier and the user plane address such as a MAC address.

[0123] At 677, the PCF 636 obtains the Device Identifier from the UDR (not shown) and identifies its QoS requirements. The PCF 636 also stores the Device Identifier.

[0124] At 678, the PCF 636 may trigger (within a PCC rule) the SMF 633 to report full IP address corresponding to the Device Identifier. This may be carried out by means of a Policy Control Trigger Request.

[0125] At 679, 680, as per PDU session establishment procedures the PCC rule is received at SMF 633 and SMF 633 selects a UPF 639. At this point the SMF 633 may assign an IPv4 address or an IPv6 prefix plus an interface identifier for link-local address of the UE / 5G-RG 610.

[0126] At 681, 682, the N4 rule sent to the UPF 639.

[0127] At 683, 684, 685, the PDU session establishment continues and UE / 5G-RG 610 receives the PDU session establishment accept message. At 683 an N1N2 message transfer request is sent from the SMF 633 to the AMF 630. Message 683 may comprise at least one of UE Context, PDU Session ID, N2 Info Container, 5QI, Allocation and Retention Priority (ARP), PPI, and PDU Session Est. Accept.

[0128] At 686, if IP address is not allocated at step 10, the UE / 5G-RG 610 may request IPv4 or IPv6 address by sending a Router Solicitation message. The request is received to the SMF 633 via the UPF 639.

[0129] At 687, the SMF 633 assigns an IPv4 address or an IPv6 prefix plus an interface identifier for link-local of the UE / 5G-RG 610. Each Router Advertisement message 687a and 687b may comprise either an IPv4 address or IPv6 prefix + interface identifier for linklocal address.

[0130] At 688, at this point the non-3GPP device 614 starts sending uplink traffic and the UE / 5G-RG 610 derives IPv4 or IPv6 address for the non-3GPP device 614. For IPv4 the UE / 5G-RG 610 assigns a port number for each non-3GPP device 614. For IPv6 the UE / 5G-RG 610 assigns an interface identifier for each non-3GPP device 614.

[0131] At 689, the UE / 5G-RG 610 determines that the IP address used for a non-3GPP device 614 is linked to a Device Identifier that was reported in step 672.

[0132] At 690, 691, the UE / 5G-RG 610 triggers a PDU session modification request including the Device Identifier and Full IP address (IPv4 or IPv6) that is received at the SMF 633. An UL NAS Transport at 690 may comprise at least one of: PDU Session ID, S- NSSAI, DNN, Request Type, Payload Container Type = N1 SM Info, Payload: PDU session modification request, Device Identifier, and the user plane address such as a Full IP address. The Device Identifier and user plane address may be included within the PDU session modification request. The Device Identifier and user plane address may be exchanged outside the PDU session modification request within N1 SM info. An Update session management context request at 691 may comprise at least one of: SUPI, PDU Session ID, S-NSSAI, DNN, AMF-ID, GUAMI, Request Type, Access Type, RAT Type, and PDU session modification request (...).

[0133] At 690 instead of including the Device Identifier and user plane address within PDU session modification request signalling, the UE / 5G-RG may act as a DHCPv6 relay agent and send DHCPv6 solicit messages to the SMF. The solicit message may contain an encapsulated container including the Device Identifier and user plane address).

[0134] At 692, the SMF 633 determines to report the Device Identifier and Full IP address to the PCF 636 based on a policy from the PCF 636 (i.e. a Policy Control Request Trigger). An SM Policy Control Update Request at 692b may comprise at least one of SUPI, PDU Session ID, DNN, S-NSSAI, Access Type, Location, Device Identifier, Full IP address.

[0135] At 693, the SMF 633 forwards the Device Identifier and IP address information to the PCF 636 via an existing policy association (created in step 676).

[0136] At 692, the PCF 636 associates the received IP address to the Device Identifier, retrieves QoS information for the Device Identifier from the UDR and derives PCC rules for the UE / 5G-RG 610 using the associated IP address.

[0137] At 693, PCC rules are sent to the UE / 5G-RG 610 and the core network as per existing procedures.

[0138] In a further alternative, not illustrated, a UE based solution is provided. In this alternative the UE / 5G-RG provides the association of Device Identifier to IP address inPDU session signalling after the UE / 5G-RG assigns an IP address for a non-3GPP device, i.e., in step 488 of Figure 4 or in step 588 of Figure 5. The UE / 5G-RG does not provide any Device Identifier information at PDU session establishment.

[0139] In a further alternative, also not illustrated, a combination of the alternatives shown in Figures 4, 5 and 6 is provided. In this alternative the UE includes the MAC address and PDU Session Establishment as in Step 472 of Figure 4, step 572 of Figure 5, and step 672 of Figure 6. This is done irrespective of the PDU Session Type (i.e. Ethernet, IPv4 and / or IPv6 type).

[0140] For the case of the PDU session type being IPv4 and / or IPv6 the PCF may decide to trigger the SMF to report an IP address corresponding to the MAC address of the non-3GPP device provided by the UE. Alternatively, also for the case of the PDU session type being IPv4 and / or IPv6 the PCF may decide to instead trigger the SMF to report the IP address corresponding to the Device Identifier of the non-3GPP device provided by the UE in a PDU session modification request.

[0141] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0142] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0143] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). Insome implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0144] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0145] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein. The UE 700 may be configured to support a means for establishing a tethering connection with a first device; receiving a request from the first device for a first data connection; and sending a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0146] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0147] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. Thetransceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0148] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0149] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0150] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may be in electronic communication orotherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0151] The processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0152] The controller 802 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0153] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flowof data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0154] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).

[0155] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0156] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with avariety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0157] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to support a means for establishing a tethering connection with a first device; receiving a request from the first device for a first data connection; and sending a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device. Alternatively, the processor 800 may be configured to or operable to support a means for receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; sending a policy association request to a PCF the policy association request including the Device Identifier; receiving a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, sending a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receiving a notification of the source user plane address from the UPF; determining whether the source user plane address needs to be reported to the PCF.

[0158] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0159] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0160] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0161] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0162] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein. The NE 900 may be configured to support a means for receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; sending a policy association request to a PCF the policy association request including the Device Identifier; receiving a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, sending a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receiving anotification of the source user plane address from the UPF; determining whether the source user plane address needs to be reported to the PCF.

[0163] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0164] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0165] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0166] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0167] Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an NE s described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0168] At 1002, the method 1000 may include receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a NE as described with reference to Figure 9.

[0169] At 1004, the method 1000 may include sending a policy association request to a PCF the policy association request including the Device Identifier. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a NE as described with reference to Figure 9.

[0170] At 1006, the method 1000 may include receiving a policy association response from the PCF, the policy association response comprising a policy control request trigger. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed a NE as described with reference to Figure 9.

[0171] At 1008, the method may include in response to receiving the policy association response, sending a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1008 may be performed by a NE as described with reference to Figure 9.

[0172] At 1010, the method may include receiving a notification of the source user plane address from the UPF. The operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a NE as described with reference to Figure 9.

[0173] At 1012, the method may include determining whether the source user plane address needs to be reported to the PCF. The operations of 1012 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1012 may be performed a NE as described with reference to Figure 9.

[0174] It should be noted that the method 1000 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0175] Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0176] At 1102, the method 1100 may include establishing a tethering connection with a first device. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a UE as described with reference to Figure 7.

[0177] At 1104, the method 1100 may include receiving a request from the first device for a first data connection. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a UE as described with reference to Figure 7.

[0178] At 1106, the method 1100 may include sending a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed a UE as described with reference to Figure 7.

[0179] An SMF for wireless communication is described. The SMF may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the SMF may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the SMF to: receive a first request toestablish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a PCF the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

[0180] The SMF operates within a wireless communication network. The wireless communication network comprises at least one PCF. A wireless communication device connects to and communicates with the wireless communication network. The SMF may allow a PCF to identify the first device and thus allocate PCC rules to traffic sent from and / or received by the first device. This is particularly useful when the first device is a tethered device connected to the wireless communication network via the wireless communication device.

[0181] The at least one processor may be further configured to cause the SMF to report the source user plane address to the PCF.

[0182] The at least one processor may be further configured to cause the SMF to trigger a PCC rule update.

[0183] The source user plane address may be the Media Access Control (MAC) address of the first device. The policy association request may include the MAC address of the first device.

[0184] The source user plane address may be the full Internet Protocol (IP) address. The at least one processor may be further configured to cause the SMF to, in response receiving a notification of the source user plane address from the UPF, send a query to a UE for the MAC address of the first device.

[0185] The full IP address may comprise an IPv4 address or an IPv6 address. The full IP address may comprise an IPv4 address and port number. The full IP address may comprise an IPv6 prefix and interface identifier.

[0186] The query for the MAC address of the first device sent to the UE may comprise a query using the Address Resolution Protocol (ARP) or NDP. It should be noted that any Address Resolution Protocol (ARP) or NDP messages and / or queries between the UE and SMF may be carried out either via IP signalling or via NAS signalling.

[0187] The source user plane address may be a full IP address. The at least one processor may be further configured to cause the SMF to, after sending a trigger condition to the UPF to report the source user plane address of uplink traffic, receive a MAC address from the UPF.

[0188] The first device may be a non- Third Generation Partnership Project (3 GPP) device. The first device may be a NAS device. The first device may be connected to the 3 GPP network via a UE. The connection between the first device and the UE may be a tethered connection. The tethered connection may use Wi-Fi.

[0189] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a PCF the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

[0190] A method performed or performable by the SMF is described herein. The method may comprise: receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; sending a policy association request to a PCF the policy association request including the Device Identifier; receiving a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receivingthe policy association response, sending a trigger condition to a UPF, the trigger condition reporting a source user plane address of uplink traffic from the first device; receiving a notification of the source user plane address from the UPF; determining whether the source user plane address needs to be reported to the PCF.

[0191] The SMF operates within a wireless communication network. The wireless communication network comprises at least one PCF. A wireless communication device connects to and communicates with the wireless communication network. The method may allow a PCF to identify the first device and thus allocate PCC rules to traffic sent from and / or received by the first device. This is particularly useful when the first device is a tethered device connected to the wireless communication network via the wireless communication device.

[0192] The method may further comprise reporting the source user plane address to the PCF. The method may further comprise triggering a PCC rule update.

[0193] The source user plane address may be the MAC address of the first device. The policy association request may include the MAC address of the first device.

[0194] The source user plane address may be the full IP address. The method may further comprise, in response receiving a notification of the source user plane address from the UPF, sending a query to a UE for the MAC address of the first device.

[0195] The full IP address may comprise an IPv4 address or an IPv6 address. The full IP address may comprise an IPv4 address and port number. The full IP address may comprise an IPv6 prefix and interface identifier.

[0196] The query for the MAC address of the first device sent to the UE may comprise a query using the Address Resolution Protocol (ARP) and / or NDP. It should be noted that any Address Resolution Protocol (ARP) or NDP messages and / or queries between the UE and SMF may be carried out either via IP signalling or via NAS signalling.

[0197] The source user plane address may be a full IP address. The method may further comprise, after sending a trigger condition to the UPF to report the source user plane address of uplink traffic, receiving a MAC address from the UPF.

[0198] The first device may be a non- 3 GPP device. The first device may be a NAS device. The first device may be connected to the 3 GPP network via a UE. The connection between the first device and the UE may be a tethered connection. The tethered connection may use Wi-Fi.

[0199] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: establish a tethering connection with a first device; receive a request from the first device for a first data connection; send a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0200] The UE operates within a wireless communication network. The UE may connect to and communicate with the wireless communication network. The wireless communication network comprises at least one PCF. The UE may allow a PCF to identify the first device and thus allocate PCC rules to traffic sent from and / or received by the first device. This is particularly useful when the first device is a tethered device connected to the wireless communication network via the UE.

[0201] The at least one processor is further configured to cause the UE to: receive uplink data from the first device; and send the uplink data to the wireless communication network. The first device may be a non-3GPP device.

[0202] The first device may be a NAS device. The first device may be connected to the 3 GPP network via a UE. The connection between the first device and the UE may be a tethered connection. The tethered connection may use Wi-Fi. The first device may be connected to the UE via a tethered connection.

[0203] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: establish a tethering connectionwith a first device; receive a request from the first device for a first data connection; send a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0204] A method performed or performable by a UE is described. The method comprising: establishing a tethering connection with a first device; receiving a request from the first device for a first data connection; and sending a first request to an AMF the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

[0205] The UE operates within a wireless communication network. The UE may connect to and communicate with the wireless communication network. The wireless communication network comprises at least one PCF. The method allows a PCF to identify the first device and thus allocate PCC rules to traffic sent from and / or received by the first device. This is particularly useful when the first device is a tethered device connected to the wireless communication network via the UE.

[0206] The method may further comprise receiving uplink data from the first device and sending the uplink data to the wireless communication network.

[0207] The first device may be a non-3GPP device. The first device may be a NAS device. The first device may be connected to the 3 GPP network via a UE. The connection between the first device and the UE may be a tethered connection. The tethered connection may use Wi-Fi.

[0208] The first device may be connected to the UE via a tethered connection.

[0209] In some examples disclosed herein, the UE includes a Device Identifier and a MAC address in PDU session signalling. The PDF stores the Device Identifier, the MAC address, and a mapping between the Device Identifier and the MAC address. The SMF may request that the UPF notify IP address information for received uplink traffic and queries the 5G-RG / UE to provide the MAC address associated to the IP address and reports the information to the PCF. PCF associates the received MAC address to the Device Identifier (based on the mapping stored), retrieves QoS information for the DeviceIdentifier from the UDR and derives PCC rules for the UE / 5G-RG using the IP address associated to the MAC address provided by the SMF. In an alternative example the UE includes Device Identifier and Full IP address in PDU session modification signalling when the UE determines that the IP address of a non-3GPP device is linked to a Device Identifier. The SMF may forward the information to the PCF that is used by the PCF to derive PCC rules based on the Device Identifier.

[0210] It may be assumed that the UE includes Device Identifier and User Plane Address in PDU session establishment messages. However, this is not always possible as the IP address for a UE may not be allocated at initial PDU session establishment.

[0211] As defined herein, a UE provides only Device Identifier and MAC address of non-3GPP device in PDU session signalling. SMF or UPF derives IP address associated to MAC address by querying the UE (e.g. using Address Resolution Protocol (ARP) messages and / or NDP messages). Alternatively, the UE includes Device Identifier and Full IP address in PDU session modification signalling when the UE determines that the IP address of a non-3GPP device is linked to a Device Identifier. The SMF forwards the information to the PCF that is used by the PCF to derive PCC rules based on the Device Identifier. It should be noted that any Address Resolution Protocol (ARP) or NDP messages and / or queries between the UE and SMF may be carried out either via IP signalling or via NAS signalling.

[0212] There is further provided a method comprising: receiving a first request to establish a first data connection, the first data connection associated with a Device Identifier of a non-3GPP device; and receiving configuration information to provide the user plane address of the Device Identifier.

[0213] The first request may include a first address of the non-3GPP device and a Device Identifier. The first address of the non-3GPP device may be a MAC address.

[0214] A second request may be sent to a first network function to provide information associated to uplink traffic. In response to the second request IP address information for an uplink packet may be received.

[0215] A third request may be sent to provide MAC address associated to IP address. The third request may be sent to a UE / 5G-RG. The IP address and associated Device Identifier may be sent to a third network function. The first request may be associated to a Device Identifier.

[0216] A fourth request may be received including an address linked to Device Identifier. A fifth request is sent including address and Device Identifier to a third network function. The third network function may be a PCF. The fourth request may be a PDU session modification signalling.

[0217] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0218] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A Session Management Function (SMF) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the SMF to: receive a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; send a policy association request to a Policy Control Function (PCF) the policy association request including the Device Identifier; receive a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, send a trigger condition to a User Plane Function (UPF), the trigger condition reporting a source user plane address of uplink traffic from the first device; receive a notification of the source user plane address from the UPF; determine whether the source user plane address needs to be reported to the PCF.

2. The SMF of claim 1, wherein the at least one processor is further configured to cause the SMF to report the source user plane address to the PCF.

3. The SMF of claim 1 or 2, wherein the at least one processor is further configured to cause the SMF to trigger a Policy and Charging Control (PCC) rule update.

4. The SMF of claim 1, 2 or 3, wherein the source user plane address is the Media Access Control (MAC) address of the first device, and wherein the policy association request includes the MAC address of the first device.

5. The SMF of any of claims 1, 2 or 3, wherein the source user plane address is the full Internet Protocol (IP) address, and wherein the at least one processor is further configuredto cause the SMF to, in response receiving a notification of the source user plane address from the UPF, send a query to a user equipment (UE) for the MAC address of the first device.

6. The SMF of claim 5, wherein the query for the MAC address of the first device sent to the UE comprises a query using the Address Resolution Protocol (ARP) or the Neighbour Discovery Protocol (NDP).

7. The SMF of any of claims 1, 2 or 3, wherein the source user plane address is a full internet protocol (IP) address, and wherein the at least one processor is further configured to cause the SMF to, after sending a trigger condition to the UPF to report the source user plane address of uplink traffic, receive a MAC address from the UPF.

8. The SMF of any preceding claim, wherein the first device is a non-Third Generation Partnership Project (3 GPP) device.

9. A method performed or performable by a Session Management Function (SMF), the method comprising: receiving a first request to establish a first data connection for a first device, the first request comprising a Device Identifier associated with the first device; sending a policy association request to a Policy Control Function (PCF) the policy association request including the Device Identifier; receiving a policy association response from the PCF, the policy association response comprising a policy control request trigger; in response to receiving the policy association response, sending a trigger condition to a User Plane Function (UPF), the trigger condition reporting a source user plane address of uplink traffic from the first device; receiving a notification of the source user plane address from the UPF; determining whether the source user plane address needs to be reported to the PCF.

10. A user equipment (UE), comprising:at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: establish a tethering connection with a first device; receive a request from the first device for a first data connection; send a first request to an Access & Mobility Management Function (AMF) the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

11. The UE of claim 10, wherein the at least one processor is further configured to cause the UE to: receive uplink data from the first device; and send the uplink data to the wireless communication network.

12. The UE of claim 10 or 11, wherein the first device is a non-3GPP device.

13. The UE of claim 10, 11 or 12, wherein the first device is connected to the UE via a tethered connection.

14. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: establish a tethering connection with a first device; receive a request from the first device for a first data connection; send a first request to an Access & Mobility Management Function (AMF) the first request comprising a request to establish a first data connection for the first device, the first request comprising a Device Identifier of the first device.

Images