Non-access stratum (NAS) and core network (CN) updates for identifying non-3GPP devices connecting behind a UE or residential gateway

The implementation of NAS and CN updates in wireless communication systems addresses the challenge of identifying and managing non-3GPP devices behind a UE or RG, enabling QoS differentiation and monetization by signaling PDU Session Modifications, thus enhancing network efficiency and service delivery.

WO2026235886A1PCT designated stage Publication Date: 2026-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/023701
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-14
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems struggle to identify and provide Quality of Service (QoS) differentiation and monetization of services for non-3GPP devices connected behind a User Equipment (UE) or Residential Gateway (RG), as they lack the necessary protocols and mechanisms to differentiate and manage these devices effectively.

Method used

Implementing Non-Access Stratum (NAS) and Core Network (CN) updates to enable the identification and management of non-3GPP devices, allowing for QoS differentiation and monetization of services by signaling Protocol Data Unit (PDU) Session Modification Requests and authorization QoS rules through the network.

Benefits of technology

Enables effective identification and management of non-3GPP devices, ensuring differentiated Quality of Service and facilitating monetization of services by providing authorization and QoS rules, enhancing network efficiency and service delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026023701_12112026_PF_FP_ABST
    Figure US2026023701_12112026_PF_FP_ABST
Patent Text Reader

Abstract

An apparatus of a user equipment (UE) comprises processors configured to send, at the UE to a network (NW) via a base station (BS), a Protocol Data Unit (PDU) session modification request message comprising a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE) comprising information to enable a non-3GPP device to communicate with the NW via the UE operating as a gateway to the NW. The processors are configured to receive, at the UE from the NW via the BS, a PDU session modification command message comprising authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE or the non-3GPP device with authorized QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the gateway UE and obtain services with differentiated QoS.
Need to check novelty before this filing date? Find Prior Art

Description

Client Ref. No. P71774WO1NON-ACCESS STRATUM (NAS) AND CORE NETWORK (CN) UPDATES FOR IDENTIFYING NON-3GPP DEVICES CONNECTING BEHIND A UE OR RESIDENTIAL GATEWAY

[0001] Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for Non-Access Stratum (NAS) and core network (CN) updates for identifying non-Third Generation Partnership Project (non-3GPP) devices connecting behind a user equipment (UE) or a Residential Gateway (RG) in wireless communication systems.DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are used to provide various communication services such as telephone, video, data and messaging. The wireless communication systems can support communication with multiple users by sharing available system resources such as bandwidth and transmit power.

[0003] The wireless communication system may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, or the like. A UE may be referred to as a wireless mobile device or cellular phone.

[0004] Telecommunication standards have been adopted to provide a common protocol to enable different UEs and BSs to communicate on a municipal, national, regional, and even global level. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) or new radio (NR) (e.g., 5G). In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and / or Radio Network Controller (RNC) in an E-UTRAN, which communicate with the UE. In fifth generation (5G) wireless RANs, RAN Nodes can include a 5G Node, or NR node (also referred to as a next generation Node B or g Node B (gNB)).Client Ref. No. P71774WO1BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0006] FIG. 1A illustrates an example wireless communication system according to some embodiments.

[0007] FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.

[0008] FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.

[0009] FIG. 3 illustrates an example block diagram of a server according to some embodiments.

[0010] FIG. 4 illustrates an example block diagram of a UE according to some embodiments.

[0011] FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.

[0012] FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.

[0013] FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.

[0014] FIG. 8 illustrates example components of a core network in accordance with some embodiments.

[0015] FIG. 9 illustrates an example of an architecture to provide differentiated services (quality of service (QoS)) to a non-3GPP device behind a UE or a RG, according to some embodiments.

[0016] FIG. 10 illustrates an example of a flow to provision device profile andClient Ref. No. P71774WO1provide differentiated services, according to some embodiments.

[0017] FIG. 11 illustrates an example of signaling to modify a PDU session, according to some embodiments.

[0018] FIG. 12 illustrates an example coding for a non-3GPP device connection information IE, according to some embodiments.

[0019] FIG. 13 illustrates an example coding for a non-3GPP device connection information entry, according to some embodiments.

[0020] FIG. 14 illustrates an example coding for a user plane information when the user plane information type = “Ethernet”, according to some embodiments.

[0021] FIG. 15 illustrates an example coding for a user plane information when the user plane information type = “IPv4”, according to some embodiments.

[0022] FIG. 16 illustrates an example coding for a user plane information when the user plane information type = “IPv6”, according to some embodiments.

[0023] FIG. 17 illustrates an example coding for a user plane information when the user plane information type = "IPv4v6", according to some embodiments.

[0024] FIG. 18 illustrates an example coding for a non-3GPP device connection information IE, according to some embodiments.

[0025] FIG. 19 illustrates an example coding for a non-3GPP device information when VLAN TAG Indicator VTI = “1”, according to some embodiments.

[0026] FIG. 20 illustrates an example coding for a non-3GPP device information when IPv4 port range Indicator I4PRI = “1”, according to some embodiments.

[0027] FIG. 21 illustrates an example coding for a non-3GPP device information when IPv6 port range Indicator I6PRI = “1”, according to some embodiments.

[0028] While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, theClient Ref. No. P71774WO1intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.DETAILED DESCRIPTIONTerms

[0029] The following is a glossary of terms used in this disclosure:

[0030] Memory Medium or Memory - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

[0031] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0032] Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDsClient Ref. No. P71774WO1(Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.

[0033] Computer System (or Computer) - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0034] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, Internet of Things, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0035] Base Station - The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate with UEs as part of a wireless telephone system or radio system, including but not limited Next Generation Node-Bs (gNB or gNodeB) in NR and NG-RAN nodes.

[0036] Processing Element (or Processor) - refers to various elements orClient Ref. No. P71774WO1combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

[0037] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0038] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0039] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automaticClient Ref. No. P71774WO1procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system will update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken.

[0040] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as set by the particular application.

[0041] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0042] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaningClient Ref. No. P71774WO1“having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.

[0043] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0044] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to apparatuses, systems and methods for identifying non-3GPP devices connecting behind a UE or a Residential Gateway (RG), such as a 5G-RG or other desired type off RG, to support Quality of Service (QoS) differentiation and monetization of services.

[0045] The example embodiments are described with regard to communication between a network (NW) or core network (CN) and a UE or a RG, and one or more non-3GPP devices connected behind the UE or the RG, via a base station (BS) or a Next Generation Node B (gNB). However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to support communication and data transfer between the NW or the CN and the UE, the RG, and / or the one or more non-3GPP devices via the BS or gNB. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronicClient Ref. No. P71774WO1component.

[0046] The example embodiments are also described with regard to a fifth generation (5G) New Radio (NR). However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any appropriate type of network.

[0047] Throughout this description various information elements (lEs) are referred to by specific names. It should be understood that these names are only examples and the lEs carrying the information referred to throughout this description may be referred to by other names by various entities.Figures 1 A and 1 B: Communication Systems

[0048] FIG. 1 A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0049] As shown, the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more UEs 106A, 106B, etc., through 106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the UEs 106 are referred to as UEs or UE devices.

[0050] The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106A through 106N.

[0051] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radioClient Ref. No. P71774WO1(5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0052] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network 820 of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and / or between the user devices and the network 100. In particular, the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and / or data services.

[0053] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0054] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in FIG. 1A, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and / or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in FIG. 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.Client Ref. No. P71774WO1

[0055] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, a gNB cell may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0056] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0057] In some embodiments, the base station 102A may select a paging configuration and a PEI configuration for UEs 106. The base station 102A may encode and transmit the paging configuration and the PEI configuration to UEs 106 as part of a registration process. Using the paging configuration, UEs 106 can determine which PO and PF to monitor in a paging cycle. Using the PEI configuration, UEs 106 can determine the radio frame that carries relevant PEI.

[0058] FIG. 1 B illustrates user equipment 106 (e.g., one of the UEs 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, aClient Ref. No. P71774WO1computer or a tablet, or virtually any type of wireless device.

[0059] The UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0060] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD I eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 may share one or more parts of a receive and / or transmit chain between multiple wireless communication technologies, such as those discussed above.

[0061] In some embodiments, the UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or IxRTTor LTE or GSM), and separate radios forClient Ref. No. P71774WO1communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0062] As described herein, messages can be signaled between a UE 106 or a RG and the NW 100 via a BS 102 or gNB. The signaling can enable the NW 100 to identify one or more no-3GPP devices connected behind the UE 106 or the RG and to provide QoS differentiation and monetized services. The UE 106 or the RG can signal a Protocol Data Unit (PDU) Session Modification Request message to the NW 100 with a non-3GPP device connection information. The NW 100 can signal a PDU Session Modification Command message with authorization QoS rules and / or an authorized QoS flow description.FIG. 2: Block Diagram of a Base Station (gNB)

[0063] FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.

[0064] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UEs 106, access to the telephone network as described above in Figures 1 and 2.

[0065] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and / or other services to a plurality of devices, such as UEs 106. In some cases, the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., among other UEClient Ref. No. P71774WO1devices serviced by the cellular service provider).

[0066] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0067] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UEs 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0068] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0069] As described further subsequently herein, the base station 102 may include hardware and software components for implementing or supportingClient Ref. No. P71774WO1implementation of features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 204 of the base station 102, in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.

[0070] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.

[0071] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.

[0072] In some embodiments, the BS 102 or the gNB, and / or processors 204 thereof, can be capable of and configured to signal messages between the UE 106 or the RG and the NW 100 regarding identification information for non-3GPP devices connected behind the UE 106 or the RG, and authorization QoS rules and authorized QoS flow descriptions.Client Ref. No. P71774WO1FIG. 3: Block Diagram of a Server

[0073] FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.

[0074] The server 104 may be configured to provide a plurality of devices, such as base station 102, and UEs 106 access to network functions, e.g., as further described herein.

[0075] In some embodiments, the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server 104 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network.

[0076] As described herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 may be configured to implement or support implementation of part or all of the features described herein.

[0077] In addition, as described herein, processor(s) 344 may be comprised of one or more processing elements. In other words, one or more processingClient Ref. No. P71774WO1elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.FIG. 4: Block Diagram of a User Equipment (UE)

[0078] FIG. 4 illustrates an example simplified block diagram of a communication device 405, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device. According to embodiments, communication device 405 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices, among other devices. As shown, the communication device 405 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as separate components or groups of components for the various purposes. The set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 405.

[0079] For example, the communication device 405 may include various types of memory (e.g., including NAND flash memory 410), an input / output interface such as connector l / F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 405, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communicationClient Ref. No. P71774WO1circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 405 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0080] The cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. The short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438. The short to medium range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

[0081] In some embodiments, as further described below, cellular communication circuitry 430 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.

[0082] The communication device 405 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and / or speakers, one orClient Ref. No. P71774WO1more cameras, one or more buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.

[0083] The communication device 405 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUlCCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and / or the SIMs may be one or more embedded cards (such as embedded UICCs (eUlCCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUlCC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUlCC cards that implement eSIM functionality), as desired. For example, the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

[0084] As noted above, in some embodiments, the UE 106 may include two or more SIMs. The inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 to communicate on corresponding two or more respective networks. For example, aClient Ref. No. P71774WO1first SIM may support a first RAT such as LTE, and a second SIM support a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the LIE 106 comprises two SIMs, the UE 106 may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUlCC) that executes multiple SIM applications for different carriers and / or RATs.

[0085] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 405 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and / or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector l / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[0086] As described herein, the communication device 405 may includeClient Ref. No. P71774WO1hardware and software components for implementing the above features for a communication device 405 to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 405 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 405, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.

[0087] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.

[0088] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform theClient Ref. No. P71774WO1functions of short to medium range wireless communication circuitry 429.FIG. 5: Block Diagram of Cellular Communication Circuitry

[0089] FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 530, which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 405 described above. As noted above, communication device 405 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and / or a combination of devices, among other devices.

[0090] The cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4). In some embodiments, cellular communication circuitry 530 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 5, cellular communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

[0091] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 535. RF front end 535 may include circuitry for transmitting and receiving radio signals. For example, RF front end 535 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. InClient Ref. No. P71774WO1some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0092] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0093] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 530 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0094] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or inClient Ref. No. P71774WO1addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 535, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0095] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.

[0096] The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0097] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.FIG. 6: Block Diagram of a Baseband Processor Architecture for a UE

[0098] FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.

[0099] In some embodiments, the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end moduleClient Ref. No. P71774WO1(FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated device 600 may be included in a UE 106 or a BS 102A in a RAN node. In some embodiments, the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 600 may include additional elements such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0100] The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 600. In some embodiments, processors of application circuitry 602 may process IP data packets received from an EPC.

[0101] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband circuitry 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) basebandClient Ref. No. P71774WO1processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, modulation / demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, encoding / decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder / decoder functionality. Embodiments of modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0102] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F may be include elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).

[0103] In some embodiments, the baseband circuitry 604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), aClient Ref. No. P71774WO1wireless personal area network (WPAN). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0104] RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[0105] In some embodiments, the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. In some embodiments, the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.Client Ref. No. P71774WO1

[0106] In some embodiments, the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.

[0107] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.

[0108] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.

[0109] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0110] In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequencyClient Ref. No. P71774WO1synthesizers may be suitable. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0111] The synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N / N+1 synthesizer.

[0112] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 604 or the application circuitry 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 602.

[0113] Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0114] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrierClient Ref. No. P71774WO1frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ / polar converter.

[0115] FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[0116] In some embodiments, the FEM circuitry 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[0117] In some embodiments, the PMC 612 may manage power provided to the baseband circuitry 604. In particular, the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0118] While FIG. 6 shows the PMC 612 coupled only with the basebandClient Ref. No. P71774WO1circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.

[0119] In some embodiments, the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.

[0120] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 goes into a very low power state and it performs paging where, again, it periodically wakes up to listen to the network and then powers down at least portions of the device again. The device 600 may not receive data in this state. In order to receive data, it will transition back to an RRC_Connected state.

[0121] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[0122] In some embodiments, the UE 106 and / or the baseband circuitry 604 of the one or more processors thereof can send (encode for transmission): a tunnel establishment message to a network (NW) via a Radio Access Networks (RAN) comprising an address of the UE-side training server and a permission for a tunnel establishment between the NW training entity and the UE-side training server; a UE request message to the RAN with a request for non-over-the air (non-OTA)Client Ref. No. P71774WO1signaling, the address of the UE-side training server, a UE identification (ID) and a UE vendor and / or a UE type; a registration request message to an Access and Mobility Management Function (AMF) via Non-Access-Stratum (NAS) signaling comprising a request for non-over-the air (non-OTA) signaling, the address of the UE-side training server, a UE identification (ID) and UE vendor and / or UE type; a registration request message to an Access and Mobility Management Function (AMF) via Non-Access-Stratum (NAS) signaling comprising a request for non-over-the air (non-OTA) signaling, the address of the UE-side training server, a UE identification (ID) and UE vendor and / or UE type; an analytics request message to a Data Collection Analytics Function (DCAF) via a HyperText Transfer Protocol Secure (HTTPS) signaling comprising the address of the AF, a UE identification (ID) and a UE vendor and / or a UE type; a registration request message to an Access and Mobility Management Function (AMF) via a Non-Access-Stratum (NAS) signaling comprising a request for non-over-the air (non-OTA) signaling, the address of the UE-side training server, a UE identification (ID) and UE vendor and / or UE type; and a registration request message to an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) using a mobile terminal (MT) of the UE.

[0123] In addition, the UE 106 and / or the baseband circuitry 604 of the one or more processors thereof can be configured to send a Protocol Data Unit (PDU) session modification request message with a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE) with information to enable a non-3GPP device to communicate with the NW via the UE operating as a gateway UE to the NW; and receive a PDU session modification command message with authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE or the non-3GPP device with QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the gateway UE.FIG. 7: Block Diagram of an Interface of Baseband CircuitryClient Ref. No. P71774WO1

[0124] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.

[0125] As discussed above, the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors. Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send / receive data to / from the memory 604G.

[0126] The baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 712 (e.g., an interface to send / receive data to / from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send / receive data to / from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send / receive data to / from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send / receive power or control signals to / from the PMC 612.FIG. 8: Core Network

[0127] FIG. 8 illustrates an example architecture of a system 800 including a core network (CN) 820 in accordance with various embodiments. The CN 820 may be a core network for a 5G System (which may be referred to as a 5GC). The system 800 is shown to include a UE 801 , which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R)AN 810, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 803, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 820. The CN 820 may include a number of network functions including an Authentication Server Function (AUSF) 822; an Access andClient Ref. No. P71774WO1Mobility Management Function (AMF) 821 ; a Session Management Function (SMF) 824; a Network Exposure Function (NEF) 823; a Policy Control Function (PCF) 826; a Network Repository Function (NRF) 825; a Unified Data Management (UDM) 827; an Application Function (AF) 828; a User Plane Function (UPF) 802; and a Network Slice Selection Function (NSSF) 829. These network functions may be implemented, in some cases, as virtualized software-based functions / services.

[0128] The UPF 802 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 803, and a branching point to support mufti-homed PDU session. A PDU session is a logical connection between the UE and the DN. The UPF 802 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection), perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UUDL rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 802 may include an uplink classifier to support routing traffic flows to a data network, The DN 803 may represent various network operator services, Internet access, or third-party services. DN 803 may include, or be similar to, server 104 discussed previously. The UPF 802 may interact with the SMF 824 via an N4 reference point between the SMF 824 and the UPF 802.

[0129] The AUSF 822 may store data for authentication of UE 801 and handle authentication-related functionality, The AUSF 822 may facilitate a common authentication framework for various access types. The AUSF 822 may communicate with the AMF 821 via an N12 reference point between the AMF 821 and the AUSF 822; and may communicate with the UDM 827 via an N13 reference point between the UDM 827 and the AUSF 822. Additionally, the AUSF 822 may exhibit an Nausf service-based interface.

[0130] The AMF 821 may be responsible for registration management (e.g., forClient Ref. No. P71774WO1registering UE 801 , etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 821 may be a termination point for the an N11 reference point between the AMF 821 and the SMF 824. The AMF 821 may provide transport for SM messages between the UE 801 and the SMF 824, and act as a transparent proxy for routing SM messages. AMF 821 may also provide transport for Short Message Service (SMS) messages between UE 801 and an SMSF (not shown by FIG. 8). AMF 821 may act as a security anchor function (SEAF), which may include interaction with the AUSF 822 and the UE 801 , receipt of an intermediate key that was established as a result of the UE 801 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 821 may retrieve the security material from the AUSF 822. AMF 821 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 821 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 810 and the AMF 821 ; and the AMF 821 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.

[0131] AMF 821 may also support NAS signaling with a UE 801 over a non-3GPP Inter-Working Function (N3IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 810 and the AMF 821 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 810 and the UPF 802 for the user plane. As such, the AMF 821 may handle N2 signaling from the SMF 824 and the AMF 821 for PDU sessions and encapsulate / de- encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 801 and AMF 821 via an N1 reference point between the UE 801 and the AMF 821, and relay uplink and downlink user-plane packets between theClient Ref. No. P71774WO1UE 801 and UPF 802. The N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 801. The AMF 821 may exhibit an Namf service based interface, and may be a termination point for an N14 reference point between two AMFs 821 and an N17 reference point between the AMF 821 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 8).

[0132] The UE 801 may need to register with the AMF 821 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 801 with the network (e.g., AMF 821), and establish a UE context in the network (e.g., AMF 821 ). The UE 801 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 801 is not registered with the network, and the UE context in AMF 821 holds no valid location or routing information for the UE 801 so the UE 801 is not reachable by the AMF 821. In the RM REGISTERED state, the UE 801 is registered with the network, and the UE context in AMF 821 may hold a valid location or routing information for the UE 801 so the UE 801 is reachable by the AMF 821 . In the RM-REGISTERED state, the UE 801 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 801 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

[0133] The AMF 821 may store one or more RM contexts for the UE 801 , where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter glia, a registration state per access type and the periodic update timer. The AMF 821 may also store a 5GC mobility management (MM) context that may be the same or similar to the evolved packet services (EPS) Mobility Management (E)MM context discussed previously. In various embodiments, the AMF 821 may store a GE mode B Restriction parameter of the UE 801 in an associated MM context or registration management (RM) context. The AMF 821 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and / or MM / RM context).Client Ref. No. P71774WO1

[0134] Connection Management (CM) may be used to establish and release a signaling connection between the LIE 801 and the AMF 821 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 801 and the CN 820, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 801 between the AN (e.g., AN 810) and the AMF 821 . The UE 801 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 801 is operating in the CM-IDLE state / mode, the UE 801 may have no NAS signaling connection established with the AMF 821 over the N1 interface, and there may be (R)AN 810 signaling connection (e.g., N2 and / or N3 connections) for the UE 801 . When the UE 801 is operating in the CM-CONNECTED state / mode, the UE 801 may have an established NAS signaling connection with the AMF 821 over the Nl interface, and there may be a (R)AN 810 signaling connection (e.g., N2 and / or N3 connections) for the UE 801. Establishment of an N2 connection between the (R)AN 810 and the AMF 821 may cause the UE 801 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 801 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN 810 and the AMF 821 is released.

[0135] The SMF 824 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 801 and a data network (DN) 803 identified by a Data Network Name (DNN).Client Ref. No. P71774WO1PDU sessions may be established upon UE 801 request, modified upon UE 801 and CN 820 request, and released upon UE 801 and CN 820 request using NAS SM signaling exchanged over the N1 reference point between the UE 801 and the SMF 824. Upon request from an application server, the CN 820 may trigger a specific application in the UE 801 . In response to receipt of the trigger message, the UE 801 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 801 . The identified application(s) in the UE 801 may establish a PDU session to a specific data network name (DNN). The SMF 824 may check whether the UE 801 requests are compliant with user subscription information associated with the UE 801. In this regard, the SMF 824 may retrieve and / or request to receive update notifications on SMF 824 level subscription data from the UDM 827.

[0136] The SMF 824 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization / authentication by external DN. An N16 reference point between two SMFs 824 may be included in the system 800, which may be between another SMF 824 in a visited network and the SMF 824 in the home network in roaming scenarios. Additionally, the SMF 824 may exhibit the Nsmf service-based interface.

[0137] The NEF 823 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, Application Functions (e.g., AF 828), edge computing or fog computing systems, etc. In such embodiments, the NEF 823 may authenticate, authorize, and / or throttle the AFS. NEF 823 may also translate information exchanged with the AF 828 and information exchanged with internal network functions. For example, the NEF 823 may translate between an AF-Service-Identifier and an internal SCC information. NEF 823 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 823 as structured data, or atClient Ref. No. P71774WO1a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 823 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 823 may exhibit an Nnef servicebased interface.

[0138] The NRF 825 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 825 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 825 may exhibit the Nnrf service-based interface.

[0139] The PCF 826 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior, The PCF 826 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 827. The PCF 826 may communicate with the AMF 821 via an N15 reference point between the PCF 826 and the AMF 821 , which may include a PCF 826 in a visited network and the AMF 821 in case of roaming scenarios. The PCF 826 may communicate with the AF 828 via an NS reference point between the PCF 826 and the AF 828; and with the SMF 824 via an N7 reference point between the PCF 826 and the SMF 824, The system 800 and / or CN 820 may also include an N24 reference point between the PCF 826 (in the home network) and a PCF 826 in a visited network, Additionally, the PCF 826 may exhibit an Npcf service-based interface.

[0140] The UDM 827 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 801 . For example, subscription data may be communicated between the UDM 827 and the AMF 821 via an NS reference point between the UDM 827 and the AMF. The UDM 827 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 8). The UDR may store subscription data and policy data for the UDM 827 and the PCF 826, and / orClient Ref. No. P71774WO1structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 801) for the NEF 823. The Nadr service-based interface may be exhibited by the UDR to allow the UDM 827, PCF 826, and NEF 823 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 824 via an NIO reference point between the UDM 827 and the SMF 824. UDM 827 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 827 may exhibit the Nudm servicebased interface.

[0141] The AF 828 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the CN 820 and AF 828 to provide information to each other via NEF 823, which may be used for edge computing implementations. In such implementations, the network operator and third-party services may be hosted close to the UE 801 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 802 close to the UE 801 and execute traffic steering from the UPF 802 to DN 803 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 828. In this way, the AF 828 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 828 is considered to be a trusted entity, the network operator may permit AF 828 to interact directly with relevant NFs. Additionally, the AF 828 may exhibit an Naf service-based interface.Client Ref. No. P71774WO1

[0142] The NSSF 829 may select a set of network slice instances serving the UE 801. The NSSF 829 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed. The NSSF 829 may also determine the AMF set to be used to serve the UE 801, or a list of candidate AMF(s) 821 based on a suitable configuration and possibly by querying the NRF 825. The selection of a set of network slice instances for the UE 801 may be triggered by the AMF 821 with which the UE 801 is registered by interacting with the NSSF 829, which may lead to a change of AMF 821 . The NSSF 829 may interact with the AMF 821 via an N22 reference point between AMF 821 and NSSF 829; and may communicate with another NSSF 829 in a visited network via an N31 reference point (not shown by FIG. 8). Additionally, the NSSF 829 may exhibit an Nnssf service-based interface.

[0143] As discussed previously, the CN 820 may include a short message service function (SMSF), which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 801 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS may also interact with AMF 821 and UDM 827 for a notification procedure that the UE 801 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 827 when UE 801 is available for SMS).

[0144] The CN 820 may further include a location management function (LMF) 830. The LMF 830 receives measurements and assistance information from the base station 102A and the UE 106 via the AMF 821 over the NLs interface to compute the position of the UE 106.

[0145] The CN 820 may also include other elements that are not shown by FIG.8, such as a Data Storage system / architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system may include a Structured Data Storage Network Function (SDSF), air Unstructured Data Storage Function (UDSF), and / or the like. Any network function (NF) may store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 8), Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may eachClient Ref. No. P71774WO1have their own UDSF located at or near the individual NFs. Addition- ally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 8). The 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment / entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

[0146] Additionally, there may be many more reference points and / or servicebased interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 8 for clarity. In one example, the CN 820 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 821 in order to enable interworking between CN 820 and a CN in a 4G system. Other example interfaces / reference points may include an N5G-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

[0147] As described herein, the NW 100 and / or the CN 820 can have processors capable of and configured to receive a Protocol Data Unit (PDU) session modification request message with a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE) with information to enable a non-3GPP device to communicate with the NW via the UE or the RG; and send a PDU session modification command message with authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE, the RG or the non-3GPP device with QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the UE or the RG.Identifying non-3GPP Devices Connectina behind a UE or RG

[0148] Network settings can be adapted, and services can be offered to users according to users’ needs, different from a subscription identifier that is used by aClient Ref. No. P71774WO1user to establish the connection. This will allow an operator to charge, e.g. monetize, and provide service differentiation based on the user identifier and offer services to devices and users that are not part of the operator’s 3GPP network.

[0149] One or more user identifiers may be associated with the subscription, i.e., identified by a Subscription Permanent Identifier (SUPI), of a UE or Residential Gateway (RG) and the users require different treatment, i.e., service differentiation. In one scenario, the user identifier is used to identify the traffic that is sent to and / or from the UE. For example, this applies to the case where the user identifier identifies all traffic to and / or from the UE, i.e., the human user case. In another scenario, an identifier identifies a non-3GPP device behind a UE or RG.

[0150] Support for the identification of non-3GPP devices that communicate via a gateway UE may also enable use cases such as the deployment of a Mobile Virtual Private Network (VPN), such as a 5G, 6G, or other type of Mobile VPN, that is managed by the network. A Mobile VPN can provide a secure and reliable connection between an enterprise’s equipment, which includes non-3GPP devices, and authorized UEs that are located off-premises.

[0151] In addition, a goal can be to enable the non-3GPP devices to be identified and to use only the subscription of the UE or RG to access the Core Network (CN), such as a 5G Core (5GC) or 6G Core. Support for associating an identifier with traffic of a UE may enable charging and service differentiation by an RG’s home network operator for users who’s non-3GPP device(s) connect to the CN via the RG. This involves determining how user specific Quality of Service (QoS) settings are taken into account by the 3GPP system in order to provide service differentiation when providing communication services.

[0152] Enhancements to the Session Management (SM), such as a 5G SM or a 6G SM, to support association of the traffic from individual non-3GPP devices with a device identifier and use the device identifier to obtain QoS Settings for the traffic is needed. Enhancements to policy association procedures to support non-3GPP devices requiring QoS differentiation are needed, e.g., the Policy Control Function (PCF) may base its policy decision on the device identifier information.Client Ref. No. P71774WO1Updates to device identifiers and their corresponding QoS and / or Policies associated with a UE and / or RG subscription (e.g. 5G-RG) provisioned into the Unified Data Repository (UDR) are needed.

[0153] In addition, multiple non-3GPP device identifiers may be allowed in a single PDU Session Modification Request message. For a non-3GPP device identifier not available scenario, the Session Management Function (SMF) may reject the non-3GPP device identifier or may reject the whole PDU Session Modification Request message. For the scenario of removal of more than one non-3GPP device identifier from a subscription in the UDR, a single or multiple non-3GPP device identifiers may be permitted in a single PDU Session Modification Command message.

[0154] Furthermore, an identifier may be used by the network to control the traffic to and / or from UE or RG when the traffic is associated with the non-3GPP devices. The CN may need to identify individual non-3GPP devices connecting behind a UE or RG, e.g. in order to charge and / or monetize the individual non-3GPP devices. Enabling the non-3GPP devices to be identified and to use only the subscription of the UE or RG to access the CN is needed, i.e. , the UE or RG may have to maintain only a NAS Context itself and not for each non-3GPP device. Providing policy control for the traffic of individual non-3GPP devices connecting behind a UE or RG is needed. This may include triggering policy control for the traffic of individual non-3GPP devices via PCF and Network Exposure Function (NEF) Application Programming Interfaces (APIs), including support for concurrent services with differing QoS requirements launched by the different non-3GPP devices. Non-Access Stratum (NAS) signaling can be used to identify the non-3GPP devices. The operator can optionally restrict the number of simultaneously active User Identifiers per UE or RG. Other enhancements may be used to support QoS differentiation and provide additional services.FIG. 9: Architecture to Provide Differentiated Services to Non-3GPP Device Behind UE / RGClient Ref. No. P71774WO1

[0155] FIG. 9 illustrates an example of an architecture 900 to provide differentiated services (quality of service (QoS)) to a non-3GPP device behind a UE or a RG, according to some embodiments. One or more non-3GPP devices (1 to N) can be connected behind a user equipment (UE) or a Residential Gateway (RG), such as a 5G-RG or a 6G-RG. The UE or the RG can have a device profile client. The UE or the RG can connect to a Home Public Land Mobile Network (HPLMN) via an Auto-Configuration Server (ACS). In addition, the UE or the RG can connect to a Visited Public Land Mobile Network (VPLMN).

[0156] The HPLMN and the VPLMN can each have a Core Network (CN). The CN of the VPLMN can have a Visited Network Function (VNF). The CN of the HPLMN can have a Policy Control Function (PCF) and a Home Network Function (hNF). In addition, the HPLMN can have a Device Profile Server with an Application Function (AF). The ACS can connect to the AF of the HPLMN. The CN can connect to the AF.

[0157] A client program can run on the UE or the RG and can store the device information on a Device Profile Server. This program can determine the QoS for the non-3GPP devices behind the UE or the RG. The administrator of the UE or the RG can access the Device Profile Server and can select the appropriate QoS profile for each device.

[0158] The device information can be provided to the Policy Control Function (PCF) via a Network Exposure Function (NEF), and the PCF can provide relevant policies to enable differentiated policy and charging / monetization for each non-3GPP device.

[0159] The Device Profile (which is stored on the Device Profile server) can contain the following information for each non-3GPP device behind the UE or the RG; a) A Generic Public Subscription Identifier (GPSI) for the UE or the RG that can be used for addressing a 3GPP subscription in data network names (DNNs) outside the 3GPP system, b) Device Traffic Descriptors to detect the traffic to and / or from the non-3GPP device and to provide differentiated service (QoS) to this traffic and can include a source internet protocol (IP) address, port numbers, aClient Ref. No. P71774WO1Medium Access Control (MAC) address, etc.; c) a Device Identifier to uniquely identify the non-3GPP device and that can be host name or device credentials on a Authentication, Authorization, and Accounting (AAA) server; and / or d) a QoS Profile that identifies the QoS provided for the device.

[0160] The protocol between the Device Profile Client and the Device Profile Server may be out of scope of 3GPP (in Rel-19) but could be standardized.

[0161] Protocol Data Unit (PDU) sessions can be established for carrying traffic between devices and external Data Network Names (DNNs). Once PDU sessions are established, the Device Profile Server can request differentiated QoS. The PCF can use the Device Profile information and make policy decisions and provide Policy and Charging Control (PCC) rules for charging / monetizing the differentiated QoS.

[0162] The Device Profile Server may authenticate the device at an application layer (outside the scope of 3GPP.FIG. 10: Flow to Provision Device Profile and Provide Differentiated Services

[0163] FIG. 10 illustrates an example of a flow 1000 to provision device profile and provide differentiated services, according to some embodiments. One or more non-3GPP devices can connect behind a UE or a RG. The UE or the RG can be a Device Profile (DP) client. The UE or the -RG can connect to the network (NW) via a base station (BS), such a gNB.

[0164] The NW can comprise different Network Functions such as a Unified Data Management (UDM), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), and a Network Exposure Function (NEF). The NW can connect to a Devise Profile (DP) server with an Application Function (AF) and an external data network (DN) identified by a Data Network Name (DNN).

[0165] To provision and apply QoS for differentiated service, the administrator / user of the UE / RG can access the device portal (indicated at 1) andClient Ref. No. P71774WO1can provide information on non-3GPP devices to create a profile. The user can create a QoS profile for each of the non-3GPP devices. The DP Server can request information on the non-3GPP device (indicated at 2).

[0166] The non-3GPP device can be connected to the UE / RG and may be authenticated locally or via an external AAA server. The UE / RG can obtain device traffic descriptors and a device identifier from the non-3GPP device (indicated at 3).

[0167] The UE / RG can provision information on each non-3GPP device profile on the operator server (indicated at 4).

[0168] The non-3GPP device can connect to the UE / RG (indicated at 5)

[0169] The UE / RG can establish a PDU session to transfer data traffic (indicated at 6).

[0170] The Device Profile (DP) Server can set up an Application Function (AF) session with required QoS as specified using a QoS profile to generate QoS parameters and using a traffic descriptor (e.g. source IPv4 and port range, IPv6, or MAC address) for flow description information. Furthermore, the device identifier can be added to identify each non-3GPP device connected to the UE / RG. The QoS requirement can be obtained from the PCF (indicated at 7)

[0171] The UE Route Selection Policy (URSP) rules can be provided (indicated at 8) for differentiated QoS and a PDU session can be modified using a PDU Session Modification procedure (indicated at 9) to apply differentiated QoS in a user plane.

[0172] The UE or the RG can send the non-3GPP Device Identifier and may also send the MAC address and / or the VLAN tag ID (Ethernet PDU Session Type) or IP Address and / port ranges (IP PDU Session Type) associated with the non-3GPP Device Identifier to the SMF in the PDU session modification procedure.

[0173] Further, multiple non-3GPP device identifiers can be added in the PDU session modification procedure for efficiency. The UE or the RG can request to add, remove, and / or modify one or more of the non-3GPP device identifiers for theClient Ref. No. P71774WO1PDU session.

[0174] If the non-3GPP device identifier is not available for any reason, the SMF can reject the entire PDU Session Modification Request message.

[0175] T raff ic can flow with differentiated QoS (indicated at 10) .

[0176] In case the traffic descriptor in Device Profile is changed during the lifetime of a PDU session, items 7 to 9 can be executed to update the device information in the 5GC.

[0177] The number of non-3GPP devices using differentiated services can be enforced to be kept below a maximum number by configuring the Device Profile server to reject additional connections notified by the Device Profile client.

[0178] If the PCF indicates to the SMF that the corresponding non-3GPP Device Identifier is not available for the UE or the 3G-RG, the SMF can reject the PDU Session Modification Request message with a cause code to notify the UE or the RG that the non-3GPP Device Identifier is not available for the UE or the RG. A new SM cause value, such as a 5GSM cause value, dedicated for the scenario when the non-3GPP device identifier is not available for the UE can be defined.

[0179] As indicated above, multiple non-3GPP device identifiers can be allowed in a single PDU Session Modification Request message. The PDU Session Modification Request message can have multiple non-3GPP device identifiers.

[0180] For the non-3GPP device identifier not available scenario, the SMF can reject the non-3GPP device identifier or can reject the whole PDU Session Modification Request message. If any non-3PP Device Identifier in the PDU session modification request is not available in the UDR, the SMF can reject the entire PDU Session Modification Request message, without sending any non-3GPP Device Identifier. If any non-3GPP Device Identifiers received in a PDU Session Modification Request is not present within the Non-3GPP Device Identifier Information for the UE, the PCF can indicate to the SMF that one or more of the non-3GPP Device Identifier(s) is not available for the UE. In such case, the PCF can reject a SM Policy Association Modification and, based on the rejection received, the SMF can reject the PDU Session Modification message with a causeClient Ref. No. P71774WO1code to notify the UE that at least one of the non-3GPP Device Identifiers is not present for the UE.

[0181] For the scenario of removal of more than one non-3GPP device identifier from the subscription in the UDR, a single or multiple non-3GPP device identifiers can be permitted in a single PDU Session Modification Command message. If any non-3GPP device identifier is invalid or not available in the UDR, it may not be included in the PDU Session Modification Command message. When the non-3GPP Device Identifier Information is updated / removed in the UDR for one or more non-3GPP Device Identifiers, the UDR can notify the PCF via a Nudr DM Notify service of update / removal of non-3GPP Device Identifier Information. If there are PCC rule(s) associated to the traffic associated with the updated / removed non-3GPP Device Identifier in a PDU session, the PCF can remove or update the PCC rules and start a PCF initiated SM Policy Association Modification procedure, in which case the SMF can remove / update the corresponding QoS and N4 rule(s).FIG. 11 : Siqnalinq Flow to Modify PDU Session

[0182] FIG. 11 illustrates an example of signaling 1100 to modify a PDU session, according to some embodiments. The UE 106 or the RG can send to the NW 100 (or an AMF 821 thereof) via the base station (BS) 102 (e.g. a gNB), a PDU Session Modification Request message. The PDU Session Modification Request message can comprise non-3GPP device connection information, Requested QoS Rules, and / or Requested QoS Flow Descriptions. The NW 100 (or AMF) can send to the UE 106 or the RG via the BS 102 a PDU Session Modification Command message comprising Authorized QoS Rules and / or Authorized QoS Flow Descriptions. In some embodiments, the UE 106 or the RG can send to the NW 100 (or AMF) via the BS 102, a PDU Session Modification Command Reject message in case of failure. The he UE 106 or the RG can send to the NW 100 (or AMF) via the BS 102, a PDU Session Modification Complete message.

[0183] In one aspect, an apparatus of a user equipment (UE) 106 can comprise one or more processors 402 and / or 604A-D coupled to a memory 406 and / or 604G.Client Ref. No. P71774WO1The processors 604A-D can be configured to send, at the UE 106 to a network (NW) 100 via a base station (BS) 102, a Protocol Data Unit (PDU) session modification request message. The PDU session modification request message can comprise a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE). The non-3GPP device connection information IE can comprise information to enable a non-3GPP device to communicate with the NW 100 via the UE 106 operating as a gateway to the NW 100. The processors 604 can be configured to receive, at the UE 106 from the NW 100 via the BS 102, a PDU session modification command message. The PDU session modification command message can comprise authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE 106 or the non-3GPP device with authorized QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW 100 via the gateway UE.

[0184] In another aspect, the PDU session modification request message further comprises a non-3GPP device identifier to enable the NW to provide service differentiation.

[0185] In another aspect, the PDU session modification request message further comprises a request for QoS rules IE or a requested QoS flow descriptions IE.

[0186] In another aspect, the processors 604A-D are further configured to send, at the UE to the NW via the BS, a PDU session modification command reject message when the non-3GPP device is unable to communicate according to the authorized QoS rules or the authorized QoS flow descriptions.

[0187] In another aspect, the processors 604A-D are further configured to send, at the UE to the NW via the BS, a PDU session modification complete message when the non-3GPP device can communicate with the NW according to the authorized QoS rules or the authorized QoS flow descriptions.

[0188] In another aspect, the processors 604A-D are further configured to send, at the UE to a Device Profile (DP) server or Application Function (AF) of the NW in an Operator Portal via the BS, a message to create a QoS profile for the non-3GPPClient Ref. No. P71774WO1device and register the non-3GPP device for differentiated service from the NW. The processors 604A-D are further configured to receive, at the UE from the DP server of the NW via the BS, a request message for information regarding the non-3GPP device. The processors 604A-D are further configured to obtain, at the UE from the non-3GPP device, information regarding traffic descriptors and a non-3GPP device identifier. The processors 604A-D are further configured to send, at the UE to the DP server of the NW via the BS, an information message comprising the information regarding the non-3GPP device to provision the non-3GPP device profile on the DP server. The processors 604A-D are further configured to establish, at the UE, a connection with the non-3GPP device. The processors 604A-D are further configured to establish, at the UE, a PDU session with the NW including with one or more of Network Functions comprising a Unified Data Management (UDM), a Unified Data Repository (UDR), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), or a Network Exposure Function (NEF). The NW enables the DP server to set up an AF session with a required QoS as specified using a QoS profile to generate QoS parameters and using a traffic descriptor including a source IP address (IPv4 and port range, IPv6, or MAC address) for traffic flow description information, and enables the NW to use non-3GPP device identifier to enable differentiated monetization services provided to of the non-3GPP device. The processors 604A-D are further configured to obtain, at the UE, QoS requirements from the PCF. The processors 604A-D are further configured to enable differentiated QoS, between the UE and the NW, using UE Route Selection Policy (URSP) rules that are provisioned at the UE. A PDU session modification procedure enables modification of the PDU session to apply the differentiated QoS in a user plane. The PDU session modification procedure establishes end-to-end traffic between the NW and the non-3GPP device via the UE with differentiated QoS.

[0189] In another aspect, the NW stores a Device Profile for each non-3GPP device comprising one or more of: a) a Generic Public Subscription Identifier (GPSI) to enable addressing a 3GPP subscription of UE from external data networks (DNNs); b) Device Traffic Descriptors to enable detection of traffic toClient Ref. No. P71774WO1and / or from the non-3GPP device and to provide differentiated service based on the traffic to the non-3GPP device and comprising one or more of a source internet protocol (IP) address, port numbers, or a Medium Access Control (MAC) address; c) a Device Identifier configured to uniquely identify the non-3GPP device and comprises a host name or device credentials on an Authentication, Authorization, and Accounting (AAA) server; or d) a QoS Profile configured to identify the QoS provided for the non-3GPP device.

[0190] In another aspect, the PDU session modification request message comprises multiple non-3GPP identifiers. In another aspect, the processors are further configured to add, remove, or modify, at the UE, one or more of the multiple non-3GPP identifiers.

[0191] In another aspect, the processors 604A-D are further configured to receive, at the UE from a Session Management Function (SMF) of the NW, a rejection of the PDU session modification request message when a Policy Control Function (PCF) of the NW indicates to the SMF that a non-3GPP device identifier is not available in a Unified Data Repository (UDR) of the NW for the UE.

[0192] In another aspect, a Unified Data Repository (UDR) of the NW notifies a Policy Control Function (PCF) of the NW via a Nudr_DM_Notify service of update / removal of a non-3GPP device identifier information when the non-3GPP device identifier information is updated / removed in the UDR for one or more non-3GPP device identifiers. In another aspect, the PCF removes or updates Policy and Charging Control (PCC) rules and starts a PCF initiated Session Management (SM) Policy Association Modification procedure. In another aspect, a Session Management Function (SMF) removes / updates corresponding QoS rules when PCC rules for traffic associated with the updated / removed non-3GPP device identifier are updated / removed in the PDU session.

[0193] In one aspect, an apparatus of a network (NW) 100 can comprise one or more processors coupled to a memory. The processors can be configured to receive, at the NW 100 from a user equipment (UE) 106 or a Residential Gateway (RG) via a base station (BS) 102, a Protocol Data Unit (PDU) session modificationClient Ref. No. P71774WO1request message. The PDU session modification request message comprises a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE). The non-3GPP device connection information IE comprises information to enable a non-3GPP device to communicate with the NW via the UE or the RG. The processors can be configured to send, at the NW 100 to the UE 106 or the RG via the BS 102, a PDU session modification command message. The PDU session modification command message comprises authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE, the RG or the non-3GPP device with QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the UE or the RG.

[0194] In another aspect, the PDU session modification request message further comprises a non-3GPP device identifier to enable the NW to provide service differentiation.

[0195] In another aspect, the PDU session modification request message further comprises a request for QoS rules IE or a requested QoS flow descriptions IE.

[0196] In another aspect, the processors are further configured to receive, at the NW from the UE or the RG via the BS, a PDU session modification command reject message when the non-3GPP device is unable to communicate according to the authorized QoS rules or the authorized QoS flow descriptions.

[0197] In another aspect, the processors are further configured to receive, at the NW from the UE or the RG via the BS, a PDU session modification complete message when the non-3GPP has can communicate with the NW according to the authorized QoS rules or the authorized QoS flow descriptions.

[0198] In another aspect, the processors are further configured to receive, at a Device Profile (DP) server or Application Function (AF) of the NW in an operator portal from the UE or the RG via the BS, a message to create a QoS profile for the non-3GPP device and register the non-3GPP device for differentiated service from the NW. The processors are further configured to send, at the DP server of the NWClient Ref. No. P71774WO1to the UE or the 5-G-RF via the BS, a request message for information regarding the non-3GPP device. The UE is configured to obtain from the non-3GPP device information regarding traffic descriptors and a non-3GPP device identifier. The processors are further configured to receive, at the DP server of the NW from the UE or the RG via the BS, an information message comprising the information regarding the non-3GPP device to provision the non-3GPP device profile on the DP server. The UE or the RG is configured to establish a connection with the non-3GPP device. The processors are further configured to establish, at the NW with the UE or the RG, a PDU session with one or more Network Functions comprising a Unified Data Management (UDM), a Unified Data Repository (UDR), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), or a Network Exposure Function (NEF). The NW enables the DP server to set up an AF session with a required QoS as specified using a QoS profile to generate QoS parameters and using a traffic descriptor including a source IP address (IPv4 and port range, IPv6, or MAC address) for traffic flow description information, and enables the NW to use non-3GPP device identifier to enable monetization of differentiated services provided to the non-3GPP device. The processors are further configured to send, at the NW to the UE, the RG or the non-3GPP device, QoS requirements from the PCF. The processors are further configured to enable differentiated QoS, between the UE and the NW, using UE Route Selection Policy (URSP) rules that are provisioned at the UE for guidance. A PDU session modification procedure enables modification of the PDU session to apply the differentiated QoS in a user plane. The PDU session modification procedure establishes end-to-end traffic between the NW and the non-3GPP device via the UE with differentiated QoS.

[0199] For QoS differentiation of traffic for a non-3GPP device identifier, a 5G System (5GS) can support QoS differentiation of traffic for non-3GPP devices connecting through the UE. The UE and the network may support QoS differentiation of traffic for non-3GPP devices.

[0200] When a non-3GPP device is connecting to the UE, the UE can bind theClient Ref. No. P71774WO1non-3GPP device identifier to a non-3GPP device, for the traffic of non-3GPP devices that require differentiated QoS. This binding enables the 5GS to distinguish between the traffic generated by different non-3GPP devices connected through the same UE.

[0201] The QoS differentiation of traffic for non-3GPP device identifier also applies to the wireline access when a non-3GPP device is connecting to the 5G-RG.

[0202] The UE enables QoS differentiation of traffic from each non-3GPP device associated with a non-3GPP device identifier by providing the non-3GPP device identifier and the corresponding connection information to the SMF in the PDU session modification procedure. The Non-3GPP Device Connection Information may include information of more than one non-3GPP device. The SMF forwards the Non-3GPP Device Connection Information to the PCF for policy control. The UE shall provide the non-3GPP device connection information for the non-3GPP device depending on the PDU session type of the PDU session:a) for Ethernet PDU session type the UE shall include the non-3GPP device identifier and ethernet connection information;b) for IPv4 PDU session type the UE shall include the non-3GPP device identifier and IPv4 connection information;c) for IPv6 PDU session type the UE shall include the non-3GPP device identifier and IPv6 connection information; andd) for IPv4IPv6 PDU session type the UE shall include the non-3GPP device identifier and:1) IPv4 connection information;2) IPv6 connection information; or3) a combination of both 1) and 2).

[0203] In another aspect, the processors 402 or 604A-D are further configuredClient Ref. No. P71774WO1to bind, at the UE, a non-3GPP device identifier to a non-3GPP device when the non-3GPP device is connecting to the UE. Traffic of the non-3GPP device requires differentiated QoS. Binding the non-3GPP device identifier to the non-3GPP device enables the NW to distinguish between traffic generated by one or more non-3GPP devices connected through the UE.

[0204] In another aspect, the processors 402 or 604A-D are further configured to provide, at the UE, a non-3GPP device identifier and corresponding connection information of a non-3GPP device to a Session Management Function (SMF) of the NW in a PDU session modification procedure to enable QoS differentiation of traffic from one or more non-3GPP devices associated with the non-3GPP device identifier.

[0205] In another aspect, the processors 402 or 604A-D are further configured to provide, at the UE, non-3GPP device connection information for a non-3GPP device based on a PDU session type of a PDU session. The non-3GPP device connection information comprises: a non-3GPP device identifier and ethernet connection information for Ethernet PDU session type; a non-3GPP device identifier and IPv4 type IP connection information for a IPv4 PDU session type; a non-3GPP device identifier and IPv6 type IP connection information for a IPv6 PDU session type; or a non-3GPP device identifier for a IPv4IPv6 PDU session type along with: IPv4 connection information; IPv6 connection information; or both.

[0206] The purpose of the UE-requested PDU session modification procedure is:a) to enable the UE to request modification of a PDU session;b) to indicate a change of 3GPP PS data off UE status for a PDU session; c) to revoke the previously indicated support for reflective QoS;k) to request for differentiated QoS for one or more non-3GPP devices connecting through the UE.Client Ref. No. P71774WO1

[0207] For UE-requested PDU session modification procedure initiation, in order to initiate the UE-requested PDU session modification procedure, the UE shall create a PDU SESSION MODIFICATION REQUEST message.

[0208] The UE may include the Non-3GPP device connection information IE in the PDU SESSION MODIFICATION REQUEST message, when requesting to modify an established PDU session for one or more non-3GPP devices connecting through the UE for differentiated QoS. When the Non-3GPP device connection information IE is included in the PDU SESSION MODIFICATION REQUEST message, the operation code shall be set to:a) "add new non-3GPP device identifier" if the UE indicates adding the corresponding non-3GPP device to the network;b) "delete existing non-3GPP device identifier" if the UE indicates removing the corresponding non-3GPP device to the network; orc) "replace existing non-3GPP device identifier" if the UE indicates modifying the corresponding non-3GPP device to the network.

[0209] In another aspect, the PDU session modification request message comprises a request to modify an established PDU session for one or more non-3GPP devices connecting through the UE for differentiated QoS. The non-3GPP device connection information IE comprises an operation code to be sent to: "add new non-3GPP device identifier" when the UE indicates adding a corresponding non-3GPP device to the NW; "delete existing non-3GPP device identifier" when the UE indicates removing a corresponding non-3GPP device from the NW; or "replace existing non-3GPP device identifier" when the UE indicates modifying a corresponding non-3GPP device to the NW

[0210] The PDU SESSION MODIFICATION REQUEST message is sent by the UE to the SMF to request a modification of a PDU session. The Information element identifier (IEI) can be a unique number; the information element (IE) canClient Ref. No. P71774WO1be “Non-3GPP device connection information”; the type / reference can be “Non-3GPP device connection information 9.11.4. YY”; the presence can be O; the format can be TLV-E; and the length can be 7-n. The Message type can be PDU SESSION MODIFICATION REQUEST; the Significance can be dual; and the Direction can be UE to network.

[0211] For Non-3GPP device connection information, this IE is included in the message when the UE requests to add, remove or modify one or more non-3GPP devices connecting through the UE.

[0212] In another aspect, the PDU session modification request message is sent by the UE to a Session Management Function (SMF) of the NW to request a modification of a PDU session. The non-3GPP device connection information IE is included in the PDU session modification request message when the UE requests to add, remove or modify one or more non-3GPP devices connecting through the UE.FIGS. 12-17: Non-3GPP Device Connection Information IE

[0213] FIGS. 12-17 illustrate example coding for non-3GPP device connection information-information element (IE), according to some embodiments. The 9.11.4.YY reference, indicated above for the PDU Session Modification Request message, for the non-3GPP device connection information is shown in FIGS. 12-17, and discussed below. The purpose of the non-3GPP device connection information-information element (IE) is to indicate the non-3GPP device identifier(s) and the corresponding user plane information associated with the non-3GPP device identifier(s). The non-3GPP device connection informationinformation element is coded as shown in FIGS. 12-17 and discussed below. The non-3GPP device connection information-information element is a type 6 information element with minimum length of 7 octets.

[0214] FIG. 12 illustrates an example coding 1200 for a non-3GPP device connection information IE, according to some embodiments. The IE comprises a Non-3GPP device connection information IEI field, a length of Non-3GPP deviceClient Ref. No. P71774WO1connection information contents field, and Non-3GPP device connection information entry fields.

[0215] FIG. 13 illustrates an example coding 1300 for a non-3GPP device connection information entry, according to some embodiments. The IE comprises a length of non-3GPP device connection information entry field (octet 4). The length of non-3GPP device connection information entry field indicates the length of the non-3GPP device connection information entry field. The IE comprises a length of non-3GPP device identifier field (octet 5). The length of non-3GPP device identifier field indicates the length of the non-3GPP device identifier field. The IE comprises one or more Non-3GPP device identifier fields (octet 6 to octet s). The non-3GPP device identifier field indicates the identifier of the non-3GPP device connecting through the LIE. The non-3GPP device identifier is encoded as a Unicode Transformation Format, 8 bit, (UTF-8) string. The terms IPv4 and IPv6 used below are Internet Protocols to address and route data packets, while the term IPv4V6 indicates that both IPv4 and IPv6 are running on the same network. The IE comprises user plane information type field (octet (s+1 ), bits 1 to 3). The bits 3, 2 and 1 indicate:00 0 User plane information not included;00 1 Ethernet;0 1 0 IPv4;0 1 1 IPv6; and1 00 IPv4v6.

[0216] All other values are spare. The receiving entity shall ignore the user plane information field with user plane information type set to a spare value. When the user plane information type field is set to "user plane information not included", the user plane information field is not included in the IE.

[0217] The IE comprises an Operation code field (octet (s+1), bits 4 to 5). The bits 5 and 4 indicate:0 1 Add new non-3GPP device identifier;Client Ref. No. P71774WO11 0 Delete existing non-3GPP device identifier; and1 1 Replace existing non-3GPP device identifier.

[0218] All other values are spare. The receiving entity shall ignore the corresponding non-3GPP device connection information entry with operation code set to a spare value. For the "Add new non-3GPP device identifier" operation, the user plane information type field shall not be set to "user plane information not included". For the "delete existing non-3GPP device identifier" operation, the user plane information type field is set to "user plane information not included".

[0219] FIG. 14 illustrates an example coding 1400 for a user plane information when the user plane information type = “Ethernet”, according to some embodiments. The IE comprises a VLANTIPI (VLAN tag ID presence indicator) field (octet (s+2), bit 1 ). The VLANTIPI field indicates whether the VLAN tag ID field is included in the IE or not when the user plane information type is "Ethernet". The bit 1 indicates:0 VLAN tag ID not included; and1 VLAN tag ID included.

[0220] The IE comprises a MAC address field (octet (s+3) to octet (s+8)). The MAC address field indicates the MAC address of the non-3GPP device when the user plane information type is "Ethernet" (the MAC address is defined as in subclause 8 of IEEE Std 802).

[0221] The IE comprises a VLAN tag ID field (octet (s+9) to octet (s+10)). The VLAN tag ID field indicates the VLAN tag ID of the non-3GPP device when the user plane information type is "Ethernet" (the VLAN tag ID is defined as specified in IEEE Std 802.1Q).

[0222] FIG. 15 illustrates an example coding 1500 for a user plane information when the user plane information type = “IPv4”, according to some embodiments. The IE comprises a TPRI4PI (TCP port range for IPv4 presence indicator) field (octet (s+2), bit 1 ). The TPRI4PI field indicates whether the TCP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4". TheClient Ref. No. P71774WO1bit 1 indicates:0 TCP port range for IPv4 not included; and1 TCP port range for IPv4 included.

[0223] The IE can comprise a UPRI4PI (UDP port range for IPv4 presence indicator) field (octet (s+2), bit 2). The UPRI4PI field indicates whether the UDP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4". The bit 2 indicates:0 UDP port range for IPv4 not included; and1 UDP port range for IPv4 included.

[0224] The IE can comprise an IPv4 address field (octet (s+3) to octet (s+6)). The IPv4 address field indicates the IPv4 address of the non-3GPP device when the user plane information type is “IPv4".

[0225] The IE can comprise a TCP port range for IPv4 field (octet (s+7) to octet octet (s+10)). The TCP port range for IPv4 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv4". The TCP port range for IPv4 field consists of the lowest TCP port number coded in the octet (s+7) and octet (s+8), followed by the highest TCP port number coded in the octet (s+9) and octet (s+10).

[0226] The IE can comprise a UDP port range for IPv4 field (octet v to octet octet (v+3)). The UDP port range for IPv4 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv4". The UDP port range for IPv4 field consists of the lowest UDP port number coded in the octet v and octet (v+1 ), followed by the highest UDP port number coded in the octet (v+2) and octet (v+3).

[0227] FIG. 16 illustrates an example coding 1600 for a user plane information when the user plane information type = “IPv6”, according to some embodiments. The IE comprises an IPV6API (IPv6 address presence indicator) field (octet (s+2), bit 1) The IPV6API field indicates whether the IPv6 address field is included in the IE or not when the user plane information type is "IPv6". The bit 1 indicates:Client Ref. No. P71774WO10 IPv6 address not included; and1 IPv6 address included.

[0228] The IE can comprise an IPV6PPI (IPv6 prefix presence indicator) field (octet (s+2), bit 2). The IPV6PPI field indicates whether the IPv6 prefix field is included in the IE or not when the user plane information type is "IPv6". The bit 2 indicates:0 IPv6 prefix not included; and1 IPv6 prefix included.

[0229] The IE can comprise a TPRI6PI (TCP port range for IPv6 presence indicator) field (octet (s+2), bit 3). The TPRI6PI field indicates whether the TCP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6". The bit 3 indicates:0 TCP port range for IPv6 not included; and1 TCP port range for IPv6 included.

[0230] The IE can comprise a UPRI6PI (UDP port range for IPv6 presence indicator) field (octet (s+2), bit 4). The UPRI6PI field indicates whether the UDP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6". The bit 4 indicates:0 UDP port range for IPv6 not included; and1 UDP port range for IPv6 included.

[0231] The IE can comprise an IPv6 address field (octet (s+3) to octet (s+18)). The IPv6 address field contains an IPv6 address when the user plane information type value indicates "IPv6".

[0232] The IE can comprise an IPv6 prefix field (octet t to octet (t+16)). The IPv6 prefix field contains a sixteen octet IPv6 address field and one octet prefix length field when the user plane information type value indicates "IPv6". The IPv6 address field shall be transmitted first.

[0233] The IE can comprise a TCP port range for IPv6 field (octet a to octetClient Ref. No. P71774WO1octet (a+3)). The TCP port range for IPv6 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv6". The TCP port range for IPv6 field consists of the lowest TCP port number coded in the octet a and octet (a+1), followed by the highest TCP port number coded in the octet (a+2) and octet (a+3).

[0234] The IE can comprise a UDP port range for IPv6 field (octet b to octet octet (b+3)). The UDP port range for IPv6 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv6". The UDP port range for IPv6 field consists of the lowest UDP port number coded in the octet b and octet (b+1 ), followed by the highest UDP port number coded in the octet (b+2) and octet (b+3).

[0235] FIG. 17 illustrates an example coding 1700 for a user plane information when the user plane information type = "IPv4v6", according to some embodiments. The IE comprises an IPV6API (IPv6 address presence indicator) field (octet (s+2), bit 1). The IPV6API field indicates whether the IPv6 address field is included in the IE or not when the user plane information type is "IPv6". The bit 1 indicates:0 IPv6 address not included; and1 IPv6 address included.

[0236] The IE can comprise an IPV6PPI (IPv6 prefix presence indicator) field (octet (s+2), bit 2). The IPV6PPI field indicates whether the IPv6 prefix field is included in the IE or not when the user plane information type is "IPv6". The bit 2 indicates:0 IPv6 prefix not included; and1 IPv6 prefix included.

[0237] The IE can comprise a TPRI4PI (TCP port range for IPv4 presence indicator) field (octet (s+2), bit 3). The TPRI4PI field indicates whether the TCP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4". The bit 3 indicates:0 TCP port range for IPv4 not included; andClient Ref. No. P71774WO11 TCP port range for IPv4 included.

[0238] The IE can comprise a UDP UPRI4PI (UDP port range for IPv4 presence indicator) field (octet (s+2), bit 4). The UPRI4PI field indicates whether the UDP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4". The bit 4 indicates:0 UDP port range for IPv4 not included; and1 UDP port range for IPv4 included.

[0239] The IE can comprise a TPRI6PI (TCP port range for IPv6 presence indicator) field (octet (s+2), bit 5). The TPRI6PI field indicates whether the TCP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6". The bit 5 indicates:0 TCP port range for IPv6 not included; and1 TCP port range for IPv6 included.

[0240] The IE can comprise a UPRI6PI (UDP port range for IPv6 presence indicator) field (octet (s+2), bit 6). The UPRI6PI field indicates whether the UDP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6". The bit 6 indicates:0 UDP port range for IPv6 not included; and1 UDP port range for IPv6 included.

[0241] The IE can comprise an IPv4 address field (octet (s+3) to octet (s+6)). The IPv4 address field indicates the IPv4 address of the non-3GPP device when the user plane information type is "IPv4".

[0242] The IE can comprise an IPv6 address field (octet (s+7) to octet (s+22)). The IPv6 address field contains an IPv6 address when the user plane information type value indicates "IPv6".

[0243] The IE can comprise an IPv6 prefix field (octet c to octet (c+16)). The IPv6 prefix field contains a sixteen octet IPv6 address field and one octet prefix length field when the user plane information type value indicates "IPv6". The IPv6Client Ref. No. P71774WO1address field shall be transmitted first.

[0244] The IE can comprise a TCP port range for IPv4 field (octet d to octet octet (d+3)). The TCP port range for IPv4 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv4". The TCP port range for IPv4 field consists of the lowest TCP port number coded in the octet d and octet (d+1 ), followed by the highest TCP port number coded in the octet (d+2) and octet (d+3).

[0245] The IE can comprise a UDP port range for IPv4 field (octet e to octet octet (e+3)). The UDP port range for IPv4 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv4". The UDP port range for IPv4 field consists of the lowest UDP port number coded in the octet e and octet (e+1 ), followed by the highest UDP port number coded in the octet (e+2) and octet (e+3).

[0246] The IE can comprise a TCP port range for IPv6 field (octet f to octet octet (f+3)). The TCP port range for IPv6 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv6". The TCP port range for IPv6 field consists of the lowest TCP port number coded in the octet f and octet (f+1), followed by the highest TCP port number coded in the octet (f+2) and octet (f+3).

[0247] The IE can comprise a UDP port range for IPv6 field (octet g to octet octet (g+3)). The UDP port range for IPv6 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv6". The UDP port range for IPv6 field consists of the lowest UDP port number coded in the octet g and octet (g+1), followed by the highest UDP port number coded in the octet (g+2) and octet (g+3). When User plane information type is "IPv6" or "IPv4v6", the IPV6API bit is set to 1 or the IPV6PPI bit is set to 1 .FIGS. 18-21 : Non-3GPP Device Connection Information IE

[0248] FIGS. 18-21 illustrate example coding for non-3GPP device connection information-information element (IE), according to some embodiments. TheClient Ref. No. P71774WO19.11.4.YY reference, indicated above for the PDU Session Modification Request message, for the non-3GPP device connection information is shown in FIGS. 18-22, and discussed below. The purpose of the non-3GPP device connection information-information element (IE) is to indicate the non-3GPP device identifier(s) and the corresponding user plane information associated with the non-3GPP device identifier(s). The non-3GPP device connection informationinformation element is coded as shown in FIGS. 18-22 and discussed below. The non-3GPP device connection information-information element is a type 6 information element with minimum length of 7 octets.

[0249] FIG. 18 illustrates an example coding 1800 for a non-3GPP device connection information IE, according to some embodiments. The IE comprises a Non-3GPP device connection information IEI field (octet 1), a length of Non-3GPP device connection information contents field (octet 2), and a Non-3GPP device connection information entry field (octet 4). The IE also comprises a field (octet 3) with bits indicating PDU session type; IPv6 Address Indicator I6AI; IPv4 Address Indicator I4AI ; IPv6 port range indicator I6PRI; IPv4 port range indicator I4PRI; and VLAN TAG Indicator VTI.

[0250] FIG. 19 illustrates an example coding 1900 for a non-3GPP device information when VLAN TAG Indicator VTI = “1 ”, according to some embodiments. The IE comprises a Non-3GPP device identifier field (octet 4); a MAC address field (octet (k+1) to octet (k+5); and a VLAN tab ID field (octet (K+6)).

[0251] FIG. 20 illustrates an example coding 2000 for a non-3GPP device information when IPv4 port range Indicator I4PRI = “1”, according to some embodiments. The IE comprises Non-3GPP device identifier field (octet 4); an IPv4 address field (octet (k+1) to octet (k+5); and an IPv4 port range information field (octet (K+6)).

[0252] FIG. 21 illustrates an example coding 2100 for a non-3GPP device information when IPv6 port range Indicator I6PRI = “1”, according to some embodiments. The IE comprises Non-3GPP device identifier field (octet 4); an IPv6 address field (octet (k+1) to octet (k+5); and an IPv6 port range information fieldClient Ref. No. P71774WO1(octet (K+6)).New 5GSM Cause Value When Non-3GPP Device Identifier Not Available

[0253] A 5thGeneration Session Management (5GSM) cause value can be specified when a non-3GPP device identifier is not available.

[0254] Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF does not accept the request to modify the PDU session, the SMF shall create a PDU SESSION MODIFICATION REJECT message.

[0255] The SMF shall set the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message to indicate the reason for rejecting the PDU session modification.

[0256] The 5GSM cause IE typically indicates one of the following SM cause values:#26 insufficient resources;#83 Semantic error in the QoS operation;#84 Syntactical error in the QoS operation;#XX non-3GPP device identifier not available; or#95 - 111 protocol errors.

[0257] If the UE requests a PDU session modification for a Local Area Data Network (LADN) when the UE is located outside of the LADN service area, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.

[0258] If the UE initiates UE-requested PDU session modification procedure to request differentiated QoS for non-3GPP device identified by non-3GPP device identifier and the SMF determines that the non-3GPP device identifier is notClient Ref. No. P71774WO1available for the UE, the SMF shall include the 5GSM cause value #XX "non-3GPP device identifier not available" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.

[0259] For causes related to nature of request:Cause #8 - Operator Determined BarringThis 5GSM cause is used by the network to indicate that the requested service was rejected by the SMF due to Operator Determined Barring.Cause #26 - Insufficient resourcesThis 5GSM cause is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources.Cause #XX - Non-3GPP device identifier not availableThis 5GSM cause is used by the network to indicate that the requested non-3GPP device identifier is not available for the UE.

[0260] In another aspect, the processors 604A-D are further configured to receive, at the UE from the NW, a PDU session modification reject message comprising a 5thGeneration Session Management (5GSM) cause IE indicating a reason for rejecting the PDU session modification request message. The 5GSM cause IE comprises a session management (SM) value comprising “non-3GPP device identifier not available”. A Session Management Function (SMF) is configured to determine that the non-3GPP device identifier is not available for the UE.

[0261] The solutions outlined above allow the network to control the traffic to / from UE or RG when the traffic is associated with the non-3GPP devices using an identifier.

[0262] In one aspect, a baseband processor (e.g. baseband processor 604A-Client Ref. No. P71774WO1D), or functionally similar component(s) whose function may include supporting baseband layer operations (e.g., to facilitate wireless communication between the UE 106 and other wireless devices) in the UE 106, can be configured to cause the UE 106 to perform any of the methods described herein. In another aspect, the UE 106 can have one or more processors (e.g. processors 402 and / or 604A-D) coupled to a memory 406 or 604G to cause the user equipment 106 to perform any of the methods described herein. In another aspect, a baseband processor (e.g. baseband processor 604A-D can be configured to cause a base station 102 to perform one or more of the methods described herein. In another aspect, the base station 102 can have one or more processors 204 and / or 604A-D coupled to memory 260 or 604G configured to cause the base station 102 to perform any of the methods described herein. In another aspect, a computer program product, comprising computer instructions which, when executed by one or more processors, can perform any of the operations described herein.

[0263] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[0264] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

[0265] In some embodiments, a device (e.g., a UE 106) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where theClient Ref. No. P71774WO1program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.

[0266] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as message / signal X transmitted by the base station, and each message / signal Y transmitted in the uplink by the UE as a message / signal Y received by the base station.

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

Claims

Client Ref. No. P71774WO1CLAIMSWhat is claimed is:1 . An apparatus of a user equipment (UE) comprising:one or more processors, coupled to a memory, configured to:send, at the UE to a network (NW) via a base station (BS), a Protocol Data Unit (PDU) session modification request message;wherein the PDU session modification request message comprises a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE); wherein the non-3GPP device connection information IE comprises information to enable a non-3GPP device to communicate with the NW via the UE operating as a gateway to the NW; and receive, at the UE from the NW via the BS, a PDU session modification command message;wherein the PDU session modification command message comprises authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE or the non-3GPP device with authorized QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the gateway UE.

2. The apparatus of claim 1 , wherein the PDU session modification request message further comprises a non-3GPP device identifier to enable the NW to provide service differentiation.

3. The apparatus of claim 1 , wherein the PDU session modification request message further comprises a request for QoS rules IE or a requested QoS flow descriptions IE.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to:Client Ref. No. P71774WO1send, at the UE to the NW via the BS, a PDU session modification command reject message when the non-3GPP device is unable to communicate according to the authorized QoS rules or the authorized QoS flow descriptions.

5. The apparatus of claim 1 , wherein the one or more processors are further configured to:send, at the UE to the NW via the BS, a PDU session modification complete message when the non-3GPP device can communicate with the NW according to the authorized QoS rules or the authorized QoS flow descriptions.

6. The apparatus of claim 1 , wherein the one or more processors are further configured to:send, at the UE to a Device Profile (DP) server or Application Function (AF) of the NW in an Operator Portal via the BS, a message to create a QoS profile for the non-3GPP device and register the non-3GPP device for differentiated service from the NW;receive, at the UE from the DP server of the NW via the BS, a request message for information regarding the non-3GPP device;obtain, at the UE from the non-3GPP device, information regarding traffic descriptors and a non-3GPP device identifier;send, at the UE to the DP server of the NW via the BS, an information message comprising the information regarding the non- 3GPP device to provision the non-3GPP device profile on the DP server;establish, at the UE, a connection with the non-3GPP device; establish, at the UE, a PDU session with the NW including with one or more of Network Functions comprising a Unified Data Management (UDM), a Unified Data Repository (UDR), a User Plane Function (UPF), a Session Management Function (SMF), aClient Ref. No. P71774WO1Policy Control Function (PCF), or a Network Exposure Function (NEF);wherein the NW enables the DP server to set up an AF session with a required QoS as specified using a QoS profile to generate QoS parameters and using a traffic descriptor including a source IP address (IPv4 and port range, IPv6, or MAC address) for traffic flow description information, and enables the NW to use non- 3GPP device identifier to enable differentiated monetization of services provided to the non-3GPP device;obtain, at the UE, QoS requirements from the PCF; enable differentiated QoS, between the UE and the NW, using UE Route Selection Policy (URSP) rules that are provisioned at the UE; andwherein a PDU session modification procedure enables modification of the PDU session to apply the differentiated QoS in a user plane;wherein the PDU session modification procedure establishes end-to-end traffic between the NW and the non-3GPP device via the UE with differentiated QoS.

7. The apparatus of claim 6, wherein:the NW stores a Device Profile for each non-3GPP device comprising one or more of:a) a Generic Public Subscription Identifier (GPSI) to enable addressing a 3GPP subscription of UE from external data networks (DNNs);b) Device Traffic Descriptors to enable detection of traffic to and / or from the non-3GPP device and to provide differentiated service based on the traffic to the non-3GPP device and comprising one or more of a source internet protocol (IP) address, port numbers, or a Medium Access Control (MAC) address;Client Ref. No. P71774WO1c) a Device Identifier configured to uniquely identify the non- 3GPP device and comprises a host name or device credentials on an Authentication, Authorization, and Accounting (AAA) server; or d) a QoS Profile configured to identify the QoS provided for the non-3GPP device.

8. The apparatus of claim 1 , wherein the PDU session modification request message comprises multiple non-3GPP identifiers.

9. The apparatus of claim 8, wherein the one or more processors are further configured to:add, remove, or modify, at the UE, one or more of the multiple non-3GPP identifiers.

10. The apparatus of claim 1 , wherein the one or more processors are further configured to:receive, at the UE from a Session Management Function (SMF) of the NW, a rejection of the PDU session modification request message when a Policy Control Function (PCF) of the NW indicates to the SMF that a non-3GPP device identifier is not available in a Unified Data Repository (UDR) of the NW for the UE.11 .The apparatus of claim 1 , wherein:a Unified Data Repository (UDR) of the NW notifies a Policy Control Function (PCF) of the NW via a Nudr DM Notify service of update / removal of a non-3GPP device identifier information when the non-3GPP device identifier information is updated / removed in the UDR for one or more non-3GPP device identifiers;the PCF removes or updates Policy and Charging Control (PCC) rules and starts a PCF initiated Session Management (SM) Policy Association Modification procedure; anda Session Management Function (SMF) removes / updatesClient Ref. No. P71774WO1corresponding QoS rules when PCC rules for traffic associated with the updated / removed non-3GPP device identifier are updated / removed in the PDll session.

12. The apparatus of claim 1 , wherein the one or more processors are further configured to:bind, at the LIE, a non-3GPP device identifier to a non-3GPP device when the non-3GPP device is connecting to the LIE; and wherein traffic of the non-3GPP device requires differentiated QoS;wherein binding the non-3GPP device identifier to the non- 3GPP device enables the NW to distinguish between traffic generated by one or more non-3GPP devices connected through the UE.

13. The apparatus of claim 1, wherein the one or more processors are further configured to:provide, at the UE, a non-3GPP device identifier and corresponding connection information of a non-3GPP device to a Session Management Function (SMF) of the NW in a PDU session modification procedure to enable QoS differentiation of traffic from one or more non-3GPP devices associated with the non-3GPP device identifier.

14. The apparatus of claim 1 , wherein the one or more processors are further configured to:provide, at the UE, non-3GPP device connection information for a non-3GPP device based on a PDU session type of a PDU session;wherein the non-3GPP device connection information comprises:a non-3GPP device identifier and ethernet connectionClient Ref. No. P71774WO1information for Ethernet PDU session type;a non-3GPP device identifier and IPv4 type IP connection information for a IPv4 PDU session type;a non-3GPP device identifier and IPv6 type IP connection information for a IPv6 PDU session type; ora non-3GPP device identifier for a IPv4IPv6 PDU session type along with:IPv4 connection information;IPv6 connection information; orboth.

15. The apparatus of claim 1 , further comprising:wherein the PDU session modification request message comprises a request to modify an established PDU session for one or more non-3GPP devices connecting through the UE for differentiated QoS;wherein the non-3GPP device connection information IE comprises an operation code to be sent to:"add new non-3GPP device identifier" when the UE indicates adding a corresponding non-3GPP device to the NW;"delete existing non-3GPP device identifier" when the UE indicates removing a corresponding non-3GPP device from the NW; or"replace existing non-3GPP device identifier" when the UE indicates modifying a corresponding non-3GPP device to the NW.

16. The apparatus of claim 1 , further comprising:wherein the PDU session modification request message is sent by the UE to a Session Management Function (SMF) of the NW to request a modification of a PDU session;wherein the non-3GPP device connection information IE is included in the PDU session modification request message when theClient Ref. No. P71774WO1UE requests to add, remove or modify one or more non-3GPP devices connecting through the UE.

17. The apparatus of claim 1 , further comprising:wherein the non-3GPP device connection information IE is configured to indicate one or more non-3GPP device identifiers and corresponding user plane information associated with the one or more non-3GPP device identifiers;wherein the non-3GPP device connection information IE is a Type 6 IE with a minimum length of 7 octets.

18. The apparatus of claim 17, wherein the non-3GPP device connection information IE is coded as:a Non-3GPP device connection information-information element identifier (IEI) field (octet 1);a Length of Non-3GPP device connection information contents field (octet 2); andone or more Non-3GPP device connection information entry fields (octet 4).

19. The apparatus of claim 17, wherein a Non-3GPP device connection information IE is coded as:a length of a non-3GPP device connection information entry field (octet 4);the length of the non-3GPP device connection information field indicates the length of the non-3GPP device connection information entry;a length of non-3GPP device identifier field (octet 5);the length of the non-3GPP device identifier field indicates the length of the non-3GPP device identifier field;a Non-3GPP device identifier field (octet 6 to octet s); the non-3GPP device identifier field indicates the identifier ofClient Ref. No. P71774WO1the non-3GPP device connecting through the UE;the non-3GPP device identifier is encoded as a UTF-8 string; a user plane information type field (octet (s+1 ), bits 1 to 3); wherein the bits 3, 2 and 1 indicate:00 0 user plane information not included;00 1 ethernet;0 1 0 IPv4;0 1 1 IPv6; and1 00 IPv4v6;wherein all other values are spare and a receiving entity ignores the user plane information field with user plane information type set to a spare value;wherein when the user plane information type field is set to "user plane information not included", the user plane information field is not included in the IE;an operation code field (octet (s+1), bits 4 to 5); wherein the bits 5 and 4 indicate:0 1 add new non-3GPP device identifier;1 0 delete existing non-3GPP device identifier; and 1 1 replace existing non-3GPP device identifier; wherein all other values are spare;wherein a receiving entity ignores a corresponding non-3GPP device connection information entry with operation code set to a spare value; andwherein for the "add new non-3GPP device identifier" operation the user plane information type field is not be set to "user plane information not included";wherein for the "delete existing non-3GPP device identifier" operation the user plane information type field is set to "user plane information not included".Client Ref. No. P71774WO120. The apparatus of claim 17, wherein a user plane information type equals “Ethernet” and the user plane information is coded as:a VLANTIPI (VLAN tag ID presence indicator) field (octet (s+2), bit 1);the VLANTIPI field indicates whether the VLAN tag ID field is included in the IE or not when a user plane information type is "Ethernet";wherein the bit 1 indicates:0 VLAN tag ID not included; and1 VLAN tag ID included;a MAC address field (octet (s+3) to octet (s+8));the MAC address field indicates the MAC address of the non- 3GPP device when a user plane information type is "Ethernet"; a VLAN tag ID field (octet (s+9) to octet (s+10)); and the VLAN tag ID field indicates the VLAN tag ID of the non- 3GPP device when the user plane information type is "Ethernet".21 .The apparatus of claim 17, wherein a user plane information type equals “IPv4” and the user plane information is coded as:a TPRI4PI (TCP port range for IPv4 presence indicator) field (octet (s+2), bit 1);the TPRI4PI field indicates whether the TCP port range for IPv4 field is included in the IE or not when a user plane information type is "IPv4";wherein the bit 1 indicates:0 TCP port range for IPv4 not included; and1 TCP port range for IPv4 included;a UPRI4PI (UDP port range for IPv4 presence indicator) field (octet (s+2), bit 2);the UPRI4PI field indicates whether the UDP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4";Client Ref. No. P71774WO1wherein the bit 2 indicates:0 UDP port range for IPv4 not included; and1 UDP port range for IPv4 included;an IPv4 address field (octet (s+3) to octet (s+6));the IPv4 address field indicates the IPv4 address of the non- 3GPP device when the user plane information type is “IPv4";a TCP port range for IPv4 field (octet (s+7) to octet (s+10)); the TCP port range for IPv4 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv4";the TCP port range for IPv4 field comprises a lowest TCP port number coded in the octet (s+7) and octet (s+8) followed by a highest TCP port number coded in the octet (s+9) and octet (s+10); a UDP port range for IPv4 field (octet v to octet octet (v+3)); the UDP port range for IPv4 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv4"; andthe UDP port range for IPv4 field comprises a lowest UDP port number coded in the octet v and octet (v+1) followed by a highest UDP port number coded in the octet (v+2) and octet (v+3).

22. The apparatus of claim 17, wherein a user plane information type equals “IPv6” and the user plane information is coded as:an IPV6API (IPv6 address presence indicator) field (octet (s+2), bit 1);the IPV6API field indicates whether the IPv6 address field is included in the IE or not when a user plane information type is "IPv6";wherein the bit 1 indicates:0 IPv6 address not included; and1 IPv6 address included;an IPV6PPI (IPv6 prefix presence indicator) field (octet (s+2), bit 2);Client Ref. No. P71774WO1the IPV6PPI field indicates whether the IPv6 prefix field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 2 indicates:0 IPv6 prefix not included; and1 IPv6 prefix included;a TPRI6PI (TCP port range for IPv6 presence indicator) field (octet (s+2), bit 3);the TPRI6PI field indicates whether the TCP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 3 indicates:0 TCP port range for IPv6 not included; and 1 TCP port range for IPv6 included;a UPRI6PI (UDP port range for IPv6 presence indicator) field (octet (s+2), bit 4);the UPRI6PI field indicates whether the UDP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 4 indicates:0 UDP port range for IPv6 not included; and 1 UDP port range for IPv6 included;an IPv6 address field (octet (s+3) to octet (s+18));the IPv6 address field contains an IPv6 address when a user plane information type value indicates "IPv6";an IPv6 prefix field (octet t to octet (t+16));the IPv6 prefix field contains a sixteen octet IPv6 address field and one octet prefix length field when the user plane information type value indicates "IPv6", and the IPv6 address field is transmitted first;a TCP port range for IPv6 field (octet a to octet (a+3)); the TCP port range for IPv6 field indicates the TCP port range of the non-3GPP device when the user plane information type isClient Ref. No. P71774WO1"IPv6";the TCP port range for IPv6 field comprises a lowest TCP port number coded in the octet a and octet (a+1) followed by a highest TCP port number coded in the octet (a+2) and octet (a+3);a UDP port range for IPv6 field (octet b to octet (b+3)); the UDP port range for IPv6 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv6"; andthe UDP port range for IPv6 field comprises a lowest UDP port number coded in the octet b and octet (b+1) followed by a highest UDP port number coded in the octet (b+2) and octet (b+3).

23. The apparatus of claim 17, wherein a user plane information type equals “IPv4v6” and the user plane information is coded as:an IPV6API (IPv6 address presence indicator) field (octet (s+2), bit 1);the IPV6API field indicates whether the IPv6 address field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 1 indicates:0 IPv6 address not included; and1 IPv6 address included;an IPV6PPI (IPv6 prefix presence indicator) field (octet (s+2), bit 2);the IPV6PPI field indicates whether the IPv6 prefix field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 2 indicates:0 IPv6 prefix not included; and1 IPv6 prefix included;a TPRI4PI (TCP port range for IPv4 presence indicator) field (octet (s+2), bit 3);Client Ref. No. P71774WO1the TPRI4PI field indicates whether the TCP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4";wherein the bit 3 indicates:0 TCP port range for IPv4 not included; and 1 TCP port range for IPv4 included;a UDP UPRI4PI (UDP port range for IPv4 presence indicator) field (octet (s+2), bit 4);the UPRI4PI field indicates whether the UDP port range for IPv4 field is included in the IE or not when the user plane information type is "IPv4";wherein the bit 4 indicates:0 UDP port range for IPv4 not included; and 1 UDP port range for IPv4 included;a TPRI6PI (TCP port range for IPv6 presence indicator) field (octet (s+2), bit 5);the TPRI6PI field indicates whether the TCP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 5 indicates:0 TCP port range for IPv6 not included; and 1 TCP port range for IPv6 included;a UPRI6PI (UDP port range for IPv6 presence indicator) field (octet (s+2), bit 6);the UPRI6PI field indicates whether the UDP port range for IPv6 field is included in the IE or not when the user plane information type is "IPv6";wherein the bit 6 indicates:0 UDP port range for IPv6 not included; and 1 UDP port range for IPv6 included;an IPv4 address field (octet (s+3) to octet (s+6));the IPv4 address field indicates the IPv4 address of the non-Client Ref. No. P71774WO13GPP device when the user plane information type is "IPv4";an IPv6 address field (octet (s+7) to octet (s+22));the IPv6 address field contains an IPv6 address when a user plane information type value indicates "IPv6";an IPv6 prefix field (octet c to octet (c+16));the IPv6 prefix field contains a sixteen octet IPv6 address field and one octet prefix length field when the user plane information type value indicates "IPv6";the IPv6 address field is transmitted first;a TCP port range for IPv4 field (octet d to octet octet (d+3)); the TCP port range for IPv4 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv4";the TCP port range for IPv4 field comprises a lowest TCP port number coded in the octet d and octet (d+1) followed by a highest TCP port number coded in the octet (d+2) and octet (d+3);a UDP port range for IPv4 field (octet e to octet octet (e+3)); the UDP port range for IPv4 field indicates the UDP port range of the non-3GPP device when the user plane information type is "IPv4";the UDP port range for IPv4 field comprises a lowest UDP port number coded in the octet e and octet (e+1) followed by a highest UDP port number coded in the octet (e+2) and octet (e+3);a TCP port range for IPv6 field (octet f to octet octet (f+3)); the TCP port range for IPv6 field indicates the TCP port range of the non-3GPP device when the user plane information type is "IPv6";the TCP port range for IPv6 field comprises a lowest TCP port number coded in the octet f and octet (f+1 ) followed by a highest TCP port number coded in the octet (f+2) and octet (f+3);a UDP port range for IPv6 field (octet g to octet octet (g+3)); the UDP port range for IPv6 field indicates the UDP port rangeClient Ref. No. P71774WO1of the non-3GPP device when the user plane information type is "IPv6"; andthe UDP port range for IPv6 field comprises a lowest UDP port number coded in the octet g and octet (g+1) followed by a highest UDP port number coded in the octet (g+2) and octet (g+3); wherein when the user plane information type is "IPv6" or "IPv4v6", the IPV6API bit is set to 1 or the IPV6PPI bit is set to 1 .

24. The apparatus of claim 17, wherein the one or more processors are further configured to:receive, at the UE from the NW, a PDU session modification reject message comprising a 5thGeneration Session Management (5GSM) cause IE indicating a reason for rejecting the PDU session modification request message; andwherein the 5GSM cause IE comprises a session management (SM) value comprising “non-3GPP device identifier not available”;wherein a Session Management Function (SMF) is configured to determine that the non-3GPP device identifier is not available for the UE.

25. An apparatus of a network (NW) comprising:one or more processors, coupled to a memory, configured to:receive, at the NW from a user equipment (UE) or a Residential Gateway (RG) via a base station (BS), a Protocol Data Unit (PDU) session modification request message;wherein the PDU session modification request message comprises a non-Third Generation Partnership Project (non-3GPP) device connection information-information element (IE); wherein the non-3GPP device connection information IE comprises information to enable a non-3GPP device to communicate with the NW via the UE or the RG; andClient Ref. No. P71774WO1send, at the NW to the UE or the RG via the BS, a PDU session modification command message;wherein the PDU session modification command message comprises authorized quality of service (QoS) rules and authorized QoS flow descriptions to provide the UE, the RG or the non-3GPP device with QoS rules or QoS flow descriptions for the non-3GPP device to communicate with the NW via the UE or the RG.

26. The apparatus of claim 25, wherein the PDU session modification request message further comprises a non-3GPP device identifier to enable the NW to provide service differentiation.

27. The apparatus of claim 25, wherein the PDU session modification request message further comprises a request for QoS rules IE or a requested QoS flow descriptions IE.

28. The apparatus of claim 25, wherein the one or more processors are further configured to:receive, at the NW from the UE or the RG via the BS, a PDU session modification command reject message when the non-3GPP device is unable to communicate according to the authorized QoS rules or the authorized QoS flow descriptions.

29. The apparatus of claim 25, wherein the one or more processors are further configured to:receive, at the NW from the UE or the RG via the BS, a PDU session modification complete message when the non-3GPP has can communicate with the NW according to the authorized QoS rules or the authorized QoS flow descriptions.

30. The apparatus of claim 25, wherein the one or more processors are further configured to:Client Ref. No. P71774WO1receive, at a Device Profile (DP) server or Application Function (AF) of the NW in an operator portal from the UE or the RG via the BS, a message to create a QoS profile for the non-3GPP device and register the non-3GPP device for differentiated service from the NW;send, at the DP server of the NW to the UE or the RG via the BS, a request message for information regarding the non-3GPP device;wherein the UE is configured to obtain from the non-3GPP device information regarding traffic descriptors and a non-3GPP device identifier;receive, at the DP server of the NW from the UE or the RG via the BS, an information message comprising the information regarding the non-3GPP device to provision the non-3GPP device profile on the DP server;wherein the UE or the RG is configured to establish a connection with the non-3GPP device;establish, at the NW with the UE or the RG, a PDU session with one or more Network Functions comprising a Unified Data Management (UDM), a Unified Data Repository (UDR), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), or a Network Exposure Function (NEF);wherein the NW enables the DP server to set up an AF session with a required QoS as specified using a QoS profile to generate QoS parameters and using a traffic descriptor including a source IP address (IPv4 and port range, IPv6, or MAC address) for traffic flow description information, and enables the NW to use non-3GPP device identifier to enable monetization of differentiated services provided to the non-3GPP device;send, at the NW to the UE, the RG or the non-3GPP device, QoS requirements from the PCF;Client Ref. No. P71774WO1enable differentiated QoS, between the UE and the NW, using UE Route Selection Policy (URSP) rules that are provisioned at the UE for guidance; andwherein a PDU session modification procedure enables modification of the PDU session to apply the differentiated QoS in a user plane;wherein the PDU session modification procedure establishes end-to-end traffic between the NW and the non-3GPP device via the UE with differentiated QoS.

31. A user equipment (UE) configured to perform any of the operations described herein.

32. A baseband processor configured to perform any of the operations described herein.

33. A computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the operations described herein.