WO2020201207A1 - System information for wireline access - Google Patents

Abstract

There is currently no specified solution on how the information broadcasted by the NG-RAN node can be sent to 5G-RG over the Y4 interface and what of the RRC information that is relevant for wireline access. Certain aspects of the present disclosure, and their embodiments, may provide solutions to the aforementioned or other challenges.

Description

Title

SYSTEM INFORMATION FOR WIRELINE ACCESS

Technical field

[0001] The present disclosure relates to methods of communications systems, particularly to how information broadcasted by the NG-RAN node can be sent to 5G-RG over the Y4 interface.

Background

[0002] The present disclosure relates to methods of communications systems, particularly to how information broadcasted by the NG-RAN node can be sent to 5G- Residential Gateway (5G-RG) over the Y4 interface. For ease of understanding of the disclosure, below follows a general description of communications system architectures. Herein, communications systems are also referred to as wireless communication system.

[0003] Figure 1 illustrates a wireless communication system represented as a Fifth Generation (5G) network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface. Figure 1 can be viewed as one particular implementation of the system 400 of Figure 4.

[0004] Seen from the access side the 5G network architecture shown in Figure 1 comprises a plurality of User Equipment (UEs) connected to either a Radio Access Network (RAN) or an Access Network (AN) as well as an Access and Mobility Management Function (AMF). Typically, the R(AN) comprises base stations, e.g. such as evolved Node Bs (eNBs) or 5G base stations (gNBs) or similar. Seen from the core network side, the 5G core NFs shown in Figure 1 include a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), a Unified Data Management (UDM), an AMF, a Session Management Function (SMF), a Policy Control Function (PCF), and an Application Function (AF).

[0005] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE and AMF. The reference points for connecting between the AN and AMF and between the AN and User Plane Function (UPF) are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF and SMF, which implies that the SMF is at least partly controlled by the AMF. N4 is used by the SMF and UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its state to the SMF. N9 is the reference point for the connection between different UPFs, and N14 is the reference point connecting between different AMFs, respectively. N15 and N7 are defined since the PCF applies policy to the AMF and SMP, respectively. N12 is required for the AMF to perform authentication of the UE. N8 and N10 are defined because the subscription data of the UE is required for the AMF and SMF.

[0006] The 5G core network aims at separating user plane and control plane. The user plane carries user traffic while the control plane carries signaling in the network. In Figure 1, the UPF is in the user plane and all other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user and control planes guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from control plane functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0007] The core 5G network architecture is composed of modularized functions. For example, the AMF and SMF are independent functions in the control plane. Separated AMF and SMF allow independent evolution and scaling. Other control plane functions like the PCF and AUSF can be separated as shown in Figure 1. Modularized function design enables the 5G core network to support various services flexibly.

[0008] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the control plane, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0009] A Fifth Generation Core Network (5GC) is defined in 3GPP 23.501 and the system architecture is illustrated in Figure 2. Figure 2 illustrates a 5G network architecture using service-based interfaces between the NFs in the control plane, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 1. However, the NFs described above with reference to Figure 1 correspond to the NFs shown in Figure 2. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 2 the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g. Namf for the service based interface of the AMF and Nsmf for the service based interface of the SMF etc. The Network Exposure Function (NEF) and the Network Repository Function (NRF) in Figure 2 are not shown in Figure 1 discussed above. However, it should be clarified that all NFs depicted in Figure 1 can interact with the NEF and the NRF of Figure 2 as necessary, though not explicitly indicated in Figure 1.

[0010] Some properties of the NFs shown in Figures 1 and 2 may be described in the following manner. The AMF provides UE-based authentication, authorization, mobility management, etc. A UE even using multiple access technologies is basically connected to a single AMF because the AMF is independent of the access technologies. The SMF is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF for data transfer. If a UE has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF provides information on the packet flow to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies about mobility and session management to make the AMF and SMF operate properly. The AUSF supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM stores subscription data of the UE. The Data Network (DN), not part of the 5G core network, provides Internet access or operator services and similar.

[0011] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0012] The R(AN) box can be any type of access node and in release 15 the defined nodes are gNB (for 3GPP access) and N3IWF (for untrusted non-3GPP access). A general concept for 5GC is (23.501, section 4.1): [0013] "Minimize dependencies between the Access Network (AN) and the Core Network (CN). The architecture is defined with a converged core network with a common AN - CN interface which integrates different Access Types e.g. 3GPP access and non-3GPP access."

[0014] This means that the reference points between UE and AMF and between R(AN) should be access agnostic so that adding support for new accesses should not impact these interfaces. From experience working with release 15, some variances are allowed but that is typically limited to that some procedures are only applicable for certain accesses and that information elements might differ to some extent.

Problems with Existing Solutions

[0015] There currently exist certain challenges. There is currently no specified solution on how the information broadcasted by the NG-RAN node can be sent to 5G-RG over the Y4 interface and what of the RRC information that is relevant for wireline access.

Brief Summary of Some Aspects of the Proposed Solutions

[0016] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. In 3GPP release 16 it will probably be possible to do a limited solution which does not require the broadcasted RRC information but:

1. In some embodiments, additional features for wireline access rely on Y4 extensions.

2. In some embodiments, Y4 can be enhanced to send similar information as is broadcasted in RRC. Also, some examples of what broadcasted information in RRC that could be applicable/useful for wireline access are provided.

[0017] The information relevant to 5G-RG could be any combination of the following:

• PLMN identity list: PLMNs supported by the NG-RAN node.

• Location information: This could be the line-id of the wireline access. Corresponds to cell and tracking area information for 3GPP access. • Barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason (e.g., overload).

• Non-public network identities: If the wireline access network belong to a non-public network (feature added for 3GPP access in release 16) .

• Indication for support of emergency services: If network supports emergency services.

• IoT parameters: E.g., if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that.

• TS 23.502 already requires N3IWF to allocate signalling IPsec Service and Systems Aspects (SA) solely for NAS signalling and to allocate separate IPsec Child SA for QoS flow of the PLMN based on Primary Common Control (PCC) rules from the PCF.

• Network indication indicating support of access to RLOS (Restricted Local Operator Services).

[0018] For a 5G-RG to start using the services of 5GC it is required that the 5G-RG registers to the network. This procedure is described in 23.502 for 3GPP access and untrusted non-3GPP access. The registration procedure will be similar for fixed access and 5G-RG will need to authenticate itself to the 5GC network using Subscriber Identity Module (SIM) (or other e.g., Public Key Infrastructure certificate) credentials. To be able to do the registration procedure there should be a transport protocol between 5G-RG and AGF i.e., the Y4 interface and what protocols to use on this interface is not agreed yet.

[0019] Therefore, in some embodiments disclosed herein, similar System Information is provided to 5G-RG as is being provided to UE over 3GPP access (e.g., PLMN identity list, location info, etc.).

[0020] There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. In some embodiments, a method performed by a wireline device for receiving network information includes receiving network information that is similar to information as is broadcasted in RRC; and using the network information.

[0021] In some embodiments, the wireline device is a 5G-Residential Gateway (5G-RG).

[0022] In some embodiments, receiving the network information comprises receiving the network information during the setup of the W-CP connection.

[0023] In some embodiments, receiving the network information comprises receiving the network information in an Extensible Authentication Protocol (EAP)-Request/5G-Start packet.

[0024] In some embodiments, receiving the network information comprises receiving the network information in the first IKE_AUTH response as an IKEv2 notify payload.

[0025] In some embodiments, receiving the network information comprises fetching the network information from a DNS server available in/via the local IP network using some particular Fully Qualified Domain Name (FQDN). In some embodiments, Domain Name System Security Extensions (DNSSECs) are used to secure the fetching.

[0026] In some embodiments, receiving the network information comprises receiving the network information included as parameters in the Point to Point Protocol over Ethernet (PPPoE) Active Discovery Offer (PADO) message.

[0027] In some embodiments, receiving the network information comprises receiving the network information over a second "Wireline access Control Protocol" (W-CP) that can be used to carry NAS and AS parameters.

[0028] In some embodiments, the network information comprises one or more of: PLMN identity list: PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason (e.g., overload); non-public network identities: If the wireline access network belong to a non^¬ public network; indication for support of emergency services: If network supports emergency services; IoT parameters: e.g., if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; TS 23.502 already requires N3IWF to allocate signalling IPsec SA solely for NAS signalling and to allocate separate IPsec Child SA for QoS flow of the PLMN based on PCC rules from the PCF; network indication indicating support of access to RLOS (Restricted Local Operator Services). [0029] Accordingly, some embodiments disclosed herein refer to: a method performed by a wireline device for receiving network information, the method comprising: a method performed by a wireline device for receiving network information, the method comprising:

- receiving network information comprising one or more of: PLMN identity list; PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non-public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services, and

- using the network information.

[0030] Some embodiments disclosed herein refer to: a method performed by a network node such as a base station for transmitting network information, the method comprising:

- transmitting, to a wireline device, network information comprising one or more of: PLMN identity list; PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non^¬ public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services.

[0031] Yet further embodiments of the disclosure refer to a wireline device configured to perform the abovementioned method performed by a wireline device, and to a network node configured to perform the abovementioned method performed by a network node.

[0032] Certain embodiments may provide one or more of the following technical advantage(s): Provides the same architectural capabilities for wireline access as for 3GPP access which can be used for many future features/capabilities. Brief description of the drawings

Figure 1 illustrates a wireless communication system,

Figure 2 illustrates a 5G network architecture using service-based interfaces between the NFs in the control plane,

Figure 3 shows the general architecture for a scenario of adding support for fixed access in 5GC,

Figure 4 illustrates one example of a cellular communications network,

Figure 5A and 5B (divided on two pages) illustrates a procedure for 5G-RG registration via W-5GAN according to embodiments of the disclosure,

Figure 6 illustrates; Option 2, Solution 1: System Information (SI) is included in the EAP- Request/5G-Start as "AN parameters" (AN=access network),

Figure 7 illustrates; Option 2, Solution 2: System Information (SI) is included in the first IKE_AUTFI response as an IKEv2 notify payload,

Figure 8 illustrates; Option 1, solution 1 : System Information (SI) is included as parameters in the PPPoE Active Discovery Offer (PADO) message (second arrow from the top) from AGF (W-AGF) to 5G-RG,

Figure 9 is a schematic block diagram of a radio access node,

Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node,

Figure 11 is a schematic block diagram of the radio access node according to some other embodiments of the present disclosure,

Figure 12 is a schematic block diagram of a UE,

Figure 13 is a schematic block diagram of the UE according to some other embodiments of the present disclosure,

Figure 14 is a communication system includes a telecommunication network, in accordance with an embodiment,

Figure 15 is example implementations, in accordance with an embodiment, of the UE, base station, and host computer

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment, Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment,

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment, and

Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

[0033] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Radio Node: As used herein, a "radio node" is either a radio access node or a wireless device.

[0034] Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a radio access network of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

[0035] Core Network Node: As used herein, a "core network node" is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

[0036] Wireless Device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

[0037] Network Node: As used herein, a "network node" is any node that is either part of the radio access network or the core network of a cellular communications network/system.

[0038] Thus, according to embodiments a network node may be a node of a radio access network, i.e. any one of the Radio Access Nodes previously defined, such as for example a Next Generation Radio Access Network node (NG-RAN node). According to embodiments a wireline device may be a 5G-Residential Gateway (5G-RG).

[0039] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0040] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0041] 3GPP and BroadBand Forum (BBF) is currently working on adding support for fixed access in 5GC. Figure 3 shows the general architecture for that scenario.

[0042] Figure 3 will be added to 23.501 as Figure 4.2.8.4-1. The 5G-Residential Gateway (5G-RG) can be connected to 5GC via Wireline 5G Access Network (W-5GAN), Next Generation RAN (NG RAN) or via both accesses. The reference architecture in Figure 3 only shows the architecture and the network functions directly connected to Wireline 5G Access Network, and other parts of the architecture are the same as defined in clause 4.2. The reference architecture in Figure 3 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. The two N2 instances in Figure 3 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network. The two N3 instances in Figure 3 may apply to different UPFs when different PDU Sessions are established over 3GPP access and Wireline 5G Access Network.

[0043] It has also been agreed to add in 23.501:

"Y4 Reference point between the 5G-RG and the Wireline-Access Gateway Function (W-AGF) which transports the user plane traffic and the N1 Non Access Stratum (NAS) protocol. The definition of this interface is outside the scope of 3GPP."

[0044] 6.2.x W-AGF - The functionality of W-AGF is specified in TS 23.316, and in 23.316 which is the specification for wireline access:

[0045] Wireline access Control Plane protocol (W-CP): Protocol used to transport Access Stratum (AS) and NAS signalling between the 5G-RG and the W-AGF over the Y4 reference point. W-CP is specified by BBF and CableLabs. There is no assumption that W-CP refers to only a single protocol or only a specific protocol layer.

[0046] 5.1.1 W-AGF

The functionality of W-AGF in the case of Wireline 5G Access network includes the following:

1. - Termination of N2 and N3 interfaces to 5G Core Network for control - plane and user- plane respectively.

2. - Handling of N2 signalling from SMF (relayed by AMF) related to PDU Sessions and QoS.

3. - Relaying uplink and downlink user-plane packets between the 5G-RG and UPF and between a Fixed Network RG (FN-RG) and UPF. This involves:

- Enforcing QoS corresponding to N3 packet marking, taking into account QoS requirements associated to such marking received over N2

- N3 user-plane packet marking in the uplink.

4. - Supporting AMF selection.

5. - Termination of wireline access protocol on Y4 and Y5.

6. - In case of FN-RG the W-AGF acts as end point of N1 on behalf of the FN-RG. [0047] In case of Wireline 5G Broadband Access network the definition of W-AGF functionalities is specified in WT-456 and WT-457. In case of Wireline 5G Cable Access network the definition of W-AGF functionalities is specified by CableLabs.

[0048] The main difference between Figure 2 and Figure 3 is that the UE is replaced with a 5G-Residential Gateway (5G-RG) and that the R(AN) node is called Wireline Access Gateway Function (W-AGF). The 5G-RG is using a wireline access network (cable, fiber, xDSL) to connect to the W-AGF. The 5G-RG is an adapted residential gateway that includes support for N1 (NAS) signaling with the 5GC so there is a direct N1 interface between 5G- RG and AMF. These messages will be carried first between 5G-RG and W-AGF and then relayed over N2.

[0049] For a 5G-RG to start using the services of 5GC it's required that the 5G-RG registers to the network. This procedure is described in 23.502 for 3GPP access and untrusted non- 3GPP access. The registration procedure will be similar for fixed access and 5G-RG will need to authenticate itself to the 5GC network using Subscriber Identity Module (SIM) (or other e.g., Public Key Infrastructure certificate) credentials. To be able to do the registration procedure there should be a transport protocol between 5G-RG and AGF i.e., the Y4 interface and what protocols to use on this interface is not agreed yet.

[0050] For 3GPP accesses (e.g., New Radio (NR), Evolved Universal Terrestrial Radio Access Network (E-UTRAN)) the interface between UE and NG-RAN node (e.g., eNB, gNB) is implemented with a stack of protocols and all are defined within 3GPP organization. To transport NAS messages, the Radio Resource Control protocol (RRC) is used (3GPP TS 38.300 and 36.331). On top of the capability to carry NAS message, NAS also implements other capabilities and one of these is to the broadcast of System Information related to AS and NAS. Examples of broadcasted information are a Public Land Mobile Network (PLMN) identity list (PLMNs supported by the NG-RAN node), cell-id, barring information, non-public network identities, indication for support of emergency services and Internet of Things (IoT) parameters. The UE use the broadcasted information for various features and one important feature is for the UE to be able to do PLMN/network selection.

[0051] Figure 4 illustrates one example of a cellular communications network 400 according to some embodiments of the present disclosure. In the embodiments described herein, the cellular communications network 400 is a 5G NR network. In this example, the cellular communications network 400 includes base stations 402-1 and 402-2, which in LTE are referred to as eNBs and in 5G NR are referred to as gNBs, controlling corresponding macro cells 404-1 and 404-2. The base stations 402-1 and 402-2 are generally referred to herein collectively as base stations 402 and individually as base station 402. Likewise, the macro cells 404-1 and 404-2 are generally referred to herein collectively as macro cells 404 and individually as macro cell 404. The cellular communications network 400 may also include a number of low power nodes 406-1 through 406-4 controlling corresponding small cells 408-1 through 408-4. The low power nodes 406-1 through 406-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 408-1 through 408-4 may alternatively be provided by the base stations 402. The low power nodes 406-1 through 406-4 are generally referred to herein collectively as low power nodes 406 and individually as low power node 406. Likewise, the small cells 408-1 through 408-4 are generally referred to herein collectively as small cells 408 and individually as small cell 408. The base stations 402 (and optionally the low power nodes 406) are connected to a core network 410.

[0052] The base stations 402 and the low power nodes 406 provide service to wireless devices 412-1 through 412-5 in the corresponding cells 404 and 408. The wireless devices 412-1 through 412-5 are generally referred to herein collectively as wireless devices 412 and individually as wireless device 412. The wireless devices 412 are also sometimes referred to herein as UEs.

[0053] For clarity reasons, figure 5, showing a signalling diagram, is divided in two parts, wherein the upper part of the signalling diagram is shown on figure 5A (1/2) and the bottom part of the signalling diagram is shown on figure 5B (2/). Figure 5A and 5B are herein simply referred to as figure 5.

[0054] Figure 5 illustrates a procedure for 5G-RG registration via W-5GAN according to embodiments of the disclosure. 1. The 5G-RG connects to a W-5GAN with procedures outside the scope of 3GPP and creates an initial not authenticated W-CP EAP connection. This connection shall support EAP messages transfer between 5G-RG and W-AGF. Option 1: During this setup of the W-CP connection, the 5G-RG receives system information related to AS and NAS.

2. The W-AGF sends an EAP-Request/5G-Start packet over the W-CP connection. The EAP-Request/5G-Start packet informs the 5G-RG to initiate an EAP-5G session, i.e. to start sending NAS messages encapsulated within EAP-5G packets. Option 2: The EAP- Request/5G-Start packet includes system information related to AS and NAS. In some embodiments, this step depends on a decision for what protocols to use for NAS transport.

3. The 5G-RG sends an EAP-Response/5G-NAS packet that contains the Access Network parameters (SUCI or 5G-GUTI, the selected PLMN, Requested NSSAI and Establishment Cause) and a NAS Registration Request message (SUCI or 5G-GUTI, last visited TAI, security parameters/UE security capability, NSSAI parameters, UE MM Core Network Capability, PDU session status, Follow-on request). The Establishment cause provides the reason for requesting a signalling connection with 5GC. Option 1 & 2: The selected PLMN parameter is the output of the 5G-RG PLMN selection algorithm. In release 16 this algorithm will be very primitive and just use the home PLMN of the SIM card. Normally (for 3GPP access), the RRC system information is used (PLMN identity list and location information i.e., cell and tracking area).

4. The W-AGF shall select an AMF based on the received AN parameters and local policy, as specified in TS 23.501, clause 6.3.5. The W-AGF shall then forward the Registration Request received from the UE to the selected AMF within a NG Application Protocol (NGAP) initial UE message (NAS message, Line-id based ULI, Establishment cause, AMF set id, UE context request, Allowed NSSAI).

5. The selected AMF may decide to request the SUCI by sending a NGAP Downlink NAS transport message (NAS Identity Request) message to W-AGF. This NAS message and the response are sent between W-AGF and 5G-RG encapsulated within EAP/5G-NAS packets. 6. The AMF may decide to authenticate the UE by invoking an AUSF. In this case, the AMF shall select an AUSF as specified in TS 23.501 clause 6.3.4 based on SUPI or SUCI.

The AUSF executes the authentication of the UE as specified in TS 33.501. The AUSF selects a UDM as described in TS 23.501, clause 6.3.8 and gets the authentication data from UDM. The authentication packets are encapsulated within NAS authentication messages and the NAS authentication messages are encapsulated within EAP/5G-NAS packets. Between W-AGF and AMF, the messages are encapsulated within NGAP downlink/uplink NAS transport messages. After the successful authentication:

In step 6c, the AUSF shall send the anchor key (Security Anchor Function (SEAF) key) to AMF which is used by AMF to derive NAS security keys and a security key for W-AGF (W-AGF key). The UE also derives the anchor key (SEAF key) and from that key it derives the NAS security keys and the security key for W-AGF (W-AGF key).

In step 6c, the AUSF shall also include the SUPI, if in step 6a the AMF provided to AUSF a SUCI.

The AMF decides if the Registration Request needs to be rerouted as described in clause TS 23.502 clause 4.2.2.2.3, where the initial AMF refers to the AMF.

NOTE 2: EAP-AKA' or 5G-AKA are allowed for the authentication of 5G-RG via W-5GAN access, as specified in TS 33.501. Figure 7.2.1.1-1 only shows authentication flow using EAP-AKA'.

7a. The AMF shall send a NAS Security Mode Command (Selected NAS security algorithm, ngKSI, Replayed UE security capabilities, (IMEISV) International Mobile Equipment Identity Software Version request, Additional 5G security information, EAP message) to UE in order to activate NAS security. If an EAP-AKA' authentication was successfully executed in step 6, the AMF shall encapsulate the EAP-Success received from AUSF within the NAS Security Mode Command message. The message is encapsulated within a NGAP downlink NAS transport message. 7b. The W-AGF shall forward the NAS Security Mode Command message to UE within an EAP/5G-NAS packet.

7c. The 5G-RG completes the EAP-AKA' authentication (if initiated in step 6), creates a NAS security context and a W-AGF key and sends the NAS Security Mode Complete message (IMEISV) within an EAP/5G-NAS packet.

7d. The W-AGF relays the NAS Security Mode Complete message to the AMF in a NGAP Uplink NAS transport message.

8a. Upon receiving NAS Security Mode Complete, the AMF shall send an NGAP Initial Context Setup Request message (Old AMF, UE Aggregate Maximum Bit Rate (MBR), GUAMI, Allowed NSSAI, UE security capability, Security Key, Trace Activation, Masked IMEISV).

8b. This triggers the W-AGF to send an EAP-Success to UE, which completes the EAP-5G session. After this step, NAS messages between 5G-RG and W-AGF are transported without EAP-5G using W-CP signalling connection.

9. [Conditional] An authenticated W-CP signalling connection is established between the 5G-RG and W-AGF by using the common W-AGF key that was created in the 5G-RG in step 7c and received by the W-AGF in step 8a.

10. W-AGF notifies the AMF that the 5G-RG context (including AN security) was created by sending a NGAP Initial Context Setup Response.

11. [Conditional] The AMF requests the PEI from the 5G-RG as described in TS 23.502, clause 4.2.2.2.2 step 11.

12. The AMF performs step 12-16 in TS 23.502 clause 4.2.2.2.2. At 5G-RG registration to UDM, the Access Type non-3GPP access is used.

13. The AMF sends the NGAP Downlink NAS transport with NAS Registration Accept message (5GS registration result, 5G-GUTI, Equivalent PLMNs, Non-3GPP TAI, Allowed NSSAI, Reject NSSAI, Configured NSSAI, 5GS network feature support, network slicing indication, Non-3GPP de-registration timer value, Emergency number lists, SOR transport container, NSSAI inclusion mode) to the W-AGF which forwards the NAS Registration accept message to the 5G-RG.

14. [Conditional] The 5G-RG responds with NAS Registration Complete message as described in TS 23.502 clause 4.2.2.2.2 step 22 and W-AGF forwards the NAS Registration Accept to AMF in a NGAP Uplink NAS transport message.

15. The AMF performs step 23-24 in TS 23.502 clause 4.2.2.2.2.

[0055] In some embodiments, EAP is used as currently assumed by SA2. In some embodiments, EAP is not used as currently assumed by SA2.

[0056] Option 2, Solution 1: System Information (SI) is included in the EAP-Request/5G- Start as "AN parameters" (AN=access network). This is illustrated in Figure 6.

[0057] Option 2, Solution 2: System Information (SI) is included in the first IKE_AUTFI response as an IKEv2 notify payload. This is illustrated in Figure 7.

[0058] Option 2, Solution 3: System Information (SI) may also be fetched by UE from a DNS server available in/via the local IP network using some particular FQDN (for plain DNS, this is not secure. According to embodiments DNSSEC could be used to secure it.) - see FQDN used to fetch the emergency numbers in 23.003 subclause 19.4.2.9A.6

[0059] Option 1, solution 1: System Information (SI) is included as parameters in the PPPoE Active Discovery Offer (PADO) message (second arrow from the top) from AGF (W- AGF) to 5G-RG. This is illustrated in Figure 8 which is from a contribution on NASoPPP/PPPoE.

[0060] Option 1, solution 2: Define a second "Wireline access Control Protocol" (W-CP) that can be used to carry NAS and AS parameters between UE and 5G-RG. The System Information is sent as parameters. According to embodiment, this protocol might include an IP broadcasted packet with AN/SI parameters sent from W-AGF to all 5G-RGs connected to the IP subnet.

[0061] Note that 23.316 already includes a definition of W-CP protocol so it is used in SA2 terminology but in some embodiments it may be based on an already existing protocol such as a re-use of PPPoE.

[0062] Figure 9 is a schematic block diagram of a radio access node 900 according to some embodiments of the present disclosure. The radio access node 900 may be, for example, a base station 402 or 406. As illustrated, the radio access node 900 includes a control system 902 that includes one or more processors 904 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 906, and a network interface 908. The one or more processors 904 are also referred to herein as processing circuitry. In addition, the radio access node 900 includes one or more radio units 910 that each includes one or more transmitters 912 and one or more receivers 914 coupled to one or more antennas 916. The radio units 910 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 910 is external to the control system 902 and connected to the control system 902 via, e.g., a wired connection (e.g., an optical cable). Flowever, in some other embodiments, the radio unit(s) 910 and potentially the antenna(s) 916 are integrated together with the control system 902. The one or more processors 904 operate to provide one or more functions of a radio access node 900 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 906 and executed by the one or more processors 904.

[0063] Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 900 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures.

[0064] As used herein, a "virtualized" radio access node is an implementation of the radio access node 900 in which at least a portion of the functionality of the radio access node 900 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 900 includes the control system 902 that includes the one or more processors 904 (e.g., CPUs, ASICs, FPGAs, and/or the like), the memory 906, and the network interface 908 and the one or more radio units 910 that each includes the one or more transmitters 912 and the one or more receivers 914 coupled to the one or more antennas 916, as described above. The control system 902 is connected to the radio unit(s) 910 via, for example, an optical cable or the like. The control system 902 is connected to one or more processing nodes 1000 coupled to or included as part of a network(s) 1002 via the network interface 908. Each processing node 1000 includes one or more processors 1004 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1006, and a network interface 1008.

[0065] In this example, functions 1010 of the radio access node 900 described herein are implemented at the one or more processing nodes 1000 or distributed across the control system 902 and the one or more processing nodes 1000 in any desired manner. In some particular embodiments, some or all of the functions 1010 of the radio access node 900 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1000. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1000 and the control system 902 is used in order to carry out at least some of the desired functions 1010. Notably, in some embodiments, the control system 902 may not be included, in which case the radio unit(s) 910 communicate directly with the processing node(s) 1000 via an appropriate network interface(s).

[0066] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 900 or a node (e.g., a processing node 1000) implementing one or more of the functions 1010 of the radio access node 900 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0067] Figure 11 is a schematic block diagram of the radio access node 900 according to some other embodiments of the present disclosure. The radio access node 900 includes one or more modules 1100, each of which is implemented in software. The module(s) 1100 provide the functionality of the radio access node 900 described herein. This discussion is equally applicable to the processing node 1000 of Figure 10 where the modules 1100 may be implemented at one of the processing nodes 1000 or distributed across multiple processing nodes 1000 and/or distributed across the processing node(s) 1000 and the control system 902. [0068] Figure 12 is a schematic block diagram of a UE 1200 according to some embodiments of the present disclosure. As illustrated, the UE 1200 includes one or more processors 1202 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1204, and one or more transceivers 1206 each including one or more transmitters 1208 and one or more receivers 1210 coupled to one or more antennas 1212. The transceiver(s) 1206 includes radio-front end circuitry connected to the antenna(s) 1212 that is configured to condition signals communicated between the antenna(s) 1212 and the processor(s) 1202, as will be appreciated by on of ordinary skill in the art. The processors 1202 are also referred to herein as processing circuitry. The transceivers 1206 are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE 1200 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1204 and executed by the processor(s) 1202. Note that the UE 1200 may include additional components not illustrated in Figure 12 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the UE 1200 and/or allowing output of information from the UE 1200), a power supply (e.g., a battery and associated power circuitry), etc.

[0069] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 1200 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0070] Figure 13 is a schematic block diagram of the UE 1200 according to some other embodiments of the present disclosure. The UE 1200 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provide the functionality of the UE 1200 described herein.

[0071] With reference to Figure 14, in accordance with an embodiment, a communication system includes a telecommunication network 1400, such as a 3GPP-type cellular network, which comprises an access network 1402, such as a RAN, and a core network 1404. The access network 1402 comprises a plurality of base stations 1406A, 1406B, 1406C, such as NBs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1408A, 1408B, 1408C. Each base station 1406A, 1406B, 1406C is connectable to the core network 1404 over a wired or wireless connection 1410. A first UE 1412 located in coverage area 1408C is configured to wirelessly connect to, or be paged by, the corresponding base station 1406C. A second UE 1414 in coverage area 1408A is wirelessly connectable to the corresponding base station 1406A. While a plurality of UEs 1412, 1414 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 base station 1406.

[0072] The telecommunication network 1400 is itself connected to a host computer 1416, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server, or as processing resources in a server farm. The host computer 1416 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1418 and 1420 between the telecommunication network 1400 and the host computer 1416 may extend directly from the core network 1404 to the host computer 1416 or may go via an optional intermediate network 1422. The intermediate network 1422 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1422, if any, may be a backbone network or the Internet; in particular, the intermediate network 1422 may comprise two or more sub-networks (not shown).

[0073] The communication system of Figure 14 as a whole enables connectivity between the connected UEs 1412, 1414 and the host computer 1416. The connectivity may be described as an Over-the-Top (OTT) connection 1424. The host computer 1416 and the connected UEs 1412, 1414 are configured to communicate data and/or signaling via the OTT connection 1424, using the access network 1402, the core network 1404, any intermediate network 1422, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1424 may be transparent in the sense that the participating communication devices through which the OTT connection 1424 passes are unaware of routing of uplink and downlink communications. For example, the base station 1406 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1416 to be forwarded (e.g., handed over) to a connected UE 1412. Similarly, the base station 1406 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1412 towards the host computer 1416.

[0074] Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to Figure 15. In a communication system 1500, a host computer 1502 comprises hardware 1504 including a communication interface 1506 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1500. The host computer 1502 further comprises processing circuitry 1508, which may have storage and/or processing capabilities. In particular, the processing circuitry 1508 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 1502 further comprises software 1510, which is stored in or accessible by the host computer 1502 and executable by the processing circuitry 1508. The software 1510 includes a host application 1512. The host application 1512 may be operable to provide a service to a remote user, such as a UE 1514 connecting via an OTT connection 1516 terminating at the UE 1514 and the host computer 1502. In providing the service to the remote user, the host application 1512 may provide user data which is transmitted using the OTT connection 1516.

[0075] The communication system 1500 further includes a base station 1518 provided in a telecommunication system and comprising hardware 1520 enabling it to communicate with the host computer 1502 and with the UE 1514. The hardware 1520 may include a communication interface 1522 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1500, as well as a radio interface 1524 for setting up and maintaining at least a wireless connection 1526 with the UE 1514 located in a coverage area (not shown in Figure 15) served by the base station 1518. The communication interface 1522 may be configured to facilitate a connection 1528 to the host computer 1502. The connection 1528 may be direct or it may pass through a core network (not shown in Figure 15) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 1520 of the base station 1518 further includes processing circuitry 1530, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 1518 further has software 1532 stored internally or accessible via an external connection.

[0076] The communication system 1500 further includes the UE 1514 already referred to. The UE's 1514 hardware 1534 may include a radio interface 1536 configured to set up and maintain a wireless connection 1526 with a base station serving a coverage area in which the UE 1514 is currently located. The hardware 1534 of the UE 1514 further includes processing circuitry 1538, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 1514 further comprises software 1540, which is stored in or accessible by the UE 1514 and executable by the processing circuitry 1538. The software 1540 includes a client application 1542. The client application 1542 may be operable to provide a service to a human or non-human user via the UE 1514, with the support of the host computer 1502. In the host computer 1502, the executing host application 1512 may communicate with the executing client application 1542 via the OTT connection 1516 terminating at the UE 1514 and the host computer 1502. In providing the service to the user, the client application 1542 may receive request data from the host application 1512 and provide user data in response to the request data. The OTT connection 1516 may transfer both the request data and the user data. The client application 1542 may interact with the user to generate the user data that it provides.

[0077] It is noted that the host computer 1502, the base station 1518, and the UE 1514 illustrated in Figure 15 may be similar or identical to the host computer 1416, one of the base stations 1406A, 1406B, 1406C, and one of the UEs 1412, 1414 of Figure 14, respectively. This is to say, the inner workings of these entities may be as shown in Figure 15 and independently, the surrounding network topology may be that of Figure 14. [0078] In Figure 15, the OTT connection 1516 has been drawn abstractly to illustrate the communication between the host computer 1502 and the UE 1514 via the base station 1518 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 1514 or from the service provider operating the host computer 1502, or both. While the OTT connection 1516 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0079] The wireless connection 1526 between the UE 1514 and the base station 1518 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1514 using the OTT connection 1516, in which the wireless connection 1526 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0080] A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1516 between the host computer 1502 and the UE 1514, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1516 may be implemented in the software 1510 and the hardware 1504 of the host computer 1502 or in the software 1540 and the hardware 1534 of the UE 1514, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1516 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1510, 1540 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1516 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1518, and it may be unknown or imperceptible to the base station 1518. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 1502's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 1510 and 1540 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1516 while it monitors propagation times, errors, etc.

[0081] Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 14 and 15. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1600, the host computer provides user data. In sub-step 1602 (which may be optional) of step 1600, the host computer provides the user data by executing a host application. In step 1604, the host computer initiates a transmission carrying the user data to the UE. In step 1606 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1608 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0082] Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 14 and 15. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1700 of the method, the host computer provides user data. In an optional sub-step (not shown) the host computer provides the user data by executing a host application. In step 1702, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1704 (which may be optional), the UE receives the user data carried in the transmission. [0083] Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 14 and 15. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1800 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1802, the UE provides user data. In sub-step 1804 (which may be optional) of step 1800, the UE provides the user data by executing a client application. In sub-step 1806 (which may be optional) of step 1802, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 1808 (which may be optional), transmission of the user data to the host computer. In step 1810 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0084] Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 14 and 15. For simplicity of the present disclosure, only drawing references to Figure 19 will be included in this section. In step 1900 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1902 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1904 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0085] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0086] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0087] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Exemplary embodiments of the disclosure

Group A Embodiments

1. A method performed by a wireline device for receiving network information, the method comprising: - receiving network information that is similar to information as is broadcasted in RRC; and

- using the network information.

2. The method of any of the previous embodiments wherein the wireline device is a 5G- Residential Gateway, 5G-RG.

3. The method of any of the previous embodiments wherein receiving the network information comprises receiving the network information during the setup of the W-CP connection.

4. The method of any of the previous embodiments wherein receiving the network information comprises receiving the network information in an EAP-Request/5G-Start packet.

5. The method of any of the previous embodiments wherein receiving the network information comprises receiving the network information in the first IKE_AUTH response as an IKEv2 notify payload.

6. The method of any of the previous embodiments wherein receiving the network information comprises fetching the network information from a DNS server available in/via the local IP network using some particular FQDN.

7. The method of the previous embodiment wherein DNSSEC is used to secure the fetching.

8. The method of any of the previous embodiments wherein receiving the network information comprises receiving the network information included as parameters in the PPPoE Active Discovery Offer (PADO) message. 9. The method of any of the previous embodiments wherein receiving the network information comprises receiving the network information over a new "Wireline access Control Protocol" (W-CP) that can be used to carry NAS and AS parameters.

10. The method of any of the previous embodiments wherein the network information comprises one or more of: PLMN identity list: PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason (e.g., overload); non-public network identities: If the wireline access network belong to a non-public network; indication for support of emergency services: If network supports emergency services; IoT parameters: E.g., if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; TS 23.502 already requires N3IWF to allocate signalling IPsec SA solely for NAS signalling and to allocate separate IPsec Child SA for QoS flow of the PLMN based on PCC rules from the PCF; network indication indicating support of access to RLOS (Restricted Local Operator Services).

11. The method of any of the previous embodiments, further comprising:

- providing user data; and

- forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

12. A method performed by a network node such as a base station for transmitting network information, the method comprising:

- transmitting, to a wireline device, network information that is similar to information as is broadcasted in RRC.

13. The method of any of the previous embodiments wherein the wireline device is a 5G- Residential Gateway, 5G-RG. 14. The method of any of the previous embodiments wherein transmitting the network information comprises transmitting the network information during the setup of the W-CP connection.

15. The method of any of the previous embodiments wherein transmitting the network information comprises transmitting the network information in an EAP-Request/5G-Start packet.

16. The method of any of the previous embodiments wherein transmitting the network information comprises transmitting the network information in the first IKE_AUTH response as an IKEv2 notify payload.

17. The method of any of the previous embodiments wherein transmitting the network information comprises transmitting the network information included as parameters in the PPPoE Active Discovery Offer (PADO) message.

18. The method of any of the previous embodiments wherein transmitting the network information comprises transmitting the network information over a new "Wireline access Control Protocol" (W-CP) that can be used to carry NAS and AS parameters.

19. The method of any of the previous embodiments wherein the network information comprises one or more of: PLMN identity list: PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason (e.g., overload); non-public network identities: If the wireline access network belong to a non-public network; indication for support of emergency services: If network supports emergency services; IoT parameters: E.g., if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; TS 23.502 already requires N3IWF to allocate signalling IPsec SA solely for NAS signalling and to allocate separate IPsec Child SA for QoS flow of the PLMN based on Primary Component Carrier (PCC) rules from the PCF; network indication indicating support of access to RLOS (Restricted Local

Operator Services.

20. The method of any of the previous embodiments, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device.

Group C Embodiments

21. A wireline device for receiving network information, the wireline device comprising:

- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

- power supply circuitry configured to supply power to the wireless device.

22. A network node such as a base station for transmitting network information, the base station comprising:

- processing circuitry configured to perform any of the steps of any of the Group B embodiments; and

- power supply circuitry configured to supply power to the base station.

23. A User Equipment, UE, for receiving network information, the UE comprising:

- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply power to the UE.

24. A communication system including a host computer comprising: - processing circuitry configured to provide user data; and

- a communication interface configured to forward the user data to a network for transmission to a User Equipment, UE;

- wherein the network comprises a base station having an interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

25. The communication system of the previous embodiment further including the base station.

26. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

27. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE comprises processing circuitry configured to execute a client application associated with the host application.

28. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

29. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. 30. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

31. A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.

32. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE;

- wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.

33. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

34. The communication system of the previous 2 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE's processing circuitry is configured to execute a client application associated with the host application.

35. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

- at the host computer, providing user data; and - at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

36. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

37. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station;

- wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.

38. The communication system of the previous embodiment, further including the UE.

39. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

40. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

41. The communication system of the previous 4 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and - the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

42. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

43. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

44. The method of the previous 2 embodiments, further comprising:

- at the UE, executing a client application, thereby providing the user data to be transmitted; and

- at the host computer, executing a host application associated with the client application.

45. The method of the previous 3 embodiments, further comprising:

- at the UE, executing a client application; and

- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application;

- wherein the user data to be transmitted is provided by the client application in response to the input data.

46. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

47. The communication system of the previous embodiment further including the base station.

48. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

49. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

50. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

51. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

52. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer. Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

• W-AGF Wireline-Access Gateway Function

• 5G Fifth Generation

• 5GC Fifth Generation Core Network

• 5G-RG 5G-Residential Gateway

• ABS Almost Blank Subframe

• AF Application Function

• AMF Access and Mobility Management Function

• AN Access Network

• AP Access Point

• AS Access Stratum

• ASIC Application Specific Integrated Circuit

• AUSF Authentication Server Function

• BBF Broadband Forum

• CPU Central Processing Unit

• DN Data Network

• DNSSEC Domain Name System Security Extension

• DSP Digital Signal Processor

• EAP Extensible Authentication Protocol

• eNB Enhanced or Evolved Node B

• E-UTRAN Evolved Universal Terrestrial Radio Access Network

• FN-RG Fixed Network Residential Gateway

• FPGA Field Programmable Gate Array

• FQDN Fully Qualified Domain Name

• GHz Gigahertz

. gNB New Radio Base Station • GUAMI Globally Unique AMF Identifier

• GUTI Globally Unique Temporary ID

• IMEISV International Mobile Equipment Identity Software Version

• IoT Internet of Things

• IP Internet Protocol

• KSI Key Set Identifier

• LTE Long Term Evolution

• MBR Maximum Bit Rate

• MME Mobility Management Entity

• MTC Machine Type Communication

• NAS Non Access Stratum

• NEF Network Exposure Function

• NF Network Function

• NG-RAN Next Generation Radio Access Network

• NGAP Next Generation Access Point

• NR New Radio

• NRF Network Repository Function

• NSSAI Network Slice Selection Assistance Information

• NSSF Network Slice Selection Function

• OFDM Orthogonal Frequency Division Multiplexing

• PADO Point to Point Protocol over Ethernet Active Discovery Offer

• PCC Primary Common Control

• PCF Policy Control Function

• PDU Protocol Data Unit

• P-GW Packet Data Network Gateway

• PLMN Public Land Mobile Network

• PPPoE Point to Point over Ethernet

• QoS Quality of Service

• RACH Random Access Channel

• RAID Redundant Array of Independent Disks RAM Random Access Memory

RAN Radio Access Network

RAT Radio Access Technology

RE Resource Element

RF Radio Frequency

RLM Radio Link Management

RLOS Restricted Local Operator Source

ROM Read Only Memory

RRC Radio Resource Control

RRH Remote Radio Head

RRM Radio Resource Management

RRU Remote Radio Unit

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power / Reference Signal Received

Power

RSRQ Reference Symbol Received Quality / Reference Signal Received

Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

RTT Round Trip Time

SA Service and Systems Aspects

SCEF Service Capability Exposure Function

SEAF Security Anchor Function

SFN System Frame Number

S-GW Serving Gateway

SI System Information

SIB System Information Block

SIM Subscriber Identity Module

SMF Session Management Function • SUCI Subscription Concealed Identifier

• SUPI Subscriber Permanent Identifier

• UDM Unified Data Management

• UE User Equipment

• UL Uplink

• ULI User Location Information

• UMTS Universal Mobile Telecommunications System

• UPF User Plane Function

• USB Universal Serial Bus

• USIM Universal Subscriber Identity Module

• UTDOA Uplink Time Difference of Arrival

• UTRA Universal Terrestrial Radio Access

• UTRAN Universal Terrestrial Radio Access Network

• V2I Vehicle-to-Infrastructure

• V2V Vehicle-to-Vehicle

• V2X Vehicle-to-Everything

• VMM Virtual Machine Monitor

• VNE Virtual Network Element

• VNF Virtual Network Function

• VoIP Voice over Internet Protocol

• WAN Wide Area Network

• WCDMA Wideband Code Division Multiple Access

• WD Wireless Device

• WiMax Worldwide Interoperability for Microwave Access

• WLAN Wireless Local Area Network

• W-5GAN Wireline 5G Access Network

• W-AGF Wireline-Access Gateway Function

• W-CP Wireline Access Control Protocol

Claims

1. A method performed by a wireline device for receiving network information, the method comprising:

- receiving network information comprising one or more of:

PLMN identity list; PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non-public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services, and

- using the network information.

2. The method of claim 1, wherein the wireline device is a 5G-Residential Gateway, 5G- RG.

3. The method of claim 1 or 2, wherein receiving the network information comprises receiving the network information during the setup of the Wireline Access Control Protocol, W-CP, connection.

4. The method of any of the previous claims, wherein receiving the network information comprises receiving the network information in an EAP-Request/5G-Start packet.

5. The method of any of the previous claims, wherein receiving the network information comprises receiving the network information in the first IKE_AUTH response as an IKEv2 notify payload.

6. The method of any of the previous claims, wherein receiving the network information comprises fetching the network information from a Domain Name System, DNS, server available in/via the local IP network using some particular FQDN.

7. The method of any of the previous claims, wherein Domain Name System Security Extension, DNSSEC, is used to secure the fetching.

8. The method of any of the previous claims, wherein receiving the network information comprises receiving the network information included as parameters in the PPPoE Active Discovery Offer, PADO, message.

9. The method of any of the previous claims, wherein receiving the network information comprises receiving the network information over a second Wireline Access Control Protocol, W-CP, that can be used to carry Non Access Stratum, NAS, and Access Stratum, AS, parameters.

10. The method of any of the previous claims, further comprising:

- providing user data; and

- forwarding the user data to a host computer (1416, 1502) via the transmission to the base station (402, 406, 1406, 1518).

11. A method performed by a network node such as a base station (402, 406, 1406, 1518) for transmitting network information, the method comprising:

- transmitting, to a wireline device, network information comprising one or more of:

PLMN identity list; PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non-public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services.

12. The method of claim 11, wherein the wireline device is a 5G-Residential Gateway, 5G- RG.

13. The method of any of claims 11 or 12, wherein transmitting the network information comprises transmitting the network information during the setup of the Wireline access Control Protocol, W-CP, connection.

14. The method of any of claims 11 to 13, wherein transmitting the network information comprises transmitting the network information in an EAP-Request/5G-Start packet.

15. The method of any of claims 11 to 14, wherein transmitting the network information comprises transmitting the network information in the first IKE_AUTH response as an IKEv2 notify payload.

16. The method of any of claims 11 to 15, wherein transmitting the network information comprises transmitting the network information included as parameters in the PPPoE Active Discovery Offer, PADO, message.

17. The method of any of claims 11 to 16, wherein transmitting the network information comprises transmitting the network information over a second Wireline Access Control Protocol, W-CP, that can be used to carry Non Access Stratum, NAS, and Access Stratum, AS, parameters.

18. The method of any of claims 11 to 17, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer (1416, 1502) or a wireless device (412, 1200, 1412, 1414, 1514).

19. A wireline device for receiving network information, the wireline device comprising:

- processing circuitry; and - power supply circuitry configured to supply power to the wireless device (412, 1200, 1412, 1414, 1514),

wherein the processing circuitry is configured to perform a method comprising:

- receiving network information comprising one or more of: PLMN identity list;

PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non-public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services, and

- using the network information.

20. A wireline device according to claim 19, wherein the

processing circuitry is configured to perform any of the steps of any of claims 2 to 10.

21. A network node such as a base station (402, 406, 1406, 1518) for transmitting network information, the base station (402, 406, 1406, 1518) comprising:

- processing circuitry (1530); and

- power supply circuitry configured to supply power to the base station (402, 406, 1406, 1518),

wherein the processing circuitry (1530) is configured to perform a method

comprising:

- transmitting, to a wireline device, network information comprising one or more of:

PLMN identity list; PLMNs supported by the NG-RAN node; location information; barring information that could indicate to 5G-RG if it is not allowed to access the network for some reason; non-public network identities; if the wireline access network belong to a non-public network; indication for support of emergency services; if network supports emergency services; IoT parameters; if 5G-RG can go to sleep mode without capability of receiving downlink traffic and timers for that; network indication indicating support of access to RLOS, Restricted Local Operator Services.

22. A network node such as a base station (402, 406, 1406, 1518) according to claim 21, wherein the processing circuitry (1530) is configured to perform any of the steps of any of claims 12 to 18.