Wireless communication method and device

By providing first indication information based on terminal device capability, the method optimizes PUCCH resource allocation in non-terrestrial networks, reducing waste and enhancing random access success rates.

JP2026502560APending Publication Date: 2026-01-23QUECTEL WIRELESS SOLUTIONS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025540887
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-01-12
Filing Date
2023-02-28
Publication Date
2026-01-23

AI Technical Summary

Technical Problem

In non-terrestrial network systems, the repeated transmission of physical uplink control channels (PUCCH) to improve uplink coverage results in waste of network resources due to the network not knowing the terminal device's capability for repeated transmissions.

Method used

A wireless communication method where the network device provides first indication information based on terminal device capability to repeatedly transmit PUCCH, optimizing resource allocation and reducing resource waste.

Benefits of technology

This approach reduces network resource waste by ensuring that PUCCH transmissions are only scheduled if the terminal device supports repeated transmissions, thereby improving the success rate of random access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026502560000001_ABST
    Figure 2026502560000001_ABST
Patent Text Reader

Abstract

The present application provides a wireless communication method and apparatus, in which, before a terminal device establishes an RRC connection with a network device, the network device instructs the terminal device to repeatedly transmit a PUCCH based on whether the terminal device supports repeated transmission of the PUCCH, thereby helping to reduce waste of network resources. The method includes the steps of: receiving a first message of a random access process by the terminal device; and repeatedly transmitting a first PUCCH by the terminal device based on first indication information of the network device, the first PUCCH being used to carry feedback information corresponding to the first message, the first indication information being determined based on first information, and the first information being used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] TECHNICAL FIELD This application relates to the field of communications, and more particularly to wireless communication methods and apparatus. [Background technology]

[0002] Some communication systems (e.g., non-terrestrial network (NTN) systems) have large transmission delays. In the random access process of such communication systems, the terminal equipment can improve uplink coverage through repeated transmissions. For example, the terminal equipment can ensure a high random access success rate by repeatedly transmitting a physical uplink control channel (PUCCH) carrying feedback information of message 4.

[0003] However, in the random access process, when the network equipment configures resources for repeatedly transmitting PUCCH to the terminal equipment, this may result in a waste of network resources. Summary of the Invention [Problem to be solved by the invention]

[0004] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Various aspects of the present embodiments are described below. [Means for solving the problem]

[0005] In a first aspect, a wireless communication method is provided, comprising the steps of: a terminal device receiving a first message of a random access process; and the terminal device repeatedly transmitting a first PUCCH based on first indication information of a network device, the first PUCCH being used to carry feedback information corresponding to the first message, wherein the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.

[0006] In a second aspect, a wireless communication method is provided, comprising the steps of: a network device transmitting a first message of a random access process; and the network device receiving a first PUCCH repeatedly transmitted by a terminal device based on first indication information of the network device, the first PUCCH being used to carry feedback information corresponding to the first message, wherein the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.

[0007] In a third aspect, a wireless communication device is provided, wherein the device is a terminal device, the terminal device including a receiving unit for receiving a first message of a random access process and a transmitting unit for repeatedly transmitting a first PUCCH based on first indication information of a network device, the first PUCCH being used to carry feedback information corresponding to the first message, the first indication information being determined based on first information, and the first information being used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.

[0008] In a fourth aspect, a wireless communication device is provided, wherein the device is a network equipment, the network equipment including a transmitting unit for transmitting a first message of a random access process and a receiving unit for receiving a first PUCCH repeatedly transmitted by a terminal equipment based on first indication information of the network equipment, the first PUCCH being used to carry feedback information corresponding to the first message, the first indication information being determined based on first information, and the first information being used to indicate whether the terminal equipment has the capability to repeatedly transmit the first PUCCH.

[0009] In a fifth aspect, there is provided a communications device comprising a memory and a processor, the memory being adapted to store a program, and the processor being adapted to call the program in the memory to perform the method of the first or second aspect.

[0010] In a sixth aspect, there is provided an apparatus including a processor for calling a program from a memory to perform a method according to the first or second aspect.

[0011] In a seventh aspect, there is provided a chip including a processor for calling a program from a memory to cause a device in which the chip is installed to carry out a method according to the first or second aspect.

[0012] In an eighth aspect, there is provided a computer-readable storage medium having stored thereon a program for causing a computer to execute the method according to the first or second aspect.

[0013] In a ninth aspect, there is provided a computer program product comprising a program that causes a computer to carry out a method according to the first or second aspect.

[0014] In a tenth aspect, there is provided a computer program causing a computer to carry out the method according to the first or second aspect. [Effects of the Invention]

[0015] The terminal device according to the embodiment of the present application repeatedly transmits the first PUCCH based on the first indication information of the network device. The first indication information is related to whether the terminal device has the capability to repeatedly transmit the first PUCCH. Therefore, it can be seen that the network device according to the embodiment of the present application takes into account the capability information of the terminal device when determining the first indication information, which contributes to reducing waste of network resources. [Brief explanation of the drawings]

[0016] [Figure 1] 1 is a diagram illustrating a wireless communication system applied in an embodiment of the present application. [Figure 2] 1 is a flowchart of a random access process. [Figure 3] FIG. 10 is a schematic diagram of the preamble structure in step S210. [Figure 4] 1 is a flowchart of a wireless communication method according to an embodiment of the present application; [Figure 5] 1 is a schematic structural diagram of a possible implementation of a preamble in an embodiment of the present application; [Figure 6] FIG. 10 is a schematic structural diagram of another possible implementation of a preamble in an embodiment of the present application; [Figure 7] 1 is a structural schematic diagram of a wireless communication device according to an embodiment of the present application; [Figure 8] FIG. 2 is a structural schematic diagram of another wireless communication device according to an embodiment of the present application; [Figure 9] 1 is a structural schematic diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, the technical solutions in the embodiments of the present application will be described with reference to the drawings in the embodiments of the present application, and obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments, and all other embodiments that can be obtained by those skilled in the art without any creative work for the embodiments of the present application also fall within the scope of protection of the present application.

[0018] Embodiments of the present application may be applied to various communication systems. For example, embodiments of the present application may be applied to a global system of mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolution of an NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system, an NTN system, a universal mobile telecommunication system (UMTS), a wireless local area network (WLAN), a wireless fidelity (WFI), a wireless local area network (WLAN), a wireless cellular ... The present invention may be applied to wireless communication systems, such as WiFi (Wireless Internet Protocol) and 5th-generation (5G) systems. The present invention may also be applied to other communication systems, such as future communication systems. The future communication systems may be, for example, sixth-generation (6G) mobile communication systems and satellite communication systems.

[0019] Conventional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, etc., and embodiments of the present application can also be applied to communication systems supporting such communication methods.

[0020] The communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0021] The communication system according to the embodiment of the present application may be applied to an unlicensed spectrum, which may be considered a shared spectrum, or may be applied to a licensed spectrum, which may be considered a dedicated spectrum.

[0022] The embodiments of the present application may be applied to terrestrial networks (TN) systems, and may also be applied to NTN systems, including, for example, 4G-based NTN systems, NR-based NTN systems, internet of things (IoT)-based NTN systems, and narrowband internet of things (NB-IoT)-based NTN systems.

[0023] A communication system may include one or more terminal devices, which may be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment.

[0024] In some embodiments, the terminal device may be a station (ST) in a WLAN, hi some embodiments, the terminal device 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) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system (e.g., an NR system), or a terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0025] In some embodiments, a terminal device may refer to a device that provides voice and / or data connectivity to a user. For example, the terminal device may be a handheld device with wireless connectivity, an in-vehicle device, etc. As some specific examples, the terminal device may be a mobile phone, a tablet PC (Pad), a laptop, a palmtop computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0026] In some embodiments, the terminal equipment may be located on land, for example, the terminal equipment may be located indoors or outdoors, in some embodiments, the terminal equipment may be located on water, for example, on a ship, in some embodiments, the terminal equipment may be located in the air, for example, on an airplane, a balloon, or a satellite.

[0027] In addition to terminal devices, a communication system may include one or more network devices. The network device in the present embodiment may be a device for communicating with terminal devices, and may be referred to as an access network device or a radio access network device. The network device may be, for example, a base station. The network device in the present embodiment may refer to a radio access network (RAN) node (or device) that allows terminal devices to access a wireless network. The base station may broadly cover or be replaced with various names such as a Node B (Node B), evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), primary base station MeNB, secondary base station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, radio node, access point (AP), transmission node, transmitting and receiving node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station may also be a macro base station, micro base station, relay node, donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem, or chip installed in the aforementioned device or apparatus, etc. The base station may also be a mobile switching center and a device that functions as a base station in D2D, V2X, or M2M communications, a network-side device in a 6G network, or a device that functions as a base station in a future communication system.The base station can support networks of the same or different access technologies, and the embodiments of the present application do not limit the specific technologies adopted by the network equipment and the specific equipment configurations.

[0028] The base station may be fixed or mobile. For example, a helicopter or a drone may be configured as a mobile base station, and one or more cells may move depending on the location of the mobile base station. In another example, a helicopter or a drone may be configured as a device for communicating with another base station.

[0029] In some deployments, the network equipment in the embodiments of the present application may refer to a CU or a DU, or may include a CU and a DU. The gNB may further include an AAU.

[0030] As an example and not by way of limitation, in some embodiments of the present application, the network equipment may have mobile characteristics, e.g., the network equipment may be a mobile equipment. In some embodiments of the present application, the network equipment may be a satellite or balloon station. In some embodiments of the present application, the network equipment may also be a base station located on land, in water, or other locations.

[0031] In an embodiment of the present application, a network device can provide a service to a cell, and a terminal device communicates with the network device via transmission resources (e.g., frequency domain resources or spectrum resources) used by the cell. The cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell. The small cell here may include a metro cell, a micro cell, a pico cell, a femto cell, etc. These small cells have the characteristics of a small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0032] 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application. As shown in FIG. 1, the communication system 100 may include a network device 110, which may be a device that communicates with terminal devices 120 (communication terminals, also referred to as terminals). The network device 110 may provide communication coverage to a specific geographic area and communicate with terminal devices located within the coverage area.

[0033] FIG. 1 exemplarily illustrates one network device and two terminal devices, and in some embodiments of the present application, the communication system 100 may include multiple network devices, and other numbers of terminal devices may be included within the coverage range of each network device, and the embodiments of the present application are not limited thereto.

[0034] In an embodiment of the present application, the wireless communication system shown in FIG. 1 may further include other network entities such as a mobility management entity (MME), an access and mobility management function (AMF), etc., and the embodiment of the present application is not limited thereto.

[0035] In the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, and the embodiments of the present application are not limited thereto.

[0036] For ease of understanding, we first introduce some related technical knowledge related to the embodiments of the present application. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional technical solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents:

[0037] With the development of mobile communication technology, coverage issues have gradually emerged and attracted widespread attention in the industry. Taking 5G network systems as an example, comparing them with 4G networks, the following two factors can be seen as the main causes of coverage issues. First, the operating frequency band of 5G systems is higher than that of 4G. For example, 5G systems include the 3.5 GHz frequency band (Frequency Range 1, FR1) and the 26 GHz millimeter-wave frequency band (FR2). FR1 refers to the 5G sub-6 GHz frequency band, and FR2 refers to the 5G millimeter-wave frequency band. Higher frequency bands have higher path loss than lower frequency bands. For example, the path loss at 3.5 GHz is 6 to 7 dB higher than at 1.8 GHz, and indoor coverage is 5 to 10 dB weaker. Second, 5G systems aim to provide higher user experience rates and cell edge rates, which places higher requirements on coverage performance. Therefore, 5G networks face greater challenges than 4G networks in terms of coverage, especially in outdoor-to-indoor coverage scenarios.

[0038] Wireless communication systems typically use repeated transmission to improve coverage performance. Repeated transmission is a very effective means of improving signal transmission quality. Signal repetition can improve receiver detection and decoding performance. For example, in the random access process of an NR system, the network equipment and terminal equipment can resolve contention that may occur when multiple terminal equipment in a cell simultaneously transmit the same preamble by exchanging messages (Message 3 and Message 4). Message 3 is transmitted from the terminal equipment to the network equipment via an uplink channel. The coverage performance of Message 3 is poorer than that of other channels, making it difficult for terminal equipment in areas with poor signal coverage quality to access the cell. Therefore, in NR systems, a mechanism for repeated transmission of Message 3 is introduced to improve the coverage performance of Message 3. However, the entire random access process is completed and the RRC connection is initiated only after the user receives Message 4 and sends hybrid automatic repeat request (HARQ) feedback. The coverage performance of the HARQ feedback similarly affects the success rate of random access by the terminal equipment.

[0039] The random access process will be described in detail below with reference to Figure 2. In a wireless communication system, a terminal device can establish or reestablish a radio resource control (RRC) connection with a network device through a random access process.

[0040] There are two types of random access methods: contention-based random access (CBRA) and contention-free random access (CFRA). The main flow of the random access process is described below with reference to Figure 2.

[0041] The random access process shown in Fig. 2 includes steps S210 to S250. Steps S210 to S240 are a four-step random access channel (RACH) process.

[0042] In step S210, the terminal device transmits a message 1 (message1, MSG1) to the network device.

[0043] In the 4-step RACH, a terminal device can select a RACH resource and a preamble, and send Message 1 to a network device on the selected resource. The RACH resource is also called a physical random access channel (PRACH) resource. Message 1 includes a preamble for the PRACH resource.

[0044] The network device can broadcast PRACH configuration information to the terminal device. The PRACH configuration information may include PRACH time-frequency resource configuration information and starting preamble root sequence configuration information. Based on the PRACH configuration information, the network device can determine a preamble or a preamble set corresponding to the PRACH.

[0045] The network equipment can inform the terminal equipment of available random access preambles in advance via a system broadcast (e.g., in an initial access scenario) or an RRC message (e.g., in an HO or SN Addition scenario). The preamble may be called a preamble sequence. These preambles support four long sequence preambles with a length of 839 and nine short sequence preambles with a length of 139, the length of which is indicated by the upper layer parameter prach-RootSequenceIndex. In FR1, long sequences and short sequences with subcarrier spacings of 15 KHz and 30 KHz are supported. In FR2, only short sequences with subcarrier spacings of 60 KHz and 120 KHz are supported. Each cell has 64 available preambles, and the terminal equipment can select one of them (or one specified by the network equipment) to upload via PRACH.

[0046] For ease of understanding, the following description will be made with reference to the schematic diagram of preambles shown in Figure 3. Figure 3 is a preamble mapping group diagram when the configuration parameter SSB-perRACHOfRA-Occasion is 1 or less. As shown in Figure 3, the 64 preambles can be divided into two parts: one part is preambles used for CBRA and CFRA and higher capabilities / other needs of terminal equipment indicated by totalNumberOfRA-Preambles, and the other part is other preambles other than totalNumberOfRA-Preambles, and the preambles in this part are used for other purposes. If totalNumberOfRA-Preambles is not a specific number of preambles, all 64 preambles are used for CBRA and CFRA.

[0047] Continuing to refer to FIG. 3, the CBRA preambles are divided into two groups, CBRA group A and CBRA group B. CBRA group A is configured by totalNumberOfRA-PreambleGroupA. CBRA group B does not necessarily exist, and its parameter configuration is configured by ssb-perRACH-OccasionAndCB-PreamblesPerSSB. For CBRA parameter configuration, the network device can transmit these configurations via RACH-ConfigCommon (BWP-Common in system information block 1 (SIB1)). For CFRA parameter configuration, the network device can configure the parameters via RACH-ConfigDedicated.

[0048] A terminal device can select a preamble based on a specific strategy. Because a preamble is shared by multiple terminal devices, there may be a conflict situation where multiple terminal devices select the same preamble. To resolve the conflict, the network device can handle such conflict using a subsequent resolution mechanism.

[0049] In step S220, the network device sends a message 2 (MSG2) to the terminal device.

[0050] Message 2 is also called a random access response (RAR), and may be carried by a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0051] After transmitting the preamble, the terminal device monitors the PDCCH within the RAR time window. By monitoring the PDCCH, the terminal device receives the RAR scheduled on the PDCCH scrambled by a random access-radio network temporary identifier (RA-RNTI). The RA-RNTI is associated with the time-frequency resource of the RACH used by the terminal device to transmit message 1. After receiving the PDCCH, the terminal device can decode the PDCCH using the RA-RNTI.

[0052] After the terminal device successfully receives the PDCCH, the terminal device can obtain a physical downlink shared channel (PDSCH) scheduled by the PDCCH, and the PDSCH includes an RAR. The RAR may include multiple pieces of information. For example, a subheader of the RAR includes a backoff instruction for indicating a backoff time for retransmitting message 1, a random access preamble identifier in the RAR indicates a preamble index received by the network device in response, a timing advance group (TAG) may be included in the payload of the RAR, which may be used to adjust uplink timing, an uplink grant (UL grant) used to indicate uplink resources for scheduling message 3, and a temporary cell-radio network temporary identifier (TC-RNTI) may be included in the RAR, and the initially accessed terminal device can use the TC-RNTI to decode the PDCCH of message 4.

[0053] The preamble index in the RAR can be used by the terminal device to determine whether reception is successful. If the preamble index in the RAR received by the terminal device is the same as the preamble index transmitted by the terminal device itself, the terminal device can consider that reception of the RAR is successful. After successfully receiving the RAR, the terminal device can stop monitoring the RAR and perform step S230 based on the grant indication carried in the RAR.

[0054] If the terminal device does not receive an RAR within the random access response time window, or if the authentication is not successful, it indicates a failed response. In this case, if the terminal device's random access attempt count is less than a certain upper limit (e.g., 10 attempts), the terminal device can continue to attempt random access. If the number of attempts is greater than the upper limit, it indicates a failed random access.

[0055] In step S230, the terminal device sends a message 3 (MSG3) to the network device.

[0056] The terminal device may transmit a message 3 on an uplink grant scheduled by the network device. The message 3 may be referred to as an RRC connection establishment request message.

[0057] After receiving the preamble in step S210, the network device configures physical uplink shared channel (PUSCH) resources for Message 3 according to the RAR message, so that Message 3 is transmitted on the uplink shared channel (UL-SCH) and uses HARQ, scrambling the PDCCH with the TC-RNTI indicated by the RAR, and scheduling retransmission of Message 3 in a downlink control information (DCI) format, i.e., DCI.

[0058] Message 3 includes a unique identifier (ID) of each terminal device, which is used for contention resolution in step S240. Message 3 may also be used to notify the network device of which event triggers the random access process. Message 3 sent by the terminal device varies in different scenarios. For example, in an initial access scenario of RRC connection establishment, the terminal device may send an RRC connection establishment request using message 3. For example, in an RRC connection re-establishment scenario, the terminal device may send an RRC re-establishment request message using message 3. For example, in a cell handover (HO) scenario, when the terminal device accesses a target cell and there is no dedicated preamble during the handover process, contention-based random access may be triggered. The terminal device may send an RRC handover confirm message and a C-RNTI using message 3.

[0059] In step S240, the network device transmits message 4 (MSG4) to the terminal device.

[0060] After receiving Message 3, the network device schedules Message 4 with DCI scrambled by the TC-RNTI. Message 4 may include a contention resolution identity (CRID) and acknowledgement (ACK) information. Message 4 may carry an RRC configuration message (RRCSetup). Message 4 may be carried via the PDCCH and PDSCH.

[0061] If the terminal device carries a C-RNTI for an RRC re-establishment process or the like in message 3, message 4 is scheduled on a PDCCH scrambled by the C-RNTI, and the terminal device can correspondingly decode the PDCCH using the C-RNTI in message 3 to obtain message 4. If the terminal device does not carry a C-RNTI for initial access or the like in message 3, message 4 may be scheduled on a PDCCH scrambled by the TC-RNTI, and the terminal device can correspondingly decode the PDCCH using the TC-RNTI in message 2 to obtain message 4.

[0062] If the UE contention resolution identity MAC control element included in message 4 successfully decoded by the terminal device matches the UE contention resolution identity sent in message 3, the terminal device considers the random access successful. The terminal device sets the TC-RNTI carried in the RAR to the C-RNTI, thereby completing the four-step random access.

[0063] In step S250, the terminal device sends message 5 (MSG5) to the network device.

[0064] Message 5 may include HARQ ACK information for Message 4 and may further include information related to the RRC connection. Message 5 may be carried in the PUCCH. After completing the transmission of Message 4 in the random access process, the terminal device will feedback whether Message 4 was correctly received via the PUCCH (Message 5).

[0065] Briefly, the terminal device selects a preamble from the preamble pool as its temporary identifier and transmits a random access request to the network equipment. In one cell, each preamble is associated with one preamble index. When the terminal device receives the RAR and it contains a preamble index corresponding to the preamble selected by the terminal device, the terminal device considers that the network equipment has responded to its request. Before transmitting message 5, two interactions occur between the terminal device and the network equipment, and four messages are called, in order, message 1 (random access preamble, uplink), message 2 (random access response, downlink), message 3 (schedule transmission, uplink), and message 4 (contention resolution, downlink). If the terminal device does not successfully receive message 2 or message 4, it means that the random access has failed. The terminal device initiates an RRC connection only after receiving message 4 and transmitting HARQ feedback in message 5.

[0066] In the above random access process, messages transmitted over the uplink channel include Message 1, Message 3, and Message 5. In some scenarios, these uplink communications have poor coverage performance. For example, in the initial access phase, the terminal device cannot perform complex channel measurement or beam training processes, resulting in poorer coverage performance than PDSCH or PUSCH in a connected state. Message 5 contains ACK feedback for Message 4, and whether the transmission is successful is directly related to the establishment or re-establishment of an RRC connection. Therefore, to improve uplink coverage, repeated transmission over PUCCH for ACK feedback supporting Message 4 can be introduced.

[0067] Some communication systems have relatively large transmission delays, which lengthens the overall time required for the random access process. For these systems, the key performance indicator is whether the terminal equipment can finally successfully access the system. For example, the round trip time (RTT) of the NTN network is very long, and some satellite orbits are movable, which can cause long message transmission times. Therefore, ensuring the success rate of random access is very important.

[0068] To ensure the success rate of random access, the coverage performance of data transmission can be improved. For example, in an NTN network, whether message 4 is successfully transmitted determines whether a terminal device can access the NTN network. The ACK feedback (message 5) of message 4 is carried on the PUCCH. When accessing the NTN network, the PUCCH is repeatedly transmitted, which can increase the success rate of terminal devices accessing the NTN cell. In other words, by supporting the repeated transmission of the PUCCH, the success rate of random access can be ensured.

[0069] In the RRC connected state, PUCCH resource scheduling may be dynamically instructed to the terminal device by DCI. Each terminal device is configured with PUCCH resources and the number of PUCCH repetitions for each resource. Therefore, by dynamically instructing PUCCH resources, the network device can instruct the terminal device on the number of repetitions within the same PUCCH. However, this resource scheduling mechanism cannot be used before RRC configuration establishment. However, the terminal device initiates the RRC connection only after sending ACK feedback in message 4. Therefore, a mechanism for instructing PUCCH to repeatedly send ACK before RRC configuration establishment needs to be introduced.

[0070] However, the repeated transmission of the PUCCH depends on the capability of the terminal equipment. During the random access process, the terminal equipment has not yet reported its capability information to the network equipment, so the network equipment does not know whether the terminal equipment supports the repeated transmission of the PUCCH. This means that if the network equipment schedules the repeated transmission of message 5 to a terminal equipment that does not support this feature, it will not only reduce the performance of the PUCCH channel, but also waste network resources.

[0071] Based on this, an embodiment of the present application proposes a wireless communication method, which introduces capability support information related to the terminal device supporting PUCCH repetition, and enables the network device to determine the number of PUCCH repetitions and resources based on this information, thereby optimizing its scheduling decision and system performance. The wireless communication method according to the embodiment of the present application is described in detail below with reference to FIG.

[0072] The method shown in Figure 4 is described from the perspective of interaction between a terminal device and a network device. The terminal device and the network device may be devices that communicate in any of the communication systems described above. For example, the terminal device may be a device that establishes an RRC connection with the network device through a random access procedure.

[0073] In some embodiments, the terminal equipment and the network equipment may be communication equipment in an NTN system. For example, the network equipment may be a satellite corresponding to a quasi-earth fixed cell in the NTN network, or a satellite corresponding to a quasi-earth mobile cell. For example, the terminal equipment may be a terrestrial communication equipment applying to access the NTN network.

[0074] The terminal device can perform random access in various states. In some embodiments, the terminal device can perform initial access in an RRC idle state (RRC_IDLE). In some embodiments, the terminal device can perform access recovery in an RRC inactive state (RRC_INACTIVE).

[0075] The terminal device and the network device may be connected in various application scenarios, such as an RRC connection re-establishment scenario, an other system information (SI) request scenario, and a handover scenario, etc. The various application scenarios may also include uplink desynchronization, uplink data arrival, and downlink data arrival scenarios.

[0076] 4, in step S410, the network device sends a first message of the random access process to the terminal device, and the terminal device receives the first message in response.

[0077] The random access process may be the above-mentioned CBRA process or CFRA process, and may be random access in different states of the terminal equipment and various application scenarios, and is not limited here.

[0078] The first message may be a message exchanged between the network device and the terminal device before establishing or re-establishing an RRC connection in a random access process. In some embodiments, the first message may be message 4 shown in Figure 2 sent by the network device to the terminal device, or may be message 2 shown in Figure 2. In some embodiments, the first message may be an RAR sent by the network device in a non-contention based random access method.

[0079] In step S420, the terminal device repeatedly transmits a first PUCCH according to the first indication information of the network device, where the first PUCCH is used to carry feedback information corresponding to the first message.

[0080] The first indication information of the network device can be determined based on the first information. The first information can indicate whether the terminal device is capable of repeatedly transmitting the first PUCCH. In some embodiments, if the terminal device supports PUCCH repetition in an RRC disconnected state, the terminal device can use the first information to indicate to the network side that it supports repeated transmission of message 5. For example, in uplink transmission of a random access process, the terminal device can use the first information or information related to the first information to indicate to the network side whether it supports repeated transmission of PUCCH HARQ of message 4.

[0081] The network device may obtain the first information in various ways, that is, the first information may be associated with various information, which will be described in detail below with reference to FIGS. 5 and 6.

[0082] Whether the terminal device has the capability to repeatedly transmit the first PUCCH may refer to whether the terminal device supports PUCCH repetition in an RRC disconnected state, that is, whether the terminal device can repeatedly transmit the PUCCH when the network device cannot configure PUCCH dedicated resources for the terminal device through DCI.

[0083] In some embodiments, when the first information indicates that the terminal device has the capability to repeatedly transmit the first PUCCH, the network device can schedule resources for repeated transmission to the terminal device, thereby improving the success rate of random access of the terminal device. The resources for repeated transmission can prevent the terminal device from restarting the random access process due to a single failed transmission of message 5. In a possible implementation, the first indication information of the network device can inform the terminal device of the resources for repeated transmission and the number of repeated transmissions via downlink transmission.

[0084] In some embodiments, if the first information indicates that the terminal device does not have the capability, the network device does not allocate resources for repeated transmission to the terminal device and does not wait for reception, thereby reducing resource waste. As a possible implementation, the first indication information of the network device can indicate that the number of repeated transmissions is 1, and at the same time indicate the resources for the single transmission. As another possible implementation, the network device may not further transmit the first indication information.

[0085] The first PUCCH may be an uplink control channel transmitted by the terminal device after receiving the first message. In some embodiments, the first PUCCH may be an uplink control channel that transmits message 3 or message 5 when the terminal device performs initial access.

[0086] The first PUCCH may carry feedback information corresponding to the first message. The feedback information may be HARQ feedback for the first message, or other information confirming whether the first message has been received. For example, after receiving Message 4, the terminal device may transmit a HARQ ACK for Message 4 via the first PUCCH. Also, for example, after receiving Message 2, the terminal device may transmit confirmation information related to RAR via the first PUCCH.

[0087] In some embodiments, the first PUCCH may further carry other random access related information, for example, the first PUCCH may carry information related to the RRC connection in message 5.

[0088] As can be seen from Figure 4, the network device in the embodiment of the present application can know through the first information whether the terminal device supports repeated transmission of the first PUCCH. If the first PUCCH carries message 5, the network side can know whether the terminal device has the ability to repeatedly transmit message 5. The terminal device can inform the network side of this information before the network side allocates retransmission resources, thereby avoiding the network side from having to wait and also avoiding the terminal device from re-initiating the random access process.

[0089] As described above, the first information may be associated with one or more pieces of information. By associating the information, the requirement of repeated transmission capability can be realized. The associated information may be the first preamble selected by the terminal device, the channel quality detected by the terminal device, the capability information of the terminal device recorded by the network device, or the port number for the terminal device to transmit a demodulation reference signal (DMRS).

[0090] In some embodiments, the first information may be associated with a first preamble selected by the terminal device. As described above, the network device may configure selectable preambles for the terminal device and notify the terminal device via broadcast information or RRC information. For example, the network device may transmit RACH-ConfigCommon via broadcast information to notify the terminal device of the preamble grouping.

[0091] The terminal device may transmit the selected preamble in message 1 of the random access process. In some embodiments, the terminal device may select a first preamble before step S410 of FIG. 4 and then transmit the first preamble. The first preamble is a preamble in a first preamble group configured by the network device, and the first preamble group can be used to indicate that the terminal device is capable of repeatedly transmitting the first PUCCH. That is, to enable the network device to grasp the capability information of the terminal device, the network device may introduce a new preamble set, i.e., a first preamble group, in the configuration of the preamble. If the terminal device selects a preamble in the first preamble group, it means that the terminal device supports repeated transmission of message 5.

[0092] The first preamble group may be determined based on one or more preambles transmitted by the network equipment. In some embodiments, the first preamble group may be determined based on a plurality of preambles corresponding to CBRA transmitted by the network equipment. In some embodiments, the first preamble group may be determined based on a plurality of preambles corresponding to CFRA transmitted by the network equipment. In some embodiments, the first preamble group may be determined based on a plurality of preambles transmitted by the network equipment other than the preambles corresponding to CBRA and CFRA. That is, the first preamble group may be determined based on other preambles in the preamble sequence structure.

[0093] For ease of understanding, several methods for determining the first preamble group will be described below with reference to the embodiments shown in Figures 5 and 6. The first preamble group in Figure 5 is determined based on a preamble used for CBRA. The first preamble group in Figure 6 is determined based on a preamble used for CFRA or other preambles.

[0094] 5, the network device divides the preambles used for CBRA into groups, CBRA group A, CBRA group B, and CBRA group C. Compared with FIG. 3, the added group C is the first preamble group mentioned above.

[0095] In some embodiments, Group A and Group B can maintain their original functionality, and Group C is added for terminal devices that support retransmission of random access messages, such as retransmission of Message 3 and Message 5. If the terminal device itself has retransmission capability, the terminal device selects a preamble in Group C when initiating random access, such as an R18 terminal device.

[0096] In some embodiments, when the multiple preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group can be determined based on preamble group B. In a possible implementation, group A can maintain the original function, and group C can be part of group B and is used for terminal devices that support retransmission of random access messages, such as retransmission of message 3 and message 5. If the terminal device itself has retransmission capability, it selects a preamble from group C, such as an R18 terminal device. In another possible implementation, group C can be group B, and the function of the original preamble group B is added with preamble selection that the terminal device has retransmission capability.

[0097] In some embodiments, if the multiple preambles corresponding to CBRA only include preamble group A and do not include preamble group B, the first preamble group can be determined based on preamble group A. For example, if group B does not exist, the system can directly separate the preambles used for CBRA into preamble group A and preamble group C. Preamble group C may be part of the original group A.

[0098] The terminal device can select a preamble in preamble group A, group B, or group C based on its own capability information. If the terminal device completes the exchange of message 1 / message 2 / message 3 in the random access process and the access fails, the preamble used by the terminal device when reattempting access should belong to the same preamble group as the preamble used for the first transmission. For example, if the terminal device selects a first preamble in group C and step S230 fails, the terminal device will again select a preamble in group C when re-initiating random access.

[0099] As mentioned above, the NTN system has a long delay. When the NTN system adopts the preamble structure shown in Figure 5, a situation may occur in which the preamble in Group C is insufficient. For example, if there are many R18 terminal devices accessing the NTN area, or if there are many terminal devices supporting retransmission of Message 3 and Message 5, Group C may become insufficient.

[0100] In a possible implementation, the network device can increase the number of preambles in group C by reducing the size of group A or group B the next time it transmits a preamble for selection through broadcast information. For example, if group B exists, some preambles in group B can be assigned to group C, that is, group B can be periodically reduced in size. Also, for example, if group B does not exist, preambles in group A can be transferred to group C under the assumption that group C is insufficient. Also, for example, a threshold value Target_preambleA for group A can be set, which represents the smallest number of preambles in group A in one cell.

[0101] As shown in FIG. 5, when the first preamble group is determined based on the preamble used for CBRA, the parameter corresponding to the first preamble group may be configured by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0102] 6, the network device may allocate some other preambles in the preamble set or some preambles used for CFRA as a first preamble group selected by the terminal device, which is also called a contention preamble random access (CPRA) group shown in FIG.

[0103] In some embodiments, the CPRA may be targeted to terminal devices that support retransmission of random access messages and terminal devices with higher levels of capability in subsequent evolutionary versions, such as the ability to retransmit messages 3 and 5. If the terminal device itself has retransmission capability, the terminal device may select the CPRA preamble when initiating random access, such as an R18 terminal device.

[0104] When the first preamble group is determined based on the preamble used for CFRA or another preamble, the parameters corresponding to the first preamble group may have various configuration manners. For example, the first preamble group may be configured individually, based on RACH-ConfigCommon carried by BWP-Common in the SIB, or based on RACH-ConfigDedicated.

[0105] In a possible implementation, the network device may configure the first preamble group by other parameters in the SIB, which may indicate the capability information of the terminal device.

[0106] In some embodiments, if the number of consecutive failures in random access by the terminal device selecting the first preamble is greater than a first threshold, the terminal device selects a preamble in another preamble group transmitted by the network device. The first threshold may be configured by the network device. For example, if random access of a preamble selected by the terminal device in group C fails n or more consecutive times, the terminal device selects a preamble in group A and abandons the selection of group C. For example, if random access of a preamble selected by the terminal device in CPRA fails n or more consecutive times, the terminal device may select a preamble in CBRA.

[0107] In some embodiments, when the network device allocates resource blocks (RBs) and modulation and coding schemes (MCSs) to the terminal device, the network device does not know the size of the data volume of message 3 or message 5 that the terminal device will next transmit. Allocating too many resources will result in wasted resources, and allocating too few resources will result in insufficient resources. Therefore, when the network device performs grouping processing on preambles according to FIG. 5 or FIG. 6, preambles in different groups can use different RB+MCS scheduling combinations. By selecting the required preambles, the terminal device provides a reference for the network device's scheduling.

[0108] The preamble structures shown in Figures 5 and 6 are used to select a preamble that can indicate the capabilities of the terminal device. That is, the first information may be determined based on the first preamble selected by the terminal device. The first information may further be associated with other information.

[0109] In some embodiments, the first information may be associated with a channel quality detected by the terminal device, which may be a channel quality detected by the terminal device in an initial access process, such as a reference signal received power (RSRP).

[0110] In a possible implementation, the network device can configure the terminal device with an RSRP threshold associated with the PUCCH repetition and a dedicated preamble resource in the broadcast information. The dedicated preamble resource may be the first preamble group in FIG. 5 or FIG. 6, or another designated dedicated resource. If the channel quality detected by the terminal device is lower than the first threshold, the terminal device can select the dedicated preamble resource, i.e., the second preamble. The second preamble can be used to request the network device to send the first indication information.

[0111] For example, if the RSRP detected by the terminal device during the initial access process is lower than a set value, the corresponding preamble is selected and transmitted. After detecting message 1 in the random access dedicated resource, the network device can specify in message 2 the number of times the terminal device is to repeatedly transmit message 5. The terminal device can repeatedly transmit message 5 within the specified uplink available time slot.

[0112] In some embodiments, the first information may be associated with capability information of the terminal device recorded by the network device. The capability information of the terminal device may include whether the terminal device has the capability to repeatedly transmit the first PUCCH. The network device can transmit the first indication information during random access other than the initial access based on the recorded capability information. That is, the capability to retransmit the first PUCCH is added to the capability information of the terminal device. In the initial access process, the terminal device cannot inform the network device of its own capability information, and therefore, in the transmission, the network device cannot allocate retransmission resources for the first PUCCH to it. However, after establishing a connection with the network device, the network device has already recorded the capability information of the terminal device. The network device can directly allocate retransmission resources for the first PUCCH in the next random access process.

[0113] In a possible implementation, the capability information of the terminal device can enhance the ability to retransmit the message 5. The network device can directly send first indication information when the terminal device performs a random access other than the initial random access, and the terminal device can start retransmitting the message 5 based on the first indication information.

[0114] In some embodiments, the first information may be associated with a port number for the terminal device to transmit the DMRS. When the network device schedules uplink resources, it may configure indication information for some DMRS port numbers through different formats of the DCI, or port numbers different from the default DMRS port number may have specific indication information. These DMRS port numbers may indicate that the terminal device has the capability to repeatedly transmit the first PUCCH. That is, the terminal device may inform the network device that it has the capability to support PUCCH retransmission through the port number for transmitting the DMRS.

[0115] In a possible implementation, when the terminal device supports retransmission of the PUCCH of the HARQ-ACK in message 4, it can select a corresponding DMRS port to transmit the DMRS. For example, if the first PUCCH carries message 5, the terminal device can report the associated capability by the port number of the DMRS in message 3 when transmitting message 3.

[0116] In another possible implementation manner, when the terminal device supports retransmission of the PUCCH for the HARQ-ACK of message 4, it can select a DMRS port different from that for message 3 to transmit the DMRS. This different DMRS port number can indicate that the terminal device has the ability to support repeated transmission of the first PUCCH. For example, if the DMRS port number used for message 3 is 0, the port number for the terminal device to transmit message 5 may be port number 1, which is different from this.

[0117] In some embodiments, the first information may be further associated with other information in message 3. The terminal device may report by message 3 that it has the capability to support PUCCH retransmission. In a possible implementation, the terminal device may indicate that it supports repeated transmission of the first PUCCH by a logical channel identifier (LCID) in message 3. For example, an R18 terminal device may indicate that it supports repeated transmission of the PUCCH of the HARQ-ACK for message 4 by an LCID code point within a reserved index value range. The reserved index value range of LCID is, for example, an LCID code point within the reserved range shown in Tables 6.2.1-2 of TS38.321. The above describes related information of the first information for determining the first indication information. The following describes the first indication information in detail.

[0118] In some embodiments, the first indication information may include or be used to determine the number of repetitions of the first PUCCH and resources for repeatedly transmitting the first PUCCH, i.e., the number of retransmissions and retransmission resources of the first PUCCH, and may be used to determine them. For example, the first indication information may directly include the number of repetitions of the first PUCCH and / or the retransmission resources. Also, for example, the first indication information may determine the number of repetitions of the first PUCCH and / or the retransmission resources.

[0119] The first indication information may indicate the number of retransmissions or the retransmission resources according to the information in message 2, or may configure the number of retransmissions and resources of the PUCCH for the terminal device in other ways.

[0120] The number of repeated transmissions of the first PUCCH is related to various factors. In some embodiments, when using common PUCCH resources, the number of repeated transmissions may be determined according to the size of the available resources. In some embodiments, to enable flexibility in NTN network configuration, the number of repeated transmissions of the first PUCCH may be determined according to the state of the satellite. The state of the satellite can determine whether the cell to which the terminal equipment requests access is a quasi-earth fixed cell or a quasi-earth mobile cell. For example, in the case of a quasi-earth mobile cell, the number of repeated transmissions can be reduced. In the case of a quasi-earth fixed cell, the number of repeated transmissions can be increased.

[0121] The number of repetitions of the first PUCCH can be indicated by one or more pieces of information. This information can directly indicate the number of retransmissions of the first PUCCH, or can be combined with configuration information to determine the number of retransmissions of the first PUCCH. This information can be a channel state information (CSI) request bit, an MCS index bit, or a transmit power control (TPC) command bit in the RAR uplink grant sent by the network device, a timing advance command (TAC) sent by the network device, a repetition factor configured by the network device through an SIB, a scenario in which the terminal device transmits message 3, a downlink assignment index (DAI) bit of the DCI sent by the network device, or a port number for the terminal device to transmit the DMRS.

[0122] In some embodiments, the MCS, transmit power control (TPC), and channel state information (CSI) request bits in the RAR uplink grant sent in message 2 are all reserved bits and can be used to indicate the number of retransmissions.

[0123] In a possible implementation, the network device can indicate the number of repetitions by the CSI request bit of the RAR uplink grant in the SIB. For example, when the CSI request bit is 1, it means that the number of repetitions is 4, and when the CSI request bit is 0, it is a reserved value and it may mean that the number of repetitions is 1 or there is no repetition. Also, for example, when the CSI request bit is 1, it may mean that the number of repetitions is 8, and when the CSI request bit is 0, it may mean that the number of repetitions is 1 or there is no repetition.

[0124] In a possible implementation, the network device may use two bits in the MCS index bits to represent different repetition counts, and may use the same count indication method as that for the repeated transmission of message 3. For message 3, the most significant two bits of the MCS information domain indicate the number of repeated transmissions of message 3, and the remaining bits of the MCS are used to indicate the MCS value. If the first PUCCH carries message 5, the terminal device may support a repetition indicator for message 3 to indicate the number of retransmissions of message 5.

[0125] In a possible implementation, the network device can identify the number of repetitions of the first PUCCH transmission by the command bit of the TPC field. If there is no repetition, the terminal device can interpret all bits of the TPC field of the RAR uplink grant as a TPC command. If repetition is indicated, the terminal device can interpret multiple bits of the TPC field. The TPC is represented by three bits, and each of the three bits can represent a different number of repetitions and a corresponding power value. The number of retransmissions of the first PUCCH may be directly or inversely proportional to the power value. For example, the larger the number of repetitions, the higher the transmission power.

[0126] For example, if the first PUCCH carries Message 5, the number of retransmissions of Message 5 may be related to the transmission power of Message 3. The terminal device can simultaneously determine the number of retransmissions and the TPC command by decoding the TPC command. The terminal device can transmit Message 3 based on the TPC command in the decoding result, and repeatedly transmit Message 5 based on the number of retransmissions.

[0127] For ease of understanding, Table 1 shows the meanings that the TPC field in the uplink grant can represent, taking the retransmission of message 5 as an example. As shown in Table 1, different TPC commands in the first column can respectively indicate different transmit powers for message 3 and different retransmissions of message 5. The third column indicates the number of retransmissions of message 5 or an index corresponding to the number of retransmissions. The index can indicate different numbers of retransmissions.

[0128] [Table 1]

[0129] Since the first PUCCH cannot ensure that the first retransmission is received correctly, the network device can further dynamically schedule the repeated transmission of the first PUCCH using DCI, and the dynamic scheduling may include the number of retransmissions and MCS level to improve the reception performance of the first PUCCH and improve uplink coverage.

[0130] In some embodiments, the network device may further indicate the number of retransmissions of the first PUCCH by 6 bits of the TAC in message 2. For example, a special bit in the 6 bits may indicate the number of retransmissions of message 5.

[0131] In some embodiments, the network device may configure a repetition factor associated with the first PUCCH through a SIB, for example, adding a repetition factor for PUCCH repetition transmission of the HARQ-ACK in message 4 to the SIB configuration information.

[0132] In a possible implementation, the repetition factor configured by the SIB may be one or more repetition factors. If only one repetition factor is configured by the SIB, a terminal device that supports PUCCH retransmission will perform repeated transmission using the repetition factor. The value of the repetition factor may be one of {1, 2, 4, 8}. If the repetition factor configured by the SIB is multiple, the PUCCH repetition of the terminal device can be dynamically determined by the network device. For example, the multiple repetition factors configured by the SIB may be {1, 2, 4, 8}. The repetition factor may also have other integer values. That is, if the repetition factor configured by the network device by the SIB includes multiple parameter values, the number of repeated transmissions of the first PUCCH can be dynamically adjusted according to the order of the multiple parameter values.

[0133] For example, the system can specify multiple repetition factors in a stepwise upgrade order from low to high. For example, if the multiple repetition factors are {1, 2, 4, 8}, and the first repetition factor specified is 1, after a failure, the next repetition factor specified will be 2.

[0134] In some embodiments, the number of repeated transmissions of the first PUCCH may be determined by a port number used by the terminal device to transmit the DMRS. As is clear from the above, the network device can configure indication information for different DMRS ports. The indication information may include the number of PUCCH retransmissions configured by the network device. That is, when the terminal device reports its capability according to the port number of the DMRS, the number of repeated transmissions of the first PUCCH is determined.

[0135] In some embodiments, the network device may indicate the number of repetitions of the first PUCCH transmission by a DAI bit of the DCI. The network device may indicate this by a reserved DAI bit, or may configure a previously used DAI bit to indicate the number of repetitions of the PUCCH transmission. These DAIs may be applied to different DCI formats. For example, the number of repetitions of the first PUCCH transmission may be indicated by a DAI bit of DCI format 1_0 transmitted by the network device.

[0136] In a possible implementation, the network equipment can use two reserved DAI bits of DCI format 1_0 scrambled by the TC-RNTI to indicate the number of PUCCH transmissions of the HARQ-ACK of message 4. For example, the network equipment can reuse the two reserved DAI bits in the PDCCH of message 4, which uses DCI format 1_0 scrambled by the TC-RNTI. The two bits make it possible to indicate one of four possible transmission amounts, for example, one of 1, 2, 4 and 8.

[0137] In some embodiments, the network device may determine different transmission times or whether retransmission is necessary based on different reasons for sending Message 3. As mentioned above, the content of Message 3 may vary depending on different states of the terminal devices and application scenarios. Message 3 includes one important piece of information, which is a unique identifier of each terminal device, which may be used for subsequent contention resolution. As the third message in the random access process, Message 3 is described below in different scenarios.

[0138] Scenario 1: Initial access is performed in the RRC_IDLE state by RRCSetupRequest. Scenario 2: Access is restored in the RRC_INACTIVE state by RRCRequest. Scenario 3: Reestablishing the RRC connection via RRCReestablishmentRequest; Scenario 4: Uplink desynchronization, uplink data arrival, and downlink data arrival (conflict), due to CRNTI; Scenario 5: Another SI request, via RRCSystemInfoRequest, Scenario 6: Handover (contention) with CRNTI+RRCReconfigurationComplete.

[0139] As a possible implementation, when the first PUCCH carries Message 5, the network device can determine whether Message 5 needs to be retransmitted based on different scenarios for transmitting Message 3. Table 2 is one possible implementation that indicates whether Message 5 needs to be retransmitted depending on the scenario for transmitting Message 3. However, Table 2 is merely an example and does not limit the scenarios, and the network device can set whether Message 5 needs to be retransmitted in other scenarios.

[0140] [Table 2]

[0141] As a possible implementation, in the NTN system, the network equipment can dynamically configure different retransmission factors based on different reasons for transmitting message 3. That is, the number of repetitions of the first PUCCH is dynamically adjusted according to the scenario in which the terminal equipment transmits message 3. For example, if message 3 is an initial access in the RRC_IDLE state, the number of repetitions of the first PUCCH is large.

[0142] The above describes the manner of determining and indicating the number of retransmissions of the first PUCCH in the embodiment of the present application, and the first indication information may further include a resource for repeatedly transmitting the first PUCCH. The determination of the retransmission resource in the embodiment of the present application will be specifically described below.

[0143] When it is determined to repeatedly transmit the first PUCCH, the retransmission resources may include common PUCCH resources and dedicated PUCCH resources of the terminal device. The common PUCCH resources usually belong to the PUCCH resources indicated in SIB1. In some embodiments, when the first PUCCH carries message 5, whether the retransmission resources use common resources or dedicated resources may be associated with the information carried by message 4 and may be related to the operation of the terminal device.

[0144] In a possible implementation, if message 4 does not carry RRC Setup but only contention resolution, then since the dedicated PUCCH resources of the terminal device are in RRC Setup, there may be no dedicated PUCCH resources when feeding back the ACK, and therefore only the PUCCH resources indicated in SIB1 can be used.

[0145] In a possible implementation, when RRC Setup and contention resolution are in the same PDSCH, the retransmission resource of the first PUCCH can be determined based on the operation of the terminal device. For example, if the terminal device calculates the PUCCH resource when receiving the DCI of message 4, it can only use the PUCCH resource indicated in SIB1. Also, for example, if the terminal device decides to feed back an ACK and determines the PUCCH resource at the timing scheduled one time slot earlier, the physical layer may have already obtained the PUCCH resource indicated in RRC Setup. Therefore, in this case, the repeated transmission of message 5 can be sent using the PUCCH resource dedicated to the terminal device.

[0146] The common PUCCH resources corresponding to the retransmission resources may be some resources in SIB1. In some embodiments, if there are no dedicated resources in the terminal device, the retransmission resources for the first PUCCH may be determined using one or more indices in a PUCCH resource set provided in the protocol. In a possible implementation, if there are no dedicated PUCCH resources in the terminal device, the common PUCCH resources may be resources corresponding to a first index range in the PUCCH resource set. The PUCCH resource set may be the PUCCH resource set before the dedicated PUCCH resources are allocated, as defined by the relevant protocol. For example, the first index range may be resources from index 10 onwards in the resource set. The first index range may be specified in SIB1.

[0147] The number of retransmissions and the retransmission resources included in the first indication information are determined based on the first information. In the case of a network device, whether it is a common PUCCH resource or a dedicated PUCCH resource, the number of retransmissions is determined based on the capability status of the terminal device, and then resources for repeatedly transmitting the ACK are allocated based on the number of repetitions and the resources.

[0148] Above, method embodiments of the present application have been described in detail with reference to Figures 2 to 6. Hereinafter, device embodiments of the present application will be described in detail with reference to Figures 7 to 9. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments, and therefore, parts not described in detail can be referred to the above method embodiments.

[0149] 7 is an exemplary block diagram of a wireless communication device according to one embodiment of the present application. The device may be any of the terminal devices described above. The device 700 shown in FIG. 7 includes a receiving unit 710 and a transmitting unit 720.

[0150] The receiving unit 710 may be used to receive a first message of a random access process; The transmitting unit 720 is used to repeatedly transmit a first PUCCH based on first indication information of the network equipment, the first PUCCH is used to carry feedback information corresponding to the first message, the first indication information is determined based on the first information, and the first information is used to indicate whether the terminal equipment has the ability to repeatedly transmit the first PUCCH.

[0151] Optionally, the first information is associated with one or more of the following information: a first preamble selected by the terminal device; a channel quality detected by the terminal device; capability information of the terminal device recorded by the network device; and a port number for the terminal device to transmit the DMRS.

[0152] Optionally, the device 700 further includes a selection unit for selecting a first preamble, where the first preamble is a preamble in a first preamble group configured by the network equipment, and the first preamble group is used to indicate that the terminal equipment has the ability to repeatedly transmit the first PUCCH, and the transmitting unit 720 is further used to transmit the first preamble.

[0153] Optionally, the first preamble group is determined based on one or more preambles from a plurality of preambles corresponding to CBRA transmitted by the network equipment, a plurality of preambles corresponding to CFRA transmitted by the network equipment, and a plurality of preambles other than the preambles corresponding to CBRA and CFRA transmitted by the network equipment.

[0154] Optionally, the first preamble group is determined based on a plurality of preambles corresponding to the CBRA, and if the plurality of preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined based on preamble group B, or if the plurality of preambles corresponding to the CBRA include preamble group A, the first preamble group is determined based on preamble group A.

[0155] For example, the parameter corresponding to the first preamble group is constituted by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0156] Optionally, the first preamble group is determined based on a plurality of preambles corresponding to CFRA, or a plurality of preambles other than the preambles corresponding to CBRA and CFRA, and the first preamble group is configured by one of a method of configuring the first preamble group individually, a method of configuring based on RACH-ConfigCommon, and a method of configuring based on RACH-ConfigDedicated.

[0157] Optionally, when the number of consecutive failures when the selection unit selects the first preamble to perform random access is greater than a first threshold, the selection unit is further used to select a preamble in another preamble group transmitted by the network device.

[0158] Optionally, the first information is associated with a channel quality detected by the terminal equipment, and the selection unit is further used to select a second preamble for requesting the network equipment to transmit the first indication information when the channel quality is lower than a first threshold.

[0159] Optionally, the capability information of the terminal device includes whether the terminal device has the capability to repeatedly transmit the first PUCCH, and the capability information is used by the network device to send the first indication information when the terminal device performs random access other than the initial random access.

[0160] Optionally, the first indication information is used to determine one or more pieces of information: the number of times to repeatedly transmit the first PUCCH; and resources for repeatedly transmitting the first PUCCH.

[0161] Optionally, the number of repetitions of the first PUCCH transmission is indicated by one or more pieces of information: a CSI request bit in the RAR uplink grant sent by the network equipment; an MCS index bit in the RAR uplink grant sent by the network equipment; a TPC command bit in the RAR uplink grant sent by the network equipment; a TAC sent by the network equipment; a repetition factor configured by the network equipment by the SIB; a scenario in which the terminal equipment transmits message 3; a DAI bit in DCI format 1_0 sent by the network equipment; and a port number for the terminal equipment to transmit the DMRS.

[0162] Optionally, the repetition factor configured by the network device through the SIB includes a plurality of parameter values, and the number of repetitions of the first PUCCH transmission is dynamically adjusted according to the order of the plurality of parameter values.

[0163] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted in ascending order of the values ​​of the plurality of parameters.

[0164] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted according to the scenario in which the terminal device transmits message 3.

[0165] Optionally, the resources for repeatedly transmitting the first PUCCH include common PUCCH resources, where the common PUCCH resources are resources corresponding to a first index range in the PUCCH resource set.

[0166] 8 is an exemplary block diagram of a wireless communication device according to another embodiment of the present application. The device may be any of the network devices described above. The device 800 shown in FIG. 8 includes a transmitting unit 810 and a receiving unit 820.

[0167] The sending unit 810 may be used to send a first message of a random access process; The receiving unit 820 may be used to receive a first PUCCH repeatedly transmitted by a terminal equipment based on first indication information of the network equipment, where the first PUCCH is used to carry feedback information corresponding to a first message, the first indication information is determined based on the first information, and the first information is used to indicate whether the terminal equipment has the ability to repeatedly transmit the first PUCCH.

[0168] Optionally, the first information is associated with one or more of the following information: a first preamble selected by the terminal device; a channel quality detected by the terminal device; capability information of the terminal device recorded by the network device; and a port number for the network device to transmit the DMRS.

[0169] Optionally, the receiving unit 820 is further used to receive a first preamble selected by the terminal equipment, where the first preamble is a preamble in a first preamble group configured by the network equipment, and the first preamble group is used to indicate that the terminal equipment has the ability to repeatedly transmit the first PUCCH.

[0170] Optionally, the first preamble group is determined based on one or more preambles from a plurality of preambles corresponding to CBRA transmitted by the network equipment, a plurality of preambles corresponding to CFRA transmitted by the network equipment, and a plurality of preambles other than the preambles corresponding to CBRA and CFRA transmitted by the network equipment.

[0171] Optionally, the first preamble group is determined based on a plurality of preambles corresponding to the CBRA, and if the plurality of preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined based on preamble group B, or if the plurality of preambles corresponding to the CBRA include preamble group A, the first preamble group is determined based on preamble group A.

[0172] For example, the parameter corresponding to the first preamble group is constituted by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0173] Optionally, the first preamble group is determined based on a plurality of preambles corresponding to CFRA, or a plurality of preambles other than the preambles corresponding to CBRA and CFRA, and the first preamble group is configured by one of a method of configuring the first preamble group individually, a method of configuring based on RACH-ConfigCommon, and a method of configuring based on RACH-ConfigDedicated.

[0174] Optionally, the first information is associated with the channel quality detected by the terminal equipment, and the receiving unit 820 is further used for the network equipment to receive a second preamble selected by the terminal equipment when the channel quality is lower than a first threshold, and the second preamble is used to request the network equipment to send the first indication information.

[0175] Optionally, the capability information of the terminal device includes whether the terminal device has the capability to repeatedly transmit the first PUCCH, and the capability information is used by the network device to send the first indication information when the terminal device performs random access other than the initial random access.

[0176] Optionally, the first indication information is used to determine one or more pieces of information: the number of times to repeatedly transmit the first PUCCH; and resources for repeatedly transmitting the first PUCCH.

[0177] Optionally, the number of repetitions of the first PUCCH transmission is indicated by one or more pieces of information: a CSI request bit in the RAR uplink grant sent by the network equipment; an MCS index bit in the RAR uplink grant sent by the network equipment; a TPC command bit in the RAR uplink grant sent by the network equipment; a TAC sent by the network equipment; a repetition factor configured by the network equipment by the SIB; a scenario in which the terminal equipment transmits message 3; a DAI bit in DCI format 1_0 sent by the network equipment; and a port number for the terminal equipment to transmit the DMRS.

[0178] Optionally, the repetition factor configured by the network device through the SIB includes a plurality of parameter values, and the number of repetitions of the first PUCCH transmission is dynamically adjusted according to the order of the plurality of parameter values.

[0179] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted in ascending order of the values ​​of the plurality of parameters.

[0180] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted according to the scenario in which the terminal device transmits message 3.

[0181] Optionally, the resources for repeatedly transmitting the first PUCCH include common PUCCH resources, where the common PUCCH resources are resources corresponding to a first index range in the PUCCH resource set.

[0182] 9 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dashed lines in FIG. 9 indicate that the units or modules are optional. The device 900 can be used to implement the methods described in the above method embodiments. The device 900 can be a chip, a terminal device, or a network device.

[0183] The device 900 may include one or more processors 910. The processor 910 can support the device 900 in implementing the methods described in the method embodiments above. The processor 910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

[0184] The apparatus 900 may further include one or more memories 920. The memories 920 may store programs that are executable by the processor 910 to cause the processor 910 to perform the methods described in the method embodiments above. The memory 920 may be separate from the processor 910 or may be integrated into the processor 910.

[0185] The device 900 may further include a transceiver 930. The processor 910 may communicate with other devices or chips via the transceiver 930. For example, the processor 910 may transmit and receive data to and from other devices or chips via the transceiver 930.

[0186] An embodiment of the present application further provides a computer-readable storage medium for storing a program, which can be applied to a terminal device or a network device according to the embodiment of the present application, and the program can cause a computer to execute the method performed by the terminal device or the network device according to each embodiment of the present application.

[0187] As will be appreciated, the computer-readable storage medium according to the embodiments of the present application may be any available medium that can be read by a computer, or a data storage device that integrates one or more available media, such as a server, a data center, etc. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital versatile disk (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0188] An embodiment of the present application further provides a computer program product, which includes a program that can be applied to a terminal device or a network device according to an embodiment of the present application, and causes a computer to execute a method performed by the terminal device or the network device according to each embodiment of the present application.

[0189] The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, all or in part may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded into and executed by a computer, the computer generates all or some of the procedures or functions described in the embodiments of the present application. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.).

[0190] The embodiments of the present application further provide a computer program, which is applicable to the terminal device or network device according to the embodiments of the present application, and causes a computer to execute the method executed by the terminal device or network device according to each embodiment of the present application.

[0191] In this application, the terms "system" and "network" may be used interchangeably. Furthermore, the terms used in this application are used only to interpret specific embodiments of the present application and are not intended to limit the present application. The terms "first," "second," "third," "fourth," etc. in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "include," "have," and any variations thereof are intended to cover a non-exclusive inclusion.

[0192] In the embodiments of the present application, the "indication" referred to may be a direct indication or an indirect indication, and may indicate an association relationship. For example, when A indicates B, it may mean that A directly indicates B, e.g., that B can be obtained by A, or that A indirectly indicates B, e.g., that A indicates C, e.g., that B can be obtained by C, and it may indicate an association relationship between A and B.

[0193] In the embodiments of the present application, the term "correspondence" may indicate a direct or indirect correspondence relationship between the two, or an association relationship between the two, such as a relationship of indicating and indicated, or a relationship of configuring and configured.

[0194] In an embodiment of the present application, "pre-configuration" may be realized by pre-storing corresponding code, form, or a format capable of instructing related information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation form.

[0195] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied to future communication systems, but the present application is not limited thereto.

[0196] In the embodiment of the present application, determining B depending on A does not mean determining B depending only on A, but may also determine B depending on A and / or other information.

[0197] In the examples of the present application, the term "and / or" simply describes the relationship between related objects and indicates that three types of relationships exist, for example, A and / or B includes three situations: only A exists, both A and B exist, and only B exists. In addition, in this specification, the symbol " / " generally indicates that the related objects before and after it have an "or" relationship.

[0198] In various embodiments of the present application, the order of the numbers of the above processes does not indicate the order of execution, and the order of execution of each process should be determined based on its function and inherent logic, and does not constitute any limitation on the implementation process of the embodiments of the present application.

[0199] It should be understood that in some embodiments of the present application, the disclosed systems, devices, and methods can be realized in other forms. For example, the device embodiments described above are merely exemplary, and the division of the units is merely one type of logical function division. In actual implementation, other division forms may be adopted, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be indirect couplings or communication connections via some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0200] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the means of this embodiment according to actual needs.

[0201] Furthermore, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

[0202] Although specific embodiments of the present application have been described above, the scope of protection of the present application is not limited thereto, and all modifications and substitutions that can be easily conceived by those skilled in the art without departing from the technical scope disclosed in the present application fall within the scope of protection of the present application. Therefore, the scope of protection of the present application should be in accordance with the scope of protection of the claims. [Explanation of symbols]

[0203] 100 Communication Systems 110 Network Equipment 120 Terminal Equipment 700 equipment 710 receiving unit 720 sending unit 800 equipment 810 Transmitting Unit 820 receiving unit 900 Device 910 Processor 920 memory 930 Transceiver

Claims

1. 1. A wireless communication method, comprising: receiving a first message of a random access procedure by a terminal device; The terminal device repeatedly transmits a first physical uplink control channel (PUCCH) according to first indication information of a network device, the first PUCCH being used to carry feedback information corresponding to the first message; The wireless communication method, characterized in that the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.

2. The first information is a first preamble selected by the terminal device; a channel quality detected by the terminal device; and capability information of the terminal device recorded by the network device; and a port number for transmitting a demodulation reference signal (DMRS) from the terminal device.

3. The first information is associated with the first preamble, and before the terminal device receives a first message of a random access procedure, the method includes: a step of the terminal device selecting a first preamble, the first preamble being a preamble in a first preamble group configured by the network device, the first preamble group being used to indicate that the terminal device has the capability to repeatedly transmit the first PUCCH; 3. The method of claim 2, further comprising the step of: the terminal device transmitting the first preamble.

4. The first preamble group a plurality of preambles corresponding to contention-based random access (CBRA) transmitted by the network equipment; a plurality of preambles corresponding to non-contention based random access (CFRA) transmitted by the network device; 4. The method of claim 3, wherein the determination is based on one or more preambles of a plurality of preambles other than a preamble corresponding to CBRA and a preamble corresponding to CFRA transmitted by the network equipment.

5. the first preamble group is determined based on a plurality of preambles corresponding to the CBRA; When the plurality of preambles corresponding to the CBRA include a preamble group A and a preamble group B, the first preamble group is determined based on the preamble group B; or The method of claim 4 , wherein when the plurality of preambles corresponding to the CBRA includes a preamble group A, the first preamble group is determined based on the preamble group A.

6. The method of claim 5, wherein the parameters corresponding to the first preamble group are configured as ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

7. The first preamble group is determined based on a plurality of preambles corresponding to the CFRA or a plurality of preambles other than the preambles corresponding to the CBRA and the CFRA, and the first preamble group is A method of individually configuring the first preamble group; A method of configuring based on RACH-ConfigCommon; 5. The method according to claim 4, wherein the method is configured by one of the following methods: a method for configuring based on RACH-ConfigDedicated;

8. The method according to any one of claims 3 to 7, further comprising the step of, when the number of consecutive failures in the terminal device selecting the first preamble to perform random access is greater than a first threshold, the terminal device selecting a preamble in another preamble group transmitted by the network device.

9. The first information is associated with a channel quality detected by the terminal device, and the method further comprises:

3. The method of claim 2, further comprising the step of: when the channel quality is lower than a first threshold, the terminal device selecting a second preamble for requesting the network device to transmit the first indication information.

10. The method of claim 2, wherein the capability information of the terminal device includes whether the terminal device has the capability to repeatedly transmit the first PUCCH, and the capability information is used by the network device to send the first indication information when the terminal device performs a random access other than an initial random access.

11. The first instruction information is The number of times the first PUCCH is repeatedly transmitted; The method according to any one of claims 1 to 10, characterized in that the method is used to determine one or more pieces of information including a resource for repeatedly transmitting the first PUCCH.

12. The number of times of repeated transmission of the first PUCCH is a channel state information (CSI) request bit in a random access response (RAR) uplink grant sent by the network device; a modulation and coding scheme (MCS) index bit in the RAR uplink grant transmitted by the network device; a transmit power control (TPC) command bit in a RAR uplink grant sent by the network device; a timing advance command (TAC) sent by the network device; and a repetition factor configured by the network device through a system information block (SIB); a scenario in which the terminal device sends message 3; A Downlink Allocation Index (DAI) bit of a Downlink Control Information (DCI) format 1_0 transmitted by the network device; and and a port number for the terminal device to transmit the DMRS.

13. 13. The method of claim 12, wherein the repetition factor configured by the network device through the SIB includes a plurality of parameter values, and the number of repetitions of the first PUCCH is dynamically adjusted according to the order of the plurality of parameter values.

14. The method of claim 13, wherein the number of repetitive transmissions of the first PUCCH is dynamically adjusted in ascending order of the parameter values.

15. The method of claim 12, wherein the number of repeated transmissions of the first PUCCH is dynamically adjusted according to a scenario in which the terminal device transmits message 3.

16. The method according to any one of claims 11 to 15, characterized in that the resources for repeatedly transmitting the first PUCCH include common PUCCH resources, and the common PUCCH resources are resources corresponding to a first index range in a PUCCH resource set.

17. 1. A wireless communication method, comprising: a network device sending a first message of a random access process; receiving, by the network device, a first physical uplink control channel (PUCCH) repeatedly transmitted by a terminal device based on first indication information of the network device, the first PUCCH being used to carry feedback information corresponding to the first message; The wireless communication method, characterized in that the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the capability to repeatedly transmit the first PUCCH.

18. The first information is a first preamble selected by the terminal device; a channel quality detected by the terminal device; and capability information of the terminal device recorded by the network device; and a port number for the terminal device to transmit the DMRS.

19. The first information is associated with the first preamble, and before the step of the network device transmitting a first message of a random access process, the method includes:

19. The method of claim 18, further comprising: a step of receiving, by the network device, a first preamble selected by the terminal device, the first preamble being a preamble in a first preamble group configured by the network device, the first preamble group being used to indicate that the terminal device has the capability to repeatedly transmit the first PUCCH.

20. The first preamble group a plurality of preambles corresponding to contention-based random access (CBRA) transmitted by the network equipment; a plurality of preambles corresponding to non-contention based random access (CFRA) transmitted by the network device; 20. The method of claim 19, wherein the determination is based on one or more preambles of a plurality of preambles other than a preamble corresponding to CBRA and a preamble corresponding to CFRA transmitted by the network equipment.

21. the first preamble group is determined based on a plurality of preambles corresponding to the CBRA; When the plurality of preambles corresponding to the CBRA include a preamble group A and a preamble group B, the first preamble group is determined based on the preamble group B; or The method of claim 20, wherein when the plurality of preambles corresponding to the CBRA includes a preamble group A, the first preamble group is determined based on the preamble group A.

22. The method of claim 21, wherein the parameters corresponding to the first preamble group are configured as ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

23. The first preamble group is determined based on a plurality of preambles corresponding to the CFRA or a plurality of preambles other than the preambles corresponding to the CBRA and the CFRA, and the first preamble group is A method of individually configuring the first preamble group; A method of configuring based on RACH-ConfigCommon; 21. The method of claim 20, wherein the method is configured by one of the following: a method for configuring based on RACH-ConfigDedicated;

24. The first information is associated with a channel quality detected by the terminal device, and the method further comprises:

20. The method of claim 18, further comprising the step of: when the channel quality is lower than a first threshold, the network device receiving a second preamble selected by the terminal device, the second preamble being used to request the network device to transmit the first indication information.

25. 19. The method of claim 18, wherein the capability information of the terminal device includes whether the terminal device has the capability to repeatedly transmit the first PUCCH, and the capability information is used by the network device to send the first indication information when the terminal device performs a random access other than an initial random access.

26. The first instruction information is The number of times the first PUCCH is repeatedly transmitted; The method according to any one of claims 17 to 25, characterized in that the method is used to determine one or more pieces of information including a resource for repeatedly transmitting the first PUCCH.

27. The number of times of repeated transmission of the first PUCCH is a channel state information (CSI) request bit in a random access response (RAR) uplink grant sent by the network device; a modulation and coding scheme (MCS) index bit in the RAR uplink grant transmitted by the network device; a transmit power control (TPC) command bit in a RAR uplink grant sent by the network device; a timing advance command (TAC) sent by the network device; and a repetition factor configured by the network device through a system information block (SIB); a scenario in which the terminal device sends message 3; A Downlink Allocation Index (DAI) bit of a Downlink Control Information (DCI) format 1_0 transmitted by the network device; and and a port number for the terminal device to transmit DMRS.

28. 28. The method of claim 27, wherein the repetition factor configured by the network device through the SIB includes a plurality of parameter values, and the number of repetitions of the first PUCCH is dynamically adjusted according to the order of the plurality of parameter values.

29. The method of claim 28, wherein the number of repetitive transmissions of the first PUCCH is dynamically adjusted in ascending order of the plurality of parameter values.

30. The method of claim 27, wherein the number of repeated transmissions of the first PUCCH is dynamically adjusted according to a scenario in which the terminal device transmits message 3.

31. The method according to any one of claims 26 to 30, wherein the resources for repeatedly transmitting the first PUCCH include common PUCCH resources, and the common PUCCH resources are resources corresponding to a first index range in a PUCCH resource set.

32. A wireless communication device, the device being a terminal device, the terminal device comprising: a receiving unit for receiving a first message of a random access process; a transmitting unit for repeatedly transmitting a first physical uplink control channel (PUCCH) according to first indication information of a network device, the first PUCCH being used to carry feedback information corresponding to the first message; The wireless communication device, characterized in that the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

33. A wireless communication device, the device being a network device, the network device comprising: a sending unit for sending a first message of a random access process; a receiving unit for receiving a first physical uplink control channel (PUCCH) repeatedly transmitted by a terminal device based on first indication information of the network device, the first PUCCH being used to carry feedback information corresponding to the first message; The wireless communication device, characterized in that the first indication information is determined based on first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

34. A communication device comprising a memory and a processor, the memory being used to store a program, and the processor being used to call the program in the memory and execute the method of any one of claims 1 to 31.

35. An apparatus, characterized in that it comprises a processor for calling a program from a memory to perform the method according to any one of claims 1 to 31.

36. A chip, comprising a processor for calling a program from a memory to cause a device in which said chip is installed to carry out the method of any one of claims 1 to 31.

37. A computer-readable storage medium having stored thereon a program for causing a computer to execute the method according to any one of claims 1 to 31.

38. A computer program product, characterized in that it comprises a program that causes a computer to carry out the method according to any one of claims 1 to 31.

39. A computer program, characterized in that it causes a computer to carry out the method according to any one of claims 1 to 31.

Citation Information

Patent Citations

  • Pucch repetition before RRC connection setup

    US20210100004A1