Apparatus, method and computer program

Abstract

An apparatus comprises means for monitoring an uplink transmission from a communication device to determine whether a frequency and / or timing of the uplink transmission is as expected, and means for scheduling a position acquisition gap for the communication device when the frequency and / or timing of the uplink transmission is not as expected.

Description

Technical Field

[0001] The present disclosure relates to apparatus, methods and computer programs, and particularly, but not exclusively, to apparatus, methods and computer programs related to position acquisition. Background Art

[0002] A communication system may be viewed as a facility that enables communication sessions between two or more entities (such as communication devices, base stations, and / or other nodes) by providing carrier waves between the various entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards (such as those provided by 3GPP), satellite-based communication systems, and different wireless local area networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.

[0004] Communication systems and related equipment typically operate according to a given standard or specification that specifies what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters that should be used for the connection are also typically defined. An example of a standard is the so-called 5G standard. Summary of the invention

[0005] According to one aspect, an apparatus is provided, comprising: a component for monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of the uplink transmissions are as expected; and a component for obtaining gaps for a communication device scheduling position when the frequency and / or timing of the uplink transmissions are not as expected.

[0006] The apparatus may include means for causing a message to be sent to the communication device, the message including information regarding the scheduled position acquisition slot.

[0007] The component for monitoring uplink transmissions from the communication device determines that the frequency and / or timing of the uplink transmissions is not as expected when the frequency and / or timing of the uplink transmissions differs from an expected frequency and / or timing for the uplink transmissions by more than a threshold amount.

[0008] The apparatus may include means for causing a message to be sent to the communication device, the message indicating that the communication device is to cease uplink transmissions until the communication device has reacquired a valid position.

[0009] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0010] The apparatus may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The apparatus may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0011] According to another aspect, an apparatus is provided, comprising: a component for monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of the uplink transmissions are as expected; a component for determining that a location acquisition validity timer associated with the communication device is about to expire; and a component for causing a message to be sent to the communication device when it is determined that the frequency and / or timing of the uplink transmissions are as expected and when it is determined that the location acquisition validity timer associated with the communication device is about to expire, the message indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix.

[0012] The message may also include information indicating a new timing value for the location acquisition validity timer.

[0013] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0014] The apparatus may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The apparatus may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0015] According to another aspect, an apparatus is provided, the apparatus comprising: a component for receiving a message from a network device indicating that a location acquisition validity timer associated with a communication device is to be restarted without performing a location acquisition fix; and a component for restarting the location acquisition validity timer without performing a location acquisition fix.

[0016] The means for restarting the location acquisition validity timer may restart the validity timer with a different timing value compared to a previous timing value.

[0017] The apparatus may comprise means for causing information to be sent to the network device, the information indicating the timing value being used for the restarted validity timer.The different timing value may be greater than the previous timing value.

[0018] The apparatus may include means for determining different timing values ​​based on an elevation angle associated with a serving satellite of the non-terrestrial network.

[0019] The apparatus may comprise means for determining different timing values ​​based on a table of values ​​stored by the apparatus.

[0020] The apparatus may comprise means for determining a different timing value by incrementing a previous timing value by a fixed value to provide the different timing value.

[0021] The apparatus may include means for determining a different timing value by selecting a next value in a set of timing values.

[0022] Information about the different timing values ​​may be provided by the network device.

[0023] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0024] The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0025] According to another aspect, an apparatus is provided that includes means for receiving a message indicating scheduling of a location acquisition gap from a network device and means for performing a location acquisition fix in the location acquisition gap.

[0026] The apparatus may include means for discontinuing uplink communications with the network device until a valid position has been reacquired.

[0027] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0028] The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0029] According to one aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: monitor uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions are as expected; and acquire gaps for a communication device scheduling position when the frequency and / or timing of the uplink transmissions are not as expected.

[0030] The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least: cause a message to be sent to a communication device, the message comprising information regarding the scheduled position acquisition gap.

[0031] The at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to at least: determine that the frequency and / or timing of the uplink transmission is not as expected when the frequency and / or timing of the uplink transmission differs from the expected frequency and / or timing for the uplink transmission by more than a threshold amount.

[0032] The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least: cause a message to be sent to the communication device indicating that the communication device is to cease uplink transmission until the communication device has reacquired a valid position.

[0033] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0034] The apparatus may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The apparatus may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0035] According to one aspect, a device is provided, the device comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the device to at least: monitor uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions are as expected; determine that a location acquisition validity timer associated with the communication device is about to expire; and upon determining that the frequency and / or timing of the uplink transmissions are as expected and upon determining that the location acquisition validity timer associated with the communication device is about to expire, cause a message to be sent to the communication device, the message indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing location acquisition positioning.

[0036] The message may also include information indicating a new timing value for the location acquisition validity timer.

[0037] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0038] The apparatus may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The apparatus may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0039] According to one aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the apparatus to at least: receive a message from a network device indicating that a location acquisition validity timer associated with a communication device is to be restarted without performing location acquisition positioning; and restart the location acquisition validity timer without performing location acquisition positioning.

[0040] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: restart the validity timer using a different timing value than a previous timing value.

[0041] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: cause information to be sent to a network device, the information indicating a timing value being used for the restarted validity timer.

[0042] The different timing value may be greater than the previous timing value.

[0043] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determine different timing values ​​based on an elevation angle associated with a serving satellite of the non-terrestrial network.

[0044] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determine different timing values ​​based on a table of values ​​stored by the apparatus.

[0045] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determine a different timing value by incrementing a previous timing value by a fixed value to provide a different timing value.

[0046] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determine a different timing value by selecting a next value in a set of timing values.

[0047] Information about the different timing values ​​may be provided by the network device.

[0048] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0049] The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0050] According to one aspect, a device is provided, the device comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the device to at least: receive a message indicating scheduling of a location acquisition gap from a network device; and perform location acquisition positioning in the location acquisition gap.

[0051] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: cease uplink communications with the network apparatus until a valid position has been reacquired.

[0052] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0053] The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0054] According to one aspect, a method is provided, comprising: monitoring uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions is as expected; and when the frequency and / or timing of the uplink transmissions is not as expected, obtaining a gap for a communication device scheduling position.

[0055] The method may include causing a message to be sent to the communication device, the message including information regarding the scheduled position acquisition slot.

[0056] The method may include determining that the frequency and / or timing of the uplink transmission is not as expected when the frequency and / or timing of the uplink transmission differs from an expected frequency and / or timing for the uplink transmission by more than a threshold amount.

[0057] The method may include causing a message to be sent to the communication device indicating that the communication device is to cease uplink transmissions until the communication device has reacquired a valid position.

[0058] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0059] The method may be performed by a device. The device may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The device may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0060] According to another aspect, a method is provided, the method comprising: monitoring uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions are as expected; determining that a location acquisition validity timer associated with the communication device is about to expire; and when it is determined that the frequency and / or timing of the uplink transmissions are as expected, and when it is determined that the location acquisition validity timer associated with the communication device is about to expire, causing a message to be sent to the communication device, the message indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing location acquisition positioning.

[0061] The message may also include information indicating a new timing value for the location acquisition validity timer.

[0062] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0063] The method may be performed by a device. The device may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The device may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0064] According to another aspect, a method is provided that includes receiving a message from a network apparatus indicating that a location acquisition validity timer associated with a communication device is to be restarted without performing a location acquisition fix, and restarting the location acquisition validity timer without performing a location acquisition fix.

[0065] The method may include restarting the validity timer using a different timing value compared to a previous timing value.

[0066] The method may include causing information to be sent to the network device, the information indicating the timing value being used for the restarted validity timer.

[0067] The different timing value may be greater than the previous timing value.

[0068] The method may include determining different timing values ​​based on an elevation angle associated with a serving satellite of the non-terrestrial network.

[0069] The method may comprise determining the different timing values ​​based on a table of values ​​stored by the apparatus.

[0070] The method may include determining the different timing value by incrementing a previous timing value by a fixed value to provide the different timing value.

[0071] The method may include determining a different timing value by selecting a next value in a set of timing values.

[0072] Information about the different timing values ​​may be provided by the network device.

[0073] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0074] The method may be executed by an apparatus. The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0075] According to another aspect, a method is provided, the method comprising: receiving a message indicating a schedule for a location acquisition gap from a network device; and performing a location acquisition fix in the location acquisition gap.

[0076] The method may include ceasing uplink communications with the network device until a valid position has been reacquired.

[0077] Position acquisition may be performed through a global navigation satellite process, a network-based position process, or a network-verified position process.

[0078] The method may be executed by an apparatus. The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0079] According to one aspect, a computer-readable medium is provided, the computer-readable medium including program instructions stored thereon, the program instructions being used to execute at least one of the above methods.

[0080] According to one aspect, a non-transitory computer-readable medium having stored thereon program instructions for executing at least one of the above methods is provided.

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

[0082] In another aspect, there is provided a computer program embodied on a non-transitory computer readable storage medium, the computer program comprising program code for providing any one of the above methods.

[0083] In another aspect, there is provided a computer program product for a computer, the computer program product comprising software code portions for performing the steps of any one of the preceding methods when said product is run.

[0084] A computer program may be provided, the computer program comprising program code means adapted to perform the method(s).The computer program may be stored and / or implemented in another way by means of a carrier medium.

[0085] In the above, many different aspects have been described. It should be understood that other aspects can be provided by combining any two or more of the above aspects.

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

[0087] List of abbreviations

[0088] AF Application Function

[0089] AMF Access and Mobility Management Function

[0090] AUSF authentication server function

[0091] BS Base Station

[0092] CE control components

[0093] CIoT Cellular Internet of Things

[0094] CU Centralized Unit

[0095] DCI Downlink Control Information

[0096] DN Data Network

[0097] DU Distributed Unit

[0098] eMTC Enhanced Machine Type Communication

[0099] GEO Earth is stationary

[0100] gNB gNodeB

[0101] GNSS Global Navigation Satellite System

[0102] HARQ Hybrid Automatic Repeat Request

[0103] IoT

[0104] LEO Low Earth Orbit

[0105] LTE Long Term Evolution

[0106] MAC Media Access Control

[0107] MS Mobile Station

[0108] MTC Machine Type Communication

[0109] NB-IoT Narrowband Internet of Things

[0110] NEF Network Exposure Function

[0111] NF Network Function

[0112] NR New Radio

[0113] NRF Network Repository Features

[0114] NTN Non-Terrestrial Network

[0115] PSS Primary Synchronization Signal

[0116] RAM Random Access Memory

[0117] (R)AN (Radio) Access Network

[0118] ROM Read Only Memory

[0119] RRC Radio Resource Control

[0120] SMF session management functions

[0121] SSS Secondary synchronization signal

[0122] TA Timing Advance

[0123] TN Terrestrial Network

[0124] TR Technical Report

[0125] TS Technical Specifications

[0126] UDM User Data Management

[0127] UE User Equipment

[0128] UMTS Universal Mobile Telecommunications System

[0129] UPF User Plane Function

[0130] WLAN Wireless Local Area Network

[0131] WiMAX Worldwide Interoperability for Microwave Access

[0132] WID Work Item Description

[0133] 3GPP Third Generation Partnership Project

[0134] 5G Fifth Generation

[0135] 5GC 5G Core Network

[0136] 5GS 5G System BRIEF DESCRIPTION OF THE DRAWINGS

[0137] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0138] Figure 1aAn example of the architecture is depicted;

[0139] Figure 1b A schematic diagram of a 5G system is shown;

[0140] Figure 1c A schematic diagram of a non-terrestrial network is shown;

[0141] Figure 2 shows a schematic diagram of the control device;

[0142] Figure 3 A schematic diagram of a user equipment is shown;

[0143] Figure 4 A graph showing UE position error (in m) and TA error (in μs);

[0144] Figure 5 illustrates signaling between a UE and a network according to some embodiments;

[0145] Figure 6 The method flow of some embodiments is shown;

[0146] Figure 7 A first method performed by an apparatus is shown;

[0147] Figure 8 A second method performed by the apparatus is shown;

[0148] Fig. 9 A third method performed by the apparatus is shown;

[0149] Fig.10 A fourth method performed by an apparatus is shown; and

[0150] Fig.11 A schematic diagram of a non-volatile memory medium storing instructions that, when executed by a processor, allow the processor to perform Figures 7 to 10 One or more of the steps of the method. DETAILED DESCRIPTION

[0151] In the following, certain embodiments are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Figure 1a , Figure 1b , Figure 1c , Figure 2 and Figure 3 Certain general principles of wireless communication systems, their access systems and mobile communication devices are briefly explained to help understand the technology behind the described examples.

[0152] In the following, different examples will be described using radio access architectures based on Advanced Long Term Evolution (Advanced LTE, LTE-A) or New Radio (NR, 5G) as examples of access architectures to which the presently described technology can be applied, however, the embodiments are not limited to such architectures. By appropriately adjusting the parameters and procedures, these embodiments can also be applied to other types of communication networks with appropriate means. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Networks (WLAN or Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANETs), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0153] Figure 1a An example of a simplified system architecture is depicted, showing only some elements and functional entities, all of which are logical units, the implementation of which may differ from what is shown. Figure 1a The connections shown are logical connections; the actual physical connections may be different. It will be clear to those skilled in the art that the system typically also includes Figure 1a Other functions and structures than those shown.

[0154] However, the embodiments are not limited to the systems given as examples, but a person skilled in the art may apply the solution to other communication systems having the necessary characteristics.

[0155] Figure 1a The example of FIG. 4 shows a portion of an exemplary radio access network. For example, the radio access network may support sidelink communications as described in more detail below.

[0156] Figure 1a Devices 100 and 102 are shown. Devices 100 and 102 are configured to be wirelessly connected to a node 104 on one or more communication channels. Node 104 is also connected to a core network 106. In one example, node 104 may be an access node, such as an (e / g)NodeB serving devices in a cell. In one example, node 104 may be a non-3GPP access node. The physical link from a device to an (e / g)NodeB is referred to as an uplink or reverse link, while the physical link from an (e / g)NodeB to a device is referred to as a downlink or forward link. It should be understood that an (e / g)NodeB or its functions may be implemented using any node, host, server, or access point entity suitable for such use.

[0157] A communication system typically includes more than one (e / g)NodeB, in which case the (e / g)NodeBs may also be configured to communicate with each other via wired or wireless links designed for this purpose. These links may be used for signaling purposes. A (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. A NodeB may also be referred to as a base station, an access point, or any other type of interface device, including a relay station capable of operating in a wireless environment. The (e / g)NodeB includes or is coupled to a transceiver. From the transceiver of the (e / g)NodeB, a connection to an antenna unit is provided, which establishes a bidirectional radio link to the device. The antenna unit may include multiple antennas or antenna elements. The (e / g)NodeB is also connected to a core network 106 (CN or next generation core NGC). Depending on the deployed technology, the (e / g)NodeB is connected to a serving and packet data network gateway (S-GW+P-GW) or a user plane function (UPF) for routing and forwarding user data packets, and for providing the device with connectivity to one or more external packet data networks, and to a mobility management entity (MME) or an access mobility management function (AMF) for controlling access and mobility of the device.

[0158] A relay node may be provided. An example of a relay node is a layer 3 relay (self-backhaul relay) towards a base station. The device (or, in some embodiments, a layer 3 relay node) is configured to perform one or more of the user equipment functions.

[0159] Various techniques described in this article can also be applied to cyber-physical systems (CPS) (systems of cooperating computing elements that control physical entities). CPS can enable the implementation and utilization of a large number of interconnected information and communication technologies, ICTs, devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems, and the physical systems discussed in mobile cyber-physical systems have inherent mobility. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0160] Furthermore, although the apparatus is depicted as a single entity, different units, processors and / or memory units (not all of which are present in the Figure 1a ) can be implemented.

[0161] 5G enables the use of multiple-input multiple-output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites that operate in cooperation with smaller sites and use various radio technologies depending on service needs, use cases and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods and various forms of machine-type applications (such as (massive) machine-type communications (mMTC), including vehicle safety, different sensors and real-time control). 5G is expected to have multiple radio interfaces, such as below 6 GHz or above 24 GHz, cmWave and mmWave, and can also be integrated with existing traditional radio access technologies (such as LTE). At least in the early stages, integration with LTE can be implemented as a system in which macro coverage is provided by LTE and 5G radio interface access comes from small cells by aggregation to LTE. In other words, 5G plans to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6 GHz - cmWave, 6 or above 24 GHz - cmWave and mmWave).

[0162] One of the concepts considered to be used in 5G networks is network slicing, in which multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput and mobility.

[0163] The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. Low latency applications and services in 5G require content to be close to the radio, which leads to local burst and multi-access edge computing (MEC). 5G enables analysis and knowledge generation to be performed at the data source. This approach requires the use of resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also enables the storage and processing of content close to the cellular subscriber for faster response times. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, collaborative distributed peer-to-peer self-organizing networks and processing (also categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0164] The communication system may also be capable of communicating with other networks 112, such as a public switched telephone network, a VoIP network, the Internet, or a private network, or utilizing services provided by them. The communication network may also be capable of supporting the use of cloud services, for example, at least a portion of the core network operations may be performed as a cloud service (this is in the Figure 1a 114). The communication system may also include a central control entity that provides facilities for networks of different operators to cooperate, for example, in spectrum sharing.

[0165] Edge cloud technology can be introduced into the radio access network (RAN) by leveraging network function virtualization (NFV) and software defined networking (SDN). The use of edge cloud technology can mean that access node operations are at least partially performed in a server, host or node that is operably coupled to a remote radio head or base station including radio components. Node operations can also be distributed among multiple servers, nodes or hosts. The application of cloud RAN architecture enables RAN real-time functions to be performed at or near remote antenna sites (in distributed units DU 108), while non-real-time functions can be performed in a centralized manner (in centralized units CU 110).

[0166] It should also be understood that the distribution of work between core network operations and base station operations may be different from LTE or even non-existent. Some other technological advances that may be used are big data and all-IP, which can change the way networks are built and managed. 5G (or New Radio NR) networks are designed to support multiple hierarchical structures, where MEC servers can be placed between the core and the base station or NodeB (gNB). It should be understood that MEC can also be applied to 4G networks.

[0167] 5G can also use satellite communications to enhance or supplement the coverage of 5G services, for example by providing backhaul. Reference numeral 116 is an example satellite. Possible use cases are to provide service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or on-board passengers, mobile broadband (MBB), or to ensure service availability for critical communications and future railway / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems, or low Earth orbit (LEO) satellite systems, in particular giant constellations (systems in which hundreds of (nano) satellites are deployed). Each satellite in a giant constellation can cover several satellite network entities that create ground cells. Ground cells can be created by ground relay nodes, or by gNBs located on the ground or in satellites.

[0168] It is clear to a person skilled in the art that the described system is only an example of a part of a radio access system, and in practice the system may include a plurality of (e / g)NodeBs, which may access a plurality of radio cells, and the system may also include other devices, such as physical layer relay nodes or other network elements, etc. At least one of the (e / g)NodeBs may be a home (e / g)NodeB. Furthermore, in a geographical area of ​​the radio communication system, a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. A radio cell may be a macro cell (or umbrella cell), which is a large cell, which typically has a diameter of up to tens of kilometers, or a smaller cell, such as a micro cell, a femto cell or a pico cell. Figure 1a The (e / g)NodeB can provide any type of these cells. A cellular radio system can be implemented as a multi-layer network including several cells. Typically, in a multi-layer network, one access node provides one or more cells, and thus multiple (e / g)NodeBs are required to provide such a network structure.

[0169] In order to meet the needs of improving the deployment and performance of communication systems, the concept of "plug and play" (e / g) NodeB is introduced. Generally, the network that can use "plug and play" (e / g) NodeB includes the home nodeB gateway or HNB-GW (H(e / g)NodeB) in addition to the home nodeB. Figure 1a (not shown). An HNB gateway (HNB-GW) usually installed in an operator's network can aggregate services from a large number of HNBs back to the core network.

[0170] Figure 1b A schematic diagram of a 5G system (5GS) is shown. The 5GS may include a terminal, a (radio) access network ((R)AN), a 5G core network (5GC), one or more application functions (AFs) and one or more data networks (DNs).

[0171] The 5G(R)AN may include a terrestrial network (TN) portion, in which one or more gNBs are located on one or more masts or towers. The 5G(R)AN may include a non-terrestrial network (NTN) portion, which adopts a transparent satellite-based RAN architecture or a regenerative satellite-based RAN architecture.

[0172] The concepts of transparent architecture and regenerative architecture are defined in 3GPP TS 38.821. Satellites can implement transparent architecture or payload. Transparent payload can only include RF functions such as RF filtering, frequency conversion and amplification. For transparent architecture, one or more gNBs can be located on the ground.

[0173] The regenerative satellite payload enables the regeneration of the signal received from the Earth, i.e., transforming and amplifying the uplink RF signal before transmitting it on the downlink. For the regenerative architecture, one or more gNBs can be located on one or more satellites. In some cases, part of the gNB (e.g., DU) can be located on the satellite, while part of the gNB (e.g., CU) can be located on the ground.

[0174] One or more gNBs may include one or more gNB distributed unit functions connected to one or more gNB centralized unit functions.

[0175] 5GC may include access and mobility management function (AMF), session management function (SMF), authentication server function (AUSF), user data management (UDM), user plane function (UPF) and / or network exposure function (NEF). 5GC may include a gateway to the NTN part of the 5G(R)AN.

[0176] Figure 1c An exemplary embodiment of a non-terrestrial network is illustrated. A non-terrestrial network may refer to a network or network segment using radio frequency RF resources in a satellite 150 or an unmanned aircraft system UAS. A satellite 150 or UAS may provide services, such as NR services, on the earth via one or more satellite beams and one or more cells 152 (e.g., NR cells) in a given service area defined by the field of view of the satellite 150. The beam footprint (i.e., cell 152) may be elliptical. A service link 154, i.e., a radio link, may exist between the satellite 150 and one or more UEs 156 in the target service area. The satellite may be configured to send one or more signals to one or more UEs via a service link, and one or more UEs may be configured to receive one or more signals from the satellite. In addition, a feeder link 156, i.e., a radio link, may exist between the satellite 150 and one or more satellite gateways 160. The satellite gateway 160 may connect the satellite to, for example, a public data network 162. The satellite 150, the gateway 160, and / or the data network 162 may at least partially include base station functions, such as gNB functions.

[0177] Satellite 150 may implement a transparent payload with RF filtering, frequency conversion, and amplification, wherein the waveform signal repeated by the payload is unchanged.

[0178] Alternatively, satellite 150 may implement a regenerative payload with RF filtering, frequency conversion and amplification as well as demodulation and / or decoding, switching and / or routing, and encoding and / or modulation. In other words, in a regenerative architecture, satellite 150 may include all or at least some base station functionality.

[0179] As a non-limiting example, satellite 150 may be located in a low earth orbit, for example, between 400 and 2000 km. At such an altitude, the satellite may move relative to the earth at a speed of about 7.5 km / s. The UAS may operate at an altitude of, for example, 8 to 50 km, and it may be stationary or moving relative to the earth.

[0180] Figure 2 An example of an apparatus 200 is illustrated. The apparatus may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The apparatus may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0181] The apparatus may be a communication device, a part of a communication device, or provided in a communication device.

[0182] The apparatus may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be performed to perform one or more aspects of the present invention. The software code 215 may be stored in the ROM 211b.

[0183] Now refer to Figure 3 Describing possible communication devices in more detail, Figure 3A schematic partial cross-sectional view of a communication device 300 is shown. The communication device 300 may be provided by any device capable of sending and receiving radio signals. The device generally refers to a mobile or static device (e.g., a portable or non-portable computing device), which includes a wireless mobile communication device operating with or without a universal subscriber identity module (USIM). Non-limiting examples include user equipment, terminal equipment, mobile stations (MS) or mobile devices (such as mobile phones or so-called "smart phones"), computers equipped with wireless interface cards or other wireless interface facilities (e.g., USB dongles), devices using wireless modems (alarm or measurement equipment, etc.), personal data assistants (PDAs) or tablets equipped with wireless communication capabilities, machine type communication (MTC) devices, cellular Internet of Things (CIoT) devices, or any combination of these devices, etc. It should be understood that the device may also be an almost exclusively uplink-only device, an example of which is a camera or video camera that loads images or video clips to a network. The device may also be a device with the ability to operate in an Internet of Things (IoT) network, in which case objects are able to transmit data over a network without requiring human-to-human interaction or human-to-computer interaction, such as for smart grids and connected vehicles. The device may also use the cloud. In some applications, the device may include a user-portable device with a radio component (such as a watch, headphones, or glasses), and the computation is performed in the cloud.

[0184] The communication device may provide, for example, communications for carrying data for communication, such as voice, electronic mail (email), text messaging, multimedia, machine data, etc. Services may be provided via the communication device. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or simply access to a data communications network system such as the Internet. Users may also be provided with broadcast or multicast data. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alerts, and other information.

[0185] In the following, the communication device is referred to as UE, but it should be understood that any alternative communication device may be used instead of UE. UE 300 may receive signals via an air or radio interface 307 via appropriate means for receiving, and may send signals via appropriate means for sending radio signals. Figure 3 In the mobile device, the transceiver arrangement is schematically represented by a block 306. The transceiver arrangement 306 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0186] The UE 300 may be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for software and hardware assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow execution of one or more aspects of the present aspect. The software code 308 may be stored in the ROM 302a.

[0187] The processor, storage means and other related control means may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface, such as a keypad 305, a touch-sensitive screen or touchpad, a combination thereof, etc. Depending on the type of device, one or more of a display, a speaker and a microphone may optionally be provided.

[0188] One example of a wireless communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). The 5G or NR standards part of the 3GPP-based development currently under development is generally referred to as the Long Term Evolution (LTE) or Advanced LTE Pro of the Universal Mobile Telecommunications System (UMTS) radio access technology. Other examples of radio access systems include those provided by base stations of systems based on technologies such as wireless local area networks (WLAN) and / or WiMAX (Worldwide Interoperability for Microwave Access). It should be understood that embodiments may also be used with later or different standards.

[0189] Some embodiments may be used in conjunction with NB-IoT / eMTC over non-terrestrial networks (NTN). This may be used with Release 18 work associated with 5G and subsequent standardization. Of course, this may be used with any other suitable standard. The Release 18 work item (RP-220979) includes the following goals:

[0190] 4.1.1 IoT-NTN performance enhancements in Rel-18 to address legacy issues in Rel-17

[0191] This work takes Rel-17 IoT-NTN as the baseline and considers Rel-17 NR-NTN results, and additional IoT-NTN performance enhancement goals are as follows:

[0192] - Disable HARQ feedback to mitigate the impact of HARQ stalling on UE data rate

[0193] - If needed, study and specify improved GNSS operation for new position fixes with UE pre-compensation during long connection times and for reduced power consumption. Simultaneous GNSS and NTN NB-IoT / eMTC operation is not assumed.

[0194] The UE may need to utilize GNSS to pre-compensate uplink transmissions for time and frequency errors. This may be necessary because NTN scenarios may rely on low earth orbit (LEO) satellites. These satellites may move relative to the earth at speeds of 7.5 km / s, i.e., resulting in rapidly varying time drift and Doppler shift.

[0195] For example, according to TR 38.821 (NR NTN), the maximum round trip delay for a transparent LEO satellite at 600 km is 25.77 ms, with a differential delay within the cell of 3.12 ms. In addition, the maximum Doppler shift is 24 ppm, while the Doppler shift variation is 0.27 ppm / s.

[0196] LEO satellite movement is known, as the satellites move in well-defined orbits. Therefore, 3GPP has agreed that the network will provide information about satellite movement (ephemeris) to the UE.

[0197] A UE that knows its position based on GNSS can then exploit the knowledge of satellite position and movement to determine how uplink transmissions should be adjusted for time and frequency drift.

[0198] However, IoT NTN devices are assumed to be simple and therefore 3GPP has assumed that a UE cannot operate using both GNSS and NTN IoT simultaneously.

[0199] In version 17, the following agreements were reached:

[0200] RAN2#116bis-e protocol:

[0201] - The UE needs to have a valid GNSS position before entering connected mode. If necessary, RAN2 assumes that the UE may need to reacquire a GNSS position before establishing a connection (regardless of whether it was previously valid) to avoid interruptions during the connection.

[0202] - When the GNSS positioning is outdated in RRC_CONNECTED mode, the UE enters idle mode.

[0203] RAN1#107-e protocol:

[0204] - The UE autonomously determines its GNSS validity duration X and reports information associated with this validity duration to the network via RRC signaling.

[0205] -X = {10s, 20s, 30s, 40s, 50s, 60s, 5min, 10min, 15min, 20min, 25min, 30min, 60min, 90min, 120min, infinity}

[0206] RAN1#106-e protocol:

[0207] - For sporadic short transmissions, if GNSS is out of date, a UE in RRC_CONNECTED mode shall return to idle mode and reacquire GNSS positioning.

[0208] - Note: The duration of a short transmission is no longer than the "Validity timer for UL synchronization" mentioned in the WID target (but further discussion is still needed to specify more details)

[0209] In Release 17, the protocol for the UE to move to RRC Idle when the GNSS position is out of date was acceptable because the connection time was assumed to be short. However, the goals of Release 18 now consider longer connection times. Therefore, it may not be feasible for the UE to move to RRC Idle because data transmission may be interrupted and may not be able to be resumed.

[0210] The assumed UE behavior during a long connection can be as follows:

[0211] 1. The UE obtains GNSS positioning before the connection is established (RAN2 protocol).

[0212] 2. GNSS validity timer communicates with the network (RAN1 protocol).

[0213] 3. If the UE is moving / if the GNSS validity timer is about to expire, the UE may need a new GNSS position fix.

[0214] 4. For connected UEs, the network needs to schedule GNSS measurement gaps.

[0215] 5. Similar to the transmission gaps during repetitions, the network needs to retain information about ongoing transmissions during GNSS measurement gaps.

[0216] 6. After the UE has reacquired GNSS positioning, the network and UE need to have a common understanding of this - for example, was the acquisition successful?

[0217] Some embodiments may address the problem of how to detect the need for a new GNSS position fix. If the GNSS validity timer is set accurately, the NW may be aware of the upcoming expiration, and the NW may schedule GNSS measurement gaps accordingly. However, if the UE is moving, the GNSS validity timer may not be accurate. One challenge may be that the UE does not detect movement because the IE does not have measurement gaps that allow it to use GNSS.

[0218] Some embodiments may provide network and UE components to perform such detection.

[0219] Errors in the UE position due to UE movement since the last GNSS fix or inaccuracies in the GNSS fix may result in errors in its timing advance (TA) estimate. The largest TA error may occur when the UE is in the terrestrial lateral path of the satellite and the position error direction is also aligned with this path. The effect of UE position error on timing advance in this worst case is shown in Figure 1. Figure 4 shown. Figure 4 A graph showing UE position error (in m) and TA error (in μs) is shown. The allowed timing error Te for NB-IoT is 80Ts, and the allowed timing error Te for eMTC is 24Ts. Ts is a constant timing unit defined in the LTE specification and is directly mapped to the value on the y-axis. Ts is defined in 36.211 as:

[0220] The sizes of various fields in the time domain, expressed as the number of time units: T s =1 / (15000×2048 seconds.

[0221] Downlink, uplink and sidelink transmissions are organized into f =307200×T s = A radio frame of duration 10 ms.

[0222] (Different standards may have different timing values. For example, in 5G, the timing value is called Tc, and its value is 0.509ns).

[0223] For an elevation angle of 10 degrees, the aforementioned timing errors correspond to position errors of 126m and 38m, respectively. Therefore, even a small UE movement may affect the uplink timing. For example, an IoT device installed on a container loaded on a truck traveling at 80km / h (22.2m / s) will violate the timing requirements of 1.7s for eMTC and 5.7s for NB-IoT, respectively. If the device is on a freight train, it may move faster.

[0224] Some of the current arrangements do not address the situation where the GNSS validity timer is invalid due to UE movement.

[0225] In the current implementation, the (terrestrial) network will monitor whether the UE's uplink transmission is misaligned and then issue a TA command. The misalignment can be determined by the base station based on the UE's reference signal during the channel estimation process. However, the (terrestrial) network will not know the UE's location and movement, nor will it take into account the changing propagation delay. The same can be done for NTN, and the network can send a TA command. However, when the UE reads the GNSS, it may reset the previous TA command, which may cause some jumps. Some embodiments can reduce or avoid these jumps.

[0226] Some embodiments may provide one or more methods to determine whether the GNSS position of the UE is valid or invalid and needs to be updated or can be continuously reused.Some embodiments may use predictable satellite movement and the UE shares its valid position with the network at least once.

[0227] In some embodiments, one or more of the following may be provided.

[0228] 1. The network acquires the UE location and schedules uplink transmission(s).

[0229] 2. The network monitors the UE's uplink transmissions and detects any time / frequency drift that is not as expected. The network may check if the frequency and / or timing is different from the expected frequency and / or timing.

[0230] 3. If the time and / or frequency drift exceeds a threshold, the network schedules a GNSS measurement gap. The network may check if the frequency and / or timing differs by a threshold amount from the expected frequency and / or timing.

[0231] In some embodiments, the network may optionally command the UE to stop any ongoing transmissions.

[0232] If the time / frequency drift is as expected, the network may instruct the UE to restart the GNSS validity timer without performing GNSS positioning.

[0233] refer to Figure 5 , Figure 5 Signaling between a UE and a network according to some embodiments is shown. Figure 5 The signal flow shows the situation where the UE needs to be positioned.

[0234] In S1, the UE receives satellite ephemeris from the network.

[0235] In S2, the network receives UE location information from the UE.

[0236] In S3, the UE receives a schedule for uplink transmission from the network.

[0237] In S4, the network estimates when the UE transmission is expected to be received.

[0238] In S5, the UE sends an uplink transmission to the network.

[0239] In S6, the network determines that the transmission drift is within a threshold.

[0240] In S7, the UE sends an uplink transmission to the network.

[0241] In S8, the network determines that the transmission drift exceeds a threshold.

[0242] In S9, the network indicates the scheduled GNSS measurement gap to the UE. Optionally, the UE is commanded to stop uplink communications. This may be until the UE has reacquired a valid position.

[0243] In S10, the UE obtains a new GNSS position.

[0244] refer to Figure 6 , Figure 6 The method flow of some embodiments is shown.

[0245] As indicated by reference numeral T1 , the RAN is monitoring the uplink timing and frequency of transmissions from the UE.

[0246] As shown in the reference numeral T2, the RAN determines whether the timing and / or frequency is as expected. Since the RAN knows the UE location, satellite ephemeris and common delays, the RAN can calculate the expected values. A small margin can be applied to cover other errors, such as UE clock, etc. If the time and / or frequency is as expected, it is followed by T3.

[0247] As indicated by reference numeral T3, it is checked whether the GNSS validity timer of the UE is close to expiration. For example, it may be checked whether there is less than a threshold amount of time remaining. If there is less than a threshold amount of time remaining, it may be determined that the validity timer is close to expiration. This may be performed by the RAN. Alternatively or additionally, this may be performed in the UE. If the timer is not close to expiration, the method reverts to T1. If the timer is close to expiration, it is followed by T4. As indicated by reference numeral T4, if the GNSS validity timer is close to expiration, but the timing and / or frequency (e.g., determined in T2) indicates that the UE is not moving, the network signals the UE that the UE may restart its GNSS validity timer without GNSS positioning. The signaling may be performed by MAC-CE signaling or in any other suitable manner. In some embodiments, the timer may be restarted with the same value. Alternatively, the UE may use a different validity timer value. This may be based on the elevation angle to the serving NTN satellite. For example, when the serving satellite (i.e., the satellite providing connectivity to the UE in the NTN) is at a high elevation angle, a larger UE position error may be tolerated, such as Figure 4 As shown, the validity timer value can be relaxed in this case. (In this example, the NTN satellites are different from the GNSS satellites). Alternatively or additionally, this can be based on a different value provided by the network. If the UE is in a stationary state, a larger value can be used. Alternatively or additionally, the timer value can be based on a pre-programmed table with values.

[0248] One metric for the NW could be to check if a timer will expire before an "upcoming scheduled" uplink transmission is completed. Due to repeated use, in IoT LTE uplink transmissions can last for seconds or even tens of seconds. "Upcoming scheduled" could be the time from when the NW receives a buffer status report from the UE indicating that an uplink transmission is needed and until the NW has made a scheduling decision. This can be used to determine if the GNSS time is close to expiration.

[0249] Alternatively or additionally, near expiration may be, for example, at least 90% (or other suitable value) of the timer has expired.

[0250] If it is determined in T2 that the timing and / or frequency values ​​are not as expected, this is followed by T5. As indicated by reference numeral T5, it is checked whether the change in timing and / or frequency will exceed an acceptable maximum value before the GNSS validity timer expires. If not, this is followed by T1. If so, this is followed by T6.

[0251] As indicated by reference numeral T6 , the network schedules GNSS gaps and notifies the UE so that the UE can update the GNSS positioning.

[0252] Some embodiments may have one or more of the following advantages:

[0253] Detecting UE position errors and scheduling GNSS measurement gaps enables the network and UE to avoid misaligned uplink transmissions. This may mean reduced interference.

[0254] Network-based UE position error detection may be useful for IoT NTNs where the UE cannot operate both GNSS and IoT simultaneously.

[0255] Avoid GNSS readings if they are not needed.

[0256] Therefore, some embodiments allow uplink misalignment to be monitored and detected by the network. In determining whether the UE's uplink transmission is actually misaligned, the network may consider one or more of the following:

[0257] A. UE's reported location

[0258] B. Satellite movement causes changes in the propagation delay between the satellite and the UE location

[0259] C. Drift caused by inaccurate ephemeris. The ephemeris is determined for a certain epoch time. After this epoch time, the actual satellite position and the predicted position based on the ephemeris will drift.

[0260] D. Past TA commands that have been sent by the network.

[0261] E. UE trajectory / movement (if known).

[0262] F. Common TA, indicating the feeder link delay TA_common, represents the feeder link delay for which the UE is compensating and which is based on information broadcast by the network.

[0263] G.GNSS validity timer

[0264] An indication of "good time alignment" from the network to the UE (e.g., determined in T2) may be provided via one or more of the following:

[0265] - A bit indicator in the DCI (DCI with new UL allocation, or with other DL content). There may also be an indication that the time alignment timer is to be restarted.

[0266] - A MAC-CE with a timing advance command with a net value equal to 0. In this case, using this feature, the UE will interpret the MAC-CE command as an indication of good timing alignment. In response to this MAC-CE command, the UE may postpone, restart and / or extend the validity timer.

[0267] When the UE receives the "good time alignment indication", the UE may perform one or more of the following:

[0268] - The UE may restart the validity timer (e.g., start again from 0)

[0269] - The UE may increment the expiry value for the timer by a fixed value. For example, this may be specified in the standard and / or indicated by the gNB. Alternatively, there may be a set of values ​​and the UE may increment to the next or previous value in the set of values. The gNB may indicate whether the next value is to be used. This may alternatively be known by the UE based on, for example, the time since the last scheduling of the gap.

[0270] - The UE may set a higher baseline (ie, a longer period) for the validity timer at the next opportunity (ie, after the UE updates its location).

[0271] In some embodiments, after receiving the "measurement gap" command, the UE takes one or more of the following actions:

[0272] - If the measurement gap order is indicated to the UE earlier (time X earlier) than the validity timer: the UE may reduce the expiry value of the validity timer for the next iteration. The expiry value time may be reduced by a fixed amount or by a value depending on time X.

[0273] - If the UE receives several MAC-CEs with timing advance commands different from 0, or if the total value of the MAC-CE commands is greater than a set threshold, the UE may also decrease the expiration value of the timer for the next iteration.

[0274] In an alternative embodiment, timing misalignment detection may be performed by the UE as follows:

[0275] When considering one or more of the above parameters AD, the UE receives a TA command that is inconsistent with the original location of the UE.

[0276] The UE compares the timing of the PSS and / or SSS (and / or any other DL signaling with known timing) in the transmission gap with the GNSS-based time and determines whether there is a difference between the time when the PSS and / or SSS and / or other DL signals are expected and the time when the PSS and / or SSS and / or other DL signals are actually received.

[0277] If the UE detects a problem, the UE may request a GNSS measurement gap.

[0278] Thus, some embodiments may involve behavior of a network entity such as a gNB, etc. This may enable transmission of GNSS measurement gaps to a UE, which may be used to perform GNSS positioning (i.e., determining the location of a communication device based on satellite positioning data).

[0279] Some embodiments may be performed in an NTN network with UEs that cannot operate GNSS and 3GPP (or other cellular networks) simultaneously. When the location data associated with the UE becomes invalid, a network-based mechanism may allow GNSS measurement gaps. The network (e.g., gNodeB) checks whether the location is still valid (via TA) and schedules GNSS measurement gaps when needed. Therefore, the RAN knows the UE location and the satellite location, and therefore knows what the TA value should be. If they are not the same, the UE is using a different GNSS location (due to movement or due to incorrect GNSS positioning). Some embodiments enable the network to schedule GNSS measurement gaps when the UE's transmissions are aligned / misaligned in time and / or frequency. The NW monitors the UE's uplink transmissions and detects time and / or frequency drift to determine whether the GNSS location data is still valid for the UE. If the location data is still invalid, the NW can re-acquire the scheduled measurement gap for GNSS. If the location data is still valid, the NW requires the UE to reset the GNSS validity timer. The monitored time / frequency refers to the degree of alignment of the UE's uplink transmission (PUSCH, PUCCH, SRS, etc.) with the time-frequency resources (symbols in time, subcarriers in frequency).

[0280] So, for example, the NW may notice that symbols arrive too early / late compared to the receiver's symbol timing. Likewise, the network may find that the subcarriers of the transmitted signal are not perfectly aligned with the receiver.

[0281] However, frequency drift may occur at the satellite and the satellite may convert it into a feeder link transition, so for the transparent case, frequency drift information may not be available in the RAN. However, in other embodiments, frequency drift information may be used.

[0282] The UE may need to use GNSS to pre-compensate uplink transmissions for time and / or frequency errors. This may be necessary because, as mentioned earlier, NTNs may rely on low earth orbit (LEO) satellites. These satellites move relative to the earth at a speed of 7.5km / s, i.e., causing rapidly changing time drift and Doppler shift. The maximum round-trip delay for a transparent LEO satellite at 600km is 25.77ms, with a differential delay of 3.12ms within the cell. In addition, the maximum Doppler shift is 24ppm, while the Doppler shift variation is 0.27ppm / s. LEO satellite movement is known because the satellite moves on a well-defined orbit. Therefore, the network will provide information about satellite movement (ephemeris) to the UE. A UE that knows its position based on GNSS can then use knowledge of satellite position and movement to determine how to adjust uplink transmissions for time and / or frequency drift. IoT NTN devices may be simple and may not be able to operate GNSS and NTN IoT at the same time.

[0283] If the GNSS validity timer is set accurately, the NW is aware of the impending expiration and the NW can schedule GNSS measurement gaps accordingly. However, if the UE is moving, the GNSS validity timer may not be accurate. The challenge is that the UE cannot detect the movement because it does not have measurement gaps that allow it to use GNSS. Some embodiments propose network and / or UE components for performing such detection. Errors in the UE's position due to UE movement since the last GNSS fix or inaccuracies in the GNSS fix may result in errors in its timing advance (TA) estimate.

[0284] Some embodiments provide methods for determining whether a UE's GNSS position is valid or invalid and whether it needs to be updated or can be continuously reused. Some embodiments use predictable satellite movement, and the UE shares its valid position with the network at least once. The network can obtain the UE position and schedule uplink transmissions. The network can monitor the UE's uplink transmissions and detect any time and / or frequency drift that is not as expected. If the time and / or frequency drift exceeds a threshold, the network can schedule a GNSS measurement gap. The network can also optionally command the UE to stop any ongoing transmissions. If the time / frequency drift is as expected, the network can instruct the UE to restart the GNSS validity timer without performing GNSS positioning.

[0285] An advantage of some embodiments is that UE position error is detected and GNSS measurement gaps are scheduled so that the network and UE can avoid misaligned uplink transmissions, i.e. interference is reduced. Network-based UE position error detection may be particularly useful for IoT NTNs, since the UE cannot operate GNSS and IoT simultaneously. Some embodiments may avoid GNSS readings if not required.

[0286] Now refer to Figure 7 The method of some embodiments is described. The method may be performed by an apparatus. For example, the apparatus may be as follows Figure 2 As shown. The device may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The device may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0287] In A1 , the method includes monitoring uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions is as expected.

[0288] In A2, the method includes scheduling a position acquisition gap for the communication device when the frequency and / or timing of the uplink transmission is not as expected.

[0289] Now refer to Figure 8 The method of some embodiments is described. The method may be performed by an apparatus. For example, the apparatus may be as follows Figure 2 As shown. The device may be a base station, a part of a base station, or provided in a base station. The base station may be a gNB, etc. The device may alternatively be provided in any other suitable network entity, or may be any other suitable network entity.

[0290] In B1 , the method includes monitoring uplink transmissions from a communication device to determine whether a frequency and / or timing of the uplink transmissions is as expected.

[0291] In B2, the method includes determining that a location acquisition validity timer associated with the communication device is about to expire.

[0292] In B3, the method includes causing a message to be sent to the communication device when it is determined that the frequency and / or timing of the uplink transmission is as expected, and when it is determined that the location acquisition validity timer associated with the communication device is about to expire, the message indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing location acquisition positioning.

[0293] Now refer to Fig. 9 The method of some embodiments is described. The method may be performed by an apparatus. For example, the apparatus may be as follows Figure 2 and / or Figure 3The apparatus may be provided in a communication device, or may be a communication device.

[0294] In C1 , the method includes receiving a message from a network device indicating that a location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix.

[0295] In C2, the method includes restarting the location acquisition validity timer without performing the location acquisition fix.

[0296] Now refer to Fig.10 The method of some embodiments is described. The method may be performed by an apparatus. For example, the apparatus may be as follows Figure 2 and / or Figure 3 The apparatus may be provided in a communication device, or may be a communication device.

[0297] In D1 , the method includes receiving a message from a network device indicating a schedule of a location acquisition gap.

[0298] In D2, the method includes performing a position acquisition fix in a position acquisition gap.

[0299] Fig.11 A schematic diagram of a non-volatile memory medium storing instructions and / or parameters that, when executed by a processor, allow the processor to perform Figures 6 to 10 One or more of the steps of the method.

[0300] It should be noted that while the above describes exemplifying embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0301] GNSS positioning and GNSS measurement gaps have been mentioned. In other embodiments, other location acquisition technologies may be used. By way of example only, the location acquisition technology may be a network-based or network-verified location technology. Location acquisition gaps may be provided using a network-based or network-verified location technology.

[0302] It should be understood that although the above concepts have been discussed in the context of 5GS, one or more of these concepts may be applied to other cellular systems.

[0303] Therefore, the embodiments may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the embodiments are not limited thereto. Although various embodiments may be illustrated and described as block diagrams, flow charts, or using some other graphical representations, it is well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0304] The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. Further, in this regard, it should be noted that any process (e.g., Figures 6 to 10 The software may be stored on physical media such as memory chips or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as DVD and its data variants CD.

[0305] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0306] Alternatively or additionally, some embodiments may be implemented using a circuit system. The circuit system may be configured to perform one or more of the previously described functions and / or method steps. The circuit system may be provided in a base station and / or a communication device.

[0307] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0308] (a) Pure hardware circuit implementation (such as an implementation using only analog and / or digital circuit systems)

[0309] now);

[0310] (b) A combination of hardware circuits and software, such as:

[0311] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0312] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to enable an apparatus (such as a communication device or base station) to perform the various functions previously described; and

[0313] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) to operate, but the software may be absent when not required for operation.

[0314] This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuitry also covers, for example, an integrated device.

[0315] The foregoing description provides a complete and informative description of some embodiments by way of exemplary and non-limiting examples. However, various modifications and adaptations may become apparent to one skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications to the teachings will still fall within the scope defined in the appended claims.

Claims

1. A device, include: means for monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of said uplink transmissions are as expected; as well as Means for obtaining a gap for said communication device scheduling position when said frequency and / or timing of said uplink transmission is not as expected.

2. The apparatus of claim 1, comprising means for causing a message to be sent to the communication device, the message comprising information regarding the scheduled position acquisition gap.

3. An apparatus according to any preceding claim, wherein the component for monitoring uplink transmissions from the communication device determines that the frequency and / or timing of the uplink transmission is not as expected when the frequency and / or timing of the uplink transmission differs from an expected frequency and / or timing for the uplink transmission by more than a threshold amount.

4. An apparatus according to any preceding claim, comprising means for causing a message to be sent to the communication device, the message indicating that the communication device is to cease uplink transmission until the communication device has reacquired a valid position.

5. A device, include: means for monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of said uplink transmissions are as expected; means for determining that a location acquisition validity timer associated with the communication device is about to expire; as well as A component for causing a message to be sent to the communication device upon determining that the frequency and / or timing of the uplink transmission is as expected and upon determining that the location acquisition validity timer associated with the communication device is about to expire, the message indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix.

6. The apparatus of claim 5, wherein the message further comprises information indicating a new timing value for the location acquisition validity timer.

7. A device, include: means for receiving a message from a network device indicating that a location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix; and Means for restarting the location acquisition validity timer without performing a location acquisition fix.

8. The apparatus of claim 7, wherein the means for restarting the location acquisition validity timer restarts the validity timer with a different timing value compared to a previous timing value.

9. An apparatus as claimed in claim 7 or 8, comprising means for causing information to be sent to the network device, the information indicating the timing value being used for the restarted validity timer.

10. An apparatus according to claim 8 or 9, comprising means for determining the different timing values ​​in dependence on an elevation angle associated with a serving satellite of a non-terrestrial network.

11. An apparatus as claimed in any one of claims 8 to 10, comprising means for determining the different timing values ​​based on a table of values ​​stored by the apparatus.

12. An apparatus as claimed in any one of claims 8 to 11, comprising means for determining the different timing value by incrementing the previous timing value by a fixed value to provide the different timing value.

13. An apparatus as claimed in any one of claims 8 to 11, comprising means for determining the different timing value by selecting a next value in a set of timing values.

14. The apparatus according to claim 8 or 9, wherein information about the different timing values ​​is provided by the network device.

15. A device, include: means for receiving a message from a network device, the message indicating a schedule for a location acquisition gap; as well as Means for performing position acquisition and positioning in the position acquisition gap.

16. The apparatus of claim 15, comprising means for ceasing uplink communications with the network device until a valid position has been reacquired.

17. An apparatus according to any preceding claim, wherein position acquisition is performed by a global navigation satellite procedure, a network-based position procedure or a network-verified position procedure.

18. A method, include: monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of the uplink transmissions are as expected; as well as When the frequency and / or timing of the uplink transmission is not as expected, a position acquisition gap is scheduled for the communication device.

19. A method, include: monitoring uplink transmissions from a communication device to determine whether the frequency and / or timing of the uplink transmissions are as expected; determining that a location acquisition validity timer associated with the communication device is about to expire; as well as When it is determined that the frequency and / or timing of the uplink transmission is as expected, and when it is determined that the location acquisition validity timer associated with the communication device is about to expire, a message is sent to the communication device, indicating that the location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix.

20. A method, include: receiving a message from a network device indicating that a location acquisition validity timer associated with the communication device is to be restarted without performing a location acquisition fix; as well as In the case where the position acquisition positioning is not performed, the position acquisition validity timer is restarted.

21. A method, include: receiving a message from a network device, the message indicating scheduling of a location acquisition gap; as well as Position acquisition and positioning are performed in the position acquisition gap.

22. A computer program comprising computer executable instructions which, when executed, cause the method according to any one of claims 18 to 21 to be performed.

Images