A method for indicating time domain parameters of data transmission, UE and base station

Abstract

The present invention discloses a method for indicating a time domain parameter of data transmission, and a UE and a base station, including: indicating whether the user terminal UE scheduling data includes a beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agreeing with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions; when it is determined that the GAP is included, the GAP is determined according to the UE switching capability parameter agreed in the interface protocol; and the scheduling data is transmitted on the beam after the GAP. By using the method provided by the present invention, in the high-frequency scheduling design, the impact on the protocol can be reduced, and the complexity of the UE and base station implementation can be reduced.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method for indicating a time domain parameter of data transmission, a UE and a base station. Background Art

[0002] With the development of wireless communications, people have higher and higher demands for mobile communications, especially in terms of communication bandwidth and communication rate, and expect to reach G-bit rates. In order to meet people's requirements for high communication rates, it is necessary to develop spectrum with larger bandwidth. In the current 5G NR technology, mobile phones and base stations are already supported to communicate on two FR (Frequency Range), where FR1 is 410MHz to 7.125GHz and FR2 is 24.25GHz to 52.6GHz.

[0003] The current 3GPP standard has begun to study mobile wireless communications in the frequency band of 52.6GHz0-71GHz. Although higher communication frequencies can bring greater bandwidth advantages, they also bring greater challenges to wireless communication design. The main reason is that higher frequencies have greater Doppler frequency deviations and greater phase noise. In order to solve the impact of Doppler and phase noise caused by high frequencies, higher SCS (Sub-Carrier Spacing) is used. In order to solve the problem of large attenuation of high-frequency transmission, beam transmission technology will be used.

[0004] When the base station selects a suitable beam for communication, beam switching may be involved. During the beam switching period, the transceiver can neither receive nor send signals, which is the phenomenon of beam switching interval. When the SCS is relatively small, beam switching can be performed during the CP period. When the SCS is relatively large, its CP length is less than the beam switching time, so it is necessary to reserve symbols for beam switching.

[0005] To solve this problem, the following solutions are currently used:

[0006] The above negotiation is implemented based on base station scheduling, that is, when the base station sends data scheduling, the starting position and number of scheduled data are determined according to whether beam switching is required.

[0007] Consider in advance the content of the data time domain indication, the different beam switching GAP (beam switching time interval) values ​​(such as some UEs support a switching GAP of 1 symbol, and some UEs support a switching GAP of 2 symbols) and the possible data time domain indication content corresponding to the switching position, encode these contents, and use the encoded bits for indication.

[0008] With this method, as the data time domain indication content increases, more scenarios need to be considered, which brings complexity to the protocol update and leads to poor protocol compatibility. Summary of the invention

[0009] The present invention provides a method for indicating a time domain parameter of data transmission, a UE and a base station, which solve the problem that when a higher CSC performs beam switching, the protocol negotiation beam switching position is complex and the compatibility with the existing protocol is poor.

[0010] In a first aspect, the present invention provides a method for indicating a time domain parameter of data transmission, which is applied to a base station, and the method includes:

[0011] Indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions;

[0012] When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0013] The scheduling data is transmitted on the beam after the GAP.

[0014] Optionally, if it is agreed with the UE that whether the scheduling data includes a GAP is determined by a scheduling condition, when any of the following scheduling conditions is met, it is determined that the scheduling data does not include a GAP:

[0015] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0016] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0017] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0018] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0019] Scheduling data is data configured by high-level signaling;

[0020] The scheduled data is data scheduled by a specific DCI format.

[0021] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0022] Optionally, determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes:

[0023] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0024] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0025] Optionally, the indicating information carried in the downlink control information DCI to indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP includes:

[0026] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0027] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0028] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0029] Optionally, the scheduling data includes any of the following data:

[0030] Physical downlink shared channel PDSCH data;

[0031] Channel state information measurement reference signal CSI-RS;

[0032] Physical uplink shared channel PUSCH data.

[0033] Optionally, transmitting scheduling data on a beam after the GAP includes:

[0034] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0035] Optionally, the introduction of resource overhead associated with beam switching include:

[0036] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0037] Optionally, the introduction of resource overhead associated with beam switching include:

[0038] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0039] In a second aspect, the present invention provides a method for indicating a time domain parameter of data transmission, which is applied to a user terminal UE, comprising:

[0040] Determine whether the scheduling data includes the beam switching time interval GAP through indication information carried in the received downlink control information DCI or through scheduling conditions;

[0041] When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0042] The scheduling data is transmitted on the beam after the GAP.

[0043] Optionally, if it is determined whether the scheduling data includes a GAP by a scheduling condition agreed with the base station, it is determined that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0044] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0045] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0046] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0047] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0048] Scheduling data is data configured by high-level signaling;

[0049] The scheduled data is data scheduled by a specific DCI format.

[0050] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0051] Optionally, determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes:

[0052] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0053] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0054] Optionally, determining whether the scheduling data includes a GAP by using indication information carried in the received downlink control information DCI includes:

[0055] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0056] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0057] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0058] Optionally, the scheduling data includes any of the following data:

[0059] Physical downlink shared channel PDSCH data;

[0060] Channel state information measurement reference signal CSI-RS;

[0061] Physical uplink shared channel PUSCH data.

[0062] Optionally, transmitting scheduling data after the GAP performs beam switching includes:

[0063] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0064] Optionally, the introduction of resource overhead associated with beam switching include:

[0065] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0066] Optionally, the introduction of resource overhead associated with beam switching include:

[0067] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0068] In a third aspect, the present invention provides a base station for data transmission time domain parameter indication, including a memory and a processor, wherein:

[0069] The memory is used to store computer programs;

[0070] The processor is used to read the program in the memory and execute the following steps:

[0071] Indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions;

[0072] When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0073] The scheduling data is transmitted on the beam after the GAP.

[0074] Optionally, if the processor agrees with the UE to determine whether the scheduling data includes a GAP through a scheduling condition, the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0075] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0076] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0077] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0078] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0079] Scheduling data is data configured by high-level signaling;

[0080] The scheduled data is data scheduled by a specific DCI format.

[0081] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0082] Optionally, the processor determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0083] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0084] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0085] Optionally, the processor indicates, through indication information carried in downlink control information DCI, whether scheduling data of a user terminal UE includes a beam switching time interval GAP, including:

[0086] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0087] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0088] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0089] Optionally, the scheduling data includes any of the following data:

[0090] Physical downlink shared channel PDSCH data;

[0091] Channel state information measurement reference signal CSI-RS;

[0092] Physical uplink shared channel PUSCH data.

[0093] Optionally, the processor transmitting scheduling data on a beam after the GAP includes:

[0094] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0095] Optionally, the processor introduces resource overhead associated with beam switching include:

[0096] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0097] Optionally, the processor introduces resource overhead associated with beam switching include:

[0098] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0099] In a fourth aspect, the present invention provides a user terminal UE for transmitting a time domain parameter indication of data, comprising a memory and a processor, wherein:

[0100] The memory is used to store computer programs;

[0101] The processor is used to read the program in the memory and execute the following steps:

[0102] Determine whether the scheduling data includes the beam switching time interval GAP through indication information carried in the received downlink control information DCI or through scheduling conditions;

[0103] When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0104] The scheduling data is transmitted on the beam after the GAP.

[0105] Optionally, the processor determines whether the scheduling data includes a GAP according to a scheduling condition agreed with the base station, and the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0106] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0107] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0108] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0109] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0110] Scheduling data is data configured by high-level signaling;

[0111] The scheduled data is data scheduled by a specific DCI format.

[0112] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0113] Optionally, the processor determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0114] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0115] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0116] Optionally, the processor determines, by indication information carried in received downlink control information DCI, whether the scheduling data includes a GAP, including:

[0117] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0118] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0119] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0120] Optionally, the scheduling data includes any of the following data:

[0121] Physical downlink shared channel PDSCH data;

[0122] Channel state information measurement reference signal CSI-RS;

[0123] Physical uplink shared channel PUSCH data.

[0124] Optionally, the processor transmitting scheduling data after the GAP performs beam switching includes:

[0125] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0126] Optionally, the processor introduces resource overhead associated with beam switching include:

[0127] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0128] Optionally, the processor introduces resource overhead associated with beam switching include:

[0129] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0130] In a fifth aspect, the present invention provides a base station for indicating a time domain parameter of data transmission, including:

[0131] an indication judgment unit, configured to indicate, through indication information carried in downlink control information DCI, whether the scheduling data of the user terminal UE includes the beam switching time interval GAP, or to determine, through scheduling conditions agreed with the UE, whether the scheduling data includes the GAP;

[0132] A GAP determining unit, configured to determine the GAP according to the UE handover capability parameter agreed upon in the interface protocol when determining that the GAP is included;

[0133] A data transmission unit is used to transmit scheduling data on the beam after the GAP.

[0134] Optionally, if the indication judgment unit agrees with the UE to judge whether the scheduling data includes GAPP by the scheduling condition, it is determined that the scheduling data does not include GAP when any of the following scheduling conditions is met:

[0135] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0136] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0137] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0138] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0139] Scheduling data is data configured by high-level signaling;

[0140] The scheduled data is data scheduled by a specific DCI format.

[0141] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0142] Optionally, the indication judgment unit determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0143] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0144] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0145] Optionally, the indication judgment unit indicates, through indication information carried in downlink control information DCI, whether the scheduling data of the user terminal UE includes the beam switching time interval GAP, including:

[0146] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0147] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0148] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0149] Optionally, the scheduling data includes any of the following data:

[0150] Physical downlink shared channel PDSCH data;

[0151] Channel state information measurement reference signal CSI-RS;

[0152] Physical uplink shared channel PUSCH data.

[0153] Optionally, the data transmission unit transmits the scheduling data on the beam after the GAP, including:

[0154] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0155] Optionally, the data transmission unit introduces resource overhead associated with beam switching include:

[0156] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0157] Optionally, the data transmission unit introduces resource overhead associated with beam switching include:

[0158] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0159] In a sixth aspect, the present invention provides a user terminal UE for data transmission time domain parameter indication, including:

[0160] A receiving judgment unit, configured to judge whether the scheduling data includes a beam switching time interval GAP through indication information carried in the received downlink control information DCI or through a scheduling condition;

[0161] A determining unit, configured to determine, when determining that a GAP is included, the GAP according to a UE handover capability parameter agreed upon in an interface protocol;

[0162] A transmission unit is used to transmit scheduling data on the beam after the GAP.

[0163] Optionally, if the receiving judgment unit judges whether the scheduling data includes a GAP according to the scheduling condition agreed with the base station, it is determined that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0164] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0165] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0166] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0167] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0168] Scheduling data is data configured by high-level signaling;

[0169] The scheduled data is data scheduled by a specific DCI format.

[0170] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0171] Optionally, the receiving judgment unit determines the GAP according to a UE switching capability parameter agreed upon in an interface protocol, including:

[0172] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0173] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0174] Optionally, the receiving judgment unit determines whether the scheduling data includes a GAP through indication information carried in the received downlink control information DCI, including:

[0175] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0176] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0177] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0178] Optionally, the scheduling data includes any of the following data:

[0179] Physical downlink shared channel PDSCH data;

[0180] Channel state information measurement reference signal CSI-RS;

[0181] Physical uplink shared channel PUSCH data.

[0182] Optionally, the transmission unit transmits the scheduling data after the GAP performs beam switching, including:

[0183] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0184] Optionally, the transmission unit introduces resource overhead associated with beam switching include:

[0185] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0186] Optionally, the transmission unit introduces resource overhead associated with beam switching Also used for:

[0187] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0188] In the seventh aspect, the present invention provides a computer program medium having a computer program stored thereon, which, when executed by a processor, implements the steps of indicating the time domain parameters of data transmission as provided in the first aspect above, or, when executed by a processor, implements the steps of indicating the time domain parameters of data transmission as provided in the second aspect above.

[0189] In an eighth aspect, the present invention provides a chip, which is coupled to a memory in a device so that the chip calls program instructions stored in the memory during operation to implement the above-mentioned various aspects of the embodiments of the present application and any possible method involved in each aspect.

[0190] In a ninth aspect, the present invention provides a computer program product. When the computer program product runs on an electronic device, the electronic device executes and implements the above-mentioned various aspects of the embodiments of the present application and any possible method involved in each aspect.

[0191] The present invention provides a method for indicating a time domain parameter of data transmission, a UE, and a base station, which have the following beneficial effects:

[0192] The method of DCI indication or scheduling condition judgment is used to determine whether the data scheduling includes the beam switching time interval GAP. When determining the GAP, the network equipment and UE determine the corresponding GAP based on the UE capability switching parameters, so that in the high-frequency scheduling design, the impact on the protocol is reduced and the complexity of UE and base station implementation is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0193] Figure 1 A schematic diagram of time domain information indication for scheduling PDSCH;

[0194] Figure 2 A schematic diagram comparing a scenario with a switching GAP and a scenario without a switching GAP;

[0195] Figure 3 It is a schematic diagram of the calculation steps of TB size in the prior art;

[0196] Figure 4 A schematic diagram showing the comparison of the data time domain indication contents required for switching GAP and those required for not switching GAP;

[0197] Figure 5 A system for indicating time domain parameters of data transmission provided by an embodiment of the invention;

[0198] Figure 6 A flowchart of implementation method 1 of data transmission time domain parameter indication;

[0199] Figure 7 Schematic diagram of beam switching symbols;

[0200] Figure 8 Schematic diagram of two scenarios where the beam switching GAP is not included in the scheduling data;

[0201] Fig. 9 This is a schematic diagram of a third scenario where the scheduling data does not include a beam switching GAP;

[0202] Fig.10 This is a schematic diagram of a fourth scenario in which the scheduling data does not include a beam switching GAP;

[0203] Fig.11 A flowchart of implementation method 3 of data transmission time domain parameter indication;

[0204] Fig.12 Schematic diagram of beam switching symbols;

[0205] Fig.13 A flow chart of a method for indicating time domain parameters of data transmission at a base station side provided in an embodiment of the present invention;

[0206] Fig.14 A flow chart of a method for indicating time domain parameters of data transmission at a user terminal UE side provided in an embodiment of the present invention;

[0207] Fig.15 A schematic diagram of a base station for indicating a time domain parameter for data transmission provided by an embodiment of the present invention;

[0208] Fig.16 A schematic diagram of a base station user terminal UE indicating a time domain parameter for data transmission provided by an embodiment of the present invention;

[0209] Fig.17 A schematic diagram of a base station for indicating a time domain parameter for data transmission provided by an embodiment of the present invention;

[0210] Fig.18 A schematic diagram of a base station user terminal UE indicating a time domain parameter for data transmission provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0211] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0212] In order to solve the influence of Doppler and phase noise caused by high frequency, a higher SCS (Sub-Carrier Spacing) is used. As the SCS increases, the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols decreases, and its CP length also decreases. The relationship between CP length and SCS is shown in Table 1:

[0213] Table 1: Relationship between CP length and SCS

[0214] u SCS(Hz) CP length (us) CP (length ns) 3 120K 0.59 586 4 240K 0.29 293 5 480K 0.15 146 6 960K 0.07 73

[0215] During the communication process, when the beam needs to be switched, the transceiver can neither send nor receive. This switching time is called the switching interval (beam switching GAP). The size of the beam switching GAP (call GAPping) depends on the device's capabilities, but the switching GAP of most devices is generally between 150 nanoseconds and 200 nanoseconds. That is to say, when the SCS reaches 480KHz or 960KHz, the GAP needs to be switched.

[0216] The base station and UE need to reach a consensus to determine whether beam switching is required and the time point for beam switching during a certain data / signal transmission, such as PDSCH (Physical Downlink Shared Channel) transmission.

[0217] At the same time, in actual data communication, the transmission of a certain data, such as PDSCH, may not require beam switching. For example, before the PDSCH data is sent / received:

[0218] Transmitter: When sending other data or signals, the beam direction has been adjusted and does not need to be adjusted again;

[0219] Receiver: When receiving other data or signals, its beam direction has been adjusted and does not need to be adjusted again.

[0220] One solution of the current existing technical solutions is to implement the time domain parameter indication of data transmission based on base station scheduling, that is, when the base station sends data scheduling, the starting position and length of the scheduling data are determined according to whether beam switching is required.

[0221] The existing solution for beam switching is described below in conjunction with scheduling PDSCH.

[0222] like Figure 1The figure shows a schematic diagram of the time domain information indication information for scheduling PDSCH. The DCI (Downlink Control Information) information carried on the PDCCH (Physical Downlink Control Channel) includes the time domain information indication of PDSCH. The time domain information for indicating PDSCH mainly includes 3 information contents:

[0223] (1) A time slot offset k0 relative to the time slot where the PDCCH is located. When k0=0, it indicates that the PDCCH is in the same time slot.

[0224] (2) The starting symbol (S) of PDSCH, the number of symbols from the time slot boundary.

[0225] (3) The length of PDSCH (L), which is the number of symbols used to schedule PDSCH.

[0226] To reduce the scheduling overhead in the time domain, the scheduling information in the time domain is usually configured in a table (PDSCH time domain allocation table, pdsch-TimeDomainAllocationList), each table includes: k0, S and L information. In order to ensure the flexibility of base station scheduling and reduce the overhead of DCI indication, the current standard determines that the indication of time domain information uses 4 bits, with a total of 16 possibilities. When the base station sends scheduling signaling, it indicates which item in the table to use.

[0227] For example, the information in the scheduling time domain has the following 3 optional items:

[0228] k0=0, S=7, L=7;

[0229] k0=1, S=0, L=7;

[0230] k0=1, S=7, L=7.

[0231] When the scheduling time domain indication is "00", it means k0 = 0, S = 7, L = 7. The meaning is: in the current time slot scheduling, the starting symbol of the scheduled PDSCH is 7, and the number of symbols is 7.

[0232] like Figure 2 As shown, it is a schematic diagram comparing the scenarios with switching GAP and without switching GAP, where from top to bottom are Case 1 and Case 2 respectively.

[0233] The base station sends scheduling signaling at symbol 0 of a certain time slot, the beam direction for scheduling PDSCH is beam1, and the candidate symbols for PDSCH scheduling are symbol 7 to symbol 13, a total of 7 symbols; at the same time, before data symbol 7 (excluding 7), other data or signals have been scheduled for transmission.

[0234] The following describes the actual scheduling of beam1 data in two cases:

[0235] (1) Case 1: No beam switching is required: Before symbol 7, the base station's transmit beam is already in the direction of beam1. Therefore, when the base station continues to transmit on beam1, no additional beam switching is required. At this time, the starting position of the PDSCH scheduling data is 7, and the number is 7.

[0236] (2) Case 2: beam switching is required: the data / signal transmitted before symbol 7 uses beam2. That is, if the base station wants to schedule data on beam1, a beam switching interval is required (switching from beam2 to beam1). The base station performs beam switching on symbol 7. At this time, the starting position of the PDSCH scheduled data is 8 and the number is 6.

[0237] The calculation of TB size (transport block size) in the prior art is described below:

[0238] In the transmission of calculation data, the TB size parameter is not indicated by explicit signaling, but is calculated from other parameters. The main parameters are: the number of resource RBs (Resource Blocks), data time domain information (number of symbols), adjustment of coding format, bit rate, number of layers, and constants configured by high-level layers. The calculation process is as follows: Figure 3 As shown, the following steps are included:

[0239] Step S301: The UE first calculates the number of REs (Resource Element) allocated in a PRB (physical resource block);

[0240] One PRB contains 12 frequency domain units;

[0241] in

[0242] It is the number of time domain symbols of PDSCH, which is indicated by the time domain parameter of scheduling signaling;

[0243] It is the header overhead of DMRS (Demodulation Reference Symbol), which is configured or dynamically indicated by the base station;

[0244] It is other overhead, which is configured by the base station to the UE. This parameter is semi-statically configured.

[0245] Step S302: The UE calculates the total number of REs allocated to the PDSCH;

[0246] N RE =min(156,N' RE )·n PRB , where n PRB It is the number of PRBs allocated to PDSCH, and is indicated by the frequency domain parameters of the scheduling signaling;

[0247] Step 303: According to N RE , code rate, modulation order, and number of layers to calculate TB size. The detailed process refers to the 5G standard and will not be repeated here.

[0248] The above solution to solve the beam switching problem has the following problems:

[0249] When designing the PDSCH / PUSCH (Physical Uplink Shared Channel) time domain scheduling parameters, it is necessary to consider the factors of base station / UE switching beamGAP, which increases the complexity of designing time domain scheduling parameters and the complexity involved in other protocols. For example:

[0250] (1) The existing protocol table content based on the default PDSCH / PUSCH needs to be redesigned.

[0251] (2) It is necessary to add more configuration items based on the time domain scheduling parameter table configured by the UE.

[0252] To further illustrate the problem, assume that only two PDSCH scheduling starting positions and numbers are configured as an example:

[0253] The diagram of the comparison of the data time domain indication content required for the scenario with switching GAP and without switching GAP (only one switching length) is as follows Figure 4 As shown, from top to bottom, they are respectively when there is no beam switching GAP, when there is 1 beam switching GAP, when there are 2 beam switching GAPs, and when there are 2 beam switching GAPs.

[0254] When there is no beam switching, two data time domain indication contents are required. When considering beam switching GAP, the number needs to be increased to 6.

[0255] When different UEs support different beam switching GAP values, such as some UEs support a switching GAP of 1 symbol and some UEs support a switching GAP of 2 symbols, more scenarios need to be considered, which will increase the complexity of protocol updates and lead to poor protocol compatibility.

[0256] In response to the above problems, the embodiments of the present application provide a method for indicating time domain parameters of data transmission, a UE, and a base station, which adopts a method of displaying DCI or implicitly indicating through a judgment rule to determine whether the data scheduling includes a beam switching GAP, and corrects the calculation method of the TB size, so as to achieve the purpose of reducing the impact on the protocol and reducing the complexity of UE and base station implementation in high-frequency scheduling design.

[0257] The method, the base station and the UE are based on the same application concept. Since the method, the base station and the UE solve problems based on similar principles, the implementation of the base station, the UE and the method can refer to each other, and the repeated parts will not be repeated.

[0258] Example 1

[0259] like Figure 5 As shown, an embodiment of the present invention provides a system for indicating a time domain parameter of data transmission, including:

[0260] The base station 500 is used to indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or to agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions; when it is determined that the GAP is included, the GAP is determined according to the UE switching capability parameters agreed upon in the interface protocol; and the scheduling data is transmitted on the beam after the GAP.

[0261] The user terminal UE510 is used to determine whether the scheduling data contains a beam switching time interval GAP through the indication information carried in the received downlink control information DCI, or through the scheduling conditions agreed with the base station; when it is determined that the GAP is included, the GAP is determined according to the UE switching capability parameters agreed in the interface protocol; and the scheduling data is transmitted on the beam after the GAP.

[0262] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, applicable systems may be global system of mobile communication (Global System of Mobilecommunication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) general packet radio service (General Packet Radio Service, GPRS) system, long term evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (Frequency Division Duplex, FDD) system, LTE time division duplex (Time Division Duplex, TDD), Universal Mobile Telecomm Unication System (UMTS), Worldwide interoperability for Microwave Access (WiMAX) system, 5G system and 5GNR system, etc. These various systems include UE equipment and network equipment.

[0263] The user terminal UE involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0264] The base station involved in the embodiment of the present application may include multiple cells. Depending on the specific application scenario, the base station may also be called an access point, or may refer to a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or other names. The network device may be used to convert received air frames to and from Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application can be a network device (Base Transceiver Station, BTS) in the Global System For Mobile communications (Global System For Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolved network device (evolutional NodeB, eNB or e-NodeB) in the Long Term Evolution (Long Term Evolution, LTE) system, a 5G base station in the 5G network architecture (Next generation System), or a home evolved node B (Home evolved node B, HeNB), a relay node (Relay Node), a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application.

[0265] In this embodiment, the transmission of scheduling data on the beam after the GAP specifically refers to the transmission of a valid scheduling data signal. The above-mentioned valid scheduling data signal is explained as follows: Under normal circumstances, the base station and the terminal need to perform a beam switching process at a determined beam switching position, which results in a data sending / receiving terminal during the beam switching process. Due to different hardware capabilities, in the actual implementation process, a node in the base station and the terminal may complete the beam switching process in advance, but still consider the received or sent signal to be invalid or bad, that is, it cannot be considered a valid signal or channel. The above-mentioned valid scheduling data signal is a signal that meets the requirements of the standard. In the beam switching time interval GAP, the base station does not send any signal, or the sent signal is invalid, that is, it cannot be used as a valid received signal for data demodulation.

[0266] In an embodiment of the present invention, the base station determines whether the scheduling data includes a GAP and notifies the UE through DCI, or agrees with the UE to determine whether the scheduling data includes a GAP through scheduling conditions. Possible implementation methods of the two methods are described below.

[0267] 1. Determine whether the scheduling data contains GAP based on the agreed scheduling conditions;

[0268] When this method is used, the base station and the UE use the agreed scheduling conditions to determine whether the scheduling data contains a GAP, and the base station does not need to indicate it using signaling.

[0269] Specifically, when any of the following scheduling conditions is met, it is determined that the scheduling data does not include a GAP:

[0270] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0271] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0272] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0273] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0274] Scheduling data is data configured by high-level signaling;

[0275] The scheduled data is data scheduled by a specific DCI format, such as the DCI format based on format 0 in the existing NR.

[0276] If the above conditions are not met, it is considered that the scheduling data may contain a GAP. When it is determined that the GAP is contained, the GAP is determined according to the UE handover capability parameter agreed upon in the interface protocol.

[0277] 2. Indicate whether the UE scheduling data contains GAP through the indication information carried in the downlink control DCI;

[0278] A bit of information is added to the DCI of the PDCCH channel to indicate whether the time domain information of the scheduling data contains a beam switching symbol.

[0279] The indication information carried in the DCI is used to indicate to the user terminal UE, and any of the following methods can be used:

[0280] Different values ​​of a bit are used to indicate whether the scheduling data contains GAP, such as 0 indicates that the beam switching time is included, 1 indicates that the beam switching time is not included, or vice versa.

[0281] Different values ​​of two bits are used to indicate whether the scheduling data contains GAP and the corresponding switching position when GAP is contained. The specific method can be as follows:

[0282] When 00 is used to indicate that the number of symbols occupied by the GAP is two, the switching positions of the GAP are located at the first symbol and the last symbol of the scheduling data time domain respectively;

[0283] When 01 is used to indicate that the number of symbols occupied by the GAP is 1, the switching position of the GAP is located at the first symbol in the time domain of the scheduled data symbol;

[0284] When 10 is used to indicate that the number of symbols occupied by the GAP is 1, the switching position of the GAP is located at the last symbol of the scheduling data time domain;

[0285] Use 11 to indicate that no beam switching is performed.

[0286] When the UE and the base station determine that the scheduling data includes the GAP in the above manner, the GAP information may be determined according to the UE switching capability parameter. The GAP information here includes the number of GAP symbols and the switching position of the GAP.

[0287] The base station and the UE may determine the GAP corresponding to different UE switching capability parameters through the interface protocol. As an optional implementation, the GAP here may only include the number of symbols of the GAP, that is, the number of symbols of the GAP is determined through the UE switching capability parameter, and the switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol. The number of time units may be the number of symbols or the number of sampling points.

[0288] As another optional implementation, when the interface protocol determines the GAPs corresponding to different UE switching capability parameters, the GAPs may also include the number of GAP symbols and the switching position.

[0289] The UE switching capability parameter includes a UE switching capability device level related to the UE itself, and also includes at least one UE switching capability transmission parameter of subcarrier spacing, DCI format of scheduling data, and transmission direction of scheduling data.

[0290] For example, for a specific subcarrier, one or more GAP switching durations are determined as follows:

[0291] GAP duration based on UE switching capability device level 1: when SCS=480KHz, GAP=1 symbol; when SCS=960KHz, GAP=2 symbols.

[0292] GAP duration based on UE switching capability device level 2: when 480KHz, GAP = 0 symbol, when SCS = 960KHz, GAP = 1 symbol.

[0293] Normally, before the initial access is completed, the base station does not know the UE's UE switching capability equipment level. At the same time, different UEs in a cell may have different UE switching capability equipment levels. Therefore, it is necessary to distinguish the application scenarios of different UE switching capability equipment levels. Specifically:

[0294] For the initial access process, or for receiving paging information and system broadcast information, the beam switching GAP capability is the basic capability (such as capability 1, when SCS = 960KHz, a switching interval of 2 symbols is required). For the base station, when it is determined that the UE is not in a connected state, the lowest UE switching capability device level and the UE switching capability related data parameters are used to determine the GAP included in the scheduling data; for the UE, when it is determined that the UE is not in a connected state, the lowest UE switching capability device level and the UE switching capability related data parameters are used to determine the GAP included in the scheduling data.

[0295] When the UE enters the connected state, the UE reports the beam switching GAP capability, and the base station reconfirms the beam switching capability value (e.g., in the connected state, based on the UE's data scheduling, the capability is 2, and when SCS = 960KHz, a switching interval of 1 symbol is required). For the base station, when it is determined that the UE enters the connected state, the UE switching capability device level reported by the UE is received, and the GAP is determined based on the reported UE switching capability device level and the UE switching capability transmission parameter. For the UE, when it is determined that the UE enters the connected state, the GAP is determined based on the UE switching capability device level and the UE switching capability transmission parameter.

[0296] As an optional implementation manner, in an embodiment of the present invention, the base station and the UE transmit valid scheduling data on the beam after the GAP, including: when transmitting valid scheduling data on the beam after the GAP, introducing resource overhead related to beam switching Used to calculate the length TBsize of the scheduled data transmission block.

[0297] The resource overhead introduced by beam switching can be determined according to the number of symbols of the GAP and the number of symbols of valid scheduling data. The more symbols of effective scheduling data there are, The smaller the value, the smaller the value. The specific methods are as follows:

[0298] Determine whether the number of symbols of valid scheduling data is less than a preset low threshold or greater than a preset high threshold, and determine is 0, the preset high threshold is greater than the preset low threshold;

[0299] Otherwise, the larger the number of symbols of effective scheduling data, The smaller the rule, the smaller the number of symbols in the GAP and the number of symbols in the valid scheduling data.

[0300] Using the The number of resource elements RE allocated in a physical resource block PRB is corrected, and the transmission data block size TBsize is calculated using the corrected number of REs and related parameters.

[0301] UE and base station introduce variables Finally, the process of calculating the transmission data block size TBsize is as follows:

[0302] Calculate the number of REs allocated in a PRB N' RE , the process is as follows:

[0303] First calculate the number of REs allocated in a PRB, N' RE :

[0304] in:

[0305] is the number of time domain symbols of PDSCH (indicated by the time domain parameter of scheduling signaling);

[0306] It is the header overhead of DMRS (configured by the base station or dynamically indicated);

[0307] It is other overhead, which is configured by the base station to the UE. This parameter is semi-statically configured;

[0308] Due to the overhead introduced by beam switching.

[0309] variable The calculation is related to beamGaP and the number of symbols of the scheduled data L. An example of the relationship is shown in Table 2:

[0310] Table 2: beamGaP parameter table ( Value)

[0311]

[0312] When L = 2, It is 0, indicating that no switching occurs within the schedule when L=2. The main consideration is that the number of data symbols is relatively small.

[0313] When L = 2 / 3 / 4 / 5 / 6, different The larger the L, The smaller.

[0314] When L is greater than or equal to 7, 0, indicating The impact on the calculated TB size is negligible.

[0315] The embodiments of the present invention provide some examples. Of course, other data may also be configured as long as they are reflected. The value of is related to L or beamGap. That is, when L is less than a certain threshold or greater than a certain threshold, Other values ​​are related to the number of Ls. The threshold of the number of Ls can be configured as a default value or through high-level configuration.

[0316] The above scheduling data includes any of the following data: physical downlink shared channel PDSCH data; channel state information measurement reference signal CSI-RS; physical uplink shared channel PUSCH data. The following is a possible implementation method in combination with the specific form of the scheduling data.

[0317] Implementation Method 1

[0318] In this implementation, DCI=1 bit, the scheduling data is PDSCH, the number of scheduling data symbols L=6, GAP=1OS, SCS=960KHz, where OS is an OFDM symbol.

[0319] like Figure 6 As shown, the data transmission time domain parameter indication process is as follows:

[0320] Step S601: confirm the GAP duration beamGap of beam switching, in units of the number of symbols.

[0321] As the SCS increases, the number of symbols and the CP length decrease. Therefore, for a specific beam switching duration, the number of GAP symbols required is different. At the same time, different UE / base station capabilities have different beamGap values. To facilitate base station and UE operations, this embodiment determines the beam switching capability table through the protocol, corresponding to different SCS and UE switching capability equipment levels, as shown in Table 3.

[0322] For the convenience of description, in this embodiment, the UE switching capability device level is referred to as capability for short.

[0323] Table 3: Beam switching GAP parameters for different SCS / different capabilities (unit symbol)

[0324]

[0325] The above table content defines the number of symbols corresponding to different UE switching capability parameters under different SCS. Of course, the above number of symbols is only a reference example, and its value can be other integers or decimals, or replaced by time units; in order to simplify the operation of UE and base station, it can also be simplified into a capability type and a value. For example, for all SCS greater than 480KHz, the switching value is 1 symbol.

[0326] Step S602: Determine the corresponding beam switching GAP capability when scheduling different data.

[0327] The process of confirming the beam switching GAP duration beamGap value can adopt the default method, such as: the default UE and base station are based on capability 1. Alternatively, after the UE enters the connected state, it can report the capability to the base station, and the base station replies to confirm the capability to be used. The capability confirmed by the base station is not higher than the capability reported by the UE. For example, if the UE reports capability 2 to the base station, the capability confirmed by the base station can be 1 or 2, but not 3.

[0328] Although the base station obtains the UE's capabilities through reporting, a default capability needs to be defined before the UE reports the capabilities. At the same time, different UEs in a cell may have different capabilities. Therefore, it is necessary to distinguish the application scenarios of different switching capabilities. Specifically:

[0329] For the initial access process, or for receiving paging information (such as data scheduled by PDCCH encrypted with P-RNT) and system broadcast information (such as data scheduled by PDCCH encrypted with SI-RNT), the beam switching GAP capability is the minimum capability (such as capability 1, when SCS = 1900KHz, a switching interval of 2 symbols is required).

[0330] When the UE enters the connected state, the UE reports the beam switching GAP capability, and reconfirms the beam switching capability value with the base station (for example, in the connected state, based on the UE's data scheduling, the UE's capability is 2, and when SCS = 960KHz, a switching interval of 1 symbol is required).

[0331] Step S603: when scheduling data, the base station indicates whether the scheduling data includes a GAP through a bit in the DCI.

[0332] Add 1 bit of information in the DCI to indicate whether the scheduling data contains GAP:

[0333] Beam_switch_ind: 1 bit, indicating whether the scheduling data contains a beam switching GAP; for example, 0 indicates that the scheduling data contains a GAP, and 1 indicates that the scheduling data does not contain a GAP, or vice versa.

[0334] As described in step S602, in data scheduled in different DCI formats, if the scheduling data indicates that the scheduling data includes a GAP, the number of GAP symbols may also be different.

[0335] For example, when PDSCH scheduling is performed using C-RNTI scheduling, if Beam_switch_ind is 0, it indicates that the beam switching symbol is 1; when PDSCH scheduling is performed using SI-RNTI, if Beam_switch_ind is 0, it indicates that the beam switching symbol is 2.

[0336] The schematic diagram of beam switching symbols is as follows Figure 7 As shown, from top to bottom they are Case 1 and Case 2:

[0337] Case 1: The UE and the base station negotiate that the number of symbols of the beam switching GAP is 1. For the PDSCH scheduled by the C-RNTI scrambled PDCCH, the DCI content is: S=7, L=7, and Beam_switch_ind is 0 (indicating that the scheduled data length includes the beam switching GAP). In this case, at symbol 7, the data sent is considered invalid, and the valid data is from symbol 8 to symbol 13, or the real start of the data starts from symbol 8 and ends at symbol 13.

[0338] Case 2: By default, the UE and the base station set the number of beam switching GAP symbols to 2. The DCI content of the PDSCH scheduled by the SI-RNTI scrambled PDCCH is: S=7, L=7, and Beam_switch_ind is 0 (indicating that the scheduled data length includes the beam switching GAP). In this case, the data sent on symbols 7 and 8 are considered invalid, and the valid data is from symbol 9 to symbol 13. In other words, the real start of the data starts from symbol 9 and ends at symbol 13.

[0339] Step S604: The UE receives data according to the DCI instruction. The specific process is as follows:

[0340] (1) Perform beam switching according to beam switching information:

[0341] The UE determines the beam switching position according to the Beam_switch_ind indication, including the following two cases:

[0342] When Beam_switch_ind=1, it means that the time domain parameters of the scheduling data do not contain the symbol of beam switching, that is, the UE needs to complete the beam switching before the starting symbol of the scheduling time domain.

[0343] When Beam_switch_ind=0, it means that the time domain parameters of the scheduling data include the symbol of beam switching, that is, the UE only needs to complete the switching in the starting symbol of the scheduling time domain.

[0344] (2) Calculate the TB size based on the beam switching information and the time domain scheduling length.

[0345] This example introduces a variable Calculate the number of REs allocated in a PRB N' RE , the process is as follows:

[0346] Step 1: The UE first calculates the number of REs allocated in a PRB (physical resource block, containing 12 frequency domain units) N' RE .

[0347] in:

[0348] The number of time domain symbols of PDSCH (indicated by the time domain parameters of scheduling signaling);

[0349] It is the header overhead of DMRS (configured by the base station or dynamically indicated);

[0350] It is other overhead, which is configured by the base station to the UE. This parameter is semi-statically configured;

[0351] Due to the overhead introduced by beam switching.

[0352] variable The calculation is related to beamGaP and the duration of the scheduled data. An example of the relationship is shown in Table 2:

[0353] As shown in Table 2, when L = 2, It is 0, indicating that when L=2, no switching occurs within the schedule, and the main consideration is that the number of data symbols is relatively small.

[0354] When L=2 / 3 / 4 / 5 / 6, different The larger the L, The smaller.

[0355] When L is greater than or equal to 7, 0, indicating The impact on the calculated TB size is negligible.

[0356] This implementation method provides some examples. Of course, it can also be configured as other data as long as it reflects The value of is related to L, or to beamGap.

[0357] Assuming that in the scheduling information: L = 6, that is Assume beamGAP = 1 symbol. Then we can get To calculate TB size, Substituting into the above formula, whether Beam_switch_ind=0 or 1.

[0358] Implementation Method 2

[0359] In this implementation manner, DCI=0 bit, the scheduled data is PDSCH / CSI-RS or PUSCH, the number of symbols of the scheduled data is L=7, and GAP=1OS.

[0360] Steps 1, 2, and 4 of this embodiment are the same as those of embodiment 1. Here, the focus is on how to determine whether the number of symbols indicated by the data includes the symbol of the beam switching GAP when Beam_switch_ind is 0 bits, or when the scheduling signaling does not include the Beam_switch_ind indication.

[0361] When any of the following scheduling conditions is met, the base station and the UE consider that the scheduling data does not contain a GAP:

[0362] The schematic diagrams of two scenarios where the scheduling data does not include beam switching GAP are as follows: Figure 8 ,in Figure 8 From top to bottom are dispatching condition 1 and dispatching condition 2:

[0363] (1) Scheduling condition 1, d <= threshold_GAP: When the distance between the start symbol of the DCI scheduling indication downlink data or signal and the last symbol of the PDCCH of the DCI is less than a threshold. As shown in Figure 8, d <= threshold_GAP, threshold_GAP is an integer symbol, and the number of symbols is related to the SCS. In the specific implementation process, the threshold can be defined as the minimum delay from the UE receiving the DCI to the beam switching.

[0364] The DCI here is scheduling signaling, and the scheduling object can be PDSCH channel data or reference signal.

[0365] (2) Scheduling condition 2, L <= threshold_L: When the number of scheduled PDSCH / PUSCH data is less than a certain threshold. Figure 8 In the example, L<=threshold_L, and a typical value of L is 2, 3 or 4.

[0366] (3) Scheduling condition 3, such as Fig. 9 As shown, when the starting position of the scheduling data is in the SS / PBCH signal, the scheduling data does not include the beam switching GAP.

[0367] SS / PBCH is a synchronization signal block, a physical layer broadcast message of the synchronization signal sent by the base station. During the 4 symbols of SS / PBCH, the base station will not adjust the beam direction. Therefore, when the starting position of the scheduled data is at the SS / PBCH symbol position, it can be considered that it does not include the beam switching GAP. Fig. 9 In the example, the symbol positions occupied by SS / PBCH are #8, #9, #10, and #11. When the PDSCH start symbol is on any symbol among #8, #9, #10, and #11, it can be considered that the beam switching GAP is not included.

[0368] (4) Scheduling condition 4: Fig.10 As shown, when the starting position of the scheduled data is at the first symbol after "up / downlink conversion" (including from uplink to downlink, or from downlink to uplink, where Fig.10 From top to bottom, the starting symbol of the scheduled PDSCH is on the first downlink symbol, and the starting symbol of the scheduled PDSCH is on the first uplink symbol), such as Fig.10 As shown in the figure, when the scheduled data is in the first symbol after the uplink / downlink switching, it is considered that the beam switching GAP is not included. When the base station or UE performs uplink / downlink switching, the beam switching can be performed at the same time. For example, when scheduling PUSCH data, symbol #6 is the starting symbol, and the symbol before symbol 6 is the uplink / downlink switching time. Then the UE performs beam switching while performing uplink / downlink switching.

[0369] (5) When the scheduling information is configured by high-level signaling, such as SPS (Semi-Persistent Scheduling) of PDSCH and CG (configured grant) of PUSCH.

[0370] When PDSCH / PUSCH is configured for scheduling, each time PDSCH / PUSCH data is sent, its time domain information is agreed upon through high-level signaling (or through one DCI scheduling, multiple data schedulings are performed). In this case, it can be considered that the data time domain information does not include the beam switching GAP.

[0371] Supplementary explanation: To simplify the protocol, the base station and the UE may also agree that when the DCI does not include the Beam_switch_ind indication information (or when the data scheduling signaling is configured by the higher layer), the scheduling time domain information may be assumed to include no beam switching GAP; and the scheduling information may be assumed to include the beam switching GAP; or it may be determined through the higher layer signaling configuration that when the DCI does not include the Beam_switch_ind indication information, whether the scheduling time domain information includes the beam switching GAP by default.

[0372] Implementation 3

[0373] In this implementation, DCI=2 bits, the scheduled data is PUSCH data, the number of symbols of the scheduled data is L=7, and GAP=1OS.

[0374] A flowchart of implementation method 3 of data transmission time domain parameter indication, as shown in Fig.11 As shown:

[0375] Step S1101: confirming the GAP duration beamGap of uplink beam switching, in units of the number of symbols.

[0376] As the SCS increases, the number of symbols and CP length of the uplink channel decrease. Therefore, in the duration of a specific beam switch, different SCSs require different numbers of beam switch GAP symbols. At the same time, different UE / base station capabilities have different beam switch GAPs. To facilitate base station and UE operations, a better method is to determine the uplink beam switching capability table by protocol. Corresponding to different SCSs and capabilities, the relevant values ​​can be the same as the downlink or different. Examples of different values ​​are as follows:

[0377] For the convenience of description, in this embodiment, the UE switching capability device level is referred to as capability for short.

[0378] Table 4: Uplink beam switching GAP parameters for different SCS / different capabilities (unit symbol)

[0379]

[0380]

[0381] The above table content defines the number of symbols corresponding to different capability types under different SCS. Of course, the above number of symbols is only a reference example, and its value can be replaced by other integers or decimals, or time units. In order to simplify the operation of UE and base station, it can also be simplified into a capability type and a value. For example, for all SCS greater than 480KHz, the switching value is 1 symbol.

[0382] Step S1102: Determine the corresponding beam switching GAP capability when scheduling different uplink data.

[0383] The process of confirming the beam switching GAP duration beamGap can adopt the default method, such as: the default UE and base station are based on capability 1. Alternatively, after the UE enters the connected state, the capability is reported to the base station, and the base station replies to confirm the capability to be used. The capability confirmed by the base station is not higher than the capability reported by the UE. If the UE reports capability 2 to the base station, the base station replies to confirm that the capability can be 1 or 2.

[0384] Although the base station obtains the UE's capabilities through reporting, a default capability needs to be defined before the UE reports the capabilities. At the same time, different UEs in a cell may have different capabilities. Therefore, it is necessary to distinguish the application scenarios of different switching capabilities. Specifically:

[0385] During the initial access process, when sending a random access signal or sending other messages (such as Msg3, the third step message of the random access process), the GAP capability is switched according to the minimum beam.

[0386] When the UE enters the connected state, the UE reports the beam switching GAP capability and reconfirms the beam switching capability value with the base station (for example, in the connected state, based on the UE's data scheduling, the capability is 2, and when SCS=960KHz, a switching interval of 0 symbols is required).

[0387] Step S1103: When scheduling data, the base station indicates whether the scheduling data includes a GAP and a beam switching position through two bits carried in the DCI.

[0388] In this embodiment, 2 bits of information are added to the DCI to indicate the beam switching information included in the time domain information of the scheduling data, and the corresponding beam switching position when the GAP is included;

[0389] Beam_switch_ind: 2 bits, indicating whether the scheduling data contains a beam switching GAP and the location of the beam switching GAP, such as:

[0390] 00: indicates that two beam switching GAPs are included (distributed in the first symbol and the last symbol in the scheduling data time domain).

[0391] 01: Indicates that 1 beam switching GAP is included, in the first symbol of the scheduled data symbol.

[0392] 10: Indicates that 1 beam switching GAP is included, which is the last symbol of the scheduled data symbol.

[0393] 11: Indicates whether any beam switching GAP is included.

[0394] The schematic diagram of beam switching symbols is as follows Fig.12 As shown, from top to bottom, Beam_switch_ind is 00 and Beam_switch_ind is 10: When using C-RNTI-scheduled PDSCH scheduling, if Beam_switch_ind is 00, it means that there are two beam switching GAPs in the scheduling with a length of 7 symbols, which are located at the starting symbol 7 and symbol 13 respectively. When using C-RNTI-scheduled PDSCH scheduling, if Beam_switch_ind is 10, it means that there is one beam switching GAP in the scheduling with a length of 7 symbols, which is located at the starting symbol 13.

[0395] Step S1104: The UE receives data according to the DCI instruction.

[0396] (1) Perform beam switching according to beam switching information:

[0397] The UE determines whether it needs to complete beam switching before the start symbol of PDSCH according to the Beam_switch_ind indication. When Beam_switch_ind = 11, the beam switching needs to be completed before the start of PDSCH, and when Beam_switch_ind = 01, the beam switching needs to be completed before the "end of the last beam switching GAP symbol".

[0398] (2) Calculate the TB size based on the beam switching information and the time domain scheduling length.

[0399] In step 1 of the background technology, a variable is introduced Calculate the number of REs allocated in a PRB N' RE , the process is as follows:

[0400] The UE first calculates the number of REs allocated in a PRB (physical resource block, containing 12 frequency domain units) N' RE .

[0401] in:

[0402] The number of time domain symbols of PUSCH (indicated by the time domain parameters of scheduling signaling),

[0403] is the DMRS header overhead (configured by the base station or dynamically indicated),

[0404] It is other overhead, which is configured by the base station to the UE. This parameter is semi-statically configured.

[0405] Due to the overhead introduced by beam switching.

[0406] variable The calculation is related to beamGaP and the duration of the scheduled data. An example of the relationship is shown in Table 5:

[0407] Table 5: beamGaP parameter table

[0408]

[0409] As shown in Table 5, when L = 2, It is 0, indicating that no switching occurs within the schedule when L=2. The main consideration is that the number of data symbols is relatively small.

[0410] When L=2 / 3 / 4 / 5 / 6, different The larger the L, The smaller.

[0411] When L is greater than or equal to 7, 0, indicating The impact on the calculated TB size is negligible.

[0412] This implementation method provides some examples. Of course, it can also be configured as other data as long as it reflects The value of is related to L, or to beamGap.

[0413] Example 2

[0414] An embodiment of the present invention provides a method for indicating a time domain parameter of data transmission, which is applied to a base station, as shown in FIG13, and includes:

[0415] Step S1301, indicating whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agreeing with the UE to determine whether the scheduling data includes the GAP through the scheduling condition;

[0416] Step S1302, when it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0417] Step S1303: Transmit valid scheduling data on the beam after the GAP.

[0418] Optionally, if it is agreed with the UE that whether the scheduling data includes a GAP is determined by a scheduling condition, when any of the following scheduling conditions is met, it is determined that the scheduling data does not include a GAP:

[0419] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0420] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0421] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0422] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0423] Scheduling data is data configured by high-level signaling;

[0424] The scheduled data is data scheduled by a specific DCI format.

[0425] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0426] Optionally, determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes:

[0427] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0428] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0429] Optionally, the indicating information carried in the downlink control information DCI to indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP includes:

[0430] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0431] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0432] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0433] Optionally, the scheduling data includes any of the following data:

[0434] Physical downlink shared channel PDSCH data;

[0435] Channel state information measurement reference signal CSI-RS;

[0436] Physical uplink shared channel PUSCH data.

[0437] Optionally, transmitting scheduling data on a beam after the GAP includes:

[0438] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0439] Optionally, the introduction of resource overhead associated with beam switching include:

[0440] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0441] Optionally, the introduction of resource overhead associated with beam switching include:

[0442] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0443] The embodiment of the present invention also provides a method for indicating a time domain parameter of data transmission, which is applied to a user terminal UE. Fig.14 As shown, including:

[0444] Step S1401, judging whether the scheduling data includes a beam switching time interval GAP through indication information carried in the received downlink control information DCI or through a scheduling condition agreed with the base station;

[0445] Step S1402, when it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0446] Step S1403: Transmit valid scheduling data on the beam after the GAP.

[0447] Optionally, if it is determined whether the scheduling data includes a GAP by a scheduling condition agreed with the base station, it is determined that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0448] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0449] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0450] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0451] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0452] Scheduling data is data configured by high-level signaling;

[0453] The scheduled data is data scheduled by a specific DCI format.

[0454] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0455] Optionally, determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes:

[0456] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0457] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0458] Optionally, determining whether the scheduling data includes a GAP by using indication information carried in the received downlink control information DCI includes:

[0459] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0460] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0461] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0462] Optionally, the scheduling data includes any of the following data:

[0463] Physical downlink shared channel PDSCH data;

[0464] Channel state information measurement reference signal CSI-RS;

[0465] Physical uplink shared channel PUSCH data.

[0466] Optionally, transmitting scheduling data after the GAP performs beam switching includes:

[0467] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0468] Optionally, the introduction of resource overhead associated with beam switching include:

[0469] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0470] Optionally, the introduction of resource overhead associated with beam switching include:

[0471] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0472] The base station for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the base station in the above-mentioned embodiment 1 of the present invention. The various implementation methods of the time domain parameter indication of base station data transmission applied to the system provided in the above-mentioned embodiment can be applied to the base station for indicating the time domain parameters of data transmission in this embodiment, and will not be repeated here.

[0473] The user terminal UE for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the user terminal UE in the above-mentioned embodiment 1 of the present invention, and the various implementation methods of indicating the time domain parameters of data transmission for the user terminal UE in the system provided in the above-mentioned embodiment can be applied to the user terminal UE for indicating the time domain parameters of data transmission in the present embodiment, which will not be repeated here.

[0474] Example 3

[0475] The embodiment of the present invention provides a base station for indicating a time domain parameter of data transmission, such as Fig.15 As shown, including:

[0476] Memory 1501 , processor 1502 , transceiver 1503 , and bus interface 1504 .

[0477] The processor 1502 is responsible for managing the bus architecture and general processing, and the memory 1501 can store data used by the processor 1502 when performing operations. The transceiver 1503 is used to receive and send data under the control of the processor 1502.

[0478] The bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1502 and memory represented by memory 1501. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. Processor 1502 is responsible for managing the bus architecture and general processing, and memory 1501 may store data used by processor 1502 when performing operations.

[0479] The process disclosed in the embodiment of the present invention can be applied to the processor 1502, or implemented by the processor 1502. In the implementation process, each step of the signal processing process can be completed by the hardware integrated logic circuit or software instructions in the processor 1502. The processor 1502 can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor can be executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1501, and the processor 1502 reads the information in the memory 1501 and completes the steps of the signal processing process in combination with its hardware.

[0480] Specifically, the processor 1502 is used to read the program in the memory 1501 and execute:

[0481] Indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions; when it is determined that the GAP is included, determine the GAP according to the UE switching capability parameter agreed in the interface protocol;

[0482] Valid scheduling data is transmitted on the beam after the GAP.

[0483] Optionally, if the processor agrees with the UE to determine whether the scheduling data includes a GAP through a scheduling condition, the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0484] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0485] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0486] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0487] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0488] Scheduling data is data configured by high-level signaling;

[0489] The scheduled data is data scheduled by a specific DCI format.

[0490] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0491] Optionally, the processor determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0492] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0493] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0494] Optionally, the processor indicates, through indication information carried in downlink control information DCI, whether scheduling data of a user terminal UE includes a beam switching time interval GAP, including:

[0495] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0496] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0497] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0498] Optionally, the scheduling data includes any of the following data:

[0499] Physical downlink shared channel PDSCH data;

[0500] Channel state information measurement reference signal CSI-RS;

[0501] Physical uplink shared channel PUSCH data.

[0502] Optionally, the processor transmitting scheduling data on a beam after the GAP includes:

[0503] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0504] Optionally, the processor introduces resource overhead associated with beam switching include:

[0505] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0506] Optionally, the processor introduces resource overhead associated with beam switching include:

[0507] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0508] An embodiment of the present invention provides a user terminal UE for indicating a time domain parameter for data transmission, such as Fig.16 As shown, including:

[0509] Memory 1601 , processor 1602 , transceiver 1603 , and bus interface 1604 .

[0510] The processor 1602 is responsible for managing the bus architecture and general processing, and the memory 1601 can store data used by the processor 1602 when performing operations. The transceiver 1603 is used to receive and send data under the control of the processor 1602.

[0511] The bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1602 and memory represented by memory 1601. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. Processor 1602 is responsible for managing the bus architecture and general processing, and memory 1601 may store data used by processor 1602 when performing operations.

[0512] The process disclosed in the embodiment of the present invention can be applied to the processor 1602, or implemented by the processor 1602. In the implementation process, each step of the signal processing process can be completed by the hardware integrated logic circuit or software instructions in the processor 1602. The processor 1602 can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor can be executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1601, and the processor 1602 reads the information in the memory 1601 and completes the steps of the signal processing process in combination with its hardware.

[0513] Specifically, the processor 1602 is used to read the program in the memory 1601 and execute:

[0514] Determine whether the scheduling data includes the beam switching time interval GAP through indication information carried in the received downlink control information DCI or through scheduling conditions;

[0515] When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol;

[0516] Valid scheduling data is transmitted on the beam after the GAP.

[0517] Optionally, the processor determines whether the scheduling data includes a GAP according to a scheduling condition agreed with the base station, and the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0518] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0519] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0520] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0521] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0522] Scheduling data is data configured by high-level signaling;

[0523] The scheduled data is data scheduled by a specific DCI format.

[0524] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0525] Optionally, the processor determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0526] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0527] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0528] Optionally, the processor determines, by indication information carried in received downlink control information DCI, whether the scheduling data includes a GAP, including:

[0529] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0530] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0531] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0532] Optionally, the scheduling data includes any of the following data:

[0533] Physical downlink shared channel PDSCH data;

[0534] Channel state information measurement reference signal CSI-RS;

[0535] Physical uplink shared channel PUSCH data.

[0536] Optionally, the processor transmitting scheduling data after the GAP performs beam switching includes:

[0537] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0538] Optionally, the processor introduces resource overhead associated with beam switching include:

[0539] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0540] Optionally, the processor introduces resource overhead associated with beam switching include:

[0541] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0542] The base station for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the base station in the above-mentioned embodiment 1 of the present invention. The various implementation methods of the time domain parameter indication of base station data transmission applied to the system provided in the above-mentioned embodiment can be applied to the base station for indicating the time domain parameters of data transmission in this embodiment, and will not be repeated here.

[0543] The user terminal UE for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the user terminal UE in the above-mentioned embodiment 1 of the present invention, and the various implementation methods of indicating the time domain parameters of data transmission for the user terminal UE in the system provided in the above-mentioned embodiment can be applied to the user terminal UE for indicating the time domain parameters of data transmission in the present embodiment, which will not be repeated here.

[0544] The embodiment of the present invention provides a base station for indicating a time domain parameter of data transmission, such as Fig.17 As shown, including:

[0545] The indication judgment unit 1701 indicates to the user terminal UE whether the scheduling data includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agrees with the UE to determine whether the scheduling data includes the GAP through the scheduling condition;

[0546] A GAP determining unit 1702, configured to determine the GAP according to the UE handover capability parameter agreed upon in the interface protocol when determining that the GAP is included;

[0547] The data transmission unit 1703 is used to transmit valid scheduling data on the beam after the GAP.

[0548] Optionally, if the indication judgment unit agrees with the UE to judge whether the scheduling data includes GAPP by the scheduling condition, it is determined that the scheduling data does not include GAP when any of the following scheduling conditions is met:

[0549] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0550] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0551] The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal;

[0552] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0553] Scheduling data is data configured by high-level signaling;

[0554] The scheduled data is data scheduled by a specific DCI format.

[0555] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0556] Optionally, the indication judgment unit determines the GAP according to a UE handover capability parameter agreed upon in an interface protocol, including:

[0557] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0558] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0559] Optionally, the indication judgment unit indicates, through indication information carried in downlink control information DCI, whether the scheduling data of the user terminal UE includes the beam switching time interval GAP, including:

[0560] Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or

[0561] Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP;

[0562] Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

[0563] Optionally, the scheduling data includes any of the following data:

[0564] Physical downlink shared channel PDSCH data;

[0565] Channel state information measurement reference signal CSI-RS;

[0566] Physical uplink shared channel PUSCH data.

[0567] Optionally, the data transmission unit transmits the scheduling data on the beam after the GAP, including:

[0568] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0569] Optionally, the data transmission unit introduces resource overhead associated with beam switching include:

[0570] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0571] Optionally, the data transmission unit introduces resource overhead associated with beam switching include:

[0572] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0573] An embodiment of the present invention provides a user terminal UE for indicating a time domain parameter for data transmission, such as Fig.18 As shown, including:

[0574] The receiving judgment unit 1801 is used to judge whether the scheduling data includes the beam switching time interval GAP through the indication information carried in the received downlink control information DCI or through the scheduling condition;

[0575] The determination unit 1802 is used to determine the GAP according to the UE switching capability parameters agreed upon in the interface protocol when determining that the GAP is included; the transmission unit 1803 is used to transmit valid scheduling data on the beam after the GAP.

[0576] Optionally, if the receiving judgment unit judges whether the scheduling data includes a GAP according to the scheduling condition agreed with the base station, it is determined that the scheduling data does not include a GAP when any of the following scheduling conditions is met:

[0577] The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold;

[0578] The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than the preset length;

[0579] The starting position of the scheduling data is the synchronization signal SS / PBCH signal;

[0580] The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion;

[0581] Scheduling data is data configured by high-level signaling;

[0582] The scheduled data is data scheduled by a specific DCI format.

[0583] Optionally, the UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

[0584] Optionally, the receiving judgment unit determines the GAP according to a UE switching capability parameter agreed upon in an interface protocol, including:

[0585] Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol;

[0586] The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

[0587] Optionally, the receiving judgment unit determines whether the scheduling data includes a GAP through indication information carried in the received downlink control information DCI, including:

[0588] Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or

[0589] Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI;

[0590] Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

[0591] Optionally, the scheduling data includes any of the following data:

[0592] Physical downlink shared channel PDSCH data;

[0593] Channel state information measurement reference signal CSI-RS;

[0594] Physical uplink shared channel PUSCH data.

[0595] Optionally, the transmission unit transmits the scheduling data after the GAP performs beam switching, including:

[0596] When the scheduling data is transmitted on the beam after the GAP, the resource overhead related to beam switching is introduced. Used to calculate the length TBsize of the scheduled data transmission block.

[0597] Optionally, the transmission unit introduces resource overhead associated with beam switching include:

[0598] Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

[0599] Optionally, the transmission unit introduces resource overhead associated with beam switching Also used for:

[0600] When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

[0601] The base station for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the base station in the above-mentioned embodiment 1 of the present invention. The various implementation methods of the time domain parameter indication of base station data transmission applied to the system provided in the above-mentioned embodiment can be applied to the base station for indicating the time domain parameters of data transmission in this embodiment, and will not be repeated here.

[0602] The user terminal UE for indicating the time domain parameters of data transmission provided in the embodiment of the present invention belongs to the same inventive concept as the user terminal UE in the above-mentioned embodiment 1 of the present invention, and the various implementation methods of indicating the time domain parameters of data transmission for the user terminal UE in the system provided in the above-mentioned embodiment can be applied to the user terminal UE for indicating the time domain parameters of data transmission in the present embodiment, which will not be repeated here.

[0603] An embodiment of the present invention further provides a computer program medium on which a computer program is stored. When the program is executed by a processor, the steps of the method for indicating the time domain parameters of data transmission applied to a base station provided in the above-mentioned embodiment 2 are implemented.

[0604] The present invention also provides a computer program medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for indicating the time domain parameters of data transmission applied to a user terminal UE provided in the above-mentioned embodiment 2.

[0605] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0606] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0607] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium.

[0608] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0609] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

[0610] The technical solution provided by the present application is introduced in detail above. The principles and implementation methods of the present application are explained by using specific examples in the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

[0611] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0612] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0613] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0614] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0615] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for indicating a time domain parameter of data transmission, applied to a base station, characterized in that: The method includes: Indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions; When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol; Transmitting scheduling data on the beam after the GAP and introducing resource overhead associated with beam switching Used to calculate the length TBsize of the scheduled data transmission block.

2. The method according to claim 1, characterized in that If it is agreed with the UE that whether the scheduling data contains a GAP is determined by the scheduling condition, then when any of the following scheduling conditions is met, it is determined that the scheduling data does not contain a GAP: The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold; The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than a preset length; The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal; The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion; Scheduling data is data configured by high-level signaling; The scheduled data is data scheduled by a specific DCI format.

3. The method according to claim 1 or 2, characterized in that: The UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

4. The method according to claim 1, characterized in that The determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes: Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol; The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

5. The method according to claim 1 or 2, characterized in that: The indication information carried in the downlink control information DCI indicates whether the scheduling data of the user terminal UE includes the beam switching time interval GAP, including: Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP; Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

6. The method according to claim 1, characterized in that The scheduling data includes any of the following data: Physical downlink shared channel PDSCH data; Channel state information measurement reference signal CSI-RS; Physical uplink shared channel PUSCH data.

7. The method according to claim 1, characterized in that The introduction of resource overhead associated with beam switching include: Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

8. The method according to claim 1 or 7, characterized in that: The introduction of resource overhead associated with beam switching include: When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

9. A method for indicating a time domain parameter of data transmission, applied to a user terminal UE, characterized in that: include: Determine whether the scheduling data includes the beam switching time interval GAP through indication information carried in the received downlink control information DCI or through scheduling conditions agreed with the base station; When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol; Transmitting scheduling data on the beam after the GAP and introducing resource overhead associated with beam switching Used to calculate the length TBsize of the scheduled data transmission block.

10. The method according to claim 9, characterized in that If it is determined whether the scheduling data includes a GAP by the scheduling condition agreed with the base station, it is determined that the scheduling data does not include a GAP when any of the following scheduling conditions is met: The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold; The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than a preset length; The starting position of the scheduling data is the synchronization signal SS / PBCH signal; The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion; Scheduling data is data configured by high-level signaling; The scheduled data is data scheduled by a specific DCI format.

11. The method according to claim 9 or 10, characterized in that: The UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

12. The method according to claim 9, characterized in that The determining the GAP according to the UE handover capability parameter agreed upon in the interface protocol includes: Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol; The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

13. The method according to claim 9 or 10, characterized in that: The determining whether the scheduling data includes a GAP by using indication information carried in the received downlink control information DCI includes: Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI; Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

14. The method according to claim 9, characterized in that The scheduling data includes any of the following data: Physical downlink shared channel PDSCH data; Channel state information measurement reference signal CSI-RS; Physical uplink shared channel PUSCH data.

15. The method according to claim 9, characterized in that The introduction of resource overhead associated with beam switching include: Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

16. The method according to claim 9 or 15, characterized in that The introduction of resource overhead associated with beam switching include: When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

17. A base station for data transmission time domain parameter indication, characterized in that: comprising a memory and a processor, wherein: The memory is used to store computer programs; The processor is used to read the program in the memory and execute the following steps: Indicate whether the scheduling data of the user terminal UE includes the beam switching time interval GAP through the indication information carried in the downlink control information DCI, or agree with the UE to determine whether the scheduling data includes the GAP through the scheduling conditions; When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol; Transmitting scheduling data on the beam after the GAP and introducing resource overhead associated with beam switching Used to calculate the length TBsize of the scheduled data transmission block.

18. The base station according to claim 17, characterized in that: If the processor agrees with the UE to determine whether the scheduling data includes a GAP according to a scheduling condition, the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met: The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold; The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than a preset length; The starting position of the scheduling data is the synchronization signal SS / physical broadcast channel PBCH signal; The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion; Scheduling data is data configured by high-level signaling; The scheduled data is data scheduled by a specific DCI format.

19. The base station according to claim 17 or 18, characterized in that: The UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

20. The base station according to claim 17, characterized in that: The processor determines the GAP according to the UE handover capability parameter agreed upon in the interface protocol, including: Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol; The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

21. The base station according to claim 17 or 18, characterized in that: The processor indicates, through indication information carried in downlink control information DCI, whether scheduling data of a user terminal UE includes a beam switching time interval GAP, including: Using different values ​​of a bit to indicate whether the scheduling data contains GAP; or Using different values ​​of a bit to indicate that the scheduling data includes a GAP and a switching position of the GAP; Different values ​​of the two bits are used to indicate whether the scheduling data includes a GAP and the switching position of the GAP.

22. The base station according to claim 17, characterized in that The scheduling data includes any of the following data: Physical downlink shared channel PDSCH data; Channel state information measurement reference signal CSI-RS; Physical uplink shared channel PUSCH data.

23. The base station according to claim 17, characterized in that: The processor introduces resource overhead associated with beam switching include: Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

24. The base station according to claim 17 or 23, characterized in that: The processor introduces resource overhead associated with beam switching include: When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

25. A user terminal UE for transmitting a time domain parameter indication of data, characterized in that: comprising a memory and a processor, wherein: The memory is used to store computer programs; The processor is used to read the program in the memory and execute the following steps: Determine whether the scheduling data includes the beam switching time interval GAP through indication information carried in the received downlink control information DCI or through scheduling conditions; When it is determined that a GAP is included, the GAP is determined according to a UE handover capability parameter agreed upon in the interface protocol; Transmitting scheduling data on the beam after the GAP and introducing resource overhead associated with beam switching Used to calculate the length TBsize of the scheduled data transmission block.

26. The user terminal UE according to claim 25, characterized in that: The processor determines whether the scheduling data includes a GAP according to the scheduling condition agreed with the base station, and the processor determines that the scheduling data does not include a GAP when any of the following scheduling conditions is met: The delay between the start symbol of the scheduling data indicated by the DCI scheduling indication and the last symbol of the physical downlink control channel PDCCH of the DCI is less than a preset threshold; The length of scheduled physical downlink shared channel PDSCH / physical uplink shared channel PUSCH data is less than a preset length; The starting position of the scheduling data is the synchronization signal SS / PBCH signal; The starting position of the scheduling data is the first symbol after the uplink signal / downlink signal conversion; Scheduling data is data configured by high-level signaling; The scheduled data is data scheduled by a specific DCI format.

27. The user terminal UE according to claim 25 or 26, characterized in that: The UE switching capability parameter includes a UE switching capability device level related to the UE itself, and at least one UE switching capability transmission parameter including a subcarrier spacing, a DCI format of scheduling data, and a transmission direction of scheduling data.

28. The user terminal UE according to claim 26, characterized in that: The processor determines the GAP according to the UE handover capability parameter agreed upon in the interface protocol, including: Determining the number of symbols of the GAP according to the UE handover capability parameter agreed upon in the interface protocol; The switching position of the GAP is determined according to the switching positions corresponding to different numbers of time units defined in the interface protocol.

29. The user terminal UE according to claim 25 or 26, characterized in that: The processor determines, by means of indication information carried in received downlink control information DCI, whether the scheduling data includes a GAP, including: Determine whether the scheduling data includes a GAP by taking different values ​​of a bit carried in the DCI; or Determine whether the scheduling data includes a GAP and a switching position of the GAP through different values ​​of a bit carried in the DCI; Whether the scheduling data includes a GAP and the switching position of the GAP are determined by different values ​​of the two bits carried in the DCI.

30. The user terminal UE according to claim 25, characterized in that: The scheduling data includes any of the following data: Physical downlink shared channel PDSCH data; Channel state information measurement reference signal CSI-RS; Physical uplink shared channel PUSCH data.

31. The user terminal UE according to claim 25, characterized in that: The processor introduces resource overhead associated with beam switching include: Determine according to the number of symbols of the GAP and the number of symbols of the scheduling data The more symbols there are in the scheduling data, The smaller.

32. The user terminal UE according to claim 25 or 31, characterized in that: The processor introduces resource overhead associated with beam switching include: When it is determined that the number of symbols of the scheduling data is less than a preset low threshold or greater than a preset high threshold, the is 0, the preset high threshold is greater than the preset low threshold.

33. A base station for data transmission time domain parameter indication, characterized in that: include: An indication judgment unit, used to determine whether the scheduling data includes a beam switching time interval GAP, and indicate it to the user terminal UE through the indication information carried in the downlink control information DCI, or judge by agreeing on a scheduling condition with the UE; A GAP determining unit, configured to determine the GAP according to the UE handover capability parameter agreed upon in the interface protocol when determining that the GAP is included; A data transmission unit, used to transmit scheduling data on the beam after the GAP and introduce resource overhead related to beam switching Used to calculate the length TBsize of the scheduled data transmission block.

34. A user terminal UE for data transmission time domain parameter indication, characterized in that: include: A receiving judgment unit, configured to judge whether the scheduling data includes a beam switching time interval GAP through indication information carried in the received downlink control information DCI or through a scheduling condition; A determining unit, configured to determine, when determining that a GAP is included, the GAP according to a UE handover capability parameter agreed upon in an interface protocol; A transmission unit, used to transmit scheduling data on the beam after the GAP and introduce resource overhead related to beam switching Used to calculate the length TBsize of the scheduled data transmission block.

35. A computer program medium, characterized in that A computer program is stored thereon, which implements the steps of the method as claimed in any one of claims 1 to 8 when executed by a processor, or implements the steps of the method as claimed in any one of claims 9 to 16 when executed by a processor.

Images