TERRESTRIAL NETWORK COVERAGE

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to configuration of a wireless device with a low activity state configuration.

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes (NWs), such as base stations, and mobile wireless devices (WDs)(e.g., user equipment (UE)), as well as communication between network nodes and between wireless devices. Sixth Generation (6G) wireless communication systems are also under development.

Further, 5G system (5GS) is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), narrowband-internet of things (NB-IOT) and massive machine-type communications (mMTC). 5G includes an NR access stratum interface and a 5G Core Network (5GC). The NR physical and higher layers may reuse parts of the LTE specification, and to that components may be added when motivated by new use cases. To benefit from the mobile ecosystem and economy of scale, a satellite network based on the terrestrial wireless access technologies including LTE and NR for satellite networks, is being specified in the 3GPP standard.

Internet of Things (loT) Non-Terrestrial Network (NTN) and NTN Characteristics A satellite radio access network usually includes the following components:

• A satellite that refers to a space-borne platform.

• An earth-based gateway that connects the satellite to a base station (e.g., network node) or a core network, depending on the architecture.

• Feeder link that refers to the link between a gateway and a satellite

• Access link, or service link, that refers to the link between a satellite and a wireless device.

Depending on the orbit altitude, a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite.

• LEO: typical heights ranging from 250 - 1,500 km, with orbital periods ranging from 90 - 120 minutes.

• MEO: typical heights ranging from 5,000 - 25,000 km, with orbital periods ranging from 3 - 15 hours.

• GEO: height at about 35,786 km, with an orbital period of 24 hours.

Two basic architectures can be distinguished for satellite communication networks, depending on the functionality of the satellites in the system:

• Transparent payload (also referred to as bent pipe architecture). The satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency. When applied to general 3GPP architecture and terminology, the transparent payload architecture means that the network node is located on the ground and the satellite forwards signals/data between the network node and the wireless device;

• Regenerative payload. The satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth. When applied to general 3 GPP architecture and terminology, the regenerative payload architecture means that the network node is located in the satellite.

In the work item for NR NTN in 3 GPP release 17, only the transparent payload architecture is considered.

A satellite network or satellite based mobile network may also be referred to as non-terrestrial network (NTN), while mobile network with network nodes on the ground may also be referred to as terrestrial network (TN) or non-NTN network. A satellite within NTN may be referred to as NTN node, NTN satellite or a satellite.

FIG. 1 depicts an example architecture of a satellite network with bent pipe transponders. The network node may be integrated in the gateway or connected to the gateway via a terrestrial connection (e.g., wire, optic fiber, wireless link).

A communication satellite typically generates several beams over a given area. The footprint of a beam is usually in an elliptic shape, which has traditionally been considered as a cell, but cells consisting of the coverage footprint of multiple beams are not excluded in the 3GPP work. The footprint of a beam may be referred to as a spotbeam. The footprint of a beam may move over the earth’s surface with the satellite movement or may be earth fixed with a beam pointing mechanism used by the satellite to compensate for the satellite’s motion. The size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers.

In a LEO or MEO communication system, a large number of satellites deployed over a range of orbits may be required to provide continuous coverage across the globe/earth. Launching a mega satellite constellation is both an expensive and timeconsuming procedure. It is therefore expected that all LEO and MEO satellite constellations for some time only provide partial earth-coverage. In cases where some constellations are dedicated to massive loT services with relaxed latency requirements, it may not even be necessary to support full earth-coverage. It may be sufficient to provide occasional or periodic coverage according to the orbital period of the constellation.

A 3 GPP device in connection state such as RRC IDLE or RRC INACTIVE state may be required to perform number of procedures including measurements for mobility purposes, paging monitoring, logging measurement results, tracking area update, and search for a new PLMN, etc.. These procedures will consume power in devices, and a general trend in 3 GPP has been to allow for relaxation of these procedures to prolong device battery life. This trend has been especially pronounced for loT devices supported by reduced capability (redcap (e.g., non-legacy)), NB-IoT and LTE for machines (LTE-M).

Propagation delay may be one aspect of satellite communications that is different from the delay expected in a terrestrial mobile system. For a bent pipe satellite network, the round-trip delay may, depending on the orbit height, range from tens of ms in the case of LEO satellites to several hundreds of ms for GEO satellites. As a comparison, the round-trip delays in terrestrial cellular networks are typically below 1 ms.

The distance between the wireless device and a satellite can vary significantly, depending on the position of the satellite and thus the elevation angle 8 seen by the wireless device. Assuming circular orbits, the minimum distance is realized when the satellite is directly above the wireless device (a = 90°), and the maximum distance when the satellite is at the smallest possible elevation angle. Table 1 shows the distances between satellite and wireless device for different orbital heights and elevation angles together with the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay at 8 = 90°). Note that this table assumes regenerative payload architecture. For the transparent payload case, the propagation delay between gateway and satellite needs to be considered as well, unless the network node corrects for that.

Table 1: Propagation delay for different orbital heights and elevation angles.

The propagation delay may also be highly variable due to the high velocity of the LEO and MEO satellites and change in the order of 10 - 100 ps every second, depending on the orbit altitude and satellite velocity.

Ephemeris data

In 3GPP Technical Reference (TR) 38.821, it has been captured that ephemeris data should be provided to the wireless device, for example to assist with pointing a directional antenna (or an antenna beam) towards the satellite. A wireless device knowing its own position, e.g., due to GNSS support, may also use the ephemeris data to calculate correct timing related and/or frequency drifts, e.g., Timing Advance (TA) and Doppler shift. The contents of the ephemeris data and the procedures on how to provide and update such data have not yet been studied in detail.

A satellite orbit can be described using, e.g., six parameters. Exactly which set of parameters is used can be decided by the user; many different representations are possible. For example, a choice of parameters used often in astronomy is the set (a, a, i, Q, co, t). Here, the semi -major axis a and the eccentricity a describe the shape and size of the orbit ellipse; the inclination i, the right ascension of the ascending node Q, and the argument of periapsis co determine its position in space, and the epoch t determines a reference time (e.g., the time when the satellites moves through periapsis). The set of these parameters is illustrated in FIG. 2. A two-line element (TLE) set is a data format encoding a list of orbital elements of an Earth-orbiting object for a given point in time, the epoch. As an example of a different parametrization, TLEs use mean motion n and mean anomaly M instead of a and t.

A completely different set of parameters is the position and velocity vector (x, y, z, vx, v _y , Vz) of a satellite. These are sometimes called orbital state vectors. They can be derived from the orbital elements and vice versa since the information they contain is equivalent. All these formulations (and many others) are possible choices for the format of ephemeris data to be used in NTN.

Additionally, the ephemeris data may be accompanied with information on possible coverage area, or timing information when the satellite is going to serve a certain geographical area on Earth.

Measurement rules for NTN in RRC idle/inactive state

The parameter, “t-Service” is broadcasted by a cell (e.g., serving cell) in the system information (SI) (e.g., in a SIB). More specifically t-Service is the time information on when a cell served or managed by NTN node (e.g., NTN quasi-Earth fixed cell) is going to stop serving the area it is currently covering. t-Service is time offset with respect to the UTC time. It is therefore expressed in Coordinated Universal Time (UTC), e.g., in seconds.

A wireless device served by NTN node (e.g., satellite node) applies one or more existing measurement rules defined for legacy wireless device (i.e., wireless device served by terrestrial network). The NTN capable wireless device is also required to perform measurements according to additional rules which are specific to operation in NTN, i.e., wireless device served by the NTN node. In one example, wireless device also uses ‘t- Service’ for performing the measurements. According to 3GPP Technical Specification (TS) 36.304 V17.1.0, if a parameter, “t-Service” of the serving cell is present in system information (SI) (e.g., in a SIB) then the wireless device should start to perform intrafrequency, inter-frequency or inter-RAT measurements before the t-Service, regardless of the distance between wireless device and the serving cell reference location or whether the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, or Srxlev > SnonlntraSearchP and Squal > SnonlntraSearchQ and the exact time to start measurement before t-Service is up to wireless device implementation. The wireless device performs measurements of higher priority NR. inter-frequency or inter-RAT frequencies regardless of the remaining service time of the serving cell. loT eMTC

The eMTC features specified in, for example, 3GPP RP-152024 and 3GPP Rl- 157926, include a low-complexity wireless device (e.g., UE) category called UE category Ml (or Cat-Mi for short) and coverage enhancement (CE) techniques (CE modes A and B) that can be used together with UE category Ml or any other LTE UE category.

All eMTC features (both Cat-Mi and E modes A and B) operate using a reduced maximum channel bandwidth compared to normal LTE. The maximum channel bandwidth in eMTC is 1.4 MHz whereas it is up to 20 MHz in normal LTE. The eMTC wireless devices are still able to operate within the larger LTE system bandwidth without problem. One difference compared to normal LTE wireless devices is that the eMTCs can only be scheduled with 6 physical resource blocks (PRBs), a 180 kHz at a time.

In CE modes A and B, the coverage of physical channels is enhanced through various coverage enhancement techniques, the most important being repetition or retransmission. This means that the 1-ms subframe to be transmitted is repeated a number of times, e.g., just a few times if a small coverage enhancement is needed or hundreds or thousands of times if a large coverage enhancement is needed.

NB-IoT

The objective of Narrow Band Internet of Things (NB-IoT) is to specify a radio access for cellular internet of things (loT), based to a certain extent on a non-backwardcompatible variant of E-UTRA, that addresses improved indoor coverage, support for massive number of low throughput devices, low delay sensitivity, ultra-low device cost, low device power consumption and (optimized) network architecture.

The NB-IoT carrier BW (Bw2) is 200 KHz. Examples of operating bandwidth (Bwl) of LTE are 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz etc.

NB-IoT supports 3 different modes of operation:

• ‘ Stand-alone operation’ utilizing for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers. In principle it operates on any carrier frequency which is neither within the carrier of another system nor within the guard band of another system’s operating carrier. The other system can be another NB-IoT operation or any other RAT, e.g., LTE.

• ‘Guard band operation’ utilizing the unused resource blocks within an LTE carrier’s guard-band. The term guard band may also interchangeably be called guard bandwidth. As an example in case of LTE BW of 20 MHz (i.e., Bwl= 20 MHz or 100 RBs), the guard band operation of NB-IOT can place anywhere outside the central 18 MHz but within 20 MHz LTE BW.

• ‘In-band operation’ utilizing resource blocks within a normal LTE carrier. The in-band operation may also interchangeably be called in-bandwidth operation. More generally the operation of one RAT within the BW of another RAT is also called in-band operation. As an example in an LTE BW of 50 RBs (i.e., Bwl of 0 MHz or 50 RBs), NB-IoT operation over one resource block (RB) within the 50 RBs is called in-band operation.

In NB-IoT the downlink (DL) transmission is based on OFDM with 15 kHz subcarrier spacing for all the scenarios: standalone, guard-band, and in-band. For uplink (UL) transmission, both multi-tone transmissions based on SC-FDMA, and single tone transmission is supported. This means that the physical waveforms for NB-IoT in downlink and also partly in uplink is similar to legacy LTE.

In the DL design, NB-IoT supports both master information broadcast and system information broadcast which are carried by different physical channels. For in-band operation, it is possible for NB-IoT wireless device to decode NB packet broadcast control channel (NB-PBCH) without knowing the legacy PRB index. NB-IoT supports both downlink physical control channel (NB physical downlink control channel (NB-PDCCH), or NB Machine-type PDCCH (NB-M-PDCCH)) and downlink physical shared channel (PDSCH). The operation mode of NB-IoT must be indicated to the wireless device, and currently 3 GPP consider indication by means of NB secondary synchronization signal (NB-SSS), NB master information block (NB-MIB) or perhaps other downlink signals.

In existing systems, reference signals used in NB-IoT have not been decided. However it is expected that the general design principle will follow that of legacy LTE. Downlink synchronization signals will most likely consist of NB primary synchronization signal (NB-PSS) and NB-SSS.

Discontinuous reception (DRX) cycle operation

The wireless device can be configured with a DRX cycle to use in all radio resource control (RRC) states (e.g., RRC idle state, RRC inactive state and RRC connected state) to save wireless device battery power. Examples of lengths of DRX cycles currently used in RRC idle/inactive state are 320 ms, 640 ms, 1.28 s, 2.56 s, etc. Examples of lengths of DRX cycles currently used in RRC connected state may range from 2 ms to 10.24 s. The DRX cycle is configured by the network node and is characterized by the following parameters:

• On duration: During the on duration of the DRX cycle, a timer called ‘onDurationTimer’, which is configured by the network node, is running. This timer specifies the number of consecutive control channel subframes (e.g., NPDCCH slots) at the beginning of a DRX Cycle. It is also interchangeably called as DRX ON period. It is the duration (e.g., in number of downlink subframes) during which the wireless device after waking up from DRX may receive control channel (e.g., NPDCCH, wake up signal, etc). If the wireless device successfully decodes the control channel (e.g., NPDCCH) during the on duration then the wireless device starts a drx-inactivity timer (as described below) and stays awake until its expiry.

• drx-inactivity timer: It specifies the number of consecutive control channel (e.g., NPDCCH,) subframe(s) after the subframe in which a control channel (e.g., NPDCCH) indicates an initial UL or DL user data transmission for this MAC entity. It is also configured by the network node.

• DRX active time: This time is the duration during which the wireless device monitors the control channel (e.g., NPDCCH, wake up signals etc). In other words, this is the total duration during which the wireless device is awake. This includes the “on-duration” of the DRX cycle, the time during which the wireless device is performing continuous reception while the inactivity timer has not expired and the time the wireless device is performing continuous reception while waiting for a DL retransmission after one HARQ RTT. This means duration over which the drx-inactivity timer is running is called as DRX active time, i.e., no DRX is used by the wireless device.

• DRX inactive time: The time during the DRX cycle other than the active time is called as DRX inactive time, i.e., DRX is used by the wireless device.

The DRX active time and DRX inactive time, also called DRX ON and DRX OFF durations of the DRX cycle respectively, are shown in FIG. 3, which depicts DRX cycle illustrating on and off durations. The DRX inactive time may also be called as non-DRX or non-DRX period. The DRX operation with more detailed parameters is illustrated in FIG. 4, which depicts DRX cycle operation illustrating different DRX related parameters. FIG. 5 depicts DRX cycle variation in on and off durations due to wireless device receiver activity. It shows that the DRX active and inactive times may vary depending on wireless device receiver activity, e.g., DRX inactivity timer is running upon wireless device being scheduled. This in turn increases DRX active time and proportionally shortens the DRX inactive time. eDRX cycle operation

In NR, the enhanced DRX (eDRX) cycle is being specified for wireless devices in RRC IDLE and RRC INACTIVE. The purpose of eDRX cycle is to further enable wireless device power saving even more than achieved by the wireless device when configured only with DRX cycle. The eDRX ranges between a few seconds to several minutes or even hours. In one example eDRX cycle may range from 5.12 seconds (shortest eDRX) up to 10485.76 s (largest eDRX). eDRX cycle may also be multiple of 1.28 second which is typical DRX cycle used in idle and inactive states. eDRX configuration parameters are negotiated between wireless device and the network via higher layer signaling, e.g., via non-access stratum (NAS) messages. During the negotiation the network transmits eDRX parameters, which may include eDRX cycle length; paging time window (PTW), hyper system frame number (H-SFN), paging H-SFN (PH), etc.

FIG. 6 depicts an example of the H-SFN cycle. H-SFN includes multiple SFN cycles as shown in FIG. 6. A SFN cycle is a counter which initializes after a certain number of frames. In one example SFN cycle comprises 1024 frames, i.e., varies from 0 to 1023. H-SFN is a frame structure on top of the legacy SFN structure, where each H-SFN value corresponds to a cycle of legacy frames (e.g., 1024 frames) and one H-SFN cycle contains XI number of SFN cycles, e.g., Xl=1024. The network (e.g., core network (NW) nodes such as mobile management entities (MMEs), radio network nodes such as base stations (BSs), gNodeBs, etc.) have the same H-SFN, and cells broadcast their H-SFN via system information, e.g., SIB. The eDRX acquisition period is the time during which the eDRX is configured or is applicable or valid. The boundaries (e.g., starting and ending time) of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod Xl=0, e.g., Xl=256.

The term frame may also be called a radio frame (as used below). The transmission of signals takes place in a frame (or radio frame). The frame includes a certain time period or duration, e.g., 10 ms. The frame further includes certain number of smaller time resources, e.g., 10 subframes each of 1 ms, certain number of slots depending on the numerology of the signal (e.g., 10 slots for Subcarrier Spacing (SCS) =15 kHz, 20 slots for SCS=30 kHz and so on), certain number of symbol per slot, etc.

The wireless device is configured with PTW by the network (e.g., by MME) via NAS during, e.g., attach/tracking area update. The beginning of PTW is calculated by a pre-defined formula (as described below). Within a PTW, the wireless device is further configured with one or more legacy DRX cycles as shown in FIG. 7, which depicts a relationship between H-SFN, PTW, and eDRX periodicity. The PTW length may be expressed in terms of any one or more of: number of DRX cycles, multiples of certain time period (e.g., multiple of 1.28 second periods) or in absolute time (e.g., Y1 seconds), etc.

In one example PTW is characterized by or determined by the wireless device using the following mechanism:

• Paging H-SFN (PH) (calculated by a formula): o H-SFN mod TeDRX= (UE ID mod TeDRX) o UE ID: IMSI mod X2, e.g., X2=1024 o TeDRX : eDRX cycle of the wireless device, (TeDRX =1, 2, . . ., X3 in hyper-frames) and configured by upper layers, e.g., X3=256.

• PTW start is calculated within PH as follows: o The start of PTW is uniformly distributed across X4 (e.g., X4=4) paging starting points within the PH. o PTW start denotes the first radio frame of the PH that is part the paging window and has SFN satisfying the following equation: o SFN = X3 * ieDRX, where ieDRX = floor(UE_ID/TeDRX,H) mod X4 o PTW end is the last radio frame of the PTW and has SFN satisfying the following equation: o SFN = (PW start + L*X5 - X6) mod X2, e.g., X5=100, X6=l, where:

■ L = Paging Window length (in seconds) configured by upper layers, e.g., via RRC.

• PTW length (configured by higher layers). eDRX related procedures and requirements were specified for NB-IoT and eMTC in LTE. In 3 GPP release 17 (Rel-17), similar eDRX related procedures are being specified for NB-IoT and eMTC over NTN. In NTN the coverage of the cells served by satellites may be dynamic depending on the type of satellite serving the cell. This means that the coverage of the cell may disappear for some time or be degraded for some time as the satellites move. Hence, existing systems are not without issues.

SUMMARY Some embodiments advantageously provide methods, systems, and apparatuses for configuration of a wireless device with a low activity state configuration.

According to an aspect, a wireless device (WD) configured to communicate with a network node in a communication system is described. The communication system includes a non-terrestrial network (NTN). The NTN includes a serving cell associated with the network node. The serving cell is for serving the WD in a coverage area. The WD is configured to obtain first information about one or more configurations corresponding to an operation of the WD in a low activity state and receive second information relating to the serving cell of the NTN. The second information indicates at least one of coverage and availability of the serving cell. Further, the second information is broadcasted by the network node. The one or more configurations are adapted based on the received second information.

In some embodiments, the second information includes a time available (ATI) for the serving cell to serve the coverage area that the serving cell is currently serving.

In some other embodiments, ATI is based on at least T-service and Tr. T-service is time information about when the serving cell is going to stop serving the coverage area, and Tr is a reference time.

In some embodiments, the WD is further configured to determine a coverage state of the serving cell based at least in part on ATI.

In some other embodiments, the one or more configurations include one or both of a discontinuous reception (DRX) cycle and an enhanced DRX (eDRX) cycle.

In some embodiments, the one or more configurations further include one or more parameters associated with at least one of the DRX cycle and the eDRX cycle. The one or more parameters include one or more of a DRX cycle length, an eDRX cycle length, a discontinuous reception inactivity timer, an ON duration, a paging time window (PTW) length, a PTW location, a hyper system frame number (H-SFN), and one or more DRX cycles within the eDRX.

In some other embodiments, the WD is configured to adapt the one or more configurations by being configured to adjust one or both of the DRX cycle length and the eDRX cycle length.

In some embodiments, the WD is configured to adapt the one or more configurations by being configured to adjust the discontinuous reception inactivity time to allow the WD to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN, and/or being configured to adjust the ON duration to allow the WD to receive control channel signaling while being served by the serving cell of the NTN, and/or being configured to adjust the PTW length to complete measurements while being served by the serving cell of the NTN, and/or being configured to increase the H-SFN to accommodate an adjusted number of DRX cycles.

In some other embodiments, the WD is configured to adapt the one or more configurations by being configured to disable one or both of DRX and eDRX.

In some embodiments, the WD is further configured to perform one or more tasks based on the adapted one or more configurations. The one or more tasks include one or more of perform one or more measurements on one or more cells, monitor paging, acquire system information of the serving cell, and transmit a message to the network node informing the network node about the adaptation of the one or more configurations.

According to another aspect, a method in a wireless device (WD) for communicating with a network node in a communication system is described. The communication system includes a non-terrestrial network (NTN). The NTN includes a serving cell associated with the network node. The serving cell is for serving the WD in a coverage area. The method includes obtaining first information about one or more configurations corresponding to an operation of the WD in a low activity state and receiving second information relating to the serving cell of the NTN. The second information indicates at least one of coverage and availability of the serving cell and is broadcasted by the network node. The one or more configurations are adapted based on the received second information.

In some embodiments, the second information includes a time available (ATI) for the serving cell to serve the coverage area that the serving cell is currently serving.

In some other embodiments, ATI is based on at least T-service and Tr. T-service is time information about when the serving cell is going to stop serving the coverage area, and Tr is a reference time.

In some embodiments, the method further includes determining a coverage state of the serving cell based at least in part on ATI.

In some other embodiments, the one or more configurations include one or both of a discontinuous reception (DRX) cycle and an enhanced DRX (eDRX) cycle.

In some embodiments, the one or more configurations further include one or more parameters associated with at least one of the DRX cycle and the eDRX cycle, the one or more parameters including one or more of a DRX cycle length, an eDRX cycle length, a discontinuous reception inactivity timer, an ON duration, a paging time window, (PTW) length, a PTW location, a hyper system frame number (H-SFN) and one or more DRX cycles within the eDRX.

In some other embodiments, adapting the one or more configurations includes adjusting one or both of the DRX cycle length and the eDRX cycle length.

In some embodiments, adapting the one or more configurations includes one or more of adjusting the discontinuous reception inactivity time to allow the WD to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN, adjusting the ON duration to allow the WD to receive control channel signaling while being served by the serving cell of the NTN, adjusting the PTW length to complete measurements while being served by the serving cell of the NTN, and increasing the H-SFN to accommodate an adjusted number of DRX cycles.

In some other embodiments, adapting the one or more configurations includes disabling one or both of DRX and eDRX.

In some embodiments, the method further includes performing one or more tasks based on the adapted one or more configurations. The one or more tasks include one or more of performing one or more measurements on one or more cells, monitoring paging, acquiring system information of the serving cell, and transmitting a message to the network node informing the network node about the adaptation of the one or more configurations.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. l is a schematic diagram of a satellite network with bent pipe transponders (i.e., the transparent payload architecture);

FIG. 2 is a schematic diagram of orbital elements;

FIG. 3 is a diagram of a DRX cycle;

FIG. 4: is a diagram of DRX cycle operation;

FIG. 5: is a diagram of DRX cycle variations;

FIG. 6 is a diagram of the H-SFN cycle; FIG. 7 is a diagram of a relationship between H-SFN, PTW, and eDRX periodicity;

FIG. 8 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 9 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 11 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 12 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 13 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 14 is a flowchart of an example process in a network node for configuration of a wireless device with a low activity state configuration according to some embodiments of the present disclosure;

FIG. 15 is a flowchart of an example process in a wireless device for implementation of the configured low activity state configuration according to some embodiments of the present disclosure;

FIG. 16 is a flowchart of another example process in a wireless device according to some embodiments of the present disclosure;

FIG. 17 is diagram of a Np number of DRX cycles within PTW of the configured eDRX cycle according to some embodiments of the present disclosure; FIG. 18 is a diagram of another example process of a wireless device according to some embodiments of the present disclosure; and

FIG. 19 is a diagram of availability of serving cell served by NTN node during ATI according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to configuration of a wireless device with a low activity state configuration. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The terms “node” or “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

As used herein, “satellite” can be understood to include “network node 16 associated with the satellite.” The term “satellite” may also be called as a satellite node, an NTN node, node in the space etc. Here, network node 16 associated with a satellite might include both a regenerative satellite, where the network node 16 is the satellite payload, i.e., the network node 16 is integrated with the satellite, or a transparent satellite, where the satellite payload is a relay and network node 16 is on the ground (i.e., the satellite relays the communication between the network node 16 on the ground and the wireless device 22).

Time period or duration over which a wireless device 22 can maintain connection, or can camp on, or can maintain communication, and so on to a satellite or a network node 16 by wireless device 22 is referred to as term "coverage time" or "serving time" or “network availability” or “sojourn time” or “dwell time” etc. The term ‘Non-coverage time’, also known as "non-serving time" or “network unavailability”, or “non-sojoum time” or “non-dwell time” refers to a period of time during which a satellite or network node 16 cannot serve or communicate or provide coverage to a wireless device 22. Another way to interpret the availability is that is not about a satellite/network strictly not able to serve the wireless device 22 due to lack of coverage but that wireless device 22 does not need to measure certain “not likely to be serving cell (satellite via which serving cell is broadcasted)”. In this case, the terminology may still be as in no coverage case or it may be different, e.g., “no need to measure.”

The term radio access technology, or RAT, may refer to any RAT, e.g., UTRA, E-UTRA, narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, New Radio (NR), 4G, 5G, NR NTN, loT NTN, LTE NTN, etc. Any of the equipment denoted by the term node, network node 16 or radio network node 16 may be capable of supporting a single or multiple RATs.

The terms “signal” or “radio signal” used herein can be any physical signal or physical channel. Examples of DL physical signals are reference signal (RS) such as PSS, SSS, channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), signals in SS/packet broadcast control channel (PBCH) block (SSB), discovery reference signal (DRS), cell-specific RS (CRS), positioning RS (PRS), etc. An RS may be periodic e.g., RS occasion carrying one or more RSs may occur with certain periodicity e.g., 20 ms, 40 ms etc. The RS may also be aperiodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols. One or multiple SSBs are transmitted in one SSB burst which is repeated with certain periodicity e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The wireless device is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration includes parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with respect to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. Examples of UL physical signals are reference signals such as SRS, DMRS etc. The term physical channel refers to any channel carrying higher layer information e.g., data, control etc. Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, short physical uplink control channel (sPUCCH), short PDSCH (sPDSCH), short physical uplink shared channel (sPUSCH), machine-type communication PDCCH (MPDCCH), NB PDCCH (NPDCCH), NB PDSCH (NPDSCH), enhanced PDCCH (E-PDCCH), PUSCH, PUCCH, NPUSCH, etc.

In some embodiments, the term “low activity state” is used and may refer to a state associated with the WD (and/or network node and/or the network). In some embodiments, the state may be state of WD corresponding to a reception mode (e.g., such as DRX and/or eDRX. For example, the WD may be configured with a DRX cycle and/or eDRX cycle, which allows the WD to operate in a mode causes the WD to be less active than in other modes (e.g., transmit/receive fewer signals, enter a sleep mode such as a temporary sleep mode, etc.). In some embodiments, the low activity state includes an active period (e.g., receiving/transmitting signals) and/or an inactive period (e.g., not transmitting signals). DRX and/or eDRX cycles allows the WD to save battery power. In some embodiments, the low activity state is defined in a configuration, predetermined, preconfigured in the WD, received from the network node, etc.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide configuration of a wireless device with a low activity state configuration.

Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 8 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 8 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a configuration unit 32 which is configured to perform one or more network node 16 functions described herein, including, for example, functions related to configuration of a wireless device with a low activity state configuration. A wireless device 22 is configured to include an implementation unit 34 which is configured to perform one or more wireless device 22 functions as described herein, including, for example, one or more functions relating to implementation of the configured low activity state configuration.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 9. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a control unit 54 configured to enable the service provider to observe, monitor, control, and/or transmit to/receive from the network node 16 and or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include configuration unit 32 configured to perform one or more network node 16 functions described herein, including functions related to configuration of a wireless device with a low activity state configuration.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include an implementation unit 34 configured to perform one or more wireless device 22 functions as described herein, including, for example, one or more functions relating to implementation of the configured low activity state configuration.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 9 and independently, the surrounding network topology may be that of FIG. 8.

In FIG. 9, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 8 and 9 show various “units” such as configuration unit 32, and implementation unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 10 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 8 and 9, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 9. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 11 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8 and 9. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 12 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8 and 9. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 13 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 8, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 8 and 9. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

In some embodiments, the loT NTN wireless device 22 can be provided with assistance information related to serving cell coverage of the network node 16. For example, this information may indicate when the serving cell stops covering/serving the current coverage area 18. The assistance information is provided using timing and/or location information signaled by the network node 16. One principle of eDRX allows the wireless device to be inactive (“sleep”) for long duration and to operate signals during the PTW which occurs once every eDRX cycle. In conventional systems, the interaction or the measurement behavior (including paging reception) in eDRX during the time the coverage of the cell is impacted due to satellite moving is undefined or unknown. If the eDRX related procedures and requirements are not clearly defined and specified, then the mobility may fail, and the wireless device 22 may also miss the paging messages.

The present disclosure solves one or more problems with conventional systems by providing, in one or more scenarios, the wireless device 22 that is configured with at least a first cell (Celli) served by a first network node 16 (e.g., NW1) and with a low activity state configuration which includes extended DRX cycle (eDRX) and a DRX cycle, e.g., via higher layer signaling. Where DRX cycle < eDRX cycle (e.g., DRX = 0.32 s and eDRX = 5.12 s, etc.).

The present disclosure includes methods in both wireless device 22 and network node 16 (e.g., BS, core network node, etc.).

A first embodiment includes a method in a wireless device 22 of obtaining low activity state configuration, obtaining serving cell coverage information from the network node 16, determining whether to adapt one or more procedures associated with low activity state configuration (e.g., eDRX configuration) based on the determined information. In one example, the serving cell coverage information includes time available (ATI) for the serving cell to serve the area or region, which it is currently serving. If the time available (ATI) is equal to or larger than certain threshold (Hl) then the wireless device 22 continues operating according to the current low activity state configuration. But if (AT1<H1) then the wireless device 22 applies one or more adapted procedures for performing one or more radio operations (e.g., performing measurements, receiving paging, etc.). Examples of the adapted procedures are:

• In one example, the wireless device 22 adapts or adjusts the eDRX cycle based on the information related to the coverage of the serving cell served by an NTN node, e.g., a satellite.

• In a second example, the wireless device 22 adapts or adjusts the duration of the PTW (TPTW ) based on the coverage state of the serving cell served by an NTN node, e.g., satellite.

• In a third example, the wireless device 22 adapts or adjusts both eDRX cycle and duration of PTW based on the coverage state of the serving cell served by an NTN satellite.

• In a fourth example, the wireless device 22 decides whether to abandon or discard the eDRX cycle or continue applying the currently configured eDRX cycle.

• In a fifth example, the wireless device 22 decides whether to abandon or discard the DRX cycle or continue applying the currently configured DRX cycle.

In one example, the adaptation herein includes the wireless device 22 applying or using an eDRX cycle (eDRX cycle’) shorter than what was initially configured (eDRX cycle). This means eDRX_cycle’< eDRX cycle. Similarly, the adaptation also includes the wireless device 22 applies or uses a longer PTW (TPTW’) than what was initially configured (TPTW’). Alternatively, the wireless device 22 may extend the current PTW by a certain duration to allow the wireless device to complete the ongoing measurement before the coverage of the current cell is impacted. In another example, the adaptation includes not using the eDRX cycle anymore, e.g., discarding or disabling the eDRX. In another example, the adaptation includes not using the DRX cycle anymore, e.g., discarding or disabling the DRX, i.e., operating in non-DRX. The wireless device 22 may further perform one or more operational tasks using the adapted low activity state configuration, e.g., measurements on cells using the adapted DRX and/or adapted eDRX cycle, monitoring paging using the adapted ON duration of DRX and/or adapted PTW of the eDRX cycle, transmitting information about the adapted low activity state configuration to a network node, etc.

FIG. 14 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to transmit to the wireless device 22 at least one of information relating to at least one configuration corresponding to operation of the wireless device 22 in a low activity state and information relating to a serving cell where the information includes at least one of coverage and availability (Block SI 34). The network node 16 is also configured to communicate with the wireless device 22 based on an adapted low activity state configuration of the wireless device 22 (Block SI 36).

In at least one embodiment, the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE. In at least one embodiment, the configuration includes an enhanced DRX (eDRX) cycle.

FIG. 15 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the implementation unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 is configured to receive information relating to at least one of: at least one configuration corresponding to operation of the wireless device in a low activity state and a serving cell, the information indicating at least one of coverage and availability (Block S138). The wireless device 22 is also configured to adapt at least one low activity state configuration based on the received information (Block S140).

In at least one embodiment, the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE. In at least one embodiment, the configuration includes an enhanced DRX (eDRX) cycle.

FIG. 16 is a flowchart of another example process in a WD 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of WD 22 such as by one or more of processing circuitry 84 (including the implementation unit 34), processor 86, radio interface 82 and/or communication interface 60. WD 22 is configured to communicate with a network node 16 in a communication system 10. The communication system 10 includes a nonterrestrial network (NTN). The NTN includes a serving cell associated with the network node 16. The serving cell is for serving the WD 12 in a coverage area 18. The WD 22 is configured to obtain (Block S142) first information about one or more configurations corresponding to an operation of the WD 22 in a low activity state and receive (Block S144) second information relating to the serving cell of the NTN. The second information indicates at least one of coverage and availability of the serving cell and is broadcasted (e.g., in the serving cell and/or any other cell) by the network node 16. Further, WD 22 is configured to adapt (Block S146) the one or more configurations based on the received second information.

In some embodiments, the second information includes a time available (ATI) for the serving cell to serve the coverage area that the serving cell is currently serving.

In some other embodiments, ATI is based on at least T-service and Tr. T-service is time information about when the serving cell is going to stop serving the coverage area 18, and Tr is a reference time.

In some embodiments, the method further includes determining a coverage state of the serving cell based at least in part on ATI. In such embodiments, the WD 22 is further configured to determine a coverage state of the serving cell based at least in part on ATI.

In some other embodiments, the one or more configurations include one or both of a discontinuous reception (DRX) cycle and an enhanced DRX (eDRX) cycle.

In some embodiments, the one or more configurations further include one or more parameters associated with at least one of the DRX cycle and the eDRX cycle, the one or more parameters including one or more of a DRX cycle length, an eDRX cycle length, a discontinuous reception inactivity timer, an ON duration, a paging time window, (PTW) length, a PTW location, a hyper system frame number (H-SFN) and one or more DRX cycles within the eDRX.

In some other embodiments, adapting the one or more configurations includes adjusting one or both of the DRX cycle length and the eDRX cycle length. In such embodiments, the WD 22 is further configured to adjust one or both of the DRX cycle length and the eDRX cycle length.

In some embodiments, adapting the one or more configurations includes one or more of adjusting the discontinuous reception inactivity time to allow the WD 22 to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN, adjusting the ON duration to allow the WD 22 to receive control channel signaling while being served by the serving cell of the NTN, adjusting the PTW length to complete measurements while being served by the serving cell of the NTN, and increasing the H-SFN to accommodate an adjusted number of DRX cycles. In such embodiments, the WD 22 is further configured to adjust the discontinuous reception inactivity time to allow the WD 22 to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN, and/or adjust the ON duration to allow the WD 22 to receive control channel signaling while being served by the serving cell of the NTN, and/or adjust the PTW length to complete measurements while being served by the serving cell of the NTN, and/or increase the H-SFN to accommodate an adjusted number of DRX cycles.

In some other embodiments, adapting the one or more configurations includes disabling one or both of DRX and eDRX. In such embodiments, the WD 22 is further configured to disable one or both of DRX and eDRX.

In some embodiments, the method further includes performing one or more tasks based on the adapted one or more configurations. The one or more tasks include one or more of performing one or more measurements on one or more cells, monitoring paging, acquiring system information of the serving cell, and transmitting a message to the network node informing the network node about the adaptation of the one or more configurations. In such embodiments, the WD 22 is further configured to perform one or more of said one or more tasks.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for configuration of a wireless device with a low activity state configuration.

Some embodiments provide for configuration of a wireless device 22 with a low activity state configuration. One or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, implementation unit 34, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, configuration unit 32, etc.

One or more embodiments described herein may provide one or more of the following benefits: Interaction between eDRX related procedures and dynamic change of satellite coverage is defined;

The wireless device 22 measures on candidate cells for possible cell change before losing the coverage of the serving cell; and

The time to select new serving cell when the wireless device is about to lose the coverage of the current serving cell is reduced.

Example Embodiments

Scenario description

Various embodiments are applicable in scenario including a wireless device that is capable of operating in a NTN network, served by an NTN cell, which in turn is served or managed by NTN node. Examples of NTN nodes are satellite node, high altitude platform BS (HAPS), any network node 16 in air (e.g., drone BS, etc.). The wireless device 22 is configured to operate a signal between a wireless device 22 and a first cell (Celli), or between a wireless device 22 and another wireless device 22 on a carrier Fl which may be a licensed carrier or unlicensed carrier (e.g., carrier subject to clear channel assessment (CCA)). Celli may be a serving cell or a non-serving cell. The wireless device 22 may be operating in any of the RRC states such as idle state, inactive state, CONNECTED state, etc. In some embodiments the wireless device 22 may be operating in or configured in low activity RRC state. Examples of low activity states are RRC IDLE state, RRC INACTIVE state, etc. In some embodiments the wireless device 22 may be operating in or configured in high activity RRC state. An example of high activity RRC state is CONNECTED state, etc.

The wireless device 22 may further be configured with an eDRX cycle (e.g., 5.12 seconds or longer) via higher layers e.g., via core network such as via NAS signaling. In one example for a wireless device 22 operating in RRC INACTIVE state, the eDRX cycle is configured via RRC signaling by NW1 when the wireless device 22 is in RRC CONNECTED state. In another example for a wireless device 22 operating in RRC IDLE state, the eDRX cycle is configured via NAS signaling. The wireless device 22 may further be configured with at least one DRX cycle (e.g., 0.32 seconds) via higher layers e.g., via RRC signaling.

The PTW occurs once every eDRX cycle as shown in FIG. 17. Within each paging window the wireless device 22 is configured with certain number of DRX cycles as also shown in FIG. 17. The term PTW may also be referred to as paging window, paging transmission window, etc. The PTW length or duration (TPTW) can be expressed in terms of suitable time units e.g., Z1 seconds, number of DRX cycles (Nl), number (N2) of minimum PTW period (Tmin), in time resources (e.g., slots, frames, SFN cycles) etc. Examples of Tmin are 0.64 second, 1.28 second etc. The term PTW is used hereinafter for consistency.

Example Embodiment: Methods in the wireless device 22 for adapting eDRX configurations based on coverage information of an NTN cell

Embodiments described herein may also be implemented in any combination and in any order. A wireless device 22 embodiment may comprise at least the following:

• Step 1 : The wireless device 22 obtains information about one or more configurations allowing the wireless device 22 to operate in low activity states;

• Step 2: The wireless device 22 obtains information about the serving cell (e.g., Celli) coverage or availability related information (e.g., where the information is broadcasted by network node 16 in the serving cell and/or any other cell);

• Step 3 : The wireless device 22 adapts the one or more low activity state configuration based on whether determined coverage state of Celli and uses for one or more operational tasks. An example of this embodiment is illustrated by a flow chart in FIG. 18, which depicts an example embodiment of a wireless device 22 adapting low activity state configurations for operating signals and receiving paging based on the coverage state information of the cell. A UE/wireless device 22 obtains a low activity state configuration (Block S200). UE/wireless device 22 determines whether it will soon enter a coverage state S2 for the serving cell (Block S202). If yes, UE/wireless device 22 applies adapted low activity state configurations (Block S204). The UE/wireless device 22 then follows the adapted configurations for operating signals and receiving paging (Block S206). If the UE/wireless device 22 will not soon enter the coverage state S2, it follows the default low activity state configurations (Block S208). UE/wireless device 22 follows the default configurations for operating signals and receiving paging (Block S210).

Step 1: wireless device 22 obtaining information about one or more configuration allowing the wireless device 22 to operate in low activity states.

In this step, the wireless device 22 obtains information about one or more wireless device 22 activity related configurations enabling the wireless device 22 to operate in low activity states. Examples of such wireless device 22 activity related configurations are related to DRX cycle and/or eDRX cycle, which include one or more parameters as described herein. Examples DRX cycle and eDRX cycle related parameters are DRX cycle length (TDRX) and eDRX cycle length (T _C DRX) as also described herein. For example the DRX cycle related configuration contains different parameters required for the DRX operation such as DRX cycle length, DRX active time, drx-inactivity timer, ON duration etc. For example, the DRX cycle related configuration contains different parameters required for eDRX operation such as PTW length, PTW start, H-SFN, DRX cycle, etc.

The wireless device 22 activity related configuration can be obtained by the wireless device 22 from first network node 16 (NW1) and/or from a second network node 16 (NW2). In one example, NW 1 is included in or belongs to a radio access network (RAN), and NW2 is included in or belongs to a core network (CN). In this case NW1 and NW2 are RAN node and CN node respectively. Examples of RAN node are base station, gNB, eNB, access point, etc. Examples of CN node are AMF, MME etc. In another example both NW 1 and NW2 may be included in the same or different radio access networks. In another example both NW 1 and NW2 may be included in the same or different core network node 16s.

In one example embodiment, the wireless device 22 is configured with a first DRX cycle (DRX1) and/or with a first eDRX cycle (eDRXl) by NW1, and is configured with a second DRX cycle (DRX2) and/or with a second eDRX cycle (eDRX2) by NW2. In one example DRX1 and DRX2 may be the same, or in another example DRX1 and DRX2 may be different. In one example eDRXl and eDRX2 may be the same, or in another example eDRXl and eDRX2 may be different.

NW1 may configure the wireless device 22 with DRX cycle and/or eDRX cycle via higher layer signaling related to RAN e.g., RRC signaling. NW2 may configure the wireless device 22 with DRX cycle and/or eDRX cycle via higher layer signaling related to CN, e.g., NAS signaling.

In one example embodiment the length of the DRX cycle and length of the eDRX cycle configured by the RAN network node 16 (e.g., NW1) are denoted by TDRX-RAN and TeDRx-RAN respectively. In another example the length of the DRX cycle and length of the eDRX cycle configured by the core network (CN) node (e.g., NW2) are denoted by TDRX- CN and TeDRx-CN respectively. The wireless device 22 in RRC_INACTIVE state uses these wireless device 22 activity related configurations to decide when to receive paging messages.

In one example embodiment it is assumed that the wireless device 22 is configured with only DRX cycles by CN node and RAN node. In this case the wireless device 22 uses that configuration (e.g., parameters related to DRX cycles configured by RAN or CN node such as TDRX-RAN, TDRX-CN) for performing different types of measurement procedures and receive paging messages.

In another example embodiment, it is assumed that the wireless device 22 is configured with only extended DRX (eDRX) cycles by CN and RAN node. In this case the wireless device 22 uses that configuration (e.g., parameters related to eDRX cycles configured by RAN such as T ₆ DRX-RAN, T ₆ DRX-CN) for performing different types of measurement procedures and receiving paging messages.

In another example embodiment, it is assumed that the wireless device 22 is configured with extended DRX (eDRX) cycles and DRX cycles which is used for eDRX within PTW by CN and RAN node. In this case the wireless device 22 uses that configuration (e.g., parameters related to DRX/eDRX cycles configured by RAN such as TDRX-RAN, TDRX-CN T ₆ DRX-RAN, T ₆ DRX-CN) for performing different types of measurement procedures and receiving paging messages.

Step 2: wireless device 22 obtaining information about the serving cell coverage/availability related information.

In this step, the wireless device 22 obtains information about the coverage information of the serving cell which is served or managed or operated by an NTN node e.g., by a satellite node.

The information related to or defining the serving cell coverage is defined as the amount of time available (or available or remaining time) for the serving cell to serve an area or region, which the serving cell is currently serving. The term serving an area may refer to operation of signals (e.g., reference signals, system information, paging, data, random access, etc.) between the serving cell and the wireless device 22 served by that serving cell. The operation of signals refers to transmission of the signals by the wireless device 22 to the serving cell and/or reception of the signals at the wireless device 22 from the serving cell. The area or region or zone may be a geographical area comprising of one or more dimensions e.g., 1 -dimensional, 2-dimensional or 3-dimensional in Euclidean space. The available time for the serving cell may be defined with respect to a reference time (Tr) as described further below.

In one example embodiment, the amount of available time (ATI) for the serving cell to serve the area is function of at least T-service (same as t-Service described herein) and a reference time (Tr) as expressed below by a general function:

ATI = f(T-service, Tr, a, 0) (1)

Examples of function are sum, difference, average, maximum, minimum, ratio, xth percentile, product, combination of two or more functions (e.g., difference, product, etc.).

Where, a and 0 are margins or scaling factors associated with T-service and Tr respectively. They can have positive or negative values, which can be integer or floating point. In one example, a=0=l.

One example of the function defining ATI is expressed below:

ATI = (T-service*a - Tr*0) (2)

In another specific example of the function defining ATI, assuming a=0=l, is expressed as follows:

ATI = (T-service - Tr) (3)

In one example embodiment, Tr is the current time of the wireless device 22. In another example, Tr is a future time at the wireless device 22 e.g., time which the wireless device 22 can estimate or determine with certain accuracy or precision. In another example, Tr is a time closet to certain reference number e.g., to certain SFN value (e.g., closest to the next SFN#0) or H-SFN value. In another example, Tr is a time at the wireless device 22 at or around the occurrence of certain phase of the eDRX cycle. Examples of eDRX cycle phases are start of eDRX cycle, end of eDRX cycle, start of PTW, end of PTW, during PTW, time between successive PTWs (e.g., time between end of the PTW and start of the next PTW) etc. For example, Tr may be the time when the PTW starts or is about to start.

ATI can be expressed in terms of length of time, absolute time, relative time, number of time resources etc. Examples of time resources are: symbol, sub-slot, minislot, time slot, subframe, radio frame, TTI, interleaving time, frame, SFN cycle, hyper- SFN (H-SFN) cycle, etc.

As described herein, the parameter, T-service is obtained by the wireless device 22 from the serving cell by acquiring its SI e.g., SIB.

The wireless device 22 may estimate or update the available coverage time of the serving cell according to one or more of the following principles:

• periodically (e.g., once every LI ms or L2 number of time resources, etc.),

• occasionally (e.g., upon reading SI) and

• when one or more conditions is met e.g., when received signal level such as reference signal receive power (RSRP) or reference signal receive quality (RSRQ) is below threshold, if T-service changes, etc.

FIG. 19 shows an example of the time available for the serving cell of the wireless device 22 to serve or cover the area which is being currently served by that cell. In this example, the available time (ATI) is the same as expressed above by (3).

The serving cell coverage with respect to the wireless device 22 location or with respect to area where the wireless device 22 is located based on the value of ATI may further be characterized into at least two categories or states:

Low or short coverage: In this case the serving cell (Celli) with respect to the wireless device 22 location is considered in a first coverage state (CS1). In one example, Celli is in CS1 provided that ATI > Hl; where Hl is threshold.

• High or long coverage: In this case Celli with respect to the wireless device 22 location is considered in a second coverage state (CS2). In one example, Celli is in CS2 provided that ATI < Hl .

From the wireless device 22 perspective, the serving cell in state, CS2, is in more critical situation as it may soon lose coverage.

The parameter, Hl, can be defined by one or more rules. The parameter, Hl, and/or the rule defining Hl may be pre-defined or configured by the network node 16. This is described with several examples below:

• In one example, Hl may be related to or is function of one or more parameters (e.g., eDRX cycle length, PTW duration, etc.) defining or characterizing the eDRX cycle. For example, Hl and eDRX can be related by any of the following expressions:

Hl = Kl*TeDRX (4)

Hl= K2*TPTW (5) where KI and K2 are scaling factors. Both have positive values and can be integers or can be floating point values. In one example, K1=K2=1. The values of KI and K2 can be predefined or configured by the network node 16.

• In another example, Hl may depend on one or more measurement requirements associated with a measurement (e.g., reference signal receive power (RSRP), reference signal receive quality (RSRQ), cell identification etc.) and which the wireless device 22 is required to meet when performing the measurement. Examples of measurement requirements are measurement time (Tm), measurement accuracy, etc. Examples of measurement time are measurement period, cell identification delay, RS index (e.g., SSB index) acquisition time, etc. In one example, Hl is defined as follows:

Hl= K3*T _m (6) where KI is a scaling factor having positive value and it can be integer or can be floating point value. In one example, K3=l. The value of K3 can be pre-defined or configured by the network node 16.

• In another example, Hl may depend on type of satellite serving or managing or operating Cell 1. Since different satellites move with different speeds, the time the wireless device 22 will spend in CS2 may also depend on the type of satellite. For example, certain types of satellites may not be available for service for a short time meaning that the period of time the wireless device 22 will spend in CS2 is rather short. On the other hand, other types of satellites may not be available for serving for a longer time duration which leads to wireless device 22 spending more time in CS2.

The wireless device 22 may also estimate or update the coverage state of the serving cell according to one or more of the following principles:

• periodically (e.g., once every L3 ms or L4 number of time resources, etc.),

• occasionally (e.g., upon reading SI) and

• when one or more conditions is met e.g., when received signal level such as RSRP or RSRQ is below threshold, if T-service changes, if KI and/or K2 is changed, upon any change in ATI value, etc.

Step 3: wireless device 22 adapts the one or more low activity states based on the determined coverage related information of Celli and uses for one or more operational tasks.

In this step, the wireless device 22 adapts one or more low activity states based on the determined information about the coverage of Celli and uses for one or more operational tasks.

Adapting of the low activity state configurations are triggered based on the coverage state of Celli. The rationale for applying the adapted configuration is that if the coverage of the current cell is going to be impacted and therefore it would be beneficial for the wireless device 22 to apply different set of low activity configuration that allows the wireless device 22 to complete the measurements and evaluate faster compared to following the previous or original configurations. This allows the wireless device 22 to start new measurement or complete an ongoing measurement before the cell (e.g., cells that are indicated by the coverage related information) is going to be out of service or coverage of the area serving the wireless device 22. The term measurement herein includes any combination of cell detection, cell measurement and cell evaluation.

The adapted low activity state configurations can be predefined, configured by any of the network nodes 16 (NW1, NW2) or autonomously determined by the wireless device 22 based on the triggering of coverage change of Celli .

If the coverage state of the serving cell is determined to be CS1 then the wireless device 22 does not adapt or change the low activity state configuration. In this case the wireless device 22 continues operating according to the low activity state configured by the network node 16 e.g., according to the currently configured eDRX and/or DRX cycles. In another example, when the serving cell is in CS1 then the wireless device 22 may use default low activity state configuration for operating signals on the serving cell including reception of paging messages from that serving cell.

If the coverage state of the serving cell is determined to be CS2, then the wireless device 22 adapts or changes or modifies one or more parameters associated with the low activity state configuration configured by the network node 16. The triggering conditions for applying the adapted low activity state configuration can be based on one or more rules, which may be pre-defined or configured by the network node 16. Examples of rules are:

• If the wireless device 22 is currently in coverage state CS2 or expected to be in CS2 in near future, then the wireless device 22 applies the adapted low activity state configuration and operates one or more signals on the cell indicated by CS2, including receiving of paging messages from that cell.

Specific examples of the wireless device 22 adapting one or more parameters associated with the low activity state configuration includes adapting one or more of following parameters related to DRX and/or eDRX:

• Adapting of DRX cycle length or eDRX cycle length; o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 applies a shorter or different DRX cycle length or eDRX cycle length than what was originally configured or intended to be used. A shorter DRX cycle or eDRX cycle would allow the wireless device 22 to wake up more frequently compared to applying longer cycle length and therefore the measurements and evaluations can be completed faster. For example, the wireless device 22 may switch from applying DRX cycle length of 2.56 s to 0.32 s. In another example, the wireless device 22 would switch from applying eDRX cycle length of 10.24 s to 5.12 s. The shorter DRX or eDRX to which the wireless device 22 switches under this condition (i.e., when in state, CS2) can be pre-defined or configured by the network node 16.

• Adapting of drx-inactivity timer o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 applies a shorter or different value for the drx-inactivity timer than what was originally configured or intended to be used. This would allow the wireless device 22 to stay active for longer time and complete the intended UL or DL user data transmissions. In a second example, the wireless device 22 would apply a loner value for the drx-inactivity timer, e.g., this could be the case when the wireless device 22 won’t have sufficient time to complete the UL or DL user data transmission indicated by control channel before the coverage of the cell is impacted.

• Adapting of ON duration o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 applies longer or different ON duration than what was originally configured or intended to be used. This allows the wireless device 22 to receive the control channel (e.g., NPDCCH, PDCCH, wake up signal) faster instead of waiting for the next occasion.

• Adapting of PTW length o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 applies longer or different PTW length than what was originally configured or intended to be used. This would allow the wireless device 22 to stay active for longer time and complete the measurements and evaluations before the coverage of the cell is impacted.

• Adapting of PTW location o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 adapts the PTW location (in time) within the eDRX cycle. In one example the wireless device 22 advances the PTW location (in time) compared to the currently configured location in time. This will allow the wireless device 22 to complete the PTW before the serving cell’s coverage expires. In another example, the wireless device 22 delays the PTW location (in time) compared to the currently configured location in time. This may allow the wireless device 22 to complete other tasks such as receiving SI of the cell before the serving cell’s coverage expires.

• Adapting of H-SFN or DRX cycles used within eDRX. o In one example, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 increases the number of DRX cycles within the PTW of the eDRX cycle by certain margin. For example, the wireless device 22 may increase the number of DRX cycle of 320 ms from 4 to 8 within the PTW provided that the PTW is large enough to accommodate the increased number of DRX cycles.

• Disabling of eDRX. o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 assumes that the eDRX is disabled or discarded. The wireless device 22 therefore disables or discards the eDRX configurations and only operates signals following the DRX configurations i.e., the wireless device 22 disregards the PTW. In this case the wireless device 22 may further monitor the serving cell once every K4*DRX cycle. In one example, K4=l. In another example, K4=2. The wireless device 22 may further perform one or more measurements (e.g., SS-RSRP, SS-RSRQ, etc.) on one or more cells (including serving cell) once every K4 number of DRX cycle. o In a second example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 switches from applying eDRX cycle with PTW to eDRX without PTW. o In a third example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 may disable the eDRX based on relation between one or more eDRX cycle parameters and a threshold:

■ For example, the eDRX cycle is disabled if the eDRX cycle is larger than certain threshold (H21); otherwise the eDRX cycle is not disabled.

■ In another example embodiment, the eDRX cycle is disabled if the PTW of the eDRX cycle is larger than certain threshold (H22); otherwise the eDRX cycle is not disabled.

■ In another example embodiment, the eDRX cycle is disabled if the number of DRX cycles within the PTW of the eDRX cycle is larger than certain threshold (H23); otherwise the eDRX cycle is not disabled.

■ In another example embodiment, the eDRX cycle is disabled if the eDRX cycle is larger than ATI; otherwise the eDRX cycle is not disabled.

■ In another example embodiment, the eDRX cycle is disabled if the PTW of the eDRX cycle is larger than ATI; otherwise the eDRX cycle is not disabled.

■ In another example embodiment, the eDRX cycle is disabled if the number of DRX cycles within the PTW of the eDRX cycle is larger than ATI; otherwise the eDRX cycle is not disabled.

■ In the above example embodiments, the parameters, H21, H22 and H23 can be pre-defined or configured by the network node 16.

• Disabling of DRX o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 assumes DRX to be disabled. The wireless device 22 therefore discards or disables any DRX configuration and operates signals in non-DRX (active) state. If eDRX is configured then the wireless device 22 may further monitor the paging during PTW assuming non-DRX operation within the PTW. o In a second example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 may disable the DRX based on relation between one or more DRX cycle parameters and a threshold:

■ For example, the DRX cycle is disabled if the DRX cycle is larger than certain threshold (H31); otherwise the DRX cycle is not disabled.

■ In another example embodiment, the DRX cycle is disabled if the DRX cycle is larger than ATI; otherwise the DRX cycle is not disabled.

■ In the above example embodiments, the parameter, H31 can be pre-defined or configured by the network node 16.

• Disabling of both DRX and eDRX o In one example embodiment, upon fulfilling the conditions for applying the adapted configuration, the wireless device 22 assumes both eDRX and DRX to be disabled. The wireless device 22 therefore discards or disables any eDRX or DRX configurations and operates signals in non-DRX (active) state.

The wireless device 22 further uses the adapted low activity configuration (e.g., adapted DRX and/or adapted eDRX) for performing one or more operational tasks. Examples of tasks are:

• Performing one or more measurements on one or more cells according to the adapted DRX and/or adapted eDRX configuration e.g., measures once every Km number of DRX cycle, measures during the adapted PTW etc.

• Monitors paging according to the adapted DRX cycle and/or adapted eDRX cycle e.g., monitors the paging during the adapted ON duration of the DRX cycle.

• Acquiring SI of the cell according to the adapted DRX cycle and/or adapted eDRX cycle.

• Informing the network node 16 about the adaptation of the low activity state configuration e.g., by transmitting a message such as via RRC.

Some example embodiments corresponding to network node 16 are as follows:

1 A. A network node 16 configured to communicate with a wireless device, WD

22, in a communication system, the communication system comprising a non-terrestrial network, NTN, the NTN comprising a serving cell associated with the network node 16, the serving cell being configurable for serving the WD 22 in a coverage area, the network node 16 being configured to: cause transmission, to the WD 22, of first information about one or more configurations corresponding to an operation of the WD 22 in a low activity state; broadcast second information relating to the serving cell of the NTN, the second information indicating at least one of coverage and availability of the serving cell. The second information may be broadcasted by network node 16 in the serving cell and/or any other cell; receive a message informing the network node 16 about an adaptation of the one or more configurations based on the second information; and perform one or more actions based on the received message. For example, network node 16 can reconfigure the low activity state of the WD 22 based on the received message. More specifically, network node 16 can update the DRX or eDRX parameters which are listed below based on the received updated info from the WD 22. Network node 16 may also send/update system information to the WD 22 regarding the adaptation or the time instant of starting/ending adaptation.

2 A. The network node 16 of Embodiment 1 A, wherein the second information includes a time available, ATI, for the serving cell to serve the coverage area that the serving cell is currently serving, ATI being based on T-service and Tr, T-service being time information about when the serving cell is going to stop serving the coverage area, Tr being a reference time.

3A. The network node 16 of any one of Embodiments 1A and 2A, wherein the one or more configurations include one or both of: a discontinuous reception, DRX, cycle; and an enhanced DRX, eDRX, cycle.

4A. The network node 16 of Embodiment 3 A, wherein the one or more configurations further include one or more parameters associated with at least one of the DRX cycle and the eDRX cycle, the one or more parameters including one or more of: a DRX cycle length; an eDRX cycle length; a discontinuous reception inactivity timer; an ON duration; a paging time window, PTW, length; a PTW location; a hyper system frame number, H-SFN; and one or more DRX cycles within the eDRX.

5 A. The network node 16 of Embodiment 4 A, wherein the one or more configurations are adapted by one or more of: adjusting one or both of the DRX cycle length and the eDRX cycle length; adjusting the discontinuous reception inactivity time to allow the WD 22 to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN. Measurements may also be performed on a neighbor cell. In addition, the WD 22 may be served by the serving cell of the NTN. adjusting the ON duration to allow the WD 22 to receive control channel signaling while being served by the serving cell of the NTN; adjusting the PTW length to complete measurements while being served by the serving cell of the NTN; increasing the H-SFN to accommodate an adjusted number of DRX cycles; and disabling one or both of DRX and eDRX.

6 A. A method in a network node 16 configured to communicate with a wireless device, WD 22, in a communication system, the communication system comprising a nonterrestrial network, NTN, the NTN comprising a serving cell associated with the network node 16, the serving cell being configurable for serving the WD 22 in a coverage area, the method comprising: transmitting, to the WD 22, first information about one or more configurations corresponding to an operation of the WD 22 in a low activity state; broadcasting second information relating to the serving cell of the NTN, the second information indicating at least one of coverage and availability of the serving cell; receiving a message informing the network node 16 about an adaptation of the one or more configurations based on the second information; and performing one or more actions based on the received message.

7 A. The method of Embodiment 6 A, wherein the second information includes a time available, ATI, for the serving cell to serve the coverage area that the serving cell is currently serving, ATI being based on T-service and Tr, T-service being time information about when the serving cell is going to stop serving the coverage area, Tr being a reference time.

8 A. The method of any one of Embodiments 6 A and 7 A, wherein the one or more configurations include one or both of: a discontinuous reception, DRX, cycle; and an enhanced DRX, eDRX, cycle.

9 A. The method of Embodiment 8 A, wherein the one or more configurations further include one or more parameters associated with at least one of the DRX cycle and the eDRX cycle, the one or more parameters including one or more of: a DRX cycle length; an eDRX cycle length; a discontinuous reception inactivity timer; an ON duration; a paging time window, PTW, length; a PTW location; a hyper system frame number, H-SFN; and one or more DRX cycles within the eDRX.

10 A. The method of Embodiment 9 A, wherein the one or more configurations are adapted by one or more of: adjusting one or both of the DRX cycle length and the eDRX cycle length; adjusting the discontinuous reception inactivity time to allow the WD 22 to complete transmission of uplink signaling and/or reception of downlink signaling while being served by the serving cell of the NTN; adjusting the ON duration to allow the WD 22 to receive control channel signaling while being served by the serving cell of the NTN; adjusting the PTW length to complete measurements while being served by the serving cell of the NTN; increasing the H-SFN to accommodate an adjusted number of DRX cycles; and disabling one or both of DRX and eDRX.

The following is a nonlimiting list of other example embodiments.

Embodiment Al . A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: transmit to the wireless device at least one of: information relating to at least one configuration corresponding to operation of the wireless device in a low activity state; and information relating to a serving cell, the information comprising at least one of coverage and availability; and communicate with the wireless device based on an adapted low activity state configuration of the wireless device.

Embodiment A2. The network node of Embodiment Al, wherein the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE.

Embodiment A3. The network node of Embodiment Al, wherein the configuration includes an enhanced DRX (eDRX) cycle.

Embodiment Bl. A method implemented in a network node, the method comprising: transmitting to a wireless device at least one of: information relating to at least one configuration corresponding to operation of the wireless device in a low activity state; and information relating to a serving cell, the information comprising at least one of coverage and availability; and communicating with the wireless device based on an adapted low activity state configuration of the wireless device.

Embodiment B2. The method of Embodiment Bl, wherein the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE.

Embodiment B3. The method of Embodiment B 1 , wherein the configuration includes an enhanced DRX (eDRX) cycle.

Embodiment Cl . A wireless device (WD) configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive information relating to at least one of: at least one configuration corresponding to operation of the wireless device in a low activity state; a serving cell, the information indicating at least one of coverage and availability; and adapt at least one low activity state configuration based on the received information.

Embodiment C2. The WD of Embodiment Cl, wherein the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE.

Embodiment C3. The WD of Embodiment Cl, wherein the configuration includes an enhanced DRX (eDRX) cycle.

Embodiment DI . A method implemented in a wireless device (WD), the method comprising: receiving information relating to at least one of: at least one configuration corresponding to operation of the wireless device in a low activity state; a serving cell, the information indicating at least one of coverage and availability; and adapting at least one low activity state configuration based on the received information.

Embodiment D2. The method of Embodiment DI, wherein the low activity state correlates to a radio resource control (RRC) state, the state including at least one of RRC IDLE and RRC INACTIVE.

Embodiment D3. The method of Embodiment DI, wherein the configuration includes an enhanced DRX (eDRX) cycle.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include: Abbreviation Explanation 3GPP 3rd Generation Partnership Project

5G 5th Generation

BS Base Station

CHO Conditional Handover eNB Evolved NodeB (LTE base station)

GEO Geostationary Orbit gNB Base station in NR.

GNSS Global Navigation Satellite System

HO Handover

LEO Low Earth Orbit

LTE Long Term Evolution

MAC Medium Access Control

NR New Radio

NW Network

NTN Non-Terrestrial Network

RAT Radio Access Technology

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSRP Reference Signal Received Power

SMTC SSB Measurement Timing Configuration

SNR Signal to noise ratio

UE User Equipment

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.