A method and apparatus for operating a wireless device in fixed access and mobile networks

Abstract

This invention describes apparatuses / methods for enhanced mobility of a wireless device between a fixed network and a mobile network comprising, obtaining, by the wireless device, measurements of a first non-3GPP wireless access device and / or a first 3GPP wireless access device, and receiving, by the wireless device, a configuration to perform handover the communication between the first 3GPP wireless access device and the first non-3GPP wireless device.

Description

[0001] 2025PF00152

[0002] 1

[0003] A METHOD AND APPARATUS FOR OPERATING A WIRELESS DEVICE IN FIXED ACCESS AND MOBILE NETWORKS

[0004] FIELD OF THE INVENTION

[0005] This invention relates to a method, apparatus and system for operating a wireless device such as a cellular device in fixed access and mobile networks. In particular, operating the wireless device may involve a residential gateway, efficient mobility between fixed access and mobile networks, and the capability of registering and / or authenticating the device through the residential gateway.

[0006] BACKGROUND OF THE INVENTION

[0007] In conventional cellular networks, a primary station serves a plurality of secondary stations located within a cell served by this primary station. Wireless communication from the primary station towards each secondary station is done on downlink channels. Conversely, wireless communication from each secondary station towards the primary station is done on uplink channels. The wireless communication can include data traffic (sometimes referred to User Data), and control information (also referred sometimes as signaling). This control information typically comprises information to assist the primary station and / or the secondary station to exchange data traffic (e.g. resource allocation / requests, physical transmission parameters, information on the state of the respective stations).

[0008] In the context of cellular networks as standardized by 3GPP, the primary station is referred to a base station, or a gNodeB (or gNB) in 5G (NR) or an eNodeB (or eNB) in 4G (LTE). The eNB / gNB is part of the Radio Access Network RAN, which interfaces to functions in the Core Network (CN). In the same context, the secondary station corresponds to a mobile station, or a User Equipment (or a UE) in 4G / 5G, which is a wireless client device or a specific role played by such device. The term “node” is also used to denote either a UE or a gNB / eNB.

[0009] Additionally, for example, in the case of PC5 interface or Sidelink communication, it is possible to have Direct communication between secondary stations, here UEs. It is then also possible for UEs to operate as Relays to allow for example out of coverage UEs to get an intermediate (or indirect) connection to the eNB or gNB. To be able to work as a relay, a UE may use discovery messages to establish new connections with other UEs.

[0010] In home networks, wireless connectivity is provided to wireless devices by means of a local area network, e.g., Wi-Fi based, wherein one or more access points may provide wireless connectivity to the wireless devices (e.g., Wi-Fi stations).2025PF00152

[0011] 2

[0012] In home networks, access to the Internet and / or a data network is sometimes enabled by means of a fixed wireless access device denoted as a residential gateway. The residential gateway provides connectivity to the wireless devices in the local area network as received through the cellular infrastructure.

[0013] However, existing residential gateway devices still suffer from certain problems, e.g., capability of supporting seamless mobility with the mobile network and / or capability of identifying the wireless devices connected through the residential gateway.

[0014] SUMMARY OF THE INVENTION

[0015] It is an object of the present invention to enable an enhanced procedure for providing connectivity to and supporting mobility of a wireless device in a customer premises network.

[0016] To this end, it is proposed methods, apparatus and computer program product as in the appended claims.

[0017] In accordance with a first aspect of the invention, it is proposed a method for enhanced mobility of a wireless device between a fixed wireless access device, FWA, and a mobile network, the method comprising,

[0018] obtaining, by the wireless device, measurements of a first non-3GPP FWA wireless access device and / or a first 3GPP wireless access device, and

[0019] receiving, by the wireless device, a configuration to handover the communication of a data connection between the first 3GPP wireless access device and the first non-3GPP FWA wireless access device.

[0020] In a variant of the invention that may be combined with the first aspect of the invention, the method further comprises providing, by the wireless device, measurements relative to the first non-3GPP FWA wireless access device to the first 3GPP wireless access device and / or measurements relative to the first 3GPP wireless access device to the non-3GPP FWA wireless access device.

[0021] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the configuration comprises one or more conditions to conditionally perform the communication handover, and

[0022] the method further comprises evaluating, by the wireless device, the configuration and measurements to determine whether to handover the communication of the data connection with the data network between the first 3GPP wireless access device and the first non-3GPP wireless device.

[0023] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the configuration comprises a command to perform the handover of the communication of the data connection with the data network, and the method further comprises performing, by the wireless device, the handover of the communication of the data connection with the data network between the first 3GPP wireless access device and the first non-3GPP FWA wireless access device.2025PF00152

[0024] 3

[0025] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the measurements of a first non-3GPP FWA and / or first 3GPP wireless access device comprise estimating / obtaining one or more of:

[0026] - a signal strength,

[0027] - a network identifier,

[0028] - an access device identifier,

[0029] - a Layer 2 address,

[0030] - device capabilities,

[0031] - identification information of the serving network,

[0032] - SIB.

[0033] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the method further comprises:

[0034] performing, by the wireless device, an initial handover of the communication from a second 3GPP access device to the first 3GPP access device upon determining that the first non-3GPP FWA wireless access device is connected to the first 3GPP access device.

[0035] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the wireless device is configured with one or more policy rules comprising WLAN selection policies, QoS policies, or Access Traffic Steering, Switching, and Splitting (ATSSS) rules, the policy rules including latency-related conditions and / or connection-setup-delay-related conditions that influence whether traffic is transferred via 3GPP or non-3GPP access.

[0036] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the methos may further comprise measuring and / or obtaining, by the wireless device, latency information and / or connection setup delay information for the non-3GPP access, and determining, based on the measured and / or obtained information, whether to establish or maintain a connection via the non-3GPP access and / or whether to offload one or more traffic streams to the non-3GPP access.

[0037] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the wireless device may receive handover-related information including predicted connection setup delay and / or predicted handover interruption duration, the predictions being generated locally by an Al model of the wireless device or provided by a network-based Al model, and wherein the wireless device uses the predicted information to determine a timing to initiate or reject a handover to the non-3GPP access.

[0038] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the wireless device may obtain FWA credentials for the communication with the 3GPP wireless access device, wherein the credentials are associated to the subscription of the non-3GPP wireless access device. This means that the wireless device may not need to use its own credentials (from the user subscription), but that the communication may be based on the credentials of2025PF00152

[0039] 4

[0040] the FWA wireless access device. This reduces the load of the FWA wireless access device and it may provide better service to the wireless device.

[0041] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the credentials may be obtained upon determining that the measurements of the first non-3GPP FWA wireless access device are below a threshold; and / or may be valid as long as the wireless device remains within a maximum distance of the first non-3GPP FWA wireless access device. This means, e.g., that if the throughput measured by the wireless device is lower than a threshold, and the wireless device is closed to the FWA wireless access device, the wireless device may obtain said credentials.

[0042] In another variant of the invention that may be combined with the first aspect of the invention and previous variant(s), the wireless device may perform a communication relying on the FWA credentials. In accordance with a second aspect of the invention, it is proposed a method for registering a wireless device through a fixed wireless access device, FWA, the method comprising:

[0043] receiving, by the wireless device, an indication of a first non-3GPP FWA wireless access device being capable of registering the wireless device,

[0044] establishing, by the wireless device, a non-3GPP connection with the first non-3GPP FWA wireless access device,

[0045] transmitting, by the wireless device, a registration message over the non-3GPP connection,

[0046] performing, by the wireless device, a primary authentication with a core network, establishing, by the wireless device, a communication of a data connection.

[0047] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the first non-3GPP FWA wireless access device comprises a non-3GPP transceiver adapted to communicate with the wireless device and a 3GPP wireless device adapted to communicate with a 3 GPP access device.

[0048] In another variant, PDCP and / or RRC and / or SDAP messages exchanged by the wireless device are transmitted transparently through the non-3GPP FWA wireless access device.

[0049] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), RLC / MAC / PHY layers of the non-3GPP FWA wireless access are controlled by the 3GPP access device to allocate communication resources fortransport of PDCP and / or RRC and / or SDAP messages exchanged by the wireless device.

[0050] In another variant, SDAP messages carry the communication of the data connection with the data network.

[0051] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the non-3GPP FWA wireless access device comprises a 3GPP wireless device capable of exchanging RRC and PDCP messages with a 3GPP wireless access device and NAS messages with an access and mobility function.2025PF00152

[0052] 5

[0053] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the methods further comprise:

[0054] determining, by the wireless device, a root key from the security context of the wireless device, and using the root key to setup the security of a non-3GPP transceiver with the non-3GPP FWA wireless access device.

[0055] In another variant, of the invention that may be combined with the first and second aspects or any of their variant(s) the methods further comprise:

[0056] determining, by the wireless device, the serving network serving the non-3GPP access device,

[0057] performing, by the wireless device, a registration procedure with the serving network serving the non-3GPP access device.

[0058] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the methods further comprise:

[0059] receiving, by the wireless device, a validation token from the first non-3GPP FWA wireless access device through the non-3GPP interface, wherein the token validates the non-3GPP FWA wireless access device as capable of registering the wireless device in the wireless device core network and / or providing connectivity through the wireless device core network.

[0060] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the methods further comprise:

[0061] transmitting to and / or receiving from the first non-3GPP FWA wireless access device and the first 3GPP access device messages of the data connection to perform data aggregation and / or load balancing.

[0062] In another variant of the invention that may be combined with the first and second aspects or any of their variant(s), the methods further comprise:

[0063] transmitting to and / or receiving from the first non-3GPP FWA wireless access device and a second non-3GPP FWA wireless access device messages of the data connection to perform data aggregation and / or load balancing.

[0064] In accordance with a third aspect of the invention, it is proposed an apparatus for enhanced mobility a fixed network and a mobile network comprising,

[0065] a non-3GPP transceiver,

[0066] a 3GPP transceiver,

[0067] a processor, and

[0068] a memory,

[0069] wherein the apparatus is adapted to:

[0070] obtain measurements of a first non-3GPP wireless access device and / or a first 3GPP wireless access device via the non-3GPP and 3GPP transceivers,2025PF00152

[0071] 6

[0072] provide measurements of the first non-3GPP wireless access device to first 3GPP wireless access device and / or the first 3GPP wireless access device to the non-3GPP wireless access device via the non-3GPP and 3GPP transceivers,

[0073] receive a configuration via the non-3GPP and / or 3GPP transceivers, wherein the apparatus is adapted to store the configuration in the apparatus memory and / or process the configuration by means of the apparatus processor to perform the communication handover between the first 3GPP wireless access device and the first non-3GPP wireless device.

[0074] In accordance with a fourth aspect of the invention, it is proposed an apparatus for registering a wireless device through a fixed access network in a core network, the apparatus comprising:

[0075] a non-3GPP transceiver,

[0076] a 3GPP transceiver,

[0077] a processor, and

[0078] a memory,

[0079] wherein the apparatus is adapted to:

[0080] receive via its non-3GPP transceiver an indication of a first non-3GPP access device being capable of registering the wireless device,

[0081] establish via the non-3GPP transceiver a non-3GPP connection with the first non-3GPP access device,

[0082] transmit via the non-3GPP transceiver a registration message over the non-3GPP connection,

[0083] perform via the non-3GPP transceiver a primary authentication with the wireless device core network,

[0084] establish via the non-3GPP transceiver a data connection with the data network.

[0085] In accordance with a fifth aspect of the invention, it is proposed a computer program for operating a wireless device having instructions for producing the steps of the methods of the first or second aspects or their variants.

[0086] The third, fourth, and fifth aspects of the invention may be combined with one or more of the variants of the first and second aspects of the invention.

[0087] It is noted that the above apparatus may be implemented based on discrete hardware circuitries with discrete hardware components, integrated chips, or arrangements of chip modules, or based on signal processing devices or chips controlled by software routines or programs stored in memories, written on a computer readable media, or downloaded from a network, such as the Internet.

[0088] It shall be understood that the apparatus, the UE, the residential gateway unit, the system, the methods, and the computer program product of the various aspects of the invention may have similar and / or identical preferred embodiments, in particular, as defined in the dependent claims.

[0089] It shall be understood that a preferred embodiment of the invention can also be any combination of the dependent claims or above embodiments with the respective independent claim.2025PF00152

[0090] 7

[0091] These and other aspects of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter.

[0092] BRIEF DESCRIPTION OF THE DRAWINGS

[0093] In the following drawings:

[0094] Fig. 1 schematically represents the overall cellular system including UEs, RAN, and core network;

[0095] Fig. 2 provides a schematic representation of a UE and its components;

[0096] Fig. 3 schematically represents different entities involved in a non-terrestrial network; Fig. 4 schematically represents a random-access procedure in a wireless network;

[0097] Fig. 5 schematically represents a signalling procedure by an access device;

[0098] Fig. 6 schematically represents the periodic transmission of SSB bursts;

[0099] Fig. 7 schematically represents examples of wireless devices according to some embodiments;

[0100] Fig. 8 schematically describes the components in a residential gateway deployment; Fig. 9 schematically describes a procedure for the distribution of credentials to a user equipment device in a residential gateway deployment;

[0101] Fig. 10 schematically describes the components in a distributed residential gateway deployment;

[0102] Fig. 11 schematically describes a procedure for the distribution of credentials to a user equipment device / unit in a distributed residential gateway deployment;

[0103] Fig. 12 schematically describes the load of different communication links in residential gateway deployments;

[0104] Fig. 13 schematically describes the components of a unit in a distributed residential gateway;

[0105] Fig. 14 schematically describes a procedure to handle the load of different communication links in residential gateway deployments;

[0106] Fig. 15 schematically describes an embodiment of the invention based on DualSteer devices;

[0107] Fig. 16 schematically describes components of a DualSteer device;

[0108] Fig. 17 to Fig. 23 schematically describe different mobility scenarios of a wireless device when moving between a cellular network and a local network such as customer premises network or home network;

[0109] Fig. 24 describes an exemplary protocol stack to enable the functionalities in some embodiments of the invention; and

[0110] Fig. 25 describes an exemplary mobility procedure according to some embodiments of the invention.2025PF00152

[0111] 8

[0112] DETAILED DESCRIPTION OF EMBODIMENTS

[0113] Embodiments of the present invention are now described based on a cellular communication network environment, such as 5G or 6G. However, the present invention may also be used in connection with other wireless technologies.

[0114] Throughout the present disclosure, the abbreviation “gNB” (5G terminology) or “BS” (base station) or the term “access device” is intended to mean a wireless access device such as a cellular base station or a WiFi access point or a ultrawide band (UWB) personal area network (PAN) coordinator. The gNB may consist of a centralized control plane unit (gNB-CU-CP), multiple centralized user plane units (gNB-CU-UPs) and / or multiple distributed units (gNB-DUs). The gNB is part of a radio access network (RAN), which provides an interface to functions in the core network (CN). The RAN is part of a wireless communication network. It implements a radio access technology (RAT). Conceptually, it resides between a communication device such as a mobile phone, a computer, or any remotely controlled machine and provides connection with its CN. The CN is the communication network’s core part, which offers numerous services to customers who are interconnected via the RAN. More specifically, it directs communication streams over the communication network and possibly other networks.

[0115] Furthermore, the terms “base station” (BS) and “network” may be used as synonyms in this disclosure. This means for example that when it is written that the “network” performs a certain operation it may be performed by a CN function of a wireless communication network, or by one or more base stations that are part of such a wireless communication network, and vice versa. It can also mean that part of the functionality is performed by a CN function of the wireless communication network and part of the functionality by the base station.

[0116] It is further noted that throughout the present disclosure only those blocks, components and / or devices that are relevant are shown in the accompanying drawings. Other blocks have been omitted for reasons of brevity. Furthermore, blocks designated by same reference numbers are intended to have the same or at least a similar function, so that their function is not described again later.

[0117] A cellular system is a wireless communication system that consists of three main components: user equipment (UE), radio access network (RAN), and core network (CN). These components work together to provide voice and data services to mobile users over a large geographic area.

[0118] In conventional cellular networks, a primary station serves a plurality of secondary stations located within a cell served by this primary station. Wireless communication from the primary station towards each secondary station is done on downlink channels. Conversely, wireless communication from each secondary towards the primary station is done on uplink channels. The wireless communication can include data traffic (sometimes referred to User Data), and control information (also referred sometimes as signalling). This control information typically comprises information to assist the primary station and / or the secondary station to exchange data traffic (e.g. resource allocation / requests,2025PF00152

[0119] 9

[0120] physical transmission parameters, information on the state of the respective stations). In the context of cellular networks as standardized by 3GPP, the primary station is referred to a base station, or a gNodeB (or gNB) in 5G (NR) or an eNodeB (or eNB) in 4G (LTE). The eNB / gNB is part of the Radio Access Network RAN, which interfaces to functions in the Core Network (CN). In the same context, the secondary station corresponds to a mobile station, or a User Equipment (or a UE) in 4G / 5G, which is a wireless client device or a specific role played by such device. The term “node” is also used to denote either a UE or a gNB / eNB.

[0121] Additionally, for example, in the case of PC5 interface or Sidelink communication, it is possible to have Direct communication between secondary stations, here UEs. It is then also possible for UEs to operate as Relays to allow for example out of coverage UEs to get an inter-mediate (or indirect) connection to the eNB or gNB. To be able to work as a relay, a UE may use discovery messages to establish new connections with other UEs. Certain UEs may communicate with each other by using device-to-device communication, also known as sidelink communication using the PC5 interface that may rely on physical sidelink (PS) broadcast channel, PS shared channel, PS control, etc. Furthermore, the role of a relay node has been introduced in 3GPP. This relay node is a wireless communication station that includes functionalities for relaying communication between a primary station, e.g. a gNB and a secondary station, e.g. a UE. This relay function for example allows to extend the coverage of a cell to an out-of-coverage (OoC) secondary station. This relay node may be a mobile station or could be a different type of device. In the specifications for 4G, the Proximity Services (ProSe) functions are defined inter aha in TS 23.303, and TS 24.334 to enable - amongst others -connectivity for the cellular User Equipment (UE) that is temporarily not in coverage of the cellular network base station (eNB) serving the cell. This particular function is called ProSe UE-to-network relay, or Relay UE for short. The Relay UE relays application and network traffic in two directions between the OoC UE and the eNB. The local communication between the Relay UE and the OoC UE is called device-to-device (D2D) communication or Sidelink (also known as PC5) communication in TS 23.303 and TS 24.334. Once the relaying relation is established, the OoC-UE is, e.g., IP -connected via the Relay UE and acts in a role of “Remote UE”. This situation means the Remote UE has an indirect network connection to selected functions of the Core Network as opposed to a direct network connection to all Core Network functions that is the normal case. Furthermore, it has been introduced the role of a UE-to-UE relay node, i.e., a relay node re-laying the communication between two UE devices. The relay node relays the communications between UE devices. UEs may connect to the core network through a base station when in-coverage. In such relay scenarios, the relay devices may receive and store some information for some time before forwarding it towards the target device. This information that may be stored and forwarded may be discovery messages received from a source UE whereby the relay UE may release them at some point of time later. This information that may be stored and forwarded may be a SIB that may contain a timestamp.2025PF00152

[0122] 10

[0123] User equipment (UE) is the device that a user uses to access the cellular system, such as a smartphone, a tablet, a laptop, loT device, or a wearable device. A UE typically may contain the following components:

[0124] - A universal integrated circuit card (UICC), which stores the user's identification and authentication information, such as the subscription permanent identifier (SUPI) or credentials.

[0125] - A transceiver, which converts the digital signals from the processor into analog signals for transmission and reception over the air interface. The transceiver also performs modulation, demodulation, coding, decoding, and other signal processing functions.

[0126] - A processor, which controls the operation of the UE and executes the applications and services that the user requests. The processor also communicates with the RAN and the CN using various protocols.

[0127] - A display, which shows the user the information and feedback from the UE, such as the signal strength, the battery level, the call status, the messages, the contacts, the menu, etc.

[0128] - A microphone and a speaker, which enable the user to make and receive voice calls, as well as use other audio features, such as voice mail, voice recognition, etc.

[0129] - A keyboard and / or a touch screen, which allow the user to enter and select commands, text, numbers, etc.

[0130] - A camera and / or a video recorder, which enable the user to capture and send images and videos, as well as use other multimedia features, such as video calling, video streaming, etc.

[0131] - A memory, which stores the data and programs that the user needs, such as the phone book, the messages, the photos, the videos, the applications, etc as well as a computer program to perform the operations of the RAN and CN protocols.

[0132] - A battery, which provides the power supply for the UE.

[0133] Fig. 2 provides a schematic representation of a UE and its components, e.g., UICC (201), processor (202), transceiver (203), memory (204), input devices (205) such as camera, microphone, etc and output devices (206) such as display, speaker, etc. Fig. 7 schematically represents wireless devices that may include the capabilities of a UE and / or a STA. Fig. 7a) represents AR / VR glasses; Fig. 7b) represents a connected vehicle; and Fig. 7c) represents a mobile phone. In these devices, a reflective intelligent surface (RIS) may be embedded, e.g., by covering and / or under the whole a part of the UE surface. This may be used, e.g., to better deal with interferences or improve wireless sensing.

[0134] A UE access the cellular network via the radio access network, as described below. Certain UEs may communicate with each other by using device-to-device communication, also known as sidelink communication using the PC5 interface that may rely on physical sidelink (PS) broadcast channel, PS shared channel, PS control, etc.

[0135] A UE may receive a configuration by means of different procedures:

[0136] Downlink control information (DCI) is a type of control information that is sent from the BS to the UE on the physical downlink control channel (PDCCH). DCI contains various parameters that2025PF00152

[0137] 11

[0138] instruct the UE how / when to decode and transmit data on the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH), such as the resource allocation, the modulation and coding scheme. The UE needs to monitor the PDCCH in each subframe to detect and decode the DCI that is addressed to it.

[0139] Uplink control information (UCI) is a type of control information that is sent from the UE to the BS on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). UCI contains various feedback signals that inform the BS about the status and quality of the downlink transmission, such as the HARQ acknowledgments (ACKs), the channel state information (CSI), and the scheduling requests (SRs). The UE needs to encode and transmit the UCI according to the configuration and timing indicated by the BS.

[0140] Sidelink control information (SCI) is a type of control information that is sent from the UE to another UE on the physical sidelink control channel (PSCCH) in device-to-device (D2D) communication scenarios. The main functions of SCI include resource allocation, synchronization, channel quality reporting.

[0141] Medium access control (MAC) control element (MAC CE) is a type of control information that is sent from the BS to the UE or vice versa on the MAC layer. MAC CE contains various commands or indications that regulate the MAC layer functions, such as the buffer status report (BSR), the timing advance command (TAC), the discontinuous reception (DRX) command, etc. The UE needs to process the MAC CE according to the MAC protocol and the configuration provided by the BS.

[0142] Radio resource control (RRC) command is a type of control information that is exchanged between the BS and the UE on the RRC layer. RRC Command contains various messages that modify / configure RRC parameters and / or initiate, modify, or release the RRC connection or the radio bearers between the UE and the BS, such as the RRC connection setup, the RRC connection reconfiguration, the RRC connection release, the security mode command, the mobility from E-UTRA command, the handover from E-UTRA preparation request, etc. The UE needs to respond to the RRC Command according to the RRC protocol and the configuration provided by the BS.

[0143] Non-access stratum (NAS) messages are used for signalling between UE and core network (CN) on the non-access stratum (NAS) layer. NAS messages enable functionality such as registration, session establishment, security, and mobility management. The UE needs to respond to the NAS Command according to the NAS protocol and the configuration provided by the CN.

[0144] UE parameter update (UPU) is a procedure between the UE and the home network that enables the home network to update configuration parameters in mobile phones and / or USIM using the UDM control plane procedure (TS 23.502). The UE can receive Parameters Update Data from the UDM after the UE has registered in the 5G network.

[0145] Steering of Roaming (SoR) enables the home network to guide the user equipment (UE) when registering on a visited network. For detailed information about the interfaces and registration in the 5G System, referto 3GPP TS.23.501 (Release 15)

[0017] and 3GPP TS 24.501 (Release 15)

[0018] , The 5G2025PF00152

[0146] 12

[0147] CP-SOR is activated during or after registration to update the UE's "Operator Controlled PLMN Selector with Access Technology" list via secure NAS messages, as directed by the home PLMN based on specific operator policies, such as preferred networks or UE location.

[0148] UE configuration update (UCU) is used to update configuration parameters as per TS 23.502 that may include Access and Mobility Management related parameters decided and provided by the AMF, UE Policy provided by the PCF. When AMF wants to change the UE configuration for access and mobility management related parameters the AMF initiates the procedure defined in clause 4.2.4.2. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure defined in clause 4.2.4.3. If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly. The procedure in clause 4.2.4.2 may be triggered also when the AAA Server that performed Network Slice-Specific Authentication and Authorization for an S-NSSAI revokes the authorization.

[0149] Radio access network (RAN) is the part of the cellular system that connects the UEs to the CN via the air interface. The RAN consists of base stations (BSs). A base station (BS) is a fixed or mobile transceiver that covers a certain geographic area, called a cell. In 5G, a BS is also called a gNB (next generation node B). A BS can serve multiple UEs simultaneously within its cell, by using different frequencies, time slots, codes, or beams. A BS also performs functions such as power control, handover control, channel allocation, interference management, etc. A base station can be divided into two units: a central unit (CU) and a distributed unit (DU). The CU performs the higher layer functions, such as RLC, PDCP, RRC, etc. The DU performs the lower layer functions, such as PHY and MAC. The CU and the DU can be co-located or separated, depending on the network architecture and deployment. In cellular systems, a base station may be denoted, based on context, as a cell, or gNB.

[0150] The cell may also refer to the coverage area of a base station. A BS may have different coverage areas such as a macro cell (e.g. several kilometres wide), a pico cell (e.g., for a given location such as a stadium) or a femto cell for a small location (e.g., a home or part of it).

[0151] A base station may communicate with the core network. Since there can be base stations for different cellular systems, different interfaces are required. For instance, a base station, eNB, in a 4G Long Term Evolution (LTE) system (also known as Evolved Universal Mobile Telecommunications Systems (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the 4G CN known as EPC through the corresponding interface. For instance, a base station, gNB, in a 5G system (i.e., 5G New Radio or Next Generation RAN) may communicate with the 5GC through a different interface. 4G and 5G base stations may communicate with each other directly or through their corresponding core networks.

[0152] The main protocols used between the UEs and the RAN are:

[0153] - The physical layer (PHY), which defines the characteristics of the air interface, such as the frequency bands, the modulation schemes, the coding rates, the frame structure, the synchronization, etc.2025PF00152

[0154] 13

[0155] - The medium access control (MAC) layer, which regulates the access of the UEs to the shared radio channel, by using techniques such as orthogonal frequency division multiple access (OFDMA), time division duplex (TDD), frequency division duplex (FDD), etc.

[0156] - The radio link control (RLC) layer, which provides reliable data transmission over the radio channel, by using techniques such as segmentation, reassembly, error detection, error correction, retransmission, etc.

[0157] - The packet data convergence protocol (PDCP) layer, which compresses and decompresses the headers of the data packets, encrypts and decrypts the data, and performs data integrity protection.

[0158] - The radio resource control (RRC) layer, which establishes, maintains, and releases the radio bearers between the UEs and the RAN, as well as exchanges the signaling messages for functions such as connection setup, handover, measurement reporting, security activation, etc.

[0159] A transmission / reception communication unit or transceiver may be used by BS and UE to transmit / receive data. Control data may be required for a physical broadcast channel, physical downlink control channel, etc. Data may be for the physical downlink shared channel.

[0160] Data may be encoded by the UE and / or BS to obtain data symbols and / or control symbols that may be exchanged over the wireless interface. The conversion from digital data into analog symbols may be done by the transmission / reception communication unit.

[0161] A medium access control control-element (MAC-CE) is a MAC layer communication element that is used to control the communication between wireless devices. A MAC-CE may be exchanged in a shared channel, e.g., the physical downlink / uplink / sidelink shared channel.

[0162] The communication between a UE and a base station or the communication between UEs (when sidelink is used) may involve the exchange of reference signals. Reference signals may include primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS). Core network (CN) is the part of the cellular system that connects the RAN to other networks, such as the Internet, or other cellular systems. The CN consists of two main (control / user) domains. The control domain is responsible for providing signalling and control functions for the UEs, such as authentication, authorization, mobility management, session management, etc. The control plane consists of several network functions (NFs), such as the access and mobility management function (AMF), the session management function (SMF), the unified data management (UDM), the policy control function (PCF), the network exposure function (NEF), and the authentication server function (AUSF). The access and mobility management function (AMF) is a NF that handles the registration, deregistration, connection management, and mobility management for the UEs. The session management function (SMF) is a NF that handles the establishment, modification, and release of the sessions for the UEs. The SMF also communicates with the user plane devices to perform functions such as IP address allocation, tunneling, QoS, etc. The unified data management (UDM) is a NF that stores and manages the user data, such as the2025PF00152

[0163] 14

[0164] SUPI, the service profile, the subscription status, etc. The policy control function (PCF) is a NF that provides the policy rules and charging information for the UEs, such as the access type, the service level, the data rate, the quota, etc. The network exposure function (NEF) is a NF that exposes the network capabilities and services to external applications and devices, such as the IMS, the Internet of Things (loT), etc. The authentication server function (AUSF) is a NF that performs the primary authentication with the by using credentials and the SUPI. The user domain is responsible for providing data and multimedia services to the UEs, by using packets and IP addresses. The user plane consists of two main functions: the user plane function (UPF) and the data network (DN). The user plane function (UPF) is a device that forwards the data packets between the UEs and the DNs, as well as performs functions such as tunneling, firewall, QoS, charging, etc. The data network (DN) is a network that provides access to the services and applications that the UEs request, such as the Internet, the IMS, etc.

[0165] A residential gateway (RG) is a device that connects a home network to an external network, such as the Internet or a cellular system. An RG typically provides functions such as routing, switching, firewall, NAT, DHCP, DNS, VPN, etc. An RG can also support various types of interfaces, such as Ethernet, Wi-Fi, Bluetooth, USB, etc. A cellular-capable RG is an RG that has a cellular interface, such as a UICC slot, a cellular modem, or an antenna, that enables it to access the cellular system as a backup or an alternative to the wired or wireless broadband connection. A cellular-capable RG can provide benefits such as: (1) Enhanced reliability, by switching to the cellular connection in case of a failure or a degradation of the broadband connection; (2) Increased bandwidth, by aggregating the cellular connection and the broadband connection to achieve higher data rates or QoS.

[0166] A multi-SIM subscription is a subscription that allows a user to have multiple SIMs (or eSIMs) that are linked to the same account and service profile. A user can use the multi-SIM subscription to access the cellular system from different devices, such as a smartphone, a tablet, a laptop, or a wearable device, without having to switch the SIM card or the device.

[0167] Overall system: Fig. 1 provides an overall description of a wireless system wherein devices 100, 102, and 128 can play the role of UEs. Device 102 is part of a cellular-capable RG providing connectivity to a home network 129 e.g., by means of a local area network and / or wireless local area network. Device 102 is served by base station 104.

[0168] The RAN 127 comprises base station 103 and serves UE 128. UE 128 may also be a UE to Network relay given access to remote UE 136 that is out of coverage of base station 103. UEs 134 and 136 also communicate with each other via a UE-to-UE relay 135. UE to UE communication via relays is enabled by means of side link communication / PC5 interface.

[0169] Within the RAN, the range of base station 103 is extended via smart repeater 137 and reflective intelligent surface (RIS) 138. Smart repeater 137 and RIS 138 give access to UE 142.

[0170] The RAN 143 includes base station 104 tand serves as wireless access infrastructure for the home network. Base station 104 also serves a mobile access device and / or UE as a UAV 139. UAV 139 may provide connectivity to remote UE 136.2025PF00152

[0171] 15

[0172] Furthermore, a satellite gateway 141 is shown that connects to satellite 140 and may provide connectivity services to remote UE 136 or UE 100.

[0173] In Fig. 1, the 5G core network 133 may include one or more an AMF 121, SMF 123, UPF 122, AUSF 124, UDM 125, PCF 131, NEF 132 and allows the connection to a data network 130.

[0174] In Fig. 1, a second core network 142, e.g., a legacy core network as a 4G core network, is also shown that may interface with the 5G core network 133, interface with base stations denoted eNB in 4G, and provide a connection to the data network 130. The legacy 4G core network is denoted EPC and may include one or more mobility management entities (MME), a serving gateway, a multimedia broadcast multicast service gateway, a broadcast multicast service center, a packet data network gateway, etc. The mobility management entity may handle the signalling between UE and the 4G CN and may interact with the home subscriber server (HSS) in charge of the storage and management of subscriber data and secrets. The MME may provide connection management, similar to the AMF in 5G. The serving gateway may be used to exchange user internet protocol messages whereby the serving gateway may interact with the packet data network gateway that is connected to IP services. Multiple protocols in 4G and 5G have similar features. For example, the 5G network registration and 4G attach registration message are initially sent by the UE to establish a connection between the UE and the CN, which involves sending an initial request from the UE with its identity and capabilities, receiving an authentication request from the CN with a challenge, sending an authentication response from the UE with a response, receiving an authentication result from the CN with an indication of success or failure, and sending a security mode command from the CN with the selected security algorithms. As a result of this connection establishment procedure, NAS and AS keys are derived from the K_AMF (5G) and K_ASME (4G) where K_AMF is managed by the AMF and K_ASME is managed by the MME. A UE may connect to a serving network or serving Public Land Mobile Network (PLMN). A UE may have a subscription with a home PLMN, and during the registration procedure, the (AMF of the) serving PLMN may forward the registration request to the (AUSF of the) home PLMN that may perform an initial authentication procedure between home PLMN and UE. If the authentication procedure is successful, keys are derived and the home PLMN may share derived credentials with the serving PLMN, including K_SEAF, that may be used to derive K_AMF, from which NAS keys and AS keys are derived. The registration request sent by the UE includes an identifier that can be used by the home PLMN to identify the UE. To prevent privacy vulnerabilities, the long-term subscriber’s identifier known as Subscriber Permanent Identifier (SUPI) may not be exchanged in the clear, but instead, either a Subscription Concealed Identifier (SUCI) or a pseudonym known as GUTI are exchanged with the AMF of the serving PLMN. The AMF of the PLMN may then forward the SUCI to the home PLMN so that the home PLMN decrypts / verifies it.

[0175] Satellite access: Fig. 1 depicts satellite 140 providing access to one or more UEs. Satellite access can be performed by means of non-terrestrial devices at different altitudes such as Low Earth Orbit (LEO), Medium Earth Orbit (MEO) or Geosynchronous Equatorial Orbit (GEO) satellites. Other types of non-terrestrial devices may include high-altitude platform station (HAPS) or unmanned aerial vehicle2025PF00152

[0176] (UAVs) that may comprise a base station. Fig. 3 illustrates different elements including a GEO satellite 302, a MEO satellite 303, a LEO satellites 304 and 304’, a UAV 305, all of them potential non-terrestrial mobile access devices giving coverage to wireless device (e.g., a UE) 301. GEO satellite 302 remains static over a given earth position while MEO and LEO satellites move. MEO satellites 303 have a slower moving vector 306 in relation to the earth compared with LEO satellites 304 / 304’ that have a faster moving vector 307 / 307’. A non-terrestrial gateway 308 is included that provides connectivity to the mobile access device via a feeder link 310. A mobile access device provides service to the wireless device via a service link 311. Two mobile access devices in the same orbit may communicate with each other via an intra-orbit-satellite link 312 while two mobile access devices in different orbits may communicate with each other via an inter-orbit-satellite link 313. Fig. 3 finally also includes a terrestrial access device 309 that may also provide connectivity to wireless device 301. The terrestrial access device 309, the wireless device 301, and non-terrestrial gateway are on the earth surface 314.

[0177] A UE in a cellular system performs an initial random-access procedure to connect an access device. The 5G random access procedure is illustrated by means of Fig. 4 wherein 401 represents a user equipment and 402 represents an access device. The access device distributes signals 402. Signals 402 can be distributed periodically or on demand. Signals 402 may comprise the Master Information Block (MIB) transmitted together with / in the physical broadcast channel (PBCH) and the synchronization signals. The MIB comprises:

[0178] MIB ::= SEQUENCE {

[0179] systemFrameNumber BIT STRING (SIZE (6)), subCarrierSpacingCommon ENUMERATED {scsl5or60, scs30orl20}, ssb-SubcarrierOffset INTEGER (0..15),

[0180] dmrs-TypeA-Position ENUMERATED {pos2, pos3},

[0181] pdcch-ConfigSIB 1 INTEGER (0..255),

[0182] cellBarred ENUMERATED {barred, notBarred}, intraFreqReselection ENUMERATED {allowed, notAllowed},

[0183] spare BIT STRING (SIZE (1))

[0184]

[0185] MIB and PBCH are transmitted as part of a Synchronization Signal Block, and the access device may transmit multiple SSBs through different beams, allowing the user equipment to determine the preferred beam, and once the preferred beam is obtained, retrieve the MIB, and use the information in the MIB to attempt to retrieve System Information Block 1 (SIB1) that may also be distributed periodically. The UE can the use the information in SIB1 to perform the random -access procedure selecting a preamble to indicate its intention to access the cell by means of message 404, e.g., preamble transmission. This message may use a random-access radio network temporary identifier (RA-RNTI). Upon reception of message 404, access device 402 replies with message 405, e.g., a random access response. This message may include a time advance field to adapt the transmission timing, a value2025PF00152

[0186] 17

[0187] matching the preamble used by wireless device 401, and a grant (communication resources) for the wireless device. The access device also assigns a temporary cell radio network temporary identifier (TC-RNTI). Prior to this message 405, the access device may send a PDCCH DCI message assigning resources (a communication grant). This message may be addressed using the RA-RNTI. Upon reception of message 405, wireless device uses the initial grant received in the previous message and the RA-RNTI to transmit a subsequent message 406, e.g, an RRCSetupRequest or PHY layer. This message may include a Contention Resolution Identifier (CRI). This message may be sent in the PUSCH. As a response, access device replies with message 407, e.g., RRCSetup, that includes / repeats the received CRI confirming that the access device has identified the access device. This message includes a Cell RNTI (C-RNTI). Next, wireless device replies with message 408, e.g., an RRCSetupComplete that includes the RegistrationRequest message, and UE capabilities.

[0188] MIB and PBCH are transmitted as part of a Synchronization Signal Block, and the access device may transmit multiple SSBs through different beams. Multiple SSBs transmitted through multiple beams form an SSB burst. The multiple SSBs in an SSB burst are transmitted sequentially in the first part of a frame. SSB bursts are transmitted periodically, typically every 20 ms, or more.

[0189] Fig. 5 schematically illustrates an access device 500 transmitting four beams, each of them transmitting an SSB, namely 501, 502, 503, and 504. A wireless device 505 can measure the signal strength, i.e., RSRP (Reference Signal Received Power), of the beams. This is illustrated by means of the graph in Fig. 5 where 501’, 502’, 503’, and 504’ represent the RSRP of beams 501, 502, 503, and 504, respectively, as measured by wireless device 505. Wireless device 505 can use this information to determine which one of the beams is the preferred beam for further communication, e.g., to perform the random access procedure.

[0190] Fig. 6 further schematically illustrates SSB bursts transmitted periodically. In this case, each SSB burst comprises four SSBs transmitted in the first part / half of every second frame. In this figure, frames are denoted as f, f+1, f+2, f+3,...A frame has atypical duration of 10 ms.

[0191] Resource grid: in a cellular network, such as a 5G network, the resource grid is a structured framework used to allocate and manage communication resources efficiently. It is characterized by a time-frequency matrix where each element, known as a resource element, is defined by its position in both time and frequency domains. The vertical axis represents frequency, segmented into subcarriers, which are spaced at intervals. The subcarrier spacing can vary depending on the deployment scenario, with common spacings being 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz (corresponding to mu equal to 0, 1, 2, 3, 4, and 5, respectively). The horizontal axis of the grid represents time and is divided into frames, subframes, and slots, each frame has a duration of 10 ms and each subframe has a duration of 1 millisecond. Within these subframes, the time is further divided into slots. For mu, there are 2Amu symbols per subframe. Each slot typically spans 14 OFDM symbols. Each resource element in the grid, defined by the intersection of a time symbol and a frequency subcarrier, can carry a small portion of data, control information, or reference signals. These resource elements are2025PF00152

[0192] 18

[0193] grouped into larger units called Resource Blocks (RBs), which span 12 subcarriers in frequency and one slot in time. The allocation of these RBs is dynamically managed.

[0194] Reflective intelligent surfaces (RIS): may be used as part of the wireless infrastructure or as part of the wireless devices. RIS, often referred to as metasurfaces, are advanced materials engineered with sub-wavelength structures that can manipulate electromagnetic waves in a controlled manner. These surfaces consist of an array of unit cells, each capable of adjusting its electromagnetic response through electronic control, thus enabling dynamic alteration of the wavefront of the incident signal. The wireless device can utilize the RIS to fine-tune the reflection properties of the wireless sensing signal, such as phase, amplitude, and polarization. By dynamically adjusting these parameters, the RIS can enhance signal strength, directivity, and overall signal quality. For instance, the RIS can focus the reflected signal towards the transmitter, significantly improving signal reception. This capability is particularly advantageous in urban environments where obstacles and interference are prevalent. Technical details of the RIS involve the implementation of tunable elements, such as varactor diodes or microelectromechanical systems (MEMS), in each unit cell. These elements allow real-time reconfiguration of the surface's electromagnetic properties in response to control signals from the wireless device. The control signals can be generated based on real-time analysis of the received signal's quality and contextual parameters, ensuring optimal reflection under varying conditions. The RIS can operate in various frequency bands, including sub-6 GHz and millimeter-wave (mmWave) frequencies, making it versatile for different wireless applications. Additionally, the RIS can incorporate sensing capabilities to monitor the environment and further refine the reflection parameters. For example, integrated sensors can detect changes in temperature, humidity, or the presence of obstacles, and adjust the reflection properties accordingly to maintain high signal quality.

[0195] Quality of Service: a wireless system may be used to transport data belonging to different types of applications such as Machine Type Communication (MTC), Critical Machine Type Communication (CMTC), Enhanced Mobile Broadband (EMB), or Fixed Wireless Access (FWA). MTC (e.g., smart meters, tracking,...) requires low bandwidth and non-latency critical, CMTC (e.g., industrial applications) has strict throughput, latency, and availability needs, EMB (VR / AR, 4K UDH, ...) and FWA (e.g., in the home) require high data rate, with low latency, and low end-to-end response time. In wireless network such as 5G the Quality of Service has to accommodate different applications such as EMB, MTC, ultra-reliable low latency communications. QoS is influenced by the entities involved in the communication, UE, RAN, UPF, and DN. Data exchanges between UE and DN are mapped to QoS flows, and each QoS flow is mapped to a 5G QoS Identifier (5QI) in TS 23.501 (Table 5.7.4-1) that describes resource types, priority, packet delay budget, packet error rate, maximum data burst volume. Network is configured to configure RAN and core network interfaces to achieve the requirements of a 5QI. QoS is applied to a data stream from the wireless physical layer to the core network. Between RAN and UPF, QoS is applied in terms of a QoS flow. QoS in the RAN is managed by means of Data Radio Bearers (DRB). A QoS flow on core network side is created by means of a PDU session establishment2025PF00152

[0196] 19

[0197] accept. The mapping between a QoS flow and a DRM is done by means of SDAP configuration in an RRC message (RRCSetup or RRCReconfiguration) The indication or identifier that connects the whole QoS pipe is called QoS flow identifier. Downlink traffic requires mapping IP messages and the QoS pipe, and this is done by the UPF. For each IP message or packet, the UPF checks (by means of a packet QoS assignment / detection rule) the packet information (source / destination / protocol / type of service / ...) and directs the IP packet to a QoS flow. The packet QoS assignment / detection rule is provided by SMF interacting with PCF. In the uplink, the UE performs a similar task by applying QoS rules provided in NAS messages (e.g., PDU session establishment) by the SMF or are pre-configured / derived by the UE.

[0198] Discontinuous reception (DRX) in cellular networks such as 5G is in two types, Idle mode DRX and Connected mode DRX. In Idle mode DRX, the UE wakes up to monitor for paging messages. If no paging message is detected, it sleeps further. In Connected DRX mode, the UE enters in sleep mode periodically and during the sleep period the UE is not required to monitor the Physical Download Control Channel. The access device configures the UE device with C-DRX parameters.

[0199] Connected DRX approach reduces energy consumption of the device because it does not require monitoring the PDCCH periodically and it also reduces the transmissions of CSI or SRS signals, that also has a positive effect in the network / access devices load. There are two types of DRX cycles, long and short. A long DRX cycle consists of an on period and an off period. The on duration is in terms of milliseconds. The long DRC cycle may be configured or the long DRX cycle and short DRX cycles may be configured. The access device can configure the time (drx-onDurationTimer) during which the UE is awake and goes back to sleep if there is no PDCCH received. The access device can also configure a given drx-LongCycleStartOffiset to start to awake period at a subframe boundary and / or drx-SlotOffset relative to the subframe boundary. If there is activity in an awake period, the UE may remain awake some more time determined by the drx-InactivityTimer. Furthermore, the access device can configure long DRX cycle together with additional DRX cycle which is shorter than long DRX cycle. Configurable parameters include the drx-ShortCycle (duration of the short cycle) and drx-ShortCycleTImer that determines how many short cycles before the device should apply.

[0200] Data scheduling in a cellular network such as a 5G cellular network may be performed by means of a scheduler wherein the scheduler takes as input information such as measurements of UE / network, buffer status report, QoS requirements, associated radio bearers, or a scheduling request. In the downlink, data scheduling may be performed by means of dynamic scheduling and semi persistent scheduling (SPS). In dynamic scheduling, every data exchange in the Physical Downlink Shared Channel (PDSCH) is scheduled by means of a downlink control information (DCI) message in the Physical Downlink Control Channel (PDCCH). In SPS, the scheduling is done by means of an RRC message. In the uplink, scheduling can be performed by means of dynamic scheduling and configured scheduling (CS). In dynamic scheduling each Physical Uplink Shared Channel (PUSCH) is scheduled over DCI. In CS, the PUSCH transmission is scheduled via RRC message. Furthermore, a Scheduling Request message may be sent over the PUCCH (Physical Uplink Control Channel) or in an Uplink Control2025PF00152

[0201] 20

[0202] Information (UCI) in the PUSCH (Physical Uplink Shared Channel). An SR may be sent by a UE device when it has data to transmit. Upon reception, the access device can allocate resources (Uplink Grant by means of the Physical Downlink Control Channel. Upon resource allocation, the UE device can transmit data in the Physical Uplink Shared Channel.

[0203] Wireless sensing and integrated wireless sensing and communication: wireless systems are evolving to include wireless sensing capabilities. These wireless sensing capabilities may be implemented e.g. by a radar functionality in wireless communication involving one or more access devices (e.g., base stations (BS)) and / or one or more terminal devices (e.g., UEs). As an example, Frequency Modulated Continuous Wave (FMCW) mmWave radar systems can measure range, velocity, and angle of arrival (if two receivers are available) of objects in the scene which reflect radio waves. Such radar systems emit a chirp signal, e.g., a sine wave that increases in frequency over time. The chirp signal (e.g., a continuous wave pulse) has a bandwidth and a frequency increase rate. Generally, a continuous series of such chirps are emitted. The transmitted and received analogue chirp signals are mixed to generate an intermediate frequency (IF) signal which corresponds to the difference in frequencies of the two signals (outbound and inbound) and whose output phase corresponds to the difference in the phases of the two signals. Each surface of a scene or environment will therefore produce a constant frequency IF signal whose frequency relates to the distance to the surface (i.e., a first distance from the transmitter of the chirp signal to the surface plus a second distance from the surface to the receiver of the chirp signal). To resolve two surfaces at different distances, the two IF signals can be frequency resolved. A longer time window of the IF signal results in greater resolution. As the chirp time is related to its bandwidth (with constant chirp frequency change) the resolution of the radar is related to the chirp bandwidth. The IF signal may then be band pass filtered (to remove signals below some minimal range and frequencies above the maximum frequency for a subsequent analogue-to-digital converter (ADC)) and digitized prior to further processing. The upper frequency sensing range of the bandpass filter and ADC sets the maximum range that can be detected (i.e., IF frequencies increase with range). To detect vibrations, the phase of the IF signal is important, since the phase (i.e., the difference in phases of the transmitted and received chirp signals) is a sensitive measure of small changes in the distance of a surface. Small distance changes can be detected in the phase signal but may be indiscernible in the frequency signal. Moreover, phase difference measures between two consecutive chirp signals can be used to determine the velocity of the surface. As an example, a fast Fourier transform (FFT) processing can be performed across multiple chirp signals to enable separation of objects with the same range but moving at different velocities. A Fourier transform converts a signal from a space or time domain into the frequency domain. In the frequency domain the signal is represented by a weighted sum of sine and cosine waves. A discrete digital signal with N samples can be represented exactly by a sum of N waves. FFT provides a faster way of computing a discrete Fourier transform by using the symmetry and repetition of waves to combine samples and reuse partial results. This method can save a huge amount of processing time, especially with real -world signals that can have many thousands or even millions of samples. As a further example, angle2025PF00152

[0204] 21

[0205] estimation can be performed by using the phase difference between the received chirp signal at two separated receivers.

[0206] As another option, a channel state information (CSI) can be used, which is a measure of the phases and amplitudes of many frequencies detected at a receiver, thereby forming a complex ‘map’ of the radio environment, including effects of objects within that environment. CSI characterizes how wireless signals propagate from the transmitter to the receiver at certain carrier frequencies. CSI amplitude and phase are impacted by multi-path effects including amplitude attenuation and phase shift, e.g., by the displacements and movements of the transmitter, receiver, and surrounding objects and humans. In other words, CSI captures the wireless characteristics of the nearby environment. These characteristics, assisted by mathematical modeling or machine learning algorithms, can be used for different sensing applications. A radio channel may be divided into multiple subcarriers, as is done e.g. in 5G communication systems (using e.g. orthogonal frequency division multiplexing (OFDM)). To measure CSI, the transmitter may send long training symbols (LTFs), which contain pre-defined symbols for each subcarrier, e.g., in a packet preamble. When those LTFs are received, the receiver can estimate a CSI matrix using the received signals and the original LTFs. For each subcarrier, the channel can be modeled by y = Hx + n, where y is the received signal, x is the transmitted signal, H is the CSI matrix, and n is the noise vector. The receiver estimates the CSI matrix H using a pre-defined signal x and the received signal y after signal processing such as removing cyclic prefix, de-mapping and demodulation. The estimated CSI is then a three-dimensional matrix of complex values and this matrix represents an ‘image’ of the radio environment at that time. By processing a time series of such ‘images’ information on movements, locations and vibrations of objects can be extracted. Such a processing of a CSI matrix can be used for vital signs monitoring, presence detection, and human movement recognition. As an example, neural network like recognition techniques can be used to process the CSI matrix to perform such kinds of recognition.

[0207] It is noted that systems using channel state information (CSI) are somehow related to systems with FMCW mmWave radar. In a CSI-based system, the input signal X may be defined and the receiver may use the received signal Y to obtain H, i.e., as H = (Y - N) / X . In a FMCW mmWave radar, the transmitted signal Chirp X may also be predefined, and the receiver may uses the received signal Y to obtain a transfer function as H = Y / X . This last step is in fact somehow related to multiplying the locally computed chirp signal and the received chirp signal and applying a bandpass filter. According to various embodiments in this invention, the above-described wireless sensing techniques are implemented in a mobile communication system (e.g. 5G or 6G or other cellular or WiFi communication systems), while the functional coexistence of radar and communication operating in the same frequency bands is configured to avoid interference bandwidths. Thereby, radio sensing can be integrated into large-scale mobile networks to create perceptive mobile networks.

[0208] As another example, the sensing signal may consist of a number of pulses sent, e.g., at specific frequencies and timing (sensing signal parameter information) by a sensing transmitter. The2025PF00152

[0209] 22

[0210] sensing receiver may include a number of bandpass fdters that allow identifying the sensing signal parameter information, e.g, timing and frequency of the received pulses. In particular, if the transmitter determines a given pseudo-random sequence of frequency / timing pulses and beams it, e.g., by means of beamforming, in a specific direction, and if the transmitter communicates to the receiver the timing / frequency, in general, the sensing signal parameter information, of the transmitted sensing signal, the receiver can use its bandpass filters to identify the reception of the same transmitted pulses, i.e., sensing signal, based on the received sensing signal parameter information.

[0211] The wireless sensing signal may be part of the synchronization signal block. For instance, the wireless sensing signal may be a reference signal included in the primary synchronization signal or in the secondary synchronization signal. It may consist of a number of reference signals and / or it may be a wide band signal. This wireless sensing signal can allow the access devices to determine the presence of a wireless device. The wireless device may also use this wireless sensing signal to determine the access device that is more suitable to (re-)select.

[0212] Wireless local area network technologies such as Wi-Fi allow devices to connect to the Internet or to each other without using cables. Wi-Fi is based on radio waves that are transmitted and received by a device called a wireless access point (AP). The AP acts as a hub that connects Wi-Fi enabled devices, such as laptops, smartphones, tablets, smart TVs, etc., to a wired network, such as a local area network (LAN) or the Internet.

[0213] The term Wi-Fi is a trademark of the Wi-Fi Alliance, an industry association that certifies products that comply with the IEEE 802.11 standards for wireless local area networks (WLANs). These standards define the physical and data link layers of the communication protocol, such as the frequency bands, modulation schemes, encryption methods, authentication mechanisms, and data rates used by WiFi devices. The most common Wi-Fi standards are 802.11a, 802.11b, 802.11g, 802.1 In, 802.1 lac, and 802.1 lax, which operate in different frequency bands (2.4 GHz, 5 GHz, or both) and offer different levels of performance and compatibility.

[0214] To use Wi-Fi, a device needs to have a wireless network interface card (NIC) that can send and receive radio signals. The NIC scans the available wireless channels and detects the presence of nearby APs. The device then selects an AP to connect to, based on factors such as signal strength, security settings, and network name (SSID). The device and the AP exchange information, such as the MAC address, IP address, encryption key, and password, to establish a connection. This process is called association. After the connection is established, the device can communicate with the AP and other devices on the same network, or access the Internet through the AP.

[0215] IEEE 802.1 In (Wi-Fi 4) provided new features such as MIMO and frame aggregation to increase throughput. IEEE 802.1 lac (Wi-Fi 5) introduced wider bandwidth and MU-MIMO. IEEE 802.11 ax (WIFI-6) included OFDMA and BSS color or spatial reuse to use spectrum resources more efficiently. IEEE 802.11 ah introduced target wake time (TWT) to support low power loT applications by allowing STAs to go into sleep when not in a wake period after negotiation with AP. IEEE 802.1 Ibe (Wi-Fi 7)2025PF00152

[0216] 23

[0217] aims at improving throughput and latency operating in unlicensed bands between 1GHz and 7.125 GHz. Wi-Fi 7. Increases bandwidths up to 320 MHz, 4096 QAM modulation, and supporting up to 16 spatial streams in MU-MIMO with an improved sounding procedure. Wi-FI 7 also enables multiple resource units to be assigned to a single device. Furthermore, it includes an enhanced preamble with a universal SIG filed indicating the PHY version. It also extends the negotiated ack buffer size to 1024 bits. It also enables multilink operation (MLO) enabling multiple links between a station and an access point, for instance an AP can have two radios 2.4 and 5 GHz and use both of them for simultaneous transmission and / or reception with a multi-link capable device (MLD) capable station. Wi-Fi 7 also includes a restricted TWT providing predictable latency by assigning STAs to different rTWT types and making sure that other STAs do not transmit if they do not belong to a given rTWT type. Wi-Fi 7 also include multi-AP coordination performing, e.g., coordinated transmission, beamforming, or joint transmission.

[0218] For instance, in references to Fig. 1, devices 100, 101 and 102 may be Wi-Fi access points and device 106 may be a wireless station. Station 106 and access point 101 may be MLD and communicate with two links 126. Device 102 may be a cellular capable residential gateway.

[0219] Embodiments of this invention are illustrated in the context of ubiquitous connectivity through the convergence of fixed wireless access (FWA) and mobile access. In this context, a problem that needs to be addressed is how to enable more seamless mobility between fixed wireless access (FWA) and mobile access networks. Another problem refers to the registration process of a wireless device (UE) when the wireless device connects through the FWA.

[0220] Fig. 17, Fig. 18, and Fig. 19 describe a number of entities providing access to a data network. Different entities are identified by means of a number. Furthermore, an exemplary indication of the potential entity is given between brackets. For instance, “Number XYZ (Entity’s name XYZ)”, an entity may be identified by “Number XYZ” and the entity may be “Entity’s name XYZ”.

[0221] In particular, an entity 1703 (e.g., a residential gateway) may get and / or provide access to the data network 1714. Entity 1703 may comprise entities 1704 and 1705. Entity 1704 may be a communication interface to provide a device in 1715 (e.g., a local network, e.g., customer premises network (CPN)) with access to the data network 1714. Entity 1705 may be a communication interface to interact with a cellular system, e.g., a core network, e.g., via wireline or wirelessly, e.g., it may be a cellular interface such as 5G.

[0222] In particular, an entity 1700 (e.g., a user equipment (UE)) may get access to the data network 1714. Entity 1700 may comprise entities 1701 and 1702. Entity 1701 may be a communication interface to obtain access to the data network 1715 when located in 1715, e.g., a local area network. Entity 1702 may be a communication interface to interact with a cellular system, e.g., it may be a cellular interface such as 5G.

[0223] The devices 1700 and / or 1703 may connect to a cellular core network via wireless access devices (e.g., part of the cellular infrastructure) and / or wireline access. These wireless access devices may be, e.g., 1706 and 1707, that may be, e.g., two cellular base stations, e.g., 5G gNBs.2025PF00152

[0224] 24

[0225] The wireless access devices 1706 and / or 1707 may give access to one or more access and mobility functions (e.g., 1708 and / or 1709, e.g., 5G AMF) or other core network functions (e.g. SMF, PCF, N3IWF, AAA server) that may be in the same or different (cellular core) networks.

[0226] The access and mobility functions (e.g., 1708 and / or 1709, e.g., 5G AMF) may give access to multiple network functions in one or more core networks, e.g., a function for authentication and / or containing subscriber’s data, e.g., 5G AUSF / UDM, e.g., entities 1712 and / or 1713.

[0227] The access and mobility functions (e.g., 1708 and / or 1709, e.g., 5G AMF) may give access to one or more functions in one or more networks (e.g., 1710 and / or 1711) providing access to the data network 1714.

[0228] In Fig. 17, Fig. 18, and Fig. 19 the user plane of 1705 and 1702 is shown as a solid line, the control plane is shown as a dashed line. The traffic from / to 1702 is showed as thick lines, while the traffic from / to 1705 is shown as thin lines.

[0229] Fig. 17 shows a configuration in which both entity 1700 and entity 1703 are connected through the same wireless access device 1706. This means that if entity 1700 moves to the local network 1715, the ongoing connections of entity 1700 may still run through the same access device 1706.

[0230] Fig. 18 shows a further configuration in which entity 1700 connects to wireless access device 1707 and entity 1703 connects to wireless access device 1706 and both wireless access devices connect to the same access mobility function 1708 in the same network. This may mean that if entity 1700 moves to the local network 1715, the ongoing connections of entity 1700 may need to move from wireless access device 1707 to wireless access device 1706 and / or the ongoing connection may still run through 1707, but entity 1703 (1705) may need to connect to 1707.

[0231] Fig. 19 shows a further configuration in which entity 1703 connects to wireless access device 1706 and entity 1700 connects to wireless access device 1707. Furthermore, each of the wireless access devices connect to different access and mobility functions 1708 and / or 1709 in different networks 1716 and / or 1717. This may mean that if entity 1700 moves to the local network 1715, the ongoing connections of entity 1700 may need to move from network 1717 to network 1716, e.g., entity 1700 may need to register in network 1716. Additionally or alternatively, the ongoing connections of entity 1700 may remain in network 1717, but entity 1703 may need to connect to that network (e.g., through wireless access device 1707).

[0232] Fig. 20 shows a situation in which entity 1700 moved into the local network 1715 (from the situation depicted in Fig. 17 to the situation depicted in Fig. 20). In this case, only the user plane (e.g., data connection) may be re-routed through the local area interface(s) 1701 - 1704 while the control plane may still run through the cellular interface 1702.

[0233] Fig. 21 shows a situation in which entity 1700 moved into the local network 1715 (e.g., from the situation depicted in Fig. 17 / Fig. 18 / Fig. 19 to the situation depicted in Fig. 21). In this case, both the user plane (e.g., data connection) and control plane connection may be re-routed through the2025PF00152

[0234] 25

[0235] local area interface(s) 1701 - 1704. If entity 1700 was registered to network 1717, entity 1700 may need to register in network 1716 (used by entity 1703).

[0236] Fig. 22 shows a situation in which entity 1700 moved into the local network 1715 (from the situation depicted in Fig. 18 to the situation depicted in Fig. 22). In this case, only the user plane (e.g., data connection) may be re-routed through the local area interface(s) 1701 - 1704 while the control plane may still run through the cellular interface 1702.

[0237] Fig. 23 shows a situation in which entity 1700 moved into the local network 1715 (from the situation depicted in Fig. 19 to the situation depicted in Fig. 23). In this case, only the user plane (e.g., data connection) may be re-routed through the local area interface(s) 1701 - 1704 while the control plane may still run through the cellular interface 1702. Entity 1703 may need to connect to entity 1707 and / or register with network 1717.

[0238] Fig. 24 shows exemplary protocol stacks for the some of the entities in the system, e.g., in Fig. 17, including a wireless device such as a UE (1700 in Fig. 17) and a residential gateway (RG), 1703 in Fig. 17., which may connect to a base station through Fixed Wireless Access (FWA) and hance may also sometimes be called FWA device or FWA Consumer Premise Equipment. Fig. 24. a illustrates the control plane and Fig. 24.b illustrates the user plane. The protocols used in these exemplary protocol stacks are based on a 5G UE, however, this should not be considered as a limitation since other protocols providing similar functionality may also be applicable.

[0239] The protocol stack of the RG may be designed to act as a layer-2 relay for the traffic between the wireless device (UE) and the access device (gNB). This protocol stack may allow the wireless device to connect to the base station transparently through the RG. On the side of the local area network / customer premises network, the RG protocol stack may comprise a local area network protocol (e.g., non-3gpp, e.g., Wi-Fi, e.g., WLAN) and optionally an adaptation layer. On the side of the cellular network, the RG protocol stack may comprise the lower layers of the communication stack (Physical layer, MAC layer, and RLC layer) and potentially a further adaptation layer (e.g. similar or same as SDAP). The higher level protocols, e.g., for the control plane: PDCP / RRC / NAS and for the user plane PDCP / SDAP may be then transported transparently through the RG.

[0240] It is to be noted that the RG device may still have a full UE protocol stack for its normal communication with the access device, e.g., PDCP and RRC and NAS messages. The RG device may then connect to an access device and / or register with the core network. The access device may control the RG via NAS and / or RRC.

[0241] An access device (e.g., 1706 in Fig. 17) may control the RG (e.g. 1703 in Fig. 17) to transmit / receive traffic to / from the wireless device (e.g., 1700 in Fig. 17). This may be user plane traffic or control plane traffic. The access device may allocate resources to the RG depending on the traffic requirements of wireless device. The wireless device may still keep the control link (e.g., as indicated in Fig. 20 via Uu interface or as in Fig. 21) with the access device open (e,g, via 3GPP radio access technology) e.g., to transmit control signals to the access device, e.g., RRC messages, scheduling2025PF00152

[0242] 26

[0243] requests, etc. The access device, knowing the wireless device connects through the RG or is expected to connect through the RG (e.g. because the wireless device is getting in vicinity of the RG, or is requesting access via the RG through a handover request message or other message), may use input information received from the wireless device or the RG to:

[0244] control / adapt the communication link of the RG (e.g. based on traffic requirements or scheduling requests received from the wireless device), and / or

[0245] transmit a message / signal to trigger a wake-up of the RG (e.g. in case it was in a sleep mode), and / or

[0246] configure the RG with information related to the wireless device (e.g. to accept the connection of the incoming wireless device), and / or

[0247] configure the RG with information about how to adapt the link between the RG and the network if the wireless device connects to the RG.

[0248] For instance, the wireless device may send a control message such as an RRC scheduling message or LI resource allocation message or a LI scheduling request to the access device, the access device may then schedule resources for the communication link between access device and RG.

[0249] For instance, the access device may then use the allocated resources for the exchange of data from / to the wireless device.

[0250] For instance, the access device may also inform the wireless device directly about the allocated resources. In this way, the wireless device knows about the allocated resources, and may prepare the non-3GPP interface correspondingly. For instance, if the wireless device requested resources to transmit X bytes, and the wireless device receives a direct confirmation from the access device that Y bytes are allocated, the wireless device may then send a request through the transceiver of the local communication network to transmit Y bytes (e.g. if already connected to the RG).

[0251] A related embodiment of the invention illustrated by means of Fig. 25, that may be combined with other embodiments or used independently, describes an exemplary mobility procedure from a base station 2501 to the RG 2504 comprising a non-3GPP transceiver 2502 (e.g., Wi-Fi) and a 3GPP wireless transceiver 2503 (e.g., UE). In step 2505, the wireless device 2500 (e.g. UE) is connected to the base station 2501 (e.g., gNB) via, e.g., 5G Uu interface.

[0252] The wireless device 2500 may then move closer to the RG 2504. The wireless device may make measurements of the RG’s local area non-3GPP interface and it may report them to the base station. The wireless device may be configured to do so through means of a measurement configuration received from base station 2501, whereby the measurement configuration may include location / area information based on the RG’s location and / or one or more conditions to trigger measurements when the wireless device gets in vicinity of the RG. The measurements may be measurements of the signal strength, network ID (e.g., SSID), base station it is connected to. In particular, the RG may forward all / or part of the information about UE 2500 and / or 3GPP access device 2501 it is connected to, e.g., all or part of MIB, SIB1, e.g., cell ID, PLMN, etc. Additionally or alternatively, the wireless device 2500 may use the2025PF00152

[0253] 27

[0254] measurements itself e.g. to determine whether it is close enough proximity of the RG, and to predict a good moment for handing over (part of) its connection to the RG 2504.

[0255] The access device 2501 may have configured wireless device 2500 with a set of conditions determining whether the wireless device 2500 may join / attempt to join and / or leave RG 2504 and / or more generally to connect via non-3GPP access to the core network. The conditions may comprise one or more of:

[0256] Location (where the wireless device is located),

[0257] Signal strength (of the RG or a 3GPP access device),

[0258] SSID / network identifier (of the RG or 3GPP access device),

[0259] Security level,

[0260] Time / date (when the connection is allowed),

[0261] Context (e.g., energy level,... when the connection is allowed),

[0262] QoS requirements (e.g. whether or not certain interruptions are allowed / possible given the services requested / used by the UE, for example to cater for connection setup via the RG and / or non-3GPP access function (e.g. ePDG or N3IWF).

[0263] When measurements performed by the wireless device match one or more of the provided conditions and / or information obtained by the wireless device (e.g. from the network or predicted by the wireless device) from the RG, base station, non-3GPP access gateway matches or fulfuils one or more of the provided conditions (e.g. SSID matches an SSID / network identifier in a condition), the wireless device may connect / associate (or alternatively, disconnect / stop association) to the RG (and / or more generally to connect via non-3GPP access to the core network) through the non-3GPP interface.

[0264] The access device 2501 (and or network / core network) may have provided wireless device 2500 with a set configurations determining how some communication flows are to be rerouted, if connected to an RG. The configurations may comprise one or more:

[0265] Whether control plane remains over the 3GPP interface and / or moves to the non-3GPP interface (or the other way around),

[0266] Whether user plane remains over the 3GPP interface and / or moves to the non-3GPP interface (or the other way around),

[0267] Which data connections (e.g., PDU sessions) are transferred,

[0268] Whether packet / frame (e.g. PDCP, MAC) duplication may be used, and how long, Whether the wireless device acts as a non-3GPP device (i.e. solely connects to the RG through non-3GPP access (e.g. Wi-Fi), but not connect to a non-3GPP access function (e.g. ePDG or N3IWF), or acts as a 3GPP device (e.g. can be identified and authenticated as such) connecting to a non-3GPP access function (e.g. ePDG or N3IWF)2025PF00152

[0269] 28

[0270] This embodiment may also allow for the conditional setup of a multipath link between a remote UE and the network via a UE to Network relay (whereby the RG may act as a UE to Network Relay). The access device 2501 may indicate to the wireless device 2500 that one or more communication flows / sessions / data connection of wireless device 2500 will be transferred to the RG, e.g., either directly, or after initial duplication, so that wireless device 2500 receives said communication flows via the RG 2504. This may include indicating the communication flows, the timing of the transfer, whether they will be initially duplicated (e.g., as a multipath relay) and later only forwarded via RG 2504.

[0271] In an embodiment of the invention that may be combined with other embodiments or used independently, the access device 2501 may indicate to the wireless device 2500 that one or more communication flows / sessions / data connection of wireless device 2500 will be transferred to the RG (or more generally through non-3GPP access), e.g., either directly, or after initial duplication, so that wireless device 2500 receives said communication flows via the RG 2504. This may include indicating the communication flows (e.g. a set of QoS flow identifiers), the timing of the transfer, whether they will be initially duplicated (e.g., as a multipath relay) and later only forwarded via RG 2504.

[0272] Additionally or alternatively, the timing of the transfer, which communication flows get transferred / duplicated may be decided by the wireless device based on the set of configurations provided by the network (as described in other embodiments).

[0273] Wireless device 2500 may connect to RG 2504 via its non-3GPP transceiver creating link 2506. The base station may also enable and / or configure communication bearers 2507 between access device 2501 and RG 2504 for the communication flows used to transport the traffic from / to wireless device 2500.

[0274] Once established, the base station can start forwarding communication flows, e.g., at PDCP layer following the exemplary protocol stack in Fig. 24 towards RG 2504.

[0275] The adaptation layer may determine that the traffic carried by certain communication bearers is to be forwarded towards wireless device 2500 via the non-3GPP transceiver. This may be done by using an adaptation layer to this non-3GPP communication stack. At this stage, all the traffic or selected traffic may be transmitted via communication link 2508.

[0276] Additionally or alternatively, the decision of which traffic gets transferred via non-3GPP or 3GPP access may be configured at the wireless device by the core network through a set of WLAN Selection Policy or similar policy rules.

[0277] In an embodiment of the invention that may be combined with other embodiments or used independently, the wireless device may be configured with a set of policies (e.g. WLAN selection policies, QoS policies / rules, Access Traffic Steering, Switching, and Splitting (ATSSS) rules) that may include a set of latency related information / conditions and / or connection setup delay related information / conditions. This may include information / conditions related to an expected / minimum / maximum (end-to-end) latency and / or a related threshold when communicating over non-3GPP access (possibly in relative terms to 3GPP access, e.g. 1ms longer), and / or2025PF00152

[0278] 29

[0279] information / conditions related to an expected / minimum / maximum delay and / or a related threshold to establish a (new) connection via non-3GPP (e.g. to the RG and / or to a non-3GPP access function (e.g. ePDG orN3IWF).

[0280] Such delay to establish a connection via non-3GPP access may lead to an interruption of a communication service (e.g. phone call), e.g. if the underlying connection (e.g. via 3GPP RAT) of the communication service may have deteriorated and / or have broken before the connection via non-3GPP access was established. Therefore, the communication setup delay needs to be taken into account during handover decisions (e.g. initiate handover procedure some time before the quality of the underlying connection (e.g. via 3GPP RAT) has deteriorated too much, and / or to determine the best time to switch the transmission of packets / frames (and / or start buffering, emptying the buffer or flushing the buffer) related to the communication service from the 3GPP RAT connection to non-3GPP access connection and vice versa.

[0281] The latency and / or connection setup delay may be measured and / or predicted by the wireless device (e.g. after connection via non-3GPP has been established), and / or the wireless device may receive information (e.g. from the RG or from anon-3GPP access function (e.g. ePDG orN3IWF) or other network function or base station) based on which it can determine the (expected / additional) latency and / or connection setup delay.

[0282] Based on the above mentioned policies / conditions and / or the measured or obtained information related to latency and / or connection setup delay, the wireless device may determine whether or not to establish a connection via non-3GPP radio access technologies (e.g. establish Wi-Fi connection with a nearby RG) and / or register with the core network via non-3GPP access (e.g. with / via ePDG or N3IWF), possibly in addition to having / keeping an ongoing connection via 3GPP radio access, or possibly instead of a 3GPP radio access connection (e.g. in case of handover), and / or

[0283] which traffic streams and / or which services to setup / transfer / offload via non-3GPP radio access technology, possibly in addition to traffic streams and / or services over 3GPP access, or possibly instead of traffic streams and / or services over 3GPP access (e.g. in case of ATSSS).

[0284] Using these policies allows the wireless device to compensate for the delay and / or select a different radio access technology for certain services / traffic streams or handover and / or stay connected a bit longer via 3GPP radio access and / or reject a proposed handover.

[0285] Additionally or alternatively, the wireless device may receive (conditional) handover information / conditions from a base station through 3GPP connection (or tunneled via the RG) or directly from the RG that includes information related to connection setup delay (e.g. expected delay to establish a new connection via non-3GPP) and / or handover delay / interruption (e.g. expected delay to complete a handover procedure between 3GPP connection and non-3GPP connection), whereby the information / conditions may be adapted or may have separate values based on whether the wireless device acts as a non-3GPP device (i.e. solely connects to the RG through non-3GPP access (e.g. Wi-Fi), but not2025PF00152

[0286] 30

[0287] connect to a non-3GPP access function (e.g. ePDG or N3IWF), or acts as a 3GPP device (e.g. can be identified and authenticated as such) connecting to a non-3GPP access function (e.g. ePDG or N3IWF).

[0288] The connection setup and / or handover delay information / interruption information as provided in the (conditional) handover information and / or policies may be based on connection setup and / or handover delays / interruptions measured by one or more wireless devices or RGs. In order to facilitate this, a base station or Core Network (e.g. base station or NF such as ePDG or N3IWF) or the RG may instruct wireless devices to measure connection setup delay and / or handover delay / interruption, and / or to provide information about a measured connection setup and / or handover delay / interruption to the base station / core network / RG. Similarly, information about end-to-end latency of the connection via non-3GPP access may be measured and provided to the base station / core network / RG.

[0289] Additionally or alternatively, an Al model (e.g. on the wireless device) is used to predict an expected connection setup or handover delay / interruption, and / or expected latency related to the non-3GPP connection. The Al model can be trained by the measurements of connection setup or handover delays / interruptions experienced by one or more wireless devices (e.g. wireless devices in similar location / area, or wireless devices connecting to the same RG or ePDG / N3IWF). The Al model may be provided to the wireless device (e.g. after it was sufficiently trained) and / or the wireless device may be given access to the Al model (e.g. if it runs on a server in the network) to obtain the predicted connection setup or handover delay / interruption and / or latency. Additionally or alternatively, the connection setup delay information and / or handover delay / interruption information as received or determined by the wireless device may include information about whether a re-authentication of the wireless device is expected to be performed or not.

[0290] In some situations, a given home network / customer network may have two or more non-3GPP access devices, e.g., FWA devices, Wi-Fi router, Wi-Fi range extenders, etc. When a user (carrying his wireless device / UE) gets close (but still far) to the home network (e.g., when the user is walking towards the home), the wireless device may first receive signals / measure a first FWA devices, e.g., a device that is in an upper floor. When the user / wireless device is very close, the wireless device may still receive signals / measure the first FWA device, but the wireless device may then receive another FWA device better, e.g., the main router in the ground floor. A problem is that the wireless device / UE may have already started a handover procedure from the 3GPP to non-3GPP access via the first FWA device, and as a result, the quality of the communication drops.

[0291] To address this problem, in an embodiment of the invention that may be combined with other embodiments or used independently, the wireless device may report measurements of one or more FWA devices together with measurements of 3GPP access devices so that the network (e.g., an access device and / or network function in the core network) can determine which FWA devices may provide a reliable connection, e.g., when, where, or under which circumstances. For instance, in previous scenario, the network may know (have collected data) that the detection of the signal of the first FWA device is a trigger to actually connect to the second FWA device, and not the first FWA device. The network may2025PF00152

[0292] 31

[0293] use the collected data to predict / indicate the best FWA device to connect to and / or the timing to connect to and / or perform the handover.

[0294] In some examples, the configuration available at a wireless device (i.e., configuration received by the wireless device from an access device) may comprise one or more connection / measurement patterns in a policy that the wireless device may use to select a FWA device. For instance, a connection / measurement pattern may be:

[0295] Time 0: Measure first FWA device with weak signal

[0296] Time 1 : Measure first FWA device with medium signal and measure second FWA device with strong signal

[0297] Time 2: Connect to second FWA device

[0298] Such a connection / measurement pattern in the policy provides an indication and / or rules to the wireless device about the timing to connect and / or the device to connect. For instance, upon detection of first FWA, the wireless device should not trigger the (conditional) handover from the 3GPP access towards the first FWA device, but the wireless device wait a given time (that may be part of the policy, in this case Time 2 - Time 0) and then perform the handover towards the second FWA device.

[0299] It is to be noted that in the procedure in Fig. 25, wireless device 2500 may remain connected to the same base station that resembles the transition from Fig. 17 to Fig. 20 and / or 21. This means that the UE may not perform an actual handover (changing base stations). This may be required, however, in other cases, related to Fig. 18 and / or 19. However, in the procedure in Fig. 25, wireless device 2500 may only remain connected through the higher layers (PDCP / RRC / SDAP). Lower layers may remain “dormant”, e.g., RNTIs may not be used.

[0300] In an embodiment of the invention that may be combined with other embodiments or used independently, wireless device 1700 (e.g., as in Fig. 18) may make measurements of the RG 1703 and report them to its access device 1707, but access device 1707 may not be aware of the residential gateway 1703. An option may be to report the measurements to a network function / entity that may be aware of the / all RG in the area, e.g., the 5 G AMF. Such an entity may then indicate which base station is managing / providing connectivity to the RG. The wireless device may then perform a handover operation towards that base station, and then the procedure in Fig. 25 could be executed. In another option, a SIB may provide an indication of which RGs are used under which access device. Such an SIB may be transmitted periodically or on demand. This indication may also be received via RRC signalling.

[0301] In an embodiment of the invention (related to the operation in Fig. 18) that may be combined with other embodiments or used independently, wireless device 1700 may connect to the non-3GPP transceiver / interface and send an RRC command towards base station 1706 managing RG 1703. This may be feasible using the protocol stack in Fig. 24, whereby the RRC messages / PDCP (or other type of 3GPP frames / messages) may be encapsulated in IP packets as payload / MSDUs as 802.11 MAC frames, whereby a dedicated protocol identifier may be used to indicate the type of 3GPP message (e.g. PDCP indicated as EtherType 0x9E65, similar to clause 22A.1.2 of 3GPP TS 36.300 ). Base station 17062025PF00152

[0302] 32

[0303] may report back its identity, e.g., in an RRC message. Wireless device 1700 may report this identity to base station 1707 that may then communicate with base station 1706 and trigger a handover procedure from cell 1707 to cell 1706. Additionally or alternatively, the handover procedure may be triggered by wireless device 1700 via the RRC command described before.

[0304] In an embodiment of the invention (illustrated by means of the protocol stack of Fig. 24, where the non-3GPP communication link between the wireless device (UE) and RG may be Wi-Fi based) that may be combined with other embodiments or used independently, a root key used to protect the non-3GPP communication link between the non-3GPP communication link of the wireless device (UE) and the non-3GPP interface of the RG. The root key may be derived from, e.g., the current security context, e.g., the current AS security context of the wireless device (UE). For instance, next to the keys to protect the UP and CP traffic, i.e., PDCP and SDAP and RRC protocols, the wireless device (UE) may derive K_L2. The same key may be derived by the base station (gNB). The base station (gNB) may provide the RG with this key K_L2 in a secure manner. For instance, since the RG has a UE with a secure RRC connection, the key K_L2 may be sent to the UE of the RG via RRC. The RG may then use K_L2 to protect the non-3GPP interface when used to exchange traffic with the UE. For instance, K_L2 may be used to derive other keys for the non-3GPP interface, protect the communication link, authenticate the communication link, etc.

[0305] In an example, key K_L2 may be derived taking as input a root key (e.g., AS security root key, e.g., 5G KgNB) and the identity of the RG. This ensures that different RGs under the same access devices are allocated different keys K_L2, so that the wireless device can differentiate them.

[0306] In an example, key K_L2 may be derived taking as input a root key (e.g., AS security root key, e.g., 5G KgNB) and a freshness parameter, e.g., UTC time. This ensures that if a same wireless device connects multiple times to the same RG, different keys K_L2 will be generated.

[0307] In an example, key K_L2 may be derived taking as input a root key (e.g., AS security root key, e.g., 5G KgNB) and a session ID. This may be required, e.g., when a wireless device connects and the AS security context (e.g., AS security root key) remains unchanged for long time. This may allow the wireless device / access device to derive a fresh K_L2 without updating the AS security context.

[0308] It is to be noted that this embodiment and the way of deriving keys for the non-3GPP communication link may be applicable to other scenarios, e.g., the L2 multi-path relay using non-3GPP access in the indirect path as in TS 38.300 Clause 16.21.2.2.

[0309] In an embodiment of the invention that may be combined with other embodiments or used independently, the AS security keys used between a wireless device and access device to communicate via a residential gateway (RG) may be different than the AS security keys used between a wireless device and access device to communicate directly. In a normal situation, given the AS security root key, e.g., 5G KgNB, keys for the protection of PDCP / SDAP / RRC messages are derived. In particular, an encryption and an integrity key. According to this embodiment, different encryption / integrity keys used to protect the PDCP / SDAP / RRC messages may be derived depending2025PF00152

[0310] 33

[0311] on whether the PDCP / SDAP / RRC messages between wireless device / access device are transmitted via the RG or directly. This embodiment may be advantageous to make sure that traffic cannot be retransmitted through different interfaces. This embodiment may be advantageous to make sure that, e.g., if the RRC control traffic is exchanged directly, is not routed through the RG.

[0312] In an embodiment of the invention that may be combined with other embodiments or used independently, the RG may be configured to only allow control plane traffic (e.g., RRC messages) and / or user plane traffic (e.g., PDCP messages).

[0313] In an embodiment of the invention that may be combined with other embodiments or used independently, the RG may indicate its identity and / or other information as in other embodiments, e.g., via an EAP message, e.g., EAPRequest / identity. This message may only be used to convey the identity of the RG, in particular, its non-3GPP interface. The wireless device (UE) receiving it may report it (e.g., via Uu interface) to the 3GPP access device / base station.

[0314] In an embodiment of the invention that may be combined with other embodiments or used independently, the RG may indicate its identity and / or other information as in other embodiments, e.g., via a Wi-Fi beacon. The wireless device may have been configured (via the 3GPP wireless access) with information about the beacon (e.g., SSID), so that the wireless device may monitor such an RG upon reception of the beacon. The reception of a suitable beacon (e.g., with the correct SSID) with suitable information and suitable measurements (e.g., strong received signal) may trigger the association procedure, e.g., transmission of a probe request, and / or exchange of authentication messages.

[0315] In an embodiment of the invention that may be combined with other embodiments or used independently, if a wireless device (UE) has derived / obtained a root key to protect the non-3GPP communication interface with the non-3GPP communication interface of the residential gateway, and the residential gateway has also obtained such a root key, the wireless device and residential gateway may run a protocol such as the authentication procedure in 802.11 based on / taking as input the root key.

[0316] In an embodiment of the invention that may be combined with other embodiments or used independently, the AS security keys used to communicate via a residential gateway

[0317] In an embodiment of the invention that may be combined with other embodiments or used independently, if a wireless device (UE) has derived / obtained a root key to protect the non-3GPP communication interface with the non-3GPP communication interface of the residential gateway, and the residential gateway has also obtained such a root key, the wireless device and residential gateway may run a protocol such as IEEE 802.1 li key exchange protocol that may consist in the exchange of a number of messages

[0318] EAPoL-Key / ANonce (from RG to wireless device)

[0319] EAPoL-Key / SNonce (from wireless device to RG)

[0320] EAPoL-Key / Install (from RG to wireless device)

[0321] EAPoL-Key (from wireless device to RG).2025PF00152

[0322] 34

[0323] In an embodiment of the invention that may be combined with other embodiments or used independently, the wireless device may act as EAP peer, the RG may act as EAP authenticator, and the 3 GPP access device and / or a network function may act as authentication server.

[0324] In an embodiment of the invention that may be combined with other embodiments or used independently, the exemplary protocol stack described in Fig. 24 may also be used to enable a distributed residential gateway as described in other embodiments of the invention. For instance, as illustrated in Fig. 10, wherein devices 100 and 102 are two distributed residential gateway units connected to a same access device 104 and serving wireless device (UE) 107. In this case, the downlink (PDCP) messages may be exchanged with wireless device 107 via devices 100 and 102 by reserving / allocating data bearers with devices 100 and 102 to carry them. The (PDCP) messages may then be delivered to wireless device 107 from devices 100 and 102, e.g., based on the protocol stack in Fig. 24.

[0325] In an embodiment of the invention that may be combined with other embodiments or used independently, a wireless device (e.g., UE) may receive a validation token from a non-3GPP access device (e.g., a residential gateway unit) through the non-3GPP interface (e.g., Wi-Fi), wherein the token may validate the non-3GPP access device as capable of registering the wireless device in the wireless device core network and / or providing connectivity through the wireless device core network. The token may be, e.g., information about the non-3GPP access device signed by a trusted party, e.g., a signing authority in the cellular network / cellular core network. The information may contain parameters / identification parameters / etc about the non-3GPP access device. For instance, information may comprise some parameters as included in SIB 1. The wireless device may be configured with a digital certificate that may allow verifying the validation token (e.g., digital signature), e.g., by means of a certificate chain.

[0326] In an embodiment of the invention that may be combined with other embodiments or used independently, a wireless device (e.g., UE) may be able to transmit to and / or receive messages from a non-3GPP access device / residential gateway and an 3GPP access device, wherein the messages may belong to a single communication session. For instance, PDCP messages may be routed through the 3GPP access device and the non-3GPP access device / residential gateway (e.g., based on the protocol stack in Fig. 24) (PDCP duplication activated). This may be advantageous because it allows performing data aggregation and / or load balancing. This embodiment may be used, e.g., when performing a mobility procedure as in other embodiments, e.g., when performing a handover from the 3GPP access device to the non-3GPP access device / residential gateway. Once the handover is performed, such a PDCP traffic duplication may be deactivated.

[0327] In an embodiment of the invention that may be combined with other embodiments or used independently, the residential gateway (e.g., 2504 in Fig. 25) may receive a configuration from the 3GPP access device (e.g., 2501 in Fig. 25) and / or from a network function in the core network (e.g., AMF) determining how many wireless devices it can serve. This may be based on a subscription, e.g., the subscription of the residential gateway and / or the capabilities of the residential gateway.2025PF00152

[0328] 35

[0329] In an embodiment of the invention that may be combined with other embodiments or used independently, a wireless device (e.g., UE, e.g., 107 in Fig. 11) may be able to transmit to and / or receive messages from a first non-3GPP access device (e.g., a first residential gateway unit, e.g., 100 in Fig. 11) and a second non-3GPP access device (e.g., a second residential gateway unit, e.g., 102 in Fig.

[0330] 11). The messages may belong to a single communication session. This may allow performing, e.g., data aggregation and / or load balancing. The 3GPP access device (e.g., 104 in Fig. 11) may configure 100 and 102 (e.g., via RRC signaling, e.g., RRCReconfiguration message) data bearers to transport higher level messages, e.g., PDCP messages.

[0331] In an embodiment of the invention that may be combined with other embodiments or used independently, a wireless device (e.g., UE, e.g., 2500 in Fig. 25 or 1700 in Fig. 21) may have a first subscription S_A, while the residential gateway (e.g., RG 2504 in Fig. 25 or 1703 in Fig. 21) may have a second subscription S B. In some cases S A may be superior to S B (S A > S B) and in some cases S_B may be superior to S_A (S_A < S_B). A subscription is superior when it allows achieving a higher QoS, e.g., higher data rate, lower latency, is entitled to more data, etc. In this embodiment, when the wireless device 1700 moves to the local network (e.g., 1715 as in Fig. 21), wireless device can keep the properties of its subscription, e.g., higher data rate. For instance, if the residential gateway is entitled to a max. Downlink speed of 1 Gb, and the wireless device has a maximum downlink speed of 2 Gb, the wireless device may still keep this speed in the local network. In an example, while the wireless device is in the local network, the residential gateway may handle a max. Downlink speed of 1 + 2 Gb (i.e., the addition of the maximum downlink speeds) so that the wireless device can keep its QoS and other devices in the local network can be served as well. To achieve this functionality, the core network (e.g., serving network) may be able to determine the identity (e.g., long-term identity) of the wireless device(s) connecting through the local network, a network function in charge of mobility and access (e.g., 5G AMF) may retrieve / request the capabilities of the wireless device, and may inform about them to the radio access network and / or residential gateway. The network function may also interact with other network functions in charge of management of policies (e.g., 5G PCF) and / or a function in charge of managing the communication sessions (e.g., 5G SMF) that may reconfigure the residential gateway and / or steer the communication sessions according to the required capabilities / QoS of the wireless device. The radio access network (e.g., base station) may use the configuration to determine the amount of data bearers that may be configured / required to be setup with the residential gateway to handle the traffic of the wireless device. The residential gateway may also report information about the local network (e.g., available capacity) so that RAN can determine whether the traffic can be routed via the residential gateway. If the whole traffic cannot be routed through the residential gateway (e.g., because the local network cannot route all that traffic), the traffic may also be routed (1) partially via the residential gateway and (2) partially via the direct 3GPP communication link with the wireless device (e.g., Uu interface in 5G). The first route (1) may be RAN — (Uu interface of RG) — > RG — (local2025PF00152

[0332] 36

[0333] communication) — > Wireless device. The second route (2) may be RAN — (Uu interface of wireless device) — > Wireless device.

[0334] Section: Identification behind a 5G-RG via sidelink

[0335] The 5G-RG is defined in TS 23.501. A 5G-RG allows a device to access the 5G core network playing the role of a UE. The 5G-RG may access the core network via a 3GPP RAN or wireline. Then the UE 5G-RG may provide connectivity to other devices in the area, e.g., in the home (network). A 5G-RG is a device that can enable other devices to access the 5G core network and its services, such as IMS or Internet, by acting as a relay. For example, a 5G-RG may be installed in a home or office environment and provide wireless connectivity to other devices via WiFi, Bluetooth, or Zigbee. These devices may include smartphones, tablets, laptops, smart TVs, smart speakers, or loT sensors. The 5G-RG may also support different types of access networks (towards other devices), such as 3GPP (e.g., LTE, NR), non-3GPP (e.g., DSL, Ethernet), or hybrid (e.g., LWA, LWIP). The advantage of using a 5G-RG is that it can offer seamless and secure access to the 5G core network and its features, such as network slicing, QoS, policy control, charging, mobility management, or identity management. The 5G-RG can also optimize the traffic routing and the radio resource utilization by selecting the most suitable access network for each device and service. Furthermore, the 5G-RG can enhance the user experience and privacy by allowing the devices to use their own credentials and profiles when accessing the network through the relay. As already discussed, a challenge is how to identify a device behind this 5G-RG, e.g., a UE that may be in the area and may rely on the connectivity offered by the 5G-RG via a non-3GPP protocol, e.g., WiFi, instead of the 3GPP connectivity of the UE itself. For this case, the core network may still desire to identify the specific UE that is being served through the 5G-RG since then the communication profile of the UE (or user associated to the UE) may be used or applied to the 5G-RG. This may be achieved by means of embodiments as follows:

[0336] In an embodiment that may be combined with other embodiments or used independently, the 5G-RG may act as a UE-to-Network relay announcing its capabilities or being discoverable as a 5G-RG. A UE (e.g., associated to the environment / home network) may have the credentials to monitor or discover said 5G-RG. Upon discovery, the UE may send a Direct Communication Request to the 5G-RG to establish a security communication with the core network through the 5G-RG acting UE to Network relay. The core network may then authorize the communication, and the core network may then become aware that the specific UE is getting connectivity through the 5G-RG where the data connection between the 5G-RG and UE may not be 3GPP-based, but non-3GPP based, e.g., WiFi based. This may allow the core network to associate the UE profile, or a given user profile associated to the UE with the communication provided through the 5G-RG. For instance, the 5G-RG may enable a WiFi connection with the UE, and the 5G-RG may then link the communication data received through the WiFi connection with the communication profile of the identified UE / user.2025PF00152

[0337] 37

[0338] In an embodiment that may be combined with other embodiments, e.g., previous one, the non-3GPP communication link between UE and 5G-RG may be considered as the user plane communication link while the 3GPP communication link between UE (remote UE) and 5G-RG (UE-to-Network relay) may be considered as the control plane. The communication link between UE and 5G-RG may be identified based on, e.g., the L2 address of the UE networking technology, e.g., WiFi.

[0339] In an embodiment that may be combined with other embodiments, e.g., previous one, the 5G-RG may use a secure communication link established with a UE, where the UE acts as remote UE and the 5G-RG acts as a UE-to-Network relay, to provide the UE with credentials for the non-3GPP connectivity technologies in a secure way, e.g., a WiFi password.

[0340] In an embodiment that may be combined with other embodiments, the discovery procedures may be based on other discovery types, e.g., direct discovery.

[0341] In an embodiment that may be combined with other embodiments, a UE may be provisioned with credentials enabling the access to the 5G-RG, e.g., the 5G-RG may include a QR code that allows a UE to scan it and be directed to the PKMF or DDNMF so that it can be provisioned with corresponding credentials, e.g., discovery keying materials, that may then be used for the discovery / access of the 5G-RG, and later access to the core network.

[0342] Section: Redistribution of credentials

[0343] In a further embodiment that may be combined with other embodiments or used independently, the first and the second UEs may be served by a 5G-RG as in other embodiments that may be subject to a given subscription. The 5G-RG may be connected through a 3GPP RAN. When the connection between 5G-RG and the first UE and / or second UE may not be optimal in the home environment, e.g., due to a weak non-3GPP connection, the 5G-RG may be configured to provide (directly and / or indirectly) temporal credentials to either the first UE or the second UE so that they can directly access the core network through the 3GPP RAN. This configuration (e.g., determined by a policy) may determine how many devices may receive these credentials, the type of allowed communication, the communication features (latency, max. download / upload data rates,...), etc. This may involve distributing or assigning certain credentials (e.g., an access token, or temporary root credentials, etc) that allow the first and / or second UEs to access the core network to obtain direct access.

[0344] For instance, assume that the first and second UE are associated with a 3GPP subscription that allows up to 1 mbps download speed while the 5G-RG allows up to 2 mbps download speed. If the 5G-RG determines that this speed cannot be achieved because of the non-3GPP communication link between 5G-RG and the first and / or second UEs, the 5G-RG may share said temporary credentials so that the first and / or second UEs can achieve said download speed. Other communication key performance indicators, next to download speed, may also be applicable, e.g., upload speed, latency, QoS, etc. The credentials may identify the first and / or second UEs as members of the network served by the 5G-RG.2025PF00152

[0345] 38

[0346] For instance, Fig. 8 illustrates an embodiment that may be combined with other embodiments or used independently, of a home network including a 5G-RG 100 that is connected to two base stations 103 and 104. The 5G-RG 100 serves two wireless devices 106 and 107 by means of local connectivity, e.g., WiFi. In this situation, the 5G-RG determines that one of the devices, 107, cannot be allocated with the required resources to achieve the desired QoS. Thus, Fig. 9 illustrates a subsequent step in which 5G-RG 100 transfers / allocates or requires the transference or allocation of credentials in Step 108. The credentials of the 5G-RG are illustrated by 109 and the credentials assigned to device 107 are illustrated by 110. The transfer may be direct from device 100 to device 107, or it may via a different channel. In the direct case, the credentials may be securely shared via local communication interface, or via an out of band channel, e.g., a QR code that may be scanned by device 107. Additionally or alternatively, device 100 may request the creation of the credentials for device 107 to the core network of the telecommunication system, and the credentials may be deployed to device 107 via its own (cellular) connection, if it has an active (cellular) connection. Once device 107 has received these credentials, device 107, may use them to directly access the RAN of the telecommunications system, in this case, device 107 accesses base station 104 in step / messages 109.

[0347] In a further embodiment that may be combined with other embodiments or used independently, the transfer of credentials may be the other way around, e.g., from UE 107 or residential gateway 100. This may be applicable, e.g., when a user with UE 107 moves to a new environment (e.g., hotel, rental house, etc) with a residential gateway and the user may not trust the connection provided in the new environment or the performance may not be sufficient. In this case, the user may trigger the transfer of part of the credentials of his UE 107 to residential gateway 100 so that the residential gateway provides local connectivity (LAN, WLAN, etc) based on those credentials. For instance, a user may use its UE to request new credentials, e.g., cellular credentials, to the operator. The user may create a trigger to deploy the credentials. For instance, the user may use his user equipment to create a token and / or code (e.g., QR code) that may be scanned / obtained by and / or provided to a residential gateway. The residential gateway may then use such token and / or code to retrieve the credentials. These credentials may be linked to metadata and / or a configuration that determine the conditions for its usage, e.g., location, time, type of data, etc. For instance, the credentials may only be used when the user’s UE is in close proximity.

[0348] In a further embodiment that may be combined with other embodiments or used independently, the credentials that may be distributed from a residential gateway (e.g., as in previous embodiments) to a user equipment may be valid in a given context. In an example, the context may refer to an area close to the area served by the residential gateway (e.g., in the same home network / local area network). In another example, the context may refer to a time window during which the credentials are valid. In another example, the context may refer to the execution of a given communication task, e.g., watch a given movie with certain quality of service / quality of experience. Multiple context criteria may be considered in combination and may be received by the user equipment as a configuration, e.g., a configuration linked to the received credentials.2025PF00152

[0349] 39

[0350] Section: Distributed residential gateway

[0351] The capability of sharing the credentials of a 5G-RG may lead to a concept of a distributed residential gateway wherein two or more devices may connect to the RAN of the telecommunications system to provide connectivity to the “residence”. For instance, a user may get a new subscription and receive or buy two or more access points that may act as a (distributed) residential gateway if configured with suitable credentials and be capable of connecting to the RAN of the telecommunications system (e.g., 5G RAN) and provide local wireless connectivity (e.g., Wi-Fi) to local devices or as wireless repeaters using the local wireless connectivity technology (e.g., Wi-Fi) to communicate with configured residential gateway and provide local wireless connectivity (e.g., Wi-Fi) to local devices.

[0352] In an embodiment of the invention that may be combined with other embodiments or used independently, a first (distributed) residential gateway unit may provide access to a data network (DN), e.g., the internet, and the residential gateway unit may comprise:

[0353] an interface for receiving a Universal Integrated Circuit Card / subscriber identity module (SIM) card / an eSIM / universal SIM (USIM comprising an identifier associated with at least one of a subscriber and a residential gateway unit;

[0354] a local area network (LAN) interface (e.g., Wi-Fi or Ethernet) for receiving DN access through a second residential gateway;

[0355] a wireless access interface (e.g., 4G, 5G, 6G, etc) for connecting to the DN wirelessly directly through a wireless access infrastructure;

[0356] wherein if the UICC / SIM / eSIM / USIM (terms can be used interchangeably) is provided to the wireless access interface providing and / or configuring credentials for the wireless access interface, the wireless access interface is adapted to connect to the core network of a cellular system to receive DN access. This embodiment means that if the first (distributed) residential gateway unit is not configured with the credentials for the wireless access interface, then the first (distributed) residential gateway receives access through the second residential gateway, but if it is provided with the credentials, it receives access through the wireless access interface (e.g., cellular, 4G, 5G, 6G, etc).

[0357] In embodiments of this invention, a Universal Integrated Circuit Card and / or subscriber identity module (SIM) card and / or an eSIM and / or USIM may refer to means to provide credentials to a distributed residential gateway unit. These terms may be used interchangeably.

[0358] In embodiments of this invention, when a distributed residential gateway unit receives access through the local area network (EAN) interface, it may receive access directly from another distributed residential gateway unit, and / or through a mesh network.

[0359] In embodiments this invention, a distributed residential gateway unit may receive access through the local area network (LAN) interface, and additionally, the distributed residential gateway unit may communicate with each other by means of other communication means, e.g., powerline.2025PF00152

[0360] 40

[0361] For instance, Fig. 10 shows such a distributed residential gateway comprising three units 100, 101 and 102 where each of the units have the required credentials, and thus, can connect to the RAN of the telecommunications system, in this case, base stations 103, 104, and 105. This concept of distributed residential gateway allows a device (e.g., 106 in Fig. 10) to be served by two or more units (e.g., 100 and 101 in Fig. 10) of the distributed residential gateway, where each of those units is directly connected to the RAN of the telecommunications system (e.g., 103, 104 and 105 in Fig. 10).

[0362] It is to be noted that a unit of a distributed residential gateway, e.g., the first one that becomes active may share relevant credentials and / or trigger the sharing of relevant credentials with other 3GPP devices, e.g., a user equipment (Case (1)) or another distributed residential gateway unit (Case (2)) as described in other embodiments of the invention. Case (1) may happen when the user equipment is in the local area (e.g., home network) and may have bad connectivity due to the local area communication technology (e.g., Wi-Fi) so that it receives credentials from the distributed residential gateway to access the cellular network directly. Case (2) may happen when the user decides to activate another distributed residential gateway to provide better connectivity in the local area (e.g., home network). It is to be noted that a wireless device may be a 3GPP device such as user equipment or a Wi-Fi device, etc. In this case, the devices that may received credentials may be devices such as 3GPP devices, e.g., as user equipments.

[0363] In an embodiment that may be combined with other embodiments or used independently, one or more units of the distributed residential gateway may need to allow scheduling traffic related to a given device, this means that the telecommunications system (e.g, RAN) may need to know that / consider the different (distributed residential gateway) units are parts of a single entity. For instance, when one of the units (e.g., 103 in Fig. 10) registers in the telecommunication systems and may perform the primary authentication, the unit may be authenticated as part of the distributed residential gateway. These capabilities may be checked against the subscription. The (home) network may configure the (serving) network functions with relevant parameters, e.g., related to communication parameters, communication sessions served (e.g., in the 5G SMF), and the network function handling the different communication sessions (e.g., 5G SMF) may control a user plane function (e.g., 5F UPF) to steer the traffic to and from one or more units of the distributed residential gateway so that a device served by the units of the distributed residential gateway can receive data through them.

[0364] In an embodiment that may be combined with other embodiments or used independently, the distributed residential gateway units may need to verify that they are in close proximity (e.g., providing access to a common local network / home network) to work in such a mode. In order to perform such a verification, the distributed residential gateway units may provide certain parameters (e.g., name of the network in the local area network, e.g., password of the network, ...) to the core network in a secure manner. This may allow the core network to verify that they are close by, and after confirmation, enable their operation. The distributed residential gateway units may also interact, e.g., through the local area network interface to verify that they are located close by, e.g., by exchanging a token and / or nonce.2025PF00152

[0365] 41

[0366] In an embodiment that may be combined with other embodiments or used independently, one of the units may play the role of master determining how the downlink / uplink traffic for a device is to be exchanged through the RAN of the telecommunication systems. For instance, in reference to Fig. 10, unit 100 may act as the master determining which traffic is received / transmitted by unit 100 and unit 101 with base stations 103 / 104 and 105 respectively. Said traffic is then exchanged with device 106 through the local wireless communication technology (e.g., Wi-Fi) wherein communication link 113 may be used to coordinate both units 100 and 101. This communication link 113 may be based on the local wireless communication technology (e.g., Wi-Fi) or may be based on the RAT of the telecommunication systems (e.g., be sidelink). Which unit plays the role of master may depend on a configuration and / or policy and / or context. For instance, a unit connected to the wireline may act as the default master. But a policy may determine that if more than x% of the traffic is handled by a unit or most of the devices are connected to a unit, the unit becomes the master unit, e.g., because it may then reduce the control signaling between the units (e.g., link 113).

[0367] In an embodiment that may be combined with other embodiments or used independently, a specific procedure of distributing traffic towards a given device through two or more units may be as follows. Device 106 may receive data from units 100 and 101. Unit 100 may be configured to provide data to 106 in the 2.4 GHz band and to 107 in the 5 GHz band. Unit 101 may be configured to provide data to 106 in the 5GHz band. Units 100 and 101 may be seen / considered as Access Points (AP) in a WiFi multi AP deployment wherein multiple APs are able to provide connectivity to one or more wireless devices. Units 100 and 101 may have agreed on this split by using link 113. Device 100 may actsas the master of the local network. The incoming traffic for device 106 is then to be split so that the telecommunication system sends part of it through unit 100 and part of it through unit 101. Unit 100 may interact with the RAN (operating cells 103, 104, and / or 105) and / or core network (e.g., AMF) indicating the current configuration with two active units in the distributed residential gateway, and indicating that unit 100 may consume a fraction x of the traffic and unit 101 may consume a fraction 1-x of the traffic. The core network (e.g., SMF) may then configure the communication sessions for the user plane function to be split accordingly. A way to split the traffic may be by setting up a multi-path communication link, e.g., using multipath TCP or multipath QUIC.

[0368] Fig. 11 schematically illustrates a procedure by means of which one of the units in the distributed residential gateway obtains credentials (e.g., an eSIM in a multiSIM package). Unit 100 may have determined that the RAN of the telecommunication system is not capable of providing the required throughput alone, e.g., because of the traffic conditions around base stations 103 and 104 and / or interferences. This may cause the transmission of a reconfiguration message 112 towards unit 101 so that unit 101 becomes active and starts using base station 105 to transmit / receive data, e.g., from / for device 106. This reconfiguration message may be a message sent through the local wireless technology and / or a communication interface of the telecommunication system (e.g., sidelink, Uu interface) 113. The reconfiguration message may involve one or more of:2025PF00152

[0369] 42

[0370] providing credentials to 101 so that it can connect to the telecommunication system as part of the distributed residential gateway and access 105,

[0371] activate 101 so that it connects to the network and access 105,

[0372] offload request that may include information regarding requested throughput / QoS, scheduling related information, frequency alignment information, ...

[0373] Additionally or alternatively, units 100 and / or 101 may also send messages 114 and 115 indicating to the RAN and / or core network of the telecommunication system the activation of a single unit and / or communication policy for the active units so that the incoming / outgoing traffic can be routed in a suitable manner.

[0374] In a related embodiment that may be combined with other embodiments or used independently, for instance, if a unit (e.g., 100) determines capacity / reliability / coverage issues, unit 100 may request the core network to activate another unit of the distributed residential gateway. The core network may check whether the subscription allows it, and it may trigger the activation of, e.g., unit 101, e.g., by sending a paging message. The core network may retrieve suitable policies (e.g., from a policy network function) and provide them to the unit, e.g., unit 101. The core network may control a network function managing the communication sessions (e.g., SMF) so that SMF is aware of the newly activated unit 101. Such a session function may then interact with an entity such as the UPF indicating that two units of the distributed residential gateway are active, so that traffic can be (re)routed accordingly.

[0375] In a related embodiment that may be combined with other embodiments or used independently, a distributed residential gateway unit (e.g., that is to be activated) may be requested to transmit measurements, e.g., measurements of pilot signals transmitted by the radio access network. Such measurements may provide the radio access network about the quality of the communication link, Quality of Service that may be achievable, etc. Based on the transmitted measurements, the radio access network may determine which of the units may provide the best connectivity, and activate it / them. The radio access network may provide a given schedule for the reporting of measurements, e.g., because the (distributed) residential gateway unit is a static device. This reporting may be less frequent than in standard (mobile) user equipment. Reporting may be triggered by a movement of the (distributed) residential gateway unit, e.g., due a change of position. Reporting may also be triggered when the unit and / or radio access network notice a change in the achievable performance.

[0376] In an embodiment that may be combined with other embodiments or used independently, in some cases, the distributed residential gateway may have a maximum number of units active at the same time, thus, the core network may verify whether the maximum number of units is reached, and not allow the activation of any further units.

[0377] When a UE is behind a 5G-Residential Gateway, Clause 7B. 4 in TS 33.501 indicates that when the UE uses untrusted non-3GPP access, the authentication of the UE is as specified in clause 7.2.1 and when the UE uses trusted non-3GPP access, the authentication of the UE is as specified in clause 7A.2.1. A residential gateway unit as described in this invention can be considered a UE when configured2025PF00152

[0378] 43

[0379] with the corresponding credentials, e.g., SIM or eSIM, and otherwise, a non-cellular device. Thus, in an embodiment that may be combined with other embodiments or used independently, when a first residential gateway unit is configured with credentials but it is not connected to the RAN of the cellular system (e.g., 5G RAN), the first residential gateway unit may connect to the core network of the cellular system via a second residential gateway unit that has credentials and is connected to the RAN of the cellular system. The first residential gateway may not connect directly to the cellular system / RAN because the first residential gateway may be dormant, e.g., or not active yet in the RAN. The second residential gateway unit can authenticate as a normal UE while the first residential gateway unit may authenticate, e.g., based on the procedure in clause 7.2.1.

[0380] In an option, when the first residential gateway unit may become connected, the first residential gateway unit may receive other set of credentials / configuration parameters that may allow it to connect to the cellular system through its RAN without needing to reperform the normal primary authentication procedure and using the communication parameters of the second residential gateway unit. As described in other embodiments / options, the first residential gateway may also use its own credentials that may be linked to the ones of the second residential gateway unit via a combined subscription.

[0381] This may be an authorization token provided by the (home / serving) network and that signs, e.g., the fact that the device is a residential gateway, the current AMF, validity period, or its current identity (e.g., GUTI). When the registration request reaches the AMF with this authorization token, the AMF may skip the triggering of the primary authentication, stop the connection to it via the first residential gateway unit and enable through the cellular RAN, e.g., by deriving AS keys. This way, the first unit 100 may avoid primary authentication and select the same AMF it is currently using when it switches from untrusted non-3GPP access to trusted non-3GPP access. This procedure may also be applicable in other settings.

[0382] In an option, the first residential gateway unit may be a regular UE that becomes a “temporary first residential unit” sharing the subscription of the residential gateway. The distribution of a token, e.g., as above, would be a secure way of telling the network that the two RGs are related. The first RG unit would be configured as a secondary station and therefore may need the token to connect to the cellular system as part of the distributed RG. Its own credentials, if any, might provide network access for another role.

[0383] In an embodiment that may be combined with other embodiments or used independently, there is a scheduler or load balancer that determines how much traffic and which traffic is received through wireline (if available) and / or through each of the residential gateway units. The scheduler may require receiving information from the residential gateway units so that they are aware of the quality of the cellular RAN links, the devices that connect to them, and the location of those devices. Based on this information, the scheduler may decide how to allocate the available bandwidth and resources among the different residential gateway units and the devices connected to them. For example, the scheduler may prioritize the traffic of some devices or applications over others, or may balance the load across the2025PF00152

[0384] 44

[0385] residential gateway units according to their connection quality or capacity. The scheduler may also adjust the allocation dynamically based on the changing network conditions or user demands. The scheduler may be located in one of the residential gateway units, or in a network node of the cellular system, such as the AMF, SMF, or UPF. Alternatively, the scheduler may be distributed across multiple nodes or units, and use a distributed algorithm or protocol to coordinate the traffic allocation. The scheduler may communicate with the residential gateway units and the network nodes through signaling messages or control plane data. The scheduler may also implement some security mechanisms to protect the communication and prevent unauthorized access or interference.

[0386] In an embodiment that may be combined with other embodiments or used independently, the (distributed) residential gateway unit may be adapted to provide the wireless access infrastructure (e.g., radio access network) with information about the communication parameters of the local area network (e.g., related to its LAN interface) when providing a device, e.g., a wireless access device, with access to a data network wherein the information may comprise one or more of:

[0387] frequency band, e.g., the frequency band used for communication in the local network, e.g., 2.4 GHz, 5 GHz, 6 GHz, etc

[0388] quality of the communication link, e.g., signal strength, data rate, modulation, error correction configuration, etc.

[0389] communication schedule, e.g., frequency of data exchanges, size of the data exchanges, etc bandwidth requirements, e.g., how much data is required by the wireless device,

[0390] path identifier, e.g., an identifier indicating a communication path, e.g., in a multipath communication protocol,

[0391] communication session identifier, and

[0392] device identifier, e.g., an identifier such as the MAC address that identifies the wireless device.

[0393] In an embodiment that may be combined with other embodiments or used independently, a (distributed) residential gateway unit may adapted to request and / or receive from the wireless access infrastructure and / or core network and / or another distributed residential gateway unit information about the communication parameters of the LAN interface and / or wireless access interface of one or more distributed residential gateway units wherein the information may comprise one or more of:

[0394] status of the interfaces (e.g., enabled, disabled),

[0395] frequency band of the LAN interface and / or wireless access interface (e.g., which frequency bands are enabled),

[0396] quality of the communication link of the LAN interface and / or wireless access interface (e.g., how fast and / or reliable the links are),

[0397] communication schedule of the LAN interface and / or wireless access interface (e.g., periodicity, communication length, DRX schedule, sleep period, etc),

[0398] bandwidth requirements and / or communication load of the LAN interface and / or wireless access interface (e.g., how much data is required),2025PF00152

[0399] 45

[0400] path identifier of the LAN interface and / or wireless access interface (e.g., identifiers of communication paths exchanged through the interfaces),

[0401] communication session identifier of the LAN interface and / or wireless access interface (e.g., identifiers of communication sessions), and

[0402] device identifier, e.g., an identifier such as the MAC address that identifies the wireless device.

[0403] In an embodiment that may be combined with other embodiments or used independently, a (distributed) residential gateway unit may provide another (distributed) residential gateway unit with information about the communication parameters of the local area network (LAN) interface and / or wireless access interface when providing a wireless device with access to a data network wherein the information may comprise one or more of:

[0404] frequency band of the LAN interface and / or wireless access interface,

[0405] quality of the communication link of the LAN interface and / or wireless access interface, communication schedule of the LAN interface and / or wireless access interface,

[0406] bandwidth requirements of the LAN interface and / or wireless access interface,

[0407] path identifier of the LAN interface and / or wireless access interface,

[0408] communication session identifier of the LAN interface and / or wireless access interface, and wireless device identifier of the LAN interface and / or wireless access interface.

[0409] In an embodiment that may be combined with other embodiments or used independently, the exchange of above information may allow routing the data through the most suitable link, e.g., through the wireless access interface and / or the LAN interface.

[0410] In an embodiment that may be combined with other embodiments or used independently, the invention may comprise one, two, or more control links that coordinate the communication when serving, e.g., devices 106 and 107 with, e.g., the residential gateway units 100 and 101 (in e.g., Fig. 11). The control links when serving device 107 via residential gateway units 100 and 101 served by access device 104 may be one or more of, e.g.:

[0411] a control link between device 107 and access device 104,

[0412] a control link between residential gateway 100 and access device 104,

[0413] a control link between residential gateway 101 and access device 104.

[0414] A first control link is responsible for assigning and managing which residential gateway units and with which communication resources are used to serve a device, e.g., 106, by means of the local communication technology (e.g., Wi-Fi based).

[0415] A second control link is responsible for selecting and controlling which residential gateway unit is used to download / upload which data with the core network where the data may be made available directly to a device (e.g., 106) or through another residential gateway unit.

[0416] The first control link may be local and can be realized via Wi-Fi or a cellular link, e.g., sidelink. The second control link may also be based on sidelink, or could also be based on Wi-Fi or the2025PF00152

[0417] 46

[0418] decision may be centralized, e.g., performed by the cellular RAN (e.g., the central unit of a base station) or a network function (e.g., SMF).

[0419] Both control links are also related, and thus, information may be exchanged about the control decisions in each of them. For example, the first control link may inform the second control link about the quality and availability of the local communication links and communication preferences of the devices, and the second control link may inform the first control link about the connectivity level (e.g., the coverage level, achievable uplink / downlink speeds, etc) and achievable quality of service.

[0420] The two control links may use different protocols or mechanisms to communicate and coordinate, such as signaling messages, control plane data, or data plane headers.

[0421] In an embodiment that may be combined with other embodiments or used independently, the invention describes a wireless sensing module and / or localization that can be integrated in the residential gateway units to determine the location of the devices and use that information to make decisions regarding which residential gateway unit serves which device, and how the resources are coordinated. Sensing may be based on the measurement reports (CSI) of reference signals provided by devices. Sensing may be based on a wireless sensing signals, e.g., chirp based. Localization may be based on round trip time and / or angle of departure / arrival, e.g., based on IEEE 802.1 laz. Residential gateway units may gather information from wireless sensing / positioning procedures and keep track of the devices. A residential gateway unit may act as master and control the distribution of reference signals and collection of measurements. For instance, in reference to Fig. 14, if there are two active residential gateway units 100 and 101, and they sense that device 106 is close (POINT A, 122) to the first residential gateway unit 100, all data is transmitted through it, e.g., through Wi-Fi bands in 2.4 GHz and 5 GHz. When the wireless sensing module determines that the device 106 is getting closer (POINT B, 120) to the second residential gateway unit 101 (e.g., through a corridor), the first and second residential gateway units may determine a location to move the 2.4 GHz communication link from the first unit 100 to the second unit 101. The “handover” of the low frequency band is done first due to its longer range. Next, when the device 106 gets further close (POINT C, 121) to the second residential gateway unit 101, the first unit 100 further transfers the data link over the 5 GHz band to the second unit 101. This way, the wireless sensing module can optimize the communication quality and efficiency for the devices by dynamically selecting the best residential gateway unit and the best communication resources. Similarly, the wireless sensing module may also influence which of the residential gateway units is used to receive / transmit data from / to the cellular network. For instance, in POINT A 122, all data with the cellular network may go through the first residential gateway unit exchanging data with base stations 103 and 104. At POINT B, the data exchanged may go through both the first and second residential gateways exchanging data with base station 103, 104, and 105. At POINT C 121, all data with the cellular network may go through the second residential gateway unit and be exchanged through base station 105. Of course, if it happens that the connectivity of one of the residential gateway units is not “ideal”, the other unit may support. For instance, when the communication link between 101 and 105 cannot deliver all2025PF00152

[0422] 47

[0423] throughput needed by device 106 at POINT C 121, residential gateway unit 100 may receive part of the data and either transfer it directly to device 106 or through residential gateway unit 101 (after forwarding the data in communication link 113). To perform such handover one or more of the following options may apply:

[0424] 1) The units may gather channel state information (measured from a reference signal) of the wireless device, and may determine based on it, where the wireless device is located, and whether there are obstacles in between,

[0425] 2) The units may transmit a wireless sensing signal such as a radar signal that may allow determining obstacles and / or the position of the wireless device,

[0426] 3) The units may determine when the “handover” in the local area network (e.g., when a Wi-Fi MLD station is going to move one of its links to another Wi-Fi MLD access point) is going to take place, and may signal this to the radio access network (cellular network) of the (distributed residential gateway) units. This may be an indication that the handover (of a communication link or part of it) is going to take place. This may trigger the handover of part of the communication from a first unit to a second unit, e.g., triggered by the radio access network and / or a network function (e.g., SMF) in the core network of the telecommunications system,

[0427] 4) The cellular network may act as the backbone of the communication of the (distributed residential gateway) units so that communication / control / coordination messages between the units (e.g., WiFi MLD access points) that determine which Wi-Fi MLD access point handles which part of the traffic are exchanged through the cellular network (e.g., as Ethernet PDUs). In this case, a controller in the (cellular) network may use those coordination messages to determine which traffic should be sent to which unit through the cellular network.

[0428] In an embodiment that may be combined with other embodiments or used independently, to support wireless sensing, the residential gateway units may include sensors that may detect rotation or changes in the location of the units. This can be useful to determine whether the environment has changed, for example, if a wall or a furniture has been moved, or if there is a new source of interference. The residential gateway units may also cooperate in the sensing, e.g., knowing the locations of the residential gateway units and using beamforming and sensing capabilities to determine the distance, two or more units may determine the location of the devices within the coverage area. They may also be able to learn a (3D) map of the environment and determine which area is best served by which unit, based on factors such as signal strength, quality, latency, traffic, and user preferences. The residential gateway units may dynamically adjust their configurations and resource allocations based on the sensed information and the feedback from the devices.

[0429] In an embodiment that may be combined with other embodiments or used independently, the local area network may be based on wireless LAN. Thus, the (distributed) residential gateway units may receive / transmit ethemet PDUs towards / through the radio access network. This may allow creating a virtual ethemet network having as backbone the radio access network and / or a network function in the2025PF00152

[0430] 48

[0431] core network. Control traffic in the local area network, e.g., wireless LAN control network to coordinate multiple access points providing connectivity to a wireless device may be exchanged through the cellular network. The radio access network and / or core network of the cellular system may then direct the ethemet PDUs towards the suitable (distributed) residential gateway unit as suitable. It is to be noted that coordination message within the local area network may only consider only the connectivity between the “access points” of the local area network (e.g., Wi-Fi access points) and the wireless device, but the cellular system should also consider the connectivity level from the (distributed) residential gateway units and the radio access network when performing load balancing. This may requires therefore information about the control messages in the local area network to coordinate the local access network interface (e.g., Wi-FI access point) and the quality of the communication link between (distributed) residential gateway units and the radio access network. Both messages / measurements may be provided to core network. The core network may coordinate the cellular network and / or local area network (e.g., as software defined network (SDN) wherein the SDN controller of the local area network is run remotely, e.g., in the core network.

[0432] In an embodiment that may be combined with other embodiments or used independently, the invention describes a procedure that may be used by one or more residential gateway units to determine the quality of the communication link with the devices. For instance, in reference to Fig. 14, residential gateway units 100 and 101 may gather the information of the quality of the communication link with device 106. For instance, channel state information. This information may be reported to the telecommunication system, e.g., to some of the RAN devices, e.g., 103, 104, 105, that may use this information to perform resource allocation and / or load balancing between residential gateway units 100 and 101 that are serving device 106. Additionally or alternatively, residential gateway units may use the gathered information about the quality of the communication link to request resources and / or perform load balancing between them.

[0433] The cellular network may need or be able to identify which device is behind a residential gateway, e.g., as being study on the User Identities study in SA2 and SA3 in R19. If the UE in the residential gateway, or cellular RAN, or cellular system become aware of the identity of a UE and may need to store device identity information (e.g. device ID, associated UE / RG ID, authentication information, authorized DNN, S-NSSAI, QoS, PDU session type etc.), it may need to perform device authentication / authorization, and may need to request URSP configuration or differentiated QoS for the traffic of device. (If) The multiple residential gateway units are involved, it is a question whether the device authentication / authorization needs to be redone, or how to transfer the URSP rules. To address these questions and / or enable identification, some embodiments may apply:

[0434] In an embodiment that may be combined with other embodiments or used independently, the cellular system (e.g., a network function storing the device identities, or the residential gateway units) may store to which residential gateway units a device (e.g., a Wi-Fi device or a UE) is currently connected. When a device moves (changes the residential gateway unit from a first one to a second one),2025PF00152

[0435] 49

[0436] the URSP configuration or QoS rules may be transferred from a residential gateway unit to the second residential gateway unit.

[0437] In an embodiment that may be combined with other embodiments or used independently, when a UE that is currently connected to the wireless access infrastructure (e.g., cellular network) moves in the home network and gets connected through a residential gateway (e.g., a distributed residential gateway unit) via local area network interface (e.g., Wi-Fi), the UE may provide its identity (e.g., SUPI) to the residential gateway that may share it with the core network. Additionally, the residential gateway and / or core network may use the identity to verify the UE, e.g., by performing an authentication procedure.

[0438] In an embodiment that may be combined with other embodiments or used independently, a residential gateway (e.g., a distributed residential gateway unit) may announce via its local area network interface (e.g., Wi-Fi), that it is a residential gateway. A UE configured with a USIM / 3GPP credentials may be configured to register to a residential gateway. For instance, provide a registration message including its identity.

[0439] In an embodiment that may be combined with other embodiments or used independently, the UE may perform a registration with and / or through the residential gateway (e.g., as a network registration in 5G), wherein the registration message is forwarded by the residential gateway to the serving network, and from there to the home network. Such messages (e.g., registration message) may be exchanged through the local area network communication technology. The residential gateway may transport the registration messages (e.g., registration request / primary authentication), e.g., as payload of some type of control messages, e.g., as payload of NAS messages, or as a specific type of NAS messages. The residential gateway may then serve as a relay (e.g., as illustrated in other embodiments) so that the UE and home network can authenticate with each other. The home network may authorize the UE to connect to the residential gateway via the serving network of the residential gateway, and the home network may provide the UE identity to the serving network of the residential gateway, i.e., the serving network handling / enabling / providing the connection of the residential gateway. The residential gateway may act as a base station providing a non-3GPP RAT. The residential gateway may register in a serving network / its home network using a registration message, e.g., as in 5G, indicating its capabilities as a residential gateway, and the serving network may store its identity, e.g., its long-term identity (e.g., 5G SUPI). When a UE connects to the residential gateway through a local network area interface (e.g., WiFi), the residential gateway and / or UE may determine that the UE is a cellular / 3GPP device, and the residential gateway may request 3GPP credentials and / or the UE may provide 3GPP credentials (e.g., as explained above) via a registration message.

[0440] In an embodiment that may be combined with other embodiments or used independently, the residential gateway may keep track of an identifier of a UE (e.g., address of the local area network interface, e.g., L2 MAC address) so that all traffic originated from the UE and exchanged with the residential gateway through the local area network interface can be tracked back to it. The residential2025PF00152

[0441] 50

[0442] gateway may, e.g., exchange such data / traffic with the core network using messages making use of an identifier linked to the UE. For instance, it may use a communication session, e.g., PDU session, specific to the UE. The serving network may be able to identify all PDU sessions originated at a residential gateway and associated with a UE. The messages exchanged by the residential gateway may be specific per device (e.g., UE). For instance, the PDU frames (e.g., PDU Ethernet frames) may include an identifier identifying the residential gateway and another identifier identifying the UE (in general, device) to which the residential gateway is serving, e.g., the layer 2 identifier of the local area network interface of the device, e.g., MAC address.

[0443] In another example, the traffic (or specific traffic) for a specific device (UE) may be carried in a specific QUIC connection, e.g., a multipath QUIC connection. For instance, if the UE is connected to two distributed residential gateway units and the UE has two types of traffic flows, each traffic flow may be mapped to a QUIC connection. A first QUIC connection may carry a first traffic flow and may require multipath through two distributed residential gateway units. A second QUIC connection may carry a second traffic flow that may not require multipath and may just be exchanged through one of the distributed residential gateway units. The QUIC connections may identify both the residential gateway units and the device (UE) originating the traffic flows. The traffic flows that are originated / received by the wireless device (UE) in the local area network may be carried as payload in QUIC multipath and may terminate, e.g., in a network function giving access to the data network, e.g., the 5G UPF.

[0444] The RAN of the cellular system provides different methods to reserve communication resources for a device (UE) in the downlink and uplink, including on (1) dynamic scheduling in which a DCI message is used to configured resources to be used by the UE in the uplink (PUSCH) or downlink (PDSCH) or scheduled procedures, namely semi persistent scheduling (downlink) or configured scheduling (uplink) wherein a DCI message or an RRC message are used to configure communication resources to be used by the UE in the uplink (PUSCH) or downlink (PDSCH). Local wireless systems such as Wi-Fi incorporate features to enable also more deterministic traffic, e.g., restricted target wake time (rTWT) that indicates when the devices (stations) need to wake up to transmit / receive data. The introduction of multiple residential gateways and the coordination between them introduces multiple challenges: (1) how to align cellular RAN scheduling of residential gateway units; (2) how to reduce the end-to-end latency (since rTWT and cellular scheduling may not be aligned). To this end, the following embodiments may be applicable.

[0445] In an embodiment that may be combined with other embodiments or used independently, N residential gateways units may receive a common resource budget, e.g., the same set of scheduled resources in up / downlink. The N residential gateways units may be assigned a same RNTI to transmit in those resources. Which resources are used by which residential gateway unit may be determined by the residential gateway units based on the current communication load. This may require signaling between the residential gateway units to agree on how the resources are shared at a given instant of time.2025PF00152

[0446] 51

[0447] In an embodiment that may be combined with other embodiments or used independently, all N residential gateway units receive the same traffic (e.g., the same downlink traffic at PDCP layer). This means that they have the same data available to distribute within the home network. This means that all N residential gateways may share some RAN parameters, e.g., (e.g., AS keys, etc) so that all of them can process / receive the same downlink traffic. In this operation mode, the reliability of the system increases because all residential gateway units may receive a copy of the data so that independently of where the device is in the home network, the residential gateway units may deliver a copy.

[0448] In an embodiment that may be combined with other embodiments or used independently, the residential gateway units may operate in two modes: a mode in which load balancing is performed and data is distributed according to the internal connectivity in the “local” (home) network (e.g., depending on where the devices are located) and a mode in which all residential gateway units receive a “copy” of the same downlink data so that all data is available to all residential gateway units and the units can distribute it according to protocols within the “local” network.

[0449] In an embodiment that may be combined with other embodiments or used independently, each residential gateway unit may receive a resource budget based on the current communication load at time t. This may require signaling between the residential gateway units to agree on how the resources are shared at a given instant of time so that if a residential gateway unit requests more resources, another residential gateway unit decreases them (since otherwise they may surpass a maximum). This may be a communication based on a “local” network protocol, e.g., WiFi. This may also require the cellular RAN (e.g., base stations) or a network function (e.g., SMF) to monitor two or more connections to make sure that the resource requirements do not surpass a maximum.

[0450] In an embodiment that may be combined with other embodiments or used independently, the residential gateway units may inform the cellular RAN about their scheduling (e.g., scheduling in the local area network interface, e.g., bandwidth needs for different rTWT, distribution among residential gateway units, etc) so that the cellular RAN may allocate resources fitting that schedule (and also other UEs in the cellular RAN). This allows coordinating the scheduling between cellular RAN and local wireless system to minimize the end-to-end latency. This embodiment may be applicable to use cases in which there is a single residential gateway unit. The residential gateway unit may send a report (e.g., via an RRC message) summarizing the scheduling of the “local” network. The RAN (e.g., access device) may use this information to perform and / or optimize resource scheduling.

[0451] In an embodiment that may be combined with other embodiments or used independently, the residential gateway units may inform the cellular RAN about the local network devices (e.g., number of devices, traffic type, communication resources, etc) so that the cellular RAN may allocate resources fitting their needs.

[0452] In an embodiment that may be combined with other embodiments or used independently, the residential gateway units may request the cellular RAN resources to enable the communication with2025PF00152

[0453] 52

[0454] the local network devices. Once the allocated resources are allocated, the residential gateway units determine the local scheduling (rTWT) minimizing resources and latency.

[0455] In a related embodiment that may be combined with other embodiments or used independently, the residential gateway units may also perform resource scheduling on the local communication interface with the wireless devices (e.g. as in Wi-Fi 6 / 7), so a residential gateway may perform such scheduling of local resources based on the received resources and / or request resources accordingly and in advance, e.g. to minimize latency

[0456] In an embodiment that may be combined with other embodiments or used independently, the device may transmit a reference signal that is measured by the residential gateway units to assess which of the residential gateway units are best suitable to receive uplink traffic from the device.

[0457] Similarly, the residential gateway units may transmit a reference signal so that the device can assess which of the devices are best suitable to transmit downlink traffic. The reference signals may be transmitted on demand, for example, when the device or the residential gateway units detect a change in the channel conditions or the quality of service requirements or when / shortly before the devices are configured to wake up (e.g., using the target wake time parameter in Wi-Fi). The device and the residential gateway units may be configured with a time to wake up for the transmission and reception of data / the reference signals, respectively. The reference signals may be transmitted / received shortly before the actual data transmission, and input may be provided on the performance achieved, such as signal-to-noise ratio, interference level, latency, packet error rate, etc. Based on this input, the device and / or the residential gateway units may select the best residential gateway units and bands for uplink / downlink transmission. This selection may be done by the device, by the residential gateway units, or by a centralized controller, e.g., one of the residential gateway units collecting the data measurements and allocating resources. The selection may also take into account other factors, such as the load of the residential gateway units, the battery level of the device, the user preferences, or the link quality of the cellular RAN etc. This information may also be reported by one or more of the residential gateway units to one or more of the RAN access devices so that they can optimize the communication, perform load balancing, and / or adjust resource allocation, etc.

[0458] Fig. 12 illustrates four different communication situations illustrating the advantages of a distributed residential gateway as per different embodiments. Fig. 12, a) shows a situation in which there is a single unit 100 and all resources (1) can be allocated to the communication with device 106. Fig. 12, b) shows a situation in which there is a single unit 100 and two devices 106 and 107 so that all resources (1) can distributed equality forthe communication of device 106 (1 / 2) and 107 (1 / 2). Fig. 12, c) shows a situation in which there are two units 100 and 101 and two devices 106 and 107, and unit 100 cannot efficiently communicate with device 107, so that unit 101 provides the communication with device 107, and unit 101 receives / sends said data from / to unit 100. In other words, the link between 100 and 101 is there to enable the communication with 107. The communication resources can be divided between link 100-106, link 100-101, and link 101-107, (1 / 3) each. Finally, Fig. 12, d) shows a situation in which there2025PF00152

[0459] 53

[0460] are two units 100 and 101 and two devices 106 and 107, and unit 100 cannot efficiently communicate with device 107 so that unit 101 is configured with credentials to access the RAN of the telecommunication system directly so that unit 100 serves device 106 with 1 / 2 of the available resources and 101 serves device 107 with 1 / 2 of the available resources.

[0461] In an embodiment that may be combined with other embodiments or used independently, a network operator may offer a distributed residential gateway offering a package of N units, and a single unit with an active subscription to access the RAN of the telecommunication system. The other N-l units may work as a Wi-Fi repeater / extender. The operator may offer the possibility of adding additional subscriptions (e.g., eSIM in a multiSIM package) for the other N-l units. The operator may handle all units with an active subscription as units in a single entity so that routed traffic to / from them can be optimized jointly. The residential gateway units may store credentials and / or be configured with credentials so that they can operate in this manner.

[0462] In an embodiment that may be combined with other embodiments or used independently, a user interface may be used to manage the units of the distributed residential gateway. Units may announce their presence via beacons, e.g., WiFi beacons or sidelink beacons. A unit acting as master (and where a SIM card may be configured or plugged) may receive those beacons and when the user logs in in the master unit (e.g., connecting to the Wi-Fi SSID, entering an IP address of a local server, and entering a user name / password), the available units may be shown. The user may be able to request new (3GPP) credentials (e.g., a new eSIM related to the distributed residential gateway subscription) from the new units (without credentials) though the user interface, where the request may involve interacting with the network operator and updating the subscription. If new credentials are purchased, the credentials (e.g., eSIM) may be deployed to a chosen unit. The user may then also configure the mode of operation of the different units, e.g., whether all units with credentials are always connected to the RAN or not.

[0463] Fig. 13 schematically shows the architecture and components of a unit 100 in a distributed residential gateway. It may comprise one or more of:

[0464] a radio 115 of a telecommunication system (e.g., 5G or 6G) that may correspond to a user equipment,

[0465] credentials 116 to access the telecommunication system,

[0466] a transceiver (e.g., radio) 117 of a local area network technology, e.g., wireless or wired, e.g., a local wireless communication technology (e.g., Wi-Fi),

[0467] a wireline interface 134,

[0468] a controller 118 to configure how radio 115 and / or 117 and / or wireline interface 134 is / are to be used, e.g., based on a local policy or configuration 119.

[0469] The local area network (LAN) technology may be wired or wireless.2025PF00152

[0470] 54

[0471] Section: DualSteer related aspects

[0472] In an embodiment that may be combined with other embodiments or used independently, a distributed residential gateway is a multiple steer device (MSD), including some similarities with a dual steer device as per TS 22.841. For instance, an MSD may comprise N (physical) devices, each of them accessing the data network via the same or different a RAT and / or core network. For instance, an MSD may comprise N residential gateway units and or UEs giving access to one or more wireless devices to a data network. A residential gateway unit and / or UE may also be a dual steer device or a multiple steer device itself where in this case each of the UEs may be in the same device. For instance, Fig. 15 shows a residential gateway unit 100 that includes two UEs 134 and 135 (being a DualSteer device), a residential gateway unit 102 that includes a single UE 128, and a DualSteer device 107 that also includes two UEs 136 and 137, being also a Dual Steer device.

[0473] Fig. 16 illustrates some components of a DualSteer UE 1400. In this UE, 1404 and 1405 refer to two protocol stacks as may be present in two Release 18 UEs. For instance, in an option the user plane protocol stack may include PHY / MAC / RLC / PDCP / SDAP layers. For instance, in another option the user plane protocol stack may include PHY / MAC / RLC / PDCP / SDAP / IP / UDP layers. For instance, the control plane protocol stack may include PHY / MAC / RLC / PDCP / RRC / NAS-MM / NAS-SM. 1406 represents a DualSteer control functionality module in charge of managing the operations of the protocol stacks. 1407 represents the multipath logic below the application layer or the IP layer, i.e., a layer in charge of enabling a multipath communication layer over both protocol stacks. This multipath logic maybe as in other embodiments describing MPQUIC. 1403 represents the USIM management module managing at least two SIMs / eSIMs 1401 and 1402. SIMs may include the required credentials (keys, counters, user identities, etc).

[0474] When the device is implemented in a distributed manner, the DualSteer control functionality (in general, multiSteer control functionality) may be present in a physical device next to one or more protocol stacks and the corresponding SIM / eSIM, and another physical device may implement another protocol stack and include the SIM / eSIM

[0475] A residential gateway unit (or UE) may register with the home network and indicate the fact that it is a residential gateway unit part of a distributed residential gateway, and indicate this in its UE capabilities. A first mobility function (e.g., AMF) may then trigger a primary authentication procedure with the home network. The home network may then check whether the credentials are entitled to be used in a residential gateway unit part of a distributed residential gateway. If authorized, the home network may indicate to the mobility function its authorization, that may then send a registration accept message. Upon acceptance, the residential gateway unit (or UE) may first work standalone. If further communication resources are needed, the residential gateway unit (or UE) need to inform another residential gateway unit (or UE) that it needs to be added / configured to the system. This indication may be done by means of the multisteer control logic functionality that may steer / determine which residential gateway unit (or UE) is to be added / configured. The addition / configuration may involve the distribution2025PF00152

[0476] 55

[0477] of suitable credentials (e.g., SIM) to that residential gateway unit (or UE). Once credentials are available, the residential gateway unit (or UE) may need to send a registration message indicating the type of device and purpose (a new residential gateway unit part of an existing distributed gateway unit). The mobility function (e.g., AMF) may then trigger the primary authentication and check whether it is authorized. If authorized, it may inform the mobility function, that may then inform the residential gateway with a registration accept message.

[0478] In an embodiment that may be combined with other embodiments or used independently, the association of the connection between residential gateway units / UEs may require the exchange of a token between both residential gateway units. For instance:

[0479] a first residential gateway unit may register / perform primary authentication, indicating it is an MSD,

[0480] credentials / SIM may be created for a new second MSD, and the second MSD may use those credentials / SIM to register / perform primary authentication,

[0481] second MSD may receive a token (e.g., encrypted by the first MSD with the public-key of the home network) as a proof of being connected to the same local area network.

[0482] For instance, the first MSD may generate a random number and encrypt the random number and its SUPI with the public key of the home network, the first MSD may share it over the local area network with the second MSD. Then the first MSD shares the random number with the core network and the second MSD shares the received token with the home network. The home network can then validate through the token that both devices are locally connected.

[0483] In a related embodiment that may be combined with other embodiments or used independently, as observed and described in the context of Fig. 9, a wireless device / UE may receive temporary credentials from a first residential gateway unit to access the cellular RAT / network. This same wireless device / UE may already have an existing subscription, and thus, it may become a dual steer device after step 108. The received credentials may be used by device 107 to register with the core network, indicate its capabilities, and shared subscription, and perform dual steer by means of both the existing and residential gateway unit subscriptions.

[0484] In a related embodiment that may be combined with other embodiments or used independently, in dual steer it is assumed that a DualSteer device is a device supporting traffic steering and switching of user data (for different services) across two 3GPP access networks; it can be a single UE, in case of non-simultaneous data transmission over the two networks, or two separate UEs in case of simultaneous data transmission over the two networks. A reason for requiring two UEs is because each of them has a different set of credentials (e.g., a different SUPI). This can mean that the cellular RAN / core network cannot group the data traffic (protocol data units) under a single RAN identifier (e.g., RNTI), so two RNTIs are used to deliver the related traffic. However, to better optimize performance, the following optimizations may apply:2025PF00152

[0485] 56

[0486] The RAN / CN know / are aware that two RAN identities or sets of credentials belong together, so that it is allowed to perform load balancing / scheduling between them, e.g., as in the case of devices 100 and 101 in Fig. 11.

[0487] In the case of the example of Fig. 9, the two sets of credentials / SUPIs associated to device 107 after step 108 may be linked to a single RAN identifier, or set of RAN identifiers, (e.g., RNTI) because it allows performing scheduling in a simplified manner.

[0488] In an embodiment that may be combined with other embodiments or used independently, the subscription data of an MSD as per TS 22.841 may include the SUPI in each of the SIMs associated to a UE, and it may include whether those SIMs are in a single physical device or in multiple physical devices. For instance, a dual steer device may comprise two collocated UEs. For instance, a dual steer device may comprise two different physical residential gateway units. This information may be linked to location information of those devices and / or UEs. The subscription data may also include whether they may be served by a single network or multiple networks. The reason is that the definition of DualSteer device, a dual steer device is served by two networks, and thus, two AMFs. However, in the case of a multiple residential gateway units part of a distributed gateway unit, the same serving network / AMF may be used.

[0489] In an embodiment that may be combined with other embodiments or used independently, a distributed residential gateway may be configured as a dual steer device, i.e. provide the dual steer with policies (e.g. DualSteer policies and / or URSP rules or ATSSS rules extended for dual steer (e.g. including which RAT or which UE within the dualsteer device to select, which traffic goes via which UE within the dualsteer device, etc.)).

[0490] It is noted that in this invention, a DualSteer device may be such that the two (in general N UEs / units of the device) units are controlled through a single network / PLMN.

[0491] In an embodiment that may be combined with other embodiments or used independently and in reference to Fig. 9, wireless device / UE 107 may receive credentials from a residential gateway unit, or it may have its own 3GPP credentials. The UE may then use those credentials to establish a connection with the 5G system and request access to the data network through the UPF. The 5G system may know that the wireless device / UE is capable of connecting through multiple networks or radio access networks, or distributed gateway units. In particular, it may be able to connect through the 3GPP RAN and N residential gateway units, so the core network (e.g., SMF) may instruct the UPF (e.g., via the N4 interface) to configure multiple multipath connections, e.g., using multipath QUIC. Additionally, or alternatively, the UE may attempt to connect with a residential gateway unit (e.g., sending a layer 2 indication). The residential gateway unit may trigger the establishment of a secure connection, e.g., an IPSec tunnel by sending an IKE message, and / or an authorization token, and / or a multipath-QUIC, towards the core network (e.g., UPF). When received, the UPF may check with the SMF whether the request is authorized. The SMF may further check with the AUSF / UDM. If authorized to establish an additional path, the SMF may configure the UPF to finish the setup of the secure communication link.2025PF00152

[0492] 57

[0493] The device / UE 107 may then have multiple connections through multiple residential gateway units, e.g., 3 connections through 3 residential gateway units. The UE may also need to map those connections (e.g., IPSec tunnels or multipath QUIC connections, etc) to different WLAN / WiFi frequency bands, e.g., Wi-Fi 2.4 GHz, Wi-Fi 5 Ghz, and Wi-Fi 6 Ghz. Note that when this is done, the UE may inform the cellular network about the feature s / configuration of the lower WLAN layers, e.g., frequency band, communication frequency, rTWT, etc so that the core network (e.g., SMF / UPF) can configure the communication parameters for each of those connections, e.g., this may be done by using multipath QUIC.

[0494] In an embodiment that may be combined with other embodiments or used independently, the first protocol stack 1404 may be in a first physical device (first UE) and the second protocol stack 1405 may be in a second physical device (second UE). The first UE and second UE may be carried by / be owned by a user. A DualSteer capability may be used to use the second protocol stack of the second device to deliver a service to the first UE. For instance, if a user is watching a video with the first UE using the first protocol stack, the user may have coupled both the first UE and second UE to operate in Dual Steer mode so that the first UE / first protocol stack steers the second UE to handle part of the connection / communication. The coupling of the first UE and second UE may be done by some type of non-cellular wireless communication (e.g., WiFi, Bluetooth, NFC, etc) or a cellular wireless communication (e.g., Sidelink).

[0495] To summarize, apparatuses / methods for enhanced authentication in cellular networks have been described, wherein the apparatus / method checks for a preferred authentication procedure, performs the preferred authentication procedure with a core network, and sets up a connection. Thereby, authentication challenges (such as retrieving core network data, optimizing resources and strength of authentication) arising from users of one or more devices (e.g., UEs) using multiple / different networks, (e.g., with multiple subscriber identity modules and / or different radio access technologies), avatar-based communication and / or biometrics (e.g., by means of embedded sensors or wireless sensing) can be addressed.

[0496] Although embodiments have been described in the context of virtual space such as metaverse, their applications are not limited to such a type of operation. Low latency systems, e.g., in Industrial loT systems, would also benefit from the teachings of this invention and its embodiments. The invention can be applied to various types of UEs or terminal devices, such as mobile phone, vital signs monitoring / telemetry devices, smartwatches, detectors, vehicles (for vehicle-to-vehicle (V2V) communication or more general vehicle-to-everything (V2X) communication), V2X devices, Internet of Things (loT) hubs, loT devices, including low-power medical sensors for health monitoring, medical (emergency) diagnosis and treatment devices, for hospital use or first-responder use, virtual reality (VR) headsets, etc.

[0497] Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure and the2025PF00152

[0498] 58

[0499] appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. A single processor or other unit may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in the text, the invention may be practiced in many ways, and is therefore not limited to the embodiments disclosed. It should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to include any specific characteristics of the features or aspects of the invention with which that terminology is associated. Additionally, the expression “at least one of A, B, and C” is to be understood as disjunctive, i.e., as “A and / or B and / or C”.

[0500] A single unit or device may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

[0501] The described operations like those indicated in the above embodiments may be implemented as program code means of a computer program and / or as dedicated hardware of the related network device or function, respectively. The computer program may be stored and / or distributed on a suitable medium, such as an optical storage medium or a solid-state medium, supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.

Claims

1. 2025PF0015259CLAIMS:

1. A method for enhanced mobility of a wireless device between a fixed wireless access device, FWA, and a mobile network, the method comprising,obtaining, by the wireless device, measurements of a first non-3GPP FWA wireless access device and / or a first 3GPP wireless access device, andreceiving, by the wireless device, a configuration to handover the communication of a data connection between the first 3GPP wireless access device and the first non-3GPP FWA wireless access device.

2. The method of Claim 1, further comprising,providing, by the wireless device, measurements relative to the first non-3GPP FWA wireless access device to the first 3GPP wireless access device and / or measurements relative to the first 3GPP wireless access device to the non-3GPP FWA wireless access device.

3. The method of claims 1 or 2, wherein the configuration comprises one or more conditions to conditionally perform the communication handover, andthe method further comprises evaluating, by the wireless device, the configuration and measurements to determine whether to handover the communication of the data connection with the data network between the first 3GPP wireless access device and the first non-3GPP wireless device.

4. The method of claim 1, wherein the configuration comprises a command to perform the handover of the communication of the data connection with the data network, and the method further comprises performing, by the wireless device, the handover of the communication of the data connection with the data network between the first 3GPP wireless access device and the first non-3GPP FWA wireless access device.

5. The method of any of the previous claims, wherein the measurements of a first non-3GPP FWA and / or first 3GPP wireless access device comprise estimating / obtaining one or more of:- a signal strength,- a network identifier,- an access device identifier,- a Layer 2 address,- device capabilities,- identification information of the serving network,2025PF0015260- SIB,- latency information,- connection setup delay information.

6. The method of any of the previous claims, further comprising:performing, by the wireless device, an initial handover of the communication from a second 3GPP access device to the first 3GPP access device upon determining that the first non-3GPP FWA wireless access device is connected to the first 3GPP access device.

7. The method of any of the previous claims, wherein the wireless device is configured with one or more policy rules comprising WLAN selection policies, QoS policies, or Access Traffic Steering, Switching, and Splitting (ATSSS) rules, the policy rules including latency-related conditions and / or connection-setup-delay-related conditions that influence whether traffic is transferred via 3GPP or non-3GPP access.

8. The method of any of the previous claims, further comprising measuring and / or obtaining, by the wireless device, latency information and / or connection setup delay information for the non-3GPP access, and determining, based on the measured and / or obtained information, whether to establish or maintain a connection via the non-3GPP access and / or whether to offload one or more traffic streams to the non-3GPP access.

9. The method of any of the preceding claims, comprising receiving, by the wireless device, handover-related information including predicted connection setup delay and / or predicted handover interruption duration, the predictions being generated locally by an Al model of the wireless device or provided by a network-based Al model, anddetermining, by the wireless device, using the predicted information, a timing to initiate or reject a handover to the non-3GPP access.

10. The method of claim 1, further comprising:obtaining, by the wireless device, FWA credentials for the communication with the 3GPP wireless access device, wherein the credentials are associated to the subscription of the non-3GPP wireless access device.

11. The method of claim 10, wherein the credentials are:- obtained upon determining that the measurements of the first non-3GPP FWA wireless access device are below a threshold; and / or2025PF0015261- valid as long as the wireless device remains within a maximum distance of the first non-3GPP FWA wireless access device.

12. The method of any of claims 1 and / or 10, further comprising performing, by the wireless device, a communication relying on the FWA credentials.

13. A method for registering a wireless device through a fixed wireless access device, FWA, the method comprising:receiving, by the wireless device, an indication of a first non-3GPP FWA wireless access device being capable of registering the wireless device,establishing, by the wireless device, a non-3GPP connection with the first non-3GPP FWA wireless access device,transmitting, by the wireless device, a registration message over the non-3GPP connection,performing, by the wireless device, a primary authentication with a core network, establishing, by the wireless device, a communication of a data connection.

14. The method of any previous claims, wherein the first non-3GPP FWA wireless access device comprises a non-3GPP transceiver adapted to communicate with the wireless device and a 3GPP wireless device adapted to communicate with a 3GPP access device.

15. The method of any previous claims, wherein PDCP and / or RRC and / or SDAP messages exchanged by the wireless device are transmitted transparently through the non-3GPP FWA wireless access device.

16. The method of any previous claims, wherein RLC / MAC / PHY layers of the non-3GPP FWA wireless access are controlled by the 3GPP access device to allocate communication resources for transport of PDCP and / or RRC and / or SDAP messages exchanged by the wireless device.

17. The method of any previous claims, wherein SDAP messages carry the communication of the data connection with the data network.

18. The method of any previous claims , wherein the non-3GPP FWA wireless access device comprises a 3GPP wireless device capable of exchanging RRC and PDCP messages with a 3GPP wireless access device and NAS messages with an access and mobility function.

19. The method of any previous claims, further comprising:2025PF0015262determining, by the wireless device, a root key from the security context of the wireless device, and using the root key to setup the security of a non-3GPP transceiver with the non-3GPP FWA wireless access device.

20. The method of any previous claims, further comprising:determining, by the wireless device, the serving network serving the non-3GPP access device,performing, by the wireless device, a registration procedure with the serving network serving the non-3GPP access device.

21. The method of any previous claims, further comprising receiving, by the wireless device, a validation token from the first non-3GPP FWA wireless access device through the non-3GPP interface, wherein the token validates the non-3GPP FWA wireless access device as capable of registering the wireless device in the wireless device core network and / or providing connectivity through the wireless device core network.

22. The method of any previous claims, further comprising transmitting to and / or receiving from the first non-3GPP FWA wireless access device and the first 3GPP access device messages of the data connection to perform data aggregation and / or load balancing.

23. The method of any previous claims, further comprising transmitting to and / or receiving from the first non-3GPP FWA wireless access device and a second non-3GPP FWA wireless access device messages of the data connection to perform data aggregation and / or load balancing.

24. An apparatus for enhanced mobility a fixed network and a mobile network comprising, a non-3GPP transceiver,a 3GPP transceiver,a processor adapted to perform the steps of the method of any of the previous claims 1 to 12.

25. An apparatus for registering a wireless device through a fixed access network in a core network, the apparatus comprising:a non-3GPP transceiver,a 3GPP transceiver,a processor, anda memory,2025PF0015263wherein the apparatus is adapted to perform the steps of the method of any of the previous claims 13 to 23.

26. A computer program for operating a wireless device having instructions for producing the steps of the methods in claim 1 to 23 when run on a computer.

Images