Wireless communication method, terminal device and network device

By including bit-indicating the number of repeated transmissions of PUSCH in the RAR, the problem of inconsistent understanding of the Msg3 PUSCH transmission method by terminal equipment and network equipment is solved, and the transmission reliability and efficiency of the NR system are improved.

CN119071902APending Publication Date: 2024-12-03GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411483828.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-05-28
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the new wireless (NR) system, terminal devices and network devices have inconsistent understanding of the number of repeated transmission information of PUSCH that carry Msg3, resulting in unclear transmission methods.

Method used

The number of repeated transmissions of PUSCH is indicated by including at least one bit in the random access response (RAR), and the terminal device determines the meaning of the bit based on the information associated with the RAR to ensure that the terminal device and the network device have the transmission method Consistent understanding.

Benefits of technology

It effectively solves the problem of understanding consistency of Msg3 PUSCH transmission method and improves transmission reliability and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071902A_ABST
    Figure CN119071902A_ABST
Patent Text Reader

Abstract

A wireless communication method, a terminal device and a network device, the method comprising: a terminal device receiving a random access response (RAR) sent by a network device, the RAR comprising at least one first bit, the at least one first bit being used for indicating the number of repeated transmissions of a physical uplink shared channel (PUSCH), the PUSCH is used for bearing a third message in a random access process; and the terminal device determines, according to first information, whether the at least one first bit indicates the number of repeated transmission times of the PUSCH, the first information being associated with the RAR. Therefore, the terminal device can determine, according to the first information associated with the RAR, whether the at least one first bit in the RAR indicates the repeated transmission frequency information of the PUSCH bearing the Msg3, thereby ensuring that the terminal device and a network device have consistent understanding on the transmission mode of the PUSCH bearing the Msg3.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2021 / 096898 with an application date of May 28, 2021, which entered the Chinese national phase with Chinese patent application number 202180091874.0 and the invention name of “Wireless Communication Methods, Terminal Equipment and Network Equipment”. Technical Field

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

[0003] In the New Radio (NR) system, a four-step random access process can be supported, including the transmission of message 1 (Msg1), message 2 (Msg2), message 3 (Msg3) and message 4 (Msg4). Msg3 is carried by the Physical Uplink Shared Channel (PUSCH), and the uplink grant (UL grant) of the PUSCH of the initial transmission of Msg3 is carried by the Random Access Response (RAR) in Msg2.

[0004] In some scenarios, the reliability of uplink transmission can be improved by repeatedly transmitting the PUSCH carrying Msg3. The number of repeated transmissions of the PUSCH carrying Msg3 can be indicated by the information field in the RAR. In some cases, the terminal device can request the network device to repeatedly transmit the PUSCH carrying Msg3, and the network device can decide whether to schedule the repeated transmission of the PUSCH carrying Msg3. In this case, how the terminal device interprets the information field in the RAR multiplexed to indicate the number of repeated transmissions of the PUSCH to ensure that the network device and the terminal device have a consistent understanding of the transmission method of the PUSCH carrying Msg3 is an urgent problem to be solved. Summary of the invention

[0005] The present application provides a wireless communication method, terminal device and network device. The terminal device can determine whether at least one first bit in the RAR indicates the number of repeated transmissions of the PUSCH carrying Msg3 based on the first information associated with the RAR, thereby ensuring that the terminal device and the network device have a consistent understanding of the transmission method of the PUSCH carrying Msg3.

[0006] In a first aspect, a method for wireless communication is provided, comprising: a terminal device receives a random access response RAR sent by a network device, the RAR comprising at least one first bit, and the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, and the PUSCH is used to carry the third message in the random access process; the terminal device determines, based on first information, whether the at least one first bit indicates the number of repeated transmissions of the PUSCH, wherein the first information is associated with the RAR.

[0007] In a second aspect, a method for wireless communication is provided, comprising: a network device indicates to a terminal device through first information whether at least one first bit in a random access response RAR indicates the number of repeated transmissions of a physical uplink shared channel PUSCH, wherein the first information is associated with the RAR, the at least one first bit can be used to indicate the number of repeated transmissions of the PUSCH, and the PUSCH is used to carry the third message in the random access process.

[0008] In a third aspect, a terminal device is provided for executing the method in the first aspect or its various implementations.

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

[0010] In a fourth aspect, a network device is provided for executing the method in the second aspect or its respective implementation manners.

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

[0012] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.

[0013] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.

[0014] In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or in each of their implementations.

[0015] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the device executes a method as described in any one of the first to second aspects or their respective implementations.

[0016] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0017] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above or in each of their implementations.

[0018] In a tenth 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 in each of their implementations.

[0019] Through the above technical solution, the network device can send a RAR to the terminal device, and at least one first bit in the RAR can be used to indicate the number of repeated transmissions of Msg3 PUSCH. The network device can indicate whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH through the first information associated with the RAR, or in other words, whether the at least one first bit includes the number of repeated transmissions of Msg3 PUSCH. Correspondingly, the terminal device can receive the RAR sent by the network device, and further determine whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH according to the first information associated with the RAR, or in other words, whether the at least one first bit includes the number of repeated transmissions of Msg3 PUSCH, and further transmit the Msg3 PUSCH according to the transmission mode of Msg3 PUSCH indicated by the network device, thereby ensuring that the network device and the terminal device have a consistent understanding of the transmission mode of Msg3 PUSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0021] Figure 2 It is a schematic interaction diagram of a wireless communication method provided according to an embodiment of the present application.

[0022] Figure 3 This is a schematic diagram of different transmission modes of indicating Msg3 through different RA-RNTIs.

[0023] Figure 4 It is a schematic diagram of different transmission modes of requesting Msg3 by indicating the reserved bit in the PDCCH for scheduling RAR.

[0024] Figure 5 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0025] Figure 6 It is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0026] Figure 7 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0027] Figure 8 It is a schematic block diagram of a chip provided according to an embodiment of the present application.

[0028] Fig. 9 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

[0031] 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 (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type 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.

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

[0033] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein 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, wherein the authorized spectrum can also be considered as an unshared spectrum.

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

[0035] The terminal device can be a station (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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0036] In the embodiments 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 (for example, on airplanes, balloons and satellites, etc.).

[0037] In the embodiment of the present application, the terminal device can 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.

[0038] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as 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 powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices 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 types of smart bracelets and smart jewelry for vital sign monitoring.

[0039] 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 (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, 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.

[0040] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, 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.

[0041] 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), and 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.

[0042] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 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 geographical area and may communicate with terminal devices located in the coverage area.

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

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

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

[0046] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

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

[0048] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0049] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0050] 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 the present application does not limit this.

[0051] In the NR system, the network device can send an uplink grant (UL grant) to schedule PUSCH transmission. The uplink grant is carried by downlink control information (DCI) format 0_0 or DCI format 0_1.

[0052] In some cases, when a network device schedules uplink data transmission through a DCI carrying a UL grant, a time domain resource assignment (TDRA) field is carried in the DCI. The TDRA field can be, for example, 4 bits, which is used to indicate 16 rows in a time domain resource allocation table. Each row contains different resource allocation combinations, such as the starting position S of the PUSCH, the length L, k2, and different types. Among them, k2 represents the number of offset slots between the slot where the DCI is located and the slot where the PUSCH is located. The Type of PUSCH time domain resource allocation includes Type A and Type B. The difference between Type A and Type B is that the value ranges of the S and L candidate values ​​corresponding to the two methods are different. Type A is mainly for slot-based services, S is relatively forward, and L is relatively long. Type B is mainly for Ultra-Reliable and Low Latency Communication (URLLC) services, which have high requirements for latency, so the position of S is more flexible to transmit URLLC services that arrive at any time, and L is shorter, which can reduce transmission latency. As an example, the candidate value ranges of S and L are shown in Table 1 below.

[0053] Table 1

[0054]

[0055] In addition to the above-mentioned time domain resource allocation information, the DCI carrying the UL grant may also include frequency domain resource information, modulation and coding scheme (MCS), transmission power control (TPC) command, frequency hopping information, redundant version, hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process number, etc., which will not be repeated here.

[0056] In the NR system, in order to support URLLC services, uplink data transmission repetition is used to improve transmission reliability. PUSCH repetition transmission includes two types: PUSCH repetition Type A and PUSCH repetition Type B. The PUSCH repetition type is determined by high-level signaling. For PUSCH repetition Type A and Type B, the time domain resource allocation method of PUSCH is different.

[0057] For example, for PUSCH repetition Type A, the starting symbol S of the PUSCH and the number of consecutive symbols L starting from the symbol S are determined by the SLIV indicated in the PDCCH that schedules the PUSCH.

[0058] For PUSCH repetition Type B, the starting symbol S of the PUSCH and the number of consecutive symbols L starting from the symbol S are respectively determined by the starting symbol (startSymbol) and length (length) information corresponding to the row in the time domain resource allocation table.

[0059] In Release 16 (R16), PUSCH-TimeDomainResourceAllocationList-r16 is introduced to support the time domain resource allocation information of PUSCH retransmission, such as the symbol where PUSCH is located (such as the starting symbol and length), the number of retransmissions K (numberOfRepetitions) of PUSCH, etc. The terminal device determines the time domain resources for PUSCH retransmission based on the above information and the PUSCH repetition Type determined by high-level signaling.

[0060] In the NR system, a four-step random access process can be supported, including the transmission of message 1 (Msg1), message 2 (Msg2), message 3 (Msg3) and message 4 (Msg4). Among them, Msg3 is carried by PUSCH, and the UL grant of PUSCH for the initial transmission of Msg3 is carried by the random access response (Random Access Response, RAR) in Msg2. As shown in Table 2, the UL grant information in RAR includes the time domain and frequency domain resource allocation information of PUSCH, power control command TPC, frequency hopping, and MCS, etc.

[0061] Table 2

[0062]

[0063]

[0064] If the network device does not correctly receive the Msg3 of the terminal device, it will use the DCI indication to indicate the scheduling information for retransmitting Msg3. For example, the scheduling information is carried by the DCI format 0_0 scrambled by the temporary cell radio network temporary identifier (Temporary Cell Radio Network Temporary Identity, TC-RNTI). In addition to the content contained in the UL grant information in the RAR, the DCI format 0_0 may also include a new data indication (New Data Indicator, NDI), a redundant version, a HARQ process number and other information.

[0065] In some embodiments, the network device may reuse the information field in the UL grant information in the RAR to indicate the number of repeated transmissions of Msg3, for example, through a TDRA field, or through a PUSCH frequency domain resource allocation field.

[0066] In some cases, the terminal device can request the network device to retransmit Msg3, and the network device can decide whether to schedule the retransmission of Msg3. That is to say, in some cases, the network device schedules the retransmission of Msg3, in which case it is necessary to indicate the number of retransmissions of Msg3. In some cases, the network device does not schedule the retransmission of Msg3, in which case it is not necessary to indicate the number of retransmissions of Msg3. The terminal device does not know whether the network device agrees to its request. Therefore, how the terminal device interprets the information field in RAR that is multiplexed to indicate the number of retransmissions of PUSCH to ensure that the network device and the terminal device have a consistent understanding of the transmission method of Msg3 is an urgent problem to be solved.

[0067] 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 above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0068] Figure 2 is a schematic interaction diagram of a wireless communication method 200 according to an embodiment of the present application, such as Figure 2 As shown, the method 200 includes at least part of the following:

[0069] S210, the terminal device receives a random access response RAR sent by the network device, where the RAR includes at least one first bit, where the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, where the PUSCH is used to carry the third message (i.e., Msg3) in the random access process;

[0070] S220, the terminal device determines whether the at least one first bit indicates the number of repeated transmissions of the PUSCH based on first information, wherein the first information is associated with the RAR.

[0071] In the embodiment of the present application, the RAR is used to schedule the transmission of Msg3, for example, to schedule the initial transmission of Msg3, and the RAR includes Ul grant information for the initial transmission of Msg3.

[0072] In the embodiment of the present application, the RAR used to schedule the transmission of Msg3 may refer to the RAR used to schedule the transmission of the PUSCH carrying Msg3.

[0073] In this embodiment of the present application, the PUSCH carrying Msg3 may also be referred to as Msg3 PUSCH.

[0074] In some embodiments, the terminal device may request the network device to retransmit Msg3, or in other words, request the network device to retransmit PUSCH carrying Msg3.

[0075] In some embodiments, the terminal device indicates to the network device via a first message whether the terminal device requests repeated transmission of Msg3 PUSCH, wherein the first message is the first message in the random access process, namely Msg1, or a random access preamble.

[0076] For example, the terminal device indicates to the network device whether the terminal device requests repeated transmission of Msg3 PUSCH through at least one of a random access preamble code, an initial uplink bandwidth part (Band Width Part, BWP) for sending the first message, and a physical random access channel (Physical Random Access Channel, PRACH) resource for sending the first message.

[0077] In some embodiments, the PRACH resources may include PRACH occasion (RO) resources.

[0078] As an example, the network device may configure the terminal device with a Preamble or Preamble group used for requesting repeated transmission of Msg3 PUSCH, and a Preamble or Preamble group used for not requesting repeated transmission of Msg3 PUSCH. When the terminal device needs to request repeated transmission of Msg3 PUSCH, it sends the corresponding Preamble or the Preamble in the corresponding Preamble group.

[0079] As another example, the network device may configure the terminal device with an initial uplink BWP used for requesting repeated transmission of Msg3 PUSCH and an initial uplink BWP used for not requesting repeated transmission of Msg3 PUSCH. When the terminal device needs to request repeated transmission of Msg3 PUSCH, it sends a Preamble on the corresponding initial uplink BWP.

[0080] As another example, the network device may configure the terminal device with RO resources used for requesting repeated transmission of Msg3 PUSCH and RO resources used for not requesting repeated transmission of Msg3 PUSCH. When the terminal device needs to request repeated transmission of Msg3 PUSCH, it sends the Preamble on the corresponding RO resources.

[0081] In some embodiments, the network device may decide whether to agree to the request of the terminal device, or whether to schedule repeated transmission of the carrying Msg3, or whether to schedule repeated transmission of the PUSCH carrying Msg3.

[0082] For example, the network device may not schedule repeated transmission of Msg3 when the channel condition of the terminal device is relatively good, and may schedule repeated transmission of Msg3 when the channel condition of the terminal device is relatively poor.

[0083] In an embodiment of the present application, the RAR may include at least one first bit, and the at least one first bit may be used to indicate the number of repeated transmissions of the PUSCH carrying Msg3.

[0084] It should be understood that the at least one first bit can be used to indicate the number of repeated transmissions of the PUSCH carrying Msg3, which can mean that the at least one first bit can be used to indicate the number of repeated transmissions of the Msg3 PUSCH, but it cannot indicate the number of repeated transmissions of the Msg3 PUSCH in any case. That is, the at least one first bit can indicate the number of repeated transmissions of the Msg3 PUSCH in some cases, and may not indicate the number of repeated transmissions of the Msg3 PUSCH in other cases.

[0085] In some embodiments, the at least one first bit comprises at least one bit in a first information field in the RAR. Optionally, the first information field may comprise one or more information fields in the RAR.

[0086] In some embodiments, the first information field includes at least one information field in the uplink grant information in the RAR. That is, the at least one first bit may include at least one bit in the uplink grant information of the RAR.

[0087] For example, the first information field may include at least one information field shown in Table 2. That is, the at least one first bit includes at least one bit in the at least one information field shown in Table 2.

[0088] As an example, the first information field includes one or more information fields of PUSCH frequency domain resource allocation information, MCS, TPC for PUSCH, ChannelAccess-CPext and CSI request information fields in the uplink grant information in the RAR. That is, the at least one first bit includes one or more bits of one or more information fields of PUSCH frequency domain resource allocation information, MCS, TPC for PUSCH, ChannelAccess-CPext and CSI request information fields in the uplink grant information in the RAR.

[0089] In other words, the network device can reuse the PUSCH frequency domain resource allocation information, MCS, TPC field for PUSCH, ChannelAccess-CPext and CSI request information field in the RAR to indicate the number of repeated transmissions of Msg3 PUSCH.

[0090] As another example, the first information field includes a PUSCH time domain resource allocation information field in the uplink grant information in the RAR, that is, a TDRA information field. For example, the at least one first bit includes at least one bit in the TDRA information field in the uplink grant information in the RAR.

[0091] In other words, the network device may reuse at least one bit in the TDRA information field in the uplink grant information in the RAR to indicate the number of repetition transmissions of the Msg3 PUSCH.

[0092] In some other embodiments, the network device may multiplex one or more bits in other information fields except the UL grant information in the RAR to indicate the number of repeated transmissions of the Msg3 PUSCH.

[0093] In an embodiment of the present application, the RAR is included in a Media Access Control Protocol Data Unit (MAC PDU), and a MAC PDU includes a MAC PDU header, at least one MAC sub-PDU, and possible padding bits.

[0094] Among them, a MAC subPDU may include a MAC subPDU subheader (subheader), and a MACsubPDU subheader may correspond to a MAC service data unit (service data unit, SDU) or a MAC control element (MAC Control Element, MAC CE) or padding bits.

[0095] In some further embodiments, the network device may reuse information in the MAC PDU carrying the RAR to indicate the number of repeated transmissions of the Msg3PUSCH. For example, the header of the MAC PDU may be reused, or the subheader of the MAC subPDU in the MAC PDU may indicate the number of repeated transmissions of the Msg3PUSCH. That is, the at least one first bit may include one or more bits in the MAC PDU carrying the RAR.

[0096] In the following, the at least one first bit includes at least one bit in the RAR, which is described as an example, but the present application is not limited to this.

[0097] In summary, in the embodiments of the present application, the at least one first bit has a first meaning in some cases, and the first meaning is the meaning when Msg3 is not transmitted repeatedly, or, in other words, the original meaning of the at least one first bit before the at least one first bit is multiplexed to indicate the number of repeated transmissions of Msg3PUSCH; the at least one first bit has a second meaning in other cases, and the at least one first bit is at least used to indicate the number of repeated transmissions of Msg3 PUSCH. For example, in addition to indicating the number of repeated transmissions of Msg3 PUSCH, the at least one first bit is also used to indicate the information content that needs to be indicated in the original meaning.

[0098] In some embodiments of the present application, the terminal device may determine the meaning or interpretation of the at least one first bit based on the first information associated with the RAR, for example, the meaning of the at least one first bit is the first meaning or the second meaning, and for example, the at least one first bit is interpreted according to the first meaning or the second meaning. Alternatively, the first information is used to determine whether the at least one first bit indicates the number of repeated transmissions of the Msg3 PUSCH, or in other words, the first information is used to determine whether the at least one first bit includes information on the number of repeated transmissions of the Msg3 PUSCH, or in other words, the first information is used to determine the transmission mode of the Msg3PUSCH, such as repeated transmission of Msg3 PUSCH or non-repeated transmission of Msg3 PUSCH.

[0099] It should be understood that in the embodiment of the present application, the first information associated with the RAR may include but is not limited to the following information: information included in the RAR, relevant information of the PDCCH that schedules the RAR, and other downlink information received before the RAR during this random access process.

[0100] Therefore, in an embodiment of the present application, the network device can indicate to the terminal device whether the at least one first bit in the RAR indicates the number of repeated transmissions of the Msg3 PUSCH, or the transmission mode of the Msg3 PUSCH, through the first information associated with the RAR.

[0101] Correspondingly, after receiving the RAR, the terminal device can determine whether the at least one first bit in the RAR indicates the number of repeated transmissions of the Msg3 PUSCH, or the transmission mode of the Msg3PUSCH, based on the first information associated with the RAR, and further transmit the Msg3 PUSCH according to the transmission mode of the Msg3 PUSCH indicated by the network device, thereby ensuring that the network device and the terminal device have a consistent understanding of the transmission mode of the Msg3 PUSCH.

[0102] The specific implementation of the first information is described below in conjunction with a specific embodiment.

[0103] Embodiment 1: The first information includes at least one second bit in the RAR, and the at least one second bit is different from the at least one first bit.

[0104] It should be understood that the at least one second bit being different from the at least one first bit may mean that the at least one first bit and the at least one second bit are located in different positions in the RAR, for example, the at least one first bit and the at least one second bit are located in different information domains in the RAR, or the at least one first bit and the at least one second bit are different bit positions in the same information domain.

[0105] That is, the network device may indicate whether the at least one first bit indicates the number of repeated transmissions of the Msg3 PUSCH through other bit information except the at least one first bit in the RAR.

[0106] Correspondingly, the terminal device can determine whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH based on other bit information in the RAR except the at least one first bit, and further transmit Msg3 PUSCH according to the transmission mode of Msg3 PUSCH indicated by the network device.

[0107] It should be understood that the at least one second bit may be any one or more bits in the RAR that are different from the at least one first bit, and this application does not limit this.

[0108] In some embodiments, the at least one second bit comprises at least one bit in a second information field in the RAR. Optionally, the second information field may comprise one or more information fields in the RAR.

[0109] In some embodiments, the second information field includes at least one information field in the uplink grant information in the RAR. That is, the at least one second bit may include at least one bit in the uplink grant information of the RAR.

[0110] For example, the second information field may include at least one of the information fields shown in Table 2. That is, the at least one second bit includes at least one bit in the at least one information field shown in Table 2.

[0111] As an example, the second information field includes one or more information fields of PUSCH frequency domain resource allocation information, MCS, TPC for PUSCH, ChannelAccess-CPext and CSI request information fields in the uplink grant information in the RAR. That is, the at least one second bit includes one or more bits of one or more information fields of PUSCH frequency domain resource allocation information, MCS, TPC for PUSCH, ChannelAccess-CPext and CSI request information fields in the uplink grant information in the RAR.

[0112] As another example, the second information field includes a PUSCH time domain resource allocation information field in the uplink grant information in the RAR, that is, a TDRA information field. For example, the at least one second bit includes at least one bit in the TDRA information field in the uplink grant information in the RAR.

[0113] In some other embodiments, the network device may indicate whether the at least one first bit indicates the number of repeated transmissions of the Msg3 PUSCH through one or more bits in other information fields except the UL grant information in the RAR.

[0114] In some embodiments of the present application, the at least one second bit and the at least one first bit are carried in the same information field in the RAR.

[0115] In some embodiments, the at least one second bit and the at least one first bit are both carried in the same information field in the UL grant in the RAR.

[0116] As an example, the at least one first bit and the at least one second bit are both carried in the TDRA information field in the UL grant in the RAR.

[0117] For example, the at least one second bit takes a first value indicating that the at least one first bit indicates the number of repeated transmissions of Msg3PUSCH, and the at least one second bit takes a second value indicating that the at least one first bit does not indicate the number of repeated transmissions of Msg3PUSCH.

[0118] It should be understood that, when the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH, the at least one first bit includes the information of the number of repeated transmissions of Msg3 PUSCH, in which case the terminal device can determine the number of repeated transmissions of Msg3 PUSCH based on the at least one first bit; when the at least one first bit does not indicate the number of repeated transmissions of Msg3 PUSCH, the at least one first bit does not include the information of the number of repeated transmissions of Msg3 PUSCH, in which case the terminal device does not determine the number of repeated transmissions of Msg3 PUSCH based on the at least one first bit.

[0119] In some other embodiments of the present application, the at least one second bit and the at least one first bit are carried in different information fields in the RAR.

[0120] In some embodiments, the at least one second bit and the at least one first bit are carried in different information fields in the UL grant information in the RAR.

[0121] In some embodiments, the at least one first bit is carried in at least one information field among the PUSCH time domain resource allocation, PUSCH frequency domain resource allocation, MCS, TPC command for PUSCH, ChannelAccess-CPext information field and CSI request information field in the UL grant information, and the at least one second bit is carried in other information fields in the UL grant information except the at least one information field.

[0122] As an example, the at least one first bit includes at least one bit in the TDRA information field in the UL grant in the RAR, and the at least one second bit may include at least one bit in other information fields in the UL grant in the RAR except the TDRA information field. For example, the at least one second bit may include at least one bit in at least one of the information fields of PUSCH frequency domain resource allocation, MCS, TPC for PUSCH, ChannelAccess-CPext, and CSI request in the UL grant.

[0123] Taking the at least one first bit being implemented through the TDRA information field as an example, the at least one second bit is used to indicate whether the at least one first bit indicates the number of repeated transmissions of the PUSCH, and may include:

[0124] The at least one second bit is used to indicate the meaning of the TDRA information field, for example, whether the TDRA information field is interpreted according to the time domain resource allocation information or according to the time domain resource allocation information and the number of repeated transmissions; or,

[0125] The value of the TDRA information field is interpreted according to the first TDRA list information or the second TDRA list information, wherein the first TDRA list information includes time domain resource allocation information but does not include repeated transmission number information, and the second TDRA list information includes time domain resource allocation information and repeated transmission number information.

[0126] Optionally, the first TDRA list information may include multiple rows, each row including a set of resource allocation information.

[0127] Optionally, the second TDRA list information may include multiple rows, each row including a group of resource allocation information and repeated transmission information.

[0128] Optionally, the first TDRA list information may be pre-configured or configured by a network device, for example, may be configured through a common PUSCH configuration (pusch-ConfigCommon).

[0129] Optionally, the second TDRA list information may be pre-configured or configured by a network device, for example, may be configured through a common PUSCH configuration (pusch-ConfigCommon).

[0130] Take the example that the TDRA information field includes 4 bits, the at least one first bit includes 4 bits of the TDRA information field, and the at least one second bit includes 1 bit in the CSI request information field. When the value of the 1-bit information in the CSI request information field is the first value, such as 0, it means that the TDRA information field indicates the number of repeated transmissions of the Msg3PUSCH. In this case, the TDRA information field is used to determine both the number of repeated transmissions of the Msg3 PUSCH and the time domain resource allocation information of the Msg3 PUSCH. The terminal device can determine the number of repeated transmissions of the Msg3 PUSCH and the time domain resource allocation information according to the second TDRA list information. When the value of the 1-bit information in the CSI request information field is the second value, for example 1, it means that the TDRA information field does not indicate the number of repeated transmissions of the Msg3PUSCH. In this case, the TDRA information field is used to determine the time domain resource allocation information of the Msg3 PUSCH, but is not used to determine the number of repeated transmissions of the Msg3PUSCH. The terminal device can determine the time domain resource allocation information of the Msg3 PUSCH based on the first TDRA list information.

[0131] Therefore, in this embodiment 1, for the terminal device that requests repeated transmission of Msg3 PUSCH, it can be determined based on the value of at least one second bit whether the network device has scheduled repeated transmission of Msg3 PUSCH, that is, the transmission mode of Msg3 PUSCH configured by the network device, so that the meaning or interpretation method of the at least one first bit can be determined, and further, the Msg3 PUSCH can be transmitted according to the transmission mode of Msg3PUSCH indicated by the network device, which is conducive to ensuring that the network device and the terminal device have a consistent understanding of the transmission mode of Msg3 PUSCH.

[0132] Embodiment 2: The first information includes a random access RNTI (Random Access RNTI, RA-RNTI) corresponding to a physical downlink control channel PDCCH that schedules the RAR.

[0133] In this embodiment 2, the RA-RNTI of the PDCCH that schedules the RAR is determined according to the first identification information, and the first identification information is related to the transmission mode of the Msg3 PUSCH determined by the network device.

[0134] Optionally, the transmission mode of the PUSCH includes repeated transmission of PUSCH and non-repeated transmission of PUSCH.

[0135] Optionally, for different transmission modes of Msg3 PUSCH, the first identification information corresponds to different values. In this way, when the network device schedules different transmission modes of Msg3 PUSCH, the RA-RNTI determined according to the first identification information is also different. That is to say, the network device can indicate whether to schedule repeated transmission of Msg3 PUSCH through different RA-RNTIs. Correspondingly, the terminal device can determine whether the network device has scheduled repeated transmission of Msg3 PUSCH based on the RA-RNTI received from the PDCCH.

[0136] In some embodiments of the present application, the RA-RNTI is used to scramble the cyclic redundancy check (CRC) of the PDCCH.

[0137] In some embodiments, the terminal device determines the RA-RNTI corresponding to the PDCCH scheduling the RAR according to the following formula (1):

[0138] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×Q formula (1)

[0139] Wherein, Q is the first identification information;

[0140] s_id is the index of the first orthogonal frequency division multiplexing OFDM symbol occupied by the physical random access channel PRACH resource;

[0141] t_id is the index of the first time slot occupied by the PRACH resource;

[0142] f_id is the index of the PRACH resource in the frequency domain;

[0143] ul_carrier_id is the uplink carrier where the PRACH resource is located.

[0144] Optionally, if the network device determines to schedule repeated transmission of Msg3 PUSCH, Q takes a third value, and a first RA-RNTI is generated, or, if the network device determines not to schedule repeated transmission of Msg3 PUSCH, Q takes a fourth value, and a second RA-RNTI is generated, wherein the third value and the fourth value are not equal. As an example, the third value is not 0, and the fourth value is zero.

[0145] Correspondingly, the terminal device may also generate a first RA-RNTI and a second RNTI respectively according to the third value and the fourth value of Q, further receive PDCCH according to the first RA-RNTI and the second RA-RNTI, and determine whether the network device has scheduled repeated transmission of Msg3 PUSCH according to the RA-RNTI of the successfully received PDCCH. For example, if PDCCH is successfully received according to the first RA-RNTI, it indicates that the network device has scheduled repeated transmission of Msg3 PUSCH, or, if PDCCH is successfully received according to the second RA-RNTI, it indicates that the network device has not scheduled repeated transmission of Msg3 PUSCH.

[0146] It should be understood that in the embodiment of the present application, the network device not scheduling repeated transmission of Msg3 PUSCH may mean that the network device schedules non-repeated transmission of Msg3 PUSCH.

[0147] In some embodiments, regardless of whether the terminal device requests repeated transmission of Msg3 PUSCH, the RA-RNTI is determined according to formula (1).

[0148] In some embodiments, for a terminal device that requests repeated transmission of Msg3 PUSCH, the RA-RNTI of the PDCCH that schedules the RAR is determined according to the following formula (2):

[0149] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×Q formula (2)

[0150] Wherein, Q is the first identification information;

[0151] s_id is the index of the first orthogonal frequency division multiplexing OFDM symbol occupied by the physical random access channel PRACH resource;

[0152] t_id is the index of the first time slot occupied by the PRACH resource;

[0153] f_id is the index of the PRACH resource in the frequency domain;

[0154] ul_carrier_id is the uplink carrier where the PRACH resource is located.

[0155] In some embodiments, for a terminal device that does not request repeated transmission of Msg3 PUSCH, the RA-RNTI of the PDCCH that schedules the RAR is determined according to the following formula (2):

[0156] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id formula (3)

[0157] Wherein, s_id is the index of the first orthogonal frequency division multiplexing OFDM symbol occupied by the physical random access channel PRACH resource;

[0158] t_id is the index of the first time slot occupied by the PRACH resource;

[0159] f_id is the index of the PRACH resource in the frequency domain;

[0160] ul_carrier_id is the uplink carrier where the PRACH resource is located.

[0161] In some embodiments, when a terminal device requesting repeated transmission of Msg3 PUSCH determines the RA-RNTI according to formula (2), and a terminal device not requesting repeated transmission of Msg3 PUSCH determines the RA-RNTI according to formula (3), the Q is not equal to 0, or the Q is not equal to 0 and not equal to 1, so as to distinguish the RA-TNTI of a terminal device requesting repeated transmission of Msg3 PUSCH from the RA-RNTI of a terminal device not requesting repeated transmission of Msg3 PUSCH, or to distinguish the RA-TNTI of a terminal device requesting repeated transmission of Msg3 PUSCH from the RA-RNTI of a terminal device not requesting repeated transmission of Msg3 PUSCH and the MSGB-RNTI of a terminal device not requesting repeated transmission of Msg3 PUSCH.

[0162] Based on the implementation method in Example 2, the RA-RNTI corresponding to the PDCCH of the RAR that schedules repeated transmission of Msg3 PUSCH is different from that of the PDCCH of the RAR that does not schedule repeated transmission of Msg3 PUSCH. Therefore, the terminal device that requests repeated transmission of Msg3 PUSCH can determine whether the at least one first bit in the RAR indicates the number of repeated transmissions of Msg3 PUSCH, or whether the network device has scheduled the repeated transmission of Msg3 PUSCH, or whether the network device has configured the number of repeated transmissions of Msg3 PUSCH.

[0163] Combination Figure 3For example, for terminal devices that share RO resources, different Preambles can be used to distinguish whether repeated transmission of Msg3PUSCH is requested. For example, Preamble 1 is a Preamble configured by the network device to request repeated transmission of Msg3 PUSCH. The terminal device can send Preamble 1 on the shared RO. After receiving Preamble 1, the network device can determine that the terminal device has requested repeated transmission of Msg3 PUSCH.

[0164] Further, if the network device decides to schedule repeated transmission of Msg3 PUSCH, the CRC of PDCCH is encrypted through RA-RNTI 1 to indicate to the terminal device that the network device has scheduled repeated transmission of Msg3 PUSCH, or the at least one first bit indicates the number of repeated transmissions of Msg3PUSCH.

[0165] Alternatively, if the network device decides not to schedule repeated transmission of Msg3 PUSCH, the CRC of PDCCH is encrypted through RA-RNTI 2 to indicate to the terminal device that the network device does not schedule repeated transmission of Msg3 PUSCH, or the at least one first bit does not indicate the number of repeated transmissions of Msg3PUSCH.

[0166] Furthermore, the terminal device can receive the RAR sent by the network device in the RAR receiving window. If the RAR is successfully received according to RA-RNTI 1, it can be determined that the network device has scheduled the repeated transmission of Msg3 PUSCH. Alternatively, if the RAR is successfully received according to RA-RNTI 2, it can be determined that the network device has not scheduled the repeated transmission of Msg3 PUSCH, or has scheduled the non-repeated transmission of Msg3PUSCH.

[0167] Embodiment 3: The first information includes information in the PDCCH that schedules the RAR.

[0168] It should be understood that in Embodiment 3, the first information may be any information in the PDCCH for scheduling RAR, and the present application does not specifically limit the position and number of bits of the information.

[0169] As an example, the network device may reuse at least one bit in the information field with existing meaning in the PDCCH to indicate whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH, or may also indicate whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH through at least one reserved bit in the PDCCH.

[0170] In some embodiments, the first information includes at least one reserved bit in the PDCCH that schedules the RAR. The at least one reserved bit can be used to indicate how the terminal device that has requested repeated transmission of the Msg3 PUSCH interprets the at least one first bit in the RAR.

[0171] In some embodiments, whether the terminal device has requested repeated transmission of Msg3 PUSCH can be determined by the Preamble sent by the terminal device or the Preamble set corresponding to the Preamble sent by the terminal device. For a terminal device that requests repeated transmission of Msg3 PUSCH through different Preambles or different Preamble sets, the network device can indicate whether the at least one first bit in the RAR corresponding to the different Preamble or different Preamble sets indicates the number of repeated transmissions of Msg3 PUSCH, or whether the network device has scheduled the repeated transmission of Msg3 PUSCH, or whether the network device has configured the number of repeated transmissions of Msg3 PUSCH.

[0172] As an example, the first information includes multiple reserved bit groups, each reserved bit group includes at least one reserved bit, each reserved bit group corresponds to a Preamble or a Preamble group, and the value of each reserved bit group is used to indicate whether the at least one first bit in the Preamble corresponding to each reserved bit group or the RAR corresponding to the Preamble group indicates the number of repeated transmissions of Msg3 PUSCH, or whether the network device has scheduled the repeated transmission of Msg3 PUSCH, or whether the network device has configured the repeated transmission number information of Msg3 PUSCH.

[0173] Optionally, the RAR corresponding to the Preamble or the Preamble group may refer to the RAR that carries response information of a terminal device that sends the Preamble or the Preamble in the Preamble group.

[0174] Optionally, the Preambles or Preamble groups corresponding to the multiple reserved bit groups are all Preambles or Preamble groups used by the terminal device to request repeated transmission of Msg3PUSCH.

[0175] Combination Figure 4For example, the first information includes four reserved bit groups, corresponding to four indication subfields in the DCI, indication subfield 1 to indication subfield 4, each indication subfield corresponds to a Preamble or a Preamble group, and the value of each indication subfield is used to indicate whether the at least one first bit in the RAR corresponding to the corresponding Preamble or Preamble group indicates the number of repeated transmissions of Msg3 PUSCH.

[0176] For example, each indication subfield includes 1 bit, and the value of the 1 bit is used to indicate whether the at least one first bit in the RAR corresponding to the corresponding Preamble or Preamble group indicates the number of repeated transmissions of the Msg3 PUSCH.

[0177] As an example, the value of the indication subfield is 0, indicating that the at least one first bit in the RAR does not indicate the number of repeated transmissions of Msg3PUSCH. In this case, the terminal device that uses the Preamble or Preamble group corresponding to the request for repeated transmission of Msg3 PUSCH does not perform repeated transmission of Msg3PUSCH.

[0178] As an example, the value of the indication sub-domain is 1, indicating that the at least one first bit in the RAR carries the information of the number of repeated transmissions of Msg3PUSCH, and the terminal device of the Preamble or Preamble group corresponding to the request for repeated transmission of Msg3 PUSCH is used to perform repeated transmission of Msg3PUSCH.

[0179] Embodiment 4: The first information includes information in the MAC PDU carrying the RAR.

[0180] In some embodiments, the RAR is included in a MAC PDU, where a MAC PDU includes a MAC PDU header, 0 or at least one MAC sub-PDU, and possible padding bits.

[0181] A MAC subPDU may include a MAC subPDU subheader, and a MAC subPDU subheader may correspond to a MAC service data unit (SDU) or a MAC control element (MAC Control Element, MAC CE) or padding bits.

[0182] In some embodiments, the at least one second bit may be included in a MAC PDU carrying the RAR, for example, carried in a header of the MAC PDU, or carried in a subheader of a MAC subPDU in the MAC PDU.

[0183] In summary, the network device can send a RAR to the terminal device, and at least one first bit in the RAR can be used to indicate the number of repeated transmissions of Msg3PUSCH. The network device can indicate whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH through the first information associated with the RAR, or in other words, whether the at least one first bit includes the number of repeated transmissions of PUSCH. Correspondingly, the terminal device can receive the RAR sent by the network device, and further determine whether the at least one first bit indicates the number of repeated transmissions of Msg3 PUSCH according to the first information associated with the RAR, or in other words, whether the at least one first bit includes the number of repeated transmissions of PUSCH, and then transmit the Msg3 PUSCH according to the transmission mode of Msg3 PUSCH indicated by the network device, thereby ensuring that the network device and the terminal device have a consistent understanding of the transmission mode of Msg3 PUSCH.

[0184] It should be noted that, in an embodiment of the present application, the terminal device can determine whether at least one first bit in the RAR indicates the number of repeated transmissions of the Msg3 PUSCH based on the first information, and the number of repeated transmissions of the Msg3 PUSCH here may refer to the number of repeated transmissions information for the initial transmission of the Msg3 PUSCH. In some other embodiments, the network device can schedule the retransmission of the Msg3 PUSCH through the DCI, and the network device can also indicate the number of repeated transmissions information for the retransmission of the Msg3PUSCH. In this case, the DCI may include at least one third bit, and the at least one third bit can be used to indicate the number of repeated transmissions information for the retransmission of the Msg3 PUSCH. Further, the network device can indicate to the terminal device whether at least one third bit indicates the number of repeated transmissions information for the retransmission of the Msg3 PUSCH, or whether the network device has scheduled the repeated transmission of the retransmission of the Msg3 PUSCH, through at least one fourth bit in the DCI and / or the TC-RNTI corresponding to the PDCCH carrying the DCI.

[0185] It should be understood that the specific implementation of the at least one third bit and the at least one fourth bit may refer to the specific implementation of the first bit and the second bit in the aforementioned embodiment, and for the sake of brevity, they will not be repeated here.

[0186] It should be understood that the specific implementation of the TC-RNTI corresponding to the PDCCH carrying the DCI can refer to the specific implementation of the RA-RNTI corresponding to the PDCCH carrying the RAR in the aforementioned embodiment, which will not be repeated here for the sake of brevity.

[0187] As an example, the at least one third bit may include at least one bit in at least one information field in the DCI, the at least one fourth bit may include at least one bit in at least one information field in the DCI, and the at least one fourth bit is different from the at least one third bit.

[0188] Optionally, the at least one third bit and the at least one fourth bit are carried in the same information field in the DCI. For example, the at least one third bit and the at least one fourth bit are carried in the TDRA field in the UL grant information in the DCI.

[0189] Optionally, the at least one third bit and the at least one fourth bit are carried in different information fields in the DCI. For example, the at least one third bit is carried in the TDRA field in the UL grant information in the DCI, and the at least one fourth bit is carried in other information fields except the TDRA field in the UL grant information in the DCI.

[0190] As an example, the network device generates a TC-RNTI for a PDCCH scrambled to carry DCI based on the first identification information, wherein the specific implementation of the first identification information refers to the relevant implementation in the previous text and is not repeated here for the sake of brevity. Based on this implementation, the TC-RNTI corresponding to the PDCCH of the RAR for repeated transmission of the retransmission of the scheduled Msg3PUSCH is different from the TC-RNTI corresponding to the PDCCH of the RAR for repeated transmission of the retransmission of the unscheduled Msg3 PUSCH. Therefore, the terminal device requesting the repeated transmission of the retransmission of the Msg3 PUSCH can determine whether the at least one third bit in the DCI indicates the number of repeated transmissions of the retransmission of the Msg3 PUSCH.

[0191] Combination of the above Figures 2 to 4 , describes in detail the method embodiment of the present application, and the following is combined with Figures 5 to 9 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0192] Figure 5 FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. Figure 5 As shown, the terminal device 400 includes:

[0193] A communication unit 410 is configured to receive a random access response RAR sent by a network device, wherein the RAR includes at least one first bit, and the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, and the PUSCH is used to carry a third message in a random access process;

[0194] The processing unit 420 is used to determine whether the at least one first bit indicates the number of repeated transmissions of the PUSCH according to first information, wherein the first information is associated with the RAR.

[0195] In some embodiments of the present application, the first information includes at least one second bit in the RAR, and the at least one second bit is different from the at least one first bit.

[0196] In some embodiments of the present application, the at least one second bit and the at least one first bit are carried in the same information field in the RAR.

[0197] In some embodiments of the present application, the at least one second bit and the at least one first bit are carried in different information fields in the RAR.

[0198] In some embodiments of the present application, the at least one second bit and the at least one first bit are both carried in uplink authorization information in the RAR.

[0199] In some embodiments of the present application, the first information includes a random access radio network temporary identifier RA-RNTI corresponding to a physical downlink control channel PDCCH that schedules the RAR.

[0200] In some embodiments of the present application, the RA-RNTI of the PDCCH that schedules the RAR is determined according to first identification information, and the first identification information is related to the transmission mode of the PUSCH determined by the network device.

[0201] In some embodiments of the present application, the PUSCH transmission mode includes repeated transmission of PUSCH and non-repeated transmission of PUSCH.

[0202] In some embodiments of the present application, the processing unit 420 is further configured to:

[0203] The RA-RNTI of the PDCCH that schedules the RAR is determined according to the following formula:

[0204] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×Q

[0205] Wherein, Q is the first identification information;

[0206] s_id is the index of the first orthogonal frequency division multiplexing OFDM symbol occupied by the physical random access channel PRACH resource;

[0207] t_id is the index of the first time slot occupied by the PRACH resource;

[0208] f_id is the index of the PRACH resource in the frequency domain;

[0209] ul_carrier_id is the uplink carrier where the PRACH resource is located.

[0210] In some embodiments of the present application, the Q is not equal to 0, or the Q is not equal to 0 and 1.

[0211] In some embodiments of the present application, the first information includes information in a PDCCH that schedules the RAR.

[0212] In some embodiments of the present application, the first information includes at least one reserved bit in a PDCCH that schedules the RAR.

[0213] In some embodiments of the present application, the first information includes multiple reserved bit groups, each reserved bit group includes at least one reserved bit, each reserved bit group corresponds to a random access preamble code or a random access preamble code group, and the value of each reserved bit group is used to indicate whether the at least one first bit in the random access preamble code corresponding to each reserved bit group or the RAR corresponding to the random access preamble code group indicates the number of repeated transmissions of the PUSCH.

[0214] In some embodiments of the present application, the random access preamble codes or random access preamble code groups corresponding to the multiple reserved bit groups are random access preamble codes or random access preamble code groups used to request repeated transmission of PUSCH.

[0215] In some embodiments of the present application, the processing unit 420 is further configured to:

[0216] The first message is used to indicate to the network device whether the terminal device requests repeated transmission of the PUSCH, wherein the first message is the first message in the random access process.

[0217] In some embodiments of the present application, the processing unit 420 is specifically used for:

[0218] Through at least one of a random access preamble code, an initial uplink bandwidth part BWP for sending the first message, and a PRACH resource for sending the first message, the network device is indicated whether the terminal device requests repeated transmission of the PUSCH.

[0219] In some embodiments of the present application, the first information includes information in a media access control MAC protocol data unit PDU that carries the RAR.

[0220] In some embodiments of the present application, the information in the MAC PDU carrying the RAR includes information in a header of the MAC PDU and / or information in a sub-header in a MAC sub-PDU in the MAC PDU.

[0221] In some embodiments of the present application, the at least one first bit is carried in a time domain resource allocation TDRA information field in an uplink grant of the RAR.

[0222] In some embodiments of the present application, the processing unit 420 is further configured to:

[0223] If it is determined that the at least one first bit is used to indicate the number of repeated transmissions of the PUSCH, the number of repeated transmissions of the PUSCH is determined according to the value of the at least one first bit; or

[0224] If it is determined that the at least one first bit is not used to indicate the number of repeated transmissions of the PUSCH, the time domain resource allocation information of the PUSCH is determined according to the value of the TDRA information field.

[0225] Optionally, 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.

[0226] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively to implement Figure 2 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.

[0227] Figure 6 It is a schematic block diagram of a network device according to an embodiment of the present application. Figure 6 The network device 500 includes:

[0228] The processing unit 510 is used to indicate to the terminal device through the first information whether at least one first bit in the random access response RAR indicates the number of repeated transmissions of the physical uplink shared channel PUSCH, wherein the first information is associated with the RAR, and the at least one first bit can be used to indicate the number of repeated transmissions of the physical uplink shared channel PUSCH, and the PUSCH is used to carry the third message in the random access process.

[0229] In some embodiments of the present application, the first information includes at least one second bit in the RAR, and the at least one second bit is different from the at least one first bit.

[0230] In some embodiments of the present application, the at least one second bit and the at least one first bit are carried in the same information field in the RAR.

[0231] In some embodiments of the present application, the at least one second bit and the at least one first bit are carried in different information fields in the RAR.

[0232] In some embodiments of the present application, the at least one second bit and the at least one first bit are both carried in uplink authorization information in the RAR.

[0233] In some embodiments of the present application, the first information includes a random access radio network temporary identifier RA-RNTI corresponding to a physical downlink control channel PDCCH that schedules the RAR.

[0234] In some embodiments of the present application, the RA-RNTI of the PDCCH that schedules the RAR is determined according to first identification information, and the first identification information is related to the transmission mode of the PUSCH determined by the network device.

[0235] In some embodiments of the present application, the PUSCH transmission mode includes repeated transmission of PUSCH and non-repeated transmission of PUSCH.

[0236] In some embodiments of the present application, the processing unit 510 is further configured to:

[0237] The RA-RNTI of the PDCCH that schedules the RAR is determined according to the following formula:

[0238] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×Q

[0239] Wherein, Q is the first identification information;

[0240] s_id is the index of the first orthogonal frequency division multiplexing OFDM symbol occupied by the physical random access channel PRACH resource;

[0241] t_id is the index of the first time slot occupied by the PRACH resource;

[0242] f_id is the index of the PRACH resource in the frequency domain;

[0243] ul_carrier_id is the uplink carrier where the PRACH resource is located.

[0244] In some embodiments of the present application, the Q is not equal to 0, or the Q is not equal to 0 and 1.

[0245] In some embodiments of the present application, the first information includes information in a PDCCH that schedules the RAR.

[0246] In some embodiments of the present application, the first information includes at least one reserved bit in a PDCCH that schedules the RAR.

[0247] In some embodiments of the present application, the first information includes multiple reserved bit groups, each reserved bit group includes at least one reserved bit, each reserved bit group corresponds to a random access preamble code or a random access preamble code group, and the value of each reserved bit group is used to indicate whether the at least one first bit in the random access preamble code corresponding to each reserved bit group or the RAR corresponding to the random access preamble code group indicates the number of repeated transmissions of the PUSCH.

[0248] In some embodiments of the present application, the random access preamble codes or random access preamble code groups corresponding to the multiple reserved bit groups are random access preamble codes or random access preamble code groups used to request repeated transmission of PUSCH.

[0249] In some embodiments of the present application, the processing unit 510 is further configured to:

[0250] Determine whether the terminal device requests repeated transmission of the PUSCH according to a first message, wherein the first message is the first message in the random access process.

[0251] In some embodiments of the present application, the processing unit 510 is further configured to:

[0252] Determine whether the terminal device requests repeated transmission of the PUSCH based on at least one of a random access preamble code, an initial uplink bandwidth part BWP for sending the first message, and a PRACH resource for sending the first message.

[0253] In some embodiments of the present application, the first information includes information in a media access control MAC protocol data unit PDU that carries the RAR.

[0254] In some embodiments of the present application, the information in the MAC PDU carrying the RAR includes information in a header of the MAC PDU and / or information in a sub-header in a MAC sub-PDU in the MAC PDU.

[0255] In some embodiments of the present application, the at least one first bit is carried in a time domain resource allocation TDRA information field in an uplink grant of the RAR.

[0256] In some embodiments of the present application, the at least one first bit may be used for the number of repeated transmissions of the initial transmission of the PUSCH.

[0257] Optionally, 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.

[0258] It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 500 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes of the network device in the method 200 are not described in detail here.

[0259] Figure 7 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Figure 7 The communication device 600 shown 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.

[0260] Alternatively, if Figure 7 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

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

[0262] Alternatively, if Figure 7 As shown, 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, may send information or data to other devices, or receive information or data sent by other devices.

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

[0264] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0265] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of 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 of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

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

[0267] Alternatively, if Figure 8 As shown, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

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

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

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

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

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

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

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

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

[0276] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. 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.

[0277] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can 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 can 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.

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

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

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

[0281] 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 are not repeated here.

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

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

[0284] 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 are not repeated here.

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

[0286] 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 in the embodiments of the present application. For the sake of brevity, they are not described here.

[0287] 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 are not repeated here.

[0288] Those of ordinary skill 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 to be beyond the scope of this application.

[0289] Those skilled in the art can 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.

[0290] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

[0291] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0293] 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 can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods 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.

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

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a random access response RAR sent by the network device, where the RAR includes at least one first bit, where the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, where the PUSCH is used to carry the third message in the random access process; The terminal device determines, based on first information, whether the at least one first bit indicates the number of repeated transmissions of the PUSCH, wherein the first information is associated with the RAR.

2. The method according to claim 1, characterized in that The at least one first bit is: at least one bit in a modulation and coding scheme MCS field in the RAR.

3. The method according to claim 1, characterized in that: The first information includes at least one second bit in the RAR, and the at least one second bit is different from the at least one first bit.

4. The method according to claim 3, characterized in that The at least one second bit and the at least one first bit are carried in different information fields in the RAR.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The terminal device indicates to the network device via a first message whether the terminal device requests repeated transmission of the PUSCH, wherein the first message is the first message in the random access process.

6. The method according to claim 5, characterized in that The terminal device indicating, through a first message, to the network device whether the terminal device requests repeated transmission of the PUSCH, includes: The terminal device indicates to the network device whether the terminal device requests repeated transmission of the PUSCH through at least one of a random access preamble code, an initial uplink bandwidth part BWP for sending the first message, and a PRACH resource for sending the first message.

7. The method according to any one of claims 1 to 4, characterized in that The first information includes information in a media access control MAC protocol data unit PDU that carries the RAR.

8. The method according to claim 7, characterized in that The information in the MAC PDU carrying the RAR includes information in a subheader in a MAC sub-PDU in the MAC PDU.

9. A wireless communication method, characterized in that: include: The network device indicates to the terminal device through the first information whether at least one first bit in the random access response RAR indicates the number of repeated transmissions of the physical uplink shared channel PUSCH, wherein the first information is associated with the RAR, and the at least one first bit can be used to indicate the number of repeated transmissions of the PUSCH, and the PUSCH is used to carry the third message in the random access process.

10. The method according to claim 9, characterized in that The at least one first bit is: at least one bit in a modulation and coding scheme MCS field in the RAR.

11. The method according to claim 9, characterized in that The first information includes at least one second bit in the RAR, and the at least one second bit is different from the at least one first bit.

12. The method according to claim 11, characterized in that The at least one second bit and the at least one first bit are carried in different information fields in the RAR.

13. The method according to any one of claims 9 to 12, characterized in that: The method further comprises: The network device determines whether the terminal device requests repeated transmission of the PUSCH based on a first message, wherein the first message is the first message in a random access process.

14. The method according to claim 13, characterized in that The network device determines, according to the first message, whether the terminal device requests repeated transmission of the PUSCH, including: The network device determines whether the terminal device requests repeated transmission of the PUSCH based on at least one of a random access preamble code, an initial uplink bandwidth part BWP for sending the first message, and a PRACH resource for sending the first message.

15. The method according to any one of claims 9 to 12, characterized in that: The first information includes information in a media access control MAC protocol data unit PDU that carries the RAR.

16. The method according to claim 15, characterized in that The information in the MAC PDU carrying the RAR includes information in a subheader in a MAC sub-PDU in the MAC PDU.

17. A terminal device, characterized in that: include: A communication unit, configured to receive a random access response RAR sent by a network device, wherein the RAR includes at least one first bit, and the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, and the PUSCH is used to carry a third message in the random access process; A processing unit is used to determine whether the at least one first bit indicates the number of repeated transmissions of the PUSCH according to first information, wherein the first information is associated with the RAR.

18. A network device, characterized in that: include: A processing unit, used to indicate to a terminal device through first information whether at least one first bit in a random access response RAR indicates the number of repeated transmissions of a physical uplink shared channel PUSCH, wherein the first information is associated with the RAR, and the at least one first bit can be used to indicate the number of repeated transmissions of a physical uplink shared channel PUSCH, and the PUSCH is used to carry the third message in the random access process.

19. 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 execute the method according to any one of claims 1 to 8.

20. 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 as claimed in any one of claims 9 to 16.

Citation Information

Patent Citations

  • Msg3 transmission method and device, equipment and storage medium

    CN114765896A

  • User equipment, base station, and related method

    US20210058823A1