WO2025120027A1

WO2025120027A1 - Measurement and initial access configuration steering for redcap/eredcap devices during fallback

Info

Publication number: WO2025120027A1
Application number: PCT/EP2024/084801
Authority: WO
Inventors: Volker Breuer; Sahil Bahri; Florian Denzin
Original assignee: Telit Cinterion Deutschland GmbH
Current assignee: Telit Cinterion Deutschland GmbH
Priority date: 2023-12-08
Filing date: 2024-12-05
Publication date: 2025-06-12
Anticipated expiration: 2026-06-08

Abstract

Systems and methods for operating a user equipment supporting reduced capability (REDCAP) operation or enhanced reduced capability (eREDCAP) operation, include: determining an available network; determining a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network; and operating the UE according to the determined supported mode of principal operation, wherein, if the determined supported mode of principal operation is not available, then the method comprises operating the UE according to the determined supported fallback mode of operation.

Description

MEASUREMENT AND INITIAL ACCESS CONFIGURATION STEERING FOR REDCAP/EREDCAP DEVICES DURING FALLBACK

FIELD OF THE INVENTION

[0001] The invention relates generally to steering measurements and initial access configurations for devices during a fallback mode of operation, in particular for reduced capability or evolved reduced capability devices.

BACKGROUND

[0002] It is known that REDCAP (reduced capability) and eREDCAP (enhanced/evolved reduced capability) will be introduced within the framework of the Third Generation Partnership Project “3GPP” Release 17 and Release 18, respectively. The REDCAP/eREDCAP technology only works if the new radio (NR) network is of a standalone (SA) type of said release or higher, otherwise the user equipment (UE) will work in a so-called fallback mode of operation.

[0003] Given the time taken for different network operators to upgrade different parts of the network, user equipments may need to operate in different network types, and thus there may be different supported modes of fallback operation, and smooth interoperability when the need for a network change arises may be affected.

[0004] Accordingly, there is a need in the art for systems and methods which address these problems.

BRIEF SUMMARY OF THE INVENTION

[0005] According to one or more embodiments of the invention, there is provided a method for operating a user equipment (UE) supporting reduced capability (REDCAP) operation or enhanced reduced capability (eREDCAP) operation, the method comprising: determining an available network; determining a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network; and operating the UE according to the determined supported mode of principal operation, wherein, if the determined supported mode of principal operation is not available, then the method comprises operating the UE according to the determined supported fallback mode of operation.

[0006] According to some embodiments, the method includes determining the supported mode of principal operation and the supported fallback mode of operation using network data stored by the UE.

[0007] According to some embodiments, the network data is comprised in a lookup table which associates with the network, at least one of: a 3GPP release number of the network; a 5G standalone (SA) network support indication; a 5G non-standalone (NSA) network support indication; the supported principal mode of operation; the supported fallback mode of operation; a supported feature indication; a measurement periodicity; or a startup mode, wherein the network is identified by at least one of a mobile country code “MCC”, or a mobile network code “MNC”.

[0008] According to some embodiments, the supported fallback mode of operation is one of: Long Term Evolution (LTE); Enhanced Mobile Broadband (eMBB); restricted eMBB; Universal Mobile Telecommunications System (UMTS); or Global System for Mobile Communications (GSM).

[0009] According to some embodiments, the lookup table comprises network data for one or more different networks deployed by one or more different network operators.

[00010] According to some embodiments, the lookup table is maintained by a device management service.

[00011] According to some embodiments, the method includes modifying a startup mode of the UE when the UE has previously determined that the network does not support the principal mode of operation.

[00012] According to some embodiments, a new startup mode to be active at a next startup is set to the determined supported fallback mode of operation.

[00013] According to some embodiments, the method includes evaluating whether a new network is available based on a change in the MNC or MCC since a last startup, and modifying the startup mode of the UE to be the principal mode of operation if the principal mode of operation is supported and available on the new network.

[00014] According to some embodiments, the method includes reducing a measurement periodicity based on the UE determining that the network does not support the principal mode of operation. [00015] According to some embodiments, the method includes disabling the measurement periodicity until at least one of the MNC or MCC changes.

[00016] According one or more embodiments, there is provided a computer readable module containing instructions which, when executed by at least one processor in a user equipment “UE” supporting reduced capability (REDCAP) operation or enhanced reduced capability (eREDCAP) operation, cause the UE to: determine an available network; determine a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network; and operate according to the determined supported mode of principal operation, wherein, if the determined supported mode of principal operation is not available, then operate according to the determined supported fallback mode of operation.

[00017] According to some embodiments, the computer readable module contains network data suitable for determining the supported mode of principal operation and the supported fallback mode of operation of the network.

[00018] According to some embodiments, the network data is comprised in a lookup table which associates with the network, at least one of: a 3GPP release number of the network; a 5G standalone (SA) network support indication; a 5G non-standalone (NSA) network support indication; the supported principal mode of operation; the supported fallback mode of operation; a measurement periodicity; or a startup mode, wherein the network is identified by at least one of a mobile country code “MCC”, or a mobile network code “MNC”.

[00019] According to one or more embodiments, there is provided a user equipment “UE” configured to perform one or more methods disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

[00020] Non-limiting examples of embodiments of the disclosure are described below with reference to figures attached hereto. Dimensions of features shown in the figures are chosen for convenience and clarity of presentation and are not necessarily shown to scale. The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may be understood by reference to the following detailed description when read with the accompanied drawings. Embodiments are illustrated without limitation in the figures, in which like reference numerals indicate corresponding, analogous, or similar elements, and in which:

[00021] Fig. 1 shows an overview of 5G architectures;

[00022] Fig. 2 shows a flowchart of a method, according to some embodiments of the invention;

[00023] Figs. 3 A, 3B, and 3C show different example connection scenarios where the supported features of the available networks are different;

[00024] Fig. 4 shows a block diagram of an exemplary computing device which may be used with some embodiments of the present invention;

[00025] Fig. 5 shows a block diagram of an exemplary user equipment (UE) which may be used with embodiments of the present invention; and

[00026] Fig. 6 shows a block diagram of an exemplary base station (BS) which may be used with embodiments of the present invention.

[00027] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION

[00028] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention can be practiced without these specific details. In other instances, well-known methods, procedures, components, modules, units and/or circuits have not been described in detail so as not to obscure the invention.

[00029] As used herein, (e)REDCAP is used to refer to a device which is either a REDCAP (reduced capability) device or an eREDCAP (evolved/enhanced reduced capability) device. (e)REDCAP devices may be as defined by ETSI in TS 138 306 (for example release 17 and 18). For example, for REDCAP, the maximum bandwidth is 20 MHz for FR1, and is 100 MHz for FR2. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 or wider than 100 MHz in FR2 are not supported by RedCap UEs. An eREDCAP UE is the UE with reduced peak data rate and, with or without reduced baseband bandwidth in FR1, for example the maximum bandwidth is 20 MHz for FR1. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 are not supported by eRedCap UEs. eRedCap UEs do not support operation in FR2 and in FR1 60kHz SCS. Such use of REDCAP/eREDCAP will be known and understood by one skilled in the art.

[00030] The Inventors anticipate that some network operators may bar or prevent a REDCAP UE in restricted eMBB mode from legacy 5G NR 3 GPP Rel.-15 and Rel.-16 networks, in which case the UE may drop automatically to LTE/4G in fallback mode. Other fallback modes may be required of the UE depending on the network architecture and supported features.

[00031] In fallback mode, the UE may work in LTE as Cat-M or Catlbis/Catl/2/4/6 depending on what capabilities are supported. The UE may fallback in 5G SA networks of lower releases e.g. Rel.-15 or 16 as an eMBB (enhanced mobile broadband) device if supported by the network operator, especially for frequency bands where REDCAP and eMBB devices have same capabilities. The reduced receiver bandwidth of the REDCAP device may be larger than or equal to the frequency bandwidth operated.

[00032] Since network operators typically only own/operate a 20MHz bandwidth portion in the lower frequency bands, and a REDCAP device supporting 256QAM with 2 RX, this may mean that an (e)REDCAP device in such a small bandwidth band may not be able to be nominally distinguished from an eMBB device which supports only one frequency band. For example, eMBB in frequency bands below 2500MHz are required per 3GPP only to have 2 receivers (Limited space and receivers are only independent if spaced by half of the wavelength, so 4 receivers are not recommended in low frequency bands). 256QAM modulation is max modulation order of normal eMBB devices. So such an (e)REDCAP device fulfils all requirements as an eMBB device and can be treated/handled accordingly by the network.

[00033] In addition, for such devices, technology selection at startup can be a critical issue. The Inventors anticipate that customers would like to see the highest supported technology (e.g. 5G/New Radio “NR”) at startup. However, it may be advantageous if startup time is minimized, in particular for subsequent startup routines to improve operational efficiency especially for battery powered use cases. Hence choice of technology may be an important factor here.

[00034] Furthermore, there are multiple reasons why, in networks where REDCAP would normally be supported, the device may drop into fallback mode (e.g. a coverage hole), and for other networks where searching for NR is not technically sensible from a REDCAP device perspective. The 3 GPP measures and indications for such scenarios involving REDCAP/eREDCAP typically only work under “ideal” conditions, for example where UE, LTE and NR network are of same advanced release e.g. Rel.-17 or higher, otherwise the UE may need to employ less effective “best effort” modes of operation. However, the Inventors anticipate that it is unlikely that for an eREDCAP device which due to an NR coverage hole or for other reasons falls back to LTE, that the operator has invested in LTE up to Rel.-18. As such, in fallback to an LTE Rel.-14 network there is no indication for NR at all, in case of LTE Rel.-16 NR standalone could be indicated but not whether release is high enough to support REDCAP i.e. Rel.-17 will not be indicated. The Inventors also find it doubtful that a network operator investing in 5G will take care to update LTE for smooth interworking with REDCAP.

[00035] Given all of these different combinations (e.g.: REDCAP supported, eREDCAP supported, support only in SA networks, support only in NSA networks , (e)REDCAP supported in legacy NR networks (e.g. Rel.-15/16)), the Inventors have identified a need for a discriminator feature for (e)REDCAP devices to be distinguishable from other (e)REDCAP devices with different configurations that enable said devices to perform best decision on NR measurements and re-selection or whether to remain in fallback mode. For example, an eREDCAP device supporting only IRx but where an NR SA network only supports 2RX REDCAP devices, the device will be rejected on NR even when the Release would be high enough, because the required support for IRx is not there in the network, and hence the device will operate in fallback as a Catibis device. Embodiments of the invention may address these problems, and may have the advantage of smoother operation, assisting the UE behaviour for power saving, decreasing startup time, and improved connectivity.

[00036] Embodiments of the invention may solve the above identified problems by determining a supported principal mode of operation (e.g. “main” or default mode) and a supported fallback mode of operation supported by a network available to a user equipment (UE) and operating the UE according to the determined supported mode of principal operation, or operating the UE according to the determined supported fallback mode of operation if the determined supported mode of principal operation is not available. A measurement periodicity and/or a startup mode of the UE may be changed (e.g. switched) to reflect the features supported by the available networks. [00037] Fig. 1 shows an overview of 5G architectures. Option 1 shows plain (e.g. legacy) LTE and option 2 shows 5G standalone. Combining one or more of the possible base stations eNB (4G), gNB (5G) with one of the respective cores EPC (4G) or 5GC (5G) leads to the various architecture options.

[00038] Typically, most operators are currently running 5G network architectures labelled as Option 3/3a in Fig. 1. This may mean running an LTE network connected to an EPC core for authentication and registration and in case of connected mode adding the 5G gNB as an additional data pump.

[00039] In option 3/3a architecture, a 5G network is provided as a non-standalone (NSA) network, and includes a UE 100 communicating with an enhanced node B (eNB) base station and where some 5G functionality is provided by a next generation node B (gNB). The core network is an LTE core network using Evolved Packet Core (EPC) system architecture. In Option 3/3 a all authentication signalling is done by the eNB, and only once the UE is connected does the 5G gNB begin to play a role.

[00040] In option 2 architecture, a 5G network is provided as a standalone network. The UE 100 communicates with a gNB which communicates with the 5G core network (5GC). Only in a network according to option 2 can (e)REDCAP devices work as fully intended.

[00041] (e)REDCAP devices can also work in networks according to option 4 architectures, where authentication and signalling are carried by a gNB to 5GC otherwise the devices cannot work as a (e)REDCAP device. For example, option 4 performs all authentication actions via gNB to 5GC and would only add in connected mode the LTE base- station. Hence a REDCAP device could work in option 4. However, anticipated EN-DC when in connected mode, (enhanced dual connectivity to gNB and eNB) would not be supported by the device. Hence a second standalone mode (4a) is part of the option 4 that would be used from perspective of a REDCAP device. The same would apply for a 5G only device. The anticipated EN-DC (enhanced dual connectivity to gNB and eNB) to increase data throughput when in connected mode, would not be supported by the REDCAP device, and hence only the 5G fraction of said architecture would be used, which from REDCAP device perspective is then the same as option 2.

[00042] Fig. 2 shows a flowchart of a method 200 for operating a user equipment (UE) supporting reduced capability (REDCAP) operation or enhanced/evolved reduced capability (eREDCAP) operation, according to some embodiments of the invention. [00043] Method 200 may include determining an available network (Step 210). Available networks may be determined using means known in the art, for example using a broadcast channel, system information block (SIB), or the like.

[00044] Method 200 may include determining a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network (Step 220).

[00045] For example, a network may support any combination of principal modes of operation and fallback modes of operation depending on the network architecture, and may be influenced, for example, by such factors as age of the network (e.g. a 3GPP release of elements of the network). [00046] As discussed for Fig. 1, a network may support (e)REDACP if the UE communicates with a gNB which communicates with 5GC.

[00047] In some embodiments, determining the supported mode of principal operation and the supported fallback mode of operation comprises using network data stored by the UE. For example, the network data may be stored in a memory or chip installed in the UE.

[00048] In some embodiments, the network data is included in a lookup table or other equivalent data structure. The lookup table may associate the network with at least one of: a 3 GPP release number of the network; a 5G standalone (SA) network support indication; a 5G non-standalone (NSA) network support indication; the supported principal mode of operation; the supported fallback mode of operation; a supported feature indication; a measurement periodicity; and/or a startup mode. The network, or networks where the lookup table includes multiple networks, may be identified by at least one of a mobile country code “MCC”, and/or a mobile network code “MNC”.

[00049] A supported feature indication may include if the network supports half-duplex operation (e.g. HD-FDD). A measurement periodicity may include a frequency of measurements for NR that the UE should switch to, and may be based on, for example, a known state of deployment of other NR networks in the geographic vicinity of the network in question, for example based on the MNC and/or MCC.

[00050] Method 200 may include operating the UE according to the determined supported mode of principal operation (Step 230). For example, if the network supports 5G REDCAP as the principal mode of operation, the UE may be operated as a 5G REDCAP device. [00051] Method 200 may include, if the determined supported mode of principal operation is not available, then operating the UE according to the determined supported fallback mode of operation (Step 240).

[00052] The supported mode of principal operation may not be available for example due to a coverage hole in the network. A principal mode of operation may not be available if a network does not support it: for example for a 5G REDCAP device, the principal mode of operation is 5G REDCAP but no available networks may support that mode of operation (for example because the only networks are of Rel.-16 or lower) and thus embodiments of the invention may include operating the UE in a supported fallback mode of that network.

[00053] In some embodiments, the supported fallback mode of operation is one of: Long Term Evolution (LTE); Enhanced Mobile Broadband (eMBB); restricted eMBB; Universal Mobile Telecommunications System (UMTS); or Global System for Mobile Communications (GSM). LPWAN mode (low power wide area) may be used for 4G loT devices, especially Cat-M being available for LTE. For example, Low end eREDCAP devices with single Rx and HD-FDD may fallback to Cat-M.

[00054] A lookup table, according to some embodiments of the invention, may include data for one or more different networks deployed by one or more different network operators. For example, the lookup table may include data for first, second, and third networks deployed by network operator A, fourth and fifth networks deployed by network operator B, and sixth network deployed by network operator C. Each network may be distinguished by MNC and/or MCC.

[00055] The lookup table may be maintained by a device management service. For example, remote editing/updating of entries in the lookup table may be performed by a remote server operated by a device management service. An example device management service is OneEdge TM provided by Telit Cinterion.

[00056] The lookup table may be edited in response to, for example, network upgrades, or acquisition of a network operator by a different network operator.

[00057] In some embodiments, method 200 may include modifying (e.g. changing) a startup mode of the UE when the UE has previously determined that the network does not support the principal mode of operation. For example, an initial startup mode of a UE may be 5G eREDCAP, however if it is determined that the available network does not support 5G eREDCAP it may not make sense to start the UE in 5G eREDCAP mode to only have to fallback to the supported fallback of operation (e.g. eMBB). Accordingly, embodiments of the invention may include modifying a startup mode of the UE when it is known that the available networks in the vicinity of the UE do not support other startup modes. This may save battery resources, for example by avoiding unnecessary scanning from the UE for the network regarding the availability or lack thereof of principal modes of operation.

[00058] As an example, the lookup table may contain network data that suggests that when in Germany (e.g. determined by MCC) or within a respective network in Germany (e.g. determined by MNC/MCC), a certain principal mode of operation (e.g. an initial startup mode) is not supported. Thus, having identified this, embodiments of the invention may include changing the startup mode of the UE, e.g. to startup in fallback mode, thereby conserving battery resources and promoting smoother operation.

[00059] Accordingly, in some embodiments, the new startup mode to be active at a next startup is set to the determined supported fallback mode of operation.

[00060] To account for the UE moving and entering an area covered by a network that does support the principal mode of operation, embodiments of the invention may include evaluating whether a new network is available based on a change in the MNC or MCC since a last startup, and modifying the startup mode of the UE to be the principal mode of operation if the principal mode of operation is supported and available on the new network. For example, the startup mode may be changed, e.g. reverted to the principal mode of operation, if it is detected that the UE has moved such that the MNC and/or MCC has changed.

[00061] According to some embodiments, method 200 includes reducing the measurement periodicity based on the UE determining that the network does not support the principal mode of operation. For example, if it is determined that the network does not support the principal mode of operation, it may be unnecessary to regularly query the available networks to see if the principal mode of operation is available, particularly where the UE has not moved. In this way, embodiments of the invention may “steer” the measurements of the UE. Reducing the measurement periodicity may go as far as disabling the measurement periodicity, which may last until at least one of the MNC or MCC changes (which may indicate that the UE has moved, and there may now be other available networks that support the principal mode of operation).

Table 1

[00062] Table 1 shows an example lookup table according to some embodiments of the invention. The lookup table in Table 1 identifies the available networks based on MNC and MCC. The available networks are 00A/XXX and 00B/XXX, e.g. the mobile networks 00A and 00B are covering the same country with mobile country code XXX (e.g. they have the same MCC).

[00063] The lookup table may indicate if the network(s) support (e.g. by a Yes/No Y/N value) new radio standalone (e.g. column 2).

[00064] The lookup table may indicate if the network(s) support new radio standalone lower than Rel. 17 (e.g. Rel.-15/16) in which an (e)REDCAP will need to fallback to an eMBB mode of operation (e.g. column 3).

[00065] The lookup table may indicate if the network(s) support new radio standalone of less than Rel.-17 (e.g. column 4).

[00066] The lookup table may indicate if the network(s) support Rel.-17 REDCAP operation (e.g. column 5).

[00067] The lookup table may indicate if the network(s) support Rel.-l 8 eREDCAP operation (e.g. column 6).

[00068] The lookup table may indicate if the network(s) support eREDCAP 20MHz + PR1 operation (e.g. column 7). For an eREDCAP device of Rel.- 18 having an RF bandwidth of 20MHz, supporting signalling and DRBs (dedicated radio bearer) over the entire 20MHz RX bandwidth, the throughput is limited to a maximum throughput of about lOMBits.

[00069] The lookup table may indicate if the network(s) support eREDCAP BW3/PR3 + PR1 operation (e.g. column 8). For an eREDCAP device of Rel.- 18 having an RF bandwidth of 20MHz, supporting signalling over the entire 20MHz but when operating in connected mode supporting a maximum accumulated bandwidth for the DRBs of 5MHz, the throughput is limited to a maximum throughput of about lOMBits.

[00070] The aforementioned types may need to be respected by the base station scheduler, e.g. whether to restrict scheduling to 10Mbit throughput and band limitation, or whether to distribute the throughput in connected mode across the entire 20MHz.

[00071] The lookup table may indicate if the network(s) support 1 RX feature operation (e.g. column 9). [00072] The lookup table may indicate if the network(s) support HD-FDD (Half-duplex frequency division duplexing) operation (e.g. column 10).

[00073] The lookup table may include other columns for other support indications, and could be updated in future with other support indications that have yet to be developed.

[00074] Network 00A may be seen as a typical entry for a 5G NSA network e.g. architecture option 3 of Fig. 1. This may mean that 5G SA is not available and hence no (e) REDCAP specific features are supported.

[00075] Network 00B may be seen as a typical entry for a 5G standalone network of Rel.-17 hence supporting REDCAP with a certain feature set, but not eREDCAP devices which require Rel.-18 standalone.

[00076] Figs. 3 A, 3B, and 3C show different example connection scenarios where the supported features of the available networks are different. In these Figures, time may be considered as progressing downwards.

[00077] In Fig. 3A, a first network operator, OP1, has deployed a 5G REDCAP SA network 310. A 5G (e)REDCAP supporting user equipment 300 operating according to embodiments of the invention and scanning available networks identifies network 310, and receives an indication (e.g. via a stored or otherwise accessible lookup table of network data) that the network supports 5G (e) REDCAP, and so UE 300 attaches on the network (311). Subsequently, the UE enters a coverage hole in network 311 (312) and falls back to a fallback mode 320 of network 310, which here is LTE. The UE attaches to the fallback mode of the network (313). The UE may periodically maintain measurements for NR, in order to be able to return to / regain 5G REDCAP SA operation at the next opportunity. For example, as shown in Fig. 3A, UE 300 may return to / regain 5G (e)REDCAP SA operation at 314, for example because the UE has moved out of the coverage hole.

[00078] In Fig. 3B, a first network operator, OP1, has deployed a 5G NSA network 330. A 5G (e)REDCAP supporting user equipment 300 operating according to embodiments of the invention and scanning available networks identifies network 330, and receives an indication (e.g. via a stored or otherwise accessible lookup table of network data) that the network does not support 5G (e)REDCAP, but does support LTE (network 340) and so UE 300 falls back and registers on LTE network 340 (331). LTE network 340 may send an attachment acknowledgement 332 to UE 300. UE 300 may limit or disable its NR search measurements whilst not moving. If the UE moves to another area (e.g. there is a change in MNC and/or MCC) then embodiments of the invention may cause the UE to resume or increase the density of NR measurements in an attempt to identify a network which supports the principal mode of operation of 5G (e)REDCAP, for example so that the UE can regain (e)REDCAP operation. Additionally, embodiments of the invention may modify the startup mode of UE 300, for example changing the startup mode to LTE, to decrease the startup time in network 340: the Inventors have identified that it is a waste of time and resources to startup in 5G modes when it is known (e.g. based on the lookup table) that the available networks in the geographic vicinity of the UE (e.g. as determined by MNC/MCC) do not support 5G operation.

[00079] In Fig. 3C a first network operator, OP1, has deployed a 5G NSA network 350. A 5G (e)REDCAP supporting user equipment 300 operating according to embodiments of the invention and scanning available networks identifies network 350, and receives an indication (e.g. via a stored or otherwise accessible lookup table of network data) that the network does not support 5G REDCAP, but does support LTE (network 360) and so UE 300 falls back and attaches on LTE network 360 (351). LTE network 360 may send an attach acknowledgement 352 to UE 300. UE 300 may determine (e.g. via a stored or otherwise accessible lookup table of network data) that a second network operator has a 5G SA REDCAP network deployed (network 370). UE 300 may stay on LTE network 360, and may correspondingly, according to embodiments of the invention, change/modify a startup mode to start in LTE mode. Alternatively, UE 300 may perform RPS (remote provisioning service, e.g. to contact a server to acquire a new or additional set of credentials so as to be able to change the operator) for example using a remote service, to change operator and register as an (e)REDCAP device on 5G SA network 370 of operator 2 (e.g. shown by setup request 353, with corresponding acknowledgment 354). UE 300 may receive the necessary credentials to access the network of Operator 2 via a device management service, such as OneEdge.

[00080] Fig. 4 shows a block diagram of an exemplary computing device 400 which may be used with some embodiments of the present invention.

[00081] As described herein, any of: a user equipment; a network element; a core network element a base station; and/or a server (e.g. a server in connection with a core network element), may be, or may include elements of, a computing device 400 as shown in Fig. 4.

[00082] Computing device 400 may include a controller or computer processor 405 that may be, for example, a central processing unit processor (CPU), a chip or any suitable computing device, an operating system 415, a memory 420, a storage 430, input devices 435 and output devices 440 such as a computer display or monitor displaying for example a computer desktop system.

[00083] Operating system 415 may be or may include code to perform tasks involving coordination, scheduling, arbitration, or managing operation of computing device 100, for example, scheduling execution of programs. Memory 420 may be or may include, for example, a Random Access Memory (RAM), a read only memory (ROM), a Flash memory, a volatile or nonvolatile memory, or other suitable memory units or storage units. At least a portion of Memory 420 may include data storage housed online on the cloud. Memory 420 may be or may include a plurality of different memory units. Memory 420 may store for example, instructions (e.g., code 425) to carry out a method as disclosed herein, such as method 200. Memory 420 may use a datastore, such as a database.

[00084] Executable code 425 may be any application, program, process, task, or script. Executable code 425 may be executed by controller 405 possibly under control of operating system 415. For example, executable code 425 may be, or may execute, one or more applications performing methods as disclosed herein, such as method 200. In some embodiments, more than one computing device 400 or components of device 400 may be used. One or more processor(s) 405 may be configured to carry out embodiments of the present invention by, for example, executing software or code.

[00085] Storage 430 may be or may include, for example, a hard disk drive, a floppy disk drive, a compact disk (CD) drive, a universal serial bus (USB) device or other suitable removable and/or fixed storage unit. Data described herein may be stored in a storage 430 and may be loaded from storage 430 into a memory 420 where it may be processed by controller 405. Storage 430 may include cloud storage. Storage 430 may include storing data in a database. Storage 430 may include or contain network data, such as a lookup table described herein, for use in methods according to embodiments of the invention, such as method 200.

[00086] Storage 430 may store, for example, an MNC, MCC, IMSI, secret value, UE capability information, or other data.

[00087] Input devices 435 may be or may include a mouse, a keyboard, a touch screen or pad or any suitable input device or combination of devices. Input devices 435 may include a receiver, such as an antenna receiver. Output devices 440 may include one or more displays, speakers and/or any other suitable output devices or combination of output devices. Output devices 440 may include a transmitter, such as an antenna transmitter. Any applicable input/output (I/O) devices may be connected to computing device 400, for example, a wired or wireless network interface card (NIC), a modem, printer, a universal serial bus (USB) device or external hard drive may be included in input devices 435 and/or output devices 440.

[00088] Embodiments of the invention may include one or more article(s) (e.g., memory 420 or storage 430) such as a computer or processor non-transitory readable medium, or a computer or processor non-transitory storage medium, such as for example a memory, a disk drive, or a USB flash memory encoding, including, or storing instructions, e.g., computer-executable instructions, which, when executed by a processor or controller, carry out methods disclosed herein.

[00089] Reference is now made to Fig. 5, which is a block diagram of an exemplary user equipment (UE) 500 which may be used with embodiments of the present invention. UE 500 may be, for example, a smartphone or internet of things (loT) device. UE 600 may include a REDCAP device or eREDCAP device, such as a smartphone with (e)REDCAP capabilities.

[00090] UE 500 may include a radio interface 505. Radio interface 505 may include an antenna, a transceiver and/or any other suitable component to allow communication between UE 500 and a telecommunications network.

[00091] UE 500 may include a user identity module 510. User identity module 510 may store userspecific information such as the International Mobile Subscriber Identity (IMSI) and may be used for authentication and authorization on the telecommunications network.

[00092] UE 500 may include a mobile equipment 515. Mobile equipment 515 may include a processor, a memory, a display and a user interface.

[00093] UE 500 may include a battery 520. Battery 520 may provide power to UE 500, allowing it to operate without being connected to an external power source.

[00094] UE 500 may include an operating system 525. Operating system 525 may manage UE’s 500 resources and/or provide a platform for running applications.

[00095] UE 500 may include application software 530. Application software 530 may be user- installed and system applications that run on UE 500, providing UE 500 various functionalities.

[00096] UE 500 may include a user interface 535. UE 535 may include a touchscreen, buttons, display and/or any other suitable components through which users may interact with UE 500.

[00097] UE 500 may include sensors 540. Sensors 540 may include accelerometers, gyroscopes, GPS, and ambient light sensors, cameras and/or any other suitable sensors known in the art. Sensors 540 may allow features such as orientation detection, location-based services, and any other suitable features known in the art.

[00098] UE 500 may include connectivity module 545. Connectivity model 545 may support various connectivity options, including cellular networks (e.g., 4G/LTE, 5G), Wi-Fi, Bluetooth, and NFC (Near Field Communication), allowing UE 500 to connect to other devices and telecommunications networks.

[00099] UE 500 may include security components 550. Security components 550 may be responsible for ensuring the security and privacy of user data and communications. Security components 550 may include encryption/decryption hardware and software, as well as security features to protect against malware and unauthorized access.

[000100] UE 500 may include a memory 555 (e.g., RAM) for running applications. UE 500 may include a storage 560 (e.g., internal storage or removable SD cards) and storage (e.g., internal storage or removable SD cards) for storing data and applications. For example, according to some embodiments of the invention, storage 560 may include network data, such as a lookup table as described herein.

[000101] UE 500 may include a charging port 565 for recharging battery 520.

[000102] In some embodiments, some of the components shown in Fig. 5 may be omitted. In some embodiments, UE 500 may include additional components in accordance with standards specifications (e.g., 3GPP specifications) that are not shown in Fig. 5.

[000103] Reference is now made to Fig. 6, which is a block diagram of an exemplary base station (BS) 600 which may be used with embodiments of the present invention. Base station 600 may be, for example, an eNB or gNB.

[000104] BS 600 may include a radio transceiver 605. Radio transceiver 605 may transmit and receive radio signals.

[000105] BS 600 may include an antenna system 610. Antenna system 610 may include one or more antennas that may transmit and receive signals via the air in specific directions and patterns. For example, antenna system 610 may include advanced antenna technologies such as Multiple- Input Multiple-Output (MIMO) and beamforming that may improve network performance and coverage.

[000106] BS 600 may include baseband processing unit 615. Baseband processing unit 615 may handle the baseband processing of communication signals. Baseband processing unit 615 may perform tasks such as modulation/demodulation, encoding/decoding, error correction, and channel allocation.

[000107] BS 600 may include a digital signal processing unit 620. Digital signal processing unit 620 may process and manipulate digital signals within baseband processing unit 615. Digital signal processing unit 620 may perform tasks such as signal processing, beamforming, interference cancellation, and MIMO processing.

[000108] BS 600 may include a backhaul connection 625. Backhaul connection 625 may provide a high-capacity backhaul connection to connect BS 600 to the core network. Backhaul connection 625 may include wired connections such as optical fibre or microwave links.

[000109] BS 600 may include a power supply unit 630. Power supply unit 630 may provide electrical power to BS’s 600 components to ensure continuous operation.

[000110] BS 600 may include a control and management unit 635. Control and management unit 635 may be responsible for controlling and managing the operation of BS 600. Control and management unit 635 may handle tasks such as network configuration, software updates, and fault management.

[000111] BS 600 may include a cooling system 640. Cooling system 640 may include fans, heat sinks, and/or liquid cooling systems that may maintain the equipment of BS 600 within its operating temperature range.

[000112] BS 600 may include a timing and synchronization unit 645. Timing and synchronization unit 645 may perform timing and synchronization for maintaining the integrity of the communication network, e.g., to ensure that all base stations in the network are synchronized with a common timing reference.

[000113] BS 600 may include a security and encryption unit 650. Security and encryption unit 650 may perform tasks such as encryption of user data and authentication of UEs for protecting the network from unauthorized access and malicious attacks.

[000114] BS 600 may include a fault detection and alarming unit 655. Fault detection and alarming unit 655 may monitoring equipment health and raising alarms in case of hardware or software issues are critical for maintaining network reliability and availability.

[000115] In some embodiments, some of the components shown in Fig. 6 may be omitted. In some embodiments, BS 600 may include additional components in accordance with standards specifications (e.g., 3GPP specifications) that are not shown in Fig. 6. [000116] The principles of the invention disclosed herein may also be embodied as a system, for example a system which includes a core network element, base station and user equipment configured to carry out methods disclosed herein. For example, a user equipment according to embodiments of the invention may be configured to carry out one or more steps of method 200. The user equipment may have stored thereon, may be configured to have stored thereon, or may otherwise be configured to access, network data which indicates supported modes of principal and fallback operation. The network data may be, or may include, a lookup table as described herein. The network data, for example in the form of a lookup table, may be stored on a chip, chipset, or other computer readable module or memory which may be installed in the UE. The network data stored on any such chip, chipset, module or memory may be remotely editable, for example by a device management service (such as OneEdge) which may remotely add, delete, change, update or otherwise edit the network data.

[000117] It is anticipated that embodiments of the invention may have an impact on existing or future non-terrestrial network telecommunications architecture and associated standards. For example, embodiments of the invention may be employed in, beyond 5G, 6G, and/or future NTN architectures. The ongoing development of these standards, and the conceptualization and implementation of future standards, may rely on systems and/or methods of the present invention. [000118] For example, embodiments of the invention may extend the capabilities of the 3 GPP, 5G, and/or 6G standards in that the density or periodicity of NR measurements and the startup mode of the UE are changed in response to features or modes of operation supported by locally available networks as indicated in network data such as a stored or otherwise accessible lookup table, and where the measurement density /periodicity and startup mode may be further changed if the UE changes location (e.g. based on a change in MNC and/or MCC).

[000119] Unless specifically stated otherwise, as apparent from the foregoing discussion, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," "determining," or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulates and/or transforms data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices. [000120] Embodiments of the invention may include an article such as a computer or processor readable non-transitory storage medium, such as for example a memory, a disk drive, or a USB flash memory encoding, including, or storing instructions, e.g., computer-executable instructions, which when executed by a processor or controller, cause the processor or controller to carry out methods disclosed herein.

[000121] It should be recognized that embodiments of the invention may solve one or more of the objectives and/or challenges described in the background, and that embodiments of the invention need not meet every one of the above objectives and/or challenges to come within the scope of the present invention.

[000122] In the above description, an embodiment is an example or implementation of the inventions. The various appearances of "one embodiment,” "an embodiment" or "some embodiments" do not necessarily all refer to the same embodiments.

[000123] Although various features of the invention may be described in the context of a single embodiment, the features may also be provided separately or in any suitable combination. Conversely, although the invention may be described herein in the context of separate embodiments for clarity, the invention may also be implemented in a single embodiment. While the invention has been described with respect to a limited number of embodiments, it should be understood by a person of ordinary skill in the art that one or more features from one particular embodiment or group of embodiments may be combined with features of another embodiment or group of embodiments.

[000124] Reference in the specification to "some embodiments", "an embodiment", "one embodiment" or "other embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments, of the inventions.

[000125] It is to be understood that the phraseology and terminology employed herein is not to be construed as limiting and are for descriptive purposes only.

[000126] It is to be understood that the details set forth herein do not construe a limitation to an application of the invention.

[000127] It is to be understood that the terms “including”, “comprising”, “consisting” and grammatical variants thereof do not preclude the addition of one or more components, features, steps, or integers or groups thereof and that the terms are to be construed as specifying components, features, steps, or integers.

[000128] If the specification or claims refer to "an additional" element, that does not preclude there being more than one of the additional elements.

[000129] It is to be understood that where the claims or specification refer to "a" or "an" element, such reference is not to be construed that there is only one of that element.

[000130] It is to be understood that where the specification states that a component, feature, structure, or characteristic "may", "might", "may" or "could" be included, that a particular component, feature, structure, or characteristic is not required to be included.

[000131] Where applicable, although state diagrams, flow diagrams or both may be used to describe embodiments, the invention is not limited to those diagrams or to the corresponding descriptions. For example, flow need not move through each illustrated box or state, or in exactly the same order as illustrated and described.

Claims

1. A method for operating a user equipment (UE) supporting reduced capability (REDCAP) operation or enhanced reduced capability (eREDCAP) operation, the method comprising: determining an available network; determining a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network; and operating the UE according to the determined supported mode of principal operation, wherein, if the determined supported mode of principal operation is not available, then the method comprises operating the UE according to the determined supported fallback mode of operation.

2. The method of claim 1 , wherein determining the supported mode of principal operation and the supported fallback mode of operation comprises using network data stored by the UE.

3. The method of claim 2, wherein the network data is comprised in a lookup table which associates with the network, at least one of:

• a 3 GPP release number of the network;

• a 5G standalone (SA) network support indication;

• a 5G non-standalone (NSA) network support indication;

• the supported principal mode of operation;

• the supported fallback mode of operation;

• a supported feature indication;

• a measurement periodicity; or

• a startup mode, wherein the network is identified by at least one of a mobile country code “MCC”, or a mobile network code “MNC”.

4. The method of claim 3, wherein the supported fallback mode of operation is one of:

• Long Term Evolution (LTE);

• Enhanced Mobile Broadband (eMBB); • restricted eMBB;

• Universal Mobile Telecommunications System (UMTS); or

• Global System for Mobile Communications (GSM).

5. The method of any of claims 3-4, wherein the lookup table comprises network data for one or more different networks deployed by one or more different network operators.

6. The method of claim any of claims 3-5, wherein the lookup table is maintained by a device management service.

7. The method of any of claims 3-5, comprising modifying a startup mode of the UE when the UE has previously determined that the network does not support the principal mode of operation.

8. The method according to claim 7, wherein a new startup mode to be active at a next startup is set to the determined supported fallback mode of operation.

9. The method according claim 8, comprising evaluating whether a new network is available based on a change in the MNC or MCC since a last startup, and modifying the startup mode of the UE to be the principal mode of operation if the principal mode of operation is supported and available on the new network.

10. The method of any of claims 3-9, comprising reducing a measurement periodicity based on the UE determining that the network does not support the principal mode of operation.

11. The method of claim 10, comprising disabling the measurement periodicity until at least one of the MNC or MCC changes.

12. A computer readable module containing instructions which, when executed by at least one processor in a user equipment “UE” supporting reduced capability (REDCAP) operation or enhanced reduced capability (eREDCAP) operation, cause the UE to: determine an available network; determine a supported principal mode of operation and a supported fallback mode of operation of the UE based on the determined network; and operate according to the determined supported mode of principal operation, wherein, if the determined supported mode of principal operation is not available, then operate according to the determined supported fallback mode of operation.

13. The computer readable module of claim 12 containing network data suitable for determining the supported mode of principal operation and the supported fallback mode of operation of the network.

14. The computer readable module of claim 12, wherein the network data is comprised in a lookup table which associates with the network, at least one of: