CN115915264A

CN115915264A - Msg3 repetition frequency determining and indicating method and device

Info

Publication number: CN115915264A
Application number: CN202110898710.0A
Authority: CN
Inventors: 杨坤; 吴凯; 塔玛拉卡·拉盖施; 王理惠
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-08-05
Filing date: 2021-08-05
Publication date: 2023-04-04

Abstract

The application discloses a method, a device, a terminal and network side equipment for determining and indicating Msg3 repetition times, and belongs to the technical field of communication. The Msg3 repetition number determining method is executed by a terminal and comprises the following steps: after sending a first Msg1 to network side equipment, receiving Msg3 scheduling information of the network side equipment, and determining the Msg3 repeated transmission times according to the Msg3 scheduling information; the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission. The technical scheme of the embodiment of the application can flexibly indicate the configuration information of the Msg3 repeated transmission.

Description

Msg3 repetition frequency determining and indicating method and device

Technical Field

The application relates to the technical field of communication, in particular to a method and a device for determining and indicating Msg3 repetition times.

Background

In a New Radio (NR) system, coverage performance of a message 3 (Msg 3) is poor compared with coverage performance of other channels, so that a terminal in an area with poor signal coverage quality is difficult to access a cell. Therefore, a mechanism of Msg3 repeated sending is introduced to improve the coverage performance of Msg 3.

Disclosure of Invention

The embodiment of the application provides a method and a device for determining and indicating the number of Msg3 repetitions, which can efficiently schedule the Msg3 repeated transmission.

In a first aspect, an embodiment of the present application provides a method for determining a number of Msg3 repetitions, where the method is executed by a terminal, and includes:

after sending a first Msg1 to network side equipment, receiving Msg3 scheduling information of the network side equipment, and determining the Msg3 repeated transmission times according to the Msg3 scheduling information;

the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal request Msg3, and the Msg3 scheduling information is Msg2 for scheduling Msg3 initial transmission or DCI for scheduling Msg3 retransmission.

In a second aspect, an embodiment of the present application provides a method for indicating a number of Msg3 repetitions, where the method is performed by a network side device, and includes:

receiving a first Msg1 of a terminal, wherein the first Msg1 is an uplink signal which is requested by the terminal to have Msg3 repeatedly transmitted;

and sending Msg3 scheduling information to the terminal, indicating the Msg3 repeated transmission times through the Msg3 scheduling information, wherein the Msg3 scheduling information is the Msg2 for scheduling the initial transmission of the Msg3 or the DCI for scheduling the retransmission of the Msg 3.

In a third aspect, an embodiment of the present application provides an Msg3 repetition number determining device, which is applied to a terminal and includes:

the system comprises a receiving module and a scheduling module, wherein the receiving module is used for receiving Msg3 scheduling information of network side equipment after sending a first Msg1 to the network side equipment;

the determining module is used for determining the number of Msg3 repeated transmission according to the Msg3 scheduling information;

the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission.

In a fourth aspect, an embodiment of the present application provides an Msg3 repetition number indicating device, which is applied to a network side device, and includes:

the receiving module is used for receiving a first Msg1 of a terminal, wherein the first Msg1 is an uplink signal which is requested by the terminal to have Msg3 repeatedly transmitted;

and the sending module is used for sending Msg3 scheduling information to the terminal, indicating the Msg3 repeated transmission times through the Msg3 scheduling information, wherein the Msg3 scheduling information is the Msg2 for scheduling the Msg3 to initially transmit or the DCI for scheduling the Msg3 to retransmit.

In a fifth aspect, a terminal is provided, the terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.

A sixth aspect provides a terminal, including a processor and a communication interface, where 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 Msg3 retransmission times according to the Msg3 scheduling information; the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission.

In a seventh aspect, a network-side device is provided, which includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, and when executed by the processor, the program or the instruction implements the steps of the method according to the second aspect.

In an eighth aspect, a network side device is provided, which includes a processor and a communication interface, where the communication interface is configured to receive Msg3 scheduling information of the network side device after sending a first Msg1 to the network side device, and determine how many times Msg3 is repeatedly transmitted according to the Msg3 scheduling information; the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission.

In a ninth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, carries out the steps of the method of the first aspect or carries out the steps of the method of the second aspect.

In a tenth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement the method according to the first aspect, or to implement the method according to the second aspect.

In an eleventh aspect, there is provided a computer program/program product stored in a non-volatile storage medium, the program/program product being executable by at least one processor to implement the steps of the method according to the first or second aspect.

In the embodiment of the application, after the terminal sends the first Msg1, the network side equipment sends the Msg3 scheduling information to the terminal, so that the configuration information of the Msg3 repeated transmission can be flexibly indicated, and the Msg3 repeated transmission can be efficiently scheduled.

Drawings

FIG. 1 shows a schematic diagram of a wireless communication system;

fig. 2 is a schematic flowchart illustrating a method for determining the number of repetitions of Msg3 performed by a terminal according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a Msg3 repeat time indication method executed by a network side device according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an Msg3 repetition number determination device applied to a terminal according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an Msg3 repetition number indicating device applied to a network-side device according to an embodiment of the present application;

fig. 6 is a schematic diagram showing the components of the communication apparatus according to the embodiment of the present application;

fig. 7 is a schematic diagram illustrating a terminal according to an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a configuration of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in other sequences than those illustrated or otherwise described herein, and that the terms "first" and "second" used herein generally refer to a class and do not limit the number of objects, for example, a first object can be one or more. In addition, "and/or" in the specification and claims means at least one of connected objects, and a character "/" generally means that the former and latter related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may 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 the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications, such as 6th generation,6g communication systems.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: smart watches, bracelets, earphones, glasses, and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, wherein the Base Station may 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 WLAN access Point, a WiFi node, a Transmission Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but the specific type of the Base Station is not limited, and the core network device may be a location management device, such as a location management function (LMF, slemc), and the like.

NR supports two types of Random Access (RA) procedures: 4-step RA type (4-step RACH) and 2-step RA type (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 flow is generally applied to areas with better coverage, and the access time of the terminal is shortened. For areas with poor signal coverage, the terminal accesses the cell using a 4-step RACH procedure.

In 4-step RACH, the UE first sends Msg1 to the network, containing a random access preamble; after the UE transmits the Msg1, the UE monitors a Physical Downlink Control Channel (PDCCH) in an RAR time window (RA Response window), and receives a Random Access Response (RAR) scheduled by a DCI scrambled by an RA-Radio Network Temporary Identifier (RNTI) using a fallback (fallback) Downlink Control Information (DCI) format, i.e., DCI format 1_0. If the PRID in the RAR is the same as the preamble index sent by the UE, the RAR is considered to be successfully received, and at this time, the UE can stop monitoring the RAR and send Msg3 according to an indication of authorization (grant) carried in the RAR, wherein the indication is shown in table 1; msg3 is transmitted on the uplink shared channel, and uses hybrid automatic repeat request (HARQ), scrambles DCI with a Temporary Cell (TC) -RNTI indicated by the RAR, and schedules retransmission of Msg3 with a fallback (fallback) DCI format, i.e., DCI format 0 \. The Msg3 needs to include a unique flag for each UE. This flag will be used for conflict resolution in step four. After receiving the Msg3, the network schedules the PDCCH scrambled by the TC-RNTI to Msg4, and when the UE successfully decodes that the UE context Resolution MAC control element contained in the Msg4 is matched with the UE context Resolution capability sent by the Msg3, the UE considers that the random access is successful and sets the C-RNTI of the UE as the TC-RNTI, namely 4-step random access is completed.

The Msg2 message contains 27-bit UL grant for indicating configuration parameters of Msg3 transmission, wherein the PUSCH time resource allocation length is 4 bits, the time domain resources occupied by the Msg3 PUSCH in the time slot are indicated, and different time slot offsets K2 and different mapping mode PUSCH mapping types A/B can be supported; the MCS length is 4 bits, and the MCS length is used for indicating modulation and coding parameters of the Msg3 PUSCH, indicating the first 16 rows of the MCS and maximally indicating a 16QAM modulation 0.6 code rate; and the TPC length is 3bit, is used for indicating the adjustment quantity of the Msg3 PUSCH transmission power, and has an indication range of [ -6,8] dB.

In the related art, when the terminal is located at a cell edge or in a shadow fading region of a building, the base station may schedule the terminal to use the Msg3 repeat transmission mode to improve the Msg3 transmission success rate. In case of poor signal coverage (synchronization signal block signal quality below a predefined threshold), the terminal sends a dedicated Msg1 requesting Msg3 to repeat the transmission to the base station. And the base station schedules the Msg3 according to the channel condition of the terminal and indicates the number of the Msg3 repetitions. Meanwhile, the forward compatibility requirement of the system is guaranteed, and the total length of the UL grant which is scheduled to be transmitted repeatedly by the Msg3 is kept unchanged.

The related art has a limited length of the UL grant and each field has defined a corresponding parameter, and the MAC subprotocol data sheet (subPDU) of Msg2 has a fixed length, so that the UL grant length cannot be directly increased to explicitly indicate the Msg3 repetition number.

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) in the TPC field for increasing the transmit power may not be used, because in the scenario of coverage enhancement, the terminal transmit power is already close to the full power, and therefore the margin of the Msg3 transmit power is not increased. The configuration of high code rate indicated in MCS field (MCS index >10 configuration, using 16QAM modulation) is unlikely to be applied to the Msg3 coverage enhancement scenario, because the transmission mode of high-order MCS is not suitable for the transmission scenario with high requirement on robustness. The table corresponding to the Time Domain Resource Allocation (TDRA) contains the PUSCH mapping type b, which is unlikely to be configured in the Msg3 repeated transmission, because the PUSCH mapping type b cannot efficiently utilize the available ODFM symbols of the slot when the Msg3 repeated transmission occurs, which results in fragmentation of time domain resources. Therefore, redundant contents of the UL grant, or parameter values that are not likely to be configured in the Msg3 coverage enhancement scene, can be redefined to indicate the Msg3 repetition number.

An embodiment of the present application provides a method for determining a number of Msg3 repetitions, which is performed by a terminal, and as shown in fig. 2, the method includes:

step 101: after sending a first Msg1 to network side equipment, receiving Msg3 scheduling information of the network side equipment, and determining the number of Msg3 repeated transmission times according to the Msg3 scheduling information;

step 102: the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission.

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

in an initial transmission (initial transmission) stage of the Msg3 repeat transmission, the terminal device monitors Msg2 in a RAR window, detects a specific field of Msg2, and determines whether to schedule the Msg3 repeat transmission and the number of Msg3 repeat transmissions according to the specific field, where the specific field adopts any one of:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

fields in the UL grant.

Therefore, configuration information of Msg3 repeated transmission can be flexibly indicated through a specific field of the Msg2, the Msg3 repeated transmission is efficiently scheduled, the length of the Msg2 is guaranteed to be unchanged, and compatibility with the Msg2 defined by a related protocol such as Rel-15/16 is kept.

In some embodiments, whether to schedule the Msg3 for repeated transmission is determined by a 1-bit field in the MAC sub PDU or MAC PDU sub header; and/or

And determining a scaling coefficient N of the Msg3 repeated transmission times through a 2bit field in the MAC sub PDU and the MAC PDU sub header.

Therefore, the configuration information of the Msg3 repeated transmission can be flexibly indicated through the fields in the MAC sub PDU and/or the MAC PDU sub header, and the Msg3 repeated transmission is efficiently scheduled.

In some embodiments, the transmission is performed using N times the determined number of the Msg3 repeat transmissions.

In some embodiments, the 2bit field consists of a 1bit field in the MAC PDU subheader and a 1bit field in the MAC subPDU.

In some embodiments, the determining the number of the Msg3 repeated transmissions according to the Msg3 scheduling information specifically includes:

judging whether Msg3 repeated transmission is scheduled or not and the number of Msg3 repeated transmission times according to a first field in the UL grant, wherein the first field comprises at least one of the following items:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

Therefore, the configuration information of the Msg3 repeated transmission can be flexibly indicated through the first field in the UL grant, and the Msg3 repeated transmission can be efficiently scheduled.

In some embodiments, a value of one part of the TPC field indicates that the Msg3 repeat transmission is scheduled, and a value of the other part indicates that the Msg3 repeat transmission is not scheduled; or

One part of the MCS field is taken as a value to schedule the Msg3 repeated transmission, and the other part is taken as a value to not schedule the Msg3 repeated transmission.

In some embodiments, different value ranges of the MCS field correspond to different Msg3 repetition times.

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

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

In some embodiments, determining the TDRA table further comprises:

after a first Msg1 is sent to network side equipment, if a specific field in the Msg2 indicates that Msg3 is scheduled for repeated transmission, a special TDRA table is used for reading a TDRA field in a UL grant;

each entry in the dedicated TDRA table indicates a time domain resource configuration and a number of Msg3 repetitions within a time slot.

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

In some embodiments, further comprising:

and determining the length of the TDRA field or the field division of the UL grant according to whether the network side equipment schedules Msg3 repeated transmission.

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

The MCS field and the TDRA field jointly indicate TDRA and MCS.

In some embodiments, determining the length of the TDRA field or the field partition of the UL grant includes any one of:

determining that the TDRA field is larger than a first preset value, and the total number of entries of the special TDRA table is larger 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.

The first preset value, the second preset value and the third preset value may be defined by system message configuration or a protocol.

In some embodiments, the content of the TDRA entry is configured for the network side device through a system message.

In some embodiments, further comprising:

and determining an available time slot of the Msg3 PUSCH repeated transmission according to the MCS field or the TPC field. Therefore, the available time slot of the Msg3 PUSCH repeated transmission can be configured through the MCS field or the TPC field, and the Msg3 PUSCH repeated transmission is efficiently scheduled.

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 of a first transmission of the Msg3 retransmission;

the time slot configuration information is predefined by a protocol or configured by a system message of network side equipment, and Msg3 is indicated to repeatedly transmit uplink and downlink time slot configuration;

the number of the continuous available time slots of the first transmission of the Msg3 repeated transmission is predefined by a protocol or configured by a system message of a network side device, and the first available time slot of the Msg3 repeated transmission determined by the UL grant is indicated to start M continuous time slots as available time slots, wherein M is a positive integer.

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

determining a carrier for an upstream initial BWP (bandwidth part), comprising:

and if the uplink carrier has a plurality of carriers available, determining the carrier of the uplink initial BWP through the system message of the network side equipment.

In some embodiments, if the network side device supports the SUL capability and supports the NUL to support the Msg3 retransmission, a first decision threshold is determined and an uplink carrier is selected by using the first decision threshold, where the first decision threshold is obtained by explicit configuration of a system message or implicit calculation according to the number of Msg3 repetitions.

In some embodiments, determining the number of Msg3 retransmissions from the Msg3 scheduling information comprises:

judging whether Msg3 repeated transmission is scheduled or not and the number of Msg3 repeated transmission times according to a second field in the DCI, wherein the second field comprises at least one of the following items:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

In some embodiments, determining whether to schedule the Msg3 repeat transmission and the number of Msg3 repeat transmissions according to the second field in the DCI includes any of:

determining the number of Msg3 repeated transmission times or determining the adjustment quantity of the Msg3 repeated times according to the content in the TPC field, wherein the number of Msg3 retransmission times is equal to the number of Msg3 initial transmission times plus the adjustment quantity of the Msg3 repeated times;

determining the Msg3 repeated transmission times or determining the adjustment quantity of the Msg3 repeated times according to the content in the MCS field;

determining a special TDRA table corresponding to a New data indicator field, and determining the Msg3 repeated transmission times according to the special TDRA table;

determining the Msg3 repetition times in the corresponding special TDRA table directly according to the TDRA field;

and determining the Msg3 repetition times according to the HARQ process number field.

An embodiment of the present invention further provides a method for indicating a number of Msg3 repetitions, where the method is executed by a network side device, and as shown in fig. 3, the method includes:

step 201: receiving a first Msg1 of a terminal, wherein the first Msg1 is an uplink signal which is requested by the terminal to have Msg3 repeatedly transmitted;

step 202: and sending Msg3 scheduling information to the terminal, indicating the Msg3 repeated transmission times through the Msg3 scheduling information, wherein the Msg3 scheduling information is the Msg2 for scheduling the initial transmission of the Msg3 or the DCI for scheduling the retransmission of the Msg 3.

In some embodiments, whether to schedule the Msg3 repeat transmission and the number of Msg3 repeat transmissions is indicated by a specific field of the Msg2, the specific field employing any of:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

a field in a UL grant.

In some embodiments, whether the Msg3 is scheduled for repeated transmission is indicated by a 1bit field in the MAC sub PDU or MAC PDU subheader; and/or

And indicating a scaling coefficient N of the Msg3 repeated transmission times through a 2bit field in the MAC sub PDU and the MAC PDU subheader.

In some embodiments, whether Msg3 retransmission is scheduled and the number of Msg3 retransmissions is indicated by a first field in the UL grant, the first field comprising at least one of:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

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

The MCS field and the TDRA field jointly indicate TDRA and MCS.

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

In some embodiments, further comprising:

and indicating the available time slot of the Msg3 PUSCH repeated transmission to the terminal through the MCS field or the TPC field.

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

the number of the continuous available time slots of the first transmission of the Msg3 repeated transmission is predefined by a protocol or configured by a system message of a network side device, and the first available time slot of the Msg3 repeated transmission determined by the UL grant is indicated to start M continuous time slots as available time slots, wherein M is an integer greater than or equal to zero.

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

and if the uplink carrier has a plurality of carriers available, indicating the carrier supporting the Msg3 repeated transmission to the terminal through a system message.

In some embodiments, the method specifically comprises:

indicating, by a second field in the DCI, whether to schedule Msg3 repeat transmissions and a number of Msg3 repeat transmissions, the second field comprising at least one of:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

In some embodiments, indicating, by a second field in the DCI, whether to schedule the Msg3 repeat transmission and the number of Msg3 repeat transmissions comprises any of:

through the content in the TPC field indicating the Msg3 repeat transmission times or indicating the adjustment quantity of the Msg3 repeat times, it can be understood that the Msg3 repeat times are equal to the Msg3 initial transmission repeat times plus the adjustment quantity of the Msg3 repeat times;

indicating the Msg3 repeated transmission times or indicating the adjustment amount of the Msg3 repeated times through the content in the MCS field;

indicating the Msg3 repeated transmission times through a special TDRA table corresponding to a New data indicator field;

directly indicating an entry of the special TDRA table through a TDRA field, and further indicating the Msg3 repetition times;

the number of the Msg3 repetitions is indicated according to the HARQ process number field.

The invention will be further described with reference to specific examples:

the first embodiment of the invention:

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 interpretation method of Msg3 retransmission to determine the number of Msg3 retransmission and other scheduling information of Msg3 transmission.

1. The Msg3 repeat sending terminal determines the interpretation mode of the UL grant field, or determines whether the base station schedules the Msg3 repeat sending.

The Msg3 repeat sending terminal monitors the Msg2 in the RAR window after sending the Msg3 repeat request (namely the first Msg 1), and whether the base station schedules the Msg3 repeat transmission is determined according to information carried in the Msg 2.

And (I) the determination mode of the Msg3 repeated transmission is a 1bit field in a MAC subheader or a subPDU. For example, the 1-bit field may be a 1-bit reserved field included in a MAC header of the RAR in the relevant protocol. When the 1bit field is 0, the Msg3 repeated transmission is not scheduled, namely the Msg3 single transmission is scheduled; and for the Msg3 repeated sending terminal, when the 1bit field is 1, the Msg3 repeated transmission is scheduled. For another example, the 1bit field is a 1bit reserved field included in a MAC sub pdu payload (payload) in the relevant protocol. The 1bit field is 0, which indicates that the Msg3 repeated transmission is not scheduled, namely the Msg3 single transmission is scheduled; for the Msg3 repeated sending terminal, when the 1bit field is 1, the Msg3 repeated transmission is scheduled.

Still further alternatively, a scaling factor N that indicates the number of Msg3 retransmissions or the number of Msg3 retransmissions is used using a 2bit field in the MAC subheader and the subPDU. The 2-bit field consists of a 1-bit reserved field contained in a MAC subheader of the RAR in the relevant protocol and a 1-bit reserved field contained in a MAC subPDU load (payload) in the relevant protocol. When the 2bit field is 00, the Msg3 repeated transmission is not scheduled; 01 10, 11 represent the scaling factor N for three different retransmission times or Msg3 retransmission times, respectively, determined by the protocol pre-definition or system message configuration.

And secondly, the judging method of the Msg3 repeated transmission is a field in the RAR UL grant. For example, a CSI request field of 0 indicates that the Msg3 retransmission is not scheduled, and a CSI request field of 1 indicates that the Msg3 retransmission is scheduled. Or, the CSI request field indicates the selection of the TDRA table, that is, when the CSI request field is 0, the TDRA table 1 is used to interpret the TDRA field; the TDRA field is read using TDRA table 2 for 1. The TDRA table 1 and table 2 are predefined by a protocol or configured by a system message. Alternatively, the CSI request field is used for a scaling factor indicating the number of repetitions. That is, when the CSI request field is 0, it indicates that the scaling factor is 1, and the number of repetitions indicated by the TDRA field is used for transmission; a value of 1 indicates that the scaling slot is N (e.g., 2), and the transmission is performed using N times the number of repetitions indicated by the TDRA field. It is understood that the configuration results of TDRA table 1 and TDRA table 2 are different from each other, and there is at least one table explicitly indicating the Msg3 repetition number, optionally one of the tables is a TDRA table for scheduling Msg3 single transmission defined in the prior art.

Another indication method is that the Msg3 retransmission is judged by determining whether to schedule the Msg3 retransmission or determining the number of Msg3 retransmissions according to the re-interpretation of the 3bit tpc field. One part of the TPC field is valued to indicate that the Msg3 repeat transmission is scheduled, and the other part of the TPC field is valued to indicate that the Msg3 repeat transmission is not scheduled. One possible way of defining this is shown in table 1. When the TPC field is 000, 001, 010, 011, it indicates that the Msg3 transmission number is 1, that is, the Msg3 is not scheduled for repeated transmission, and each value corresponds to a transmission power offset; and the value of the other TPC field indicates that the base station schedules Msg3 to repeatedly transmit.

Another indication is that the TPC and TDRA fields jointly indicate the TDRA and the power control parameters. When the value of the TPC field is 000 to 011, the repetition times are determined according to the special TDRA table, and the power control parameters corresponding to the TPC value of 000 to 011 are predefined by a protocol; the TPC field is set to 100 to 111, and the number of repetitions determined according to the TDRA table is enlarged by N times, where N is a predefined value of the protocol (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 parameter corresponding to the TPC value 000 to 011 is predefined by the protocol.

Another way to indicate this is to redefine the 4-bit MCS field to indicate whether to schedule the Msg3 retransmission or to determine the number of Msg3 retransmissions. Specifically, a value of one part of the MCS field indicates that the Msg3 is repeatedly transmitted, and a value of the other part indicates that the Msg3 is not scheduled to be repeatedly transmitted. One possible definition is that the MCS field takes a value ranging from 0000 to 0111 to indicate that the Msg3 retransmission is not scheduled, and 1000 to 1111 to indicate that the Msg3 retransmission is scheduled.

Another indication is that the MCS and TDRA fields jointly indicate TDRA and MCS. The MCS field takes values of 0000 to 0111, the repetition times determined by using a special TDRA table is used, and the MCS table corresponding to the MCS field takes values of 0000 to 0111 is predefined by a protocol; and when the MCS field takes a value of 1000 to 1111, the number of repetitions determined according to the TDRA table is increased by N times, N is a predefined value of the protocol (for example, N = 2), and the MCS table corresponding to the MCS taking a value of 0000 to 0111 is predefined by the protocol. It is understood that the dedicated TDRA table is used to indicate the time domain resources for the Msg3 repeat transmission and the number of Msg3 repeats.

(III) Msg3 repeated sending terminal determining TDRA table

If the base station does not schedule the Msg3 repeat transmission, the terminal uses the TDRA table defined in the prior art that schedules the Msg3 single transmission. If the base station schedules the Msg3 for repeated transmission, the terminal uses a dedicated TDRA table indicating time domain resource configuration and repetition times as shown in table 2.

The dedicated TDRA table may be protocol predefined, or configured via system messages, or a combination thereof. E.g., msg3 repeatedly sends a UL grant with a TDRA field length of 4 bits, then the TDRA field corresponds to a 16-row dedicated TDRA table. In the dedicated TDRA table, the contents of the first X rows are determined by protocol predefinition, and the contents of the next 16-X rows are configured by system messages, such as the table 1 example. The indication mode of the system message can follow the parameter configuration mode of PUSCH repetition type A defined in the prior art NR Rel-15/16 protocol; or define a special indication mode, for example, default to PUSCH mapping type a, indicating K2, PUSCH length, msg3 repetition number.

Further, when the system message is used to indicate the entry of the dedicated TDRA table, the value range of the TDRA parameter may be different from the value range of the TDRA entry configuration parameter in the connected state. For example, for the parameter k2, the range of values in the connection state is 0-32 and occupies 5 bits, and the range of values in the system message is 0-3 and occupies 2 bits; the value ranges of the initial symbol position and the length startsymbol and length in the time slot are 0-127, the value ranges of 0-15 occupy 4 bits in the system message, wherein the initial symbol position and the length in the time slot corresponding to the value ranges of 0-15 are predefined by a protocol. As another example, the system message configuration may be a combination of the number of repetitions and entries in the TDRA table for a Msg3 single transmission in the prior art NR Rel-15/16 protocol. For example, if the number of repetitions contains 4 candidate values occupying 2bits, the TDRA table for a single transmission of Msg3 has 16 entries occupying 4 bits, then the system message overhead for the TDRA entry indicating a repeated transmission of Msg3 is 6 bits.

Further optionally, the length of the TDRA field or the field partition of the UL grant is determined according to whether the base station schedules the Msg3 repeated transmission. For example, if the base station schedules Msg3 for repeat transmission, the TDRA field is 5bit, the MCS field is 3bit, where the 3bit MCS field is used to indicate the first 8 MCS configurations in the MCS table; or the TDRA field is 5bit, the TPC field is 2bit, wherein the 2bit TPC field redefines the power control value. The other fields are unchanged in length and meaning.

2. Terminal parsing UL grant to determine number of repeated transmissions

And the terminal determines the Msg3 time domain resource parameter and the repetition times according to the TDRA field of the UL grant and determines according to the determined contents of the items of the TDRA table.

Optionally, the available timeslot for Msg3 PUSCH retransmission is determined according to the MCS field or the TPC field in the UL grant, that is, the configuration parameter of the available timeslot for Msg3 PUSCH retransmission is determined according to different values or value ranges of the MCS field or the TPC field, where the configuration parameter includes at least one of the following information:

and (I) configuring temporary uplink and downlink time slots. Different uplink and downlink time slot configurations corresponding to the values of the TPC field part are defined through protocol predefinition or system message configuration. The uplink and downlink time slot configuration information is protocol predefining or system message configuration. And the temporary uplink and downlink time slot configuration and the cell-level uplink and downlink time slot configuration broadcasted by the system message determine an uplink time slot and an uplink symbol in the time slot so as to determine an available time slot of the Msg3 repeated transmission, namely the uplink time slot and the time slot which contains the uplink symbol and has the uplink symbol time range larger than the Msg3 time are determined as the available time slot.

(ii) the number of available time slots for continuous transmission. For example, the field of TPC is interpreted as bitmap information when values 100 to 111 are taken, which indicates whether the beginning of the Msg3 slot of the first transmission is 3 consecutive slots available, where 1 indicates an available slot and 0 indicates an unavailable slot. Or the corresponding relation between the partial value of the TPC field and the number of available time slots for continuous transmission is defined through protocol predefinition or system message configuration.

And (III) defining the beginning of the Msg3 time slot of the first transmission to be available M time slots continuously through protocol predefining or system message configuration. When the available time slot determined in the above manner conflicts with the downlink time slot configured by the system message, the conflict time slot determines the time slot transmission direction according to the system message. The M value is contained in the TPC field or MCS field. Or the value of M is a fixed value and is defined by a system message or a protocol.

The slot configuration or available slot configured by the MCS field or TPC field is valid only when Msg3 repeats transmission.

TABLE 1

Optionally, before sending the PRACH, a carrier supporting the Msg3 repeat transmission is determined.

When multiple carriers are available for the uplink carrier, NUL and SUL, the carrier that can support the Msg3 retransmission is indicated by the system message.

Further, the carriers supporting the Msg3 repeated transmission are respectively configured with the repeated transmission times or a dedicated TDRA table through a system message, or a criterion for instructing the terminal to select the SSB. The terminal selects one SSB from the SSBs with channel quality higher than the first threshold as the SSB associated with the subsequent random access procedure, or selects one SSB from Y SSBs with the best channel quality result of all the SSBs as the SSB associated with the subsequent random access procedure, where Y is a positive integer and is predefined by a protocol or configured by a system message.

The terminal selects and determines an uplink carrier. And the Msg3 repeated transmission terminal determines the decision threshold of the SUL according to the rsrp-threshold SSB-SUL defined by the related protocol and the Msg3 repeated transmission configuration condition of the uplink carrier. For a terminal that supports SUL and supports Msg3 repetition, if the base station indicates NUL supports Msg3 repetition transmission, then:

the terminal determines a special SUL decision threshold and selects an uplink carrier by using the special threshold (namely, the selection is carried out according to RSRP, the RSRP is higher than the threshold and selects NUL, and the selection is carried out below the threshold and selects SUL). The special threshold can be directly configured by the system message, or calculated according to rsrp-threshold ssb-SUL defined by the relevant protocol, i.e. rsrp-threshold ssb-SUL + deta, where deta indicates that the offset is determined by the system message configuration or according to the number of repetitions of Msg 3.

Table 2Msg3 dedicated TDRA table example for repeat transmission

The second embodiment of the invention:

in this embodiment, the Msg3 repeat sending terminal reads the TPC field in the UL grant, and determines the number of repetitions of Msg3 according to the content of the TPC field. Wherein the interpretation of the TPC field may be defined as shown in table 3. Or the value of the TPC field 000-011 multiplexes the value of the TPC field 2bit in the DCI 1-0; values from 100 to 111 are used to indicate the number of repetitions of Msg 3. The interpretation of the other fields of the UL grant remains unchanged.

TABLE 3

The third embodiment of the invention:

in this embodiment, the Msg3 repeat sending terminal reads the MCS field in the UL grant, and determines the number of Msg3 repeats according to the MCS field. The MCS field is 4bit, different value ranges are defined to correspond to different Msg3 repetition times, for example, 0000 to 0100 indicate that the repetition time is 1, 0101 to 1000 indicate that the repetition time is 2, 1001 to 1100 indicate that the repetition time is 4, and 1101 to 1111 indicate that the repetition time is 8; and respectively correspond to the first N MCS configurations in the MCS table.

The fourth embodiment of the invention:

in this embodiment, the Msg3 repeat sending terminal reads the TDRA field in the UL grant, and determines the Msg3 repeat number according to the MCS field. The MCS field is 4 bits, and the corresponding entry in the dedicated TDRA table shown in table 4 is read to determine the number of times of repeated transmission. The dedicated TDRA table may be protocol predefined or configured via system messages or a combination of both. Each configuration entry in the dedicated TDRA table indicates a number of repetitions.

Another possibility is that the terminal reads the 5-bit length MCS field and the 3-bit length MCS field. And determining the repetition times according to a special TDRA table corresponding to the 5-bit length MCS field.

TABLE 4

/>

The fifth embodiment of the invention:

in this embodiment, the Msg3 retransmission is scheduled by DCI0-0 scrambled with TC-RNTI. The MCS, TPC field in the DCI0-0 field determines the number of Msg3 repetitions according to the scheme in the above embodiment.

A New data indicator in the DCI0-0 scrambled with TC-RNTI, a HARQ process number field is defined in retransmission scheduling of the Msg3 repeat transmission as an indicator indicating the number of Msg3 repeat transmissions or whether to schedule the Msg3 repeat.

It should be noted that, in the Msg3 repetition number determining method provided in the embodiment of the present application, the executing body may be the Msg3 repetition number determining device, or a module in the Msg3 repetition number determining device for executing the loading Msg3 repetition number determining method. In the embodiment of the present application, a method for determining the number of repetitions of loading Msg3, which is performed by the Msg3 repetition number determining device, is taken as an example, and the Msg3 repetition number determining method provided in the embodiment of the present application is described.

The embodiment of the present application provides a Msg3 repetition number determining device, which is applied to a terminal 300, and as shown in fig. 4, the device includes:

the 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;

the determining module 320 is configured to determine the number of Msg3 repeated transmissions according to the Msg3 scheduling information;

In some embodiments, the determining module 320 is specifically configured to monitor Msg2 in a RAR window, detect a specific field of Msg2, and determine whether to schedule Msg3 retransmission and the number of Msg3 retransmission according to the specific field, where the specific field adopts any one of:

a field in a MAC PDU subheader;

a field in a MAC sub PDU;

a field in a UL grant.

In some embodiments, the determining module 320 is specifically configured to determine whether to schedule the Msg3 for repeated transmission through a MAC sub PDU or a 1bit field in a MAC PDU subheader; and/or

In some embodiments, the determining module 320 is specifically configured to transmit using N times the determined number of the Msg3 repeated transmissions.

In some embodiments, the 2-bit field consists of a 1-bit field in the MAC PDU subheader and a 1-bit field in the MAC subPDU.

In some embodiments, the determining module 320 is specifically configured to determine whether to schedule the Msg3 retransmission and the number of Msg3 retransmissions according to a first field in the UL grant, where the first field includes at least one of:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

And one part of the MCS field is valued to schedule Msg3 repeated transmission, and the other part of the MCS field is valued to not schedule Msg3 repeated transmission.

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

In some embodiments, the determining module 320 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 that Msg3 is scheduled for repeated transmission, use the dedicated TDRA table to interpret a 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.

In some embodiments, the determining module 320 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 repeated transmission.

The MCS field and the TDRA field jointly indicate TDRA and MCS.

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

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

In some embodiments, the determining module 320 is further configured to determine an available slot for a Msg3 PUSCH retransmission according to the MCS field or the TPC field.

In some embodiments, the determining module 320 is further configured to determine a carrier of an upstream initial BWP, including:

In some embodiments, the determining module 320 is further configured to determine a first decision threshold and select an uplink carrier by using the first decision threshold if the network-side device supports the SUL capability and supports the NUL to support the Msg3 retransmission, where the first decision threshold is obtained by explicit configuration of a system message or implicit calculation according to the number of Msg3 repetitions.

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

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

In some embodiments, the determining module 320 is further configured to perform any of:

determining the Msg3 repeated transmission times or determining the adjustment quantity of the Msg3 repeated times according to the content in the TPC field;

determining a corresponding special TDRA table according to the New data indicator field, and determining the Msg3 repeated transmission times according to the special TDRA table;

determining the Msg3 repetition times in the corresponding special TDRA table according to the TDRA field;

The Msg3 repetition number determination device in the embodiment of the present application may be a device, a device or an electronic device having an operating system, or may be a component, an integrated circuit, or a chip in a terminal. The device or the electronic equipment can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The Msg3 repetition number determining device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 2, and achieve the same technical effect, and is not described here again to avoid repetition.

The embodiment of the present application provides an Msg3 repetition number indicating device, which is applied to a network side device 400, and as shown in fig. 5, the device includes:

a receiving module 410, configured to receive a first Msg1 of a terminal, where the first Msg1 is an uplink signal that the terminal requests the Msg3 to repeatedly transmit;

the sending module 420 is configured to send Msg3 scheduling information to the terminal, indicate the number of Msg3 repeated transmission times through the Msg3 scheduling information, and the Msg3 scheduling information is Msg2 for scheduling Msg3 initial transmission or DCI for scheduling Msg3 retransmission.

In some embodiments, the sending module 420 is specifically configured to indicate whether to schedule the Msg3 retransmission and the number of Msg3 retransmission times through a specific field of the Msg2, where the specific field employs any one of the following:

a field in a MAC PDU subheader;

a field in a MAC sub PDU;

fields in the UL grant.

In some embodiments, the sending module 420 is specifically configured to indicate whether to schedule the Msg3 retransmission through a MAC sub PDU or a 1bit field in a MAC PDU subheader; and/or

In some embodiments, the sending module 420 is specifically configured to indicate whether Msg3 retransmission is scheduled and the number of Msg3 retransmission times through a first field in the UL grant, where the first field includes at least one of the following:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

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

The MCS field and the TDRA field jointly indicate TDRA and MCS.

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

In some embodiments, the sending module 420 is specifically configured to indicate available slots for Msg3 PUSCH retransmission to the terminal through the MCS field or the TPC field.

the number of the continuous available time slots of the first transmission of the Msg3 repeated transmission is predefined by a protocol or configured by a system message of a network side device, and the first available time slot of the Msg3 repeated transmission determined by the UL grant is indicated to start continuous M time slots as available time slots, wherein M is a positive integer.

In some embodiments, the sending module 420 is further configured to indicate, by a system message, a carrier supporting the Msg3 retransmission to the terminal if multiple carriers are available for the uplink carrier.

In some embodiments, the sending module 420 is further configured to indicate whether to schedule the Msg3 retransmission and the number of Msg3 retransmissions through a second field in the DCI, the second field comprising at least one of:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

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

indicating the Msg3 repeated transmission times or indicating the adjustment quantity of the Msg3 repeated times through the content in the TPC field;

indicating the Msg3 repetition times in the corresponding special TDRA table through a TDRA field;

and indicating the Msg3 repetition number according to the HARQ process number field.

The Msg3 repetition number indicating device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 6, an embodiment of the present application further provides a communication device 500, which includes a processor 501, a memory 502, and a program or an 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 the instruction is executed by the processor 501 to implement the above-mentioned processes of the embodiment of the Msg3 repetition number determination method applied to the terminal, and can achieve the same technical effect. When the communication device 500 is a network-side device, the program or the instruction is executed by the processor 501 to implement the processes of the Msg3 repetition number indication method embodiment applied to the network-side device, and can achieve the same technical effect, and the details are not repeated here to avoid repetition.

The embodiment of the application further provides a terminal, which comprises a processor and a communication interface, wherein the processor is used for receiving the Msg3 scheduling information of the network side equipment after sending the first Msg1 to the network side equipment, and determining the number of times of Msg3 repeated transmission according to the Msg3 scheduling information; the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission. The terminal embodiment corresponds to the terminal-side method embodiment, and all implementation processes and implementation manners of the method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, fig. 7 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.

The terminal 1000 includes, but is not limited to: 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, and the like.

Those skilled in the art will appreciate that terminal 1000 can also include a power supply (e.g., a battery) for powering the various components, which can be logically coupled to processor 1010 via a power management system to provide management of charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and will not be described again here.

It should be understood that in the embodiment of the present application, the input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In this embodiment of the application, the radio frequency unit 1001 receives downlink data from a network side device and then processes the downlink data to the processor 1010; in addition, the uplink data is sent to the network side equipment. In general, 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, and the like.

The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the Memory 1009 may include a high-speed random access Memory, and may further include a nonvolatile Memory, which may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (erasab PROM, EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 1010 may include one or more processing units; alternatively, processor 1010 may integrate an application processor that handles primarily the operating system, user interface, and application programs or instructions, and a modem processor that handles primarily wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The processor 1010 is configured to receive Msg3 scheduling information of a network-side device after sending a first Msg1 to the network-side device; determining the number of Msg3 repeated transmission according to the Msg3 scheduling information; the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal requesting Msg3, and the Msg3 scheduling information is a DCI which schedules Msg2 for initial transmission of Msg3 or schedules Msg3 for retransmission.

In some embodiments, the processor 1010 is specifically configured to listen to Msg2 in a RAR window, detect a specific field of Msg2, and determine whether to schedule Msg3 retransmission and the number of Msg3 retransmission according to the specific field, where the specific field adopts any one of:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

fields in the UL grant.

In some embodiments, the processor 1010 is specifically configured to determine whether to schedule the Msg3 retransmission by using a 1bit field in the MAC sub PDU or the MAC PDU subheader; and/or

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

In some embodiments, the processor 1010 is specifically configured to determine whether to schedule the Msg3 retransmission and the number of Msg3 retransmission according to a first field in the UL grant, where the first field includes at least one of:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

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 that Msg3 is scheduled for repeated transmission, use the dedicated TDRA table to interpret a TDRA field in the UL grant;

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 repeated transmission.

The MCS field and the TDRA field jointly indicate TDRA and MCS.

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

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

In some embodiments, the processor 1010 is further configured to determine an available slot for a Msg3 PUSCH retransmission based on the MCS field or the TPC field.

In some embodiments, the processor 1010 is further configured to determine a carrier of an upstream initial BWP, including:

In some embodiments, the processor 1010 is further configured to determine a first decision threshold and select an uplink carrier by using the first decision threshold if the network-side device supports the SUL capability and supports the NUL to support the Msg3 retransmission, where the first decision threshold is obtained by explicit configuration of a system message or implicit calculation according to the number of the Msg3 repetitions.

In some embodiments, the processor 1010 is further configured to determine whether to schedule the Msg3 retransmission and the number of Msg3 retransmissions according to a second field in the DCI, where the second field includes at least one of:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

In some embodiments, the processor 1010 is further configured to perform any of:

determining the Msg3 repeated transmission times or the adjustment quantity of the Msg3 repeated times according to the content in the MCS field;

The embodiment of the application further provides a network side device, which comprises a processor and a communication interface, wherein the communication interface is used for receiving a first Msg1 of a terminal, and the first Msg1 is an uplink signal which is requested by the terminal to have Msg3 repeatedly transmitted; and sending Msg3 scheduling information to the terminal, indicating the Msg3 repeated transmission times through the Msg3 scheduling information, wherein the Msg3 scheduling information is the Msg2 for scheduling the initial transmission of the Msg3 or the DCI for scheduling the retransmission of the Msg 3. The embodiment of the network side device corresponds to the embodiment of the method of the network side device, and all implementation processes and implementation modes of the embodiment of the method can be applied to the embodiment of the network side device and can achieve the same technical effect.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 8, the network device 700 includes: an antenna 71, a radio frequency device 72, a baseband device 73. The antenna 71 is connected to a radio frequency device 72. In the uplink direction, the rf device 72 receives information via the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes information to be transmitted and transmits the information to the rf device 72, and the rf device 72 processes the received information and transmits the processed information through the antenna 71.

The above-mentioned band processing means may be located in the baseband device 73, and the method performed by the network side device in the above embodiment may be implemented in the baseband device 73, where the baseband device 73 includes a processor 74 and a memory 75.

The baseband device 73 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 8, where one of the chips, for example, the processor 74, is connected to the memory 75 to call up a program in the memory 75 to execute the network device operation shown in the above method embodiment.

The baseband device 73 may further include a network interface 76, such as a Common Public Radio Interface (CPRI), for exchanging information with the radio frequency device 72.

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 75 and capable of being executed on the processor 74, and the processor 74 calls the instructions or programs in the memory 75 to execute the method executed by each module shown in fig. 5, and achieve the same technical effect, and are not described herein in detail to avoid repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the Msg3 repetition number determining method or the indication method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, to implement each process of the Msg3 repetition number determining method or the indication method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for determining the number of repetitions of Msg3, performed by a terminal, comprising:

the first Msg1 is an uplink signal which is transmitted repeatedly by the terminal request Msg3, and the Msg3 scheduling information is Msg2 for scheduling Msg3 initial transmission or downlink control information DCI for scheduling Msg3 retransmission.

2. The method of claim 1, wherein the determining the number of Msg3 retransmissions according to the Msg3 scheduling information comprises:

monitoring Msg2 in a Random Access Response (RAR) window, detecting a specific field of the Msg2, and judging whether to schedule Msg3 repeated transmission and the number of the Msg3 repeated transmission according to the specific field, wherein any one of the following fields is adopted in the specific field:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

a field in a UL grant.

3. The method of claim 2,

determining whether to schedule Msg3 for repeated transmission through a 1bit field in the MAC sub PDU or the MAC PDU sub header; and/or

And determining a scaling factor N of the Msg3 repeated transmission times through a 2bit field in the MAC sub PDU and the MAC PDU sub header.

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

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

6. The method of claim 2, wherein the determining the number of the Msg3 retransmission according to the Msg3 scheduling information specifically comprises:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

7. The method of claim 6,

one part of the TPC field is valued to represent that Msg3 repeated transmission is scheduled, and the other part of the TPC field is valued to represent that Msg3 repeated transmission is not scheduled; or

8. The method of claim 6,

and different value ranges of the MCS field correspond to different Msg3 repetition times.

9. The method of claim 6, wherein the CSI request field, or MAC sub PDU, or 1bit field in MAC PDU subheader, or 2bit field in MAC sub PDU and MAC PDU subheader indicates any of the following:

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

10. The method of claim 6 or 8, further comprising determining a TDRA table, comprising:

after the first Msg1 is sent to the network side device, if a specific field in the Msg2 indicates that the Msg3 is scheduled for repeated transmission, a special TDRA table is used for reading a TDRA field in a UL grant;

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

12. The method of claim 10, further comprising:

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

The MCS field and the TDRA field jointly indicate TDRA and MCS.

14. The method of claim 12, wherein determining the length of the TDRA field or the field partition of the UL grant comprises any one of:

the length of the TPC field or the MCS field is less than the third preset value.

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

16. The method of claim 6, further comprising:

and determining an available time slot of the Msg3 PUSCH repeated transmission according to the MCS field or the TPC field.

17. The method of claim 16,

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 continuous available time slots of the first transmission of the Msg3 repeated transmission;

18. The method of claim 1, wherein prior to sending the first Msg1, the method further comprises:

determining a carrier for uplink initial BWP, comprising:

19. The method of claim 18,

if the network side equipment supports SUL capability and supports NUL to support Msg3 repeated transmission, a first decision threshold is determined and an uplink carrier is selected by using the first decision threshold, wherein the first decision threshold is obtained through system message explicit configuration or implicit calculation according to Msg3 repeated times.

20. The method of claim 6, wherein determining the number of Msg3 retransmissions according to the Msg3 scheduling information comprises:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

21. The method of claim 20, wherein determining whether to schedule the Msg3 retransmission and the number of Msg3 retransmissions according to the second field in the DCI comprises any of:

22. A Msg3 repetition number indication method, implemented by a network-side device, includes:

23. The method of claim 22, wherein a specific field of the Msg2 indicates whether Msg3 retransmission is scheduled and the number of Msg3 retransmissions, and wherein the specific field is any of:

a field in a MAC PDU subheader;

a field in the MAC subpPDU;

fields in the UL grant.

24. The method of claim 23,

whether Msg3 is scheduled for repeated transmission is indicated through a 1bit field in the MAC sub PDU or the MAC PDU sub header; and/or

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

26. The method of claim 25, wherein the indication of whether Msg3 retransmission is scheduled and the number of Msg3 retransmissions is provided by a first field in a UL grant, wherein the first field comprises at least one of:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

27. The method of claim 26, wherein a portion of the TPC field is valued to indicate that Msg3 retransmission is scheduled, and another portion is valued to indicate that Msg3 retransmission is not scheduled; or

28. The method of claim 26,

29. The method of claim 26, wherein the CSI request field, or the MAC sub PDU, or a 1bit field in a MAC PDU subheader, or a 2bit field in a MAC sub PDU and a MAC PDU subheader indicates any one of the following:

indicating whether to schedule the Msg3 repeat transmission;

indicating selection of a TDRA table;

a scaling factor indicating the number of repetitions.

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

31. The method of claim 30, wherein the dedicated TDRA table is predefined for a protocol and/or configured by a network side device via a system message.

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

The MCS field and the TDRA field jointly indicate TDRA and MCS.

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

34. The method of claim 26, further comprising:

35. The method of claim 34,

36. The Msg3 repetition number indication method of claim 22, wherein prior to receiving the first Msg1, the method further comprises:

37. The Msg3 repetition number indication method according to claim 26, wherein the method specifically comprises:

indicating, by a second field in the DCI, whether to schedule Msg3 repeat transmission and a number of Msg3 repeat transmissions, the second field including at least one of:

a TDRA field;

a TPC field;

an MCS field;

a New data indicator field;

HARQ process number field.

38. The method of claim 37, wherein indicating whether Msg3 retransmission is scheduled and the number of Msg3 retransmissions by a second field in the DCI comprises any of:

indicating the Msg3 repeated transmission times or indicating the adjustment quantity of the Msg3 repeated times through the content in the MCS field;

39. An Msg3 repetition number determination device, applied to a terminal, includes:

the system comprises a receiving module and a scheduling module, wherein the receiving module is used for receiving the Msg3 scheduling information of the network side equipment after sending a first Msg1 to the network side equipment;

40. The Msg3 repetition number determination device according to claim 39, wherein,

the determining module is specifically configured to monitor Msg2 in a RAR window, detect a specific field of Msg2, and determine whether to schedule Msg3 retransmission and the number of Msg3 retransmission according to the specific field, where the specific field employs any one of:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

fields in the UL grant.

41. The Msg3 repeat count determination device of claim 40, wherein the determination module is specifically configured to determine whether to schedule the Msg3 repeat transmission and the Msg3 repeat transmission count according to a first field in a UL grant, and the first field comprises at least one of:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

42. The Msg3 repetition number indicating device is applied to a network side device, and comprises:

43. The Msg3 repeat count indication device of claim 42, wherein the sending module is specifically configured to indicate whether to schedule Msg3 repeat transmissions and the Msg3 repeat transmission count through a specific field of the Msg2, wherein the specific field employs any one of the following:

a field in the MAC PDU subheader;

a field in a MAC sub PDU;

fields in the UL grant.

44. The Msg3 repeat count indication device of claim 43, wherein the sending module is specifically configured to indicate whether Msg3 repeat transmission and the Msg3 repeat transmission count are scheduled through a first field in a UL grant, the first field comprises at least one of the following fields:

a CSI request field;

an MCS field;

a TPC field;

a TDRA field.

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

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

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