Apparatuses, methods and computer programs for non-3gpp access

Abstract

A user equipment UE registering with a 3GPP core network AMF, by sending indication of support for discontinuous reception (DRX, eDRX) of the UE, when the UE is on a non-3GPP network (WLAN, Wi-Fi) 1.

Description

APPARATUSES, METHODS AND COMPUTER PROGRAMS FORNON-3GPP ACCESS

[0001] TECHNICAL FIELD

[0002] Various example embodiments of this disclosure relate generally to apparatuses, computer programs, and methods, and - in particular, but not exclusively - to apparatuses, computer programs, and methods where a terminal can be on a non-3GPP access network.

[0003] BACKGROUND

[0004] A communication system may be a facility that enables communication sessions between two or more entities such as user terminals, base stations / access points and / or other nodes by providing carriers between the various entities involved in the communications path. A communication system may be provided, for example, by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

[0005] SUMMARY

[0006] Some example embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be readily apparent to a person skilled in the art in view of this disclosure.

[0007] According to a first aspect, there is provided a user equipment comprising: means for registering with a 3GPP core network, said registering comprising providing information indicating that the user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; and means for receiving, from the 3GPP core network, a first value for discontinuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3GPP access network.

[0008] The user equipment may be configured to support discontinuous reception when the user equipment is in a connected state with the non-3GPP access network.

[0009] The connected state with the non-3GPP access network may be a connection management state.

[0010] The first value for discontinuous reception may be a value for extended discontinuous reception.

[0011] The first value for discontinuous reception may be a value for determining one or more paging occasions for the user equipment with respect to the 3GPP access network.

[0012] The user equipment may comprise means for applying the first value for discontinuous reception when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

[0013] The means for receiving the first value for discontinuous reception may further be for receiving a first timer value, said first timer value defining a period for periodically notifying the 3GPP access network of an availability of the user equipment when the user equipment is connected to the non-3GPP access network.

[0014] The user equipment may comprise means for applying for applying the first timer value when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

[0015] The means for receiving the first value for discontinuous reception may further be for receiving a second value for discontinuous reception for use when the user equipment has no coverage via the non-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

[0016] The user equipment may comprise means for applying the second value for discontinuous reception when the user equipment has no coverage via the non-3GPP access network

[0017] The user equipment may comprise means for determining that the user equipment has no coverage via the non-3GPP access network, wherein in response to determining that the user equipment has no coverage via the non-3GPP access network, the means for applying the second value may be for applying the second value.

[0018] The means for receiving the first value for discontinuous reception may further be for receiving a second timer value, said second timer value defining a period for periodically notifying the 3GPP core network of an availability of the user equipment to the 3GPP access network, when the user equipment has no coverage via the non-3GPP access network.

[0019] The non-3GPP access network may be served by a non-roaming 3GPP core network.

[0020] The non-3GPP access network and the 3 GPP access node may be served by an access and mobility management function network function of the3GPP core network.

[0021] According to a second aspect, there is provided a method comprising: registering with a 3GPP core network, said registering comprising providing information indicating that a user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; and receiving, from the 3GPP core network, a first value for discontinuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3GPP access network.

[0022] The method may comprise supporting discontinuous reception when the user equipment is in a connected state with the non-3GPP access network.

[0023] The connected state with the non-3GPP access network may be a connection management state.

[0024] The first value for discontinuous reception may be a value for extended discontinuous reception.

[0025] The first value for discontinuous reception may be a value for determining one or more paging occasions for the user equipment with respect to the 3GPP access network.

[0026] The method may comprise applying the first value for discontinuous reception when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

[0027] The method may comprise receiving a first timer value, said first timer value defining a period for periodically notifying the 3GPP access network of an availability of the user equipment when the user equipment is connected to the non-3GPP access network.

[0028] The method may comprise applying the first timer value when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3 GPP access network.

[0029] The method may comprise receiving a second value for discontinuous reception for use when the user equipment has no coverage via the non-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

[0030] The method may comprise applying the second value for discontinuous reception when the user equipment has no coverage via the non-3GPP access network

[0031] The method may comprise determining that the user equipment has no coverage via the non-3GPP access network, wherein in response to determining that the user equipment has no coverage via the non-3GPP access network, applying the second value.

[0032] The method may comprise receiving a second timer value, said second timer value defining a period for periodically notifying the 3 GPP core network of an availability of the user equipment to the 3GPP access network, when the user equipment has no coverage via the non- 3GPP access network.

[0033] The non-3GPP access network may be served by a non-roaming 3GPP core network.

[0034] The non-3GPP access network and the 3GPP access node may be served by an access and mobility management function network function of the3GPP core network.

[0035] The method may be performed by an apparatus. The apparatus may be the user equipment or provided in the user equipment.

[0036] According to a third aspect, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: register with a 3GPP core network, said registering comprising providing information indicating that a user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; and receive, from the 3GPP core network, a first value for discontinuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3 GPP access network.

[0037] The instructions, when executed by the at least one processor, may further cause the apparatus to support discontinuous reception when the user equipment is in a connected state with the non-3GPP access network.

[0038] The connected state with the non-3GPP access network may be a connection management state.

[0039] The first value for discontinuous reception may be a value for extended discontinuous reception.

[0040] The first value for discontinuous reception may be a value for determining one or more paging occasions for the user equipment with respect to the 3GPP access network.

[0041] The method may comprise applying the first value for discontinuous reception when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

[0042] The instructions, when executed by the at least one processor, may further cause the apparatus to receive a first timer value, said first timer value defining a period for periodically notifying the 3GPP access network of an availability of the user equipment when the user equipment is connected to the non-3GPP access network.

[0043] The instructions, when executed by the at least one processor, may further cause the apparatus to apply the first timer value when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

[0044] The instructions, when executed by the at least one processor, may further cause the apparatus to receive a second value for discontinuous reception for use when the user equipment has no coverage via the non-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

[0045] The instructions, when executed by the at least one processor, may further cause the apparatus to apply the second value for discontinuous reception when the user equipment has no coverage via the non-3GPP access network.

[0046] The instructions, when executed by the at least one processor, may further cause the apparatus to determine that the user equipment has no coverage via the non-3GPP access network, and wherein in response to determining that the user equipment has no coverage via the non-3GPP access network, to apply the second value.

[0047] The instructions, when executed by the at least one processor, may further cause the apparatus to receive a second timer value, said second timer value defining a period for periodically notifying the 3GPP core network of an availability of the user equipment to the 3GPP access network, when the user equipment has no coverage via the non-3GPP access network.

[0048] The non-3GPP access network may be served by a non-roaming 3GPP core network.

[0049] The non-3GPP access network and the 3GPP access node may be served by an access and mobility management function network function of the3GPP core network.

[0050] The apparatus may be the user equipment or provided in the user equipment.

[0051] According to another aspect, there is provided a computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.

[0052] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.

[0053] According to an aspect, there is provided a non-volatile tangible memory medium comprising program instructions stored thereon for performing at least one of the above methods.

[0054] In the above, many different aspects have been described. It should be appreciated that further aspects may be provided by the combination of any two or more of the aspects described above.

[0055] Various other aspects are also described in the following detailed description and in the attached claims.

[0056] DESCRIPTION OF FIGURES

[0057] Some example embodiments will be further described in the detailed description below and with respect to the accompanying drawings, which are provided by way of illustration only and thus are not limiting of this disclosure.

[0058] FIG. 1 shows an example of a communication network to which examples disclosed herein may be applied;

[0059] FIG. 2 shows a non-roaming architecture with untrusted non-3GPP access;

[0060] FIG. 3 shows a non-roaming architecture with trusted non-3GPP access;

[0061] FIG. 4 shows a first method in accordance with some example embodiments;

[0062] FIGS. 5a and 5b shows a message sequence chart for an untrusted non-3GPP access scenario in accordance with some example embodiments;

[0063] FIG. 6 shows a method in accordance with some example embodiments; and

[0064] FIG.7 shows an apparatus in accordance with some example embodiments.

[0065] DETAILED DESCRIPTION

[0066] Although this disclosure may refer to “an”, “one”, or “some” embodiment(s) or example embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s) or example embodiment(s), or that a particular feature only applies to a single embodiment or to a single example embodiment. Single features of different embodiments or of different example embodiments may also be combined to provide other embodiments or other example embodiments, respectively. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment or with an example embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments or with other example embodiments whether or not explicitly described.

[0067] It shall be understood that although the terms “first”, “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0068] For the purposes of this disclosure, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). For the purposes of this disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0069] Some example embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0070] As used herein, the term “network device” or “network node” refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a nonterrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0071] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralised unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU (e.g., server, host or node) operationally coupled to the DU (e.g., a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some example embodiments, the DUs may comprise, e.g., a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and internet protocol (IP) layers. Other functional splits are possible, too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0072] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehiclemounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0073] A term “resource”, as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include, e.g., a resource block (RB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0074] FIG. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network or a cellular communication network may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0075] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0076] There may be a plurality of UEs 120, 122 in the system. Each of the plurality of UEs 120, 122 may be served by the same or by different network nodes 110, 112. Each of the plurality of UEs 120, 122 may be configured with dual connectivity (DC), wherein a UE, e.g., UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0077] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0078] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise, e.g., a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise, e.g., an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other network entities (e.g., network functions). The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering &integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0079] 3GPP allows for access networks to be comprised of 3GPP access nodes provided by a RAN (for example, a NG-RAN (next generation RAN)) and / or non-3GPP access nodes connecting to a 5G core network. 3GPP specifications allow for several methods to integrate non-3GPP access nodes with the 5G system (5GS). This may depend on whether the non-3GPP access nodes are trusted or untrusted and whether the devices support 5GC NAS over wireless local area network (WLAN) access (N5CW).

[0080] A non-3GPP access network may advertise the public land mobile networks (PLMN) for which it supports trusted connectivity. The non-3GPP access network may advertise the type of supported trusted connectivity (e.g., "5G connectivity"). Therefore, UEs may discover the non-3GPP access networks that can provide trusted connectivity to one or more PLMNs.

[0081] A UE connected (e.g., simultaneously connected and / or concurrently connected) to the same 5G core network of a PLMN over a 3GPP access and a non-3GPP access may be served by a single AMF in this 5G Core Network. However, in other situations a UE connected (e.g., simultaneously connected and / or concurrently connected) to the same 5G core network of a PLMN over a 3GPP access and a non-3GPP access may be served by different AMFs in this 5G Core Network. The different AMFs may need to communicate as required.

[0082] Currently, a UE is not paged on non-3GPP access network.

[0083] 3GPP TS 23.501 states that it is assumed that a UE configured to receive services from a 5GC over non-3GPP access, where the UE is RM (registration management)-DEREGISTERED or CM (connection management)-IDLE over the non-3GPP access, will attempt to establish a non-3GPP access connection and transition to the CM-CONNECTED state whenever the UE successfully connects to a non-3GPP access, unless the UE is prohibited by the network from making a non-3GPP access connection (e.g., due to network congestion).

[0084] Whenever a UE registered over non-3GPP access enters the CM-IDLE state for the non-3GPP access, the UE starts a UE non-3GPP deregistration timer according to a value received from the AMF during a registration procedure.

[0085] For a UE in CM-CONNECTED state, the AMF knows the UE location on a non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), trusted WLAN interworking function (TWIF) and / or wireline access gateway function (W-AGF) node granularity.

[0086] For a UE in CM-CONNECTED state, the N3IWF, TNGF, TWIF and W-AGF releases the N2 connection (the connection with the AMF) when the UE becomes unreachable from a N3IWF, TNGF, TWIF and / or W-AGF point of view (e.g., on non-3GPP access connection release).

[0087] FIG. 2 shows an architecture from 3GPP TS 23.501 for a non-roaming architecture for 5GC with untrusted non-3GPP access.

[0088] A UE can support (i.e., is capable of) registering with a 5GC of a wireless communication system over one or more accesses. When the UE requests registration with a 5GC over an access, the UE generates a registration request to register with the AMF via the 3GPP access. The AMF responds to the registration request by sending a registration accept message when the AMF accepts the UE’s registration request and registers the UE with the 5GC.

[0089] An access path may comprise an access network that provides access to the UE and a connection between access network and the UPF of the 5GC that connects to the data network (DN). The access network in each access or access path can be a 3 GPP access network that can employ different radio access technologies, or a non-3GPP access network. In the example of FIG. 2, the non-3GPP access network is untrusted.

[0090] Furthermore, the UE may support (e.g., may be capable of) registering with the AMF over the non-3GPP access network. In some example embodiments, the UE may register with the AMF of the 5GC over non-3GPP access network by sending a registration request to the AMF. In some example embodiments, the registration request may be sent via a non-3GPP access network. In some example embodiments, the registration request may be sent via an interworking function. In some example embodiments, the registration request may be sent via connections between the non-3GPP access network and the interworking function and the interworking function and the AMF. The non-3GPP access network may be any wireless or wired access network. The interworking function may be an N3IWF as shown in FIG. 2.

[0091] FIG. 2 also shows a session management function SMF which amongst other functions manages session context with the UPF.

[0092] FIG. 3 shows a non-roaming architecture from 3GPP TS 23.501 for 5GC with a trusted non-3GPP access network.

[0093] The arrangement of FIG. 3 is similar to that shown in FIG. 2. However, in this case the non-3GPP access is trusted. In this example embodiment, the trusted non-3GPP access comprises a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF). The non-3GPP access point is configured to interface with the UE and the trusted non-3GPP gateway function is configured to interface with the AMF.

[0094] In order to modify UE power utilization, a discontinuation reception (DRX) and extended DRX (eDRX) framework may be implemented for idle state (e.g., resulting in UE battery savings). The UE monitors one paging occasion per DRX or eDRX cycle. The determination of the paging occasion for eDRX differs depending on if the eDRX cycle is longer than 10.24 seconds. For eDRX cycles larger than 10.24 seconds, a hyper system frame number (SFN) frame structure may employed to determine the paging occasions. The extended DRX framework may be configured for cycles of up to 2.91 hours for an RRC Idle state and 10.24 seconds for an RRC inactive state.

[0095] The values for the DRX and / or eDRX framework may be negotiated between the UE and the AMF.

[0096] Applications that want to use extended idle state DRX may need to consider specific handling of mobile terminating services or data transfers. For example, applications may need to consider the delay tolerance of mobile terminated data.

[0097] Usage of higher DRX values may require larger buffering requirements in the 5GS.

[0098] A UE configured for eDRX may only employ eDRX if the UE receives an indication from the serving cell of the UE that eDRX is allowed in idle state or inactive state. This indication may be provided via, for example, system information.

[0099] A periodic registration update procedure may be used over 3GPP access to periodically notify the availability of the UE to the network. The procedure may be controlled in the UE by the periodic registration update timer, referred to as T3512.

[00100] The value of the timer T3512 is sent by the network to the UE in a REGISTRATION ACCEPT message. The UE applies this value in all tracking areas of the list of tracking areas assigned to the UE until a new value is received. The periodic registration update timer only applies to the UE registered to the 5GS services over 3GPP access.

[00101] If the timer T3512 received by the UE in a REGISTRATION ACCEPT message contains an indication that the timer is deactivated or the timer value is zero, then the timer T3512 is deactivated, and the UE does not perform the periodic registration update procedure.

[00102] Due to the recent proliferation of smart devices, mobile network operators are facing increases in data traffic, particularly by over-the-top applications. Typically, significant cellular traffic (e.g., up to 80% in some scenarios) may be originated from indoor locations. The increasing demands of indoor traffic and new applications, such as virtual reality (VR) and extended reality (XR), may be served with the help of WLAN or Wi-Fi (wireless fidelity) networks. Licenced frequencies of cellular networks (e.g., 3GPP networks using 3GPP access networks, such as used by mobile network operators) may experience relative high propagation losses when used in indoor environments. Wi-Fi nodes may be provided or integrated as non-3GPP access nodes into 5G core networks. This may address problems relating to increased traffic demands and / or QoS demands for traffic where a UE is located in an indoor environment. This may be as shown in FIG. 2 or FIG. 3.

[00103] A UE, which is in an indoor environment, may be connected to the 3GPP access network. The UE may monitor the 3GPP access network for 3GPP services.

[00104] The UE, which is in an indoor environment, may be connected to an indoor Wi-Fi access point (which is a non-3GPP access point). The UE may use the Wi-Fi access point for at least some of the data services of the UE. The UE may use the Wi-Fi access point for voice calls, for example via voice over Wi-Fi (VoWi-Fi).

[00105] In this scenario, the UE with an established communications channel via the non-3GPP access node continues to consume power for 3GPP access node monitoring. Some example embodiments may address this issue.

[00106] Some example embodiments may aim to provide a modified UE power utilization as described below.

[00107] Some example embodiments may, for example, aim to decrease UE battery power consumption.

[00108] Some example embodiments may, for example, aim to improve UE power saving.

[00109] As technology advances more and more sophisticated functions, such as artificial intelligence / machine learning (AI / ML) chipsets, are integrated in devices increasing their capabilities. However, power consumption of AI / ML chipsets is quickly becoming a limitation that is not only related to the UE’s battery capacity but also to the problems associated with the dissipation of heat. Accordingly, a modified UE power utilization (e.g., a reduction in UE battery power consumption) may be advantageous for certain use cases.

[00110] Some example embodiments may improve power utilization (e.g., power consumption) when the UE is connected via non-3GPP access. In some example embodiments, the power utilization associated with 3 GPP access may be modified based on a state of a connection of the UE via a non-3GPP access node. For example, the power consumption associated with 3GPP access may be reduced when the UE is connected via a non-3GPP access node.

[00111] Some example embodiments will be described where non-3GPP access and 3GPP access are intra-PLMN. In this scenario, a UE may be served by the same AMF.

[00112] In some example embodiments, the UE may be served by different AMFs. The AMF serving the non-3GPP access and the AMF serving the 3GPP access may need to communicate.

[00113] In some example embodiments, the non-3GPP access and 3GPP access are inter-PLMN.

[00114] One example method in accordance with some example embodiments will now be described with reference to FIG. 4.

[00115] Reference is made to the part of the method referenced 10. In some example embodiments, the UE will provide capability information to a network. The capability information may provide information about a capability of the UE to support DRX when the UE is connected a non-3GPP access node. The capability of the UE may be the capability of the UE to support extended DRX.

[00116] The capability information may provide information about the capability of the UE to support DRX when the UE is connected to a non-3GPP access node in a connected state, for example a connection management connected (CM-CONNECTED) state.

[00117] Reference is made to the part of the method referenced 20. The UE may receive a DRX value for when the UE is connected to the non-3GPP access node. The DRX value may be an eDRX value. This DRX value will be referred to as an eDRXWLAN value in the following. This eDRX WLAN value may be used when the UE is connected to a non-3GPP access node in a connected state, e.g., CM-CONNECTED state.

[00118] The eDRX WLAN value may be received from a 3GPP access node. The eDRX WLAN value may be received in a registration accept message or the like.

[00119] In some example embodiments, the UE will also receive a DRX value for when the UE is connected to a 3GPP access node. This DRX value may be a DRX value or eDRX. This DRX value may be as previously described. This DRX value is referred to as DRX 3GPP in the following.

[00120] It should be noted that in this disclosure, reference is made to a DRX value.

[00121] In some example embodiments, there may be more than one value associated with eDRX WLAN. In some example embodiments, the eDRX WLAN value may comprise one or more parameters.

[00122] In some example embodiments, the eDRX WLAN value may comprise a time duration (e.g., 102.4 sec).

[00123] In some example embodiments, the eDRX WLAN value may comprise a multiple of the DRX3GPP value.

[00124] In some example embodiments, the eDRX WLAN value may be defined with reference to another time reference known to the UE. For example, the eDRX WLAN value may be defined as a multiple the another time reference known to the UE.

[00125] In some example embodiments, there may be more than one value associated with DRX 3GPP. In some example embodiments, the DRX 3GPP value may comprise one or more parameters.

[00126] Optionally, a timer value is provided. This timer value may be provided with the eDRX WLAN value or in a separate message. This timer may be a periodic registration update timer. This timer for may be for use when the UE is connected to the non-3GPP access network. This timer may be referred to as T3512_WLAN in the following.

[00127] Optionally, a timer value is provided for use when the UE is connected to the 3GPP access network. This timer value may be provided with the DRX 3GPP value or in a separate message. This timer may be a periodic registration update timer. This timer may be referred to as T3512 3GPP in the following.

[00128] One or more of the timers may allow for a modified power utilization (e.g., power savings). In some example embodiments, if the timer assigned to the UE is not longer than an extended idle mode DRX cycle, then the power savings may not be maximized.

[00129] In some example embodiments, the time period associated with the T3512WLAN value is longer than the time period associated with the eDRXWLAN value.

[00130] In some example embodiments, the time period associated with the T3512 3GPP value is longer than the time period associated with the DRX3GPP value.

[00131] Reference is made to the part of the method referenced 30.

[00132] It is determined if the UE is in a state where the UE is connected to a non-3GPP access node. The state may be a CM-connected state for non-3GPP access. It may be determined if the UE is in a state where the UE is an idle state for 3GPP access. The idle state may be a CM-IDLE state.

[00133] Reference is made to the part of the method referenced 40.

[00134] If the UE is connected to the non-3GPP access node, for example in a CM-connected state and the UE is in an idle state for 3GPP access, then the UE will use the eDRX WLAN value for discontinuous reception on 3GPP access and the T3512WLAN value for Periodic Registration updates.

[00135] Thus, in some example embodiments, when the UE registers via non-3GPP access, as long as the UE is in the connected state, for example CM- CONNECTED state, for non-3GPP access and within the coverage of a non-3GPP access node, the UE will employ the eDRX WLAN value for discontinuous reception on 3GPP access. The UE may use the optional timer value, T3512 WLAN, for periodic registration updates.

[00136] The AMF may apply an eDRX_WLAN value and optionally a T3512_WLAN values for a UE which is registered via non-3GPP access and is in a connected state, such as a CM-CONNECTED state for non-3GPP access.

[00137] Reference is made to the part of the method referenced 50.

[00138] If the UE is not in a connected state with respect to the non-3GPP access node, the UE will use the DRX 3GPP value and optionally the T3512 3GPP value. This may occur when the UE has no access to the non-3GPP access node. The UE may have no access to the non-3GPP access node due to a loss of coverage, due to traffic considerations associated with the non-3GPP access node, or availability of a 3GPP access node which can service the UE.

[00139] The UE may transition into an idle state, e.g., CM-IDLE state, with respect to the non-3GPP access node, or de-register from the non-3GPP access node.

[00140] The AMF may revert to the DRX 3GPP value and optionally the T3512 3GPP timer when the UE is not in a connected state with respect to the non-3GPP access network.

[00141] The example embodiments described with reference to FIG. 4 may be used with non-3GPP trusted access.

[00142] The example embodiments described with reference to FIG. 4 may be used with non-3GPP untrusted access.

[00143] The example embodiments described with reference to FIG. 4 may be used with UEs which support 5GC NAS over WLAN access (N5CW).

[00144] The example embodiments described with reference to FIG. 4 may be used with UEs which do not support 5GC NAS over WLAN access (N5CW).

[00145] An example of a message sequence chart for an untrusted non-3GPP access scenario will now be described with reference to FIGS. 5a and 5b.

[00146] As referenced at 1, the UE initiates a 3GPP registration procedure. The 3GPP registration procedure may be with an AMF. In some example embodiments, the UE will provide information in the registration procedure indicating that the UE supports DRX, for example, eDRX when the UE has non-3GPP access.

[00147] The information provided by the UE may indicate support for the capability to support eDRX when the UE has non-3GPP access. The capability information may provide information about a capability of the UE to support DRX when the UE is connected a non-3GPP access node. The capability of the UE may be the capability of the UE to support extended DRX. The capability information may provide information about the capability of the UE to support DRX when the UE is connected to a non-3GPP access node in connected state, e.g., a CM-CONNECTED state.

[00148] Alternatively or additionally, the UE may provide a suggested value for the eDRX cycle.

[00149] In some example embodiments, the UE may determine the suggested value for the eDRX cycle based on the services which the UE is capable of supporting and / or the services the network supports via 3GPP access and / or non-3GPP access.

[00150] As referenced at 2, the UE receives a registration accept response from the AMF. The response may comprise a DRX value for when the UE is connected to the non-3GPP access node. The DRX value may be an eDRX value. This may be the eDRXWLAN value as previously discussed. The eDRX WLAN value is provided by the AMF to be used when the UE is a connected state, e.g. CM-CONNECTED state with respect to a non-3GPP access node and within coverage of a non-3GPP access node.

[00151] The registration accept response may additionally comprise a DRX value for when the UE is connected to a 3GPP access node. This may be the DRX3GPP value as previously described.

[00152] Optionally, the registration accept response may additionally comprise a timer value for when the UE is connected to a non-3GPP access node. This may be a periodic registration update timer value. This may be the T3512_WLAN value as previously described.

[00153] Optionally, a timer is provided for a timer value for when the UE is connected to a GPP access node. This may be a periodic registration update timer value. This timer may be referred to as T3512 3GPP in the following.

[00154] As referenced at 3, the UE may transition to an idle state, for example a CM-IDLE state, for 3GPP access after having completed the registration and optionally one or more other procedures and / or any required data transfer.

[00155] As referenced at 4, the UE may apply the DRX3GPP value for discontinuous reception of the 3GPP access. Optionally, the UE may apply the timer, for example T3512 3GPP, for periodic registration updates.

[00156] As referenced at 5, the UE may discover a WLAN network or other non-3GPP access network

[00157] As referenced at 6, the UE may initiate a connection to a non-3GPP access node of the WLAN network.

[00158] As referenced at 7, the UE performs a registration procedure via the untrusted non-3GPP access network. During this procedure, the UE may provide a Global Unique AMF Identifier (GUAMI) or other suitable indemnity information associated with an AMF. This GUAMI or other identifier is the identifier of the AMF which is handling the 3GPP access. The GUAMI or other identifier may enable the same AMF to handle the connection management of the UE for 3GPP access and for non-3GPP access. The registration procedure may be performed between the UE and the AMF.

[00159] As referenced at 8, the UE may be in a connected state, for example a CM-CONNECTED state, for the non-3GPP access. The UE may be in an idle state, for example CM-IDLE state, for 3GPP access.

[00160] As referenced at 9, the AMF applies the eDRXWLAN value to determine the paging occasions which will be monitored by the UE for 3GPP access. The AMF also applies a T3512 timer set to the value of T3512 WLAN.

[00161] As referenced at 10, as the UE in the coverage area of the non-3GPP access node, the UE applies eDRX WLAN values for paging monitoring of the 3GPP access. This allows the UE to reduce its monitoring of the 3GPP access network (e.g., RAN). This may allow for a longer sleep duration of the 3GPP access functions of the UE. This may lead to a modified power utilization (e.g., an increased battery life and / or a reduced power consumption). The UE also starts to employ the T3512WLAN timer if provided by the network. This value of T351 may allow for a larger time between periodic registration updates.

[00162] It should be appreciated that prior to starting the usage of T3512WLAN timer, the timer T3 512 3 GPP would be running at the UE and AMF side.

[00163] T3512 is a timer describing how often the UE should inform the network that it is “available”. This allows the network to know that it can reach the UE and the UE is active and / or available. Consider an example where T3512 3GPP is set to 6 hours. T3512 3GPP may already be running at the UE. The UE may initiate this timer after transition to an idle state with the network. If say, T3512_3GPP was already at 2.3 hours, the T3512_WLAN may start from zero or alternative from the last value of T3512 3GPP, for example 2.3 hours in the scenario set out above. In the latter case, the starting value for the T3512WLAN may be the last value of T3 512 3 GPP.

[00164] T3512_WLAN could be set to 12 hours in this example.

[00165] As referenced at 11 to 15, an example of a paging procedure will be described when the UE is in a connected state, for example a CM-CONNECTED state for the non-3GPP access and in an idle state, for example a CM-IDLE state for 3GPP access.

[00166] As referenced at 11, the AMF receives a request to page the UE. This may be derived from a downlink notification.

[00167] As referenced at 12, the AMF may initiate the paging procedure based on the eDRXWLAN value.

[00168] As referenced at 13, the AMF sends a paging request for the UE to the RAN. This may comprise the eDRX_WLAN value.

[00169] As referenced at 14, the RAN (the 3GPP access) employs the eDRX WLAN value to determine and transmit the paging occasion for the UE to the UE.

[00170] As referenced at 15, the UE performs a connection establishment procedure with the RAN.

[00171] As referenced at 16 to 25, a scenario in which the UE stops having non-3GPP access coverage is shown.

[00172] As referenced at 16, the UE may determine it no longer has non-3GPP access coverage. This may be based on, for example, a block error rate or a signal strength threshold of the serving node.

[00173] As referenced at 17, as a consequence of the loss of coverage, the UE applies the DRX3GPP value to determine the paging monitoring occasions for the idle state. The UE also employs the T3 512 3 GPP timer if configured. Since prior to starting the usage of T3 512 3 GPP timer, the timer T3512_WLAN was running at the UE and the AMF, the starting value for T3 512 3 GPP may be considered as the last value of T3512_WLAN or may start from zero. If based on this starting value, the UE timer for T3512WLAN is larger than T3512 3GPP, the UE initiates a Periodic Registration update. In the example embodiment shown, the UE timer value for T3512_WLAN is less than T3512_3GPP.

[00174] As referenced at 18, the non-3GPP access, e.g., N3IWF, detects the loss of connectivity and initiates a connection release.

[00175] As referenced at 19, the AMF is notified that the UE is unreachable via the non-3GPP access. The AMF may be notified by the non-3GPP access, e.g., N3IWF.

[00176] As referenced at 20, the AMF transitions the non-3GPP access state of the UE to the idle state, for example to the idle state, for example a CM-IDLE state, for 3GPP access. The AMF employs the DRX3GPP value and optionally the T3512 3GPP timer.

[00177] As referenced at 21, the AMF receives a request to page the UE. This may be derived from a downlink notification.

[00178] As referenced at 22, based on the connection management state of the UE, the AMF determines that the UE should be paged using the DRX3GPP value.

[00179] As referenced at 23, the AMF sends a paging request for the UE to the RAN. This may comprise the DRX 3GPP value.

[00180] As referenced at 24, the RAN (the 3GPP access) employs the DRX 3GPP value to determine and transmit the paging occasion for the UE to the UE.

[00181] As referenced at 25, the UE performs a connection establishment procedure with the RAN.

[00182] The eDRXWLAN value may be set to be a multiple of the DRX3GPP discontinuous reception monitoring cycle. This may mean that when the UE autonomously switches to DRX 3GPP monitoring, even if the AMF has not made the switch to DRX 3GPP. Any paging sent by the network using the eDRX_WLAN cycle is monitored by the UE.

[00183] In some example embodiments, to provide the eDRX on the 3GPP access the UE maintains the connected state, for example the CM-Connected state, on the non-3GPP access. In some scenarios, paging via non-3GPP access may not be supported by 3GPP.

[00184] A UE may transition from the idle state, for example, the CM-Idle state, to the connected state, for example the CM-Connected state, upon transmitting an initial NAS message. The initial NAS message maybe a service request, a registration request, or a deregistration request.

[00185] A UE may mostly be in the connected state, for example the CM-Connected state, when a non-3GPP access node is available.

[00186] In some example embodiments, the UE may be configured to receive services from a 5GC over non-3GPP access. Where the UE is deregistered, for example RM DEREGISTERED, form the non-3GPP access, or in an idle state, for example a CM-IDLE state with respect to non-3GPP access, the UE will attempt to establish a connection with the non-3GPP access and transition to the connected state, for example the CM-CONNECTED state when the UE successfully connects to a non-3GPP access, This attempt to connect with non-3GPP access network will be attempted unless the UE is prohibited by the network from making a non-3GPP access connection (e.g., due to network congestion).

[00187] Some example embodiments may provide a modified UE power utilization as described below

[00188] Some example embodiments may, for example, improve the life of a battery of a UE.

[00189] Some example embodiments, may, for example, decrease the energy used by a UE.

[00190] Some example embodiments, may, for example, decrease UE battery consumption given the amount of time devices are under WLAN coverage.

[00191] Some example embodiments may, for example, reduce buffering needs in elements, such as 5GS elements, given that access is available via one or more non-3GPP access nodes.

[00192] Reference is made to FIG. 6 which shows a method of some example embodiments.

[00193] The method may be performed by an apparatus.

[00194] The apparatus may comprise suitable means, such as circuitry for providing the method.

[00195] Alternatively or additionally, the apparatus may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor cause the apparatus at least to provide the method below.

[00196] Alternatively or additionally, the apparatus may be such as discussed in relation to FIG. 7

[00197] The respective methods may be provided by computer program code or computer executable instructions.

[00198] The method may comprise as referenced at Al, registering with a 3GPP core network, said registering comprising providing information indicating that a user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network.

[00199] The method may comprise as referenced at A2, receiving, from the 3GPP core network, a first value for discontinuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3GPP access network.

[00200] FIG. 7 shows, by way of example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and any of the example embodiments thereof. In an example embodiment, the at least one memory and the instructions (e.g., computer program code, software, etc.), are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and any of the example embodiments thereof.

[00201] A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used herein, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in analog, digital, and / or quantum circuitry, and (b) combinations of hardware circuit(s) and software, such as, as applicable: (i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)), with software, and memory(ies) that work together to cause an apparatus, such as a device, computing device, user equipment, or server to perform various functions) and (c) any or all portions of hardware circuit(s), such as microprocessor(s), processor(s) and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[00202] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[00203] The instructions 15 may be comprised in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory, RAM, vs. read only memory, ROM).

[00204] For example, the apparatus 10 is a terminal device, such as the UE of FIG. 1. As another example, the apparatus is comprised in such a terminal device, e.g., as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform at least the method of FIGs. 4, 5a, 5b or 6 and / or any one or more of the example embodiments described.

[00205] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity. In some example embodiments, the entity is configured to perform at least the method of FIG. Y or FIG. Z, and / or any one or more of the various example embodiments described.

[00206] The apparatus 10 comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmitter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[00207] The apparatus 10 may comprise a user interface 18 comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 may be used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[00208] In some example embodiments, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Means for performing method steps as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the various example embodiments thereof. As used herein the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[00209] Even though various example embodiments of this disclosure have been described above with reference to the accompanying drawings, it is clear that various example embodiments are not restricted thereto but can be modified in several ways within the scope of this disclosure. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the various example embodiments. It is understood, as technology advances, the scope of this disclosure can be implemented and adapted in various ways. Further, it is clear to a person skilled in the art that any of example embodiments of this disclosure may, but are not required to, be combined with any other example embodiments of this disclosure in various manners.

Claims

1. A user equipment comprising:means for registering with a 3GPP core network, said registering comprising providing information indicating that the user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; andmeans for receiving, from the 3GPP core network, a first value for dis-continuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3GPP access network.

2. The user equipment as claimed in claim 1, wherein the user equipment is configured to support discontinuous reception when the user equipment is in a connected state with the non-3GPP access network.

3. The user equipment as claimed in claim 2, wherein the connected state with the non-3GPP access network is a connection management state.

4. The user equipment as claimed in any preceding claim, wherein the first value for discontinuous reception is a value for extended discontinuous reception.

5. The user equipment as claimed in any preceding claim, wherein the first value for discontinuous reception is a value for determining one or more paging occasions for the user equipment with respect to the 3GPP access network.

6. The user equipment as claimed in any preceding claim, comprising means for applying the first value for discontinuous reception when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

7. The user equipment as claimed in any preceding claim, wherein the means for receiving the first value for discontinuous reception is further for receiving a first timer value, said first timer value defining a period for periodically notifying the 3GPP access network of an availability of the user equipment when the user equipment is connected to the non-3GPPaccess network.

8. The user equipment as claimed in claim 7, comprising means for applying the first timer value when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

9. The user equipment as claimed in any preceding claim, wherein the means for receiving the first value for discontinuous reception is further for receiving a second value for discontinuous reception for use when the user equipment has no coverage via the non-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

10. The user equipment as claimed in claim 9, comprising means for applying the second value for discontinuous reception when the user equipment has no coverage via the non-3GPP access network.

11. The user equipment as claimed in claim 10, comprising means for determining that the user equipment has no coverage via the non-3GPP access network, wherein in response to determining that the user equipment has no coverage via the non-3GPP access network, the means for applying the second value applies the second value.

12. The user equipment as claimed in any preceding claim, wherein the means for receiving the first value for discontinuous reception is further for receiving a second timer value, said second timer value defining a period for periodically notifying the 3GPP core network of an availability of the user equipment to the 3GPP access network, when the user equipment has no coverage via the non-3GPP access network.

13. The user equipment as claimed in any preceding claim, wherein the non-3GPP access network is served by a non-roaming 3GPP core network.

14. The user equipment as claimed in any preceding claim, wherein the non-3GPP access network and the 3 GPP access node are served by an access and mobility management network function of the 3 GPP core network.

15. A method comprising:registering with a 3GPP core network, said registering comprising providing information indicating that a user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; andreceiving, from the 3GPP core network, a first value for discontinuous reception when the user equipment is on a non-3GPP access network, the first value being for discontinuous reception with respect to a 3GPP access network.

16. The method as claimed in claim 15, wherein the user equipment is configured to support discontinuous reception when the user equipment is in a connected state with the non-3GPP access network.

17. The method as claimed in claim 15 or 16, wherein the first value for discontinuous reception is a value for extended discontinuous reception.

18. The method as claimed in any of claims 15 to 17, wherein the first value for discontinuous reception is a value for determining one or more paging occasions for the user equipment with respect to the 3GPP access network.

19. The method as claimed in any of claims 15 to 18, comprising applying the first value for discontinuous reception when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.20.The method as claimed in any of claims 15 to 19, comprising receiving a first timer value, said first timer value defining a period for periodically notifying the 3GPP access network of an availability of the user equipment when the user equipment is connected to the non-3GPP access network.

21. The method as claimed in claim 20, comprising applying the first timer value when the user equipment is in a connected state with respect to the non-3GPP access network and in an idle state with respect to the 3GPP access network.

22. The method as claimed in any of claims 15 to 21, comprising receiving a second value for discontinuous reception for use when the user equipment has no coverage via thenon-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

23. The method as claimed in claim 22, comprising applying the second value for 5 discontinuous reception when the user equipment has no coverage via the non-3GPP access network.

24. The method as claimed in claim 23, comprising determining that the user equipment has no coverage via the non-3GPP access network, wherein in response to 10 determining that the user equipment has no coverage via the non-3GPP access network, applying the second value.

25. A computer readable medium comprising program instructions stored thereon for performing the method of any of claims 15 to 24.28

Images