Wireless communication method and device

Abstract

The present application provides a method and apparatus for wireless communication. 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 terminal device receives a first message of a random access process; the terminal device repeatedly transmits a first PUCCH based on first indication information of the network device, where the first PUCCH is 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 ability to repeatedly transmit the first PUCCH.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and more specifically, to a method and apparatus for wireless communication. Background Art

[0002] Some communication systems, such as non-terrestrial networks (NTNs), have significant transmission delays. During random access in such systems, a terminal device can improve uplink coverage through repeated transmissions. For example, a terminal device can ensure the success rate of random access by repeatedly transmitting the physical uplink control channel (PUCCH) carrying Message 4 feedback information.

[0003] However, when the network device configures resources for repeated transmission of the PUCCH for the terminal device during the random access process, it may cause a waste of network resources. Summary of the Invention

[0004] The embodiments of the present application provide a method and apparatus for wireless communication. The following describes various aspects of the embodiments of the present application.

[0005] In a first aspect, a method for wireless communication is provided, the method comprising: a terminal device receives a first message of a random access process; the terminal device repeatedly sends a first PUCCH according to first indication information of a network device, and the first PUCCH is 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 ability to repeatedly transmit the first PUCCH.

[0006] In a second aspect, a method for wireless communication is provided, the method comprising: a network device sends a first message of a random access process; the network device receives a first PUCCH repeatedly sent by a terminal device according to 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 ability to repeatedly transmit the first PUCCH.

[0007] According to a third aspect, a device for wireless communication is provided, which is a terminal device, and the terminal device includes: a receiving unit for receiving a first message of a random access process; a sending unit for repeatedly transmitting a first PUCCH according to first indication information of a network device, and the first PUCCH is used to carry feedback information corresponding to the first message; wherein the first indication information is determined based on the first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

[0008] In a fourth aspect, a wireless communication device is provided, which is a network device, and the network device includes a sending unit for sending a first message of a random access process; a receiving unit for receiving a first PUCCH repeatedly sent by a terminal device according to first indication information of the network device, and the first PUCCH is used to carry feedback information corresponding to the first message; wherein the first indication information is determined according to the first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

[0009] In a fifth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method described in the first aspect or the second aspect.

[0010] In a sixth aspect, a device is provided, comprising a processor for calling a program from a memory to execute the method as described in the first aspect or the second aspect.

[0011] In a seventh aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect or the second aspect.

[0012] In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0013] In a ninth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0014] In a tenth aspect, a computer program is provided, which enables a computer to execute the method as described in the first aspect or the second aspect.

[0015] In the embodiment of the present application, the terminal device repeatedly transmits the first PUCCH according to the first indication information of the network device. The first indication information is related to whether the terminal device has the ability to repeatedly transmit the first PUCCH. Therefore, it can be seen that in the embodiment of the present application, the network device considers the capability information of the terminal device when determining the first indication information, which helps to reduce the waste of network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 The figure shows a wireless communication system applied in an embodiment of the present application.

[0017] Figure 2 The figure shows a flowchart of the random access process.

[0018] Figure 3 FIG. 4 is a schematic diagram showing the structure of the preamble in step S210 .

[0019] Figure 4 The figure shows a flow chart of a wireless communication method provided in an embodiment of the present application.

[0020] Figure 5 The figure shows a structural diagram of a possible implementation method of the preamble code in an embodiment of the present application.

[0021] Figure 6 Shown is a structural diagram of another possible implementation method of the preamble code in an embodiment of the present application.

[0022] Figure 7 Shown is a structural diagram of a wireless communication device provided in an embodiment of the present application.

[0023] Figure 8 Shown is a structural diagram of another wireless communication device provided in an embodiment of the present application.

[0024] Figure 9 Shown is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0026] The embodiments of the present application can be applied to various communication systems. For example, the embodiments of the present application can be applied to global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system on unlicensed spectrum, NR-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, NTN system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (WiFi), and fifth generation communication (5G) system. The embodiments of the present application may also be applied to other communication systems, such as future communication systems, such as sixth-generation (6G) mobile communication systems or satellite communication systems.

[0027] Traditional 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 communications, but also one or more other types of communications. For example, a communication system can support one or more of the following communications: device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, and vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to communication systems that support the above-mentioned communication methods.

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

[0029] The communication system in the embodiments of the present application can be applied to unlicensed spectrum. The unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in the embodiments of the present application can also be applied to licensed spectrum. The licensed spectrum can also be considered a dedicated spectrum.

[0030] The embodiments of the present application can be applied to terrestrial networks (TN) systems and NTN systems. As an example, the NTN system may include a 4G-based NTN system, an NR-based NTN system, an Internet of Things (IoT)-based NTN system, and a narrowband Internet of Things (NB-IoT)-based NTN system.

[0031] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber 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 device, etc.

[0032] In some embodiments, the terminal device may be a station (ST) in a WLAN. In 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., a NR system), or a terminal device in a future-evolved public land mobile network (PLMN) network.

[0033] In some embodiments, a terminal device may be a device that provides voice and / or data connectivity to a user. For example, the terminal device may be a handheld device, an in-vehicle device, etc. with wireless connection capabilities. As some specific examples, the terminal device may be a mobile phone, a tablet computer, a laptop computer, a PDA, 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.

[0034] In some embodiments, the terminal device can be deployed on land. For example, the terminal device can be deployed indoors or outdoors. In some embodiments, the terminal device can be deployed on the water, such as on a ship. In some embodiments, the terminal device can be deployed in the air, such as on an airplane, a balloon, or a satellite.

[0035] In addition to the terminal device, the communication system may also include one or more network devices. The network device in the embodiment of the present application may be a device for communicating with the terminal device, and the network device may also 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 embodiment of the present application may refer to a radio access network (RAN) node (or device) that connects the terminal device to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by network devices.

[0036] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

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

[0038] By way of example and not limitation, in embodiments of the present application, a network device may be mobile, for example, a mobile device. In some embodiments of the present application, the network device may be a satellite or balloon station. In some embodiments of the present application, the network device may also be a base station located on land, water, or the like.

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

[0040] For example, Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 1 As shown, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0041] Figure 1 A network device and two terminal devices are shown as an example. In some embodiments of the present application, the communication system 100 may include multiple network devices and the coverage area of each network device may include other numbers of terminal devices, which is not limited in the embodiments of the present application.

[0042] In the embodiments of this application, Figure 1 The wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this embodiment of the present application does not limit this.

[0043] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be called a communication device. Figure 1Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here; the communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0044] For ease of understanding, some relevant technical knowledge involved in the embodiments of this application is first introduced. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0045] With the development of mobile communication technology, coverage issues have gradually emerged and garnered widespread attention in the industry. Taking 5G network systems as an example, a comparison with 4G networks reveals two main reasons for these coverage issues. First, 5G systems operate at higher frequency bands than 4G. For example, 5G systems include the 3.5 GHz band in frequency range 1 (FR1) and the 26 GHz millimeter wave band in FR2. FR1 refers to the 5G sub-6 GHz band, and FR2 refers to the 5G millimeter wave band. Path loss in high-frequency bands is higher than in low-frequency bands. For example, the path loss at 3.5 GHz is 6-7 dB higher than at 1.8 GHz, and indoor coverage is 5-10 dB weaker. Second, 5G systems strive to provide higher user experience rates and cell-edge rates, placing higher demands on coverage performance. Therefore, 5G networks face greater coverage challenges than 4G networks, especially in both outdoor and indoor coverage scenarios.

[0046] Wireless communication systems usually use repeated transmission to enhance coverage performance. Repeated transmission is a very effective solution to improve signal transmission quality. Signal repetition can improve the detection and decoding performance of the receiver. For example, during the random access process of the NR system, the network device and the terminal device can resolve conflicts caused by multiple terminal devices in the cell sending the same preamble code at the same time by exchanging messages (message 3 and message 4). Among them, message 3 is sent by the terminal device to the network device through the uplink channel. The coverage performance of message 3 is poor compared to the coverage performance of other channels, which makes it difficult for terminal devices in areas with poor signal coverage quality to access the cell. Therefore, the NR system introduces a mechanism for repeated transmission of message 3 (multiple transmission) to improve the coverage performance of message 3. However, the entire random access process is completed after the user receives message 4 and sends a hybrid automatic repeat request (HARQ) feedback before starting the RRC connection. The coverage performance of HARQ feedback will also affect the success rate of random access of the terminal device.

[0047] The following combination Figure 2 The random access process is described in detail. In a wireless communication system, a terminal device can establish or restore a radio resource control (RRC) connection with a network device through a random access process.

[0048] There are two types of random access: contention based random access (CBRA) and contention free random access (CFRA). Figure 2 The main flow of the random access process is described.

[0049] Figure 2 The random access process shown includes steps S210 to S250, wherein steps S210 to S240 are a 4-step random access channel (RACH) process.

[0050] In step S210, the terminal device sends message 1 (message 1, MSG1) to the network device.

[0051] In 4-step RACH, a terminal device selects a RACH resource and a preamble and sends Message 1 to a network device on the selected resource. This RACH resource is also called a physical random access channel (PRACH) resource. Message 1 includes the preamble of the PRACH resource.

[0052] The network device may broadcast PRACH configuration information to the terminal device. The PRACH configuration information may include configuration information for the PRACH time-frequency resources and configuration information for the starting preamble root sequence. Based on the PRACH configuration information, the preamble or preamble set corresponding to the network device may be determined.

[0053] The network device can inform the terminal device of the available random access preamble in advance through system broadcast (such as initial access scenario) or RRC message (such as HO or SNAddition scenario). The preamble code can also be called a preamble sequence. These preamble codes support 4 types of long sequence preambles with a length of 839 and 9 types of short sequence preambles with a length of 139. The preamble code length is indicated by the high-level parameter prach-RootSequenceIndex. Under FR1, long sequences and short sequences with subcarrier spacing of 15KHz and 30KHz are supported. Under FR2, only short sequences with subcarrier spacing of 60KHz and 120KHz are supported. Each cell has 64 available preamble codes, and the terminal device can select one of them (or specified by the network device) to upload on PRACH.

[0054] For ease of understanding, the following Figure 3 The preamble code diagram shown is used for explanation. Figure 3 The figure shows the mapping group diagram of the preamble code when the configuration parameter SSB-perRACHOfRA-Occasion is less than or equal to 1. Figure 3 As shown in Figure 1, the 64 preambles can be divided into two parts: one part is the preambles indicated by totalNumberOfRA-Preambles for CBRA and CFRA, as well as higher capabilities / other requirements of the terminal equipment; the other part is the preambles other than totalNumberOfRA-Preambles, which are used for other purposes. If totalNumberOfRA-Preambles is not just a specific preamble number, then all 64 preambles are used for CBRA and CFRA.

[0055] Continue to see Figure 3, the CBRA preamble is divided into two groups, namely CBRA group A (group A) and CBRA group B (group B). CBRA group A is configured through totalNumberOfRA-PreambleGroupA. CBRA group B may not exist, and its parameters are configured by ssb-perRACH-OccasionAndCB-PreamblesPerSSB. For the configuration of CBRA parameters, the network device can send these configurations through RACH-ConfigCommon (BWP-Common in system information block 1 (SIB1)). For the configuration of CFRA parameters, the network device can configure the parameters through RACH-ConfigDedicated.

[0056] Terminal devices can select preambles based on certain policies. Because preambles are shared by multiple terminal devices, conflicts may arise when multiple terminal devices select the same preamble. To resolve these conflicts, network devices can use subsequent conflict resolution mechanisms.

[0057] Step S220: The network device sends message 2 (message 2, MSG2) to the terminal device.

[0058] Message 2 is also called a random access response (RAR). Message 2 can be carried via a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0059] After sending the preamble, the terminal device monitors the PDCCH within the RAR time window. By monitoring the PDCCH, the terminal device receives the RAR scheduled by the PDCCH, which is scrambled with the random access-radio network temporary identifier (RA-RNTI). The RA-RNTI is related to the time-frequency resources of the RACH used by the terminal device to send Message 1. After receiving the PDCCH, the terminal device can use the RA-RNTI to decode the PDCCH.

[0060] After the terminal device successfully receives the PDCCH, the terminal device can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH, wherein the PDSCH contains the RAR. The RAR can contain multiple information. For example, the subheader of the RAR can include a fallback indication for indicating the fallback time for retransmitting message 1; the random access preamble identifier in the RAR indicates the preamble index to which the network device responds; the payload in the RAR can include a timing advance group (TAG), which can be used to adjust the uplink timing; the RAR can also include an uplink grant (UL grant) for scheduling the uplink resource indication of message 3; the RAR can also include a temporary cell-radio network temporary identifier (TC-RNTI), and the terminal device that initially accesses can use the TC-RNTI to decode the PDCCH of message 4.

[0061] 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 it sent, the terminal device can determine that the RAR has been successfully received. After successfully receiving the RAR, the terminal device can stop monitoring the RAR and execute step S230 based on the authorization indication carried in the RAR.

[0062] If the terminal device does not receive the RAR within the random access response time window, or fails to verify the result, the response fails. In this case, if the terminal device's number of random access attempts is less than the upper limit (e.g., 10), the terminal device can continue to attempt random access. If the number of attempts is greater than the upper limit, the random access fails.

[0063] Step S230: The terminal device sends message 3 (MSG3) to the network device.

[0064] The terminal device may send message 3 on the uplink grant scheduled by the network device. Message 3 may also be referred to as an RRC connection establishment request message (RRC connection request).

[0065] After receiving the preamble in step S210, the network device configures the physical uplink shared channel (PUSCH) resources for Message 3 through a RAR message. Message 3 is then transmitted on the uplink shared channel (UL-SCH) using HARQ, scrambling the PDCCH with the TC-RNTI indicated by the RAR, and scheduling retransmissions of Message 3 using the downlink control information (DCI) format.

[0066] Message 3 contains a unique identifier (identity, ID) for each terminal device, which is used for contention resolution in step S240. Message 3 can be used to inform the network device what event triggered the random access process. In different scenarios, the message 3 sent by the terminal device will be different. For example, for the initial access scenario of RRC connection establishment, the terminal device can send an RRC connection establishment request through message 3. For another example, for the RRC connection reconstruction scenario, the terminal device can send an RRC reconstruction request message through message 3. For another example, for a cell handover (HO) scenario, if the terminal device accesses the target cell and there is no dedicated preamble during the handover process, contention-based random access can be triggered. The terminal device can send an RRC handover confirmation message and C-RNTI through message 3.

[0067] Step S240: The network device sends message 4 (MSG4) to the terminal device.

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

[0069] If the terminal device carries C-RNTI in message 3, such as in the RRC reconstruction process, message 4 is scheduled using the PDCCH scrambled by the C-RNTI. Accordingly, the terminal device can use the C-RNTI in message 3 to decode the PDCCH to obtain message 4. If the terminal device does not carry C-RNTI in message 3, such as in the initial access, message 4 can be scheduled using the PDCCH scrambled by TC-RNTI. Accordingly, the terminal device can use the TC-RNTI in message 2 to decode the PDCCH to obtain message 4.

[0070] When the terminal device successfully decodes the UE contention resolution identity MAC control element contained in message 4 and matches the UE contention resolution identity sent in message 3, the terminal device will consider the random access successful. The terminal device will set the TC-RNTI carried in the RAR to the C-RNTI, completing the four-step random access.

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

[0072] Message 5 may include HARQ ACK information for Message 4 and may also include information related to the RRC connection. Message 5 may be carried on the PUCCH. After sending Message 4 during the random access process, the terminal device will provide feedback via the PUCCH on whether Message 4 (Message 5) was received correctly.

[0073] Simply put, the terminal device selects one from the preamble pool as its temporary identifier and sends a random access request to the network device. In a cell, each preamble is associated with a preamble index. If the terminal device receives a RAR and contains the preamble index corresponding to the preamble selected by the terminal device, the terminal device believes that the network device has responded to its request. Before sending message 5, there are two interactions between the terminal device and the network device. The four messages are respectively called 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 failed. The RRC connection is started only after the terminal device receives message 4 and sends the HARQ feedback in message 5.

[0074] In the above random access process, the messages sent through the uplink channel are Message 1, Message 3, and Message 5. In some scenarios, the coverage performance of these uplink communications is poor. For example, in the initial access phase, the terminal device cannot perform complex channel measurements or beam training processes, and the coverage performance is worse than that of PDSCH or PUSCH in the connected state. Among them, Message 5 contains the ACK feedback of Message 4, and whether it is successfully sent is directly related to the establishment or re-establishment of the RRC connection. Therefore, in order to improve uplink coverage, PUCCH can be introduced to support repeated transmission of ACK feedback for Message 4.

[0075] Some communication systems have significant transmission delays, which can increase the overall random access process time. For these systems, the ultimate success of a terminal device accessing the system is a critical performance metric. For example, the round-trip time (RTT) of an NTN network is very long, and some satellite orbits are mobile, which can lead to lengthy message transmission times. Therefore, ensuring the success rate of random access is crucial.

[0076] To ensure the success rate of random access, data transmission coverage can be improved. For example, in an NTN network, the successful transmission of Message 4 determines whether a terminal device can access the NTN network. The ACK feedback for Message 4 (Message 5) is carried on the PUCCH. When accessing the NTN network, repeated PUCCH transmission can be used to increase the success rate of terminal devices accessing the NTN cell. In other words, by supporting repeated PUCCH transmission, the success rate of random access is guaranteed.

[0077] In the RRC connected state, the scheduling of PUCCH resources can be dynamically indicated to the terminal device by DCI. Each terminal device is configured with PUCCH resources and the number of PUCCH repetitions for each resource. Therefore, through the dynamic indication of PUCCH resources, the network device can indicate the number of repetitions in the same PUCCH to the terminal device. However, this resource scheduling mechanism is not available before the RRC configuration is established. However, the RRC connection is not started until the terminal device sends the ACK feedback of message 4. Therefore, it is necessary to introduce a mechanism for indicating the repetition of PUCCH ACK transmission before the RRC configuration is established.

[0078] However, PUCCH repetition is subject to the capabilities of the terminal device. During random access, the terminal device has not yet reported its capabilities to the network device, so the network device does not know whether the terminal device supports PUCCH repetition. This means that if the network device schedules repeated transmissions of Message 5 to a terminal device that does not support this feature, it will not only degrade PUCCH channel performance but also waste network resources.

[0079] Based on this, the embodiment of the present application proposes a wireless communication method. Through this method, the ability auxiliary information related to the terminal device's support for PUCCH repetition is introduced, and the network device can determine the number of PUCCH repetitions and resources based on this information, thereby optimizing its scheduling decision and system performance. Figure 4 The wireless communication method provided in the embodiment of the present application is described in detail.

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

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

[0082] A terminal device may perform random access in a variety of states. In some embodiments, the terminal device may perform initial access in the RRC idle state (RRC_IDLE). In some embodiments, the terminal device may perform recovery access in the RRC inactive state (RRC_INACTIVE).

[0083] The terminal device and the network device can be connected in various application scenarios. Various application scenarios include RRC connection reestablishment scenarios, other system information (SI) request scenarios, and handover scenarios. Various application scenarios can also include uplink desynchronization, uplink data arrival, and downlink data arrival scenarios.

[0084] See also Figure 4 In step S410, the network device sends a first message of a random access process to the terminal device. Correspondingly, the terminal device receives the first message.

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

[0086] The first message may be a message exchanged between the network device and the terminal device before the RRC connection is established or reestablished during the random access process. In some embodiments, the first message may be a message sent by the network device to the terminal device. Figure 2 Message 4 shown, can also be Figure 2Message 2 is shown. In some embodiments, the first message may be a RAR sent by the network device based on a non-contention based random access method.

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

[0088] 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 has the ability to repeatedly transmit the first PUCCH. In some embodiments, if the terminal device supports PUCCH repetition in the RRC non-connected state, the terminal device can inform the network side through the first information that it supports repeated transmission of message 5. For example, in the uplink transmission of the random access process, the terminal device can inform the network side through the first information or associated information of the first information whether it supports repeated transmission of PUCCH HARQ for message 4.

[0089] The network device can obtain the first information in a variety of ways, that is, the first information can be associated with a variety of information. Figure 5 and Figure 6 Give a detailed introduction.

[0090] Whether the terminal device has the ability to repeatedly transmit the first PUCCH may refer to whether the terminal device supports PUCCH repetition in the RRC non-connected state. In other words, when the network device cannot configure dedicated PUCCH resources for the terminal device through DCI, whether the terminal device can perform PUCCH repetition.

[0091] In some embodiments, if the first information indicates that the terminal device has the ability to repeatedly transmit the first PUCCH, the network device can schedule resources for repeated transmission for the terminal device to improve the success rate of random access by the terminal device. The resources for repeated transmission can also prevent the terminal device from initiating a random access procedure again due to a single failure to transmit Message 5. As a possible implementation method, 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.

[0092] In some embodiments, if the first information indicates that the terminal device does not have the capability, the network device will not allocate resources for repeated transmissions to the terminal device, nor will it wait for reception, thereby reducing resource waste. As one possible implementation, the first indication information of the network device may indicate the number of repeated transmissions as 1, and also indicate the resources for this single transmission. As another possible implementation, the network device may not send the first indication information.

[0093] 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 for sending message 3 or message 5 when the terminal device performs initial access.

[0094] The first PUCCH can carry feedback information corresponding to the first message. The feedback information can 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 can send a HARQ ACK for message 4 via the first PUCCH. For another example, after receiving message 2, the terminal device can send confirmation information related to RAR via the first PUCCH.

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

[0096] Depend on Figure 4 It can be seen that the network device in the embodiment of the present application can know whether the terminal device supports repeated transmission of the first PUCCH through the first information. When the first PUCCH carries Message 5, the network side can know whether the terminal device has the ability to repeat message 5. By informing the network side of this information before the network side allocates retransmission resources, the terminal device can avoid the network side waiting and can also avoid the terminal device initiating a random access process again.

[0097] As mentioned above, the first information can be associated with one or more types of information. By associating the information, a request for repeated transmission capability can be implemented. This associated information can 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 of the terminal device sending the demodulation reference signal (DMRS).

[0098] 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 a selectable preamble for the terminal device and notify the terminal device of the preamble via a broadcast message or an RRC message. For example, the network device may send a RACH-ConfigCommon broadcast message to notify the terminal device of the preamble packet.

[0099] The terminal device may send the selected preamble in message 1 of the random access procedure. In some embodiments, the terminal device may Figure 4Before step S410, the first preamble is selected and then sent. The first preamble is a preamble in the first preamble group configured by the network device. The first preamble group can be used to indicate that the terminal device has the ability to repeatedly transmit the first PUCCH. In other words, in order to allow the network device to know the capability information of the terminal device, the network device can introduce a new preamble set, that is, the first preamble group, in the preamble configuration. If the terminal device selects a preamble in the first preamble group, it indicates that the terminal device supports repeated transmission of message 5.

[0100] The first preamble group can be determined based on one or more preambles sent by the network device. In some embodiments, the first preamble group can be determined based on multiple preambles corresponding to CBRA sent by the network device. In some embodiments, the first preamble group can be determined based on multiple preambles corresponding to CFRA sent by the network device. In some embodiments, the first preamble group can be determined based on multiple preambles sent by the network device other than preambles corresponding to CBRA and CFRA. In other words, the first preamble group can be determined based on other preambles in the preamble sequence structure.

[0101] For ease of understanding, the following Figure 5 and Figure 6 The illustrated embodiment describes several ways of determining the first preamble code group. Figure 5 The first preamble group is determined according to the preamble used by CBRA. Figure 6 The first preamble group is determined according to CFRA or other preambles.

[0102] See also Figure 5 , the network device groups the multiple preambles used by CBRA into CBRA group A, CBRA group B and CBRA group C (group C). Figure 3 In comparison, the added group C is the first preamble code group mentioned above.

[0103] In some embodiments, Group A and Group B can maintain their original functions, and Group C is added for terminal devices that support random access message retransmission, such as retransmission of Message 3 and Message 5. If the terminal device itself has the retransmission capability, it will select the preamble code in Group C when initiating random access, such as R18 terminal devices.

[0104] In some embodiments, if the multiple preambles corresponding to CBRA include preamble group A and preamble group B, the first preamble group can be determined based on preamble group B. As one possible implementation, group A can retain its original functionality, and group C can be a portion of group B, used by terminal devices supporting random access message retransmission, such as retransmission of messages 3 and 5. If the terminal device itself has retransmission capabilities, it will select the preamble of group C, such as R18 terminal devices. As another possible implementation, group C can be the same as group B, that is, the functionality of the original preamble group B is added with a preamble selection for terminal devices with retransmission capabilities.

[0105] In some embodiments, if the multiple preambles corresponding to the CBRA include only 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 divide the preambles used by the CBRA into preamble group A and preamble group C. Preamble group C can also be part of the original group A.

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

[0107] As mentioned above, the delay of NTN system is long. Figure 5 When using the preamble structure shown in the figure, there may be a situation where the preambles in group C are insufficient. For example, if more and more R18 terminal devices are connected to the NTN area, or more and more terminal devices support the retransmission of messages 3 and 5, group C may not be sufficient.

[0108] As a possible implementation, the next time the network device broadcasts a preamble for selection, it can increase the number of preambles in group C by reducing the size of group A or group B. For example, if group B exists, some preambles in group B can be allocated to group C, that is, group B can be periodically reduced. For another example, if group B does not exist, preambles in group A can be transferred to group C if group C is insufficient. For another example, a threshold value Target_preambleA for group A can be set to indicate the minimum number of preambles in group A in a cell.

[0109] like Figure 5As shown, when the first preamble group is determined according to the preamble used by CBRA, the parameters corresponding to the first preamble group can be configured through ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0110] See also Figure 6 , the network device can occupy a portion of other (others) preambles in the preamble set, or a portion of the preambles used by CFRA, as the first preamble group selected by the terminal device. The first preamble group can also be called Figure 6 The contention preamble random access (CPRA) shown in FIG.

[0111] In some embodiments, CPRA can be targeted at terminal devices that support random access message retransmission and terminal devices with more advanced capabilities in subsequent evolution versions, such as the retransmission capability of message 3 and message 5. If the terminal device itself has retransmission capability, the terminal device can select the CPRA preamble when initiating random access, such as R18 terminal devices.

[0112] When the first preamble group is determined based on the preamble used by CFRA or other preambles, the parameters corresponding to the first preamble group can be configured in multiple ways. For example, the first preamble group can be configured individually, or can be configured based on RACH-ConfigCommon carried by BWP-Common in the SIB, or can be configured based on RACH-ConfigDedicated.

[0113] As a possible implementation method, when the network device configures the first preamble code group that can indicate the terminal device capability information, it can also be configured through other parameters in the SIB.

[0114] In some embodiments, if the number of consecutive failures of a terminal device to select a first preamble for random access exceeds a first threshold, the terminal device selects a preamble from another preamble group sent by the network device. The first threshold can be configured by the network device. For example, if a terminal device fails to select a preamble from group C for more than n consecutive times, the terminal device selects a preamble from group A and abandons the selection of group C. For example, if a terminal device fails to select a preamble from CPRA for more than n consecutive times, the terminal device may select a preamble from CBRA.

[0115] In some embodiments, when the network device allocates resource blocks (RBs) and modulation and coding schemes (MCSs) to the terminal device, it does not know the size of the data of the message 3 or message 5 that the terminal device will send next. If too much is allocated, resources will be wasted; if too little is allocated, resources will be insufficient. Figure 5 or Figure 6 When grouping preambles, different groups of preambles can use different RB+MCS scheduling combinations. The terminal device provides a reference for the network device's scheduling by selecting the required preamble.

[0116] Figure 5 and Figure 6 The preamble structure shown is used by the terminal device to select a preamble that can indicate its capabilities. In other words, the first information can be determined based on the first preamble selected by the terminal device. The first information can also be associated with other information.

[0117] In some embodiments, the first information may be associated with a channel quality detected by the terminal device. The channel quality detected by the terminal device may be a channel quality detected by the terminal device during an initial access process. The channel quality may be, for example, a reference signal received power (RSRP).

[0118] As a possible implementation, the network device can configure the RSRP threshold related to PUCCH repetition and the dedicated preamble resource for the terminal device in the broadcast information. The dedicated preamble resource can be Figure 5 or Figure 6 The first preamble group in the packet may also be other designated dedicated resources. If the channel quality detected by the terminal device is lower than the first threshold, the terminal device may select a dedicated preamble resource, that is, a second preamble. The second preamble may be used to request the network device to send the first indication information.

[0119] For example, if the RSRP detected by the terminal device during initial access is lower than a set value, it will select and send the corresponding preamble. After detecting Message 1 in the random access dedicated resource, the network device can specify the number of repetitions of Message 5 of the terminal device in Message 2. The terminal device can repeatedly transmit Message 5 in the indicated uplink available time slots.

[0120] In some embodiments, the first information may be associated with the 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 may send the first indication information during random access other than 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. During the initial access process, the terminal device cannot inform the network device of its own capability information, so the network device cannot allocate retransmission resources for the first PUCCH for it during the transmission. However, after establishing contact with the network device, the capability information of the terminal device has been recorded in the network device. The network device can directly allocate retransmission resources for the first PUCCH during the next random access process.

[0121] As a possible implementation, the capability information of the terminal device can be increased to enable retransmission of message 5. The network device can directly send first indication information when the terminal device performs random access other than initial random access. The terminal device can initiate retransmission of message 5 based on the first indication information.

[0122] In some embodiments, the first information may be associated with the port number of the terminal device that transmits 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 a port number different from the default DMRS port number may have specific indication information. These DMRS port numbers may indicate that the terminal device has the ability to repeatedly transmit the first PUCCH. In other words, the terminal device may inform the network device of its ability to support PUCCH retransmission by sending the DMRS port number.

[0123] As a possible implementation, when the terminal device supports PUCCH retransmission of HARQ-ACK of message 4, it can select the corresponding DMRS port to send DMRS. For example, when the first PUCCH carries message 5, the terminal device can report the relevant capabilities through the DMRS port number in message 3 when sending message 3.

[0124] As another possible implementation, when the terminal device supports PUCCH retransmission of the HARQ-ACK in Message 4, it can select a different DMRS port number than that used in Message 3 to send 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, when the DMRS port number used in Message 3 is 0, the port number used by the terminal device to send Message 5 can be a different port number 1.

[0125] In some embodiments, the first information may also be associated with other information in message 3. The terminal device may report through message 3 that it has the ability to support PUCCH retransmission. As a possible implementation method, the terminal device may indicate that it supports repeated transmission of the first PUCCH through a logical channel identifier (LCID) in message 3. For example, an R18 terminal device may indicate that it supports repeated transmission of PUCCH for HARQ-ACK regarding message 4 through an LCID code point within a reserved index value range. The index value range for which LCID is reserved is, for example, an LCID code point within a reserved range indicated in Table 6.2.1-2 in TS38.321. The above introduces the associated information of the first information used to determine the first indication information, and the first indication information is introduced in detail below.

[0126] In some embodiments, the first indication information may include or be used to determine the number of repeated transmissions of the first PUCCH and the resources used to repeatedly transmit the first PUCCH, that is, the number of retransmissions of the first PUCCH and the retransmission resources. For example, the first indication information may directly include the number of repeated transmissions of the first PUCCH and / or the retransmission resources. For another example, the first indication information may determine the number of repeated transmissions of the first PUCCH and / or the retransmission resources.

[0127] The first indication information may indicate the number of retransmissions or retransmission resources through the information in message 2, or may configure the number of retransmissions and resources of the PUCCH to the terminal device through other methods.

[0128] The number of repetitions for the first PUCCH can be related to various factors. In some embodiments, when using common PUCCH resources, the number of repetitions can be determined based on the available resources. In some embodiments, to allow for flexibility in NTN network configuration, the number of repetitions for the first PUCCH can be determined based on the satellite status. The satellite status can determine whether the cell a terminal device requests access to is a quasi-Earth fixed cell or a quasi-Earth mobile cell. For example, for a quasi-Earth mobile cell, the number of repetitions can be reduced. For a quasi-Earth fixed cell, the number of repetitions can be increased.

[0129] The number of repeated transmissions of the first PUCCH can be indicated by one or more types 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 authorization sent by the network device, or a timing advance command (TAC) sent by the network device, or a repetition factor configured by the network device through the SIB, or a scenario in which the terminal device sends message 3, or a downlink assignment index (DAI) bit of the DCI sent by the network device, or a port number for the terminal device to send DMRS.

[0130] 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 reserved bits and can be used to indicate the number of retransmissions.

[0131] As a possible implementation, the network device can indicate the number of repetition mappings through the CSI request bit of the RAR uplink grant in the SIB. For example, when the CSI request bit = 1, it can indicate that the number of repetitions is 4, while when the CSI request bit = 0, it is a reserved value, indicating that the number of repetitions is 1 or no repetition. For another example, when the CSI request bit = 1, it can mean that the number of repetitions is 8, while when the CSI request bit = 0, it means that the number of repetitions is 1 or no repetition.

[0132] As a possible implementation, the network device can use two bits in the MCS index bit to indicate different repetition times, or use the same number indication method as the repeated transmission of message 3. For message 3, the highest two bits of the MCS information field indicate the number of repeated transmissions of message 3, and the remaining bits of the MCS are used to indicate the MCS value. When the first PUCCH carries message 5, the terminal device supports the identification of message 3 repetitions, which can also represent the number of retransmissions of message 5.

[0133] As a possible implementation method, the network device can identify the number of times the first PUCCH is repeatedly transmitted through 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 TPC commands. If repetition is indicated, the terminal device can interpret multiple bits of the TPC field. TPC is represented by 3 bits, and each 3-bit bit can represent a different number of repetitions and corresponding power values. The number of retransmissions of the first PUCCH can be proportional or inversely proportional to the power value. For example, the higher the number of repetitions, the greater the transmit power.

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

[0135] For ease of understanding, Table 1 uses the retransmission of Message 5 as an example to illustrate the meaning of the TPC field in an uplink grant. As shown in Table 1, the different TPC commands in the first column indicate different Message 3 transmit powers and Message 5 retransmission counts. The third column indicates the number of Message 5 retransmissions or the index corresponding to the retransmission count. This index can indicate different retransmission counts.

[0136] Table 1

[0137]

[0138] Since the first PUCCH cannot guarantee that the initial retransmission is correctly received, the network device can also dynamically schedule the repeated transmission of the first PUCCH through DCI. The dynamic scheduling can include the number of retransmissions and the MCS level to increase the reception performance of the first PUCCH and improve the uplink coverage.

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

[0140] In some embodiments, the network device may configure a repetition factor related to the first PUCCH through the SIB. For example, the repetition factor for the PUCCH retransmission of the HARQ-ACK of message 4 may be added to the SIB configuration information.

[0141] As a possible implementation method, the repetition factor configured by the SIB may be one or more repetition factors. If only one repetition factor is configured through the SIB, the terminal device that supports PUCCH retransmission uses the repetition factor to perform repeated transmission. The value of the repetition factor may be one of {1, 2, 4, 8}. If the SIB configures multiple repetition factors, the PUCCH repetition of the terminal device may be dynamically determined by the network device. For example, the multiple repetition factors configured by the SIB may be {1, 2, 4, 8}. Among them, the repetition factor may also be other integer values. That is to say, when the repetition factor configured by the network device through the SIB includes multiple parameter values, the number of repeated transmissions of the first PUCCH may be dynamically adjusted according to the order of the multiple parameter values.

[0142] For example, the system can indicate multiple repetition factors in a sequential order of increasing from low to high. For example, if the repetition factors are {1, 2, 4, 8}, if the first indication of repetition factor is 1 and it fails, the next indication of repetition factor is 2.

[0143] In some embodiments, the number of repetitions of the first PUCCH can also be determined by the port number of the terminal device sending the DMRS. As previously mentioned, the network device can be configured with indication information for different DMRS ports. This indication information can also include the number of PUCCH retransmissions configured by the network device. In other words, when the terminal device reports its capabilities using the DMRS port number, it also determines the number of repetitions of the first PUCCH.

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

[0145] As a possible implementation, the network device may use the two reserved DAI bits of DCI format 1_0 scrambled by TC-RNTI to indicate the number of transmissions of the PUCCH for HARQ-ACK of message 4. For example, the network device may reuse the two reserved DAI bits in the PDCCH of message 4, which uses DCI format 1_0 scrambled by TC-RNTI. These two bits allow one of four possible transmission numbers to be indicated, such as one of 1, 2, 4, and 8.

[0146] In some embodiments, the network device may determine the number of transmissions or whether retransmission is required based on the different reasons for sending Message 3. As mentioned above, the content of Message 3 may be different depending on the different states of the terminal device and the different application scenarios. Message 3 will contain an important piece of information, which is the unique identifier of each terminal device, which can be used for subsequent conflict resolution. Message 3, as the third message of the random access process, is described in different scenarios as follows:

[0147] Scenario 1: Initial access in RRC_IDLE state, through RRCSetupRequest;

[0148] Scenario 2: Recover access in RRC_INACTIVE state via RRCRequest;

[0149] Scenario 3: RRC connection reestablishment, via RRCReestablishmentRequest;

[0150] Scenario 4: Uplink synchronization is lost, uplink data arrives, downlink data arrives (contention), and passes CRNTI;

[0151] Scenario 5: Other SI requests, via RRCSystemInfoRequest;

[0152] Scenario 6: Handover (contention), through CRNTI+RRCReconfigurationComplete.

[0153] 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 the different transmission scenarios of Message 3. Table 2 shows a possible implementation of indicating whether Message 5 needs to be retransmitted based on the transmission scenario of Message 3. It should be noted that Table 2 is only an example and does not limit the scenarios. The network device can also determine whether Message 5 needs to be retransmitted in other scenarios.

[0154] Table 2

[0155]

[0156] As a possible implementation, in the NTN system, network devices can dynamically configure different retransmission factors based on the different reasons for sending Message 3. In other words, the number of retransmissions of the first PUCCH can be dynamically adjusted based on the scenario in which the terminal device sends Message 3. For example, when Message 3 is an initial access in the RRC_IDLE state, the number of retransmissions of the first PUCCH can be higher.

[0157] The above describes the determination and indication method of the number of retransmissions of the first PUCCH in the embodiment of the present application. The first indication information may also include resources for repeated transmission of the first PUCCH. The determination of the retransmission resources in the embodiment of the present application is described in detail below.

[0158] When the first PUCCH determines that it needs to be retransmitted, the retransmission resources may include public PUCCH resources and dedicated PUCCH resources for the terminal device. Public PUCCH resources typically belong to the PUCCH resources indicated in SIB1. In some embodiments, when the first PUCCH carries Message 5, whether the retransmission resources use public resources or dedicated resources may be related to the information carried in Message 4 or the behavior of the terminal device.

[0159] As a possible implementation method, if Message 4 does not carry RRCSetup but only carries contention resolution, since the dedicated PUCCH resources of the terminal device are in RRCSetup, there may be no dedicated PUCCH resources when ACK is fed back, so only the PUCCH resources indicated in SIB1 can be used.

[0160] As a possible implementation method, if RRC Setup and conflict resolution are in the same PDSCH, the retransmission resources of the first PUCCH can be determined based on the behavior of the terminal device. For example, if the terminal device has calculated the PUCCH resources when receiving the DCI of message 4, only the PUCCH resources indicated in SIB1 can be used at this time. For another example, if the terminal device determines that it wants to feedback ACK and determines the PUCCH resources only one time slot in advance, for the physical layer, the PUCCH resources indicated in the RRC Setup may have been obtained. Therefore, the exclusive PUCCH resources of the terminal device can be used to send repeated transmissions of message 5.

[0161] The public PUCCH resources corresponding to the retransmission resources may be part of the resources in SIB1. In some embodiments, when the terminal device does not have dedicated resources, the retransmission resources of the first PUCCH may be determined using one or more indexes in the PUCCH resource set given in the protocol. As a possible implementation method, if the terminal device does not have dedicated PUCCH resources, the public PUCCH resources may be the resources corresponding to the first index range in the PUCCH resource set. The PUCCH resource set may be the PUCCH resource set specified by the relevant protocol before the allocation of dedicated PUCCH resources. For example, the first index range may be the resources after index 10 in the resource set. The first index range may be specified in SIB1.

[0162] The number of retransmissions and the retransmission resources included in the first indication information are determined based on the first information. For the network device, whether it is a public PUCCH resource or a dedicated PUCCH resource, the number of retransmissions is determined based on the capabilities of the terminal device, and then the resources for ACK retransmission are allocated based on the number of retransmissions and the resources.

[0163] Combined with the above Figures 2 to 6 , describes the method embodiment of the present application in detail. Figures 7 to 9 , the device embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so that parts not described in detail can be referred to the previous method embodiment.

[0164] Figure 7 This is a schematic block diagram of a wireless communication device according to an embodiment of the present application. The device may be any terminal device described above. Figure 7 The illustrated apparatus 700 includes a receiving unit 710 and a sending unit 720 .

[0165] The receiving unit 710 may be configured to receive a first message of a random access procedure;

[0166] The sending unit 720 can be used to repeatedly send the first PUCCH according to the first indication information of the network device, and the first PUCCH is used to carry feedback information corresponding to the first message; wherein, the first indication information is determined according to the first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

[0167] Optionally, the first information is associated with one or more of the following information: a first preamble code 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 send DMRS.

[0168] Optionally, the device 700 also includes a selection unit, which can be used to select a first preamble code, where the first preamble code is a preamble code in a first preamble code group configured by the network device, and the first preamble code group is used to indicate that the terminal device has the ability to repeatedly transmit the first PUCCH; the sending unit 720 is also used to send the first preamble code.

[0169] Optionally, the first preamble group is determined based on one or more of the following preambles: multiple preambles corresponding to CBRA sent by the network device; multiple preambles corresponding to CFRA sent by the network device; and multiple preambles sent by the network device except the preambles corresponding to CBRA and CFRA.

[0170] Optionally, the first preamble group is determined according to multiple preambles corresponding to the CBRA; if the multiple preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined according to preamble group B; or, if the multiple preambles corresponding to the CBRA include preamble group A, the first preamble group is determined according to preamble group A.

[0171] For example, the parameters corresponding to the first preamble group are configured through ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0172] Optionally, the first preamble code group is determined according to multiple preamble codes corresponding to CFRA or multiple preamble codes other than the preamble codes corresponding to CBRA and CFRA, and the first preamble code group is configured in one of the following ways: configuring the first preamble code group separately; configuring according to RACH-ConfigCommon; and configuring according to RACH-ConfigDedicated.

[0173] Optionally, if the number of consecutive failures of the selection unit in selecting the first preamble code for random access is greater than a first threshold, the selection unit is further configured to select a preamble code from another preamble code group sent by the network device.

[0174] Optionally, the first information is associated with the channel quality detected by the terminal device, and the selection unit is further used to select a second preamble code if the channel quality is lower than a first threshold, and the second preamble code is used to request the network device 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 a random access other than the initial random access.

[0176] Optionally, the first indication information is used to determine one or more of the following information: the number of repeated transmissions of the first PUCCH; and resources used for repeated transmission of the first PUCCH.

[0177] Optionally, the number of repeated transmissions of the first PUCCH is indicated by one or more of the following information: the CSI request bit in the RAR uplink grant sent by the network device; the MCS index bit in the RAR uplink grant sent by the network device; the TPC command bit in the RAR uplink grant sent by the network device; the TAC sent by the network device; the repetition factor configured by the network device through the SIB; the scenario in which the terminal device sends message 3; the DAI bit of the DCI format 1_0 sent by the network device; and the port number for the terminal device to send DMRS.

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

[0179] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted according to a plurality of parameter values in an ascending order.

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

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

[0182] Figure 8 This is a schematic 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. Figure 8 The illustrated apparatus 800 includes a sending unit 810 and a receiving unit 820 .

[0183] The sending unit 810 may be configured to send a first message of a random access procedure;

[0184] The receiving unit 820 can be used to receive the first PUCCH repeatedly sent by the terminal device according to the first indication information of the network device, and the first PUCCH is used to carry feedback information corresponding to the first message; wherein, the first indication information is determined according to the first information, and the first information is used to indicate whether the terminal device has the ability to repeatedly transmit the first PUCCH.

[0185] Optionally, the first information is associated with one or more of the following information: a first preamble code selected by the terminal device; 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 send DMRS.

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

[0187] Optionally, the first preamble group is determined based on one or more of the following preambles: multiple preambles corresponding to CBRA sent by the network device; multiple preambles corresponding to CFRA sent by the network device; and multiple preambles sent by the network device except the preambles corresponding to CBRA and CFRA.

[0188] Optionally, the first preamble group is determined according to multiple preambles corresponding to the CBRA; if the multiple preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined according to preamble group B; or, if the multiple preambles corresponding to the CBRA include preamble group A, the first preamble group is determined according to preamble group A.

[0189] Optionally, parameters corresponding to the first preamble code group are configured through ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0190] Optionally, the first preamble code group is determined according to multiple preamble codes corresponding to CFRA or multiple preamble codes other than the preamble codes corresponding to CBRA and CFRA, and the first preamble code group is configured in one of the following ways: configuring the first preamble code group separately; configuring according to RACH-ConfigCommon; and configuring according to RACH-ConfigDedicated.

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

[0192] 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 a random access other than the initial random access.

[0193] Optionally, the first indication information is used to determine one or more of the following information: the number of repeated transmissions of the first PUCCH; and resources used for repeated transmission of the first PUCCH.

[0194] Optionally, the number of repeated transmissions of the first PUCCH is indicated by one or more of the following information: the CSI request bit in the RAR uplink grant sent by the network device; the MCS index bit in the RAR uplink grant sent by the network device; the TPC command bit in the RAR uplink grant sent by the network device; the TAC sent by the network device; the repetition factor configured by the network device through the SIB; the scenario in which the terminal device sends message 3; the DAI bit of the DCI format 1_0 sent by the network device; and the port number for the terminal device to send DMRS.

[0195] Optionally, the repetition factor configured by the network device through the SIB includes multiple parameter values, and the number of repeated transmissions of the first PUCCH is dynamically adjusted according to the order of the multiple parameter values.

[0196] Optionally, the number of repeated transmissions of the first PUCCH is dynamically adjusted according to a plurality of parameter values in an ascending order.

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

[0198] Optionally, the resources used for repeatedly transmitting the first PUCCH include common PUCCH resources, and the common PUCCH resources are resources corresponding to the first index range in the PUCCH resource set.

[0199] Figure 9 Shown is a schematic structural diagram of a communication device according to an embodiment of the present application. Figure 9 The dotted lines in the figure indicate that the unit or module is optional. The apparatus 900 can be used to implement the method described in the above method embodiment. The apparatus 900 can be a chip, a terminal device, or a network device.

[0200] The device 900 may include one or more processors 910. The processor 910 may support the device 900 to implement the method described in the above method embodiment. 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, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0201] The apparatus 900 may further include one or more memories 920. The memories 920 store programs that can be executed by the processor 910, causing the processor 910 to perform the methods described in the above method embodiments. The memories 920 may be independent of the processor 910 or integrated into the processor 910.

[0202] The apparatus 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 with other devices or chips via the transceiver 930.

[0203] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0204] It should be understood that the computer-readable storage medium mentioned in the embodiments of the present application can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0205] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal device or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0206] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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 and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0207] The present application also provides a computer program that can be applied to a terminal device or network device provided in the present application, and enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0208] The terms "system" and "network" in this application may be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.

[0209] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0210] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0211] In an embodiment of the present application, "pre-configuration" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device). This application does not limit its specific implementation method.

[0212] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0213] In the embodiments of the present application, determining B based on A does not mean determining B only based on A. B can also be determined based on A and / or other information.

[0214] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0215] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0216] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0217] 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, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

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

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a downlink allocation index DAI bit of downlink control information DCI format 1_0 sent by a network device, where the network device is a network device of a non-terrestrial network NTN; The terminal device receives message 4 of the random access process; The terminal device repeatedly sends the feedback information corresponding to message 4 according to the DAI bit and whether the terminal device has the ability to repeatedly transmit the feedback information corresponding to message 4 of the random access process; Among them, the DAI bit is used to indicate the number of repeated transmissions of the feedback information corresponding to the message 4, and the repeated transmission is also based on the reference signal received power RSRP threshold related to the physical uplink control channel PUCCH repetition, and the RSRP threshold comes from the broadcast information.

2. The method according to claim 1, characterized in that The repeated transmission is further performed based on one or more of the following information: a first preamble selected by the terminal device; Channel quality detected by the terminal device; and The port number of the terminal device sending the demodulation reference signal DMRS.

3. The method according to claim 2, characterized in that The repeated transmission is associated with the first preamble, and before the terminal device receives message 4 of the random access procedure, the method further includes: The terminal device selects a first preamble, where the first preamble is a preamble in a first preamble group configured by the network device, and the first preamble group is used to indicate that the terminal device has the ability to repeatedly transmit feedback information corresponding to message 4 of the random access process; The terminal device sends the first preamble code.

4. The method according to claim 3, characterized in that The first preamble group is determined according to one or more preambles selected from the following: Multiple preamble codes corresponding to contention-based random access (CBRA) sent by the network device; Multiple preamble codes corresponding to the non-contention-based random access CFRA sent by the network device; and The network device sends multiple preamble codes except the preamble codes corresponding to CBRA and CFRA.

5. The method according to claim 4, characterized in that The first preamble group is determined according to a plurality of preambles corresponding to the CBRA; If the multiple preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined according to the preamble group B; or, If the multiple preambles corresponding to the CBRA include preamble group A, the first preamble group is determined according to the preamble group A.

6. The method according to claim 5, characterized in that The parameters corresponding to the first preamble code group are configured through ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

7. The method according to claim 4, characterized in that The first preamble group is determined according to the multiple preambles corresponding to the CFRA or the multiple preambles other than the preambles corresponding to the CBRA and CFRA, and the first preamble group is configured in one of the following ways: Separately configuring the first preamble group; Configured according to RACH-ConfigCommon; and Configure according to RACH-ConfigDedicated.

8. The method according to claim 3, characterized in that The method further comprises: If the number of consecutive failures of the terminal device in selecting the first preamble code for random access is greater than a first threshold, the terminal device selects a preamble code from other preamble code groups sent by the network device.

9. The method according to any one of claims 1 to 8, characterized in that The repeated transmission is also performed based on the resources used for repeated transmission of the feedback information corresponding to the message 4.

10. The method according to claim 9, characterized in that The resources used for repeatedly transmitting the feedback information corresponding to the message 4 include common PUCCH resources, and the common PUCCH resources are resources corresponding to the first index range in the PUCCH resource set.

11. A wireless communication method, characterized in that: include: The network device sends a downlink allocation index DAI bit of downlink control information DCI format 1_0, wherein the network device is a network device of a non-terrestrial network NTN; The network device sends message 4 of the random access process; The network device receives feedback information corresponding to the message 4 repeatedly sent by the terminal device, wherein the repeated sending is performed according to the DAI bit and whether the terminal device has the ability to repeatedly transmit the feedback information corresponding to the message 4 of the random access process; Among them, the DAI bit is used to indicate the number of repeated transmissions of the feedback information corresponding to the message 4, and the repeated transmission is also based on the reference signal received power RSRP threshold related to the physical uplink control channel PUCCH repetition, and the RSRP threshold comes from the broadcast information.

12. The method according to claim 11, characterized in that The repeated transmission is further performed based on one or more of the following information: a first preamble selected by the terminal device; Channel quality detected by the terminal device; and The port number of the terminal device sending DMRS.

13. The method according to claim 12, characterized in that The repeated transmission is associated with the first preamble, and before the network device sends message 4 of the random access procedure, the method further includes: The network device receives a first preamble code selected by the terminal device, where the first preamble code is a preamble code in a first preamble code group configured by the network device, and the first preamble code group is used to indicate that the terminal device has the ability to repeatedly transmit feedback information corresponding to message 4 of the random access process.

14. The method according to claim 13, characterized in that The first preamble group is determined according to one or more preambles selected from the following: Multiple preamble codes corresponding to contention-based random access (CBRA) sent by the network device; Multiple preamble codes corresponding to the non-contention-based random access CFRA sent by the network device; and The network device sends multiple preamble codes except the preamble codes corresponding to CBRA and CFRA.

15. The method according to claim 14, characterized in that The first preamble group is determined according to a plurality of preambles corresponding to the CBRA; If the multiple preambles corresponding to the CBRA include preamble group A and preamble group B, the first preamble group is determined according to the preamble group B; or, If the multiple preambles corresponding to the CBRA include preamble group A, the first preamble group is determined according to the preamble group A.

16. The method according to claim 15, characterized in that The parameters corresponding to the first preamble code group are configured through ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

17. The method according to claim 14, characterized in that The first preamble group is determined according to the multiple preambles corresponding to the CFRA or the multiple preambles other than the preambles corresponding to the CBRA and CFRA, and the first preamble group is configured in one of the following ways: Separately configuring the first preamble group; Configured according to RACH-ConfigCommon; and Configure according to RACH-ConfigDedicated.

18. The method according to any one of claims 11 to 17, characterized in that The repeated transmission is also performed based on the resources used for repeated transmission of the feedback information corresponding to the message 4.

19. The method according to claim 18, characterized in that The resources used for repeatedly transmitting the feedback information corresponding to the message 4 include common PUCCH resources, and the common PUCCH resources are resources corresponding to the first index range in the PUCCH resource set.

20. A wireless communication device, characterized in that: The apparatus is a terminal device, and the terminal device includes: A receiving unit, configured to receive a downlink allocation index (DAI) bit of downlink control information (DCI) format 1_0 sent by a network device, wherein the network device is a network device of a non-terrestrial network (NTN); The receiving unit is further configured to receive message 4 of a random access process; A sending unit, configured to repeatedly send the feedback information corresponding to message 4 according to the DAI bit and whether the terminal device has the ability to repeatedly transmit the feedback information corresponding to message 4 of the random access process; Among them, the DAI bit is used to indicate the number of repeated transmissions of the feedback information corresponding to the message 4, and the repeated transmission is also based on the reference signal received power RSRP threshold related to the physical uplink control channel PUCCH repetition, and the RSRP threshold comes from the broadcast information.

21. A wireless communication device, characterized in that: The device is a network device, and the network device includes: A sending unit, configured to send a downlink allocation index DAI bit of downlink control information DCI format 1_0, wherein the network device is a network device of a non-terrestrial network NTN; The sending unit is further configured to send message 4 of the random access process; a receiving unit, configured to receive feedback information corresponding to message 4 repeatedly sent by a terminal device, wherein the repeated sending is performed based on the DAI bit and whether the terminal device has the ability to repeatedly transmit the feedback information corresponding to message 4 of the random access process; Among them, the DAI bit is used to indicate the number of repeated transmissions of the feedback information corresponding to the message 4, and the repeated transmission is also based on the reference signal received power RSRP threshold related to the physical uplink control channel PUCCH repetition, and the RSRP threshold comes from the broadcast information.

22. A communication device, characterized in that: The system comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1 to 19.

23. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 19.

Images