Method and apparatus for determining and indicating number of msg3 repetitions

Abstract

The application discloses a Msg3 repetition number determination method, device, terminal and network side equipment, and belongs to the technical field of communication. The Msg3 repetition number determination method is executed by a terminal and comprises the following steps: after a first Msg1 is sent to a network side equipment, Msg3 scheduling information of the network side equipment is received, and the number of Msg3 repetition transmissions is determined according to the Msg3 scheduling information; the first Msg1 is an uplink signal for the terminal to request Msg3 repetition transmission, and the Msg3 scheduling information is Msg2 for scheduling Msg3 initial transmission or DCI for scheduling Msg3 retransmission. The technical scheme of the embodiment of the application can flexibly indicate the configuration information of Msg3 repetition transmission.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a method and device for determining and indicating a number of Msg3 repetitions. BACKGROUND

[0002] In a new radio (NR) system, the coverage performance of message 3 (Msg3) is poorer than that of other channels, which makes it difficult for terminals in areas with poor signal coverage quality to access a cell. Therefore, a mechanism of Msg3 repetition transmission is introduced to improve the coverage performance of Msg3. SUMMARY

[0003] Embodiments of the present application provide a method and device for determining and indicating a number of Msg3 repetitions, which can efficiently schedule Msg3 repetition transmission.

[0004] In a first aspect, embodiments of the present application provide a method for determining a number of Msg3 repetitions, which is performed by a terminal and includes:

[0005] After sending a first Msg1 to a network side device, receiving Msg3 scheduling information of the network side device, and determining a number of Msg3 repetition transmissions according to the Msg3 scheduling information.

[0006] The first Msg1 is an uplink signal for the terminal to request Msg3 repetition transmission, and the Msg3 scheduling information is Msg2 for scheduling initial transmission of Msg3 or DCI for scheduling retransmission of Msg3.

[0007] In a second aspect, embodiments of the present application provide a method for indicating a number of Msg3 repetitions, which is performed by a network side device and includes:

[0008] Receiving a first Msg1 of a terminal, which is an uplink signal for the terminal to request Msg3 repetition transmission.

[0009] Sending Msg3 scheduling information to the terminal, indicating a number of Msg3 repetition transmissions through the Msg3 scheduling information, and the Msg3 scheduling information is Msg2 for scheduling initial transmission of Msg3 or DCI for scheduling retransmission of Msg3.

[0010] In a third aspect, embodiments of the present application provide a device for determining a number of Msg3 repetitions, which is applied to a terminal and includes:

[0011] A receiving module is configured to receive Msg3 scheduling information of a network side device after sending a first Msg1 to the network side device.

[0012] A determining module is configured to determine a number of Msg3 repetition transmissions according to the Msg3 scheduling information.

[0013] The first Msg1 is an uplink signal for the terminal to request Msg3 repeated transmission, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission.

[0014] In a fourth aspect, an embodiment of the present application provides a Msg3 repetition number indication device, applied to a network side device, and comprising:

[0015] The receiving module is configured to receive first Msg1 of a terminal, the first Msg1 being an uplink signal for the terminal to request Msg3 repeated transmission;

[0016] The sending module is configured to send Msg3 scheduling information to the terminal, and indicate a Msg3 repetition number through the Msg3 scheduling information, the Msg3 scheduling information being Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission.

[0017] In a fifth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and when the program or instruction is executed by the processor, the steps of the method according to the first aspect are implemented.

[0018] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to, after sending first Msg1 to a network side device, receive Msg3 scheduling information of the network side device, and determine a Msg3 repetition number according to the Msg3 scheduling information; the first Msg1 is an uplink signal for the terminal to request Msg3 repeated transmission, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission.

[0019] In a seventh aspect, a network side device is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and when the program or instruction is executed by the processor, the steps of the method according to the second aspect are implemented.

[0020] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to, after sending first Msg1 to a network side device, receive Msg3 scheduling information of the network side device, and determine a Msg3 repetition number according to the Msg3 scheduling information; the first Msg1 is an uplink signal for the terminal to request Msg3 repeated transmission, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission.

[0021] In a ninth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the steps of the method in the first aspect or the steps of the method in the second aspect.

[0022] In a tenth aspect, a chip is provided, and the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or instructions to implement the method in the first aspect or the method in the second aspect.

[0023] In an eleventh aspect, a computer program / program product is provided, and the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method in the first aspect or the second aspect.

[0024] In the embodiments of the present application, after the terminal sends the first Msg1, the network side device sends the Msg3 scheduling information to the terminal, which can flexibly indicate the configuration information of the Msg3 repeated transmission and efficiently schedule the Msg3 repeated transmission. BRIEF DESCRIPTION OF DRAWINGS

[0025] Figure 1 A schematic diagram of a wireless communication system is shown;

[0026] Figure 2 A flowchart of a method for determining the number of Msg3 repetitions performed by a terminal according to an embodiment of the present application is shown;

[0027] Figure 3 A flowchart of a method for indicating the number of Msg3 repetitions performed by a network side device according to an embodiment of the present application is shown;

[0028] Figure 4 A structural diagram of a device for determining the number of Msg3 repetitions applied to a terminal according to an embodiment of the present application is shown;

[0029] Figure 5 A structural diagram of a device for indicating the number of Msg3 repetitions applied to a network side device according to an embodiment of the present application is shown;

[0030] Figure 6 A composition diagram of a communication device according to an embodiment of the present application is shown;

[0031] Figure 7 A composition diagram of a terminal according to an embodiment of the present application is shown;

[0032] Figure 8 A composition diagram of a network side device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0033] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0034] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0035] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th Generation (6G) communication systems.

[0036] Figure 1A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (UE). The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a palm computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. The wearable device includes a smart watch, a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art so long as the same technical result is achieved. The base station is not limited to a specific technical term as long as the same technical result is achieved. It should be noted that only a base station in an NR system is taken as an example in the embodiments of the present application, but the specific type of the base station is not limited. The core network device can be a location management device, such as a location management function (LMF, E-SLMC), etc.

[0037] NR supports two types of random access (RA) procedures: 4-step RACH and 2-step RACH. Both types of random access procedures support contention based random access (CBRA) and contention free random access (CFRA). The 2-step RACH procedure is generally applied in areas with good coverage, shortening the terminal access time. For areas with poor signal coverage, the terminal uses the 4-step RACH procedure to access the cell.

[0038] In 4-step RACH, UE first sends Msg1 to network, containing random access preamble; after UE sends Msg1, it will listen to PDCCH in RAR time window (RA Response window) to receive DCI scheduled random access response (RAR) scrambled with RA-radio network temporary identifier (RNTI) in fallback downlink control information (DCI) format DCI format 1_0. If the PRID in the RAR is the same as the preamble index sent by the UE, it is considered that the RAR is successfully received, at this time the UE can stop listening to the RAR and send Msg3 according to the indication of the grant carried in the RAR as shown in Table 1; Msg3 is transmitted on the uplink shared channel and uses hybrid automatic repeat request (HARQ), and the retransmission of Msg3 is scheduled by DCI scrambled with temporary cell (TC)-RNTI indicated by RAR in fallback DCI format DCI format 0_0. Msg3 needs to contain a unique identifier for each UE. The identifier will be used for conflict resolution in step four. After the network receives Msg3, it will schedule Msg4 using PDCCH scrambled with TC-RNTI. When the UE successfully decodes the UE Contention Resolution Identity MAC control element contained in Msg4 to match the UE Contention Resolution Identity sent in Msg3, the UE considers that the random access is successful and sets its C-RNTI to TC-RNTI, that is, completes the 4-step random access.

[0039] The 27-bit UL grant in Msg2 message is used to indicate the configuration parameters of Msg3 transmission, wherein the PUSCH time resource allocation length is 4 bits, which is used to indicate the time domain resource occupied by Msg3 PUSCH in a time slot, and can support different time slot offsets K2 and different mapping modes PUSCH mapping type A / B; the MCS length is 4 bits, which is used to indicate the modulation and coding parameters of Msg3 PUSCH, and can indicate the first 16 rows of MCS, and the maximum can indicate 16QAM modulation 0.6 code rate; the TPC length is 3 bits, which is used to indicate the adjustment amount of Msg3 PUSCH transmission power, and the indication range is [-6, 8] dB.

[0040] In the related art, when a terminal is located at the edge of a cell or in a shadow fading area of a building, a base station can schedule the terminal to use Msg3 repetition transmission to improve the success rate of Msg3 transmission. In a case of poor signal coverage (synchronization signal block signal quality is lower than a predefined threshold), the terminal sends a dedicated Msg1 to the base station to request Msg3 repetition transmission. The base station schedules Msg3 according to the channel condition of the terminal and indicates the number of Msg3 repetitions. At the same time, the total length of the UL grant scheduling Msg3 repetition transmission remains unchanged to ensure system forward compatibility requirements.

[0041] The length of the UL grant defined in the related art is limited, and each field has defined corresponding parameters. The MAC subPDU of Msg2 is of fixed length, so the length of the UL grant cannot be directly increased to explicitly indicate the number of Msg3 repetitions.

[0042] In the application scenario of Msg3 coverage enhancement, the configuration parameters of the UL grant may not be used. For example, the configuration parameters (+2, +4, +6, +8) for increasing the transmission power in the TPC field may not be used, because in the coverage enhancement scenario, the terminal transmission power is already close to the full power, so there is no margin to increase the Msg3 transmission power. The high-rate configurations (MCS index > 10 configurations, using 16QAM modulation) indicated in the MCS field are unlikely to be applied to the Msg3 coverage enhancement scenario, because the transmission mode of high-order MCS is not suitable for transmission scenarios with high robustness requirements. The table corresponding to the time domain resource allocation (TDRA) contains PUSCH mapping TypeB, which is unlikely to be configured in Msg3 repetition transmission, because PUSCH mapping typeB cannot efficiently utilize the available ODFM symbols of the time slot in Msg3 repetition transmission, resulting in time domain resource fragmentation. Therefore, the redundant content of the UL grant, or the parameter values that are unlikely to be configured in the Msg3 coverage enhancement scenario, can be redefined to indicate the number of Msg3 repetitions.

[0043] Embodiments of the present application provide a method for determining the number of Msg3 repetitions, which is performed by a terminal, as shown in Figure 2 The method comprises the following steps:

[0044] Step 101: After sending a first Msg1 to a network side device, receiving Msg3 scheduling information of the network side device, and determining the number of Msg3 repetition transmissions according to the Msg3 scheduling information;

[0045] Step 102: The first Msg1 is an uplink signal for the terminal to request Msg3 repetition transmission, and the Msg3 scheduling information is a Msg2 scheduling Msg3 initial transmission or a DCI scheduling Msg3 retransmission.

[0046] In the embodiments of the present application, after the terminal sends the first Msg1, the network side device sends the Msg3 scheduling information to the terminal, which can flexibly indicate the configuration information of the Msg3 repeated transmission and efficiently schedule the Msg3 repeated transmission.

[0047] In some embodiments, the determining the number of Msg3 repeated transmissions according to the Msg3 scheduling information comprises:

[0048] In the initial transmission stage of the Msg3 repeated transmission, the terminal device listens to the Msg2 in the RAR window, detects a specific field of the Msg2, and determines whether to schedule the Msg3 repeated transmission and the number of the Msg3 repeated transmission according to the specific field, wherein the specific field adopts any one of the following:

[0049] a field in the MAC PDU subheader;

[0050] a field in the MAC subPDU;

[0051] a field in the UL grant.

[0052] In this way, the configuration information of the Msg3 repeated transmission can be flexibly indicated by the specific field of the Msg2, the Msg3 repeated transmission can be efficiently scheduled, and the length of the Msg2 is unchanged, which ensures the compatibility with the related protocol such as the Msg2 defined in Rel-15 / 16.

[0053] In some embodiments, whether to schedule the Msg3 repeated transmission is determined by a 1-bit field in the MAC subPDU or the MAC PDU subheader; and / or

[0054] The scaling factor N of the number of the Msg3 repeated transmissions is determined by a 2-bit field in the MAC subPDU and the MAC PDU subheader.

[0055] In this way, the configuration information of the Msg3 repeated transmission can be flexibly indicated by the field in the MAC subPDU and / or the MAC PDU subheader, and the Msg3 repeated transmission can be efficiently scheduled.

[0056] In some embodiments, the transmission is performed using N times of the determined number of the Msg3 repeated transmissions.

[0057] In some embodiments, the 2-bit field is composed of a 1-bit field in the MAC PDU subheader and a 1-bit field in the MAC subPDU.

[0058] In some embodiments, the determining the number of Msg3 repetition transmissions according to the Msg3 scheduling information specifically comprises:

[0059] determining whether to schedule the Msg3 repetition transmission and the number of Msg3 repetition transmissions according to a first field in the UL grant, the first field comprising at least one of:

[0060] a CSI request field;

[0061] an MCS field;

[0062] a TPC field;

[0063] a TDRA field.

[0064] In this way, the configuration information of the Msg3 repetition transmission can be flexibly indicated by the first field in the UL grant, and the Msg3 repetition transmission can be efficiently scheduled.

[0065] In some embodiments, a part of the TPC field is used to indicate scheduling of the Msg3 repetition transmission, and another part is used to indicate no scheduling of the Msg3 repetition transmission; or

[0066] a part of the MCS field is used to indicate scheduling of the Msg3 repetition transmission, and another part is used to indicate no scheduling of the Msg3 repetition transmission.

[0067] In some embodiments, different ranges of values of the MCS field correspond to different numbers of Msg3 repetition transmissions.

[0068] In some embodiments, the CSI request field, or a 1-bit field in the MAC subPDU, or a 2-bit field in the MAC PDU subheader, or the MAC subPDU and the MAC PDU subheader indicates any of:

[0069] whether to schedule the Msg3 repetition transmission;

[0070] selection of a TDRA table;

[0071] a scaling factor of the number of repetitions.

[0072] In some embodiments, the method further comprises determining the TDRA table, comprising:

[0073] after sending the first Msg1 to the network side device, if a specific field in the Msg2 indicates scheduling of the Msg3 repetition transmission, using a dedicated TDRA table to interpret the TDRA field in the UL grant;

[0074] Each entry of the dedicated TDRA table indicates time domain resource configuration within a slot and number of Msg3 repetition.

[0075] In some embodiments, the dedicated TDRA table is pre-defined by a protocol and / or configured by a network-side device through a system message.

[0076] In some embodiments, the method further comprises:

[0077] Determining a length of the TDRA field or a field division of the UL grant according to whether the network-side device schedules Msg3 repetition transmission.

[0078] In some embodiments, the TPC field and the TDRA field jointly indicate TDRA and power control parameter; or

[0079] The MCS field and the TDRA field jointly indicate TDRA and MCS.

[0080] In some embodiments, determining the length of the TDRA field or the field division of the UL grant comprises any of the following:

[0081] Determining that the TDRA field is greater than a first preset value, and a total number of entries of the dedicated TDRA table is greater than a second preset value and does not exceed an indication range of the TDRA field;

[0082] A length of the TPC field or the MCS field is less than a third preset value.

[0083] The first preset value, the second preset value and the third preset value can be configured by a system message or defined by a protocol.

[0084] In some embodiments, content of the TDRA entry is configured by the network-side device through a system message.

[0085] In some embodiments, the method further comprises:

[0086] Determining available slots for Msg3 PUSCH repetition transmission according to the MCS field or the TPC field. In this way, the MCS field or the TPC field can be configured to configure available slots for Msg3 PUSCH repetition transmission, and Msg3 PUSCH repetition transmission can be efficiently scheduled.

[0087] In some embodiments, a specific value or a specific value range of the MCS field or the TPC field indicates slot configuration information or a number of consecutive available slots for a first transmission of Msg3 repetition transmission;

[0088] The slot configuration information is pre-defined by a protocol or configured by a system message of the network-side device, and indicates uplink and downlink slot configuration in Msg3 repetition transmission.

[0089] The number of consecutive available time slots of the first transmission of the Msg3 repetition transmission is predefined by a protocol or configured by a system message of the network-side device, and the first available time slot of the Msg3 repetition transmission determined by the UL grant starts from the consecutive M time slots, where M is a positive integer.

[0090] In some embodiments, before sending the first Msg1, the method further comprises:

[0091] Determining the carrier of the uplink initial BWP (bandwidth part) comprises:

[0092] If multiple carriers are available for the uplink carrier, the carrier of the uplink initial BWP is determined by a system message of the network-side device.

[0093] In some embodiments, if the network-side device supports SUL capability and supports NUL to support Msg3 repetition transmission, a first decision threshold is determined and used to select the uplink carrier, and the first decision threshold is explicitly configured by a system message or implicitly calculated according to the number of Msg3 repetitions.

[0094] In some embodiments, determining the number of Msg3 repetition transmissions according to the Msg3 scheduling information comprises:

[0095] Determining whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to a second field in the DCI, the second field comprising at least one of:

[0096] A TDRA field;

[0097] A TPC field;

[0098] An MCS field;

[0099] A new data indicator field;

[0100] A HARQ process number field.

[0101] In some embodiments, determining whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to the second field in the DCI comprises any of:

[0102] Determining the number of Msg3 repetition transmissions according to the content in the TPC field, or determining the adjustment amount of the number of Msg3 repetitions, and it can be understood that the number of Msg3 retransmissions is equal to the number of Msg3 initial transmissions plus the adjustment amount of the number of Msg3 repetitions;

[0103] Determining the number of Msg3 repetition transmissions or determining the adjustment amount of the number of Msg3 repetitions according to the content in the MCS field;

[0104] determining a dedicated TDRA table corresponding to the New data indicator field, and determining the number of Msg3 repetition transmissions according to the dedicated TDRA table;

[0105] directly determining the number of Msg3 repetition transmissions according to the TDRA field in the corresponding dedicated TDRA table;

[0106] determining the number of Msg3 repetition transmissions according to the HARQ process number field.

[0107] The embodiment of the application further provides a method for indicating the number of Msg3 repetition transmissions, which is executed by a network side device, and as shown in the method comprises the following steps: Figure 3

[0108] Step 201: receiving a first Msg1 of a terminal, wherein the first Msg1 is an uplink signal for requesting Msg3 repetition transmission of the terminal;

[0109] Step 202: sending Msg3 scheduling information to the terminal, wherein the Msg3 scheduling information is used for indicating the number of Msg3 repetition transmissions, and the Msg3 scheduling information is Msg2 for scheduling initial transmission of Msg3 or DCI for scheduling retransmission of Msg3.

[0110] In some embodiments, whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions are indicated by a specific field of the Msg2, and the specific field adopts any one of the following:

[0111] a field in a MAC PDU subheader;

[0112] a field in a MAC subPDU;

[0113] a field in an UL grant.

[0114] In some embodiments, whether to schedule Msg3 repetition transmission is indicated by a 1bit field in a MAC subPDU or a MAC PDU subheader; and / or

[0115] a scaling coefficient N of the number of Msg3 repetition transmissions is indicated by a 2bit field in the MAC subPDU and the MAC PDU subheader.

[0116] In some embodiments, the 2bit field is composed of a 1bit field in a MAC PDU subheader and a 1bit field in a MAC subPDU.

[0117] ​In some embodiments, whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmission are indicated by a first field in the UL grant, the first field comprising at least one of:

[0118] a CSI request field;

[0119] an MCS field;

[0120] a TPC field;

[0121] a TDRA field.

[0122] In some embodiments, a part of the TPC field has a value indicating scheduling Msg3 repetition transmission, and another part has a value indicating not scheduling Msg3 repetition transmission; or

[0123] a part of the MCS field has a value indicating scheduling Msg3 repetition transmission, and another part has a value indicating not scheduling Msg3 repetition transmission.

[0124] In some embodiments, different value ranges of the MCS field correspond to different numbers of Msg3 repetition.

[0125] In some embodiments, a 1-bit field in the CSI request field, or a MAC subPDU, or a MAC PDU subheader, or a 2-bit field in the MAC subPDU and the MAC PDU subheader indicates any of:

[0126] whether to schedule Msg3 repetition transmission;

[0127] selection of a TDRA table;

[0128] a scaling factor of the number of repetitions.

[0129] In some embodiments, in the TDRA field, each entry in a dedicated TDRA table indicates a time domain resource configuration and a number of Msg3 repetition.

[0130] In some embodiments, the dedicated TDRA table is pre-defined by a protocol and / or configured by a network-side device through a system message.

[0131] In some embodiments, the TPC field and the TDRA field jointly indicate a TDRA and a power control parameter; or

[0132] the MCS field and the TDRA field jointly indicate a TDRA and an MCS.

[0133] In some embodiments, part of the entries in the TDRA table are indicated by a network-side device through a system message.

[0134] In some embodiments, the method further comprises:

[0135] indicating available time slots for Msg3 PUSCH repetition transmission to the terminal through the MCS field or the TPC field.

[0136] In some embodiments, a specific value or a specific value range of the MCS field or the TPC field indicates time slot configuration information or a number of consecutive available time slots for a first transmission of Msg3 repetition transmission.

[0137] The time slot configuration information is predefined by a protocol or configured by a system message of a network side device, and indicates uplink and downlink time slot configuration in Msg3 repetition transmission.

[0138] The number of consecutive available time slots for the first transmission of Msg3 repetition transmission is predefined by a protocol or configured by a system message of a network side device, and indicates that a first available time slot determined by the UL grant starts from consecutive M time slots, and M is an integer greater than or equal to zero.

[0139] In some embodiments, before receiving the first Msg1, the method further comprises:

[0140] If multiple carriers are available for the uplink carrier, indicating a carrier supporting Msg3 repetition transmission to the terminal through a system message.

[0141] In some embodiments, the method specifically comprises:

[0142] indicating whether to schedule Msg3 repetition transmission and a number of Msg3 repetition transmissions through a second field in the DCI, the second field comprising at least one of:

[0143] a TDRA field;

[0144] a TPC field;

[0145] an MCS field;

[0146] a new data indicator field;

[0147] a HARQ process number field.

[0148] In some embodiments, indicating whether to schedule Msg3 repetition transmission and a number of Msg3 repetition transmissions through a second field in the DCI comprises any of:

[0149] The number of repetitions of Msg3 retransmission is equal to the number of repetitions of Msg3 initial transmission plus the adjustment amount of the number of repetitions of Msg3 retransmission, which is indicated by the content in the TPC field;

[0150] The number of repetitions of Msg3 retransmission is equal to the number of repetitions of Msg3 initial transmission plus the adjustment amount of the number of repetitions of Msg3 retransmission, which is indicated by the content in the TPC field;

[0151] The number of repetitions of Msg3 retransmission is equal to the number of repetitions of Msg3 initial transmission plus the adjustment amount of the number of repetitions of Msg3 retransmission, which is indicated by the content in the TPC field;

[0152] The number of repetitions of Msg3 retransmission is equal to the number of repetitions of Msg3 initial transmission plus the adjustment amount of the number of repetitions of Msg3 retransmission, which is indicated by the content in the TPC field;

[0153] The number of repetitions of Msg3 retransmission is equal to the number of repetitions of Msg3 initial transmission plus the adjustment amount of the number of repetitions of Msg3 retransmission, which is indicated by the content in the TPC field.

[0154] The application will be further described in combination with specific embodiments:

[0155] Embodiment one of the application:

[0156] In this embodiment, the Msg3 retransmission terminal determines whether to perform Msg3 retransmission according to the indication information in Msg2, and reads the scheduling information according to the UL grant reading mode of Msg3 retransmission to determine the number of repetitions of Msg3 retransmission, and other scheduling information of Msg3 transmission.

[0157] I. The Msg3 retransmission terminal determines the reading mode of the UL grant field, or determines whether the base station schedules Msg3 retransmission.

[0158] The Msg3 retransmission terminal listens to Msg2 in the RAR window after sending the Msg3 retransmission request (i.e. the first Msg1), and determines whether the base station schedules Msg3 retransmission through the information carried in Msg2.

[0159] (1) The judgment method of Msg3 repetition transmission is a 1-bit field in MAC subheader or subPDU. For example, the 1-bit field can be a 1-bit reserved field contained in the MAC subheader of RAR in the relevant protocol. When the 1-bit field is 0, it means that Msg3 repetition transmission is not scheduled, i.e., Msg3 single transmission is scheduled; for Msg3 repetition transmission terminals, when the 1-bit field is 1, it means that Msg3 repetition transmission is scheduled. For another example, the 1-bit field is a 1-bit reserved field contained in the MAC subPDU payload in the relevant protocol. When the 1-bit field is 0, it means that Msg3 repetition transmission is not scheduled, i.e., Msg3 single transmission is scheduled; for Msg3 repetition transmission terminals, when the 1-bit field is 1, it means that Msg3 repetition transmission is scheduled.

[0160] Further optionally, a 2-bit field in MAC subheader and subPDU is used to indicate the number of Msg3 repetition transmissions or the scaling factor N of the number of Msg3 repetition transmissions. The 2-bit field is composed of a 1-bit reserved field contained in the MAC subheader of RAR in the relevant protocol and a 1-bit reserved field contained in the MAC subPDU payload in the relevant protocol. When the 2-bit field is 00, it means that Msg3 repetition transmission is not scheduled; 01, 10, and 11 respectively represent three different repetition transmission numbers or scaling factors N of the number of Msg3 repetition transmissions, which are determined by protocol predefinition or system message configuration.

[0161] (2) The judgment method of Msg3 repetition transmission is a field in RAR UL grant. For example, when the CSI request field is 0, it means that Msg3 repetition transmission is not scheduled, and when it is 1, it means that Msg3 repetition transmission is scheduled. Or, the CSI request field indicates the selection of the TDRA table, i.e., when the CSI request field is 0, TDRA table 1 is used to interpret the TDRA field; when it is 1, TDRA table 2 is used to interpret the TDRA field. The TDRA table 1 and table 2 are pre-defined by the protocol or configured by the system message. Or, the CSI request field is used to indicate the scaling factor of the repetition number. That is, when the CSI request field is 0, the scaling factor is 1, and the transmission is performed using the repetition number indicated by the TDRA field; when it is 1, the scaling factor is N (e.g., 2), and the transmission is performed using N times of the repetition number indicated by the TDRA field. It can be understood that the configuration results of TDRA table 1 and TDRA table 2 are different from each other, and at least one of the tables explicitly indicates the number of Msg3 repetitions, and optionally one of the tables is the TDRA table for scheduling Msg3 single transmission defined in the prior art.

[0162] Another indication mode is to determine whether to schedule Msg3 repetition transmission or determine the number of Msg3 repetition transmission according to the re-interpretation of 3bit TPC field. Part of the value of TPC field indicates to schedule Msg3 repetition transmission, and the other part indicates not to schedule Msg3 repetition transmission. One possible definition is shown in Table 1. When TPC field is 000, 001, 010, 011, it indicates that the number of Msg3 transmission is 1, i.e. not to schedule Msg3 repetition transmission, and each value corresponds to a transmission power offset; other TPC field values indicate that the base station schedules Msg3 repetition transmission.

[0163] Another indication mode is to jointly indicate TDRA and power control parameters by TPC and TDRA fields. When TPC field value is 000 to 011, the number of repetitions is determined according to the special TDRA table, and the power control parameters corresponding to TPC values 000 to 011 are predefined by the protocol; when TPC field value is 100 to 111, the number of repetitions is determined according to the TDRA table and amplified by N times, N is a protocol predefined value (for example, 100 corresponds to N=0.5, 101 corresponds to N=1, 110 corresponds to N=2, 111 corresponds to N=3), and the power control parameters corresponding to TPC values 000 to 011 are predefined by the protocol.

[0164] Another indication mode is to redefine the 4bit MCS field to indicate whether to schedule Msg3 repetition transmission or determine the number of Msg3 repetition transmission. Specifically, part of the value of the MCS field indicates Msg3 repetition transmission, and the other part indicates not to schedule Msg3 repetition transmission. One possible definition is that when the value of the MCS field ranges from 0000 to 0111, it indicates not to schedule Msg3 repetition transmission, and 1000 to 1111 indicates to schedule Msg3 repetition transmission.

[0165] Another indication mode is to jointly indicate TDRA and MCS by MCS and TDRA fields. When the value of the MCS field ranges from 0000 to 0111, the number of repetitions is determined using the special TDRA table, and the MCS table corresponding to the values 0000 to 0111 of the MCS field is predefined by the protocol; when the value of the MCS field ranges from 1000 to 1111, the number of repetitions is determined according to the TDRA table and amplified by N times, N is a protocol predefined value (for example, N=2), and the MCS table corresponding to the values 0000 to 0111 of the MCS field is predefined by the protocol. It can be understood that the special TDRA table is used to indicate the time domain resource of Msg3 repetition transmission and the number of Msg3 repetition.

[0166] (Three) Msg3 repetition sending terminal determines TDRA table

[0167] If the base station does not schedule Msg3 repetition transmission, the terminal uses the TDRA table defined in the prior art to schedule the single transmission of Msg3. If the base station schedules Msg3 repetition transmission, the terminal uses a dedicated TDRA table, as shown in Table 2, which indicates the time domain resource configuration and the number of repetitions.

[0168] The dedicated TDRA table can be protocol predefined, or configured by system message, or determined by the above two ways. For example, the length of the TDRA field in the UL grant of Msg3 repetition transmission is 4 bits, and the TDRA field corresponds to a dedicated TDRA table with 16 rows. In the dedicated TDRA table, the contents of the first X rows are determined by protocol predefinition, and the contents of the remaining 16-X rows are configured by system message, such as the example in Table 1. The indication method of the system message can follow the parameter configuration method of PUSCH repetition typeA defined in the prior art NR Rel-15 / 16 protocol; or define a dedicated indication method, such as default PUSCH mapping typeA, indicate K2, PUSCH length, and Msg3 repetition number.

[0169] Further, when using the system message to indicate the entries of the dedicated TDRA table, the value range of the TDRA parameter can be different from the value range of the TDRA entry configuration parameter in the connected state. For example, the parameter k2 has a value range of 0-32 occupying 5 bits in the connected state, and a value range of 0-3 occupying 2 bits in the system message; the value range of the start symbol position and length startSymbolAndLength is 0-127, and the value range in the system message is 0-15 occupying 4 bits, wherein the start symbol position and length corresponding to the values 0-15 are protocol predefined. For another example, the system message configuration method can be a combination of the repetition number and the entries of the TDRA table of the single transmission of Msg3 in the prior art NR Rel-15 / 16 protocol. For example, if the repetition number contains 4 candidate values occupying 2 bits, and the TDRA table of the single transmission of Msg3 has 16 entries occupying 4 bits, the system message overhead for indicating a TDRA entry of Msg3 repetition transmission is 6 bits.

[0170] Further optionally, the length of the TDRA field or the field division of the UL grant is determined according to whether the base station schedules Msg3 repetition transmission. For example, if the base station schedules Msg3 repetition transmission, the TDRA field is 5 bits and the MCS field is 3 bits, wherein the 3-bit MCS field is used to indicate the first 8 MCS configurations in the MCS table; or the TDRA field is 5 bits and the TPC field is 2 bits, wherein the 2-bit TPC field redefines the power control value. The lengths and meanings of other fields remain unchanged.

[0171] II. Terminal determines the number of repetitions of the UL grant

[0172] The terminal determines the Msg3 time domain resource parameters and the number of repetitions according to the TDRA field of the UL grant, and determines according to the content of the entry of the above-mentioned TDRA table.

[0173] Optionally, the available time slots for Msg3 PUSCH repetition transmission are determined according to the MCS field or the TPC field in the UL grant, that is, the configuration parameters of the available time slots for Msg3 repetition transmission are determined through different values or value ranges of the MCS field or the TPC field, and the configuration parameters contain at least one of the following information:

[0174] (1) Temporary uplink-downlink time slot configuration. Through protocol predefinition or system message configuration, different uplink-downlink time slot configurations corresponding to part of the values of the TPC field are defined. The uplink-downlink time slot configuration information is pre-defined by the protocol or configured by the system message. The temporary uplink-downlink time slot configuration, together with the cell-level uplink-downlink time slot configuration broadcast by the system message, determines the uplink time slots and the uplink symbols in the time slots, and further determines the available time slots for Msg3 repetition transmission, that is, the uplink time slots and the time slots containing uplink symbols and having a time range greater than that of Msg3 are determined as available time slots.

[0175] (2) The number of available time slots for continuous transmission. For example, the TPC field is interpreted as bitmap information when its value is 100 to 111, which is used to indicate whether the first transmission of Msg3 starts from 3 consecutive time slots that are available time slots, where 1 represents an available time slot and 0 represents an unavailable time slot. Or the correspondence between part of the values of the TPC field and the number of available time slots for continuous transmission is defined by protocol predefinition or system message configuration.

[0176] (3) Through protocol predefinition or system message configuration, it is defined that the first transmission of Msg3 starts from M consecutive time slots that are available time slots. When the available time slots determined in the above manner conflict with the downlink time slots configured by the system message, the conflicting time slots are transmitted according to the time slot transmission direction determined by the system message. The value of M is contained in the TPC field or the MCS field. Or the value of M is a fixed value defined by the system message or the protocol.

[0177] The time slot configuration or the available time slots configured by the MCS field or the TPC field are only valid for Msg3 repetition transmission.

[0178] Table 1

[0179]

[0180] Optionally, before sending PRACH, determine the carrier supporting Msg3 repetition transmission.

[0181] When multiple carriers are available for uplink carrier, NUL and SUL, the carrier supporting Msg3 repetition transmission can be indicated by system message.

[0182] Further, the number of repetition transmission or dedicated TDRA table for the carrier supporting Msg3 repetition transmission is configured by system message respectively, or the terminal selects the SSB criteria. The terminal selects SSB criteria can be that the terminal selects one of the SSBs from the SSBs with channel quality higher than the first threshold as the SSB associated with the subsequent random access process, or selects one of the SSBs from the Y SSBs with the best channel quality as the SSB associated with the subsequent random access process, where Y is a positive integer and is predefined by the protocol or configured by system message.

[0183] The terminal selects and determines the uplink carrier. The Msg3 repetition transmission terminal determines the SUL decision threshold according to the rsrp-ThresholdSSB-SUL defined by the relevant protocol and the configuration of Msg3 repetition transmission of the uplink carrier. For the terminal supporting SUL and supporting Msg3 repetition, if the base station indicates that NUL supports Msg3 repetition transmission, then:

[0184] The terminal determines the dedicated SUL decision threshold and selects the uplink carrier using the dedicated threshold (i.e. according to RSRP, RSRP higher than the threshold selects NUL, lower than the threshold selects SUL). The dedicated threshold can be directly configured by system message, or calculated according to rsrp-ThresholdSSB-SUL defined by the relevant protocol, i.e. rsrp-ThresholdSSB-SUL+deta, where deta represents the offset configured by system message or determined according to the number of Msg3 repetition.

[0185] Table 2: Example of dedicated TDRA table for Msg3 repetition transmission

[0186]

[0187] Embodiment two of the application:

[0188] In this embodiment, the Msg3 repetition transmission terminal reads the TPC field in the UL grant, and determines the number of Msg3 repetition according to the content of the TPC field. The interpretation method of the TPC field can be defined as shown in Table 3. Or the values of TPC field 000 to 011 reuse the values of 2 bits of TPC field in DCI 1-0; the values of 100 to 111 are used to indicate the number of Msg3 repetition. The interpretation method of other fields of UL grant remains unchanged.

[0189] Table 3

[0190]

[0191] Embodiment three of the present application:

[0192] In this embodiment, the terminal reading the MCS field in the UL grant determines the number of Msg3 repetitions according to the MCS field. The MCS field is 4 bits, and different ranges of values correspond to different numbers of Msg3 repetitions, for example, 0000 to 0100 represent a repetition number of 1, 0101 to 1000 represent a repetition number of 2, 1001 to 1100 represent a repetition number of 4, and 1101 to 1111 represent a repetition number of 8; and correspond to the first N MCS configurations in the MCS table respectively.

[0193] Embodiment four of the present application:

[0194] In this embodiment, the terminal reading the TDRA field in the UL grant determines the number of Msg3 repetitions according to the MCS field. The MCS field is 4 bits, and the number of repetitions is determined by reading the corresponding entry in the dedicated TDRA table as shown in Table 4. The dedicated TDRA table can be pre-defined by the protocol, or configured by the system message, or determined by the combination of the above two ways. Each configuration entry in the dedicated TDRA table indicates a repetition number.

[0195] Another possibility is that the terminal reads a 5-bit length MCS field and a 3-bit length MCS field. The number of repetitions is determined according to the dedicated TDRA table corresponding to the 5-bit length MCS field.

[0196] Table 4

[0197]

[0198]

[0199] Embodiment five of the present application:

[0200] In this embodiment, Msg3 retransmission is scheduled by DCI 0-0 scrambled with TC-RNTI. The MCS and TPC fields in the DCI 0-0 field determine the number of Msg3 repetitions according to the scheme in the above embodiment.

[0201] The New data indicator in the DCI scrambled with TC-RNTI, and the HARQ process number field is defined as an indicator indicating the number of Msg3 repetition transmissions or whether the Msg3 repetition is scheduled in the retransmission scheduling of the Msg3 repetition transmission.

[0202] It should be noted that the method for determining the number of Msg3 repetition transmissions provided in the embodiments of the present application can be executed by a device for determining the number of Msg3 repetition transmissions, or a module in the device for determining the number of Msg3 repetition transmissions for executing the method for determining the number of Msg3 repetition transmissions. In the embodiments of the present application, the device for determining the number of Msg3 repetition transmissions is taken as an example for executing the method for determining the number of Msg3 repetition transmissions, and the method for determining the number of Msg3 repetition transmissions provided in the embodiments of the present application is described.

[0203] The embodiments of the present application provide a device for determining the number of Msg3 repetition transmissions, which is applied to a terminal 300, as shown in the figure. Figure 4 The device comprises:

[0204] A receiving module 310 is configured to receive Msg3 scheduling information of a network side device after sending a first Msg1 to the network side device;

[0205] A determining module 320 is configured to determine the number of Msg3 repetition transmissions according to the Msg3 scheduling information.

[0206] The first Msg1 is an uplink signal for requesting Msg3 repetition transmission by the terminal, and the Msg3 scheduling information is Msg2 scheduling initial transmission of Msg3 or DCI scheduling retransmission of Msg3.

[0207] In some embodiments, the determining module 320 is specifically configured to listen to Msg2 in a RAR window, detect a specific field of Msg2, and determine whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to the specific field, wherein the specific field adopts any one of the following:

[0208] A field in a MAC PDU subheader;

[0209] A field in a MAC subPDU;

[0210] A field in an UL grant.

[0211] In some embodiments, the determining module 320 is specifically configured to determine whether to schedule Msg3 repetition transmission through a 1-bit field in a MAC subPDU or a MAC PDU subheader; and / or

[0212] A scaling factor N of the number of Msg3 repetition transmissions is determined by a 2-bit field in the MAC subPDU and the MAC PDU subheader.

[0213] In some embodiments, the determining module 320 is specifically configured to perform the transmission using N times of the determined number of Msg3 repetition transmissions.

[0214] In some embodiments, the 2-bit field is composed of a 1-bit field in the MAC PDU subheader and a 1-bit field in the MAC subPDU.

[0215] In some embodiments, the determining module 320 is specifically configured to determine whether the Msg3 repetition transmission is scheduled and the number of Msg3 repetition transmissions according to a first field in the UL grant, the first field including at least one of the following:

[0216] a CSI request field;

[0217] an MCS field;

[0218] a TPC field;

[0219] a TDRA field.

[0220] In some embodiments, a part of the TPC field has a value indicating that the Msg3 repetition transmission is scheduled, and another part has a value indicating that the Msg3 repetition transmission is not scheduled; or

[0221] a part of the MCS field has a value indicating that the Msg3 repetition transmission is scheduled, and another part has a value indicating that the Msg3 repetition transmission is not scheduled.

[0222] In some embodiments, different ranges of values of the MCS field correspond to different numbers of Msg3 repetition transmissions.

[0223] In some embodiments, the CSI request field, or a 1-bit field in the MAC subPDU, or a 1-bit field in the MAC PDU subheader, or a 2-bit field in the MAC subPDU and the MAC PDU subheader indicates any of the following:

[0224] whether the Msg3 repetition transmission is scheduled;

[0225] selection of a TDRA table;

[0226] a scaling factor of the number of repetitions.

[0227] In some embodiments, the determining module 320 is further configured to determine a TDRA table, and if a specific field in the Msg2 indicates that the network device schedules the Msg3 repetition transmission, use a dedicated TDRA table to interpret the TDRA field in the UL grant after sending the first Msg1 to the network device.

[0228] Each entry in the dedicated TDRA table indicates a time domain resource configuration and a number of Msg3 repetitions.

[0229] In some embodiments, the dedicated TDRA table is predefined by a protocol and / or configured by the network device through a system message.

[0230] In some embodiments, the determining module 320 is further configured to determine a length of the TDRA field or a field division of the UL grant according to whether the network device schedules the Msg3 repetition transmission.

[0231] In some embodiments, the TPC field and the TDRA field jointly indicate the TDRA and the power control parameter; or

[0232] The MCS field and the TDRA field jointly indicate the TDRA and the MCS.

[0233] In some embodiments, the determining module 320 is specifically configured to perform any one of the following:

[0234] determine that the TDRA field is greater than a first preset value, and a total number of entries in the dedicated TDRA table is greater than a second preset value and does not exceed an indication range of the TDRA field;

[0235] a length of the TPC field or the MCS field is less than a third preset value.

[0236] In some embodiments, content of the TDRA entry is configured by the network device through a system message.

[0237] In some embodiments, the determining module 320 is further configured to determine available time slots for the Msg3 PUSCH repetition transmission according to the MCS field or the TPC field.

[0238] In some embodiments, a specific value or a specific value range of the MCS field or the TPC field indicates time slot configuration information or a number of consecutive available time slots for a first transmission of the Msg3 repetition transmission.

[0239] The time slot configuration information is predefined by a protocol or configured by a system message of the network device, and indicates uplink and downlink time slot configurations in the Msg3 repetition transmission.

[0240] The number of consecutive available time slots of the first transmission of the Msg3 repetition transmission is predefined by a protocol or configured by a system message of the network-side device, and the first available time slot of the Msg3 repetition transmission determined by the UL grant starts from the consecutive M time slots, where M is a positive integer.

[0241] In some embodiments, the determining module 320 is further configured to determine the carrier of the uplink initial BWP, including:

[0242] If multiple carriers are available for the uplink carrier, the carrier of the uplink initial BWP is determined by a system message of the network-side device.

[0243] In some embodiments, the determining module 320 is further configured to determine a first decision threshold and select the uplink carrier using the first decision threshold if the network-side device supports SUL capability and supports Msg3 repetition transmission on NUL, where the first decision threshold is explicitly configured by a system message or implicitly calculated according to the number of Msg3 repetitions.

[0244] In some embodiments, the determining module 320 is further configured to determine whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to a second field in the DCI, where the second field includes at least one of:

[0245] a TDRA field;

[0246] a TPC field;

[0247] an MCS field;

[0248] a new data indicator field;

[0249] a HARQ process number field.

[0250] In some embodiments, the determining module 320 is further configured to perform any one of the following:

[0251] determine the number of Msg3 repetition transmissions or an adjustment amount of the number of Msg3 repetitions according to the content of the TPC field;

[0252] determine the number of Msg3 repetition transmissions or an adjustment amount of the number of Msg3 repetitions according to the content of the MCS field;

[0253] determine a corresponding dedicated TDRA table according to the new data indicator field, and determine the number of Msg3 repetition transmissions according to the dedicated TDRA table;

[0254] determine the number of Msg3 repetitions in a corresponding dedicated TDRA table according to the TDRA field;

[0255] The Msg3 repetition number is determined according to the HARQ process number field.

[0256] The Msg3 repetition number determination apparatus in the embodiments of the present application can be an apparatus, an apparatus with an operating system, or an electronic device, and can also be a component in a terminal, an integrated circuit, or a chip. The apparatus or the electronic device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include, but is not limited to, the types of the terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a cash register, a self-service machine, and the like, without specific limitation in the embodiments of the present application.

[0257] The Msg3 repetition number determination apparatus provided in the embodiments of the present application can implement the various processes of the method embodiments and achieve the same technical effects, and thus repeated descriptions are not given herein. Figure 2

[0258] The embodiments of the present application provide a Msg3 repetition number indication apparatus, applied to a network side device 400, as shown in Figure 5 The apparatus includes:

[0259] A receiving module 410 is configured to receive a first Msg1 of a terminal, the first Msg1 being an uplink signal in which the terminal requests Msg3 repetition transmission;

[0260] A sending module 420 is configured to send Msg3 scheduling information to the terminal, the Msg3 scheduling information indicating the number of Msg3 repetition transmissions, and the Msg3 scheduling information being Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission.

[0261] In some embodiments, the sending module 420 is specifically configured to indicate whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions through a specific field of the Msg2, and the specific field uses any of the following:

[0262] A field in a MAC PDU subheader;

[0263] A field in a MAC subPDU;

[0264] A field in an UL grant.

[0265] ​In some embodiments, the sending module 420 is specifically configured to indicate whether to schedule Msg3 repetition transmission through a 1-bit field in a MAC subPDU or a MAC PDU subheader; and / or

[0266] The number of Msg3 repetition transmissions is indicated through a 2-bit field in a MAC subPDU and a MAC PDU subheader.

[0267] In some embodiments, the 2-bit field is composed of a 1-bit field in a MAC PDU subheader and a 1-bit field in a MAC subPDU.

[0268] In some embodiments, the sending module 420 is specifically configured to indicate whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions through a first field in an UL grant, and the first field includes at least one of the following:

[0269] A CSI request field;

[0270] A MCS field;

[0271] A TPC field;

[0272] A TDRA field.

[0273] In some embodiments, a part of the TPC field takes a value to indicate scheduling Msg3 repetition transmission, and another part takes a value to indicate not scheduling Msg3 repetition transmission; or

[0274] A part of the MCS field takes a value to indicate scheduling Msg3 repetition transmission, and another part takes a value to indicate not scheduling Msg3 repetition transmission.

[0275] In some embodiments, different value ranges of the MCS field correspond to different numbers of Msg3 repetition.

[0276] In some embodiments, the CSI request field, or a 1-bit field in a MAC subPDU or a MAC PDU subheader, or a 2-bit field in a MAC subPDU and a MAC PDU subheader indicates any of the following:

[0277] Indicates whether to schedule Msg3 repetition transmission;

[0278] Indicates the selection of a TDRA table;

[0279] Indicates the scaling factor of the number of repetitions.

[0280] In some embodiments, each entry in the dedicated TDRA table in the TDRA field indicates a time domain resource configuration and a number of Msg3 repetitions.

[0281] In some embodiments, the dedicated TDRA table is predefined by a protocol and / or configured by a network-side device through a system message.

[0282] In some embodiments, the TPC field and the TDRA field jointly indicate a TDRA and a power control parameter; or

[0283] the MCS field and the TDRA field jointly indicate a TDRA and an MCS.

[0284] In some embodiments, the content of the TDRA entry is indicated by a network-side device through a system message.

[0285] In some embodiments, the sending module 420 is specifically configured to indicate, to the terminal, available time slots for Msg3 PUSCH repetition transmission through the MCS field or the TPC field.

[0286] In some embodiments, a specific value or a specific value range of the MCS field or the TPC field indicates time slot configuration information or a number of consecutive available time slots for a first transmission of Msg3 repetition transmission;

[0287] The time slot configuration information is predefined by a protocol or configured by a system message of a network-side device, and indicates uplink and downlink time slot configuration in Msg3 repetition transmission.

[0288] The number of consecutive available time slots for the first transmission of Msg3 repetition transmission is predefined by a protocol or configured by a system message of a network-side device, and indicates that a first available time slot for Msg3 repetition transmission determined by the UL grant starts from consecutive M time slots, where M is a positive integer.

[0289] In some embodiments, the sending module 420 is further configured to indicate, to the terminal, a carrier supporting Msg3 repetition transmission through a system message if multiple carriers are available for an uplink carrier.

[0290] In some embodiments, the sending module 420 is further configured to indicate, through a second field in the DCI, whether to schedule Msg3 repetition transmission and a number of Msg3 repetition transmissions, and the second field includes at least one of the following:

[0291] a TDRA field;

[0292] a TPC field;

[0293] an MCS field;

[0294] a new data indicator field;

[0295] HARQ process number field.

[0296] In some embodiments, the sending module 420 is specifically configured to perform any one of the following:

[0297] indicate the number of Msg3 repetitions or the adjustment amount of the number of Msg3 repetitions through the content in the TPC field;

[0298] indicate the number of Msg3 repetitions or the adjustment amount of the number of Msg3 repetitions through the content in the MCS field;

[0299] indicate the number of Msg3 repetitions through the dedicated TDRA table corresponding to the New data indicator field;

[0300] indicate the number of Msg3 repetitions in the corresponding dedicated TDRA table through the TDRA field;

[0301] indicate the number of Msg3 repetitions according to the HARQ process number field.

[0302] The Msg3 repetition number indication apparatus provided by the embodiments of the present application can implement the various processes of the method embodiments and achieve the same technical effects. To avoid repetition, the various processes will not be described here again. Figure 3

[0303] Optionally, as shown in Figure 6 the embodiments of the present application also provide a communication device 500, which includes a processor 501, a memory 502, a program or instruction stored in the memory 502 and executable on the processor 501. For example, when the communication device 500 is a terminal, the program or instruction is executed by the processor 501 to implement the various processes of the above-mentioned Msg3 repetition number determination method embodiments applied to the terminal, and the same technical effects can be achieved. When the communication device 500 is a network side device, the program or instruction is executed by the processor 501 to implement the various processes of the above-mentioned Msg3 repetition number indication method embodiments applied to the network side device, and the same technical effects can be achieved. To avoid repetition, the various processes will not be described here again.

[0304] ​The terminal provided in the embodiments of the present application also includes a processor and a communication interface. The processor is configured to receive Msg3 scheduling information of a network side device after sending a first Msg1 to the network side device, and determine a number of repeated transmissions of Msg3 according to the Msg3 scheduling information. The first Msg1 is an uplink signal in which the terminal requests repeated transmission of Msg3, and the Msg3 scheduling information is Msg2 scheduling initial transmission of Msg3 or DCI scheduling retransmission of Msg3. The terminal embodiment corresponds to the terminal side method embodiment described above. Each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, Figure 7 A hardware structure diagram of a terminal according to an embodiment of the present application is shown in FIG. 10.

[0305] The terminal 1000 includes, but is not limited to, at least part of components such as a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

[0306] Those skilled in the art can understand that the terminal 1000 can also include a power supply (such as a battery) for supplying power to each component. The power supply can be logically connected to the processor 1010 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in FIG. 10 does not constitute a limitation on the terminal. The terminal can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components, which will not be described here.

[0307] It should be understood that in the embodiments of the present application, the input unit 1004 can include a graphics processing unit (GPU) 10041 and a microphone 10042. The graphics processing unit 10041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 can include a display panel 10061, which can be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 can include a touch detection device and a touch controller. The other input devices 10072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, etc., which will not be described here.

[0308] In the embodiments of the present application, the radio frequency unit 1001 receives the downlink data from the network side device and processes the data for the processor 1010. In addition, the radio frequency unit 1001 sends the uplink data to the network side device. Generally, the radio frequency unit 1001 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0309] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), etc. In addition, the memory 1009 can include a high-speed random access memory, and can also include a non-volatile memory, which can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state memory device.

[0310] The processor 1010 can include one or more processing units; optionally, the processor 1010 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1010.

[0311] The processor 1010 is configured to send a first Msg1 to a network side device, receive Msg3 scheduling information of the network side device after sending the first Msg1, determine a Msg3 repetition transmission number according to the Msg3 scheduling information, wherein the first Msg1 is an uplink signal for the terminal to request Msg3 repetition transmission, and the Msg3 scheduling information is a Msg2 scheduling Msg3 initial transmission or a DCI scheduling Msg3 retransmission.

[0312] In some embodiments, the processor 1010 is specifically configured to listen to a Msg2 in a RAR window, detect a specific field of the Msg2, and determine whether to schedule Msg3 repetition transmission and a Msg3 repetition transmission number according to the specific field, wherein the specific field adopts any one of the following:

[0313] a field in a MAC PDU subheader;

[0314] a field in a MAC subPDU;

[0315] Fields in UL grant.

[0316] In some embodiments, the processor 1010 is specifically configured to determine whether to schedule Msg3 repetition transmission through a 1-bit field in a MAC subPDU or a MAC PDU subheader; and / or

[0317] Determine a scaling factor N of the number of Msg3 repetition transmissions through a 2-bit field in a MAC subPDU and a MAC PDU subheader.

[0318] In some embodiments, the processor 1010 is specifically configured to transmit using N times the determined number of Msg3 repetition transmissions.

[0319] In some embodiments, the 2-bit field is composed of a 1-bit field in a MAC PDU subheader and a 1-bit field in a MAC subPDU.

[0320] In some embodiments, the processor 1010 is specifically configured to determine whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to a first field in a UL grant, the first field including at least one of:

[0321] A CSI request field;

[0322] A MCS field;

[0323] A TPC field;

[0324] A TDRA field.

[0325] In some embodiments, a part of the TPC field has a value indicating scheduling Msg3 repetition transmission, and another part has a value indicating not scheduling Msg3 repetition transmission; or

[0326] A part of the MCS field has a value indicating scheduling Msg3 repetition transmission, and another part has a value indicating not scheduling Msg3 repetition transmission.

[0327] In some embodiments, different value ranges of the MCS field correspond to different numbers of Msg3 repetition.

[0328] In some embodiments, the CSI request field, or a 1-bit field in a MAC subPDU, or a 1-bit field in a MAC PDU subheader, or a 2-bit field in a MAC subPDU and a MAC PDU subheader indicates any of:

[0329] indicate whether to schedule Msg3 repetition transmission;

[0330] indicate selection of a TDRA table;

[0331] indicate a scaling factor of repetition number.

[0332] In some embodiments, the processor 1010 is further configured to determine a TDRA table, and after sending the first Msg1 to the network side device, if a specific field in the Msg2 indicates to schedule Msg3 repetition transmission, use a dedicated TDRA table to interpret the TDRA field in the UL grant;

[0333] each entry in the dedicated TDRA table indicates time domain resource configuration and Msg3 repetition number.

[0334] In some embodiments, the dedicated TDRA table is predefined by a protocol and / or configured by the network side device through a system message.

[0335] In some embodiments, the processor 1010 is further configured to determine the length of the TDRA field or the field division of the UL grant according to whether the network side device schedules Msg3 repetition transmission.

[0336] In some embodiments, the TPC field and the TDRA field jointly indicate TDRA and power control parameters; or

[0337] the MCS field and the TDRA field jointly indicate TDRA and MCS.

[0338] In some embodiments, the processor 1010 is specifically configured to perform any one of the following:

[0339] determine that the TDRA field is greater than a first preset value, and the total number of entries of the dedicated TDRA table is greater than a second preset value and does not exceed the indication range of the TDRA field;

[0340] the length of the TPC field or the MCS field is less than a third preset value.

[0341] In some embodiments, the content of the TDRA entry is configured by the network side device through a system message.

[0342] In some embodiments, the processor 1010 is further configured to determine available time slots for Msg3 PUSCH repetition transmission according to the MCS field or the TPC field.

[0343] In some embodiments, a specific value or a specific value range of the MCS field or the TPC field indicates time slot configuration information or the number of consecutive available time slots for the first transmission of Msg3 repetition transmission.

[0344] The time slot configuration information is predefined by a protocol or configured by a system message of the network side device, and indicates uplink and downlink time slot configuration in Msg3 repetition transmission.

[0345] The number of continuous available time slots of the first transmission of the Msg3 repetition transmission is predefined by a protocol or configured by a system message of the network side device, and indicates that the first available time slot determined by the UL grant starts from the continuous M time slots, and M is a positive integer.

[0346] In some embodiments, the processor 1010 is further configured to determine the carrier of the uplink initial BWP, including:

[0347] If multiple carriers are available for the uplink carrier, the carrier of the uplink initial BWP is determined by a system message of the network side device.

[0348] In some embodiments, the processor 1010 is further configured to determine a first decision threshold and select the uplink carrier using the first decision threshold if the network side device supports SUL capability and supports Msg3 repetition transmission on NUL, the first decision threshold being explicitly configured by a system message or implicitly calculated according to the number of Msg3 repetitions.

[0349] In some embodiments, the processor 1010 is further configured to determine whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmissions according to a second field in the DCI, the second field including at least one of:

[0350] a TDRA field;

[0351] a TPC field;

[0352] an MCS field;

[0353] a new data indicator field;

[0354] a HARQ process number field.

[0355] In some embodiments, the processor 1010 is further configured to perform any one of:

[0356] determine the number of Msg3 repetition transmissions or determine the adjustment amount of the number of Msg3 repetitions according to the content of the TPC field;

[0357] determine the number of Msg3 repetition transmissions or determine the adjustment amount of the number of Msg3 repetitions according to the content of the MCS field;

[0358] determine a corresponding dedicated TDRA table according to the new data indicator field, and determine the number of Msg3 repetition transmissions according to the dedicated TDRA table;

[0359] determining the number of Msg3 repetitions according to the TDRA field in the corresponding dedicated TDRA table;

[0360] determining the number of Msg3 repetitions according to the HARQ process number field.

[0361] The embodiment of the present application also provides a network side device, comprising a processor and a communication interface, the communication interface is used for receiving a first Msg1 of a terminal, the first Msg1 is an uplink signal used by the terminal to request Msg3 repetition transmission; and the network side device is used for sending Msg3 scheduling information to the terminal, the Msg3 scheduling information is used for indicating the number of Msg3 repetition transmissions, and the Msg3 scheduling information is Msg2 used for scheduling Msg3 initial transmission or DCI used for scheduling Msg3 retransmission. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

[0362] Specifically, the embodiment of the present application also provides a network side device. As shown in the Figure 8 The network device 700 comprises an antenna 71, a radio frequency device 72 and a baseband device 73. The antenna 71 is connected with the radio frequency device 72. In the uplink direction, the radio frequency device 72 receives information through the antenna 71, and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be sent, and sends the processed information to the radio frequency device 72. The radio frequency device 72 processes the received information, and sends the processed information through the antenna 71.

[0363] The above frequency band processing device can be located in the baseband device 73. The method executed by the network side device in the above embodiment can be implemented in the baseband device 73. The baseband device 73 comprises a processor 74 and a memory 75.

[0364] The baseband device 73 can comprise at least one baseband board, and a plurality of chips are arranged on the baseband board, as shown in the Figure 8 One of the chips is a processor 74, which is connected with the memory 75 to call the program in the memory 75 and execute the network device operation shown in the above method embodiment.

[0365] The baseband device 73 can also comprise a network interface 76 for interacting information with the radio frequency device 72. The interface is, for example, a common public radio interface (CPRI).

[0366] Specifically, the network side device of the embodiment of the present application further comprises instructions or programs stored on the memory 75 and executable on the processor 74, and the processor 74 invokes the instructions or programs in the memory 75 to execute the method shown by each module and achieve the same technical effect, and thus the details are not described herein again. Figure 5 The method executed by each module shown and the same technical effect achieved are not described herein again to avoid repetition.

[0367] The embodiment of the present application further provides a readable storage medium, and the readable storage medium stores programs or instructions, the programs or instructions are executed by a processor to implement each process of the method for determining the number of Msg3 repetitions or the method for indicating the number of Msg3 repetitions, and the same technical effect can be achieved, and thus the details are not described herein again to avoid repetition.

[0368] The processor is the processor in the terminal in the above-described embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

[0369] The embodiment of the present application further provides a chip, and the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run programs or instructions to implement each process of the method for determining the number of Msg3 repetitions or the method for indicating the number of Msg3 repetitions, and the same technical effect can be achieved, and thus the details are not described herein again to avoid repetition.

[0370] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, and the like.

[0371] It should be noted that in this paper, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the present application is not limited to the order of functions shown or discussed, and can also include functions performed in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method can be performed in an order different from the described order, and various steps can also be added, omitted or combined. In addition, the features described with reference to certain examples can be combined in other examples.

[0372] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned example methods can be realized by means of software and a necessary general hardware platform, and of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a computer software product in essence or in the form of a part that contributes to the prior art, which is stored in a storage medium (such as a ROM / RAM, a magnetic disc, an optical disc), and includes a plurality of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present application.

[0373] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, and the above-mentioned specific embodiments are only illustrative and not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims.

Claims

1. A method for determining the number of repetitions of Msg3, characterized in that, The method is performed by a terminal and comprises: after sending a first Msg1 to a network side device, receiving Msg3 scheduling information of the network side device, and determining a number of Msg3 repeated transmissions according to the Msg3 scheduling information; the first Msg1 is an uplink signal in which the terminal requests Msg3 repeated transmission, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or downlink control information (DCI) scheduling Msg3 retransmission; the determining of the number of Msg3 repeated transmissions according to the Msg3 scheduling information comprises: listening to Msg2 in a random access response (RAR) window, detecting a specific field of the Msg2, and determining whether to schedule Msg3 repeated transmission and the number of Msg3 repeated transmissions according to the specific field, wherein the specific field uses a field in UL grant.

2. The method of claim 1, wherein, the specific field also uses any one of the following: a field in MAC PDU subheader; and a field in MAC subPDU.

3. The method of claim 2, wherein: whether to schedule Msg3 repeated transmission is determined by a 1-bit field in MAC subPDU or MAC PDU subheader; and / or a scaling factor N of the number of Msg3 repeated transmissions is determined by a 2-bit field in MAC subPDU and MAC PDU subheader.

4. The method of claim 3, wherein, transmission is performed using N times the determined number of Msg3 repeated transmissions.

5. The method of claim 3, wherein, the 2-bit field is composed of a 1-bit field in MAC PDU subheader and a 1-bit field in MAC subPDU.

6. The method of claim 2, wherein, the determining of the number of Msg3 repeated transmissions according to the Msg3 scheduling information specifically comprises: whether to schedule Msg3 repeated transmission and the number of Msg3 repeated transmissions are determined according to a first field in UL grant, wherein the first field includes at least one of the following: a CSI request field; an MCS field; a TPC field; and a TDRA field.

7. The method of claim 6, wherein: one part of the TPC field has a value indicating scheduling of Msg3 repeated transmission, and another part has a value indicating no scheduling of Msg3 repeated transmission; or one part of the MCS field has a value indicating scheduling of Msg3 repeated transmission, and another part has a value indicating no scheduling of Msg3 repeated transmission.

8. The method of claim 6, wherein: different value ranges of the MCS field correspond to different numbers of Msg3 repeated transmissions.

9. The method of claim 6, wherein, a 1-bit field in the CSI request field, or a MAC subPDU, or a MAC PDU subheader, or a 2-bit field in the MAC subPDU and the MAC PDU subheader indicates any one of the following: whether to schedule Msg3 repeated transmission; selection of a TDRA table; and a scaling factor of the number of repeated transmissions.

10. The method of claim 6 or 8, wherein, the method further comprises determining a TDRA table, comprising: After sending the first Msg1 to the network side device, if a specific field in the Msg2 indicates scheduling of Msg3 repeated transmission, a dedicated TDRA table is used to interpret the TDRA field in the UL grant; Each entry in the dedicated TDRA table indicates a time domain resource configuration and a number of Msg3 repetitions.

11. The method of claim 10, wherein, The dedicated TDRA table is predefined by a protocol and / or configured by the network side device through a system message.

12. The method of claim 10, wherein, Further comprising: Determining the length of the TDRA field or the field division of the UL grant according to whether the network side device schedules Msg3 repeated transmission.

13. The method of claim 6, wherein, The TPC field and the TDRA field jointly indicate the TDRA and the power control parameter; or The MCS field and the TDRA field jointly indicate the TDRA and the MCS.

14. The method of claim 12, wherein, Determining the length of the TDRA field or the field division of the UL grant includes any of the following: Determining that the TDRA field is greater than a first preset value, and the total number of entries in the dedicated TDRA table is greater than a second preset value and does not exceed the indication range of the TDRA field; The length of the TPC field or the MCS field is less than a third preset value.

15. The method of claim 6, wherein, The content of the TDRA entry is configured by the network side device through a system message.

16. The method of claim 6, wherein, Further comprising: Determining the available time slots for Msg3 PUSCH repeated transmission according to the MCS field or the TPC field.

17. The method of claim 16, wherein A specific value or a specific value range of the MCS field or the TPC field indicates time slot configuration information or the number of consecutive available time slots for the first transmission of Msg3 repeated transmission; The time slot configuration information is predefined by a protocol or configured by a system message of the network side device, and indicates uplink and downlink time slot configuration in Msg3 repeated transmission; The number of consecutive available time slots for the first transmission of Msg3 repeated transmission is predefined by a protocol or configured by a system message of the network side device, and indicates that the first available time slot determined by the UL grant starts with M consecutive time slots, and M is a positive integer.

18. The method of claim 1, wherein, Before sending the first Msg1, the method further comprises: Determining the carrier of the uplink initial BWP, comprising: If multiple carriers are available for the uplink carrier, determining the carrier of the uplink initial BWP through a system message of the network side device.

19. The method of claim 18, wherein If the network side device supports SUL capability and supports Msg3 repeated transmission on NUL, determining a first decision threshold and selecting the uplink carrier using the first decision threshold, the first decision threshold being explicitly configured through a system message or implicitly calculated according to the number of Msg3 repetitions.

20. The method of claim 6, wherein, Determining the number of Msg3 repetitions according to the Msg3 scheduling information includes: Determining whether to schedule Msg3 repeated transmission and the number of Msg3 repetitions according to a second field in the DCI, the second field including at least one of the following: The TDRA field; The TPC field; The MCS field; The New data indicator field; The HARQ process number field.

21. The method of claim 20, wherein, According to the second field in the DCI, whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmission include any of the following: According to the content in the TPC field, determine the number of Msg3 repetition transmission or determine the adjustment amount of the number of Msg3 repetition; According to the content in the MCS field, determine the number of Msg3 repetition transmission or determine the adjustment amount of the number of Msg3 repetition; According to the New data indicator field, determine the corresponding dedicated TDRA table, and determine the number of Msg3 repetition transmission according to the dedicated TDRA table; According to the TDRA field, determine the number of Msg3 repetition in the corresponding dedicated TDRA table; According to the HARQ process number field, determine the number of Msg3 repetition. 22.A method for indicating a number of Msg3 repetitions, the method comprising: Executed by a network side device, comprising: Receive the first Msg1 of the terminal, the first Msg1 is an uplink signal of the terminal requesting Msg3 repetition transmission; Send Msg3 scheduling information to the terminal, indicate the number of Msg3 repetition transmission through the Msg3 scheduling information, the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission; Through the specific field of the Msg2, indicate whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmission, the specific field uses the field in the UL grant.

23. The method of claim 22, wherein, The specific field also uses any of the following: The field in the MAC PDU subheader; The field in the MAC subPDU.

24. The method of claim 23, wherein Indicate whether to schedule Msg3 repetition transmission through the 1bit field in the MAC subPDU or the MAC PDU subheader; and / or Indicate the scaling coefficient N of the number of Msg3 repetition transmission through the 2bit field in the MAC subPDU and the MAC PDU subheader.

25. The method of claim 24, wherein, The 2bit field is composed of the 1bit field in the MAC PDU subheader and the 1bit field in the MAC subPDU.

26. The method of claim 25, wherein, Indicate whether to schedule Msg3 repetition transmission and the number of Msg3 repetition transmission through the first field in the UL grant, the first field includes at least one of the following: CSI request field; MCS field; TPC field; TDRA field.

27. The method of claim 26, wherein, Part of the value of the TPC field represents scheduling Msg3 repetition transmission, and the other part represents not scheduling Msg3 repetition transmission; or Part of the value of the MCS field represents scheduling Msg3 repetition transmission, and the other part represents not scheduling Msg3 repetition transmission.

28. The method of claim 26, wherein Different value ranges of the MCS field correspond to different numbers of Msg3 repetition.

29. The method of claim 26, wherein, The CSI request field, or a 1-bit field in the MAC subPDU, or a 1-bit field in the MAC PDU subheader, or a 2-bit field in the MAC subPDU and the MAC PDU subheader indicates any of the following: Indicates whether to schedule Msg3 repetition transmission; Indicates the selection of the TDRA table; Indicates the scaling factor of the repetition number.

30. The method of claim 26, wherein, In the TDRA field, each entry in the dedicated TDRA table indicates the time domain resource configuration and the number of Msg3 repetitions.

31. The method of claim 30, wherein, The dedicated TDRA table is pre-defined by the protocol and / or configured by the network side device through the system message.

32. The method of claim 26, wherein, The TPC field and the TDRA field jointly indicate the TDRA and the power control parameter; or The MCS field and the TDRA field jointly indicate the TDRA and the MCS.

33. The method of claim 26, wherein, The content of the TDRA entry is indicated by the network side device through the system message.

34. The method of claim 26, wherein, Further comprising: Indicating the available time slots for Msg3 PUSCH repetition transmission to the terminal through the MCS field or the TPC field.

35. The method of claim 34, wherein: A specific value or a specific value range of the MCS field or the TPC field indicates the time slot configuration information or the number of consecutive available time slots for the first transmission of the Msg3 repetition transmission; The time slot configuration information is pre-defined by the protocol or configured by the system message of the network side device, indicating the uplink and downlink time slot configuration in the Msg3 repetition transmission; The number of consecutive available time slots for the first transmission of the Msg3 repetition transmission is pre-defined by the protocol or configured by the system message of the network side device, indicating that the first available time slot determined by the UL grant starts from the consecutive M time slots, and M is a positive integer.

36. The method of indication of number of Msg3 repetitions according to claim 22, wherein, Before receiving the first Msg1, the method further comprises: If multiple carriers are available for the uplink carrier, indicating the carrier supporting the Msg3 repetition transmission to the terminal through the system message.

37. The method of indicating the number of Msg3 repetitions according to claim 26, wherein, The method specifically comprises: Indicating whether to schedule the Msg3 repetition transmission and the number of Msg3 repetition transmissions through a second field in the DCI, the second field comprising at least one of the following: TDRA field; TPC field; MCS field; New data indicator field; HARQ process number field.

38. The method of claim 37, wherein, Indicating whether to schedule the Msg3 repetition transmission and the number of Msg3 repetition transmissions through the second field in the DCI comprises any of the following: Indicating the number of Msg3 repetition transmissions or the adjustment amount of the number of Msg3 repetition transmissions through the content in the TPC field; Indicating the number of Msg3 repetition transmissions or the adjustment amount of the number of Msg3 repetition transmissions through the content in the MCS field; Indicating the number of Msg3 repetition transmissions through the dedicated TDRA table corresponding to the new data indicator field; Indicating the number of Msg3 repetition transmissions through the dedicated TDRA table corresponding to the TDRA field; Indicating the number of Msg3 repetition transmissions according to the HARQ process number field.

39. An Msg 3 repetition number determination apparatus, comprising: Applied to a terminal, comprising: a receiving module, configured to receive Msg3 scheduling information of a network side device after sending a first Msg1 to the network side device; a determining module, configured to determine a number of Msg3 repeated transmissions according to the Msg3 scheduling information; the first Msg1 is an uplink signal for requesting Msg3 repeated transmissions by the terminal, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission; the determining module is specifically configured to listen to Msg2 within a RAR window, detect a specific field of the Msg2, and determine whether to schedule Msg3 repeated transmissions and the number of Msg3 repeated transmissions according to the specific field, wherein the specific field adopts a field in UL grant.

40. The Msg3 repeated transmission number determination apparatus according to claim 39, wherein the specific field further adopts any one of the following: a field in MAC PDU subheader; a field in MAC subPDU.

41. The Msg3 repetition number determination apparatus of claim 40, wherein, The determining module is specifically configured to determine whether to schedule Msg3 repeated transmissions and the number of Msg3 repeated transmissions according to a first field in UL grant, wherein the first field includes at least one of the following: a CSI request field; an MCS field; a TPC field; a TDRA field.

42. A Msg3 repetition count indicator, characterized in that, Applied to a network side device, comprising: a receiving module, configured to receive a first Msg1 of a terminal, wherein the first Msg1 is an uplink signal for requesting Msg3 repeated transmissions by the terminal; a sending module, configured to send Msg3 scheduling information to the terminal, wherein the Msg3 scheduling information indicates a number of Msg3 repeated transmissions, and the Msg3 scheduling information is Msg2 scheduling Msg3 initial transmission or DCI scheduling Msg3 retransmission; the sending module is specifically configured to indicate whether to schedule Msg3 repeated transmissions and the number of Msg3 repeated transmissions through a specific field of the Msg2, wherein the specific field adopts a field in UL grant.

43. The Msg3 repetition number indication apparatus of claim 42, wherein, the specific field further adopts any one of the following: a field in MAC PDU subheader; a field in MAC subPDU.

44. The Msg3 repetition number indication apparatus of claim 43, characterized by, The sending module is specifically configured to indicate whether to schedule Msg3 repeated transmissions and the number of Msg3 repeated transmissions through a first field in UL grant, wherein the first field includes at least one of the following: a CSI request field; an MCS field; a TPC field; a TDRA field.

45. A terminal, characterized by comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, and the program or instructions are executed by the processor to implement the steps of the method according to any one of claims 1 to 21.

46. A network-side device, comprising: comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, and the program or instructions are executed by the processor to implement the steps of the method according to any one of claims 22 to 38.

47. A readable storage medium characterized by, The program or instructions are stored on a readable storage medium, and when executed by a processor, implement the method of any one of claims 1-21, or implement the steps of the method of any one of claims 22-38.

Images