Time determination method and device, terminal and network side equipment

Abstract

The invention discloses a time determination method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the time determination method comprises the steps that under a target condition, the terminal determines the sending time of an uplink channel or the receiving time of a downlink channel; wherein the target condition comprises at least one of the following items: the downlink channel performs repeated transmission, and the downlink channel supports repeated transmission; the downlink channel comprises a downlink channel which needs to be received before the terminal enters a connected state; the uplink channel is an uplink channel corresponding to the downlink channel.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a time determination method, device, terminal and network side equipment. Background Art

[0002] Before entering the connected state, the terminal often needs to receive some downlink channels, such as messages in the random access process or paging messages, etc. In some related technologies, the downlink channels that the terminal needs to receive before entering the connected state often only support single transmission, which results in a low success rate for the terminal to receive the downlink channels, resulting in poor service performance of the terminal. Summary of the invention

[0003] The embodiments of the present application provide a time determination method, apparatus, terminal, and network-side equipment, which can solve the problem of poor service performance of the terminal.

[0004] In a first aspect, a time determination method is provided, comprising:

[0005] Under the target conditions, the terminal determines the transmission time of the uplink channel or the reception time of the downlink channel;

[0006] The target condition includes at least one of the following:

[0007] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0008] The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state;

[0009] The uplink channel is an uplink channel corresponding to the downlink channel.

[0010] In a second aspect, a time determination method is provided, comprising:

[0011] Under target conditions, the network side device determines the sending time of the uplink channel or the receiving time of the downlink channel;

[0012] The target condition includes at least one of the following:

[0013] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0014] The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state;

[0015] The uplink channel is an uplink channel corresponding to the downlink channel.

[0016] In a third aspect, a time determination device is provided, comprising:

[0017] A determination module, used for the terminal to determine the sending time of the uplink channel or the receiving time of the downlink channel under target conditions;

[0018] The target condition includes at least one of the following:

[0019] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0020] The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state;

[0021] The uplink channel is an uplink channel corresponding to the downlink channel.

[0022] In a fourth aspect, a time determination device is provided, characterized in that it includes:

[0023] A determination module, used to determine the sending time of the uplink channel or the receiving time of the downlink channel under target conditions;

[0024] The target condition includes at least one of the following:

[0025] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0026] The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state;

[0027] The uplink channel is an uplink channel corresponding to the downlink channel.

[0028] In a fifth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the terminal-side time determination method provided in an embodiment of the present application are implemented.

[0029] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to determine the sending time of an uplink channel or the receiving time of a downlink channel under target conditions; wherein the target conditions include at least one of the following: the downlink channel performs repeated transmission and the downlink channel supports repeated transmission; the downlink channel includes: a downlink channel that the terminal needs to receive before entering a connected state; the uplink channel is an uplink channel corresponding to the downlink channel.

[0030] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the time determination method on the network side device side provided in the embodiment of the present application are implemented.

[0031] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the processor is used to determine the sending time of an uplink channel or the receiving time of a downlink channel under target conditions; wherein the target conditions include at least one of the following: the downlink channel performs repeated transmission and the downlink channel supports repeated transmission; the downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters a connected state; the uplink channel is an uplink channel corresponding to the downlink channel.

[0032] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the time determination method on the terminal side as provided in the embodiment of the present application are implemented, or the steps of the time determination method on the network side device side as provided in the embodiment of the present application are implemented.

[0033] In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the terminal side time determination method provided in the embodiment of the present application, and the network side device can be used to execute the steps of the network side device side time determination method provided in the embodiment of the present application.

[0034] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement a time determination method on the terminal side as provided in an embodiment of the present application, or to implement a time determination method on the network side device side as provided in an embodiment of the present application.

[0035] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the time determination method on the terminal side as provided in the embodiments of the present application, or the program / program product is executed by at least one processor to implement the steps of the time determination method on the network side device side as provided in the embodiments of the present application.

[0036] In an embodiment of the present application, under target conditions, the sending time of the uplink channel or the receiving time of the downlink channel is determined; wherein the target conditions include at least one of the following: the downlink channel performs repeated transmission, the downlink channel supports repeated transmission; the downlink channel includes: the downlink channel that the terminal needs to receive before entering the connected state; the uplink channel is the uplink channel corresponding to the downlink channel. In this way, when the downlink channel performs repeated transmission or the downlink channel supports repeated transmission, the sending time of the uplink channel or the receiving time of the downlink channel can be determined, thereby enabling the terminal to support repeated transmission of the downlink channel, thereby improving the success rate of the terminal receiving the downlink channel, and improving the service performance of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0038] Figure 2 is a flow chart of a time determination method provided by an embodiment of the present application;

[0039] Figure 3 is a flow chart of another time determination method provided by an embodiment of the present application;

[0040] Figure 4 is a structural diagram of a time determination device provided in an embodiment of the present application;

[0041] Figure 5 is a structural diagram of another time determination device provided in an embodiment of the present application;

[0042] Figure 6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0043] Figure 7 is a structural diagram of a terminal provided in an embodiment of the present application;

[0044] Figure 8 It is a structural diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0046] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0047] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0048] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0049] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0050] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0051] In some embodiments, the random access process may be a contention-based random access process or a non-contention-based random access process. The random access process may be a four-step random access process (also called a Type-1 random access process) or a two-step random access process (also called a Type-2 random access process).

[0052] In the competitive 4-step random access process (Random Access Channel, RACH), the terminal first sends message 1 (Msg1) to the network, including a preamble; after the network detects the preamble, it will send message 2 (Msg2) / Random Access Response (RAR) message, including the number of the preamble detected by the network and the uplink wireless resources allocated to the terminal to send message 3 (Msg3); after receiving Msg2, the terminal confirms that at least one of the preamble numbers carried in Msg2 is consistent with the number of the preamble sent by itself, and then sends Msg3 containing contention resolution information according to the resources indicated by RAR; after receiving Msg3, the network will send message 4 (Msg4) containing contention resolution information; after receiving Msg4, the terminal confirms that the resolution information is consistent with that sent by itself in Msg3, that is, the 4-step random access is completed.

[0053] The network includes uplink grant (UL grant) information in the RAR to indicate the scheduling information of the Msg3 physical uplink shared channel (PUSCH), and includes information such as the random access preamble ID (RAPID), temporary cell-radio networktemporary identifier (TC-RNTI), and timing advance (TA). If the network does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the TC-RNTI-scrambled physical downlink control channel (PDCCH).

[0054] For the competitive random access process, different terminals randomly select preambles for transmission, so different terminals may select the same preamble to send on the same time-frequency wireless resources (such as random access opportunity (RACH Occasion, RO) resources), which can be understood as a preamble conflict of the terminal. In this case, different terminals will receive the same RAR, and at this time, different terminals will transmit Msg3PUSCH according to the scheduling information in the RAR UL grant. In some related technologies, since repeated transmission of Msg3 PUSCH is not supported, the network can only decode the PUSCH (including contention resolution information) sent by one terminal on one Msg3 PUSCH scheduling resource, so the network will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information in Msg4 received by the terminal matches the contention resolution information sent by the terminal in Msg3 PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0055] If the contention resolution is unsuccessful, the terminal reselects RACH transmission resources, performs physical random access channel (PRACH) transmission, and makes the next random access attempt.

[0056] In some embodiments, the first step in the two-step random access process (2-step RACH) is that the terminal sends message A (MsgA) to the network side. After receiving MsgA, the network side sends message B (MsgB) to the terminal. If the terminal does not receive MsgB within a certain period of time, the terminal will accumulate the counter that counts the number of times MsgA is sent and resend MsgA. If the counter that counts the number of times MsgA is sent reaches a certain threshold, the terminal will switch from the two-step random access process to the four-step random access process. MsgA includes the MsgA preamble part and the MsgA PUSCH part. The preamble part is sent on the RO used for the two-step random access process, and the PUSCH part is sent on the MsgA PUSCH resources associated with the sending of the MsgA preamble and the RO. MsgA PUSCH resources are a group of PUSCH resources configured relative to each PRACH slot, including time-frequency resources and DMRS resources.

[0057] In some embodiments, during the random access process, the reception of scheduling information of the physical downlink shared channel (PDSCH) of Msg2 / MsgB / Msg4 needs to be within a certain window, and the size of the window is configured by the network.

[0058] For Msg2, the above window starts from the first symbol of the control resource set (Control resource set, CORESET) in the Type 1 PDCCH common search space set (Type1-PDCCH CSS set) after PRACH is sent. For MsgB, the above window starts from the first symbol of the CORESET in the Type 1-PDCCH CSS set after PRACH (MsgA PRACH part) sends the corresponding PUSCH (MsgAPUSCH part). For Msg3, the above window is actually controlled by the random access contention resolution timer (ra-ContentionResolutionTimer), which will start or restart after the Msg3 is sent (if Msg3 repetition is supported, it is the last repetition of the Msg3).

[0059] The time determination method, apparatus, terminal and network side equipment provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0060] See also Figure 2 , Figure 2 is a flow chart of a time determination method provided in an embodiment of the present application, such as Figure 2 As shown, the following steps are included:

[0061] Step 201: Under target conditions, determine the sending time of the uplink channel or the receiving time of the downlink channel;

[0062] The target condition includes at least one of the following:

[0063] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0064] The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state;

[0065] The uplink channel is an uplink channel corresponding to the downlink channel.

[0066] The downlink channel supports repeated transmission, which may be that the network side configures the downlink channel to repeat transmission, or the protocol stipulates the downlink channel to repeat transmission, or the terminal requests the uplink channel to repeat transmission, etc. In addition, in the embodiment of the present application, the downlink channel supports repeated transmission, which may also be referred to as downlink channel repeated transmission or downlink channel repetition.

[0067] The repeated transmission of the downlink channel may be that the downlink channel has been repeatedly transmitted, or the downlink channel will be repeatedly transmitted, or the downlink channel needs to be repeatedly transmitted, etc.

[0068] The above determination of the transmission time of the uplink channel may be to directly determine the transmission time of the uplink channel, or to indirectly determine the transmission time of the uplink channel, such as determining a reference time of the transmission time of the uplink channel, or determining the time interval between the reception time of the downlink channel and the transmission time of the uplink channel.

[0069] The above-mentioned determination of the reception time of the downlink channel may be the reception time domain resource of the downlink channel, or determination of the absolute reception time of the downlink channel, or determination of the reception duration of the downlink channel, and the like.

[0070] In the embodiment of the present application, the above steps can be used to determine the sending time of the uplink channel or the receiving time of the downlink channel when the downlink channel is repeatedly transmitted or the downlink channel supports repeated transmission, so as to achieve the terminal supporting repeated transmission of the downlink channel, thereby improving the success rate of the terminal receiving the downlink channel, so as to improve the service performance of the terminal. For example: when the above downlink channel is a downlink channel in a random access process, the random access delay can be reduced and the terminal reception complexity can be reduced.

[0071] In some embodiments, the above method further comprises at least one of the following:

[0072] The terminal sends an uplink channel based on the sending time of the uplink channel;

[0073] The terminal receives the downlink channel based on the reception time of the downlink channel.

[0074] In addition, the network side device includes at least one of the following:

[0075] The network side device receives the uplink channel based on the transmission time of the uplink channel;

[0076] The network side device sends the downlink channel based on the reception time of the downlink channel.

[0077] As an optional implementation manner, the downlink channel that the terminal needs to receive before entering the connected state includes at least one of the following:

[0078] Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH, paging PDSCH.

[0079] In this implementation, repeated transmission of at least one of Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH and paging PDSCH can be achieved, that is, enhancement of Msg2 PDSCH, MsgB PDSCH, Msg4 PDSCH and paging PDSCH is achieved, thereby improving the random access performance of the terminal and improving the paging performance of the terminal.

[0080] It should be noted that in the embodiment of the present application, Msg2 PDSCH repeated transmission may also be referred to as Msg2 PDSCH repetition (Msg2 PDSCH repetition) or Msg2 repetition; MsgB PDSCH repeated transmission may also be referred to as MsgB PDSCH repetition (MsgB PDSCH repetition) or MsgB repetition; Msg4 PDSCH repeated transmission may also be referred to as Msg4PDSCH repetition (Msg4 PDSCH repetition) or Msg4 repetition; paging PDSCH repeated transmission may also be referred to as paging PDSCH repetition (paging PDSCH repetition).

[0081] It should be noted that the above-mentioned downlink channel is not limited in the embodiments of the present application. For example, in some implementations, the above-mentioned downlink channel may be all or part of the downlink channel before the terminal enters the Radio Resource Control (RRC) connection state.

[0082] As an optional implementation manner, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0083] PUSCH scheduled by RAR, Physical Uplink Control Channel (PUCCH) for feedback of Hybrid automatic repeat request acknowledgement (HARQ-ACK) of Msg4, PUCCH for feedback of HARQ-ACK of MsgB;

[0084] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0085] The RAR carried by the Msg2 PDSCH may also be referred to as the RAR carried by Msg2, the RAR carried by the MsgB PDSCH may also be referred to as the RAR carried by MsgB, and the PDSCH carrying the RAR may also be referred to as the RAR PDSCH.

[0086] In this implementation, the RAR may be a RAR message in Msg2 in a four-step random access (4-step RACH), or a success RAR or a fallback RAR in a two-step random access (2-step RACH).

[0087] In this implementation, it is possible to determine the transmission time of the RAR-scheduled PUSCH, the transmission time of the PUCCH for Msg4 HARQ-ACK feedback, and the transmission time of the PUCCH for MsgB HARQ-ACK feedback, so as to improve the transmission performance of the terminal for these uplink channel transmissions, such as making the terminal and the network side device have a consistent understanding of the transmission time of these uplink channels, thereby improving the reliability of these uplink channel transmissions.

[0088] As an optional implementation manner, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0089] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0090] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point of the RAR time window (RAR window), or the second reference time domain resource corresponds to a time point of the MsgB response time window (MsgBresponse window).

[0091] In some implementations, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0092] A time domain resource for actually sending the first PDSCH;

[0093] An effective time domain resource capable of sending the first PDSCH;

[0094] Available time domain resources capable of sending the first PDSCH;

[0095] The time domain resource where the first PDSCH is located.

[0096] For example, the first reference time domain resource includes at least one of the following:

[0097] The slot where the first PDSCH repetition is actually sent;

[0098] A valid slot in which the first PDSCH repetition can be sent;

[0099] Available slots in which the first PDSCH repetition can be sent;

[0100] The slot where the first PDSCH repetition is located.

[0101] In some implementations, the first PDSCH may be Msg2 PDSCH or MsgB PDSCH. In addition, the first PDSCH is a specific transmission or a predefined transmission for repeated transmission of the downlink channel. Here, one transmission may also be referred to as one repetition.

[0102] In some implementations, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0103] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0104] The above-mentioned nth transmission can be understood as the nth repetition, such as the first transmission, the second transmission, and the last transmission.

[0105] The last transmission mentioned above may also be referred to as the last downlink channel repetition transmission or the last downlink channel repetition.

[0106] For example, the reference slot of the RAR-scheduled PUSCH transmission time is a slot where a predefined PDSCH carrying RAR is repeatedly transmitted. For example, when the RAR PDSCH supports repeated transmission, the reference slot of the RAR-scheduled PUSCH transmission time is determined to be the slot where the last PDSCH is repeatedly transmitted.

[0107] The reference time domain resource of the transmission time of the RAR-scheduled PUSCH can be accurately determined by the above method, so as to accurately determine the transmission time of the RAR-scheduled PUSCH, so that the network and the terminal have a consistent understanding of the scheduling time of the RAR PUSCH, thereby improving the transmission performance of the PUSCH. In addition, since the first PDSCH is the last transmission of the downlink channel for repeated transmission, there can be enough time interval between the transmission time of the first PDSCH and the RAR-scheduled PUSCH, so that the terminal can better process the first PDSCH and prepare for the transmission of the PUSCH, so as to improve the transmission reliability of the PUSCH.

[0108] The above-mentioned second reference time domain resource corresponds to a time point of the RAR time window, which may be a time domain resource corresponding to a predefined time point of the RAR time window, such as the starting slot of the RAR window; the above-mentioned second reference time domain resource corresponds to a time point of the MsgB response time window, which may be a time domain resource corresponding to a predefined time point of the MsgB response time window, such as the starting slot of the MsgB response time window.

[0109] The first reference time domain resource and the second reference time domain resource may be a first reference slot and a second reference slot, ie, reference slots for determining the transmission time of the PUSCH.

[0110] The transmission time determined based on the first reference time domain resource may be determined according to the method of determining the transmission time of PUSCH based on the reference time domain resource agreed upon in the protocol, for example: determining the transmission time of RAR-scheduled PUSCH based on the first reference slot according to the method of determining the transmission slot of PUSCH based on the reference slot agreed upon in the protocol. Similarly, the transmission time determined based on the second reference time domain resource may be determined according to the method of determining the transmission time of PUSCH based on the reference time domain resource agreed upon in the protocol.

[0111] In the above implementation, the transmission time of the RAR-scheduled PUSCH can be accurately determined based on the first reference time domain resource and the second reference time domain resource, so that the network and the terminal have a consistent understanding of the scheduling time of the RAR PUSCH, thereby improving the transmission performance of the PUSCH.

[0112] As an optional implementation manner, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0113] The first time interval plus the target time;

[0114] a second time interval determined based on the first processing time;

[0115] a third time interval determined based on the second processing time;

[0116] or,

[0117] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0118] The first minimum time interval plus the target time;

[0119] A second minimum time interval determined based on the first processing time

[0120] a third minimum time interval determined based on the second processing time;

[0121] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0122] In this implementation, determining the transmission time of the uplink channel includes: determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR, so that the transmission time of the PUSCH scheduled by the RAR can be determined by the time interval.

[0123] The first time interval may be the time interval between the reception time of the RAR defined in the protocol and the transmission time of the PUSCH scheduled by the RAR, and the target time may be the target time determined by the protocol agreement or the network side configuration, which may be understood as a time offset.

[0124] The first minimum time interval may be the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR, which is defined in the protocol.

[0125] In the above implementation, the time interval or minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR can be enhanced by introducing the target time, so as to improve the transmission performance of the PUSCH.

[0126] The first processing time is a processing time for the transmission repetition of the downlink channel, which may be a newly defined or additionally defined processing time for the transmission repetition of the downlink channel, for example, an additional processing time for RAR PDSCH repetition transmission (RAR PDSCH repetition) is defined instead of N T,1 , where N T,1 A parameter in a protocol-defined formula for determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR.

[0127] The second processing time is the processing time of the PUSCH in the case of repeated transmission of the downlink channel. It can be a newly defined or additionally defined PUSCH processing time for the case of repeated transmission of the downlink channel. For example, an additional PUSCH processing time for RAR PDSCH repetition is defined to replace N T,2 , where N T,2A parameter in a protocol-defined formula for determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR.

[0128] The second time interval determined based on the first processing time may be a method for determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR according to the protocol, and a second time interval determined based on the first processing time; the second minimum time interval determined based on the first processing time may be a method for determining the minimum time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR according to the protocol, and a second minimum time interval determined based on the first processing time.

[0129] The third time interval determined based on the second processing time may be a third time interval determined based on the second processing time according to a method for determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR as defined in the protocol; the third minimum time interval determined based on the second processing time may be a third minimum time interval determined based on the second processing time according to a method for determining the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR as defined in the protocol.

[0130] In the above implementation, it is possible to determine the time interval or minimum time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR based on the first processing time or the second processing time, thereby enhancing the time interval or minimum time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR to improve the transmission performance of the PUSCH.

[0131] As an optional implementation manner, when the uplink channel includes a PUCCH for feedback of the HARQ-ACK of Msg4, the time interval from the reception time of the Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 includes:

[0132] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0133] or,

[0134] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0135] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0136] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0137] In some implementations, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0138] A time domain resource for actually sending the second PDSCH;

[0139] An effective time domain resource capable of sending the second PDSCH;

[0140] Available time domain resources capable of sending the second PDSCH;

[0141] The time domain resource where the second PDSCH is located.

[0142] In some implementations, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0143] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0144] In some embodiments, the second PDSCH may be a Msg4 PDSCH. In addition, the second PDSCH is a specific transmission or a predefined transmission for repeated transmission of the Msg4 PDSCH, specifically a transmission carrying a contention resolution ID. Here, a transmission may also be referred to as a repetition.

[0145] For example, for the HARQ feedback transmission of Msg4 PDSCH, the reference time of the Msg4 PDSCH reception time and the corresponding PUCCH transmission time interval is the slot where a predefined PDSCH repetition transmission carrying the contention resolution ID is located.

[0146] The above-mentioned time interval determined based on the third reference time domain resource may be determined in accordance with the method for determining the time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 as agreed in the protocol, for example: according to the method for determining the time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 based on the reference slot as agreed in the protocol, the time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 is determined based on the third reference slot. Similarly, the above-mentioned time interval determined based on the fourth reference time domain resource may be determined in accordance with the method for determining the time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 as agreed in the protocol.

[0147] The above-mentioned minimum time interval determined based on the third reference time domain resource may be determined in accordance with the method for determining the minimum time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 agreed upon in the protocol, for example: according to the method for determining the minimum time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 based on the reference slot agreed upon in the protocol, the minimum time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 is determined based on the third reference slot. Similarly, the above-mentioned minimum time interval determined based on the fourth reference time domain resource may be determined in accordance with the method for determining the minimum time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the Msg4 agreed upon in the protocol, to determine the above-mentioned minimum time interval.

[0148] In the above implementation manner, it is possible to determine the time interval or minimum time interval from the reception time of Msg4 to the transmission time of PUCCH for feedback of HARQ-ACK of the Msg4 based on the third reference time domain resource or the fourth reference time domain resource, thereby enhancing the time interval or minimum time interval from the reception time of Msg4 to the transmission time of PUCCH for feedback of HARQ-ACK of the Msg4 to improve the transmission performance of PUCCH.

[0149] As an optional implementation manner, when the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval from the reception time of the MsgB to the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0150] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0151] or,

[0152] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0153] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0154] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0155] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0156] The sixth reference time domain resource may correspond to a time point of the RAR time window, and the sixth reference time domain resource may be a time domain resource corresponding to a predefined time point of the RAR time window, such as the starting slot of the RAR time window; the sixth reference time domain resource may correspond to a time point of the MsgB response time window, and the sixth reference time domain resource may be a time domain resource corresponding to a predefined time point of the MsgB response time window, such as the starting slot of the MsgB response time window.

[0157] In some implementations, the time domain resource corresponding to the third PDSCH includes at least one of the following:

[0158] The time domain resource for actually sending the third PDSCH;

[0159] An effective time domain resource capable of sending the third PDSCH;

[0160] Available time domain resources capable of sending the third PDSCH;

[0161] The time domain resource where the third PDSCH is located.

[0162] In some implementations, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0163] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0164] In some embodiments, the third PDSCH may be an MsgB PDSCH. In addition, the third PDSCH is a specific transmission or a predefined transmission for repeated transmission of the MsgB PDSCH, specifically a transmission carrying a contention resolution ID. Here, a transmission may also be referred to as a repetition.

[0165] For example, for HARQ feedback transmission of MsgB PDSCH, the reference time of the MsgB PDSCH reception time and the corresponding PUCCH transmission time interval is the slot where a predefined PDSCH repetitive transmission carrying the contention resolution ID is located.

[0166] The above-mentioned time interval determined based on the fifth reference time domain resource may be determined in accordance with the method for determining the time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB as agreed in the protocol, for example: according to the method for determining the time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB based on the reference slot as agreed in the protocol, the time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB is determined based on the third reference slot. Similarly, the above-mentioned time interval determined based on the sixth reference time domain resource may be determined in accordance with the method for determining the time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB as agreed in the protocol.

[0167] The above-mentioned minimum time interval determined based on the fifth reference time domain resource may be determined in accordance with the method for determining the minimum time interval from the reception time of MsgB to the transmission time of the PUCCH for feedback of the HARQ-ACK of the MsgB agreed upon in the protocol, for example: according to the method for determining the minimum time interval from the reception time of MsgB to the transmission time of the PUCCH for feedback of the HARQ-ACK of the MsgB based on the reference slot agreed upon in the protocol, the minimum time interval from the reception time of Msg4 to the transmission time of the PUCCH for feedback of the HARQ-ACK of the MsgB is determined based on the fifth reference slot. Similarly, the above-mentioned minimum time interval determined based on the sixth reference time domain resource may be determined in accordance with the method for determining the minimum time interval from the reception time of MsgB to the transmission time of the PUCCH for feedback of the HARQ-ACK of the MsgB agreed upon in the protocol, to determine the above-mentioned minimum time interval.

[0168] In the above implementation manner, it is possible to determine the time interval or minimum time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB based on the fifth reference time domain resource or the sixth reference time domain resource, thereby enhancing the time interval or minimum time interval from the reception time of MsgB to the transmission time of PUCCH for feedback of HARQ-ACK of the MsgB to improve the transmission performance of PUCCH.

[0169] As an optional implementation manner, the receiving time of the downlink channel includes at least one of the following:

[0170] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0171] The RAR time window may be a RAR window under a 4-step RACH, and the MsgB response time window may be a MsgB response window under a 2-step RACH.

[0172] This implementation method specifically determines the size of the RAR time window, determines the size of the MsgB response time window, and determines the duration of the contention resolution timer.

[0173] In this implementation, when repeated transmission is performed on the downlink channel and the downlink channel supports repeated transmission, at least one of the durations of the RAR time window, the MsgB response time window and the contention resolution timer can be determined, so that the terminal can better receive the downlink channel within the reception time of the downlink channel to improve the reception performance of the downlink channel, such as reducing the complexity of downlink channel reception.

[0174] In some implementations, at least one of the durations of the RAR time window, the MsgB response time window, and the contention resolution timer may be enhanced.

[0175] Optionally, the RAR time window includes:

[0176] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel.

[0177] The RAR time window defined for repeated transmission of the downlink channel may be an RAR time window additionally defined for repeated transmission of the downlink channel, for example, an additionally defined RAR window size specifically corresponding to supporting Msg2 / MsgB repetition.

[0178] The RAR time window that does not support repeated transmission of the downlink channel may be a RAR time window that has been defined in the protocol or is newly defined subsequently and does not support repeated transmission of the downlink channel.

[0179] The above added offset may be agreed upon by the protocol or configured on the network side.

[0180] In this implementation, the RAR time window can be enhanced by the above two methods to improve the downlink channel receiving performance of the terminal.

[0181] Optionally, the MsgB response time window includes:

[0182] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel.

[0183] The MsgB response time window defined for repeated transmission of the downlink channel may be an MsgB response time window additionally defined for repeated transmission of the downlink channel, for example, an additionally defined size of the MsgB response time window specifically corresponding to supporting MsgB repetition.

[0184] The MsgB response time window for not supporting repeated transmission of the downlink channel may be an MsgB response time window that is defined in the protocol or is newly defined subsequently and does not support repeated transmission of the downlink channel.

[0185] The above added offset may be agreed upon by the protocol or configured on the network side.

[0186] In this implementation, the MsgB response time window can be enhanced by the above two methods to improve the downlink channel receiving performance of the terminal.

[0187] Optionally, the duration of the contention resolution timer includes:

[0188] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0189] The duration of the contention resolution timer defined for the repeated transmission of the downlink channel may be the duration of the contention resolution timer additionally defined for the repeated transmission of the downlink channel, for example: the duration of the contention resolution timer (Contention resolution timer duration) additionally defined specifically corresponding to supporting Msg4 repetition.

[0190] The above-mentioned contention resolution timer for not supporting repeated transmission of the downlink channel may be a contention resolution timer that has been defined in the protocol or is newly defined subsequently and does not support repeated transmission of the downlink channel.

[0191] The above added offset may be agreed upon by the protocol or configured on the network side.

[0192] In this implementation, the duration of the contention resolution timer can be enhanced by the above two methods to improve the downlink channel reception performance of the terminal.

[0193] Optionally, the reception of repeated transmissions of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmissions of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, and the number of repetitions of the downlink channel.

[0194] The above-mentioned reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window. It can be pre-configured or pre-agreed that the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window, so as to achieve consistent understanding of the reception of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0195] The network side configuration may be that the network side configuration received by the terminal indicates whether crossing the RAR time window is allowed, so as to achieve consistent reception and understanding of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0196] The above determination based on the number of repetitions of the downlink channel may be a relationship between the number of repetitions and whether crossing the RAR time window is allowed, which may be determined based on the number of repetitions. This may also achieve consistent reception and understanding of repeated transmissions of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0197] Optionally, the reception of repeated transmissions of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmissions of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0198] The reception of repeated transmission of the above-mentioned downlink channel is not allowed to cross the MsgB response time window. It can be pre-configured or pre-agreed that the reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window, so as to achieve consistent understanding of the reception of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0199] The above network side configuration may be that the network side configuration received by the terminal indicates whether to allow crossing the MsgB response time window, so as to achieve consistent reception and understanding of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0200] The above determination based on the number of repetitions of the downlink channel may be a protocol agreement or a network-side configuration of the relationship between the number of repetitions and whether crossing the MsgB response time window is allowed, thereby determining whether crossing the MsgB response time window is allowed based on the number of repetitions. This may also enable the terminal and the network to have consistent reception and understanding of repeated transmissions of the downlink channel, thereby improving the transmission reliability of the downlink channel.

[0201] Optionally, the reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, and the number of repetitions of the downlink channel.

[0202] The reception of repeated transmission of the above-mentioned downlink channel is not allowed to cross the duration of the contention resolution timer. It can be pre-configured or pre-agreed that the reception of repeated transmission of the downlink channel is not allowed to cross the duration of the contention resolution timer, so as to achieve consistent understanding of the reception of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0203] The above-mentioned network side configuration may be that the network side configuration received by the terminal indicates whether to allow the duration of the contention resolution timer to be crossed, so as to achieve consistent reception and understanding of repeated transmission of the downlink channel by the terminal and the network, thereby improving the transmission reliability of the downlink channel.

[0204] The above-mentioned determination of the number of repetitions based on the downlink channel can be a protocol agreement or a network-side configuration of the relationship between the number of repetitions and whether the duration of the contention resolution timer is allowed to be crossed, thereby determining whether the duration of the contention resolution timer is allowed to be crossed based on the number of repetitions. In this way, the terminal and the network can also achieve consistent reception and understanding of the repeated transmission of the downlink channel, thereby improving the transmission reliability of the downlink channel.

[0205] In an embodiment of the present application, under target conditions, the sending time of the uplink channel or the receiving time of the downlink channel is determined; wherein the target conditions include at least one of the following: the downlink channel performs repeated transmission, the downlink channel supports repeated transmission; the downlink channel includes: the downlink channel that the terminal needs to receive before entering the connected state; the uplink channel is the uplink channel corresponding to the downlink channel. In this way, when the downlink channel performs repeated transmission or the downlink channel supports repeated transmission, the sending time of the uplink channel or the receiving time of the downlink channel can be determined, thereby enabling the terminal to support repeated transmission of the downlink channel, thereby improving the success rate of the terminal receiving the downlink channel, and improving the service performance of the terminal.

[0206] For example: In some scenarios, such as non-terrestrial network (NTN) scenarios, when the satellite needs to support multiple beams, the downlink transmission power of each beam will be reduced. At this time, the reception performance of Msg2 or MsgB or Msg4 PDSCH cannot meet the requirements because it does not support repeated transmission, making random access impossible, and thus making all services (such as new air interface carrying voice (Voice over New Radio, VoNR), low-speed data transmission) channels unable to proceed further. In this way, the embodiment of the present application supports reporting of the repeated transmission function of Msg2 / MsgB / Msg4PDSCH or the terminal's request for Msg2 / MsgB / Msg4 PDSCH repetition, thereby improving the service performance of the terminal.

[0207] It should be noted that the NTN scenario is only an applicable scenario provided by the embodiments of the present application. For example, the method provided by the embodiments of the present application can also be applied to the terrestrial network (TN) scenario.

[0208] For another example: When RAR supports repeated transmission, the reference slot of the scheduled PUSCH transmission time may be the slot where one of the multiple RAR repetitions is located. When Msg4 supports repeated transmission, the corresponding reference slot of the PUCCH transmission time for HARQ feedback may be the slot where one of the multiple Msg4 repetitions is located. When MsgB supports repeated transmission, the corresponding reference slot of the PUCCH transmission time for HARQ feedback may be the slot where one of the multiple MsgB repetitions is located. In these situations, the reference slot determined by the embodiments of the present application ensures that the network and the terminal have a consistent understanding of the scheduling time.

[0209] For another example: In some embodiments, in order to allow the network to send multiple PDCCHs and multiple RARs that schedule RARs within the RAR window (similar to multiple RAR transmissions within the RAR window), the RAR transmission time may also need to be completed within the RAR window as much as possible. In an embodiment of the present application, when RAR supports repetition, the RAR window length is extended, and it is determined whether the RAR repetition is allowed to exceed the RAR window to improve the performance of the terminal receiving RAR.

[0210] For another example: In some embodiments, in order to allow the network to schedule multiple Msg4 transmissions within the contention resolution timer duration (similar to multiple Msg4 transmissions within the contention resolution timer duration), the sending time of Msg4 may also need to be completed within the contention resolution timer duration as much as possible. In an embodiment of the present application, when Msg4 supports repetition, the length of the contention resolution timer duration is extended, and it is determined whether the repetition of Msg4 is allowed to exceed the contention resolution timer duration, so as to improve the performance of the terminal receiving Msg4.

[0211] See also Figure 3 , Figure 3 is a flow chart of another time determination method provided in an embodiment of the present application, such as Figure 3 As shown, the following steps are included:

[0212] Step 301: Under target conditions, the network side device determines the sending time of the uplink channel or the receiving time of the downlink channel;

[0213] The target condition includes at least one of the following:

[0214] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0215] The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state;

[0216] The uplink channel is an uplink channel corresponding to the downlink channel.

[0217] The above-mentioned network side device determines the sending time of the uplink channel or the receiving time of the downlink channel, which can also be understood as:

[0218] The network side device determines the receiving time of the uplink channel or the sending time of the downlink channel.

[0219] Optionally, the downlink channel that needs to be sent to the terminal before the terminal enters the connected state includes at least one of the following:

[0220] Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

[0221] Optionally, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0222] Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB;

[0223] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0224] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0225] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0226] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

[0227] Optionally, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0228] A time domain resource for actually sending the first PDSCH;

[0229] An effective time domain resource capable of sending the first PDSCH;

[0230] Available time domain resources capable of sending the first PDSCH;

[0231] The time domain resource where the first PDSCH is located.

[0232] Optionally, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0233] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0234] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0235] The first time interval plus the target time;

[0236] a second time interval determined based on the first processing time;

[0237] a third time interval determined based on the second processing time;

[0238] or,

[0239] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0240] The first minimum time interval plus the target time;

[0241] A second minimum time interval determined based on the first processing time

[0242] a third minimum time interval determined based on the second processing time;

[0243] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0244] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0245] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0246] or,

[0247] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0248] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0249] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0250] Optionally, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0251] A time domain resource for actually sending the second PDSCH;

[0252] An effective time domain resource capable of sending the second PDSCH;

[0253] Available time domain resources capable of sending the second PDSCH;

[0254] The time domain resource where the second PDSCH is located.

[0255] Optionally, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0256] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0257] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0258] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0259] or,

[0260] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0261] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0262] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0263] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0264] Optionally, the time domain resources corresponding to the third PDSCH include at least one of the following:

[0265] The time domain resource for actually sending the third PDSCH;

[0266] An effective time domain resource capable of sending the third PDSCH;

[0267] Available time domain resources capable of sending the third PDSCH;

[0268] The time domain resource where the third PDSCH is located.

[0269] Optionally, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0270] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0271] Optionally, the receiving time of the downlink channel includes at least one of the following:

[0272] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0273] Optionally, the RAR time window includes:

[0274] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel;

[0275] or,

[0276] The MsgB response time window includes:

[0277] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel;

[0278] or,

[0279] The duration of the contention resolution timer includes:

[0280] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0281] Optionally, the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0282] or,

[0283] The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0284] or,

[0285] The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0286] It should be noted that this embodiment is Figure 2 The implementation of the corresponding network side device in the embodiment shown in the figure can be found in the specific implementation of Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

[0287] The method provided in the embodiments of the present application is illustrated below by means of multiple embodiments:

[0288] Embodiment 1:

[0289] In this implementation, the determination of the PUSCH transmission time scheduled by the RAR is mainly described, which is specifically as follows:

[0290] When RAR supports repeated transmission, the reference slot of the PUSCH transmission time scheduled by RAR may be the slot where one of the multiple RAR repetitions is located, so that the reference slot is clearly determined to ensure that the network and the terminal have a consistent understanding of the scheduling time.

[0291] In some embodiments, the reference slot of the PUSCH scheduled by RAR (including RAR under 4-step RACH and fallback RAR under 2-step RACH) is a slot where a predefined PDSCH carrying a RAR message is repeatedly transmitted.

[0292] For example, when RAR PDSCH supports repeated transmission, the reference slot for determining the RAR scheduled PUSCH transmission time is defined as the slot where the last PDSCH is repeatedly transmitted. For example, the description is as follows:

[0293] For the reference time slot of a PUSCH transmission scheduled with a RAR UL grant, if the UE receives a PDSCH or the last repeated PDSCH (if PDSCH repetition is supported), and the RAR message carried by the PDSCH corresponds to a PRACH transmission from the terminal and ends in time slot n, the terminal shall receive the RAR message in time slot n+k2+Δ+2 μ ·K cell,offset PUSCH is sent in, where k2 is the slot level offset of the scheduling, Δ is a time offset specifically defined for PUSCH scheduled by RAR UL authorization, which is specifically agreed upon by the protocol, μ represents the subcarrier spacing configuration of PUSCH transmission, and K cell,offset Provided by the cell-specific offset (cellSpecificKoffset) parameter, otherwise, if not provided, K cell,offset =0.

[0294] As a sub-embodiment of the previous embodiment, the repetitive transmission of the predefined PDSCH needs to meet one or more of the following conditions:

[0295] The slot where PDSCH is actually sent.

[0296] A valid slot in which PDSCH repetitions can be sent;

[0297] Available slots where PDSCH repetitions can be sent;

[0298] The slot where the last PDSCH repetition is located.

[0299] For example, the description is as follows:

[0300] For the reference time slot of a PUSCH transmission scheduled by a RAR UL grant, if the UE receives a PDSCH and the RAR message carried by the PDSCH corresponds to a PRACH transmission from the terminal and ends in time slot n, or if the UE receives the last repeated PDSCH (if PDSCH repetition is supported) and the RAR message carried by the PDSCH corresponds to a PRACH transmission from the terminal and ends in an available time slot n, the terminal shall μ ·K cell,offset PUSCH is sent in, where k2 is the slot level offset of the scheduling, Δ is a time offset specifically defined for PUSCH scheduled by RAR UL authorization, which is specifically agreed upon by the protocol, μ represents the subcarrier spacing configuration of PUSCH transmission, and K cell,offset Because the cell-specific offset (cellSpecificKoffset) parameter is provided, otherwise, if it is not provided, K cell,offset =0.

[0301] In addition, considering that the corresponding PDSCH processing time is different when the RAR performs repeated transmission and when the RAR does not perform repeated transmission, in this embodiment, the interval between the RAR reception time and the RAR scheduled PUSCH transmission time is enhanced.

[0302] In some embodiments, when RAR supports repeated transmission, the interval from the RAR reception time to the RAR scheduled PUSCH transmission time needs to introduce one or more of the following changes compared to the case where RAR repeated transmission is not supported:

[0303] Introduce an additional time requirement, such as introducing a time offset;

[0304] An additional processing time for RAR PDSCH repetition is defined instead of N T,1 ;

[0305] An additional PUSCH processing time is defined for RAR PDSCH repetition instead of N T,2 .

[0306] The above new parameters or changed parameters may be configured by the network or specified by a protocol or determined by other parameters (such as the number of repetitions of the RAR PDSCH).

[0307] For example, it is described as follows:

[0308] The UE may assume that the minimum time interval between the last symbol of a received PDSCH carrying a RAR or the last symbol of the last received PDSCH repetition carrying a RAR and the first symbol of a PUSCH transmission scheduled by the corresponding RAR uplink grant is equal to N T,1 +N T,2 +0.5+N T,3 ms, where N T,1 Indicates the time length of N1 symbols, which is the time for UE to process downlink PDSCH and assumes that the UE has processing capability level 1 and is configured with additional PDSCH demodulation reference signal, N T,2 is the time length of N2 symbols, represents the time for UE to process uplink PUSCH and assumes that the UE has processing capability level 1. The symbols of N1 and N2 are determined by the smaller subcarrier spacing of PDSCH and PUSCH. For a subcarrier spacing of 15kHz, the UE assumes N 1,0 = 14. The time offset here is N T,3 In case of PDSCH repetition, it is provided by the parameter DeltaRARRepetition (if DeltaRARRepetition exists), otherwise it is 0. The above N1 and N2 are specifically integers greater than or equal to 1.

[0309] In some embodiments, the reference slot of the PUSCH scheduled by RAR (including RAR under 4-step RACH and fallback RAR under 2-step RACH) is a reference to a certain time point of the RAR window, such as the first slot at the beginning of the RAR window.

[0310] Embodiment 2:

[0311] In this embodiment, the determination of the PUCCH transmission time of Msg4 HARQ-ACK feedback is mainly described, which is as follows:

[0312] When Msg4 supports repeated transmission, the reference slot of the corresponding PUCCH transmission time for HARQ feedback may be the slot where one of the multiple Msg4 repetitions is located. The reference slot is clearly determined in this embodiment to ensure that the network and the terminal have a consistent understanding of the scheduling time.

[0313] In some embodiments, for HARQ feedback transmission of Msg4 PDSCH, the reference time of the Msg4 PDSCH reception time and the corresponding PUCCH transmission time interval is a predefined slot carrying a contention resolution ID where a PDSCH is repeatedly transmitted.

[0314] For example, it is described as follows:

[0315] The UE may assume that the minimum time interval between the last symbol of a received PDSCH or the last PDSCH repetition (if PDSCH repetition is supported) and the first symbol of the PUCCH transmission carrying the HARQ-ACK feedback information for the corresponding PDSCH is equal to N T,1 +0.5ms, where N T,1 Indicates the time length of N1 symbols, which is the time for the UE to process the downlink PDSCH and assumes that the UE has processing capability level 1 and is configured with additional PDSCH demodulation reference signals. For a subcarrier spacing of 15kHz, the UE assumes N 1,0 = 14. The above N1 is specifically an integer greater than or equal to 1.

[0316] As a sub-embodiment of the previous embodiment, the repetitive transmission of the predefined PDSCH needs to meet one or more of the following conditions:

[0317] The slot where PDSCH is actually sent.

[0318] A valid slot in which PDSCH repetitions can be sent;

[0319] Available slots where PDSCH repetitions can be sent;

[0320] The slot where the last PDSCH repetition is located.

[0321] In some embodiments, for HARQ feedback transmission of Msg4 PDSCH, the reference time of the Msg4 PDSCH reception time and the corresponding PUCCH transmission time interval is the slot where the contention resolution timer start or restart is located.

[0322] Embodiment three:

[0323] This embodiment mainly describes the determination of the PUCCH transmission time of MsgB HARQ-ACK feedback, which is as follows:

[0324] When MsgB supports repeated transmission, the reference slot of the corresponding PUCCH transmission time for HARQ feedback may be the slot where one of the multiple MsgB repetitions is located. The reference slot is clearly determined in this embodiment to ensure that the network and the terminal have a consistent understanding of the scheduling time.

[0325] In some embodiments, for HARQ feedback transmission of MsgB PDSCH, the reference time of the MsgB PDSCH reception time and the corresponding PUCCH transmission time interval is a predefined slot carrying a contention resolution ID where PDSCH is repeatedly transmitted.

[0326] For example, the predefined PDSCH repetition here is the last PDSCH repetition.

[0327] As a sub-embodiment of the previous embodiment, the repetitive transmission of the predefined PDSCH needs to meet one or more of the following conditions:

[0328] The slot where PDSCH is actually sent.

[0329] A valid slot in which PDSCH repetitions can be sent;

[0330] Available slots where PDSCH repetitions can be sent;

[0331] The slot where the last PDSCH repetition is located.

[0332] In some embodiments, for HARQ feedback transmission of MsgB PDSCH, the reference time of the time interval between MsgB PDSCH reception time and the corresponding PUCCH transmission time is a certain time point of the MsgB window, such as the slot where the start point of the MsgB response window is located.

[0333] Embodiment 4:

[0334] This embodiment mainly describes the enhancement of the RAR window when Msg2 / MsgB are repeated, as follows:

[0335] In this embodiment, in order to allow the network to send multiple PDCCHs and multiple RARs (similar to multiple RAR transmissions in the RAR window) that schedule RARs within the RAR window, the RAR transmission time also needs to be completed within the RAR window as much as possible. When the RAR supports repetition, in this embodiment, the RAR window length is extended. At the same time, it is also determined whether the repetition of the RAR is allowed to exceed the RAR window.

[0336] In some embodiments, when Msg2 / MsgB are repeated, the length of the RAR window is increased by one or more of the following methods:

[0337] Additional definitions specifically correspond to the size of the RAR window that supports Msg2 / MsgB repetitions;

[0338] Relative to the size of the RAR window that does not support Msg2 / MsgB duplication, the offset of introducing the additional RAR window size may be predefined by the protocol or configured by the network.

[0339] In some embodiments, when Msg2 / MsgB are repeated, the reception of the repeated Msg2 / MsgB is not allowed to cross the RAR window.

[0340] In some embodiments, when Msg2 / MsgB is repeated, whether the repeated reception of Msg2 / MsgB is allowed to cross the RAR window depends on one of the following factors:

[0341] Configured by the network;

[0342] Depends on the number of Msg2 / MsgB repeats.

[0343] Embodiment five:

[0344] This embodiment mainly describes the enhancement of contention resolution time when Msg4 is repeated, as follows:

[0345] In this embodiment, in order to allow the network to schedule multiple Msg4 transmissions within the Contention resolution timer duration (similar to multiple Msg4 transmissions within the Contention resolution timer duration), the sending time of Msg4 may also need to be completed within the Contention resolution timer duration as much as possible. When Msg4 supports repetition, the length of the Contention resolution timer duration is extended in this embodiment. At the same time, it is also determined whether the repetition of Msg4 is allowed to exceed the Contention resolution timer duration.

[0346] In some embodiments, when Msg4 is repeated, the length of the Contentionresolution timer duration is enhanced according to one or more of the following methods:

[0347] The size of the Contention resolution timer duration specifically corresponding to the support of Msg4 repetition is additionally defined;

[0348] Relative to the size of the RAR window that does not support Msg4 repetition, an additional offset of the Contention Resolution Timer duration size is introduced, which can be predefined by the protocol or configured by the network.

[0349] In some embodiments, when Msg4 is repeated, the reception of the repeated Msg4 is not allowed to exceed the Contention Resolution Timer duration.

[0350] In some embodiments, when Msg4 is repeated, whether the reception of the repeated Msg4 is allowed to exceed the Contentionresolution timer duration depends on one of the following factors:

[0351] Configured by the network;

[0352] Depends on the number of repetitions of Msg4.

[0353] In the embodiment of the present application, the enhancement of Msg2 / MsgB / Msg4 PDSCH in the NTN scenario can be achieved, and it can also be applied to the enhancement of Msg2 / MsgB / Msg4 PDSCH in the TN network, and can be applied to all downlink channels before the terminal enters the RRC connection state.

[0354] In the embodiments of the present application, a variety of methods for determining the uplink and downlink scheduling time under Msg2 / MsgB / Msg4 PDSCH repetition are proposed, so that the network and the terminal have the same understanding of the scheduling time of the uplink and downlink channels, thereby ensuring that the relevant channels can be correctly received. In addition, in the embodiments of the present application, while ensuring that Msg2, MsgB and Msg4 can use time domain repetition to improve robustness, it ensures that the time window for RAR and Msg4 reception is maintained within a certain controllable range, reducing random access delay and reducing terminal reception complexity.

[0355] The time determination method provided in the embodiment of the present application can be executed by a time determination device. In the embodiment of the present application, the time determination device provided in the embodiment of the present application is described by taking the notification device executing the time determination method as an example.

[0356] See also Figure 4 , Figure 4 is a structural diagram of a time determination device provided in an embodiment of the present application, such as Figure 4 As shown, the time determination device 400 includes:

[0357] A determination module 401, configured to determine a transmission time of an uplink channel or a reception time of a downlink channel under target conditions;

[0358] The target condition includes at least one of the following:

[0359] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0360] The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state;

[0361] The uplink channel is an uplink channel corresponding to the downlink channel.

[0362] Optionally, the downlink channel that the terminal needs to receive before entering the connected state includes at least one of the following:

[0363] Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

[0364] Optionally, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0365] Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB;

[0366] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0367] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0368] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0369] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

[0370] Optionally, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0371] A time domain resource for actually sending the first PDSCH;

[0372] An effective time domain resource capable of sending the first PDSCH;

[0373] Available time domain resources capable of sending the first PDSCH;

[0374] The time domain resource where the first PDSCH is located.

[0375] Optionally, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0376] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0377] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0378] The first time interval plus the target time;

[0379] a second time interval determined based on the first processing time;

[0380] a third time interval determined based on the second processing time;

[0381] or,

[0382] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0383] The first minimum time interval plus the target time;

[0384] A second minimum time interval determined based on the first processing time

[0385] a third minimum time interval determined based on the second processing time;

[0386] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0387] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0388] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0389] or,

[0390] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0391] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0392] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0393] Optionally, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0394] A time domain resource for actually sending the second PDSCH;

[0395] An effective time domain resource capable of sending the second PDSCH;

[0396] Available time domain resources capable of sending the second PDSCH;

[0397] The time domain resource where the second PDSCH is located.

[0398] Optionally, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0399] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0400] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0401] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0402] or,

[0403] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0404] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0405] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0406] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0407] Optionally, the time domain resources corresponding to the third PDSCH include at least one of the following:

[0408] The time domain resource for actually sending the third PDSCH;

[0409] An effective time domain resource capable of sending the third PDSCH;

[0410] Available time domain resources capable of sending the third PDSCH;

[0411] The time domain resource where the third PDSCH is located.

[0412] Optionally, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0413] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0414] Optionally, the receiving time of the downlink channel includes at least one of the following:

[0415] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0416] Optionally, the RAR time window includes:

[0417] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel;

[0418] or,

[0419] The MsgB response time window includes:

[0420] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel;

[0421] or,

[0422] The duration of the contention resolution timer includes:

[0423] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0424] Optionally, the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0425] or,

[0426] The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0427] or,

[0428] The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0429] The above time determination device can improve the service performance of the terminal.

[0430] In the embodiments of the present application, the time determination device may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. For example, the electronic device may be a terminal, or may be other devices other than a terminal. For example, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0431] The time determination device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0432] See also Figure 5 , Figure 5 is a structural diagram of another time determination device provided in an embodiment of the present application, such as Figure 5 As shown, the time determination device 500 includes:

[0433] The determination module 501 is used to determine the sending time of the uplink channel or the receiving time of the downlink channel under the target conditions;

[0434] The target condition includes at least one of the following:

[0435] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0436] The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state;

[0437] The uplink channel is an uplink channel corresponding to the downlink channel.

[0438] Optionally, the downlink channel that needs to be sent to the terminal before the terminal enters the connected state includes at least one of the following:

[0439] Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

[0440] Optionally, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0441] Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB;

[0442] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0443] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0444] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0445] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

[0446] Optionally, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0447] A time domain resource for actually sending the first PDSCH;

[0448] An effective time domain resource capable of sending the first PDSCH;

[0449] Available time domain resources capable of sending the first PDSCH;

[0450] The time domain resource where the first PDSCH is located.

[0451] Optionally, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0452] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0453] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0454] The first time interval plus the target time;

[0455] a second time interval determined based on the first processing time;

[0456] a third time interval determined based on the second processing time;

[0457] or,

[0458] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0459] The first minimum time interval plus the target time;

[0460] A second minimum time interval determined based on the first processing time

[0461] a third minimum time interval determined based on the second processing time;

[0462] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0463] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0464] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0465] or,

[0466] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0467] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0468] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0469] Optionally, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0470] A time domain resource for actually sending the second PDSCH;

[0471] An effective time domain resource capable of sending the second PDSCH;

[0472] Available time domain resources capable of sending the second PDSCH;

[0473] The time domain resource where the second PDSCH is located.

[0474] Optionally, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0475] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0476] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0477] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0478] or,

[0479] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0480] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0481] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0482] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0483] Optionally, the time domain resources corresponding to the third PDSCH include at least one of the following:

[0484] The time domain resource for actually sending the third PDSCH;

[0485] An effective time domain resource capable of sending the third PDSCH;

[0486] Available time domain resources capable of sending the third PDSCH;

[0487] The time domain resource where the third PDSCH is located.

[0488] Optionally, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0489] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0490] Optionally, the receiving time of the downlink channel includes at least one of the following:

[0491] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0492] Optionally, the RAR time window includes:

[0493] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel;

[0494] or,

[0495] The MsgB response time window includes:

[0496] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel;

[0497] or,

[0498] The duration of the contention resolution timer includes:

[0499] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0500] Optionally, the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0501] or,

[0502] The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0503] or,

[0504] The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0505] The above time determination device can improve the service performance of the terminal.

[0506] The time determination device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or a network side device.

[0507] The time determination device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0508] Optional, such as Figure 6 As shown, the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, and the memory 602 stores a program or instruction that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned terminal side time determination method embodiment, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various steps of the network side device side time determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0509] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the processor is used for the terminal to determine the sending time of an uplink channel or the receiving time of a downlink channel under a target condition; wherein the target condition includes at least one of the following: the downlink channel performs repeated transmission, the downlink channel supports repeated transmission; the downlink channel includes: the downlink channel that the terminal needs to receive before entering a connected state; the uplink channel is the uplink channel corresponding to the downlink channel. Specifically, Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0510] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of a processor 710.

[0511] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The communication device structure shown in the figure does not constitute a limitation on the communication device. The communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0512] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processing unit 7041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0513] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 701 can transmit the data to the processor 710 for processing; in addition, the RF unit 701 can send uplink data to the network side device. Generally, the RF unit 701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0514] The memory 709 can be used to store software programs or instructions and various data. The memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 709 may include a volatile memory or a non-volatile memory, or the memory 709 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0515] The processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.

[0516] The processor 710 or the radio frequency unit 701 is configured to determine a transmission time of an uplink channel or a reception time of a downlink channel under target conditions;

[0517] The target condition includes at least one of the following:

[0518] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0519] The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state;

[0520] The uplink channel is an uplink channel corresponding to the downlink channel.

[0521] Optionally, the downlink channel that the terminal needs to receive before entering the connected state includes at least one of the following:

[0522] Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

[0523] Optionally, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0524] Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB;

[0525] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0526] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0527] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0528] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

[0529] Optionally, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0530] A time domain resource for actually sending the first PDSCH;

[0531] An effective time domain resource capable of sending the first PDSCH;

[0532] Available time domain resources capable of sending the first PDSCH;

[0533] The time domain resource where the first PDSCH is located.

[0534] Optionally, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0535] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0536] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0537] The first time interval plus the target time;

[0538] a second time interval determined based on the first processing time;

[0539] a third time interval determined based on the second processing time;

[0540] or,

[0541] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0542] The first minimum time interval plus the target time;

[0543] A second minimum time interval determined based on the first processing time

[0544] a third minimum time interval determined based on the second processing time;

[0545] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0546] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0547] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0548] or,

[0549] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0550] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0551] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0552] Optionally, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0553] A time domain resource for actually sending the second PDSCH;

[0554] An effective time domain resource capable of sending the second PDSCH;

[0555] Available time domain resources capable of sending the second PDSCH;

[0556] The time domain resource where the second PDSCH is located.

[0557] Optionally, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0558] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0559] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0560] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0561] or,

[0562] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0563] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0564] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0565] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0566] Optionally, the time domain resources corresponding to the third PDSCH include at least one of the following:

[0567] The time domain resource for actually sending the third PDSCH;

[0568] An effective time domain resource capable of sending the third PDSCH;

[0569] Available time domain resources capable of sending the third PDSCH;

[0570] The time domain resource where the third PDSCH is located.

[0571] Optionally, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0572] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0573] Optionally, the receiving time of the downlink channel includes at least one of the following:

[0574] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0575] Optionally, the RAR time window includes:

[0576] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel;

[0577] or,

[0578] The MsgB response time window includes:

[0579] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel;

[0580] or,

[0581] The duration of the contention resolution timer includes:

[0582] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0583] Optionally, the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0584] or,

[0585] The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0586] or,

[0587] The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0588] The above terminal can improve the service performance of the terminal.

[0589] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment, and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0590] An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the processor is used to determine the sending time of an uplink channel or the receiving time of a downlink channel under a target condition; wherein the target condition includes at least one of the following: the downlink channel performs repeated transmission and the downlink channel supports repeated transmission; the downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters a connected state; the uplink channel is an uplink channel corresponding to the downlink channel.

[0591] like Figure 8 As shown, the network side device 800 includes: an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804 and a memory 805. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and sends it out through the antenna 801.

[0592] The method executed by the wireless access network device in the above embodiment may be implemented in the baseband device 803, which includes a baseband processor.

[0593] The baseband device 803 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 8 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 805 through a bus interface to call the program in the memory 805 to execute the network device operations shown in the above method embodiment.

[0594] The radio access network device may further include a network interface 806, which is, for example, a common public radio interface (CPRI).

[0595] Specifically, the network side device 800 of the embodiment of the present invention further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0596] The processor 804 or the radio frequency device 802 is used to determine the transmission time of the uplink channel or the reception time of the downlink channel under the target conditions;

[0597] The target condition includes at least one of the following:

[0598] The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission;

[0599] The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state;

[0600] The uplink channel is an uplink channel corresponding to the downlink channel.

[0601] Optionally, the downlink channel that needs to be sent to the terminal before the terminal enters the connected state includes at least one of the following:

[0602] Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

[0603] Optionally, the uplink channel corresponding to the downlink channel includes at least one of the following:

[0604] Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB;

[0605] The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

[0606] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes:

[0607] A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or

[0608] The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

[0609] Optionally, the time domain resource corresponding to the first PDSCH includes at least one of the following:

[0610] A time domain resource for actually sending the first PDSCH;

[0611] An effective time domain resource capable of sending the first PDSCH;

[0612] Available time domain resources capable of sending the first PDSCH;

[0613] The time domain resource where the first PDSCH is located.

[0614] Optionally, the first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0615] The first PDSCH is the last transmission of repeated transmission of the downlink channel.

[0616] Optionally, when the uplink channel includes the PUSCH scheduled by the RAR, the time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0617] The first time interval plus the target time;

[0618] a second time interval determined based on the first processing time;

[0619] a third time interval determined based on the second processing time;

[0620] or,

[0621] In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following:

[0622] The first minimum time interval plus the target time;

[0623] A second minimum time interval determined based on the first processing time

[0624] a third minimum time interval determined based on the second processing time;

[0625] The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

[0626] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0627] A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource;

[0628] or,

[0629] In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes:

[0630] A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource;

[0631] Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

[0632] Optionally, the time domain resource corresponding to the second PDSCH includes at least one of the following:

[0633] A time domain resource for actually sending the second PDSCH;

[0634] An effective time domain resource capable of sending the second PDSCH;

[0635] Available time domain resources capable of sending the second PDSCH;

[0636] The time domain resource where the second PDSCH is located.

[0637] Optionally, the second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0638] The second PDSCH is the last transmission of repeated transmission of the downlink channel.

[0639] Optionally, in a case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back the HARQ-ACK of the MsgB includes:

[0640] A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource;

[0641] or,

[0642] In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes:

[0643] A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource;

[0644] The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel;

[0645] The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

[0646] Optionally, the time domain resources corresponding to the third PDSCH include at least one of the following:

[0647] The time domain resource for actually sending the third PDSCH;

[0648] An effective time domain resource capable of sending the third PDSCH;

[0649] Available time domain resources capable of sending the third PDSCH;

[0650] The time domain resource where the third PDSCH is located.

[0651] Optionally, the third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or

[0652] The third PDSCH is the last transmission of repeated transmission of the downlink channel.

[0653] Optionally, the receiving time of the downlink channel includes at least one of the following:

[0654] The duration of the RAR time window, MsgB response time window, and contention resolution timer.

[0655] Optionally, the RAR time window includes:

[0656] A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel;

[0657] or,

[0658] The MsgB response time window includes:

[0659] an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel;

[0660] or,

[0661] The duration of the contention resolution timer includes:

[0662] The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

[0663] Optionally, the reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0664] or,

[0665] The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel;

[0666] or,

[0667] The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

[0668] The above network side equipment can improve the service performance of the terminal.

[0669] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned time determination method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0670] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0671] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned time determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0672] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0673] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned time determination method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0674] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the terminal side time determination method provided in the embodiment of the present application, and the network side device can be used to execute the steps of the network side device side time determination method provided in the embodiment of the present application.

[0675] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0676] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0677] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A time determination method, characterized in that: include: Under the target conditions, the terminal determines the transmission time of the uplink channel or the reception time of the downlink channel; The target condition includes at least one of the following: The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission; The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state; The uplink channel is an uplink channel corresponding to the downlink channel.

2. The method according to claim 1, characterized in that The downlink channel that the terminal needs to receive before entering the connected state includes at least one of the following: Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

3. The method according to claim 1 or 2, characterized in that The uplink channel corresponding to the downlink channel includes at least one of the following: Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB; The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

4. The method according to claim 3, characterized in that In the case where the uplink channel includes the PUSCH scheduled by the RAR, the transmission time of the PUSCH scheduled by the RAR includes: A transmission time determined based on a first reference time domain resource, where the first reference time domain resource is a time domain resource corresponding to a first PDSCH carrying the RAR, where the first PDSCH is one transmission in repeated transmission of the downlink channel; or The sending time is determined based on the second reference time domain resource, where the second reference time domain resource corresponds to a time point in the RAR time window, or the second reference time domain resource corresponds to a time point in the MsgB response time window.

5. The method according to claim 4, characterized in that The time domain resource corresponding to the first PDSCH includes at least one of the following: A time domain resource for actually sending the first PDSCH; An effective time domain resource capable of sending the first PDSCH; Available time domain resources capable of sending the first PDSCH; The time domain resource where the first PDSCH is located.

6. The method according to claim 4 or 5, characterized in that The first PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or The first PDSCH is the last transmission of repeated transmission of the downlink channel.

7. The method according to any one of claims 3 to 6, characterized in that In the case where the uplink channel includes the PUSCH scheduled by the RAR, the time interval from the reception time of the RAR to the transmission time of the PUSCH scheduled by the RAR is one of the following: The first time interval plus the target time; a second time interval determined based on the first processing time; a third time interval determined based on the second processing time; or, In the case where the uplink channel includes the PUSCH scheduled by the RAR, the minimum time interval between the reception time of the RAR and the transmission time of the PUSCH scheduled by the RAR is one of the following: The first minimum time interval plus the target time; A second minimum time interval determined based on the first processing time a third minimum time interval determined based on the second processing time; The first processing time is a processing time for repeated transmission of the downlink channel, and the second processing time is a processing time for PUSCH when repeated transmission is performed on the downlink channel.

8. The method according to claim 3, characterized in that In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes: A time interval determined based on a third reference time domain resource; or a time interval determined based on a fourth reference time domain resource; or, In the case where the uplink channel includes a PUCCH for feeding back the HARQ-ACK of Msg4, the minimum time interval between the reception time of the Msg4 and the transmission time of the PUCCH for feeding back the HARQ-ACK of the Msg4 includes: A minimum time interval determined based on a third reference time domain resource; or a minimum time interval determined based on a fourth reference time domain resource; Among them, the third reference time domain resource is the time domain resource corresponding to the second PDSCH carrying the contention resolution identifier, the second PDSCH is one of the repeated transmissions of the downlink channel, and the fourth reference time domain resource is the time domain resource where the contention resolution timer is started or restarted.

9. The method according to claim 8, characterized in that The time domain resource corresponding to the second PDSCH includes at least one of the following: A time domain resource for actually sending the second PDSCH; An effective time domain resource capable of sending the second PDSCH; Available time domain resources capable of sending the second PDSCH; The time domain resource where the second PDSCH is located.

10. The method according to claim 8 or 9, characterized in that The second PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or The second PDSCH is the last transmission of repeated transmission of the downlink channel.

11. The method according to claim 3, characterized in that In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes: A time interval determined based on a fifth reference time domain resource; or a transmission time determined based on a sixth reference time domain resource; or, In the case where the uplink channel includes a PUCCH for feeding back HARQ-ACK of MsgB, the minimum time interval between the reception time of the MsgB and the transmission time of the PUCCH for feeding back HARQ-ACK of the MsgB includes: A minimum time interval determined based on the fifth reference time domain resource; or a minimum time interval determined based on the sixth reference time domain resource; The fifth reference time domain resource is a time domain resource corresponding to a third PDSCH carrying a contention resolution identifier, and the third PDSCH is one transmission in repeated transmission of the downlink channel; The sixth reference time domain resource corresponds to a time point of the RAR time window, or the sixth reference time domain resource corresponds to a time point of the MsgB response time window.

12. The method according to claim 11, characterized in that The time domain resource corresponding to the third PDSCH includes at least one of the following: The time domain resource for actually sending the third PDSCH; An effective time domain resource capable of sending the third PDSCH; Available time domain resources capable of sending the third PDSCH; The time domain resource where the third PDSCH is located.

13. The method according to claim 11 or 12, characterized in that: The third PDSCH is the nth transmission in repeated transmission of the downlink channel, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the downlink channel; or The third PDSCH is the last transmission of repeated transmission of the downlink channel.

14. The method according to any one of claims 1 to 13, characterized in that The receiving time of the downlink channel includes at least one of the following: The duration of the RAR time window, MsgB response time window, and contention resolution timer.

15. The method according to claim 14, characterized in that The RAR time window includes: A RAR time window defined for repeated transmission of the downlink channel; or a RAR time window obtained by adding an offset to a RAR time window that does not support repeated transmission of the downlink channel; or, The MsgB response time window includes: an MsgB response time window defined for repeated transmission of the downlink channel; or an MsgB response time window obtained by adding an offset to an MsgB response time window that does not support repeated transmission of the downlink channel; or, The duration of the contention resolution timer includes: The duration of a contention resolution timer defined for repeated transmission of the downlink channel; or the duration of a contention resolution timer obtained by adding an offset to a contention resolution timer that does not support repeated transmission of the downlink channel.

16. The method according to claim 14 or 15, characterized in that The reception of repeated transmission of the downlink channel is not allowed to cross the RAR time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the RAR time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel; or, The reception of repeated transmission of the downlink channel is not allowed to cross the MsgB response time window; or, whether the reception of repeated transmission of the downlink channel is allowed to cross the MsgB response time window is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel; or, The reception of repeated transmissions of the downlink channel is not allowed to span the duration of the contention resolution timer; or, whether the reception of repeated transmissions of the downlink channel is allowed to span the duration of the contention resolution timer is determined based on at least one of the following: network side configuration, the number of repetitions of the downlink channel.

17. A time determination method, characterized in that: include: Under target conditions, the network side device determines the sending time of the uplink channel or the receiving time of the downlink channel; The target condition includes at least one of the following: The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission; The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state; The uplink channel is an uplink channel corresponding to the downlink channel.

18. The method according to claim 17, characterized in that The downlink channel that needs to be sent to the terminal before the terminal enters the connected state includes at least one of the following: Message 2 Msg2 physical downlink shared channel PDSCH, message B MsgB PDSCH, message 4 Msg4 PDSCH, paging PDSCH.

19. The method according to claim 17 or 18, characterized in that The uplink channel corresponding to the downlink channel includes at least one of the following: Physical uplink shared channel PUSCH for random access response RAR scheduling, physical uplink control channel PUCCH for feedback of hybrid automatic repeat request confirmation HARQ-ACK of Msg4, and PUCCH for feedback of HARQ-ACK of MsgB; The RAR includes at least one of the following: RAR carried by Msg2 PDSCH and RAR carried by MsgB PDSCH.

20. The method according to any one of claims 17 to 19, characterized in that The receiving time of the downlink channel includes at least one of the following: The duration of the RAR time window, MsgB response time window, and contention resolution timer.

21. A time determination device, characterized in that: include: A determination module, used for the terminal to determine the sending time of the uplink channel or the receiving time of the downlink channel under target conditions; The target condition includes at least one of the following: The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission; The downlink channel includes: a downlink channel that the terminal needs to receive before entering the connected state; The uplink channel is an uplink channel corresponding to the downlink channel.

22. A time determination device, characterized in that: include: A determination module, used to determine the sending time of the uplink channel or the receiving time of the downlink channel under target conditions; The target condition includes at least one of the following: The downlink channel performs repeated transmission, and the downlink channel supports repeated transmission; The downlink channel includes: a downlink channel that needs to be sent to the terminal before the terminal enters the connected state; The uplink channel is an uplink channel corresponding to the downlink channel.

23. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the time determination method according to any one of claims 1 to 16 are implemented.

24. A network side device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the time determination method according to any one of claims 17 to 20 are implemented.

25. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the time determination method as described in any one of claims 1-16, or implements the steps of the time determination method as described in any one of claims 17 to 20.

Images