Method, apparatus and computer program product for reporting of user equipment time-frequency compensated timing
By reporting time and frequency compensation updates to base stations in 5G networks, the problem of difficulty in maintaining phase and power consistency when the transmission environment changes is solved, and channel estimation performance and communication quality are improved.
Patent Information
- Application Number
- CN202410180634.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-15
- Filing Date
- 2024-02-18
- Publication Date
- 2024-11-01
AI Technical Summary
In 5G networks, the DMRS binding framework requires the UE to maintain phase and power consistency, but due to changes in the transmission environment, the UE may not be able to maintain this consistency continuously, resulting in a degradation of channel estimation performance and affecting communication quality.
Provided a method and apparatus for reporting time and frequency compensation updates to a base station, indicating the time or frequency adjustment of the reference signal by determining the actual time domain window at the user equipment and sending a compensation report in the uplink communication flow, to ensure phase and power consistency.
The communication channel estimation performance and coverage between the base station and the user equipment are improved, the channel estimation capability of the 5G network is enhanced, and the communication accuracy and efficiency are ensured.
Smart Images

Figure CN118890694A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments relate generally to providing compensation reports to a base station, and more particularly to informing a base station of timing and frequency adjustments to reference signals in an uplink communication flow. Background Art
[0002] In fifth generation (5G) networks, demodulation reference signals (DMRS) are used to enable reliable and efficient communication between base stations and user equipment (UE) on physical channels. DMRS is typically sent along with the transmitted data to provide a reference signal, thereby facilitating more accurate demodulation of the transmitted data. One way in which the transmitted DMRS enables the receiver to more accurately demodulate the transmitted data is to perform channel estimation. Channel estimation involves estimating the characteristics of the communication channel between the transmitter and the receiver so that the transmitted data can be more accurately decoded. The receiver uses a reference signal (e.g., DMRS) to estimate channel characteristics, such as signal delay, amplitude offset, phase shift, speed / distance of the transmitter and receiver, and other anomalies. Using DMRS to enable channel estimation is critical to enabling advanced 5G features, such as beamforming, spatial multiplexing, multiple-input multiple-output (MIMO) communications, and non-terrestrial network (NTN) communications.
[0003] The DMRS bundling framework has been further introduced to improve the performance of channel estimation and provide performance gains in 5G communications. The traditional DMRS framework sends one or more time domain symbols across multiple resource blocks in the frequency domain. However, the traditional DMRS framework only sends these symbols in one time slot. Therefore, the base station can use the traditional DMRS framework to perform channel estimation, but only for a specific time slot. DMRS bundling extends the traditional DMRS framework to allow DMRS to be sent across multiple time slots. Through the transmission of DMRS across multiple time slots, joint channel estimation can be performed on the base station side, thereby improving the performance of channel estimation and coverage. As described above, DMRS bundling involves sending DMRS symbols in multiple time slots so that joint channel estimation can be performed across the transmission time slots. In order to achieve the performance gain of DMRS bundling, several conditions must first be met. For example, one or more communication channels must be relatively static, which means that the time variation between channels is below a certain threshold. In addition, the UE is required to maintain power consistency and phase continuity across the transmitted DMRS symbols in consecutive time slots within the configured time domain window (TDW). Receiving multiple coherent (meeting phase and power continuity requirements) DMRS symbols enables components of the 5G network to more accurately estimate the characteristics of the physical channel and improve coverage.
[0004] In some applications, the standard establishes a maximum allowed phase difference across DMRS symbols in a DMRS bundle. In order to ensure that the base station and the UE can coordinate over several time slots where DMRS bundling occurs, the concept of a time domain window is introduced within the DMRS bundling framework, in which power consistency and phase continuity are maintained. Coordination between the base station and the UE is usually achieved by allowing the base station to configure a nominal time domain window (TDW), within which multiple actual TDWs can be created. The nominal TDW defines the time interval in which the DMRS symbols can be coherently sent, so that there is a basic assumption of continuous operation, in which consistency between time slots can be assumed. The nominal TDW is a time domain window that is wider than the time domain window to which the DMRS bundling framework is usually applied. Therefore, the nominal TDW may include multiple actual TDWs. The actual TDW is such a time domain window: the UE sends multiple physical uplink shared channel (PUSCH) messages, including associated DMRS symbols, through this time domain window. The coherent transmission of PUSCH messages and associated DMRS symbols within the actual TDW requires phase continuity and power consistency. The actual TDW may be included in a nominal TDW and may be autonomously generated at the UE based on certain standardized conditions and events. Some of these events may interrupt continuous operation and thereby produce an actual TDW that is different from the nominal TDW. Events that interrupt continuous operation may result in a situation where the UE is unable to maintain phase continuity. Such events may require the UE to compensate for transmissions in order to maintain consistency. The UE's update of the timing advance (TA) of its uplink transmissions may be considered an event that disrupts phase and power consistency. Summary of the invention
[0005] A method, apparatus, and computer program product for reporting time and frequency compensation updates to a base station in a 5G network are disclosed. In one embodiment, a method is provided. The method may include: receiving information defining a time domain window from a base station at a user equipment, wherein the time domain window indicates a time window in an uplink communication stream in which at least a reference signal is to be sent. The method may also include determining an actual time domain window, wherein the actual time domain window is based at least in part on the information defining the time domain window in the uplink communication stream, and at least one adjustment of at least one of time or frequency to the reference signal due to the physical characteristics of the transmission environment. In addition, the method may include causing a compensation report to be sent to the base station in a control channel message within the uplink communication stream, wherein the compensation report includes an indication of at least one adjustment. The method may also include causing the reference signal to be sent to the base station in the actual time domain window.
[0006] In some embodiments, the method may further include generating a compensation report including compensation information related to at least one of the frequency adjustment and the timing adjustment.
[0007] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, a physical location of a base station, or a physical location of a user equipment.
[0008] In some embodiments, the method may further include causing the control channel message to be sent according to a physical uplink control channel (PUCCH).
[0009] In some embodiments, the method may further include causing the compensation report to be sent in a dedicated data field of a control channel message.
[0010] In some embodiments, the method may further include causing the compensation report to be sent in a shared data field of the control channel message.
[0011] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0012] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0013] In some embodiments, the method may further include allocating a subset of control channel resources to a compensation resource set group, and causing the compensation report to be sent on the available compensation resource set in the control channel message if the compensation report is updated.
[0014] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the method further includes causing the compensation report to be sent in coordination with the shared channel repetitions.
[0015] In some embodiments, the method may further include causing a compensation report to be sent after the shared channel is repeated, wherein the compensation report indicates at least one adjustment to a previously sent reference signal.
[0016] In some embodiments, the shared channel repetition may include at least a first shared channel repetition and a second shared channel repetition, wherein in a case where the first shared channel repetition does not fill the allocated time slot for the shared channel repetition, the method may further include causing a compensation report indicating at least one adjustment of the reference signal to be sent in a control channel message after the first shared channel repetition and before the second shared channel repetition.
[0017] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been applied or is to be applied.
[0018] In some embodiments, the method may further include causing a compensation report to be sent prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment to a future reference signal.
[0019] In another embodiment, a device is provided. The device 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 being configured to, together with the at least one processor, cause the device to: receive information defining a time domain window from a base station, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent; determine an actual time domain window, wherein the actual time domain window is based at least in part on the information defining the time domain window in the uplink communication flow, and at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment; cause a compensation report to be sent to the base station in a control channel message within the uplink communication flow, wherein the compensation report includes an indication of at least one adjustment; and cause the reference signal to be sent to the base station in the actual time domain window.
[0020] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to generate a compensation report comprising compensation information related to at least one of frequency adjustment and timing adjustment.
[0021] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0022] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to: cause the control channel message to be sent in accordance with a physical uplink control channel (PUCCH).
[0023] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to: cause the compensation report to be sent in a dedicated data field of a control channel message.
[0024] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to: cause the compensation report to be sent in a shared data field of a control channel message.
[0025] In some embodiments, the shared data field may include a base sequence, wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0026] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0027] In some embodiments, the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to: allocate a subset of control channel resources to a compensation resource set group, and, in a case where the compensation report is updated, cause the compensation report to be sent on the available compensation resource set in the control channel message.
[0028] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: cause the compensation report to be sent in coordination with the shared channel repetitions.
[0029] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to: cause a compensation report to be sent after a shared channel repetition, wherein the compensation report indicates at least one adjustment to a previously sent reference signal.
[0030] In some embodiments, in a situation where one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to: cause a confirmation control channel message indicating at least one adjustment of a reference signal to be sent.
[0031] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0032] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to: cause a compensation report to be sent prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment to a future reference signal.
[0033] In another embodiment, a computer program product includes at least one non-transitory computer-readable storage medium having a computer-readable program code portion stored therein, the computer-readable program code portion including an executable portion, the executable portion being configured to: receive information defining a time domain window from a base station at a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which at least a reference signal is to be sent. The computer program product may also be configured to determine an actual time domain window, wherein the actual time domain window is based at least in part on the information defining the time domain window in the uplink communication flow, and at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment. The computer program product may also be configured to cause a compensation report to be sent to the base station in a control channel message within the uplink communication flow, wherein the compensation report includes an indication of at least one adjustment. The computer program product may also be configured to cause the reference signal to be sent to the base station in the actual time domain window.
[0034] In some embodiments, the computer program product may be further configured to generate a compensation report including compensation information related to at least one of frequency adjustment and timing adjustment.
[0035] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0036] In some embodiments, the computer program product may be further configured such that the control channel message is sent according to a physical uplink control channel (PUCCH).
[0037] In some embodiments, the computer program product may be further configured such that the compensation report is sent in a dedicated data field of a control channel message.
[0038] In some embodiments, the computer program product may be further configured to cause the compensation report to be sent in a shared data field of a control channel message.
[0039] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0040] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0041] In some embodiments, the computer program product may be further configured to allocate a subset of control channel resources to a compensation resource set group and, if the compensation report is updated, cause the compensation report to be sent on the available compensation resource set in the control channel message.
[0042] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the method further includes causing the compensation report to be sent in coordination with the shared channel repetitions.
[0043] In some embodiments, the computer program product may be further configured to cause a compensation report to be sent after the shared channel is repeated, wherein the compensation report indicates at least one adjustment to a previously sent reference signal.
[0044] In some embodiments, the shared channel repetition may include at least a first shared channel repetition and a second shared channel repetition, wherein in a case where the first shared channel repetition does not fill the allocated time slot for the shared channel repetition, the method may further include causing a compensation report indicating at least one adjustment of the reference signal to be sent in a control channel message after the first shared channel repetition and before the second shared channel repetition.
[0045] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0046] In some embodiments, the computer program product may be further configured to cause a compensation report to be sent prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal.
[0047] In another embodiment, an apparatus is provided. The apparatus may include a component for receiving, at a user equipment, information defining a time domain window from a base station, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent; a component for determining an actual time domain window, wherein the actual time domain window is based at least in part on the information defining the time domain window in the uplink communication flow, and at least one adjustment of the reference signal in time or frequency due to physical characteristics of the transmission environment; a component for causing a compensation report to be sent to the base station in a control channel message within the uplink communication flow, wherein the compensation report includes an indication of at least one adjustment; and a component for causing the reference signal to be sent to the base station in the actual time domain window.
[0048] In some embodiments, the apparatus may further include means for generating a compensation report, the compensation report including compensation information related to at least one of frequency adjustment and timing adjustment.
[0049] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0050] In some embodiments, the apparatus may further include means for causing the control channel message to be transmitted according to a physical uplink control channel (PUCCH).
[0051] In some embodiments, the apparatus may further include means for causing the compensation report to be sent in a dedicated data field of a control channel message.
[0052] In some embodiments, the apparatus may further include means for causing the compensation report to be sent in a shared data field of the control channel message.
[0053] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0054] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0055] In some embodiments, the apparatus may further include means for allocating a subset of control channel resources to a compensation resource set group, and causing the compensation report to be sent on the available compensation resource set in the control channel message if the compensation report is updated.
[0056] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the apparatus further comprises means for causing the compensation report to be sent in coordination with the shared channel repetitions.
[0057] In some embodiments, the apparatus may further include means for causing a compensation report to be sent after the shared channel is repeated, wherein the compensation report indicates at least one adjustment to a previously sent reference signal.
[0058] In some embodiments, where in the event that one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the apparatus may further include means for causing an acknowledgement control channel message to be sent indicating at least one adjustment of a reference signal.
[0059] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0060] In some embodiments, the apparatus may further include means for causing a compensation report to be sent prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal.
[0061] In another embodiment, a method is provided. In some embodiments, the method may include causing information defining a time domain window to be sent to a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent; receiving a compensation report from the user equipment in a control channel message within the uplink communication flow, wherein the compensation report includes: an indication of at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment; and receiving the reference signal from the user equipment in an actual time domain window, wherein the actual time domain window is based at least in part on the at least one adjustment.
[0062] In some embodiments, the method may further include receiving a compensation report including compensation information related to at least one of a frequency adjustment and a timing adjustment.
[0063] In some embodiments, the physical characteristics of the transmission environment include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0064] In some embodiments, the method may further include receiving a control channel message according to a physical uplink control channel (PUCCH).
[0065] In some embodiments, the method may further include receiving the compensation report in a dedicated data field of the control channel message.
[0066] In some embodiments, the method may further include receiving the compensation report in a shared data field of the control channel message.
[0067] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0068] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0069] In some embodiments, the method may further include receiving a compensation report on the compensation resource set in a control channel message.
[0070] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the method further includes receiving the backoff report in coordination with the shared channel repetitions.
[0071] In some embodiments, the method may further include receiving a compensation report after the shared channel repetition, wherein the compensation report indicates at least one adjustment to a previously transmitted reference signal.
[0072] In some embodiments, in the event that one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the method may further include receiving an acknowledgement control channel message indicating at least one adjustment of the reference signal.
[0073] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0074] In some embodiments, the method may further include receiving a compensation report prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal.
[0075] In another embodiment, an apparatus is provided. The apparatus 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 being configured to, together with the at least one processor, cause the apparatus to: cause information defining a time domain window to be sent toward a user equipment, wherein the time domain window indicates a time window in an uplink communication stream in which a reference signal is to be sent; receive a compensation report from the user equipment in a control channel message within the uplink communication stream, wherein the compensation report includes an indication of at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment; and receive a reference signal from the user equipment in an actual time domain window, wherein the actual time domain window is based at least in part on at least one adjustment.
[0076] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive a compensation report including compensation information related to at least one of a frequency adjustment and a timing adjustment.
[0077] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0078] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive a control channel message in accordance with a physical uplink control channel (PUCCH).
[0079] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive the compensation report in a dedicated data field of a control channel message.
[0080] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive the compensation report in a shared data field of a control channel message.
[0081] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0082] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0083] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive a compensation report on the compensation resource set in a control channel message.
[0084] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to receive the compensation report in coordination with the shared channel repetitions.
[0085] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive a compensation report after a shared channel repetition, wherein the compensation report indicates at least one adjustment to a previously transmitted reference signal.
[0086] In some embodiments, in a situation where one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive an acknowledgment control channel message indicating at least one adjustment of a reference signal.
[0087] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0088] In some embodiments, the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to receive a compensation report prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal.
[0089] In another embodiment, a computer program product is provided. In some embodiments, the computer program product may include at least one non-transitory computer-readable storage medium having a computer-readable program code portion stored therein, the computer-readable program code portion including an executable portion configured to cause information defining a time domain window to be sent toward a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent; receiving a compensation report from the user equipment in a control channel message within the uplink communication flow, wherein the compensation report includes an indication of at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment; and receiving a reference signal from the user equipment in an actual time domain window, wherein the actual time domain window is based at least in part on the at least one adjustment.
[0090] In some embodiments, the computer program product may be further configured to receive a compensation report including compensation information related to at least one of a frequency adjustment and a timing adjustment.
[0091] In some embodiments, the physical characteristics of the transmission environment include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0092] In some embodiments, the computer program product may be further configured to receive a control channel message based on a physical uplink control channel (PUCCH).
[0093] In some embodiments, the computer program product may be further configured to receive the compensation report in a dedicated data field of the control channel message.
[0094] In some embodiments, the computer program product may be further configured to receive the compensation report in a shared data field of the control channel message.
[0095] In some embodiments, the shared data field may include a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0096] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0097] In some embodiments, the computer program product may be further configured to receive a compensation report on the compensation resource set in a control channel message.
[0098] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the method further includes receiving the backoff report in coordination with the shared channel repetitions.
[0099] In some embodiments, the computer program product may be further configured to receive a compensation report after the shared channel repetition, wherein the compensation report indicates at least one adjustment to a previously transmitted reference signal.
[0100] In some embodiments, in the event that one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the method may further include receiving an acknowledgement control channel message indicating at least one adjustment of the reference signal.
[0101] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0102] In some embodiments, the computer program product may be further configured to receive a compensation report prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal.
[0103] In another embodiment, an apparatus is provided. In some embodiments, the apparatus may include a component for causing information defining a time domain window to be sent to a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent; a component for receiving a compensation report from the user equipment in a control channel message within the uplink communication flow, wherein the compensation report includes an indication of at least one adjustment of at least one of time or frequency to the reference signal due to physical characteristics of the transmission environment; and a component for receiving the reference signal from the user equipment in an actual time domain window, wherein the actual time domain window is based at least in part on the at least one adjustment.
[0104] In some embodiments, the apparatus may further include means for receiving a compensation report including compensation information related to at least one of a frequency adjustment and a timing adjustment.
[0105] In some embodiments, the physical characteristics of the transmission environment may include at least one of physical characteristics of the transmission medium, physical location of the base station, or physical location of the user equipment.
[0106] In some embodiments, the apparatus may further include means for receiving a control channel message in accordance with a physical uplink control channel (PUCCH).
[0107] In some embodiments, the apparatus may further include means for receiving the compensation report in a dedicated data field of the control channel message.
[0108] In some embodiments, the apparatus may further include means for receiving the compensation report in a shared data field of the control channel message.
[0109] In some embodiments, the shared data field may include a base sequence, wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
[0110] In some embodiments, the shared data field may be at least one of a modulation symbol data field or a resource selection data field.
[0111] In some embodiments, the apparatus may further include means for receiving a compensation report on the compensation resource set in a control channel message.
[0112] In some embodiments, the uplink communication flow may include one or more shared channel repetitions, and the apparatus further comprises means for receiving the compensation report in coordination with the shared channel repetitions.
[0113] In some embodiments, the apparatus may further include means for receiving a compensation report after the shared channel repetition, wherein the compensation report indicates at least one adjustment to a previously transmitted reference signal.
[0114] In some embodiments, in the event that one or more shared channel repetitions do not fill an allocated time slot for the shared channel repetitions, the apparatus may further include means for receiving an acknowledgement control channel message indicating at least one adjustment of the reference signal.
[0115] In some embodiments, the compensation report may confirm the transmission of a reference signal in which at least one adjustment has been or will be applied.
[0116] In some embodiments, the apparatus may further include means for receiving a compensation report prior to a shared channel repetition, wherein the compensation report indicates at least one adjustment for a future reference signal. BRIEF DESCRIPTION OF THE DRAWINGS
[0117] Having generally described certain example embodiments of the present disclosure, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:
[0118] Figure 1 A block diagram of a system including a user equipment (UE) and a base station according to an example embodiment of the present disclosure is illustrated;
[0119] Figure 2 illustrates a block diagram of an apparatus that may be specifically configured according to an example embodiment of the present disclosure;
[0120] Figure 3 illustrates a signal diagram for reporting time and frequency compensation by a UE through explicit indication according to an example embodiment of the present disclosure;
[0121] Figure 4illustrates a signal diagram for reporting time and frequency compensation by a UE through implicit indication according to an example embodiment of the present disclosure;
[0122] Figure 5 depicts a graph illustrating cyclic shifts in the frequency domain according to an example embodiment of the present disclosure;
[0123] Figure 6 illustrates a signal diagram for reporting time and frequency compensation by a UE through an implicit indication with a scheduling request (SR) according to an example embodiment of the present disclosure;
[0124] Figure 7 depicts a graph illustrating transmission of compensation reports coordinated with scheduling requests according to an example embodiment of the present disclosure;
[0125] Figure 8 illustrates a signal diagram for reporting time and frequency compensation by sending a compensation report in a control channel message prior to a shared channel transmission according to an example embodiment of the present disclosure;
[0126] Fig. 9 illustrates a signal diagram for reporting time and frequency compensation by sending a compensation report in a control channel message after a shared channel transmission according to an example embodiment of the present disclosure;
[0127] Fig.10 illustrates a signal diagram for reporting time and frequency compensation over a specific set of control channel resources according to an example embodiment of the present disclosure;
[0128] Fig.11 illustrates a flow chart of a process for a UE to report time and frequency compensation via a control channel message according to an example embodiment of the present disclosure; and
[0129] Fig.12 A flow chart of a process of receiving time and frequency compensation from a UE through a control channel message at a base station according to an example embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION
[0130] Some embodiments of the present disclosure will be described more fully below with reference to the accompanying drawings, in which some but not all embodiments are shown. In fact, various embodiments of the present disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; on the contrary, these embodiments are provided so that the present disclosure will satisfy applicable legal requirements. The same figure numerals refer to the same elements throughout. As used herein, the terms "data", "content", "information" and similar terms may be used interchangeably to refer to data that can be sent, received and / or stored according to embodiments of the present disclosure. Therefore, the use of any such terms should not be viewed as limiting the spirit and scope of the embodiments of the present disclosure.
[0131] In addition, as used herein, the term "circuitry" refers to (a) a hardware circuit implementation only (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of circuits and (multiple) computer program products including software and / or firmware instructions stored on one or more computer-readable memories, which work together to cause the device to perform one or more functions described herein; and (c) circuits, such as (multiple) microprocessors or a portion of (multiple) microprocessors, which require software or firmware to operate even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of the term herein, including in any claims. As a further example, as used herein, the term "circuitry" also includes an implementation including one or more processors and / or (multiple) portions thereof and accompanying software and / or firmware. As another example, for example, as used herein, the term "circuitry" also includes a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network equipment, other network equipment (such as a core network device), a field programmable gate array, and / or other computing devices. Furthermore, as used herein, the term "module" refers to hardware or a combination of hardware and software, wherein the execution of the software directs the operation of the hardware.
[0132] Overview
[0133] Various example embodiments address technical issues related to reporting updates of time and frequency compensation parameters to a base station. As will be appreciated by those skilled in the art, there are many scenarios where it may be advantageous to send time and frequency compensation parameters to a base station to improve the accuracy and efficiency of data transmission.
[0134] As mentioned above, in 5G networks, demodulation reference signals (DMRS) are used to enable reliable and efficient communication between base stations and user equipment (UE) on physical channels. DMRS is typically sent along with the transmitted data to provide a reference signal, thereby facilitating more accurate demodulation of the transmitted data. The base station can configure the UE to send DMRS and other data in the nominal (and actual) TDW, where the UE must maintain phase and power consistency. The DMRS accompanying the transmitted data enables the receiver to determine the characteristics of the communication channel, which helps the receiver demodulate the transmitted data.
[0135] A DMRS bundling framework has been further introduced to improve the performance of channel estimation, including joint channel estimation performance, and provide performance gains in 5G communications. The DMRS bundling framework extends the traditional DMRS framework to allow DMRS to be transmitted consistently across multiple time slots. The DMRS bundling framework is introduced to improve channel estimation for PUSCH / PUCCH transmissions. Some important aspects of the DMRS bundling framework are: (1) DMRS bundling can be used for various uplink channel repetition types; (2) the UE can report the maximum duration (in terms of the number of consecutive time slots) during which the UE can maintain power consistency and phase continuity; and (3) the base station can configure the nominal TDW so that the duration of the nominal TDW is shorter than the maximum duration of (2). The maintenance of power consistency and phase continuity can be subject to a certain tolerance level.
[0136] In order to achieve the performance gain of DMRS bundling, several conditions must first be met. For example, the UE may be required to maintain power consistency and phase continuity. The UE must commit to and achieve phase continuity. Coordination of the duration of the nominal TDW and the actual TDW is a mechanism used by the UE and the base station to ensure that both the UE and the base station can determine that the time slot on the PUSCH is sent with bound DMRS. However, several events may lead to situations where the UE cannot maintain phase continuity. For example, the UE can update the timing advance (TA) of its uplink transmission based on the position and / or movement of the UE, the base station, or another network node.
[0137] In the current example, there are no restrictions on when or how the timing advance is sent. Incorrect or neglected timing advance adjustments may result in phase discontinuities and prevent the communication network from operating accurately and efficiently.
[0138] Various example embodiments described herein utilize various techniques to communicate compensating updates to time and / or frequency parameters of UE operation.As a result of the example embodiments described herein and in some examples, the accuracy and efficiency of communications between network nodes may be greatly improved.
[0139] System Architecture
[0140] Reference now Figure 1 , an example communication network 100, such as a 5G network, is provided in which certain illustrative embodiments are to be implemented. However, it should be understood that the embodiments are not limited to the network configurations shown herein or described below. It should be understood that the elements shown in the communication network 100 are intended to represent various functions provided within the system. Therefore, Figure 1 The blocks shown refer to specific elements in the 5G network that provide these functions. However, other network elements may be used to implement some or all of the functions represented. In addition, it should be understood that not all functions of the 5G network are depicted in FIG. Figure 1 Rather, functionality is represented to facilitate the description of the illustrative embodiments. Furthermore, although described in the context of a 5G network, reference to the 5G network is by way of example, and the methods, apparatus, and computer program products of other example embodiments may be deployed in other types of networks, including legacy networks and networks to be developed, such as sixth generation (6G) or other types of networks.
[0141] like Figure 1 As shown, UE 102 is communicatively connected to base station 104. UE 102 can be configured to send control channel messages (such as physical uplink control channel (PUCCH) messages) and data channel messages (such as physical uplink shared channel (PUSCH) messages) on uplink communication flow 106. In addition, UE 102 can be configured to receive control channel messages (such as physical downlink control channel (PDCCH) messages) and data channel messages (such as physical downlink shared channel (PDSCH) messages) on downlink communication flow 108. In addition, UE 102 can be configured to communicate with base station 104 via a non-terrestrial network, such as via a low earth orbit (LEO) satellite (e.g., satellite 110).
[0142] Figure 1 A communication network 100 is depicted. For example, the communication network 100 can be deployed within a radio access architecture. However, the system can be deployed in other applications, including within other communication networks, including, for example, Long Term Evolution Advanced (LTE-Advanced, LTE-A), Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANETs), and Internet Protocol Multimedia Subsystems (IMS), or any combination thereof. Instead of a base station, any access network that is eligible to access the 5G core network may be used, such as an untrusted non-3GPP access terminated at a non-3GPP interworking function (N3IWF), a trusted non-3GPP access terminated at a trusted non-3GPP gateway function (TNGF), or a wired access terminated at a wireless access gateway function (W-AGF).
[0143] like Figure 1As further depicted in the example communication network 100, the example communication network 100 may include one or more UEs 102, which may communicate with a base station 104, such as via a wireless interface, as shown. The UE 102 may be a mobile station, and such a mobile station may include a location and a velocity. The UE 102 may be equipped with functionality that may provide the UE 102 with its geographic location, such as via a global navigation satellite system (GNSS). For example, by utilizing a global positioning system (GPS), GloNass, Gallileo, or other similar geolocation systems.
[0144] The term "user equipment" as used herein is intended to be interpreted broadly to encompass a variety of different types of mobile stations, subscriber stations, or broader communication devices. In addition to or in lieu of those identified above, UE 102 may also refer to a portable computing device, which includes a wireless mobile communication device operating with or without a subscriber identity module (SIM), including but not limited to the following types of devices: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), vehicles, UEs mounted on vehicles, Internet of Things (IoT) devices, wearable devices, handheld devices, devices using wireless modems (alarm or measurement devices, etc.), laptop computers and / or touch screen computers, tablet computers, game consoles, notebook computers, and multimedia devices. UE 102 may also be referred to as a subscriber unit, mobile station, remote terminal, access terminal, user terminal, or user equipment, to name a few.
[0145] Figure 1 Further depicted is a base station 104 that is communicatively connected to the UE 102. Figure 1 In the radio access architecture of , UE 102 is configured to be in wireless connection with base station 104 (such as next generation Node B (gNB)) on one or more communication channels in a cell. The physical link from UE 102 to base station 104 is called uplink or reverse link (e.g., uplink communication system 106), and the physical link from base station 104 to UE 102 is called downlink or forward link (e.g., downlink communication system 108). It should be understood that base station 104 or its functions can be implemented using any node, host, server, access point (AP) or other entity suitable for such purpose.
[0146] The communication network 100 typically includes more than one base station 104, in which case the base stations 104 may also be configured to communicate with each other via wired or wireless links designed for this purpose. The base station 104 may also be referred to as a gNB, an access point, or any other type of interface device, including a relay station capable of operating in a wireless environment. The base station 104 includes or is coupled to (multiple) transceivers. From the transceiver of the base station 104, a connection is provided to the antenna unit, which establishes a two-way radio link to the UE 102. In this way, the transceiver of the base station 104 and the transceiver of the UE 102 may include a transmitter and a receiver configured to communicate via a channel.
[0147] like Figure 1 As further shown, the communication network 100 may include an uplink communication system 106. The uplink communication system 106 may include multiple communication channels, such as PUSCH and PUCCH, to enable communication from the UE 102 to the base station 104. The PUSCH transmission(s) from the UE 102 may be dynamically scheduled by the base station 104 via an uplink grant indicated in a downlink communication flow 108 (e.g., PDCCH). In addition, the PUSCH transmission(s) from the UE 102 may be semi-persistently and / or statically scheduled using a higher layer configuration grant, such as configuredGrantConfig.
[0148] PUCCH transmissions may be used to provide uplink control information (UCI) from the UE 102 to the base station 104. Such UCI may include channel quality information (CQI), channel state information (CSI), information related to downlink transmissions (e.g., hybrid automatic repeat request acknowledgement (HARQ-ACK)), and other control information. The various types of UCI carried on the PUCCH may be multiplexed or sent as independent information. In this way, the payload size sent on the PUCCH may be time-varying but sized to be decoded by the base station 104 upon reception.
[0149] like Figure 1As further shown, the communication network 100 may include a non-terrestrial network (NTN) using one or more satellites (e.g., satellite 110). The communication network 100 defined according to the Third Generation Partnership Project (3GPP) may support communications between the satellite 110 and the UE 102. Communications between the satellite 110 and the UE 102 introduce unique challenges. For example, the satellite 110 may move at high speeds (7500 m / s in low earth orbit) and potentially have very long round trip times (due to the satellite being at an altitude of 36000 km in geostationary / geosynchronous orbit, which results in a round trip time of approximately 0.5 seconds). In some embodiments, the satellite 110 used for communication with the UE 102 may operate in a "transparent mode", which means that the satellite 110 may act as a mobile remote radio head in communication with a traditional base station 104 located on the ground. In some embodiments, the satellite 110 used for communication with the UE 102 may operate in a "regeneration mode", which means that the functionality of the base station 104 may be implemented at least partially on the satellite 110.
[0150] like Figure 1 As shown, a first communication link (eg, service link 112 ) is established between UE 102 and satellite 110 , and a second communication link (eg, feeder link 114 ) is established between satellite 110 and base station 104 .
[0151] One of the main challenges of communicating with satellites 110 is that satellites in LEO move at high speeds, causing the path distances of both feeder links 114 and service links 112 to vary over time. To facilitate accurate and efficient data transmission over service links 112, UEs 102 may receive the position and velocity of satellites 110. Knowing the position and velocity of satellites 110 enables UEs 102 to determine impairments in service links 112 and the Doppler effect experienced by the movement of satellites 110 and / or the movement of UEs 102. Thus, UEs 102 may determine time adjustments that may be applied to transmit signals and / or receive signals to compensate for the movement of UEs 102 and / or satellites 110. Similarly, base stations 104 may determine time variations in signals transmitted on feeder links 114 between satellites 110 and base stations 104. The time adjustments applied to feeder links 114 are referred to as common TA parameters because these time adjustments apply to all UEs 102 utilizing satellites 110. The UE 102 may use the common TA parameters to perform additional compensation on the transmitted signal based on the applicable impairments on the feeder link 114. Due to the dynamic nature of the NTN communication system, additional parameters are provided to ensure the accuracy of the received data. For example, the epoch time may accompany the data transmission. The epoch time defines the time during which the transmitted information is considered valid. The epoch time enables the UE to determine the validity of the position of the satellite 110 at a given time.
[0152] In addition, a validity timer may accompany the data transmission. The validity timer may be sent by the base station 104 to inform the UE 102 how long after the epoch time the UE 102 may consider the ephemeris information of the satellite 110 to be applicable. The validity timer ensures that the UE 102 does not use information outside the "prediction horizon".
[0153] Reference now Figure 2 , Figure 2 An example network node 200 is illustrated in accordance with at least some example embodiments of the present disclosure. The example network node 200 includes a processor 202, a communication interface 204, and a data storage medium 206. In some embodiments, the example network node 200 may be embodied in various computing devices such as UE 102, base station 104, and satellite 110 as described above.
[0154] Although the components are described with respect to functional limitations, it should be understood that specific implementations necessarily include the use of specific computing hardware. It should also be understood that in some embodiments, some of the components described herein include similar or common hardware. For example, two groups of circuit systems can utilize the same (multiple) processors, (multiple) network interfaces, (multiple) storage media, etc. to perform their associated functions, so that duplicate hardware is not required for each group of circuit systems. Therefore, the term "circuitry" used herein with respect to components of the devices described herein should be understood to include specific hardware configured to perform functions associated with the specific circuit systems described herein.
[0155] In particular, the term "circuitry" should be broadly understood to include hardware, and in some embodiments, software for configuring hardware. For example, in some embodiments, "circuitry" includes processing circuitry, storage media, network interfaces, input / output devices, etc. Alternatively or additionally, in some embodiments, other elements of the network node 200 provide or supplement the functionality of other specific circuitry collections. For example, in some embodiments, the processor 202 provides processing functionality to any of the various groups of circuitry, the data storage medium 206 provides storage functionality to any of the various groups of circuitry, the communication interface 204 provides network interface functionality to any of the various groups of circuitry, and so on.
[0156] In some embodiments, processor 202 (and / or a coprocessor, or any other processing circuitry assisting a processor or otherwise associated with a processor) communicates with data storage medium 206 via a bus to transfer information between components of network node 200. In some embodiments, for example, data storage medium 206 is non-transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, in some embodiments, data storage medium 206 includes or embodies an electronic storage device (e.g., a computer-readable storage medium). In some embodiments, data storage medium 206 is configured to store information, data, content, applications, instructions, etc. to enable network node 200 to perform various functions according to example embodiments of the present disclosure.
[0157] The processor 202 may be embodied in a variety of different ways. For example, in some example embodiments, the processor 202 includes one or more processing devices configured to execute independently. Additionally or alternatively, in some embodiments, the processor 202 includes one or more processors configured in series via a bus to enable independent execution of instructions, pipelining, and / or multithreading. The use of the terms "processor" and "processing circuit system" should be understood to include a single-core processor, a multi-core processor, multiple processors within the network node 200, and / or one or more remote or "cloud" processors outside the network node 200.
[0158] In an example embodiment, the processor 202 is configured to execute instructions stored in the data storage medium 206 or otherwise accessible to the processor. Alternatively or additionally, in some embodiments, the processor 202 is configured to perform hard-coded functions. Therefore, whether configured by hardware or software methods, or by a combination thereof, the processor 202 represents an entity (e.g., physically embodied in a circuit system) that is capable of performing operations according to embodiments of the present disclosure when configured accordingly. Alternatively or additionally, as another example, in some example embodiments, when the processor 202 is embodied as an executor of software instructions, the instructions specifically configure the processor 202 to perform algorithms embodied in specific operations described herein when such instructions are executed.
[0159] In some embodiments, the network node 200 includes a communication interface 204. The communication interface 204 includes any component configured to receive data from and / or send data to a network and / or any other device, circuit system or module that communicates with the network node 200, such as a device or circuit system embodied in hardware or a combination of hardware and software. In this regard, for example, in some embodiments, the communication interface 204 includes a network interface for enabling communication with a wired or wireless communication network. Additionally or alternatively, in some embodiments, the communication interface 204 includes one or more network interface cards, antennas, buses, switches, routers, modems, and any other device that supports hardware, firmware and / or software, or is suitable for enabling communication via one or more communication networks. Additionally or alternatively, the communication interface 204 includes a circuit system for interacting with (multiple) antennas and / or other hardware or software to enable transmission of signals via (multiple) antennas or processing of signals received via (multiple) antennas. In some embodiments, the communication interface 204 enables transmission of data to and / or reception from a client device that communicates with the network node 200.
[0160] Additionally or alternatively, in some embodiments, one or more of the groups of circuit systems 202-206 are combinable. Additionally or alternatively, in some embodiments, one or more of the groups of circuit systems perform some or all of the functions described in association with another component. For example, in some embodiments, one or more of the groups of circuit systems 202-206 are combined into a single module embodied in hardware, software, firmware, and / or a combination thereof.
[0161] Reference now Figure 3 , a signal diagram depicting a process 300 for providing compensation reports to a base station 104 is provided. Figure 3 As shown, a signal 302 sent by the base station 104 configures the UE 102 for transmission of periodic control channel message transmission. Periodic control channel message transmission can be any transmission mode in which a control channel message including uplink control information (UCI) is sent by the UE 102 at predetermined time intervals (rather than immediately in response to a downlink control message). In some embodiments, the control channel message can be a PUCCH message. The configuration of the periodic PUCCH can include parameters such as the format used to send control information, resource index, hopping mode, power offset, channel quality indicator (CQI) report configuration, and other transmission parameters.
[0162] Additionally, the base station 104 may configure the UE 102 to send DMRS according to a DMRS bundling framework. The use of DMRS on uplink channels may ensure accurate and reliable data transmission. In some embodiments, the DMRS may be sent according to the DMRS bundling framework. The DMRS bundling framework is introduced to improve channel estimation for PUSCH and PUCCH transmissions. The main goal of the DMRS bundling framework is to ensure that the base station 104 and the UE 102 coordinate the number of time slots in which DMRS bundling is applied. Therefore, using signal 302, the base station may configure the nominal and actual TDW of the UE 102 for DMRS bundling. DMRS bundling specifies a time domain window (TDW) within which the UE must maintain power consistency and phase continuity across PUSCH / PUCCH transmissions, including corresponding DMRS symbols. TDW determination includes two steps, namely nominal TDW determination and actual TDW determination.
[0163] As it relates to TDW within the framework of DMRS bundling, the 5G technical reference produced by the 3rd Generation Partnership Project (3GPP) states: When PUSCH-DMRS-Bundling is enabled, for PUSCH transmissions scheduled by DCI format 0_1 or 0_2 with PUSCH repetition type A, PUSCH repetition type A with a configured grant, PUSCH repetition type B and TB handling over multiple slots, and when PUCCH-DMRS-Bundling is enabled, for PUCCH transmissions with PUCCH repetition, the UE determines one or more nominal TDWs as follows: For PUSCH transmissions with repetition type A, PUSCH repetition type B and TB handling over multiple slots, for each nominal TDW except the last nominal TDW The duration of W is (in number of consecutive time slots): (a) given by PUSCH-TimeDomainWindowLength (if configured); (b) calculated as min([maxDMRS-BundlingDuration], M) (if PUSCH-TimeDomainWindowLength is not configured), where [maxDMRS-BundlingDuration] is the maximum duration of the nominal TDW constrained by UE capabilities [13, TS38.306], M is the duration of N·K PUSCH transmissions in consecutive time slots, and where (i) for PUSCH transmissions of PUSCH repetition type A, N=1 and K is the number of repetitions, as in TS (ii) for PUSCH transmission of PUSCH repetition type B, N=1 and K is the nominal number of repetitions as defined in Section 6.1.2.1 or Section 6.1.2.3 of TS 38.214; and (iii) for PUSCH transmission with TB processing over multiple timeslots, N is the number of timeslots determined for TBS and K is the number of repetitions for the number of timeslots N determined for TBS, as defined in Section 6.1.2.1 or Section 6.1.2.3 of TS 38.214.
[0164] As it relates to nominal TDW within the framework of DMRS bundling, the 5G technical reference produced by 3GPP states that: (1) For PUSCH repetition type A scheduled by DCI format 0_1 or 0_2 and PUSCH transmissions of PUSCH repetition type A with a configured grant, when AvailableSlotCounting is enabled, and for TB processing over multiple timeslots: (a) the start of the first nominal TDW is the first timeslot determined for the first PUSCH transmission; (b) the end of the last nominal TDW is the last timeslot determined for the last PUSCH transmission; and (c) the start of any other nominal TDW is after the last timeslot determined for the PUSCH transmission of the previous nominal TDW. the first timeslot determined for a PUSCH transmission; and (2) for PUSCH repetition type A scheduled by DCI format 0_1 or 0_2 and PUSCH repetition type A with configured grant, when the UE is not configured with AvailableSlotCounting or when AvailableSlotCounting is disabled, and for PUSCH repetition type B: (a) the start of the first nominal TDW is the first timeslot used for the first PUSCH transmission; (b) the end of the last nominal TDW is the last timeslot used for the last PUSCH transmission; and (c) the start of any other nominal TDW is the first timeslot after the last timeslot of the previous nominal TDW.
[0165] As it relates to the determination of the actual TDW within the framework of DMRS bundling, the 5G technical reference document produced by 3GPP states: For PUSCH transmissions handled by PUSCH repetition type A, PUSCH repetition type A with configured grant, PUSCH repetition type B, and TBs over multiple time slots scheduled by DCI format 0_1 or 0_2, the nominal TDW includes one or more actual TDWs. The UE determines the actual TDW as follows: (1) the start of the first actual TDW is the first symbol of the first PUSCH transmission in the time slot for PUSCH transmissions handled by PUSCH repetition type A, PUSCH repetition type A with configured grant, PUSCH repetition type B, or TBs over multiple time slots scheduled by DCI format 0_1 or 0_2 within the nominal TDW; (2) the end of the actual TDW is: (a) if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW, then the end of the actual TDW is: (b) if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW, then the end of the actual TDW is: (c) if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW, then the end of the actual TDW is: (d) if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW, then the end of the actual TDW is: (d) if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW, then the end of the actual TDW is: (a) if an event occurs that causes a PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition type A with a configured grant, or PUSCH repetition type B, or PUSCH transmission handled by a TB over multiple slots within the nominal TDW to fail to maintain power. (c) when PUSCH-Window-Restart is enabled, the start of a new actual TDW is the last symbol of the PUSCH transmission preceding the event that causes the PUSCH-Window-Restart to span the nominal TDW scheduled by DCI format 0_1 or 0_2 within the specified TDW; or (d) when PUSCH-Window-Restart is enabled, the start of a new actual TDW is the last symbol of the PUSCH transmission preceding the event that causes the PUSCH-Window-Restart to span the nominal TDW scheduled by DCI format 0_1 or 0_2 within the specified TDW. The first symbol of a PUSCH transmission after an event in which power consistency and phase continuity cannot be maintained for PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition type A with configured authorization, or PUSCH repetition type B, or PUSCH transmission handled by TB on multiple time slots, and the PUSCH transmission is in a time slot for PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition type A with configured authorization, or PUSCH repetition type B, or PUSCH transmission handled by TB on multiple time slots.
[0166] In an example embodiment, the base station 104 may configure the UE 102 to have periodic PUCCH transmissions. For example, the periodic configuration of the PUCCH may be accomplished via a scheduling request (SR) configuration (e.g., "SchedulingRequestResourceConfig") and a radio resource control (RRC) parameter (e.g., "periodicityAndOffset"). In one embodiment, the RRC parameter (e.g., "periodicityAndOffset") may be in a symbol or slot duration with different range values for different subcarrier spacings. As an example, the subcarrier spacing may be 15 kHz and the period is 160 slots.
[0167] like Figure 3 As further shown, a signal 304 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During PUSCH transmissions with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling can be particularly useful for PUSCH transmissions with repetitions. DMRS bundling coherently sends DMRS associated with PUSCH transmission repetitions. In the case where multiple PUSCH messages are sent as part of a PUSCH repetition frame and each PUSCH transmission is further configured with DMRS bundling, the DMRSs of the multiple transmissions can be processed jointly rather than individually to provide additional transmission improvement over the transmission improvement achieved by repetition.
[0168] like Figure 3As further shown, at box 306, UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent UE 102 from maintaining the phase continuity required for DMRS bundling. For example, UE 102 may perform an update of a timing advance (TA) value. At box 306, UE 102 determines the time point at which it expects to perform a TA value update, or the time point at which it performs a TA value update. In the first case, the determination may occur before the nominal / actual TDW begins, and in the second case, the determination may occur after the nominal or actual TDW ends. In another embodiment, UE 102 determines the time point at which it performs a TA value update. TA is a mechanism for compensating for the time difference taken for an uplink signal to propagate from UE 102 to a base station. TA may be based on the distance between UE 102 and base station 104. As described herein, TA may be necessary when communication from UE 102 to base station 104 passes through satellite 110. In this case, the TA may take into account a common TA on the feeder link 114 and a UE 102 specific TA on the serving link 112. Based on any TA updates, the UE 102 may further determine an actual TDW within the nominal TDW.
[0169] The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within a nominal time domain window for data transmission, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment to the time domain window (which results in the actual time domain window) may be the result of an event that results in a phase discontinuity of the channel of the portion of the DMRS being transmitted. For example, a TA update may result in the adjustment to the time domain window and the determination of the actual time domain window. The adjustment to the time domain window may include, but is not limited to, time offset, phase offset, frequency change, and other similar adjustments. In some embodiments, the actual time domain window may be determined based on one or more physical characteristics of the transmission environment. The physical characteristics of the transmission environment may include physical characteristics of the transmission medium, such as attenuation, refraction, reflection, absorption, and / or other signal attenuation effects caused by the transmission medium. The physical location of the base station 104 and the UE 102 may also affect the compensation that may be applied to the time domain window, such as the distance between the UE 102 and the base station 104. The physical layout of the communication network may be another physical characteristic of the transmission environment that may affect the compensation applied to the time domain window. For example, if UE 102 communicates via satellite 110 in an NTN, the travel distance and speed of satellite 110 and / or UE 102 may affect the compensation applied to the actual time domain window.
[0170] like Figure 3As further shown, the signal 308 sent by the UE 102 reports to the base station 104 a confirmation of the UE 102 uplink time / frequency compensation to indicate a successful TA update to the base station 104, or reports a planned or executed (multiple) TA update instance by providing a compensation report. The compensation report can be any indication of a planned time instance at which a TA adjustment occurs, or an execution time instance at which a TA adjustment has occurred. In some embodiments, the compensation report may include a mechanism for indicating to the base station 104 that the timing / frequency adjustment has been applied. For example, the compensation report may confirm and / or indicate that the timing adjustment has been received and applied. In such an embodiment, the compensation report may be a Boolean indicator. In some embodiments, the compensation report may provide absolute timing to indicate that a timing / frequency adjustment has been made (in milliseconds or time slots). In such an embodiment, the compensation report may include multiple data bits and / or fields to convey absolute timing. In some embodiments, the compensation report may include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on the provided time domain window (e.g., offset). In some embodiments, the compensation report may be a form of confirmation that the UE 102 has successfully performed time / frequency compensation on the transmitted data. The confirmation may indicate that the TDW has been adjusted, but may not necessarily indicate the precise timing of the TDW. The confirmation from UE 102 may be sufficient for the base station to understand the ability of UE 102 to maintain phase continuity and power consistency for a certain duration in the future, however, the precise timing of the adjustment may not be conveyed. In this way, the confirmation may not provide flexibility in compensation reporting, but less overhead may be used. In some embodiments, the compensation report may be sent after the time / frequency adjustment is performed. For example, after the data has been sent to the base station 104, the compensation report may be sent to the base station 104 to provide confirmation of the time / frequency compensation. In some embodiments, the compensation report may be sent to the base station 104 before the data is transmitted according to the actual time domain window.
[0171] like Figure 3As shown, an example mechanism for sending a compensation report may include the UE 102 explicitly indicating the compensation report to the base station 104 via a dedicated data field. The dedicated data field may be any bit or bit sequence that is primarily used to indicate the compensation report. For example, a new data field may be allocated to be sent in a control channel message (e.g., PUCCH) within an uplink communication flow (e.g., uplink communication flow 106). In some embodiments, the compensation report may indicate a confirmation made by a new bit field, such as using a new bit field including 1 bit, where 1 indicates a confirmation that time / frequency compensation has been performed. In some embodiments, the compensation report may indicate an absolute timing (e.g., in milliseconds or time slots) or relative timing of the time and frequency compensation, for example, relative to the start of the nominal TDW (in milliseconds or time slots). In such an embodiment, multiple bits may be used to indicate the absolute time / frequency, and / or offset time / frequency.
[0172] like Figure 3 As further shown, at block 310, the base station 104 may receive a compensation report including a timing and / or frequency adjustment within a time domain window so that a time instance window for performing compensation may be determined. The base station 104 may determine an actual TDW for transmissions by the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0173] like Figure 3 As further shown, the signal 312 sent by the UE 102 can send a PUSCH and / or PUCCH transmission with repetitions, wherein the actual TDW is adjusted according to the time instance of the determined time / frequency compensation. In addition, the base station 104 can receive the PUSCH and / or PUCCH transmission and demodulate the DMRS according to the actual time domain window.
[0174] In some embodiments, a shared channel repetition (e.g., a PUSCH repetition) does not fill a time slot allocated for the transmission of the shared channel repetition. In this case, there may be a time space between the transmission of the first shared channel repetition and the transmission of the second shared channel repetition. In this case, a control channel message (e.g., a PUCCH) may be sent in the time gap between the transmission of the first shared channel repetition and the transmission of the second shared channel repetition. In such an embodiment, UE102 may send a compensation report on the control channel message between the transmissions of the shared channel repetitions. In some embodiments, the compensation report may indicate a compensation time instance of a previously sent shared channel repetition. In some embodiments, the compensation report may indicate a compensation time instance of an upcoming shared channel repetition. In some embodiments, the compensation report may indicate a successful compensation in the form of a confirmation.
[0175] Reference now Figure 4, a signal diagram depicting a process 400 for providing compensation reports to a base station 104 is provided. Figure 4 As shown, a signal 402 sent by the base station 104 configures the UE 102 for transmission of periodic control channel message transmission. Periodic control channel message transmission can be any transmission mode in which a control channel message including uplink control information (UCI) is sent by the UE 102 at predetermined time intervals (rather than immediately in response to a downlink control message). In some embodiments, the periodic control channel message transmission may include a PUCCH message. The configuration of the periodic PUCCH may include parameters such as the format for sending control information, resource index, hopping mode, power offset, channel quality indicator (CQI) report configuration, DMRS bundling framework parameters, and other transmission parameters.
[0176] In an example embodiment, the base station 104 may configure the UE 102 to have periodic PUCCH transmissions. For example, the periodic configuration of the PUCCH may be accomplished via a scheduling request (SR) configuration (e.g., "SchedulingRequestResourceConfig") and a radio resource control (RRC) parameter (e.g., "periodicityAndOffset"). In one embodiment, the RRC parameter (e.g., "periodicityAndOffset") may be in a symbol or slot duration with different range values for different subcarrier spacings. As an example, the subcarrier spacing may be 15 kHz and the period is 160 slots.
[0177] like Figure 4 As further shown, a signal 404 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During a PUSCH transmission with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling consistently sends DMRS associated with PUSCH transmission repetitions. In the case where multiple PUSCH messages are sent as part of a PUSCH repetition frame and each PUSCH transmission is further configured with DMRS bundling, the DMRSs of the multiple transmissions can be processed jointly rather than individually to provide additional transmission improvement over the transmission improvement achieved by repetition.
[0178] like Figure 4As further shown, at block 406, the UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent the UE 102 from maintaining the phase continuity required for DMRS binding. Based on any TA updates, the UE 102 may further determine the actual TDW within the nominal TDW. The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within the nominal TDW, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment to the time domain window (which results in the actual time domain window) may be the result of an event that results in a phase discontinuity of the channel of the portion of the DMRS being transmitted. For example, a TA update may result in an adjustment to the time domain window and a determination of the actual time domain window. The adjustment to the time domain window may include, but is not limited to, a time offset, a phase offset, a frequency change, and other similar adjustments.
[0179] like Figure 4 As further shown, UE 102 sends signal 408 to report confirmation of UE 102 uplink time / frequency compensation to base station 104, thereby indicating a successful or planned TA update instance to base station 104 by providing a compensation report. The compensation report can be any indication of a planned or performed adjustment of the time domain window. In some embodiments, the compensation report can include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on a provided time domain window (e.g., an offset).
[0180] like Figure 4 As further shown, an example mechanism for sending the compensation report may include the UE 102 implicitly indicating the compensation report via a shared data field in a control channel message. The shared data field may be any bit, bit sequence, or other data field in the control channel message that is at least partially allocated for purposes other than sending the compensation report, such as an existing data field in the PUCCH. As an example, the UE 102 may send the compensation report by applying a particular cyclic shift to a PUCCH sequence used to send the compensation report. In some embodiments, the PUCCH may be PUCCH format 0. For example, in PUCCH format 0, information is conveyed by applying different cyclic shifts to a base sequence of length 12 as follows:
[0181] r(n)=e jαn ×k(n), 0≤n<12
[0182] where k(n) represents the basis sequence, and the term e jαn Provides the frequency domain phase shift of the base sequence. More specifically, α is calculated as follows:
[0183]
[0184] where m0 is the initial cyclic shift, p is a function based on a pseudo-random sequence, and mcs transmits the information content of the UCI. cs The value of (and subsequently different values of α) determines the information content of the UCI. The term α can take the values However, in some embodiments, the value is reserved and is not used to apply cyclic shift to the base sequence. Therefore, α={2,5,8,11} may be utilized to carry compensation reports, for example, asserting a specific value of the cyclic shift parameter may be an indicator for a confirmed compensation report.
[0185] Figure 5 An exemplary cyclic shift diagram 500 for encoding UCI data on a PUCCH is illustrated. As shown herein, certain cyclic shift values may be unused, such as 502, 504, 506, and 508. The available cyclic shift values may be used to encode a compensation report confirming successful time / frequency compensation.
[0186] like Figure 4 As shown, at block 410, the base station 104 may receive a compensation report in a shared data field that includes a timing and / or frequency adjustment within a time domain window, such that a time instance at which compensation is performed may be determined. The base station 104 may determine an actual TDW for transmissions by the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0187] like Figure 4 As further shown, the signal 412 sent by the UE 102 can send a PUSCH and / or PUCCH transmission with repetitions, wherein the actual TDW is adjusted according to the time instance of the determined time / frequency compensation. In addition, the base station 104 can receive the PUSCH and / or PUCCH transmission and demodulate the DMRS according to the actual time domain window.
[0188] Reference now Figure 6 , a signal diagram depicting a process 600 for providing compensation reports to a base station 104 is provided. Figure 6As shown, a signal 602 sent by the base station 104 configures the UE 102 for transmission of periodic control channel message transmission. Periodic control channel message transmission can be any transmission mode in which a control channel message including uplink control information (UCI) is sent by the UE 102 at predetermined time intervals (rather than immediately in response to a downlink control message). In some embodiments, the periodic control channel message transmission may include a PUCCH message. The configuration of the periodic PUCCH may include parameters such as the format for sending control information, resource index, hopping mode, power offset, channel quality indicator (CQI) report configuration, DMRS bundling framework parameters, and other transmission parameters.
[0189] In an example embodiment, the base station 104 may configure the UE 102 to have periodic PUCCH transmissions. For example, the periodic configuration of the PUCCH may be accomplished via a scheduling request (SR) configuration (e.g., "SchedulingRequestResourceConfig") and a radio resource control (RRC) parameter (e.g., "periodicityAndOffset"). In one embodiment, the RRC parameter (e.g., "periodicityAndOffset") may be in a symbol or slot duration with different range values for different subcarrier spacings. As an example, the subcarrier spacing may be 15 kHz and the period is 160 slots.
[0190] like Figure 6 As further shown, a signal 604 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During a PUSCH transmission with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling consistently sends DMRS associated with PUSCH transmission repetitions. In the case where multiple PUSCH messages are sent as part of a PUSCH repetition frame and each PUSCH transmission is further configured with DMRS bundling, the DMRSs of the multiple transmissions can be processed jointly rather than individually to provide additional transmission improvement over the transmission improvement achieved by repetition.
[0191] like Figure 6As further shown, at block 606, the UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent the UE 102 from maintaining the phase continuity required for DMRS bundling. Based on any TA updates, the UE 102 may further determine the actual TDW within the nominal TDW. The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within the nominal TDW, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment to the time domain window (which results in the actual time domain window) may be the result of an event that results in a phase discontinuity of the channel of the portion of the DMRS being transmitted. For example, a TA update may result in an adjustment to the time domain window and a determination of the actual time domain window. The adjustment to the time domain window may include, but is not limited to, a time offset, a phase offset, a frequency change, and other similar adjustments.
[0192] like Figure 6 As further shown, a signal 608 sent by the UE 102 reports to the base station 104 a confirmation of the uplink time / frequency compensation of the UE 102 to indicate a successful TA update to the base station 104, or to report a planned or executed TA update instance(s) by providing a compensation report. The compensation report may be any indication of a planned time instance at which a TA adjustment occurred, or an executed time instance at which a TA adjustment has occurred. In some embodiments, the compensation report may include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on a provided time domain window (e.g., an offset).
[0193] like Figure 6As further shown, an example mechanism for sending a compensation report may include using a shared data field. As shown herein, a shared data field may be any bit, bit sequence, or other data field in a control channel message that is at least partially allocated for purposes other than sending a compensation report, such as an existing data field in a PUCCH. As an example, the UE 102 may send a compensation report using a combination of modulation symbols and control channel time / frequency resources. In particular, in conjunction with PUCCH format 1, the UE 102 may use a scheduling request (SR) data field and a HARQ-ACK data field to send a compensation report. In some embodiments, PUCCH format 1 is used to carry one or two ACK / NACK and / or SR symbols. When only SR is sent (e.g., it is not carried concurrently with HARQ ACK / NACK), SR is carried by π / 2 binary phase shift keying (BPSK) modulation. In some embodiments, it may be specified that for sending only SR, the information bit is set to a default value of 0 (e.g., mapped to BPSK symbol (+1)). By utilizing the SR resource, the presence of the compensation report may be indicated by setting the information bit on the SR resource to a value of 1 (eg, mapped to a BPSK symbol (-1)). Figure 6 Therefore, Figure 7 As shown, the compensation report 702 may be sent on a different BPSK modulation scheme than the SR request 704 .
[0194] like Figure 6 As further shown, at block 610, the base station 104 may receive a compensation report in a shared data field that includes a timing and / or frequency adjustment within a time domain window, such that a time instance when compensation is performed may be determined. The base station 104 may determine an actual TDW for transmissions by the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0195] like Figure 6 As further shown, the signal 612 sent by the UE 102 can send a PUSCH and / or PUCCH transmission with repetitions, wherein the actual TDW is adjusted according to the time instance of the determined time / frequency compensation. In addition, the base station 104 can receive the PUSCH and / or PUCCH transmission and demodulate the DMRS according to the actual TDW.
[0196] Reference now Figure 8 , a signal diagram depicting a process 800 for providing compensation reports to a base station 104 is provided. Figure 8 As shown, a signal 802 sent by the base station 104 configures the UE 102 for transmission of a periodic control channel message transmission. In some embodiments, the periodic control channel message transmission may include a PUCCH message.
[0197] like Figure 8 As further shown, a signal 804 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During a PUSCH transmission with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling can be particularly useful for PUSCH transmissions with repetitions.
[0198] like Figure 8 As further shown, at block 806, the UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent the UE 102 from maintaining the phase continuity required for DMRS binding. Based on any TA updates, the UE 102 may further determine the actual TDW within the nominal TDW. The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within the nominal TDW, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment of the time domain window that results in the actual time domain window may be the result of an event that results in a phase discontinuity of the channel of the portion of the DMRS being transmitted. For example, a TA update may result in an adjustment of the time domain window and a determination of the actual time domain window. The adjustment of the time domain window may include, but is not limited to, time offset, phase offset, frequency change, and other similar adjustments.
[0199] like Figure 8 As further shown, a signal 808 sent by the UE 102 reports to the base station 104 a confirmation of the uplink time / frequency compensation of the UE 102 to indicate a successful TA update to the base station 104, or to report a planned or executed TA update instance(s) by providing a compensation report. The compensation report may be any indication of a planned time instance at which a TA adjustment occurred, or an executed time instance at which a TA adjustment has occurred. In some embodiments, the compensation report may include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on a provided time domain window (e.g., an offset).
[0200] like Figure 8As further shown, signal 810 provides another example mechanism for sending a compensation report. As shown, in the case where the PUCCH is sent in a time slot before the PUSCH repetition, the UE can provide a compensation report to the base station before the transmission of the PUSCH repetition sent according to the actual time domain window. The compensation report can include information about when the time / frequency pre-compensation can occur so that the base station can determine the boundaries of the actual TDW applied by the UE.
[0201] like Figure 8 As further shown, at block 812, the base station 104 may receive a compensation report in a shared data field that includes a timing and / or frequency adjustment within a time domain window, such that a time instance when compensation is performed may be determined. The base station 104 may determine an actual TDW for transmissions by the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0202] like Figure 8 As further shown, the signal 814 sent by the UE 102 can send a PUSCH and / or PUCCH transmission with repetitions, wherein the actual TDW is adjusted according to the time instance of the determined time / frequency compensation. In addition, the base station 104 can receive the PUSCH and / or PUCCH transmission and demodulate the DMRS according to the actual TDW.
[0203] Reference now Fig. 9 , a signal diagram depicting a process 900 for providing a compensation report to a base station 104 is provided. Fig. 9 As shown, a signal 902 sent by the base station 104 configures the UE 102 for transmission of a periodic control channel message transmission. In some embodiments, the periodic control channel message transmission may include a PUCCH message.
[0204] like Fig. 9 As further shown, a signal 904 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During a PUSCH transmission with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling can be particularly useful for PUSCH transmissions with repetitions.
[0205] like Fig. 9As further shown, at block 906, the UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent the UE 102 from maintaining the phase continuity required for DMRS bundling. Based on any TA updates, the UE 102 may further determine the actual TDW within the nominal TDW. The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within the nominal TDW, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment to the time domain window (which results in the actual time domain window) may be the result of an event that results in a phase discontinuity of the channel of the portion of the DMRS being transmitted. For example, a TA update may result in an adjustment to the time domain window and a determination of the actual time domain window. The adjustment to the time domain window may include, but is not limited to, a time offset, a phase offset, a frequency change, and other similar adjustments.
[0206] like Fig. 9 As further shown, a signal 908 sent by the UE 102 may send a PUSCH and / or PUCCH transmission with repetitions according to the actual TDW calculated at block 906 and adjusted according to the time instance of the determined time / frequency compensation.
[0207] like Fig. 9 As further shown, a signal 910 sent by the UE 102 reports to the base station 104 a confirmation of the uplink time / frequency compensation of the UE 102 to indicate a successful TA update to the base station 104, or to report a planned or executed TA update instance(s) by providing a compensation report. The compensation report may be any indication of a planned time instance at which a TA adjustment occurred, or an executed time instance at which a TA adjustment has occurred. In some embodiments, the compensation report may include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on a provided time domain window (e.g., an offset).
[0208] like Fig. 9 As further shown, one example mechanism for sending a compensation report may include sending the compensation report in a control channel time slot after a shared channel repetition. As shown, in the case where the PUCCH is sent in a time slot after the PUSCH repetition, the UE may provide a compensation report to the base station after the transmission of the PUSCH repetition that was sent according to the actual time domain window. The compensation report may include information about when time / frequency pre-compensation occurs in the PUSCH transmission so that the base station can determine the boundaries of the actual TDW applied by the UE.
[0209] like Fig. 9As further shown, the signal 912 transmitted by the base station 104 may receive a compensation report in a shared data field that includes a timing and / or frequency adjustment within a time domain window, such that a time instance when compensation is performed may be determined. The base station 104 may determine an actual TDW for a previously transmitted transmission of the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0210] Reference now Fig.10 , a signal diagram depicting a process 1000 for providing a compensation report to a base station 104 is provided. Fig.10 As shown, a signal 1002 sent by the base station 104 configures the UE 102 for transmission of a periodic control channel message transmission. In some embodiments, the periodic control channel message transmission may include a PUCCH message.
[0211] like Fig.10 As further shown, a signal 1004 sent by the base station 104 schedules a PUSCH transmission with repetitions. PUSCH transmissions with repetitions can improve the reliability of data transmission from the UE 102 to the base station 104. During a PUSCH transmission with repetitions, a transmitter (e.g., UE 102) sends data packets with different redundancy versions (RVs) multiple times. The receiver can then combine the received packets and request retransmission of any lost or damaged packets. DMRS bundling can be particularly useful for PUSCH transmissions with repetitions because DMRS bundling consistently sends DMRS symbols associated with the PUSCH transmission repetitions.
[0212] like Fig.10 As further shown, at block 1006, the UE 102 determines the pre-compensation timing and the actual TDW. Certain events may occur within the communication network 102 that prevent the UE 102 from maintaining the phase continuity required for DMRS binding. Based on any TA updates, the UE 102 may further determine the actual TDW within the nominal TDW. The actual time domain window may be any time domain window resulting from one or more adjustments to time and / or frequency within the nominal TDW, such as an uplink time domain window configured by the base station 104 for the UE 102. In some embodiments, the adjustment to the time domain window (which results in the actual time domain window) may be the result of an event that results in a phase discontinuity of a DMRS symbol. For example, a TA update may result in an adjustment to the time domain window and a determination of the actual time domain window. The adjustment to the time domain window may include, but is not limited to, a time offset, a phase offset, a frequency change, and other similar adjustments.
[0213] like Fig.10As further shown, a signal 1008 sent by the UE 102 reports to the base station 104 a confirmation of the uplink time / frequency compensation of the UE 102 to indicate a successful TA update to the base station 104, or to report a planned or performed TA update instance(s) by providing a compensation report. The compensation report may be any indication of a planned time instance at which a TA adjustment occurred, or a performed time instance at which a TA adjustment has occurred. In some embodiments, the compensation report may include an actual time domain window, information for determining the actual time domain window, and / or information for determining the actual time domain window based on a provided time domain window (e.g., an offset).
[0214] like Fig.10 As further shown, one example mechanism for sending a compensation report may include the UE notifying the base station by sending a specific control channel resource across all configured control channel resource sets. In such an embodiment, the UE may not send a compensation report containing absolute timing information or confirmation periodically (but only when an update is needed). The compensation report may be carried across all configured control channel resource sets via a specific time / frequency control channel (e.g., PUCCH-ResourceIdXX). Thus, the receipt of UCI via a specific selected control channel resource may be an indicator to the base station that a compensation report has been sent.
[0215] An example implementation may include allocating some of the control channel resources to a compensation resource set group. The compensation resource set group may include control channel resources, such as ResourceId, that have been allocated as potential resources for sending compensation report information. The UE may select the control channel resources allocated for sending the compensation report so as to send the compensation report containing the actual time domain window. The UE may select the control channel resources based on availability and / or according to a set of predefined rules so that the control channel resources may still achieve any other purpose they may serve. Due to the need to share control channel resources to achieve other purposes, the UE may choose to send the compensation report only if the compensation report has been updated or otherwise changed.
[0216] As a specific example, the UE may allocate PUCCHs with PUCCH-ResourceId equal to 124, 125, 126, and 127 to a compensation resource set group designated for sending compensation reports. As described herein, the selected PUCCH-ResourceId may potentially belong to a different PUCCH resource set supporting other PUCCH formats. Thus, the UE will use the allocated resource set only when confirmation or absolute timing needs to be reported via compensation reports (e.g., when the compensation reports have been changed or updated). The described method may be advantageous because the method is consistently applied to all PUCCH formats.
[0217] Similarly, in some embodiments, the UE may be configured with up to four PUCCH-ResourceSets. In addition, PUCCH-ResourceSetId0 may contain only resources for PUCCH format 0 and PUCCH format 1, and up to thirty-two PUCCH-Resource instances. Alternatively, PUCCH-ResourceSetId1, PUCCH-resourceSetId2, and PUCCH-ResourceSetId3 may contain only resources for PUCCH formats 2, 3, and 4, and each PUCCH-ResourceSet may have up to 8 PUCCH-Resource instances. In addition, each PUCCH-Resource has a unique ID across all PUCCH-ResourceSets, so the PUCCH resources can be identified by the base station when received. In addition, in some embodiments, PUCCH-ResourceId 31, 39, 47, and 55 may not be used at any other time. Therefore, the unused resource IDs used for PUCCH transmissions may be used to indicate compensation reports determined by the UE. The above concept can be easily extended to the case where only a subset of PUCCH-ResourceSets are configured and in each of the configured PUCCH-ResourceSets, more than one PUCCH-ResourceId is allocated for carrying compensation reports.
[0218] In another implementation, the UE may provide information about the actual TDW as a port of a MAC control element (MAC-CE), where the UE provides information about the exact time at which it will update the timing advance parameter. Under this approach, the UE may be restricted to changing the transmit timing only at dedicated times, such as every 4th or 8th time slot. The UE may lose some freedom in providing compensation reports, however, the UE can guarantee that phase consistency can remain consistent during this period.
[0219] like Fig.10 As further shown, at block 1010, the base station 104 may receive a compensation report in a shared data field that includes a timing and / or frequency adjustment within a time domain window, such that a time instance when compensation is performed may be determined. The base station 104 may determine an actual TDW for transmissions by the UE 102 on the uplink communication flow 106 within the configured nominal TDW based on the compensation report.
[0220] like Fig.10As further shown, a signal 1012 sent by the UE 102 may send a PUSCH and / or PUCCH transmission with repetitions, wherein the actual TDW is adjusted according to the time instance of the determined time / frequency compensation. In addition, the base station 104 may receive the PUSCH and / or PUCCH transmission and demodulate the DMRS according to the actual TDW.
[0221] Reference now Fig.11 , a flow chart depicting a process 1100 for notifying a base station (e.g., base station 104) of a compensation report is provided. At box 1102, an apparatus 200 (which may be implemented by or associated with a UE (e.g., UE 102)) includes components, such as a processor 202, a communication interface 204, etc., for receiving information defining a time domain window from a base station, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be sent. As described herein, a base station (e.g., base station 104) may configure the UE to send a reference signal, such as a DMRS, in a particular time window. For example, as described with respect to Figure 3 As described above, the base station may configure the UE to have periodic PUCCH transmission. The base station may search for DMRS in a specific configured time window.
[0222] At block 1104, the apparatus 200 includes means, such as the processor 202, for determining an actual time domain window, wherein the actual time domain window is based at least in part on information defining a time domain window in an uplink communication flow and on at least one adjustment of a reference signal in at least one of time or frequency due to physical characteristics of a transmission environment. Figure 3 As described, the UE may consider the relative positions and velocities of other components of the communication network, such as the position and velocity of the UE, the position and velocity of the base station, and / or the position and velocity of the satellites in the NTN, to determine any time and / or frequency adjustments that may be required for the transmitted signal. Any time or frequency adjustment of the TDW will result in a TDW that is different from the nominal TDW. The UE may coordinate with the base station on the timing of the adjustments to ensure accurate and reliable communication.
[0223] At block 1106, the apparatus 200 includes components, such as the processor 202, the communication interface 204, etc., for causing a compensation report to be sent to the base station in a control channel message within an uplink communication flow, wherein the compensation report includes an indication of at least one adjustment. The compensation report may include a confirmation that the UE successfully performed time / frequency compensation, for example, in the case where the compensation report is sent after the transmitted data is sent on the uplink communication flow. In some embodiments, the compensation report may include an absolute timing indicating the number of milliseconds and / or time slots at which the DMRS is to be sent. The actual time domain window may be determined based on the compensation report. Once the compensation report is received, the base station may begin looking for the DMRS in the actual time domain window.
[0224] There are many ways to send compensation reports to the base station. Figure 4-Figure 7 As described above, the compensation report may use a shared data field to implicitly indicate the compensation report. For example, the UE may use a cyclic shift parameter, an SR parameter, or a HARQ ACK / NACK parameter to indicate the compensation report.
[0225] In addition, as regards Fig.10 As described above, the UE may implicitly send the compensation report on the PUCCH via a specific PUCCH resource (eg, PUCCH-resourceID).
[0226] In another embodiment, the compensation report may be sent using periodic PUCCH transmission opportunities, where the UE explicitly indicates the duration, or the UE explicitly indicates the acknowledgement through a dedicated data field. Figure 3 Sending the compensation report via a dedicated data field is further described.
[0227] In some embodiments, the compensation report may be sent via a control channel message on the uplink communication flow in coordination with an uplink shared control channel repetition message, such as with respect to Figures 8 to 9 As further described.
[0228] In another embodiment, the compensation report may be sent via UCI multiplexing on one of the PUSCH transmissions of a set of scheduled PUSCH repetitions including DMRS bundling. In such an embodiment, the UCI including the compensation report may be multiplexed across PUSCH repetitions in the first PUSCH transmission, the last PUSCH transmission, or one PUSCH transmission in the PUSCH transmission. The base station may further configure the interval for such UCI multiplexing to ensure that the information contained in the compensation report is sent in a timely manner, but not in all PUSCH repetitions. Such an embodiment frees up resources that may otherwise be required to send compensation reports at a higher frequency.
[0229] At block 1108, the apparatus 200 includes means, such as the processor 202, the communication interface 204, etc., for causing a reference signal to be transmitted to a base station in an actual time domain window.
[0230] Determining the actual time domain window based on one or more physical characteristics of the transmission environment using process 1100 can enable accurate and efficient communication on a communication network (e.g., communication network 100) as described herein. By determining and reporting time / frequency compensation through compensation reporting, the UE can further improve channel estimation through DMRS bundling and other similar mechanisms. In addition, advanced 5G features such as beamforming, spatial multiplexing, multiple-input multiple-output (MIMO) communications, and communications on non-terrestrial networks (NTNs) can be greatly enhanced.
[0231] Reference now Fig.12 , a flow chart depicting a process 1200 for receiving a compensation report from a UE at a base station is provided. At box 1202, the apparatus 200 (which can be implemented by a base station (e.g., base station 104) or associated with a base station (e.g., base station 104)) includes components, such as a processor 202, a communication interface 204, etc., for causing information defining a time domain window to be sent toward a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which at least a reference signal is to be sent. As described herein, the base station can configure the UE to send a reference signal, such as a DMRS, in a specific time window. For example, as described with respect to Figure 3 As described above, the base station may configure the UE to have periodic PUCCH transmission. The base station may be configured to search for DMRS in a specified time domain window.
[0232] At block 1204, the apparatus 200 includes means, such as the processor 202, the communication interface 204, etc., for receiving a compensation report from a user equipment in a control channel message within an uplink communication flow, wherein the compensation report includes an indication of at least one adjustment of at least one of time or frequency to a reference signal due to a physical characteristic of a transmission environment. Figure 3As described, the UE can determine and send a compensation report based on the physical characteristics of the transmission medium and the physical settings of the communication network. The compensation report can take into account the relative positions and speeds of the components of the communication network, such as the position and speed of the UE, the position and speed of the base station, and / or the position and speed of the satellite in the NTN. Any time or frequency adjustment to the TDW will result in an actual TDW, in which the DMRS can be sent to ensure accurate and reliable communication. The compensation report may include confirmation that the UE successfully performs time / frequency compensation, for example, in the case where the compensation report is sent after the transmitted data is sent on the uplink communication stream. In some embodiments, the compensation report may include an absolute timing indicating the milliseconds and / or the number of time slots in which the DMRS is to be sent. The actual time domain window can be determined based on the compensation report. Once the compensation report is received, the base station can start looking for the DMRS in the actual time domain window.
[0233] At block 1206, the apparatus 200 includes components, such as the processor 202, the communication interface 204, etc., for receiving a reference signal from the user equipment in an actual time domain window, wherein the actual time domain window is based at least in part on at least one adjustment. Once the base station is notified of an update to the TDW based on the compensation report, the base station may receive the reference signal in the actual time domain window.
[0234] Coordinated reception of time and frequency adjustments to transmitted control channel signals can enable accurate and efficient communications over a communication network (e.g., communication network 100) as described herein. Reception of time and frequency adjustments through compensation reporting can enable the use of various techniques to improve transmission speed, accuracy, and reliability of wireless transmissions. Enhanced channel estimation can greatly enable advanced features, including beamforming, spatial multiplexing, multiple-input multiple-output (MIMO) communications, and communications over non-terrestrial networks (NTNs).
[0235] Fig.11 and Fig.1220 is a flowchart depicting a method according to an example embodiment of the present disclosure. It should be understood that each block of the flowchart and the combination of blocks in the flowchart can be implemented by various means, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more of the above processes can be implemented by computer program instructions. In this regard, the computer program instructions embodying the above processes can be stored by a volatile memory and / or a non-volatile memory of a device using an embodiment of the present disclosure, and executed by processor 202. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine so that the resulting computer or other programmable device implements the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable memory, which can instruct a computer or other programmable device to work in a specific manner so that the instructions stored in the computer-readable memory produce a manufactured product, the execution of which implements the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions executed on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
[0236] Therefore, the block of the flow chart supports the combination of the components for performing the specified functions and the combination of the operations for performing the specific functions. It will also be understood that one or more blocks of the flow chart and the combination of the blocks in the flow chart can be implemented by a computer system based on special-purpose hardware that performs the specified functions, or a combination of special-purpose hardware and computer instructions.
[0237] The term "comprising" is used in this document in an inclusive rather than exclusive sense. That is, any reference to X including Y indicates that X may include only one Y or more than one Y. If the exclusive meaning of "comprising" is intended, it will be clear in the context by referring to "including only one" or using "consisting of".
[0238] In this specification, reference has been made to various examples. The description of features or functions of an example indicates that those features or functions are present in the example. The use of the term "example" or "for example" or "may" or "can" in the text indicates that, whether explicitly stated or not, such features or functions are present in at least the described example, whether described as an example or not, and they may, but not necessarily, be present in some or all other examples. Therefore, "example", "for example", "may" or "can" refers to a specific instance in a class of examples. The attributes of an instance may be attributes of only the instance, or attributes of a class, or attributes of a subclass of a class, wherein the subclass includes some but not all instances in the class. Therefore, it is implicitly disclosed that features described with reference to one example rather than with reference to another example may be used in the other example as part of a working combination where possible, but not necessarily in the other example.
[0239] Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.
[0240] Features described in the above description may be used in other combinations than the combinations explicitly described above.
[0241] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.
[0242] Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not.
[0243] The terms "a" or "the" as used in this document are inclusive and not exclusive. That is, any reference to X that includes one / the Y indicates that X may include only one Y or more than one Y, unless the context clearly indicates otherwise. If the exclusive meaning of "a" or "the" is intended, it should be clearly stated in the context. In some cases, "at least one" or "one or more" may be used to emphasize the inclusive meaning, but the absence of these terms should not be regarded as inferring any exclusive meaning.
[0244] The presence of a feature (or combination of features) in a claim refers to the feature or (combination of features) itself, as well as features that achieve substantially the same technical effect (equivalent features). For example, equivalent features include features that are variants and achieve substantially the same result in substantially the same way. For example, equivalent features include features that perform substantially the same function in substantially the same way to achieve substantially the same result.
[0245] In this specification, reference has been made to various examples using adjectives or adjective phrases to describe features of the examples. Such description of a characteristic associated with an example indicates that the characteristic exists in some examples exactly as described, and in other examples substantially as described.
[0246] While efforts have been made in the foregoing description to draw attention to those features regarded as being of significance, it should be understood that the applicant may seek protection by way of claims for any patentable feature or combination of features mentioned above and / or shown in the drawings, whether or not emphasis has been placed thereon.
[0247] With the benefit of the teachings given in the above description and the related drawings, those skilled in the art to which these embodiments belong will come to think of many modifications and some embodiments of the present disclosure set forth herein. Therefore, it should be understood that the present disclosure is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims.
[0248] In addition, although the above description and related drawings describe some embodiments in the context of certain example combinations of elements and / or functions, it should be understood that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated, as described in some of the appended claims. Although specific terms are used herein, they are used only in a general and descriptive sense, and not for the purpose of limitation.
Claims
1. A device for communication, comprising: means for receiving, at a user equipment, from a base station, information defining a time domain window, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be transmitted; A component used to determine the actual time domain window, wherein the actual time domain window is based at least in part on the information defining the time domain window in the uplink communication flow and on at least one adjustment of at least one of time or frequency to a reference signal due to physical characteristics of a transmission environment; means for causing a compensation report to be sent to said base station in a control channel message within said uplink communication flow, wherein the compensation report includes an indication of the at least one adjustment; and means for causing the reference signal to be sent to the base station in the actual time domain window.
2. The apparatus according to claim 1, further comprising: A component for generating a compensation report, the compensation report comprising: compensation information related to at least one of frequency adjustment and timing adjustment.
3. The apparatus according to any one of claims 1 to 2, wherein the physical characteristics of the transmission environment include: At least one of a physical characteristic of a transmission medium, a physical location of a base station, or a physical location of a user equipment.
4. The device according to any one of claims 1 to 2, further comprising: Means for causing the control channel message to be transmitted according to a physical uplink control channel (PUCCH).
5. The device according to any one of claims 1 to 2, further comprising: Means for causing the compensation report to be sent in a dedicated data field of the control channel message.
6. The device according to any one of claims 1 to 2, further comprising: Means for causing the compensation report to be sent in a shared data field of the control channel message.
7. The apparatus of claim 6, wherein the shared data field comprises a base sequence, and wherein the compensation report is encoded by applying a cyclic shift to the base sequence.
8. The apparatus of claim 6, wherein the shared data field is at least one of a modulation symbol data field or a resource selection data field.
9. The device according to any one of claims 1 to 2, further comprising: Means for allocating a subset of control channel resources to a group of compensation resource sets and causing the compensation report to be sent on the available compensation resource set in a control channel message if the compensation report is updated.
10. The apparatus according to any one of claims 1 to 2, wherein the uplink communication flow comprises one or more shared channel repetitions, and the apparatus further comprises: Means for causing the compensation report to be transmitted in coordination with the shared channel repetitions.
11. The apparatus according to claim 9, further comprising: Means for causing the compensation report to be sent subsequent to the shared channel repetition, wherein the compensation report indicates the at least one adjustment to a previously sent reference signal.
12. The apparatus of claim 10, wherein in a case where the one or more shared channel repetitions do not fill an allocated time slot for a shared channel repetition, the apparatus further comprises: Means for causing an acknowledgement control channel message to be sent indicating the at least one adjustment of the reference signal.
13. The apparatus of any one of claims 1 to 2, wherein the compensation report confirms the transmission of the reference signal, wherein the at least one adjustment has been applied or is to be applied.
14. The apparatus according to claim 10, further comprising: Means for causing the compensation report to be sent prior to a repetition of the shared channel, wherein the compensation report indicates the at least one adjustment to a future reference signal.
15. An apparatus for communication, comprising: means for causing information defining the time domain window to be sent to a user equipment, wherein the time domain window indicates a time window in an uplink communication flow in which a reference signal is to be transmitted; means for receiving a compensation report from the user equipment in a control channel message within the uplink communication flow, wherein the compensation report includes: an indication of at least one adjustment made to the reference signal in at least one of time or frequency due to a physical characteristic of a transmission environment; as well as means for receiving the reference signal from the user equipment in an actual time domain window, Wherein the actual time-domain window is based at least in part on the at least one adjustment.
Citation Information
Cited By
Uplink transmission compensation
WO2026086254A1
