Wireless communication method, terminal device and network device

Abstract

A wireless communication method, a terminal device and a network device, the method comprising: a terminal device determining, according to first information, whether a random access process is applicable to repeated transmission of a first physical uplink shared channel (PUSCH) and / or an interpretation mode of a target modulation and coding scheme (MCS) information domain, the first PUSCH is used for bearing a third message in the random access process, and the first information is related to repeated transmission of a physical random access channel (PRACH) in the random access process.

Description

Wireless communication method, terminal device and network device Technical Field

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

[0002] In the New Radio (NR) system, a four-step random access process is supported, specifically including the transmission process of Message 1 (Msg1, i.e., Physical Random Access Channel (PRACH)) to Message 4 (Msg4). Among them, Message 3 (Msg3) is carried by the Physical Uplink Shared Channel (PUSCH). In order to improve the coverage performance of Msg3 PUSCH and PRACH, it is considered to introduce repeated transmission of Msg3 PUSCH and repeated transmission of PRACH. In this case, how to perform repeated transmission of Msg3 PUSCH and repeated transmission of PRACH is an urgent problem to be solved.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device, and network device. By associating the repeated transmission of Msg3 PUSCH with the repeated transmission of PRACH, it is beneficial to reduce the implementation complexity of the terminal device and improve the uplink coverage performance of Msg3 PUSCH and PRACH.

[0005] In a first aspect, a method for wireless communication is provided, including: a terminal device determines, based on first information, whether a random access process is applicable to repeated transmission of a first physical uplink shared channel PUSCH and / or an interpretation method of a target modulation and coding scheme MCS information field, wherein the first PUSCH is used to carry a third message in the random access process, and the first information is related to the repeated transmission of a physical random access channel PRACH in the random access process.

[0006] According to a second aspect, a method for wireless communication is provided, including: a terminal device determines, based on second information, whether a random access process is applicable to repeated transmission of a physical random access channel PRACH, wherein the second information is related to repeated transmission of a first physical uplink shared channel PUSCH in the random access process, and the first PUSCH is used to carry a third message in the random access process.

[0007] According to a third aspect, a method for wireless communication is provided, including: a network device determines, based on third information, whether a random access process is applicable to repeated transmission of a first physical uplink shared channel PUSCH and / or information carried in a target modulation and coding scheme MCS information field, wherein the first PUSCH is used to carry a third message in the random access process, and the third information is related to repeated transmission of a physical random access channel PRACH in the random access process.

[0008] In a fourth aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or its various implementation modes.

[0009] Specifically, the terminal device includes a functional module for executing the method in any one of the first to second aspects or their respective implementations.

[0010] In a fifth aspect, a network device is provided for executing the method in the third aspect or its various implementations.

[0011] Specifically, the network device includes a functional module for executing the method in the above-mentioned third aspect or its various implementation modes.

[0012] In a sixth aspect, a terminal device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, so that the terminal device executes the method of any one of the first to second aspects or their respective implementations.

[0013] In a seventh aspect, a network device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, so that the network device executes the method of the third aspect or its respective implementations.

[0014] In an eighth aspect, a chip is provided for implementing the method described in any one of the first to third aspects or their respective implementations. Specifically, the chip includes a processor configured to load and execute a computer program from a memory, causing a device equipped with the chip to perform the method described in any one of the first to third aspects or their respective implementations.

[0015] In a ninth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method of any one of the first to third aspects or their respective implementations.

[0016] In a tenth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method of any one of the first to second aspects or their respective implementations.

[0017] In an eleventh aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or their respective implementations.

[0018] Through the above technical solution, the terminal device can associate the repeated transmission of Msg3 PUSCH with the repeated transmission of PRACH, which is conducive to reducing the implementation complexity of the terminal device and improving the uplink coverage performance of Msg3 PUSCH and PRACH. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0020] FIG2 is a schematic diagram of a four-step random access process.

[0021] FIG3 is a schematic diagram of repeated transmission of PRACH.

[0022] FIG4 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0023] FIG5 is a schematic diagram of repeated transmission of Msg3 PUSCH and repeated transmission of PRACH provided in the present application.

[0024] FIG6 is a schematic diagram of a configuration method of PRACH resources provided in this application.

[0025] FIG7 is a schematic flowchart of another wireless communication method provided according to an embodiment of the present application.

[0026] FIG8 is a schematic flowchart of another wireless communication method provided according to an embodiment of the present application.

[0027] FIG9 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0028] FIG10 is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

[0029] FIG11 is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0030] FIG12 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0031] FIG13 is a schematic block diagram of a chip provided according to an embodiment of the present application.

[0032] FIG14 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] 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.

[0034] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: 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 on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0035] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

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

[0037] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0038] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0039] The terminal device can be a station (ST) in a WLAN, 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, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0040] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0041] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0042] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0043] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0044] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0045] 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.

[0046] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . 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.

[0047] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0048] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

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

[0050] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0051] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0052] In the description of 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 being indicated, configuration and being configured, etc.

[0053] In the embodiments of the present application, "pre-defined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

[0054] 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, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0055] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0056] In the NR system, a four-step random access process is supported, specifically including the sending process of message 1 (Msg1) to message 4 (Msg4). As an example, as shown in Figure 2, the four-step random access process includes the following steps:

[0057] Step 1: The terminal device sends a random access preamble (Preamble, also known as Msg 1) to the network device.

[0058] The random access preamble may also be referred to as a preamble, a random access preamble sequence, a preamble sequence, etc.

[0059] Specifically, the terminal device can select a physical random access channel (PRACH) resource, which may include time domain resources, frequency domain resources, and code domain resources. The network device sends random access related parameters to the terminal device by broadcasting a system information block (SIB) 1, wherein the reference signal receiving power (RSRP) threshold value (rsrp-ThresholdSSB) for the synchronization signal block (SSB) in the random access common configuration information element (RACH-ConfigCommon IE) is used by the terminal device to select the SSB. The terminal device compares the RSRP measurement result under each SSB with the rsrp-ThresholdSSB, and selects the SSB with a measurement value higher than the configured threshold value for access. If there is no SSB that meets the configured threshold value, it randomly selects one from all SSBs for access. Each SSB corresponds to a set of random access preamble resources and random access opportunity (RACH Occasion, RO) resources. The terminal device randomly selects from the selected SSB for contention-based random access resources and sets the Preamble index (PREAMBLE_INDEX) to the selected random access Preamble. The network device can estimate the transmission delay between it and the terminal device based on the Preamble and calibrate the uplink timing (timing) based on this, and can roughly determine the resource size required for the terminal device to transmit Msg 3. In order to allow the network device to more accurately understand the size of the Msg 3 to be transmitted and allocate appropriate uplink resources, the Preamble is divided into Preamble group A and Preamble group B. If Preamble group B exists in the random access resources, the terminal device can select the Preamble group based on the size of Msg 3 and path loss.

[0060] Step 2: The network device sends a Random Access Response (RAR, also known as Msg 2) to the terminal device.

[0061] After the terminal device sends the Preamble to the network device, it can open a random access response window (ra-ResponseWindow) and detect the corresponding physical downlink control channel (PDCCH) within the ra-ResponseWindow according to the random access radio network temporary identifier (RA-RNTI). If the terminal device detects the PDCCH scrambled by the RA-RNTI, it can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH. The PDSCH includes the RAR corresponding to the Preamble.

[0062] RA-RNTI is calculated based on the time-frequency position of the PRACH that sends the Preamble. Therefore, if multiple terminal devices send Preamble on the same RO, the corresponding RARs are multiplexed in the same RAR Media Access Control Protocol Data Unit (MAC PDU). If the terminal successfully receives the RA-RNTI-scrambled PDCCH corresponding to the RO resource that sends the Preamble, and the RAR contains a MAC sub-PDU (subPDU) carrying a random access sequence identifier (RAPID) that corresponds to the PREAMBLE_INDEX selected in the above Msg 1, then the RAR is received successfully, and the terminal can decode the Timing Advance Command (TAC), uplink authorization resources (UL Grant) and temporary cell RNTI (TC-RNTI) and proceed to Msg 3.

[0063] If the RA-RNTI scrambled PDCCH corresponding to the RO resource for sending the Preamble is not received during the operation of the ra-ResponseWindow, or the RA-RNTI scrambled PDCCH is received but the RAR does not contain the MAC subPDU corresponding to PREAMBLE_INDEX, the RAR reception is considered to have failed in the above two situations. At this time, if the number of Preamble transmissions does not exceed the maximum number of transmissions configured by the network (preambleTransMax), the terminal device needs to retransmit Msg 1. If the number of Preamble transmissions exceeds the maximum number of transmissions configured by the network (preambleTransMax), the terminal device reports the random access problem to the upper layer.

[0064] Step 3: The terminal device sends Msg 3.

[0065] After receiving the RAR message, the terminal device determines whether the RAR is its own RAR message. For example, the terminal device can use the preamble code index to check. After determining that it is its own RAR message, it can generate Msg 3 at the RRC layer and send Msg 3 to the network device, which needs to carry the identification information of the terminal device, etc.

[0066] Msg 3 is mainly used to notify the network device of the random access triggering event. For different random access triggering events, the Msg 3 sent by the terminal device in step 3 may include different content.

[0067] For example, for the initial access scenario, Msg 3 may include an RRC Setup Request message generated by the RRC layer. In addition, Msg 3 may also carry, for example, the 5G-Serving Temporary Mobile Subscriber Identity (S-TMSI) of the terminal device or a random number.

[0068] For another example, in an RRC connection reestablishment scenario, Msg 3 may include an RRC connection reestablishment request message (RRC Reestabilshment Request) generated by the RRC layer. In addition, Msg 3 may also carry, for example, a Cell Radio Network Temporary Identifier (C-RNTI).

[0069] For another example, in a handover scenario, Msg 3 may include an RRC Handover Confirm message generated by the RRC layer, which carries the C-RNTI of the terminal device. In addition, Msg 3 may also carry information such as a Buffer Status Report (BSR). For other triggering events, such as the arrival of uplink / downlink data, Msg 3 may at least include the C-RNTI of the terminal device.

[0070] In step 4, the network device sends a contention resolution message (Msg 4) to the terminal device.

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

[0072] Message 3 (Msg3) is carried over the Physical Uplink Shared Channel (PUSCH). The RAR in Msg2 carries the PUSCH UL grant for the initial transmission of Msg3. The UL grant carried in the RAR is called the RAR UL grant. The RAR UL grant carries information such as PUSCH time and frequency resource allocation, power control commands (TPC), frequency hopping, and MCS.

[0073] If the network device does not receive Msg3 correctly, it will indicate the scheduling information of the retransmission of Msg3 through DCI, such as the DCI format 0_0 carried by the temporary cell radio network temporary identifier (Temporary Cell Radio Network Temporary Identity, TC-RNTI), which includes the new data indication (New Data Indicator, NDI), redundancy version, and HARQ process number in addition to the content contained in the RAR UL grant.

[0074] To improve the coverage performance of Msg3 PUSCH, repeated transmission of Msg3 PUSCH is introduced. The base station needs to indicate the number of repeated transmissions of Msg3 PUSCH. Due to the limited options for Msg3 size and the fact that repeated transmission of Msg3 PUSCH is used in coverage enhancement scenarios, the MCS levels used for Msg3 PUSCH transmission are also limited. Therefore, it is considered to use some bits in the MCS information field to indicate the number of repeated transmissions of Msg3 PUSCH.

[0075] For the initial transmission of Msg3 PUSCH scheduled by RAR UL grant, the number of repeated transmissions is indicated by the most significant 2 bits in the MCS information field in the RAR UL grant. The least significant 2 bits of the MCS information field are used to indicate the MCS index, which indicates one of the four MCS indices. The number of candidate repeated transmissions indicated by the most significant 2 bits in the MCS information field may be configured by the network device in the system message. If the network device is not configured with the candidate repeated transmission number, the default candidate repeated transmission number may be {1, 2, 3, 4}. The mapping relationship between the value of the most significant 2 bits of the MCS information field and the indicated number of repeated transmissions K of the Msg3 PUSCH is shown in Table 1 below, where the high-level parameter (i.e., NumofMsg3Repetition) is used to configure the four candidate repeated transmission numbers.

[0076] Table 1

[0077]

[0078] The least significant two bits of the MCS information field indicate one of four MCS indices. These four MCS indices are configured by the network device using the higher-layer parameter mcs-Msg3Repetition. If mcs-Msg3Repetition is not configured, the four MCS indices use default values ​​0-3. The correspondence between the values ​​of the two least significant bits and the four indicated MCS indices is shown in Table 2 below.

[0079] Table 2

[0080]

[0081] For the retransmission of Msg3, the scheduling information of Msg3 PUSCH is carried by DCI format 0_0 with TC-RNTI scrambled CRC. The scheduling information contains a 5-bit MCS information field. The most significant 2 bits can indicate one of the four repetition transmission times. The least significant 3 bits are used to indicate the MCS index, which indicates 8 MCS indexes in this case. The 8 MCS indexes are configured by the network device through the parameter mcs-Msg3Repetition. If mcs-Msg3Repetition is not configured, the 8 MCS indexes take the default value 0-7. Table 3 shows the mapping relationship between the least significant 3 bits of the MCS information field in DCI format 0_0 with TC-RNTI scrambled CRC and the MCS index.

[0082] Table 3

[0083]

[0084] During random access, after the UE sends the PRACH, it receives the RAR sent by the network in the RAR reception window. If the UE does not receive the RAR, it will send the PRACH again on the next available PRACH resource and increase the PRACH power by one step.

[0085] However, in coverage-limited scenarios, the UE cannot infinitely increase PRACH power to ensure detection by network equipment. To improve PRACH coverage, repeated PRACH transmissions are considered. As shown in Figure 3, repeated PRACH transmissions correspond to the same RAR receive window. Network equipment can combine and receive repeated PRACH transmissions to improve detection performance, thereby enhancing PRACH coverage. In this case, how to repeat Msg3 PUSCH transmissions and repeated PRACH transmissions is an urgent issue that needs to be addressed.

[0086] FIG4 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG4 , the method 200 includes at least part of the following:

[0087] S210, the terminal device determines whether the random access process is applicable to the repeated transmission of the first physical uplink shared channel PUSCH and / or the interpretation method of the target modulation and coding scheme MCS information field based on the first information, wherein the first PUSCH is used to carry the third message (i.e., Msg3) in the random access process, and the first information is related to the repeated transmission of the physical random access channel PRACH in the random access process.

[0088] In some embodiments, the terminal device supports repeated transmission of PRACH and repeated transmission of Msg3 PUSCH at the same time.

[0089] In the embodiment of the present application, the PUSCH used to carry Msg3 may also be referred to as Msg3 PUSCH. That is, the first PUSCH is Msg3 PUSCH.

[0090] In some embodiments, whether the random access procedure is applicable to repeated transmission of Msg3 PUSCH may refer to:

[0091] Whether repeated transmission of Msg3 PUSCH is required during the random access process, or whether repeated transmission of Msg3 PUSCH is required.

[0092] In some embodiments, the terminal device may determine whether the random access procedure is applicable to repeated transmission of Msg3 PUSCH, including at least one of the following:

[0093] The terminal device determines whether to request repeated transmission of the Msg3 PUSCH, and the terminal device determines whether to perform (or adopt) repeated transmission of the Msg3 PUSCH.

[0094] In some embodiments, in two cases where the random access process applies to repeated transmission of Msg3 PUSCH and does not apply to repeated transmission of Msg3 PUSCH, the target MCS information field corresponds to different interpretation methods.

[0095] For example, when the random access procedure is applicable to repeated transmission of Msg3 PUSCH, the target MCS information field is used to indicate the number of repeated transmissions of Msg3 PUSCH.

[0096] In some embodiments, the target MCS information field may be the MCS information field in the RAR UL grant. For example, when the random access procedure applies to repeated transmission of Msg3 PUSCH, the most significant 2 bits in the MCS information field indicate the number of repeated transmissions of Msg3 PUSCH.

[0097] In other embodiments, the target MCS information field may be the MCS information field carried by the TC-RNTI scrambled DCI format 0_0. For example, when the random access procedure applies to repeated transmission of Msg3 PUSCH, the most significant 2 bits in the MCS information field indicate the number of repeated transmissions of Msg3 PUSCH.

[0098] It should be understood that in an embodiment of the present application, the first information may refer to any information related to the repeated transmission of PRACH, for example, whether the random access process is applicable to the repeated transmission of PRACH, whether the terminal device adopts the repeated transmission of PRACH, whether the conditions for repeated transmission of PRACH are met, the judgment threshold for determining whether the repeated transmission of PRACH is met, the RAR corresponding to the repeated transmission of PRACH (i.e., the RAR in the random access process), etc. The present application is not limited to this.

[0099] In some embodiments, the first information includes whether the random access procedure is applicable to repeated transmission of PRACH and / or RAR in the random access procedure.

[0100] In some embodiments, whether the random access procedure is applicable to repeated transmission of PRACH can also be expressed as:

[0101] Whether the terminal device adopts repeated transmission of PRACH, whether the terminal device performs repeated transmission of PRACH.

[0102] For example, the application of repeated transmission of PRACH in the random access process can be expressed as the terminal device adopts repeated transmission of PRACH and the terminal device performs repeated transmission of PRACH; the application of repeated transmission of PRACH in the random access process can be expressed as the terminal device does not adopt repeated transmission of PRACH and the terminal device does not perform repeated transmission of PRACH.

[0103] In some embodiments, whether the random access process is applicable to repeated transmission of the PRACH may be determined based on the uplink coverage (or the uplink coverage level). For example, the terminal device may determine that repeated transmission of the PRACH is applicable to the random access process when the uplink coverage is poor to a certain extent.

[0104] Optionally, the uplink coverage condition may be determined by measuring a downlink signal.

[0105] That is, whether the random access process is applicable to repeated transmission of the PRACH may be determined according to the measurement result of the downlink signal.

[0106] In some embodiments, the measurement result of the downlink signal includes but is not limited to at least one of the following:

[0107] Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Received Signal Strength Indication (RSSI).

[0108] In some embodiments, the terminal device may determine whether the random access process is applicable to repeated transmission of the PRACH based on whether the measurement result of the downlink signal meets the second threshold.

[0109] For example, if the measurement result of the downlink signal meets the second threshold, it is determined that the random access process is applicable to repeated transmission of the PRACH.

[0110] For another example, if the measurement result of the downlink signal does not meet the second threshold, it is determined that the random access process is not applicable to repeated transmission of the PRACH.

[0111] Optionally, the measurement result of the downlink signal meeting the second threshold may include:

[0112] The measurement result of the downlink signal is lower than the second threshold; or

[0113] The measurement result of the downlink signal is lower than or equal to the second threshold.

[0114] Optionally, the measurement result of the downlink signal failing to meet the second threshold may include:

[0115] The measurement result of the downlink signal is higher than the second threshold; or

[0116] The measurement result of the downlink signal is higher than or equal to the second threshold.

[0117] Optionally, the second threshold may be configured by the network device or predefined.

[0118] In some embodiments, the second threshold may be specifically used to determine whether the random access procedure is applicable to repeated transmission of the PRACH. In other words, the second threshold is specifically used to determine whether the conditions for repeated transmission of the PRACH are met.

[0119] That is, repeated transmission of the PRACH corresponds to an independent decision threshold.

[0120] In some embodiments, the second threshold may be used to determine whether repeated transmission of the PRACH is applicable to the random access procedure, and may also be used to determine whether repeated transmission of the Msg3 PUSCH is applicable to the random access procedure. In other words, the second threshold may be used to determine whether the conditions for repeated transmission of the PRACH are met, and may also be used to determine whether the conditions for repeated transmission of the Msg3 PUSCH are met.

[0121] That is, repeated transmission of PRACH and repeated transmission of Msg3 PUSCH can share the same judgment threshold.

[0122] In some embodiments, the number of repeated transmissions of the PRACH may be determined based on a measurement result of a downlink signal.

[0123] For example, the terminal device may determine the number of repeated transmissions of the PRACH based on the measurement results of the downlink signal and multiple measurement result ranges, wherein the multiple measurement result ranges respectively correspond to different numbers of repeated transmissions of the PRACH.

[0124] In some embodiments, the plurality of measurement result ranges are determined according to a plurality of thresholds.

[0125] In some embodiments, the multiple measurement result ranges or the multiple thresholds are configured by the network device, or may be predefined. For example, the network device may configure the multiple measurement result ranges or the multiple thresholds via a broadcast message, dedicated signaling (e.g., RRC signaling), or the like.

[0126] In other embodiments, the number of repeated transmissions of the PRACH is configured by the network device or is predefined.

[0127] The following describes a method for determining repeated transmission of Msg3 PUSCH in conjunction with specific embodiments.

[0128] Example 1:

[0129] In this embodiment 1, the first information includes whether the random access process is applicable to repeated transmission of PRACH, that is, whether the terminal device adopts repeated transmission of PRACH.

[0130] In some embodiments, S210 may include:

[0131] The terminal device determines whether to request repeated transmission of Msg3 PUSCH and / or the interpretation method of the target MCS information field based on the first information.

[0132] That is, the terminal device determines whether to request repeated transmission of Msg3 PUSCH based on whether repeated transmission of PRACH is adopted.

[0133] For example, when the terminal device adopts repeated transmission of PRACH, it is determined to request repeated transmission of Msg3 PUSCH.

[0134] For another example, when the terminal device does not adopt repeated transmission of PRACH, it is determined not to request repeated transmission of Msg3 PUSCH.

[0135] Among them, the judgment method of whether the terminal device adopts repeated transmission of PRACH refers to the relevant description of the aforementioned embodiment, and for the sake of brevity, it will not be repeated here.

[0136] That is, in this embodiment 1, when the terminal device adopts repeated transmission of PRACH, it also requests repeated transmission of Msg3 PUSCH. In other words, the judgment condition of repeated transmission of PRACH can be understood as the judgment condition of requesting repeated transmission of Msg3 PUSCH.

[0137] When the terminal device determines to adopt repeated transmission of PRACH, it indicates that the current uplink coverage is poor and repeated transmission of PRACH is needed to improve the uplink coverage of PRACH. Correspondingly, the uplink coverage of Msg3 PUSCH may also be poor. Therefore, when the terminal device determines to adopt repeated transmission of PRACH, it can request repeated transmission of Msg3 PUSCH at the same time to improve the uplink coverage of Msg3 PUSCH.

[0138] In some embodiments, the terminal device may send a PRACH through a first PRACH resource to implicitly indicate to the network device a request for repeated transmission of the Msg3 PUSCH. The first PRACH resource may be a resource used for repeated transmission of the PRACH.

[0139] That is, the first PRACH resource can be used to indicate repeated transmission of the PRACH and also to indicate a request for repeated transmission of the Msg3 PUSCH. In other words, the first PRACH resource is associated with repeated transmission of the PRACH and repeated transmission of the Msg3 PUSCH.

[0140] Correspondingly, after receiving the PRACH sent by the terminal device on the first PRACH resource, the network device can determine that the terminal device adopts repeated transmission of PRACH and also requests repeated transmission of Msg3 PUSCH.

[0141] In some embodiments, the terminal device determines, based on the first information, a method for interpreting the target MCS information field, including:

[0142] When the terminal device adopts repeated transmission of PRACH, the number of repeated transmissions of Msg3 PUSCH is determined according to the target MCS information field.

[0143] Optionally, when the terminal device requests repeated transmission of Msg3 PUSCH, the network device may decide whether to schedule repeated transmission of Msg3 PUSCH and / or indicate the number of repeated transmissions of Msg3 PUSCH to the terminal device.

[0144] For example, when the terminal device requests repeated transmission of Msg3 PUSCH, the network device indicates the number of repeated transmissions of Msg3 PUSCH through the target MCS information field.

[0145] That is, when the terminal device requests repeated transmission of Msg3 PUSCH, the network device can carry the repeated transmission number information of Msg3 PUSCH in the target MCS information field.

[0146] With reference to the example of Figure 5, the terminal device initiates random access and selects resources for repeated transmission of PRACH to perform repeated transmission of PRACH. When the network device receives PRACH on the resource for repeated transmission of PRACH, it can be determined that the terminal device adopts repeated transmission of PRACH and requests repeated transmission of Msg3 PUSCH. Furthermore, the network device can indicate the number of repeated transmissions of Msg3 PUSCH in the RAR. For example, the number of repeated transmissions of Msg3 PUSCH is indicated by the highest 2 bits in the MCS information field in the UL grant in the RAR. Furthermore, the terminal device performs repeated transmission of Msg3 PUSCH according to the number of repeated transmissions.

[0147] Example 2:

[0148] In this embodiment 2, the first information includes the RAR in the random access process.

[0149] In some embodiments, S210 may include:

[0150] When repeated transmission of PRACH is adopted, the terminal device determines whether to repeat transmission of Msg3 PUSCH based on the RAR in the random access process.

[0151] In some embodiments, during repeated PRACH transmissions, the terminal device may transmit multiple preambles, where the transmit power used to transmit the multiple preambles may be gradually increased to increase the probability of successful detection by the network device. That is, the preamble may be used to indicate the transmit power.

[0152] In some embodiments, the network device may indicate the received preamble code to the terminal device when sending the RAR, so that the terminal device may determine the power used to send the Msg3 PUSCH based on the preamble code to improve the uplink coverage performance.

[0153] In some embodiments, the power used to send the preamble code and the power used to send the Msg3 PUSCH are associated with each other, for example, there is a specific power offset. Optionally, the specific power offset is configured through a higher layer parameter.

[0154] In some embodiments, the RAR includes first indication information, which can be used to determine the reception status of repeated PRACH transmissions, and the reception status of repeated PRACH transmissions can reflect the current uplink coverage level. For different uplink coverage levels, the requirement for repeated Msg3 PUSCH transmissions is different.

[0155] That is to say, when the terminal device adopts repeated transmission of PRACH, the terminal device can determine the current uplink coverage level according to the RAR sent by the network device, and further determine whether to perform repeated transmission of Msg3 PUSCH according to the current uplink coverage level.

[0156] Alternatively, when the terminal device adopts repeated transmission of PRACH, the network device can determine the current uplink coverage level through repeated transmission of PRACH, and then determine whether there is a need for repeated transmission of Msg3 PUSCH, and further indicate to the terminal device through RAR whether to repeat transmission of Msg3 PUSCH.

[0157] In some embodiments, the first indication information is used to determine a target preamble, where the target preamble is a preamble in repeated transmissions of the PRACH. For example, in repeated transmissions of the PRACH, the terminal device may send multiple preambles, and the target preamble may be a preamble detected by the network device, such as the first preamble detected, or all preambles detected.

[0158] It can be understood that the reception status of the preamble code in the repeated transmission of the PRACH can reflect the current uplink coverage level.

[0159] It should be understood that the present application does not limit the indication method of the target preamble code. For example, the network device can explicitly or implicitly indicate the target preamble code in the RAR, for example, by a preamble code index (PREAMBLE_INDEX) or number, resource location, and the corresponding sequence number of the target preamble code in the repeated transmission of PRACH.

[0160] That is, in the embodiment of the present application, in addition to being used to determine the transmit power of Msg3 PUSCH, the target preamble is also used to determine whether to perform repeated transmission of Msg3 PUSCH.

[0161] In some embodiments, if the target preamble is received on a PRACH resource that is received earlier in the repeated PRACH transmissions, the network device may determine that the uplink coverage is not poor, and therefore, may not perform repeated transmissions of the Msg3 PUSCH. Alternatively, if the target preamble is received on a PRACH resource that is received later in the repeated PRACH transmissions, the network device may determine that the uplink coverage is poor, and therefore, may perform repeated transmissions of the Msg3 PUSCH.

[0162] Correspondingly, the terminal device determines the target preamble code based on the first indication information in the received RAR. If the target preamble code is sent on a PRACH resource that is earlier in the repeated transmission of the PRACH, the terminal device determines not to perform repeated transmission of the Msg3 PUSCH. Alternatively, if the target preamble code is sent on a PRACH resource that is later in the repeated transmission of the PRACH, the terminal device may determine to perform repeated transmission of the Msg3 PUSCH.

[0163] It should be understood that in an embodiment of the present application, the target preamble code can be directly used to indicate the judgment result of whether to repeatedly transmit Msg3 PUSCH. For example, the target preamble code and whether to repeatedly transmit Msg3 PUSCH have a corresponding relationship. Alternatively, the terminal device can also determine whether to repeatedly transmit Msg3 PUSCH based on the target preamble code. For example, the terminal device can determine whether to repeatedly transmit Msg3 PUSCH based on the number of the target preamble code and the first threshold. This application does not limit the specific judgment method.

[0164] In some embodiments, the first indication information is used to indicate at least one of the following:

[0165] Index information of the target preamble (i.e., PREAMBLE_INDEX);

[0166] a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR;

[0167] The PRACH occasion where the target preamble code is located;

[0168] Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH;

[0169] The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

[0170] In some embodiments, the RAR sent by the network device may be scheduled by a PDCCH, and the PDCCH may be scrambled by an RA-RNTI, which may be determined based on the time-frequency resource location of the preamble. That is, different PRACH resources may correspond to different RA-RNTIs. Therefore, a terminal device that selects a specific PRACH resource to send a PRACH may receive the RAR based on the RA-RNTI corresponding to the specific PRACH resource and determine the target preamble based on the RA-RNTI.

[0171] In some embodiments, the network device may number the PRACH opportunities where multiple preambles are located, and further carry the PRACH opportunity number in the RAR, so that the terminal device may determine which preamble corresponds to the PRACH opportunity number.

[0172] In some embodiments, the network device may notify the terminal device via the RAR which of the repeated PRACH transmissions the target preamble received by the network device represents. For example, the network device may number the repeated PRACH transmissions according to the transmission time, and further include in the RAR the number of the transmission corresponding to the received preamble.

[0173] In some embodiments, the network device may number the multiple preambles sent by the terminal device in repeated PRACH transmissions, for example, by sequentially numbering them in chronological order of transmission. For example, if the multiple preambles include four preambles, the four preambles may be numbered 0 to 3. The preamble numbers may be further carried in the RAR.

[0174] In some embodiments, the terminal device may determine whether to perform repeated transmission of the Msg3 PUSCH based on the preamble code indicated by the first indication information in the RAR.

[0175] For example, whether to perform repeated transmission of the Msg3 PUSCH is determined according to the number of the target preamble transmission in the repeated transmission of the PRACH.

[0176] It should be understood that the number of the target preamble code transmission in the repeated transmission of the PRACH can be determined according to the index information of the target preamble code. For example, according to the index information of the target preamble code, it can be determined which transmission the target preamble code corresponds to, or it can be determined according to the RA-RNTI of the PDCCH of the scrambled scheduling RAR, or it can be determined according to the PRACH timing where the preamble code is located, or it can be determined according to the number of the target preamble code in multiple preamble codes, or it can be determined according to the transmission number corresponding to the transmission of the target preamble code. This application does not limit this.

[0177] In some embodiments, the number of the target preamble code in the repeated transmission of the PRACH may correspond to whether the repeated transmission of the Msg3 PUSCH is performed. For example, the number 0 or 1 corresponds to not repeatedly transmitting the Msg3 PUSCH, and the number 2 or 3 corresponds to repeatedly transmitting the Msg3 PUSCH.

[0178] For example, the preambles sent in four repeated PRACH transmissions are numbered 0-3 in sequence according to the transmission time. If the network device detects a preamble on an earlier PRACH resource in the repeated PRACH transmission and indicates the preamble number in the RAR, for example, indicating preamble number 0 or 1, the terminal device considers that repeated transmission of Msg3 PUSCH is not performed. If the network device detects a preamble on a later PRACH resource in the repeated PRACH transmission and indicates the preamble number in the RAR, for example, indicating preamble number 2 or 3, the terminal device considers that repeated transmission of Msg3 PUSCH is performed.

[0179] Optionally, the corresponding relationship may be configured by the network device or predefined.

[0180] In other embodiments, the terminal device may determine whether to perform repeated transmission of the Msg3 PUSCH according to the number of the target preamble code transmission in the repeated transmission of the PRACH and the first threshold.

[0181] For example, if the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, it is determined to perform repeated transmission of the Msg3 PUSCH.

[0182] For another example, if the number of the target preamble transmission in the repeated transmission of the PRACH does not meet the first threshold, it is determined not to perform repeated transmission of the Msg3 PUSCH.

[0183] In some embodiments, the first threshold is predefined or configured by the network device.

[0184] In some embodiments, the number of the target preamble code transmitted in the repeated transmission of the PRACH meeting the second threshold may include:

[0185] The number of transmissions of the target preamble in repeated transmissions of the PRACH is greater than a first threshold; or

[0186] The number of transmissions of the target preamble code in repeated transmissions of the PRACH is greater than or equal to a first threshold.

[0187] That is, when the preamble code is received at a later time position, it can be considered that the uplink coverage is poor, so the terminal device can repeat the transmission of Msg3 PUSCH.

[0188] In some embodiments, the number of the target preamble code transmitted in the repeated transmission of the PRACH not meeting the second threshold may include:

[0189] The number of transmissions of the target preamble in repeated transmissions of the PRACH is less than a first threshold; or

[0190] The number of transmissions of the target preamble code in repeated transmissions of the PRACH is less than or equal to a first threshold.

[0191] That is, when the preamble code is received at an earlier time position, it can be considered that the uplink coverage is not bad, and the terminal device does not need to repeatedly transmit the Msg3 PUSCH.

[0192] Optionally, when the network device instructs repeated transmission of the Msg3 PUSCH, the network device may further indicate information on the number of repeated transmissions of the Msg3 PUSCH.

[0193] For example, the network device may indicate the number of repeated transmissions of Msg3 PUSCH through the target MCS information field. For the specific indication method, please refer to the relevant description of the above embodiment, which will not be repeated here.

[0194] Correspondingly, in the case of repeated transmission of Msg3 PUSCH, the terminal device can determine the number of repeated transmissions of Msg3 PUSCH according to the target MCS information field.

[0195] In some other embodiments, when repeated transmission of the Msg3 PUSCH is performed, the network device may indicate the number of repeated transmissions of the Msg3 PUSCH through a target preamble code.

[0196] For example, different target preamble codes correspond to different repetition transmission times information.

[0197] In some embodiments, the number of the preamble code (which may also be replaced by other content indicated by the first indication information) and the number of repeated transmission times of the Msg3 PUSCH have a corresponding relationship.

[0198] In some embodiments, the preamble code number and the default Msg3 PUSCH repetition transmission count information have a corresponding relationship.

[0199] For example, the preamble code numbers 0-3 correspond to the number of repetition transmissions of Msg3 PUSCH 1-4 respectively.

[0200] In some other embodiments, there is a corresponding relationship between the preamble code number and the Msg3 PUSCH repetition transmission count information configured by the network device.

[0201] For example, the preamble code numbers 0-3 correspond to the number of repetition transmissions of Msg3 PUSCH 1, 2, 4, and 8 configured by the network device.

[0202] In some embodiments of the present application, the network device may distinguish random access of terminal devices with different characteristics through PRACH resources.

[0203] For example, the network device may configure PRACH resources according to a feature combination (FeatureCombination).

[0204] Optionally, Msg3 PUSCH repeated transmission is one of the features in the feature combination.

[0205] Optionally, the feature combination may include at least one of the following:

[0206] Repeated transmission of PRACH (denoted as characteristic combination 1), repeated transmission of PRACH and repeated transmission of Msg3 PUSCH (denoted as characteristic combination 2), repeated transmission of Msg3 PUSCH (denoted as characteristic combination 3).

[0207] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of Msg3 PUSCH.

[0208] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of PRACH.

[0209] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of the PRACH and repeated transmission of the Msg3 PUSCH.

[0210] For terminal devices that support repeated transmission of Msg3 PUSCH, when requesting repeated transmission of Msg3 PUSCH, you can select PRACH resources with the characteristics of repeated transmission of Msg3 PUSCH to send PRACH. When not requesting repeated transmission of Msg3 PUSCH, you can select PRACH resources that are not associated with the characteristics of repeated transmission of Msg3 PUSCH to send PRACH.

[0211] In some embodiments, when repeated transmission of the PRACH is associated with repeated transmission of the Msg3 PUSCH, the PRACH resources associated with the repeated transmission of the PRACH and the PRACH resources associated with the repeated transmission of the Msg3 PUSCH may be shared, for example, a shared preamble set and / or a shared PRACH opportunity set.

[0212] For example, the network device may configure a preamble set and / or a shared PRACH occasion through a Feature Combination Preambles information element. The preamble set or the shared PRACH occasion is associated with Feature Combination 3.

[0213] In some embodiments, as shown in FIG6 , the network configures three FeatureCombinationPreambles information elements, where FeatureCombinationPreambles information element 1 is associated with a FeatureCombination that includes PRACH repetition transmission but does not include Msg3 PUSCH repetition transmission, FeatureCombinationPreambles information element 2 is associated with a FeatureCombination that includes PRACH repetition transmission and Msg3 PUSCH repetition transmission, and FeatureCombinationPreambles information element 3 is associated with a FeatureCombination that includes Msg3 PUSCH repetition transmission but does not include PRACH repetition transmission. Each FeatureCombinationPreambles information element is used to configure the PRACH resources associated with the corresponding feature combination.

[0214] Optionally, if the terminal device determines to adopt repeated transmission of PRACH and requests repeated transmission of Msg3 PUSCH, PRACH is transmitted through the first PRACH resource, wherein the first PRACH resource belongs to a first PRACH resource set, and the first PRACH resource set is associated with the repeated transmission of the PRACH and the repeated transmission of Msg3 PUSCH, wherein the first PRACH resource set can be a PRACH resource set allocated by FeatureCombinationPreambles information element 1.

[0215] Optionally, if the terminal device adopts repeated transmission of PRACH and does not request repeated transmission of Msg3 PUSCH, PRACH is transmitted through a second PRACH resource, and the second PRACH resource belongs to a second PRACH resource set, and the second PRACH resource set is associated with the repeated transmission of the PRACH, wherein the second PRACH resource set can be a PRACH resource set allocated by FeatureCombinationPreambles information element 2.

[0216] Optionally, the terminal device does not adopt repeated transmission of PRACH and requests repeated transmission of Msg3 PUSCH, then transmits PRACH through a third PRACH resource, the third PRACH resource belongs to a third PRACH resource set, and the third PRACH resource set is associated with the repeated transmission of the first PUSCH, wherein the third PRACH resource set can be a PRACH resource set allocated by FeatureCombinationPreambles information element 3.

[0217] In summary, in the embodiment of the present application, the terminal device can associate the repeated transmission of Msg3 PUSCH with the repeated transmission of PRACH, which is beneficial to improving the uplink coverage performance of Msg3 PUSCH and reducing the implementation complexity of the terminal device.

[0218] FIG7 is a schematic flow chart of another wireless communication method 300 according to an embodiment of the present application. As shown in FIG7 , the method 300 includes at least part of the following:

[0219] S310, the terminal device determines whether the random access process is applicable to the repeated transmission of the physical random access channel PRACH based on the second information, wherein the second information is related to the repeated transmission of the first physical uplink shared channel PUSCH in the random access process, and the first PUSCH is used to carry the third message in the random access process.

[0220] In some embodiments, the terminal device supports repeated transmission of PRACH and repeated transmission of Msg3 PUSCH at the same time.

[0221] In the embodiment of the present application, the PUSCH used to carry Msg3 may also be referred to as Msg3 PUSCH, that is, the first PUSCH is Msg3 PUSCH.

[0222] In some embodiments, whether the random access process uses repeated transmission of PRACH can also be expressed as:

[0223] Whether the terminal device adopts repeated transmission of PRACH, whether the terminal device performs repeated transmission of PRACH.

[0224] It should be understood that the same terms in method 300 and method 200 may be interpreted in the same way, and for the sake of brevity, they are not repeated here.

[0225] The following describes in detail the determination of whether the random access procedure is applicable to repeated transmission of the PRACH.

[0226] Method 1:

[0227] In some embodiments, whether the random access process is applicable to repeated transmission of the PRACH may be determined based on the uplink coverage (or the uplink coverage level). For example, the terminal device may determine that repeated transmission of the PRACH is applicable to the random access process when the uplink coverage is poor to a certain extent.

[0228] Optionally, the uplink coverage condition may be determined by measuring a downlink signal.

[0229] That is, whether the random access process uses repeated transmission of the PRACH may be determined according to the measurement result of the downlink signal.

[0230] In some embodiments, the measurement result of the downlink signal includes at least one of the following:

[0231] RSRP, RSRQ, SINR, RSSI.

[0232] In some embodiments, the terminal device may determine whether the random access process is applicable to repeated transmission of PRACH based on whether the measurement result of the downlink signal meets the second threshold.

[0233] For example, if the measurement result of the downlink signal meets the second threshold, it is determined that the random access process is applicable to repeated transmission of the PRACH.

[0234] For another example, if the measurement result of the downlink signal does not meet the second threshold, it is determined that the random access process is not applicable to repeated transmission of the PRACH.

[0235] Optionally, the measurement result of the downlink signal meeting the second threshold may include:

[0236] The measurement result of the downlink signal is lower than the second threshold; or

[0237] The measurement result of the downlink signal is lower than or equal to the second threshold.

[0238] Optionally, the measurement result of the downlink signal failing to meet the second threshold may include:

[0239] The measurement result of the downlink signal is higher than the second threshold; or

[0240] The measurement result of the downlink signal is higher than or equal to the second threshold.

[0241] It should be understood that in this first approach, whether the random access process is applicable to repeated transmission of the PRACH may not be associated with repeated transmission of the Msg3 PUSCH. For example, whether the random access process is applicable to repeated transmission of the PRACH and whether the random access process is applicable to repeated transmission of the Msg3 PUSCH may be determined using independent judgment conditions, such as using different RSRP thresholds.

[0242] Mode 2: Whether the random access process is applicable to repeated transmission of the PRACH is determined according to the second information.

[0243] It should be understood that in an embodiment of the present application, the second information may refer to any information related to the repeated transmission of Msg3 PUSCH, for example, whether the random access process is applicable to the repeated transmission of Msg3 PUSCH, whether the terminal device adopts the repeated transmission of Msg3 PUSCH, whether the conditions for the repeated transmission of Msg3 PUSCH are met, the judgment threshold for determining whether the repeated transmission of Msg3 PUSCH is met, etc. The present application is not limited to this.

[0244] In the following, the second information including whether the condition for requesting repeated transmission of Msg3 PUSCH is met is used as an example for description, but the present application is not limited thereto. In other words, whether to request repeated transmission of Msg3 PUSCH and whether to use repeated transmission of PRACH can share the same judgment condition, such as a common threshold.

[0245] In some embodiments, whether the random access procedure is applicable to repeated transmission of Msg3 PUSCH may refer to:

[0246] Whether repeated transmission of Msg3 PUSCH is required during the random access process, or whether repeated transmission of Msg3 PUSCH is required.

[0247] In some embodiments, whether the random access procedure is applicable to repeated transmission of Msg3 PUSCH may include at least one of the following:

[0248] Whether the terminal device requests repeated transmission of Msg3 PUSCH in the random access process, and whether the terminal device performs repeated transmission of Msg3 PUSCH.

[0249] In some embodiments of the present application, S310 includes:

[0250] If a condition for requesting repeated transmission of the first PUSCH is met, determining that repeated transmission of the PRACH is applicable to the random access procedure; or

[0251] If a condition for requesting repeated transmission of the first PUSCH is not met, determining that repeated transmission of the PRACH is not applicable to the random access procedure.

[0252] In some embodiments, whether the condition for requesting repeated transmission of Msg3 PUSCH is met may be determined based on the uplink coverage level. Alternatively, the uplink coverage may be determined by measuring the downlink signal.

[0253] In some embodiments, the method 300 further includes:

[0254] According to the measurement result of the downlink signal, it is determined whether the conditions for requesting repeated transmission of Msg3 PUSCH are met.

[0255] For example, when the measurement result of the downlink signal meets the third threshold, it is determined that the condition for requesting repeated transmission of the Msg3 PUSCH is met.

[0256] For another example, when the measurement result of the downlink signal does not meet the third threshold, it is determined that the condition for requesting repeated transmission of the Msg3 PUSCH is not met.

[0257] Optionally, the measurement result of the downlink signal meeting the third threshold may include:

[0258] The measurement result of the downlink signal is lower than the third threshold; or

[0259] The measurement result of the downlink signal is lower than or equal to the third threshold.

[0260] Optionally, the measurement result of the downlink signal failing to meet the third threshold may include:

[0261] The measurement result of the downlink signal is higher than the third threshold; or

[0262] The measurement result of the downlink signal is higher than or equal to the third threshold.

[0263] In summary, the third threshold can be used to determine whether the random access procedure is applicable to repeated transmission of Msg3 PUSCH, and can also be used to determine whether the random access procedure is applicable to repeated transmission of PRACH. In other words, the third threshold can be used to determine whether the repeated transmission conditions of Msg3 PUSCH are met, and can also be used to determine whether the repeated transmission conditions of PRACH are met.

[0264] In some embodiments, the number of repeated transmissions of the PRACH is configured by a network device or is predefined.

[0265] In some embodiments, the number of repeated transmissions of the PRACH may be determined based on a measurement result of a downlink signal.

[0266] For example, the terminal device may determine the number of repeated transmissions of the PRACH based on the measurement results of the downlink signal and multiple measurement result ranges, wherein the multiple measurement result ranges respectively correspond to different numbers of repeated transmissions of the PRACH.

[0267] In some embodiments, the plurality of measurement result ranges are determined according to a plurality of thresholds.

[0268] In some embodiments, the multiple measurement result ranges or the multiple thresholds are configured by the network device, or may be predefined. For example, the network device may configure the multiple measurement result ranges or the multiple thresholds via a broadcast message, dedicated signaling (e.g., RRC signaling), or the like.

[0269] In some embodiments of the present application, the network device may distinguish random access of terminal devices with different characteristics through PRACH resources.

[0270] For example, the network device may configure PRACH resources according to a feature combination (FeatureCombination).

[0271] Optionally, Msg3 PUSCH repeated transmission is one of the features in the feature combination.

[0272] Optionally, the feature combination may include at least one of the following:

[0273] Repeated transmission of PRACH only (denoted as characteristic combination 1), repeated transmission of PRACH and repeated transmission of Msg3 PUSCH (denoted as characteristic combination 2), repeated transmission of Msg3 PUSCH only (denoted as characteristic combination 3).

[0274] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of Msg3 PUSCH.

[0275] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of PRACH.

[0276] In some embodiments, the network device may configure associated PRACH resources for repeated transmission of the PRACH and repeated transmission of the Msg3 PUSCH.

[0277] In some embodiments, when repeated transmission of the PRACH is associated with repeated transmission of the Msg3 PUSCH, the PRACH resources associated with the repeated transmission of the PRACH and the PRACH resources associated with the repeated transmission of the Msg3 PUSCH may be shared, for example, a shared preamble set and / or a shared PRACH opportunity set.

[0278] For example, the network device may configure a preamble set and / or a shared PRACH occasion through a Feature Combination Preambles information element. The preamble set or the shared PRACH occasion is associated with Feature Combination 3.

[0279] Among them, the configuration method of the FeatureCombinationPreambles information element refers to the relevant description of the embodiment shown in Figure 6 above, and for the sake of brevity, it is not repeated here.

[0280] Optionally, in some embodiments, if whether the random access process is applicable to repeated transmission of PRACH and whether the random access process is applicable to repeated transmission of Msg3 PUSCH are determined using independent judgment conditions respectively, in this case, the network device can configure PRACH resources associated with repeated transmission of PRACH and PRACH resources associated with repeated transmission of Msg3 PUSCH, wherein some of the PRACH resources associated with repeated transmission of PRACH can be associated with repeated transmission of Msg3 PUSCH, and some PRACH resources are not associated with repeated transmission of Msg3 PUSCH, and some of the PRACH resources associated with repeated transmission of Msg3 PUSCH can be associated with repeated transmission of PRACH, and some PRACH resources are not associated with repeated transmission of PRACH.

[0281] Then, when the terminal device determines to adopt repeated transmission of PRACH and determines to request repeated transmission of Msg3 PUSCH, the PRACH resources associated with repeated transmission of PRACH and associated with repeated transmission of Msg3 PUSCH can be used to send PRACH. Alternatively, if the terminal device does request repeated transmission of Msg3 PUSCH but does not adopt repeated transmission of PRACH, the PRACH resources not associated with repeated transmission of PRACH among the PRACH resources associated with repeated transmission of Msg3 PUSCH can be used to send PRACH.

[0282] In summary, in the embodiment of the present application, the terminal device can associate the repeated transmission of PRACH with the repeated transmission of Msg3 PUSCH, which is beneficial to reducing the implementation complexity of the terminal device and improving the uplink coverage performance of PRACH.

[0283] FIG8 is a schematic flow chart of another wireless communication method 400 according to an embodiment of the present application. As shown in FIG8 , the method 400 includes at least part of the following:

[0284] S410, the network device determines whether the random access process is applicable to the repeated transmission of the first physical uplink shared channel PUSCH and / or the information carried in the target modulation and coding scheme MCS information field based on the third information, wherein the first PUSCH is used to carry the third message in the random access process (i.e., Msg3 PUSCH), and the third information is related to the repeated transmission of the physical random access channel PRACH in the random access process.

[0285] It should be understood that the explanations of the terms in method 400 refer to the explanations of the corresponding terms in method 200, and for the sake of brevity, they are not repeated here.

[0286] It should be understood that the specific implementation of the network device side in method 400 refers to the relevant implementation of the network device in method 200, and for the sake of brevity, it will not be repeated here.

[0287] In some embodiments, the network device determines whether the random access process is applicable to repeated transmission of the first physical uplink shared channel PUSCH, which may include:

[0288] The network device determines whether the terminal device requests repeated transmission of Msg3 PUSCH during random access, or

[0289] The network device determines whether there is a need to perform repeated transmission of the Msg3 PUSCH during the random access process (or, in other words, whether repeated transmission of the Msg3 PUSCH is performed during the random access process).

[0290] It should be understood that in an embodiment of the present application, the third information may refer to any information related to the repeated transmission of PRACH, for example, whether the random access process is applicable to the repeated transmission of PRACH, whether the terminal device adopts the repeated transmission of PRACH, etc. The present application is not limited to this.

[0291] In some embodiments, the third information includes whether the terminal device adopts repeated transmission of PRACH and / or the target preamble code in the repeated transmission of PRACH.

[0292] Optionally, the specific indication method of the target preamble code refers to the relevant description in method 200, and for the sake of brevity, it is not repeated here.

[0293] In some embodiments of the present application, the method 400 may include:

[0294] According to whether the terminal device adopts repeated transmission of PRACH, it is determined whether the terminal device requests repeated transmission of Msg3 PUSCH and / or the information carried in the target MCS information field.

[0295] For example, when the terminal device adopts repeated transmission of PRACH, it is determined that the terminal device requests repeated transmission of Msg3 PUSCH.

[0296] For another example, when the terminal device does not adopt repeated transmission of PRACH, it is determined that the terminal device does not request repeated transmission of Msg3 PUSCH.

[0297] In some embodiments of the present application, S410 may include:

[0298] In the case where the terminal device adopts repeated transmission of PRACH, the target MCS information field carries the information of the number of repeated transmissions of the first PUSCH.

[0299] In some embodiments of the present application, S410 may include:

[0300] In the case where the terminal device adopts repeated transmission of PRACH, it is determined whether the random access process is applicable to repeated transmission of Msg3 PUSCH and / or the information carried in the target MCS information field based on the target preamble code in the repeated transmission of PRACH.

[0301] For example, according to the number of the target preamble transmission in the repeated transmission of the PRACH, it is determined whether the random access procedure is applicable to the repeated transmission of the Msg3 PUSCH and / or the information carried in the target MCS information field.

[0302] As an example, if the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, it is determined that the random access procedure is applicable to the repeated transmission of the Msg3 PUSCH.

[0303] As an example, if the number of the target preamble transmission in the repeated transmission of the PRACH does not meet a first threshold, it is determined that the random access procedure is not applicable to the repeated transmission of the Msg3 PUSCH.

[0304] For example, the preambles sent in four repeated PRACH transmissions are numbered 0-3 in order of transmission time. If the network device detects a preamble on an earlier PRACH resource in the repeated PRACH transmissions and indicates the preamble number in the RAR, for example, indicating preamble number 0 or 1, it indicates that repeated transmission of Msg3 PUSCH is not performed. If the network device detects a preamble on a later PRACH resource in the repeated PRACH transmissions and indicates the preamble number in the RAR, for example, indicating preamble number 2 or 3, it indicates that repeated transmission of Msg3 PUSCH is performed.

[0305] In some embodiments of the present application, the method 400 further includes:

[0306] The network device sends a random access response RAR to the terminal device, where the RAR includes first indication information, where the first indication information is used to determine the target preamble code, and where the first indication information is used by the terminal device to determine whether to repeat the transmission of the first PUSCH.

[0307] In some embodiments of the present application, the first indication information is used to indicate at least one of the following:

[0308] Index information of the target preamble;

[0309] Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH;

[0310] a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR;

[0311] The PRACH timing of the target preamble;

[0312] The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

[0313] In some embodiments of the present application, determining the information carried in the target MCS information field according to the number of the target preamble transmission in the repeated transmission of the PRACH includes:

[0314] If the number of the target preamble transmission in the repeated transmission of the PRACH meets the first threshold (ie, it is determined to perform repeated transmission of the Msg3 PUSCH), the target MCS information field carries the number of repeated transmissions of the Msg3 PUSCH.

[0315] In some embodiments, the number of the target preamble transmission in the repeated transmission of the PRACH is also used to determine the number of repeated transmissions of the first PUSCH.

[0316] In some embodiments, the method 400 further includes:

[0317] According to the PRACH resources used by the terminal device to send the PRACH, it is determined whether the terminal device adopts repeated transmission of the PRACH.

[0318] For example, if the network device receives PRACH on the first PRACH resource, and the first PRACH resource associates repeated transmission of PRACH and repeated transmission of Msg3 PUSCH, the network device can determine that the terminal device determines to use repeated transmission of PRACH and requests repeated transmission of Msg3 PUSCH.

[0319] For another example, if the network device receives PRACH on the second PRACH resource, and the second PRACH resource is associated with repeated transmission of PRACH, the network device can determine that the terminal device determines to use repeated transmission of PRACH and does not request repeated transmission of Msg3 PUSCH.

[0320] For another example, if the network device receives PRACH on the third PRACH resource, and the third PRACH resource is associated with repeated transmission of Msg3 PUSCH, the network device can determine that the terminal device requests repeated transmission of Msg3 PUSCH and does not use repeated transmission of PRACH.

[0321] In some embodiments, the method 400 further includes:

[0322] The network device sends first configuration information to the terminal device, where the first configuration information is used to configure a target PRACH resource set, where the target PRACH resource set is associated with repeated transmission of the PRACH and / or repeated transmission of the first PUSCH.

[0323] For example, the target PRACH resource set includes at least one of the following:

[0324] a first PRACH resource set, associating repeated transmission of the PRACH with repeated transmission of the first PUSCH;

[0325] a second PRACH resource set associated with repeated transmission of the PRACH;

[0326] The third PRACH resource set is associated with the repeated transmission of the first PUSCH.

[0327] The above text, in combination with Figures 4 to 8, describes in detail the method embodiment of the present application. The following text, in combination with Figures 9 to 14, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0328] Figure 9 shows a schematic block diagram of a terminal device 1000 according to an embodiment of the present application. As shown in Figure 9, the terminal device 1000 includes: a processing unit 1010, configured to determine, based on first information, whether a random access procedure is applicable to repeated transmission of a first physical uplink shared channel (PUSCH) and / or an interpretation method of a target modulation and coding scheme (MCS) information field, wherein the first PUSCH is used to carry a third message in the random access procedure, and the first information is related to repeated transmission of a physical random access channel (PRACH) in the random access procedure.

[0329] In some embodiments, the first information includes whether the random access procedure is applicable to repeated transmission of PRACH and / or a random access response RAR in the random access procedure.

[0330] In some embodiments, the processing unit 1010 is further configured to:

[0331] According to the first information, it is determined whether to request repeated transmission of the first physical uplink shared channel PUSCH and / or an interpretation method of the target modulation and coding scheme MCS information field.

[0332] In some embodiments, the processing unit 1010 is further configured to:

[0333] In a case where repeated transmission of a PRACH is applicable to the random access procedure, determining to request repeated transmission of the first PUSCH; or

[0334] In a case where repeated transmission of the PRACH is not applicable to the random access procedure, it is determined not to request repeated transmission of the first PUSCH.

[0335] In some embodiments, the processing unit 1010 is further configured to:

[0336] In a case where repeated transmission of the PRACH is applicable to the random access procedure, the number of repeated transmissions of the first PUSCH is determined according to the target MCS information field.

[0337] In some embodiments, the processing unit 1010 is further configured to:

[0338] In the case where repeated transmission of PRACH is applicable to the random access procedure, whether to perform repeated transmission of the first PUSCH and / or the interpretation method of the target MCS information field are determined according to the RAR.

[0339] In some embodiments, the RAR includes first indication information, where the first indication information is used to determine a target preamble code, where the target preamble code is a preamble code in repeated transmission of the PRACH.

[0340] In some embodiments, the first indication information is used to indicate at least one of the following:

[0341] Index information of the target preamble;

[0342] a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR;

[0343] The PRACH timing of the target preamble;

[0344] Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH;

[0345] The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

[0346] In some embodiments, the processing unit 1010 is further configured to:

[0347] Whether to perform repeated transmission of the first PUSCH and / or the method of interpreting the target MCS information field are determined according to the number of the transmission of the target preamble code in the repeated transmission of the PRACH.

[0348] In some embodiments, the processing unit 1010 is further configured to:

[0349] If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, determining to perform repeated transmission of the first PUSCH; or

[0350] If the number of the target preamble transmission in the repeated transmission of the PRACH does not meet a first threshold, it is determined not to perform repeated transmission of the first PUSCH.

[0351] In some embodiments, the processing unit 1010 is further configured to:

[0352] If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, the number of repeated transmissions of the first PUSCH is determined according to the target MCS information field.

[0353] In some embodiments, the number of repeated transmissions of the first PUSCH is determined according to the number of transmissions of the target preamble code in the repeated transmissions of the PRACH.

[0354] In some embodiments, the processing unit 1010 is further configured to:

[0355] According to the measurement result of the downlink signal, it is determined whether the random access process is applicable to repeated transmission of the PRACH.

[0356] In some embodiments, the processing unit 1010 is further configured to:

[0357] When the measurement result of the downlink signal meets a second threshold, determining that repeated transmission of the PRACH is applicable to the random access procedure; or

[0358] If the measurement result of the downlink signal does not meet the second threshold, it is determined that repeated transmission of the PRACH is not applicable to the random access procedure.

[0359] In some embodiments, the processing unit 1010 is further configured to:

[0360] The number of repeated transmissions of the PRACH is determined according to a measurement result of a downlink signal and multiple measurement result ranges, wherein the multiple measurement result ranges respectively correspond to different repeated transmission times of the PRACH, and wherein the multiple measurement result ranges are determined according to multiple thresholds.

[0361] In some embodiments, when the terminal device adopts repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a first PRACH resource, the first PRACH resource belongs to a first PRACH resource set, and the first PRACH resource set associates the repeated transmission of the PRACH and the repeated transmission of the first PUSCH.

[0362] In some embodiments, when the terminal device adopts repeated transmission of PRACH and does not request repeated transmission of the first PUSCH, the PRACH is transmitted through a second PRACH resource, the second PRACH resource belongs to a second PRACH resource set, and the second PRACH resource set is associated with the repeated transmission of the PRACH.

[0363] In some embodiments, when the terminal device does not adopt repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a third PRACH resource, the third PRACH resource belongs to a third PRACH resource set, and the third PRACH resource set is associated with the repeated transmission of the first PUSCH.

[0364] In some embodiments, the target MCS information field is the MCS information field in the uplink grant of the RAR corresponding to the PRACH; or

[0365] The target MCS information field is the MCS information field carried in the downlink control information DCI format 0_0 scrambled by the temporary cell radio network temporary identifier TC-RNTI.

[0366] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0367] It should be understood that the terminal device 1000 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 1000 are respectively for realizing the corresponding processes of the terminal device in the method 200 shown in Figures 4 to 6. For the sake of brevity, they will not be repeated here.

[0368] Figure 10 shows a schematic block diagram of a terminal device 1100 according to an embodiment of the present application. As shown in Figure 10, the terminal device 1100 includes: a processing unit 1110, configured to determine, based on second information, whether repeated transmission of a physical random access channel (PRACH) is applicable to a random access procedure, wherein the second information is related to repeated transmission of a first physical uplink shared channel (PUSCH) during the random access procedure, the first PUSCH being used to carry a third message during the random access procedure.

[0369] In some embodiments, the second information includes whether a condition for requesting repeated transmission of the first PUSCH is met.

[0370] In some embodiments, the processing unit 1110 is further configured to:

[0371] If a condition for requesting repeated transmission of the first PUSCH is met, determining that repeated transmission of the PRACH is applicable to the random access procedure; or

[0372] If a condition for requesting repeated transmission of the first PUSCH is not met, determining that repeated transmission of the PRACH is not applicable to the random access procedure.

[0373] In some embodiments, the processing unit 1110 is further configured to:

[0374] Determine, according to the measurement result of the downlink signal, whether a condition for requesting repeated transmission of the first PUSCH is met.

[0375] In some embodiments, the processing unit 1110 is further configured to:

[0376] When the measurement result of the downlink signal meets a third threshold, determining that a condition for requesting repeated transmission of the first PUSCH is met; or

[0377] When the measurement result of the downlink signal does not meet a third threshold, it is determined that a condition for requesting repeated transmission of the first PUSCH is not met.

[0378] In some embodiments, the number of repeated transmissions of the PRACH is configured by a network device or is predefined.

[0379] In some embodiments, when the terminal device adopts repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a first PRACH resource, the first PRACH resource belongs to a first PRACH resource set, and the first PRACH resource set associates the repeated transmission of the PRACH and the repeated transmission of the first PUSCH.

[0380] In some embodiments, when the terminal device adopts repeated transmission of PRACH and does not request repeated transmission of the first PUSCH, the PRACH is transmitted through a second PRACH resource, the second PRACH resource belongs to a second PRACH resource set, and the second PRACH resource set is associated with the repeated transmission of the PRACH.

[0381] In some embodiments, when the terminal device does not adopt repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a third PRACH resource, the third PRACH resource belongs to a third PRACH resource set, and the third PRACH resource set is associated with the repeated transmission of the first PUSCH.

[0382] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0383] It should be understood that the terminal device 1100 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 1100 are respectively for realizing the corresponding processes of the terminal device in the method 300 shown in Figure 7. For the sake of brevity, they will not be repeated here.

[0384] FIG11 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 1200 of FIG11 includes:

[0385] The processing unit 1210 is used to determine whether the random access process is applicable to the repeated transmission of the first physical uplink shared channel PUSCH and / or the information carried in the target modulation and coding scheme MCS information field based on the third information, wherein the first PUSCH is used to carry the third message in the random access process, and the third information is related to the repeated transmission of the physical random access channel PRACH in the random access process.

[0386] In some embodiments, the third information includes whether the terminal device adopts repeated transmission of PRACH and / or the target preamble code in the repeated transmission of PRACH.

[0387] In some embodiments, the processing unit 1210 is further configured to:

[0388] According to whether the terminal device adopts repeated transmission of PRACH, it is determined whether the terminal device requests repeated transmission of the first PUSCH and / or the information carried in the target MCS information field.

[0389] In some embodiments, the processing unit 1210 is further configured to:

[0390] In a case where the terminal device adopts repeated transmission of the PRACH, determining that the terminal device requests repeated transmission of the first PUSCH; or

[0391] In a case where the terminal device does not adopt repeated transmission of PRACH, it is determined that the terminal device does not request repeated transmission of the first PUSCH.

[0392] In some embodiments, the processing unit 1210 is further configured to:

[0393] In the case where the terminal device adopts repeated transmission of PRACH, determine the number of repeated transmission times of the first PUSCH carried in the target MCS information field.

[0394] In some embodiments, the processing unit 1210 is further configured to:

[0395] In the case where the terminal device adopts repeated transmission of PRACH, it is determined whether the random access process is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field based on the target preamble code in the repeated transmission of the PRACH.

[0396] In some embodiments, the processing unit 1210 is further configured to:

[0397] According to the number of the transmission of the target preamble code in the repeated transmission of the PRACH, it is determined whether the random access process is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field.

[0398] In some embodiments, the processing unit 1210 is further configured to:

[0399] If the number of the transmission of the target preamble in the repeated transmission of the PRACH meets a first threshold, determining that the random access procedure is applicable to the repeated transmission of the first PUSCH; or

[0400] If the number of the transmission of the target preamble code in the repeated transmission of the PRACH does not meet a first threshold, it is determined that the random access procedure is not applicable to the repeated transmission of the first PUSCH.

[0401] In some embodiments, the network device further includes:

[0402] A communication unit is used to send a random access response RAR to a terminal device, where the RAR includes first indication information, where the first indication information is used to determine the target preamble code, and where the first indication information is used by the terminal device to determine whether to repeat the transmission of the first PUSCH.

[0403] In some embodiments, the first indication information is used to indicate at least one of the following:

[0404] Index information of the target preamble;

[0405] Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH;

[0406] a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR;

[0407] The PRACH timing of the target preamble;

[0408] The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

[0409] In some embodiments, the processing unit 1210 is further configured to:

[0410] If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, the target MCS information field is determined to be used to carry the repeated transmission number information of the first PUSCH.

[0411] In some embodiments, the number of the target preamble transmission in the repeated transmission of the PRACH is also used to determine the number of repeated transmissions of the first PUSCH.

[0412] In some embodiments, the processing unit 1210 is further configured to:

[0413] According to the PRACH resources used by the terminal device to send the PRACH, it is determined whether the terminal device adopts repeated transmission of the PRACH.

[0414] In some embodiments, the network device 1100 further includes:

[0415] A communication unit is used to send first configuration information to the terminal device, where the first configuration information is used to configure a target PRACH resource set, and the target PRACH resource set is associated with repeated transmission of PRACH and / or repeated transmission of the first PUSCH.

[0416] In some embodiments, the target PRACH resource set includes at least one of the following:

[0417] a first PRACH resource set, associating repeated transmission of the PRACH with repeated transmission of the first PUSCH;

[0418] a second PRACH resource set associated with repeated transmission of the PRACH;

[0419] The third PRACH resource set is associated with the repeated transmission of the first PUSCH.

[0420] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0421] It should be understood that the network device 1200 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 1200 are respectively for implementing the corresponding processes of the network device in the method 400 shown in Figure 8. For the sake of brevity, they will not be repeated here.

[0422] Figure 12 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in Figure 12 includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0423] Optionally, as shown in FIG12 , the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0424] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0425] Optionally, as shown in FIG12 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0426] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

[0427] Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0428] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0429] Figure 13 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in Figure 13 includes a processor 710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0430] Optionally, as shown in FIG13 , the chip 700 may further include a memory 720 , wherein the processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0431] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0432] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0433] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0434] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0435] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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

[0437] FIG14 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG14 , the communication system 900 includes a terminal device 910 and a network device 920 .

[0438] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0439] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0440] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0441] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0442] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0443] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0444] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0445] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0446] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0447] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0448] The embodiment of the present application also provides a computer program.

[0449] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0450] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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

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

[0453] 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.

[0454] 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.

[0455] 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.

[0456] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0457] 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 the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present 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 determines, based on the first information, whether the random access process is applicable to the repeated transmission of the first physical uplink shared channel PUSCH and / or the interpretation method of the target modulation and coding scheme MCS information field, wherein the first PUSCH is used to carry the third message in the random access process, and the first information is related to the repeated transmission of the physical random access channel PRACH in the random access process.

2. The method according to claim 1, characterized in that The first information includes whether the random access procedure is applicable to repeated transmission of PRACH and / or a random access response RAR in the random access procedure.

3. The method according to claim 2, characterized in that The terminal device determines, based on the first information, whether the random access process is applicable to repeated transmission of the first physical uplink shared channel PUSCH and / or an interpretation method of the target modulation and coding scheme MCS information field, including: The terminal device determines whether to request repeated transmission of the first physical uplink shared channel PUSCH and / or the interpretation method of the target modulation and coding scheme MCS information field based on the first information.

4. The method according to claim 3, characterized in that The terminal device determines, based on the first information, whether to request repeated transmission of a first physical uplink shared channel (PUSCH), including: determining to request repeated transmission of the first PUSCH when repeated transmission of a PRACH is applicable to the random access procedure; or In a case where repeated transmission of the PRACH is not applicable to the random access procedure, it is determined not to request repeated transmission of the first PUSCH.

5. The method according to claim 3 or 4, characterized in that The terminal device determines, according to the first information, a method for interpreting the target modulation and coding scheme MCS information field, including: In a case where repeated transmission of the PRACH is applicable to the random access procedure, the number of repeated transmissions of the first PUSCH is determined according to the target MCS information field.

6. The method according to claim 2, characterized in that The terminal device determines, according to the first information, a method for interpreting the target modulation and coding scheme MCS information field, including: In the case where repeated transmission of PRACH is applicable to the random access procedure, whether to perform repeated transmission of the first PUSCH and / or the interpretation method of the target MCS information field are determined according to the RAR.

7. The method according to claim 6, characterized in that The RAR includes first indication information, where the first indication information is used to determine a target preamble code, where the target preamble code is a preamble code in repeated transmission of the PRACH.

8. The method according to claim 7, characterized in that The first indication information is used to indicate at least one of the following: Index information of the target preamble; a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR; The PRACH timing of the target preamble; Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH; The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

9. The method according to claim 7 or 8, characterized in that The determining, according to the RAR, whether to perform repeated transmission of the first PUSCH and / or a method for interpreting the target MCS information field includes: Whether to perform repeated transmission of the first PUSCH and / or the method of interpreting the target MCS information field are determined according to the number of the transmission of the target preamble code in the repeated transmission of the PRACH.

10. The method according to claim 9, characterized in that The determining, according to the number of the transmission of the target preamble code in the repeated transmission of the PRACH, whether to perform repeated transmission of the first PUSCH includes: If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, determining to perform repeated transmission of the first PUSCH; or If the number of the target preamble transmission in the repeated transmission of the PRACH does not meet a first threshold, it is determined not to perform repeated transmission of the first PUSCH.

11. The method according to claim 9 or 10, characterized in that The determining, according to the number of the target preamble transmission in the repeated transmission of the PRACH, a method for interpreting the target MCS information field includes: If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, the number of repeated transmissions of the first PUSCH is determined according to the target MCS information field.

12. The method according to any one of claims 6 to 10, characterized in that The number of repeated transmissions of the first PUSCH is determined according to the number of the transmission of the target preamble code in the repeated transmissions of the PRACH.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: According to the measurement result of the downlink signal, it is determined whether the random access process is applicable to repeated transmission of the PRACH.

14. The method according to claim 13, characterized in that The determining, according to the downlink signal measurement result, whether the random access procedure is applicable to repeated transmission of the PRACH includes: When the measurement result of the downlink signal meets a second threshold, determining that repeated transmission of the PRACH is applicable to the random access procedure; or If the measurement result of the downlink signal does not meet the second threshold, it is determined that repeated transmission of the PRACH is not applicable to the random access procedure.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: The number of repeated transmissions of the PRACH is determined according to a measurement result of a downlink signal and multiple measurement result ranges, wherein the multiple measurement result ranges respectively correspond to different repeated transmission times of the PRACH, and wherein the multiple measurement result ranges are determined according to multiple thresholds.

16. The method according to any one of claims 1 to 15, characterized in that In the case where the terminal device adopts repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a first PRACH resource, the first PRACH resource belongs to a first PRACH resource set, and the first PRACH resource set associates the repeated transmission of PRACH and the repeated transmission of the first PUSCH.

17. The method according to any one of claims 1 to 15, characterized in that When the terminal device adopts repeated transmission of PRACH and does not request repeated transmission of the first PUSCH, the PRACH is transmitted through a second PRACH resource, the second PRACH resource belongs to a second PRACH resource set, and the second PRACH resource set is associated with repeated transmission of PRACH.

18. The method according to any one of claims 1 to 15, characterized in that In the case that the terminal device does not adopt repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a third PRACH resource, the third PRACH resource belongs to a third PRACH resource set, and the third PRACH resource set is associated with the repeated transmission of the first PUSCH.

19. The method according to any one of claims 1 to 18, characterized in that The target MCS information field is the MCS information field in the uplink grant of the RAR corresponding to the PRACH; or The target MCS information field is the MCS information field carried in the downlink control information DCI format 0_0 scrambled by the temporary cell radio network temporary identifier TC-RNTI.

20. A wireless communication method, characterized in that: include: The terminal device determines whether the random access process is applicable to the repeated transmission of the physical random access channel PRACH based on the second information, wherein the second information is related to the repeated transmission of the first physical uplink shared channel PUSCH in the random access process, and the first PUSCH is used to carry the third message in the random access process.

21. The method according to claim 20, characterized in that The second information includes whether a condition for requesting repeated transmission of the first PUSCH is met.

22. The method according to claim 21, characterized in that The terminal device determines, according to the second information, whether repeated transmission of a physical random access channel (PRACH) is applicable to the random access process, including: If a condition for requesting repeated transmission of the first PUSCH is met, determining that repeated transmission of the PRACH is applicable to the random access procedure; or If a condition for requesting repeated transmission of the first PUSCH is not met, determining that repeated transmission of the PRACH is not applicable to the random access procedure.

23. The method according to any one of claims 20 to 22, characterized in that The method further comprises: The terminal device determines whether the conditions for requesting repeated transmission of the first PUSCH are met based on the measurement result of the downlink signal.

24. The method according to claim 23, wherein The terminal device determines, according to a measurement result of the downlink signal, whether a condition for requesting repeated transmission of the first PUSCH is met, including: When the measurement result of the downlink signal meets a third threshold, determining that a condition for requesting repeated transmission of the first PUSCH is met; or When the measurement result of the downlink signal does not meet a third threshold, it is determined that a condition for requesting repeated transmission of the first PUSCH is not met.

25. The method according to any one of claims 20 to 24, characterized in that The number of repeated transmissions of the PRACH is configured by the network device or is predefined.

26. The method according to any one of claims 20 to 25, characterized in that When the terminal device adopts repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a first PRACH resource, the first PRACH resource belongs to a first PRACH resource set, and the first PRACH resource set associates repeated transmission of PRACH and repeated transmission of the first PUSCH.

27. The method according to any one of claims 20 to 25, characterized in that When the terminal device adopts repeated transmission of PRACH and does not request repeated transmission of the first PUSCH, the PRACH is transmitted through a second PRACH resource, the second PRACH resource belongs to a second PRACH resource set, and the second PRACH resource set is associated with repeated transmission of PRACH.

28. The method according to any one of claims 20 to 25, characterized in that In the case that the terminal device does not adopt repeated transmission of PRACH and requests repeated transmission of the first PUSCH, the PRACH is transmitted through a third PRACH resource, the third PRACH resource belongs to a third PRACH resource set, and the third PRACH resource set is associated with the repeated transmission of the first PUSCH.

29. A wireless communication method, characterized in that: include: The network device determines whether the random access process is applicable to the repeated transmission of the first physical uplink shared channel PUSCH and / or the information carried in the target modulation and coding scheme MCS information field based on the third information, wherein the first PUSCH is used to carry the third message in the random access process, and the third information is related to the repeated transmission of the physical random access channel PRACH in the random access process.

30. The method according to claim 29, wherein The third information includes whether the terminal device adopts repeated transmission of PRACH and / or the target preamble code in the repeated transmission of PRACH.

31. The method according to claim 30, wherein The network device determines, based on the third information, whether the random access process is applicable to repeated transmission of the first physical uplink shared channel PUSCH and / or information carried in the target modulation and coding scheme MCS information field, including: According to whether the terminal device adopts repeated transmission of PRACH, it is determined whether the terminal device requests repeated transmission of the first PUSCH and / or the information carried in the target MCS information field.

32. The method according to claim 31, characterized in that The determining, according to whether the terminal device adopts repeated transmission of the PRACH, whether the terminal device requests repeated transmission of the first PUSCH includes: In a case where the terminal device adopts repeated transmission of the PRACH, determining that the terminal device requests repeated transmission of the first PUSCH; or In a case where the terminal device does not adopt repeated transmission of PRACH, it is determined that the terminal device does not request repeated transmission of the first PUSCH.

33. The method according to claim 31 or 32, characterized in that The determining, according to whether the terminal device adopts repeated transmission of the PRACH, information carried in the target modulation and coding scheme MCS information field includes: In the case where the terminal device adopts repeated transmission of PRACH, determine the number of repeated transmission times of the first PUSCH carried in the target MCS information field.

34. The method according to claim 30, wherein The network device determines, based on the third information, whether the random access process is applicable to repeated transmission of the first physical uplink shared channel PUSCH and / or information carried in the target modulation and coding scheme MCS information field, including: In the case where the terminal device adopts repeated transmission of PRACH, it is determined whether the random access process is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field based on the target preamble code in the repeated transmission of the PRACH.

35. The method according to claim 34, wherein The determining, according to the target preamble in the repeated transmission of the PRACH, whether the random access procedure is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field includes: According to the number of the transmission of the target preamble code in the repeated transmission of the PRACH, it is determined whether the random access process is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field.

36. The method according to claim 35, characterized in that The determining, according to the number of the transmission of the target preamble in the repeated transmission of the PRACH, whether the random access procedure is applicable to the repeated transmission of the first PUSCH and / or the information carried in the target MCS information field includes: If the number of the transmission of the target preamble in the repeated transmission of the PRACH meets a first threshold, determining that the random access procedure is applicable to the repeated transmission of the first PUSCH; or If the number of the transmission of the target preamble code in the repeated transmission of the PRACH does not meet a first threshold, it is determined that the random access procedure is not applicable to the repeated transmission of the first PUSCH.

37. The method according to any one of claims 34 to 36, characterized in that The method further comprises: The network device sends a random access response RAR to the terminal device, where the RAR includes first indication information, where the first indication information is used to determine the target preamble code, and where the first indication information is used by the terminal device to determine whether to repeat the transmission of the first PUSCH.

38. The method according to claim 37, wherein The first indication information is used to indicate at least one of the following: Index information of the target preamble; Number information of the target preamble among multiple preambles, wherein the multiple preambles are preambles sent in repeated transmissions of the PRACH; a random access radio network temporary identifier RA-RNTI of a physical downlink control channel PDCCH, wherein the RA-RNTI is determined according to a resource location of the target preamble, wherein the PDCCH is used to schedule the RAR; The PRACH timing of the target preamble; The transmission sequence number corresponding to the transmission of the target preamble code in the repeated transmission of the PRACH.

39. The method according to any one of claims 34 to 38, wherein: The determining, according to the number of the transmission of the target preamble code in the repeated transmission of the PRACH, information carried in the target MCS information field includes: If the number of the target preamble transmission in the repeated transmission of the PRACH meets a first threshold, the target MCS information field is determined to be used to carry the repeated transmission number information of the first PUSCH.

40. The method according to any one of claims 34 to 38, wherein The number of the target preamble transmission in the repeated transmission of the PRACH is also used to determine the number of repeated transmissions of the first PUSCH.

41. The method according to any one of claims 30 to 40, characterized in that The method further comprises: According to the PRACH resources used by the terminal device to send the PRACH, it is determined whether the terminal device adopts repeated transmission of the PRACH.

42. The method according to any one of claims 29 to 41, wherein The method further comprises: The network device sends first configuration information to the terminal device, where the first configuration information is used to configure a target PRACH resource set, where the target PRACH resource set is associated with repeated transmission of the PRACH and / or repeated transmission of the first PUSCH.

43. The method according to claim 42, characterized in that The target PRACH resource set includes at least one of the following: a first PRACH resource set, associating repeated transmission of the PRACH with repeated transmission of the first PUSCH; a second PRACH resource set associated with repeated transmission of the PRACH; The third PRACH resource set is associated with the repeated transmission of the first PUSCH.

44. A terminal device, characterized in that: include: a processing unit, configured to determine, based on first information, whether the random access process is applicable to repeated transmission of a first physical uplink shared channel PUSCH and / or an interpretation method of a target modulation and coding scheme MCS information field, wherein the first PUSCH is used to carry a third message in the random access process, and the first information is related to repeated transmission of a physical random access channel PRACH in the random access process.

45. A terminal device, characterized in that: include: a processing unit, configured to determine, based on second information, whether the random access procedure is applicable to repeated transmission of a physical random access channel (PRACH), wherein the second information is related to repeated transmission of a first physical uplink shared channel (PUSCH) in the random access procedure, and the first PUSCH is used to carry a third message in the random access procedure.

46. ​​A network device, characterized in that include: a processing unit, configured to determine, based on third information, whether the random access process is applicable to repeated transmission of a first physical uplink shared channel PUSCH and / or information carried in a target modulation and coding scheme MCS information field, wherein the first PUSCH is used to carry a third message in the random access process, and the third information is related to repeated transmission of a physical random access channel PRACH in the random access process.

47. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to perform the method according to any one of claims 1 to 19, or the method according to any one of claims 20 to 28.

48. A network device, characterized in that include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 29 to 43.

49. A chip, characterized in that include: A processor for calling and running a computer program from a memory so that a device equipped with the chip performs the method according to any one of claims 1 to 19, or the method according to any one of claims 20 to 28, or the method according to any one of claims 29 to 43.

50. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 19, or the method according to any one of claims 20 to 28, or the method according to any one of claims 29 to 43.

51. A computer program product, characterized in that Comprising computer program instructions which cause a computer to perform the method of any one of claims 1 to 19, or the method of any one of claims 20 to 28, or the method of any one of claims 29 to 43.

52. A computer program, characterized in that The computer program causes a computer to perform the method of any one of claims 1 to 19, or the method of any one of claims 20 to 28, or the method of any one of claims 29 to 43.

Images