Managing discontinuous coverage and discontinuous reception in NTN
By negotiating and adjusting the paging time window in the NTN environment, the problem of inefficiency of UE under coverage discontinuity and limited power is solved, and the connection efficiency of user equipment and monitoring capabilities within coverage are improved.
Patent Information
- Application Number
- CN202380034567.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-25
- Filing Date
- 2023-04-24
- Publication Date
- 2024-11-15
AI Technical Summary
In a non-terrestrial network (NTN) environment, user equipment (UE) has difficulty effectively monitoring paging messages due to coverage discontinuity and limited power, resulting in inefficiency and difficulty in connection.
By negotiating the paging time window (PTW) between the user equipment (UE) and the network, monitoring the paging message in a non-connected state, and entering low-power sleep mode during the out-of-cover period, adjusting the PTW with satellite coverage period information, Ensure that the UE wakes up and monitors messages during the overwrite period to improve connection opportunities.
Effectively reduces the UE's ineffective wake-up and low power consumption, improves the opportunity to monitor and receive notifications or data in an NTN environment, and improves the connection efficiency of user equipment.
Smart Images

Figure CN118975161A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to methods, apparatus, and articles of manufacture in wireless communication systems, such as 3GPP communication systems. Background Art
[0002] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent that it is described in this background section, and aspects of the specification that otherwise may not be considered prior art at the time of filing, are neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0003] The goals behind developing fifth-generation (5G) technology include providing a unified framework for communication types such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).
[0004] 5G technology mainly relies on traditional terrestrial networks. However, the Third Generation Partnership Project (3GPP) organization has proposed to extend 5G communications to non-terrestrial networks (NTNs) using 5G New Radio (NR) technology or using Long Term Evolution (LTE) technology customized for narrowband Internet of Things (NB-IoT) or enhanced machine type communication (eMTC) scenarios. In NTNs, RF transceivers are installed on satellites, unmanned aircraft systems (UAS) (also known as drones, balloons, airplanes), or another suitable device. For simplicity, the following discussion refers to all such devices as satellites. In addition to satellites, NTNs may also include satellite gateways (sat-gateways) that connect non-terrestrial networks to public data networks, feeder links between satellite gateways and satellites, service links between satellites, and inter-satellite links (ISLs) when satellites form constellations.
[0005] Satellites may be of one of several types based on altitude, orbit, and beam footprint size. The types include low earth orbit (LEO) satellites, medium earth orbit (LEO) satellites, geostationary orbit (GEO) satellites, UAS platforms (including high altitude platform stations (HAPS)), and highly elliptical orbit (HEO) satellites. GEO satellites are also known as geosynchronous orbit (GSO) satellites, and LEO / MEO satellites are also known as non-GSO (NGSO) satellites.
[0006] GSO satellites can communicate with one or several satellite gateways deployed over the satellite's target coverage area (e.g., a region or even a continent). Non-GSO satellites can communicate with one or several serving satellite gateways at different times. NTN is designed to ensure service and feeder link continuity between consecutive serving satellite gateways, with sufficient duration for mobile anchoring and handover.
[0007] Satellites can support transparent or regenerative (with onboard processing) payloads and typically generate several beams for a given service area defined by the field of view. The coverage area of the beam typically has an elliptical shape and depends on the onboard antenna configuration and elevation angle. For transparent payload implementations, the satellite can apply RF filtering as well as frequency conversion and amplification without changing the waveform signal. For regenerative payload implementations, the satellite can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and encoding / modulation. This approach is actually equivalent to implementing most of the functions of a base station (e.g., gNB).
[0008] NB-IoT and eMTC technologies are expected to be particularly useful for IoT devices operating in remote areas with limited or no terrestrial connectivity. Such IoT devices can be used in a variety of industries, including, for example, transportation (marine, road, rail, aviation) and logistics; solar energy, oil and gas extraction; utilities; agriculture; environmental monitoring; and mining. However, to ensure the required IoT connectivity, the deployment of these technologies requires satellite connectivity to provide coverage beyond terrestrial deployments. Satellite NB-IoT or eMTC is defined in a complementary manner to terrestrial deployments.
[0009] In these and other applications, user equipment (UE) may experience coverage that is discontinuous in time and only occasionally has coverage. Furthermore, because UEs in such applications typically have limited power, the UEs may only wake up periodically and operate in a sleep mode with no connectivity between these relatively short periods. When the time when the UE wakes up is not well aligned with the coverage time, the UE may be unreachable for long periods of time. Summary of the invention
[0010] In general, the techniques of this disclosure allow UEs to monitor paging more efficiently. The UE and the network use these techniques to align the paging time window (PTW) with the satellite coverage period to reduce the number of situations where the UE wakes up but cannot receive any downlink signals, thereby inefficiently using power. Further, these techniques increase the chance that the network can page the UE to deliver notifications or data.
[0011] An example embodiment of these techniques is a method for monitoring paging from a non-terrestrial network (NTN). The method is implemented in a UE and includes: receiving, by one or more processors, a configuration of a PTW from the NTN, during which the UE operating in a non-connected state monitors for paging messages and enters a sleep period after the PTW, during which the UE operates in a low-power sleep mode; determining, by one or more processors, that the UE lacks NTN coverage during the PTW; and modifying, by one or more processors, the PTW to generate a modified PTW in response to the determination.
[0012] Another example embodiment of these techniques is a method for monitoring paging from an NTN. The method is implemented in a UE and includes: receiving a first paging time window (PTW) indication from the NTN when the UE is in a connected state, during which the UE operating in a non-connected state monitors for paging messages; and receiving, by one or more processors during the PTW, a second PTW indication specifying a second PTW.
[0013] Still another example embodiment of the techniques is a UE including one or more processors and configured to implement the above method.
[0014] Another example embodiment of the techniques is a method for paging a UE configured with a PTW via an NTN, during which the UE operating in a non-connected state monitors paging messages and enters a sleep period after the PTW, during which the UE operates in a low-power sleep mode. The method is implemented in a network device and includes: providing, by one or more processors, an indication to the UE that if the UE lacks NTN coverage during the PTW, the UE will modify the PTW; modifying, by the one or more processors, the PTW to generate a modified PTW; and paging, by the one or more processors, during the modified PTW.
[0015] Yet another example embodiment of these techniques is a method for paging a UE via an NTN, the method being implemented in a network device and comprising: transmitting, by one or more processors, a first PTW indication specifying a first PTW to the UE when the UE is in a connected state, during which the UE operating in a non-connected state monitors for paging messages; and transmitting, by one or more processors, a second PTW indication specifying a second PTW to the UE during the PTW.
[0016] Still another embodiment of these techniques is a method for paging a UE via an NTN, the method comprising: determining, by one or more processors, a periodicity of coverage periods during which a satellite provides coverage to the UE, the coverage periods being separated by time intervals during which the satellite does not provide coverage to the UE; generating, by the one or more processors, a configuration of a paging cycle, comprising selecting a duration of the paging cycle based on the periodicity of the coverage periods, the paging cycle comprising (i) a PTW during which the UE operating in a non-connected state monitors for paging messages, and (ii) a sleep period during which the UE operates in a sleep mode; and transmitting, by the one or more processors, the configuration to the UE.
[0017] Another example embodiment of the techniques is a network device including one or more processors and configured to implement the above method. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1A is a block diagram of an example wireless communication system in which user devices and base stations of the present disclosure may implement the paging techniques of the present disclosure;
[0019] Figure 1B The centralized unit (CU) and the distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.
[0020] Figure 2A yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a base station;
[0021] Figure 2B yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a CU and a DU;
[0022] Figure 3A is a block diagram of an example NTN node with a transparent payload implementation;
[0023] Figure 3B is a block diagram of an example NTN node with a transparent payload implementation in which a base station is connected to multiple satellites via the same satellite gateway;
[0024] Figure 4A Shown is the supply Figure 3A An exemplary user plane protocol stack for use with an architecture of
[0025] Figure 4B Shown is the supply Figure 3A An exemplary control plane protocol stack for use with an architecture;
[0026] Figure 5 An example configuration is shown according to which a UE implements extended discontinuous reception (eDRX);
[0027] Figure 6 An example scenario is shown where the UE has satellite coverage during certain time periods separated by non-coverage intervals;
[0028] Figure 7 An example scenario is shown where a user equipment is configured with eDRX and is experiencing discontinuous coverage in an NTN environment;
[0029] Figure 8 is a flow chart of an example method for estimating discontinuous coverage periods in an NTN that may be implemented by a user equipment of the present disclosure;
[0030] Fig. 9 shows how a UE may use example assistance information including attributes of a cell;
[0031] Fig.10 shows how a UE may use example assistance information including attributes of a satellite;
[0032] Fig.11 An example scenario is shown in which the UE and the network adjust the PTW timing to align the PTW with the satellite coverage period;
[0033] Fig.12 is a message passing diagram for an example scenario in which a UE and a network exchange messages to align PTW timing with a satellite coverage period;
[0034] Fig.13 is a flow chart of an example method that may be implemented by a UE of the present disclosure for determining whether to shift a PTW and by how much;
[0035] Fig.14 An example scenario is shown in which the UE and the network extend the duration of the PTW to overlap at least the satellite coverage period;
[0036] Fig.15 is a message passing diagram for an example scenario in which a UE and a network exchange messages to extend the PTW length;
[0037] Fig.16 is a flow chart of an example method that may be implemented by a user device of the present disclosure for determining whether to extend a PTW;
[0038] Fig.17 An example scenario is shown where the network dynamically configures the UE to have a next PTW;
[0039] Fig.18 illustrates an example messaging diagram for an example scenario in which a UE and a network exchange messages to dynamically configure an upcoming PTW;
[0040] Fig.19 is a flow chart of an example method that may be implemented in a user device of the present disclosure for determining when to initiate a dynamically configured PTW;
[0041] Fig. 20 An example scenario is shown in which the UE and the network implement a mechanism for aligning the eDRX cycle with the periodicity of a certain satellite covering a certain area;
[0042] Fig.21 is a flow chart of an example method that may be implemented in a base station and / or MME of the present disclosure for paging a UE via an NTN using a modification of an initial PTW configuration;
[0043] Fig. 22is a flow chart of an example method that may be implemented in a base station and / or MME of the present disclosure for paging a UE via an NTN using a dynamic "next PTW" indication; and
[0044] Fig.23 is a flow chart of an example method that may be implemented in a base station and / or MME of the present disclosure for paging a UE via an NTN using alignment of PTW with satellite coverage periodicity. DETAILED DESCRIPTION
[0045] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure for managing early data communications and transitioning the UE between states of a protocol for controlling radio resources between the UE and the RAN.
[0046] First reference Figure 1A , the example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the core network (CN) 110. For example, the CN 110 may be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.
[0047] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB or an eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB or an eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of the base stations 104, 106 may be connected to the CN 110 via an interface (eg, an S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (eg, an X2 or Xn interface).
[0048] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to transmit user plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally speaking, UPF 162 is configured to transmit user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.
[0049] like Figure 1A As shown, base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or switch from one of cells 124 and 126 to the other. In order to exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.
[0050] As discussed in detail below, the UE 102 and / or the RAN 105 may utilize the techniques of this disclosure when a radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 is operating in an inactive or idle state of a protocol for controlling radio resources between the UE 102 and the RAN 105. For clarity, the examples below relate to the RRC_INACTIVE or RRC_IDLE states of the RRC protocol.
[0051] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions, and the one or more general-purpose processors execute the instructions. In addition or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a processor 132 to process data to be transmitted by the base station 104 in the downlink direction, or to process data received by the base station 104 in the uplink direction. The processing hardware 130 may also include a transmitter 136, which is configured to transmit data in the downlink direction. The processing hardware may further include a receiver 134, which is configured to receive data in the uplink direction. The base station 106 may include substantially similar components. Specifically, the components 140, 142, 144, and 146 of the base station 106 may be similar to the components 130, 132, 134, and 136, respectively.
[0052] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. In an example implementation, processing hardware 150 includes a processor 152 to process data to be transmitted by UE 102 in an uplink direction, or to process data received by UE 102 in a downlink direction. Processing hardware 150 may also include a transmitter 156 configured to transmit data in a downlink direction. Processing hardware may further include a receiver 154 configured to receive data in an uplink direction.
[0053] Figure 1B An example distributed or decentralized implementation of any one or more of base stations 104, 106 is depicted. In this implementation, base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DU) 174. CU172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on a general-purpose processor, and / or a dedicated processing unit. For example, CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller. In some implementations, CU 172 may include a radio link control (RLC) controller configured to manage or control one or more RLC operations or processes. In further implementations, CU 172 does not include an RLC controller.
[0054] Each DU in DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors, and / or dedicated processing units. For example, the processing hardware may include: a MAC controller configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or processes.
[0055] In some embodiments, the RAN 105 supports integrated access and backhaul (IAB) functionality. In some implementations, the DU 174 operates as an IAB node and the CU 172 operates as an IAB donor. In some embodiments, the RAN 105 supports non-terrestrial network (NTN) functionality.
[0056] In some implementations, the CU 172 may include a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. The CU 172 may also include a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. The CU-CP 172A may transmit control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may transmit data packets (e.g., SDAP PDUs or Internet Protocol packets).
[0057] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the service requested by UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, the connection between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.
[0058] Figure 2AAn example protocol stack 200 is shown in a simplified manner according to which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).
[0059] In the example stack 200, the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 may in turn provide data transfer services to the Service Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer ( Figure 2A (not shown) provides data transmission services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support switching between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE 102 can support the layering of NR PDCP 210 above the EUTRA RLC 206A, and the layering of SDAP sublayer 212 above the NR PDCP sublayer 210.
[0060] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as service data units (SDUs) (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as protocol data units (PDUs) (e.g., to the RLC layer 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as "packets," except where the distinction between SDUs and PDUs is relevant.
[0061] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2AThe EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide data radio bearers (DRBs) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.
[0062] Figure 2B An example protocol stack 250 is shown in a simplified manner in which UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and provides SRBs to the RRC 214.
[0063] Figure 3A A certain type of NTN deployment, referred to as a transparent payload architecture, is shown, which involves a satellite gateway 302 and a "transparent" satellite 304 for extending the range of the Uu interface. The satellite 304 implements frequency conversion and radio frequency (RF) amplifiers in both the uplink and downlink directions. The satellite functions are similar to those of an analog RF repeater. Therefore, the satellite 304 relays the Uu radio interface from the feeder link (between the NTN gateway and the satellite) to the service link (between the satellite and the UE) in the downlink direction, and vice versa in the uplink direction. The satellite radio interface (SRI) on the feeder link is Uu, and the NTN gateway 302 supports all functions necessary to forward the signals of the Uu interface. The NTN gateway 302 can be placed at the same site as the base station (e.g., eNB, gNB) 104, or connected to the base station 104 at a certain distance via a wired link. More than one NTN gateway can also be connected to the base station. Different transparent satellites can be connected to the same base station on the ground via the same NTN gateway or via different NTN gateways. Figure 3B A situation is shown where two different satellites (304 and 306) are connected to the same base station 104 via the same NTN gateway 302 and the two satellites (304 and 306) cover the earth's surface using two different physical cell IDs (PCIs).
[0064] The NTN user plane protocol stack involving UE 102, satellite 304, NTN gateway 302, BS 104 and S-GW 114 is described in detail in FIG. Figure 4A The diagram of the NTN user plane protocol stack is similar to that of the terrestrial network (TN), with the addition of two new nodes placed in the middle of the Uu interface, namely the satellite 304 and the NTN gateway 302. Similarly, Figure 4B The NTN control plane protocol stack shown is also similar to the protocol stack of the terrestrial network.
[0065] In terms of satellite mobility patterns, there are three types of service links supported by NTN: ● Geofixed: configured by a beam that always continuously covers the same geographical area (e.g. the case of GEO / GSO satellites) ● Quasi-geo-fixed: configured by beams that cover one geographical area during a limited period of time and a different geographical area during another period of time (e.g. the case of LEO / MEO satellites that can use steerable beams) • Geomobile: A beam configuration whereby its coverage area slides above the Earth's surface (eg, the case of LEO / MEO satellites using fixed or unsteerable beams).
[0066] Using LEO / MEO satellites, eNB can provide quasi-Earth fixed cell coverage or Earth mobile cell coverage. Using GEO satellites, eNB can provide Earth fixed cell coverage.
[0067] although Figure 3A / Figure 3B The transparent payload architecture shown is the focus of current 3GPP development, but the regenerative payload architecture that installs the eNB function on the satellite is also a possible NTN deployment in the future. In this type of architecture, Uu only exists between the satellite and the UE. In general, the technology of this disclosure can be applied to both the transparent payload architecture and the regenerative payload architecture.
[0068] Extended discontinuous reception (eDRX) is an extension of the DRX feature used by IoT or MTC devices to further reduce power consumption. With the DRX mechanism, a user device can enter sleep mode for a specific period of time and then wake up after the sleep period to monitor the DL signal from the base station. The DRX cycle defines the time interval between two consecutive time periods when the UE wakes up. eDRX enhancement will extend the DRX cycle to allow the device to remain in sleep mode for a longer period of time. eDRX enhancement can be used with or without power saving mode (PSM) to achieve additional power savings. eDRX was developed by the standardization organization 3GPP and was introduced since 3GPP Release 13.
[0069] In one example, a typical LTE device can be configured with a paging cycle (i.e., DRX cycle) of up to 2.56 seconds. With such a configuration, the UE wakes up every 2.56 seconds during the paging opportunity (PO) in the paging frame (PF) and monitors for paging from the network. On the other hand, an LTE device supporting eDRX can be configured with an eDRX cycle of up to 2621.44 seconds, which allows the device to wake up once every 2621.44 seconds for a paging time window (PTW). Therefore, LTE devices supporting the eDRX feature can consume much less power than devices that do not support this feature. In addition, NB-IoT devices (which support eDRX by default) can be configured with an eDRX cycle of up to 10485.76 seconds, which allows the device to wake up once every 2.9 hours, and therefore, NB-IoT devices can save even more power than LTE devices supporting eDRX. Devices supporting the eDRX feature do not need to wake up for the entire PTW (ranging from 1.28 seconds to 20.48 seconds), but only wake up at the paging occasions within the PTW determined by the legacy DRX configuration / parameters.
[0070] The UE and the network (e.g., MME) negotiate DRX and eDRX parameters using the following messages: Attach Request, Attach Accept, Tracking Area Update Request, and Tracking Area Update Accept. During the attach process, the UE provides preferred values for DRX and eDRX parameters in the AttachRequest message, and the network provides the final values of these parameters in the Attach Accept message. The UE may transmit an Attach Complete message to the network in response to the Attach Accept message. Similarly, during the Tracking Area Update (TAU) process, preferred values for DRX and eDRX parameters are provided by the UE in the Tracking Area Update Request message, and the final values of these parameters are provided by the network in the Tracking Area Update Accept message. The UE may transmit a TAU Complete message to the network in response to the TAU Accept message. In case of DRX configuration for non-NB-IoT devices, the network will only accept or reject the preferred DRX configuration set by the UE in the Attach Request / Tracking Area Update Request and will not provide the revised configuration in the Attach Accept / Tracking Area Update Accept message.
[0071] The DRX cycle length can be configured from the following values: {320ms, 640ms, 1280ms, 2560ms}. For NB-IoT devices, the PTW length can be configured from the following values: {2.56s, 5.12s, 7.68s, 10.24s, 12.8s, 15.36s,17.92s, 20.48s, 23.04s, 25.6s, 28.16s, 30.72s, 33.28s, 35.84s, 38.4s,40.96s} and the eDRX cycle length can be configured from the following values: {5.12s, 10.24s, 20.48s, 40.96s,61.44s, 81.92s, 102.4s, 122.88s, 143.36s, 163.84s, 327.68s, It should be noted that if the eDRX cycle length is configured as 5.12s, the UE will not have a PTW, and the UE will only perform conventional DRX operation in which the DRX cycle length is equal to 5.12s.
[0072] Figure 5 An example is shown in which the UE is configured with an eDRX cycle equal to 20.48 seconds, a PTW equal to 5.12 seconds, and a DRX cycle equal to 1.28 seconds. In this example, the UE is configured to wake up 4 times (one paging occasion (PO) each) in the PTW in order to monitor paging messages. In addition to the PTW, the UE can completely shut down its radio module for about 15.36 seconds per eDRX cycle and thus save a lot of power.
[0073] Figure 6 An example scenario is shown in which UE 102 is served by LEO satellite 304 from t1 to t2 and by another LEO satellite 306 from t3 to t4. During the period between t2 and t3, UE 102 is not served by any satellite or any ground base station and is therefore out of coverage. Typically, when a UE loses coverage of a serving cell, the UE begins searching for other cells and then camps on a suitable cell. However, in Figure 6 In the example shown, even if UE 102 starts searching for other cells immediately after t2, the UE cannot find the cell, and thus searching for other cells only causes the UE to consume power. Figure 6 In order to optimize the power consumption of the UE in the scenario depicted in FIG), the UE may not need to perform a cell search and the access stratum (AS) functionality may be deactivated during periods when the UE is not within the coverage area of the satellite.
[0074] However, doing so would require the UE to know when the UE will be outside the coverage area and when the UE will be inside the coverage area again, so as to reactivate its cell search or AS function before the UE falls into the coverage of another NTN cell. The ephemeris information broadcasted in the system information provides constellation and trajectory / mobility information of the serving satellite and neighboring satellites, which helps the UE predict / estimate when it will be inside the NTN coverage and when it will be outside the NTN coverage. However, relying on the ephemeris information alone may not be sufficient for the UE to estimate / predict the coverage, because not every satellite projects its beam / cell vertically onto the earth and has the same size of coverage. The UE may need some other information to estimate / predict the coverage of the NTN cell more accurately.
[0075] Figure 7 An example is shown in which the UE is configured with an eDRX cycle equal to 2621.44 seconds and a PTW length equal to 10.24 seconds. The UE is located in a coverage period 702 of an earth mobile cell controlled by a first satellite from t1 to t2, is located in a coverage period 704 of another earth mobile cell controlled by a second satellite from t5 to t6, and is located in a coverage period 705 of a second earth mobile cell controlled by a second satellite from t9 to t10. 10 Again, it is within the coverage period 706 of the earth mobile cell controlled by the first satellite. Apart from these intervals, the UE has no satellite coverage or TN coverage. The UE wakes up and monitors for paging during the PTW 708 starting at t3 and ending at t4, but the UE cannot detect any signal in this scenario because no satellite provides coverage for the UE during this time period. Therefore, it may take much longer than expected to contact the UE configured with eDRX in the discontinuous coverage scenario compared to the continuous coverage scenario or the scenario involving a terrestrial network. If no PTW falls within the coverage period of any satellite, then in the discontinuous coverage scenario, the network may not even be able to page the UE configured with eDRX at all. The techniques discussed below address these problems.
[0076] Figure 8 8 is a flow chart of an example method 800 for estimating a period of discontinuous coverage that may be implemented by a UE (e.g., UE 102 in the present disclosure). Initially, at block 802, the UE is in an RRC_IDLE state and camps on an NGSO satellite. Then, at block 804, the UE determines the type of service link (e.g., quasi-geo-fixed or geo-mobile) provided by the NGSO satellite. Generally speaking, a quasi-geo-fixed service link is on a beam that covers one geographic area for a certain period of time and then jumps to another geographic area for another period of time. On the other hand, a geo-mobile service link is on a beam whose coverage area slides over the surface of the earth. For example, the UE may determine the mobility pattern of the NGSO satellite based on received satellite ephemeris information, received system information, or received NAS information.
[0077] When the NGSO satellite provides a quasi-geo-fixed service link, the UE may expect to receive assistance information from the NTN related to the attributes of the cell projected onto the surface of the earth (block 806). This type of assistance information may be referred to as "NTN cell-related assistance information" hereinafter. When the NGSO satellite provides an earth-mobile service link, the UE may expect to receive assistance information from the NTN related to the attributes of the satellite (block 808), hereinafter referred to as "satellite-related assistance information". When the NTN provides both NTN cell-related assistance information and satellite-related assistance information, or when the UE otherwise obtains both types of assistance information, the UE may determine which set of attributes to use based on the type of service link (e.g., earth-mobile or quasi-geo-fixed) that the UE is currently using to communicate with the serving satellite.
[0078] At block 810, the UE may estimate time periods during which the UE will lack satellite coverage based on the attributes selected and applied at block 806 or block 808. Since the UE is likely to also lack terrestrial network (TN) coverage, these time periods may be understood as discontinuous coverage periods. Based at least in part on the results of the estimation at block 810, the UE may deactivate the AS functionality and / or the radio module during the discontinuous coverage period (block 812).
[0079] For further clarity, Fig. 9 An example application of NTN cell-related assistance information is shown. This type of assistance information may include information related to a serving cell 902, such as an indication of the time at which the cell 902 will no longer provide service for a particular geographic area, the center coordinates 904 of the serving cell 902, and the radius 906 of the serving cell 902. NTN cell-related assistance information may also include information related to one or more neighboring or "upcoming" (in terms of future service) cells. For example upcoming cells 908, 914, and 920, this information may indicate the time at which the cell will begin to provide service for the geographic area ("start time") and the time at which the cell will stop providing service for the geographic area ("stop time"). The information related to the upcoming cell may further indicate the center coordinates of the cell (e.g., coordinates 910, 916, and 922) and the radius of the cell (e.g., radius 912, 918, and 924).
[0080] like Fig. 9As shown, the center coordinates and the radius together define a specific geographic area, and the UE may need to obtain and use its GNSS coordinate information to determine whether the UE will be located within the geographic area defined by the center coordinates and the radius. If the information of the upcoming cell only contains the start time and the stop time, the UE may interpret this format as indicating that the upcoming cell provides the same geographic coverage as the serving cell. In this case, even without obtaining and using its GNSS coordinate information, the UE (when stationary) can determine that it will definitely be located within the coverage area of the upcoming cell.
[0081] In the above discussion, it is assumed that each cell is a circular cell, and therefore the center coordinates and the cell radius accurately define the cell geometry. However, in other scenarios these cells may be non-circular (e.g., rectangular, elliptical, hexagonal). In these cases, the NTN cell-related assistance information may specify the focus instead of the center coordinates, and specify the semi-minor axis, semi-major axis, diameter, width and / or length, etc. instead of the radius.
[0082] Fig.10 An example application of satellite-related assistance information is shown. This information may include, for example, satellite constellation information (i.e., satellite ephemeris information) of a serving satellite and adjacent or upcoming satellites, which may be used by the UE and / or the serving satellite to determine different positioning of a satellite at different times. For example, assuming that the satellite 304 projects its beam vertically onto the surface of the earth at a sub-satellite point 1002, and the UE has relevant satellite ephemeris information and the radius of the earth mobile cell, the UE may determine the geographic area of the earth mobile cell. However, in many cases, the satellite 304 may project its beam onto the surface at a non-zero (i.e., non-vertical) antenna panel tilt angle, which makes the reference point 1008 the center coordinate of the earth mobile cell at time t1. Therefore, in addition to the satellite ephemeris information and the cell radius, the base station may also need to provide the UE with the angle of the antenna panel tilt angle so that the UE determines the geographic area of the earth mobile cell corresponding to the satellite.
[0083] exist Fig.10 In the example shown, the antenna panel tilt angle provided by the base station is the angle spanned by line 1010 and line 1004, which can be represented by θ. Instead of providing the cell radius, the base station can provide the minimum antenna panel tilt angle spanned by line 1014 and line 1004 (represented by θ min ) and the maximum antenna panel tilt angle spanned by lines 1012 and 1004 (denoted by θ max ). Using satellite ephemeris information, θ, θ min and θ max , the UE can determine the geographical area of the earth mobile cell corresponding to the satellite.
[0084] Return to reference Figure 8 , if the UE can camp on the TN cell during the discontinuous coverage period, the UE should not deactivate the AS function and / or the radio module during the estimated discontinuous coverage period in some cases (see box 812). In some cases, the NTN base station signals the availability of the TN cell in the system information. The signaling can be a binary indication indicating whether there is a TN cell within the coverage area of the serving NTN cell, or a more detailed indication including the positioning and size of the TN cell deployed within the coverage of the serving NTN cell. As an alternative to box 812, upon receiving such an indication and in view of the current positioning of the UE, the UE can determine whether to deactivate the AS function and / or the radio module during the discontinuous coverage period.
[0085] Next, Fig.11 An example scenario is shown in which the UE and the NTN modify the PTW by shifting the PTW and aligning the PTW with the satellite coverage period and the UE can thus receive a paging message during the modified PTW. Fig.12 The message passing diagram and Fig.13 The flow chart further discusses this approach.
[0086] The UE obtains the original PTW configuration including PTWs 1102 and 1104. However, the UE estimates that it will be within the coverage area of the NTN cell during time periods 1108, 1110, and 1112. Outside of these time periods, the UE turns off the AS function and / or the radio module to save power, and does not monitor paging during the scheduled PTWs 1102 and 1104. In order to contact the UE regarding a mobile-terminated (MT) event, the network (e.g., MME) may need to send a paging message to the UE during the period when the UE has activated the AS function and / or the radio module (i.e., during the period 1108, 1110, and 1112), and the UE therefore needs to monitor paging during these periods.
[0087] The network may schedule paging and cause the UE to monitor for paging during a PTW 1106 that is shifted in time relative to the originally configured PTW 1102. The duration of the PTW 1106 may be equal to the duration of the PTW 1102. The UE may avoid monitoring for paging messages during the PTW 1102 and instead operate in a sleep mode during the originally configured PTW 1102. The start time of the PTW 1106 may substantially coincide with time t5 at which the UE enters (or is expected to enter) the coverage period 1110.
[0088] In another implementation or scenario, the network and the UE shift the PTW backward in time toward the period 1108 preceding the originally configured PTW 1102, rather than shifting forward in time to the period 1110 as described above. In this case, the start time of the PTW 1106 may substantially coincide with the time t1 at which the UE enters (or is expected to enter) the coverage period 1108.
[0089] For both implementations, the UE and the network should have the same understanding of whether the PTW can be shifted to align with or at least partially overlap a satellite coverage period and whether the PTW is shifted forward or backward relative to the original PTW timing. To ensure that the UE and the network apply the same PTW management logic, the base station may broadcast a PTW shift indication, for example in system information. The PTW shift indication may indicate whether a scheduled PTW may be shifted, and / or whether the shift is in a forward direction in time or in a backward direction in time. In an example implementation, the absence of an explicit PTW shift indication signals a default UE behavior, which may include applying the originally configured PTW, or applying a forward shift in time to the PTW when applicable.
[0090] Fig.12 As mentioned above Fig.11Message passing diagram for the discussed example scenario in which the UE 102 and one or more network nodes align PTW timing with a time period when the UE 102 has satellite coverage. The UE 102 initially operates 1201 in an RRC_CONNECTED state, e.g., the UE is connected to the BS 104 via a serving link provided by the satellite 304. Initially, the UE 102 transmits 1202 a NAS message such as an ATTACH REQUEST or TAU REQUEST to the BS 104, and then the BS 104 forwards 1204 the ATTACH REQUEST or TAU REQUEST message to the MME 112. The UE 102 may provide preferred values for DRX and eDRX parameters in the ATTACH REQUEST or TAU REQUEST message, and the MME 112 selects values for these parameters and indicates 1206 these values in the ATTACH ACCEPT or TAU ACCEPT message. When the BS 104 forwards 1204 the ATTACH REQUEST or TAU REQUEST message to the MME 112, the BS 104 may also provide the MME 112 with the location / position information of the UE 102. The UE 102 may send its location / position information to the BS 104 during an initial access procedure or during a measurement reporting procedure (not shown). In response to the ATTACH REQUEST or TAU REQUEST message from the UE 102, the MME sends 1206 an ATTACH ACCEPT or TAU ACCEPT message to the BS 104, and then the BS 104 forwards 1208 the ATTACH ACCEPT or TAU ACCEPT message to the UE 102.
[0091] In this scenario, MME 112 also includes a PTW shift indication in the ATTACH ACCEPT or TAU ACCEPT message, which indicates that if UE 102 is not in the coverage of any satellite during the scheduled PTW, UE 102 should shift the PTW. In this example, the PTW shift indication corresponds to shifting forward in time by default.
[0092] At some time after receiving the ATTACH ACCEPT or TAU ACCEPT message, the UE 102 transitions 1210 to the RRC_IDLE state. In some implementations, the UE 102 starts an inactivity timer, and after receiving the ATTACH ACCEPT or TAU ACCEPT message, the UE 102 transitions 1210 to the RRC_IDLE state in response to expiration of the inactivity timer. In other implementations, after receiving the ATTACH ACCEPT or TAU ACCEPT message, the UE receives an RRC Connection Release message from the BS 104 via the satellite 304, and in response, transitions 1210 to the RRC_IDLE state.
[0093] Later, the UE 102 in the RRC_IDLE state is no longer within the service area of the satellite 304 because the satellite 304 has moved 1212 to a new location and is no longer able to provide coverage for the UE 102. In some implementations, the UE 102 can estimate / predict the time when the satellite 304 will no longer provide coverage for the UE 102, and the time when the upcoming satellite (in this example, the satellite 306) begins to provide coverage for the UE 102. During the period between these two times, the UE 102 deactivates 1214 its AS function and / or its radio module to save power. Then, when the satellite 306 begins 1222 to provide service for the area, the UE 102 activates 1220 its AS function and / or its radio module again. If the PTW occurs during the period when the UE 102 has deactivated the AS function and / or the radio module, the UE 102 avoids 1216 monitoring the original PTW. In other words, the UE 102 skips 1216 the PTW and continues to operate in sleep mode.
[0094] Further, in Fig.12 In an example scenario, MME 112 receives an MT call for UE 102 before or during a scheduled PTW. MME 112 determines that UE 102 is not within coverage of any satellite based on UE location / positioning information and satellite ephemeris information, and therefore determines not to page 1218 UE 102.
[0095] After the satellite 306 begins 1222 serving the area, the UE 102 also begins 1224 monitoring for paging during a modified PTW having the same duration as the originally scheduled PTW, but with a different start time. Since the MT event for the UE 102 is still pending in this scenario, the MME 112 sends 1226 a paging message to the eNB 106 over the S1-MME interface, and the eNB 106 then informs 1228 the UE 102 of the scheduling of the paging message over the PDCCH using a paging radio network temporary identifier (P-RNTI). The eNB 106 then broadcasts 1230 a paging message with the identity of the UE 102 (i.e., S-TMSI or IMSI) over the PDSCH at the scheduled time and frequency resources.
[0096] UE 102 receives the paging message including the identity of the UE and attempts to establish an RRC connection by initiating 1232 a random access (RA) procedure with eNB 106. After the RA procedure, UE 102 transmits 1234 an RRC Connection Request message to eNB 106, and then eNB 106 responds 1236 with an RRC Connection Setup message. Upon receiving the RRC Connection Setup message, UE 102 transitions to an RRC_CONNECTED state and transmits 1238 an RRC Connection Setup Complete message including an ATTACH REQUEST (NAS message) to eNB 106. eNB 106 then transmits 1240 an Initial UE Message in response to the paging message from MME 112, wherein the Initial UE Message includes an ATTACH REQUEST (NAS message) from UE 102.
[0097] Fig.13 is a flow chart of an example method 1300 implemented by UE 102 or another suitable UE for determining whether to shift a PTW and by how much. According to the method, a modified PTW has the same duration as an originally configured PTW but is shifted forward or backward in time relative to the originally configured PTW.
[0098] At box 1302, the UE operates 1201 using an RRC connection established between the UE and an eNB operating in the NTN, and sends 1202 an ATTACH REQUEST or TAU REQUEST message containing a preferred eDRX configuration to the MME. At box 1304, the UE receives 1208 an ATTACH ACCEPT or TAU ACCEPT message from the network including a confirmed eDRX configuration and a PTW shift indication. At box 1306, the UE transitions 1210 to the RRC_IDLE state and applies the eDRX configuration so that the network can contact the UE via paging during certain periodically occurring time windows. When the UE is able to estimate the discontinuous coverage pattern using NTN cell-related assistance information or satellite-related assistance information, at box 1308, the UE deactivates 1214 its AS function and / or its radio module when it leaves the coverage of the current satellite at box 1308 (due to satellite movement). At block 1310, the UE determines that it has entered the coverage area of the next satellite and reactivates 1220 the AS functionality and / or its radio module to perform necessary idle mode operations, such as taking measurements and evaluating cell reselection criteria.
[0099] At block 1312, the UE determines whether shifting of the PTW is allowed. When the PTW shift indication received in block 1304 or the UE's default configuration indicates that the UE should shift the PTW to a later timing whenever the UE is not within the coverage of any satellite within the scheduled PTW, the flow follows the "yes" branch. At block 1314, the UE determines whether it has skipped any PTWs when the UE's AS function and / or its radio module is inactive. If the UE has skipped at least one PTW, the flow proceeds to block 1318 to monitor 1224 paging during a modified PTW, which may be a time interval having a duration equal to the duration of the originally configured PTW. However, if the UE has not skipped any PTW, the flow proceeds to block 1316, where the UE determines whether there are or will be any instances of PTWs during the period when the UE has activated its AS function and / or radio module. If such a PTW exists, the flow proceeds to block 1318. Otherwise, the flow returns to block 1308, where the UE may deactivate its AS functionality and / or radio module when leaving the coverage of the current satellite. In at least some of the implementations, after the UE completes monitoring for paging at block 1318, if the UE determines that the network has not paged the UE, the UE deactivates its AS functionality and / or radio module (e.g., by returning to block 1308).
[0100] Referring again to block 1312, when the PTW shift indication received in block 1304 or the UE's default behavior indicates that the UE should not shift the PTW, the flow proceeds to block 1320, similar to block 1316, where the UE only needs to check whether there are or will be any instances of a PTW during the period when the UE turns on its AS and / or radio module. If such a PTW exists, the flow proceeds to block 1322, and similar to block 1318, the UE monitors for paging during the PTW. Otherwise, the flow returns to block 1308. In at least some of the implementations, after the UE completes monitoring for paging at block 1322, if the UE determines that the network has not yet paged the UE, the UE deactivates its AS functionality and / or radio module (e.g., by returning to block 1308).
[0101] Reference now Fig.14 In this scenario, the UE and the NTN modify the PTW by extending it so as to overlap with the satellite coverage period, and the UE can therefore receive paging messages during the modified PTW. Fig.15 The message passing diagram and Fig.16 The flow chart further discusses this approach.
[0102] The UE wakes up and monitors for paging during the first initially configured PTW 1402. However, since the UE is not within the coverage area of any satellite during the entire PTW 1402, the UE extends the PTW by an extended period 1404 so that the extended PTW 1404 can overlap with the coverage period 1412, at which time the UE can receive a paging message from the second satellite. When at least one of the UE's paging occasions (POs) is within the coverage period 1412, the UE stops the extended PTW. If the UE has a pending MT event, the network (i.e., MME) can start paging the UE from the earliest PO that falls within the satellite coverage period 1412. Similarly, the UE wakes up and monitors for paging during the second initially configured PTW 1406. Since the UE is not within the coverage area of any satellite during the entire PTW 1406, the UE extends the PTW by an extended period 1408. When at least one of the UE's POs is within the coverage period 1414, the UE stops the extended PTW. If the UE has a pending MT event, the network may start paging the UE from the earliest PO that falls within the satellite coverage period 1414.
[0103] To ensure that the UE and the network apply the same PTW extension logic, the base station may broadcast an indication in the system information indicating whether the scheduled PTW may be extended. Depending on the implementation, the presence of the PTW extension indication may signal that the UE is allowed to extend the originally configured PTW, or conversely, the presence of the PTW extension indication may signal that the UE is not allowed to extend the originally configured PTW.
[0104] Fig.15 As mentioned above Fig.14 1500 in which UE 102 and one or more network nodes extend PTW timing. Events 1501-1512 are generally similar to Fig.12 1201 - 1212 of EMBODIMENT 1, except that here, MME 112 generates 1506 and BS 104 forwards 1508 a PTW extension indication instead of a PTW shift indication to modify the PTW.
[0105] In this scenario, UE 102 may not be aware that no satellite coverage is available during the initially configured PTW (as opposed to Fig.12 , where the UE can use NTN cell-related assistance information or satellite-related assistance information to estimate the non-coverage period and remain in sleep mode). Therefore, the UE wakes up and monitors paging 1515 from the start of the originally configured (or "scheduled") PTW, but cannot receive PDCCH or other DL signaling because the UE is not in the coverage area of any satellite during the entire originally configured PTW.
[0106] However, in this implementation, MME 112 may use the location / positioning information of UE 102 and satellite ephemeris information to determine that UE 102 is not within the coverage area of any satellite and therefore avoid paging 1518 UE 102 even if there is a pending MT event.
[0107] After the originally configured PTW ends, UE 102 extends the PTW and continues 1517 to monitor for paging. Shortly after the initiation of the extended PTW, another satellite 306 moves in and begins 1522 to serve the geographic area where UE 102 is currently located. When there is a pending MT event associated with UE 102, MME 112 can determine that UE 102 now has NTN coverage. MME 112 therefore begins paging UE 102. Events 1526-1540 are similar to events 1226-1240 discussed above.
[0108] Fig.16 1600 is a flow chart of an example method 1600 that can be implemented by UE 102 or another suitable UE. The UE may not be able to estimate / predict the discontinuous coverage pattern; however, the UE may use this method to extend the PTW. According to this method, the modified PTW may start at the same time as the originally configured PTW, but not end at the same time as the originally configured PTW.
[0109] Method 1600 starts at block 1602, which is similar to block 1302 in method 1300 discussed above. Block 1605 is generally similar to block 1304, except that the network provides a PTW extension indication instead of a PTW shift indication to instruct the UE to modify the PTW. Following block 1606, which is similar to block 1306, the UE starts monitoring paging at the start of the next scheduled PTW at block 1609.
[0110] In block 1609, the UE wakes up from the start time of the originally configured PTW and starts monitoring paging. If the UE has not received a PDCCH signal addressed to the UE with the P-RNTI at the end of the originally configured PTW, the UE determines at block 1630 whether the UE is allowed to extend the PTW.
[0111] If the PTW extension indication received in block 1604 or the default UE configuration indicates that the UE should extend the PTW if the UE is not within the coverage of any satellite in the scheduled PTW, the process proceeds to block 1632 to determine whether the UE currently has NTN coverage. If the UE currently has NTN coverage and the UE does not detect a paging message during any of the POs in the PO, the UE stops monitoring for paging after the current PTW is completed (block 1634). However, when the UE does not have NTN coverage, or when the UE remains out of the NTN coverage area in at least one of the POs for a sufficiently long time, the UE extends the current PTW until the UE has stayed within the NTN coverage period in at least one of the POs (block 1636).
[0112] On the other hand, if the PTW extension indication or the default UE configuration received in block 1604 indicates that the UE cannot extend the originally configured PTW, flow proceeds from block 1630 to block 1634 and the UE stops monitoring paging when the current PTW ends.
[0113] For example, if the network does not page the UE because there is no pending MT event, the UE continues to operate in RRC_IDLE after executing block 1634 or block 1636. Therefore, the flow may return to block 1609, and the UE may remain in RRC_IDLE and wait for the start of the next PTW.
[0114] Next, Fig.17 A method by which the UE and the network dynamically determine the PTW is shown. Fig.18 The message passing diagram and Fig.19 The flowcharts further discuss these techniques.
[0115] In this scenario, the UE operates in the RRC_CONNECTED state within the coverage period 1702 of the first satellite. The UE then receives an RRC Connection Release 1704 message from the base station and thus transitions to RRC_IDLE. The RRC Connection Release message 1704 or a NAS message encapsulated by the RRC Connection Release message contains a "next PTW" indication that specifies the start time and duration of the first PTW (in this case, PTW 1708). In order to align the first PTW 1708 with the upcoming satellite's coverage period 1706, the network (e.g., MME 112) can determine the UE's location so that the network can calculate the start time and duration of the first PTW 1708 with sufficient accuracy. In another implementation, the network determines and assigns the UE an earlier start time and longer duration of the first PTW 1708 to ensure that the first PTW 1708 will still substantially coincide with the coverage period 1706, shifted forward or backward in time due to the potential range of movement of the UE.
[0116] Based on the 'next PTW' indication included in the RRC connection release message, the UE wakes up and monitors for paging during the first PTW 1708. The UE may receive a paging message during the first PTW 1708, and the paging message may contain another 'next PTW' indication for the UE. If the UE determines that the paging is not for a pending MT event, the UE resumes sleep mode and wakes up within the next PTW 1712, which is configured by the paging message using the 'next PTW' indication. However, if the UE receives a paging message during the first PTW 1708, and the paging message specifies the identity of the UE but does not contain another 'next PTW' indication, the UE may determine that the paging is related to a pending MT event. In this case, the UE continues to establish an RRC connection with the base station.
[0117] Fig.18 As mentioned above Fig.17 1800 of the example scenario discussed, in which the UE 102 and one or more network nodes dynamically determine the timing of the next PTW. Events 1801-1812 are generally similar to Fig.12 Events 1201-1212 and Fig.15 Events 1501-1512 of BS 104 are described above, except that here, BS 104 transmits 1809 a command for releasing the RRC connection (eg, an RRC Connection Release Command), which includes a "next PTW" indication.
[0118] Specifically, the RRC connection release message or the NAS message included in the RRC connection release message contains a "next PTW" indication that specifies the start time and duration of the first PTW during which the UE 102 wakes up and monitors paging. The start time can be in the form of an absolute time (e.g., coordinated universal time), or in the form of a hyperframe number (HFN) or a system frame number (SFN).
[0119] Based on the "next PTW" indication received in the RRC Connection Release message, UE 102 wakes up within the first PTW and monitors 1825 for paging. MME 112 also pages the UE based on the next PTW indication. Events 1826, 1828, and 1830 are similar to those in reference Fig.12 The discussed events 1226, 1228, and 1230 are similar, but if no MT events are associated with the paging message, the paging message broadcast 1830 by the eNB 106 includes another "next PTW" indication for the UE to specify the start time and duration of the second PTW. The satellite 306 then leaves the coverage area.
[0120] Based on the "next PTW" indication received in the paging message during the first PTW, the UE 102 wakes up at the second PTW and monitors for paging 1858. At this point, the satellite 304 begins to provide service 1852 for the geographic area. The MME 112 may again send 1856 a paging message to the UE 102 via the BS 104 during the second PTW. After receiving the paging message from the MME 112, the BS 104 notifies 1862 the UE 102 of the scheduling of the paging message via a PDCCH addressed to the UE using the P-RNTI. The BS 104 then broadcasts 1864 the paging message over the PDSCH at the scheduled time and frequency resources, and the paging message associated with the MT event may contain the identity of the UE 102 (i.e., S-TMSI or IMSI). Events 1832-1840 are similar to events 1232-1240 discussed above.
[0121] Fig.19 is a flow chart of an example method 1900 for determining a start time of a dynamic PTW that may be implemented in UE 102 or another suitable UE. The UE may not be able to estimate / predict the discontinuous coverage pattern.
[0122] The method 1900 starts at block 1902 when the UE operates 1801 in RRC_CONNECTED and sends 1802 an ATTACH REQUEST or TAU REQUEST message including a preferred eDRX configuration to the network (e.g., MME). At block 1904, the UE receives 1808 an ATTACH ACCEPT or TAU ACCEPT message containing a confirmed eDRX configuration. At block 1906, the UE receives 1809 an RRC connection release message from the base station and transitions 1810 to the RRC_IDLE state. The RRC connection release message contains a "next PTW" indication that specifies when and how long the UE should wake up and monitor for paging.
[0123] The UE wakes up according to the "next PTW" indication received in the RRC connection release message and monitors 1825 paging at the specified time (block 1908). At block 1910, before the PTW is completed, the UE receives 1828, 1830 paging messages from the base station.
[0124] At box 1912, the UE determines whether the paging is related to a pending MT event. If the paging message contains a "next PTW" indication and references the identity of the UE, the UE determines that the network is not paging the UE at this time, and the process continues to box 1916, where the UE stores the PTW configuration included in the "next PTW" indication. The UE then remains in the RRC_IDLE state and the process returns to box 1908. On the other hand, if the paging message contains the identity of the UE but does not contain a "next PTW" indication, the UE determines that the network is paging the UE regarding an MT event. In this case, the process continues to box 1914, and the UE attempts to connect to the base station by initiating 1832 the RA process. The UE transitions to the RRC_CONNECTED state, and the process returns to box 1902.
[0125] Fig. 20 Shown is a method for solving the Figure 7 Another technique to solve the problem discussed. According to this method, the UE and the network align the eDRX cycle with the periodicity of a certain satellite return to the geographical area. In this way, the UE and the network can control the paging delay within a reasonable / acceptable range. Fig. 20In the scenario of FIG. 2 , the UE wakes up and monitors for paging during the first PTW 2002, where the start of PTW 2002 is aligned with the coverage period 2008 of the first satellite c1. If the network does not page the UE during PTW 2002, the next time the UE wakes up and monitors for paging is at the start of the second PTW 2004, which is also the time when the UE enters the coverage area provided by the first satellite again. Therefore, the interval between two consecutive PTWs (i.e., the length of the eDRX cycle) is configured to be equal to the interval between two consecutive coverage periods of the first satellite. This approach does not depend on the coverage provided by other satellites (e.g., c2 2014, c2 2016, c3 2018, and c4 2020). In this implementation, the UE does not need to wake up during these non-c1 coverage periods.
[0126] Since the 3GPP TS 24.008 specification (v17.5.0) only allows the network to use 4 bits to configure the eDRX cycle length (i.e., only 16 values are possible), and the time required for the satellite to travel to the same position can be any arbitrary value, the network may need more bits to signal / configure the eDRX cycle length with arbitrary values, ranging from a few seconds to tens of thousands of seconds. Therefore, the 'Extended DRX Parameters IE' in the ATTACH REQUEST, ATTACH ACCEPT, TAU REQUEST, and TAU ACCEPT messages needs to be extended so that the network can use more bits (e.g., 17 bits) to configure the eDRX cycle length.
[0127] Fig.21 21 is a flow chart of an example method 2100 for paging a UE via an NTN using a modification of an initial PTW configuration. At optional block 2102, a network device configures the UE to have a PTW. In some implementations, the configuration also explicitly indicates the duration of a sleep period that the UE enters after the PTW for operating in a low-power sleep mode. In other implementations, the UE stores a default configuration of the PTW and / or sleep period.
[0128] At block 2104, the network device provides an indication that if the UE lacks NTN coverage during the PTW, the UE will modify the PTW. The indication may be, for example, a PTW shift indication or a PTW extension indication. Depending on the implementation, the indication may be a binary flag or a data structure with additional information, such as whether the shift is forward or backward in time. At block 2106, the network device modifies the PTW to match the UE operation. Finally, at block 2108, the network device pages the UE during the modified PTW.
[0129] Fig. 2222 is a flow chart of an example method 2200 for paging a UE via an NTN using a dynamic "next PTW" indication. At block 2202, a network device transmits a first PTW indication specifying a first PTW to a UE operating in a connected state (e.g., RRC_CONNECTED). At block 2204, during the first PTW, the network device transmits a second PTW indication specifying a second PTW to the UE. During the first PTW, the UE operates in a non-connected state (e.g., RRC_IDLE).
[0130] Fig.23 23 is a flow chart of an example method 2300 for paging a UE via an NTN using alignment of a PTW with satellite coverage periodicity. The method 2300 begins at block 2302, where a network device determines the periodicity of coverage periods during which a certain satellite S provides coverage for a UE. As described above, the coverage periods are separated by time intervals during which the satellite does not provide coverage for the UE. At block 2304, the network device generates a configuration of a paging cycle with a PTW and, in some cases, sleep periods (which may be explicitly or implicitly indicated, depending on the implementation). The network selects a duration period such that the PTW is partially or completely aligned with the coverage period of the satellite S. At block 2306, the network device transmits the configuration to the UE.
[0131] The following description may be applicable to the above description.
[0132] In general, the description of any one of the above figures may apply to another of the above figures. Any of the above events or boxes may be optional. For example, an event or box with a dashed line may be optional. In some implementations, "message" is used, and "message" may be replaced with "information element (IE)", and vice versa. In some implementations, "IE" is used and "IE" may be replaced with "field", and vice versa. In some implementations, "configuration" or "configuration parameter" may be replaced with "configuration", and vice versa. "eNB" may be replaced with "base station", "gNB", "6G base station", "evolved gNB" or 6G gNB. The "ATTACH REQUEST" message and the "ATTACH ACCEPT" message may be replaced with the "REGISTRATION REQUEST" message and the "REGISTRATION ACCEPT" message, respectively. "MME" may be replaced with AMF or evolved AMF or 6G AMF. "RRC connection release message" may be replaced with "RRC release message".
[0133] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit or an advanced driver assistance system (ADAS) of a vehicle. Still further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0134] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code or machine-readable instruction stored on a non-temporary machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system (circuitry) or logic that is permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.). A hardware module may also include programmable logic or circuit systems (e.g., as contained in a general-purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. The decision to implement a hardware module with a dedicated and permanently configured circuit system or with a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.
[0135] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.
[0136] In preparation for the 3GPP TSG-RAN WG2 Meeting #118-e held on May 9-20, the inventors are prepared to discuss and adopt standards, methods and devices for improving assistance information for predicting discontinuous coverage. Given that the UE needs to predict the coverage of two types of satellites (quasi-Earth fixed cells and Earth mobile cells), the embodiments described below achieve a clear mapping between the content of the assistance information and the type of satellite, provide missing information fragments and prevent the network from broadcasting redundant information.
[0137] In some embodiments, to assist UEs in predicting the coverage of quasi-geo-fixed cells, the network provides satellite coverage area reference positions and coverage radius of quasi-geo-fixed cells. Each UE can then perform some simple calculations based on the received information and its GNSS coordinates to determine whether it will be within the coverage of an incoming satellite.
[0138] Since not every satellite projects its beam vertically onto the earth, in some embodiments, the eNB provides additional information such as the antenna panel tilt angle to facilitate the UE to determine the center position of the earth mobile cell. Therefore, in order to assist the UE in predicting the coverage of the earth mobile cell, in addition to the mean / average ephemeris information, the network also provides the antenna panel tilt angle and the coverage radius of both the serving cell and the incoming cell.
[0139] Since the set of information used to predict coverage of geo-mobile cells is different from the set of information used to predict coverage of quasi-geo-fixed cells, in some embodiments, the SatelliteInfo-r17 information element IE contains two IEs under the CHOICE structure. One IE contains auxiliary information for predicting geo-mobile cells, and the other IE contains auxiliary information for predicting quasi-geo-fixed cells. In this way, the possibility of having redundant information in SIB32 is eliminated. In addition, since different UEs may have different preferences for staying on a certain type of satellite (e.g., geo-mobile vs. quasi-geo-fixed), and this preference may be affected by the way the UE is implemented, the PLMN selected by the UE, and the type of cell in which the UE is currently camped, having two separate IEs representing the two cell types in SatelliteInfo-r17 makes it easier for the UE implementation to pick / filter the information it needs to predict satellite coverage.
[0140] One implementation of these features is as follows:
[0141] According to a first example, a method performed by a UE for monitoring paging from an NTN includes: receiving a configuration of a paging time window (PTW) from the NTN, during which the UE operating in a non-connected state monitors paging messages, and entering a sleep period after the PTW, during which the UE operates in a low-power sleep mode. The method further includes: determining that the UE lacks NTN coverage during the PTW, and modifying the PTW in response to the determination to generate a modified PTW.
[0142] The modification may include adjusting the start time of the PTW so that the UE has network coverage during the modified PTW. The method may further include receiving a PTW shift indication from the NTN, the PTW shift indication being used to indicate that the UE is allowed to modify the PTW. The PTW shift indication may indicate whether the PTW is shifted forward in time or backward in time relative to the time in the received configuration.
[0143] The method may further include determining one or more coverage time intervals within the sleep period in which the UE has network coverage, and the adjustment of the start time may include shifting the PTW to overlap at least one of the one or more coverage time intervals.
[0144] In one embodiment, determining the one or more coverage time intervals includes receiving, from the NTN, assistance information related to properties of cells projected onto the surface of the Earth by non-geosynchronous orbit (NGSO) satellites operating in the NTN and providing quasi-Earth fixed service links. In another embodiment, determining the one or more coverage time intervals includes receiving, from the NTN, assistance information related to properties of NGSO satellites operating in the NTN and providing Earth mobile service links.
[0145] The modification may include adjusting the end time of the PTW without adjusting the start time of the PTW to configure the modified PTW to extend the duration of the PTW by an extended period so that the UE has network coverage during the extended period. In this case, the method may further include receiving a PTW extension indication from the NTN, the PTW extension indication being used to indicate that the UE is allowed to extend the PTW. The method may also include terminating the PTW in response to receiving a paging message during a paging opportunity within the extended period or in response to expiration of a timer activated when adjusting the end time of the PTW.
[0146] The method may further include transmitting the preferred eDRX configuration to the NTN.The receiving of the configuration of the PTW may include receiving an initial eDRX configuration.
[0147] According to a second example, a method performed by a UE for monitoring paging from an NTN includes: (i) receiving a first PTW indication specifying a first PTW from the NTN when the UE is in a connected state, during which the UE operating in a non-connected state monitors paging messages, and (ii) during the PTW, receiving, by one or more processors, a second PTW indication specifying a second PTW.
[0148] The receiving of the first PTW indication may include receiving a command for releasing the radio connection. The receiving of the second PTW indication may include receiving a paging message. The method may further include determining that no mobile terminated (MT) event is to be delivered to the UE and the UE will continue to operate in a non-connected state based on the presence of the second PTW indication, and there is no PTW indication in the paging message indicating that the UE will transition to a connected state. The non-connected state may be RRC_IDLE or RRC_INACTIVE. The method may also include receiving an initial eDRX configuration from the NTN.
[0149] According to an embodiment, a UE having one or more processors is configured to implement the above-mentioned first and second example methods and their variants.
[0150] According to a third example, there is a method of paging a user equipment (UE) configured with a PTW via an NTN, during which the UE operating in a non-connected state monitors paging messages and enters a sleep period after the PTW, during which the UE operates in a low-power sleep mode. The method implemented in a network device includes: (i) providing the following indication to the UE: if the UE lacks NTN coverage during the PTW, the UE will modify the PTW; (ii) modifying the PTW to generate a modified PTW; and (iii) paging during the modified PTW. The modification may include adjusting the start time of the PTW so that the UE has network coverage during the modified PTW.
[0151] In one embodiment, providing the indication includes providing a PTW shift indication, the PTW shift indication is used to indicate that the UE is allowed to modify the PTW. In another embodiment, providing the indication includes providing a PTW shift indication to indicate whether the PTW is shifted forward or backward in time relative to the time in the initial configuration.
[0152] The method may further include determining one or more coverage time intervals within the sleep period when the UE has network coverage, and then adjusting the start time includes shifting the PTW to overlap at least one of the one or more coverage time intervals.
[0153] The method may further include transmitting to the UE assistance information related to properties of a cell projected onto the surface of the Earth via a non-geosynchronous orbit (NGSO) satellite operating in the NTN and providing a quasi-Earth fixed service link. The method may alternatively include transmitting to the UE assistance information related to properties of a NGSO satellite operating in the NTN and providing an Earth mobile service link.
[0154] The modification may include adjusting the end time of the PTW without adjusting the start time of the PTW to configure the modified PTW to extend the duration of the PTW by an extended period so that the UE has network coverage during the extended period. Then, the method may further include transmitting a PTW extension indication to the UE, the PTW extension indication being used to indicate that the UE is allowed to extend the PTW.
[0155] The method may further comprise receiving a preferred eDRX configuration from the UE.Alternatively or additionally, the method may comprise transmitting an initial eDRX configuration comprising the PTW to the UE.
[0156] According to a fourth example, a method for paging a UE via an NTN, performed by a network device, includes: (i) when the UE is in a connected state, transmitting a first PTW indication specifying a first PTW to the UE, during which the UE operating in a non-connected state monitors paging messages, and (ii) during the PTW, transmitting, by one or more processors, a second PTW indication specifying a second PTW to the UE.
[0157] The transmission of the first PTW indication may include transmitting a command for releasing the radio connection. The transmission of the second PTW indication may include transmitting a paging message. The transmission of the second PTW indication together with the paging message may be in response to determining that there is no mobile terminated (MT) event to be delivered to the UE and that the UE will continue to operate in a non-connected state.
[0158] According to a fifth example, a method for paging a UE via an NTN performed by a network device includes determining a periodicity of a coverage period during which a certain satellite provides coverage for the UE, the coverage period being separated by a time interval during which the satellite does not provide coverage for the UE. The method further includes generating, by one or more processors, a configuration of a paging cycle, including selecting a duration of the paging cycle based on the periodicity of the coverage period, the paging cycle including: (i) a PTW during which the UE operating in a non-connected state monitors for paging messages, and (ii) a sleep period during which the UE operates in a sleep mode. The method also includes: transmitting the configuration to the UE.
[0159] The method may further comprise configuring the duration of the paging cycle to be equal to the periodicity of the coverage period. The configuration may be an eDRX configuration.
[0160] According to an embodiment, a network device having one or more processors is configured to implement any one of the third example method, the fourth example method, and the fifth example method described above, and variations thereof.
Claims
1. A method (1300, 1600) performed by a user equipment (102) UE for monitoring paging from a non-terrestrial network NTN, the method comprising: receiving (1304, 1605) an indication for the UE to monitor a paging message from the NTN during a paging time window PTW when operating in a non-connected state; as well as The PTW is modified (1318, 1636) based on at least one NTN coverage time interval during which the UE has NTN coverage.
2. The method according to claim 1, wherein: The modifications include: Assistance information is received related to properties of an NTN cell projected onto the surface of the earth from a non-geosynchronous orbit NGSO satellite providing a quasi-geofixed service link during the at least one NTN coverage time interval.
3. The method according to claim 1, wherein: The modifications include: Assistance information related to properties of a non-geosynchronous orbit (NGSO) satellite providing a geomobile service link during the at least one NTN coverage time interval is received.
4. The method according to claim 1, wherein: The receiving of the indication comprises: Receive extended discontinuous reception (eDRX) configuration.
5. The method according to claim 4, further comprising: Transmission prefers eDRX configuration.
6. The method according to any one of claims 4 or 5, further comprising: A PTW shift indication is received indicating that the UE is allowed to shift the PTW.
7. The method according to any one of claims 1 to 6, wherein: The receiving of the indication occurs when the UE operates in a connected state, the method further comprising: Switch to the non-connected state.
8. The method according to any one of claims 1 to 7, wherein: The modifications include: The PTW is extended to cover the at least one NTN coverage time interval in which the UE has NTN coverage.
9. The method according to any one of claims 1 to 8, further comprising: receiving a paging message during the PTW; as well as If the paging message is related to a mobile terminated event, then a switch is made to the connected state.
10. The method according to claim 1, further comprising: During the PTW, a PTW indication is received that specifies a second PTW.
11. A user equipment comprising a processor, a transmitter and a receiver, the user equipment being configured to implement the method according to any one of claims 1 to 10.
12. A method (2100) performed by a network device (104, 106) for paging a user equipment (102) UE via a non-terrestrial network (NTN), the UE being configured with a paging time window PTW, during which the UE operating in a non-connected state monitors a paging message, the method comprising: providing (2104) to the UE an indication that the UE is allowed to modify the PTW; and The UE is paged (2108) during the PTW.
13. The method according to claim 12, further comprising: Assistance information related to properties of an NTN cell projected onto the surface of the earth from a non-geosynchronous orbit NGSO satellite providing a quasi-geo-fixed service link is transmitted to the UE.
14. The method according to claim 12, further comprising: Auxiliary information related to properties of a non-geosynchronous orbit (NGSO) satellite providing a geomobile service link is transmitted to the UE.
15. The method according to any one of claims 12 to 14, wherein: The paging includes: A PTW indication specifying a second PTW is transmitted to the UE during the PTW.
16. A network device comprising a processor, a transmitter and a receiver, the network device being configured to implement the method according to any one of claims 12-15.
