This document is directed generally to wireless communications.
In non-terrestrial networks, a relative distance between a base station (BS) and a user equipment (UE) may drastically change because of the movement of the BS and/or the UE.
Meanwhile, in a terrestrial network, although the change of the relative distance is limited (the relative distance may still change especially when UE moves with high speed and/or a relay node (e.g. integrated access and backhaul(IAB) node) has mobility), reference signal (RS) and signal design with larger overhead may be also needed to maintain the synchronization regarding the time and frequency for both DL and UL.
This document relates to methods, systems, and devices for synchronization, and more particularly to methods, systems, and devices for synchronization in both non-terrestrial network and terrestrial network.
The present disclosure relates to a wireless communication method for use in a wireless terminal, the wireless communication method comprising:
determining at least one synchronization value, and
transmitting, to a wireless network node, a signal based on the at least one synchronization value.
Various embodiments may preferably implement the following features:
Preferably, the at least one synchronization value comprises at least one of a timing advanced value or a frequency offset.
Preferably, the frequency offset is quantized by one of a sub-carrier spacing or a channel raster.
Preferably, the synchronization value is determined based on information received from the wireless network node, wherein the information includes at least one component of at least one of:
timing information related to transmissions from the wireless network node to the wireless terminal,
status information of the wireless network node,
timing advanced value obtained at the wireless network node,
timing advanced value drift rate obtained at the wireless network node,
Doppler drift obtained at the wireless network node, or
Doppler drift rate obtained at the wireless network node.
Preferably, the wireless communication method further comprises transmitting, to the wireless network node, a request for the information
Preferably, the information comprises at least one differential component corresponding to the at least one status value.
Preferably, the signal comprises at least one of a message for random access procedure, physical uplink shared channel scheduled by the wireless network node, physical uplink shared channel scheduled by the wireless network node, or periodic uplink resource configured by the wireless network node.
Preferably, the transmitting, to the wireless network node, the signal based on the at least one synchronization value comprises:
transmitting, to the wireless network node, the signal by applying the at least one synchronization value.
Preferably, the at least one synchronization value is applied for transmitting the signal after the at least one synchronization value is determined.
Preferably, the synchronization value applied for transmitting the signal comprises at least one of:
a synchronization value determined a time offset before transmitting the signal,
a synchronization value determined the time offset before receiving scheduling information for transmitting the signal, or
a synchronization value reported to the wireless network before receiving the scheduling information for transmitting the signal.
Preferably, the transmission of the signal comprises a plurality of transmission parts, wherein each of the plurality of transmission parts is transmitted by applying one of the at least one synchronization value.
Preferably, a gap is inserted between two contiguous transmission parts.
Preferably, the gap between two contiguous transmission parts is larger than a threshold.
Preferably, a time length of each of the plurality of transmission parts is smaller than a duration threshold.
Preferably, a valid time of applying each of the at least one synchronization value is smaller than a valid time threshold.
Preferably, the transmitting, to the wireless network node, the signal based on the at least one synchronization value comprises:
transmitting, to the wireless network node, the at least one synchronization value carried in the signal.
Preferably, the transmitting the signal carrying at least one synchronization value comprises at least one of:
transmitting the signal carrying at least one synchronization value in response to a request received from the wireless network node,
transmitting the signal carrying at least one synchronization value in response to a configuration received from the wireless network node, or
transmitting the signal carrying at least one synchronization value in a random access procedure.
Preferably, the at least one synchronization value is transmitted in the signal a time offset after the at least one synchronization value is determined.
Preferably, transmitting the at least one synchronization value does not collide with other channel transmissions.
Preferably, the signal comprises a random access message, wherein at least one of the first synchronization value or the last synchronization value applied for transmitting the random access message is carried in data part of random access message.
Preferably, the synchronization value applied for transmitting the signal is carried in the signal.
Preferably, the latest synchronization value applied for transmitting the signal is carried in the signal.
Preferably, the synchronization value determined a time offset before transmitting the signal is carried in the signal.
Preferably, the synchronization value determined a time offset before receiving scheduling information for transmitting the signal is carried in the signal.
Preferably, the latest determined synchronization value is carried in the signal.
The present disclosure relates to a wireless communication method for use in a wireless network node. The wireless communication method comprises:
receiving, from a wireless terminal, at least one synchronization value, and
scheduling, for the wireless terminal, uplink resources by applying the at least one synchronization value.
Various embodiments may preferably implement the following features:
Preferably, the at least one synchronization value comprises at least one of a timing advanced value or a frequency offset.
Preferably, the frequency offset is quantized by one of a sub-carrier spacing or a channel raster.
Preferably, the at least one synchronization value is carried in at least one of a message for random access procedure, physical uplink shared channel scheduled by the wireless network node, physical uplink shared channel scheduled by the wireless network node, or periodic uplink resource configured by the wireless network node.
Preferably, the synchronization value applied for scheduling the uplink resources is used a time offset after the synchronization value is received.
Preferably, the uplink resources are scheduled based on the latest synchronization value received from the wireless terminal.
The present disclosure relates to a wireless terminal. The wireless terminal comprises:
a processor, configured to determine at least one synchronization value, and
a communication unit, configured to transmit, to a wireless network node, a signal based on the at least one synchronization value.
Various embodiments may preferably implement the following feature:
Preferably, the processor is configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a wireless network node. The wireless network node comprises:
a communication unit, configured to receive, from a wireless terminal, at least one synchronization value, and
a processor, configured to schedule, for the wireless terminal, uplink resources by applying the at least one synchronization value.
Various embodiments may preferably implement the following feature:
Preferably, the processor is configured to perform a wireless communication method of any of the foregoing described methods.
The present disclosure relates to a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method of any of the foregoing described methods.
The exemplary embodiments disclosed herein are directed to providing features that will become readily apparent by reference to the following description when taken in conjunction with the accompany drawings. In accordance with various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure.
Thus, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.
In an embodiment, the storage unit 210 and the program code 212 may be omitted and the processor 200 may include a storage unit with stored program code.
The processor 200 may implement any one of the steps in exemplified embodiments on the wireless terminal 20, e.g., by executing the program code 212.
The communication unit 220 may be a transceiver. The communication unit 220 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g. a base station).
In an embodiment, the storage unit 310 and the program code 312 may be omitted. The processor 300 may include a storage unit with stored program code.
The processor 300 may implement any steps described in exemplified embodiments on the wireless network node 30, e.g., via executing the program code 312.
The communication unit 320 may be a transceiver. The communication unit 320 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless terminal (e.g. a user equipment).
In present disclosure, embodiments are exemplified for reciting how to calculate value(s) for synchronization (e.g. synchronization value(s)) by UE itself based on assistance information received from the BS. Note that, skilled person in the art should acknowledge that the embodiments may be implemented individually or in potential combinations.
In this embodiment, the value(s) for synchronization (e.g., for UL synchronization) is obtained (e.g. determined, calculated) based on the self-calculation at the UE side. After acquiring the value(s) for synchronization (e.g. timing advanced (TA) value(s) and/or frequency offset(s)), the UE applies the calculated value for corresponding UL transmission. In an embodiment, the UL transmission may comprise physical random access channel (PRACH), physical UL control channel (PUCCH), sounding reference signal (SRS), physical UL shared channel (PUSCH), etc. For example, the UL transmission may include Msg-A of a 2-step random access procedure, the PUSCH scheduled by DL control information (DCI), the PUSCH scheduled by a RACH response, and/or pre-configured PUSCH (e.g. periodic PUSCH). In addition, the UE may report the calculated value for synchronization to the BS.
In an embodiment, the UE may calculate (e.g. determine, obtain, acquire) the TA value(s) for synchronization based on timing information received from the BS. In an embodiment, the timing information may be related to transmissions from the BS to the UE. For example, the timing information may be an instant of either the beginning or ending of the sub-frame number (SFN), slot, half frame, or symbol carried in each transmission. In an embodiment, the timing information may be timing reference information (e.g., time stamp) or status information of the BS.
In an embodiment, the status information comprises location, mobility status, confidence level for each information, etc.
In an embodiment, the timing information may be included in contents of some channels (e.g. system information, physical DL shared channel (PDSCH) and physical DL control channel (PDCCH)).
In an embodiment, the timing information may be sent periodically from the BS, e.g., in dedicated system information.
In an embodiment, the timing information is associated to each PDSCH. In this embodiment, the PDSCH may be UE-specified PDSCH scheduled with UE specific DL control information (DCI) and/or group-specified PDSCH scheduled with common PDCCH.
In an embodiment, the timing information is associated to the PDCCH (i.e. DCI). For example, the timing information may be directly included within the DCI. In another example, partial of the timing information is included in the DCI. In an embodiment, the partial of the timing information may comprise only values of fine-scale time units (e.g. second, millisecond and/or nano-second). That is, values of coarse-scale time units (e.g. day, month and/or year) may not be transmitted to the UE, so as to reduce signal overhead. In an embodiment, an indicator for indicating whether additional information (e.g. DCI) is used for scheduling the PDSCH with timing information is included.
In an embodiment, the timing information is divided into different components according to the granularity of indicated time units.
In an embodiment, the timing information may consist of fine-scale time units (e.g. second, millisecond and/or nano-second) and coarse-scale time units (e.g., day, month and/or year).
In an embodiment, the fine-scale time units and/or the coarse-scale time units may be determined according to requirements of wireless network (e.g. sub-carrier spacings used for transmitting and/or configuring resources).
In an embodiment, different components of the timing information refer to different parts of one bit string for time indication. For example, the components with the fine-scale time units may correspond to (e.g. indicated by) the LSB (least significant bit) part of one bit string. In another example, the components with the coarse scale time units may correspond to the MSB (most significant bit) part of one bit string.
In an embodiment, different components of the timing information are indicated by different bit strings for time indication.
In an embodiment, the different components of timing information are transmitted to UE with different periodicities. For example, the component with fine-scale time units may be transmitted in a periodicity P1 and the component with coarse-scale time units may be transmitted in a periodicity P2, where P1 is smaller than P2.
In an embodiment, the component corresponding to the coarse-scale granularity for time indication is indicated by system information.
In an embodiment, the component corresponding to the fine-scale granularity for time indication is indicated by PDCCH (i.e. DCI).
In an embodiment, the component corresponding to the fine-scale granularity for time indication is indicated by PDSCH.
In an embodiment, the timing information may be sent in response to a request from the UE.
In an embodiment, different timing components may be sent in response to corresponding requests from the UE.
In an embodiment, only the timing component with fine-scale granularity for time indication may be sent in response to a corresponding request from the UE.
In an embodiment, the timing information refers to absolutely timing for each transmission instant (e.g., starting or ending point of slot, sub-frame and frame).
After receiving the timing information, the UE is able to calculate the TA value itself.
In an embodiment, the TA value is determined by:
TA=(T1−T0)×2
In an embodiment, the TA value is determined by:
TA=(T1−T0)×2−reference TA
where the reference TA may be a required TA adjustment which is indicated by the BS.
In an embodiment, the calculated TA value may be quantized by a certain time unit.
In an embodiment, the UE may calculate (e.g. determine) TA value(s) and/or frequency offset(s) (e.g. Doppler drift) based on information received from the BS. For example, the information used for calculating the TA values and/or the frequency offsets may be status information, which is indicated from the BS.
In an embodiment, the frequency offset may be quantized by a sub-carrier spacing (SCS) or a channel raster. Note that, the SCS may refer to the SCS used for corresponding UL transmission or the minimum value among simultaneously transmitted UL signal cross different bandwidth parts (BWPs) or component carriers (CCs).
In an embodiment, the information used for calculating the TA value(s) and the frequency offset may comprise reference information and differential information, wherein the reference information comprises reference value(s) and the differential information comprises differential component(s) corresponding to the reference value(s). For example, the BS may firstly transmit the reference information comprising a reference value to the UE. Next, the BS may transmit the differential information comprising a differential component which indicates a differential change from the reference value.
In an embodiment, the UE calculates the TA values based on at least one of:
A) TA value obtained at and/or indicated from the BS
B) TA value drift rate obtained at and/or indicated from the BS
C) TA value calculated by the UE based on the information of a reference point.
In an embodiment, the TA value and/or TA value drift rate obtained at and/or indicated from the BS may be 0.
In an embodiment, the information of a reference point is indicated from BS to UE.
In an embodiment, the information of a reference point is pre-stored within the UE (SIM card and/or universal SIM (uSIM) card).
In an embodiment, the information of a reference point is status information of reference point.
In an embodiment, the information of a reference point is timing information of signals transmitted from the reference point.
In an embodiment, the reference point is the BS.
In an embodiment, the reference point is a projection of the BS, e.g., on a wireless terminal group.
In an embodiment, the reference point is virtual node, which is used by the BS for calculating the TA value and/or TA value drift rate.
In an embodiment, the TA value and/or TA value drift rate indicated from BS is common value for the UE.
In an embodiment, the UE calculates the Doppler drift based on at least one of:
A) Doppler drift obtained at and/or indicated from the BS
B) Doppler drift rate obtained at and/or indicated from the BS
C) Doppler drift calculated by the UE based on the information of a reference point.
In an embodiment, the Doppler drift and/or Doppler drift rate obtained at and/or indicated from the BS may be 0.
In an embodiment, the information of a reference point is indicated from BS to UE.
In an embodiment, the information of a reference point is pre-stored within the UE (e.g., SIM and/or uSIM card).
In an embodiment, the information of a reference point is status information of reference point.
In an embodiment, the information of a reference point is timing information of signal transmitted from the reference point.
In an embodiment, the reference point is the BS.
In an embodiment, the reference point is a projection of the BS, e.g., on a wireless terminal group.
In an embodiment, the reference point is virtual node, which is used by the BS for calculating the TA value and/or TA value drift rate.
For example, in
In
In Embodiment 1, the synchronization value (e.g. TA value and/or Doppler drift) is calculated by the UE according to the information received/indicated from the BS.
In an embodiment, the information used by the UE for calculating the TA value may be:
1) Timing information related to (DL) transmissions only;
2) Status information of the reference point (e.g., the BS) only;
3) Timing information related to (DL) transmissions and status information of the reference point (e.g., the BS);
4) Timing information related to (DL) transmissions and TA value indicated by BS;
5) Timing information related to (DL) transmissions, TA value and TA value drift rate indicated from wireless network node;
6) Status information of the reference point (e.g. the BS), TA value and TA value drift rate indicated from wireless network node; and/or
7) TA value and TA value drift rate indicated from the BS.
In an embodiment, the indicated TA value and/or TA value drift rate from the BS is obtained by the BS.
In an embodiment, the information used by the UE for calculating the Doppler drift (i.e. frequency offset) may be:
1) Status information of the reference point (e.g. the BS) only;
2) Status information of the reference point (e.g. the BS) and Doppler drift indicated from the BS;
3) Timing information related to transmissions, Doppler drift indicated from the BS and Doppler drift rate indicated from the BS; and/or
4) Doppler drift indicated from the BS and Doppler drift rate indicated from the BS.
In an embodiment, the indicated Doppler drift and/or Doppler drift rate from the BS is obtained by the BS.
In this embodiment, the UE applies the calculated synchronization value for UL transmissions.
In an embodiment, the UE applies the calculated synchronization value a time offset after calculating the synchronization value, wherein the time offset is greater than or equal to a gap threshold T_gap. In an embodiment, the gap threshold T_gap is determined based on UE capability and/or configured by the BS (i.e. determined based on configuration from the BS).
In an embodiment, the UL transmission (e.g. PUSCH-X) has a long duration in time domain. For example, the UL transmission may have a duration exceeding a duration threshold T_dur. Under such a condition, the UL transmission is divided into several transmission parts and a time gap (e.g., TG shown in
In addition, the UE applies different TA values TA_m, TA_n and TA_o respectively for the TP1, TP2 and TP3 as shown in
In an embodiment, the TA value applied for each transmission part is obtained before each transmission part is transmitted (e.g., obtained within the time gap before each transmission part). Thus, the time gap between every two contiguous transmission parts (e.g. TG1 and TG2 shown in
In an embodiment, the gap threshold T_gap and/or the duration threshold T_dur is either configured by the BS or pre-defined with fixed value.
In an embodiment, the determinations of different TA values TA_m, TA_n and TA_o may be different. That is, the TA values TA_m, TA_n and TA_o may be determined by different manners.
In an embodiment, the determination of the first TA value is different from determinations of other TA values.
In an embodiment, the unit of the gap threshold T_gap and/or the duration threshold T_dur may be a slot, a symbol, a frame or ms.
More specifically, in
In an embodiment, the valid duration of each TA value may start from the first transmission part (e.g., first symbol of transmission part) for which the TA is applied. In this embodiment, the valid time threshold T_valid may be multiple times of T_dur or T_gap.
In an embodiment, the determinations of different TA values TA_m, and TA_n may be different from each other.
In an embodiment, the determination of the first TA value is different from those of other TA values.
In an embodiment, the valid duration of TA values may be a periodical pattern with duration of T_valid, wherein the start point of this pattern may be a time point To, which can be determined as subframe number (SFN) X (e.g. X=0).
In addition, the UE applies different frequency offsets FO_m, FO_n and FO_o respectively for the TP1, TP2 and TP3 as shown in
In an embodiment, the frequency offset applied for each transmission part is obtained before each transmission part is transmitted (e.g., obtained within the time gap before each transmission part). Thus, the time gap between every two contiguous transmission parts (e.g. TG1 and TG2 shown in
In an embodiment, the gap threshold T_gap and/or the duration threshold T_dur is either configured by the BS or pre-defined with fixed value.
More specifically, in
In an embodiment, the valid duration of each frequency offset may start from the first transmission part (e.g., first symbol of transmission part) for which the TA is applied. In this embodiment, the valid time threshold T_valid may be multiple times of T_dur or T_gap.
In an embodiment, the valid duration of frequency offsets may be a periodical pattern with duration of T_valid, wherein the start point of this pattern may be a time point To, which can be determined as subframe number (SFN) X (e.g. X=0).
In an embodiment, the synchronization value(s) applied for a UL transmission may comprises at least one of:
synchronization value(s) which is determined as a time offset (e.g. greater than the gap threshold T_gap) before the UL transmission,
synchronization value(s) which is determined as the time offset before receiving scheduling information of the UL transmission, or
synchronization value(s) which is reported before receiving the scheduling information of the UL transmission.
In this embodiment, the UE reports the calculated value for synchronization (e.g. TA value and/or frequency offset) to the BS.
In an embodiment, the UE may report the calculated value for synchronization in response to a request received from the BS. That is, the report of the calculated value for synchronization is triggered by the BS.
In an embodiment, the UE may report the calculated value for synchronization in a random access procedure (e.g. PRACH procedure). For example, the calculated value for synchronization may be reported during the initial access to the BS, in PRACH in response to the triggering due to UL synchronization error, or in PRACH during a beam failure (e.g. a link recovery procedure), etc.
In an embodiment, the UE may report the calculated value for synchronization in response to a configuration received from the BS.
In an embodiment, the UE reports the calculated value for synchronization within pre-configured resources (e.g. periodic resources). In an embodiment, the UE reports the calculated value for synchronization within pre-configured resources when at least one pre-defined criterion is fulfilled.
In an embodiment, the pre-defined criterion may be that the latest calculated value reported in a periodic resource is calculated a time offset ΔT before the periodic resource.
In an embodiment, the UE may ignore/cancel/drop the occasion for reporting the calculated value for synchronization when the at least one predefined criterion is not fulfilled.
In an embodiment, the UE may ignore/cancel/drop the occasion for reporting the calculated value for synchronization when the resource for TA report collides with other channels (e.g. PUCCH carrying ACK or PUSCH carrying CSI).
In an embodiment, the value for synchronization reported to the BS is the value applied for the UL transmission.
In an embodiment, the value for synchronization reported to the BS is the latest determined value.
In an embodiment, the value for synchronization reported to the BS is the value determined a time offset before reporting (e.g. the resources for reporting).
In an embodiment, the value for synchronization reported to the BS is the value determined a time offset before receiving scheduling information for reporting.
In an embodiment, the calculated value for synchronization is carried in a message for a random access procedure. Note that, the calculated value for synchronization is carried in data part of the message for the random access procedure. For example, the calculated value for synchronization may be carried within PUSCH for Msg-A of a two-step random access procedure.
In an embodiment, multiple different TAs may be applied between the preamble and the associated PUSCH within a single Msg-A. In this embodiment, the calculated values for synchronization reported to the BS are those applied for the associated PUSCH.
In an embodiment, the PUSCH of a single Msg-A is across multiple time durations with different TAs (i.e. multiple different TAs are used in the PUSCH across multiple time durations). In this embodiment, the first TA and/or the last TA applied for the PUSCH is reported to the BS.
In an embodiment, the calculated value for synchronization is reported in PUSCH scheduled from the BS. In this embodiment, the UE may report the latest calculated value or the value lastly applied for this PUSCH to the BS.
In an embodiment, after receiving the value for synchronization from the UE, the BS applies the received value (e.g. TA value and/or frequency offset) for scheduling UL resources (e.g. DCI based PUSCH scheduling) of the UE.
In an embodiment, the scheduling offset for the UL transmission should be determined based on the latest reported TA value which satisfies the time restriction for reporting application (e.g. after a time offset greater than the threshold T_gap).
Moreover, the subsequent UL transmission at the UE side may follow the scheduling offset which is indicated by the BS and adjusted based on the calculated value in the latest valid report.
Moreover, the UE performs a UL transmission (e.g. PUSCH) a time offset TO_2 after receiving the UL scheduling, wherein the time offset TO_2 satisfies the time restriction. That is, the scheduled offset of this UL transmission may follow the TA value indicated by the BS (i.e. UL scheduling) and be adjusted based on TA value calculated itself.
In an embodiment, the TA value applied for the UL transmission (e.g. PUSCH) is determined based on the latest calculated or reported TA value when the value is equal to or less than the value within the latest valid report.
In an embodiment, the reported TA value may refer to the directly calculated TA value, which is quantized with the pre-defined granularity with consideration on the SCS, e.g., slot, symbol, Ts or X*Ts.
In an embodiment, the reported TA value can also refer to a difference with regarding to the latest calculated value and/or the previous reported value.
In an embodiment, the self-calculation of TA value or frequency offset for synchronization may be enabled or disabled by the BS. For example, the BS may enable/disable the self-calculation of TA value or frequency offset for synchronization via an explicit signaling or a configuration on the resource for TA report. In an embodiment, when all of the TA value and/or frequency offset is indicated by the BS, report from the UE side is not needed.
In an embodiment, the self-calculation of TA value and/or frequency offset for synchronization may be enabled/disable based on the UE capability.
In an embodiment, for initial accessing, different resource configurations (e.g., PRACH format and PO) are used for different capabilities.
Step 1800: Determine at least one synchronization value;
Step 1802: Transmit, to a wireless network node, a signal based on the synchronization value.
More specifically, the wireless terminal determines (e.g. calculates) synchronization value(s) (e.g. TA value and/or frequency offset) itself, wherein references utilized by the UE for determining the synchronization value(s) may be information received from the wireless network node (e.g. BS). The information received from the wireless network node may comprises at least one component of at least one of:
timing information related to transmissions from the wireless network node to the wireless terminal,
status information of the wireless network node,
timing advanced value obtained at the wireless network node,
timing advanced value drift rate obtained at the wireless network node,
Doppler drift obtained at the wireless network node, or
Doppler drift rate obtained at the wireless network node.
In an embodiment, the wireless terminal may transmit a request for the information used for determining the synchronization value(s) to the wireless network node.
In an embodiment, the information comprises at least one differential component corresponding to the at least one status value.
Next, the wireless terminal transmits signal based on the determined synchronization value(s). In an embodiment, the signal may comprise at least one of a random access message (e.g. Msg-A or Msg-3), PUSCH scheduled by the wireless network node, PUSCH scheduled by the wireless network node, or periodic UL resource configured by the wireless network node.
Note that, the wireless terminal may apply the determined synchronization value(s) for transmitting the signal (e.g. UL transmission) and/or the wireless terminal may transmit the signal in which the determined synchronization value(s) is carried. For example, the wireless terminal may adjust timing/frequency offset of UL transmissions based on the determined synchronization value(s). In another example, the wireless terminal may report the determined synchronization value(s) in the corresponding UL transmissions.
In an embodiment, the synchronization value applied for the UL transmission is applied (a time offset) after being determined. The time offset may be greater than a threshold.
In an embodiment, the synchronization value applied for transmitting the signal comprises at least one of:
a synchronization value determined a time offset before transmitting the signal,
a synchronization value determined the time offset before receiving scheduling information for transmitting the signal, or
a synchronization value reported to the wireless network before receiving the scheduling information for transmitting the signal.
In an embodiment, the transmission of signal is divided into multiple transmission parts, e.g. a duration of the transmission is longer than a duration threshold. In this embodiment, the each of the plurality of transmission parts is transmitted by applying one of the determined synchronization value(s).
In an embodiment, a gap is inserted in every two contiguous transmission parts. Note that, the gap may have the same restriction of applying the synchronization value (i.e. larger than the threshold).
In an embodiment, a time length of each of the plurality of transmission parts is smaller than the duration threshold.
In an embodiment, the synchronization value(s) is transmitted in the signal a time offset after the synchronization value(s) is determined.
In an embodiment, the transmission of the synchronization value(s) does not collide with other channel transmissions.
In an embodiment, the synchronization value(s) is transmitted in data part of a message for random access procedure (e.g. Msg-A or Msg-3).
In an embodiment, the synchronization value(s) applied for the signal is carried in the signal.
In an embodiment, the signal carrying the at least one synchronization value is transmitted in at least one of following cases:
receiving a request for the at least one synchronization value from the wireless network node,
receiving a configuration for reporting the at least one synchronization value from the wireless network node, or
performing a random access procedure.
In an embodiment, the latest synchronization value(s) applied for the signal is carried in the signal.
In an embodiment, the synchronization value determined a time offset before transmitting the signal is carried in the signal.
In an embodiment, the synchronization value determined a time offset before receiving scheduling information for transmitting the signal is carried in the signal.
Step 1900: Receive, from a wireless terminal, at least one synchronization value;
Step 1902: Schedule, for the wireless terminal, uplink resources by applying the at least one synchronization value.
More specifically, the wireless network node (e.g. BS) may receive synchronization value(s) calculated by the wireless terminal (e.g. UE) and applies the received synchronization value(s) for scheduling UL resources of the wireless terminal.
In an embodiment, the synchronization value(s) may comprises TA value(s) and/or frequency offset(s).
In an embodiment, the frequency offset(s) is quantized by one of a sub-carrier spacing or a channel raster.
In an embodiment, the synchronization value(s) is carried in at least one of a random access message (e.g. Msg-A or Msg-3), PUSCH scheduled by the wireless network node, PUSCH scheduled by the wireless network node, or periodic uplink resource configured by the wireless network node.
In an embodiment, the synchronization value applied for scheduling the uplink resources is used a time offset after the synchronization value is received.
In an embodiment, the uplink resources are scheduled based on the latest synchronization value received from the wireless terminal.
While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand exemplary features and functions of the present disclosure. Such persons would understand, however, that the present disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.
It is also understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
A skilled person would further appreciate that any of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software unit”), or any combination of these techniques.
To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein. The term “configured to” or “configured for” as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and/or arranged to perform the specified operation or function.
Furthermore, a skilled person would understand that various illustrative logical blocks, units, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
In this document, the term “unit” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.
Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present disclosure. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
This application claims the benefit of priority under 35 U.S.C. § 120 as a continuation of PCT Patent Application No. PCT/CN2020/090625, filed on May 15, 2020, the disclosure of which is incorporated herein by reference in its entirety.
Number | Date | Country | |
---|---|---|---|
Parent | PCT/CN2020/090625 | May 2020 | US |
Child | 17851213 | US |