Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, and relates to the technical field of wireless communication. The communication method comprises the following steps: user equipment (UE) reports UE capability information; wherein the UE capability information indicates a first UE processing time; the processing time of the first UE is shorter than the processing time of the second UE under the same SCS; the second UE processing time is a UE processing time under UE capability 2. According to the embodiment of the invention, lower transmission delay can be realized.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of wireless communication technologies, and in particular, to a communication method and apparatus. Background Art

[0002] With the development of communication technologies, people's requirements for communication performance are getting higher and higher. For example, the fifth-generation (5G) wireless communication - new radio access technology (NR) system or the communication system evolved from 5G is committed to supporting higher system performance, and will support multiple service types, different deployment scenarios, and a wider spectrum range. The main 5G service scenarios include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC).

[0003] To support the communication requirements in different scenarios, two user equipment (UE) processing capabilities (UE capability 1 and UE capability 2) are supported in the NR communication system to indicate the UE processing time under different subcarrier spacings (SCSs): UE PDSCH processing time and UE PUSCH preparation time. Among them, the UE processing time indicated by UE capability 2 is lower than that of UE capability 1, and UE capability 2 is used to support services with higher requirements for latency.

[0004] However, the current UE capability 2 in the NR communication system cannot meet the latency requirements of some services. For example, in the URLLC service scenario with a latency requirement of 0.1 ms - 0.2 ms, as the communication scenarios continue to increase, there may be new service scenarios in the future, such as precise industrial control, robot collaboration, and sensory interconnection, which have high requirements for latency, and the existing UE capability 2 in the NR communication system cannot meet them. Summary of the Invention

[0005] To solve the above technical problems, the present application provides a communication method and apparatus. The communication method is used to enable the UE to support information transmission with lower transmission latency.

[0006] In a first aspect, the present application provides a communication method, which can be executed by a terminal or a module (such as a chip) in the terminal. The method includes: reporting user equipment (UE) capability information; wherein, the UE capability information indicates a first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

[0007] The present application introduces a new UE capability with a processing time lower than that of capability 2, which is used to adapt to more low-latency service scenarios.

[0008] According to the first aspect, the first UE processing time includes a first physical downlink shared channel (PDSCH) processing time and / or a first physical uplink shared channel (PUSCH) preparation time; wherein, the first PDSCH processing time indicates a first quantity, and the first quantity is the minimum number of orthogonal frequency division multiplexing (OFDM) symbols in the interval from the end of the last symbol of receiving the PDSCH to the first uplink symbol of transmitting the physical uplink control channel (PUCCH) carrying the hybrid automatic repeat request-acknowledgment (HARQ-ACK) corresponding to the PDSCH by the UE; the first PUSCH preparation time indicates a second quantity, and the second quantity is the minimum number of OFDM symbols in the interval from the end of the last symbol of receiving the physical downlink control channel (PDCCH) carrying the downlink control information (DCI) scheduling the PUSCH to the first uplink symbol of transmitting the PUSCH by the UE.

[0009] In an embodiment of the present application, a new UE capability is defined: the first UE processing time. Under the same SCS, the first UE processing time is less than the second UE processing time. The second UE processing time is the UE processing time under UE capability 2. In this way, the processing time required for the terminal device to perform data transmission based on the first UE processing time is relatively shorter than that based on UE capability 2, thereby meeting the requirements of lower transmission latency.

[0010] According to the first aspect, or any one of the above implementation manners of the first aspect, under the same SCS, the first UE processing time is less than or equal to 1 / N times of the second UE processing time; wherein, N is a positive integer greater than 1.

[0011] According to the first aspect, or any one of the above implementation manners of the first aspect, N is equal to 4 or equal to 2.

[0012] According to the first aspect, or any one of the above implementation manners of the first aspect, when the SCS is 30 KHz: the number of OFDM symbols occupied by the first PDSCH processing time, that is, the first quantity, is less than or equal to 2; and / or, the number of OFDM symbols occupied by the first PUSCH preparation time, that is, the second quantity, is less than or equal to 2.

[0013] In the embodiment of the present application, when the SCS is 30KHz, the value range of the processing time of the first UE is provided. When the number of OFDM symbols occupied by the processing time of the first PDSCH is less than or equal to 2, the number of OFDM symbols occupied by the UE processing time is further reduced, so that while meeting the lower air interface delay constraint, it is further possible to increase the number of retransmissions under the same delay constraint, thereby improving the reliability of data transmission.

[0014] According to the first aspect, or any implementation manner of the above first aspect, when the SCS is 60KHz: the number of OFDM symbols occupied by the processing time of the first PDSCH, that is, the first quantity, is less than or equal to 5; and / or, the number of OFDM symbols occupied by the preparation time of the first PUSCH, that is, the second quantity, is less than or equal to 5.

[0015] According to the first aspect, or any implementation manner of the above first aspect, the method further includes: transmitting data based on the processing time of the first UE; wherein, the transmission of data includes one or more of the following manners: the scheduling manner of data includes semi-static scheduling SPS or grant-free GF scheduling; the time-domain resource occupied by the demodulation reference signal DMRS of the data is before the time-domain resource occupied by the data; the time-domain resource occupied by the data is less than or equal to 2 OFDM symbols.

[0016] In a second aspect, the present application provides a communication method, which can be executed by a terminal or a module (such as a chip) in the terminal. The method includes: reporting user equipment UE capability information; wherein, the UE capability information includes one or more of the first UE processing time, the second UE processing time, and the third UE processing time: under the same subcarrier spacing SCS, the third UE processing time is less than the second UE processing time; the second UE processing time is less than the first UE processing time.

[0017] According to the second aspect, the first UE processing time is the UE processing time under UE capability 1; the second UE processing time is the UE processing time under UE capability 2; the third UE processing time is the UE processing time under UE capability 3.

[0018] According to a second aspect, or any implementation manner of the above second aspect, the processing time of a third UE includes a first Physical Downlink Shared Channel (PDSCH) processing time and / or a first Physical Uplink Shared Channel (PUSCH) preparation time; wherein, the first PDSCH processing time indicates a first quantity, and the first quantity is the minimum number of Orthogonal Frequency Division Multiplexing (OFDM) symbols of the interval between the end of the last symbol of receiving the PDSCH by the UE and the first uplink symbol of transmitting a Physical Uplink Control Channel (PUCCH) carrying a Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK) corresponding to the PDSCH; the first PUSCH preparation time indicates a second quantity, and the second quantity is the minimum number of OFDM symbols of the interval between the end of the last symbol of receiving a Physical Downlink Control Channel (PDCCH) carrying Downlink Control Information (DCI) for scheduling the PUSCH by the UE and the first uplink symbol of transmitting the PUSCH.

[0019] According to a second aspect, or any implementation manner of the above second aspect, under the same Sub - Carrier Spacing (SCS), the processing time of the third UE is less than or equal to 1 / N times the processing time of the second UE; wherein, N is a positive integer greater than 1.

[0020] According to a second aspect, or any implementation manner of the above second aspect, N is equal to 4 or equal to 2.

[0021] According to a second aspect, or any implementation manner of the above second aspect, when the SCS is 30 KHz: the number of OFDM symbols occupied by the first PDSCH processing time, that is, the first quantity, is less than or equal to 2; and / or, the number of OFDM symbols occupied by the first PUSCH preparation time, that is, the second quantity, is less than or equal to 2.

[0022] According to a second aspect, or any implementation manner of the above second aspect, when the SCS is 60 KHz: the number of OFDM symbols occupied by the first PDSCH processing time, that is, the first quantity, is less than or equal to 5; and / or, the number of OFDM symbols occupied by the first PUSCH preparation time, that is, the second quantity, is less than or equal to 5.

[0023] According to a second aspect, or any implementation manner of the above second aspect, the method further includes: transmitting data based on the processing time of a first UE; wherein, the transmission of data includes one or more of the following manners: the scheduling manner of data includes Semi - Persistent Scheduling (SPS) or Grant - Free (GF) scheduling; the time - domain resource occupied by the Demodulation Reference Signal (DMRS) of the data is before the time - domain resource occupied by the data; the time - domain resource occupied by the data is less than or equal to 2 OFDM symbols.

[0024] According to a second aspect, or any implementation manner of the above second aspect, UE capability 1 is the user equipment UE capability 1 defined in the 3GPP technical specification, and UE capability 2 is the user equipment UE capability 2 defined in the 3GPP technical specification.

[0025] In a third aspect, the present application provides a communication method, which can be executed by a terminal or a module (such as a chip) in the terminal. The method includes: reporting user equipment UE capability information; where the UE capability information indicates a first UE processing time; under the same subcarrier spacing SCS, the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

[0026] According to the third aspect, the first UE processing time includes a first physical downlink shared channel PDSCH processing time and / or a first physical uplink shared channel PUSCH preparation time; where the first PDSCH processing time indicates a first quantity, and the first quantity is the minimum number of orthogonal frequency division multiplexing OFDM symbols in the interval between the end of the last symbol of receiving the PDSCH by the UE and the first uplink symbol of transmitting the physical uplink control channel PUCCH carrying the hybrid automatic repeat request-acknowledgment HARQ-ACK corresponding to the PDSCH; the first PUSCH preparation time indicates a second quantity, and the second quantity is the minimum number of OFDM symbols in the interval between the end of the last symbol of receiving the physical downlink control channel PDCCH carrying the downlink control information DCI for scheduling the PUSCH by the UE and the first uplink symbol of transmitting the PUSCH.

[0027] According to the third aspect, or any implementation manner of the above third aspect, under the same SCS, the first UE processing time is less than or equal to 1 / N times the second UE processing time; where N is a positive integer greater than 1.

[0028] According to the third aspect, or any implementation manner of the above third aspect, N is equal to 4 or equal to 2.

[0029] According to the third aspect, or any implementation manner of the above third aspect, when the SCS is 30 KHz:

[0030] The number of OFDM symbols occupied by the first PDSCH processing time, that is, the first quantity, is less than or equal to 2; and / or, the number of OFDM symbols occupied by the first PUSCH preparation time, that is, the second quantity, is less than or equal to 2.

[0031] According to a third aspect, or any implementation manner of the above third aspect, when the SCS is 60 KHz: the number of OFDM symbols occupied by the first PDSCH processing time, that is, the first number, is less than or equal to 5; and / or, the number of OFDM symbols occupied by the first PUSCH preparation time, that is, the second number, is less than or equal to 5.

[0032] According to a third aspect, or any implementation manner of the above third aspect, the method further includes: transmitting data based on the first UE processing time; wherein, the transmission of data includes one or more of the following manners: the data scheduling manner includes semi-static scheduling (SPS) or grant-free (GF) scheduling; the time-domain resource occupied by the data demodulation reference signal (DMRS) is before the time-domain resource occupied by the data; the time-domain resource occupied by the data is less than or equal to 2 OFDM symbols.

[0033] According to a third aspect, or any implementation manner of the above third aspect, the second UE processing time includes the second physical downlink shared channel (PDSCH) processing time and / or the second physical uplink shared channel (PUSCH) preparation time; when the SCS is 30 KHz:

[0034] the number of OFDM symbols occupied by the second PDSCH processing time is equal to 4.5; and / or, the number of OFDM symbols occupied by the second PUSCH preparation time is equal to 5.5.

[0035] According to a third aspect, or any implementation manner of the above third aspect, the second UE processing time includes the second physical downlink shared channel (PDSCH) processing time and / or the second physical uplink shared channel (PUSCH) preparation time; when the SCS is 60 KHz:

[0036] the number of OFDM symbols occupied by the second PDSCH processing time is equal to 9; and / or, the number of OFDM symbols occupied by the second PUSCH preparation time is equal to 11.

[0037] In a fourth aspect, the present application provides a communication method, which can be executed by a terminal or a module (such as a chip) in the terminal. The method includes: reporting user equipment (UE) capability information; wherein, the UE capability information is used to indicate multiple UE processing times of the UE; receiving first indication information; wherein, the first indication information is used to indicate the transmission period of data; determining a target UE processing time among the multiple UE processing times according to the transmission period of the data; and transmitting data based on the target UE processing time.

[0038] In the embodiments of the present application, for the scenario where the UE supports multiple UE processing times, the UE determines the UE processing time that matches the transmission period according to the transmission period of the data, achieving the effect of adaptively switching the UE capabilities, thereby further reducing the UE processing complexity and power consumption on the basis of ensuring the transmission delay.

[0039] According to the fourth aspect, one of the multiple UE processing times includes one PDSCH processing time and / or one PUSCH preparation time.

[0040] In the embodiments of the present application, one of the multiple UE processing times includes one PDSCH processing time and / or one PUSCH preparation time. That is to say, different UE processing times indicate different PDSCH processing times and / or PUSCH preparation times, so as to be applicable to different transmission periods.

[0041] According to the fourth aspect, or any implementation manner of the above fourth aspect, the multiple UE processing times include two or three of the first UE processing time, the second UE processing time, and the third UE processing time; wherein, the second UE processing time is less than the first UE processing time; the third UE processing time is less than the second UE processing time.

[0042] The embodiments of the present application are applicable to the scenario where the UE supports two or three of the first UE processing time, the second UE processing time, and the third UE processing time. Among them, the third UE processing time can be used to achieve a shorter transmission delay than the first UE processing time and the second UE processing time.

[0043] According to the fourth aspect, or any implementation manner of the above fourth aspect, determine the target UE processing time among the multiple UE processing times according to the transmission period of the data and the period threshold.

[0044] According to the fourth aspect, or any implementation manner of the above fourth aspect, the period threshold is predefined or configured.

[0045] In the embodiments of the present application, the period threshold can be predefined or configured. Among them, the configuration can be performed by the peer end.

[0046] According to the fourth aspect, or any implementation manner of the above fourth aspect, there is a mapping relationship among the transmission period of the data, the period threshold, and the multiple UE processing times.

[0047] According to the fourth aspect, or any implementation manner of the above fourth aspect, UE capability 2 is the user equipment UE capability 2 defined in the 3GPP technical specification; UE capability 1 is the user equipment UE capability 1 defined in the 3GPP technical specification.

[0048] Fifth aspect, the present application provides a communication method, which can be executed by a network device or a module (such as a chip) in the network device. The method includes: receiving user equipment (UE) capability information; wherein, the UE capability information indicates the processing time of a first UE; under the same subcarrier spacing (SCS), the processing time of the first UE is less than the processing time of a second UE; the processing time of the second UE is the UE processing time under UE capability 2.

[0049] The fifth aspect and any implementation manner of the fifth aspect respectively correspond to the first aspect and any implementation manner of the first aspect. For the technical effects corresponding to the fifth aspect and any implementation manner of the fifth aspect, reference can be made to the technical effects corresponding to the first aspect and any implementation manner of the first aspect described above, which will not be elaborated here.

[0050] Sixth aspect, the present application provides a communication method, which can be executed by a network device or a module (such as a chip) in the network device. The method includes: receiving user equipment (UE) capability information; sending a first indication information, where the first indication information is used to indicate the transmission period of data; sending a second indication information, where the second indication information is used to indicate a period threshold; wherein, there is a mapping relationship among the transmission period, the period threshold, and multiple UE capabilities.

[0051] The sixth aspect and any implementation manner of the sixth aspect respectively correspond to the fourth aspect and any implementation manner of the fourth aspect. For the technical effects corresponding to the sixth aspect and any implementation manner of the sixth aspect, reference can be made to the technical effects corresponding to the fourth aspect and any implementation manner of the fourth aspect described above, which will not be elaborated here.

[0052] Seventh aspect, an embodiment of the present application provides a communication device, which includes: an information reporting module, configured to report user equipment (UE) capability information; wherein, the UE capability information indicates the processing time of a first UE; under the same subcarrier spacing (SCS), the processing time of the first UE is less than the processing time of a second UE; the processing time of the second UE is the UE processing time under UE capability 2.

[0053] According to the seventh aspect, the first UE processing time includes the first physical downlink shared channel (PDSCH) processing time and / or the first physical uplink shared channel (PUSCH) preparation time; wherein, the first PDSCH processing time indicates a first quantity, and the first quantity is the minimum number of orthogonal frequency division multiplexing (OFDM) symbols of the interval between the end of the last symbol of receiving the PDSCH by the UE and the first uplink symbol of transmitting the physical uplink control channel (PUCCH) carrying the hybrid automatic repeat request-acknowledgment (HARQ-ACK) corresponding to the PDSCH; the first PUSCH preparation time indicates a second quantity, and the second quantity is the minimum number of OFDM symbols of the interval between the end of the last symbol of receiving the physical downlink control channel (PDCCH) carrying the downlink control information (DCI) scheduling the PUSCH by the UE and the first uplink symbol of transmitting the PUSCH.

[0054] According to the seventh aspect, or any implementation manner of the above seventh aspect, the apparatus further includes a data transmission module, configured to: transmit data based on the first UE processing time; wherein, the transmission of data includes one or more of the following manners: the scheduling manner of data includes semi-persistent scheduling (SPS) or grant-free (GF) scheduling; the time domain resource occupied by the demodulation reference signal (DMRS) of data is before the time domain resource occupied by the data; the time domain resource occupied by the data is less than or equal to 2 OFDM symbols.

[0055] For the seventh aspect, or any implementation manner of the above seventh aspect, reference may be made to the first aspect. The communication apparatus provided by the seventh aspect may be a terminal device, or a device, module, circuit, or chip configured to be disposed in the terminal device, or a device capable of being used in matching with the terminal device. In one design, the communication apparatus may include modules corresponding one by one to the methods / operations / steps / actions described in the first aspect, and the module may be a hardware circuit, software, or a combination of a hardware circuit and software. In one design, the communication apparatus may include a processing module and a communication module. Wherein, the sending module is configured to perform the sending action in the method described in the first aspect above, and the processing module is configured to perform the actions related to processing in the method described in the first aspect above.

[0056] In the eighth aspect, an embodiment of the present application provides a communication apparatus, including: an information reporting module, configured to report user equipment (UE) capability information; wherein, the UE capability information is used to indicate multiple UE processing times of the UE; an information receiving module, configured to receive first indication information; wherein, the first indication information is used to indicate the transmission period of data; a capability determination module, configured to determine a target UE processing time among the multiple UE processing times according to the transmission period of data; a data transmission module, configured to transmit data based on the target UE processing time.

[0057] In an eighth aspect, or any implementation of the above eighth aspect, reference may be made to the fourth aspect. The communication device provided in the eighth aspect may be a terminal device, or a device, module, circuit, or chip configured to be disposed in the terminal device, or a device that can be used in combination with the terminal device. In one design, the communication device may include modules corresponding one by one to the methods / operations / steps / actions described in the fourth aspect. The module may be a hardware circuit, software, or a combination of hardware circuit and software. In one design, the communication device may include a processing module and a communication module. Among them, the sending module is used to perform the sending actions in the method described in the fourth aspect above, and the processing module is used to perform the actions related to processing in the method described in the fourth aspect above.

[0058] In a ninth aspect, an embodiment of the present application provides a communication device, which includes: an information receiving module, configured to receive user equipment (UE) capability information; wherein the UE capability information indicates a first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

[0059] In a ninth aspect, or any implementation of the above ninth aspect, reference may be made to the fifth aspect above. The communication device provided in the ninth aspect may be a network device, or a device, module, circuit, or chip configured to be disposed in the network device, or a device that can be used in combination with the network device. In one design, the communication device may include modules corresponding one by one to the methods / operations / steps / actions described in the first aspect. The module may be a hardware circuit, software, or a combination of hardware circuit and software. In one design, the communication device may include a processing module and a communication module. Among them, the receiving module is used to perform the receiving actions in the method described in the fifth aspect above, and the processing module is used to perform the actions related to processing in the method described in the fifth aspect above.

[0060] In a tenth aspect, an embodiment of the present application provides a communication device, which includes: an information receiving module, configured to receive user equipment (UE) capability information; an information sending module, configured to send a first indication information, where the first indication information is used to indicate a transmission period of data; and send a second indication information, where the second indication information is used to indicate a period threshold; wherein there is a mapping relationship among the transmission period, the period threshold, and multiple UE capabilities.

[0061] In a tenth aspect, or any implementation of the tenth aspect above, reference may be made to the sixth aspect above. The communication device provided in the tenth aspect may be a network device, or a device, module, circuit, or chip configured to be disposed in a network device, or a device that can be used in combination with a network device. In one design, the communication device may include modules corresponding one by one to the methods / operations / steps / actions described in the fourth aspect. The module may be a hardware circuit, software, or a combination of a hardware circuit and software. In one design, the communication device may include a processing module and a communication module. Among them, the receiving module is used to perform the receiving actions in the method described in the sixth aspect above, and the processing module is used to perform the actions related to processing in the method described in the sixth aspect above.

[0062] In an eleventh aspect, a communication device is provided, including a processor and a storage medium. The storage medium stores instructions. When the instructions are run by the processor, the methods in the first aspect or any possible implementation of the first aspect are implemented, the methods in the second aspect or any possible implementation of the second aspect are implemented, the methods in the third aspect or any possible implementation of the third aspect are implemented, the methods in the fourth aspect or any possible implementation of the fourth aspect are implemented, the methods in the fifth aspect or any possible implementation of the fifth aspect are implemented, and the methods in the sixth aspect or any possible implementation of the sixth aspect are implemented.

[0063] In a twelfth aspect, a communication device is provided, including a processor. The processor is used to process data and / or information, so that the methods in the first aspect or any possible implementation of the first aspect are implemented, the methods in the second aspect or any possible implementation of the second aspect are implemented, the methods in the third aspect or any possible implementation of the third aspect are implemented, the methods in the fourth aspect or any possible implementation of the fourth aspect are implemented, the methods in the fifth aspect or any possible implementation of the fifth aspect are implemented, and the methods in the sixth aspect or any possible implementation of the sixth aspect are implemented. Optionally, the communication device may further include a communication interface. The communication interface is used to receive data and / or information and transmit the received data and / or information to the processor. Optionally, the communication interface is further used to output the data and / or information after being processed by the processor.

[0064] In a thirteenth aspect, a chip is provided, including a processor configured to run a program or instructions to implement the method in the first aspect or any possible implementation manner of the first aspect, to implement the method in the second aspect or any possible implementation manner of the second aspect, to implement the method in the third aspect or any possible implementation manner of the third aspect, to implement the method in the fourth aspect or any possible implementation manner of the fourth aspect, to implement the method in the fifth aspect or any possible implementation manner of the fifth aspect, to implement the method in the sixth aspect or any possible implementation manner of the sixth aspect. Optionally, the chip may further include a memory configured to store the program or instructions. Optionally, the chip may further include a transceiver.

[0065] In a fourteenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including instructions which, when run by a processor, implement the method in the first aspect or any possible implementation manner of the first aspect, implement the method in the second aspect or any possible implementation manner of the second aspect, implement the method in the third aspect or any possible implementation manner of the third aspect, implement the method in the fourth aspect or any possible implementation manner of the fourth aspect, implement the method in the fifth aspect or any possible implementation manner of the fifth aspect, implement the method in the sixth aspect or any possible implementation manner of the sixth aspect.

[0066] In a fifteenth aspect, a computer program product is provided, the computer program product including computer program code or instructions which, when run, implement the method in the first aspect or any possible implementation manner of the first aspect, implement the method in the second aspect or any possible implementation manner of the second aspect, implement the method in the third aspect or any possible implementation manner of the third aspect, implement the method in the fourth aspect or any possible implementation manner of the fourth aspect, implement the method in the fifth aspect or any possible implementation manner of the fifth aspect, implement the method in the sixth aspect or any possible implementation manner of the sixth aspect.

[0067] In a sixteenth aspect, a communication system is provided, which includes a combination of one or more of the following devices: a communication device implementing the communication device in the first aspect or any possible implementation of the first aspect, a communication device implementing the communication device in the second aspect or any possible implementation of the second aspect, such that the method in the third aspect or any possible implementation of the third aspect is implemented, such that the method in the fourth aspect or any possible implementation of the fourth aspect is implemented, such that the method in the fifth aspect or any possible implementation of the fifth aspect is implemented, such that the method in the sixth aspect or any possible implementation of the sixth aspect is implemented. Description of the Drawings

[0068] To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0069] Figure 1 It is a frame example diagram of PDSCH transmission delay;

[0070] Figure 2 It is a frame example diagram of PUSCH transmission delay;

[0071] Figure 3 It is an architecture example diagram of the communication system provided by the embodiment of the present application;

[0072] Figure 4 It is an example diagram of the connection relationship between a terminal device and a network device;

[0073] Figure 5 It is one of the flow example diagrams of a communication method provided by the embodiment of the present application;

[0074] Figure 6 It is one of the flow schematic diagrams of a communication method provided by the embodiment of the present application;

[0075] Figure 7 It is a schematic diagram of the SPS PDSCH transmission process;

[0076] Figure 8 It is one of the flow schematic diagrams of a communication method provided by the embodiment of the present application;

[0077] Figure 9 It is one of the frame structure example diagrams of the communication device provided by the embodiment of the present application;

[0078] Figure 10 It is one of the frame structure example diagrams of the communication device provided by the embodiment of the present application;

[0079] Figure 11 is one of the exemplary diagrams of the framework structure of the communication device provided by the embodiments of the present application;

[0080] Figure 12 is one of the exemplary diagrams of the framework structure of the communication device provided by the embodiments of the present application;

[0081] Figure 13 is one of the exemplary diagrams of the framework structure of the communication device provided by the embodiments of the present application;

[0082] Figure 14 is one of the exemplary diagrams of the framework structure of the communication device provided by the embodiments of the present application. Detailed implementation manners

[0083] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application. It should be understood that in the present application, indication includes direct indication (also known as explicit indication) and implicit indication. Among them, directly indicating information A means including this information A; implicitly indicating information A means indicating information A through the correspondence between information A and information B and directly indicating information B. Among them, the correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0084] It should be understood that in the present application, information C is used for the determination of information D, which includes both the case where information D is determined only based on information C and the case where it is determined based on information C and other information. In addition, when information C is used for the determination of information D, there may also be an indirect determination case, for example, the case where information D is determined based on information E, and information E is determined based on information C.

[0085] In addition, in the embodiments of the present application, "network element A sends information A to network element B" can be understood as that the destination end of this information A or the intermediate network element in the transmission path between the destination ends is network element B, which may include directly or indirectly sending information to network element B. "Network element B receives information A from network element A" can be understood as that the source end of this information A or the intermediate network element in the transmission path between the source ends is network element A, which may include directly or indirectly receiving information from network element A. Necessary processing may be performed on the information between the source end and the destination end of the information transmission, such as format change, etc., but the destination end can be understood as the valid information from the source end. Similar expressions in the present application can be understood similarly and will not be elaborated here.

[0086] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone.

[0087] In the description of the embodiments of the present application, the terms "first" and "second" in the specification and claims are used to distinguish different objects, rather than to describe a specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, rather than to describe a specific order of the target objects.

[0088] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.

[0089] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality of" refers to two or more. For example, a plurality of processing units refers to two or more processing units; a plurality of systems refers to two or more systems.

[0090] To facilitate the understanding of this embodiment, some technical terms and background technologies involved in this embodiment are introduced first:

[0091] (1) Subcarrier spacing (SCS): Refers to the frequency spacing between adjacent subcarriers. The values of SCS in the NR communication system include 15KHz, 30KHz, 60KHz, 120KHz, and as the communication system evolves, SCS may also be other values.

[0092] (2) UE capability 1, UE capability 2: Two types of UE processing capabilities defined in the 3rd generation partnership project (3GPP) standard, which can be used to indicate the UE processing time under different SCSs. Among them, the UE processing time includes the UE physical downlink shared channel (PDSCH) processing time and / or the UE physical uplink shared channel (PUSCH) preparation time. UE capability 1 can also be referred to as UE processing capability 1, and UE capability 2 can also be referred to as UE processing capability 2. The present application does not limit this. That is to say, UE capability 1 and UE capability 2 are used to indicate the UE processing time with different values, so as to support the application requirements in different scenarios. For example, for a transmission scenario that pursues low latency, UE capability 2 can be adopted, and for a transmission scenario that pursues high throughput, UE capability 1 can be adopted.

[0093] (3) Orthogonal Frequency Division Multiplexing (OFDM): The communication system divides a wide-frequency carrier into multiple orthogonal subcarriers with smaller bandwidths and uses these orthogonal subcarriers to transmit and receive signals. An OFDM symbol is composed of a group of subcarriers carrying modulated signals superimposed on each other.

[0094] (4) UE PDSCH processing time: It represents the processing time between when the UE receives the downlink PDSCH data and when it sends the Physical Uplink Control Channel (PUCCH) carrying the corresponding Hybrid Automatic Repeat Request - Acknowledgment (HARQ-ACK) information. For example, in Method 1, the UE PDSCH processing time can be the minimum number of OFDM symbols in the interval between the end of the last symbol of the received PDSCH and the first uplink symbol of the PUCCH carrying the HARQ-ACK corresponding to the PDSCH. Another example is Method 2, where the UE PDSCH processing time can be the minimum number of OFDM symbols in the interval between the end of the first symbol of the received PDSCH and the first uplink symbol of the PUCCH carrying the HARQ-ACK corresponding to the PDSCH. Another example is Method 3, where the UE PDSCH processing time can be the minimum number of OFDM symbols in the interval between the end of the last symbol of the received PDSCH and the last uplink symbol of the PUCCH carrying the HARQ-ACK corresponding to the PDSCH. Another example is Method 4, where the UE PDSCH processing time is the minimum number of OFDM symbols in the interval between the end of the first symbol of the received PDSCH and the last uplink symbol of the PUCCH carrying the HARQ-ACK corresponding to the PDSCH. It should be noted that the UE PDSCH processing time in this application focuses on the time interval that can distinguish the data and the feedback information corresponding to the data, or rather, the UE PDSCH processing time in this application indicates the time interval between the data and the feedback information corresponding to the data, and the specific presentation form of the UE PDSCH processing time is not limited. For ease of description, Method 1 is used as an example below.

[0095] (5) UE PUSCH Preparation Time: It represents the processing time between when the UE receives the downlink control information (DCI) carrying the uplink scheduling information and when it transmits the uplink PUSCH data. Usually, for different UE capabilities, the number of OFDM symbols corresponding to the minimum processing time is defined, and then the UE's processing time is further calculated. For example, in Example 1, the UE PUSCH preparation time is the minimum number of OFDM symbols in the interval between the end of the last symbol of the PDCCH that receives the DCI carrying the scheduled PUSCH and the first uplink symbol of the transmitted PUSCH. For example, in Example 2, the UE PUSCH preparation time is the minimum number of OFDM symbols in the interval between the end of the last symbol of the PDCCH that receives the DCI carrying the scheduled PUSCH and the last uplink symbol of the transmitted PUSCH. For example, in Example 3, the UE PUSCH preparation time is the minimum number of OFDM symbols in the interval between the end of the first symbol of the PDCCH that receives the DCI carrying the scheduled PUSCH and the first uplink symbol of the transmitted PUSCH. For example, in Example 4, the UE PUSCH preparation time is the minimum number of OFDM symbols in the interval between the end of the first symbol of the PDCCH that receives the DCI carrying the scheduled PUSCH and the last uplink symbol of the transmitted PUSCH. It should be noted that the UE PUSCH preparation time in this application focuses on the time interval that can distinguish the control information of the scheduled data and the data. Or rather, the UE PUSCH preparation time indicates the time interval between the control information of the scheduled data and the data, and no specific form of presentation of the UE PUSCH preparation time is limited. For the convenience of description, Example 1 is used as an example for the following description.

[0096] For the convenience of understanding, the UE PDSCH processing time and the UE PUSCH preparation time in the current NR communication system are specifically described below.

[0097] For downlink transmission, in the 3GPP standard, the parameter N1 is defined to represent the minimum number of OFDM symbols in the interval between the end of the last symbol of the received PDSCH and the first uplink symbol of the transmitted PUCCH carrying its corresponding HARQ-ACK, that is, the UE PDSCH processing time, also known as the PDSCH decoding time N1. For the convenience of description, it is hereinafter referred to as the PDSCH processing time. The value of N1 is determined based on different UE processing capabilities and different SCSs. Under the same SCS, the value of N1 for UE capability 2 is less than the value of N1 for UE capability 1. Under the same UE capability, the larger the SCS, the larger the value of N1. Exemplarily, the values of the PDSCH processing time for UE capability 2 are shown in Table 1 below:

[0098] Table 1 PDSCH Processing Time for UE Capability 2

[0099]

[0100]

[0101] In Table 1 above, the parameter μ is used to represent the value of SCS: SCS = 15 × 2 μ [KHz]. For example, μ = 0 means SCS is 15 KHz, μ = 1 means SCS is 30 KHz, and μ = 2 means SCS is 60 KHz. In this way, under UE capability 2, if there is no additional demodulation reference signal (DMRS) in the PDSCH, when SCS is 15 KHz, the value of N1 is 3, indicating that the PDSCH processing occupies at least 3 OFDM symbol times; when SCS is 30 KHz, the value of N1 is 4.5, indicating that the PDSCH processing occupies at least 4.5 OFDM symbol times; when SCS is 60 KHz, the value of N1 is 9, indicating that the PDSCH processing occupies at least 9 OFDM symbol times.

[0102] The mapping relationship between UE capability 1 and the value of N1, and the mapping relationship between UE capability 2 and the value of N1 are predefined. In this way, the base station side, that is, the network device side, after determining the scheduling configuration of the PDSCH, can determine the PDSCH processing time of the UE based on the predefined mapping relationship, and configure the PUCCH resources for acknowledgment / negative acknowledgment (ACK / NACK) feedback. The UE performs the feedback of acknowledgment / negative acknowledgment based on the corresponding PDSCH processing time. In this way, it can be ensured that the delay for the UE to receive the PUCCH transmission from the PDSCH is not less than the PDSCH processing time.

[0103] For uplink transmission, in the 3GPP standard, the parameter N2 is defined to represent the minimum number of OFDM symbols in the interval from the end of the last symbol of the PDCCH that receives the DCI carrying the scheduled PUSCH to the first uplink symbol in the transmitted PUSCH, that is, the UE PUSCH preparation time. For the convenience of description, it is hereinafter referred to as the PUSCH preparation time for short. The value of N2 is determined based on different UE processing capabilities and different SCSs. Exemplarily, the values of the PUSCH preparation time under UE capability 2 are shown in Table 2 below:

[0104] Table 2 PUSCH Preparation Time under UE Capability 2

[0105] μ <![CDATA[PUSCH preparation time N2[symbols]]]> 0 5 1 5.5 2 11 for frequency range 1

[0106] Among them, the meaning of μ can be referred to the description in Table 1 above. When SCS is 15KHz, the value of N2 is 5, indicating that PUSCH is prepared to occupy at least 5 OFDM symbols of time. When SCS is 30KHz, the value of N2 is 4.5, indicating that PUSCH is prepared to occupy at least 5.5 OFDM symbols of time. When SCS is 60KHz, the value of N2 is 9, indicating that PUSCH is prepared to occupy at least 9 OFDM symbols of time.

[0107] Based on the above mapping relationships between different UE capabilities, different subcarrier spacings and PUSCH preparation times, after the network device determines the scheduling configuration of PUSCH, it can determine the PUSCH preparation time of the UE based on the mapping relationship table, and further configure PDCCH and PUSCH resources, so that the delay from the UE receiving the uplink scheduling DCI to PUSCH transmission is not less than the PUSCH preparation time. In addition, compared with UE capability 1, the UE processing time under UE capability 2 is lower, which is more suitable for low-latency transmission scenarios.

[0108] Next, in combination with Figure 1 and Figure 2 the delay of data transmission will be introduced. Figure 1 and Figure 2 In the example, one transmission of PDSCH or PDSCH means that the data transmission only considers one initial transmission, and two transmissions of PDSCH or PDSCH mean that the data transmission considers one initial transmission and one retransmission.

[0109] Exemplarily, Figure 1 is a frame example diagram of the PDSCH transmission delay. As Figure 1 shown, the delay corresponding to one transmission (one-shot transmission) of PDSCH can include the following four parts: (1) The processing time of the new radio node B (gNB) for preparing PDSCH after the data arrives (DL data arrive); (2) The PDSCH alignment delay; (3) The PDSCH duration; (4) The UE processing time for receiving PDSCH. The delay corresponding to two transmissions (Two-shot transmission) of PDSCH, on the basis of the delay corresponding to one transmission of PDSCH, can also include the following four parts: (5) The PUCCH alignment delay; (6) The PUCCH duration; (7) The gNB processing time for receiving PUCCH and preparing PDSCH, and; (8) The PDCCH alignment delay. It can be understood that gNB is a type of network device.

[0110] Exemplarily, Figure 2 is a frame example diagram of PUSCH transmission delay. As Figure 2 shown, the delay corresponding to one-shot transmission of PUSCH may include the following four parts: (1) UE processing time (UE process) for the UE to prepare PUSCH after the uplink data arrives (UL data arrive); (2) PUSCH alignment delay; (3) PUSCH duration; (4) gNB processing (gNB process) time for receiving PUSCH. In addition, the delay corresponding to two-shot transmission of PUSCH, based on the delay corresponding to one-shot transmission of PUSCH, may further include the following two parts: (5) PDCCH alignment delay; (6) PDCCH duration.

[0111] Combining the above two transmission delay frameworks, taking UE capability 2 with lower processing delay as an example, analyze the delays corresponding to one-shot transmission and two-shot transmission of the UE respectively. Exemplarily, taking the data transmission under downlink (DL) semi-persistent scheduling (SPS) as an example, the corresponding parameter assumptions and delay analysis are as follows:

[0112] Parameter assumptions:

[0113] Frame structure: frequency division duplexing (FDD) or complementary time division duplexing (TDD);

[0114] SCS: 30KHz or 60KHz;

[0115] UE capability 2: N1 = 4.5, N2 = 5.5 at 30KHz; N1 = 9, N2 = 11 at 60KHz;

[0116] gNB processing delay: downlink: 0.5 * N2, uplink: 0.5 * N1;

[0117] PDSCH symbol length: 1 OFDM symbol (OFDM symbol, OS) or 2 OS.

[0118] Among them, complementary TDD means simulating the FDD scenario through the frame structure with complementary uplink and downlink of TDD dual carriers.

[0119] Delay analysis:

[0120] Based on the above parameter assumptions and Figure 1 the PDSCH transmission delay framework shown, if the terminal device adopts the processing time under UE capability 2, the corresponding PDSCH transmission delay is shown in Table 3 below:

[0121] Table 3 Example of PDSCH transmission delay under UE capability 2

[0122]

[0123] Among them, Table 3 analyzes the corresponding PDSCH transmission delays when configured with SCS values of 30KHz and 60KHz and PDSCH symbol lengths of 1OS and 2OS. Rows 10 and 11 in the table respectively represent the number and time of OFDM symbols required for the PDSCH to complete one transmission, and the number of OFDM symbols is equal to the sum of the values in rows 3 to 5; rows 12 and 13 in the table respectively represent the number and time of OFDM symbols required for the PDSCH to complete one initial transmission and one retransmission, and the number of OFDM symbols is equal to the sum of the values in rows 3 to 9.

[0124] It can be understood that considering the relatively low alignment delay, the alignment delays of channels such as PDSCH / PUCCH / PDCCH are ignored in the delay analysis of this application. As can be seen from Table 3, based on UE capability 2, in the scenarios where SCS is 30KHz or 60KHz and the PDSCH symbol length is 1OS or 2OS, the air interface delay required for the PDSCH to complete one initial transmission is approximately 0.3ms, and the air interface delay required for the PDSCH to complete one initial transmission and one retransmission is approximately 0.6 - 0.7ms.

[0125] Similarly, for uplink grant free (UL GF) transmission, it can be evaluated based on Figure 2 the transmission delay architecture shown. The specific evaluation results include: if the terminal device adopts the processing time under UE capability 2, in the scenarios where SCS is 30KHz or 60KHz and the PUSCH symbol length is 1OS or 2OS, the air interface delay required for the PUSCH to complete one initial transmission (one-shot transmission) is approximately 0.3ms, and the air interface delay required for the PUSCH to complete one initial transmission and one retransmission, that is, two transmissions (two-shot transmission), is approximately 0.6 - 0.7ms.

[0126] Compared with traditional mobile communication systems, the 5G wireless communication system - the NR system is dedicated to supporting higher system performance and will support multiple service types, different deployment scenarios, and a wider spectrum range. The main 5G service scenarios include eMBB, URLLC, and mMTC. In these scenarios, the communication system has requirements such as high reliability, low latency, large bandwidth, and wide coverage. With the evolution of communication systems and communication technologies, there may also be new service scenarios added in the future, such as precise industrial control, robotic collaborative control, and sensory interconnection. These high-reliability and low-latency systems have put forward higher requirements for the key technical indicators of service transmission, such as reliability, latency, connection number, jitter, and rate. Exemplarily, taking the URLLC scenario as an example, as shown in Table 4 below:

[0127] Table 4 Key Technical Indicators of URLLC in Different Scenarios

[0128]

[0129] It can be seen that for scenarios such as motion control, collaborative robots, machine-assisted medical treatment, and intelligent human-machine interaction, new parameter index requirements for reliability, end-to-end latency, and transmission rate are put forward for the URLLC system. That is to say, in the future, more and more application scenarios have higher requirements for the air interface latency of the URLLC system, such as 0.1 - 0.2 ms. Among them, the future URLLC system with lower latency can also be called a hyper-reliable low-latency communication (HRLLC) system, and can also be called a URLLC+ system. This application does not limit the names of these scenarios that require low latency and high reliability. The UE processing latency corresponding to UE capability 2 (such as 0.6 - 0.7 ms) cannot meet the lower air interface latency requirements (such as 0.1 - 0.2 ms), and UE capability 1 with a processing latency higher than UE capability 2 is even more unable to meet the 0.1 - 0.2 ms air interface latency requirements.

[0130] Based on the above analysis, the embodiments of this application provide a communication method to solve the above problems. This method defines a new UE capability: the first UE processing time. Under the same SCS, the first UE processing time is less than the second UE processing time. The second UE processing time is the UE processing time under UE capability 2. In this way, the processing time required for the terminal device to perform data transmission based on the first UE processing time is relatively shorter than that based on UE capability 2, thereby meeting the lower transmission latency requirements.

[0131] It can be understood that the above-mentioned first UE processing time is a form of expression of the UE processing time under the new UE capabilities, and the present application does not limit the specific form of expression of this UE processing time. For example, the UE processing time under the new UE capabilities can be named UE capability 3.

[0132] Before describing the technical solutions of the embodiments of the present application, first, the application platform of the communication method of the embodiments of the present application will be described with reference to the accompanying drawings. The embodiments of the present application can be applied to a 5G or NR system. The present application can also be applied to other communication systems, for example, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a wireless local area network (WLAN) system, a satellite communication system, a future communication system, such as a 6th generation (6G) mobile communication system, or a fusion system of multiple systems, etc. The technical solutions provided by the present application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems, etc.

[0133] A network element in a communication system can send a signal to another network element or receive a signal from another network element. The signal can include information, signaling, data, etc. Among them, the network element can also be replaced by an entity, a network entity, a device, a communication device, a communication module, a node, a communication node, etc. In the present disclosure, the network element is used as an example for description. For example, a communication system can include at least one terminal device and at least one network device. The network device can send a downlink signal to the terminal device, and / or the terminal device can send an uplink signal to the network device. It can be understood that the terminal device in the present disclosure can be replaced by a first network element, and the network device can be replaced by a second network element, and the two execute the corresponding communication methods in the present disclosure.

[0134] In the embodiments of the present application, the terminal device can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0135] The terminal device can be a device that provides voice / data. For example, it can be a handheld device, a vehicle-mounted device, etc. with wireless connection capabilities. Currently, some examples of terminals are: mobile phones, tablet computers, laptop computers, palm computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or other processing devices connected to a wireless modem, wearable devices, terminal devices in a 5G network, or terminal devices in a future evolved public land mobile network (PLMN), etc. The embodiments of this application are not limited thereto.

[0136] By way of example and not limitation, in the embodiments of this application, the terminal device can also be a wearable device. A wearable device can also be referred to as a wearable intelligent device, which is a general term for devices developed by applying wearable technologies to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0137] In the embodiments of the present application, the device for implementing the functions of the terminal device may be the terminal device itself, or a device capable of supporting the terminal device to implement such functions, such as a chip system. This device may be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. In the embodiments of the present application, only the case where the device for implementing the functions of the terminal device is the terminal device is used as an example for illustration, which does not limit the solutions of the embodiments of the present application.

[0138] The network device in the embodiments of the present application can be a device for communicating with a terminal device. This network device can also be referred to as an access network device or a radio access network device. For example, the network device can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. The base station can be generally covered by various names as follows, or replaced with the following names. For example: Node B, evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, slave station, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip disposed in the foregoing device or apparatus. The base station can also be a mobile switching center and a device that undertakes the function of a base station in D2D, V2X, M2M communications, a network-side device in a 6G network, a device that undertakes the function of a base station in a future communication system, etc. The base station can support networks with the same or different access technologies. Optionally, the RAN node can also be a server, a wearable device, a vehicle or an in-vehicle device, etc. For example, the access network device in vehicle to everything (V2X) technology can be a road side unit (RSU). The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the network device.

[0139] In some deployments, the network device mentioned in the embodiments of this application may be a device including a CU, or a DU, or a device including a CU and a DU, or a control plane CU node (central unit-control plane, CU-CP) and a user plane CU node (central unit-user plane, CU-UP) and a DU node. For example, the network device may include a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU.

[0140] In some deployments, multiple RAN nodes cooperate to assist a terminal in achieving wireless access, and different RAN nodes respectively implement some functions of a base station. For example, the RAN node may be a CU, a DU, a CU-CP, a CU-UP, or an RU, etc. The CU and the DU may be separately provided, or may also be included in the same network element, such as a BBU. The RU may be included in a radio frequency device or a radio frequency unit, such as included in an RRU, an AAU, or an RRH.

[0141] The RAN node may support one or more types of fronthaul interfaces. Different fronthaul interfaces respectively correspond to DUs and RUs with different functions. If the fronthaul interface between the DU and the RU is a common public radio interface (CPRI), the DU is configured to implement one or more of the baseband functions, and the RU is configured to implement one or more of the radio frequency functions. If the fronthaul interface between the DU and the RU is another interface, compared with the CPRI, some of the downlink and / or uplink baseband functions, for example, for the downlink, one or more of precoding, digital beamforming (BF), or inverse fast fourier transform (IFFT) / adding cyclic prefix (CP), are moved from the DU to the RU for implementation. For the uplink, one or more of digital beamforming (BF), or fast Fourier transform (FFT) / removing cyclic prefix (CP) are moved from the DU to the RU for implementation. In a possible implementation manner, this interface may be an enhanced common public radio interface (eCPRI). In the eCPRI architecture, the splitting method between the DU and the RU is different, corresponding to different categories (Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, F.

[0142] Taking eCPRI Cat A as an example, for downlink transmission, with layer mapping as the cut-off point, the DU is configured to implement one or more functions before layer mapping (i.e., one or more of encoding, rate matching, scrambling, modulation, and layer mapping), while other functions after layer mapping (such as one or more of RE mapping, digital beamforming (BF), or inverse fast fourier transform (IFFT) / adding cyclic prefix (CP)) are moved to the RU for implementation. For uplink transmission, with de-RE mapping as the cut-off point, the DU is configured to implement one or more functions before demapping (i.e., one or more of decoding, derate matching, descrambling, demodulation, inverse discrete fourier transform (IDFT), channel equalization, and de-RE mapping), while other functions after demapping (such as one or more of digital BF or fast fourier transform (FFT) / removing CP) are moved to the RU for implementation. It can be understood that for the function descriptions of the DU and RU corresponding to various types of eCPRI, reference can be made to the eCPRI protocol, which will not be elaborated here.

[0143] In a possible design, the processing unit in the BBU for implementing baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH for implementing baseband functions is called the baseband low (BBL) unit.

[0144] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be called the O-CU (open CU), the DU can also be called the O-DU, the CU-CP can also be called the O-CU-CP, the CU-UP can also be called the O-CU-UP, and the RU can also be called the O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU units in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0145] In the embodiments of this application, the device for implementing the functions of a network device may be the network device itself; it may also be a device capable of supporting the network device to implement such functions, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. This device may be installed in the network device or used in conjunction with the network device. In the embodiments of this application, only the case where the device for implementing the functions of the network device is the network device itself is used as an example for illustration, which does not limit the solutions of the embodiments of this application.

[0146] The network device and / or the terminal device may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they may also be deployed on water; they may also be deployed on aircraft, balloons, and satellites in the air. In the embodiments of this application, the scenarios where the network device and the terminal device are located are not limited. In addition, the terminal device and the network device may be hardware devices, or software functions running on dedicated hardware or software functions running on general hardware. For example, they may be virtualized functions instantiated on a platform (such as a cloud platform), or entities including dedicated or general hardware devices and software functions. This application does not limit the specific forms of the terminal device and the network device.

[0147] For example, Figure 3 is a schematic diagram of the architecture of the communication system provided by the embodiments of this application. As Figure 3 shown, the communication system may include network devices such as gNB or base station, and terminal devices such as UE1 to UE4. In this communication system, the base station may send downlink data to the terminal devices UE1 to UE4, and the terminal devices UE1 to UE4 may also send uplink data to the base station. Exemplarily, Figure 4 is a schematic diagram of the connection relationship between the terminal device and the network device. As Figure 4 shown, the terminal device and the network device may be connected through an air interface.

[0148] It should be noted that Figure 3 is only a simplified schematic diagram for easy understanding. For example, the communication system may also include other devices, such as wireless relay devices and / or wireless backhaul devices, etc., Figure 3 which are not drawn in. In practical applications, the communication system may include multiple network devices or multiple terminal devices. The embodiments of this application do not limit the number of network devices and terminal devices included in the communication system.

[0149] Next, the communication method provided by the embodiments of this application will be specifically described in conjunction with Figures 5 to 8 For example,

[0150] Exemplarily, Figure 5 is one of the flow schematic diagrams of a communication method provided by the embodiments of this application. AsFigure 5 As shown, the communication method may include:

[0151] S501, the terminal device reports user equipment (UE) capability information to the network device; wherein, the UE capability information indicates the first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than the second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

[0152] The above UE capability 2 is the UE capability 2 defined in the 3GPP standard. The UE processing time under UE capability 2 can refer to the descriptions of Table 1 and Table 2 above, which will not be elaborated here. Exemplarily, the terminal device may be, for example, a UE, and the network device may be, for example, a gNB or a base station, etc. For the convenience of description and understanding, hereinafter, the UE and the gNB will be taken as examples to specifically illustrate S501.

[0153] Optionally, the first UE processing time may be specifically described as the first physical downlink shared channel (PDSCH) processing time and / or the first physical uplink shared channel (PUSCH) preparation time; the description of the first PDSCH processing time and / or the first PUSCH preparation time may refer to the above UE PDSCH processing time and UE PUSCH preparation time, which will not be elaborated here.

[0154] Among them, the first PDSCH processing time indicates N1; the first PUSCH preparation time indicates N2. Different SCSs correspond to different values of N1 and N2, and the values of N1 and N2 are positively correlated with the SCS. The values of N1 and N2 corresponding to the same SCS may be the same or different.

[0155] It should be noted that the embodiments of the present application do not limit the parameter forms representing the PDSCH processing time and PUSCH preparation time under UE capability 3 either. For example, N1 and N2 may be used, or other parameter forms other than N1 and N2 may be used to represent the PDSCH processing time and PUSCH preparation time respectively. For example, OFN1 and OFN2 may be used to indicate the UE PDSCH processing time and PUSCH preparation time respectively. For the convenience of description, hereinafter, N1 and N2 are used to represent the first PDSCH processing time, that is, the UE PDSCH processing time.

[0156] In an optional implementation manner, a new UE processing capability may be defined, and the UE processing time under the new UE processing capability is the above first UE processing time. Exemplarily, the new UE processing capability may be represented in any form different from the above UE capability 1 and UE capability 2, such as UE capability 3, that is, in the form of UE capability 3. The embodiments of the present application do not limit this. For the convenience of description, hereinafter, UE capability 3 is used to refer to the new UE processing capability.

[0157] Based on this, the mapping relationship between UE capability 3, PDSCH processing time N1, and PUSCH preparation time N2 can be predefined for data transmission. The specific usage method of this mapping relationship in data transmission can refer to the usage method of the existing mapping relationship between UE capability 2 and UE processing time, which will not be elaborated here. The embodiments of this application do not limit the manifestation form of the mapping relationship between UE capability 3, PDSCH processing time N1, and PUSCH preparation time N2. For example, it can be in the form of a table.

[0158] In the embodiments of this application, the specific values of N1 and N2 in the mapping relationship between UE capability 3, PDSCH processing time N1, and PUSCH preparation time N2 are not limited. Under the same SCS, the values of N1 and N2 under UE capability 3 are less than those of N1 and N2 under UE capability 2. In one example, the values of N1 and N2 under UE capability 3 are usually set to 0.5 times of a positive integer: 0.5*X, where X is a positive integer. The embodiments of this application do not make any limitations in this regard.

[0159] Exemplarily, a terminal device such as a UE reports to the network device side such as a base station which UE capability it supports, that is, UE capability information, through radio resource control (RRC) signaling. After receiving the capability information reported by the terminal device, the network device can determine which predefined mapping relationship between UE capability and UE processing time should be used by the terminal device. On this basis, when performing uplink or downlink scheduling, the network device side can determine the processing delay of the UE based on the SCS configuration information and the mapping relationship between UE capability (such as UE capability 3), PDSCH processing time N1, or PUSCH preparation time N2, so as to determine the resource configuration for data transmission.

[0160] For ease of understanding, the following combines Figure 1 and Figure 2 's delay architecture to analyze the uplink and downlink transmission delays in different scenarios, so as to describe the value situations of PDSCH processing time N1 and PUSCH preparation time N2 (that is, the above-mentioned first UE processing time) under the new UE processing capability (that is, the above-mentioned UE capability 3). It can be understood that this delay analysis process is used to analyze the situations of N1 and N2 under lower air interface delay constraints, and the parameters in the applicable scenarios of the new UE processing capability can be the same as or different from the parameter assumptions in this delay analysis process. Exemplarily, the parameter assumptions in this delay analysis are shown in Table 5 below:

[0161] Table 5 Parameter Assumptions for URLLC Delay Evaluation

[0162]

[0163] The above parameter assumptions consider the configurations commonly used in the URLLC system. Among them, DL SPS transmission means that the gNB pre-allocates SPS PDSCH resources with a specific period for the UE. The gNB does not need to send DCI to indicate downlink scheduling information every time it schedules. The UE can directly perform periodic PDSCH reception based on the configured SPS; UL Grant Free transmission means that the gNB pre-allocates PUSCH resources for the UE. When the UE has traffic arriving, it can directly send data based on the pre-configured resources without sending a scheduling request, thus effectively reducing the transmission delay and reducing the control information overhead. In addition, most of the URLLC transmissions are small packet services and the target delay requirements are extremely low. Therefore, it is assumed that the time domain symbol length occupied by PDSCH / PUSCH is 1 or 2 OSs.

[0164] Based on the above parameter assumptions, taking the example of meeting the air interface transmission delay requirement of 0.1 ms to 0.2 ms, the appropriate values of N1 and N2 are analyzed. It can be understood that the embodiments of the present application do not limit the delay requirements that the UE capability 3 can meet. To meet the URLLC delay requirements in multiple scenarios, the embodiments of the present application mainly analyze three possible delay constraints, specifically including: Delay constraint 1: Complete 1 initial transmission within 0.1 ms air interface delay; Delay constraint 2: Complete 1 initial transmission within 0.2 ms air interface delay; Delay constraint 3: Complete 1 initial transmission and 1 retransmission within 0.2 ms air interface delay. The delay analysis of DL SPS and UL Grant Free transmissions under different SCSs is carried out below. It should be noted that the 0.1 ms to 0.2 ms air interface delay constraint and the maximum of two transmissions are determined based on the service requirements of future low-delay application scenarios, and other air interface delays and transmission times constraints are not excluded.

[0165] Scenario 1: DL SPS transmission:

[0166] Still referring to Figure 1 , after the downlink data packet for the initial transmission arrives, the gNB first undergoes the physical layer processing delay and the PDSCH alignment delay caused by the time slot boundary, and then performs the PDSCH transmission and the decoding on the UE side. The time required from the arrival of the downlink data to the completion of the decoding on the UE side is recorded as one transmission delay; further, the UE generates ACK / NCAK information based on the demodulation result and sends it on the PUCCH. If the network device side receives the NCAK information, it generates the DCI for retransmission scheduling, and then through the PDSCH retransmission and the decoding on the UE side, the time required from the arrival of the downlink data to the completion of the decoding of the first retransmission data on the UE side is recorded as two transmission delays.

[0167] Exemplarily, for the scenario of DL SPS transmission and SCS = 30 KHz, the analysis of the corresponding values of N1 and N2 under the three delay constraints is shown in Table 6:

[0168] Table 6 DL SPS Transmission and Latency Evaluation Results with SCS of 30 KHz

[0169]

[0170] Among them, one-shot transmission (0.1 ms) represents the latency analysis result of completing 1 initial transmission within a 0.1 ms air interface latency; one-shot transmission (0.2 ms) represents the corresponding latency analysis result of completing 1 initial transmission within a 0.2 ms air interface latency, and two-shot transmission (0.2 ms) represents the corresponding latency analysis result of completing 1 initial transmission and 1 retransmission within a 0.2 ms air interface latency. For the same table items in Tables 7 to 9 as in Table 6, this explanation can be referred to and will not be elaborated further.

[0171] Refer to Table 6: To meet the requirement of completing 1 initial transmission of 1OS PDSCH within a 0.1 ms air interface latency, N1 and N2 can be reduced to approximately 1OS; to meet the requirement of completing 1 initial transmission of 1OS PDSCH or 2OS PDSCH within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 2OS. To meet the requirement of completing 1 initial transmission and 1 retransmission of 1OS PDSCH within a 0.2 ms air interface latency, N1 can be reduced to approximately 1OS, and N2 needs to be reduced to approximately 0.5OS.

[0172] Exemplarily, for the scenario of DL SPS transmission with SCS = 60 KHz, the value analysis of N1 and N2 under three latency constraints is shown in Table 7 below:

[0173] Table 7 DL SPS Transmission and Latency Evaluation Results with SCS of 60 KHz

[0174]

[0175]

[0176] Refer to Table 7: To meet the requirement of completing 1 initial transmission of 1OS PDSCH or 2OS PDSCH within a 0.1 ms air interface latency, N1 and N2 can be reduced to approximately 2OS. To meet the requirement of completing 1 initial transmission of 1OS PDSCH or 2OS PDSCH within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 5OS. To meet the requirement of completing 1 initial transmission and 1 retransmission of 1OS PDSCH or 2OS PDSCH within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 2OS.

[0177] Scenario 2: UL GF Transmission:

[0178] Still refer to Figure 2, the latency of a single PUSCH transmission may include: the UE processing time for preparing the PUSCH, the PUSCH alignment latency, the PUSCH duration, and the gNB processing time for receiving the PUSCH. On this basis, the latency between two PUSCH transmissions may also include: the PDCCH alignment latency and the PDCCH duration. Regarding the latency of PUSCH transmission:

[0179] Exemplarily, for the scenario of UL GF transmission with SCS = 30 KHz, the analysis of the corresponding values of N1 and N2 under three latency constraints is shown in Table 8 below. Table 8 Latency evaluation results for UL GF transmission with SCS of 30 KHz

[0180]

[0181] Referring to Table 8 above, to satisfy the requirement that 1 OS PDSCH completes one initial transmission within a 0.1 ms air interface latency, N1 and N2 can be reduced to approximately 1 OS. To satisfy the requirement that 1 OS PDSCH or 2 OS PDSCH completes one initial transmission within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 2 OS. To satisfy the requirement that 1 OS PDSCH completes one initial transmission and one retransmission within a 0.2 ms air interface latency, N1 can be reduced to approximately 1 OS, and N2 needs to be reduced to approximately 0.5 OS.

[0182] Exemplarily, for the scenario of UL Grant Free transmission with SCS = 60 KHz, the analysis of the corresponding values of N1 and N2 under three latency constraints is shown in Table 9 below:

[0183] Table 9 Latency evaluation results for UL GF transmission with SCS of 60 KHz

[0184]

[0185] Referring to Table 9: To satisfy the requirement that approximately 2 OS PDSCH completes one initial transmission within a 0.1 ms air interface latency, N1 and N2 can be reduced to approximately 2 OS. To satisfy the requirement that 1 OS PDSCH or 2 OS PDSCH completes one initial transmission within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 5 OS. To satisfy the requirement that approximately 2 OS PDSCH completes one initial transmission and one retransmission within a 0.2 ms air interface latency, N1 and N2 can be reduced to approximately 2 OS.

[0186] In summary, to meet the lower air interface transmission delay requirements of URLLC, such as 0.1 ms to 0.2 ms, new UE processing capabilities need to be defined, including the PDSCH processing time N1 and the PUSCH preparation time N2. Compared with the original UE capability 2: when the SCS is 30 KHz, N1 is equal to 4.5 and N2 is equal to 5.5; when the SCS is 60 KHz, N1 is equal to 9 and N2 is equal to 11, the new UE processing capabilities can be specifically different as follows:

[0187] In an optional implementation, at the same SCS, the first UE processing time is less than or equal to 1 / N times the second UE processing time; where N is a positive integer greater than 1.

[0188] The embodiments of the present application provide the value range of the number of OFDM symbols occupied by the first PDSCH processing time and / or the first PUSCH preparation time, so as to further ensure that the terminal device can achieve a lower data transmission delay and further improve the reliability of the transmission.

[0189] In an optional implementation, N is equal to 4 or equal to 2.

[0190] Exemplarily, at the same SCS, if the first UE processing time is less than or equal to 1 / 4 times the second UE processing time, the UE can complete an initial transmission within 0.1 ms of the air interface delay, or the UE can complete an initial transmission and a retransmission within 0.2 ms of the air interface delay. At the same SCS, if the first UE processing time is less than or equal to 1 / 2 times the second UE processing time, the UE can complete an initial transmission within 0.2 ms of the air interface delay.

[0191] In an optional implementation, when the SCS is 30 KHz:

[0192] The number of OFDM symbols occupied by the first PDSCH processing time is less than or equal to 2; and / or,

[0193] The number of OFDM symbols occupied by the first PUSCH preparation time is less than or equal to 2.

[0194] In an optional implementation, when the SCS is 60 KHz:

[0195] The number of OFDM symbols occupied by the first PDSCH processing time is less than or equal to 5; and / or,

[0196] The number of OFDM symbols occupied by the first PUSCH preparation time is less than or equal to 5.

[0197] The embodiments of the present application do not limit the maximum value of SCS. That is, SCS can be 15 KHz, 30 KHz, 60 KHz, 120 KHz or other values. As an example, only the new UE processing capabilities with SCS up to 60 KHz are listed. Specifically, the mapping relationships between different SCSs corresponding to UE capability 3 and the PDSCH processing time and PUSCH preparation time may include, but are not limited to, the forms shown in Tables 10 to 14 below, or the forms obtained by any combination of Tables 10 to 14. It should be noted that in Tables 10 to 14, " / " means that the required air interface delay cannot be achieved under the corresponding SCS. The meaning of μ can be referred to the description in Table 1 above.

[0198] Table 10 Example 1 of N1 and N2 values under UE capability 3

[0199] μ <![CDATA[PDSCH decoding time N1[symbols]]]> 0 0.5 or / 1 1 2 2

[0200] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 0.5 or / 1 1 2 2

[0201] At this time, under the same SCS, N1 = N2 under UE capability 3, and the values of N1 and N2 are less than or equal to one-fourth of the values of N1 and N2 under UE capability 2. With such values, the terminal device can complete an initial transmission within an air interface delay of 0.1 ms, or complete an initial transmission within an air interface delay of 0.2 ms, or complete an initial transmission and a retransmission within an air interface delay of 0.2 ms.

[0202] Table 11 Example 2 of N1 and N2 values corresponding to UE capability 3

[0203] μ <![CDATA[PDSCH decoding time N1[symbols]]]> 0 / 1 0.5 2 1.5

[0204] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 / 1 0.5 2 1.5

[0205] At this time, under the same SCS, N1 = N2 under UE capability 3, and the values of N1 and N2 are less than or equal to one-fourth of the values of N1 and N2 under UE capability 2. With such values, the terminal device can complete an initial transmission within an air interface delay of 0.1 ms, or complete an initial transmission within an air interface delay of 0.2 ms, or complete an initial transmission and a retransmission within an air interface delay of 0.2 ms.

[0206] Table 12 Example 3 of N1 and N2 values corresponding to UE capability 3

[0207] μ <![CDATA[PDSCH decoding time N1[symbols]]]> 0 1 1 1.5 2 4.5

[0208] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 1 1 1.5 2 4.5

[0209] At this time, under the same SCS, N1 under UE capability 3 is equal to N2, and the values of N1 and N2 are less than or equal to half of the values of N1 and N2 in UE capability 2. With such values, the terminal device can complete an initial transmission within a radio interface latency of 0.2 ms.

[0210] From the several possible value cases of N1 and N2 listed in Table 10 to Table 12 above, it can be seen that under the same SCS, the values of N1 and N2 can be the same; as the value of SCS increases, the values of N1 and / or N2 also increase, that is, the values of N1 and N2 are positively correlated with SCS. In addition, different values of SCS correspond to different N1 and different N2. For example, in Table 12 above, the N1 corresponding to an SCS value of 15 KHz is 1, the N1 corresponding to an SCS value of 30 KHz is 1.5, and the N1 corresponding to an SCS value of 60 KHz is 4.5; the N2 corresponding to an SCS value of 15 KHz is 1, the N2 corresponding to an SCS value of 30 KHz is 1.5, and the N2 corresponding to an SCS value of 60 KHz is 4.5.

[0211] Table 13 Example 4 of the values of N1 and N2 corresponding to UE capability 3

[0212] μ <![CDATA[PDSCH decoding time N1[symbols]]]> 0 / 1 0.5 2 1.5

[0213] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 / 1 1 2 2

[0214] At this time, under the same SCS, the values of N1 and N2 under UE capability 3 can be different, and the values of N1 and N2 are less than or equal to one-fourth of the values of N1 and N2 in UE capability 2. With such values, the terminal device can complete an initial transmission within a radio interface latency of 0.1 ms, or complete an initial transmission within a radio interface latency of 0.2 ms, or complete an initial transmission and a retransmission within a radio interface latency of 0.2 ms.

[0215] Table 14 Example 5 of the values of N1 and N2 corresponding to UE capability 3

[0216] μ <![CDATA[PDSCH decoding time N1[symbols]]]> 0 1 1 1.5 2 4.5

[0217] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 1 1 2 2 5

[0218] At this time, under the same SCS, the values of N1 and N2 under UE capability 3 can be the same or different, and the values of N1 and N2 are respectively less than or equal to half of the values of N1 and N2 in UE capability 2. With such values, the terminal device can complete an initial transmission within a radio interface latency of 0.2 ms.

[0219] As can be seen from Table 13 and Table 14 above, under the same SCS, the values of N1 and N2 can be different, and the value of N2 can be greater than or equal to the value of N1. As the value of SCS increases, the value of N1 and / or N2 also increases, that is, the values of N1 and N2 are positively correlated with SCS. In addition, different values of SCS correspond to different N1 and different N2. For example, in Table 14 above, the N1 corresponding to the SCS value of 15KHz is 1, the N1 corresponding to the SCS value of 30KHz is 1.5, and the N1 corresponding to the SCS value of 60KHz is 4.5; the N2 corresponding to the SCS value of 15KHz is 1, the N2 corresponding to the SCS value of 30KHz is 2, and the N2 corresponding to the SCS value of 60KHz is 5.

[0220] It can be understood that Tables 10 to 14 above are only examples of the values of N1 and N2 under UE capability 3, and can also be used as examples of the mapping relationship between UE capability 3 and the PDSCH processing time N1 and the PUSCH preparation time N2, and do not constitute a limitation on the specific values of N1 and N2. That is, the specific values of N1 and N2 can be different from the examples in Tables 10 to 14 above, and do not constitute a limitation on the mapping relationship between UE capability 3 and the PDSCH processing time N1 and the PUSCH preparation time N2. In practical applications, the values of N1 and N2 under UE capability 3, and the mapping relationship between UE capability 3 and the PDSCH processing time N1 and the PUSCH preparation time N2, can be in the form of any possible combination results of Tables 10 to 14 above.

[0221] In a possible implementation manner, the mapping relationship between different SCSs and the UE processing time under UE capability 3 can be predefined or configured based on the mapping relationship between different SCSs and the UE processing time under UE capability 2 and the first offset value. Among them, the first offset value includes the first PDSCH processing time offset value and the first PUSCH preparation time offset value. The first offset value can be used to represent how many OFDM symbol numbers the OFDM symbol numbers corresponding to the UE processing time under UE capability 3 are offset from the OFDM symbol numbers corresponding to the UE processing time under UE capability 2. This embodiment does not limit the specific offset method, and any offset method that can ensure that for the same SCS, the UE processing time under UE capability 3 is less than the UE processing time under UE capability 2 can be used in this application. The following takes the addition / subtraction offset method as an example for illustration.

[0222] In one example, if the sign of the first offset value is positive, then the number of OFDM symbols corresponding to the UE processing time under UE capability 3 = the number of OFDM symbols corresponding to the UE processing time under UE capability 2 - the first offset value. In one example, if the sign of the first offset value is negative, then the number of OFDM symbols corresponding to the UE processing time under UE capability 3 = the number of OFDM symbols corresponding to the UE processing time under UE capability 2 + the first offset value. It can be understood that the first offset value can be predefined or configured by a network device such as a base station or a gNB.

[0223] In addition, the first offset values corresponding to different SCSs can be the same or different. Under the same SCS, the first PDSCH processing time offset value and the first PUSCH preparation time offset value can be the same or different, and this application does not limit this. Exemplarily, the mapping relationship between different SCSs and the first PDSCH processing time offset value and the first PUSCH preparation time offset value under UE capability 3 can include but is not limited to the following forms shown in Table 15:

[0224] Table 15 Examples of the first PDSCH processing time offset value and the first PUSCH preparation time offset value under UE capability 3

[0225]

[0226]

[0227] Optionally, the mapping relationship between different SCSs and the UE processing time under UE capability 3 can also be determined based on the mapping relationship between different SCSs and the UE processing time under UE capability 1 and a second offset value. This application does not limit this. Specifically, it is similar to the method of determining based on the mapping relationship between different SCSs and the UE processing time under UE capability 2 and the first offset value, except that the UE capability it is based on is UE capability 1. Accordingly, the second offset value can be set based on UE capability 1. For the same parts, they will not be elaborated here, and the corresponding implementation manners in Table 15 above can be referred to.

[0228] In one possible implementation manner, the above communication method may further include:

[0229] Transmitting data based on the first UE processing time; wherein, the transmission of data includes one or more of the following methods:

[0230] The data scheduling method includes SPS or GF scheduling;

[0231] The time-domain resources occupied by the demodulation reference signal DMRS of the data are located before the time-domain resources occupied by the data;

[0232] The time-domain resources occupied by the data are less than or equal to 2 OFDM symbols.

[0233] Exemplarily, considering that the air interface latency requirement in the future URLLC scenario is more stringent, the newly defined UE processing capability needs to be used in conjunction with a specific scheduling scenario to meet the latency requirement. The new UE processing capability has higher requirements for the UE, which will increase the UE processing complexity and power consumption. Optionally, scenario information associated with the new UE capability can be defined, that is, the applicable scenarios of the new UE processing capability are restricted. For example, when the UE uses UE capability 3, one or more of the following scenario information can be satisfied:

[0234] It is not expected to perform DCI-based dynamic scheduling; it is expected to perform SPS scheduling or GF scheduling; it is expected to perform early DMRS transmission, where the early DMRS transmission means that the DMRS is transmitted before the service data arrives, enabling the receiving end to perform channel estimation in advance to reduce the data reception latency; it is expected that the data scheduling of PDSCH / PUSCH occupies at most 2 OFDM symbols; it is expected that there are no additional DMRS symbols in the data transmission, etc.

[0235] In the embodiments of the present application, there are certain restrictions on the mapping relationship between the predefined SCS and the UE capability, that is, the application scenarios of the newly defined UE capability, so as to reduce the UE processing difficulty and power consumption and further improve the performance of data transmission.

[0236] Figure 6 is one of the schematic flowcharts of a communication method provided by the embodiments of the present application. As Figure 6 shown, the communication method may include:

[0237] S6S601, the terminal device reports user equipment UE capability information to the network device; wherein, the UE capability information is used to indicate multiple UE processing times of the UE.

[0238] Exemplarily, Figure 7 is a schematic diagram of the SPS PDSCH transmission process. As Figure 7As shown, URLLC transmission may have mixed data packet transmissions with different data transmission periods. For example, SPS period = 1ms: the transmission period (SPS period) of service 1 is 1ms; SPS period = 4ms: the transmission period (SPS period) of service 2 is 4ms. The service transmission period, that is, the time corresponding to the data transmission period, can be understood as the end-to-end delay. In addition to the air interface delay, the end-to-end delay also includes high-level and core network processing delays. Therefore, the end-to-end delay is greater than the air interface transmission delay. Exemplarily, based on the decomposition of the end-to-end delay structure, in order to meet the 1ms end-to-end delay, the corresponding air interface delay is approximately 0.2ms; in order to meet the 4ms end-to-end delay, the corresponding air interface delay is approximately 1ms. It can be seen that the air interface delays required for data packets with different data transmission periods are different, and different UE processing capabilities can be used.

[0239] In view of the characteristics of URLLC periodic small packet transmission, the downlink usually adopts the SPS transmission method with pre-reserved resources. Corresponding to the above transmission scenario, the gNB can indicate two sets of SPS configurations for the UE, including SPS PDSCH#1 and SPS PDSCH#2, where the SPS period configured for SPS PDSCH#1 is 1ms, and the SPS period configured for SPS PDSCH#2 is 4ms.

[0240] S602, the network device sends first indication information to the terminal device, where the first indication information is used to indicate a data transmission period.

[0241] Still see Figure 7 , usually, if the UE reports to the base station that it can support the processing capability under UE capability 3, it means that no matter whether the UE receives SPS PDSCH#1 or SPS PDSCH#2, it will use the extremely low processing delay corresponding to UE capability 3 to demodulate the PDSCH, which will greatly increase the complexity and power consumption of UE processing. In fact, for SPS PDSCH#2, which has a looser delay requirement, the UE only needs to use UE capability 2 to meet the 1ms air interface delay requirement without using UE capability 3. In this regard, the network device can indicate the data transmission period through S602 to ensure that the UE can use the appropriate UE capability in a targeted manner.

[0242] S603, the terminal device determines the target UE processing time among the multiple UE processing times according to the data transmission period.

[0243] Optionally, the above S603 may specifically include: the terminal device determines the target UE processing time among the multiple UE processing times according to the data transmission period and the period threshold.

[0244] Optionally, the period threshold is predefined or configured by the network device.

[0245] Optionally, before S603, the above communication method may further include:

[0246] S604, the network device sends second indication information to the terminal device, and the second indication information is used to indicate a period threshold; wherein, there is a mapping relationship among the transmission period, the period threshold, and multiple UE capabilities.

[0247] Exemplarily, by predefining / configuring in advance the period threshold for capability switching, the UE can determine the UE processing time, that is, the target UE processing time, based on the transmission period indicated in the SPS configuration and the period threshold for capability switching. For example, when the transmission period configured by the SPS is greater than the period threshold for capability switching, a slower UE processing capability is adopted; when the transmission period configured by the SPS is less than or equal to the period threshold for capability switching, a faster UE processing capability is adopted. The following takes the downlink transmission as an example for specific description. It can be understood that the solution of this embodiment is equally applicable to the uplink transmission. The difference from the downlink transmission is that after the UE determines the target UE processing time in the uplink transmission, the data transmission performed is the uplink transmission. For the specific process, reference can be made to the existing uplink transmission process, which will not be elaborated here.

[0248] Exemplarily, Figure 8 is one of the flow diagrams of a communication method provided by an embodiment of the present application. As Figure 8 shown, the communication method may include:

[0249] S801, the network device sends a UE capability request to the terminal device.

[0250] Exemplarily, the network device, such as a gNB, sends a capability request to the terminal device, such as a UE, through RRC signaling to query the UE capability. After the gNB and the UE are connected through RRC, when the gNB needs the UE to report the UE capability, the gNB will send a UE capability enquiry information element (IE) to the UE through RRC, which is used to indicate the UE to report the capability-related information. The Filter field in the UE capability query signaling will indicate which UE capabilities the UE base station specifically wants to know.

[0251] It can be understood that in an optional example, the UE can actively report the UE capability. In this case, the network device does not need to query the UE capability, or rather, it does not need the network device to send UE capability query information, that is, the UE capability enquiry IE, to the terminal device.

[0252] S802, the terminal device reports the UE capability to the network device.

[0253] Exemplarily, the UE reports capability information to the gNB via RRC signaling. The capability information includes at least a first processing capability and a second processing capability. Under the same SCS, the time required for the first processing capability is greater than that required for the second processing capability. When the UE receives the UE capability enquiry IE, the UE reports its UE capabilities according to the instruction indication, which is sent on the UE capability enquiry IE carried by RRC. For the case where the UE has more than one processing capability, the UE needs to report at least two processing capabilities it supports to the base station. For example, UE capability 1 and UE capability 2, or UE capability 2 and UE capability 3, or UE capability 1 and UE capability 3, or UE capability 1, UE capability 2, and UE capability 3, etc.

[0254] Optionally, if the UE can only support the switching between two processing capabilities, when the UE reports that it has three processing capabilities at the same time, the gNB can further instruct the UE on the two processing capabilities for which the capability switching is to be performed.

[0255] It should be noted that for UE capability 3, a new field needs to be added in RRC to indicate UE capability 3. This configuration also applies to Figure 5 the embodiments shown.

[0256] S803. The network device configures multiple semi-persistent scheduling SPS configurations for the terminal device.

[0257] Exemplarily, the gNB configures at least two SPS configurations for the UE via RRC signaling and activates at least two SPS configurations via DCI. The relevant parameters of the DL SPS configuration are jointly indicated by RRC and DCI. The gNB can configure one or more SPS-configurations (SPS-Config) for the UE via RRC signaling, and different SPS-Configs correspond to different SPS configuration indices, that is, SPS-ConfigIndex-r16. The parameter periodicity or periodicityExt-r16 or periodicityExt-r17 is used to indicate the SPS configuration period.

[0258] S804. The network device activates the configured multiple semi-persistent scheduling SPS configurations.

[0259] After a network device configures one or more SPSs through RRC signaling but they cannot be used yet, they can be activated through DCI. The index of the SPS configuration is indicated by the HARQ process number field in the DCI, that is, the SPS configuration with the sps-ConfigIndex-r16 value in SPS-Config equal to the HARQ process number value in the DCI is activated. For the activation of multiple SPS configurations, they can be activated separately through multiple DCIs, or multiple SPS configurations can be activated through one DCI. The embodiments of this application do not limit this.

[0260] Exemplarily, for the scenario of hybrid periodic service transmission, the gNB can configure two SPS configurations for the UE through the combined indication of RRC + DCI. For example Figure 11 the SPS PDSCH#1 and SPS PDSCH#2 shown, where the SPS transmission periods configured for SPS PDSCH#1 and SPS PDSCH#2 are 1 ms and 4 ms respectively. Optionally, the above SPS transmission period can also be represented by slots.

[0261] S805, the network device sends a period threshold to the terminal device.

[0262] Exemplarily, the gNB indicates a period threshold for capacity switching to the UE. The period threshold for capacity switching is used to indicate what processing capacity the UE should adopt for the reception of different SPS services. The gNB can send a first indication message to indicate the capacity switching threshold. The first indication message can be DCI, can be a media access control control element (MAC CE), can also be RRC signaling, or can also be any combination of 2 or 3 of the above three.

[0263] S806, the terminal device determines the UE processing time based on the transmission period and period threshold indicated by the SPS configuration.

[0264] Exemplarily, the UE determines the UE processing time based on the SPS configuration period and the period threshold for capacity switching. Among them, if the SPS configuration period is greater than the period threshold for capacity switching, the UE uses the first processing capacity; if the SPS configuration period is less than the period threshold for capacity switching, the UE uses the second processing capacity.

[0265] Exemplarily, when the SPS configuration period corresponding to the current transmission service is greater than the period threshold for capacity switching, a slower UE processing capacity is adopted. When the SPS period is less than or equal to the period threshold for capacity switching, a faster UE processing capacity is adopted. If the configured period threshold for capacity switching is 3 ms, for the SPS PDSCH#1 with a data transmission period of 1 ms, its SPS period is less than the period threshold for capacity switching, and the UE capacity 3 with a low processing delay can be adopted. For the SPS PDSCH#2 with a data transmission period of 4 ms, its SPS period is greater than the period threshold for capacity switching, and the UE capacity 2 with a high processing delay can be adopted.

[0266] S605, the terminal device transmits data based on the target UE processing time.

[0267] Exemplarily, still referring to Figure 8 , S605 may specifically include:

[0268] S807, the network device sends the PDSCH corresponding to the SPS to the terminal device.

[0269] Exemplarily, the gNB sends the SPS PDSCH to the UE. The specific process can refer to the PDSCH sending process shown above Figure 1 and will not be elaborated here.

[0270] S808, the terminal device receives the PDSCH corresponding to the SPS based on the determined UE processing time.

[0271] Exemplarily, the UE receives the SPS PDSCH on the corresponding resources based on the determined processing capacity. The specific process can refer to the PDSCH receiving process shown above Figure 1 and will not be elaborated here.

[0272] In addition, the above examples illustrate that the UE can perform UE handover for different transmission periods. In addition to this, the UE can also adaptively determine the UE processing time according to different scheduling configuration information. Exemplarily, in the URLLC low-latency transmission scenario, the base station realizes early channel estimation by transmitting DMRS in advance. Correspondingly, the UE side can determine which processing capability to adopt based on the configuration of DMRS in the scheduling information. For example, if the base station configures the DMRS symbol to be transmitted before the data resources for the UE, it means that the current transmitted service is a URLLC service that pursues extremely low latency (such as 0.1 - 0.2 ms), and the UE can use a lower processing time for data reception, such as UE capability 3. If the base station does not configure the DMRS symbol to be transmitted in advance for the UE, it means that the current transmitted service is a non-low-latency service (such as eMBB service) or a URLLC service with a 1 ms air interface latency requirement, and the UE can use a higher processing time for data reception, such as UE capability 2 or capability 1, thereby reducing the UE processing complexity and power consumption.

[0273] In the embodiments of the present application, for the scenario where the UE supports multiple UE processing times, the UE determines the UE processing time matching the transmission period according to the transmission period of the data, achieving the effect of adaptively switching the UE capabilities, thereby further reducing the UE processing complexity and power consumption on the basis of ensuring the transmission latency. In addition, this can avoid resource waste or excessive latency and improve the performance of data transmission.

[0274] Exemplarily, Figure 9 is one of the framework structure example diagrams of the digital communication device provided by the embodiments of the present application. As Figure 9 shown, the communication device 900 may include:

[0275] An information reporting module 901, configured to report user equipment UE capability information;

[0276] Among them, the UE capability information indicates the first UE processing time; under the same SCS, the first UE processing time is less than the second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

[0277] Exemplarily, Figure 10 is one of the framework structure example diagrams of the communication device provided by the embodiments of the present application. As Figure 10 shown, the communication device 1000 may include:

[0278] An information reporting module 1001, configured to report user equipment UE capability information; among them, the UE capability information is used to indicate multiple UE processing times of the UE;

[0279] An information receiving module 1002, configured to receive a first indication information; among them, the first indication information is used to indicate the transmission period of the data;

[0280] An ability determination module 1003, configured to determine a target UE processing time among multiple UE processing times according to a data transmission period;

[0281] A data transmission module 1004, configured to transmit data based on the target UE processing time.

[0282] It can be understood that the above Figure 9 and Figure 10 The communication device shown is an example. In a specific application, the device can be a terminal device, or a device, module, circuit, or chip configured to be disposed in a terminal device, or a device that can be used in combination with a terminal device. In one design, the modules in the communication device can be hardware circuits, software, or a combination of hardware circuits and software.

[0283] Exemplarily, Figure 11 is one of the schematic diagrams of the framework structure of the communication device provided in an embodiment of the present application. As Figure 11 shown, the communication device 1100 may include:

[0284] An information receiving module 1101, configured to receive user equipment (UE) ability information; wherein, the UE ability information indicates a first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE ability 2.

[0285] Exemplarily, Figure 12 is one of the schematic diagrams of the framework structure of the communication device provided in an embodiment of the present application. As Figure 12 shown, the communication device 1200 may include:

[0286] An information receiving module 1201, configured to receive user equipment (UE) ability information;

[0287] An information sending module 1202, configured to send a first indication information for indicating a data transmission period; and send a second indication information for indicating a period threshold;

[0288] wherein, there is a mapping relationship among the transmission period, the period threshold, and multiple UE capabilities.

[0289] It can be understood that the above Figure 11 and Figure 12The communication device shown is an example. In a specific application, the device can be a network device, or a device, module, circuit, or chip configured to be disposed in a network device, or a device that can be used in matching with a network device. In one design, the module in the device can be a hardware circuit, software, or a combination of a hardware circuit and software.

[0290] Exemplarily, Figure 13 is one of the schematic diagrams of the frame structure of the communication device provided in the embodiments of the present application. As Figure 13 shown, the communication device 1300 includes a processing unit 1310 and a transceiver unit 1320. The communication device 1300 is used to implement the functions of the terminal or the base station in the above method embodiments.

[0291] When the communication device 1300 is used to implement the functions of the terminal in the method embodiments: the transceiver unit 1320 is used to execute the above Figure 9 information reporting module 901, or is used to execute the functions of the information reporting module 1001, the information receiving module 1002, and the data transmission module 1004 in the above Figure 10 , or is used to execute the functions of the information receiving module 1201 and the information sending module 1202 in Figure 11 .

[0292] Exemplarily, Figure 14 is one of the schematic diagrams of the frame structure of the communication device provided in the embodiments of the present application. As Figure 14 shown, the communication device 1400 includes a processor 1410 and an interface circuit 1420. The processor 1410 and the interface circuit 1420 are coupled to each other. It can be understood that the interface circuit 1420 can be a transceiver or an input / output interface. Optionally, the communication device 1400 may further include a memory 1430, which is used to store the instructions executed by the processor 1410, or store the input data required for the processor 1410 to run the instructions, or store the data generated after the processor 1410 runs the instructions.

[0293] When the communication device 1400 is used to implement the functions of the terminal or the base station in the above method embodiments, the processor 1410 is used to implement the functions of the processing unit 1310 in the above Figure 13 , and the interface circuit 1420 is used to implement the functions of the transceiver unit 1320 in the above Figure 13 .

[0294] It can be understood that Figure 13 and Figure 14 are schematic diagrams of the possible structures of the communication device provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal or the base station in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0295] In addition, the present application Figure 3 and Figures 9 to 14 The frameworks respectively shown are, in order to implement the functions of the communication method in the embodiments of the present application, included with the corresponding hardware and / or software modules for performing each function. Combining the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving the 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 in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0296] This embodiment also provides a computer storage medium, in which computer instructions are stored. When the computer instructions run on an electronic device, the electronic device is caused to execute the above related method steps to implement the communication method in the above embodiment.

[0297] This embodiment also provides a computer program product. When the computer program product runs on a computer, the computer is caused to execute the above related steps to implement the communication method in the above embodiment.

[0298] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved by them can refer to the beneficial effects in the corresponding method provided above, and will not be elaborated here.

[0299] Any content of each embodiment of the present application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of the present application.

[0300] Those skilled in the art should be able to realize that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes computer storage media and communication media, where the communication media includes any medium that facilitates the transmission of a computer program from one place to another. The storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0301] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them fall within the protection scope of the present application.

Claims

1. A communication method, characterized in that, The method includes: Reporting user equipment (UE) capability information; Wherein, the UE capability information indicates a first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

2. The method according to claim 1, wherein The first UE processing time includes a first physical downlink shared channel (PDSCH) processing time and / or a first physical uplink shared channel (PUSCH) preparation time; Wherein, the first PDSCH processing time indicates a first quantity, the first quantity being the minimum number of orthogonal frequency division multiplexing (OFDM) symbols of the interval between the end of the last symbol of receiving the PDSCH by the UE and the first uplink symbol of transmitting a physical uplink control channel (PUCCH) carrying a hybrid automatic repeat request - acknowledgement (HARQ - ACK) corresponding to the PDSCH; the first PUSCH preparation time indicates a second quantity, the second quantity being the minimum number of OFDM symbols of the interval between the end of the last symbol of receiving a physical downlink control channel (PDCCH) carrying downlink control information (DCI) for scheduling the PUSCH by the UE and the first uplink symbol of transmitting the PUSCH.

3. The method according to claim 1 or 2, characterized in that, Under the same SCS, the first UE processing time is less than or equal to one - Nth times of the second UE processing time; N is equal to 4 or equal to 2.

4. The method according to claim 2, wherein In the case where the SCS is 30 KHz: The first quantity is less than or equal to 2; and / or, The second quantity is less than or equal to 2.

5. The method according to claim 2, wherein In the case where the SCS is 60 KHz: The first quantity is less than or equal to 5; and / or, The second quantity is less than or equal to 5.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: Transmitting data based on the first UE processing time; wherein, the transmission of the data includes one or more of the following manners: The scheduling manner of the data includes semi - persistent scheduling (SPS) or grant - free (GF) scheduling; The time - domain resource occupied by the demodulation reference signal (DMRS) of the data is located before the time - domain resource occupied by the data; The time - domain resource occupied by the data is less than or equal to 2 OFDM symbols.

7. A communication method, characterized in that, The method includes: Receiving user equipment (UE) capability information; where the UE capability information indicates a first UE processing time; under the same subcarrier spacing (SCS), the first UE processing time is less than a second UE processing time; the second UE processing time is the UE processing time under UE capability 2.

8. The method according to claim 7, wherein The first UE processing time includes a first physical downlink shared channel (PDSCH) processing time and / or a first physical uplink shared channel (PUSCH) preparation time; Wherein, the first PDSCH processing time indicates a first quantity, and the first quantity is the minimum number of Orthogonal Frequency Division Multiplexing (OFDM) symbols of the interval between the end of the last symbol of the received PDSCH and the first uplink symbol of the Physical Uplink Control Channel (PUCCH) that transmits the Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK) corresponding to the PDSCH for the User Equipment (UE); the first PUSCH preparation time indicates a second quantity, and the second quantity is the minimum number of OFDM symbols of the interval between the end of the last symbol of the Physical Downlink Control Channel (PDCCH) that receives the Downlink Control Information (DCI) carrying the scheduling of the PUSCH and the first uplink symbol of the transmitted PUSCH for the UE.

9. The method according to claim 7 or 8, characterized in that Under the same Sub - Carrier Spacing (SCS), the first UE processing time is less than or equal to 1 / N times of the second UE processing time, where N is equal to 4 or equal to 2.

10. The method according to claim 8, wherein When the SCS is 30 KHz: The first quantity is less than or equal to 2; and / or, The second quantity is less than or equal to 2.

11. The method according to claim 8, wherein When the SCS is 60 KHz: The first quantity is less than or equal to 5; and / or, The second quantity is less than or equal to 5.

12. The method according to any one of claims 7 to 11, characterized in that, The method further includes: transmitting data based on the first UE processing time; The transmission of the data includes one or more of the following manners: The scheduling manner of the data includes Semi - Persistent Scheduling (SPS) or Grant - Free (GF) scheduling; The time - domain resource occupied by the Demodulation Reference Signal (DMRS) of the data is located before the time - domain resource occupied by the data; The time - domain resource occupied by the data is less than or equal to 2 OFDM symbols.

13. A communication device, characterized in that, It includes a unit or module for executing the method according to any one of claims 1 - 12.

14. A communication device, characterized in that, It includes: A processor and a storage medium; The processor is connected to the storage medium; The storage medium is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 12.

15. A communication device includes a processor, and the processor is used to process data and / or information so that the method according to any one of claims 1 to 12 is implemented.

16. A computer-readable storage medium, characterized in that, It includes instructions, and is characterized in that when the instructions are run by a processor, the method according to any one of claims 1 to 12 is implemented.

17. A chip, characterized in that, It includes one or more processors; when the processors run programs or instructions, the method according to any one of claims 1 to 12 is implemented.

18. A computer program product, characterized in that, It includes computer program code or instructions, and when the computer program code or instructions are run, the method according to any one of claims 1 to 12 is implemented.

Images