Communication method and apparatus therefor

By determining the matching scheduling policy and delay settings between the base station and the terminal, the problem of mismatch between the processing capabilities of the base station and the eRedCap terminal is solved, and the communication performance and processing capabilities are improved.

WO2024239288A1PCT designated stage expired Publication Date: 2024-11-28BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/096115
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-24
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

Some scheduling strategies of the base station do not match the processing capabilities of the eRedCap terminal, resulting in a degradation of communication performance.

Method used

By determining the scheduling policy, the first delay is set according to the protocol agreement, including the PDSCH processing delay, ensuring that the scheduling policy matches the capabilities of the terminal, such as allowing back-to-back scheduling or introducing additional processing delays to override the additional processing delays of the eRedCap terminal.

Benefits of technology

Improve communication performance, avoid the negative impact of PDSCH processing delay on communication capabilities, and improve the processing capability of the terminal.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023096115_28112024_PF_FP_ABST
    Figure CN2023096115_28112024_PF_FP_ABST
Patent Text Reader

Abstract

A communication method and an apparatus therefor. The method comprises: determining a scheduling policy, and according to a protocol agreement, determining a first delay corresponding to the scheduling policy, wherein the first delay comprises a physical downlink shared channel (PDSCH) processing delay. The method can solve the problem of certain scheduling policies of base stations being not matched with processing capabilities of eRedCap terminals, and prevent the impact on the PDSCH processing delay, ensuring the communication performance, and improving the communication capability.
Need to check novelty before this filing date? Find Prior Art

Description

A communication method and device thereof Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method and apparatus thereof. Background Art

[0002] Enhanced Reduced Capability (eRedCap) terminals have a 5MHz PDSCH channel baseband bandwidth capability. Regarding the PDSCH processing and scheduling timelines for eRedCap terminals, how to avoid the mismatch between certain base station scheduling policies and the processing capabilities of eRedCap terminals remains unresolved.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication method and apparatus thereof to solve the problem of mismatch between certain scheduling strategies of a base station and the processing capabilities of an eRedCap terminal, thereby improving communication performance.

[0005] A first aspect of the present disclosure provides a communication method, which is executed by a terminal and includes:

[0006] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0007] The first delay includes a downlink physical shared channel PDSCH processing delay.

[0008] In the present disclosure, the terminal is an enhanced reduced capability eRedcap terminal, and determining the scheduling strategy includes:

[0009] Determining the scheduling strategy as the first scheduling strategy,

[0010] The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0011] In the present disclosure, determining the first delay corresponding to the scheduling policy according to the protocol agreement includes:

[0012] It is determined that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal.

[0013] In the present disclosure, the terminal is an enhanced reduced capability eRedcap terminal, and determining the scheduling strategy includes:

[0014] Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is:

[0015] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0016] In the present disclosure, the terminal is an enhanced reduced capability eRedcap terminal, and determining the scheduling strategy includes:

[0017] Determining that the scheduling strategy is a third scheduling strategy,

[0018] The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

[0019] In the present disclosure, according to the protocol, determining the first delay corresponding to the scheduling strategy includes:

[0020] Determine that the first delay is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0021] In the present disclosure, the baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0022] In the present disclosure, when the scheduling strategy is the third scheduling strategy, the method further includes:

[0023] Reading a system message for the first cell;

[0024] Determine a fifth delay, wherein the fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is a scheduling restriction or interruption of a non-eRedCap terminal, and within the fifth delay range, the eRedCap terminal does not send and / or receive signals on a second cell, and the second cell is a current serving cell of the eRedcap terminal.

[0025] In the present disclosure, the terminal is an enhanced reduced capability eRedCap terminal, and the method further includes:

[0026] Based on the first scheduling policy or the second scheduling policy, a first channel and a second channel are received, wherein the first channel is located before the second channel.

[0027] In the present disclosure, for a subcarrier spacing SCS of 15 kHz, the first time interval and / or the fourth time delay is 0.5 ms or 1 ms;

[0028] For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

[0029] In the present disclosure, the method further comprises:

[0030] sending a second message to the network device,

[0031] The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

[0032] In the present disclosure, determining the first delay corresponding to the scheduling policy includes:

[0033] When the scheduling strategy is the second scheduling strategy, determining that the first delay is greater than or equal to the second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction;

[0034] Among them, the second scheduling strategy is:

[0035] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0036] In the present disclosure, the method further comprises:

[0037] receiving a seventh time delay sent by the network device, wherein the seventh time delay is greater than or equal to the first time delay;

[0038] After a seventh time delay after the last symbol of the second channel, a first message is sent to the network device.

[0039] In the present disclosure, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0040] In the present disclosure, the method further comprises:

[0041] Processing of the second channel and preparation of the first message are performed based on the first delay.

[0042] A second aspect of the present disclosure provides a communication method, characterized in that the method is executed by a network device, and the method includes:

[0043] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0044] The first delay includes a downlink physical shared channel PDSCH processing delay.

[0045] In the present disclosure, determining the scheduling strategy includes:

[0046] Determining the scheduling strategy as the first scheduling strategy,

[0047] The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0048] In the present disclosure, determining the first delay corresponding to the scheduling policy according to the protocol agreement includes:

[0049] It is determined that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal.

[0050] In the present disclosure, determining a scheduling strategy includes:

[0051] Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is:

[0052] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0053] In the present disclosure, determining the scheduling strategy includes:

[0054] Determining that the scheduling strategy is a third scheduling strategy,

[0055] The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

[0056] In the present disclosure, according to the protocol, determining the first delay corresponding to the scheduling strategy includes:

[0057] Determine that the first delay is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0058] In the present disclosure, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0059] In the present disclosure, when the scheduling strategy is the third scheduling strategy, the method further includes:

[0060] Sending a system message for the first cell to the terminal;

[0061] Determine a fifth delay, where the fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is a scheduling restriction or interruption of a non-eRedCap terminal, the network device does not schedule transmission and reception for the terminal within the range of the fifth delay, and the network device does not transmit or receive messages from the terminal within the range of the fifth delay.

[0062] In the present disclosure, the method further comprises:

[0063] Based on the first scheduling strategy or the second scheduling strategy, a first channel and a second channel are scheduled, wherein the first channel is located before the second channel.

[0064] In the present disclosure, for a subcarrier spacing SCS of 15 kHz, the first time interval and / or the fourth time delay is 0.5 ms or 1 ms;

[0065] For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

[0066] In the present disclosure, the method further comprises:

[0067] receiving a second message sent by the terminal,

[0068] The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

[0069] In the present disclosure, determining the first delay corresponding to the scheduling policy includes:

[0070] When the scheduling strategy is the second scheduling strategy, determining that the first delay is greater than or equal to the second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction;

[0071] Among them, the second scheduling strategy is:

[0072] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0073] In the present disclosure, the method further comprises:

[0074] Sending a seventh delay to the terminal, where the seventh delay is greater than or equal to the first delay;

[0075] receiving a first message sent by the terminal after a seventh time delay after the last symbol of the second channel.

[0076] In the present disclosure, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0077] A third aspect of the present disclosure provides a communication device, including a processing module, configured to:

[0078] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0079] The first delay includes the downlink physical shared channel PDSCH processing delay.

[0080] A fourth aspect of the present disclosure provides a communication device, including a processing module, configured to:

[0081] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0082] The first delay includes a downlink physical shared channel PDSCH processing delay.

[0083] The fifth aspect embodiment of the present disclosure provides a communication device, including: a transceiver; a memory; a processor, which is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method described in the first aspect embodiment or the second aspect embodiment of the present disclosure.

[0084] The sixth aspect embodiment of the present disclosure provides a computer-readable storage medium for storing instructions, which, when executed, enables the method described in the first aspect embodiment or the second aspect embodiment of the present disclosure to be implemented.

[0085] The seventh aspect embodiment of the present disclosure provides a communication system, characterized in that it includes: a network device and a user equipment UE, wherein the network device is used to execute the method of the first aspect embodiment of the present disclosure; the UE is used to execute the method of the second aspect embodiment of the present disclosure.

[0086] The embodiments of the present disclosure provide a communication method and apparatus thereof, which can solve the problem of mismatch between certain scheduling strategies of the base station and the processing capabilities of the eRedCap terminal, avoid the impact on the processing delay of the PDSCH, ensure communication performance, and improve communication capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0088] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0089] FIG2 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0090] FIG3 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0091] FIG4 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0092] FIG5 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0093] FIG6 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0094] FIG7 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0095] FIG8 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0096] FIG9 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0097] FIG10 is a flow chart of a communication method provided in an embodiment of the present disclosure;

[0098] FIG11 is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0099] FIG12 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0100] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present disclosure;

[0101] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present disclosure;

[0102] FIG15 is a schematic structural diagram of a chip system provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0103] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0104] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0105] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining" For the purpose of brevity and ease of understanding, the terms used herein when characterizing size relationships are "greater than" or "less than", "higher than" or "lower than". However, for those skilled in the art, it can be understood that the term "greater than" also covers the meaning of "greater than or equal to", and "less than" also covers the meaning of "less than or equal to"; the term "higher than" covers the meaning of "higher than or equal to", and "lower than" also covers the meaning of "lower than or equal to".

[0106] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, one network device and one terminal device. The number and configuration of devices shown in Figure 1 are for example purposes only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. The communication system shown in Figure 1 includes, for example, one network device 101 and one terminal device 102.

[0107] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems. For example, long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems. It should also be noted that the side link in the embodiments of the present disclosure can also be referred to as a side link or a direct link.

[0108] The network device 101 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0109] The terminal device 102 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving (self-driving), a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the terminal device.

[0110] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0111] It should be noted that the communication method provided in any embodiment of the present disclosure can be executed alone, or in combination with possible implementation methods in other embodiments, or in combination with any technical solution in related technologies.

[0112] In order to more clearly understand the solutions proposed in the present disclosure, the concepts involved in the present disclosure are first introduced below.

[0113] 1. Terminal's Physical Downlink Shared Channel (PDSCH) processing delay

[0114] The terminal's PDSCH processing delay may include PDSCH decoding delay and Physical Uplink Control Channel (PUCCH) preparation delay. The terminal can only send uplink signals (such as HARQ-ACK feedback) after the PDSCH processing delay.

[0115] T proc,1 represents the PDSCH processing delay, then: T proc,1 =(N1+d 1,1 )(2048+144)·κ2 -μ ·T c (Formula 1)

[0116] Among them, the value of N1 is related to the μ value of the terminal device; there is a corresponding relationship between the μ value and the subcarrier spacing, which is determined according to the subcarrier spacing; d 1,1 Indicates the processing time in a specific case when the PDSCH mapping mode is A or B, T c κ is the basic time unit in the communication system and is defined in clause 4.1 of 3GPP standard TS38.214.

[0117] In other words, the terminal can only provide HARQ-ACK feedback after Tproc,1 after the end of the last PDSCH symbol transmission. In other words, the terminal is required to process the PDSCH and prepare the HARQ feedback delay no longer than Tproc,1, which is the requirement for the terminal's PDSCH processing capability.

[0118] In addition, when the base station indicates the time domain resources for HARQ-ACK feedback, it needs to consider the terminal's PDSCH decoding delay and PUCCH preparation delay. That is, the HARQ-ACK feedback delay corresponding to the PDSCH scheduled by the base station must be greater than or equal to Tproc,1.

[0119] 2. eRedCap Terminal

[0120] eRedCap technology is an enhanced capability reduction technology proposed by 3GPP in the 5G Release 18 phase, based on the RedCap technology introduced in Release 17. eRedCap terminals are also known as Release 18 RedCap terminals. This technology aims to further reduce terminal complexity and costs, while comprehensively improving 5G network quality and coverage. Non-eRedCap UEs can be traditional terminals, such as NReMBB terminals, or Release 17 RedCap terminals.

[0121] 3. eRedCap terminal PDSCH channel bandwidth and latency

[0122] In some examples, for an eRedCap terminal, the PDSCH channel baseband bandwidth capability (excluding the Fast Fourier Transform (FFT) FFT size and the post-FFT buffer) is 5 MHz, and the maximum RF bandwidth is 20 MHz.

[0123] The eRedCap broadcast PDSCH can carry at least one of the following: System Information Block 1 (SIB1), Other System Information (OSI), Paging, and Random Access Response (RAR). The channel bandwidth of these broadcast PDSCHs can reach 20 MHz, exceeding the baseband bandwidth of the eRedCap PDSCH (5 MHz). eRedCap and non-eRedCap terminals share the same broadcast PDSCH.

[0124] In some examples, the eRedCap terminal can receive broadcast PDSCH with a maximum bandwidth of 20 MHz, cache it in the post-FFT buffer, and then perform channel estimation, channel equalization, demodulation and other processing in four times. For SCS of 15 kHz or 30 kHz, the eRedcap terminal processes up to 25 or 12 resource blocks (RB) of data each time, that is, it receives once and processes multiple times.

[0125] For RAR messages, message 3 (msg3) must be fed back. Since the eRedCap terminal needs to perform three additional channel processes for RAR, additional processing delay is introduced for the feedback of msg3. In some examples, the eRedCap terminal may not provide HARQ-ACK feedback for SIB1 / OSI / paging messages.

[0126] 4. Back-to-back scheduling

[0127] In some examples, back-to-back scheduling includes no gap between symbols of two channels scheduled by the network device, or no gap between time slots of two channels. In other words, the symbols or time slots of two channels scheduled by the network device are adjacent.

[0128] In some examples, for legacy terminals, the base station may schedule broadcast PDSCH and unicast PDSCH back-to-back. Back-to-back scheduling does not affect the processing sequence of unicast PDSCH. For eRedCap terminals, since broadcast PDSCH can be received once and processed multiple times, additional processing latency may be introduced, which may further affect the processing latency of the subsequent unicast PDSCH.

[0129] 5. Neighborhood measurement

[0130] When a terminal is in connected state and performing measurements (e.g., neighboring cell measurements), the network device instructs the terminal to read the cell global ID (CGI) of the neighboring cell. The CGI is carried by SIB1, and the terminal needs to read and decode SIB1. However, the terminal can only process the content of one cell at a time. Therefore, when reading or decoding the SIB1 of a neighboring cell or other cells, scheduling restrictions or interruptions will be generated for the current cell (i.e., the current serving cell).

[0131] For eRedCap terminals, since the broadcast PDSCH can be received once and processed multiple times, the terminal may also introduce additional processing delay when reading the SIB1 of the neighboring cell, which will further affect the terminal delay of the current cell.

[0132] To this end, this disclosure proposes a communication solution, specifically a latency determination solution, to address the latency mismatch issue with eRedCap terminals in certain scenarios. For example, this issue is caused by the introduction of additional processing delays in scenarios such as back-to-back scheduling or neighboring cell measurements.

[0133] FIG2 is a flow chart of a communication method provided by an embodiment of the present disclosure. The method is executed by a terminal. In the present disclosure, the terminal may be an eRedcap terminal, an R17 Redcap terminal, a traditional terminal, or other terminals. As shown in FIG2 , the method includes but is not limited to the following steps:

[0134] S201, determine the scheduling strategy.

[0135] In some embodiments, the scheduling policy may refer to a channel scheduling policy of the network device for the terminal, wherein the terminal may determine the scheduling policy and receive the channel scheduled by the network device based on the scheduling policy.

[0136] In some embodiments, the terminal may be an eRedcap terminal. The scheduling policy may allow the network device to schedule eRedcap terminals back-to-back, i.e., there is no time gap between symbols of a first channel and a second channel scheduled by the network device, or there is no time gap between time slots of the first channel and the second channel. In some embodiments, the order of the first channel and the second channel is not restricted, for example, the first channel precedes the second channel, or vice versa.

[0137] In some embodiments, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH, wherein the broadcast PDSCH precedes the unicast PDSCH. In one example, although the scheduling policy allows the network device to perform back-to-back scheduling for the eRedcap terminal, when the first channel precedes the second channel, the network device is restricted from performing back-to-back scheduling.

[0138] In some embodiments, the broadcast PDSCH channel can be an SI channel (i.e., a channel carrying system messages, such as a channel carrying SIB1 messages), an OSI channel (i.e., a channel carrying OSI messages), a paging channel (i.e., a channel carrying paging messages), an RAR channel (i.e., a channel carrying random access response messages), etc., which is not limited in the present disclosure.

[0139] The present disclosure does not limit the types of the first channel and the second channel. For example, the first channel may be an SI channel and the second channel may be a unicast PDSCH channel; or the first channel may be an RAR channel and the second channel may be a unicast PDSCH channel; or the first channel may be a unicast PDSCH channel and the second channel may be any of the above-mentioned broadcast PDSCH channels, and so on.

[0140] In some embodiments, the scheduling policy may be to not allow the network device to schedule the eRedcap terminal back-to-back, that is, there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, and the first time interval is not zero.

[0141] In some embodiments, the size of the first time interval is not limited. Alternatively, in some embodiments, the size of the first time interval may be:

[0142] 1) When the SCS is 15 kHz, the first time interval is 0.5 ms or 1 ms;

[0143] 2) When the SCS is 30 kHz, the value of the first time interval is 0.25 ms or 0.5 ms.

[0144] In some embodiments, the scheduling policy may be to allow scheduling of neighboring cell measurements of the eRedcap terminal. For example, the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not the current serving cell of the eRedcap terminal.

[0145] In some embodiments, the scheduling policy may also be other scheduling policies in addition to the above scheduling policies, such as allowing or not allowing back-to-back scheduling for non-eRedcap terminals, or other scheduling policies for eRedcap terminals, etc., which are not limited in the present disclosure.

[0146] S202: Determine a first delay corresponding to the scheduling strategy.

[0147] In some embodiments, the first delay comprises a PDSCH processing delay.

[0148] In some embodiments, the PDSCH processing delay may include the delay of the terminal performing PDSCH decoding and the delay of the terminal performing PUCCH preparation.

[0149] In some embodiments, the processing delay between the PDSCH and the uplink channel may also include higher-layer processing delays. The higher-layer processing delays may include MAC layer processing delays, such as the processing delays of messages such as Mac CE or RRC setup request at the RRC layer. For example, the processing delay between a message carrying an RAR message and Msg3 may be equal to or greater than the sum of the PDSCH decoding delay, the terminal's PUCCH preparation delay, and the MAC layer processing delay. For example, for a RAR PDSCH, the MAC layer processing delay may be 0.5 ms.

[0150] In some embodiments, the terminal may determine the first delay corresponding to the scheduling policy according to a protocol agreement. In other optional embodiments, the terminal may determine the first delay by other means, such as by the terminal itself through processing, or by the terminal based on certain information received from a network device or other entity, which is not limited by this disclosure.

[0151] In some embodiments, the first delays corresponding to different scheduling strategies may be the same or different.

[0152] Exemplarily, in some embodiments, the scheduling policy is not to allow the network device to perform back-to-back scheduling on the eRedcap terminal, and the first delay may be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol.

[0153] Exemplarily, in some embodiments, the scheduling strategy is to allow the network device to perform back-to-back scheduling for the eRedcap terminal. The first delay may be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol plus an additional delay (additional offset) X, which may cover the additional processing delay of the eRedcap terminal. Exemplarily, the additional delay X may be the delay for the eRedcap terminal to perform baseband processing of the PDSCH N-1 times, where N is the number of baseband processing times of the eRedcap terminal for one PDSCH reception, N is a positive integer and N≥1. Exemplarily, the number of baseband processing times of the eRedcap terminal for one PDSCH reception may be 4 times, and the delay of each processing is N1, then the additional delay X may be 3*N1.

[0154] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0155] Exemplarily, in some embodiments, the scheduling strategy is to allow the network device to perform back-to-back scheduling of eRedcap terminals, and the first delay can be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol. This processing delay can support the eRedcap terminal to perform additional PDSCH baseband processing, for example, the terminal has higher parallel processing capabilities.

[0156] For example, in some embodiments, the scheduling policy allows the network device to schedule cell measurements (e.g., neighboring cell measurements) for the eRedcap terminal. The eRedcap terminal can read system messages for the first cell when performing cell measurements, wherein the first cell is not the current serving cell of the eRedcap terminal, for example, the first cell is a neighboring cell or other cell. The first delay can be the interruption or scheduling restriction of the non-eRedcap terminal determined according to the protocol plus an additional delay (additional offset) X. Within this first delay range, the eRedcap terminal does not transmit and / or receive signals on the second cell, which is the current serving cell of the eRedcap terminal. For example, the additional delay X can be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times the eRedcap terminal performs on a PDSCH reception, N is a positive integer and N≥1. For example, the number of baseband processing times the eRedcap terminal performs on a PDSCH reception can be 4 times, and the delay of each processing is N1, so the additional delay X can be 3*N1. For example, the delay of the eRedCap terminal reading and decoding the neighboring cell SIB1 is 4*N1. The interruption delay for the current serving cell determined by the eRedCap terminal is the interruption or scheduling limit of the non-eRedCap terminal plus 3*N1.

[0157] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0158] In some embodiments of the present disclosure, the terminal may determine the first delay corresponding to the determined scheduling policy based on a protocol agreement, wherein the scheduling policy is not limited by the present disclosure, and similarly, the determined first delay is not limited.

[0159] In summary, according to the solution of the present disclosure, the terminal can determine the scheduling strategy and determine the first delay based on the protocol agreement, which first delay includes the PDSCH processing delay. The solution of the embodiment of the present disclosure solves the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, thereby improving communication performance.

[0160] FIG3 is a flow chart of a communication method provided by an embodiment of the present disclosure, wherein the communication method is performed by a terminal, which is optionally an eRedcap terminal, an R17 Redcap terminal, a traditional terminal, or other terminals. Based on the embodiment shown in FIG2 , as shown in FIG3 , the method includes but is not limited to the following steps:

[0161] S301: Determine that the scheduling strategy is the first scheduling strategy.

[0162] In some embodiments, the terminal may be an eRedcap terminal, and the first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0163] In other words, the first scheduling policy is not to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0164] In some embodiments, the first time interval may be any value. Optionally, the first time interval may be set in any of the following ways:

[0165] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0166] 2) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0167] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0168] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0169] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0170] In some embodiments, the value of the first time interval may be the delay of the eRedcap terminal performing baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, and N is a positive integer and N≥1.

[0171] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0172] For example, the eRedcap terminal performs baseband processing four times for one PDSCH reception, and the delay of each baseband processing is N1. Then, the value of the first time interval may be 3*N1.

[0173] S302: Determine whether the first delay is greater than or equal to the second delay.

[0174] In some embodiments, the terminal may determine that the first delay is greater than or equal to the second delay according to a protocol agreement. For example, the terminal may determine the second delay according to a protocol agreement, and determine the first delay according to the second delay.

[0175] In some embodiments, the second delay reduces the PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capabilities.

[0176] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0177] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0178] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal as the PDSCH channel processing delay of the eRedcap terminal.

[0179] In some embodiments, since there is a time interval between the first channel and the second channel, the time interval can cover the additional processing delay of the eRedcap terminal, so the eRedcap terminal can still use the PDSCH channel processing delay of the non-eRedcap terminal without introducing additional processing delay.

[0180] S303: Receive the first channel and the second channel based on the first scheduling strategy.

[0181] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0182] In some embodiments, the eRedcap terminal can receive the scheduled first channel and the second channel. In other words, the eRedcap terminal can receive signaling or information carried by the first channel and the second channel.

[0183] S304: Process the second channel and prepare the first message based on the first delay.

[0184] In some embodiments, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0185] Since there is a first time interval between the first channel and the second channel, there is no need to introduce additional processing delay in the first delay. Therefore, the eRedcap terminal can process the second channel and prepare the first message based on the PDSCH processing delay of the non-eRedcap terminal, avoiding the impact of the additional processing delay of the eRedcap terminal on the first channel on the processing of the second channel and the preparation of the first message.

[0186] S305: Receive the seventh delay sent by the network device.

[0187] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0188] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0189] In this embodiment, K1>=Tproc,1.

[0190] Where Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal.

[0191] In some embodiments, a terminal may receive DCI signaling sent by a network device, where the DCI signaling includes the seventh delay. In other words, the seventh delay may be carried by the DCI signaling. The seventh delay may also be carried by other downlink signaling, which is not limited by this disclosure.

[0192] S306: Send a first message to the network device after the seventh time delay after the last symbol of the second channel.

[0193] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0194] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0195] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0196] In some embodiments, the terminal may support reporting capability information to the network device. For example, the terminal may send a second message to the network device, wherein the second message is used to indicate whether the terminal has a first capability, where the first capability is the ability to support back-to-back scheduling.

[0197] In this embodiment, since the scheduling policy does not allow network devices to schedule eRedcap terminals back-to-back, it means that there is a time interval between the first channel and the second channel scheduled by the network device. This time interval can cover the additional processing delay of the eRedcap terminal when performing PDSCH processing. The additional processing delay of the eRedcap terminal for the broadcast PDSCH will not affect the subsequent unicast PDSCH and the sending of feedback signals to the network device, thereby solving the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capabilities, avoiding problems with back-to-back scheduling between the eRedCap terminal broadcast PDSCH and unicast PDSCH, and thus improving communication performance.

[0198] FIG4 is a flow chart of a communication method provided by an embodiment of the present disclosure, wherein the communication method is performed by a terminal. Optionally, the terminal is an eRedcap terminal, an R17 Redcap terminal, a traditional terminal, or other terminals. Based on the embodiment shown in FIG2 , as shown in FIG4 , the method includes but is not limited to the following steps:

[0199] S401: Determine that the scheduling strategy is the second scheduling strategy.

[0200] In some embodiments, the terminal may be an eRedcap terminal, and the second scheduling strategy is:

[0201] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0202] In other words, the second scheduling policy is to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0203] S402: Determine whether the first delay is greater than or equal to the third delay.

[0204] In some embodiments, the terminal may determine that the first delay is greater than or equal to the third delay according to a protocol agreement. For example, the terminal may determine the third delay according to a protocol agreement, and determine the first delay according to the third delay.

[0205] In some embodiments, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform N-1 baseband processing of PDSCH, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0206] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0207] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0208] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0209] In some embodiments, the fourth delay may be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times performed by the eRedcap terminal for one PDSCH reception, and N is a positive integer and N ≥ 1. For example, if the eRedcap terminal performs baseband processing of one PDSCH reception four times and the delay of each baseband processing is N1, the value of the fourth delay may be 3*N1.

[0210] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0211] In some embodiments, the fourth time delay may be any value. Alternatively, the fourth time delay may be any value as follows:

[0212] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0213] 3) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0214] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0215] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0216] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0217] In some embodiments, the eRedcap terminal may determine the sum of the PDSCH channel processing delay (ie, the second delay) of the non-eRedcap terminal and the additional delay X (ie, the fourth delay) as the PDSCH channel processing delay of the eRedcap terminal.

[0218] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device schedules the eRedcap terminal back-to-back, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to schedule the eRedcap terminal back-to-back, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, an additional delay (i.e., the fourth delay mentioned above) is introduced to cover the additional processing delay of the eRedcap terminal, thereby avoiding the delay mismatch problem of the eRedcap terminal in certain scenarios. For example, the mismatch between back-to-back scheduling and the capabilities of the eRedcap terminal.

[0219] S403: Receive the first channel and the second channel based on the second scheduling strategy.

[0220] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0221] In some embodiments, the eRedcap terminal can receive the first channel and the second channel of the back-to-back scheduling. In other words, the eRedcap terminal can receive the signaling or information carried by the first channel and the second channel.

[0222] S404: Process the second channel and prepare the first message based on the first delay.

[0223] In some embodiments, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0224] In other words, an additional delay (i.e., the fourth delay mentioned above) is introduced into the first delay, and the eRedcap terminal can process the second channel based on the first delay. In other words, the second channel processing is performed after the PDSCH processing delay of the non-eRedcap terminal is added with the additional delay, so as to avoid the additional processing delay of the eRedcap terminal affecting the processing of the second channel, and prepare the first information for subsequent sending to the network device.

[0225] S405: Receive the seventh delay sent by the network device.

[0226] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0227] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0228] In this embodiment, K1>=Tproc,1+additional offset X.

[0229] Here, Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal, and additional offset X represents the fourth delay.

[0230] In some embodiments, a terminal may receive DCI signaling sent by a network device, where the DCI signaling includes the seventh delay. In other words, the seventh delay may be carried by the DCI signaling. The seventh delay may also be carried by other downlink signaling, which is not limited by this disclosure.

[0231] S406: Send a first message to the network device after the seventh time delay after the last symbol of the second channel.

[0232] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0233] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0234] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0235] In some embodiments, the terminal may support reporting capability information to the network device. For example, the terminal may send a second message to the network device, wherein the second message is used to indicate whether the terminal has a first capability, where the first capability is the ability to support back-to-back scheduling.

[0236] In this embodiment, since the scheduling policy is to allow the network device to schedule the eRedcap terminal back-to-back, it means that there is no time interval between the first channel and the second channel scheduled by the network device. In order to avoid the additional processing delay of the eRedcap terminal for the broadcast PDSCH affecting the subsequent unicast PDSCH and the signal sending to the network device, an additional delay X (i.e., the fourth delay) is introduced to solve the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, avoid problems with back-to-back scheduling between the eRedCap terminal broadcast PDSCH and unicast PDSCH, and thus improve communication performance.

[0237] FIG5 is a flow chart of a communication method provided by an embodiment of the present disclosure, wherein the communication method is executed by a terminal. Optionally, the terminal is an eRedcap terminal, an R17 Redcap terminal, a traditional terminal, or other terminals. Based on the embodiment shown in FIG2 , as shown in FIG5 , the method includes but is not limited to the following steps:

[0238] S501: Determine that the scheduling strategy is the third scheduling strategy.

[0239] In some embodiments, the terminal may be an eRedcap terminal, and the third scheduling strategy is:

[0240] The eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

[0241] In other words, the third scheduling strategy is to allow neighboring cell measurement scheduling of the eRedcap terminal.

[0242] When a terminal is in connected state and performing measurements (e.g., neighboring cell measurements), the network device instructs the terminal to read the cell global ID (CGI) of the neighboring cell. The CGI is carried by SIB1, and the terminal needs to read and decode SIB1. However, the terminal can only process the content of one cell at a time. Therefore, when reading or decoding the SIB1 of a neighboring cell or other cells, scheduling restrictions or interruptions will be generated for the current cell (i.e., the current serving cell).

[0243] For eRedCap terminals, since the broadcast PDSCH can be received once and processed multiple times, the terminal may also introduce additional processing delay when reading the SIB1 of the neighboring cell, which will further affect the terminal delay of the current cell.

[0244] S502: Determine whether the first delay is greater than or equal to the third delay.

[0245] In some embodiments, the terminal may determine that the first delay is greater than or equal to the third delay according to a protocol agreement. For example, the terminal may determine the third delay according to a protocol agreement, and determine the first delay according to the third delay.

[0246] In some embodiments, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform N-1 baseband processing of PDSCH, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0247] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0248] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0249] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0250] In some embodiments, the fourth delay may be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times performed by the eRedcap terminal for one PDSCH reception, and N is a positive integer and N ≥ 1. For example, if the eRedcap terminal performs baseband processing of one PDSCH reception four times and the delay of each baseband processing is N1, the value of the fourth delay may be 3*N1.

[0251] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0252] In some embodiments, the fourth time delay may be any value. Alternatively, the fourth time delay may be any value as follows:

[0253] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0254] 2) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0255] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0256] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0257] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0258] In some embodiments, the eRedcap terminal may determine the sum of the PDSCH channel processing delay (ie, the second delay) of the non-eRedcap terminal and the additional delay X (ie, the fourth delay) as the PDSCH channel processing delay of the eRedcap terminal.

[0259] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device schedules the eRedcap terminal back-to-back, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to schedule the eRedcap terminal back-to-back, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, an additional delay (i.e., the fourth delay mentioned above) is introduced to cover the additional processing delay of the eRedcap terminal, thereby avoiding the delay mismatch problem of the eRedcap terminal in certain scenarios. For example, the mismatch between back-to-back scheduling and the capabilities of the eRedcap terminal.

[0260] S503: Read the system message for the first cell.

[0261] In some embodiments, the first cell is a non-serving cell of the eRedcap terminal, or in other words, the first cell is not the current serving cell of the eRedcap terminal. For example, the first cell may be a neighboring cell or other cell of the current serving cell of the eRedcap terminal.

[0262] When performing cell measurement, such as performing neighboring cell measurement, the eRedcap terminal may read the system information of the neighboring cell, for example, read the SIB1 of the neighboring cell.

[0263] S504: Determine a fifth time delay.

[0264] In some embodiments, the eRedcap terminal may determine the fifth delay based on the first delay.

[0265] The fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is the scheduling restriction or interruption of the non-eRedCap terminal, and within the range of the fifth delay, the eRedCap terminal does not send and / or receive signals on the second cell, and the second cell is the current serving cell of the eRedcap terminal.

[0266] In other words, since the terminal can only process the content of one cell at the same time, when the eRedcap terminal reads the system message of the neighboring cell, the service of the current serving cell will be scheduled restricted or interrupted. Since the eRedcap terminal still receives and processes multiple times when reading and decoding the neighboring cell SIB1, additional processing delay is still introduced. This additional processing delay will affect the scheduling restriction or interruption of the serving cell.

[0267] S505: After the fifth delay, transmit and / or receive signals on the second cell.

[0268] In some embodiments, since the eRedcap terminal does not send and / or receive signals on the second cell (ie, the current serving cell) within the fifth time delay range, the eRedcap terminal may resume signal transmission and reception on the current serving cell after the fifth time delay.

[0269] In this embodiment, since the scheduling strategy is cell measurement scheduling, it means that when the eRedcap terminal reads the neighboring cell system message during the neighboring cell measurement process, it will affect the scheduling restriction or interruption of the current cell. In order to avoid the additional processing delay of the eRedcap terminal for the neighboring cell system message from affecting the scheduling restriction or interruption of the current cell, an additional delay X (i.e., the fourth delay) is introduced to solve the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, thereby improving communication performance.

[0270] FIG6 is a flow chart of a communication method provided by an embodiment of the present disclosure, wherein the communication method is executed by a terminal, optionally an eRedcap terminal. Based on the embodiment shown in FIG2 , as shown in FIG6 , the method includes but is not limited to the following steps:

[0271] S601, sending a second message to the network device,

[0272] In some embodiments, the terminal may be an eRedcap terminal.

[0273] The second message is used to indicate whether the terminal has a first capability, where the first capability is a capability of supporting back-to-back scheduling.

[0274] In some embodiments, the eRedCap terminal may also support additional reporting signaling to indicate to the base station whether it is capable of supporting back-to-back scheduling.

[0275] S602: Determine that the scheduling strategy is the second scheduling strategy.

[0276] The second scheduling strategy is:

[0277] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0278] In other words, the second scheduling policy is to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0279] In some embodiments, in step S602, the eRedcap terminal may indicate to the network device that it supports back-to-back scheduling, and when the network device performs back-to-back scheduling on the eRedcap terminal, the following steps may be performed.

[0280] S603: Determine whether the first delay is greater than or equal to the second delay.

[0281] In some embodiments, the terminal may determine that the first delay is greater than or equal to the second delay according to a protocol agreement. For example, the terminal may determine the second delay according to a protocol agreement, and determine the first delay according to the second delay.

[0282] In some embodiments, the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction.

[0283] In other words, eRedcap terminals can have additional processing capabilities to support back-to-back scheduling, such as higher parallel processing capabilities, which can support eRedcap terminals without introducing additional processing delays while still covering the additional processing delays of eRedcap terminals. If the terminal has additional PDSCH baseband processing capabilities, the eRedcap terminal does not need to introduce additional delays and will not affect back-to-back scheduling.

[0284] In other words, the eRedcap terminal can support additional reporting signaling, such as the terminal has additional parallel processing capabilities, such as the terminal has additional pipelines capable of parallel processing. For the additional broadcast PDSCH transmission of the eRedcap terminal, PDSCH decoding and PUCCH preparation can still be performed within the PDSCH channel processing delay of the non-eRedcap terminal without introducing additional delay.

[0285] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal as the PDSCH channel processing delay of the eRedcap terminal.

[0286] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device performs back-to-back scheduling on the eRedcap terminal, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to perform back-to-back scheduling on the eRedcap terminal, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, since the terminal reports its own capabilities to the base station, it can perform PDSCH decoding and PUCCH preparation within the PDSCH processing delay of the non-eRedcap terminal, and will not affect the subsequent second channel and the information feedback to the network device, thereby avoiding the delay mismatch problem of the eRedcap terminal in certain scenarios. For example, the mismatch problem with the eRedcap terminal capabilities in scenarios such as back-to-back scheduling.

[0287] S604: Receive the first channel and the second channel based on the second scheduling strategy.

[0288] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0289] In some embodiments, the eRedcap terminal can receive the first channel and the second channel of the back-to-back scheduling. In other words, the eRedcap terminal can receive the signaling or information carried by the first channel and the second channel.

[0290] S605: Process the second channel and prepare the first message based on the first delay.

[0291] In some embodiments, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0292] In other words, the eRedcap terminal can process the second channel based on the PDSCH processing delay of the non-eRedcap terminal. In other words, the second channel processing is performed after the PDSCH processing delay of the non-eRedcap terminal. Since the eRedcap terminal has certain processing capabilities, such as higher parallel processing capabilities, it can perform multiple processing of the eRedcap terminal within the PDSCH processing delay of the non-eRedcap terminal, avoiding the impact of the extra processing delay of the eRedcap terminal on the processing of the second channel, and prepare the first information for subsequent sending to the network device.

[0293] S606: Receive the seventh delay sent by the network device.

[0294] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0295] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0296] In this embodiment, K1>=Tproc,1.

[0297] Where Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal.

[0298] In some embodiments, a terminal may receive DCI signaling sent by a network device, where the DCI signaling includes the seventh delay. In other words, the seventh delay may be carried by the DCI signaling. The seventh delay may also be carried by other downlink signaling, which is not limited by this disclosure.

[0299] S607: Send a first message to the network device after the seventh delay after the last symbol of the second channel.

[0300] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0301] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0302] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0303] In this embodiment, since the scheduling strategy allows network devices to perform back-to-back scheduling of eRedcap terminals and supports terminals to report capability information to network devices, when the terminal capability can cover the additional processing delay of the eRedcap terminal and no additional delay is introduced, the eRedcap terminal can also perform multiple PDSCH processing within the PDSCH processing delay of the non-eRedcap terminal, thereby avoiding the additional processing delay of the eRedcap terminal for the broadcast PDSCH affecting the subsequent unicast PDSCH and the sending of signals to the network device, thereby solving the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, avoiding problems with back-to-back scheduling between the eRedCap terminal's broadcast PDSCH and unicast PDSCH, and improving communication performance.

[0304] In some embodiments of the present disclosure, the communication method may be executed by a terminal, such as an eRedcap terminal, and the communication method may include the following steps:

[0305] A first delay is determined, where the first delay corresponds to a scheduling policy of the network device.

[0306] In some examples, the first delay may include a PDSCH processing delay.

[0307] In some examples, the first delay corresponding to each scheduling strategy is agreed upon by a protocol. In other words, the first delay corresponding to each scheduling strategy can be agreed upon by the protocol. For example, the terminal can determine the first delay corresponding to each scheduling strategy according to the protocol agreement.

[0308] For example, when the scheduling policy is such that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first delay corresponding to the scheduling policy is greater than or equal to the second delay, where the second delay is the PDSCH channel processing delay of the non-eRedcap terminal. The first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0309] For another example, when the scheduling policy is to allow the network device to schedule the eRedcap terminal back-to-back, the first delay corresponding to the scheduling policy is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of the eRedcap terminal for one PDSCH reception, N is a positive integer and N≥1. The back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0310] For another example, when the scheduling policy is for an eRedcap terminal to read a system message for a first cell during cell measurement, the first delay corresponding to the scheduling policy is greater than or equal to the third delay, and the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, and N is a positive integer and N ≥ 1. The first cell is not the current serving cell of the eRedcap terminal.

[0311] For another example, when the scheduling policy allows the network device to perform back-to-back scheduling of eRedcap terminals, the first delay corresponding to the scheduling policy is greater than or equal to the second delay, where the second delay is the PDSCH channel processing delay for non-eRedCap terminals with non-enhanced capability reduction. The back-to-back scheduling means that there is no time interval between symbols of a first channel and a second channel scheduled by the network device, or there is no time interval between time slots of the first channel and the second channel, where the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0312] It should be understood that the steps of this embodiment can be implemented individually or in combination with the steps of other embodiments, and this disclosure is not limited to this.

[0313] In the communication method disclosed herein, the terminal may determine a first delay corresponding to a scheduling policy of a network device to resolve a problem in which certain scheduling policies of a base station do not match the processing capability of the terminal, thereby improving communication performance.

[0314] Figure 7 is a flow chart of a communication method provided by an embodiment of the present disclosure. The method is executed by a network device. In the present disclosure, the network device may be an access network device or a core network device. The present disclosure does not limit the specific device model and quantity.

[0315] As shown in FIG7 , the method includes but is not limited to the following steps:

[0316] S701: Determine a scheduling strategy.

[0317] In some embodiments, the scheduling policy may refer to a channel scheduling policy of a network device for a terminal, wherein the network device may determine the scheduling policy and perform channel scheduling based on the scheduling policy.

[0318] In some embodiments, the terminal may be an eRedcap terminal.

[0319] In some embodiments, the scheduling policy may be to allow the network device to schedule eRedcap terminals back-to-back, i.e., there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel.

[0320] In some embodiments, the order of the first channel and the second channel may not be limited, for example, the first channel is before the second channel, or the second channel is before the first channel.

[0321] In some embodiments, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH, wherein the broadcast PDSCH precedes the unicast PDSCH. In one example, although the scheduling policy allows the network device to perform back-to-back scheduling for the eRedcap terminal, when the first channel precedes the second channel, the network device is restricted from performing back-to-back scheduling.

[0322] In some embodiments, the broadcast PDSCH channel can be an SI channel (i.e., a channel carrying system messages, such as a channel carrying SIB1 messages), an OSI channel (i.e., a channel carrying OSI messages), a paging channel (i.e., a channel carrying paging messages), an RAR channel (i.e., a channel carrying random access response messages), etc., which is not limited in the present disclosure.

[0323] The present disclosure does not limit the types of the first channel and the second channel. For example, the first channel may be an SI channel and the second channel may be a unicast PDSCH channel; or the first channel may be an RAR channel and the second channel may be a unicast PDSCH channel; or the first channel may be a unicast PDSCH channel and the second channel may be any of the above-mentioned broadcast PDSCH channels, and so on.

[0324] In some embodiments, the scheduling policy may be to not allow the network device to schedule eRedcap terminals back-to-back, that is, there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminals, and the first time interval is not zero.

[0325] In some embodiments, the size of the first time interval is not limited. Alternatively, in some embodiments, the size of the first time interval may be:

[0326] 1) When the SCS is 15 kHz, the first time interval is 0.5 ms or 1 ms;

[0327] 2) When the SCS is 30 kHz, the value of the first time interval is 0.25 ms or 0.5 ms.

[0328] In some embodiments, the scheduling policy may be to allow scheduling of neighboring cell measurements of the eRedcap terminal. For example, the network device sends a system message for the first cell to the eRedcap terminal. In other words, the eRedcap terminal reads the system message for the first cell when performing cell measurement, wherein the first cell is not the current serving cell of the eRedcap terminal.

[0329] In some embodiments, the scheduling policy may also be other scheduling policies in addition to the above scheduling policies, such as allowing or not allowing back-to-back scheduling for non-eRedcap terminals, or other scheduling policies for eRedcap terminals, etc., which are not limited in the present disclosure.

[0330] S702: Determine a first delay corresponding to the scheduling policy.

[0331] In some embodiments, the first delay comprises a PDSCH processing delay.

[0332] In some embodiments, the PDSCH processing delay may include the delay of the terminal performing PDSCH decoding and the delay of the terminal performing PUCCH preparation.

[0333] In some embodiments, the processing delay between the PDSCH and the uplink channel may also include higher-layer processing delay. The higher-layer processing delay may be MAC layer processing delay, such as the processing delay of messages such as MAC CE or RRC setup request at the RRC layer. For example, the processing delay between a message carrying an RAR message and Msg3 may be the sum of the PDSCH decoding delay, the terminal's PUCCH preparation delay, and the MAC layer processing delay. For example, for a RAR PDSCH, the MAC layer processing delay may be 0.5 ms.

[0334] In some embodiments, the network device may determine the first delay corresponding to the scheduling policy according to a protocol agreement. In other optional embodiments, the network device may determine the first delay by other means, such as by the network device itself through processing, or based on certain information received from a terminal or other subject, which is not limited by this disclosure.

[0335] In some embodiments, the first delays corresponding to different scheduling strategies may be the same or different.

[0336] Exemplarily, in some embodiments, the scheduling policy is not to allow the network device to perform back-to-back scheduling on the eRedcap terminal, and the first delay may be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol.

[0337] Exemplarily, in some embodiments, the scheduling strategy is to allow the network device to perform back-to-back scheduling for the eRedcap terminal. The first delay may be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol plus an additional delay (additional offset) X, which may cover the additional processing delay of the eRedcap terminal. Exemplarily, the additional delay X may be the delay for the eRedcap terminal to perform baseband processing of the PDSCH N-1 times, where N is the number of baseband processing times of the eRedcap terminal for one PDSCH reception, N is a positive integer and N≥1. Exemplarily, the number of baseband processing times of the eRedcap terminal for one PDSCH reception may be 4 times, and the delay of each processing is N1, then the additional delay X may be 3*N1.

[0338] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0339] For example, in some embodiments, the scheduling policy allows the network device to perform back-to-back scheduling for eRedcap terminals. The first delay may be the PDSCH processing delay of the non-eRedcap terminal determined according to the protocol. This processing delay may support the eRedcap terminal to perform additional PDSCH baseband processing, for example, if the terminal has higher parallel processing capabilities. The network device may first receive capability information from the terminal, which may indicate whether the terminal has parallel processing capabilities.

[0340] Exemplarily, in some embodiments, the scheduling policy is to allow the eRedcap terminal to perform cell measurement (e.g., neighboring cell measurement) scheduling. The network device can send a system message for the first cell to the eRedcap terminal, and the eRedcap terminal can read the system message for the first cell when performing cell measurement, wherein the first cell is not the current serving cell of the eRedcap terminal, for example, the first cell is a neighboring cell or other cell. Then the first delay can be the scheduling restriction or interruption of the non-eRedCap terminal determined according to the protocol plus an additional delay (additional offset) X. Within the first delay range, the network device does not perform transmission and reception scheduling for the terminal, and the network device does not send or receive messages from the terminal. The second cell is the current serving cell of the eRedcap terminal. Exemplarily, the additional delay X can be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times received by the eRedcap terminal for one PDSCH, N is a positive integer and N≥1. For example, the eRedCap terminal may perform four baseband processing operations for a PDSCH reception, with each processing delay being N1. The additional delay X can be 3*N1. For example, the delay for an eRedCap terminal to read and decode the neighboring cell SIB1 is 4*N1. The terminal delay for the current serving cell determined by the eRedCap terminal is the scheduling restriction or interruption of the non-eRedCap terminal plus 3*N1.

[0341] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0342] In some embodiments of the present disclosure, the network device may determine the first delay corresponding to the determined scheduling policy based on the protocol agreement according to the determined scheduling policy, wherein the present disclosure does not limit the scheduling policy, and similarly does not limit the determined first delay.

[0343] In summary, according to the solution disclosed in the present invention, the network device can determine the scheduling strategy and determine the first delay based on the protocol agreement, where the first delay includes the PDSCH processing delay. The solution of the embodiment of the present invention solves the problem of mismatch between certain scheduling strategies of the network device and the terminal processing capabilities, thereby improving communication performance.

[0344] FIG8 is a flow chart of a communication method provided in an embodiment of the present disclosure. The communication method is performed by a network device. Based on the embodiment shown in FIG7 , as shown in FIG8 , the method includes but is not limited to the following steps:

[0345] S801: Determine that the scheduling strategy is the first scheduling strategy.

[0346] The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0347] In other words, the first scheduling policy is not to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0348] In some embodiments, the first time interval may be any value. Optionally, the first time interval may be set in any of the following ways:

[0349] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0350] 2) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0351] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0352] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0353] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0354] In some embodiments, the value of the first time interval may be the delay of the eRedcap terminal performing baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, and N is a positive integer and N≥1.

[0355] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0356] For example, the eRedcap terminal performs baseband processing four times for one PDSCH reception, and the delay of each baseband processing is N1. Then, the value of the first time interval may be 3*N1.

[0357] S802: Determine whether the first delay is greater than or equal to the second delay.

[0358] In some embodiments, the network device may determine that the first delay is greater than or equal to the second delay according to a protocol agreement. For example, the network device may determine the second delay according to a protocol agreement, and determine the first delay according to the second delay.

[0359] In some embodiments, the second delay reduces the PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capabilities.

[0360] In some embodiments, the eRedcap terminal may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0361] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0362] In some embodiments, the network device may determine the PDSCH channel processing delay for the non-eRedcap terminal as the PDSCH channel processing delay for the eRedcap terminal.

[0363] In some embodiments, since there is a time interval between the first channel and the second channel, the time interval can cover the additional processing delay of the eRedcap terminal, so the eRedcap terminal can still use the PDSCH channel processing delay of the non-eRedcap terminal without introducing additional processing delay.

[0364] S803 : Schedule the first channel and the second channel based on the first scheduling policy.

[0365] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0366] In some embodiments, the eRedcap terminal may schedule the first channel and the second channel.

[0367] In some embodiments, the first delay may be used for the terminal to process the second channel and prepare the first message.

[0368] In some embodiments, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0369] Since there is a first time interval between the first channel and the second channel, there is no need to introduce additional processing delay in the first delay. Therefore, the eRedcap terminal can process the second channel and prepare the first message based on the PDSCH processing delay of the non-eRedcap terminal, avoiding the impact of the additional processing delay of the eRedcap terminal on the first channel on the processing of the second channel and the preparation of the first message.

[0370] S804: Send the seventh delay to the terminal.

[0371] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0372] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0373] In this embodiment, K1>=Tproc,1.

[0374] Where Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal.

[0375] In some embodiments, the network device sends DCI signaling to the terminal, and the DCI signaling includes the seventh delay. In other words, the seventh delay can be carried by the DCI signaling. The seventh delay can also be carried by other downlink signaling, which is not limited by this disclosure.

[0376] S805: Receive a first message sent by the terminal after the seventh time delay after the last symbol of the second channel.

[0377] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0378] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0379] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0380] In some embodiments, the terminal may support reporting capability information to the network device. For example, the network device may receive a second message sent by the terminal, wherein the second message is used to indicate whether the terminal has a first capability, where the first capability is the ability to support back-to-back scheduling.

[0381] In this embodiment, since the scheduling policy does not allow network devices to schedule eRedcap terminals back-to-back, it means that there is a time interval between the first channel and the second channel scheduled by the network device. This time interval can cover the additional processing delay of the eRedcap terminal when performing PDSCH processing. The additional processing delay of the eRedcap terminal for the broadcast PDSCH will not affect the subsequent unicast PDSCH and the sending of feedback signals to the network device, thereby solving the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capabilities, avoiding problems with back-to-back scheduling between the eRedCap terminal broadcast PDSCH and unicast PDSCH, and thus improving communication performance.

[0382] FIG9 is a flow chart of a communication method provided by an embodiment of the present disclosure, the communication method being executed by a network device. Based on the embodiment shown in FIG7 , as shown in FIG9 , the method includes but is not limited to the following steps:

[0383] S901: Determine that the scheduling strategy is the second scheduling strategy.

[0384] The second scheduling strategy is:

[0385] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0386] In other words, the second scheduling policy is to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0387] S902: Determine whether the first delay is greater than or equal to the third delay.

[0388] In some embodiments, the network device may determine that the first delay is greater than or equal to the third delay according to a protocol agreement. For example, the network device may determine the third delay according to a protocol, and determine the first delay based on the third delay.

[0389] In some embodiments, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform N-1 baseband processing of PDSCH, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0390] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0391] In some embodiments, the network device may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0392] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0393] In some embodiments, the fourth delay may be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times performed by the eRedcap terminal for one PDSCH reception, and N is a positive integer and N ≥ 1. For example, if the eRedcap terminal performs baseband processing of one PDSCH reception four times and the delay of each baseband processing is N1, the value of the fourth delay may be 3*N1.

[0394] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0395] In some embodiments, the fourth time delay may be any value. Alternatively, the fourth time delay may be any value as follows:

[0396] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0397] 3) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0398] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0399] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0400] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0401] In some embodiments, the network device may determine the sum of the PDSCH channel processing delay (ie, the second delay) of the non-eRedcap terminal and the additional delay X (ie, the fourth delay) as the PDSCH channel processing delay of the eRedcap terminal.

[0402] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device schedules the eRedcap terminal back-to-back, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to schedule the eRedcap terminal back-to-back, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, an additional delay (i.e., the fourth delay mentioned above) is introduced to cover the additional processing delay of the eRedcap terminal, thereby avoiding the delay mismatch problem of the eRedcap terminal in certain scenarios. For example, the mismatch problem between back-to-back scheduling and the capabilities of the eRedcap terminal.

[0403] S903 : Schedule the first channel and the second channel based on the second scheduling policy.

[0404] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0405] In some embodiments, the eRedcap terminal may schedule the first channel and the second channel back-to-back.

[0406] In some embodiments, the first delay may be used for the terminal to process the second channel and prepare the first message.

[0407] For example, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0408] In other words, an additional delay (i.e., the fourth delay mentioned above) is introduced into the first delay, and the eRedcap terminal can process the second channel based on the first delay. In other words, the second channel processing is performed after the PDSCH processing delay of the non-eRedcap terminal is added with the additional delay, so as to avoid the additional processing delay of the eRedcap terminal affecting the processing of the second channel, and prepare the first information for subsequent sending to the network device.

[0409] S904: Send the seventh delay to the terminal.

[0410] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0411] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0412] In this embodiment, K1>=Tproc,1+additional offset X.

[0413] Here, Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal, and additional offset X represents the fourth delay.

[0414] In some embodiments, the network device may send DCI signaling to the terminal, where the DCI signaling includes the seventh delay. In other words, the seventh delay may be carried by the DCI signaling. The seventh delay may also be carried by other downlink signaling, which is not limited by this disclosure.

[0415] S905: Receive a first message sent by the terminal after the seventh time delay after the last symbol of the second channel.

[0416] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0417] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0418] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0419] In some embodiments, the terminal may support reporting capability information to the network device. For example, the network device may receive a second message sent by the terminal, wherein the second message is used to indicate whether the terminal has a first capability, where the first capability is the ability to support back-to-back scheduling.

[0420] In this embodiment, since the scheduling policy is to allow the network device to schedule the eRedcap terminal back-to-back, it means that there is no time interval between the first channel and the second channel scheduled by the network device. In order to avoid the additional processing delay of the eRedcap terminal for the broadcast PDSCH affecting the subsequent unicast PDSCH and the signal sending to the network device, an additional delay X (i.e., the fourth delay) is introduced to solve the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, avoid problems with back-to-back scheduling between the eRedCap terminal broadcast PDSCH and unicast PDSCH, and thus improve communication performance.

[0421] FIG10 is a flow chart of a communication method provided by an embodiment of the present disclosure, the communication method being executed by a network device. Based on the embodiment shown in FIG7 , as shown in FIG10 , the method includes but is not limited to the following steps:

[0422] S1001: Determine that the scheduling strategy is the third scheduling strategy.

[0423] The third scheduling strategy is:

[0424] Allows scheduling of neighboring cell measurements for eRedcap terminals.

[0425] In other words, the third scheduling strategy is that the network device sends a system message for the first cell to the eRedcap terminal, and the eRedcap terminal reads the system message for the first cell when performing cell measurement, wherein the first cell is not the current serving cell of the eRedcap terminal.

[0426] When a terminal is in connected state and performing measurements (e.g., neighboring cell measurements), the network device instructs the terminal to read the cell global ID (CGI) of the neighboring cell. The CGI is carried by SIB1, and the terminal needs to read and decode SIB1. However, the terminal can only process the content of one cell at a time. Therefore, when reading or decoding the SIB1 of a neighboring cell or other cells, scheduling restrictions or interruptions will be generated for the current cell (i.e., the current serving cell).

[0427] For eRedCap terminals, since the broadcast PDSCH can be received once and processed multiple times, the terminal may also introduce additional processing delay when reading the SIB1 of the neighboring cell, which will further affect the terminal delay of the current cell.

[0428] S1002: Determine whether the first delay is greater than or equal to the third delay.

[0429] In some embodiments, the network device may determine that the first delay is greater than or equal to the third delay according to the protocol agreement. For example, the network device may determine the second delay according to the protocol agreement and determine the first delay according to the third delay.

[0430] In some embodiments, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform N-1 baseband processing of PDSCH, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0431] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0432] In some embodiments, the network device may determine the PDSCH channel processing delay of the non-eRedcap terminal according to the protocol. In some embodiments, the PDSCH channel processing delay of the non-eRedcap terminal may include the PDSCH decoding delay and PUCCH preparation delay of the non-eRedcap terminal.

[0433] For example, the second time delay may be determined by referring to the determination method of Tproc,1 in the above formula 1.

[0434] In some embodiments, the fourth delay may be the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times performed by the eRedcap terminal for one PDSCH reception, and N is a positive integer and N ≥ 1. For example, if the eRedcap terminal performs baseband processing of one PDSCH reception four times and the delay of each baseband processing is N1, the value of the fourth delay may be 3*N1.

[0435] In some embodiments, baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0436] In some embodiments, the fourth time delay may be any value. Alternatively, the fourth time delay may be any value as follows:

[0437] 1) When the subcarrier spacing SCS is 15 kHz, the value of the first time interval is 0.5 ms;

[0438] 2) When the subcarrier spacing SCS is 15 kHz, the first time interval is 1 ms;

[0439] 3) When the SCS is 30 kHz, the first time interval is 0.25 ms;

[0440] 4) When the SCS is 30kHz, the value of the first time interval is 0.5ms.

[0441] In other words, for an SCS of 15 / 30 kHz, the value of the first time interval can be 0.5 / 0.25 ms, or 1 / 0.5 ms for 15 / 30 kHz.

[0442] In some embodiments, the network device may determine the sum of the PDSCH channel processing delay (ie, the second delay) of the non-eRedcap terminal and the additional delay X (ie, the fourth delay) as the PDSCH channel processing delay of the eRedcap terminal.

[0443] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device schedules the eRedcap terminal back-to-back, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to schedule the eRedcap terminal back-to-back, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, an additional delay (i.e., the fourth delay mentioned above) is introduced to cover the additional processing delay of the eRedcap terminal, thereby avoiding the delay mismatch problem of the eRedcap terminal in certain scenarios. For example, the mismatch problem between back-to-back scheduling and the capabilities of the eRedcap terminal.

[0444] S1003: Send a system message for the first cell to the terminal.

[0445] In some embodiments, the network device may send a system message for the first cell to the terminal, instructing the terminal to read the system message for the first cell.

[0446] In some embodiments, the first cell is a non-serving cell of the eRedcap terminal, or in other words, the first cell is not the current serving cell of the eRedcap terminal. For example, the first cell may be a neighboring cell or other cell of the current serving cell of the eRedcap terminal.

[0447] When performing cell measurement, such as performing neighboring cell measurement, the eRedcap terminal may read the system information of the neighboring cell, for example, read the SIB1 of the neighboring cell.

[0448] S1004: Determine a fifth time delay.

[0449] The fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is the scheduling restriction or interruption of the non-eRedCap terminal, the network device does not schedule sending and receiving for the terminal within the range of the fifth delay, and the network device does not send or receive messages from the terminal within the range of the fifth delay.

[0450] In other words, since the terminal can only process the content of one cell at the same time, when the eRedcap terminal reads the system message of the neighboring cell, the service of the current serving cell will be scheduled restricted or interrupted. Since the eRedcap terminal still receives and processes multiple times when reading and decoding the neighboring cell SIB1, additional processing delay is still introduced. This additional processing delay will affect the scheduling restriction or interruption of the serving cell.

[0451] S1005: After the fifth delay, schedule transmission and reception of the terminal in the second cell.

[0452] In some embodiments, since the eRedCap terminal measures the first cell (i.e., not the current service cell) within the fifth delay range and does not send and / or receive signals on the second cell (i.e., the current service cell), the network device does not schedule the transmission and reception of the terminal within the fifth delay range, and the network device does not send or receive messages to the terminal within the fifth delay range, the network device schedules the transmission and reception of the eRedcap terminal after the fifth delay, and the eRedcap terminal can resume signal transmission and reception on the current service cell after the fifth delay.

[0453] In this embodiment, since the scheduling strategy is cell measurement scheduling, it means that when the eRedcap terminal reads the neighboring cell system message during the neighboring cell measurement process, it will affect the scheduling restriction or interruption of the current cell. In order to avoid the additional processing delay of the eRedcap terminal for the neighboring cell system message from affecting the scheduling restriction or interruption of the current cell, an additional delay X (i.e., the fourth delay) is introduced to solve the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, thereby improving communication performance.

[0454] FIG11 is a flow chart of a communication method provided by an embodiment of the present disclosure, the communication method being executed by a network device. Based on the embodiment shown in FIG7 , as shown in FIG11 , the method includes but is not limited to the following steps:

[0455] S1101: Receive a second message sent by a terminal.

[0456] The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

[0457] In some embodiments, the eRedCap terminal may also support additional reporting signaling to indicate to the base station whether it is capable of supporting back-to-back scheduling.

[0458] S1102: Determine that the scheduling strategy is the second scheduling strategy.

[0459] The second scheduling strategy is:

[0460] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0461] In other words, the second scheduling policy is to allow the network device to perform back-to-back scheduling on the eRedcap terminal.

[0462] In some embodiments, in step S602, the eRedcap terminal may indicate to the network device that it supports back-to-back scheduling, and when the network device performs back-to-back scheduling on the eRedcap terminal, the following steps may be performed.

[0463] S1103: Determine whether the first delay is greater than or equal to the second delay.

[0464] In some embodiments, the network device may determine that the first delay is greater than or equal to the second delay according to a protocol agreement. For example, the network device may determine the second delay according to a protocol agreement, and determine the first delay according to the second delay.

[0465] In some embodiments, the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction.

[0466] In other words, eRedcap terminals can have additional processing capabilities to support back-to-back scheduling, such as higher parallel processing capabilities, which can support eRedcap terminals without introducing additional processing delays while still covering the additional processing delays of eRedcap terminals. If the terminal has additional PDSCH baseband processing capabilities, the eRedcap terminal does not need to introduce additional delays and will not affect back-to-back scheduling.

[0467] In other words, the eRedcap terminal can support additional reporting signaling, such as the terminal has additional parallel processing capabilities, such as the terminal has additional pipelines capable of parallel processing. For the additional broadcast PDSCH transmission of the eRedcap terminal, PDSCH decoding and PUCCH preparation can still be performed within the PDSCH channel processing delay of the non-eRedcap terminal without introducing additional delay.

[0468] In some embodiments, the network device may determine the PDSCH channel processing delay of the non-eRedcap terminal as the PDSCH channel processing delay of the eRedcap terminal.

[0469] In some embodiments, since there is no time interval between the first channel and the second channel, in other words, the network device performs back-to-back scheduling on the eRedcap terminal, where the broadcast PDSCH is before the unicast PDSCH. In one example, although the scheduling policy allows the network device to perform back-to-back scheduling on the eRedcap terminal, when the first channel is before the second channel, the network device is restricted from performing back-to-back scheduling. In order to avoid the impact of the additional processing delay of the broadcast PDSCH on the unicast PDSCH, since the terminal reports its own capabilities to the base station, it can perform PDSCH decoding and PUCCH preparation within the PDSCH processing delay of the non-eRedcap terminal, and will not affect the subsequent second channel and the information feedback to the network device, thereby avoiding the delay mismatch problem of the eRedCap terminal in certain scenarios. For example, the mismatch between back-to-back scheduling and the capabilities of the eRedcap terminal.

[0470] S1104 : Schedule the first channel and the second channel based on the second scheduling policy.

[0471] In some embodiments, the first channel is located before the second channel. Optionally, the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0472] In some embodiments, the eRedcap terminal may schedule the first channel and the second channel, for example, perform back-to-back scheduling.

[0473] In some embodiments, the first delay may be used for the terminal to process the second channel and prepare the first message.

[0474] In some embodiments, the first delay may also be used for time domain resource indication of the network device.

[0475] In some embodiments, after receiving the first channel and the second channel, the eRedcap terminal may process the second channel and prepare the first message based on the first delay.

[0476] In other words, the eRedcap terminal can process the second channel based on the PDSCH processing delay of the non-eRedcap terminal. In other words, the second channel processing is performed after the PDSCH processing delay of the non-eRedcap terminal. Since the eRedcap terminal has certain processing capabilities, such as higher parallel processing capabilities, it can perform multiple processing of the eRedcap terminal within the PDSCH processing delay of the non-eRedcap terminal, avoiding the impact of the extra processing delay of the eRedcap terminal on the processing of the second channel, and prepare the first information for subsequent sending to the network device.

[0477] S1105: Send the seventh delay to the terminal.

[0478] In some embodiments, the seventh delay is greater than or equal to the first delay.

[0479] In some embodiments, the seventh delay may be a base station scheduling delay K1, which needs to meet the constraint that it is greater than or equal to the first delay, that is, the base station scheduling delay should be greater than or equal to the PDSCH processing delay of the terminal.

[0480] In this embodiment, K1>=Tproc,1.

[0481] Where Tproc,1 represents the PDSCH processing delay of the non-eRedcap terminal.

[0482] In some embodiments, the network device may send DCI signaling to the terminal, where the DCI signaling includes the seventh delay. In other words, the seventh delay may be carried by the DCI signaling. The seventh delay may also be carried by other downlink signaling, which is not limited by this disclosure.

[0483] S1106: Receive a first message sent by the terminal after the seventh time delay after the last symbol of the second channel.

[0484] In some embodiments, the first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

[0485] For example, the first message may be a HARQ-ACK message fed back by the terminal to the network device. For application scenarios of the HARQ-ACK message, please refer to the relevant provisions of the protocol and will not be described in detail here. The feedback of the HARQ-ACK message will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends the HARQ-ACK message to the network device after the seventh delay after the last symbol of the second channel, thereby avoiding the impact of the additional processing delay of the eRedcap terminal.

[0486] For example, the first message may be msg3 sent by the terminal to the network device. For example, when the signal carried by the broadcast PDSCH is RAR, the terminal may send msg3 to the network device. The sending of msg3 will be affected by the additional processing delay of the eRedcap terminal. Therefore, the eRedcap terminal sends msg3 to the network device after the seventh delay after the last symbol of the second channel, which can avoid the impact of the additional processing delay of the eRedcap terminal.

[0487] In this embodiment, since the scheduling strategy allows network devices to perform back-to-back scheduling of eRedcap terminals and supports terminals to report capability information to network devices, when the terminal capability can cover the additional processing delay of the eRedcap terminal and no additional delay is introduced, the eRedcap terminal can also perform multiple PDSCH processing within the PDSCH processing delay of the non-eRedcap terminal, thereby avoiding the additional processing delay of the eRedcap terminal for the broadcast PDSCH from affecting the subsequent unicast PDSCH and the sending of signals to the network device, thereby solving the problem of mismatch between certain scheduling strategies of the base station and the terminal processing capability, avoiding problems with back-to-back scheduling between the eRedCap terminal's broadcast PDSCH and unicast PDSCH, and improving communication performance.

[0488] FIG12 is a schematic diagram of the structure of a communication device 1200 provided in an embodiment of the present disclosure. The communication device 1200 shown in FIG12 may include a processing module for:

[0489] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0490] The first delay includes a downlink physical shared channel PDSCH processing delay.

[0491] Optionally, the terminal is an enhanced reduced capability eRedcap terminal, and the processing module is further configured to:

[0492] Determining the scheduling strategy as the first scheduling strategy,

[0493] The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0494] Optionally, the processing module is further configured to:

[0495] It is determined that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal.

[0496] Optionally, the terminal is an enhanced reduced capability eRedcap terminal, and the processing module is configured to:

[0497] Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is:

[0498] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0499] Optionally, the terminal is an enhanced reduced capability eRedcap terminal, and the processing module is configured to:

[0500] Determining that the scheduling strategy is a third scheduling strategy,

[0501] The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

[0502] Optionally, the processing module is configured to:

[0503] Determine that the first delay is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0504] Optionally, the baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0505] Optionally, when the scheduling strategy is the third scheduling strategy, the apparatus further includes a transceiver module, configured to:

[0506] Reading a system message for the first cell;

[0507] The processing module is used to: determine a fifth delay, wherein the fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is the scheduling restriction or interruption of the non-eRedCap terminal, and within the fifth delay range, the eRedCap terminal does not send and / or receive signals on the second cell, and the second cell is the current serving cell of the eRedcap terminal.

[0508] Optionally, the terminal is an enhanced reduced capability eRedCap terminal, and the transceiver module is used for:

[0509] Based on the first scheduling policy and / or the second scheduling policy, a first channel and a second channel are received, wherein the first channel is located before the second channel.

[0510] Optionally, when the subcarrier spacing SCS is 15 kHz, the first time interval and / or the fourth time delay is 0.5 ms or 1 ms;

[0511] For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

[0512] Optionally, the transceiver module is used to:

[0513] sending a second message to the network device,

[0514] The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

[0515] Optionally, the processing module is configured to:

[0516] When the scheduling strategy is the second scheduling strategy, it is determined that the first delay is greater than or equal to the second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction.

[0517] Optionally, the transceiver module is used to:

[0518] receiving a seventh time delay sent by the network device, wherein the seventh time delay is greater than or equal to the first time delay;

[0519] After a seventh time delay after the last symbol of the second channel, a first message is sent to the network device.

[0520] Optionally, the first message is at least one of a hybrid automatic repeat request confirmation HARQ-ACK message and a random access message msg3.

[0521] Optionally, the processing module is configured to: process the second channel and prepare the first message based on the first delay.

[0522] FIG13 is a schematic diagram of the structure of a communication device 1300 provided in an embodiment of the present disclosure. The communication device 1300 shown in FIG13 is configured in a network device and may include a processing module for:

[0523] Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement,

[0524] The first delay includes a downlink physical shared channel PDSCH processing delay.

[0525] Optionally, the processing module is configured to:

[0526] Determining the scheduling strategy as the first scheduling strategy,

[0527] The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

[0528] Optionally, the processing module is configured to:

[0529] It is determined that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal.

[0530] Optionally, the processing module is configured to:

[0531] Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is:

[0532] Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

[0533] Optionally, the processing module is configured to:

[0534] Determining that the scheduling strategy is a third scheduling strategy,

[0535] The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

[0536] Optionally, the processing module is configured to:

[0537] Determine that the first delay is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

[0538] Optionally, the baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

[0539] Optionally, when the scheduling strategy is the third scheduling strategy, the apparatus further includes a transceiver module, configured to:

[0540] Sending a system message for the first cell to the terminal;

[0541] Determine a fifth delay, where the fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is a scheduling restriction or interruption of a non-eRedCap terminal, the network device does not schedule transmission and reception for the terminal within the range of the fifth delay, and the network device does not transmit or receive messages from the terminal within the range of the fifth delay.

[0542] Optionally, the device further includes a scheduling module, configured to schedule the first channel and the second channel based on the first scheduling strategy and / or the second scheduling strategy, wherein the first channel is located before the second channel.

[0543] Optionally, when the subcarrier spacing SCS is 15 kHz, the first time interval and / or the fourth time delay is 0.5 ms or 1 ms;

[0544] For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

[0545] Optionally, the transceiver module is used to: receive a second message sent by the terminal,

[0546] The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

[0547] Optionally, the processing module is configured to:

[0548] When the scheduling strategy is the second scheduling strategy, it is determined that the first delay is greater than or equal to the second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction.

[0549] Optionally, the transceiver module is used to:

[0550] Sending a seventh delay to the terminal, where the seventh delay is greater than or equal to the first delay;

[0551] receiving a first message sent by the terminal after a seventh time delay after the last symbol of the second channel.

[0552] Optionally, the first message is at least one of a hybrid automatic repeat request confirmation HARQ-ACK message and a random access message msg3.

[0553] Please refer to Figure 14, which is a schematic diagram of the structure of another communication device 140 provided in an embodiment of the present disclosure. Communication device 140 can be a network device or a terminal device, or a chip, chip system, or processor that supports the network device to implement the above method. It can also be a chip, chip system, or processor that supports the terminal device to implement the above method. This device can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0554] The communication device 140 may include one or more processors 1401. The processor 1401 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0555] Optionally, the communication device 140 may further include one or more memories 1402, on which a computer program 1403 may be stored. The processor 1401 executes the computer program 1403 to cause the communication device 140 to perform the method described in the above method embodiment. Optionally, the memory 1402 may also store data. The communication device 140 and the memory 1402 may be provided separately or integrated together.

[0556] Optionally, the communication device 140 may further include a transceiver 1404 and an antenna 1405. The transceiver 1404 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 1404 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.

[0557] Optionally, the communication device 140 may further include one or more interface circuits 1406. The interface circuit 1406 is configured to receive code instructions and transmit the code instructions to the processor 1401. The processor 1401 executes the code instructions to enable the communication device 140 to execute the method described in the above method embodiment.

[0558] The communication device 140 is a terminal device used to implement the functions of the terminal device in the aforementioned embodiments.

[0559] The communication device 140 is a network device used to implement the functions of the network device in the aforementioned embodiments.

[0560] In one implementation, processor 1401 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0561] In one implementation, processor 1401 may store a computer program 1403. Computer program 1403, when executed on processor 1401, enables communication device 140 to perform the method described in the above method embodiment. Computer program 1403 may be embedded in processor 1401, in which case processor 1401 may be implemented by hardware.

[0562] In one implementation, the communication device 140 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0563] The communication device described in the above embodiments may be a network device or, however, the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited to FIG14. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0564] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0565] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0566] (3) ASIC, such as modem;

[0567] (4) Modules that can be embedded in other devices;

[0568] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0569] (6)Others, etc.

[0570] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 15. The chip shown in Figure 15 includes a processor 1501 and an interface 1502. The number of processors 1501 can be one or more, and the number of interfaces 1502 can be multiple.

[0571] The embodiments of the present disclosure also provide a chip, as shown in FIG15 . The chip shown in FIG15 includes a processor 1501 and an interface 1502 . The number of processors 1501 can be one or more, and the number of interfaces 1502 can be multiple. Optionally, the chip also includes a memory 1503 , which is used to store computer instructions. When the processor executes the computer instructions, the electronic device executes the communication method described in the above embodiments of the present disclosure.

[0572] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0573] An embodiment of the present disclosure further provides a communication system, which includes a terminal and a network device. The terminal is used to execute the embodiments shown in Figures 2 to 6 above, and the network device is used to execute the embodiments shown in Figures 7 to 11.

[0574] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0575] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0576] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0577] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0578] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0579] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondence between information and parameters, it is not necessary to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also use other names that are understandable to the communication device, and the values ​​or representations of the parameters may also use other values ​​or representations that are understandable to the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables.

[0580] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0581] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0582] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0583] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method is executed by a terminal, and includes: Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement, The first delay includes a downlink physical shared channel PDSCH processing delay.

2. The method according to claim 1, characterized in that The terminal is an enhanced capability reduction eRedcap terminal, and the determining of the scheduling strategy includes: Determining the scheduling strategy as a first scheduling strategy, The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

3. The method according to claim 2, characterized in that The determining, according to the protocol, the first delay corresponding to the scheduling strategy includes: Determine that the first delay is greater than or equal to a second delay, where the second delay is a PDSCH channel processing delay of a non-enhanced capability reduction non-eRedCap terminal.

4. The method according to claim 1, characterized in that: The terminal is an enhanced capability reduction eRedcap terminal, and the determining of the scheduling strategy includes: Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is: Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

5. The method according to claim 1, characterized in that The terminal is an enhanced capability reduction eRedcap terminal, and the determining of the scheduling strategy includes: Determining that the scheduling strategy is a third scheduling strategy, The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

6. According to the method of claim 4 or 5, determining the first delay corresponding to the scheduling strategy according to the protocol agreement comprises: Determining that the first time delay is greater than or equal to a third time delay; The third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay of the eRedcap terminal performing baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, N is a positive integer and N≥1.

7. The method according to claim 6, characterized in that The baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

8. The method according to claim 6 or 7, characterized in that: When the scheduling strategy is the third scheduling strategy, the method further includes: Reading a system message for the first cell; Determine a fifth delay, wherein the fifth delay is the sum of the fourth delay and the sixth delay, and the sixth delay is a scheduling restriction or interruption of a non-eRedCap terminal; Within the fifth time delay range, the eRedCap terminal does not send and / or receive signals on the second cell, and the second cell is the current serving cell of the eRedcap terminal.

9. The method according to claim 2 or 4, characterized in that: The terminal is an enhanced reduced capability eRedCap terminal, and the method further includes: Based on the first scheduling strategy or the second scheduling strategy, a first channel and a second channel are received, wherein the first channel is located before the second channel.

10. The method according to claim 2 or 6, characterized in that: For a subcarrier spacing SCS of 15 kHz, a value of the first time interval and / or the fourth time delay is 0.5 ms or 1 ms; For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: sending a second message to the network device, The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

12. The method according to claim 11, characterized in that Determining the first delay corresponding to the scheduling strategy includes: In a case where the scheduling strategy is a second scheduling strategy, determining that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-enhanced capability reduction non-eRedCap terminal; The second scheduling strategy is: Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

13. The method according to any one of claims 2 to 12, characterized in that The method further comprises: receiving a seventh time delay sent by the network device, wherein the seventh time delay is greater than or equal to the first time delay; After a seventh time delay after the last symbol of the second channel, a first message is sent to the network device.

14. The method according to claim 13, characterized in that The first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

15. The method according to claim 13 or 14, characterized in that The method further comprises: Processing of the second channel and preparation of the first message are performed based on the first delay.

16. A communication method, characterized in that: The method is performed by a network device, and the method includes: Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement, The first delay includes a downlink physical shared channel PDSCH processing delay.

17. The method according to claim 16, characterized in that Determining the scheduling strategy includes: Determining the scheduling strategy as a first scheduling strategy, The first scheduling strategy is that there is a first time interval between the time slots of the first channel and the second channel scheduled by the network device for the eRedcap terminal, the first channel is a broadcast PDSCH, and the second channel is a unicast PDSCH.

18. The method according to claim 17, characterized in that The determining, according to the protocol, the first delay corresponding to the scheduling strategy includes: Determine that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-eRedCap terminal with non-enhanced capability reduction.

19. The method according to claim 16, characterized in that Determining the scheduling strategy includes: Determine that the scheduling strategy is a second scheduling strategy, wherein the second scheduling strategy is: Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

20. The method according to claim 16, characterized in that Determining the scheduling strategy includes: Determining that the scheduling strategy is a third scheduling strategy, The third scheduling strategy is that the eRedcap terminal reads a system message for a first cell when performing cell measurement, wherein the first cell is not a current serving cell of the eRedcap terminal.

21. The method according to claim 19 or 20, wherein determining the first delay corresponding to the scheduling strategy according to a protocol agreement comprises: Determine that the first delay is greater than or equal to the third delay, the third delay is the sum of the second delay and the fourth delay, the second delay is the PDSCH channel processing delay of the non-eRedCap terminal with non-enhanced capability reduction, and the fourth delay is the delay for the eRedcap terminal to perform baseband processing of PDSCH N-1 times, where N is the number of baseband processing times of a PDSCH reception by the eRedcap terminal, and N is a positive integer and N≥1.

22. The method according to claim 21, characterized in that The baseband processing includes at least one of: channel estimation, channel equalization, signal detection, and demodulation.

23. The method according to claim 21 or 22, characterized in that When the scheduling strategy is the third scheduling strategy, the method further includes: Sending a system message for the first cell to the terminal; Determine a fifth delay, wherein the fifth delay is the sum of the fourth delay and the sixth delay, the sixth delay is a scheduling restriction or interruption of a non-eRedCap terminal, the network device does not perform sending and receiving scheduling for the terminal within the range of the fifth delay, and the network device does not send or receive messages from the terminal within the range of the fifth delay.

24. The method according to claim 17 or 20, characterized in that The method further comprises: Based on the first scheduling strategy or the second scheduling strategy, a first channel and a second channel are scheduled, wherein the first channel is located before the second channel.

25. The method according to claim 17 or 21, characterized in that For a subcarrier spacing SCS of 15 kHz, a value of the first time interval and / or the fourth time delay is 0.5 ms or 1 ms; For an SCS of 30 kHz, the value of the first time interval and / or the fourth time delay is 0.25 ms or 0.5 ms.

26. The method according to any one of claims 16 to 25, characterized in that The method further comprises: receiving a second message sent by the terminal, The second message is used to indicate whether the terminal has a first capability, and the first capability is a capability of supporting back-to-back scheduling.

27. The method according to claim 26, characterized in that Determining the first delay corresponding to the scheduling strategy includes: In a case where the scheduling strategy is a second scheduling strategy, determining that the first delay is greater than or equal to a second delay, wherein the second delay is a PDSCH channel processing delay of a non-enhanced capability reduction non-eRedCap terminal; The second scheduling strategy is: Allow network devices to perform back-to-back scheduling of eRedcap terminals, wherein the back-to-back scheduling means that there is no time interval between the symbols of the first channel and the second channel scheduled by the network device, or there is no time interval between the time slots of the first channel and the second channel, wherein the first channel is a broadcast PDSCH and the second channel is a unicast PDSCH.

28. The method according to any one of claims 17 to 27, characterized in that The method further comprises: Sending a seventh time delay to the terminal, wherein the seventh time delay is greater than or equal to the first time delay; A first message sent by the terminal after a seventh time delay after the last symbol of the second channel is received.

29. The method according to claim 28, characterized in that The first message is at least one of a hybrid automatic repeat request acknowledgement HARQ-ACK message and a random access message msg3.

30. A communication device, characterized in that: The device comprises a processing module for: Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement, The first delay includes a downlink physical shared channel PDSCH processing delay.

31. A communication device, characterized in that: The device comprises a processing module for: Determine a scheduling strategy, and determine a first delay corresponding to the scheduling strategy according to the protocol agreement, The first delay includes a downlink physical shared channel PDSCH processing delay.

32. A communication device, wherein: include: Transceiver; Memory; The processor is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer executable instructions on the memory, and can implement any one of the methods of claims 1-29.

33. A computer storage medium, wherein: The computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the method described in any one of claims 1 to 29 can be implemented.

34. A communication system, characterized in that: include: A network device and a terminal, wherein the terminal is used to perform the method according to any one of claims 1 to 15; The network device is configured to execute the method according to any one of claims 16 to 29.

Citation Information

Patent Citations

  • A wireless communication method and device

    CN109803430A

  • Method executed by user equipment and user equipment

    CN111757510A

  • Terminal equipment scheduling method and device

    CN115004617A

  • Processing time delay determination method and device, equipment and storage medium

    CN115997461A

  • Signaling optimizations for wireless devices operating on harvested energy

    WO2022265567A1