Wireless communication method, terminal device and network device

Abstract

Provided in an embodiment of the present application are a wireless communication method, a terminal device and a network device, the method comprising: in an initial access stage, repeatedly sending a first physical uplink control channel (PUCCH) to the network device. According to the invention, repeated transmission of the PUCCH is introduced in the initial access stage, so that the success rate of initial access can be improved, and the coverage performance can be improved. Particularly, in a communication scene with limited coverage performance, such as an NTN system, repeated transmission of the PUCCH is introduced in the initial access stage, so that the terminal equipment can successfully send the PUCCH involved in the initial access stage, and further the success rate of initial access and the coverage performance can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, a terminal device, and a network device. Background Art

[0002] As of now, the User Equipment (UE) only supports repeated transmission of the Physical Uplink Shared Channel (PUSCH) of Message 3 (Msg3) during the initial access phase. Considering the communication scenarios with limited coverage performance, such as the Non-Terrestrial Network (NTN) system, the current transmission mechanism in the initial access phase may not be able to successfully send the Physical Uplink Control Channel (PUCCH) involved in the initial access phase, resulting in the failure of the UE's initial access and reduced coverage performance. Summary of the invention

[0003] The embodiments of the present application provide a wireless communication method, a terminal device, and a network device, which can improve the success rate of initial access and the coverage performance.

[0004] In a first aspect, the present application provides a wireless communication method, including:

[0005] In the initial access phase, the first physical uplink control channel PUCCH is repeatedly sent to the network device.

[0006] In a second aspect, the present application provides a wireless communication method, including:

[0007] In each second TDW of the at least one second nominal time window TDW, the power of the message 3 physical uplink shared channel Msg3 PUSCH is maintained consistent and the phase of the Msg3 PUSCH is maintained continuous.

[0008] In a third aspect, the present application provides a wireless communication method, including:

[0009] In the initial access phase, the first physical uplink control channel PUCCH sent by the terminal device is repeatedly received.

[0010] In a fourth aspect, the present application provides a wireless communication method, including:

[0011] Based on the demodulation reference signal DMRS in each second nominal time window TDW in at least one second nominal time window TDW, joint channel estimation is performed on the message 3 physical uplink shared channel Msg3 PUSCH.

[0012] In a fifth aspect, the present application provides a terminal device for executing the method in any one of the first to second aspects or their respective implementations. Specifically, the terminal device includes a functional module for executing the method in any one of the first to second aspects or their respective implementations.

[0013] In one implementation, the terminal device may include a processing unit, which is used to perform functions related to information processing. For example, the processing unit may be a processor.

[0014] In one implementation, the terminal device may include a sending unit and / or a receiving unit. The sending unit is used to perform functions related to sending, and the receiving unit is used to perform functions related to receiving. For example, the sending unit may be a transmitter or a transmitter, and the receiving unit may be a receiver or a receiver. For another example, the terminal device is a communication chip, the sending unit may be an input circuit or an interface of the communication chip, and the sending unit may be an output circuit or an interface of the communication chip.

[0015] In a sixth aspect, the present application provides a network device for executing the method in any one of the third to fourth aspects or their respective implementations. Specifically, the network device includes a functional module for executing the method in any one of the third to fourth aspects or their respective implementations.

[0016] In one implementation, the network device may include a processing unit, which is used to perform functions related to information processing. For example, the processing unit may be a processor.

[0017] In one implementation, the network device may include a sending unit and / or a receiving unit. The sending unit is used to perform functions related to sending, and the receiving unit is used to perform functions related to receiving. For example, the sending unit may be a transmitter or a transmitter, and the receiving unit may be a receiver or a receiver. For another example, the network device is a communication chip, the receiving unit may be an input circuit or an interface of the communication chip, and the sending unit may be an output circuit or an interface of the communication chip.

[0018] In a seventh aspect, the present application provides a terminal device, comprising a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in any one of the first to second aspects or their respective implementations.

[0019] In one implementation, the number of the processor is one or more, and the number of the memory is one or more.

[0020] In one implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0021] In one implementation, the terminal device further includes a transmitter (transmitter) and a receiver (receiver).

[0022] In an eighth aspect, the present application provides a network device, comprising a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in any one of the third to fourth aspects or their respective implementations.

[0023] In one implementation, the number of the processor is one or more, and the number of the memory is one or more.

[0024] In one implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0025] In one implementation, the network device further includes a transmitter (transmitter) and a receiver (receiver).

[0026] In a ninth aspect, the present application provides a chip for implementing the method in any one of the first to fourth aspects or in each of its implementations. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in any one of the first to fourth aspects or in each of its implementations.

[0027] In a tenth aspect, the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to fourth aspects above or its various implementations.

[0028] In an eleventh aspect, the present application provides a computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the above-mentioned first to fourth aspects or any of their implementations.

[0029] In a twelfth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method in any one of the first to fourth aspects or in each of its implementations.

[0030] Based on the above technical solution, the present application introduces repeated transmission of PUCCH in the initial access phase, which can improve the success rate of initial access and thus improve coverage performance. In particular, in communication scenarios with limited coverage performance, such as NTN systems, repeated transmission of PUCCH introduced in the initial access phase can enable the terminal device to successfully send the PUCCH involved in the initial access phase, thereby improving the success rate of initial access and coverage performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figures 1 to 3 It is a schematic block diagram of the system framework provided in the embodiment of the present application.

[0032] Figure 4 and Figure 5 Schematic diagrams of NTN scenarios based on transparent forwarding satellites and regenerative forwarding satellites are shown respectively.

[0033] Figure 6 It is a schematic flowchart of a contention-based random access process provided in an embodiment of the present application.

[0034] Figure 7 It is a schematic flowchart of a wireless communication method performed by a terminal device provided in an embodiment of the present application.

[0035] Figure 8 is a schematic diagram of at least one first nominal TDW provided in an embodiment of the present application.

[0036] Fig. 9 and Fig.10 It is a schematic diagram of the relationship between at least one first nominal TDW and a frequency hopping interval provided in an embodiment of the present application.

[0037] Fig.11 This is another schematic flowchart of a wireless communication method performed by a terminal device provided in an embodiment of the present application.

[0038] Fig.12 is a schematic diagram of at least one second nominal TDW provided in an embodiment of the present application.

[0039] Fig.13 and Fig.14 It is a schematic diagram of the relationship between at least one second nominal TDW and the frequency hopping interval provided in an embodiment of the present application.

[0040] Fig.15 It is a schematic flowchart of a wireless communication method performed by a network device provided in an embodiment of the present application.

[0041] Fig.16 This is another schematic flowchart of a wireless communication method performed by a network device provided in an embodiment of the present application.

[0042] Fig.17 and Fig.18 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0043] Fig.19 and Fig. 20 It is a schematic block diagram of a network device provided in an embodiment of the present application.

[0044] Fig.21 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0045] Fig. 22 It is a schematic block diagram of the chip provided in the embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] It should be noted that the term "indication" can be a direct indication, an indirect indication, or an indication of an associated relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an associated relationship between A and B. In addition, the description "at..." involved in the embodiments of the present application can be interpreted as "if" or "if" or "when..." or "in response to". Similarly, depending on the context, the phrase "if determined" or "if (stated condition or event) is detected" can be interpreted as "when determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)".

[0048] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0049] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0050] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0051] exist Figure 1 In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal device 110 (eg, UE) located in the coverage area.

[0052] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0053] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0054] For example, the terminal device 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0055] The terminal device 110 may be used for device-to-device (D2D) communication.

[0056] The wireless communication system 100 may also include a core network device 130 for communicating with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

[0057] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

[0058] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

[0059] Figure 1 A base station, a core network device and two terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0060] In the New Radio (NR) system, non-terrestrial networks (NTN) are considered to provide communication services to users. NTN generally uses satellite communication to provide communication services to ground users. Compared with ground cellular network communication, satellite communication has many unique advantages. First, satellite communication is not limited by the user's geographical location. For example, general land communication cannot cover areas such as oceans, mountains, deserts, etc. where communication equipment cannot be set up or where communication coverage is not provided due to sparse population. For satellite communication, since one satellite can cover a large area of ​​land, and the satellite can orbit around the earth, in theory, every corner of the earth can be covered by satellite communication. Secondly, satellite communication has great social value. Satellite communication can cover remote mountainous areas, poor and backward countries or regions at a low cost, so that people in these areas can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital divide with developed areas and promoting the development of these areas. Thirdly, satellite communication has a long distance, and the cost of communication does not increase significantly as the communication distance increases; finally, satellite communication has high stability and is not restricted by natural disasters.

[0061] Figure 2 A schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0062] like Figure 2As shown, it includes a terminal device 1101 and a satellite 1102, and wireless communication can be performed between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 can also be called NTN. Figure 2 In the architecture of the communication system shown, the satellite 1102 may have the function of a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. In the system architecture, the satellite 1102 may be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1102, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0063] Figure 3 A schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0064] like Figure 3 As shown, it includes terminal device 1201, satellite 1202 and base station 1203. Wireless communication can be performed between terminal device 1201 and satellite 1202, and satellite 1202 and base station 1203 can communicate with each other. The network formed by terminal device 1201, satellite 1202 and base station 1203 can also be called NTN. Figure 3 In the architecture of the communication system shown in FIG. 1 , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be called a network device. In some embodiments of the present application, the communication system may include multiple network devices 1203, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application. The network device 1203 may be Figure 1 The network device 120 in.

[0065] It should be understood that the satellite 1102 or satellite 1202 includes but is not limited to:

[0066] Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, High Elliptical Orbit (HEO) satellites, etc. Satellites can use multiple beams to cover the ground. For example, a satellite can form dozens or even hundreds of beams to cover the ground. In other words, a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers to ensure satellite coverage and improve the system capacity of the entire satellite communication system.

[0067] As an example, the altitude range of LEO can be 500km~1500km, the corresponding orbital period can be about 1.5 hours~2 hours, the signal propagation delay of single-hop communication between users can generally be less than 20ms, the maximum satellite visible time can be 20 minutes, the signal propagation distance of LEO is short and the link loss is small, and the transmission power requirement of user terminals is not high. The orbital altitude of GEO can be 35786km, the rotation period around the earth can be 24 hours, and the signal propagation delay of single-hop communication between users can generally be 250ms.

[0068] Normally, in order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0069] It should be noted that Figures 1 to 3 It is only to illustrate the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0070] Satellites can be divided into two types based on the functions they provide: transparent payload and regenerative payload. For transparent payload satellites, they only provide wireless frequency filtering, frequency conversion and amplification functions, and only provide transparent forwarding of signals without changing the waveform signal they forward. For regenerative payload satellites, in addition to providing wireless frequency filtering, frequency conversion and amplification functions, they can also provide demodulation / decoding, routing / conversion, encoding / modulation functions, and have some or all of the functions of a base station.

[0071] In the NTN, one or more gateways may be included for communication between satellites and terminals.

[0072] Figure 4 and Figure 5 Schematic diagrams of NTN scenarios based on transparent forwarding satellites and regenerative forwarding satellites are shown respectively.

[0073] like Figure 4 As shown in FIG, for NTN scenarios based on transparent forwarding satellites, the gateway and the satellite communicate through a feeder link, and the satellite and the terminal can communicate through a service link. Figure 5 As shown, for the NTN scenario based on regenerative forwarding satellites, satellites communicate with each other through interstar links, gateways and satellites communicate with each other through feeder links, and satellites and terminals communicate with each other through service links.

[0074] With people's pursuit of speed, latency, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the 3GPP international standard organization began to develop 5G. The main application scenarios of 5G include: Enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive machine type of communication (mMTC). Among them, eMBB aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. Since eMBB may be deployed in different scenarios. For example, indoors, urban areas, rural areas, etc., their capabilities and requirements are also quite different, so they cannot be generalized. They can be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical characteristics of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.

[0075] To facilitate understanding of the solution provided by this application, the technical contents related to the solution provided by this application are explained below.

[0076] (1) Random access process.

[0077] After the cell search process, the terminal device has achieved downlink synchronization with the cell, so the terminal device can receive downlink data. However, the terminal device can only perform uplink transmission after achieving uplink synchronization with the cell. The terminal device can establish a connection with the cell and achieve uplink synchronization through the Random Access Procedure (RAP). In other words, through random access, the terminal device can obtain uplink synchronization and obtain the unique identifier assigned to it by the network device, namely the Cell Radio Network Temporary Identity (C-RNTI). Therefore, random access can be used not only in initial access, but also in the case of user uplink synchronization loss.

[0078] Optionally, the random access process in the embodiment of the present application may generally be triggered by one of the following types of triggering events:

[0079] (1) Initial access

[0080] (2) Handover.

[0081] (3)RRC Connection Re-establishment

[0082] (4) In the RRC connected state, when downlink data arrives, the uplink is in an "out-of-sync" state.

[0083] At this time, after the downlink data arrives, the terminal device needs to reply with an Acknowledgement (ACK) or a Negative Acknowledgement (NACK).

[0084] (5) In the RRC connected state, when uplink data arrives, the uplink is in an "out-of-sync" state.

[0085] (6) In the RRC connected state, there is no available Physical Uplink Control Channel (PUCCH) resource for Scheduling Request (SR) transmission. At this time, the terminal device that is already in the uplink synchronization state can be allowed to use the Random Access Channel (RACH) to replace the role of SR.

[0086] (7) The terminal device transitions from the RRC inactive state (RRC_INACTIVE) to the active state (RRC_ACTIVE).

[0087] (8) The terminal device requests other system information (OSI).

[0088] (9) Terminal equipment beam failure recovery.

[0089] There are two main forms of random access process, including contention-based random access (Contention Based Random Access, CBRA) and non-contention-based random access (Contention free Random Access, CFRA).

[0090] Figure 6 It is a flow interaction diagram of the contention-based random access process.

[0091] Combine the following Figure 6 The contention-based random access process is described.

[0092] like Figure 6 As shown, the random access process may include the following four steps:

[0093] Step 1, Msg 1.

[0094] The terminal device sends Msg 1 to the base station to tell the network device that the terminal device has initiated a random access request. The Msg 1 carries a random access preamble (RAP), also known as a random access preamble sequence, preamble sequence, preamble code, etc. At the same time, Msg 1 can also be used by the network device to estimate the transmission delay between it and the terminal device and calibrate the uplink time.

[0095] Specifically, the terminal device selects a preamble index and a PRACH resource for sending the preamble; then the terminal device transmits the selected preamble on the PRACH. The network device will notify all terminal devices by broadcasting a system information block (SIB) to inform them of the time-frequency resources on which the preamble is allowed to be transmitted, for example, SIB2.

[0096] Step 2, Msg 2.

[0097] After receiving Msg 1 sent by the terminal device, the network device sends Msg 2, i.e., a random access response (RAR) message, to the terminal device. The Msg 2 may carry, for example, a time advance (TA), an uplink authorization instruction such as the configuration of uplink resources, and a temporary cell-radio network temporary identity (TC-RNTI).

[0098] The terminal device monitors the Physical Downlink Control Channel (PDCCH) within the random access response time window (RAR window) to receive the RAR message replied by the network device. The RAR message can be descrambled using the corresponding Random Access Radio Network Temporary Identifier (RA-RNTI).

[0099] If the terminal device does not receive a RAR message replied by the network device within the RAR time window, it is considered that the random access process has failed.

[0100] If the terminal device successfully receives a RAR message, and the preamble index carried in the RAR message is the same as the preamble index sent by the terminal device through Msg 1, it is considered that the RAR is successfully received, and the terminal device can stop monitoring within the RAR time window.

[0101] Among them, Msg 2 may include RAR messages for multiple terminal devices, and the RAR message of each terminal device may include the random access preamble code identifier (RAP Identify, RAPID) used by the terminal device, information on resources used to transmit Msg 3, TA adjustment information, TC-RNTI, etc.

[0102] Step 3, Msg 3.

[0103] After receiving the RAR message, the terminal device determines whether the RAR message belongs to itself. For example, the terminal device can use the preamble code identifier to check. After determining that it is a RAR message belonging to itself, the terminal device generates Msg3 at the RRC layer and sends Msg 3 to the network device. It needs to carry the identification information of the terminal device.

[0104] Specifically, for different random access triggering events, Msg 3 in step 3 of the 4-step random access process may include different contents for scheduled transmission.

[0105] For example, for the initial access scenario, Msg 3 may include an RRC connection request (RRCConnection Request) generated by the RRC layer, which carries at least the non-access stratum (NAS) identification information of the terminal device, and may also carry, for example, the serving temporary mobile user identity (S-TMSI) or a random number of the terminal device.

[0106] For another example, for a connection reestablishment scenario, Msg 3 may include an RRC connection reestablishment request (RRCConnection Re-establishment Request) generated by the RRC layer and does not carry any NAS message. In addition, it may also carry, for example, a cell radio network temporary identifier (Cell Radio Network Temporary Identifier, C-RNTI) and protocol control information (Protocol Control Information, PCI).

[0107] For another example, for a switching scenario, Msg 3 may include an RRC switching completion message (RRCHandover Confirm) generated by the RRC layer and the C-RNTI of the terminal device, and may also carry, for example, a buffer status report (Buffer Status Report, BSR); for other triggering events such as the arrival of uplink / downlink data, Msg 3 needs to at least include the C-RNTI of the terminal device.

[0108] Step 4, Msg 4.

[0109] The network device sends Msg 4 to the terminal device, and the terminal device correctly receives Msg 4 to complete contention resolution. For example, during the RRC connection establishment process, Msg 4 may carry the RRC connection establishment message.

[0110] Since the terminal device in step 3 carries its own unique identifier in Msg 3, such as C-RNTI or identification information from the core network (such as S-TMSI or a random number), the network device will carry the unique identifier of the terminal device in Msg 4 in the contention resolution mechanism to specify the terminal device that wins the contention. Other terminal devices that do not win the contention resolution will re-initiate the random access process.

[0111] It should be noted that when a terminal device needs to initiate contention random access on a licensed band, since multiple terminal devices may be configured with a common PRACH resource, different terminal devices may compete for resources on the same PRACH resource.

[0112] When a resource conflict occurs, for example, multiple terminal devices select the same PRACH opportunity (PRAChoccasion). In this case, the network device can carry a backoff indicator (BI) in the RAR message of Msg 2. The terminal device that has a resource conflict can generate a random number based on the backoff indicator, so that when the next PRACH resource arrives, it can delay according to the random number, thereby delaying the sending of Msg 1 by the corresponding time, thereby alleviating the probability of resource conflict to a certain extent.

[0113] For RACH triggered by HO and beam failure recovery (BFR), the network can configure dedicated RACH resources for the user, so that the UE can choose to do CF-RACH.

[0114] Taking RACH triggered by BFR as an example, when the terminal device selects the RACH resource, it needs to first determine the measurement result of the synchronization signal block (SSB) or the channel state information reference signal (CSI-RS). For example, whether the reference signal receiving power (RSRP) meets the corresponding threshold. If the threshold is met, the terminal device selects a preamble from the preamble corresponding to the SSB or CSI-RS to transmit message 1 (Msg 1); at this time, RACH is based on non-contention-based random access (Contention free Random Access, CFRA). If there is no SSB or CSI-RS that meets the threshold, the terminal device randomly selects an SSB and selects a preamble from the preamble corresponding to this SSB to send Msg 1. At this time, RACH is based on contention-based random access (Contention Based Random Access, CBRA).

[0115] (2) Msg3 PUSCH repeated transmission mechanism.

[0116] The Msg3 PUSCH repetition transmission mechanism is: the base station provides the UE with a candidate value set numberOfMsg3Repetitions for the number of PUSCH repetition transmissions scheduled by RAR uplink grant or TC-RNTI scrambled CRC DCI 0_0 in the common RACH configuration parameter RACH-ConfigCommon, and the Msg3 PUSCH repetition transmission is PUSCH repetition transmission type A.

[0117] The UE uses the RSRP result obtained by measuring the downlink signal as a reference for measuring the uplink coverage performance. For example, the threshold for repeated transmission of Msg3 PUSCH can be defined as T Msg3 , if the RSRP measurement result of the downlink path loss reference signal is lower than T Msg3 , when sending Msg1, the UE implicitly requests the base station to repeat the transmission of Msg3 PUSCH by selecting a specific PRACH resource, that is, a specific PRACH preamble set U1.

[0118] If the UE requests repeated transmission of Msg3 PUSCH, the UE repeatedly sends Msg3 PUSCH in K time slots, where:

[0119] The determination of the number of repeated transmissions K is shown in Table 1, that is, the number of repeated transmissions K can be indicated by the two most significant bits (MostSignificant Bit, MSB) (i.e., the most significant 2 bits) of the modulation and coding strategy (Modulation and Coding Scheme, MCS) field in the RAR uplink authorization or DCI0_0 from a set of four candidate values ​​provided by the system parameter numberOfMsg3Repetitions; if numberOfMsg3Repetitions is not configured, it is indicated from {1,2,3,4}.

[0120] Table 1. Mapping relationship between 2MSBs of MCS information field and the number of repeated transmissions K of Msg3

[0121]

[0122] As shown in Table 1, the code point may be the 2 MSBs of the MCS field in the RAR uplink grant or DCI 0_0. One of the code points is used to indicate a value of the number of repeated transmissions K.

[0123] Since the UE requests Msg3 PUSCH to be retransmitted, the MCS information field will be reinterpreted. MCS The determination is shown in Table 2 or Table 3, and is indicated by the 2 least significant bits (Least Significant Bit, LSB) (i.e., the least significant 2 bits) of the MCS field in the RAR uplink authorization or the 3 LSBs of the MCS field in DCI 0_0 from a set of 8 candidate values ​​provided by the system parameter mcs-Msg3Repetition; if mcs-Msg3Repetition is not configured, it is indicated from the default candidate value set.

[0124] Table 2. 2LSBs of the MCS information field in the RAR uplink grant to the MCS index I MCS Mapping

[0125]

[0126] As shown in Table 2, the code point may be 2 LSBs of the MCS field in the RAR uplink grant. One of the code points is used to indicate a value of the number of repeated transmissions K.

[0127] Table 3. 3LSBs of the MCS information field in DCI 0_0 of the TC-RNTI scrambled CRC to MCS index I MCS Mapping

[0128]

[0129]

[0130] As shown in Table 3, the code point may be 3 LSBs of the MCS field in DCI 0_0. One of the code points is used to indicate a value of the number of repeated transmissions K.

[0131] (3) Joint channel estimation mechanism.

[0132] For PUSCH repetition transmission type A scheduled by DCI 0_1 or DCI 0_2, PUSCH repetition transmission type A using unscheduled grant, PUSCH repetition transmission type B and PUSCH transmission with multi-slot determined transmission block (TB), if the high-level parameter PUSCH-DMRS-Bundling is enabled; or for PUCCH repetition transmission, if the high-level parameter PUCCH-DMRS-Bundling is enabled. The UE can determine one or more nominal time windows (Time Domain Window, TDW) according to the following process, and the base station binds the DMRS on each time slot in the TDW for joint channel estimation:

[0133] For PUSCH repetition transmission type A, PUSCH repetition transmission type B and PUSCH transmission with multi-slot determined TB, each nominal TDW is determined as follows:

[0134] If the higher-level parameter PUSCH-TimeDomainWindowLength is configured, the nominal TDW length is the value corresponding to the parameter; if the higher-level parameter is not configured, the nominal TDW length is based on Calculate the nominal TDW length, which is the minimum of the two, where It indicates the maximum time that the UE can maintain power consistency and phase continuity to support DMRS bundling, and M indicates the number of consecutive time slots occupied by PUSCH transmission;

[0135] The first time slot of the first PUSCH transmission is used as the starting point of the first nominal TDW; the last time slot of the last PUSCH transmission is used as the ending point of the nominal TDW; the first time slot used for PUSCH transmission after the last time slot of the previous nominal TDW is used as the starting point of the next nominal TDW.

[0136] For PUCCH repetitive transmission, the number of time slots for each nominal TDW except the last nominal TDW is determined as follows:

[0137] If the high-level parameter PUCCH-TimeDomainWindowLength is configured, the nominal TDW length is the value corresponding to the parameter; if the high-level parameter is not configured, the nominal TDW length is based on Calculate, which is the minimum of the two, where It indicates the maximum time that the UE can maintain power consistency and phase continuity to support DMRS bundling, and M indicates the number of consecutive time slots occupied by PUCCH transmission;

[0138] The first time slot of the first PUCCH transmission is used as the starting point of the first nominal TDW; the last time slot of the last PUCCH transmission is used as the ending point of the nominal TDW; the first time slot used for PUCCH transmission after the last time slot of the previous nominal TDW is used as the starting point of the next nominal TDW.

[0139] As can be seen from the above, the UE only supports Msg3 PUSCH repeated transmission in the initial access phase, and does not support other coverage enhancement schemes. For example, the UE does not support PUCCH repeated transmission and joint channel estimation in the initial access phase. Considering that in communication scenarios with limited coverage performance, such as the NTN system, the current transmission mechanism in the initial access phase may not be able to successfully send the physical uplink control channel (Physical Uplink Control Channel, PUCCH) involved in the initial access phase, resulting in UE initial access failure and reduced coverage performance. In view of this, the present application provides a wireless communication method that improves the coverage performance in the initial access phase through further coverage enhancement, thereby ensuring that the UE can still successfully access the system in scenarios with limited coverage performance.

[0140] Figure 7 2 is a schematic flow chart of a wireless communication method 200 provided in an embodiment of the present application. The wireless communication method 200 may be executed by a terminal device. For example, the wireless communication method 200 may be executed by Figure 1 The terminal device shown is executed.

[0141] like Figure 7 As shown, the method 200 may include:

[0142] S210, in the initial access phase, the terminal device repeatedly sends a first physical uplink control channel (Physical Uplink Control Channel, PUCCH) to the network device.

[0143] In this embodiment, repeated transmission of the PUCCH is introduced in the initial access phase, which can improve the success rate of the initial access and further improve the coverage performance.

[0144] In particular, in communication scenarios with limited coverage performance, such as the NTN system, introducing repeated transmission of PUCCH in the initial access phase can enable the terminal device to successfully send the PUCCH involved in the initial access phase, thereby improving the success rate of initial access and coverage performance.

[0145] Exemplarily, the first PUCCH includes but is not limited to feedback information of Msg4.

[0146] Of course, in other alternative embodiments, repeated transmission of PUCCH can also be introduced in other scenarios to improve coverage performance. For example, the first PUCCH can be repeatedly sent to the network after a contention-based random access process, after sending Msg4, or before establishing a radio resource control (RRC) connection.

[0147] Exemplarily, the contention-based random access process may be triggered by one of the following triggering events:

[0148] (1) Initial access

[0149] (2) Handover.

[0150] (3)RRC Connection Re-establishment

[0151] (4) In the RRC connected state, when downlink data arrives, the uplink is in an "out-of-sync" state.

[0152] At this time, after the downlink data arrives, the terminal device needs to reply with an Acknowledgement (ACK) or a Negative Acknowledgement (NACK).

[0153] (5) In the RRC connected state, when uplink data arrives, the uplink is in an "out-of-sync" state.

[0154] (6) In the RRC connected state, there is no available Physical Uplink Control Channel (PUCCH) resource for Scheduling Request (SR) transmission. At this time, the terminal device that is already in the uplink synchronization state can be allowed to use the Random Access Channel (RACH) to replace the role of SR.

[0155] (7) The terminal device transitions from the RRC inactive state (RRC_INACTIVE) to the active state (RRC_ACTIVE).

[0156] (8) The terminal device requests other system information (OSI).

[0157] (9) Terminal equipment beam failure recovery.

[0158] In some embodiments, the method 200 may further include:

[0159] The terminal device receives first indication information sent by the network device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

[0160] Exemplarily, the number of repeated transmissions of the first PUCCH is a positive integer greater than 1.

[0161] In some embodiments, the first indication information is also used to indicate the number of repeated transmissions of Msg3 PUSCH.

[0162] Exemplarily, the number of repeated transmissions of the Msg3 PUSCH is a positive integer greater than 1.

[0163] Of course, in other alternative embodiments, the indication information used to indicate the number of repeated transmissions of the first PUCCH and the indication information used to indicate the number of repeated transmissions of Msg3PUSCH may also be different indication information, and the present application does not make specific limitations on this.

[0164] In some embodiments, the first indication information is carried in a first modulation and coding scheme (MCS) field.

[0165] Exemplarily, the first indication information is the value of a bit in the first MCS domain.

[0166] In this embodiment, by reinterpreting the first MCS field, the number of repeated transmissions of the first PUCCH introduced in the initial access phase can be determined without adding an additional bit field, that is, without adding additional signaling overhead.

[0167] In some embodiments, the first MCS domain is the MCS domain in a random access response (RAR) uplink grant, or the first MCS domain is the MCS domain in downlink control information (DCI) 0_0.

[0168] Exemplarily, the RAR uplink grant or the DCI 0_0 also includes a resource indication field for scheduling Msg3 PUSCH.

[0169] In some embodiments, the first indication information is carried in at least one most significant bit (MSB) in the first MCS field.

[0170] Exemplarily, the first indication information is the value of a bit in the at least one MSB.

[0171] It should be noted that, since the first indication information is carried in the first MCS field, and the first MCS field is usually used to indicate the MCS index I MCS Therefore, the present application may be used to indicate the MCS index I in the first MCS domain. MCS The bits need to be reinterpreted.

[0172] In some embodiments, at least one least significant bit (LSB) in the first MCS field carries information for indicating an MCS index.

[0173] Exemplarily, a value of at least one LSB in the first MCS field is used to indicate the MCS index.

[0174] For example, MCS index I MCS The determination method is the same as the MCS index I after the terminal device requests Msg3PUSCH to be repeatedly transmitted MCS The determination method can be the same, that is, the MCS index I can be indicated by 2 LSBs of the MCS field in the RAR uplink grant or 3 LSBs of the MCS field in the DCI 0_0 from the index candidate value set including 8 index candidate values ​​provided by the system parameter mcs-Msg3Repetition MCS If mcs-Msg3Repetition is not configured, the MCS index I is indicated from the default index candidate value set. MCS For example, the MCS index I may be indicated from the index candidate value set in the manner of Table 2 or Table 3 mentioned above. MCS .

[0175] In some embodiments, the at least one LSB is used to indicate the MCS index in an index candidate value set configured by a system parameter, or the at least one LSB is used to indicate the MCS index in a default index candidate value set.

[0176] Exemplarily, the index candidate value set includes at least one index candidate value, and the at least one LSB is used to indicate the MCS index in the at least one index candidate value.

[0177] In some embodiments, the first indication information is carried in a first PUCCH resource indication field.

[0178] Exemplarily, all bits in the first PUCCH resource indication field are used to indicate the number of repeated transmissions of the first PUCCH and the transmission resources of the first PUCCH. Optionally, when the first PUCCH includes feedback information of Msg4, all bits in the first PUCCH resource indication field are used to indicate the number of repeated transmissions of the first PUCCH and the transmission resources of the feedback information of Msg4.

[0179] Exemplarily, the first PUCCH resource indication field includes an information field for carrying the first indication information and a resource indication field for indicating the transmission resource of the first PUCCH. Optionally, when the first PUCCH includes feedback information of Msg4, the first PUCCH resource indication field includes an information field for carrying the first indication information and a resource indication field for indicating the transmission resource of the feedback information of Msg4.

[0180] In this embodiment, considering that the first PUCCH is transmitted after the Msg3 PUSCH, by reinterpreting the first PUCCH resource indication field in the DCI used to schedule the Msg3 PUSCH (for example, DCI 1_0 of TC-RNTI scrambled CRC), the number of repeated transmissions of the first PUCCH introduced in the initial access stage can be determined without adding an additional bit field, that is, without adding additional signaling overhead.

[0181] In some embodiments, the first PUCCH resource indication field includes a resource indication field in DCI 1_0 of a temporary Cell Radio Network Temporary Identifier (TC-RNTI) scrambled cyclic redundancy check (CRC).

[0182] Exemplarily, the DCI 1_0 of the TC-RNTI scrambled CRC is a DCI used to indicate the transmission resources of the first PUCCH.

[0183] In some embodiments, the first PUCCH resource indication field is also used to indicate the transmission resources of Msg4.

[0184] Exemplarily, when the first PUCCH includes feedback information of Msg4, all bits in the first PUCCH resource indication field are simultaneously used to indicate: the number of repeated transmissions of the first PUCCH, the transmission resources of the feedback information of the Msg4 and the transmission resources of the Msg4.

[0185] Exemplarily, when the first PUCCH includes feedback information of Msg4, the first PUCCH resource indication field includes an information field for carrying the first indication information, a resource indication field for indicating the transmission resources of the feedback information of the Msg4, and a resource indication field for indicating the transmission resources of the Msg4.

[0186] In some embodiments, the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a default set of candidate values.

[0187] Exemplarily, the set of candidate values ​​for the number of times includes at least one candidate value for the number of times, and the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in the at least one candidate value for the number of times.

[0188] Exemplarily, the system parameters include parameters in a system information block (SIB) 1.

[0189] Exemplarily, the network device may configure, in a system message (e.g., the network device may configure, in SIB1 of the system message), for the terminal device a set of candidate values ​​numberOfPUCCHRepetitions for the number of PUCCH repetition transmissions that can be used in the initial access phase (i.e., the number of repetition transmissions of the first PUCCH). For example, numberOfPUCCHRepetitions = {1, 2, 4, 8}. Of course, in other alternative embodiments, the candidate values ​​in the set of candidate values ​​may also take other values ​​or include other numbers of candidate values, and this application does not specifically limit this.

[0190] In some embodiments, the maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the number candidate value set.

[0191] In some embodiments, the first indication information is carried in at least one most significant bit MSB in the first MCS domain, and the maximum number of values ​​of the at least one MSB is equal to the number of candidate values ​​in the candidate value set.

[0192] Exemplarily, assuming that the number of repeated transmissions of the first PUCCH is recorded as N, N can be indicated by the 2 MSBs of the first MCS field from the number candidate value set configured by the system parameter numberOfPUCCHRepetitions, or N can be indicated by the 2 MSBs of the MCS field in DCI 0_0 from the number candidate value set configured by the system parameter numberOfPUCCHRepetitions. For example, the number candidate value set includes 4 number candidate values, that is, if the network device configures numberOfPUCCHRepetitions for the terminal device, numberOfPUCCHRepetitions includes 4 values, and if the network device does not configure numberOfPUCCHRepetitions for the terminal device, the default number candidate value set includes 4 default number candidate values, such as {1,2,4,8}.

[0193] The following is an exemplary description of the mapping relationship between the 2 MSBs of the first MCS domain and the number of repeated transmissions N of the first PUCCH in conjunction with Table 4.

[0194] Table 4. Mapping relationship between the 2 MSBs of the first MCS domain and the number of repetition transmissions N of the first PUCCH

[0195]

[0196] As shown in Table 4, if the values ​​of the two MSBs of the first MCS domain are 00, if the network device configures numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the first value of numberOfPUCCHRepetitions; if the network device does not configure numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the first default candidate value in the default candidate value set, that is, the number of repeated transmissions N of the first PUCCH is 1. If the values ​​of the two MSBs of the first MCS domain are 01, if the network device configures numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the second value of numberOfPUCCHRepetitions; if the network device does not configure numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the second default candidate value in the default candidate value set, that is, the number of repeated transmissions N of the first PUCCH is 2. Similarly, when the values ​​of the two MSBs of the first MCS domain are 10 or 11, the corresponding number of repeated transmissions N of the first PUCCH can also be determined.

[0197] In some embodiments, if the first indication information is carried in at least one highest bit MSB in the first MCS domain, and the maximum number of values ​​of the at least one MSB is greater than the number of candidate values ​​in the number candidate value set, then the multiple values ​​of the at least one MSB correspond to a candidate value in the number candidate set; or the first indication information is carried in one or more MSBs in the at least one MSB; or the first indication information is carried in one or more LSBs in the at least one MSB.

[0198] In this embodiment, if the number of candidate values ​​in the candidate value set is less than the number of values ​​that can be indicated by at least one MSB in the first MCS domain, the introduction of specific rules can ensure that each value of at least one MSB in the first MCS domain can be mapped to the specified candidate value, thereby ensuring the validity of the first indication information.

[0199] Exemplarily, in the mapping table from the value of at least one MSB in the first MCS domain to the number of repeated transmissions N of the first PUCCH, the number of candidate values ​​in the number of candidate values ​​set can be copied. For example, when the number of candidate values ​​set includes 4 number of candidate values, and when at least one MSB in the first MCS domain is a 3-bit indication domain, at least one MSB in the first MCS domain can indicate 8 number of candidate values, at this time, in the mapping table from the value of at least one MSB in the first MCS domain to the number of repeated transmissions N of the first PUCCH, 4 number of candidate values ​​in the number of candidate values ​​set can be copied once, so that every 2 values ​​of at least one MSB in the first MCS domain can correspond to 1 number of candidate values ​​in the number of candidate values ​​set.

[0200] Exemplarily, the number of repetitions of the first PUCCH can be indicated from the number candidate value set by X LSBs (the lowest X bits) of at least one MSB in the first MCS domain, where X can be 1 / 2 / 3. For example, when the number candidate value set includes 4 number candidate values ​​and at least one MSB in the first MCS domain is a 3-bit indication domain, at this time, the number of repetitions of the first PUCCH can be indicated from the number candidate value set by 2 LSBs (the lowest 2 bits) of at least one MSB in the first MCS domain.

[0201] The following is an exemplary description of the mapping relationship between the value of at least one MSB in the first MCS domain and the number of repeated transmissions N of the first PUCCH in conjunction with Table 5.

[0202] Table 5. Mapping relationship between the value of at least one MSB in the first MCS field and the number of repetition transmissions N of the first PUCCH

[0203]

[0204] As shown in Table 5, in the mapping table of the value of at least one MSB in the first MCS domain to the number of repetition transmissions N of the first PUCCH, 000 and 100 indicate the same number of PUCCH repetition transmissions. In other words, since the two LSBs of 000 and 100 are the same, 000 and 100 indicate the same number of PUCCH repetition transmissions. Similarly, 001 and 101 indicate the same number of PUCCH repetition transmissions, 010 and 110 indicate the same number of PUCCH repetition transmissions, and 011 and 111 indicate the same number of PUCCH repetition transmissions.

[0205] Exemplarily, the number of repetitions of the first PUCCH can be indicated from the number candidate value set by X MSBs (most significant X bits) of at least one MSB in the first MCS domain, where X can be 1 / 2 / 3. For example, when the number candidate value set includes 4 number candidate values ​​and at least one MSB in the first MCS domain is a 3-bit indication domain, at this time, the number of repetitions of the first PUCCH can be indicated from the number candidate value set by 2 MSBs (most significant 2 bits) of at least one MSB in the first MCS domain.

[0206] The following is an exemplary description of the mapping relationship between the value of at least one MSB in the first MCS domain and the number of repeated transmissions N of the first PUCCH in conjunction with Table 6.

[0207] Table 6. Mapping relationship between the value of at least one MSB in the first MCS field and the number of repetition transmissions N of the first PUCCH

[0208]

[0209] As shown in Table 6, in the mapping table of the value of at least one MSB in the first MCS domain to the number of repetition transmissions N of the first PUCCH, 000 and 001 indicate the same number of PUCCH repetition transmissions. In other words, since the two MSBs of 000 and 001 are the same, 000 and 001 indicate the same number of PUCCH repetition transmissions. Similarly, 010 and 011 indicate the same number of PUCCH repetition transmissions, 100 and 101 indicate the same number of PUCCH repetition transmissions, and 110 and 111 indicate the same number of PUCCH repetition transmissions.

[0210] In some embodiments, the first indication information is carried in a first PUCCH resource indication field, and the maximum number of values ​​that the first PUCCH resource indication field can take is equal to the number of candidate values ​​in the candidate value set.

[0211] The following is an exemplary description of the mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH in conjunction with Table 7.

[0212] Table 7. Mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH

[0213]

[0214] As shown in Table 7, if the value of the first PUCCH resource indication field is 00, if the network device configures numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the first value of numberOfPUCCHRepetitions; if the network device does not configure numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the first default candidate value in the default candidate value set, that is, the number of repeated transmissions N of the first PUCCH is 1. If the value of the first PUCCH resource indication field is 01, if the network device configures numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the second value of numberOfPUCCHRepetitions; if the network device does not configure numberOfPUCCHRepetitions for the terminal device, the number of repeated transmissions N of the first PUCCH is the second default candidate value in the default candidate value set, that is, the number of repeated transmissions N of the first PUCCH is 2. Similarly, when the value of the first PUCCH resource indication field is 10 or 11, the corresponding number of repeated transmissions N of the first PUCCH can also be determined.

[0215] In some embodiments, if the first indication information is carried in the first PUCCH resource indication field, and the maximum number of values ​​of the first indication information is greater than the number of candidate values ​​in the candidate value set, then the multiple values ​​of the first PUCCH resource indication field correspond to one candidate value in the candidate value set; or the first indication information is carried in at least one highest bit MSB in the first PUCCH resource indication field; or the first indication information is carried in at least one lowest bit LSB in the first PUCCH resource indication field.

[0216] In this embodiment, if the number of candidate values ​​in the candidate value set is less than the number of values ​​that the first PUCCH resource indication field can indicate, the introduction of specific rules can ensure that each value of the first PUCCH resource indication field can be mapped to the specified candidate value, thereby ensuring the validity of the first indication information.

[0217] Exemplarily, in the mapping table from the value of the first PUCCH resource indication field to the number of repeated transmissions N of the first PUCCH, the number of candidate values ​​in the number of candidate values ​​set can be copied. For example, the number of candidate values ​​set includes 4 number of candidate values, and when the first PUCCH resource indication field is a 3-bit indication field, the first PUCCH resource indication field can indicate 8 number of candidate values. At this time, in the mapping table from the value of the first PUCCH resource indication field to the number of repeated transmissions N of the first PUCCH, the 4 number of candidate values ​​in the number of candidate values ​​set can be copied once, so that every 2 values ​​of the first PUCCH resource indication field correspond to 1 number of candidate values ​​in the number of candidate values ​​set.

[0218] Exemplarily, the number of repeated transmissions of the first PUCCH may be indicated from the number candidate value set by X LSBs (the least significant X bits) of the first PUCCH resource indication field, where X may be 1 / 2 / 3. For example, when the number candidate value set includes 4 number candidate values ​​and the first PUCCH resource indication field is a 3-bit indication field, at this time, the number of repeated transmissions of the first PUCCH may be indicated from the number candidate value set by 2 LSBs (the least significant 2 bits) of the first PUCCH resource indication field.

[0219] The following is an exemplary description of the mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH in conjunction with Table 8.

[0220] Table 8. Mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH

[0221]

[0222] As shown in Table 8, in the mapping table of the value of the first PUCCH resource indication field to the number of repeated transmissions N of the first PUCCH, 000 and 100 indicate the same number of repeated transmissions of the PUCCH. In other words, since the 2 LSBs of 000 and 100 are the same, 000 and 100 indicate the same number of repeated transmissions of the PUCCH. Similarly, 001 and 101 indicate the same number of repeated transmissions of the PUCCH, 010 and 110 indicate the same number of repeated transmissions of the PUCCH, and 011 and 111 indicate the same number of repeated transmissions of the PUCCH.

[0223] Exemplarily, the number of repeated transmissions of the first PUCCH may be indicated from the number candidate value set by X MSBs (most significant X bits) of the first PUCCH resource indication field, where X may be 1 / 2 / 3. For example, when the number candidate value set includes 4 number candidate values ​​and the first PUCCH resource indication field is a 3-bit indication field, the number of repeated transmissions of the first PUCCH may be indicated from the number candidate value set by 2 MSBs (most significant 2 bits) of the first PUCCH resource indication field.

[0224] The following is an exemplary description of the mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH in conjunction with Table 9.

[0225] Table 9. Mapping relationship between the value of the first PUCCH resource indication field and the number of repeated transmissions N of the first PUCCH

[0226]

[0227] As shown in Table 9, in the mapping table of the value of the first PUCCH resource indication field to the number of repeated transmissions N of the first PUCCH, 000 and 001 indicate the same number of repeated transmissions of the PUCCH. In other words, since the 2 MSBs of 000 and 001 are the same, 000 and 001 indicate the same number of repeated transmissions of the PUCCH. Similarly, 010 and 011 indicate the same number of repeated transmissions of the PUCCH, 100 and 101 indicate the same number of repeated transmissions of the PUCCH, and 110 and 111 indicate the same number of repeated transmissions of the PUCCH.

[0228] Exemplarily, the terminal device may simultaneously request repeated transmission of the Msg3 PUSCH and repeated transmission of the first PUCCH.

[0229] Exemplarily, the network device may simultaneously indicate the number of repeated transmissions K of the Msg3 PUSCH and the number of repeated transmissions N of the first PUCCH through the first indication information. For example, the terminal device may determine the number of repeated transmissions K of the Msg3 PUSCH through Table 1 mentioned above. For another example, the terminal device may determine the number of repeated transmissions N of the first PUCCH through any one of Tables 4 to 9 mentioned above.

[0230] In some embodiments, the S210 may include:

[0231] Repeating sending the first PUCCH to the network device over N time units;

[0232] Wherein, N represents the number of repeated transmissions of the first PUCCH.

[0233] In some embodiments, the method 200 may further include:

[0234] The terminal device sends a first request to the network device, where the first request is used to request repeated sending of the first PUCCH.

[0235] Exemplarily, when the measurement result of the downlink reference signal of the terminal device is less than or equal to the first threshold value, the first request is sent to the network device.

[0236] In some embodiments, the first request requests repetitive transmission of the first PUCCH via a physical random access channel (PRACH) resource used by message 1 in a random access procedure.

[0237] Exemplarily, for the second request, when sending Msg1, the terminal device implicitly requests the base station to repeat sending the first PUCCH by selecting a specific PRACH resource, that is, a specific PRACH preamble set U2.

[0238] Exemplarily, when the first indication information is carried in the first MCS domain mentioned above, the first request requests repeated sending of the first PUCCH through the PRACH resources used by message 1 in the random access process.

[0239] Exemplarily, for the first request, the threshold value T of the first request may be PUCCH1 , if the reference signal receiving power (RSRP) measurement result of the downlink reference signal of the terminal device is lower than T PUCCH1 , when sending Msg1, the terminal device implicitly requests the base station to repeat sending the first PUCCH by selecting a specific PRACH resource, such as a specific PRACH preamble set U2.

[0240] In this embodiment, without introducing additional initial access overhead, it is possible to ensure that the network device and the terminal device have the same understanding of the uplink transmission mode, thereby improving system performance.

[0241] Exemplarily, the PRACH resource used to request repeated transmission of the first PUCCH and the PRACH resource used to request repeated transmission of the Msg3 PUSCH are the same as or different from each other.

[0242] Exemplarily, the PRACH resource used to request repeated transmission of Msg3 PUSCH and the PRACH resource used to request repeated transmission of PUCCH may be the same or different.

[0243] Exemplarily, the PRACH resources used to request repeated transmission of Msg3 PUSCH are recorded as PRACH preamble set U1, and the PRACH resources used to request repeated transmission of PUCCH are recorded as PRACH preamble set U2; that is, U1 and U2 may be the same or different; if U1 and U2 are the same, the PRACH resources in the preamble set are used to simultaneously request repeated transmission of Msg3 PUSCH and repeated transmission of PUCCH. Of course, in other alternative embodiments, U1 may also be a PRACH resource used to request repeated transmission of Msg3 PUSCH, and U2 may also be a PRACH resource used to simultaneously request repeated transmission of Msg3 PUSCH and repeated transmission of PUCCH. This application does not make specific limitations on this.

[0244] In some embodiments, the terminal device sends Msg3 to the network device, and the Msg3 includes the first request.

[0245] Exemplarily, when the first indication information is carried in the transmission resource of the first PUCCH mentioned above, the first request is carried in the Msg3.

[0246] In this embodiment, since the network device indicates the number of repeated transmissions of the first PUCCH to the UE after receiving Msg3, the UE may also request repeated transmission of the PUCCH in Msg3.

[0247] In some embodiments, the method 200 may further include:

[0248] The terminal device maintains the power consistency of the first PUCCH and the phase continuity of the first PUCCH within each first nominal TDW of at least one first nominal TDW.

[0249] In this embodiment, the terminal device maintains the power consistency of the first PUCCH and the phase continuity of the first PUCCH in each of at least one first nominal TDW, which is beneficial for the network device to perform joint channel estimation on the first PUCCH and can further improve the uplink coverage performance.

[0250] In some embodiments, the method 200 may further include:

[0251] The terminal device determines the length of each first nominal TDW based on the number of repeated transmissions of the first PUCCH and the length of the time window indicated by the network device for performing joint channel estimation on the first PUCCH.

[0252] Exemplarily, the network device may provide the terminal device with a time window length for performing joint channel estimation on the first PUCCH in a system message (e.g., in SIB1 of the system message). For example, the time window length for performing joint channel estimation on the first PUCCH may be recorded as PUCCH-TimeDomainWindowLength. For example, PUCCH-TimeDomainWindowLength=4. Of course, in other alternative embodiments, PUCCH-TimeDomainWindowLength may also be other values, which is not limited in this application.

[0253] In some embodiments, the minimum value of the number of repeated transmissions of the first PUCCH and the length of the time window indicated by the network device for performing joint channel estimation on the first PUCCH is determined as the length of each first nominal TDW.

[0254] Exemplarily, if the network device configures PUCCH-TimeDomainWindowLength for the terminal device, the terminal device may calculate the length of each first nominal TDW according to min(PUCCH-TimeDomainWindowLength, N), that is, the minimum value of the two is used as the length of each first nominal TDW. Wherein, N is the number of repeated transmissions of the first PUCCH; if the network device does not configure PUCCH-TimeDomainWindowLength for the terminal device, the terminal device may directly determine N as the length of each first nominal TDW.

[0255] In some embodiments, the method 200 may further include:

[0256] The terminal device determines the time domain position of each first nominal TDW based on the time unit in which the first PUCCH is first transmitted and the time unit in which the first PUCCH is last transmitted.

[0257] Exemplarily, the time unit includes but is not limited to a time domain unit of fixed length such as a time slot, a subframe, a half frame, a symbol, etc.

[0258] Taking the time unit as a time slot as an example, the terminal device may determine the time domain position of each first nominal TDW based on the time slot in which the first PUCCH is first transmitted and the time slot in which the first PUCCH is last transmitted.

[0259] In some embodiments, the terminal device may determine the starting point of the first time unit in which the first transmission of the first PUCCH is located as the starting point of the first first nominal TDW in the at least one first nominal TDW; the terminal device may determine the end point of the last time unit in which the last transmission of the first PUCCH is located as the end point of the last first nominal TDW in the at least one first nominal TDW; the terminal device may determine the starting point of the first time unit for sending the first PUCCH after the last time unit in the current first nominal TDW in the at least one first nominal TDW as the starting point of the first nominal TDW after the current first nominal TDW.

[0260] Taking the time unit as a time slot as an example, the terminal device may determine the starting point of the first time slot where the first transmission of the first PUCCH is located as the starting point of the first first nominal TDW in the at least one first nominal TDW; the terminal device may determine the end point of the last time slot where the last transmission of the first PUCCH is located as the end point of the last first nominal TDW in the at least one first nominal TDW; the terminal device may determine the starting point of the first time slot used to send the first PUCCH after the last time slot in the current first nominal TDW in the at least one first nominal TDW as the starting point of the first nominal TDW after the current first nominal TDW.

[0261] In other words, the first time slot of the first PUCCH transmission of the first PUCCH serves as the starting point of the first first nominal TDW; the last time slot of the last PUCCH transmission of the first PUCCH serves as the end point of the at least one first nominal TDW; and the first time slot used for PUCCH transmission after the last time slot of the previous first nominal TDW in the at least one first nominal TDW serves as the starting point of the next first nominal TDW of the previous first nominal.

[0262] Exemplarily, the current first nominal TDW is any first nominal TDW except the last first nominal TDW among the at least one first nominal TDW.

[0263] Figure 8 is a schematic diagram of at least one first nominal TDW provided in an embodiment of the present application.

[0264] like Figure 8 As shown, assuming that the number of repeated transmissions of the first PUCCH is N=8, and PUCCH-TimeDomainWindowLength=4, at this time, the terminal device can determine that the length of each first nominal TDW is 4 based on the minimum value of the two, and determine 2 first nominal TDWs based on the first time unit used to transmit the first PUCCH.

[0265] In some embodiments, if the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, then when the length of each first nominal TDW is less than or equal to the length of the frequency hopping interval, the terminal device can maintain the power consistency of the first PUCCH and maintain the phase continuity of the first PUCCH based on each first nominal TDW.

[0266] In some embodiments, the method 200 may further include:

[0267] If the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, then when the length of each first nominal TDW is greater than or equal to the length of the frequency hopping interval, the terminal device can maintain the power consistency of the first PUCCH and the phase continuity of the first PUCCH based on the frequency hopping interval.

[0268] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0269] In this embodiment, on the basis of repeated transmission of the first PUCCH, frequency hopping between time units is introduced, and the first PUCCH is repeatedly sent to the network device based on at least one first nominal TDW, and when the length of each first nominal TDW is greater than or equal to the length of the frequency hopping interval, the terminal device can maintain the power consistency of the first PUCCH and the phase continuity of the first PUCCH based on the frequency hopping interval, thereby ensuring that the network device performs joint channel estimation on the first PUCCH, thereby further improving the uplink coverage performance.

[0270] Exemplarily, if the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, the terminal device starts from the first time unit for sending the PUCCH repetition transmission (i.e., the original transmission of the first PUCCH and the repetition transmission of the first PUCCH), and every N FH Frequency hopping is performed in consecutive time units.

[0271] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the first PUCCH.

[0272] For example, a new system parameter PUCCH-Freqhopping-Interval may be introduced in SIB1, which may be used to configure N FH Optional, if the network device is not configured with N for the terminal device FH , then N FH Equal to PUCCH-TimeDomainWindowLength. FH Indicates the frequency hopping interval.

[0273] In some embodiments, the method 200 may further include:

[0274] The terminal device receives second indication information sent by the network device, where the second indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0275] Exemplarily, the second indication information can be carried by the frequency hopping indication information field in the DCI 0_0 of the RAR uplink authorization or the TC-RNTI scrambled CRC. In other words, the terminal device can be instructed to perform frequency hopping between time units by the frequency hopping indication information field in the DCI 0_0 of the RAR uplink authorization or the TC-RNTI scrambled CRC.

[0276] In some embodiments, the S210 may include:

[0277] Numbering the frequency hopping intervals based on a time unit in which the first PUCCH is first transmitted as a starting point;

[0278] For the frequency hopping interval numbered as an even number, sending the first PUCCH at a first frequency domain position;

[0279] For the odd-numbered frequency hopping intervals, the first PUCCH is sent at a second frequency domain position.

[0280] Exemplarily, the first PUCCH is sent over multiple frequency hopping intervals, up to N time units, where N is the number of PUCCH repetition transmissions indicated by the first indication information. The first frequency hopping interval is numbered 0, regardless of whether the terminal device sends the first PUCCH in the time unit, and then the number of each frequency hopping interval is incremented in the time domain. Based on this, the terminal device can send the first PUCCH starting from the starting PRB corresponding to the first hop in the even-numbered frequency hopping intervals, and send the first PUCCH starting from the starting PRB corresponding to the second hop in the odd-numbered frequency hopping intervals. It should be understood that the present application does not limit the method for determining the starting PRB indexes of the first hop and the second hop. For example, the starting PRB indexes of the first hop and the second hop can be determined according to the frequency domain resource allocation method of the common PUCCH.

[0281] Fig. 9 and Fig.10 It is a schematic diagram of the relationship between at least one first nominal TDW and a frequency hopping interval provided in an embodiment of the present application.

[0282] like Fig. 9 As shown, assuming that the number of repeated transmissions of the first PUCCH is N=8, and PUCCH-TimeDomainWindowLength=4, at this time, the terminal device can determine that the length of each first nominal TDW is 4 based on the minimum value of the two, and determine 2 first nominal TDWs based on the first time unit used to transmit the first PUCCH. Further, assuming that the frequency hopping interval is 4, that is, the terminal device performs 1 frequency hopping every 4 consecutive time units starting from the first time unit used to send PUCCH repeated transmissions (that is, the original transmission of the first PUCCH and the repeated transmission of the first PUCCH). At this time, since the length of each first nominal TDW (that is, 4 time units) is equal to the length of the frequency hopping interval (that is, 4 time units), the terminal device can maintain the power consistency of the first PUCCH and the phase continuity of the first PUCCH based on the length of each first nominal TDW (that is, 4 time units).

[0283] like Fig.10As shown, assuming that the number of repeated transmissions of the first PUCCH is N=8, and PUCCH-TimeDomainWindowLength=4, at this time, the terminal device can determine that the length of each first nominal TDW is 4 based on the minimum value of the two, and determine 2 first nominal TDWs based on the first time unit used to transmit the first PUCCH. Further, assuming that the frequency hopping interval is 2, that is, the terminal device performs frequency hopping every 2 consecutive time units starting from the first time unit used to send PUCCH repeated transmissions (that is, the original transmission of the first PUCCH and the repeated transmission of the first PUCCH). At this time, since the length of each first nominal TDW (that is, 4 time units) is greater than the length of the frequency hopping interval (that is, 2 time units), the terminal device can maintain the power consistency of the first PUCCH and the phase continuity of the first PUCCH based on the length of the frequency hopping interval (that is, 2 time units).

[0284] In some embodiments, the method 200 may further include:

[0285] The terminal device sends a second request to the network device, where the second request is used to request joint channel estimation for the first PUCCH.

[0286] Exemplarily, when the measurement result of the downlink reference signal of the terminal device is less than or equal to the second threshold value, the terminal device sends the second request to the network device.

[0287] Exemplarily, when the terminal device sends the first request mentioned above, the terminal device sends the second request to the network device.

[0288] In some embodiments, the second request requests joint channel estimation for the first PUCCH via a PRACH resource used by message 1 in a random access procedure.

[0289] Exemplarily, for the second request, when sending Msg1, the terminal device implicitly requests the network device to perform joint channel estimation on the first PUCCH by selecting a specific PRACH resource, that is, a specific PRACH preamble set U4.

[0290] Exemplarily, when the first indication information is carried in the first MCS domain mentioned above, the second request requests joint channel estimation of the first PUCCH through the PRACH resources used by message 1 in the random access process.

[0291] Exemplarily, for the second request, the threshold value T of the second request may be PUSCH, if the reference signal receiving power (RSRP) measurement result of the downlink reference signal of the terminal device is lower than T PUSCH , when sending Msg1, the terminal device implicitly requests the network device to perform joint channel estimation on the first PUCCH by selecting a specific PRACH resource, such as a specific PRACH preamble set U4.

[0292] In this embodiment, without introducing additional initial access overhead, it is possible to ensure that the network device and the terminal device have the same understanding of the uplink transmission mode, thereby improving system performance.

[0293] In some embodiments, the PRACH resource used to request repeated transmission of the first PUCCH and the PRACH resource used to request joint channel estimation for the first PUCCH are the same or different.

[0294] Exemplarily, the PRACH resources used to request PUCCH joint channel estimation are recorded as PRACH preamble set U4, and the PRACH resources used to request PUCCH repeated transmission are recorded as PRACH preamble set U2; that is, U4 and U2 may be the same or different; if U4 and U2 are the same, the PRACH resources in the preamble set are used to simultaneously request PUCCH joint channel estimation and PUCCH repeated transmission. Of course, in other alternative embodiments, U4 may also be a PRACH resource used to request PUCCH joint channel estimation, and U2 may also be a PRACH resource used to simultaneously request PUCCH joint channel estimation and PUCCH repeated transmission. This application does not make specific limitations on this.

[0295] Fig.11 is a schematic flow chart of a wireless communication method 300 provided in an embodiment of the present application, and the wireless communication method 300 may be executed by a terminal device. For example, the wireless communication method 300 may be executed by Figure 1 The terminal device shown is executed.

[0296] like Fig.11 As shown, the method 300 may include:

[0297] S310, within each second TDW of at least one second nominal time window TDW, the terminal device maintains the power consistency of the message 3 physical uplink shared channel Msg3 PUSCH and maintains the phase continuity of the Msg3 PUSCH.

[0298] In this embodiment, within each second TDW of at least one second nominal TDW, the terminal device maintains the power consistency of the Msg3 PUSCH and the phase continuity of the Msg3 PUSCH, which is beneficial for the network device to perform joint channel estimation on the Msg3PUSCH and can further improve the uplink coverage performance.

[0299] In some embodiments, the method 300 may further include:

[0300] The terminal device determines the length of each second nominal TDW based on the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0301] Exemplarily, the network device may provide the terminal device with a time window length for performing joint channel estimation on the Msg3PUSCH in a system message (e.g., in SIB1 of the system message). For example, the time window length for performing joint channel estimation on the Msg3PUSCH may be recorded as Msg3-TimeDomainWindowLength. For example, Msg3-TimeDomainWindowLength=4. Of course, in other alternative embodiments, Msg3-TimeDomainWindowLength may also be other values, which is not limited in this application.

[0302] In some embodiments, the minimum value of the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH is determined as the length of each second nominal TDW.

[0303] Exemplarily, if the network device configures Msg3-TimeDomainWindowLength for the terminal device, the terminal device can calculate the length of each second nominal TDW according to min(Msg3-TimeDomainWindowLength, K), that is, the minimum value of the two is used as the length of each second nominal TDW. K is the number of repeated transmissions of the Msg3 PUSCH; if the network device does not configure Msg3-TimeDomainWindowLength for the terminal device, the terminal device can directly determine N as the length of each second nominal TDW.

[0304] In some embodiments, the method 300 may further include:

[0305] The terminal device determines the time domain position of each second nominal TDW based on the time unit in which the first transmission of the Msg3 PUSCH is located and the time unit in which the last transmission of the Msg3 PUSCH is located.

[0306] Exemplarily, the time unit includes but is not limited to a time domain unit of fixed length such as a time slot, a subframe, a half frame, a symbol, etc.

[0307] Taking the time unit as a time slot as an example, the terminal device may determine the time domain position of each second nominal TDW based on the time slot in which the first transmission of the Msg3 PUSCH is located and the time slot in which the last transmission of the Msg3PUSCH is located.

[0308] In some embodiments, the terminal device may determine the starting point of the first time unit in which the Msg3 PUSCH is first transmitted as the starting point of the first second nominal TDW in the at least one second nominal TDW; the terminal device may determine the end point of the last time unit in which the Msg3 PUSCH is last transmitted as the end point of the last second nominal TDW in the at least one second nominal TDW; the terminal device may determine the starting point of the first time unit for sending the Msg3PUSCH after the last time unit in the current second nominal TDW in the at least one second nominal TDW as the starting point of the second nominal TDW after the current second nominal TDW.

[0309] Taking the time unit as a time slot as an example, the terminal device may determine the starting point of the first time slot where the first transmission of the Msg3 PUSCH is located as the starting point of the first second nominal TDW in the at least one second nominal TDW; the terminal device may determine the end point of the last time slot where the last transmission of the Msg3 PUSCH is located as the end point of the last second nominal TDW in the at least one second nominal TDW; the terminal device may determine the starting point of the first time slot used to send the Msg3PUSCH after the last time slot in the current second nominal TDW in the at least one second nominal TDW as the starting point of the second nominal TDW after the current second nominal TDW.

[0310] In other words, the first time slot of the first transmission of the Msg3 PUSCH serves as the starting point of the first second nominal TDW; the last time slot of the last transmission of the Msg3PUSCH serves as the end point of the at least one second nominal TDW; the first time slot for transmitting the Msg3PUSCH after the last time slot of the previous second nominal TDW of the Msg3 PUSCH serves as the starting point of the next second nominal TDW of the previous second nominal TDW.

[0311] Exemplarily, the current second nominal TDW is any second nominal TDW except the last second nominal TDW among the at least one second nominal TDW.

[0312] Fig.12 is a schematic diagram of at least one second nominal TDW provided in an embodiment of the present application.

[0313] like Fig.12 As shown, assuming that the number of repeated transmissions of the Msg3 PUSCH is K=16, and Msg3-TimeDomainWindowLength=4, at this time, the terminal device can determine that the length of each second nominal TDW is 4 based on the minimum value of the two, and determine the 4 second nominal TDWs based on the first time unit used to transmit the first PUCCH.

[0314] In some embodiments, if the terminal device performs frequency hopping between time units and repeatedly sends the Msg3 PUSCH to the network device based on at least one second nominal TDW, then when the length of each second nominal TDW is less than or equal to the length of the frequency hopping interval, the terminal device may maintain the power consistency of the Msg3PUSCH and the phase continuity of the Msg3 PUSCH based on each second nominal TDW.

[0315] In some embodiments, the method 300 may further include:

[0316] If the terminal device performs frequency hopping between time units and repeatedly sends the Msg3PUSCH to the network device based on at least one second nominal TDW, then when the length of each second nominal TDW is greater than or equal to the length of the frequency hopping interval, the terminal device can maintain the power consistency of the Msg3 PUSCH and the phase continuity of the Msg3 PUSCH based on the frequency hopping interval.

[0317] In this embodiment, on the basis of repeated transmission of the Msg3 PUSCH, frequency hopping between time units is introduced, and when the length of each second nominal TDW is greater than or equal to the length of the frequency hopping interval, the terminal device can maintain the power consistency of the Msg3 PUSCH and the phase continuity of the Msg3 PUSCH based on the frequency hopping interval, thereby ensuring that the network device performs joint channel estimation on the Msg3 PUSCH, thereby further improving the uplink coverage performance.

[0318] Exemplarily, if the terminal device performs frequency hopping between time units, the terminal device starts from the first time unit used to send the repeated transmission of the Msg3 PUSCH (i.e., the original transmission of the Msg3 PUSCH and the repeated transmission of the Msg3 PUSCH), and every N FH Frequency hopping is performed in consecutive time units.

[0319] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0320] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0321] For example, a new system parameter Msg3-Freqhopping-Interval may be introduced in SIB1, which may be used to configure N FH Optional, if the network device is not configured with N for the terminal device FH , then N FH Equal to Msg3-TimeDomainWindowLength. FH Indicates the frequency hopping interval.

[0322] In some embodiments, the method 300 may further include:

[0323] The terminal device receives third indication information sent by the network device, where the third indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0324] Exemplarily, the third indication information can be carried by the frequency hopping indication information field in the DCI 0_0 of the RAR uplink authorization or the TC-RNTI scrambled CRC. In other words, the frequency hopping indication information field in the DCI 0_0 of the RAR uplink authorization or the TC-RNTI scrambled CRC can be used to instruct the terminal device to perform frequency hopping between time units.

[0325] In some embodiments, the method 300 may further include:

[0326] The frequency hopping intervals are numbered starting from the time unit where the first transmission of the Msg3 PUSCH is located;

[0327] For the frequency hopping interval numbered as an even number, sending the Msg3 PUSCH at a first frequency domain position;

[0328] For the odd-numbered frequency hopping interval, the Msg3 PUSCH is sent at the second frequency domain position.

[0329] Exemplarily, the Msg3 PUSCH is sent over multiple frequency hopping intervals, up to K time units, where the first frequency hopping interval is numbered 0, regardless of whether the terminal device sends the Msg3 PUSCH in the time unit, and then the number of each frequency hopping interval is incremented in the time domain. Based on this, the terminal device can send the Msg3PUSCH from the starting PRB corresponding to the first hop in the even-numbered frequency hopping interval, and send the Msg3 PUSCH from the starting PRB corresponding to the second hop in the odd-numbered frequency hopping interval. It should be understood that the present application does not limit the method for determining the starting PRB indexes of the first hop and the second hop. For example, the starting PRB indexes of the first hop and the second hop can be determined according to the frequency domain resource allocation method of the Msg3 PUSCH.

[0330] Fig.13 and Fig.14 It is a schematic diagram of the relationship between at least one second nominal TDW and the frequency hopping interval provided in an embodiment of the present application.

[0331] like Fig.13 As shown, assuming that the number of repeated transmissions of the Msg3 PUSCH is N=16, and Msg3-TimeDomainWindowLength=4, at this time, the terminal device can determine that the length of each second nominal TDW is 4 based on the minimum value of the two, and determine 4 second nominal TDWs based on the first time unit used to transmit the Msg3PUSCH. Further, assuming that the frequency hopping interval is 4, that is, the terminal device performs 1 frequency hopping every 4 consecutive time units starting from the first time unit used to send the repeated transmission of the Msg3 PUSCH (that is, the original transmission of the Msg3 PUSCH and the repeated transmission of the Msg3 PUSCH). At this time, since the length of each second nominal TDW (that is, 4 time units) is equal to the length of the frequency hopping interval (that is, 4 time units), the terminal device can maintain the power consistency of the Msg3 PUSCH and the phase continuity of the Msg3 PUSCH based on the length of each second nominal TDW (that is, 4 time units).

[0332] like Fig.14 As shown, assuming that the number of repeated transmissions of the Msg3 PUSCH is N=16, and PUCCH-TimeDomainWindowLength=8, at this time, the terminal device can determine that the length of each second nominal TDW is 8 based on the minimum value of the two, and determine 2 second nominal TDWs based on the first time unit used to transmit the Msg3PUSCH. Further, assuming that the frequency hopping interval is 4, that is, the terminal device performs frequency hopping every 4 consecutive time units starting from the first time unit used to send PUCCH repeated transmissions (that is, the original transmission of the Msg3 PUSCH and the repeated transmission of the Msg3 PUSCH). At this time, since the length of each second nominal TDW (that is, 8 time units) is greater than the length of the frequency hopping interval (that is, 4 time units), the terminal device can maintain the power consistency of the Msg3 PUSCH and the phase continuity of the Msg3 PUSCH based on the length of the frequency hopping interval (that is, 4 time units).

[0333] In some embodiments, the method 300 may further include:

[0334] The terminal device sends a third request to the network device, where the third request is used to request joint channel estimation for the Msg3PUSCH.

[0335] Exemplarily, when the measurement result of the downlink reference signal of the terminal device is less than or equal to a third threshold value, the terminal device sends the third request to the network device.

[0336] Exemplarily, when the terminal device sends a message requesting repeated transmission of the Msg3 PUSCH, the terminal device sends the third request to the network device.

[0337] In some embodiments, the third request requests joint channel estimation for the Msg3 PUSCH via a PRACH resource used by message 1 in a random access procedure.

[0338] Exemplarily, for the third request, when sending Msg1, the terminal device implicitly requests the network device to perform joint channel estimation on the Msg3 PUSCH by selecting a specific PRACH resource, that is, a specific PRACH preamble set U3.

[0339] Exemplarily, when the information indicating the number of repeated transmissions of the Msg3 PUSCH is carried in the first MCS domain mentioned above, the second request requests joint channel estimation of the Msg3 PUSCH through the PRACH resources used by message 1 in the random access process.

[0340] Exemplarily, for the second request, the threshold value T of the second request may be PUSCH , if the reference signal receiving power (RSRP) measurement result of the downlink reference signal of the terminal device is lower than T PUSCH , when sending Msg1, the terminal device implicitly requests the network device to perform joint channel estimation on the Msg3PUSCH by selecting a specific PRACH resource, such as a specific PRACH preamble set U3.

[0341] In this embodiment, without introducing additional initial access overhead, it is possible to ensure that the network device and the terminal device have the same understanding of the uplink transmission mode, thereby improving system performance.

[0342] In some embodiments, the PRACH resource used to request repeated transmission of the Msg3 PUSCH and the PRACH resource used to request joint channel estimation for the Msg3 PUSCH are the same as or different from.

[0343] Exemplarily, the PRACH resources used to request Msg3 PUSCH joint channel estimation are recorded as PRACH preamble set U3, and the PRACH resources used to request Msg3 PUSCH repeated transmission are recorded as PRACH preamble set U1; that is, U3 and U1 may be the same or different; if U3 and U1 are the same, the PRACH resources in the preamble set are used to simultaneously request Msg3 PUSCH joint channel estimation and Msg3 PUSCH repeated transmission. Of course, in other alternative embodiments, U3 may also be a PRACH resource for requesting Msg3 PUSCH joint channel estimation, and U1 may also be a PRACH resource for simultaneously requesting Msg3 PUSCH joint channel estimation and Msg3 PUSCH repeated transmission. This application does not make specific limitations on this.

[0344] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0345] It should also be understood that in various method embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In addition, in the embodiment of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of the signal or data, wherein "downlink" is used to indicate that the transmission direction of the signal or data is a first direction sent from the site to the user equipment of the cell, and "uplink" is used to indicate that the transmission direction of the signal or data is a second direction sent from the user equipment of the cell to the site, for example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. Specifically, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0346] The wireless communication method provided in accordance with the embodiment of the present application is described in detail above from the perspective of the terminal device. Figure 15 to Figure 16 , describes the wireless communication method provided according to an embodiment of the present application from the perspective of a network device.

[0347] Fig.15 400 is a schematic flow chart of a wireless communication method 400 provided in an embodiment of the present application. The method 400 may be performed as follows: Figure 1 The network devices shown are executed.

[0348] like Fig.15 As shown, the method 400 may include:

[0349] S40, in the initial access phase, repeatedly receiving the first physical uplink control channel PUCCH sent by the terminal device.

[0350] In some embodiments, the method 400 may further include:

[0351] Sending first indication information to the terminal device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

[0352] In some embodiments, the first indication information is also used to indicate the number of repeated transmissions of Msg3 PUSCH.

[0353] In some embodiments, the first indication information is carried in a first modulation and coding strategy MCS field.

[0354] In some embodiments, the first MCS domain is the MCS domain in a random access response RAR uplink grant, or the first MCS domain is the MCS domain in downlink control information DCI 0_0.

[0355] In some embodiments, the first indication information is carried in at least one most significant bit MSB in the first MCS field.

[0356] In some embodiments, at least one least significant bit (LSB) in the first MCS field carries information for indicating an MCS index.

[0357] In some embodiments, the at least one LSB is used to indicate the MCS index in an index candidate value set configured by a system parameter, or the at least one LSB is used to indicate the MCS index in a default index candidate value set.

[0358] In some embodiments, the first indication information is carried in a first PUCCH resource indication field.

[0359] In some embodiments, the first PUCCH resource indication field includes a resource indication field in downlink control information DCI 1_0 of a temporary cell radio network temporary identity TC-RNTI scrambled cyclic redundancy check CRC.

[0360] In some embodiments, the first PUCCH resource indication field is also used to indicate the transmission resources of Msg4.

[0361] In some embodiments, the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a default set of candidate values.

[0362] In some embodiments, the maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the candidate value set.

[0363] In some embodiments, if the first indication information is carried in the first PUCCH resource indication field, and the maximum number of values ​​of the first indication information is greater than the number of candidate values ​​in the candidate value set, then the multiple values ​​of the first PUCCH resource indication field correspond to one candidate value in the candidate value set; or the first indication information is carried in at least one highest bit MSB in the first PUCCH resource indication field; or the first indication information is carried in at least one lowest bit LSB in the first PUCCH resource indication field.

[0364] In some embodiments, if the first indication information is carried in at least one highest bit MSB in the first MCS domain, and the maximum number of values ​​of the at least one MSB is greater than the number of candidate values ​​in the number candidate value set, then the multiple values ​​of the at least one MSB correspond to a candidate value in the number candidate set; or the first indication information is carried in one or more MSBs in the at least one MSB; or the first indication information is carried in one or more LSBs in the at least one MSB.

[0365] In some embodiments, S410 may include:

[0366] Repeating receiving the first PUCCH sent by the terminal device over N time units;

[0367] Wherein, N represents the number of repeated transmissions of the first PUCCH.

[0368] In some embodiments, the method 400 may further include:

[0369] A demodulation reference signal DMRS in each first nominal TDW of at least one first nominal TDW is used to perform joint channel estimation on the first PUCCH.

[0370] In some embodiments, the method 400 may further include:

[0371] The length of each first nominal TDW is determined based on the number of repeated transmissions of the first PUCCH and the length of a time window indicated by the network device for performing joint channel estimation on the first PUCCH.

[0372] In some embodiments, the minimum value of the number of repeated transmissions of the first PUCCH and the length of the time window indicated by the network device for performing joint channel estimation on the first PUCCH is determined as the length of each first nominal TDW.

[0373] In some embodiments, the method 400 may further include:

[0374] The time domain position of each of the first nominal TDWs is determined based on a time unit in which the first PUCCH is first transmitted and a time unit in which the first PUCCH is last transmitted.

[0375] In some embodiments, the starting point of the first time unit in which the first transmission of the first PUCCH is located is determined as the starting point of the first first nominal TDW in the at least one first nominal TDW; the end point of the last time unit in which the last transmission of the first PUCCH is located is determined as the end point of the last first nominal TDW in the at least one first nominal TDW; the starting point of the first time unit for sending the first PUCCH after the last time unit in the current first nominal TDW in the at least one first nominal TDW is determined as the starting point of the first nominal TDW after the current first nominal TDW.

[0376] In some embodiments, the method 400 may further include:

[0377] If the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, then when the length of each first nominal TDW is greater than or equal to the length of the frequency hopping interval, joint channel estimation is performed on the first PUCCH based on the DMRS within the frequency hopping interval.

[0378] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0379] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the first PUCCH.

[0380] In some embodiments, the method 400 may further include:

[0381] Sending second indication information to the terminal device, where the second indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0382] In some embodiments, the repeatedly receiving a first physical uplink control channel PUCCH sent by a terminal device includes:

[0383] Numbering the frequency hopping intervals based on a time unit in which the first PUCCH is first transmitted as a starting point;

[0384] For the frequency hopping interval numbered as an even number, receiving the first PUCCH at a first frequency domain position;

[0385] For the odd-numbered frequency hopping intervals, the first PUCCH is received at a second frequency domain position.

[0386] It should be understood that the steps in the wireless communication method 400 may refer to the corresponding steps in the wireless communication method 200, and for the sake of brevity, they will not be repeated here.

[0387] Fig.16 is a schematic flow chart of a wireless communication method 500 provided in an embodiment of the present application. The method 500 may be performed as follows Figure 1 The network devices shown are executed.

[0388] like Fig.16 As shown, the method 500 may include:

[0389] S510: Perform joint channel estimation on a message 3 physical uplink shared channel Msg3 PUSCH based on a demodulation reference signal DMRS in each second nominal time window TDW in at least one second nominal time window TDW.

[0390] In some embodiments, the method 500 may further include:

[0391] The length of each second nominal TDW is determined based on the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0392] In some embodiments, the minimum value of the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH is determined as the length of each second nominal TDW.

[0393] In some embodiments, the method 500 may further include:

[0394] The time domain position of each second nominal TDW is determined based on a time unit in which the first transmission of the Msg3 PUSCH is located and a time unit in which the last transmission of the Msg3 PUSCH is located.

[0395] In some embodiments, the starting point of the first time unit in which the Msg3 PUSCH is first transmitted is determined as the starting point of the first second nominal TDW in the at least one second nominal TDW; the end point of the last time unit in which the Msg3 PUSCH is last transmitted is determined as the end point of the last second nominal TDW in the at least one second nominal TDW; the starting point of the first time unit for sending the Msg3 PUSCH after the last time unit in the current second nominal TDW in the at least one second nominal TDW is determined as the starting point of the second nominal TDW after the current second nominal TDW.

[0396] In some embodiments, the method 500 may further include:

[0397] If the terminal device performs frequency hopping between time units and repeatedly sends the Msg3PUSCH to the network device based on at least one second nominal TDW, then when the length of each second nominal TDW is greater than or equal to the length of the frequency hopping interval, joint channel estimation is performed on the Msg3PUSCH based on the frequency hopping interval.

[0398] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0399] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0400] In some embodiments, the method 500 may further include:

[0401] Receive third indication information, where the third indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0402] In some embodiments, the method 500 may further include:

[0403] The frequency hopping intervals are numbered starting from the time unit where the first transmission of the Msg3 PUSCH is located;

[0404] For the frequency hopping interval numbered as an even number, receiving the Msg3 PUSCH at a first frequency domain position;

[0405] For the odd-numbered frequency hopping interval, the Msg3 PUSCH is received at a second frequency domain position.

[0406] It should be understood that the steps in the wireless communication method 500 may refer to the corresponding steps in the wireless communication method 300, and for the sake of brevity, they will not be repeated here.

[0407] Combination of the above Figures 1 to 16 , describes in detail the method embodiment of the present application, and the following is combined with Figures 17 to 22 , describe in detail the device embodiments of the present application.

[0408] Fig.17 It is a schematic block diagram of a terminal device 610 according to an embodiment of the present application.

[0409] like Fig.17 As shown, the terminal device 610 may include:

[0410] The sending unit 611 is configured to repeatedly send a first physical uplink control channel PUCCH to a network device during an initial access phase.

[0411] In some embodiments, the sending unit 611 is further configured to:

[0412] Receive first indication information sent by the network device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

[0413] In some embodiments, the first indication information is also used to indicate the number of repeated transmissions of Msg3 PUSCH.

[0414] In some embodiments, the first indication information is carried in a first modulation and coding strategy MCS field.

[0415] In some embodiments, the first MCS domain is the MCS domain in a random access response RAR uplink grant, or the first MCS domain is the MCS domain in downlink control information DCI 0_0.

[0416] In some embodiments, the first indication information is carried in at least one most significant bit MSB in the first MCS field.

[0417] In some embodiments, at least one least significant bit (LSB) in the first MCS field carries information for indicating an MCS index.

[0418] In some embodiments, the at least one LSB is used to indicate the MCS index in an index candidate value set configured by a system parameter, or the at least one LSB is used to indicate the MCS index in a default index candidate value set.

[0419] In some embodiments, the first indication information is carried in a first PUCCH resource indication field.

[0420] In some embodiments, the first PUCCH resource indication field includes a resource indication field in downlink control information DCI 1_0 of a temporary cell radio network temporary identity TC-RNTI scrambled cyclic redundancy check CRC.

[0421] In some embodiments, the first PUCCH resource indication field is also used to indicate the transmission resources of Msg4.

[0422] In some embodiments, the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a default set of candidate values.

[0423] In some embodiments, the maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the candidate value set.

[0424] In some embodiments, if the first indication information is carried in the first PUCCH resource indication field, and the maximum number of values ​​of the first indication information is greater than the number of candidate values ​​in the candidate value set, then the multiple values ​​of the first PUCCH resource indication field correspond to one candidate value in the candidate value set; or the first indication information is carried in at least one highest bit MSB in the first PUCCH resource indication field; or the first indication information is carried in at least one lowest bit LSB in the first PUCCH resource indication field.

[0425] In some embodiments, if the first indication information is carried in at least one highest bit MSB in the first MCS domain, and the maximum number of values ​​of the at least one MSB is greater than the number of candidate values ​​in the number candidate value set, then the multiple values ​​of the at least one MSB correspond to a candidate value in the number candidate set; or the first indication information is carried in one or more MSBs in the at least one MSB; or the first indication information is carried in one or more LSBs in the at least one MSB.

[0426] In some embodiments, the sending unit 611 is specifically used for:

[0427] Repeating sending the first PUCCH to the network device over N time units;

[0428] Wherein, N represents the number of repeated transmissions of the first PUCCH.

[0429] In some embodiments, the sending unit 611 is further configured to:

[0430] In each of the at least one first nominal TDW, the power of the first PUCCH is maintained to be consistent and the phase of the first PUCCH is maintained to be continuous.

[0431] In some embodiments, the sending unit 611 is further configured to:

[0432] The length of each first nominal TDW is determined based on the number of repeated transmissions of the first PUCCH and the length of a time window indicated by the network device for performing joint channel estimation on the first PUCCH.

[0433] In some embodiments, the sending unit 611 is specifically used for:

[0434] The minimum value between the number of repeated transmissions of the first PUCCH and the length of the time window indicated by the network device for performing joint channel estimation on the first PUCCH is determined as the length of each first nominal TDW.

[0435] In some embodiments, the sending unit 611 is further configured to:

[0436] The time domain position of each of the first nominal TDWs is determined based on a time unit in which the first PUCCH is first transmitted and a time unit in which the first PUCCH is last transmitted.

[0437] In some embodiments, the sending unit 611 is specifically used for:

[0438] Determine a starting point of a first time unit in which the first PUCCH is first transmitted as a starting point of a first first nominal TDW in the at least one first nominal TDW;

[0439] Determine an end point of a last time unit in which the first PUCCH is last transmitted as an end point of a last first nominal TDW in the at least one first nominal TDW;

[0440] A starting point of a first time unit for sending the first PUCCH after a last time unit in a current first nominal TDW in the at least one first nominal TDW is determined as a starting point of a first nominal TDW after the current first nominal TDW.

[0441] In some embodiments, the sending unit 611 is further configured to:

[0442] If the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, then when the length of each first nominal TDW is greater than or equal to the length of the frequency hopping interval, based on the frequency hopping interval, the power of the first PUCCH is maintained consistent and the phase of the first PUCCH is maintained continuous.

[0443] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0444] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the first PUCCH.

[0445] In some embodiments, the sending unit 611 is further configured to:

[0446] Receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0447] In some embodiments, the sending unit 611 is specifically used for:

[0448] Numbering the frequency hopping intervals based on a time unit in which the first PUCCH is first transmitted as a starting point;

[0449] For the frequency hopping interval numbered as an even number, sending the first PUCCH at a first frequency domain position;

[0450] For the odd-numbered frequency hopping intervals, the first PUCCH is sent at a second frequency domain position.

[0451] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Fig.17 The terminal device 610 shown can correspond to the corresponding subject in the method 200 for executing the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the terminal device 610 are respectively for implementing the corresponding processes in each method provided in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0452] Fig.18 It is a schematic block diagram of a terminal device 620 according to an embodiment of the present application.

[0453] like Fig.18 As shown, the terminal device 620 may include:

[0454] The receiving unit 621 is configured to maintain the power consistency of the message 3 physical uplink shared channel Msg3 PUSCH and the phase continuity of the Msg3 PUSCH in each second TDW of at least one second nominal time window TDW.

[0455] In some embodiments, the maintaining unit 621 is further used for:

[0456] The length of each second nominal TDW is determined based on the number of repeated transmissions of the Msg3 PUSCH and the length of a time window indicated by a network device for performing joint channel estimation on the Msg3 PUSCH.

[0457] In some embodiments, the maintaining unit 621 is specifically used for:

[0458] The minimum value of the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH is determined as the length of each second nominal TDW.

[0459] In some embodiments, the maintaining unit 621 is further used for:

[0460] The time domain position of each second nominal TDW is determined based on a time unit in which the first transmission of the Msg3 PUSCH is located and a time unit in which the last transmission of the Msg3 PUSCH is located.

[0461] In some embodiments, the maintaining unit 621 is specifically used for:

[0462] Determine the starting point of the first time unit in which the first transmission of the Msg3 PUSCH is located as the starting point of the first second nominal TDW in the at least one second nominal TDW;

[0463] Determine the end point of the last time unit in which the last transmission of the Msg3 PUSCH is located as the end point of the last second nominal TDW in the at least one second nominal TDW;

[0464] A starting point of a first time unit for sending the Msg3 PUSCH after a last time unit in a current second nominal TDW in the at least one second nominal TDW is determined as a starting point of a second nominal TDW after the current second nominal TDW.

[0465] In some embodiments, the maintaining unit 621 is further used for:

[0466] If the terminal device performs frequency hopping between time units and repeatedly sends the Msg3PUSCH to the network device based on at least one second nominal TDW, then when the length of each second nominal TDW is greater than or equal to the length of the frequency hopping interval, based on the frequency hopping interval, the power of the Msg3 PUSCH is maintained consistent and the phase of the Msg3 PUSCH is maintained continuous.

[0467] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0468] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0469] In some embodiments, the maintaining unit 621 is further used for:

[0470] Receive third indication information, where the third indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0471] In some embodiments, the maintaining unit 621 is further used for:

[0472] The frequency hopping intervals are numbered starting from the time unit where the first transmission of the Msg3 PUSCH is located;

[0473] For the frequency hopping interval numbered as an even number, sending the Msg3 PUSCH at a first frequency domain position;

[0474] For the odd-numbered frequency hopping interval, the Msg3 PUSCH is sent at the second frequency domain position.

[0475] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Fig.18 The terminal device 620 shown can correspond to the corresponding subject in the method 300 for executing the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the terminal device 620 are respectively for implementing the corresponding processes in each method provided in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0476] Fig.19 It is a schematic block diagram of a network device 710 according to an embodiment of the present application.

[0477] like Fig.19 As shown, the network device 710 may include:

[0478] The receiving unit 711 is used to repeatedly receive the first physical uplink control channel PUCCH sent by the terminal device during the initial access phase.

[0479] In some embodiments, the receiving unit 711 is further configured to:

[0480] Sending first indication information to the terminal device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

[0481] In some embodiments, the first indication information is also used to indicate the number of repeated transmissions of Msg3 PUSCH.

[0482] In some embodiments, the first indication information is carried in a first modulation and coding strategy MCS field.

[0483] In some embodiments, the first MCS domain is the MCS domain in a random access response RAR uplink grant, or the first MCS domain is the MCS domain in downlink control information DCI 0_0.

[0484] In some embodiments, the first indication information is carried in at least one most significant bit MSB in the first MCS field.

[0485] In some embodiments, at least one least significant bit (LSB) in the first MCS field carries information for indicating an MCS index.

[0486] In some embodiments, the at least one LSB is used to indicate the MCS index in an index candidate value set configured by a system parameter, or the at least one LSB is used to indicate the MCS index in a default index candidate value set.

[0487] In some embodiments, the first indication information is carried in a first PUCCH resource indication field.

[0488] In some embodiments, the first PUCCH resource indication field includes a resource indication field in downlink control information DCI 1_0 of a temporary cell radio network temporary identity TC-RNTI scrambled cyclic redundancy check CRC.

[0489] In some embodiments, the first PUCCH resource indication field is also used to indicate the transmission resources of Msg4.

[0490] In some embodiments, the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a default set of candidate values.

[0491] In some embodiments, the maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the candidate value set.

[0492] In some embodiments, if the first indication information is carried in the first PUCCH resource indication field, and the maximum number of values ​​of the first indication information is greater than the number of candidate values ​​in the candidate value set, then the multiple values ​​of the first PUCCH resource indication field correspond to one candidate value in the candidate value set; or the first indication information is carried in at least one highest bit MSB in the first PUCCH resource indication field; or the first indication information is carried in at least one lowest bit LSB in the first PUCCH resource indication field.

[0493] In some embodiments, if the first indication information is carried in at least one highest bit MSB in the first MCS domain, and the maximum number of values ​​of the at least one MSB is greater than the number of candidate values ​​in the number candidate value set, then the multiple values ​​of the at least one MSB correspond to a candidate value in the number candidate set; or the first indication information is carried in one or more MSBs in the at least one MSB; or the first indication information is carried in one or more LSBs in the at least one MSB.

[0494] In some embodiments, the receiving unit 711 is specifically configured to:

[0495] Repeating receiving the first PUCCH sent by the terminal device over N time units;

[0496] Wherein, N represents the number of repeated transmissions of the first PUCCH.

[0497] In some embodiments, the receiving unit 711 is further configured to:

[0498] A demodulation reference signal DMRS in each first nominal TDW of at least one first nominal TDW is used to perform joint channel estimation on the first PUCCH.

[0499] In some embodiments, the receiving unit 711 is further configured to:

[0500] The length of each first nominal TDW is determined based on the number of repeated transmissions of the first PUCCH and the length of a time window indicated by the network device for performing joint channel estimation on the first PUCCH.

[0501] In some embodiments, the receiving unit 711 is specifically configured to:

[0502] The minimum value between the number of repeated transmissions of the first PUCCH and the length of the time window indicated by the network device for performing joint channel estimation on the first PUCCH is determined as the length of each first nominal TDW.

[0503] In some embodiments, the receiving unit 711 is further configured to:

[0504] The time domain position of each of the first nominal TDWs is determined based on a time unit in which the first PUCCH is first transmitted and a time unit in which the first PUCCH is last transmitted.

[0505] In some embodiments, the receiving unit 711 is specifically configured to:

[0506] Determine a starting point of a first time unit in which the first PUCCH is first transmitted as a starting point of a first first nominal TDW in the at least one first nominal TDW;

[0507] Determine an end point of a last time unit in which the first PUCCH is last transmitted as an end point of a last first nominal TDW in the at least one first nominal TDW;

[0508] A starting point of a first time unit for sending the first PUCCH after a last time unit in a current first nominal TDW in the at least one first nominal TDW is determined as a starting point of a first nominal TDW after the current first nominal TDW.

[0509] In some embodiments, the receiving unit 711 is further configured to:

[0510] If the terminal device performs frequency hopping between time units and repeatedly sends the first PUCCH to the network device based on at least one first nominal TDW, then when the length of each first nominal TDW is greater than or equal to the length of the frequency hopping interval, joint channel estimation is performed on the first PUCCH based on the DMRS within the frequency hopping interval.

[0511] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0512] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the first PUCCH.

[0513] In some embodiments, the receiving unit 711 is further configured to:

[0514] Sending second indication information to the terminal device, where the second indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0515] In some embodiments, the receiving unit 711 is specifically configured to:

[0516] Numbering the frequency hopping intervals based on a time unit in which the first PUCCH is first transmitted as a starting point;

[0517] For the frequency hopping interval numbered as an even number, receiving the first PUCCH at a first frequency domain position;

[0518] For the odd-numbered frequency hopping intervals, the first PUCCH is received at a second frequency domain position.

[0519] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Fig.19 The network device 710 shown may correspond to a corresponding subject in the method 400 for executing an embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the network device 710 are respectively for implementing the corresponding processes in each method provided in an embodiment of the present application, and for the sake of brevity, they will not be repeated here.

[0520] Fig. 20 It is a schematic block diagram of the network device 720 according to an embodiment of the present application.

[0521] like Fig. 20 As shown, the network device 720 may include:

[0522] The estimating unit 721 is configured to perform joint channel estimation on a message 3 physical uplink shared channel Msg3 PUSCH based on a demodulation reference signal DMRS in each second nominal time window TDW in at least one second nominal time window TDW.

[0523] In some embodiments, the estimation unit 721 is further configured to:

[0524] The length of each second nominal TDW is determined based on the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0525] In some embodiments, the estimation unit 721 is specifically used for:

[0526] The minimum value of the number of repeated transmissions of the Msg3 PUSCH and the length of the time window indicated by the network device for performing joint channel estimation on the Msg3 PUSCH is determined as the length of each second nominal TDW.

[0527] In some embodiments, the estimation unit 721 is further configured to:

[0528] The time domain position of each second nominal TDW is determined based on a time unit in which the first transmission of the Msg3 PUSCH is located and a time unit in which the last transmission of the Msg3 PUSCH is located.

[0529] In some embodiments, the estimation unit 721 is specifically used for:

[0530] Determine the starting point of the first time unit in which the first transmission of the Msg3 PUSCH is located as the starting point of the first second nominal TDW in the at least one second nominal TDW;

[0531] Determine the end point of the last time unit in which the last transmission of the Msg3 PUSCH is located as the end point of the last second nominal TDW in the at least one second nominal TDW;

[0532] A starting point of a first time unit for sending the Msg3 PUSCH after a last time unit in a current second nominal TDW in the at least one second nominal TDW is determined as a starting point of a second nominal TDW after the current second nominal TDW.

[0533] In some embodiments, the estimation unit 721 is further configured to:

[0534] If the terminal device performs frequency hopping between time units and repeatedly sends the Msg3PUSCH to the network device based on at least one second nominal TDW, then when the length of each second nominal TDW is greater than or equal to the length of the frequency hopping interval, joint channel estimation is performed on the Msg3PUSCH based on the frequency hopping interval.

[0535] In some embodiments, the frequency hopping interval includes at least one continuous time unit.

[0536] In some embodiments, the frequency hopping interval is configured by a system parameter, or the frequency hopping interval is a time window length indicated by the network device for performing joint channel estimation on the Msg3 PUSCH.

[0537] In some embodiments, the estimation unit 721 is further configured to:

[0538] Receive third indication information, where the third indication information is used to instruct the terminal device to perform frequency hopping between time units.

[0539] In some embodiments, the estimation unit 721 is further configured to:

[0540] The frequency hopping intervals are numbered starting from the time unit where the first transmission of the Msg3 PUSCH is located;

[0541] For the frequency hopping interval numbered as an even number, receiving the Msg3 PUSCH at a first frequency domain position;

[0542] For the odd-numbered frequency hopping interval, the Msg3 PUSCH is received at a second frequency domain position.

[0543] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Fig. 20 The network device 720 shown may correspond to the corresponding subject in the method 500 for executing the embodiment of the present application, and the aforementioned and other operations and / or functions of each unit in the network device 720 are respectively for implementing the corresponding processes in each method provided in the embodiment of the present application, and for the sake of brevity, they will not be repeated here.

[0544] The communication device of the embodiment of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0545] For example, the processing unit and the communication unit mentioned above may be implemented by a processor and a transceiver, respectively.

[0546] Fig.21 It is a schematic structural diagram of a communication device 800 according to an embodiment of the present application.

[0547] like Fig.21 As shown, the communication device 800 may include a processor 810 .

[0548] The processor 810 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0549] like Fig.21As shown, the communication device 800 may further include a memory 820 .

[0550] The memory 820 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 810. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application. The memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.

[0551] like Fig.21 As shown, the communication device 800 may further include a transceiver 830 .

[0552] The processor 810 may control the transceiver 830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0553] It should be understood that the various components in the communication device 800 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0554] It should also be understood that the communication device 800 may be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, that is, the communication device 800 of the embodiment of the present application may correspond to the terminal device 610 or the terminal device 620 in the embodiment of the present application, and may correspond to the corresponding subject in the method 200 or 300 according to the embodiment of the present application, for the sake of brevity, it will not be repeated here. Similarly, the communication device 800 may be a network device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. That is to say, the communication device 800 of the embodiment of the present application may correspond to the network device 710 or the network device 720 in the embodiment of the present application, and may correspond to the corresponding subject in the method 400 or 500 according to the embodiment of the present application, for the sake of brevity, it will not be repeated here.

[0555] In addition, a chip is also provided in an embodiment of the present application.

[0556] For example, the chip may be an integrated circuit chip with signal processing capabilities, and can implement or execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application. The chip may also be called a system-level chip, a system chip, a chip system, or a system-on-chip chip, etc. Optionally, the chip can be applied to various communication devices, so that the communication device equipped with the chip can execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application.

[0557] Fig. 22 is a schematic structural diagram of a chip 900 according to an embodiment of the present application.

[0558] like Fig. 22 As shown, the chip 900 includes a processor 910 .

[0559] The processor 910 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0560] like Fig. 22 As shown, the chip 900 may further include a memory 920 .

[0561] The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application. The memory 920 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 910. The memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

[0562] like Fig. 22 As shown, the chip 900 may further include an input interface 930 .

[0563] The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0564] like Fig. 22 As shown, the chip 900 may further include an output interface 940 .

[0565] The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0566] It should be understood that the chip 900 can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, and can also implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be repeated here.

[0567] It should also be understood that the various components in the chip 900 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0568] The processors mentioned above may include but are not limited to:

[0569] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0570] The processor can be used to implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor, or a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0571] The memory mentioned above includes but is not limited to:

[0572] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0573] It should be noted that the memory described herein is intended to include these and any other suitable types of memory.

[0574] A computer-readable storage medium is also provided in an embodiment of the present application for storing a computer program. The computer-readable storage medium stores one or more programs, and the one or more programs include instructions, which, when executed by a portable electronic device including multiple applications, can enable the portable electronic device to perform the wireless communication method provided in the present application. Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be repeated here for the sake of brevity. Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0575] A computer program product is also provided in the embodiment of the present application, including a computer program. Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity. Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0576] A computer program is also provided in the embodiment of the present application. When the computer program is executed by a computer, the computer can execute the wireless communication method provided in the present application. Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not repeated here. Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, it is not repeated here.

[0577] The embodiment of the present application also provides a communication system, which may include the terminal device and the network device involved above to form a communication system as follows: Figure 1 The communication system 100 shown is not described in detail for the sake of brevity. It should be noted that the term "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.

[0578] It should also be understood that the terms used in the embodiments of the present application and the appended claims are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present application. For example, the singular forms "a", "said", "above", and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0579] It can be appreciated by those skilled in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or in combination with computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application. If implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or part of the prior art that contributes to the prior art or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a disk, or an optical disk.

[0580] Those skilled in the art may also realize that, for the convenience and simplicity of description, the specific working process of the above-described system, device and unit may refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In several embodiments provided in the present application, it should be understood that the disclosed system, device and method may be implemented in other ways. For example, the division of units or modules or components in the device embodiment described above is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or modules or components may be combined or integrated into another system, or some units or modules or components may be ignored or not executed. For another example, the above-mentioned unit / module / component described as a separation / display component may or may not be physically separated, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the units / modules / components may be selected according to actual needs to achieve the purpose of the embodiment of the present application. Finally, it should be noted that the coupling or direct coupling or communication connection between each other shown or discussed above may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0581] The above contents are only specific implementation methods of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: The method is applicable to a terminal device, and the method comprises: In the initial access phase or before establishing a radio resource control RRC connection, the first physical uplink control channel PUCCH is repeatedly sent to the network device.

2. The method according to claim 1, characterized in that: The method further comprises: A first request is sent to the network device, where the first request is used to request repeated sending of the first PUCCH.

3. The method according to claim 2, characterized in that The sending a first request to the network device comprises: When the measurement result of the downlink reference signal of the terminal device is less than or equal to the first threshold value, the first request is sent to the network device.

4. The method according to claim 2 or 3, characterized in that: The sending a first request to the network device comprises: Send Msg3 to the network device, where the Msg3 includes the first request.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Receive first indication information sent by the network device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

6. The method according to claim 5, characterized in that The first indication information is carried in a first PUCCH resource indication field.

7. The method according to claim 6, characterized in that The first PUCCH resource indication field includes the resource indication field in the downlink control information DCI 1_0 of the temporary cell radio network temporary identity TC-RNTI scrambled cyclic redundancy check CRC.

8. The method according to any one of claims 5 to 7, characterized in that The first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of default candidate values.

9. The method according to claim 8, characterized in that The maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the candidate value set.

10. A wireless communication method, characterized in that: The method is applicable to a network device, and the method comprises: In the initial access phase or before establishing a unlimited resource control RRC connection, the first physical uplink control channel PUCCH sent by the terminal device is repeatedly received.

11. The method according to claim 10, characterized in that The method further comprises: Receive a first request sent by the terminal device, where the first request is used to request repeated sending of the first PUCCH.

12. The method according to claim 11, characterized in that The receiving a first request sent by the terminal device includes: Receive the first request sent by the terminal device when the measurement result of the downlink reference signal is less than or equal to the first threshold value.

13. The method according to claim 11 or 12, characterized in that: The receiving a first request sent by the terminal device includes: Receive Msg3 sent by the terminal device, where the Msg3 includes the first request.

14. The method according to claim 13, characterized in that The method further comprises: Sending first indication information to the terminal device, where the first indication information is used to indicate the number of repeated transmissions of the first PUCCH.

15. The method according to claim 14, characterized in that The first indication information is carried in a first PUCCH resource indication field.

16. The method according to claim 15, characterized in that The first PUCCH resource indication field includes the resource indication field in the downlink control information DCI 1_0 of the temporary cell radio network temporary identity TC-RNTI scrambled cyclic redundancy check CRC.

17. The method according to any one of claims 14 to 16, characterized in that The first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of candidate values ​​configured by system parameters, or the first indication information is used to indicate the number of repeated transmissions of the first PUCCH in a set of default candidate values.

18. The method according to claim 17, characterized in that The maximum number of values ​​that the first indication information can take is greater than or equal to the number of candidate values ​​in the candidate value set.

19. A terminal device, characterized in that: include: The sending unit is used to repeatedly send a first physical uplink control channel PUCCH to the network device in an initial access phase.

20. A network device, characterized in that: include: The receiving unit is used to repeatedly receive the first physical uplink control channel PUCCH sent by the terminal device during the initial access phase.

21. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 9.

22. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the network device executes the method according to any one of claims 10 to 18.

Images