A wireless communication method and device

Abstract

The application relates to the field of wireless communication, in particular to a wireless communication method and device. The application provides a method. If a time unit for transmitting control information is different from a time unit for transmitting data, the control information is related to the data; and timing is determined based on the same time unit. According to the application, the timing is determined based on the same time unit principle or the same time criterion, and unified timing can be determined, so that the robustness is improved, and normal communication between a base station and user equipment is ensured.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a wireless communication method and device. Background Technology

[0002] To meet the growing demands of various service types, the fifth-generation (5G) mobile communication system is required to support three major application scenarios: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC). Due to the significant differences in the reliability and latency requirements of these different application scenarios, the requirements for system parameters such as subcarrier spacing, symbol length, and time units vary depending on the specific service.

[0003] In data transmission, data is transmitted at a time unit granularity. In order to meet the different needs of different services, 5G systems have proposed a flexible mechanism for data transmission using subcarrier spacing and time units. That is, in 5G, the time unit can be different. For example, on the same carrier, uplink and downlink can use different time units for communication. In the scenario of carrier aggregation, the time units used between aggregated carriers can also be different.

[0004] Using different time units for communication may lead to timing inconsistencies between the base station and the user equipment. Summary of the Invention

[0005] This application describes a wireless communication method and device, which aims to determine timing using the same timing criteria to address the timing inconsistency problem caused by different carrier parameters due to different service requirements, thereby ensuring smooth communication.

[0006] On one hand, embodiments of this application provide a wireless communication method. The method includes determining timing based on the same time unit if the time unit used for transmitting control information differs from the time unit used for transmitting data, wherein the control information is related to the data; determining timing based on the same time unit. This "based on the same time unit" can be understood as based on the same time unit, the same time unit principle, or the same timing criterion. Therefore, timing based on the same time unit criterion ensures timing consistency between the base station and the terminal, guaranteeing smooth communication and meeting different service requirements.

[0007] In one possible design, timing is determined based on the same time unit, including: determining a first timing sequence K0 and a second timing sequence K1 based on the same time unit, wherein the first timing sequence K0 is the time relationship between the time unit for transmitting the Physical Downlink Control Channel (PDCCH) and the time unit for transmitting the Physical Downlink Shared Channel (PDSCH), the PDCCH being used to transmit control information, and the PDSCH being used to transmit data scheduled by the control information; the second timing sequence K1 is the time relationship between the time unit for transmitting the PDSCH and the time unit for transmitting the PUCCH or PUSCH, the PDSCH being used to transmit data, and the PDCCH or PUSCH being used to transmit control information corresponding to the data, the control information being uplink feedback information corresponding to the data. Thus, determining the first and second timing sequences based on the same time unit ensures timing consistency.

[0008] In one possible design, a third timing sequence K2 is also determined based on the same time unit. This third timing sequence K2 is the time relationship between the time unit for transmitting PDCCH and the time unit for transmitting PUSCH. The PDCCH is used to transmit control information, and the PUSCH is used to transmit uplink data scheduled by the control information. Determining the first, second, and third timing sequences based on the same time unit ensures timing consistency, guarantees smooth communication, and simplifies system design.

[0009] In one possible design, timing is determined based on the same time unit, including: determining timing based on the time unit used for data transmission; or, determining timing based on the time unit used for control information transmission; or, determining timing based on the longer of the time units used for control information transmission and the time units used for data transmission; or, determining timing based on the shorter of the time units used for control information transmission and the time units used for data transmission; or, determining timing based on a source time unit or a target time unit; or, determining timing based on a reference time interval. Thus, this application provides multiple methods for determining timing for flexible selection.

[0010] In one possible design, the timing is determined based on the same time unit. The method further includes: sending downlink control information (DCI) for scheduling downlink transmission to the user equipment (UE). The DCI for scheduling downlink transmission includes a first indication field for indicating the value of K0 and a second indication field for notifying the value of K1. The proportions of the first and second indication fields are equal. This saves DCI signaling overhead and ensures the flexibility of K0 and K1.

[0011] In one possible design, downlink control information (DCI) for scheduling uplink transmission is sent to the user equipment (UE). The DCI for scheduling uplink transmission includes a third indication field for notifying the value of K2, wherein the number of bits occupied by the third indication field, the first indication field, and the second indication field is equal; or the number of bits occupied by the third indication field is equal to the sum of the number of bits occupied by the first indication field and the second indication field.

[0012] In one possible design, the method further includes at least one of the following: transmitting at least one first set and a relationship between the first set and time units to the UE, wherein the first set includes at least one distinct value of K0; transmitting at least one second set and a relationship between the second set and time units to the UE, wherein the second set includes at least one distinct value of K1; and transmitting at least one third set and a relationship between the third set and time units to the UE, wherein the second set includes at least one distinct value of K2. Thus, the UE can determine the set based on time units or subcarrier intervals, and determine the specific timing based on the timing values ​​indicated in the DCI.

[0013] On the other hand, this application provides an apparatus that can implement the functions of the method provided in this application. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0014] On the other hand, this application provides a device including a processor, a transmitter, and a receiver, characterized in that if the time unit used for transmitting control information is different from the time unit used for transmitting data, the control information is related to the data; the processor is used to determine timing based on the same time unit. This device can implement the relevant functions of the method provided in this application.

[0015] On the one hand, this application provides a computer storage medium for storing computer software instructions used for the aforementioned data transmission device, which includes programs designed to perform the aforementioned aspects.

[0016] In another aspect, this application provides a computer storage medium for storing computer software instructions for use in the aforementioned data receiving device, which includes programs designed to execute the above aspects.

[0017] On the other hand, this application provides a chip system including a processor for supporting the device in implementing the functions involved in the above aspects. This chip system may be composed of chips or may include chips and other discrete devices.

[0018] This application describes a wireless communication method and device that uses the same timing criteria to determine timing sequence, thereby addressing the issue of inconsistent timing in scenarios where different carrier parameters result from different service requirements, and ensuring smooth communication. Attached Figure Description

[0019] The embodiments of this application will now be described in more detail with reference to the accompanying drawings.

[0020] Figure 1 The diagram shown illustrates one possible application scenario of this application.

[0021] Figure 2 An example diagram of downlink communication in LTE technology is shown.

[0022] Figure 3 An example diagram of uplink communication in LTE technology is shown.

[0023] Figure 4 An example diagram of one embodiment of the present application is shown.

[0024] Figure 5 An example diagram of one embodiment of the present application is shown.

[0025] Figure 6 An example diagram of one embodiment of the present application is shown.

[0026] Figure 7 An example diagram of one embodiment of the present application is shown.

[0027] Figure 8 An example diagram of one embodiment of the present application is shown.

[0028] Figure 9 An example diagram of one embodiment of the present application is shown.

[0029] Figure 10 An example diagram of one embodiment of the present application is shown.

[0030] Figure 11 An example diagram of one embodiment of the present application is shown.

[0031] Figure 12 An example diagram of one embodiment of the present application is shown.

[0032] Figure 13 An example diagram of one embodiment of the present application is shown.

[0033] Figure 14 An example diagram of one embodiment of the present application is shown.

[0034] Figure 15An example diagram of one embodiment of the present application is shown.

[0035] Figure 16 A flowchart illustrating one embodiment of the present application is shown.

[0036] Figure 17 An example diagram of one embodiment of the present application is shown.

[0037] Figure 18 An example diagram of one embodiment of the present application is shown.

[0038] Figure 19 An example diagram of one embodiment of the present application is shown.

[0039] Figure 20 An example diagram of one embodiment of the present application is shown.

[0040] Figure 21 A schematic diagram of the structure provided in this application is shown. Detailed Implementation

[0041] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0042] The network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0043] The technology described in this invention can be applied to Long Term Evolution (LTE) systems or other wireless communication systems that employ various wireless access technologies, such as systems using code division multiple access, frequency division multiple access, time division multiple access, orthogonal frequency division multiple access, and single-carrier frequency division multiple access. It can also be applied to systems that use subsequent evolutions of the LTE system, such as the fifth-generation 5G system.

[0044] like Figure 1 The diagram shown is a possible application scenario of this application. The user equipment (UE) communicates with the network-side equipment via a wireless interface, and can also communicate with another user equipment, such as in device-to-device (D2D) or machine-to-machine (M2M) scenarios.

[0045] Network-side equipment can communicate with user equipment (UE) or with other network-side equipment, such as communication between a macro base station and an access point. In this application, the terms "network" and "system" are often used interchangeably, but their meanings will be understood by those skilled in the art. The user equipment involved in this application can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, control devices, or other processing devices connected to a wireless modem, as well as various forms of UE, mobile station (MS), terminal, or terminal equipment. For ease of description, the above-mentioned devices are collectively referred to as user equipment (UE) in this application. The network-side equipment involved in this application includes base stations (BS), network controllers, or mobile switching centers, etc. The device that directly communicates with the user equipment via a wireless channel is typically a base station. The base station can include various forms of macro base stations, micro base stations, relay stations, access points, or remote radio units (RRUs), etc. Of course, other network-side equipment with wireless communication capabilities can also communicate with the user equipment; this application does not limit this to a single type. In different systems, the names of devices with base station functions may vary, such as evolved NodeB (eNB or eNodeB), Node B, Transmission and Reception Point (TRP), etc.

[0046] The technical solutions provided in this application can be applied to uplink data transmission and / or downlink data transmission. For uplink data transmission, the data transmitting device can be a user equipment and the data receiving device can be a network-side device, such as a base station. For downlink data transmission, the data transmitting device can be a network-side device, such as a base station, and the data receiving device can be a user equipment.

[0047] Figure 2 An example diagram of downlink communication in LTE technology is shown.

[0048] Taking downlink communication in existing LTE technology as an example, the time interval between the time unit used for downlink scheduling and the corresponding time unit used for downlink data transmission is denoted as K0 time units in this application. The time unit in LTE can be fixed, for example, 1 ms. Figure 2 In this context, each cell in a row can be considered a unit of time.

[0049] Specifically, if downlink scheduling information is transmitted through the Physical Downlink Control Channel (PDCCH) in the nth time unit, this downlink scheduling information can be downlink control information (DCI). The corresponding downlink data transmission through the Physical Downlink Shared Channel (PDSCH) uses n+K0 time units. In the current LTE system, K0 can be 0.

[0050] In existing LTE technology, a Hybrid Automatic Repeat Request (HARQ) mechanism has been introduced to ensure the reliability of data communication. After the sending end sends data, it needs to wait for the receiving end to send back confirmation information. This confirmation information can be an acknowledgment (ACK) or a negative acknowledgment (NACK).

[0051] The time interval between the time unit used for downlink data transmission and the time unit used for the corresponding feedback confirmation information is denoted as K1 time units in this application. Specifically, if downlink data is transmitted via PDSCH in the nth time unit, the time unit used for transmitting the corresponding confirmation information via the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) is the (n+K1)th time unit. In the current LTE system, K1 can be 4.

[0052] The time interval between the time unit used for the confirmation message feedback and the corresponding time unit for data retransmission is denoted as K3 time units in this application. Specifically, if confirmation information is fed back via PUSCH or PUCCH in the nth time unit, the time unit used by the corresponding base station for data retransmission is the (n+K3)th time unit. In the current LTE system, K3 can be 4.

[0053] like Figure 2 As shown, in LTE, if K0=0, K1=4, and K3=4, the number of processes required to ensure continuous downlink transmission is 8.

[0054] Figure 3 An example diagram of uplink communication in LTE technology is shown.

[0055] Taking existing LTE uplink communication as an example, the time interval between the time unit used for uplink scheduling and the corresponding time unit used for uplink data transmission is denoted as K2 time units in this application. For the definition of a time unit, please refer to [reference needed]. Figure 2 The relevant description in the document.

[0056] Specifically, if downlink scheduling information is sent via PDCCH in the nth time unit, the corresponding uplink data transmission via PUSCH uses the n+K2th time unit.

[0057] The time interval between the time unit used for uplink data transmission and the time unit used for the corresponding uplink data retransmission scheduling is denoted as K4 time units in this application. Specifically, if uplink data transmission is performed via PUSCH in the nth time unit, the time unit used for the corresponding uplink data retransmission scheduling via PDCCH is the (n+K4)th time unit.

[0058] like Figure 3 As shown, in LTE, if K2=4 and K4=4, the number of processes required to ensure continuous uplink transmission is 8.

[0059] Currently in LTE, K0 is 0, K1 and K2 are 4 in Frequency Division Duplexing (FDD) mode and are fixed values ​​in Time Division Duplexing (TDD) mode, specifically determined by the subframe configuration of TDD. K3 and K4 are mainly determined based on the base station's capabilities and scheduling; in LTE's FDD mode, K3 and K4 are 4.

[0060] The definitions of K0, K1, K2, K3 and K4 mentioned above can be referenced in subsequent evolution systems. In this application, K0, K1, K2, K3 and K4 are referred to as timing sequences.

[0061] To meet the diverse needs of different services, the subcarrier spacing and time units used between different carriers can vary. Different configured subcarrier spacings, or configurations for slot-based or mini-slot-based transmission, as well as different numbers of slots, mini-slots, and symbols, will all lead to different time units. The time units used for uplink and downlink transmission on the same carrier can also differ. In such cases, determining the timing sequence to ensure normal communication between the base station and user equipment is a problem that needs to be solved.

[0062] All embodiments in this article are described with different time units. They can also be replaced with different subcarrier intervals, different number of symbols, or different carrier parameter numbers. The carrier configuration parameters (numberology) of the carrier can include subcarrier interval, time unit length, CP type, etc.

[0063] Therefore, embodiments of this application provide a wireless communication method that can be executed by a network-side device, such as a base station, or a user equipment.

[0064] If the time unit used for transmitting control information is different from the time unit used for transmitting data, the timing is determined based on the same time unit.

[0065] When different subcarrier intervals or time units are configured, using the same time unit as the basic unit allows for the determination of a unified timing sequence, improving robustness, ensuring normal communication between the base station and user equipment, and simplifying system design. This "based on the same time unit" can be understood as being based on the same time unit, the same time unit principle, or the same timing criterion.

[0066] The control information is related to the transmitted data. Specifically, the control information can be downlink scheduling information (e.g., DCI), transmitted via PDCCH, and the data can be downlink data corresponding to the downlink scheduling information, transmitted via PDSCH; or, the data can be downlink data, transmitted via PDSCH, and the control information can be uplink control information, transmitted via PUSCH or PUCCH. For example, it can be acknowledgment information, such as an ACK message or a NACK message; or the control information can be downlink control information (DCI), transmitted via PDCCH, and the data can be uplink data scheduled by the downlink control information, transmitted via PUSCH. In other words, the control information can be control information for scheduled data, or feedback information corresponding to the data (used to determine whether to retransmit, which can be acknowledgment information, such as ACK or NACK messages). Further descriptions of the control information, data, and corresponding channels can be found in this section, and this application does not limit these aspects.

[0067] Timing can be determined based on the same time unit. This can also be called determining timing based on the same time unit principle or the same timing criterion. Multiple timing sequences can be determined based on the same unit. These multiple timing sequences can be a first timing sequence, which can be K0, used to indicate the time relationship between the time unit for transmitting PDCCH and the time unit for transmitting PDSCH. That is, if the base station sends downlink scheduling information (which can be DCI information) in time unit n, the corresponding downlink data will be sent in time units n+K0. Alternatively, multiple timing sequences can be determined based on the same time unit. These multiple timing sequences can include a second timing sequence, which can be K1, used to indicate the time relationship between the time unit for transmitting PDSCH and the time unit for transmitting PUSCH or PUCCH. That is, if the base station sends downlink data in time unit n, its corresponding uplink feedback information (ACK or Nack message) will be transmitted in time unit n+K1.

[0068] Multiple timing sequences are determined based on the same time unit. These multiple timing sequences can be a third timing sequence, which can be K2, used to indicate the time relationship between the transmission of PDCCH and the transmission of PUSHC. That is, if the base station sends downlink scheduling information (which can be DCI) in time unit n, the corresponding uplink data is transmitted in time unit n+K2. Optionally, K3 or K4 can also be determined based on the same time unit.

[0069] It should be noted that in the embodiments of this application, K0, K1, K2, K3, and K4 can be used to describe the timing sequence, but there are no restrictions on the names of the timing sequences, and they can also be other representations.

[0070] It is also worth noting that the PDCCH may not occupy the entire time unit. For example, in LTE, a time unit is 1ms with 14 symbols, and the PDCCH typically only occupies the first 1 to 3 symbols. PDSCH, PUSCH, and PUCCH are similar. The channel names may differ in other systems; for example, in NR, it might be NR-PDCCH, NR-PDSCH, NR-PUSCH, NR-PUCCH, etc. This article does not impose any restrictions.

[0071] Therefore, determining the timing based on the same time unit can improve robustness and simplify system design.

[0072] Furthermore, multiple timing sequences are determined based on the same timing criterion. For example, the timing sequence can be determined based on the time unit of transmission control information; or based on the time unit of transmission data; or based on the longer time unit between the time units of transmission control information and transmission data; or based on the shorter time unit between the time units of transmission control information and transmission data; or based on a reference time interval, which could be 1 ms, 7 symbols, etc., and this application is not limited to this; or the timing sequence can be determined based on the source time unit. For the first timing sequence (the time relationship between PDCCH and PDSCH), the time unit of transmission of PDCCH is used as the timing criterion or timing unit; for the third timing sequence (the time relationship between PDCCH and PUSCH), the time unit of transmission of PDCCH is used as the timing criterion or timing unit; for the second timing sequence (the time relationship between PDSCH and PUSCH / PUCCH), the time unit of transmission of PDSCH is used as the timing criterion or timing unit; or the timing sequence can be determined based on the target time unit. For example, the timing sequence can be determined based on the same time unit. For the first timing sequence K0 (the timing relationship between PDCCH and PDSCH), the timing criterion or unit is the time unit for transmitting PDSCH; for the third timing sequence K2 (the timing relationship between PDCCH and PUSCH), the timing criterion or unit is the time unit for transmitting PUSCH; for K1 (the timing relationship between PDSCH and PUSCH / PUCCH), the timing criterion or unit is the time unit for transmitting PUSCH / PUCCH; or the timing can be determined based on the time unit for transmitting data. For example, for the first timing sequence K0 (the timing relationship between PDCCH and PDSCH), the timing criterion or unit is the time unit for transmitting PDSCH; for the third timing sequence K2 (the timing relationship between PDCCH and PUSCH), the timing criterion or unit is the time unit for transmitting PUSCH; for the second timing sequence K1 (the timing relationship between PDSCH and PUSCH / PUCCH), the timing criterion or unit is the time unit for transmitting PDSCH. Therefore, determining the timing based on the same time unit, i.e., based on the same timing criterion, can guarantee the communication quality between the base station and the terminal and improve robustness.

[0073] In one embodiment of this application, the base station can send multiple sets to the UE. These multiple sets can be sets of one or more K0s, sets of one or more K1s, combinations of one or more K2s, etc. The base station sends a correspondence between the sets and at least one of the subcarrier intervals and time units to the UE. The base station further sends indication information to the UE, which can indicate the value of the timing sequence. The UE can determine the set based on the above correspondence and determine the specific timing value based on the indication information. Thus, by sending multiple different timing values, the base station allows the UE to determine different sets based on the subcarrier interval or time unit, and then determine the timing sequence based on the indication information, enabling flexible scheduling under different subcarrier or different time unit scheduling conditions.

[0074] In one embodiment of this application, the embodiment relates to scheduling. The base station configures a PDCCH and a corresponding PDSCH or PUSCH, where X > the ratio of the PDCCH and PDSCH / PUSCH time unit lengths > 1 / Y, and X and Y are positive integers, optionally X, Y = 2 or 4; or the base station configures a PDCCH and a corresponding PDSCH or PUSCH, where the subcarrier spacing of the PDCCH and the corresponding PDSCH or PUSCH is the subcarrier spacing supported by the UE. For example, if the UE supports 15kHz, 60kHz, and 120kHz, then the PDCCH and the corresponding PDSCH or PUSCH are configured as adjacent combinations of 15kHz and 60kHz or adjacent combinations of 60kHz and 120kHz; or multiple carriers configured or activated for the UE are divided into at least one carrier group, within which cross-carrier scheduling and / or cross-carrier aggregation feedback are possible.

[0075] In one possible implementation, carrier groups comprise carriers with the same subcarrier spacing or the same time unit length. That is, the network device (e.g., a base station) divides multiple carriers configured or activated for a terminal into at least one carrier group based on the same subcarrier spacing or time unit length. Therefore, this grouping method greatly simplifies the complexity of cross-carrier scheduling or feedback. Furthermore, in another possible implementation, at most one carrier group may contain carriers with different subcarrier spacings or different time unit lengths. For example, the network device may first divide multiple carriers configured for a terminal into at least one carrier group based on the same subcarrier spacing or time unit length, and then combine the remaining carriers into a single carrier group.

[0076] In one possible implementation, a carrier group includes carriers with a maximum of two different subcarrier spacing or time unit length configurations. That is, the network device allocates carriers with a maximum of two different subcarrier spacing or time unit length configurations to each carrier group. This simplifies the complexity of cross-carrier scheduling or feedback and avoids excessive subcarrier spacing or time unit length configurations within a carrier group, which would result in high complexity for cross-carrier scheduling and feedback.

[0077] Further optionally, a carrier group may contain a maximum of two different subcarrier spacing or time unit length configurations, wherein the two different subcarrier spacing or time unit lengths are two adjacent carrier spacing or time unit lengths supported by the terminal or the system. For example, if there are carriers with subcarrier spacing configurations of 15kHz, 60kHz, and 120kHz, carriers with subcarrier spacing configurations of 15kHz and 60kHz can be grouped together, but carriers with subcarrier spacing configurations of 15kHz and 120kHz cannot be grouped together.

[0078] In one embodiment of this application, the embodiment relates to feedback. The base station configures a PDSCH and its corresponding PUCCH or PUSCH, where X > the ratio of PDSCH to PUCCH / PUSCH time length > 1 / Y, and X and Y are positive integers, optionally X, Y = 2 or 4. The subcarrier spacing of the PDSCH and its corresponding PUCCH or PUSCH is the adjacent subcarrier spacing supported by the UE. For example, if the UE supports 15k, 60k, and 120k, then an adjacent 15k and 60k combination or an adjacent 60k and 120k combination is configured, but a 15k and 120k combination cannot be configured. When the base station groups carriers, at most one group has different subcarrier spacings or time unit lengths. For example, 10 carriers are divided into 4 groups, grouped according to whether the subcarrier spacing or time unit length is the same, and the remaining different subcarrier spacings or time unit lengths constitute one group. When the base station groups carriers, each group has at most 2 carriers with different subcarrier spacings or time unit lengths.

[0079] It should be noted that the transmission time unit can be a subframe, a transmission time interval (where one transmission time interval is equal to the sum of the lengths of several subframes, or the sum of several transmission time intervals is equal to the length of one subframe), or one time-domain symbol, multiple time-domain symbols, one time slot, multiple time slot aggregations, one mini-slot, multiple mini-slot aggregations, or mini-slots and time slot aggregations, etc. The subcarrier spacing can be 15kHz*2^n (n is a positive integer), that is, a subcarrier spacing of 15kHz, 30kHz, etc. The transmission time unit is determined by the subcarrier spacing and the number of symbols. The configured subcarrier spacing, number of slots, number of mini-slots, or number of symbols will result in different time units. Therefore, all embodiments in this document that involve the configuration scheme or description of the transmission time unit can be replaced with a configuration scheme or description involving the subcarrier spacing.

[0080] The following description uses examples with different time units or different subcarrier intervals. These examples can be implemented by a base station or user equipment.

[0081] Figure 4 An example diagram of one embodiment of the present application is shown.

[0082] like Figure 4 As shown, the time unit used for transmitting control information is longer than the time unit used for transmitting data, such as... Figure 4 As shown, the first time unit on carrier 1 is used to transmit the PDCCH, and the time units on carrier 2 can be used to transmit the corresponding PDSCH. Figure 4 The first column indicates the time unit used by carrier 1, and the second column indicates the time unit used by carrier 2.

[0083] In this application, the time unit refers to the minimum time interval used for transmission. It can be a subframe, one or more time-domain symbols, one time slot or a combination of multiple time slots, one mini-slot or a combination of multiple mini-slots, etc. Here, the time unit used by carrier 1 is greater than the time unit used by carrier 2. The subcarrier spacing can be 15kHz*2^m (m is a positive integer), i.e., a subcarrier spacing of 15kHz, 30kHz, etc. The transmission time unit is determined by the subcarrier spacing and the number of symbols. Therefore, the configuration scheme or description involving transmission time units in the embodiments of this application can be replaced with a configuration scheme or description involving subcarrier spacing. Here, the time unit used by carrier 1 is greater than the time unit used by carrier 2, or the subcarrier spacing used by carrier 1 is less than the subcarrier spacing used by carrier 2.

[0084] In one embodiment of this application, the timing is determined by using a short time unit as the base time unit. In this application, PDCCH is used for downlink scheduling and PDSCH is used for downlink data transmission. The time relationship between the time unit used for transmitting PDCCH and the time unit used for transmitting PDSCH is denoted as K0. If the short time unit is used as the base time unit, K0 can be 0 or 1, or 2... or 5. This application does not limit this.

[0085] Figure 5 An example diagram of one embodiment of the present application is shown.

[0086] like Figure 5 As shown, the time unit used for transmitting control information is shorter than the time unit used for transmitting data, such as... Figure 5 As shown, the first time unit of carrier 1 is used to schedule the PDCCH, and the time unit of carrier 2 can be used to schedule the corresponding PDSCH. Figure 5 In this context, the two time units used to schedule PDCCH are aligned with the time units that can be used to schedule PDSCH.

[0087] In one embodiment of this application, timing is determined using short time units as the basis for determining the timing sequence.

[0088] In this application, PDCCH is used for downlink scheduling, and PDSCH is used for corresponding downlink data transmission. The time relationship between the time unit used for transmitting PDCCH and the time unit used for transmitting PDSCH is K0. If the shortest time unit is used as the base time unit, then based on the time interval between the downlink scheduling time unit and the time unit used for PDCCH, the time unit that can be used to schedule PDSCH with a time unit no more than one time unit longer than the time unit used for PDCCH is designated as the 0th time unit. In this case, K0 can be 0, 2, or 4.

[0089] Figure 6 An example diagram of one embodiment of the present application is shown.

[0090] Figure 6 and Figure 5The difference lies in the position of the time unit used for PDCCH transmission, which is already located after the time unit A used by its corresponding carrier 2 (assuming M short time units are aligned with 1 long time unit (time unit A), and the time unit used for PDCCH transmission is the i-th of the M short time units, i>1; the corresponding part in subsequent embodiments can refer to the description here). At this time, the time unit used by the corresponding PDSCH can be the next time unit after time unit A. Optionally, if the time unit is based on short time units, and the distance between the next time unit of time unit A and the time unit used for PDCCH transmission is one short time unit, then K0 of the next time unit of time unit A is recorded as 1, and K0 of the next time unit after that can be recorded as 3, and K0 of subsequent time units is incremented by 2, and so on. In this embodiment, K0 of the time unit used for PDSCH scheduling can be 1 or 3, and this application is not limited to this.

[0091] Alternatively, since the time unit used for transmitting the PDCCH is already after time unit A, scheduling time unit A is already difficult. We can set K0 of the next time unit after time unit A to 0, then K0 of the next time unit after that can be set to 2, and so on, incrementing K0 for subsequent time units. In this embodiment, K0 of the time unit used for scheduling the PDCCH can be either 0 or 2; this application is not limited in this respect.

[0092] Figure 7 An example diagram of one embodiment of the present application is shown.

[0093] like Figure 7 As shown, the time unit used for transmitting control information is longer than the time unit used for transmitting data, such as... Figure 7 As shown, the first time unit of carrier 1 is used to transmit the PDCCH, and the time units on carrier 2 can be used to transmit the corresponding PDSCH. Here, the time units used by carrier 1 are longer than those used by carrier 2. The two time units used for scheduling the PDCCH are aligned with the time units that can be used for scheduling the PDSCH.

[0094] In one embodiment of this application, timing is determined using a long time unit as the basis for determining the timing sequence.

[0095] In this application, PDCCH is used for downlink scheduling, and PDSCH is used for corresponding downlink data transmission. The time relationship between the time unit used for transmitting PDCCH and the time unit used for transmitting PDSCH is denoted as K0. If a longer time unit is used as the base time unit, and the time unit that can be used to schedule PDSCH within the same time range as the time unit used for PDCCH is taken as the 0th time unit, then the corresponding K0 can be 0, 0, 1, 1, 2 or 2, and so on. This application does not limit this.

[0096] Figure 8 An example diagram of one embodiment of the present application is shown.

[0097] In this embodiment, the time unit used for transmitting control information is shorter than the time unit used for transmitting data, such as... Figure 8 As shown, the first time unit of carrier 1 is used to schedule the PDCCH, and the time unit of carrier 2 can be used to schedule the corresponding PDSCH. Figure 5 In this context, the two time units used to schedule PDCCH are aligned with the time units that can be used to schedule PDSCH.

[0098] In one embodiment of this application, timing is determined using a long time unit as the basis for determining the timing sequence.

[0099] In this application, PDCCH is used for downlink scheduling, and PDSCH is used for corresponding downlink data transmission. The time relationship between the time unit used for PDCCH transmission and the time unit used for PDSCH transmission is K0. If a longer time unit is used as the base time unit, then based on the time interval between the time unit used for PDCCH transmission and the time unit that can be used for PDSCH transmission (time unit A in the figure), which is no more than one longer time unit away from the time unit used for PDCCH transmission, K0 is 0. Then K0 for the next time unit is 1, and so on, with the value of K0 increasing by 1 each time.

[0100] Alternatively, the K0 of the time unit used for transmitting PDSCH is set to 0, which is no more than one long time unit away from the time unit used for transmitting PDCCH. That is, the K0 of the first time unit after time unit A is 0, the K0 of the subsequent time units is 1, and so on, with the value of K0 increasing by 1 in turn.

[0101] Figure 9 An example diagram of one embodiment of the present application is shown.

[0102] Figure 9 and Figure 8The difference lies in the position of the time unit used for PDCCH transmission, which is already located after the time unit A used by carrier 2 (assuming M short time units are aligned with 1 long time unit (time unit A), and the time unit used for PDCCH transmission is the i-th of the M short time units, i>1). In this case, if the timing is determined based on the long time unit, then the K0 of the time unit used for PDSCH that is no more than one long time unit away from the time unit used for PDCCH transmission can be denoted as 0, i.e. Figure 9 In the middle time unit, K0 for the first time unit after time unit A is recorded as 0, and K0 for subsequent time units is incremented by 1, and so on. In this embodiment, K0 for the time unit that may be used to transmit PDSCH can be 0 or 1.

[0103] Alternatively, a time unit based on a longer time period. Figure 9 If the time interval between time unit A and the time unit used for PDCCH transmission does not exceed one long time unit, then K0 of A is recorded as 1. The K0 of subsequent time units is incremented by 1, and so on. In this embodiment, K0 of the time unit used for PDSCH transmission can be 0, 1, or 2.

[0104] This application also provides an embodiment in which the time unit used for transmitting control information is different in length from the time unit used for transmitting data. In this embodiment, the transmission control information is PDCCH, which can be used to send downlink scheduling information, which is used for uplink scheduling, such as DCI information. The data transmission is PUSCH, which is used for corresponding uplink data transmission. The interval between the time unit used for uplink scheduling and the time unit used for corresponding uplink and downlink data transmission can still be recorded as timing K2. Therefore, the timing can be determined by using a short time unit or a long time unit as the time unit, as described in the above embodiment.

[0105] This application also provides an embodiment in which the time unit used for transmitting control information is different in length from the time unit used for transmitting data. In this embodiment, the data channel is PDSCH, used to transmit downlink data, and the control information can be acknowledgment information fed back to the downlink data, such as acknowledgment (ACK) information or negative-acknowledgment (NACK) information corresponding to the downlink data, transmitted through PUSCH or PUCCH. The time relationship between the time units used for transmitting control information and those used for transmitting downlink data can be denoted as K1. The timing can then be determined using either a shorter or longer time unit as the time unit, as described in the above embodiment. This will be explained below with reference to the figures.

[0106] Figure 10 An example diagram of an embodiment of this application is shown.

[0107] In this embodiment, PDSCH is used to transmit downlink data, and PUSCH or PUCCH is used to transmit control information. The time unit used for transmitting data is longer than the time unit used for transmitting control information. Figure 10 As shown, the time unit used for data transmission is aligned with two time units used for control information transmission. In this embodiment, timing K1 is determined based on the shortest time unit, which is the time unit used for transmitting control information.

[0108] Optionally, if the distance between the first time unit used by the scheduled PUSCH or PUCCH and the time unit for transmitting data is less than 1, then K1 of the first time unit is 1, and subsequently incremented by 1.

[0109] Optionally, if the distance between the second time unit used by the scheduled PUSCH or PUCCH and the time unit for transmitting data is less than 1, then K1 of the first time unit is 1, and subsequently incremented by 1.

[0110] Figure 11 An example diagram of an embodiment of this application is shown.

[0111] In this embodiment, PDSCH is used to transmit downlink data, and PUSCH or PUCCH is used to transmit control information. The time unit used for transmitting data is shorter than the time unit used for transmitting control information. Specifically, as shown... Figure 11 As shown, the two time units used for data transmission are aligned with the time unit used for control information transmission. In this embodiment, timing K1 is determined based on the shorter time unit. In this embodiment, the shorter time unit is the time unit used for data transmission.

[0112] like Figure 11 As shown, the first time unit used by a potentially scheduled PUSCH or PUCCH has a K1 of 0, and subsequent units are incremented by 2.

[0113] Figure 12 An example diagram of an embodiment of this application is shown.

[0114] Figure 12 and Figure 11 The difference lies in the fact that the time unit used for transmitting downlink data is already at the end of the time unit A used by carrier 2. At this point, if the timing is determined based on the shorter time unit, then the timing K1 of time unit A can be 0, the timing K1 of the first time unit after unit A is 1, and so on, incrementing by 2 for subsequent units.

[0115] Alternatively, the timing K1 of the first time unit after time unit A is 0, and it is incremented by 2 for each subsequent time unit, and so on.

[0116] Figure 13 An example diagram of an embodiment of this application is shown.

[0117] In this embodiment, PDSCH is used to transmit downlink data, and PUSCH or PUCCH is used to transmit control information. The time unit used for data transmission is shorter than the time unit used for control information transmission. Conversely, the time unit used for data transmission is longer than the time unit used for control information transmission. Figure 13 As shown, the time unit used for transmitting data is aligned with two time units used for transmitting control information.

[0118] In this embodiment, timing K1 is determined based on a long time unit. In this embodiment, the long time unit is the time unit used for data transmission. If the interval between the first and second time units for transmitting PUSCH or PUCCH and the time unit used for transmitting downlink data is less than one long time unit, then K1 for the first and second time units is 1. If the interval between the third time unit and the time unit used for transmitting downlink data is one long time unit, and the interval between the fourth time unit and the time unit used for transmitting downlink data is less than two long time units, then K1 for the third and fourth time units is 2, and so on.

[0119] Figure 14 An example diagram of one embodiment of the present application is shown.

[0120] In this embodiment, PDSCH is used to transmit downlink data, and PUSCH or PUCCH is used to transmit control information. The time unit used for transmitting data is shorter than the time unit used for transmitting control information. Specifically, as shown... Figure 11 As shown, the two time units used for data transmission are aligned with the time unit used for control information transmission. This embodiment uses a longer time unit as the base time unit, that is, the time unit used for transmitting control information is used as the base time unit.

[0121] Optionally, the interval between time unit A and the time unit for transmitting PDSCH is less than a long time interval. K1 of A can be 0, and K1 of subsequent time units is incremented by 1, and so on.

[0122] Alternatively, K1 is 0 for the first time unit after time unit A, and K1 is incremented by 1 for subsequent time units, and so on.

[0123] Figure 15 An example diagram of one embodiment of the present application is shown.

[0124] Figure 15 and Figure 14 The difference is that the time unit used to transmit downlink data is already at the end of the time unit A used by carrier 2. At this time, the timing is determined based on the long time unit.

[0125] Since the distance between the first time unit after time unit A and the time unit for transmitting PDSCH is less than one long time unit, K1 is set to 0 for the first time unit after A, and then K1 is incremented by 1 sequentially.

[0126] Alternatively, start with K1 as 0 in time unit A, and then increment K1 by 1 sequentially.

[0127] This application also provides an embodiment that determines timing based on the target time unit. For example, for K0 (the time relationship between PDCCH and PDSCH), the time unit for transmitting PDSCH is used as the timing criterion or timing unit; for K2 (the time relationship between PDCCH and PUSCH), the time unit for transmitting PUSCH is used as the timing criterion or timing unit; for K1 (the time relationship between PDSCH and PUSCH / PUCCH), the time unit for transmitting PUSCH / PUCCH is used as the timing criterion or timing unit; that is, in Figures 4-9 In the embodiments, the time unit is based on the time unit used for transmitting PDSCH, in Figure 10-15 In some embodiments, the time unit is based on the time unit used for transmitting PUSCH or PUCCH.

[0128] This application also provides an embodiment for determining timing based on source time units. For example, for K0 (the time relationship between PDCCH and PDSCH), the time unit for transmitting PDCCH is used as the timing criterion or timing unit; for K2 (the time relationship between PDCCH and PUSCH), the time unit for transmitting PDCCH is used as the timing criterion or timing unit; for K1 (the time relationship between PDSCH and PUSCH / PUCCH), the time unit for transmitting PDSCH is used as the timing criterion or timing unit; that is, in Figures 4-9 In the embodiments, the time unit is based on the time unit used for transmitting PDCCH, in Figure 10-15 In the embodiments, the time unit is based on the time unit used for transmitting PDSCH.

[0129] This application also provides an embodiment that determines timing based on the time unit of data transmission. For example, for K0 (the time relationship between PDCCH and PDSCH), the time unit of PDSCH transmission is used as the timing criterion or timing unit; for K1 (the time relationship between PDSCH and its corresponding PUSCH or PUCCH), the time unit of PDSCH transmission is used as the timing criterion or timing unit; that is, in Figures 4-9 In this embodiment, the time unit is based on the time unit used for transmitting the PDSCH. For cases where the time unit used for transmitting the control channel PDCCH is less than the time unit used for transmitting the data channel PDSCH: using the data channel time unit (longer time unit) for timing incurs less indication overhead than using the control channel time unit (shorter time unit) because, assuming M short time units and 1 long time unit are aligned, the interval K0 values ​​between the M short time units and the same long time unit are all equal (Note: if short time units are used for timing, the K0 values ​​are not equal; assuming the first short time unit is spaced apart from a certain long time unit). If K0 = x short time units, then the interval between the second short time unit and the long time unit is K0 = x + 1 short time units, and the interval between the Mth short time unit and the long time unit is K0 = x + M short time units. Therefore, the required size of the K0 set (and the number of DCI indicator bits required later in the text) is larger. Furthermore, the K0 value is smaller compared to the timing value using the control channel time unit (shorter time units), and its value fluctuation is smaller for a given absolute time range (therefore, the size of the K0 set is smaller, and the number of DCI indicator bits is less). If the time unit used for transmitting the control channel PDCCH is greater than the time unit used for transmitting the data channel PDSCH, using the data channel time unit (shorter time units) for timing has a smaller scheduling delay than using the control channel time unit (longer time units). For example, if both K0 = 2, then using the data channel time unit results in a scheduling delay of 2 short time units, while using the control channel time unit results in a scheduling delay of 2 long time units. Furthermore, using the same timing criterion for K1 as for K0 simplifies system design. Timing based on the time unit of data transmission can be understood as determining the time relationship by replacing, or understanding as, the time unit used for transmitting PDCCH with, the time unit used for transmitting PDSCH. Furthermore, for K2 (the time relationship between PDCCH and PUSCH), the time unit for transmitting PUSCH is used as the timing criterion or timing unit; in Figure 10-15 In the embodiments, the time unit is based on the time unit used for transmitting PUSCH.

[0130] The above embodiments of this application illustrate a method for determining timing. The communication process regarding timing between the base station and the terminal will be described later in this application. For details on timing determination and other related matters, please refer to the descriptions in the above embodiments.

[0131] like Figure 16 As shown, this application presents a flowchart of an embodiment.

[0132] S1601. The base station sends multiple sets to the UE, where each set includes different values ​​of the timing sequence.

[0133] Optionally, the multiple sets include one set K0, one set K1, and one set K2; or the multiple sets include at least two sets K0, and / or at least two sets K1, and / or at least two sets K2.

[0134] In one example, the plurality of sets may include a set of K0 (referred to as the K0 set), which can be {1,2}. The plurality of sets may also include a set of K1 (referred to as the K1 set), which can be {3,4}. The plurality of sets may also include a set of K2 (referred to as the K2 set), which can be {5,6}.

[0135] The base station can send the aforementioned sets to the UE via higher-layer signaling, such as through RRC signaling. This can be done through radio resource control (RRC) configuration, or through master information block (MIB) messages, system information block (SIB) messages, or radio resource control (RRC) signaling, or media access control element (MAC CE) signaling. Different sets can correspond to different time units, subcarrier intervals, or both.

[0136] Alternatively, different sets can correspond to different time unit intervals or different subcarrier intervals.

[0137] Alternatively, different sets can correspond to different subcarrier spacing pairs, or different sets can correspond to different time unit pairs. For example, (15kHz, 60kHz) corresponds to set 1 of K1, and (15kHz, 120kHz) corresponds to set 2 of K1.

[0138] S1602, The base station transmits the correspondence between at least one of the time units and subcarrier intervals and the set to the UE.

[0139] Optionally, the relationship can be the correspondence between the subcarrier spacing of 15 kHz and set 1, or the correspondence between the 7 symbols of the time unit and set 1, or the correspondence between the subcarrier spacing of 15 kHz and the 7 symbols of the time unit and set 1.

[0140] The correspondence can be: different sets corresponding to different time units, or subcarrier intervals, or both. Alternatively, different sets can correspond to different time unit intervals, or different subcarrier intervals. Or, different subcarrier interval / time unit length pairs can correspond to different timing sets. For example, K1 set set1 is configured for 15k_to_30k, and K1 set1 is configured for 30k_to_15k. When the PDSCH is 15k and the decoding result is fed back on the PUSCH / PUCCH at 30k, the K1 value indicated in the DCI comes from set set1; similarly, when the PDSCH is 30k and the decoding result is fed back on the PUSCH / PUCCH at 15k, the K1 value indicated in the DCI comes from set set2.

[0141] The base station can send multiple of the above-mentioned correspondences to the UE. The base station can send the above-mentioned correspondences to the UE via higher-layer signaling.

[0142] Therefore, different subcarrier intervals or time units correspond to different processing delays, which can save DCI signaling overhead.

[0143] S1603. The base station sends DCI information to the UE. The DCI includes information used to indicate timing values.

[0144] Optionally, for downlink data scheduling (DCI), it includes a first indication field for indicating the value of K0 and a second indication field for indicating the value of K1.

[0145] For uplink data scheduling (DCI), it includes a third indication field for indicating the value of K2.

[0146] As an example, the above value information indicates which value in the set. For instance, if the set K0 is {2,4,5,6}, and the first indicator field indicates a value of 2, it means that K0 is the second value in the set, i.e., K0 = 4.

[0147] As one implementation, the number of bits in the first indicator field, the second indicator field, and the third indicator field are equal, for example, all 2 bits. This ensures that the three fields have the same flexibility, i.e., the same set size.

[0148] As another implementation, the sum of the number of bits in the first indicator field and the number of bits in the second indicator field is equal to the number of bits in the third indicator field. For example, the number of bits in the first indicator field is 1, the number of bits in the second indicator field is 1, and the number of bits in the third indicator field is 2. This ensures that the overhead or size of the uplink DCI and the downlink DCI are similar or the same.

[0149] Optionally, the solution in S1603 may not be combined with S1601 and S1602, and this application does not limit this.

[0150] For different UEs, with different subcarrier spacings, number of symbols, and time units, the required minimum K1 and K2 are different. For example, for a certain UE, if the time unit is 15k slots, its K1 can be 1, but if the time unit is 60k slots, its K1 must be at least 4. For example, the set required for 15k slots is {1,2}, and the set required for 60k slots is {4,5}.

[0151] If only one set is configured, {1,2,4,5} needs to be configured, and the timing domain in the DCI requires 2 bits. However, this scheme uses two sets, so the timing domain in the DCI only requires 1 bit. Therefore, the scheme based on this application can reduce the DCI overhead.

[0152] S1604. The UE determines the timing based on the correspondence between at least one of the subcarrier intervals and time units and the set, as well as the information in the DCI information used to indicate the timing value.

[0153] Since multiple K1 sets may be configured, the UE needs to determine which set to use and then determine the specific K1 value based on the indication information in the second indication field of the DCI. Specifically, the UE determines which set to use based on the currently configured subcarrier spacing (or time unit) and the correspondence between the subcarrier spacing (or time unit) in S1601 and multiple sets.

[0154] The following example uses K1; K0 and K2 are similar and will not be repeated.

[0155] If a subcarrier interval (or time unit length) value corresponds to a K1 set, for example, 15kHz (or 1ms) corresponds to K1 set 1; 60kHz (or 0.25ms) corresponds to K1 set 2, then as one implementation, the UE determines the K1 set based on the PDSCH subcarrier interval (or time unit length) value. For example, if the PDSCH subcarrier interval is 15kHz, then K1 set 1 is used. Then, the final value of K1 is determined based on the indication information in the second indication field of the DCI and K1 set 1.

[0156] As another implementation, the UE determines the K1 set based on the subcarrier spacing (or time unit length) value of the PUSCH / PUCCH. For example, if the PUSCH / PUCCH subcarrier spacing is 60kHz, then K1 set 2 is used. The final value of K1 is then determined based on the indication information in the second indication field of the DCI and K1 set 2.

[0157] If a subcarrier interval (or time unit length) corresponds to a K1 set, for example, 15kHz to 60kHz (or 0.25ms to 1ms) corresponds to K1 set 1; 120 to 240kHz corresponds to K1 set 2, then as one implementation method, the UE determines the K1 set based on the subcarrier interval (or time unit length) value of the PDSCH. For example, if the subcarrier interval of the PDSCH is 15kHz, then K1 set 1 is selected. Then, the final value of K1 is determined based on the indication information in the second indication field of the DCI and K1 set 1.

[0158] As another implementation method, the UE determines the K1 set based on the subcarrier spacing (or time unit length) value of PUSCH / PUCCH. For example, if the subcarrier spacing of PUSCH / PUCCH is 60kHz, then K1 set 1 is determined to be used. Then, the final value of K1 is determined based on the indication information of the second indication field in DCI and K1 set 1.

[0159] A K1 set is defined as follows: a subcarrier spacing pair or subcarrier spacing interval pair (or time unit length pair or time unit length interval pair) corresponds to a K1 set. For example, (15kHz, 60kHz) corresponds to K1 set 1; (15kHz, 120kHz) corresponds to K1 set 2. In one implementation, the UE determines the K1 set based on the subcarrier spacing (or time unit length) values ​​of the PDSCH and the PUSCH / PUCCH. For example, if the PDSCH subcarrier spacing is 15kHz and the PUSCH / PUCCH subcarrier spacing is 60kHz, then K1 set 1 is used. The final K1 value is then determined based on the indication information in the second indication field of the DCI and K1 set 1. Similarly, if the PDSCH subcarrier spacing is 15kHz and the PUSCH / PUCCH subcarrier spacing is 120kHz, then K1 set 1 is used. The final K1 value is then determined based on the indication information in the second indication field of the DCI and K1 set 2.

[0160] For example, the base station carries scheduling information via carrier 1 and transmits the corresponding data via carrier 2. The carrier spacing of carrier 2 is 15 kHz. The number of time units between the time units used for scheduling information and the time units used for data transmission is set 1, which can include multiple different values, such as {1, 2}. If the carrier spacing of carrier 2 is 30 kHz, the number of time units between the time units used for scheduling information and the time units used for data transmission is set 2, which can include multiple different values, such as {3, 4}. The base station can send the correspondence between set 1 and 15 kHz, and set 2 and 30 kHz to the UE. Further, the base station sends an indication message to the UE. This indication message indicates the number of time units between the time units used for scheduling information and the time units used for data transmission. This indication message can be included in downlink scheduling information, such as DCI. If the indication message indicates the second value, the UE will determine the value based on the carrier spacing of carrier 2 being 15 kHz. HZ, determine set 1, the second value is 2 in set 1, that is, the number of time units between the time unit used by the scheduling information and the time unit used by the data information is 2.

[0161] For example, the base station carries scheduling information through carrier 1 and transmits the corresponding data through carrier 2. Considering the UE's capabilities, for a certain UE, if the carrier spacing of carrier 2 is 15 kHz and the length of the time unit is 14 symbols, then the number of time units between the time units used by the scheduling information and the time units used by the data information can be 1. If the carrier spacing of carrier 2 is 60 kHz and the length of the time unit is 7 symbols, then the number of time units between the time units used by the scheduling information and the time units used by the data information is at least 4. The base station can send set 1 and set 2, along with the carrier interval and time unit length, and the correspondence between each set to the UE. For example, set 1 is {1, 2}, corresponding to a carrier interval of 15 kHz and a time unit length of 14 symbols; set 2 is {4, 5}, corresponding to a carrier interval of 60 kHz and a time unit length of 7 symbols. Further, the base station sends indication information to the UE, which indicates the number of time units between the time unit used for scheduling information and the time unit used for data transmission. If the carrier interval of carrier 2, which performs the corresponding data transmission, is 15 kHz and the time unit length is 14 symbols, then the UE determines set 1 based on the carrier interval of 15 kHz and the time unit length of 14 symbols used for data transmission, and determines the number of time units between the time unit used for scheduling information and the time unit used for data transmission to be 2 based on the second value indicated in the indication information.

[0162] For example, the base station transmits data via carrier 1, and the UE sends back confirmation information (i.e., the decoding result) via carrier 2. If the carrier spacing of carrier 1 is 15 kHz and the carrier spacing of carrier 2 is 30 kHz, and the 15 kHz carrier is scheduled to be a 30 kHz carrier, the base station configures set 1, which consists of {1, 2}. If the carrier spacing of carrier 1 is 30 kHz and the carrier spacing of carrier 2 is 15 kHz, the base station configures set 2, which consists of {3, 4}. The base station sends set 1 and set 2 to the user equipment. Further, the base station sends indication information to the UE. Based on the carrier spacing of the carrier used for data transmission being 15 kHz and the carrier spacing of the carrier used for sending back confirmation information being 30 kHz, the UE determines set 1. Based on the second value indicated in the indication information, the UE determines 2 in set 1, that is, the number of time units between the time unit used for sending back confirmation information and the time unit used for data transmission is determined to be 2.

[0163] Therefore, by sending multiple sets corresponding to different subcarrier intervals or time units and notifying the DCI to indicate the timing values, flexible scheduling under different subcarrier intervals or time units can be achieved, reducing signaling overhead.

[0164] This application provides an embodiment relating to cross-carrier scheduling with different time unit lengths.

[0165] Figure 17 An example diagram of an implementation of this application is shown.

[0166] like Figure 17 In the illustrated embodiment, the base station configures multiple carriers for the UE, such as... Figure 16 Carrier 1 and carrier 2 are used in the data. Carrier 1 can schedule the PDSCH or PUSCH of carrier 2 across carriers. The time unit used by carrier 1 is shorter than the time unit used by carrier 2.

[0167] If carrier 1 and carrier 2 have the same time unit, and K2 = 2 and K4 = 2, then 4 processes are required to ensure continuous transmission.

[0168] When the time unit used by carrier 1 is less than the time unit used by carrier 2, the short time unit schedules the long time unit, and K2+K4 processes can guarantee continuous transmission.

[0169] Figure 18 An example diagram of one embodiment of this application is shown.

[0170] like Figure 18 In the illustrated embodiment, carrier 1 schedules the PDSCH or PUCCH of carrier 2 across carriers. The time unit used by carrier 1 is one-quarter of the time unit used by carrier 2.

[0171] If carrier 1 and carrier 2 have the same time unit, and K2 = 4 and K4 = 4, then 8 processes are required to ensure continuous transmission.

[0172] When the time unit used by carrier 2 is four times that used by carrier 1, M-1+K2+K4 processes are needed to ensure continuous transmission, where M is the ratio of the long time unit to the short time unit.

[0173] Therefore, this application proposes a scheme in which the length of the time unit for transmitting PDCCH is no greater than the length of the time unit for transmitting PUSCH or PDSCH, in order to avoid increasing the number of processes required to ensure continuous transmission.

[0174] In one embodiment of this application, if the PDCCH and either the PUSCH or PDSCH are configured on the same time slot, the subcarrier spacing for transmitting the PDCCH is not less than the subcarrier spacing for transmitting the PUSCH or PDSCH. That is, when the number of slots or symbols is the same, the subcarrier spacing is limited; for example, the subcarrier spacing for transmitting the PDCCH is not less than the subcarrier spacing for transmitting the PUSCH or PDSCH.

[0175] Specifically, as shown in the table below.

[0176] 240k 15k, 30k, 60k, 120k, 240k 120k 15k, 30k, 60k, 120k 60k 15k, 30k, 60k 30k 15k, 30k 15k 15k

[0177] In one embodiment of this application, if the PDCCH is configured with a subcarrier spacing of 60kHz and a time unit of 1 slot, then the configuration of the PUSCH or PDSCH must ensure that its time unit length is not less than the time unit length of the PDCCH. For example, the subcarrier spacing can be 15kHz, 30kHz, 60kHz, or 120kHz, and the time unit is 2 slots. That is, if the number of slots or symbols is different, the subcarrier spacing, the number of slots, or the number of symbols can be considered together. At least one of the number of symbols or the number of slots, along with the subcarrier spacing, can determine the time unit length.

[0178] As shown in the table below,

[0179]

[0180] In one embodiment provided in this application, the length of the time unit for transmitting PDCCH can be greater than the length of the time unit for transmitting PUSCH or PDSCH. To avoid an excessive increase in the number of processes ensuring continuous transmission, the length of the time unit for transmitting PDCCH is configured to be greater than the length of the time unit for transmitting PUSCH or PDSCH, and the length of the time unit for transmitting PUSCH or PDSCH is greater than 1 / X the length of the time unit in which PDCCH is transmitted, where X is a positive integer, and optionally, X can be 2 or 4.

[0181] If X=2, and PDCCH and PUSCH or PDSCH are configured on one slot, then if the subcarrier spacing of PDCCH is 60kHz, the subcarrier spacing of PUSCH or PDSCH is no greater than 120kHz.

[0182] As shown in the table below,

[0183] 240k 15k, 30k, 60k, 120k, 240k 120k 15k, 30k, 60k, 120k, 240k 60k 15k, 30k, 60k, 120k 30k 15k, 30k, 60k 15k 15k, 30k

[0184] Alternatively, if X = 2, and the PDCCH is configured on a 60k slot, then the PUSCH / PDSCH is configured with a time unit length no greater than the time unit length of the PDCCH. For example, the subcarrier spacing can be 15k, 30k, 60k, 120k, or 240k slots. That is, if the number of slots and the number of symbols are different, the time unit length is determined by combining the number of symbols or the number of slots and the subcarrier spacing.

[0185] As shown in the table below,

[0186]

[0187] Furthermore, the value of M is related to the UE's capabilities and the maximum number of processes supported by the system or the UE. In one example of this application, the configuration of M must meet the following condition: the value of K2+K4 (where K2+K4 is the number of processes required when the time unit length is the same)+M-1 is not greater than the maximum number of processes supported by the system (or the UE). If the maximum number of processes is 16, and K2+K4 = 8, then M is not greater than 9.

[0188] For UEs supporting smaller K2 and K4 values, it's not necessary to support PDCCH transmission time units longer than PUSCH or PDSCH transmission time units, or M can be kept as small as possible, ideally 2. This is primarily based on the consideration that "idle rate = (M-1) / (K2+K4+M-1)". Specifically, assuming K2=1 and K4=1, if M=4, the idle rate is 3 / 5=60%, while if K2=4 and K4=4, if M=4, the idle rate is 3 / 11=27%.

[0189] This application provides an embodiment related to scheduling. The base station configures a PDCCH and a corresponding PDSCH or PUSCH, where X > the ratio of PDCCH to PDSCH / PUSCH (this ratio can be a time unit length ratio or a subcarrier spacing ratio) > 1 / Y, where X and Y are positive integers, optional, where X, Y = 2 or 4; or the base station configures a PDCCH and a corresponding PDSCH or PUSCH, where the subcarrier spacing of the PDCCH and the corresponding PDSCH or PUSCH is the subcarrier spacing supported by the UE, for example, the UE supports 15kHz, 60kHz, 120kHz. HZ, then the PDCCH and the corresponding PDSCH or PUSCH are configured as adjacent combinations of 15 and 60 or adjacent combinations of 60 and 120; when the base station groups the carriers, at most one group of carriers has different subcarrier intervals or time lengths. For example, 10 carriers are divided into 4 groups, based on whether the subcarrier intervals or time unit lengths are the same, and the remaining different subcarrier intervals or time unit lengths are divided into 1 group; or, when the base station groups the carriers, at most two groups of carriers have different subcarrier intervals or time lengths.

[0190] This application provides an embodiment relating to HARQ feedback at different time unit lengths.

[0191] Figure 19 An example diagram of one embodiment provided in this application is shown.

[0192] like Figure 19 As shown, the base station has configured multiple carriers for the UE, such as... Figure 18 The carriers are carrier 1 and carrier 2, and the length of the time unit used by carrier 1 is 4 times the length of the time unit used by carrier 2.

[0193] As shown in Figure 19, data transmitted on a carrier with a long time unit is acknowledged on a carrier with a short time unit, such as an ACK message or a NACK message.

[0194] If the time unit lengths of carrier 1 and carrier 2 are the same, the required number of processes is K1 + K3 + K0. If K0 = 0, K1 = 2, and K3 = 2, the required number of processes is 4. However, if the time unit length of carrier 1 is greater than the time unit length of carrier 2, such as... Figure 19 As shown, it still requires 4 processes.

[0195] Figure 20 An example diagram of one embodiment of the present application is shown.

[0196] like Figure 20 As shown, the base station has configured multiple carriers for the UE, such as... Figure 19The carriers are carrier 1 and carrier 2, and the length of the time unit used by carrier 1 is 1 / 4 of the length of the time unit used by carrier 2.

[0197] like Figure 20 As shown, transmitting data on a carrier with a short time unit and sending back acknowledgment information on a carrier with a long time unit will result in an increase in the number of processes required to ensure continuous transmission.

[0198] If the time unit lengths of carrier 1 and carrier 2 are the same, then the required number of processes is K1 + K3 + K0. If K0 = 0, K1 = 4, and K3 = 4, then the required number of processes is 8.

[0199] If so Figure 20 As shown, the length of the time unit used by carrier 1 is 1 / 4 of the length of the time unit used by carrier 2, and the required process is K1+K3+K0+2M-2, which is 16. M is the ratio of the long time unit to the short time unit, which is 4 here.

[0200] Therefore, one proposed solution in this application is to configure the time unit length for transmitting PDSCH to be no less than the time unit length for transmitting PUSCH or PUCCH.

[0201] In one example provided in this application, if the time unit for transmitting PDSCH and PUSCH or PUCCH is configured to be one slot, then the subcarrier spacing must meet the following condition: if the subcarrier spacing of PDSCH is 30k, then the subcarrier spacing of PUSCH or PDSCH must be greater than or equal to 30k, such as 30k, 60k, 120k, or 240k. (If the number of slots and the number of symbols are the same, only the subcarrier spacing is considered; they together determine the length of the time unit. More examples are shown in the table below.)

[0202] For details, please see the table below:

[0203] 240k 240k 120k 120k, 240k 60k 60k, 120k, 240k 30k 30k, 60k, 120k, 240k 15k 15k, 30k, 60k, 120k, 240k

[0204] In one example provided in this application, if the PDCCH is configured on a 60kHz slot, the configuration of the PUSCH or PUCCH must satisfy the condition that its time unit length is less than or equal to the time unit length of the PDCCH. For example, the subcarrier spacing can be 60kHz, 120kHz, or 240kHz. (If the number of slots and symbols differ, the time unit length is determined by combining the number of symbols or slots and the subcarrier spacing.)

[0205] For details, please see the table below:

[0206]

[0207]

[0208] Optionally, this application proposes that the length of the time unit for transmitting PDSCH can be configured to be shorter than the time unit for transmitting PUSCH or PUCCH, and the length of the time unit for PDSCH is greater than 1 / X and the length of the time unit for transmitting PUSCH or PUCCH, where X is a positive integer. Further, X = 2 or 4.

[0209] When X=2, if PDSCH and PUSCH or PUCCH are both configured to be carried in slot 14, the subcarrier spacing must meet the following condition: if the subcarrier spacing of PDSCH is 30k, then the subcarrier spacing of PUSCH / PUCCH must be greater than or equal to 30k, such as 15k, 30k, 60k, 120k or 240k.

[0210] Specifically, see the table below:

[0211]

[0212] Furthermore, the selection of M is related to the capabilities of the UE (the values ​​of K1 and K3) and the maximum number of processes supported by the system or the UE.

[0213] Optionally, if M needs to satisfy: the value of K1+K3 (the number of processes required when the time units are the same)+2M-2 is not greater than the maximum number of processes supported by the system (or the maximum number of processes supported by the UE), the maximum number of processes supported by the system or the UE can be 16. If K1+K3=8, then M is not greater than 5.

[0214] Alternatively, for UEs that support smaller K1 and K3 values, the time unit length of PDSCH should not be shorter than the time unit length of PUSCH / PUCCH, or M should be as small as possible, such as 2. This is based on the consideration that "idle rate = (2M-2) / (K1+K3+2M-2)". Specifically, assuming K1=1 and K3=1, if M=4, the idle rate is 6 / 8=75%, while if K1=4 and K3=4, if M=4, the idle rate is 6 / 16=37.5%.

[0215] It should be noted that M above is the ratio of the length of the long time unit to the length of the short time unit (or the ratio of the length of the PUSCH or PUCCH and the length of the PDSCH time unit).

[0216] In 5G, since there may be two PUCCH time divisions for the same UE within one time unit, M can be divided by 2 for cases with two PUCCH time divisions. In 5G, the number of symbols in one slot may also be 7 or 14 symbols, while under extended CP it is 6 or 12 symbols.

[0217] This application provides an embodiment related to feedback. The base station configures PDSCH and the corresponding PUCCH or PUSCH, where X > PDSCH / PUCCH / PUSCH ratio (this ratio is the time unit length ratio or subcarrier spacing ratio) > 1 / Y, and X and Y are positive integers, optional, X, Y = 2 or 4; the base station configures PDSCH and the corresponding PUCCH or PUSCH, and the subcarrier spacing of PDSCH and the corresponding PUCCH or PUSCH is the adjacent subcarrier spacing supported by the UE. For example, if the UE supports 15k, 60k, and 120k, then the adjacent 15 and 60k combination or the adjacent 15 and 120k combination is configured, but the 15 and 120k combination cannot be configured; when the base station groups carriers, at most one group has different subcarrier spacing or time unit lengths. For example, 10 carriers are divided into 4 groups, grouped according to whether the subcarrier spacing or time unit length is the same, and the remaining different subcarrier spacing or time unit lengths constitute one group; when the base station groups carriers, each group has at most 2 carriers with different subcarrier spacing or time unit lengths.

[0218] It should be noted that the numbering of symbol sequences in this application, such as "first," "second," etc., is only for clarity of description and does not constitute a limitation. Symbol sequences with the same number may be the same or different in different embodiments. It is understood that each network element, such as network-side equipment (e.g., a base station) or UE, includes corresponding hardware structures and / or software modules to perform the above functions. Those skilled in the art should readily recognize that the various examples described in conjunction with the embodiments disclosed herein can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0219] Figure 21 A possible structural diagram of the device involved in the above embodiments is shown. This device can be a network-side device, such as a base station, or a user equipment (UE). This device can perform the functions or steps described in the above embodiments.

[0220] In one specific example, the device includes a processor and a transmitter. In another specific example, the device may also include a receiver. In a specific example, when the device is a network-side device, the data transmitting device may further include a communication unit to support communication with other network-side devices, such as communication with core network nodes. In one possible example, it may also include a memory coupled to the processor to store necessary program instructions and data for the data transmitting device. The processor controls and manages the device's operations, executing the processes performed by the device in the above embodiments, such as controlling the device to process data transmission and / or performing other processes described in this application. Figure 21 In the corresponding example, the structure of the device involved in this application includes a transmitter 2101, a receiver 2102, a processor 2103, and a memory 2104.

[0221] Understandable, Figure 21 Only a simplified design of the device is shown. In practical applications, the device can include any number of transmitters, receivers, processors, memory, etc., and all data receiving devices that can implement this application are within the protection scope of this application.

[0222] This application also provides a device that implements the functions described in the above embodiments. These functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0223] The embodiments of this application can be referenced to each other, and the embodiments of this application can be executed by network devices and user devices accordingly.

[0224] The processor used to execute the device described in this application can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0225] The steps of the methods or algorithms described in conjunction with the disclosure of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a data receiving device and / or a data transmitting device. Alternatively, the processor and storage medium can exist as discrete components in the data receiving device and / or the data transmitting device.

[0226] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0227] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A wireless communication method, characterized in that, include: In the nth time unit, downlink control information (DCI) for scheduling downlink data is transmitted through the physical downlink control channel (PDCCH). The DCI includes a first indication field indicating the value of the first timing sequence K0 and a second indication field indicating the value of the second timing sequence K1. In the (n+K0+K1)th time unit, the uplink feedback information corresponding to the downlink data is received through the Physical Uplink Control Channel (PUCCH). The time unit used for transmitting the Physical Downlink Shared Channel (PDSCH) is the timing unit of the first timing sequence K0, and the time unit used for transmitting the PUCCH is the timing unit of the second timing sequence K1.

2. The method according to claim 1, characterized in that, The proportions of the first indicator field and the second indicator field are equal.

3. The method according to claim 1 or 2, characterized in that, The method further includes at least one of the following: Send a first set and the relationship between the first set and the time unit to the user equipment UE, wherein the first set includes at least one different value of K0; Send a second set and the relationship between the second set and the time unit to the UE, wherein the second set includes at least one different value of K1.

4. A wireless communication method, characterized in that, include: In the nth time unit, downlink control information (DCI) for scheduling downlink data is received through the physical downlink control channel (PDCCH). The DCI includes a first indication field indicating the value of the first timing sequence K0 and a second indication field indicating the value of the second timing sequence K1. In the (n+K0+K1)th time unit, the uplink feedback information corresponding to the downlink data is transmitted through the Physical Uplink Control Channel (PUCCH). The time unit used for transmitting the Physical Downlink Shared Channel (PDSCH) is the timing unit of the first timing sequence K0, and the time unit used for transmitting the PUCCH is the timing unit of the second timing sequence K1.

5. The method according to claim 4, characterized in that, The proportions of the first indicator field and the second indicator field are equal.

6. The method according to claim 4 or 5, characterized in that, The method further includes at least one of the following: Receive a first set and the relationship between the first set and the time unit to the user equipment UE, wherein the first set includes at least one different value of K0; The UE receives a second set and the relationship between the second set and the time unit, wherein the second set includes at least one different value of K1.

7. An apparatus, characterized in that, It includes a processor and a memory, the processor and the memory being coupled, the processor being used to implement the method as described in any one of claims 1 to 3.

8. An apparatus, characterized in that, It includes a processor and a memory, the processor and the memory being coupled, the processor being used to implement the method as described in any one of claims 4 to 6.

9. A computer-readable storage medium, characterized in that, Includes a program that, when run on a computer, causes the method as described in any one of claims 1 to 6 to be performed.

Images