Method to handle access restrictions for network devices

Abstract

A method implemented in a first network node included in a Third Generation Partnership Project (3GPP) network is described. The first network node is configured to communicate with a first device behind a user equipment (UE). The method includes receiving from the UE via a second network node a Non-Access Stratum (NAS) registration request message to register the first device behind the UE. The UE uses a wireline connection to communicate with the second network node. The registration request message includes an indication indicating that the registration is for the first device. The method also includes obtaining subscription data indicating whether the first device is allowed connectivity to the 3GPP network and determining whether to accept or reject the NAS registration request message of the first device behind the UE based on the obtained subscription data.

Description

[0001] METHOD TO HANDLE ACCESS RESTRICTIONS FOR NETWORK DEVICES TECHNICAL FIELD The present disclosure relates to wireless communications, and in particular, to control and management of network access associated with network devices. BACKGROUND The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)), Fifth Generation (5G) (also referred to as New Radio (NR)), and Sixth Generation (6G) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes (NNs), such as base stations and user equipments (UEs), as well as communication between network nodes and between UEs. In some cases, UEs may be configured to communicate with other devices such as Authenticable Non-3GPP (AUN3) devices. More specifically, AUN3 devices may be supported to connect to 5G systems via 5G residential gateway (RG) (5G-RG) (or UE) according to 3GPP Release 18.The AUN3 device may be connected to a 5G system (5GS) via a 5G-RG and wireline access gateway function (W-AGF). The access and mobility function (AMF) and the session management function (SMF) are also involved in user registration and protocol data unit (PDU) Session Establishment for the AUN3 device. The AUN3 device has its own subscription in the Unified Data Repository (UDR). Based on Non-3GPP Device Category Definitions, the following requirement should be met: • A single subscription cannot be used to connect to both 3GPP access as a UE and non-3GPP access as an AUN3 device. The motivation behind this requirement is that the AUN3 connection is quite different from a UE connection in the sense that the AUN3 device’s non-access stratum (NAS) connection is terminated on the 5G-RG, while a UE’s NAS connection is terminated on the UE itself. Therefore, all NAS features, e.g. delivery of short message service (SMS), steering of roaming (SoR) information, etc. will not work for AUN3 devices, and a unique subscription for the AUN3 device is needed to avoid issues in deployments. An alternative solution is to use the existing ratRestriction field in the subscription data. For UEs, this field should be set to Wireline accesses, i.e., forbid UEs form accessing via wireline radio access technology (RAT) type, while for AUN3 subscriptions, it should include all the access except the Wireline ones, i.e., ensure that AUN3 devices can only connect via wireline access. Furthermore 5G-RG should be able to access both through wireline and 3GPP. This solution is very complex and requires an operator to update the subscription data for all the users, even existing mobile broadband (MBB) users. It thus creates an operation and management (O&M) burden and is prone to errors. SUMMARY Some embodiments advantageously provide methods, systems, and apparatuses for determining network access. A new field may be included in the subscription data of the AUN3 devices to indicate that the device is only allowed to access (e.g., the network) as an AUN3 device and not as a UE. During registration procedure, an AMF enforces the restriction based on the access type and the device type (AUN3 devices, 5G-RG, or UE). That is, the AMF may restrict at least some access to the device, e.g., it prevents the device from connecting using 3GPP access. In an embodiment, the access of devices is restricted based on whether the devices are trying to connect as AUN3 devices or not. In another embodiments, a new parameter is added to the subscription data in 5G core (5GC). In some embodiments, a new AMF functionality is used to accept or reject registration requests based on their access and subscription type. In some other embodiments, devices with AUN3 subscription may be prevented from connecting through 3GPP access. UEs or other devices may be prevented from connecting through wireline access (as AUN3 devices), which fulfills the 3GPP requirements. According to one aspect, a first network node configured to communicate with a second network node and / or a wireless device (WD) is described. The first network node is configured to determine whether to accept or reject a registration request based on whether: (A) subscription data associated with one or both of the WD and the second network node comprises one or both of a Residential Gateway Level Wireline Access Characteristics (RG-LWAC) parameter and a subscription data type parameter indicating whether a subscriber is allowed network access as a first type of WD; and / or (B) the registration request includes one or both of a first indication indicating a second type of the second network node and a second indication indicating the first type of the UE. According to another aspect, a method implemented in a first network node included in a Third Generation Partnership Project (3GPP) network is described. The first network node is configured to communicate with a first device behind a user equipment (UE). The method includes receiving from the UE via a second network node a Non- Access Stratum (NAS) registration request message to register the first device behind the UE. The UE uses a wireline connection to communicate with the second network node. The registration request message includes an indication indicating that the registration is for the first device. The method also includes obtaining subscription data indicating whether the first device is allowed connectivity to the 3GPP network and determining whether to accept or reject the NAS registration request message of the first device behind the UE based on the obtained subscription data. In some embodiments, the UE is a residential gateway. In some other embodiments, the residential gateway is a Fifth Generation (5G) residential gateway. In some other embodiments, the method further includes, if the subscription data indicates the first device is allowed connectivity and the NAS registration request message is not received from the UE via the wireline connection, rejecting the NAS registration request message. The wireline connection is configured to provide a wired signal path for communication between the UE and the second network node. In some embodiments, the method further includes, if the subscription data further indicates a residential gateway level wireline access characteristics (RG-LWAC) parameter and the NAS registration request message is received from the UE via the wireline connection, accepting the NAS registration request message. In some other embodiments, the method further includes, if the NAS registration request message includes a first device type indication for the first device, the subscription data indicates the first device is allowed connectivity, and the NAS registration request message is received via the wireline connection, accepting the NAS registration request message. In some embodiments, the method further includes, if the NAS registration request message includes a second device type indication for the UE and the NAS registration request message is received via the wireline connection, accepting the NAS registration request message. In some other embodiments, one or more of: (A) the first device is an authenticable non-3GPP device (AUN3) device; (B) the first network node comprises an access and mobility function (AMF); (C) the first network node is configured to communicate with the UE via the second network node; and (D) the second network node comprises wireline access gateway function (W-AGF). According to one aspect, a first network node in a Third Generation Partnership Project (3GPP) network is described. The first network node is configured to communicate with a first device behind a user equipment (UE). The first network node being configured to perform the steps of the method implemented in the first network node and / or its corresponding embodiments. According to another aspect, a first network node in a Third Generation Partnership Project (3GPP) network is described. The first network node is configured to communicate with a first device behind a user equipment (UE). The first network node includes processing circuitry and a memory comprising instructions which when executed by the processing circuitry will perform or performs the steps of the method implemented in the first network node and / or its corresponding embodiments. BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG. 1 is a schematic diagram of an exemplary network architecture illustrating a communication system according to the principles in the present disclosure; FIG. 2 shows an example architecture including an AUN3 device connected to a 5G-RG according to the principles in the present disclosure; FIG. 3 is a block diagram of a device, a UE, and one or more network nodes according to some embodiments of the present disclosure; FIG. 4 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure; FIG. 5 is a flowchart of another exemplary process in a network node according to some embodiments of the present disclosure; FIG. 6 shows an example 5GC registration of AUN3 device according to some embodiments of the present disclosure; FIG. 7 shows an example registration process according to some embodiments of the present disclosure; FIG. 8 shows another example 5GC registration of AUN3 device according to some embodiments of the present disclosure; and FIG. 9 shows an example PDU Session Release of AUN3 device behind a 5GRG. DETAILED DESCRIPTION Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to determining network access. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description. As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections. The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), an AMF, an RG, W-AGF, SMF, user plane function (UPF), authentication server function (AUSF), user data management (UDM), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a UE or a radio network node. In some embodiments, the non-limiting terms user equipment (UE) and wireless device (WD) may be used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals and / or with another device (e.g., AUN3 device) and / or with another network node via a wired or wireline connection. The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc. In some embodiments, a UE may refer to a residential gateway (RG). Similarly, the non-limiting terms device and AUN3 may be used interchangeably. An AUN3 device may refer to an authenticable Non-3GPP device, e.g., a device that may be authenticated such as by any component of a network including core network nodes, access network nodes, etc., and that is not considered to or does not support communication with network components based on 3GPP standards. In some embodiments, an AUN3 device may refer to a device that does not support NAS signaling, is connected to a core network (e.g., 5GC) via a UE (e.g., RG) and can be authenticated by the core network (e.g.,, 5GC) over the UE (e.g., RG). Further, a device may be configured to communicate with a UE such as an RG via wireline connection (i.e., wired connection), which may be configured to communicate with other network components such as access nodes, core network nodes, etc. Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises a network 12 (e.g., wireless access network, wireline access network, etc.) and a network 14 (e.g., core network). The network 12 comprises a plurality of network nodes 16a, 16b, 16c, 16d, 16e. Network nodes 16a, 16b, 16c may NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Network node 16d may an access node and may comprise and W- AGF and / or be associated with a wireline 5G access network (W-5GAN), etc. Each network node 16a, 16b, 16c, 16d is connectable to the network 14 (and / or network node 16d comprised in network 14) over a wired or wireless connection 20. Network node 16e in core network 14 may be core network node such as an AMF. Network nodes 16a, 16b, 16c, 16d, 16e may be referred to collectively as network nodes 16. Connections 100a, 100b, 100c, 100d are shown and may be collectively referred to as connection 100. A first wireless device (UE) 22a located in coverage area 18a is configured to connect (wirelessly and / or via wired connection 100a) to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is connectable (wirelessly and / or via wired connection 100b) to the corresponding network node 16b. A third UE 22c is connectable (wirelessly and / or via wired connection 100c) to the corresponding network node 16d. In some embodiments, connection 100c is a wired / wireline connection configured to provide a wired signal path between UE 22 and network node 16d. In some other embodiments, a wired / wireline connection may be configured to provide access to one or more devices via the wired signal path, where the one or more devices may access features and functions associated with the connection and / or corresponding network. UE 22c is also connectable (wirelessly and / or via wired connection 100d) to device 24 (which may be an AUN-3 device). Device 24 in this configuration may be referred to as being “behind” UE 22c, i.e., device 24 may be configured to communicate with network node 16d and / or other nodes such as network node 16e via UE 22c (e.g., RG). In some embodiments, connection 100c and / or connection 100d may be referred to as non-3GPP access. While a plurality of UEs 22a, 22b, 22c (collectively referred to as UE 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only three UEs 22 and five network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16. Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN. A network node 16 is configured to include a NN management unit 32 which is configured to perform on or more network node 16 functions such as determine network access (e.g., restrict, grant network access such as registration requests). A UE 22 is configured to include a UE management unit 34 which is configured to perform one or more UE functions described herein. FIG. 2 shows an example architecture associated with an AUN3 device and 3GPP network nodes, more specifically, an AUN3 device connected to a 5G residential gateway (RG). AUN3 device(s) 24 may be supported to connect to 5G systems via a UE 22 (e.g., 5G residential gateway (RG)). Device 24 may be connected to a network 12, 14, e.g., of a 5G system (5GS), via UE 22 and a network node 16d (e.g., W-AGF). For example, device 24 may be connected to UE 22 via a wired connection 100d (which may include also a wireless connection and may be referred to as Yt’). A wired connection may include an Ethernet connection, while a wireless connection may include a wireless local area network (WLAN) connection supporting WiFi, Bluetooth, etc. UE 22 may connect to network noes 16a, 16b, 16c supporting 3GPP access, such as via connections 100a, 100b. UE 22 may also be connected to network node 16d via a wired or wireless connection 100c (which may be referred to as Y4, non-3GPP access, etc.). Network node 16d may be configured to communicate with network node 16e (e.g., access and mobility function (AMF)), network node 16f (e.g., session management function (SMF), and network node 16g (e.g., a UPF). Network nodes 16d, 16e, 16f, 16g may also be involved in user registration and protocol data unit (PDU) Session Establishment for the AUN3 device. The AUN3 device may have its own subscription in the UDR. Further, Network node 16e may be configured to communicate with UE 22 via connection / interface N1, with network nodes 16a, 16b, 16c, 16d via connection / interface N2, and with network node 16f via connection / interface N11. Network node 16f may be configured to communicate with network node 16g via connection / interface N4, which may be configured to communicate with network node 16d via connection / interface N3 and with other components via connection / interface N6. Network nodes 16f and 16g are also part of the collection of elements generally referred to as network nodes 16. Example implementations, in accordance with an embodiment, of the UE 22, network node 16 and device 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a device 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection 100 with an interface of a different communication device of the communication system 10, such as UE 22, network node 16, etc. The device 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by device 24. Processor 44 corresponds to one or more processors 44 for performing device 24 functions described herein. The device 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the device application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to device 24. The instructions may be software associated with the device 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a device application 50. The device application 50 may be operable to provide a service to a user. In providing the service to the user, the device application 50 may provide user data and / or allow the user to make a request to access and / or connection to a network node 16 and / or UE 22, etc. The “user data” may be data and information described herein as implementing the described functionality. The processing circuitry 42 of the device 24 may include a device management unit 54 configured to which is configured to perform on or more device 24 functions. The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the device 24, the UE 22, and other network nodes 16 (such as via wired or wireless connection 102) . The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection 100 with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface may include one or more antennas 76. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the device 24 and wired connection 100 to the UE 22. The connection 66 may be direct or it may pass through a network 14 of the communication system 10 and / or through one or more intermediate networks outside the communication system 10. In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include a NN management unit 32 which is configured to perform on or more network node 16 functions such as determine network access (e.g., restrict, grant network access such as registration requests). The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located and / or communication interface 83 configured to set up and maintain wired connection 100 with a network node 16. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a UE application 92. The UE application 92 may be operable to provide a service to a human or non-human user via the UE 22. The UE application 92 may interact with the user to generate the user data that it provides. The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the UE application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 84 of the UE 22 may include a UE management unit 34 which is configured to perform one or more UE functions such as transmit a registration request, etc. In some embodiments, the inner workings of the network node 16, UE 22, and device 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2. The wireless connection 64 and wired connection 100 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. Although FIGS. 2 and 3 show various “units” such as NN management unit 32, and UE management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. FIG. 4 is a flowchart of an exemplary process in a network node 16 (e.g., an AMF). One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to determine (Block S100) whether to accept or reject a registration request based on whether subscription data associated with one or both of the WD and the second network node comprises one or both of a Residential Gateway Level Wireline Access Characteristics (RG-LWAC) parameter and a subscription data type parameter indicating whether a subscriber is allowed network access as a first type of WD; and / or the registration request includes one or both of a first indication indicating a second type of the second network node and a second indication indicating the first type of the WD. In some embodiments, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes, when the subscription data includes the RG-LWAC parameter and / or the subscription data type parameter indicating the subscriber is allowed network access as the first type of the WD, accepting the registration request. Otherwise, the registration request is rejected. In some other embodiments, when the registration request is received via a network node providing a 3GPP access or another node proving a predetermined non- 3GPP access, determining whether to accept or reject the registration request includes, when the subscription data includes the subscription data type parameter indicating the subscriber is allowed network access as the first type of the WD, rejecting the registration request. Otherwise, the registration request is accepted. In some embodiments, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes, when the registration request includes the first indication indicating the second type of the second network node and / or the second indication indicating the first type of WD, accepting the registration request. Otherwise, the registration request is rejected. In some embodiments, the WD is an Authenticable Non-3GPP device (AUN3) device, the subscription data type parameter includes an “AUN3 device connectivity allowed” field indicating whether the subscriber is allowed network access as the AUN3 device. In some other embodiments, one or both of the first network node comprises an access and mobility function (AMF) and the second network node comprises a residential gateway (RG). FIG. 5 is a flowchart of an exemplary process in a network node 16 (e.g., an AMF). More specifically, the method is implemented in a first network node 16 included in a Third Generation Partnership Project (3GPP) network (e.g., network 14). The first network node 16 is configured to communicate with a first device 24 behind a UE 22. One or more blocks described herein may be performed by one or more elements of the first network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to receive (Block S102) from the UE 22 via a second network node 16 a Non-Access Stratum (NAS) registration request message to register the first device 24 behind the UE 22. The UE 22 uses a wireline connection 100 to communicate with the second network node 16. The registration request message includes an indication indicating that the registration is for the first device 24. The first network node 16 is further configured to obtain (Block S104) subscription data indicating whether the first device 24 is allowed connectivity to the 3GPP network and determine (Block S106) whether to accept or reject the NAS registration request message of the first device 24 behind the UE 22 based on the obtained subscription data. In some embodiments, the UE 22 is a residential gateway. In some other embodiments, the residential gateway is a Fifth Generation (5G) residential gateway. In some other embodiments, the method further includes, if the subscription data indicates the first device 24 is allowed connectivity and the NAS registration request message is not received from the UE 22 via the wireline connection 100, rejecting the NAS registration request message. The wireline connection 100 is configured to provide a wired signal path for communication between the UE 22 and the second network node 16. In some embodiments, the method further includes, if the subscription data further indicates a residential gateway level wireline access characteristics (RG-LWAC) parameter and the NAS registration request message is received from the UE 22 via the wireline connection 100, accepting the NAS registration request message. In some other embodiments, the method further includes, if the NAS registration request message includes a first device type indication for the first device 24, the subscription data indicates the first device 24 is allowed connectivity, and the NAS registration request message is received via the wireline connection 100, accepting the NAS registration request message. In some embodiments, the method further includes, if the NAS registration request message includes a second device type indication for the UE and the NAS registration request message is received via the wireline connection 100, accepting the NAS registration request message. In some other embodiments, one or more of: (A) the first device 24 is an authenticable non-3GPP device (AUN3) device; (B) the first network node 16 comprises an access and mobility function (AMF); (C) the first network node 16 is configured to communicate with the UE 22 via the second network node 16; and (D) the second network node 16 comprises wireline access gateway function (W-AGF). Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for determining network access. In embodiments of this disclosure, a parameter to indicate that the AUN3 device connectivity (i.e., device 24 configured as an AUN3 device) is allowed for the subscription, e.g., an “AUN3 device connectivity allowed” parameter is added to the subscription data of the AUN3 devices, as shown in Table 1. Table 1. - Example wireline access specific UE subscription data types. In some embodiments, Table 1 may include some of the features of 3GPP TS 23.316 v18.2.0 Table 8.1.1.1-1 and further include the “AUN3 device connectivity allowed” parameter described in the present disclosure. In some embodiments, a first NN 16 (e.g., AMF) should only allow registrations via wireline access if the Registration Request corresponds to a UE 22 (e.g., an RG) registering, or a device 24 (e.g., an AUN3 device) registering. One or more embodiments of the present disclosure are related to how to handle network access of devices 24 (e.g., AUN3 devices). In some other embodiments, a NN 16 (e.g., AMF) ensures that the UE 22 (e.g., the RG) is allowed to register via wireline access (e.g., via connection 100c or any other wired connection). In some embodiments, there are two options for how the NN 16 (e.g., AMF) can know that it is the UE 22 (e.g., an RG) registering: - Alternative 1: The first NN 16 (e.g., AMF) checks if the subscription data contains an RG Level Wireline Access Characteristics (RG_LWAC) parameter. In some embodiments, this is an existing parameter in the subscription data that was added in 3GPP Release 16 to contain, e.g., quality of service (QoS) parameters for RGs using wireline access. In Alternative 1, this parameter is used as an indication that the corresponding registration request is for an RG. - Alternative 2: a NN 16 (e.g., the W-AGF) provides a “device type” indication together with the Registration Request. This “device type” indication can indicate whether the request is for a device 24 (e.g., an AUN3 device) or not. The W-AGF receives the device indication from the UE 22 (e.g., RG), based on the existing specifications. Alternatives 1 and 2 are described below in further detail. In some embodiments, e.g., in alternative 2, the UE 22 (e.g., RG)may need to be trusted to provide a correct device type indication. The UE 22 (e.g., RG) is an entity typically deployed in the home and may be comparable to a wireless device. Alternative 1 After obtaining the subscription data from a UDM, the NN 16 (e.g., AMF) checks if there exist an indication that the subscription belongs to device 24 (an AUN3 device) or not. The first NN 16 may use this information for accepting or rejecting the request as follows: If first NN 16 (e.g., AMF) receives a registration request via wireline access (i.e., from an AGF), then: - If subscription data contains “RG Level Wireline Access Characteristics (RG_LWAC)”, then NN 16 (e.g., AMF) can accept the request (e.g., it should be an RG); - If subscription data contains “AUN3 device connectivity allowed”, then NN 16 (e.g., AMF) can accept (it should a device that is allowed to access as AUN3 device); - Else, the NN 16 (e.g., AMF) rejects the request. If NN 16 (e.g., AMF) receives a registration request via 3GPP access (e.g., gNB) or some other non-3GPP access (Non-3GPP access InterWorking Function (N3IWF), Trusted Non-3GPP Gateway Function (NGF)): - If subscription data contains “AUN3 device connectivity allowed”, then NN 16 (e.g., AMF) rejects the request; - Else, NN 16 (e.g., AMF) can accept the request. The above steps ensure that only subscriptions explicitly marked for being used via wireline access (RGs and AUN3 devices) are accepted in wireline access. The registration procedure for the devices 24 (e.g., AUN3 devices) connected to the UE 22 (e.g., 5G-RG) via wireline access is shown as in FIG. 6. Network nodes 16a, 16b, 16c (not shown) may be configured as access nodes providing 3GPP network access. Network nodes 16d, 16e, 16f, 16g are shown and may be configured to perform one or more steps associated with providing / rejecting network access to device 24, e.g., via wireline access, non-3GPP access, etc. At step S200, device 24 (5G-RG) registration with 5GC is performed. Any AUN3 connection request is rejected until device 24 registration (5G-RG registration) is completed. At step S202, a connection of device 24 (e.g., AUN 3) with UE 22 (5G-RG) is established. At step S204, NAS registration request including AN parameters is transmitted from UE 22. At step S206, NN 16d (W-AGF) selects NN 16e (an AMF) and sends an N2 message including NAS registration request) at step S206a. At step S208, NN 16e performs AUSF selection. At step S210, device 24 (AUN3 device) is authenticated, and at step S212, NN 16e gets AUN3 subscription data and registers device 24 (AUN3 device) onto NN 16g (UDM). At step S214, NN 16e (AMF) ensures that the subscription belongs to an AUN3 device (i.e., device 24). At step S216, NN 16e may accept the registration request, e.g., if the subscription data has an indication that the device 24 is allowed to access the network as an AUN3 device). At step S218, a registration complete message is sent. At step S220, PDU session is established, e.g., per 3GPP TS 23.316 v18.2.0, clause 7.3.1. The registration procedure for devices connecting to non-wireline access is shown in FIG. 7. At step S300, UE 22 sends a registration request, e.g., to an access node such as NN 16a (or any one of NNs 16b, 16c). At step S302, NN 16a selects NN 16e (AMF). At step S304, NN 16a sends the registration request to NN 16e . At step S306, a request is sent requesting UE content information, and a response is received at step S308. At step S310, an identity request is sent, and at step S312, an identity response is received at NN 16e. At step S314, NN 16e selects NN 16i(AUSF). At step S316, authentication / security steps are performed. At step S318, a registration status update is sent. At step S320, an identity request and / or response is transmitted. At step S322, an identity check is performed. At step S324, NN 16j is selected by NN 16e. At step S326a Nudm_UECM_registration is transmitted, at step S326b, Nudm_SDM_get is received at NN 16e, and at step S326c, Nudm_SDM_Subscribe is transmitted by NN 16e. At step S326d a deregistration notification is received by NN 16g, and at step S326e, an unsubscribe request is sent. At step S328, PCF selection is performed. At step S330, a policy association, establishment, or modification is performed. At step S332, SM content is updated and released. At step S334, UE context modification is requested, and at step S336, a response with respect to the request of step S334 is received. At step S336a, Nudm_UECM_Registration is sent, at step S336b, a deregistration notification is received, and at step S336c a Nudm_SDM_Unsubscribe is sent. At step S338, NN 16e checks AU3 access, where NN 16e (AMF) accepts the registration request if the “AUN3 device connectivity allowed” parameter is missing from subscription data, or it indicates that the subscriber cannot connect as AUN3 device. At step S340, registration is accepted, at step S340a, a UE policy association may be established, and at step S342, the registration may be indicated as complete. At step S344 Nudm_SDM_info may be sent and received. At step S344a, an N2 message may be sent. At step S346, a Nudm_UECM_update request and response may be transmitted and received, respectively. At step S348, network slice specific authentication and authorization may be performed. Alternative 2 After obtaining the subscription data from UDM the NN 16 (e.g. AMF) checks if there exist an indication that the subscription belongs to an AUN3 device or not and uses this information for accepting or rejecting the request as follows: If the NN 16 (e.g. AMF) receives a registration request via wireline access (i.e., from an AGF), then: - If the registration request is accompanied with a device type indication for the UE 22 (e.g., an RG), then NN 16 (e.g. AMF) can accept the request (e.g. it should be an RG); - If the registration request is accompanied with a device type indication for an AUN3 device, and if subscription data contains “AUN3 device connectivity allowed”, then NN 16 (e.g. AMF) can accept (e.g., it should a device that is allowed to access as AUN3 device); - Else, the NN 16 (e.g. AMF) rejects the request. If the NN 16 (e.g. AMF) receives a registration request via 3GPP access (e.g., an gNB) or some other non-3GPP access (e.g., N3IWF, trusted NGF (TNGF), etc.) - If subscription data contains “AUN3 device connectivity allowed”, then the NN 16 (e.g. AMF) rejects the request; - Else, the NN 16 (e.g. AMF) can accept the request. In some embodiments, the above steps ensure that only subscriptions explicitly marked for being used via wireline access (AUN3 devices), or where the RG / W-AGF indicates that the registration is for an RG, are accepted in wireline access. The registration procedure for the AUN3 devices connected to the 5G-RG via wireline access is shown in FIG. 8. At step S400, 5G-RG registration with 5GC is performed. Any AUN3 connection request is rejected until 5G-RG registration is completed. At step S402, a connection of device 24 (e.g., AUN 3) with UE 22 (5G-RG) is established. At step S404, NAS registration request including AN parameters and device type is transmitted from UE 22. At step S406, NN 16d (W-AGF) selects NN 16e (an AMF) and sends an N2 message including NAS registration request and device type, at step S406a. At step S408, NN 16e performs AUSF selection. At step S410, device 24 (AUN3 device is authenticated), and at step S412, NN 16e gets AUN3 subscription data and registers device 24 (AUN3 device) onto NN 16g (UDM). At step S414, NN 16e (AMF) ensures that the subscription belongs to an AUN3 device. NN 16e accepts the registration request if the subscription data has an indication that the device 24 is allowed to access as an AUN3 device, or if the RG / W-AGF (i.e., NN 16d) indicated that the Registration Request is for an RG (i.e., UE 22). At step S416, registration is accepted, and at step S418, a registration complete message is sent. At step S420, PDU session is established. In some embodiments, the registration procedure for devices connecting to non- wireline access in Alternative 2 is the same as in Alternative 1. Embodiment A1. A first network node configured to communicate with a second network node and / or a wireless device (UE), the first network node configured to, and / or comprising a radio interface and / or communication interface and / or comprising processing circuitry configured to: determine whether to accept or reject a registration request based on whether: subscription data associated with one or both of the UE and the second network node comprises one or both of: a Residential Gateway Level Wireline Access Characteristics (RG- LWAC) parameter; and a subscription data type parameter indicating whether a subscriber is allowed network access as a first type of UE; and / or the registration request includes one or both of: a first indication indicating a second type of the second network node; and a second indication indicating the first type of the UE. Embodiment A2. The first network node of Embodiment A1, wherein, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes: when the subscription data includes the RG-LWAC parameter and / or the subscription data type parameter indicating the subscriber is allowed network access as the first type of the UE, accepting the registration request; and else, rejecting the registration request. Embodiment A3. The first network node of any one of Embodiments A1 and A2, wherein, when the registration request is received via a network node providing a Third Generation Partnership Project (3GPP) access or another node proving a predetermined non-3GPP access, determining whether to accept or reject the registration request includes: when the subscription data includes the subscription data type parameter indicating the subscriber is allowed network access as the first type of the UE, rejecting the registration request; and else, accepting the registration request. Embodiment A4. The first network node of any one of Embodiments A1-A3, wherein, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes: when the registration request includes the first indication indicating the second type of the second network node and / or the second indication indicating the first type of UE, accepting the registration request; and else, rejecting the registration request. Embodiment A5. The first network node of any one of Embodiments A1-A4, wherein the UE is an Authenticable Non-3GPP device (AUN3) device, the subscription data type parameter includes an “AUN3 device connectivity allowed” field indicating whether the subscriber is allowed network access as the AUN3 device. Embodiment A6. The first network node of any one of Embodiments A1-A5, wherein one or both of: the first network node comprises an access and mobility function (AMF); and the second network node comprises a residential gateway (RG). Embodiment B1. A method in a first network node configured to communicate with a second network node and / or a wireless device (UE), the method comprising: determining whether to accept or reject a registration request based on whether: subscription data associated with one or both of the UE and the second network node comprises one or both of: a Residential Gateway Level Wireline Access Characteristics (RG- LWAC) parameter; and a subscription data type parameter indicating whether a subscriber is allowed network access as a first type of UE; and / or the registration request includes one or both of: a first indication indicating a second type of the second network node; and a second indication indicating the first type of the UE. Embodiment B2. The method of Embodiment B1, wherein, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes: when the subscription data includes the RG-LWAC parameter and / or the subscription data type parameter indicating the subscriber is allowed network access as the first type of the UE, accepting the registration request; and else, rejecting the registration request. Embodiment B3. The method of any one of Embodiments B1 and B2, wherein, when the registration request is received via a network node providing a Third Generation Partnership Project (3GPP) access or another node proving a predetermined non-3GPP access, determining whether to accept or reject the registration request includes: when the subscription data includes the subscription data type parameter indicating the subscriber is allowed network access as the first type of the UE, rejecting the registration request; and else, accepting the registration request. Embodiment B4. The method of any one of Embodiments B1-B3, wherein, when the registration request is received via a network node providing wireline access, determining whether to accept or reject the registration request includes: when the registration request includes the first indication indicating the second type of the second network node and / or the second indication indicating the first type of UE, accepting the registration request; and else, rejecting the registration request. Embodiment B5. The method of any one of Embodiments B1-B4, wherein the UE is an Authenticable Non-3GPP device (AUN3) device, the subscription data type parameter includes an “AUN3 device connectivity allowed” field indicating whether the subscriber is allowed network access as the AUN3 device. Embodiment B6. The method of any one of Embodiments B1-B5, wherein one or both of: the first network node comprises an access and mobility function (AMF); and the second network node comprises a residential gateway (RG). Embodiment C1. A wireless device (UE) configured to communicate with a first network node and / or a second network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to perform one or more functions corresponding to any one of Embodiments A1-A6. Embodiment D1. A method implemented in a wireless device (UE) configured to communicate with a first network node and / or a second network node, the method comprising one or more steps corresponding to Embodiments B1-B6. Embodiment E1. A second network node configured to communicate with a first network node and / or a wireless device (UE), the second network node configured to, and / or comprising a radio interface and / or communication interface and / or processing circuitry configured to perform one or more functions corresponding to any one of Embodiments A1-A6. Embodiment F1. A method implemented in a second network node configured to communicate with a first network node and / or a wireless device (UE), the method comprising one or more steps corresponding to Embodiments B1-B6. Enclosed herein is a proposed change to the 3GPP standard TS 23.316 based on the one or more embodiments described herein: 3GPP TSG-WG SA2 Meeting #158 S2-2308256 Gothenburg, Sweden, Aug 21 – 25, 2023 For HELP on using this form: comprehensive instructions can be found at http: / / www.3gpp.org / Change-Requests. UICC apps ME X Radio Access Network Core Network X * * * First Change * * * * 4.10c Authenticable Non-3GPP devices behind 5G-RG This clause defines the support of AUN3 devices, i.e. Authenticable Non-3GPP devices (AUN3) as defined in clause 3.1, behind a 5G-RG. This clause applies only to 5G- RG connected via wireline access. FIG. 2 of the present disclosure (i.e., Figure 4.10c-1 of 3GPP standard TS 23.316) shows the architecture for support of AUN3 device (behind 5G-RG). Differentiated services for AUN3 devices behind 5G-RG are provided as specified below: - Each AUN3 device has its own UDM / UDR subscription data including its own SUPI and policy control subscription data. - The interface between 5G-RG and AUN3 devices is out of scope of 3GPP. - In order to serve the AUN3 device in 5GC, a 5G-RG issues a NAS register and handles RM and CM related signalling on behalf of an AUN3 device that it is requesting to be served and relays EAP signalling between the AUN3 device and the 5GC. - A 5G-RG serving an AUN3 device establishes a single PDU Session on behalf on this AUN3 device. - The AMF and the 5G-RG maintain a separate NAS connection per AUN3 device. This includes maintaining a GUTI and NAS (RM, CM, security, etc.) context per AUN3 device. - A 5G-RG may be connected to the 5GC (be in RM-REGISTERED and CM-CONNECTED mode) over Wireline access to serve an AUN3 device: the 5G-RG may not issue a NAS register or service request on behalf of an AUN3 device if it is itself not registered and connected to the 5GC. - The 5G-RG is configured with URSP for each AUN3 devices it serves. The UE PCF selected by the AMF at the registration of an AUN3 device sends this URSP to 5G-RG via the AMF and the NAS connection of the AUN3 device. - The AUN3 devices and the 5G-RG belong to the same PLMN. - A 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S- NSSAI and the AMF selects the default S-NSSAI in the subscription of the AUN3 device. - There may be a separate N2 connection per AUN3 device that is in state CM-CONNECTED. - The W-CP and W-UP protocols may be able to manage multiple separate Registrations and PDU Sessions for different SUPIs between the same pair of 5G-RG and W-AGF. In particular, W-CP needs to be able to differentiate NAS messages related to a 5G-RG and to each different AUN3 device served by this 5G-RG and W-UP needs to distinguish between user plane packets for a 5G-RG and each different AUN3 device served by this 5G-RG. - When the registration of an AUN3 device has successfully completed, the 5G-RG establishes a PDU Session on behalf of the AUN3 device. This PDU Session is handled by 5GC as part of the AUN3 subscription and is associated with the SUPI of AUN3 device. An AUN3 device can at a given time only use a single PDU Session. The parameters to establish this PDU session are based on the URSP (if any) for the AUN3 device. - Different QoS parameters may apply to PDU sessions of different AUN3 devices. - Roaming is not applicable to subscriptions for AUN3 devices. - The PCF is able to control the aggregate traffic of all the PDU Sessions that are using a wireline access to ensure that the sum of the session AMBR of these PDU Sessions remains below the Maximum Line / Cable BR, using either of the two following options o The PCF may use the Remaining Line / Cable BR parameter, which is stored in UDR and can be accessed and updated using a Line / Cable ID. The Remaining Line / Cable BR indicates the amount of bandwidth of a line that is free to use at each instance. o The PCF may subscribe to NWDAF to get the data dispersion analytics for the Line / Cable ID and apply policies to ensure that the aggregated traffic traversing the Line / Cable be less than a maximum value. * * * * Second change * * * * 7.2.8.1 AUN3 device Registration via W-5GAN An authenticable non-3GPP devices (AUN3) may get connected behind 5G-RG as defined in clause 4.10c. This clause specifies how an AUN3 device can be registered via 5G-RG. The following steps correspond to FIG. 6 of the present disclosure (Figure 7.2.8.1- 1: 5GC registration of AUN3 device), where steps 1-10 generally correspond to S200- S220, respectively. 1. The 5G-RG registers to 5GC as specified in clause 7.2.1.1: Any AUN3 device connection request prior to step 1 may be rejected by the 5G-RG. 2. The AUN3 device connects to the 5G-RG via non-3GPP access network (e.g., WLAN). The realm of the NAI used by AUN3 device to contact the 5G-RG may be used as a trigger for 5G-RG to apply procedures for AUN3 devices. An authentication procedure is triggered. This can be done either by AUN3 device sending an EAPOL-start frame to the 5G-RG or 5G-RG receives a frame from an unknown MAC address. The 5G- RG receives a permanent identifier from the AUN3 device (e.g. an NAI in form of username@realm). If the realm part is different from the realm associated with the PLMN that the 5G-RG belongs to, the 5G-RG stops performing following procedure and reject the AUN3 device. NOTE: How the 5G-RG is triggered to apply procedures for AUN3 devices is defined by BBF and / or CableLabs. 3. This may be same as step 3 of 7.2.1.1-1 with the following addition: - W-CP AN parameters may contain an indicator that the W-CP connection is for an AUN3 device; - The 5G-RG always provides a SUCI as AUN3 device identity information in the registration request and constructs the SUCI from the NAI received within EAP- Identity issued by the AUN3 device as defined in TS 33.501

[0011] ; - The 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S- NSSAI; and - When W-AGF provides (over N2) ULI to be associated with an AUN3 device, if the AUN3 device is connected behind a 5G-BRG, the W-AGF builds the AUN3's ULI using the ULI of the 5G-BRG connecting the AUN3 device. If AUN3 device is connected behind the 5G-CRG, the W-AGF builds the ULI using the ULI of the 5G- CRG connecting the AUN3 device. 4. The W-AGF selects an AMF based on the received AN parameter provided by the 5G-RG and based on local policy, as specified in clause 6.3.5 of TS 23.501 [2]. The W-AGF sends an NGAP INITIAL UE message to the selected AMF. The W-AGF indicates to AMF if there is an existing 5G-RG N2 connected to the same line (that the initial NAS message is received). 5. AMF selects AUSF as specified in clause 6.3.4 of TS 23.501 [2]. 6. The AUSF executes the authentication of the AUN3 device following TS 33.501

[0011] . The AUSF selects the UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data of the AUN3 device, from UDM. EAP based authentication defined in TS 33.501

[0011] is performed between the AUSF and the AUN3 device. Once the AUN3 device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF may return the SUPI corresponding to the AUN3 device to AMF only after the authentication is successful. 7. Same as step 8 to 12 of figure 7.2.1.1-1 with following modifications - The 5G RG uses the MAC address of the AUN3 device as a PEI; - If the W-AGF indicated in step 4 that there is no existing 5G-RG N2 connected to the same line / cable and it does not receive the RG-LWAC parameter from UDM (i.e. the device is not 5G-RG), then the AMF rejects the registration request and steps 9 onwards are skipped. Otherwise, the procedure continues in step 9. NOTE: It is assumed that only 5G-RG’s will be provisioned with RG- LWAC in its subscription data. The AMF can thus use this to determine whether the Registration Request is for a 5G-RG or AUN3 device. In case the W-AGF indicates that there is no existing 5G-RG N2 connected to the same line but the subscription data contains RG-LWAC, the AMF can accept the Registration Request. 8. The AMF sends the Registration Accept message related to the AUN3 device to the 5G-RG. This step is executed over the NAS signalling connection and the N2 connection related to the AUN3 device. 9. The 5G-RG sends the Registration Complete message related to the AUN3 device to the AMF, when the procedure is completed. This step is executed over NAS signalling connection and N2 connection related to the AUN3 device. The 5G-RG may store the 5G-GUTI of AUN3 device to be able to use it potential later NAS procedures related with the AUN3 device. 10. The 5G-RG receives the URSP corresponding to the AUN3 and continues by requesting the establishment of a PDU Session on behalf of the AUN3 device as specified in clause 7.3.1. * * * * Third change * * * * 7.3.8 Session Management Procedures for AUN3 devices 7.3.8.1 PDU Session Establishment of AUN3 device behind 5G-RG This clause specifies the PDU Session Establishment for an AUN3 device served by a 5G-RG as defined in clause 4.10c. A distinct PDU session is established for each AUN3 device. After the registration from the AUN3 device, the 5G-RG initiates the establishment of a PDU Session on behalf of the AUN3 device The PDU Session is established as specified in clause 7.3.1.1 with following differences: - Steps 1a, 1b and 2b are executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. - At step 3 in figure 4.3.2.2.1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session in the Nsmf_PDUSession_CreateSMContext Request sent to the SMF. - Steps 5 and 6 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. - - At step 7b in figure 4.3.2.2.1 [3] of TS 23.502 [3], the SMF sends in the Npcf_SMPolicyControl_Create Request the SUPI of the PDU session (i.e. the AUN3 SUPI) ), ULI containing the GLI or GCI, and the AUN3 Session AMBR. - The PCF may use the GLI or GCI to obtain the Remaining Line BR from either UDR or NWDAF and may reject the request if it is less than the Session AMBR. If the UDR option is used the PCF updates the Remaining Line BR parameter. 7.3.8.2 PDU Session Modification of AUN3 device behind 5G-RG This clause specifies the PDU Session Modification for an AUN3 device served by a 5G-RG as defined in clause 4.5.3. The PDU Session modification procedure may use clause 7.3.2 with following differences: - Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. - At step 1a in figure 4.3.3.2-1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session. - At step 2 in figure 4.3.3.2-1 of TS 23.502 [3], the SMF sends in the Npcf_SMPolicyControl_Update Request the SUPI of the PDU session (i.e. the AUN3 SUPI) and the ULI containing the GLI or GCI. The PCF may use the GLI or GCI to obtain the Remaining Line / Cabel BR from either UDR or NWDAF and use it in its policy decision. If the UDR option is used the PCF updates the Remaining Line BR parameter. - Steps 3 and 5 are executed over the AUN3 device's N2 connection. - Steps 7 and 8 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. - Only 5GC initiated PDU Session modification is supported in this Release 7.3.8.3 PDU Session Release of AUN3 device behind 5G-RG This clause specifies the PDU Session Release for an AUN3 device served by a 5G-RG as defined in clause 4.10c. This clause applies only to 5G-RG. AUN3 device may trigger explicit request for connection release, or it may be unreachable (on the 5G-RG to AUN3 device interface). In such scenarios 5G-RG may need to release the PDU session of the AUN3 device. NOTE: How an AUN3 device can trigger the release of a PDU Session is out of scope of 3GPP specifications. PDU session release for a specific AUN3 device can also be initiated by the 5GC (e.g., the subscription of the AUN3 device expires). The PDU Session release procedure is described in figure 7.3.3.y-1 FIG. 9 (i.e., Figure 7.3.x.3-1) shows PDU Session Release of AUN3 device behind 5GRG. Steps S500-S520 of FIG. 9 generally correspond to steps 0-10 of Figure 7.3.x.3-1, respectively. Steps 0-10 of Figure 7.3.x.3-1 are as follows: 0. The AUN3 device may disconnect from the 5G-RG 1. The 5G-RG sends the PDU Session Release message on the AUN3 device’s NAS connection 2. Step 3 to 10 from Figure 7.3.3.-1 is executed with following differences: - Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. In step 1a of figure 4.3.4.2-1 of TS 23.502 [3], the 5G-RG sends the PDU Session Release message on the AUN3 device's NAS connection. - Steps 4 and 6 are executed over the AUN3 device's N2 connection. - Steps 8-10 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. 1. Steps 10 to 13 from TS 23.502[3] Figure 4.3.4.2-1. 2. SMF sends in the Npcf_SMPolicyControl_Release Request the SUPI of the PDU session (i.e. the AUN3 SUPI), the PDU session ID, and the ULI containing the line ID. 3. The PCF may use the Line ID to update the Remaining Line BR in UDR. 4. The PCF sends SMPolicyControl_Update Response to the SMF 5. Steps 14 to 15 from TS 23.502[3] Figure 4.3.4.2-1 * * * * Fourth change * * * * 9.Y Policy control subscription information management The Line / Cabel ID specific policy control information is per GLI or GCI information stored by the UDR and updated by the PCF during PDU Session Establishment or Modification procedure using Nudr service for Data Set "Policy Data" and Data Subset "Line ID Specific Control Data" is described in Table 9.Y.Z-1: Table 9.Y.Z-1: Line specific policy control information * * * * Fifth change * * * * 8.1.1 Nudm_SubscriberDataManagement (SDM) Service 8.1.1.1 General In addition to the Subscription data types used in the Nudm_SubscriberDataManagement Service, as defined in Table 5.2.3.3.1-1 of TS 23.502 [3], the additional data types defined in Table 8.1.1.1-1 below are applicable for RGs connected to 5GC via W-5GAN and AUN3 devices. Table 8.1.1.1-1: Wireline access specific UE Subscription data types In the case of Wireline access, the Forbidden area information within Table 5.2.3.3.1-1 of TS 23.502 [3] may correspond to a (set of) allowed Global Line ID. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination. Abbreviations that may be used in the preceding description include: 5GC 5G Core 5GRG 5G residential gateway AMF Access & Mobility Management Function AUN3 Authenticable Non-3GPP devices AUSF Authentication Server Function RG-LWAC RG Level Wireline Access Characteristics SMF Session Management Function UDM Unified Data Management UDR Unified Data Repository UPF User Plane Function W-AGF Wireline Access Gateway Function It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings and the following claims.

Claims

What is claimed is:

1. A method implemented in a first network node (16) included in a Third Generation Partnership Project, 3GPP, network, the first network node (16) being configured to communicate with a first device (24) behind a user equipment, UE, (22) the method comprising: receiving (S102) from the UE (22) via a second network node (16) a Non-Access Stratum, NAS, registration request message to register the first device (24) behind the UE (22), the UE (22) using a wireline connection (100) to communicate with the second network node (16), the registration request message including an indication indicating that the registration is for the first device (24); obtaining (S104) subscription data indicating whether the first device (24) is allowed connectivity to the 3GPP network; and determining (S106) whether to accept or reject the NAS registration request message of the first device (24) behind the UE (22) based on the obtained subscription data.

2. The method of Claim 1, wherein the UE (22) is a residential gateway.

3. The method of Claim 2, wherein the residential gateway is a Fifth Generation, 5G, residential gateway.

4. The method of any one of Claims 1-3, wherein the method further includes: if the subscription data indicates the first device (24) is allowed connectivity and the NAS registration request message is not received from the UE (22) via the wireline connection (100), rejecting the NAS registration request message, the wireline connection (100) being configured to provide a wired signal path for communication between the UE (22) and the second network node (16).

5. The method of any one of Claims 1-4, wherein the method further includes: if the subscription data further indicates a residential gateway level wireline access characteristics, RG-LWAC, parameter and the NAS registration request message is received from the UE (22) via the wireline connection (100), accepting the NAS registration request message.

6. The method of any one of Claims 1-5, wherein the method further includes: if the NAS registration request message includes a first device type indication for the first device (24), the subscription data indicates the first device (24) is allowed connectivity, and the NAS registration request message is received via the wireline connection (100), accepting the NAS registration request message.

7. The method of any one of Claims 1-6, wherein the method further includes: if the NAS registration request message includes a second device type indication for the UE (22) and the NAS registration request message is received via the wireline connection (100), accepting the NAS registration request message.

8. The method of any one of Claims 1-7, wherein one or more of: the first device (24) is an authenticable non-3GPP device, AUN3, device; the first network node (16) comprises an access and mobility function, AMF; the first network node (16) is configured to communicate with the UE (22) via the second network node (16); and the second network node (16) comprises wireline access gateway function, W- AGF.

9. A first network node (16) in a Third Generation Partnership Project, 3GPP, network, the first network node (16) being configured to communicate with a first device (24) behind a user equipment, UE, (22) the first network node (16) being configured to perform the steps of any one of Claims 1-8.

10. A first network node (16) in a Third Generation Partnership Project, 3GPP, network, the first network node (16) being configured to communicate with a first device (24) behind a user equipment, UE, (22) the first network node (16) comprising processing circuitry (68) and a memory (72) comprising instructions which when executed by the processing circuitry (68) will perform the steps of any one of Claims 1-8.

Images