Embodiments of the present application generally relate to wireless communication technology, and especially to a method and apparatus for delay indication.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, and so on. Wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of wireless communication systems may include fourth generation (4G) systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may also be referred to as new radio (NR) systems.
To extend the coverage and availability of wireless communication systems (e.g., 5G systems), satellite and high-altitude platforms may be utilized as relay devices in communications related to ground devices such as user equipment (UE). Network or segment of network using radio frequency (RF) resources on board a satellite or an airborne aircraft may be referred to as a non-terrestrial network (NTN). In an NTN network, some or all functions of a base station (BS) may be deployed in a satellite or an airborne aircraft.
However, there is large propagation delay(s) in the NTN network due to the high attitude of satellites. Thus, how to indicate to a UE the delay(s) between a downlink (DL) channel and an uplink (UL) channel and timing advance (TA) needs to be considered.
Embodiments of the present application provide a method and apparatus for delay indication, e.g., between a DL channel and an UL channel and TA in a NTN network.
An embodiment of the present application provides a method. The method may include: receiving at least one signaling indicating at least one of a TA and a time domain difference between reception on a DL channel and transmission on an UL channel; and determining the at least one of the TA and the time domain difference based on the at least one signaling.
In an embodiment of the present application, the transmission on the UL channel is after the reception on the DL channel. The TA or the time domain difference is one value or multiple values shared by multiple UEs. In the case that the TA or the time domain difference is the multiple values, one of the multiple values is further indicated.
In an embodiment of the present application, the value or the one of the multiple values is indicated by at least one of radio resource control (RRC) signaling and medium access control (MAC) control element (CE) signaling
In another embodiment of the, present application, the value or the one of the multiple values is indicated by a group common downlink control information (DCI).
In another embodiment of the present application, the value or the one of the multiple values is indicated by a UE specific DCI. In an example, the value or the one of the multiple values is indicated by at least one added bit in the UE specific DCI compared with legacy UE specific DCI. In another example, the value or the one of the multiple values is indicated by using time domain resource assignment field in the UE specific DCI. In yet another example, the value or the one of the multiple values is indicated by using physical downlink shared channel (PDSCH) to hybrid automatic repeat request (HARQ) feedback timing indicator in the UE specific DCI.
In an embodiment of the present application, the method may further include: receiving a signaling indicating relationship between the TA or the time domain difference and random access channel (RACH) resource. In an example, the TA or the time domain difference is one value or multiple values shared by multiple UEs, and the value or the one of the multiple values is indicated by using physical random access channel (PRACH) mask index in the UE specific DCI. In another example, the TA or the time domain difference is one value or multiple values shared by multiple UEs, and method further includes: reporting the value or one of the multiple values by selection of RACH resource for PRACH transmission.
In an embodiment of the present application, the value or the one of the multiple values is indicated by using TA command in random access response (RAR) or MAC CE signaling.
In an embodiment of the present application, the value of the TA or the time domain difference is predefined or broadcasted in system information block (SIB). In an example, the value is applied to the time domain difference between 2-step RACH RAR and physical uplink control channel (PUCCH) transmission. In another example, the value is applied to a time duration between RACH retransmissions. In another example, the value is applied to a minimum time between Msg.B RAR and PUSCH transmission. In another example, the value is applied to minimum time between Msg.4 RAR and PUCCH transmission. In another example, the value is applied to a gap between non-zero power channel state information-reference signal (NZP CSI-RS) and sounding reference signal (SRS) for non-codebook based physical uplink shared channel (PUSCH) transmission.
In an embodiment of the present application, the signaling indicates at least one value and is based on misalignment between transmission(s) in the DL channel and reception(s) in the UL channel at a base station side and the reception on the DL channel is after the transmission on the UL channel at a user equipment side.
In an embodiment of the present application, the value is indicated by at least one of the following: SIB, RRC signaling, MAC CE signaling, and group common DCI.
In an embodiment of the present application, a first value of the at least one value is an initial value, and a second value is a change rate dependent on time of the first value.
In an embodiment of the present application, the at least one signaling is applied to MAC CE activation delay.
In another embodiment of the present application, the at least one signaling is applied to time domain duration between beam failure recovery (BFR) PRACH transmission and PDCCH monitoring.
In another embodiment of the present application, the at least one signaling is applied to time domain duration between configured grant based PUSCH transmission and PDCCH monitoring.
Another embodiment of the present application provides a method. The method may include: determining at least one of a TA and a time domain difference between reception on a DL channel and transmission on an UL channel; and transmitting at least one signaling indicating the at least one of the TA and the time domain difference between the reception on the DL channel and the transmission on the UL channel.
Another embodiment of the present application provides an apparatus. The apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter. The computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.
The embodiments of the present application can at least solve the technical problem concerning on how to indicate to the UE at least one the scheduling delay, the feedback delay and TA corresponding to multiple reference points and how to indicate to the UE a UL to DL timing relationship (U to D delay) for transparent payload due to misalignment between DL transmitting (Tx) and UL receiving (Rx) at a network side (e.g., a BS network side).
In order to describe the manner in which advantages and features of the application can be obtained, a description of the application is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only example embodiments of the application and are not therefore to be considered limiting of its scope.
The detailed description of the appended drawings is intended as a description of preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.
Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architecture and new service scenarios, such as 3GPP 5G (NR), 3GPP LTE, and so on. It is contemplated that along with the developments of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and moreover, the terminologies recited in the present application may change, which should not affect the principle of the present application.
Referring to
Generally, to extend the coverage and availability of wireless communication systems, some or all functions of a BS may be deployed in a satellite. That is, in the NTN network, a satellite may be also referred to as a BS. For example, a satellite may generate beams over a certain service area, which may also be referred to as a cell coverage area. The concept of cell with respect to a terrestrial BS may similarly apply to a satellite serving as a BS. Such network or segment of network using RF resources on board a satellite or an airborne aircraft may be referred to as an NTN network. Hereafter, the BS(s) illustrated in the specification all cover any type of devices with the substantial function of a BS, including a satellite 120, a terrestrial BS 140 or the like.
As shown in
Satellite(s) 120 may include low earth orbiting (LEO) satellites, medium earth orbiting (MEO) satellites, geostationary earth orbiting (GEO) satellites, as well as highly elliptical orbiting (HEO) satellites. In some embodiments of the present application, alternatively, a satellite 120 may be an unmanned aircraft systems (UAS) platform. The UAS platform(s) may include tethered UAS and lighter than air (LTA) UAS, heavier than air (HTA) UAS, and high altitude platform (HAP) UAS.
The satellite 120 may provide a plurality of geographic areas (footprint) 160 for serving UEs 110 located in one or more of the geographic areas. A geographic area 160 can be associated with a cell, and can also be associated with a beam. When the geographic area 160 is associated with a cell, it can be named as a “cell footprint.” When the geographic area 160 is associated with a beam, it can be named as a “beam footprint.” In
The gateway 130 may be coupled to a data network 150 such as, for example, the Internet, terrestrial public switched telephone network, mobile telephone network, or a private server network, etc. The gateway 130 and the satellite 120 communicate over a feeder link 120, which has both a feeder uplink from the gateway to the satellite 120 and a feeder downlink from the satellite 120 to the gateway 130. Although a single gateway 130 is shown, some implementations will include more gateways, such as five, ten, or more.
One or more terrestrial BSs 140 (i.e., not airborne or spaceborne) are provided within a typical terrestrial communication network, which provides geographical radio coverage, wherein the UEs 110 that can transmit and receive data within the radio coverage (cell coverage) of the terrestrial BS 140. In the terrestrial communication network, a terrestrial BS 140 and a UE 110 can communicate with each other via a communication link, e.g., via a downlink radio frame from the terrestrial BS 140 to the UE 110 or via an uplink radio frame from the UE 110 to the terrestrial BS 140.
Although a limited number of UEs 110 and satellites 120 etc., are illustrated in
According to some embodiments of the present application, a scheduling delay between a DL channel and a UL channel (such as a delay between PDCCH and PUSCH), a feedback delay between a DL channel and a UL channel (such as a delay between PDSCH and PUCCH) and a TA for a UL transmission will be impacted by a propagation delay between a satellite (such as, the satellites 120 in
As shown in
According to some embodiments of the present application, a geographical area (footprint) generated by a satellite is always large, and the propagation delay difference between different UEs (such as a UE nearby the satellite and a UE far away from the satellite) may be multiple symbols.
As shown in
The satellite may transmit the positions of the multiple reference points to the UEs (such as, UE #1, UE #2, and UE #3 in
However, there is no technical solution on how to indicate to the UE the scheduling delay or the feedback delay and TA corresponding to a specific reference point of the multiple reference points. In addition, compared with the case without a reference point, the signaling overhead of the scheduling or feedback delay and TA needs to be saved in the case with reference point(s).
In another aspect, transparent payload is supported in the future. As discussed above, when a satellite carries a transparent payload, it performs only radio frequency filtering, frequency conversion and/or amplification of signals on board.
For the transparent payload, a UE can know its own position and the position of the satellite, but does not know the distance between the satellite and a ground station (e.g., a ground BS). When calculating the TA, the UE may only calculate a part of the delay. Thus misalignment between transmission(s) in DL channel and reception(s) in UL channel (such as, frame, slot, or symbol boundary) at gNB side will be unavoidable.
As shown in
However, there is no technical solution on how to indicate to a UE the UL to DL timing relationship (U to D delay) for transparent payload due to the misalignment between DL Tx and UL Rx at a BS side.
As shown in
In an example, the transmission on the UL channel is after the reception on the DL channel, and the TA and the time domain difference is associated with a specific reference point of multiple reference points. The TA or the time domain difference is one value or multiple values shared by multiple UEs. In the case that the TA or the time domain difference is the multiple values, one of the multiple values may be further indicated e.g., by the BS.
In another example, the reception on the DL channel is after the transmission on the UL channel at a user equipment side. The time domain difference between UL transmission and DL reception at UE side may be based on the misalignment between transmission(s) in the DL channel and reception(s) in the UL channel at a base station side.
In step 520, the BS transmits at least one signaling indicating the at least one of the TA and the time domain difference between the reception on the DL channel and the transmission on the UL channel to a UE (e.g., UE 110 in
After receiving the signaling, in step 530, the UE determines the at least one of the TA and the time domain difference based on the received signaling.
The following will describe some embodiments of the present application in detail.
Some embodiments of the present application concern on how to indicate to a UE at least one of the scheduling delay, feedback delay and TA corresponding to multiple reference points. The scheduling delay may indicate a delay between PDCCH and PUSCH, and the PUSCH is after the PDCCH. The feedback delay may indicate a delay between PDSCH and PUCCH, and the PUCCH is after the PDSCH. In some cases, the time domain difference may indicate the scheduling delay; in some cases, the time domain difference may indicate the feedback delay; and in some other cases the time domain difference may indicate both of them. The time domain difference (the scheduling delay or the feedback delay) or the TA may be one value or multiple values shared by multiple UEs. In case that the TA or the time domain difference is multiple values, one of the multiple values may be further indicated, which will be described in detail. The multiple values may be associated with multiple reference points.
The time domain difference (the scheduling delay or the feedback delay) can be represented as: D_total=k_offset_common+D_reference_point+K1. Where K_offset_common can be common for a beam, which is defined in the legacy 3GPP release and will not be described in detail. D_reference_point is UE specific, and updated in a large time scale. D_reference_point may be also written as D_referencepoint. K1 is dynamically indicated by UE-specific DCI, which is also defined in the legacy 3GPP release and will not be described in detail.
The TA for UL transmission can be represented as: TA_total=TA_common_per_beam+TA_offset_reference_point+TA_UE. Where TA_common_per_beam is indicated in a beam specific way or a cell specific way. TA_offset_reference_point, and updated in a large time scale. In most cases, TA_offset_reference_point is the same as D_reference_point. TA_UE is the legacy TA indication, which is defined in the legacy 3GPP release and will not be described in detail either.
In some embodiments of the present application, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated in various ways, which will be described in conjunction with the following detailed embodiments of present application.
In an embodiment of the present application, the time domain difference (e.g., the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by at least one of RRC signaling and MAC CE signaling.
In an example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by RRC signaling in a UE specific way.
In another example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by MAC CE signaling.
In yet another example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by RRC signaling and MAC CE signaling. For example, the RRC signaling may configure multiple feedback delays associated with multiple reference points, and the MAC CE signaling may activate one feedback delay associated with a reference point.
Table 1 illustrates an example of a MAC CE command. In the table, R indicates a field, the serving cell index indicates a serving cell, the BWP index indicates a BWP, and Ci (i=0, 1 . . . 7) indicates an active status for the time domain difference (the scheduling delay or the feedback delay) or the TA corresponding to the (i+1)-th reference point. For example, when C4 is 1, and other elements are 0, that means the value corresponding to the specific reference point associated with C4 will be used.
In another embodiment of the present application, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by a group common DCI for a specific UE. For example, a specific payload position can be configured by RRC signaling for each UE. The specific payload position indicates a position of the delay or the TA for the specific UE in the DCI.
In another embodiment of the present application, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by a UE specific DCI. In particular, a list of multiple feedback delays or feedback delays or the TAs associated with multiple reference points can be configured by at least one of RRC signaling and MAC CE signaling, and then a value may be indicated by the UE specific DCI from the list.
In an example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by at least one added bit in the UE specific DCI compared with legacy UE specific DCI. For example, 2 bits in DCI scheduling PDSCH or PUSCH are used to indicate one of four delays or TAs, and each of the delay or TA is associated with a reference point.
In another example, the time domain difference (e.g., the scheduling delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by using time domain resource assignment field in the UE specific DCI. In this case, the time domain difference or TA is jointly encoded with K2. That is, the time domain resource assignment field in the current DCI can be reused in this example of the present application. K2 is a slot delay between PDCCH and PUSCH.
In particular, the time domain resource assignment field in the DCI may indicate a value, and K2 may be obtained by looking up a corresponding table. Thus the delay or TA will be obtained based on K2. Currently, K2=j, j+1, j+2, j+3, where j=1, 2, 3 indicated by PUSCH numerology. K2 is jointly encoded with S, L, and the PUSCH mapping type, and is represented by using 4 bits. S is a start position of PUSCH, and L is a length of PUSCH.
For example, with jointly encoding of K2 and the scheduling delay or the TA, when K2=j+2, j+3, the actual K2 is j, j+1, respectively and the scheduling delay or the TA is the value associated with a reference point, e.g., R1; and when K2=j, j+1, the actual K2 value is j and j+1 respectively, and the scheduling delay or the TA is the value associated with another reference point, e.g., R0. That is, in this example, K2 has four values, and are divided two groups, that is, K2=j, j+1 is associated with reference point R0 and the K2=j+2, j+3 is associated with reference point R1.
In another example, the time domain difference (e.g., the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by using PUSCH to hybrid automatic repeat request (HARQ) feedback timing indicator in the UE specific DCI. In this case, the time domain difference or TA is jointly encoded with K1. That is, the PDSCH to HARQ feedback timing indicator in the current DCI can be used in this example of the present application.
K1 is a slot delay between PUSCH and PUCCH. As discussed above, K1 is indicated by UE-specific DCI dynamically. Currently, K1 can be at most configured to be 3 bits. For DCI 1-0 format, K1 is one value selected from 0-7; for DCI 1-1 format, K1 is one value selected from −1 to 15; and for DCI 1-2 format, K1 is one value selected from 0-15.
For example, after jointly encoding, when K1 is to be selected from 1st to 4th value configured by RRC signaling, the feedback delay or the TA is associated with a reference point, e.g., R0, and when K1 is to be selected from 5th and 8th value configured by RRC signaling, the feedback delay or the TA is associated with another reference point, e.g., R1.
In another embodiment of the present application, there is an implicit association between the time domain difference (the scheduling delay or the feedback delay) or the TA and RACH resource, and the time domain difference or TA is associated with a specific reference point of the multiple reference points.
The mapping (or association) relationship between the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point and RACH resource is configured by broadcast or by RRC signaling by the BS. The RACH resource can be a time domain resource, frequency domain resource, or code domain resource. In an example, the RACH resource is a time domain resource. When the RACH resource at this time is associated with the time domain difference or the TA of a reference point, e.g., R0, the next RACH resource is associated with the time domain difference or the TA of a next reference point, e.g., R1.
In an example, the UE reports the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points to the BS by selecting RACH resource(s) for PRACH transmission.
In another example, a BS may indicate the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points by using a PRACH mask index in a UE specific DCI to determine RACH resource configuration. The PRACH mask index indicates a RACH resource, and the UE may know the time domain difference or the TA corresponding to the RACH resource according to the mapping relationship between the time domain difference or the TA associated with a specific reference point and the RACH resource.
The following describes an applicable case of PDCCH triggered PRACH transmission according to embodiments of the present application:
For the case of PDCCH triggered PRACH transmission, in another example, there is a default value for D_referencepoint, so the D_referencepoint in the formula can be deleted. For example, the default value may be 0 or maximum (max) RTD difference in the cell or beam coverage area.
In another embodiment of the present application, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point of the multiple reference points may be indicated by using TA command in random access response (RAR) or MAC CE signaling by a BS. That is, “TA command” is used in RAR or MAC CE signaling in the embodiment of the present application.
In particular, some of most significant bit (MSB) or least significant bit (LSB) of TA command is used to indicate the TA (or the time domain difference) associated with a specific reference point of the multiple reference points, and the remaining LSBs or MSBs are used to indicate the actual UE-specific TA value (that is, TA_UE as discussed above) or the actual UE-specific time domain difference. The mapping relationship between the remaining LSBs and the actual UE-specific TA value or the actual UE-specific time domain difference can be further updated or scaled.
Currently, for TA command in RAR, the possible index are T_A=0, 1, 2, . . . 3846, and for TA command in MAC CE, the possible index are T_A=0, 1, 2, . . . 63.
For example, when 1 MSB of TA command in MAC CE is used to indicate the time domain difference or the TA associated with a specific reference point, and when T_A is from 32 to 63, the time domain difference or the TA is associated with a reference point, e.g., R1, and the actual T_A is 0 to 31 respectively. When T_A is from 0 to 31, the time domain difference or the TA is associated with a reference point, e.g., R0, and the actual T_A is 0 to 31 respectively. When the mapping between remaining LSBs and T_A value is further updated, then the mapping may be updated to N_TA_new=N_TA_old+(TA−31)*16*64/2{circumflex over ( )}u*4.
In another example, when 1 LSB of TA command in MAC CE is used to indicate the time domain difference or the TA associated with a specific reference point, and when T_A is 0, 2, 4, 6 . . . , the time domain difference or the TA is associated with a reference point, e.g., R0; otherwise, if the T_A is 1, 3, 5, 7, the time domain difference or the TA is associated with another reference point, e.g., R1.
Although the above examples or embodiments of the present application are described with respect to the time domain difference or the TA associated with a specific reference point of multiple reference points shared by multiple UEs, it should be understood that the above examples or embodiments are also applicable when there is only the time domain difference or the TA associated with one reference point shared by multiple UEs.
In an embodiment of the present application, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a specific reference point may be predefined or broadcasted in SIB.
There are some time durations predefined in the 3GPP specification which needs to be updated based on the RTD between UE and a satellite.
In an example, the predefined time domain difference (the scheduling delay or the feedback delay) or the TA associated with a reference point may be applied to the time domain difference between 2-step RACH RAR and PUCCH transmission, and the related description in the specification may be updated as follows:
In another example, the predefined time domain difference (the scheduling delay or the feedback delay) or the TA associated with a reference point may be applied to a time duration between RACH retransmissions, and the related description may be updated as follows:
In another example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a predefined reference point may be applied to a minimum time between Msg.B RAR and PUSCH transmission, and the related description may be updated as follows:
In another example, the predefined time domain difference (the scheduling delay or the feedback delay) or the TA associated with a reference point may be applied to a minimum time between Msg.4 RAR and PUCCH, and the related description may be updated as follows:
In another example, the time domain difference (the scheduling delay or the feedback delay) or the TA associated with a predefined reference point may be applied to a gap between non-zero power channel state information-reference signal (NZP CSI-RS) and sounding reference signal (SRS) for non-codebook based PUSCH transmission, and the related description may be updated as follows:
Some embodiments of the present application concern on how to indicate to a UE the UL to DL timing relationship (U to D delay) for transparent payload due to misalignment between DL Tx and UL Rx at a BS side. A reception on the DL channel is after a transmission on the UL channel at a UE side. According to some embodiments of the present application, the signaling indicates at least one value and is based on misalignment between transmission(s) in the DL channel and reception(s) in the UL channel at a base station side, and the reception on the DL channel is after the transmission on the UL channel at a user equipment side. The at least one value can be referred to as “misalignment value” hereafter.
The misalignment value between DL Tx and UL Rx at the BS side should be known to UE(s) for DL channel or reference signal (RS) reception or application. The misalignment value is adopted for RRC connected state with a valid TA. It is applied after the UL Tx timing is already advanced by the TA indication, and it is different from the absolute delay value adopted for RRC idle state (e.g. delay between PRACH and RAR).
In an embodiment, the misalignment value can be indicated by a single value. In another embodiment, the misalignment value can be indicated by an initial value and a rate, the rate is a change rate dependent on time of the initial value. In an example, the rate may correspond to the selection of a ground station and a moving velocity of a satellite. The misalignment value can be in unit of ms or in unit of slot or symbol. When it is in unit of slot or symbol, a reference subcarrier spacing (SCS) should be determined or indicated. For example, the SCS may be determined based on the same SCS as that to determine the symbol/slot duration for the corresponding 4/1 symbol for monitoring PDCCH.
The signaling for indicating the misalignment value can be in a cell specific way or UE specific way. The misalignment value can be broadcasted or indicated in SIB, or configured by RRC signaling or MAC CE signaling, or configured by group common DCI (for example, the misalignment value can be configured in a payload position in a group common DCI).
The signaling for indicating the misalignment value can be applied to some cases.
In an embodiment of the present application, the signaling for indicating the misalignment value can be applied to MAC CE activation delay. The delay indicates the delay between ACK/NACK (A/N) transmission and application of the MAC CE command at UE side. For example, the current value indicating the U to D delay is 3 ms. In this embodiment, the value indicating the U to D delay will be updated to 3 ms+D_mis, where D_mis is the misalignment value between DL Tx and UL Rx at gNB side, and the related description in the specification may be updated as follows:
In another embodiment of the present application, the signaling for indicating the misalignment value can be applied to time domain duration between beam failure recovery (BFR) PRACH transmission and PDCCH monitoring. In this embodiment, the related description in the specification may be updated as follows:
In yet another embodiment of the present application, the signaling for indicating the misalignment value can be applied to time domain duration between configured grant based PUSCH transmission and PDCCH monitoring. For example, the current value indicating the U to D delay is 1 symbol. In this embodiment, the value indicating the U to D delay may be updated to 1 symbol+D_mis or cg-minDFIDelay-r16+D_mis, where D_mis is the misalignment value between DL Tx and UL Rx at gNB side, and the related description in the specification may be updated as follows:
Therefore, the above described embodiments can at least solve the technical problem concerning on how to indicate to the UE the scheduling delay or the feedback delay and TA corresponding to multiple reference points and how to indicate to the UE a UL to DL timing relationship (U to D delay) for transparent payload due to misalignment between DL Tx and UL Rx at a BS side.
As shown in
In some embodiments of the present application, the non-transitory computer-readable medium 607 may have stored thereon computer-executable instructions to cause a processor to implement the method according to embodiments of the present application.
As shown in
In some embodiments of the present application, the non-transitory computer-readable medium 707 may have stored thereon computer-executable instructions to cause a processor to implement the method according to embodiments of the present application.
Persons skilled in the art should understand that as the technology develops and advances, the terminologies described in the present application may change, and should not affect or limit the principle and spirit of the present application.
Those having ordinary skill in the art would understand that the steps of a method described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.
In this document, the terms “includes,” “including,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “a,” “an,” or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term “another” is defined as at least a second or more. The terms “including,” “having,” and the like, as used herein, are defined as “including.”
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2020/110507 | 8/21/2020 | WO |