Apparatus, method, and computer program for non-3gpp access

Abstract

A user equipment comprising: means for registering with a 3GPP core network, the registration 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 the non-3GPP access network, the first value being with respect to discontinuous reception for a 3GPP access network.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to apparatuses, computer programs and methods, and particularly, but not limited to, apparatuses, computer programs and methods in which terminals can access non-3GPP networks. Background Technology

[0002] A communication system can be a facility that enables a communication session between two or more entities (such as user terminals, base stations / access points, and / or other nodes) by providing carrier waves between the various entities involved in the communication path. The communication system can be provided, for example, through a communication network and one or more compatible communication devices. A communication session can include, for example, communication of data for carrying communications such as voice, email, text messages, multimedia, and / or content data. Non-limiting examples of the services provided include two-way or multi-way calling, data communication or multimedia services, and access to data network systems such as the Internet. Summary of the Invention

[0003] Some exemplary 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 limit the scope of this disclosure. Other features, aspects, and elements will become apparent to those skilled in the art in light of this disclosure.

[0004] According to a first aspect, a user equipment is provided, comprising: components for registering with a 3GPP core network, the registration including 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 components 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 relating to discontinuous reception on the 3GPP access network.

[0005] User equipment can be configured to support discontinuous reception when it is connected to a non-3GPP access network.

[0006] The connection status with a non-3GPP access network can be in connection management status.

[0007] The first value used for discontinuous reception can be the value used for extended discontinuous reception.

[0008] The first value used for discontinuous reception can be: a value used to determine one or more paging opportunities for the user equipment in relation to the 3GPP access network.

[0009] The user equipment may include a component for applying a first value for discontinuous reception when the user equipment is connected to a non-3GPP access network and idle with respect to a 3GPP access network.

[0010] The component for receiving a first value for discontinuous reception can also be used to: receive a first timer value, the first timer value defining a time period for periodically notifying the 3GPP access network of the availability of the user equipment when the user equipment is connected to a non-3GPP access network.

[0011] The user equipment may include a component for applying a first timer value when the user equipment is connected to a non-3GPP access network and idle with respect to a 3GPP access network.

[0012] The component for receiving the first value for discontinuous reception can also be used to: receive a second value for discontinuous reception for use when the user equipment does not have coverage via a non-3GPP access network, the second value being related to the 3GPP access network for discontinuous reception.

[0013] User equipment may include components for applying a second value for discontinuous reception when the user equipment does not have coverage via a non-3GPP access network.

[0014] The user equipment may include components for determining that the user equipment does not have coverage via a non-3GPP access network, wherein, in response to determining that the user equipment does not have coverage via a non-3GPP access network, the components for applying a second value may be used to apply the second value.

[0015] The component for receiving the first value for discontinuous reception can also be used to: receive a second timer value, the second timer value defining a time period for periodically notifying the 3GPP core network of the availability of the 3GPP access network when the user equipment does not have coverage via a non-3GPP access network.

[0016] Non-3GPP access networks can be served by non-roaming 3GPP core networks.

[0017] Non-3GPP access networks and 3GPP access nodes can be served by the access and mobility management function network of the 3GPP core network.

[0018] According to a second aspect, a method is provided, comprising: registering with a 3GPP core network, the registration including 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 related to the 3GPP access network for discontinuous reception.

[0019] This method may include supporting discontinuous reception when the user equipment is connected to a non-3GPP access network.

[0020] The connection status with a non-3GPP access network can be in connection management status.

[0021] The first value used for discontinuous reception can be the value used for extended discontinuous reception.

[0022] The first value used for discontinuous reception can be: a value used to determine one or more paging opportunities for the user equipment in relation to the 3GPP access network.

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

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

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

[0026] The method may include receiving a second value for discontinuous reception, for use when the user equipment does not have coverage via a non-3GPP access network, the second value relating to discontinuous reception via the 3GPP access network.

[0027] The method may include applying a second value when the user equipment does not have coverage via a non-3GPP access network.

[0028] The method may include determining that the user equipment does not have coverage when accessing a network via a non-3GPP network, wherein a second value is applied in response to determining that the user equipment does not have coverage when accessing a network via a non-3GPP network.

[0029] The method may include receiving a second timer value that defines a time period for periodically notifying the 3GPP core network of the availability of the 3GPP access network when the user equipment does not have coverage via a non-3GPP access network.

[0030] Non-3GPP access networks can be served by non-roaming 3GPP core networks.

[0031] Non-3GPP access networks and 3GPP access nodes can be served by the access and mobility management function network of the 3GPP core network.

[0032] This method can be performed by a device. The device can be a user equipment or a device located within a user equipment.

[0033] According to a third aspect, an apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: register with a 3GPP core network, the registration including 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 relating to discontinuous reception on the 3GPP access network.

[0034] When executed by at least one processor, this instruction can also enable the device to support discontinuous reception when the user equipment is connected to a non-3GPP access network.

[0035] The connection status with a non-3GPP access network can be in connection management status.

[0036] The first value used for discontinuous reception can be the value used for extended discontinuous reception.

[0037] The first value used for discontinuous reception can be: a value used to determine one or more paging opportunities for the user equipment in relation to the 3GPP access network.

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

[0039] When executed by at least one processor, the instruction can also cause the device to receive a first timer value that defines a time period for periodically notifying the 3GPP access network of the availability of the user equipment when the user equipment is connected to a non-3GPP access network.

[0040] When executed by at least one processor, the instruction can also cause the device to apply a first timer value when the user equipment is connected to a non-3GPP access network and idle with respect to a 3GPP access network.

[0041] When executed by at least one processor, the instruction can also cause the device to receive a second value for discontinuous reception, for use when the user equipment does not have coverage via a non-3GPP access network, the second value relating to the 3GPP access network for discontinuous reception.

[0042] When executed by at least one processor, the instruction can also cause the device to apply a second value for discontinuous reception when the user equipment is not covered by a non-3GPP access network.

[0043] When executed by at least one processor, the instruction may also cause the device to determine that the user equipment does not have coverage via a non-3GPP access network, and wherein a second value is applied in response to determining that the user equipment does not have coverage via a non-3GPP access network.

[0044] When executed by at least one processor, the instruction can also cause the device to receive a second timer value that defines a time period for periodically notifying the 3GPP core network of the availability of the 3GPP access network when the user equipment is not covered by a non-3GPP access network.

[0045] Non-3GPP access networks can be served by non-roaming 3GPP core network services.

[0046] Non-3GPP access networks and 3GPP access nodes can be served by the access and mobility management functions of the 3GPP core network.

[0047] The device can be a user device or be installed in a user device.

[0048] According to another aspect, a computer-readable medium is provided, including program instructions stored thereon for performing at least one of the methods described above.

[0049] According to one aspect, a non-volatile computer-readable medium is provided, including program instructions stored thereon for performing at least one of the methods described above.

[0050] According to one aspect, a non-transient tangible storage medium is provided, including program instructions stored thereon for executing at least one of the methods described above.

[0051] Many different aspects have been described above. It should be understood that additional aspects can be provided by combining any two or more of the aspects mentioned above.

[0052] Various other aspects are also described in the following detailed description and the appended claims. Attached Figure Description

[0053] Some exemplary embodiments are further described below in detail with reference to the accompanying drawings, which are provided by way of illustration only and therefore do not limit this disclosure.

[0054] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown;

[0055] Figure 2 This illustrates a non-roaming architecture with untrusted non-3GPP access;

[0056] Figure 3 A non-roaming architecture with trusted non-3GPP access is shown;

[0057] Figure 4 A first method according to some example embodiments is shown;

[0058] Figure 5a and Figure 5b The diagram illustrates a message sequence for an untrusted non-3GPP access scenario according to some example embodiments.

[0059] Figure 6 Methods according to some example embodiments are shown; and

[0060] Figure 7 An apparatus according to some example embodiments is shown. Detailed Implementation

[0061] Although this disclosure may refer to "a," "an," or "some" embodiments or example embodiments in various places, this does not necessarily mean that each reference refers to the same embodiment or example embodiment, or that a particular feature applies only to a single embodiment or example embodiment. Individual features of different embodiments or different example embodiments may also be combined to provide other embodiments or other example embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment or example embodiment, whether explicitly described or not, those skilled in the art can apply such features, structures, or characteristics in connection with other embodiments or other example embodiments.

[0062] It should be understood that although the terms “first,” “second,” etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0063] 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" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0064] Some of the example embodiments described can be implemented in communication networks such as any of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE-Advanced and Enhanced LTE (eLTE), 5G (also known as NR), or any future RAT (such as 6G). Furthermore, communication within the communication network can utilize any suitable wireless communication technology, including 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 Multiplexing (OFDM), and / or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

[0065] As used herein, the term "network device" or "network node" refers to a node in a communication network through which user equipment can access the network and / or control radio communications and manage radio resources within a cell. A network node or network device may be referred to as a base station (BS), access point (AP), or access node. Depending on the technology applied, a network device may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known 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 non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary orbit (GEO) satellites), or an aircraft network device.

[0066] Furthermore, in relation to a split radio access network (RAN), network equipment can refer to a centralized unit (CU) and / or a distributed unit (DU) of a base station. The interface between the CU and the DU can be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed at least partially in a central / centralized unit (CU, e.g., a server, host, or node) that is operationally coupled to a DU (e.g., a radio head / node). A CU can control one or more DUs, which at least act as transmit / receive (Tx / Rx) nodes. In some example embodiments, a DU may include, for example, a Radio Link Control (RLC), Media Access Control (MAC) layer, and a Physical (PHY) layer, while a CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Internet Protocol (IP) layer. Other functional divisions are also possible. In fact, any processing task can be performed in a CU or a DU, and the boundary of responsibility transfer between the CU and DU may depend on the implementation applied.

[0067] The term "terminal device" refers to any terminal device capable of wireless communication. For example, a terminal device may be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). Terminal devices can include mobile phones, cellular phones, smartphones, Voice over IP (VoIP), wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB dongles, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain scenarios), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on.

[0068] As used herein, the term "resource" can refer to radio resources in the time domain, frequency region, spatial domain, and / or code domain. Some examples of resources include, for example, resource blocks (RBs), radio frames, subframes, time slots, subbands, frequency domains, subcarriers, beams, etc. The terms "transmit" and / or "receive" can refer to wireless transmission and / or reception on radio resources via a radio propagation channel.

[0069] Figure 1Examples of communication networks to which the examples disclosed herein can be applied are shown. Such a communication network, or cellular communication network, may include 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). For example, each cell may be a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​a corresponding access node.

[0070] Network node 110 can provide user equipment (UE) 120 (one or more UEs) with radio access to a communication network. This radio access may include 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 include a Physical Uplink Control Channel (PUCCH) for transmitting control information and a Physical Uplink Shared Channel (PUSCH) for transmitting data to the network. Examples of downlink channels include a Physical Downlink Control Channel (PDCCH) for transmitting control information and a Physical Downlink Shared Channel (PDSCH) for transmitting data to the user equipment.

[0071] Multiple UEs 120 and 122 can exist in the system. Each of the multiple UEs 120 and 122 can be served by the same or different network nodes 110 and 112. Each of the multiple UEs 120 and 122 can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 110 and 112. If a device-to-device (D2D) communication interface is established between UEs 120 and 122 via a so-called side link (SL), they can communicate with each other. For example, such D2D communication can be referred to as machine-to-machine communication, point-to-point (P2P) communication, or vehicle-to-vehicle (V2V) communication, etc.

[0072] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. The LTE specification refers to such interfaces as X2 interfaces. Interfaces between LTE nodes and 5G nodes, or between two 5G nodes, can be called Xn interfaces.

[0073] Network nodes 110 and 112 can be further connected to the core network 116 of the communication network via another interface. The LTE specification defines the core network as the Evolved Packet Core (EPC), which may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices in a tracking area containing multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing within the core network and to / from terminal devices. The 5G specification defines the core network as the 5G Core (5GC). The 5G Core may include, for example, Access and Mobility Management Functions (AMF), User Plane Functions / Gateways (UPF), and other network entities (e.g., network functions). The AMF can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, a UPF node can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.

[0074] 3GPP allows access networks to consist of 3GPP access nodes provided by the RAN (e.g., NG-RAN (Next Generation RAN)) and / or non-3GPP access nodes connected to the 5G core network. The 3GPP specification allows several methods for integrating non-3GPP access nodes with the 5G system (5GS). This may depend on whether the non-3GPP access node is trusted or untrusted, and whether the device supports NAS (N5CW) access via 5GC through a wireless local area network (WLAN).

[0075] Non-3GPP access networks can advertise the Public Land Mobile Networks (PLMNs) that support trusted connectivity. Non-3GPP access networks can also advertise the types of trusted connectivity they support (e.g., "5G connectivity"). Therefore, a UE can discover non-3GPP access networks capable of providing trusted connectivity to one or more PLMNs.

[0076] A UE connected to the same 5G core network of the PLMN via 3GPP access and non-3GPP access connections (e.g., simultaneous and / or concurrent connections) can be served by a single AMF within that 5G core network. However, in other cases, a UE connected to the same 5G core network of the PLMN via 3GPP access and non-3GPP access connections (e.g., simultaneous and / or concurrent connections) can be served by different AMFs within that 5G core network. Different AMFs may need to communicate as needed.

[0077] Currently, UEs are not paging on non-3GPP access networks.

[0078] 3GPP TS 23.501 specifies that a UE configured to receive services from a 5GC via a non-3GPP access (where the UE is in RM (Registration Management) - DEREGISTERED or CM (Connection Management) - IDLE on the non-3GPP access) will attempt to establish a non-3GPP access connection, and will transition to the CM-CONNECTED state whenever the UE successfully connects to the non-3GPP access, unless the network prohibits the UE from making a non-3GPP access connection (e.g., due to network congestion).

[0079] Whenever a UE registered through non-3GPP access enters the CM-IDLE state of non-3GPP access, the UE starts the UE non-3GPP deregistration timer based on the value received from the AMF during the registration process.

[0080] For UEs in CM-CONNECTED state, AMF determines the UE's location based on the node granularity of Non-3GPP Interoperability Function (N3IWF), Trusted Non-3GPP Gateway Function (TNGF), Trusted WLAN Interoperability Function (TWIF), and / or Wired Access Gateway Function (W-AGF).

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

[0082] Figure 2 The architecture from 3GPP TS 23.501 for a non-roaming architecture of a 5GC with untrusted non-3GPP access is shown.

[0083] The UE can support (i.e., be able to) register with the 5GC of the wireless communication system through one or more access points. When the UE requests to register with the 5GC through an access point, the UE generates a registration request to register with the AMF via a 3GPP access point. When the AMF accepts the UE's registration request and registers the UE with the 5GC, the AMF responds to the registration request by sending a registration acceptance message.

[0084] Access paths may include access networks providing access to the UE and connections between these access networks and the 5GC's UPF, which is connected to the data network (DN). Each access network or access path may be a 3GPP access network that can employ different radio access technologies, or a non-3GPP access network. Figure 2 In the example, non-3GPP access networks are untrusted.

[0085] Furthermore, the UE can support (e.g., be able to) register with the AMF via a non-3GPP access network. In some example embodiments, the UE can register with the 5GC's AMF via a non-3GPP access network by sending a registration request to the AMF. In some example embodiments, the registration request can be sent via a non-3GPP access network. In some example embodiments, the registration request can be sent via an interoperability function. In some example embodiments, the registration request can be sent via a connection between the non-3GPP access network and the interoperability function, and between the interoperability function and the AMF. The non-3GPP access network can be any wireless or wired access network. The interoperability function can be, for example, such as... Figure 2 The N3IWF shown is shown.

[0086] Figure 2 The session management function SMF is also shown, which, among other functions, manages the session context with the UPF.

[0087] Figure 3 The architecture from 3GPP TS 23.501 for a non-roaming architecture of 5GC with trusted non-3GPP access networks is shown.

[0088] Figure 3 The layout and Figure 2 The arrangement shown is similar. However, in this case, the non-3GPP access is trusted. In this example embodiment, the trusted non-3GPP access includes 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, while the Trusted Non-3GPP Gateway Function is configured to interface with the AMF.

[0089] To modify UE power utilization, discontinuous reception (DRX) and extended DRX (eDRX) frameworks can be implemented for idle states (e.g., resulting in UE battery saving). The UE monitors a paging opportunity every DRX or eDRX cycle. The determination of the paging opportunity for eDRX varies depending on whether the eDRX cycle is longer than 10.24 seconds. For eDRX cycles longer than 10.24 seconds, the supersystem frame number (SFN) frame structure can be used to determine the paging opportunity. The extended DRX framework can be configured for cycles up to 2.91 hours for RRC idle states and up to 10.24 seconds for RRC inactive states.

[0090] Values ​​for the DRX and / or eDRX framework can be negotiated between the UE and the AMF.

[0091] Applications that wish to use Extended Idle State DRX may need to consider specific handling of mobile termination services or data transmission. For example, applications may need to consider latency tolerance for mobile termination data.

[0092] In 5GS, using higher DRX values ​​may require greater buffering.

[0093] A UE configured for eDRX can only use eDRX if the UE receives an indication from its serving cell that eDRX is permitted in an idle or inactive state. This indication can be provided, for example, via system information.

[0094] The UE's availability can be periodically notified to the network via a periodic registration update procedure using 3GPP access. This procedure can be controlled within the UE via a periodic registration update timer (referred to as T3512).

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

[0096] If the timer T3512 received by the UE in the REGISTRATION ACCEPT message contains an indication that the timer is disabled or the timer value is zero, then timer T3512 is disabled and the UE will not perform the periodic registration update process.

[0097] Due to the recent surge in smart devices, mobile network operators are facing increased data traffic, particularly through over-the-top applications. Typically, a significant portion of cellular traffic (e.g., up to 80% in some scenarios) may originate from indoor locations. The growing demand for indoor traffic and new applications such as virtual reality (VR) and extended reality (XR) can be served by WLAN or Wi-Fi (Wireless Fidelity) networks. Licensed frequencies for cellular networks (e.g., 3GPP networks using 3GPP access networks employed by mobile network operators) may experience relatively high propagation losses when used in indoor environments. Wi-Fi nodes can be provided as non-3GPP access nodes or integrated into the 5G core network. This can address the increased traffic demands and / or QoS requirements associated with traffic when the UE is located in an indoor environment. This can be achieved as follows: Figure 2 or Figure 3 As shown in the image.

[0098] UEs located in indoor environments can connect to 3GPP access networks. UEs can monitor 3GPP access networks to obtain 3GPP services.

[0099] A UE located in an indoor environment can connect to an indoor Wi-Fi access point (non-3GPP access point). The UE can use the Wi-Fi access point for at least some of its data services. The UE can use the Wi-Fi access point for voice calls, such as via Voice over Wi-Fi (VoWi-Fi).

[0100] In this scenario, UEs that establish communication channels via non-3GPP access nodes continue to consume power for 3GPP access node monitoring. Some implementations can address this issue.

[0101] Some embodiments may be designed to provide modified UE power utilization as described below.

[0102] For example, some implementations may be designed to reduce UE battery power consumption.

[0103] For example, some embodiments may be designed to improve UE power savings.

[0104] As technology advances, increasingly sophisticated features, such as artificial intelligence / machine learning (AI / ML) chipsets, are being integrated into devices, enhancing their capabilities. However, the power consumption of AI / ML chipsets is rapidly becoming a limiting factor, not only related to the UE's battery capacity but also to heat dissipation issues. Therefore, modifying the UE's power utilization (e.g., reducing UE battery power consumption) may be beneficial for certain use cases.

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

[0106] Some example implementations will be described, in which non-3GPP access and 3GPP access are within the PLMN. In this scenario, the UE can be served by the same AMF.

[0107] In some example embodiments, the UE may be served by different AMFs. An AMF providing non-3GPP access services and an AMF providing 3GPP access services may need to communicate.

[0108] In some example implementations, non-3GPP access and 3GPP access are between PLMNs.

[0109] Now refer to Figure 4 This describes an example method based on some example embodiments.

[0110] Refer to section 10 in the reference method. In some example embodiments, the UE will provide capability information to the network. This capability information can provide information about the UE's ability to support DRX when the UE is connected to a non-3GPP access node. The UE's capability may be its ability to support extended DRX.

[0111] This capability information can provide information about the UE's ability to support DRX when the UE is connected to a non-3GPP access node in a connected state (such as a connection management connection (CM-CONNECTED) state).

[0112] Refer to section 20 in the reference method. The UE can receive the DRX value when the UE is connected to a non-3GPP access node. This DRX value can be an eDRX value. Hereinafter, this DRX value will be referred to as the eDRX_WLAN value. The eDRX_WLAN value can be used when the UE is connected to a non-3GPP access node in a connected state (e.g., CM-CONNECTED state).

[0113] The eDRX_WLAN value can be received from the 3GPP access node. The eDRX_WLAN value can also be received in registration and acceptance messages, etc.

[0114] In some example embodiments, the UE will also receive the DRX value when the UE connects to a 3GPP access node. This DRX value can be a standard DRX or an eDRX. The DRX value can be as described above. Hereinafter, this DRX value will be referred to as DRX_3GPP.

[0115] It should be noted that the DRX value is referenced in this disclosure.

[0116] In some example embodiments, there may be more than one value associated with eDRX_WLAN. In some example embodiments, the eDRX_WLAN value may include one or more parameters.

[0117] In some example implementations, the eDRX_WLAN value may include a time duration (e.g., 102.4 seconds).

[0118] In some example implementations, the eDRX_WLAN value may include a multiple of the DRX_3GPP value.

[0119] In some example implementations, the eDRX_WLAN value can be defined with reference to another time reference known to the UE. For example, the eDRX_WLAN value can be defined as a multiple of another time reference known to the UE.

[0120] In some example embodiments, there may be more than one value associated with DRX_3GPP. In some example embodiments, the DRX_3GPP value may include one or more parameters.

[0121] Optionally, a timer value is provided. This timer value can be provided along with the eDRX_WLAN value or in a separate message. This timer can be a periodic registration update timer. This timer can be used when the UE is connected to a non-3GPP access network. In the following text, this timer may be referred to as T3512_WLAN.

[0122] Optionally, a timer value is provided for use when the UE connects to a 3GPP access network. This timer value can be provided along with the DRX_3GPP value or in a separate message. This timer can be a periodic registration update timer. In the following text, this timer may be referred to as T3512_3GPP.

[0123] One or more timers in the timer may allow for modified power utilization (e.g., power saving). In some example embodiments, if the timer assigned to the UE is not longer than the Extended Idle Mode DRX period, power saving may not be maximized.

[0124] In some example implementations, the time period associated with the T3512_WLAN value is longer than the time period associated with the eDRX_WLAN value.

[0125] In some example implementations, the time period associated with the T3512_3GPP value is longer than the time period associated with the DRX_3GPP value.

[0126] Refer to section number 30 in the reference method.

[0127] Determine whether the UE is in a state where it is connected to a non-3GPP access node. This state may be CM-CONNECTED for non-3GPP access. It can also determine whether the UE is in an idle state for 3GPP access. This idle state may be CM-IDLE.

[0128] Refer to section number 40 in the reference method.

[0129] If the UE is connected to a non-3GPP access node (e.g., in CM connection state) and the UE is in an idle state for 3GPP access, the UE will use the eDRX_WLAN value for discontinuous reception on 3GPP access and the T3512_WLAN value for periodic registration updates.

[0130] Therefore, in some example embodiments, when a UE registers via a non-3GPP access, as long as the UE is in a connected state for non-3GPP access (e.g., CM-CONNECTED state) and within the coverage of a non-3GPP access node, the UE will use the eDRX_WLAN value for discontinuous reception on 3GPP access. The UE can use the optional timer value T3512_WLAN for periodic registration updates.

[0131] For UEs registered via non-3GPP access and in a connected state (such as CM-CONNECTED state for non-3GPP access), the AMF can apply the eDRX_WLAN value and optionally the T3512_WLAN value.

[0132] Refer to section number 50 in the reference method.

[0133] If the UE is not connected to a non-3GPP access node, the UE will use the DRX_3GPP value and optionally the T3512_3GPP value. This may occur when the UE cannot access a non-3GPP access node. The UE may be unable to access a non-3GPP access node due to loss of coverage, traffic considerations associated with the non-3GPP access node, or the availability of a 3GPP access node that can serve the UE.

[0134] The UE can transition to an idle state (e.g., CM-IDLE state) relative to a non-3GPP access node, or deregister from a non-3GPP access node.

[0135] When the UE is in a disconnected state relative to a non-3GPP access network, the AMF can be restored to the DRX_3GPP value and optionally to the T3512_3GPP timer.

[0136] refer to Figure 4 The described example implementation can be used with non-3GPP trusted access.

[0137] refer to Figure 4 The described example implementation can be used with non-3GPP untrusted access.

[0138] refer to Figure 4 The described example implementation can be used with a UE that supports 5GC access via WLAN (N5CW).

[0139] refer to Figure 4 The example embodiments described can be used with UEs that do not support 5GC access via WLAN (N5CW).

[0140] Now refer to Figure 5a and Figure 5b An example of a message sequence diagram describing an untrusted, non-3GPP access scenario.

[0141] As mentioned at point 1, the UE initiates a 3GPP registration process. This 3GPP registration process may be performed with the AMF. In some example embodiments, the UE will provide information during the registration process indicating that the UE supports DRX (e.g., supporting eDRX when the UE has non-3GPP access).

[0142] Information provided by the UE can indicate support for eDRX when the UE has non-3GPP access. This capability information can provide information about the UE's ability to support DRX when connected to a non-3GPP access node. The UE's capability can also be its ability to support extended DRX. This capability information can provide information about the UE's ability to support DRX when connected to a non-3GPP access node in a connected state (e.g., CM-CONNECTED state).

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

[0144] In some example embodiments, the UE may determine the recommended value of the eDRX cycle based on the services that the UE can support and / or the services supported by the network via 3GPP access and / or non-3GPP access.

[0145] As mentioned at point 2, the UE receives a registration acceptance response from the AMF. This response may include a DRX value when the UE is connected to a non-3GPP access node. This DRX value may be an eDRX value. As previously discussed, this may be an eDRX_WLAN value. The eDRX_WLAN value is provided by the AMF for use when the UE is in a connected state (e.g., a CM-CONNECTED state with respect to a non-3GPP access node) and within the coverage of that non-3GPP access node.

[0146] The registration acceptance response may additionally include the DRX value when the UE connects to the 3GPP access node. This can be the DRX_3GPP value as previously described.

[0147] Optionally, the registration acceptance response may additionally include a timer value for when the UE connects to a non-3GPP access node. This could be a periodic registration update timer value. This could be the T3512_WLAN value as previously described.

[0148] Optionally, a timer value is provided for use when the UE connects to a 3GPP access node. This can be a periodically registered update timer value. Hereinafter, this timer will be referred to as T3512_3GPP.

[0149] As mentioned in point 3, the UE may transition to an idle state, such as the CM-IDLE state, for 3GPP access, after registration and one or more optional procedures and / or any required data transmissions have been completed.

[0150] As mentioned in point 4, the UE can apply the DRX_3GPP value for discontinuous reception of 3GPP access. Optionally, the UE can apply a timer (e.g., T3512_3GPP) for periodic registration updates.

[0151] As mentioned in point 5, the UE can discover WLAN networks or other non-3GPP access networks.

[0152] As mentioned in point 6, the UE can initiate a connection with a non-3GPP access node of the WLAN network.

[0153] As mentioned in point 7, the UE can perform the registration process via an untrusted non-3GPP access network. During this process, the UE can provide a globally unique AMF identifier (GUAMI) or other suitable identification information associated with the AMF. This GUAMI or other identifier is the identifier of the AMF handling 3GPP access. The GUAMI or other identifier enables the same AMF to handle connection management for both 3GPP and non-3GPP access by the UE. The registration process can be performed between the UE and the AMF.

[0154] As mentioned in point 8, the UE can be in a connected state for non-3GPP access, such as the CM-CONNECTED state. The UE can be in an idle state for 3GPP access, such as the CM-IDLE state.

[0155] As mentioned in point 9, the AMF uses the eDRX_WLAN value to determine the paging timing that will be initiated by the UE for 3GPP access monitoring. The AMF also sets the T3512 timer to the value of T3512_WLAN.

[0156] As mentioned at point 10, when the UE is within the coverage area of ​​a non-3GPP access node, the UE applies the eDRX_WLAN value for paging monitoring of 3GPP access. This allows the UE to reduce its monitoring of the 3GPP access network (e.g., RAN). This can allow for a longer sleep duration for the UE's 3GPP access functions. This can result in modified power utilization (e.g., increased battery life and / or reduced power consumption). If a T3512_WLAN timer is provided by the network, the UE also begins to use this T3512_WLAN timer. This value of T3512 can allow for a larger time between periodic registration updates.

[0157] It should be understood that the T3512_3GPP timer is running on the UE and AMF sides before the T3512_WLAN timer is used.

[0158] T3512 is a timer that describes how long a UE should notify the network that it is "available". This allows the network to know that it can reach the UE and that the UE is active and / or available. Consider an example where T3512_3GPP is set to 6 hours. The T3512_3GPP timer may already be running at the UE. The UE can start the timer after transitioning to an idle state with respect to the network. Suppose that T3512_3GPP has been running for 2.3 hours, then T3512_WLAN can start from zero, or from the last value of T3512_3GPP (e.g., 2.3 hours in the above scenario). In the latter case, the starting value of T3512_WLAN can be the last value of T3512_3GPP.

[0159] In this example, T3512_WLAN can be set to 12 hours.

[0160] As mentioned at 11 to 15, an example of the paging process will be described when the UE is in a connected state (e.g., CM-CONNECTED state for non-3GPP access) and an idle state (e.g., CM-IDLE state for 3GPP access).

[0161] As mentioned at point 11, the AMF receives a paging request from the UE. This can be derived from the downlink notification.

[0162] As mentioned at point 12, the AMF can initiate a paging process based on the eDRX_WLAN value.

[0163] As mentioned at point 13, the AMF sends a paging request for the UE to the RAN. This may include the eDRX_WLAN value.

[0164] As mentioned at point 14, the RAN (3GPP Access) uses the eDRX_WLAN value to determine the timing of paging for the UE and sends it to the UE.

[0165] As mentioned at point 15, the UE performs the connection establishment process with the RAN.

[0166] As mentioned in sections 16 to 25, a scenario where the UE stops having non-3GPP access coverage is shown.

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

[0168] As mentioned at point 17, due to coverage loss, the UE applies the DRX_3GPP value to determine the timing of paging monitoring for the idle state. If the T3512_3GPP timer is configured, the UE also uses the T3512_3GPP timer. Since timer T3512_WLAN runs at both the UE and AMF before T3512_3GPP timer is used, the starting value of T3512_3GPP can be considered the last value of T3512_WLAN or can start from zero. If, based on this starting value, the UE's T3512_WLAN timer value is greater than T3512_3GPP, the UE initiates a periodic registration update. In the example embodiment shown, the UE's T3512_WLAN timer value is less than T3512_3GPP.

[0169] As mentioned at point 18, non-3GPP access (e.g., N3IWF) detects the loss of connectivity and initiates connection release.

[0170] As mentioned at point 19, notify the AMF that the UE is unreachable via a non-3GPP access. This notification can be made via a non-3GPP access (e.g., N3IWF).

[0171] As mentioned at point 20, the AMF transitions the UE's non-3GPP access state to an idle state, such as the idle state for 3GPP access (e.g., CM-IDLE state). The AMF uses the DRX_3GPP value and optionally the T3512_3GPP timer.

[0172] As mentioned at point 21, the AMF receives requests from paging UEs. This can be derived from downlink notifications.

[0173] As mentioned at point 22, based on the UE's connection management status, the AMF determines that the UE should be paged using the DRX_3GPP value.

[0174] As mentioned at point 23, the AMF sends a paging request for the UE to the RAN. This may include the DRX_3GPP value.

[0175] As mentioned at point 24, the RAN (3GPP Access) uses the DRX_3GPP value to determine the timing of paging for the UE and sends it to the UE.

[0176] As mentioned at point 25, the UE performs the connection establishment process with the RAN.

[0177] The eDRX_WLAN value can be set to a multiple of the DRX_3GPP discontinuous reception monitoring period. This means that even if the AMF has not yet switched to DRX_3GPP, when the UE autonomously switches to DRX_3GPP monitoring, the UE will still monitor any paging sent by the network using the eDRX_WLAN period.

[0178] In some example implementations, to provide eDRX on 3GPP access, the UE maintains a connected state on non-3GPP access, such as CM-CONNECTED state. In some scenarios, 3GPP may not support paging via non-3GPP access.

[0179] The UE can transition from an idle state (e.g., CM-IDLE state) to a connected state (e.g., CM-CONNECTED state) after sending an initial NAS message. The initial NAS message can be a service request, a registration request, or a deregistration request.

[0180] When non-3GPP access nodes are available, the UE may mostly be in a connected state (e.g., CM-CONNECTED state).

[0181] In some example embodiments, the UE can be configured to receive services from the 5GC via a non-3GPP access network. When the UE deregisters from a non-3GPP access network (e.g., RM DEREGISTERED) or is in an idle state (e.g., CM-IDLE state regarding the non-3GPP access network), the UE will attempt to establish a connection with the non-3GPP access network and transition to a connected state (e.g., CM-CONNECTED state) upon successful connection. The UE will attempt such a connection to the non-3GPP access network unless the network prohibits it (e.g., due to network congestion).

[0182] Some example implementations can provide modified UE power utilization as described below.

[0183] Some example implementations can, for instance, improve the battery life of the UE.

[0184] Some example implementations can, for instance, reduce the energy used by the UE.

[0185] Some example implementations can reduce UE battery consumption, for example, given the amount of time a device is within WLAN coverage.

[0186] Some example implementations can reduce the buffering requirements of elements (such as 5GS elements) when a given access is available via one or more non-3GPP access nodes.

[0187] refer to Figure 6 The figure illustrates methods in some example embodiments.

[0188] This method can be performed by a device.

[0189] The device may include suitable components, such as circuitry for providing the method.

[0190] Alternatively or additionally, the device may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to provide at least the following methods.

[0191] Alternatively or additionally, the device may be, for example, regarding Figure 7 The apparatus under discussion.

[0192] The corresponding methods can be provided through computer program code or computer executable instructions.

[0193] The method may include, as mentioned in A1, registering with the 3GPP core network, the registration including providing information indicating that the user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network.

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

[0195] Figure 7 A block diagram of apparatus 10 is illustrated by way of example. Apparatus 10 includes, for example, at least one processor 12 and at least one memory 14, which stores instructions 15 that, when executed by the at least one processor, cause apparatus 10 to perform one or more methods as disclosed herein and any of their example embodiments. In example embodiments, the at least one memory and instructions (e.g., computer program code, software, etc.) together with the at least one processor are configured to cause apparatus 10 to perform one or more methods as disclosed herein and any example embodiments of their example embodiments.

[0196] Processor 12 may include, or be configured as, one or more circuits configured to perform various stages of the methods according to the exemplary embodiments described herein. As used herein, the term "circuit" may refer to one or more of the following: (a) a hardware circuit implementation, such as an implementation of analog, digital, and / or quantum circuits; and (b) a combination of hardware circuitry and software, such as, where applicable: (i) a combination of analog, digital, and / or quantum hardware circuitry with software / firmware; and (ii) any or all portions of a hardware processor (including digital processors and / or quantum processors), along with software and memory, which work together to enable a device (such as an apparatus, computing device, user equipment, or server) to perform various functions; and (c) any or all portions of a hardware circuitry, such as a microprocessor, processor, and / or quantum processor, which requires software (e.g., firmware) to operate, but may be absent when it is not required to operate. This definition of circuitry applies to all uses of the term herein, including in any claim. As yet another example, the term "circuit" as used herein also encompasses only hardware circuitry or a processor (or multiple processors) or portions thereof, and their accompanying software and / or firmware implementations. For example, and as applicable to certain claim elements, the term "circuit" also encompasses baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0197] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 is at least partially located outside the device 10, but is accessible to the device 10.

[0198] Instruction 15 may be included in a computer-readable medium or a non-transient computer-readable medium. As used herein, the term non-transient is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., random access memory RAM versus read-only memory ROM).

[0199] For example, device 10 is a terminal device, such as Figure 1 The UE. As another example, the device is included in such a terminal device, for example, as a chipset configured to control the terminal device. Device 10 can be set or configured to perform at least Figure 4 , Figure 5a , Figure 5b or Figure 6 The methods and / or any one or more of the described example embodiments.

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

[0201] Device 10 includes a radio interface 16. The radio interface 16 provides communication capabilities to device 10. The radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. The radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. More than one receiver may be included. More than one transmitter may be included. The radio interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. More than one transceiver may be included.

[0202] Device 10 may include a user interface 18, which includes at least one of, for example, a keyboard, microphone, touch screen, display screen, speaker, etc. User interface 18 can be used by a user to control the device. User interface 18 may be located external to device 10. For example, device 10 may be connected to another device (such as a computer) via a wireless or wired connection, and device 10 may be controlled by a user via that computer.

[0203] In some example embodiments, at least some of the processes described herein may be performed by means including components for performing at least some of the described processes. Components for performing the method steps disclosed herein may include software and / or hardware components of means 10. For example, at least one processor 12, memory 14, and computer program code constitute components for performing one or more methods disclosed herein and any of their various example embodiments. As used herein, the term “component” should be understood in the singular (i.e., a single element) or plural (i.e., a combination of multiple elements). Thus, the term “component for [performing A, B, C]” should be interpreted to encompass means in which there is only one component for performing A, B, and C, or multiple separate components for performing A, B, and C, or partially or completely overlapping components for performing A, B, and C. Furthermore, the terms "component for performing A, component for performing B, component for performing C" should be interpreted as covering an apparatus in which there is only one component for performing A, B, and C, or multiple separate components for performing A, B, and C, or partially or completely overlapping components for performing A, B, and C.

[0204] Although various exemplary embodiments of the present disclosure have been described above with reference to the accompanying drawings, it is obvious that the various exemplary embodiments are not limited thereto, but can be modified in several ways within the scope of the present disclosure. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the various exemplary embodiments. It should be understood that the scope of the present disclosure can be implemented and adapted in various ways as technology advances. Furthermore, those skilled in the art will appreciate that any of the exemplary embodiments of the present disclosure can, but is not required to, be combined in various ways with any other exemplary embodiments of the present disclosure.

Claims

1. A user equipment, comprising: Components for registering with the 3GPP core network under the 3rd Generation Partnership Project, the registration including providing information indicating that the user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; as well as Components 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 relating to discontinuous reception on a 3GPP access network.

2. The user equipment according to 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 according to claim 2, wherein the connection state with the non-3GPP access network is a connection management state.

4. The user equipment according to any one of claims 1 to 3, wherein the first value for discontinuous reception is a value for extended discontinuous reception.

5. The user equipment according to any one of claims 1 to 4, wherein the first value for discontinuous reception is: a value for determining one or more paging timings for the user equipment with respect to the 3GPP access network.

6. The user equipment according to any one of claims 1 to 5, comprising a component 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 according to any one of claims 1 to 6, wherein the component for receiving the first value for discontinuous reception is further configured to: receive a first timer value, the first timer value defining a time period, the time period being used to periodically notify the 3GPP access network of the availability of the user equipment when the user equipment is connected to the non-3GPP access network.

8. The user equipment of claim 7, comprising a component 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 according to any one of claims 1 to 8, wherein the component for receiving the first value for discontinuous reception is further configured to: receive a second value for discontinuous reception for use when the user equipment does not have 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 of claim 9, comprising a component for applying the second value for discontinuous reception when the user equipment is not covered via the non-3GPP access network.

11. The user equipment of claim 10, further comprising a component for determining that the user equipment does not have coverage via the non-3GPP access network, wherein, in response to determining that the user equipment does not have coverage via the non-3GPP access network, the component for applying the second value applies the second value.

12. The user equipment according to any one of claims 1 to 11, wherein the component for receiving the first value for discontinuous reception is further configured to: receive a second timer value, the second timer value defining a time period for periodically notifying the 3GPP core network of the availability of the 3GPP access network to the user equipment when the user equipment does not have coverage via the non-3GPP access network.

13. The user equipment according to any one of claims 1 to 12, wherein the non-3GPP access network is served by a non-roaming 3GPP core network.

14. The user equipment according to any one of claims 1 to 13, wherein the non-3GPP access network and the 3GPP access node are served by the access and mobility management network functions of the 3GPP core network.

15. A method for communication, comprising: Registering with the 3GPP core network under the 3rd Generation Partnership Project, the registration includes providing information indicating that the user equipment is configured to support discontinuous reception when the user equipment is on a non-3GPP access network; as well as 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 on a 3GPP access network.

16. The method of 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 of claim 15, wherein the first value for discontinuous reception is a value for extending discontinuous reception.

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

19. The method according to any one of claims 15 to 18, comprising: When the user equipment is connected to the non-3GPP access network and idle with respect to the 3GPP access network, the first value for discontinuous reception is applied.

20. The method according to any one of claims 15 to 19, comprising: A first timer value is received, the first timer value defining a time period, the time period being used to periodically notify the 3GPP access network of the availability of the user equipment when the user equipment is connected to the non-3GPP access network.

21. The method of claim 20, comprising: The first timer value is applied when the user equipment is connected to the non-3GPP access network and idle with respect to the 3GPP access network.

22. The method according to any one of claims 15 to 21, comprising: A second value is received for discontinuous reception, to be used when the user equipment does not have coverage via the non-3GPP access network, the second value being for discontinuous reception with respect to the 3GPP access network.

23. The method of claim 22, comprising: When the user equipment is not covered by the non-3GPP access network, the second value for discontinuous reception is applied.

24. The method of claim 23, comprising: It is determined that the user equipment does not have coverage via the non-3GPP access network, wherein the second value is applied in response to determining that the user equipment does not have coverage via the non-3GPP access network.

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

Images