System Broadcast Information Availability Mechanism

Abstract

The embodiments of the present disclosure propose a solution to utilize system broadcast information, such as GNSS information, which can be used to derive time domain and / or frequency domain compensation. According to the embodiments of the present disclosure, a system broadcast information validity timer is introduced in both the UE and the network that ensures that the availability status of said system broadcast information is synchronized at the two nodes, and said system broadcast information is valid for pre-correction in time domain and / or frequency domain when said timer is running. In this way, the UE can estimate and schedule the correct timing and frequency for UL transmission.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to methods, devices, apparatus, and computer-readable storage media for system broadcast information availability. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP®) has been supporting the technology of New Radio (NR) in non-terrestrial networks (NTN). To support NR radio access over satellite links, long round trip delay is one of the issues to be addressed. For example, a user equipment (UE) can pre-compensate in uplink (UL) transmission in time and / or frequency domain. Depending on whether the UE can pre-compensate for the estimated delay in UL transmission, 3GPP has identified two types of UE: Summary of the Invention

[0003] Generally, the exemplary embodiments of the present disclosure provide a solution for system information availability.

[0004] In a first aspect, a first device is provided, the first device including at least one processor and at least one memory including computer program code, the at least one memory and the at least one memory and the computer program code are configured by the at least one processor to: trigger a validity timer of system broadcast information used to derive compensation for transmission between the first device and a second device in a time domain and / or a frequency domain, determine whether the system broadcast information is valid for compensation before the validity timer expires, and according to a determination that the system broadcast is valid, transmit validity information indicating that the system broadcast is valid to the second device, and reset the validity timer.

[0005] In a second aspect, a second device is provided, the second device comprising at least one processor and at least one memory including computer program code configured by the at least one processor to cause the second device to trigger a validity timer of system broadcast information used to derive compensation for transmissions by the first device between the first device and the second device in the time domain and / or frequency domain, receive validity information from the first device indicating that the system broadcast information is valid, and reset the validity timer.

[0006] In a third aspect, a method is provided, the method including: triggering a validity timer of system broadcast information used to derive compensation for transmission between a first device and a second device in a time domain and / or a frequency domain, determining whether the system broadcast information is valid for compensation before the validity timer expires, transmitting validity information indicating that the system broadcast is valid to the second device according to a determination that the system broadcast is valid, and resetting the validity timer.

[0007] In a fourth aspect, a method is provided, comprising: triggering, at a second device, a validity timer of system broadcast information used to derive compensation for transmissions between a first device and a second device in a time domain and / or a frequency domain by a first device, receiving validity information from the first device indicating that the system broadcast information is valid, and resetting a validity timer.

[0008] In a fifth aspect, an apparatus is provided, comprising: means for triggering a validity timer of system broadcast information used to derive compensation for transmission between a first device and a second device in a time domain and / or a frequency domain, means for determining whether the system broadcast information is valid for compensation before expiration of the validity timer, means for transmitting validity information indicating that the system broadcast is valid to the second device according to a determination that the system broadcast is valid, and means for resetting the validity timer.

[0009] In a sixth aspect, an apparatus is provided, comprising: means for triggering, at a second device, a validity timer of system broadcast information used to derive compensation by a first device for transmission between a first device and a second device in a time domain and / or a frequency domain, means for receiving validity information from the first device indicating that the system broadcast information is valid, and means for resetting a validity timer.

[0010] In a seventh aspect, there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least a method according to any one of the third and fourth aspects.

[0011] It should be understood that the Summary is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. [Brief description of the drawings]

[0012] Some exemplary embodiments will now be described with reference to the accompanying drawings. [Figure 1] FIG. 1 shows a signaling flow of a random access procedure according to the prior art. [Figure 2A]2A and 2B each show a schematic diagram of a timing advance (TA) calculation according to the prior art. [Figure 2B] 2A and 2B each show a schematic diagram of a timing advance (TA) calculation according to the prior art. [Diagram 3] FIG. 3 shows a schematic diagram of Physical Uplink Shared Channel (PUSCH) scheduling from different UEs according to the prior art. [Figure 4] FIG. 4 illustrates an example communication environment in which example embodiments of the present disclosure may be implemented. [Diagram 5] FIG. 5 illustrates a signaling flow for a validity timer synchronization procedure according to some exemplary embodiments of the present disclosure. [Figure 6] FIG. 6 illustrates a flowchart of a method implemented in a first device according to some example embodiments of the present disclosure. [Figure 7] FIG. 7 shows a flowchart of a method implemented in a second device according to some other example embodiments of the present disclosure. [Figure 8] FIG. 8 illustrates a simplified block diagram of an apparatus suitable for practicing exemplary embodiments of the present disclosure. [Figure 9] FIG. 9 illustrates a block diagram of an exemplary computer-readable medium in accordance with some exemplary embodiments of the present disclosure.

[0013] Throughout the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes, to help those skilled in the art understand and practice the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. The embodiments described herein may be implemented in various ways other than those described below.

[0015] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0016] References in this disclosure to "one embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need to include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not expressly described.

[0017] In this specification, terms such as "first" and "second" may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0018] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the terms "comprises," "comprising," "has," "having," "including," and / or "including" specify the presence of stated features, elements, and / or components, etc. It will be further understood that does not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0019] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) Hardware-only circuit implementations (e.g., analog and / or digital-only implementations) and (b) A combination of hardware circuitry and software, such as (where applicable) (i) A combination of analog and / or digital hardware circuitry and software / firmware; and (ii) software (including digital signal processors), software, and parts of hardware processors with memory that work together to cause a device, such as a mobile phone or a server, to perform various functions; (c) Hardware circuits and processors, such as a microprocessor or part of a microprocessor, that require software (e.g., firmware) to operate, but the software may be absent when not necessary for operation.

[0020] This definition of circuitry applies to all uses of the term in this application, including any claims. As a further example, the term circuitry, as used in this application, also covers merely a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. The term circuitry also covers, for example, a baseband or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device, if applicable to the particular claim element.

[0021] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network may be performed according to any suitable generation of communication protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and / or other protocols now known or developed in the future. The embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communication, there will of course be future communication technologies and systems in which the present disclosure may be embodied. The scope of the present disclosure should not be considered as being limited to only the aforementioned systems.

[0022] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. A network device may refer to a base station (BS) or access point (AP), e.g., Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also called gNB), remote radio unit (RRU), radio header (RH), remote radio head (RRH), relay, integrated and access backhaul (IAB) node, low power nodes such as femto, pico, non-terrestrial network equipment such as satellite network equipment, low earth orbit (LEO) satellites, geostationary earth orbit (GEO) satellites, airborne network equipment, etc., depending on the terminology and technology applied. The term "terminal equipment" refers to any end device capable of wireless communication. In the following description, the terms "terminal equipment", "terminal", "user equipment" and "UE" may be used interchangeably.

[0023] As mentioned above, 3GPP identifies two types of UEs depending on whether the UE can pre-compensate for the estimated delay in UL transmission. Specifically, a type 1 UE can refer to a UE that can pre-compensate for Timing Advance (TA), and a type 2 UE can refer to a UE that cannot pre-compensate for TA. As used herein, the term "Timing Advance (TA)" refers to a technique that can compensate for the propagation delay as a signal travels between the UE and the Base Station (BS) or between the UE and a satellite.

[0024] FIG. 1 illustrates a signaling flow of a random access procedure according to the prior art. As shown in FIG. 1, UE 110 may transmit a 1010 message (Msg) 1 (e.g., a preamble) to gNB 120. The gNB may transmit a 1020 message (Msg 2) to UE 110. UE 110 may transmit a 1020 Msg 3 to gNB 120, and gNB 120 may transmit a Msg 4 to UE 110. If UE 110 is a type 1 UE, UE 110 should first estimate a timing advance (TA) for the gNB based on received system broadcast information (e.g., Global Navigation Satellite System (GNSS) information) before transmitting Msg 1. UE 110 may apply the estimated TA in transmitting Msg 1. The gNB 120 may determine a TA adjustment based on UE 110's TA estimation.

[0025] If UE 110 is a type 2 UE, UE 110 cannot estimate the timing advance for gNB 120. This may occur for UEs without GNSS capability, or for UEs where GNSS signals are unavailable due to poor channel conditions, or for UEs where GNSS information is temporarily out of accuracy requirements (e.g., UE moving to indoor coverage). In this case, gNB 120 may need to broadcast a common TA, where the value of the common TA is the TA of the feeder link plus the TA of the minimum service link corresponding to the terrestrial reference point. UE 110 can apply the broadcasted common TA to send Msg1. Figures 2A and 2B show schematic diagrams of TA calculation, respectively.

[0026] Figure 2A shows the TA calculation for the regenerated payload. In this case, the UE-specific TA can be determined based on:

number

[0027] The common reference TA broadcast by the gNB may be:

number

[0028] Figure 2B shows the TA calculation for a bent-pipe payload. The bent-pipe configuration means that the satellite acts like a relay, sending back to Earth exactly what is coming from the satellite. In this case, the UE-specific TA is:

number

[0029] The common reference TA broadcast by the gNB is

number

[0030] Since UEs may or may not have pre-compensation capabilities, they may apply different TAs and have different restrictions on resource allocation for the Physical Random Access Channel (PRACH). For example, for UEs without timing pre-compensation capabilities, the preamble reception window at the network (NW) must be at least twice the maximum differential delay in the cell. To ensure that the preamble reception windows between consecutive RACH occasions (ROs) do not overlap, the PRACH configuration should be such that the time interval between two consecutive ROs is greater than twice the maximum differential delay in the cell (i.e., a sparse PRACH configuration should be configured). For UEs with timing pre-compensation capabilities, no such restrictions are necessary.

[0031] Therefore, when both types of UEs coexist in the same cell, PRACH resources must be configured separately for UEs with and without pre-compensation capabilities. On top of this PRACH design, the NW can distinguish between different types of UEs, so that they can be scheduled and treated differently.

[0032] In addition, for UEs with pre-compensation capability, another topic is how to schedule the Physical Uplink Shared Channel (PUSCH) including both Msg3 on PUSCH and unicast data on PUSCH during RACH procedure when the UE is in RRC coupled state. According to 3GPP offline discussion, there are two possible ways:

[0033] Option 1: The MW schedules the PUSCH using a TA equal to the maximum RTT of the UEs in the cell. Since UEs can be in the coverage center of a cell as well as at the cell edge, for simplicity, the MW can schedule the PUSCH using the maximum round trip time (RTT) to ensure that all UEs have enough TA to transmit their PUSCH.

[0034] Option 2: The NW schedules the PUSCH using a TA equal to the maximum RTT of the UEs scheduled in the current scheduling TTI. The PUSCH can also be scheduled using the maximum possible RTT among all UEs in the current scheduling TTI (instead of all UEs in the cell) to save the UE scheduling delay.

[0035] In option 1, the max RTT can be broadcast in the cell so that all UEs know this value. In option 2, each UE has to report its estimated TA to the NW, so that the NW can determine the value of max RTT for UEs scheduled in the "current" TTI.

[0036] 3GPP has not yet decided what solution should be applied to the Radio Access Network (RAN) 2, which has decided to discuss whether the UE should report the UE-calculated TA (i.e., UE-estimated TA) to the NW to enable Option 2.

[0037] However, option 2 reduces the coverage of PUSCH because the information of the TA value applied by the UE is added as overhead to MsgA PUSCH, etc., which significantly increases the payload size of MsgA PUSCH, ultimately reducing the coverage of PUSCH.

[0038] Therefore, both Option 1 and Option 2 should be supported in NTN, which leaves flexibility to NW to balance PUSCH overhead (i.e. PUSCH coverage) and PUSCH scheduling delay. For example, if the cell size is small enough to limit the differential RTT of all UEs (differential RTT from all UEs in the cell is not too large and close to the maximum RTT of the cell) or if the UE does not have time-critical services, the UE should be scheduled as Option O. Otherwise, Option 2 can be adopted.

[0039] To support option 1, there is some discussion in 3GPP on how to allow the NW to receive all PUSCH transmissions from different UEs in the same slot (e.g., slot n) if the NW schedules these UEs in the same scheduling slot (e.g., slot m), where the distance between slot m and slot n is equal to a fixed value (e.g., max_TA or max_TA+NW indicated offset).

[0040] According to the current NW implementation principle in terrestrial networks, one basic rule is that if the NW schedules a group of UEs in the same DL scheduling slot (e.g. slot m), the NW expects all PUSCH transmissions from these UEs to arrive at the gNB in ​​the same UL PUSCH slot (e.g. slot n). If this is not the case, the NW will have to consider not only the UEs scheduled in the current scheduling slot, but also the UEs (already) scheduled in previous slots, and check whether the UEs scheduled from different scheduling slots have the same PUSCH transmission slot (e.g. both slot m and slot m-1 schedule the UE's transmission in slot n).

[0041] To satisfy this rule in NTN, the UE needs to automatically adjust the transmission time of the PUSCH transmission based on the UE_estimated_TA. In this case, the PUSCH can be scheduled based on the maximum RTT in the cell, for example, as shown in Figure 3.

number

[0042] In other words, max_TA can be broadcast in the cell so that all UEs know this value. When UE 110 receives DCI in slot m, UE 110 transmits PUSCH in slot n, where n=m+k2+Delta, and where Delta=(max_TA-UE_TA)=(max_TA-UE_estimated_TA-TAC), where TAC is the value of the timing advance command that the UE received from the gNB. This ensures that gNB 120 receives all PUSCH transmissions from different UEs after max_TA+k2 slots have elapsed since the gNB transmitted DCI0.

[0043] As mentioned in the previous discussion, the UE estimates the timing advance for the satellites before the UE transmits Msg1 based on the GNSS information it receives (e.g., GNSS location or GNSS timestamp information). Such GNSS information can be received by using a GNSS device that can function without a connection to a 3GPP / cellular radio network. However, Option 1 can be problematic if the information is out of date or if the UE is unable to obtain a new accurate estimate.

[0044] For UEs without pre-correction capability, PUSCH scheduling may follow the legacy process of terrestrial networks (i.e., relying on TA commands from the network side for UL alignment).

[0045] In an NTN system that supports both UEs with and without timing pre-correction (e.g., Type1 or Type2 UEs), before sending Msg1 to the access system, the UE needs to determine the availability of GNSS and select the corresponding dedicated PRACH resource to access the NW. According to the selected preamble resource, the gNB can identify the type of UE, so that it can set the appropriate preamble reception window during the RACH procedure and offset the start of the ra-ResponseWindow. Then the gNB can schedule PUSCH for the UE.

[0046] For a UE with pre-compensation capability, when the UE is scheduled on PUSCH, the UE needs to automatically adjust the transmission time for PUSCH transmission based on UE_estimated_TA (and the TAC command value based on UE-estimated TA). The autonomously adjusted transmission time delta is equal to (max_TA-UE_estimated_TA-TAC).

[0047] However, when the UE is in an RRC coupled state, a UE with GNSS capability (and timing pre-correction capability) may not be able to calculate the TA correctly because its GNSS information becomes unreliable, for example when the UE moves from outdoors to indoors and GNSS signals are unavailable due to poor channel conditions, or when the GNSS information temporarily falls outside the accuracy requirements for timing estimation (i.e. the status of the GNSS information switches from available to unavailable).

[0048] When UE_estimated_TA becomes incorrect, interference occurs between different UEs, for example, timing misalignment occurs in PUSCH reception between different UEs, and UE1 and UE2 do not align in gNB reception, contrary to Figure 6. If delta is larger than the cyclic prefix (for example, when the UE is moving fast along the mobility of the NTN cell), interference occurs and system performance is degraded.

[0049] Furthermore, when GNSS information is lost or not accurately received, at least in Low Earth Orbit (LEO) scenarios, frequency synchronization cannot be acquired or updated / tracked, resulting in UE-to-UE interference for UEs with adjacent Physical Resource Blocks (PRBs) for PUSCH transmission, which also degrades system performance.

[0050] To solve at least some of the above problems, a solution regarding the availability of system broadcast information is proposed. According to an embodiment of the present disclosure, a system broadcast information validity timer is introduced to ensure that the system broadcast information is valid when the timer is running so that pre-compensation is performed in the time domain and / or frequency domain. In this way, UEs can be scheduled with the correct timing estimate for UL transmission.

[0051] 4 is a schematic diagram of a communication environment 400 in which embodiments of the present disclosure may be implemented. The communication environment 400, which is part of a communication network, includes device 410-1, device 410-2, ..., device 410-N, which may be collectively referred to as "first device(s) 410." The communication environment 400 is comprised of a second device 420.

[0052] The communication environment 400 may be comprised of any suitable number of devices and cells. In the communication environment 400, the first device 410 and the second device 420 may communicate data and control information with each other. If the first device 410 is a terminal device and the second device 420 is a network device, the link from the second device 420 to the first device 410 is called a downlink (DL) and the link from the first device 410 to the second device 420 is called an uplink (UL). In some embodiments, a regenerative architecture may be applied to the communication environment 400. Alternatively, a bent pipe architecture may be applied to the communication environment 400.

[0053] It should be understood that the number of first devices and cells and their connections shown in Figure 4 are given for illustrative purposes, without implying any limitation, and that communication environment 400 may include any suitable number of devices and networks adapted to implement embodiments of the present disclosure.

[0054] Communications in the communication environment 400 may be performed according to any suitable communication protocol(s), including, but not limited to, cellular communication protocols, such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local network communication protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols now known or developed in the future. Furthermore, communications may utilize any suitable wireless communication technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or other technologies now known or developed in the future.

[0055] Exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. Reference is now made to FIG. 5, which illustrates a signaling flow 500 for a validity timer synchronization procedure according to an exemplary embodiment of the present disclosure. For discussion purposes, the signaling flow 500 is described with reference to FIG. 4. For illustrative purposes only, the signaling flow 500 may include a first device 410-1 and a second device 420.

[0056] The first device 410-1 may perform a random access procedure 5005 with the second device 420. In some embodiments, the first device 410-1 may perform a four-step random access procedure. Alternatively, the first device 410-1 may perform a two-step random access procedure.

[0057] In some embodiments, the second device 420 can configure a validity timer for the system broadcast information. In some embodiments, the system broadcast information can consist of GNSS position information provided by a global navigation satellite system. Alternatively or additionally, the system broadcast information can consist of GNSS timestamp information provided by a global navigation satellite system. In this case, the second device 420 can transmit a configuration 5010 of the validity timer to the first device 410-1. For example, the configuration can indicate a period of the validity timer. In other embodiments, the validity timer can be pre-configured in the first device 410-1. In some embodiments, the validity timer can be a UE-specific timer. In this case, the validity timer configuration may be transmitted to the first device 410-1 via radio resource control (RRC) signaling. Alternatively, or in addition, the validity timer may be common to the UEs. In this situation, the validity timer configuration may be broadcast to one or more first devices. In other embodiments, the second device 420 may transmit a configuration indicating a threshold accuracy of the system broadcast information. Alternatively or additionally, the configuration may indicate an update periodicity of the validity information.

[0058] In some embodiments, the duration of the timer may be determined based on a signal-to-noise ratio (SNR) between the first device 410-1 and the second device 420. Alternatively or additionally, the duration of the timer may be determined based on a quality of a channel between the first device 410-1 and the second device 420.

[0059] The first device 410-1 triggers a validity timer 5015. As used herein, the term "validity timer" refers to a timer for which the system broadcast information should be valid in order to derive time and / or frequency domain compensation. For example, in some embodiments, when the validity timer is running, the system broadcast information should be valid for estimating a timing advance. Alternatively, or in addition, the system should be valid for estimating a frequency shift when the validity timer is running. In some embodiments, the validity timer may be triggered at the first time that the first device 410-1 receives valid system broadcast information. In some embodiments, the validity timer may be implicitly triggered after a random access procedure is successfully completed. In some embodiments, the first device 410-1 may send an explicit instruction to trigger another validity timer in the second device 420. In this way, system performance is guaranteed.

[0060] The second device 420 triggers another validity timer 5020 in the second device 420. In some embodiments, the first device 410-1 can send a start instruction to the second device, and the second device 420 can trigger the other validity timer based on the start instruction. The second device 420 can trigger the other validity timer based on the instruction. The instruction may be implicit or explicit. For example, in some embodiments, the other validity timer can be implicitly triggered after a random access procedure is successfully completed. In some embodiments, to ensure that the validity timers of the first device 410-1 and the second device 420 are started, reset, and stopped simultaneously, the first device 410-1 can apply an offset to its validity timer. The offset can be a value that takes into account RTT and processing delays. The validity timer in the first device 410-1 and the other validity timer in the second device 420 can be started simultaneously.

[0061] The first device 410-1 determines whether the system broadcast information is valid 5025. In some embodiments, the first device 410-1 can determine whether the system broadcast information is valid prior to the start of a validity timer. Alternatively, the first device 410-1 can determine whether the system broadcast information is valid within a validity timer. In other embodiments, the first device 410-1 can determine whether the system broadcast information is valid periodically. In some embodiments, the first device 410-1 can determine a change in signal power from GNSS information provided by a global navigation satellite system. If the change exceeds a threshold change, the first device 410-1 can determine that the system broadcast information is invalid. The threshold change may be different for time domain compensation and frequency domain compensation. In other embodiments, the first device 410-1 can monitor a current TA level. In this case, if the difference between the estimates of TA based on the system broadcast information is equal to or greater than a threshold, the system broadcast information is invalid. Alternatively, if the estimate of TA based on the system broadcast information shows a large step, it means that the estimate of the location or timestamp is incorrect. In other embodiments, if the difference between the system broadcast information based estimates of the frequency shift is equal to or greater than a threshold, the system broadcast information is invalid. By way of example only, the first device 410-1 may determine the accuracy of the system broadcast information. For example, if the system broadcast information is a GNSS, the first device 410-1 may determine the accuracy of the GNSS. In this case, if the accuracy of the GNSS exceeds a threshold accuracy, the first device 410-1 may determine that the GNSS is valid.

[0062] If the system broadcast information is valid, the first device 410-1 transmits validity information 5035 indicating that the system broadcast information is valid. In some embodiments, the second device 420 may transmit a request 5030 for validity information. The first device 410-1 may transmit the validity information after receiving the request. Alternatively, the first device 410-1 may transmit the validity information periodically. For example, the validity information may be transmitted at a predetermined period. The predetermined period may be determined by the first device 410-1. Alternatively, the predetermined period may be determined by the second device 420. In other embodiments, the first device 410-1 may transmit the validity information on demand to ensure that other validity timers in the second device 420 have not expired. In other embodiments, the first device 410-1 may transmit the validity information if a condition is met that changes the validity of the system broadcast information. For example, if the first device 410-1 moves from indoors to outdoors, the first device 410-1 may transmit the validity information. It should be noted that the condition may be any suitable condition that may change the validity of the system broadcast information. In this manner, the estimation accuracy of the TA and / or frequency shift is ensured. After the first device 410-1 transmits the validity information, it resets the validity timer 5040.

[0063] In some embodiments, the validity information may indicate that the system broadcast information is valid for TA estimation. Alternatively or additionally, the validity information may indicate more validity status. For example, the validity information may indicate that the system broadcast information is valid for frequency compensation. The validity information may include an indication of whether the system broadcast information is valid for compensation in the time domain. In other embodiments, the validity information may comprise an indication of whether the system broadcast information is valid for compensation in the frequency domain. Alternatively or additionally, the validity information may comprise a timing advance currently being used. In other embodiments, the validity information may comprise a frequency shift currently being used. The validity information may also indicate the last time that accurate system broadcast information was received by the first device 410-1.

[0064] In some embodiments, the validity information may be transmitted in a Medium Access Control (MAC) control element (CE). The MAC CE may be transmitted in a Physical Uplink Shared Channel (PUSCH). For example, the MAC CE may be transmitted in uplink control information. Alternatively, the validity information may be transmitted together with other transmissions, which may save energy. For example, the validity information may be transmitted in a Channel Quality Indicator (CQI) report.

[0065] In some embodiments, the validity information may be transmitted in a scheduling request (SR). Alternatively or additionally, the validity information may be transmitted in a hybrid automatic repeat request (HARQ) feedback. In other embodiments, the validity information may be transmitted in other UL transmissions. For example, the validity information may be transmitted in RRC signaling between the first device 410-1 and the second device 420. The validity information may be transmitted implicitly. For example, if the SR transmitted by the first device 410-1 is sufficiently time-aligned with the second device 420, the second device 420 may determine that the system broadcast information is valid. Similarly, if the HARQ feedback or UL transmission is time-aligned with the second device 420, the system broadcast information may be determined to be valid. After the second device 420 determines that the system broadcast information is valid, the second device 420 may reset a timer at the second device 420.

[0066] In some embodiments, the first device 410-1 may determine the accuracy of the system broadcast information. If the accuracy of the system information is less than a threshold accuracy, the first device 410-1 may suspend the transmission of validity information to the second device 420. Alternatively or additionally, the first device 410-1 may stop transmission between the first device 410-1 and the second device 420. For example, the first device 410-1 may stop data transmission to the second device 420. Alternatively, the first device 410-1 may stop random access to the second device 420. In some embodiments, if a change in an estimated timing advance based on the system broadcast information exceeds a threshold change, the accuracy of the system broadcast information may be determined to be below the threshold accuracy. For example, the first device may monitor a current TA level, and if the estimates estimated based on the system broadcast information suddenly differ by more than a threshold, the accuracy is reduced. Alternatively, if an estimated timing advance based on the system broadcast information indicates a step that exceeds a threshold, the accuracy of the system broadcast information may be determined to be below the threshold accuracy. For example, if the TA estimated based on the system broadcast information shows a large step compared to a previously estimated TA value or within a time window, it means that the location or timestamp estimation is incorrect. In other embodiments, when the first device 410-1 moves from outdoors to indoors, the accuracy of the system broadcast information may be determined to be less than a threshold accuracy. As described above, the threshold accuracy may be provided to the first device 410-1 by the second device 420.

[0067] Additionally, the first device 410-1 may detect that the system broadcast information is inaccurate, for example, if the first device 410-1 moves indoors. In this case, if the validity timer is still running, the first device 410-1 may apply a previously valid TA (e.g., within the past x seconds) for the uplink transmission instead of using a value derived from the inaccurate system broadcast information obtained at the indoor location, because the previous system broadcast information associated with the previously valid TA is valid, but the currently system broadcast information is incorrect.

[0068] In another embodiment, if the accuracy of the system broadcast information exceeds a threshold accuracy, The first device 410-1 can send an instruction to the second device 420 to restart other validity timers in the second device 420. In this situation, the first device 410-1 can also reset the validity timer in the first device 410-1. For example, a timer recovery mechanism can be defined in the first device 410-1. For example, when the first device 410-1 moves from indoors to outdoors, it can be determined that the accuracy of the system broadcast information is restored. In this case, the first device 410-1 can send a notification to the network to reset other validity timers in the second device 420. In addition, after sending the validity information, the validity timer of the first device 410-1 can also be reset.

[0069] In some embodiments, if the validity timer in the first device 410-1 expires, the first device 410-1 may stop data transmission to avoid interference to other devices. In this case, the first device 410-1 may select one or more PRACH resources reserved for the UE without pre-compensation function. The first device 410-1 may initiate another random access procedure 5045 with the second device 420.

[0070] In addition to TA estimation, a validity timer can also be utilized to cover that the system broadcast information is valid to achieve UL frequency synchronization. The first device 410-1 can maintain a validity timer and send validity information to the second device 420 when the system broadcast information is valid for both TA estimation and UL frequency synchronization, in order to synchronize with the second device 420 that the system broadcast information is valid for both TA estimation and UL frequency synchronization. In the case of UL frequency synchronization, if the validity timer expires in the first device 410-1, the first device 410-1 should not perform random access again to avoid UE-to-UE interference in the PRB (frequency domain). Similarly, if the validity timer expires in the second device 420, the second device 420 can choose not to transmit a PDCCH order and ask the first device 410-1 to perform PRACH again.

[0071] In some embodiments, if another validity timer expires at the second device 420, the second device 420 may stop scheduling the first device 410-1 for UL transmission. In addition, the second device 420 may transmit a PDCCH order to initiate another random access procedure. As described above, the first device 410-1 may perform a PRACH again as a UE without valid system broadcast information, and the first device 410-1 may select a PRACH resource reserved for UEs without GNSS information (i.e., UEs without pre-compensation capability).

[0072] In some embodiments, in response to the estimated TA drift based on the uplink reception, the second device 420 may also transmit a MAC level command toward the first device 410-1 to initiate a timing adjustment based on the system broadcast information earlier than the expiration of the validity timer. For example, in a scenario in which the first device 410-1 is also moving at high speed with NTN cell mobility, such as at sea or in a high-speed rail scenario, the second device 420 may transmit an instruction to the first device 410-1 to initiate a timing adjustment based on the system broadcast information before the expiration of the validity timer. Alternatively or additionally, the second device 420 may transmit an instruction to the first device 410-1 to initiate a frequency adjustment based on the system broadcast information.

[0073] In some embodiments, the second device 420 may include one additional bit in the TA command MAC IE to indicate that the first device 410-1 triggers timing synchronization based on system broadcast information in connected mode. In this case, if the first device 410-1 cannot operate GNSS and cellular radio simultaneously (e.g., IoT or enhanced mobile broadband (eMBB)), the second device 420 may also create a scheduling gap to complete GNSS operation.

[0074] The embodiments of the present disclosure can avoid UE-to-UE interference in UL transmission (e.g., PUSCH) when the system broadcast information is unreliable, so as to facilitate NW work well and ensure system performance. The embodiments of the present disclosure can also enable the UE to access the system again when the system broadcast information is not available, and thus enable the UE to be served again in the system. The embodiments of the present disclosure introduce a dedicated system broadcast information availability guard timer and periodic check timer in the UE, as well as a NW control mechanism with parameters regarding how the UE detects that the accuracy of the system broadcast information has decreased.

[0075] 6 illustrates a flowchart of an example method 600 according to some example embodiments of the present disclosure. For purposes of discussion, the method 600 will be described from the perspective of the first device 410.

[0076] In some embodiments, the first device 410-1 may determine whether the first device 410-1 has valid system broadcast information before transmitting Msg1 in block 610. If there is no valid system broadcast information, the first device 410-1 may access the second device 420 in block 620 using PRACH resources reserved for UEs without valid system broadcast information.

[0077] If there is valid system broadcast information, the first device 410-1 may access the second device 420 using the PRACH resources reserved for the UE with the system broadcast information, in block 630. In some embodiments, the first device 410-1 may perform a four-step random access procedure. Alternatively, the first device 410-1 may perform a two-step random access procedure.

[0078] In some embodiments, the second device 420 can configure a validity timer for the system broadcast information. In some embodiments, the system broadcast information can consist of GNSS position information provided by a global navigation satellite system. Alternatively or additionally, the system broadcast information can consist of GNSS timestamp information provided by a global navigation satellite system. In this case, the first device 410-1 can receive a configuration of the validity timer from the second device 420. For example, the configuration can indicate a period of the validity timer. In other embodiments, the validity timer can be pre-configured in the first device 410-1. In some embodiments, the validity timer can be a UE-specific timer. In this case, the configuration of the validity timer can be transmitted to the first device 410-1 via radio resource control (RRC) signaling. Alternatively, or in addition, the validity timer can be common to the UEs. In this situation, the configuration of the validity timer can be broadcast to one or more first devices.

[0079] In some embodiments, the duration of the timer may be determined based on a signal-to-noise ratio (SNR) between the first device 410-1 and the second device 420. Alternatively or additionally, the duration of the timer may be determined based on a quality of the channel between the first device 410-1 and the second device 420.

[0080] In block 640, the first device 410-1 triggers a validity timer. For example, in some embodiments, when the validity timer is running, the system broadcast information should be valid to estimate the timing advance. Alternatively or additionally, the system should be valid to estimate the frequency shift when the validity timer is running. In some embodiments, the validity timer may be triggered at the first time that the first device 410-1 receives valid system broadcast information. In some embodiments, the validity timer may be implicitly triggered after the random access procedure is successfully completed. In some embodiments, the first device 410-1 may send an explicit instruction to trigger another validity timer in the second device 420. In this way, system performance is guaranteed.

[0081] In some embodiments, in block 650, the first device 410-1 may determine whether a validity timer has expired. If the validity timer of the first device 410-1 has expired, the first device 410-1 may stop data transmission to avoid interference to other devices in block 660. In this case, the first device 410-1 may select one or more PRACH resources reserved for a UE without valid system broadcast information. The first device 410-1 may initiate another random access procedure with the second device 420.

[0082] If the validity timer in the first device 410-1 expires, in block 670, the first device 410-1 determines whether the system broadcast information is valid. In some embodiments, the first device 410-1 may determine a change in signal power from the second device 420. If the change exceeds a threshold change, the first device 410-1 may determine that the system broadcast information is invalid. The threshold change may be different for compensation in the time domain and compensation in the frequency domain. In other embodiments, the first device 410-1 may monitor a current TA level. In this case, if the difference between the estimates of TA based on the system broadcast information is equal to or greater than a threshold, the system broadcast information is invalid. Alternatively, if the estimate of TA based on the system broadcast information shows a large step, it means that the location or timestamp estimate is incorrect. In other embodiments, if the difference between the system broadcast information-based estimates of the frequency shift is equal to or greater than a threshold, the system broadcast information is invalid.

[0083] If the system broadcast information is valid, the first device 410-1 transmits validity information indicating that the system broadcast information is valid, at block 680. In some embodiments, the first device 410-1 may receive a request for validity information from the second device 420. The first device 410-1 may transmit the validity information after receiving the request. Alternatively, the first device 410-1 may transmit the validity information periodically. For example, the validity information may be transmitted at a predetermined period. The predetermined period may be determined by the first device 410-1. Alternatively, the predetermined period may be determined by the second device 420. In other embodiments, the first device 410-1 may transmit the validity information on demand to ensure that other validity timers in the second device 420 have not expired. In this way, the accuracy of the TA and / or frequency shift estimation is ensured. The first device 410-1 may reset the validity timer after transmitting the validity information.

[0084] In some embodiments, the validity information may indicate that the system broadcast information is valid for TA estimation. Alternatively or additionally, the validity information may indicate more validity status. For example, the validity information may indicate that the system broadcast information is valid for frequency compensation. The validity information may include an indication of whether the system broadcast information is valid for compensation in the time domain. In other embodiments, the validity information may consist of an indication of whether the system broadcast information is valid for compensation in the frequency domain. Alternatively or additionally, the validity information may consist of a timing advance currently being used. In other embodiments, the validity information may consist of a frequency shift currently being used. The validity information may also indicate the last time that accurate system broadcast information was received by the first device 410-1.

[0085] In some embodiments, the validity information may be transmitted in a Medium Access Control (MAC) control element (CE). The MAC CE may be transmitted in a Physical Uplink Shared Channel (PUSCH). For example, the MAC CE may be transmitted in uplink control information. Alternatively, the validity information may be transmitted together with other transmissions that may save energy. For example, the validity information may be transmitted in a Channel Quality Indicator (CQI) report.

[0086] In some embodiments, the validity information may be transmitted in a scheduling request (SR). Alternatively or additionally, the validity information may be transmitted in a hybrid automatic repeat request (HARQ) feedback. In other embodiments, the validity information may be transmitted in other UL transmissions. The validity information may be transmitted implicitly. For example, if the SR transmitted by the first device 410-1 is well time-aligned with the second device 420, the second device 420 may determine that the system broadcast information is valid. Similarly, if the HARQ feedback or UL transmission is time-aligned with the second device 420, the system broadcast information may be determined to be valid. In some embodiments, the validity information may be transmitted by RRC signaling transmitted between the first device 410-1 and the second device 420.

[0087] In some embodiments, the first device 410-1 can determine the accuracy of the system broadcast information. If the accuracy of the system broadcast information is less than a threshold accuracy, the first device 410-1 can stop sending validity information to the second device 420. In some embodiments, the first device can monitor the current TA level, and if the estimate based on the system broadcast information suddenly differs by more than a threshold, the accuracy is degraded. Alternatively, if the TA estimate based on the system broadcast information shows a large step, it means that the location or timestamp estimate is incorrect.

[0088] Additionally, the first device 410-1 may detect that the system broadcast information is inaccurate, for example, if the first device 410-1 moves indoors. In this case, if the validity timer is still running, the first device 410-1 may apply a previously valid TA (e.g., within the past x seconds) for uplink transmissions instead of using a value derived from the inaccurate system broadcast information.

[0089] In another embodiment, when the accuracy of the system broadcast information is restored, the first device 410-1 can send an instruction to the second device 420 to restart other validity timers in the second device 420. In this situation, the first device 410-1 can also reset the validity timer in the first device 410-1. For example, a timer recovery mechanism can be defined in the first device 410-1. For example, when the first device 410-1 moves from indoors to outdoors, it can be determined whether the accuracy of the system broadcast information is restored. In this case, the first device 410-1 can send a notification to the network to reset other expiration timers of the second device 420. After sending the validity information, the validity timer of the first device 410-1 can also be reset.

[0090] In addition to TA estimation, the validity timer can also be utilized to cover that the system broadcast information is valid to achieve UL frequency synchronization. In order to synchronize with the second device 420 that the system broadcast information is valid in both TA estimation and UL frequency synchronization in the first device 410-1, the first device 410-1 can maintain a validity timer and send validity information to the second device 420 when the system broadcast information is valid for both TA estimation and UL frequency synchronization. In the case of UL frequency synchronization, if the validity timer expires in the first device 410-1, the first device 410-1 should not RACH again to avoid UE-to-UE interference in the PRB (frequency domain). Similarly, if the validity timer expires in the second device 420, the second device 420 should not send a PDCCH order and ask the first device 410-1 to PRACH again.

[0091] 7 illustrates a flowchart of an example method 700 according to some example embodiments of the present disclosure. For purposes of discussion, the method 700 will be described from the perspective of the second device 420.

[0092] In some embodiments, in block 710, the second device 420 may determine whether a start indication has been received to start another validity timer in the second device 420. If a start indication has been received, the second device 420 may trigger the other validity timer in block 720. In some embodiments, the other validity timer may be triggered after the random access procedure is successfully completed. In some embodiments, the second device 420 may receive an indication to trigger the other validity timer. The second device 420 may trigger the other validity timer based on the indication. The indication may be implicit or explicit. In some embodiments, to ensure that the validity timers of the first device 410-1 and the second device 420 can be started, reset, and stopped simultaneously, the first device 410-1 may apply an offset to its validity timer. The offset may be a value that accounts for the RTT and processing delay.

[0093] In some embodiments, at block 730, the second device 420 may determine whether the other validity timer has expired. If the other validity timer has not expired, at block 740, the second device 410 determines whether it has received validity information indicating that the system broadcast information is valid. If the validity information is not received, the second device 420 may again determine whether the other validity timer has expired. If the validity information is received, the second device 420 may again trigger the other validity timer (i.e., reset the other validity timer). In some embodiments, the validity information may indicate that the system broadcast information is valid for TA estimation. Alternatively or additionally, the validity information may indicate more validity status. For example, the validity information may indicate that the system broadcast information is valid for frequency compensation. The validity information may include an indication of whether the system broadcast information is valid for compensation in the time domain. In other embodiments, the validity information may comprise an indication of whether the system broadcast information is valid for compensation in the frequency domain. Alternatively or additionally, the validity information may comprise a currently used timing advance. In other embodiments, the validity information may comprise a currently used frequency shift. The validity information may also indicate the last time that correct system broadcast information was received by the first device 410-1.

[0094] In some embodiments, the validity information may be received in a Medium Access Control (MAC) Control Element (CE). The MAC CE may be received on a Physical Uplink Shared Channel (PUSCH). For example, the MAC CE may be received in uplink control information. Alternatively, the validity information may be received along with other transmissions that may conserve energy. For example, the validity information may be received in a Channel Quality Indicator (CQI) report.

[0095] In some embodiments, the validity information may be received in a scheduling request (SR). Alternatively or additionally, the validity information may be received in a hybrid automatic repeat request (HARQ) feedback. In other embodiments, the validity information may be received in other UL transmissions. The validity information may be received implicitly. For example, if the SR transmitted by the first device 410-1 is well time-aligned with the second device 420, the second device 420 may determine that the system broadcast information is valid. Similarly, if the HARQ feedback or UL transmission is time-aligned with the second device 420, the system broadcast information may be determined to be valid. In some embodiments, the validity information may be transmitted by RRC signaling transmitted between the first device 410-1 and the second device 420.

[0096] In some embodiments, if the other validity timer expires, in block 750, the second device 420 may stop scheduling the first device 410-1 for UL transmission. Additionally, in block 760, the second device 420 may transmit a PDCCH order to initiate another random access procedure. In some embodiments, the second device 420 may include one additional bit in the TA command MAC IE to indicate that the first device 410-1 triggers timing synchronization based on system broadcast information in connected mode. In this case, if the first device 410-1 cannot operate GNSS and cellular radio simultaneously (e.g., IoT or enhanced mobile broadband (eMBB)), the second device 420 may also create a scheduling gap to complete GNSS operation.

[0097] In some exemplary embodiments, an apparatus capable of executing any of the methods 600 (e.g., the first device 410) may configure a means for performing each operation of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The first device may be implemented as the first device 410 or may be included in the first device 410. In some exemplary embodiments, the means may comprise at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to effectuate the performance of the apparatus.

[0098] In some embodiments, the apparatus comprises means for triggering, at a first device, a validity timer for system broadcast information used to derive compensation for transmission between the first device and a second device in the time domain and / or frequency domain, means for determining whether the system broadcast information is valid for compensation before expiration of the validity timer, means for transmitting validity information to the second device indicating that the system broadcast information is valid in response to a determination that the system broadcast information is valid, and means for resetting the validity timer.

[0099] In some embodiments, the means for transmitting the validity information comprises means for transmitting validity information based on one of the predetermined period, receiving a request for the validity information from the second device, or a condition that causes a validity of the system broadcast information to be changed being met.

[0100] In some embodiments, the validity information includes at least one of an indication of whether the system broadcast information is valid for compensation in the time domain, an indication of whether the system broadcast information is valid for compensation in the frequency domain, a timing advance currently being used, a frequency shift currently being used, or the last time accurate system broadcast information was received by the first device.

[0101] In some embodiments, the apparatus further comprises means for determining an accuracy of the system broadcast information and means for pausing at least one of transmission between the first device and the second device or stopping transmission of the validity information in accordance with a determination that the accuracy of the system broadcast information is less than a threshold accuracy.

[0102] In some embodiments, the apparatus further comprises means for applying a previously valid compensation in the time domain and / or frequency domain to a transmission between the first device and the second device in accordance with a determination that the accuracy of the system broadcast information falls below a threshold accuracy and the validity timer is running.

[0103] In some embodiments, the apparatus further comprises means for transmitting validity information to a second device and restarting a further validity timer at the second device in accordance with a determination that the accuracy of the system broadcast information exceeds a threshold accuracy, and means for resetting the validity timer at the first device.

[0104] In some embodiments, the apparatus indicates that a change in the estimated timing advance based on the system broadcast information exceeds a threshold change, indicates a step by which the estimated timing advance based on the system broadcast information exceeds a threshold step, or and a detected signal strength of the system broadcast information is below a threshold accuracy when at least one of the following conditions is met: the detected signal strength of the system broadcast information is below a threshold accuracy.

[0105] In some embodiments, the means for transmitting validity information comprises means for transmitting the validity information in at least one of a Medium Access Control (MAC) control element (CE), a scheduling request, a Hybrid Automatic Repeat Request (HARQ) feedback, or radio resource control signaling transmitted between the first device and the second device.

[0106] In some embodiments, the apparatus further comprises means for performing at least one of: stopping transmission to the second device or initiating random access to the second device in accordance with a determination that the validity timer has expired.

[0107] In some embodiments, the apparatus further comprises means for receiving a configuration from the second device indicating at least one of a validity timer time, a threshold accuracy of the system broadcast information, or a validity information update period.

[0108] In some embodiments, the apparatus further comprises means for receiving, prior to expiration of the validity timer, an indication from the second device to initiate a timing and / or frequency adjustment based on the system broadcast information.

[0109] In some embodiments, the apparatus further comprises means for applying an offset to the validity timer, the offset including at least a round trip time between the first device and the second device.

[0110] In some embodiments, the apparatus further comprises means for sending an implicit or explicit start indication to the second device to trigger another validity timer at the second device.

[0111] In some demonstrative embodiments, a second device (e.g., second device 420) capable of executing any of the methods 700 may comprise means for performing each operation of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The first device may be implemented as or included in the second device 320. In some demonstrative embodiments, the means may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the performance of the apparatus.

[0112] In some embodiments, the apparatus includes means for triggering, at the second device, a validity timer of system broadcast information used to derive compensation for transmissions between the first device and the second device in the time domain and / or frequency domain by the first device, means for receiving validity information from the first device indicating that the system broadcast information is valid, and means for resetting the validity timer.

[0113] In some embodiments, the apparatus further comprises means for sending a request for validity information to the first device.

[0114] In some embodiments, the validity information includes at least one of an indication of whether the system broadcast information is valid for compensation in the time domain, an indication of whether the system broadcast information is valid for compensation in the frequency domain, a timing advance currently being used, a frequency shift currently being used, or the last time accurate system broadcast information was received by the first device.

[0115] In some embodiments, the validity timer is triggered by an implicit or explicit start instruction received from the first device.

[0116] In some embodiments, the means for receiving the validity information comprises receiving the validity information in at least one of a Medium Access Control (MAC) control element (CE), a scheduling request, a Hybrid Automatic Repeat Request (HARQ) feedback, or RRC signaling between the first device and the second device.

[0117] In some embodiments, the apparatus further comprises means for transmitting to the first device a configuration indicating at least one of a duration of a validity timer, a threshold accuracy of the system broadcast information, or an update periodicity of the validity information.

[0118] In some embodiments, the apparatus further comprises means for determining a timing advance drift based on the transmission, and means for transmitting an instruction to the first device to initiate a timing adjustment and / or a frequency adjustment based on the system broadcast information according to a determination that the timing advance drift exceeds a threshold drift.

[0119] In some embodiments, the apparatus further comprises means for suspending scheduling of the first device in accordance with a determination that the validity timer has expired, and means for sending a Physical Random Access Channel (PRACH) command to the first device triggering the first device to perform random access to the second device.

[0120] 8 is a simplified block diagram of a device 800 suitable for implementing an exemplary embodiment of the present disclosure. The device 800 may be provided to implement a communication device, such as the first device 110 or the second device 120 as shown in FIG. 1. As shown, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.

[0121] The communication module 840 is for bidirectional communication. The communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communication with other network elements. In some exemplary embodiments, the communication module 840 may include at least one antenna.

[0122] The processor 810 may be of any type suitable for a local technology network and may include, by way of non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 800 may have multiple processors, such as application specific integrated circuit chips that are slaved in time to a clock that synchronizes a main processor.

[0123] The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, Read Only Memory (ROM) 824, Electrically Programmable Read Only Memory (EPROM), flash memory, hard disks, Compact Discs (CDs), Digital Video Discs (DVDs), optical disks, laser disks, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, Random Access Memory (RAM) 822 and other volatile memories that do not persist through power-down times.

[0124] The computer program 830 includes computer executable instructions that are executed by the associated processor 810. The program 830 may be stored in a memory, for example in the ROM 824. The processor 810 may load the program 830 into the RAM 822 to perform any suitable operations and processes.

[0125] An exemplary embodiment of the present disclosure may be implemented by a program 830 such that the device 800 may execute any process of the present disclosure, as discussed with reference to Figures 5 to 7. Also, an exemplary embodiment of the present disclosure may be implemented by hardware or a combination of software and hardware.

[0126] In some exemplary embodiments, the program 830 may be included in a computer-readable medium that may be included in the device 800 (such as in the memory 820) or in contact with other storage devices accessible by the device 800. The device 800 may load the program 830 from the computer-readable medium into the RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disks, CDs, DVDs, and other magnetic and / or optical storage devices. FIG. 9 shows an example of a computer-readable medium 900 in the form of an optical storage disk. The computer-readable medium has the program 830 stored thereon.

[0127] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. 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. Although various aspects of the embodiments of the present disclosure have been illustrated and described using block diagrams, flow charts, or some other pictorial representations, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers, or other computing devices, or any combination thereof.

[0128] The present disclosure also provides at least one computer program product tangibly stored in a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in a program module, that execute on a target physical or virtual processor device to perform any of the methods as described above with reference to Figures 3-8. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various embodiments. The machine-executable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0129] The program codes for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, a special purpose computer, or other programmable data processing apparatus, and when the program codes are executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program codes may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0130] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0131] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of the computer-readable storage medium include an electrical connection with one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0132] Furthermore, although operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or sequentially, or to perform all of the operations depicted, to achieve desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0133] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A first device comprising at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code being transmitted by the at least one processor to the first device, Triggering a validity timer of system broadcast information used to derive compensation for transmission between the first device and the second device in one of a time domain and a frequency domain; determining whether the system broadcast information is valid for the compensation before the validity timer expires; and transmitting validity information to the second device indicating that the system broadcast information is valid according to a determination that it is valid for the system to provide the information.

2. The at least one memory and the computer program code are configured to, using the at least one processor, transmit to the first device, for a predetermined period of time:

2. The first device of claim 1, configured to cause the validity information to be transmitted by transmitting the validity information based on one of a request for the validity information received from the second device or a state in which a condition for changing the validity of the system broadcast information is satisfied.

3. The efficacy information comprises: an indication of whether the system broadcast information is valid for the compensation in the time domain; an indication of whether the system broadcast information is valid for compensation in the frequency domain; Currently used timing advances, The currently used frequency shift, or the last time that accurate system broadcast information was received by the first device; At least one of: The first device of claim 1 .

4. The at least one memory and the computer program code further cause the first device, using the at least one processor, to: determining accuracy of the system broadcast information; suspending at least one of the transmission between the first device and the second device or the transmission of the validity information in response to a determination that the accuracy of the system broadcast information is less than a threshold accuracy. The first device of claim 1 configured to:

5. The at least one memory and the computer program code are further configured to cause the at least one processor to transmit to the first device: the accuracy of the system broadcast information is less than the threshold accuracy; configured to apply a previous valid compensation in any one of the time domain and the frequency domain to the transmission between the first device and the second device in accordance with a determination that the validity timer is running. The first device according to claim 4 .

6. The at least one memory and the computer program code are further transmitted by the at least one processor to the first device, transmitting the validity information to the second device to restart a further validity timer at the second device in response to a determination that the accuracy of the system broadcast information exceeds the threshold accuracy; resetting the validity timer at the first device The first device according to claim 4 , configured to:

7. The at least one memory and the computer program code are configured to, by the at least one processor: a change in an estimated timing advance based on the system broadcast information exceeds a threshold change; and indicating a step at which the estimated timing advance exceeds a threshold step based on the system broadcast information; a detected signal strength of the system broadcast information falling below a threshold; and and causing the first device to determine that the accuracy of the system broadcast information is less than the threshold accuracy if at least one of the following is satisfied: The first device according to claim 4 .

8. The at least one memory and the computer program code are configured to cause the at least one processor to transmit to the first device: said validity information being a medium access control (MAC) control element (CE); Scheduling requests, Hybrid Automatic Repeat Request (HARQ) feedback; Radio resource control signaling transmitted between the first device and the second device; and causing the validity information to be transmitted by transmitting in at least one of The first device of claim 1 .

9. The at least one memory and the computer program code further cause the first device, using the at least one processor, to: ceasing the transmission to the second device in response to a determination that the validity timer has expired; and initiating random access to the second device; configured to execute at least one of The first device of claim 1 .

10. The at least one memory and the computer program code are further adapted to transmit, using the at least one processor, to the first device and from the second device: the duration of the validity timer; a threshold accuracy of the system broadcast information; Update periodicity of efficacy information, configured to receive a configuration indicative of at least one of The first device of claim 1 .

11. The at least one memory and the computer program code further cause the first device, using the at least one processor, to: and receiving, prior to expiration of a validity timer, an indication from the second device to initiate one of a timing adjustment and a frequency adjustment based on the system broadcast information. The first device of claim 1 .

12. The at least one memory and the computer program code further cause the first device, using the at least one processor, to: configured to apply an offset to the validity timer; the offset includes at least a round trip time between the first device and the second device. The first device of claim 1 .

13. The at least one memory and the computer program code are further adapted to transmit, using the at least one processor, to the first device and to the second device: and causing an implicit or explicit start instruction to be sent to trigger another validity timer at the second device. The first device of claim 1 .

14. The first device according to claim 1 , wherein the first device is a terminal device and the second device is a network device.

15. a second device comprising at least one processor and at least one memory containing computer program code, The at least one memory and the computer program code are configured to cause the second device, using the at least one processor, to: Triggering a validity timer for system broadcast information used to derive compensation for transmissions between the first device and the second device in one of a time domain and a frequency domain by a first device; receiving validity information from the first device, the validity information indicating that the system broadcast information is valid; A second device configured to execute the

16. The at least one memory and the computer program code further cause the second device, using the at least one processor, to: and configured to cause the step of transmitting the request for validity information to the first device. The second device of claim 15.

17. The efficacy information comprises: an indication of whether the system broadcast information is valid for the compensation in the time domain; an indication of whether the system broadcast information is valid for the compensation in the frequency domain; Currently used timing advances, Currently used frequency shifts, the last time that accurate system broadcast information was received by the first device; At least one of: The second device of claim 15.

18. The second device of claim 15 , wherein the validity timer is triggered by an implicit or explicit start indication received from the first device.

19. The at least one memory and the computer program code, using the at least one processor, transmit the validity information to the second device: a Medium Access Control (MAC) Control Element (CE); Scheduling requests and Hybrid Automatic Repeat Request (HARQ) feedback; a radio resource control signal transmitted between the first device and the second device; and further configured to receive the validity information by receiving in at least one of the following steps: The second device of claim 15.

20. The at least one memory and the computer program code are used to transmit, using the at least one processor, to the second device, to the first device, the duration of the validity timer; a threshold accuracy of the system broadcast information; and The update cycle of the validity information; and further configured to cause transmission of a configuration indicative of at least one of: The second device of claim 15.

21. The at least one memory and the computer program code, using the at least one processor, further configure the second device to: determining a timing advance drift based on said transmission; and transmitting, to the first device, an instruction to initiate one of a timing adjustment and a frequency adjustment based on the system broadcast information in response to a determination that the timing advance drift exceeds a threshold. It is configured as follows: The second device of claim 15.

22. The at least one memory and the computer program code further cause the second device, using the at least one processor, to: suspending scheduling of the first device in response to a determination that the validity timer has expired; or causing the first device to transmit a physical random access channel (PRACH) command that triggers the first device to perform random access to the second device; It is configured as follows: The second device of claim 15.

23. The second device according to any one of claims 15 to 22, wherein the first device is a terminal device and the second device is a network device.

24. Triggering, at a first device, a validity timer for system broadcast information used to derive compensation for transmissions between the first device and a second device in one of a time domain and a frequency domain; determining whether the system broadcast information is valid for the compensation before expiration of the validity timer; According to a determination that the system is valid for providing information, transmitting validity information to the second device indicating that the system broadcast information is valid; The method includes:

25. At least one memory and computer program code for executing, using at least one processor, A prescribed period of time; a request received from a second device for validity information; and a condition that, when met, causes a change in the validity of the system broadcast information; causing the first device to transmit the validity information by transmitting the validity information based on one of 25. The method of claim 24.

26. The efficacy information comprises: an indication of whether the system broadcast information is valid for the compensation in the time domain; and an indication of whether the system broadcast information is valid for the compensation in the frequency domain; The currently used timing advance and The currently used frequency shifts and the last time that accurate system broadcast information was received by the first device; At least one of:

25. The method of claim 24.

27. determining accuracy of the system broadcast information; suspending at least one of the transmission between the first device and the second device and the transmission of the validity information in response to a determination that the accuracy of the system broadcast information is less than a threshold accuracy; Further comprising:

25. The method of claim 24.

28. 28. The method of claim 27, further comprising: applying a previous valid compensation in any one of the time domain and the frequency domain to the transmission between the first device and the second device in accordance with a determination that the accuracy of the system broadcast information is less than the threshold accuracy and the validity timer is running.

29. transmitting the validity information to the second device for restarting a further validity timer at the second device in accordance with a determination that the accuracy of the system broadcast information exceeds the threshold accuracy; resetting the validity timer at the first device; Further comprising:

28. The method of claim 27.

30. a change in an estimated timing advance based on the system broadcast information exceeds a threshold change; and indicating a step at which the estimated timing advance exceeds a threshold step based on the system broadcast information; a detected signal strength of the system broadcast information falls below a threshold; and is satisfied, the accuracy of the system broadcast information is less than a threshold accuracy.

28. The method of claim 27.

31. The step of transmitting the validity information further comprises: a medium access control (MAC) control element (CE); A scheduling request; Hybrid Automatic Repeat Request (HARQ) feedback; and radio resource control signaling transmitted between the first device and the second device; transmitting in at least one of 25. The method of claim 24.

32. ceasing the transmission to the second device in accordance with a determination that the validity timer has expired; initiating random access to the second device; performing at least one of the following steps:

25. The method of claim 24, further comprising:

33. From the second device, the duration of the validity timer; a threshold accuracy of the system broadcast information; and Update periodicity of efficacy information receiving a configuration indicative of at least one of:

25. The method of claim 24.

34. From the second device, receiving, prior to expiration of the validity timer, an indication to initiate one of a timing adjustment and a frequency adjustment based on the system broadcast information.

25. The method of claim 24, further comprising:

35. 25. The method of claim 24, further comprising applying an offset to the validity timer, the offset including at least a round trip time between the first device and the second device.

36. 25. The method of claim 24, further comprising sending an implicit or explicit start indication to the second device to trigger another validity timer at the second device.

37. 37. The method of any one of claims 24 to 36, wherein the first device is a terminal device and the second device is a network device.

38. In the second device, Triggering a validity timer for system broadcast information used to derive compensation for transmissions between the first device and the second device in one of a time domain and a frequency domain by a first device; receiving validity information from the first device, the validity information indicating that the system broadcast information is valid; The method includes:

39. 40. The method of claim 38, further comprising the step of sending the request for validity information to the first device.

40. The efficacy information comprises: an indication of whether the system broadcast information is valid for the compensation in the time domain; and an indication of whether the system broadcast information is valid for the compensation in the frequency domain; The currently used timing advance and The currently used frequency shifts and the last time accurate system broadcast information was received by the first device; At least one of:

39. The method of claim 38.

41. 40. The method of claim 38, wherein the validity timer is triggered by an implicit or explicit start indication received from the first device.

42. The step of receiving the validity information includes: said validity information being transmitted to a medium access control (MAC) control element (CE); Scheduling requests, Hybrid Automatic Repeat Request (HARQ) feedback; radio resource control signaling transmitted between the first device and the second device; receiving at least one of the 39. The method of claim 38.

43. The first device, the duration of the validity timer; a threshold accuracy of the system broadcast information; and Update periodicity of efficacy information, transmitting a configuration indicating at least one of:

39. The method of claim 38.

44. determining a timing advance drift based on the transmission; in response to determining that the timing advance drift exceeds a threshold drift, transmitting an instruction to the first device to initiate one of a timing adjustment and a frequency adjustment based on the system broadcast information; 40. The method of claim 38, further comprising:

45. suspending scheduling of the first device in response to a determination that the validity timer has expired; or sending, to the first device, a Physical Random Access Channel (PRACH) order triggering the first device to perform random access to the second device; Further comprising:

39. The method of claim 38.

46. 46. ​​The method of any one of claims 38 to 45, wherein the first device is a terminal device and the second device is a network device.

47. Apparatus comprising at least means for carrying out the method according to any one of claims 24 to 37 or the method according to any one of claims 38 to 46.

48. A computer program product for causing an apparatus to execute a computer process on a first device, the computer program product comprising: Triggering a validity timer for system broadcast information used to derive compensation for transmissions between the first device and the second device in one of a time domain and a frequency domain; determining whether the system broadcast information is valid for the compensation before expiration of a validity timer; According to a determination that the system is valid for providing information, transmitting validity information to the second device indicating that the system broadcast information is valid; A computer program comprising:

49. A computer program product for causing an apparatus to execute a computer process on a second device, the computer program product comprising: Triggering a validity timer for system broadcast information used to derive compensation for transmissions between the first device and the second device in one of a time domain and a frequency domain by the first device; receiving validity information from a first device, the validity information indicating that the system broadcast information is valid; A computer program comprising:

Images