Message transmission method, terminal, network device, storage medium and program product

Abstract

The application provides a message transmission method, a terminal, a network device, a storage medium and a program product, which are applied to the terminal. The method comprises the following steps: receiving a first message sent by a network device; the first message comprises at least first information; the first information represents the signal quality of a first signal; sending a second message to the network device based on the fact that the first information meets a first requirement; the second message is used for requesting message transmission from the network device; receiving a third message sent by the network device; the third message comprises second information; the second information indicates the number of times of message transmission from the network device. The terminal capability identification can be realized at an early stage, so that the message transmission can be performed.

Description

Technical Field

[0001] This application relates to the field of wireless technology, and in particular to a message transmission method, terminal, network device, storage medium, and program product. Background Technology

[0002] Repetition is a common coverage enhancement method for Physical Uplink Shared Channel (PUSCH). During PUSCH repetition, the terminal needs to first report that it has the corresponding functions and then configure them accordingly. However, during the random access phase, the terminal's capabilities have not yet been reported, and the base station does not know the terminal's capabilities, which makes it impossible to configure repetition resources and transmit messages. Summary of the Invention

[0003] This application provides a message transmission method, terminal, network device, storage medium, and program product that can identify terminal capabilities at an early stage, thereby enabling message transmission.

[0004] To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:

[0005] Firstly, this application proposes a message transmission method applied to a terminal, the method comprising:

[0006] Receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal;

[0007] Based on the first information, a second message is sent to the network device to meet the first requirement; the second message is used to request message transmission from the network device.

[0008] Receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

[0009] Secondly, this application proposes a message transmission method applied to a network device, the method comprising:

[0010] Send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal;

[0011] The terminal receives a second message sent by the terminal based on the first information and meeting the first requirement; the second message is used by the terminal to request message transmission from the network device.

[0012] A third message is sent to the terminal; the third message includes second information; the second information is used to indicate the number of times a message is transmitted to the network device.

[0013] Thirdly, this application proposes a terminal, the terminal comprising:

[0014] A first receiving unit is configured to receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal.

[0015] The first sending unit is configured to send a second message to the network device based on the first information satisfying the first requirement; the second message is used to request message transmission from the network device.

[0016] The first receiving unit is further configured to receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

[0017] Fourthly, this application provides a network device, the network device comprising:

[0018] The second sending unit is configured to send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal.

[0019] The second receiving unit is configured to receive a second message sent by the terminal based on the first information and meeting the first requirement; the second message is used by the terminal to request message transmission from the network device.

[0020] The second sending unit is further configured to send a third message to the terminal; the third message includes second information; the second information is used to indicate the number of times a message is transmitted to the network device.

[0021] Fifthly, this application proposes a terminal, the terminal comprising: a first processor, a first memory, and a first communication bus; the first communication bus is used to realize the connection and communication between the first processor and the first memory; when the first processor executes the running program stored in the first memory, it implements the method described above on the terminal side.

[0022] In a sixth aspect, this application proposes a network device, the network device comprising: a second processor, a second memory, and a second communication bus; the second communication bus is used to realize the connection and communication between the second processor and the second memory; when the second processor executes the running program stored in the second memory, it implements the method described above on the network device side.

[0023] In a seventh aspect, this application proposes a storage medium storing a computer program that, when executed by a first processor, implements the method described above on the terminal side, or, when executed by a second processor, implements the method described above on the network device side.

[0024] Eighthly, this application proposes a computer program product, including a computer program that, when executed by a first processor, implements the method described above on the terminal side, or, when executed by a second processor, implements the method described above on the network device side.

[0025] This application proposes a message transmission method, terminal, network device, storage medium, and program product, applied to a terminal. The method includes: receiving a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal; sending a second message to the network device based on the first information meeting a first requirement; the second message is used to request message transmission from the network device; receiving a third message sent by the network device; the third message includes second information; and the second information indicates the number of times message transmission is performed to the network device. Using the above implementation, the terminal receives a first message sent by the network device, sends a second message to the network device based on the first message meeting the first requirement, the second message is used to request message transmission from the network device, and receives a third message from the network device including second information, the second information indicating the number of times message transmission is performed to the network device. This enables the terminal to send a second message to the network device to request message transmission, that is, the terminal reports its capabilities to the network device through the second message. The base station can identify the terminal's capabilities early on, thereby configuring repeated transmission resources and performing message transmission. Attached Figure Description

[0026] Figure 1 A schematic diagram illustrating an exemplary random access process provided in this application embodiment;

[0027] Figure 2 A schematic diagram of an exemplary TDD system retransmission scheduling process provided for embodiments of this application;

[0028] Figure 3 A flowchart illustrating a message transmission method provided in an embodiment of this application;

[0029] Figure 4 A flowchart illustrating another message transmission method provided in an embodiment of this application;

[0030] Figure 5 A schematic diagram illustrating an exemplary Msg5 repetitive transmission process provided for an embodiment of this application;

[0031] Figure 6A schematic diagram of an exemplary RO bundle provided for embodiments of this application;

[0032] Figure 7 A schematic diagram illustrating an exemplary RAR UL grant information provided for an embodiment of this application;

[0033] Figure 8 A schematic diagram of an exemplary Msg4 provided for an embodiment of this application;

[0034] Figure 9 A schematic diagram of the structure of a terminal provided in this application embodiment. Figure 1 ;

[0035] Figure 10 A schematic diagram of the structure of a terminal provided in this application embodiment. Figure 2 ;

[0036] Figure 11 A schematic diagram of the structure of a network device provided in this application embodiment. Figure 1 ;

[0037] Figure 12 A schematic diagram of the structure of a network device provided in this application embodiment. Figure 2 . Detailed Implementation

[0038] In order to gain a more detailed understanding of the features and technical content of the embodiments of this application, the implementation of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of this application.

[0039] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0040] In the following description, references to "some embodiments" are made, which describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict. It should also be noted that the terms "first," "second," etc., used in the embodiments of this application are only used to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first," "second," etc., may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0041] Coverage, especially uplink coverage, has always been a performance bottleneck for wireless networks. Due to differences in the amount of data carried and the coding methods, different New Radio (NR) channels have varying coverage capabilities. According to the "weakest link" principle, the system's coverage capability is limited by the channel with the worst coverage. Therefore, the 3rd Generation Partnership Project (3GPP) uses various technologies to enhance different channels.

[0042] Random access is an important process for terminals to access the network. Figure 1 This application provides an exemplary schematic diagram of a random access process; as shown in the embodiments of this application. Figure 1 As shown,

[0043] 1. Radio Resource Control (RRC) Idle State (RRC_IDLE).

[0044] 2. Message 1 (Msg1): Physical Random Access Channel (PRACH).

[0045] 3. Message 2 (Msg2): Respond After Receiving (RAR).

[0046] 4. Message 3 (Msg3): Radio Resource Control Setup Request (RRCSetupRequest).

[0047] 5. Message 4 (Msg4): Radio Resource Control Setup (RRCSetup).

[0048] 6. Hybrid Automatic Repeat reQuest_Acknowledge for Msg4, HAQR_ACK for Msg4.

[0049] 7. Wireless Resource Control (RRC) connected status (RRC_CONNECTED).

[0050] 8. Message 5 (Msg5): Radio Resource Control setup completed (RRCSetupComplete).

[0051] In the above process, considering the existing coverage enhancement technologies, the coverage performance of the Msg5:RRCSetupComplete message (for the physical layer, it is characterized by using the Cell Radio Network Temporary Identifier (C-RNTI) (non-temporary Cell Radio Network Temporary Identifier (TC-RNTI)) scrambled downlink control information (DCI) format 0_0 scheduled PUSCH) is relatively poor. Therefore, it is necessary to enhance the coverage of this channel to make up for the coverage shortcomings of this channel and improve the overall coverage capability of the system.

[0052] The physical layer transmission of Msg5 messages is carried on the PUSCH channel. To ensure the reliability and coverage performance of PUSCH channel transmission, HARQ is a basic function. When transmission fails, the base station can request the terminal to retransmit (retransmit) and improve demodulation performance through techniques such as soft combining until successful demodulation. However, HARQ requires the base station to reschedule the terminal for transmission when demodulation fails, which leads to increased latency. Figure 2 This application provides an exemplary TDD system retransmission scheduling process diagram, as shown in the embodiment. Figure 2 As shown, a Time Division Duplex (TDD) system consists of 6 downlink subframes (D) and 4 uplink subframes (U), totaling 9 slots. When a retransmission occurs, 9 slots are required to complete the transmission of the uplink data.

[0053] Retransmission is a common channel enhancement technique in PUSCH channels. In a single PUSCH transmission, the base station allocates uplink resources for multiple time slots to the terminal. The terminal then performs multiple actual PUSCH uplink transmissions based on either time slot-level (repetition type-A) or symbol-level (repetition type-B) time domain resource allocation. Compared to retransmission, retransmission can reduce latency to some extent. Furthermore, retransmission can support up to 32 transmissions, while retransmission typically does not exceed 4 transmissions. Therefore, retransmission can significantly improve coverage performance.

[0054] The configuration methods for repeated transmissions mainly include the following forms:

[0055] For PUSCH repetition type-A: When the DCI scheduling this PUSCH transmission is format 0_1 ​​or 0_2, and C-RNTI is used, the Modulation and Coding Scheme Control Radio Network Temporary Identifier (MCS-C-RNTI) and the Configured Scheduled Unicast Transmission Radio Network Temporary Identifier (CS-RNTI) are used (when the New Data Indication (NDI) = 1) is scrambled using Cyclic Redundancy Check (CRC), the number of repetitions K is determined as follows:

[0056] If the higher-layer parameter numberOfRepetitions is configured in the resource allocation table, K = numberOfRepetitions. In this configuration, each row of the TDRA table corresponds to a number of repetitions. When the base station scheduling terminal performs PUSCH transmission, it will instruct to use a certain row in the TDRA table, thereby simultaneously indicating the corresponding number of repetitions.

[0057] If the higher-layer parameter numberOfRepetitions is not configured, and if the higher-layer parameter Physical Uplink Shared Channel Aggregation Factor (pusch-AggregationFactor) is configured, K = pusch-AggregationFactor. This parameter is located in the Physical Uplink Shared Channel Configuration (PUSCH-config) and is a set of parameters specific to a particular UE and a portion of the bandwidth (BWP).

[0058] In other cases, K=1, and the terminal does not perform repeated transmission.

[0059] All the PUSCH retransmission actions described above require the terminal to first report that it possesses the corresponding functionality. After the User Equipment (UE) capability report, the base station configures it accordingly and activates the corresponding functionality through RRC reconfiguration. However, in the early random access phase, terminal capability reporting has not yet occurred, and the base station is unaware of the terminal's capabilities and cannot configure the corresponding functions. Therefore, some early identification methods need to be introduced during the random access phase to help the base station learn about the terminal's capabilities.

[0060] Based on this, embodiments of this application provide a message transmission method applied to a terminal. Figure 3 This is a flowchart illustrating a message transmission method provided in an embodiment of this application; as shown below. Figure 3 As shown, the method includes:

[0061] S301. Receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of the first signal.

[0062] It should be noted that this message transmission method is applied during the random access phase. In practical applications, this message transmission method can be understood as a message repetition transmission method, specifically the Msg5 repetition transmission method. The terminal can be any device capable of communicating with the network device; there are no limitations here. As an example, the terminal can be a UE (User Equipment). The network device can also be any device capable of communicating with the terminal; there are no limitations here. As an example, the network device can be a next-generation base station (gNB), or simply a base station.

[0063] It should be noted that the first message can be understood as a configuration message for Msg5 retransmission issued by the network device. The first message includes at least one of the following: the network device supports Msg5 retransmission; the Synchronization Signal Block-Reference Signal Received Power (SSB-RSRP) threshold value for triggering Msg5 retransmission; candidate retransmission count information for Msg5 retransmission; and PRACH resource information. The first information can be understood as the SSB-RSRP threshold value information for triggering Msg5 retransmission, the first signal can be understood as the Synchronization Signal Block-Reference Signal Received Power, and the signal quality of the first signal can be understood as the Synchronization Signal Block-Reference Signal Received Power.

[0064] The solution in this application embodiment is based on the distribution of Msg5 repetition configuration information via system messages, which has no impact on legacy terminals.

[0065] S302. Based on the first information, a second message is sent to the network device to meet the first requirement; the second message is used to request message transmission from the network device.

[0066] In the embodiments of this application, the first requirement includes at least one of the following: the value of the third information obtained by the terminal measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0067] It should be noted that the third piece of information can be understood as the SSB-RSRP value measured by the terminal. The first value can be determined according to the actual situation. The first value can be infinity or 0. 0 can be understood as the network device not having an configured SSB-RSRP threshold value.

[0068] It should be noted that sending a second message to the network device based on the first information meeting the first requirement can be understood as follows: if the SSB-RSRP value measured by the terminal is less than the SSB-RSRP threshold value sent by the network device, the terminal is triggered to send a second message to the network device; or, if the network device has not configured an SSB-RSRP threshold value (i.e., the SSB-RSRP threshold value sent by the network device is 0), or if the configured SSB-RSRP threshold value corresponds to the value of "infinity", the terminal is triggered to send a second message to the network device.

[0069] In this embodiment, the second message includes Msg1 and / or Msg3. The second message carries information from the terminal requesting repeated transmission of Msg5. The second message can also be understood as the terminal reporting its capabilities, i.e., the terminal reporting to the network device that it supports the capability of repeated transmission of Msg5.

[0070] In this embodiment of the application, the second message includes Msg1, which is sent using the first PRACH resource; the first PRACH resource is determined by the terminal based on the preamble and / or the random access channel occasion (RO) resource.

[0071] It should be noted that the first PRACH resource can be understood as a portion of the existing preamble resource pool designated for requests related to the Msg5 repetition function. The terminal selects the Synchronization Signal Block (SSB) and corresponding RO in a legacy manner. When the conditions for triggering Msg5 repetition are met, the terminal selects this portion of the preamble for uplink PRACH transmission. Alternatively, RO resources can be used for differentiation. In addition to the existing PRACH resources, an independent set of PRACH resources is configured for requests related to the Msg5 repetition function. When the conditions for triggering Msg5 repetition are met, the terminal selects this new set of PRACH resources for uplink PRACH transmission.

[0072] In the solution of this application embodiment, the terminal uses Msg1 message to request the Msg5 repetition function (capability reporting), which can realize early capability identification.

[0073] In this embodiment of the application, the second message includes Msg1, which is sent using a random access channel time bundle (RObundle); the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0074] It should be noted that for users who simultaneously support repeated transmission of Msg3 and Msg5, RO bundles are used for capability reporting. Encoding the preset RO resource pool can be understood as obtaining RO bundles based on explicit configuration; sorting the preset RO resource pools can be understood as obtaining RO bundles based on implicit rules. RO bundles are obtained by numbering or sorting the preset RO resource pools. For example, this can be illustrated by configuring corresponding preamble resource pools Preamble#1 and Preamble#2 for the two functions. Then, for ROs bound to the same SSB, RO bundles are configured. An RO bundle contains two ROs, which can be explicitly configured in the RRC or determined based on implicit calculation rules. Explicit configuration can number the ROs and then configure every two RO indices as one RO bundle. Implicit rules can be based on a frequency domain ascending order followed by a time domain ascending order, starting from the first valid RO corresponding to the SSB, with every two ROs forming an RO bundle.

[0075] In the solution of this application embodiment, when the terminal simultaneously supports Msg3 and Msg5 repetition functions, reporting via ROBundle can reduce the configuration of additional RACH resources and save RACH resources.

[0076] In this embodiment of the application, the second message includes Msg3; Msg3 is obtained by adding a first field to the RRC message; the first field represents the request message transmission.

[0077] It should be noted that the first field can be understood as a newly added field in RRC. The first field represents a request for message transmission; that is, the meaning of the first field can be understood as a request for Msg5 repetition. In practical applications, the first field can be recorded as Message 5 Repetition Request (Msg5RepetitionRequest).

[0078] In the solution of this application embodiment, the terminal uses Msg3 messages to request the Msg5 repetition function (capability reporting), which does not require additional RO resources.

[0079] S303, Receive a third message sent by a network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

[0080] It should be noted that the third message is a message sent by the network device indicating the number of times the terminal's Msg5 repetitions. The third message includes Msg2; and / or, Msg4; and / or, DCI.

[0081] In this embodiment of the application, the third message includes Msg2; Msg2 includes a first modulation and coding scheme bit field (MCS bit field); the first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first transmit power control command (TPC command) field; the second bit in the first TPC command field is used to indicate the number of message transmissions.

[0082] It should be noted that Msg2 carries Random Access Response Uplink Grant (RAR UL grant) information. The RAR UL grant includes a first MCS bit field, which consists of 4 bits. This first bit can be understood as 2 bits out of the 4 bits in the first MCS bit field. This first bit indicates the number of message transmissions; in other words, it indicates the number of Msg5 repetitions.

[0083] To facilitate understanding, an example can be provided: the first 4-bit MCS bit field in Msg2, reinterpreted to indicate Msg5 repetition, has its meaning changed to 2 bits indicating the MCS and 2 bits indicating the number of Msg5 repetitions, corresponding to 4 candidate values. These candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0084] It should be noted that for terminals that simultaneously report both Msg3 and Msg5 repetition functions, the 2 bits in the MCS bit field of the received Msg2, used to indicate repetition, represent candidate values ​​indicating the number of repetitions for both Msg3 and Msg5. For terminals simultaneously reporting both Msg3 and Msg5 repetition functions, if they receive TC-RNTI scrambled DCI 0_0 used for scheduling Msg3 retransmissions, then the 2 bits in the MCS bit field of this DCI, used to indicate repetition, also represent candidate values ​​indicating the number of repetitions for both Msg3 and Msg5.

[0085] It should be noted that the RAR UL grant includes a first TPC command field, which consists of 3 bits. The second bit can be understood as 2 bits of the 3 bits in the first TPC command field. The second bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5 repetitions.

[0086] To facilitate understanding, an example can be provided: the first TPC command field of the 3 bits in Msg2 is reinterpreted to indicate Msg5 repetition. Its meaning becomes: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions, corresponding to 2 and 4 candidate values ​​respectively. Candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0087] It should be noted that for terminals that simultaneously report both Msg3 and Msg5 repetition functions, the 2 bits in the MCS bit field of the received Msg2, used to indicate repetition, represent a candidate value for the number of Msg3 repetitions. The TPC command bit field then becomes: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions. For terminals simultaneously reporting both Msg3 and Msg5 repetition functions, if they receive TC-RNTI scrambled DCI 0_0 used to schedule Msg3 repetitions, then the 2 bits in the TPC bit field of this DCI, used to indicate repetition, represent a candidate value for the number of Msg5 repetitions.

[0088] In the scheme of this application embodiment, the base station sends a repeated transmission count indication through Msg2, and by reinterpreting the bit field, no additional downlink transmission bits are added.

[0089] In this embodiment of the application, the third message includes Msg4; Msg4 includes the UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0090] It should be noted that Msg4 is a Media Access Control (MAC) Control Element (CE) message carried on a Downlink Shared Channel (PDSCH) during random access. It contains conflict resolution information, namely the UE Contention Resolution Identity. The UE Contention Resolution Identity MAC CE is 48 bits long and carries the Uplink Control Channel Common Channel Service Data Unit (UL CCCH SDU) (the first 48 bits), indicated by a subheader. The first two bits of the subheader are reserved bits, and the third bit can be understood as a reserved bit. This third bit indicates the number of message transmissions; in other words, it indicates the number of Msg5 repetitions.

[0091] For ease of understanding, an example can be provided: the UE Contention Resolution Identity MAC (CE) is 48 bits long and is used to carry the UL CCCH SDU (first 48 bits). It uses a subheader for indication; the first two bits of the subheader are reserved bits, which can be reinterpreted as Msg5repetition indication information, corresponding to four candidate values. These candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0092] It should be noted that the reserved bit, which is used in the independent or joint encoding of Msg3, can be further interpreted as the relationship between the number of repetitions of Msg5 and the number of repetitions of Msg3 when Msg2 indicates Msg3 repetition.

[0093] In the scheme of this application embodiment, the base station indicates the number of retransmissions by reserving bits in Msg4, without adding additional downlink transmission bits.

[0094] In the embodiments of this application, the third message includes a DCI; the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0095] It should be noted that the second MCS bit field can be understood as the 5-bit MCS bit field in DCI. The fourth bit can be understood as 2 bits of the 5 bits in the second MCS bit field. The fourth bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5repetitions.

[0096] For ease of understanding, here's an example: in the received DCI, the 5-bit MCS bit field has the following meaning: 3 bits are used to indicate the MCS, and 2 bits are used to indicate the Msg5 repetition count, corresponding to 8 and 4 candidate values ​​respectively. Candidate values ​​can be sent via system signaling; if not configured, the terminal uses the default candidate values.

[0097] It should be noted that the second TPC command field can be understood as the 2-bit TPC command field in DCI. The fifth bit can be understood as all 2 bits in the second TPC command field. The fifth bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5repetitions.

[0098] For ease of understanding, here's an example: the 2-bit TPC command bit field in the received DCI means that 2 bits are used to indicate the number of Msg5 repetitions, corresponding to 4 candidate values. Candidate values ​​can be sent via system signaling; if not configured, the terminal uses the default candidate values. Optionally, the base station can configure the Msg5 TPC command value in the system message.

[0099] In the scheme of this application embodiment, the base station sends a repeated transmission count indication by scheduling Msg5 transmission of DCI. By reinterpreting the bit field, no additional downlink transmission bits are added, the size of DCI 0_0 is not modified, and the legacy terminal is not affected.

[0100] It should be noted that the terminal performs PUSCH repetition transmission after receiving the message repetition information sent by the network device and the scheduling information carried in the DCI of scheduling Msg5.

[0101] Accordingly, embodiments of this application provide a message transmission method applied to network devices. Figure 4 A flowchart illustrating another message transmission method provided in this application embodiment is shown below. Figure 4 As shown, the method includes:

[0102] S401. Send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal.

[0103] It should be noted that this message transmission method is applied during the random access phase. In practical applications, this message transmission method can be understood as a message repetition transmission method, specifically the Msg5 repetition transmission method. The terminal can be any device capable of communicating with the network device; there is no limitation here. As an example, the terminal can be a UE. The network device can be any device capable of communicating with the terminal; there is no limitation here. As an example, the network device can be a gNB.

[0104] It should be noted that the first message can be understood as a configuration message for Msg5 retransmission issued by the network device. The first message includes at least one of the following: the network device supports Msg5 retransmission; the SSB-RSRP threshold value for triggering Msg5 retransmission; candidate retransmission count information for Msg5 retransmission; and PRACH resource information. The first information can be understood as the SSB-RSRP threshold value information for triggering Msg5 retransmission, the first signal can be understood as the synchronization block reference signal, and the signal quality of the first signal can be understood as the received power of the synchronization block reference signal.

[0105] The solution in this application embodiment is based on the distribution of Msg5 repetition configuration information via system messages, which has no impact on legacy terminals.

[0106] S402, The receiving terminal sends a second message based on the first information to meet the first requirement; the second message is used by the terminal to request message transmission from the network device.

[0107] In the embodiments of this application, the first requirement includes at least one of the following: the value of the third information obtained by the terminal measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0108] It should be noted that the third piece of information can be understood as the SSB-RSRP value measured by the terminal. The first value can be determined according to the actual situation. The first value can be infinity or 0. 0 can be understood as the network device not having an configured SSB-RSRP threshold value.

[0109] It should be noted that the second message sent by the terminal based on the first information meeting the first requirement can be understood as follows: the terminal is triggered to send the second message to the network device when the SSB-RSRP value measured by the terminal is less than the SSB-RSRP threshold value sent by the network device; or the terminal is triggered to send the second message to the network device when the network device has not configured an SSB-RSRP threshold value (i.e., the SSB-RSRP threshold value sent by the network device is 0), or the configured SSB-RSRP threshold value corresponds to the value of "infinity".

[0110] In this embodiment, the second message includes Msg1 and / or Msg3. The second message carries information from the terminal requesting repeated transmission of Msg5. The second message can also be understood as the terminal reporting its capabilities, i.e., the terminal reporting to the network device that it supports the capability of repeated transmission of Msg5.

[0111] In this embodiment of the application, the second message includes Msg1, which is sent using the first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble and / or RO resource.

[0112] It should be noted that the first PRACH resource can be understood as a portion of the existing preamble resource pool designated for requests related to the Msg5 repetition function. The terminal selects the SSB and corresponding RO in a legacy manner. When the conditions for triggering Msg5 repetition are met, the terminal selects this portion of the preamble for uplink PRACH transmission. Alternatively, RO resources can be used for differentiation. In addition to the existing PRACH resources, an independent set of PRACH resources is configured for requests related to the Msg5 repetition function. When the conditions for triggering Msg5 repetition are met, the terminal selects this new set of PRACH resources for uplink PRACH transmission.

[0113] In the solution of this application embodiment, the terminal uses Msg1 message to request the Msg5 repetition function (capability reporting), which can realize early capability identification.

[0114] In this embodiment of the application, the second message includes Msg1, which is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0115] It should be noted that for users who simultaneously support repeated transmission of Msg3 and Msg5, RO bundles are used for capability reporting. Encoding the preset RO resource pool can be understood as obtaining RO bundles based on explicit configuration; sorting the preset RO resource pools can be understood as obtaining RO bundles based on implicit rules. RO bundles are obtained by numbering or sorting the preset RO resource pools. For example, this can be illustrated by configuring corresponding preamble resource pools Preamble#1 and Preamble#2 for the two functions. Then, for ROs bound to the same SSB, RO bundles are configured. An RO bundle contains two ROs, which can be explicitly configured in the RRC or determined based on implicit calculation rules. Explicit configuration can number the ROs and then configure every two RO indices as one RO bundle. Implicit rules can be based on a frequency domain ascending order followed by a time domain ascending order, starting from the first valid RO corresponding to the SSB, with every two ROs forming an RO bundle.

[0116] In the solution of this application embodiment, when the terminal simultaneously supports Msg3 and Msg5 repetition functions, reporting via ROBundle can reduce the configuration of additional RACH resources and save RACH resources.

[0117] In this embodiment of the application, the second message includes Msg3; Msg3 is obtained by adding a first field to the RRC message; the first field represents the request message transmission.

[0118] It should be noted that the first field can be understood as a newly added field in RRC. The first field represents a request for message transmission; that is, the meaning of the first field can be understood as a request for Msg5 repetition. In practical applications, the first field can be recorded as Msg5RepetitionRequest.

[0119] In the solution of this application embodiment, the terminal uses Msg3 messages to request the Msg5 repetition function (capability reporting), which does not require additional RO resources.

[0120] S403, Send a third message to the terminal; the third message includes second information; the second information is used to indicate the number of times the message is transmitted to the network device.

[0121] It should be noted that the third message is a message sent by the network device indicating the number of times the terminal's Msg5 repetitions. The third message includes Msg2; and / or, Msg4; and / or, DCI.

[0122] In the embodiments of this application, the third message includes Msg2; Msg2 includes a first MCS bit field; the first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first TPC command field; the second bit in the first TPC command field is used to indicate the number of message transmissions.

[0123] It should be noted that Msg2 carries RAR UL grant information, which includes a first MCS bitfield, consisting of 4 bits. This first bit can be understood as 2 bits out of the 4 bits in the first MCS bitfield. This first bit indicates the number of message transmissions; specifically, it indicates the number of Msg5 repetitions.

[0124] To facilitate understanding, an example can be provided: the first 4-bit MCS bit field in Msg2, reinterpreted to indicate Msg5 repetition, has its meaning changed to 2 bits indicating the MCS and 2 bits indicating the number of Msg5 repetitions, corresponding to 4 candidate values. These candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0125] It should be noted that for terminals that simultaneously report both Msg3 and Msg5 repetition functions, the 2 bits in the MCS bit field of the received Msg2, used to indicate repetition, represent candidate values ​​indicating the number of repetitions for both Msg3 and Msg5. For terminals simultaneously reporting both Msg3 and Msg5 repetition functions, if they receive TC-RNTI scrambled DCI 0_0 used for scheduling Msg3 retransmissions, then the 2 bits in the MCS bit field of this DCI, used to indicate repetition, also represent candidate values ​​indicating the number of repetitions for both Msg3 and Msg5.

[0126] It should be noted that the RAR UL grant includes a first TPC command field, which consists of 3 bits. The second bit can be understood as 2 bits of the 3 bits in the first TPC command field. The second bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5 repetitions.

[0127] To facilitate understanding, an example can be provided: the first TPC command field of the 3 bits in Msg2 is reinterpreted to indicate Msg5 repetition. Its meaning becomes: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions, corresponding to 2 and 4 candidate values ​​respectively. Candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0128] It should be noted that for terminals that simultaneously report both Msg3 and Msg5 repetition functions, the 2 bits in the MCS bit field of the received Msg2, used to indicate repetition, represent a candidate value for the number of Msg3 repetitions. The TPC command bit field then becomes: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions. For terminals simultaneously reporting both Msg3 and Msg5 repetition functions, if they receive TC-RNTI scrambled DCI 0_0 used to schedule Msg3 repetitions, then the 2 bits in the TPC bit field of this DCI, used to indicate repetition, represent a candidate value for the number of Msg5 repetitions.

[0129] In the scheme of this application embodiment, the base station sends a repeated transmission count indication through Msg2, and by reinterpreting the bit field, no additional downlink transmission bits are added.

[0130] In this embodiment, the third message includes Msg4; Msg4 includes UE Contention Resolution Identity; the third bit in UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0131] It should be noted that Msg4 is a MAC CE message carried by a downlink PDSCH in random access, which contains conflict resolution information, namely the UE Contention Resolution Identity. The UE Contention Resolution Identity MAC CE is 48 bits long and is used to carry the UL CCCH SDU (first 48 bits), which is indicated using a subheader. The first two bits of the subheader are reserved bits, and the third bit can be understood as a reserved bit. The third bit is used to indicate the number of message transmissions; that is, the third bit is used to indicate the number of Msg5 repetitions.

[0132] For ease of understanding, an example can be provided: the UE Contention Resolution Identity MAC (CE) is 48 bits long and is used to carry the UL CCCH SDU (first 48 bits). It uses a subheader for indication; the first two bits of the subheader are reserved bits, which can be reinterpreted as Msg5repetition indication information, corresponding to four candidate values. These candidate values ​​can be issued via system signaling; if not configured, the terminal uses the default candidate values.

[0133] It should be noted that the reserved bit, which is used in the independent or joint encoding of Msg3, can be further interpreted as the relationship between the number of repetitions of Msg5 and the number of repetitions of Msg3 when Msg2 indicates Msg3 repetition.

[0134] In the scheme of this application embodiment, the base station indicates the number of retransmissions by reserving bits in Msg4, without adding additional downlink transmission bits.

[0135] In the embodiments of this application, the third message includes a DCI; the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0136] It should be noted that the second MCS bit field can be understood as the 5-bit MCS bit field in DCI. The fourth bit can be understood as 2 bits of the 5 bits in the second MCS bit field. The fourth bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5repetitions.

[0137] For ease of understanding, here's an example: in the received DCI, the 5-bit MCS bit field has the following meaning: 3 bits are used to indicate the MCS, and 2 bits are used to indicate the Msg5 repetition count, corresponding to 8 and 4 candidate values ​​respectively. Candidate values ​​can be sent via system signaling; if not configured, the terminal uses the default candidate values.

[0138] It should be noted that the second TPC command field can be understood as the 2-bit TPC command field in DCI. The fifth bit can be understood as all 2 bits in the second TPC command field. The fifth bit is used to indicate the number of message transmissions, which can be understood as indicating the number of Msg5repetitions.

[0139] For ease of understanding, here's an example: the 2-bit TPC command bit field in the received DCI means that 2 bits are used to indicate the number of Msg5 repetitions, corresponding to 4 candidate values. Candidate values ​​can be sent via system signaling; if not configured, the terminal uses the default candidate values. Optionally, the base station can configure the Msg5 TPC command value in the system message.

[0140] In the scheme of this application embodiment, the base station sends a repeated transmission count indication by scheduling Msg5 transmission of DCI. By reinterpreting the bit field, no additional downlink transmission bits are added, the size of DCI 0_0 is not modified, and the legacy terminal is not affected.

[0141] It should be noted that the terminal performs PUSCH repetition transmission after receiving the message repetition information sent by the network device and the scheduling information carried in the DCI of scheduling Msg5.

[0142] To facilitate understanding, the above message transmission method is illustrated with an example here. Figure 5 This application provides an exemplary flowchart of Msg5 repeated transmission; as shown in the embodiments of this application. Figure 5 As shown,

[0143] 1. The base station issues Msg5 repetition configuration.

[0144] 2. Terminal reporting supports Msg5 repetition capability.

[0145] 3. The base station sends Msg5 scheduling information.

[0146] 4. The terminal repeatedly transmits Msg5 according to the scheduling information.

[0147] To make it easier to understand, the above steps are explained in detail here:

[0148] Step 1: First, the base station needs to inform the terminal that it supports this function and then distribute the resources for the terminal to report its capabilities. This process can be achieved through system message distribution.

[0149] The configuration message from the base station to the terminal should include the following:

[0150] 1. The base station supports the Msg5 repetition function (which can be implicitly indicated by configuration as described below, or explicitly configured as a field).

[0151] 2. Conditions for triggering Msg5 repetition, such as the SSB-RSRP threshold.

[0152] 3. Number of candidate repetitions for Msg5 repetition (optional; if not configured, the terminal will use the default number of one or a set of repetitions).

[0153] 4. Other optional configurations for Msg5 repetition (if the dynamic indication of Msg5 repetition affects other DCI indication information, this information may need to be reinterpreted).

[0154] The specific configuration messages that the base station sends to the terminal include:

[0155] {;

[0156] Msg5-repetition enumeration (ENUMERATED) enabled {enabled} optional (OPTIONAL);

[0157] Reference signal received power-threshold message 5 (Rsrp-ThresholdMsg5) ENUMERATED {enabled} OPTIONAL;

[0158] Number of Radio Frames Msg5, NrofMsg5 - RepetitionsList Sequence Number (SIZE) (4) OF NrofMsg5 - RepetitionsList OPTIONAL;

[0159] mcs-Msg5-Repetitions SEQUENCE(SIZE(8))OFINTEGER(0…31)OPTIONAL;

[0160] }

[0161] The second step is that when a terminal with Msg5 repetition function receives a system message sent by the base station, it can demodulate the content of the relevant fields. Terminals without this function ignore the relevant fields.

[0162] After the terminal demodulates the relevant fields, it first needs to make a decision based on the SSB-RSRP threshold configured by the base station:

[0163] If the terminal's measured SSB-RSRP is below the threshold, the terminal will be triggered to report a Msg5 repetition request.

[0164] If the base station does not configure the SSB-RSRP threshold, or if the configured threshold value is "infinity", the terminal will be triggered to report the Msg5 repetition capability.

[0165] Before the DCI for scheduling Msg5 transmission is sent, the terminal needs to request Msg5 repetition from the base station. Therefore, in the random access procedure, the uplink transmission performed by the terminal from the time the system message is sent to the time before the DCI is sent can be considered to carry the request message.

[0166] Option 1: Msg1.

[0167] The terminal uses Msg1 to report the Msg5 repetition request.

[0168] To differentiate between users with Msg5 repetition functionality and legacy users, a separate PRACH resource is needed. This can be achieved through preamble and RO resources to distinguish between the two types of users.

[0169] (1) Differentiation is achieved using preamble resources. This involves allocating a portion of the existing preamble resource pool to requests used for the Msg5 repetition function. The terminal selects the SSB and corresponding RO according to legacy criteria. When the conditions for triggering Msg5 repetition are met, the terminal selects this portion of the preamble for uplink PRACH transmission. The configuration method is as follows:

[0170] Feature Combination Preambles {;

[0171] feature Combination; feature merging;

[0172] startPreambleForThisPartition; This is the preamble for booting this partition.

[0173] numberOfPreamblesPerSSB-ForThisPartition; the number of preambles for each synchronization signal block in this partition;

[0174] …

[0175] };

[0176] featureCombination{; Functional merging;

[0177] Msg5 - Repetition; Message 5 is transmitted again.

[0178] …

[0179] }

[0180] (2) Differentiation using RO resources: This involves configuring an additional set of independent PRACH resources, in addition to the existing PRACH resources, for Msg5 repetition requests. When the terminal meets the conditions for triggering Msg5 repetition, it selects this new PRACH resource for uplink PRACH transmission. The configuration method is as follows:

[0181] BWP-UplinkCommon {Shared uplink resources for a portion of bandwidth;}

[0182] …

[0183] AdditionalRACH-Config adds random access signal configuration;

[0184] …

[0185] };

[0186] AdditionalRACH-Config {Add random access channel configuration;}

[0187] …

[0188] RACH-ConfigCommon provides shared resources for random access channel configuration.

[0189] …

[0190] };

[0191] RACH-ConfigCommon { Random access channel configuration shared resources;}

[0192] …

[0193] FeatureCombinationPreambles features preamble merging;

[0194] …

[0195] }

[0196] In Rel-17, a dynamic repetition indication function for randomly accessed Msg3 messages was introduced. The general workflow is as follows: the terminal first reports a request using PRACH resources; then, the base station indicates the repetition count in the Msg3 scheduling information; and the terminal then performs the Msg3 repetition operation. Considering that when Msg5 is in a coverage-limited scenario, Msg3 is also likely to have limited coverage, it is necessary to consider scenarios where both functions are enabled simultaneously. Since these two functions are not bound together, considering the diversity of terminals, at least three additional PRACH resources are required to indicate support for Msg3 repetition, support for Msg5 repetition, and support both features simultaneously, for a total of three terminal types. Given the limited number of PRACH resources, and the fact that more features will require PRACH resources for early identification in the present and future, it is necessary to improve the degree of resource reuse.

[0197] (3) Use preamble resources to indicate the Msg3 repetition and Msg5 repetition functions, and use RO bundles to indicate users who support both functions simultaneously, as follows. First, configure the corresponding preamble resource pools Preamble#1 and Preamble#2 for the two functions according to the method in (1). Then, configure the RO bundle for ROs bound to the same SSB. The RO bundle contains two ROs, which can be explicitly configured in RRC or determined based on implicit calculation rules. Explicit configuration can number the ROs and then configure every two RO indices as one RO bundle. Implicit rules can be based on the order of first frequency domain ascending and then time domain ascending, starting from the first valid RO corresponding to the SSB, with every two ROs forming one RO bundle. For terminals that only support the single function of Msg3 repetition or Msg5 repetition, a preamble from the preamble pool corresponding to its function will be selected, and the SSB and corresponding RO will be selected using the legacy method for uplink PRACH transmission. For terminals that support both of the above functions, the ROBundle used will be determined through RRC configuration. Within the ROBundle, one preamble representing the Msg3 repetition function (preamble #1) and one preamble representing the Msg5 repetition function (preamble #2) will be transmitted on each ROBundle. When the base station receives two of the above preambles in the ROBundle, it determines that they were sent by the same terminal and that the terminal supports both functions. Figure 6A schematic diagram of an exemplary RO bundle provided in this application embodiment, such as... Figure 6 As shown, the horizontal axis represents time and the vertical axis represents frequency. Starting from the first RO associated with the same SSB, the RO bundles are arranged in ascending order in the frequency domain (vertical axis), with every two RO bundles forming a bundle. Then, the RO bundles are arranged in ascending order in the time domain (horizontal axis), with every two RO bundles forming a bundle.

[0198] Collision avoidance analysis: When the base station receives two of the above preambles in the RO bundle, one possibility is that it is the same terminal supporting both functions, and the other possibility is that there are two terminals supporting a single function. To reduce the probability of false positives, the following two additional enhancements can be considered.

[0199] First, the order of transmission of two preambles can be specified. When terminals with two functions transmit preambles within the RO bundle, the order is to transmit the preamble with the smaller index first, followed by the preamble with the larger index (and vice versa). The order of ROs is based on ascending frequency domain order followed by ascending time domain order.

[0200] Second, an additional preamble index offset can be configured. The base station configures this parameter for terminals that support both functions simultaneously. After selecting preamble index #1 in the PRACH resource pool Preamble #1 for function 1, the terminal determines the preamble index #2 used to indicate the PRACH transmission for function 2 by adding preamble index #1 to the preamble index offset. The requirement for the preamble index offset is that the indicated preamble index #2 must fall within the preamble resource pool Preamble #2 used to indicate function 2.

[0201] Option 2: Msg3.

[0202] The terminal uses Msg3 to report a request for Msg5 repetition. Specifically, a new IE is added to the RRC message, signifying a request for Msg5 repetition. The configuration method is as follows:

[0203] RRCReestablishmentRequest::=SEQUENCE{Radio Resource Control Reestablishment Request::=Sequence Number;}

[0204] rrcReestablishmentRequest - IEs; Radio Resource Control Reestablishment Request - Information Interaction System;

[0205] };

[0206] RRCReestablishmentRequest-IEs::=SEQUENCE{Radio Resource Control Reestablishment Request-Info Interaction System::=Serial Number;

[0207] UE-Identity: Terminal identity identifier; ReestabUE-Identity: Terminal identity identifier for call reconstruction;

[0208] The cause of reestablishmentCause; The cause of reestablishmentCause;

[0209] spare; BIT STRING(SIZE(1)); bit string size(1);

[0210] Msg5RepetitionRequest ENUMERATED{enabled}; Message 5 repetition request enumeration (enabled);

[0211] }

[0212] Third, after receiving the Msg5 repetition request from the terminal, the base station needs to indicate the specific number of repetitions to the terminal in subsequent downlink information.

[0213] Option 1: Based on Msg2 instructions.

[0214] Msg2 carries RAR UL grant information, the contents of which are shown in the table below: Figure 7 A schematic diagram illustrating an exemplary RAR UL grant information provided in this application embodiment; as shown Figure 7As shown, the RAR UL grant field includes the Extension field (E), Type field (T), Reserved bit (R), Backoff Indicator (BI), Random Access Preamble Identifier (RAPID), TimingAdvance, UL, UL Grant, and Temporary C-RNTI. Table 1 shows the specific contents of the RAR UL grant field.

[0215] Table 1

[0216]

[0217] In Table 1, the RAR grant field represents the random access response grant field; Number of bits represents the number of bits; Frequency hopping flag represents the frequency hopping flag; PUSCH frequency resource allocation represents the PUSCH frequency resource allocation; PUSCH time resource allocation represents the PUSCH time resource allocation; MCS represents the modulation and coding scheme; TPC command for PUSCH represents the PUSCH transmission power control command; CSIrequest represents the channel state information request; ChannelAccess-CPext represents the channel access-CP extension; the number of bits for PUSCH frequency resource allocation has two cases: 14 bits when channel access operation does not share spectrum with other devices, and 12 bits when channel access operation does share spectrum with other devices; the number of bits for ChannelAccess_CPext also has two cases: 0 bits when channel access operation does not share spectrum with other devices, and 1 bit when channel access operation does share spectrum with other devices. A bit count of 0 indicates that PUSCH does not hop frequency; a bit count of 1 indicates that PUSCH hopping is enabled.

[0218] (1) The MCS bit field in Msg2 is reinterpreted to indicate Msg5 repetition. Specifically, after the terminal reports the Msg5 repetition function in the first step, it expects the 4-bit MCS bit field in the received Msg2 to be reinterpreted, with 2 bits indicating the MCS and 2 bits indicating the number of Msg5 repetitions, corresponding to 4 candidate values. The candidate values ​​can be issued through system signaling; if not configured, the terminal uses the default candidate values.

[0219] For a terminal that reports both Msg3 and Msg5 repetition functions in the first step, the 2 bits in the MCS bit field of the received Msg2 that indicate repetition means that it simultaneously indicates the candidate value of the number of Msg3 and Msg5 repetitions.

[0220] For a terminal that reports both Msg3 and Msg5 repetition functions in the first step, if it receives a TC-RNTI scrambled DCI 0_0 used to schedule Msg3 repetition, then the 2 bits of the MCS bit field in the DCI used to indicate repetition mean that it simultaneously indicates the candidate value of the number of Msg3 and Msg5 repetitions.

[0221] (2) TPC command field reinterpretation is used to indicate Msg5 repetition. Specifically, after the terminal reports the Msg5 repetition function in the first step, it expects the 3-bit TPC command bitfield in the received Msg2 to be interpreted as follows: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions, corresponding to 2 and 4 candidate values ​​respectively. The candidate values ​​can be issued through system signaling; if not configured, the terminal uses the default candidate values.

[0222] For a terminal that reports both Msg3 and Msg5 repetition functions in the first step, the 2 bits in the MCS bit field of the received Msg2, which indicate the repetition, represent a candidate value for the number of Msg3 repetitions. The TPC command bit field then changes its meaning: 1 bit indicates the TPC command, and 2 bits indicate the number of Msg5 repetitions.

[0223] For a terminal that reports both Msg3 and Msg5 repetition functions in the first step, if it receives a DCI 0_0 scrambled by TC-RNTI for scheduling Msg3 repetition, then the 2 bits in the TPC bit field of this DCI used to indicate repetition are candidate values ​​indicating the number of Msg5 repetitions.

[0224] Option 2: Based on Msg4 instructions.

[0225] Msg4 is a MAC CE message carried by a downlink PDSCH in random access, which contains collision resolution information. Figure 8 A schematic diagram of an exemplary Msg4 provided for an embodiment of this application; as shown Figure 8 As shown, Msg4 includes the UE Contention Resolution Identity, R, and Language Identifier (LCID)-62, with each UE Contention Resolution Identity corresponding to an octet (Oct). The UE Contention Resolution Identity MAC CE is 48 bits long and is used to carry the UL CCCH SDU (first 48 bits). It is indicated using a subheader, such as... Figure 8 As shown, the first two bits of the subheader are reserved bits, which can be reinterpreted as Msg5repetition indication information, corresponding to four candidate values. These candidate values ​​can be sent via system signaling; if not configured, the terminal uses the default candidate values.

[0226] Independent or joint encoding with Msg3: The reserved bit can be further interpreted as the relationship between the number of repetitions of Msg5 and the number of repetitions of Msg3 when Msg2 indicates Msg3 repetition.

[0227] Option 3: DCI indication based on scheduling Msg5 transmission.

[0228] The DCI for scheduling Msg5 transmission has a format of 0_0. Its specific contents are shown in Table 2, which is the content table for DCI format 0_0. Table 2 is shown below:

[0229] Table 2

[0230]

[0231] In Table 2, Field(Item) represents a field (item); Bits represents the number of bits; Reference represents a reference; Identifier for DCI formats represents the DCI format identifier; Frequency domain resource assignment represents frequency domain resource assignment; Variable with UL BWP N_RB represents the change based on the number of resource blocks (RBs) in the uplink BWP; Indicate PRB location within the BWP represents the PRB location within the BWP; The number of bits and the value is determined as described here represents the number of bits and the value determined as described here; Time domain resource assignment represents time domain resource assignment; Carries the row index of the items in pusch allocationList in RRC represents the row index of each item in puschallocationList in RRC; Frequency hopping flag represents the frequency domain frequency hopping flag; Modulation and coding scheme represents the modulation and coding scheme; New data indicator represents the new data indicator; Redundancy version represents the redundancy version; HARQ process number represents the HARQ process number; TPC command for scheduled PUSCH represents the TPC command for scheduling PUSCH; UL / SUL The indicator represents the uplink / supplementary uplink indicator; 0 bit: SUL not figured means 0 bits: SUL not configured; 1 bit: SUL configured means 1 bit: SUL configured.

[0232] After a terminal reports that it supports Msg5 repetition capability, it expects to obtain an indication of the number of repetitions in the DCI that schedules Msg5. The specific indication method is as follows:

[0233] (1) The MCS bit field is used for indication. In the received DCI, the 5 bits of the MCS bit field have the following meanings: 3 bits are used to indicate the MCS, and 2 bits are used to indicate the Msg5 repetition number, corresponding to 8 and 4 candidate values ​​respectively. The candidate values ​​can be issued through system signaling. If not configured, the terminal uses the default candidate values.

[0234] (2) TPC command field indication. The 2-bit TPC command bit field in the received DCI becomes a 2-bit indicator of the Msg5 repetition count, corresponding to 4 candidate values. Candidate values ​​can be issued through system signaling; if not configured, the terminal uses the default candidate value. Optionally, the base station can configure the Msg5 TPC command value in the system message.

[0235] This application provides a terminal. Figure 9 A schematic diagram of the structure of a terminal provided in this application embodiment. Figure 1 ,like Figure 9 As shown, terminal 900 includes:

[0236] The first receiving unit 901 is configured to receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of the first signal.

[0237] The first sending unit 902 is configured to send a second message to the network device based on the first information satisfying the first requirement; the second message is used to request message transmission from the network device.

[0238] The first receiving unit 903 is further configured to receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

[0239] Optionally, the first message includes at least one of the following: the network device supports repeated transmission of message 5 Msg5; the SSB-RSRP threshold value for triggering repeated transmission of Msg5; candidate repeated transmission count information for repeated transmission of Msg5; and PRACH resource information.

[0240] Optionally, the first requirement includes at least one of the following: the value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0241] Optionally, the second message includes: Msg1; and / or Msg3.

[0242] Optionally, Msg1 is transmitted using a first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble resource and / or RO resource.

[0243] Optionally, Msg1 is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0244] Optionally, Msg3 is configured by adding a first field to the RRC message; the first field represents the request message transmission.

[0245] Optionally, the third message includes: Msg2; and / or, Msg4; and / or, DCI.

[0246] Optionally, Msg2 includes a first MCS bit field; a first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first TPC command field; a second bit in the first TPC command field is used to indicate the number of message transmissions.

[0247] Optionally, Msg4 includes the UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0248] Optionally, the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0249] Figure 10 A schematic diagram of the structure of a terminal provided in this application embodiment. Figure 2 In practical applications, based on the same disclosed concept of the above embodiments, such as Figure 10 As shown, the terminal 900 in this embodiment includes: a first processor 903, a first memory 904, and a first communication bus 905.

[0250] The aforementioned first processor 903 can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), CPU, controller, microcontroller, and microprocessor. It is understood that, for different devices, the electronic device used to implement the functions of the aforementioned first processor can also be other types, and this embodiment does not impose specific limitations.

[0251] In this embodiment, the first communication bus 905 is used to establish communication between the first processor 903 and the first memory 904; when the first processor 903 executes the running program stored in the first memory 904, it implements the following message transmission method:

[0252] Receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal; based on the first information, a second message is sent to the network device to meet a first requirement; the second message is used to request message transmission from the network device; receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times message transmission is performed to the network device.

[0253] Further, the first message includes at least one of the following: the network device supports message 5 Msg5 retransmission; the SSB-RSRP threshold value for triggering Msg5 retransmission; candidate retransmission count information for Msg5 retransmission; and PRACH resource information.

[0254] Further, the first requirement includes at least one of the following: the value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0255] Furthermore, the second message includes: Msg1; and / or Msg3.

[0256] Furthermore, Msg1 is transmitted using a first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble resource and / or RO resource.

[0257] Furthermore, Msg1 is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0258] Furthermore, Msg3 is configured by adding a first field to the RRC message; the first field represents the request message transmission.

[0259] Furthermore, the third message includes: Msg2; and / or, Msg4; and / or, DCI.

[0260] Furthermore, Msg2 includes a first MCS bit field; a first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first TPC command field; a second bit in the first TPC command field is used to indicate the number of message transmissions.

[0261] Furthermore, Msg4 includes UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0262] Furthermore, the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0263] This application provides a network device. Figure 11 A schematic diagram of the structure of a network device provided in this application embodiment. Figure 1 ,like Figure 11 As shown, the network device 1100 includes:

[0264] The second sending unit 1101 is used to send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal.

[0265] The second receiving unit 1102 is configured to receive a second message sent by the terminal based on the first information and meeting the first requirement; the second message is used by the terminal to request message transmission from the network device.

[0266] The second sending unit 1101 is further configured to send a third message to the terminal; the third message includes second information; the second information is used to indicate the number of times a message is transmitted to the network device.

[0267] Optionally, the first message includes at least one of the following: the network device supports Msg5 retransmission; the SSB-RSRP threshold value for triggering Msg5 retransmission; candidate retransmission count information for Msg5 retransmission; and PRACH resource information.

[0268] Optionally, the first requirement includes at least one of the following: the value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0269] Optionally, the second message includes: Msg1; and / or Msg3.

[0270] Optionally, Msg1 is transmitted using a first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble resource and / or RO resource.

[0271] Optionally, Msg1 is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0272] Optionally, Msg3 is configured by adding a first field to the RRC message; the first field represents the request message transmission.

[0273] Optionally, the third message includes: Msg2; and / or, Msg4; and / or, DCI.

[0274] Optionally, Msg2 includes a first MCS bit field; a first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first TPC command field; a second bit in the first TPC command field is used to indicate the number of message transmissions.

[0275] Optionally, Msg4 includes the UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0276] Optionally, the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0277] Figure 12 A schematic diagram of the structure of a network device provided in this application embodiment. Figure 2 In practical applications, based on the same disclosed concept of the above embodiments, such as Figure 12 As shown, the network device 1100 in this embodiment includes: a second processor 1103, a second memory 1104, and a second communication bus 1105.

[0278] The aforementioned second processor 1103 can be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor. It is understood that, for different devices, the electronic device used to implement the functions of the aforementioned second processor can also be other types, and this embodiment does not impose specific limitations.

[0279] In this embodiment, the second communication bus 1105 is used to establish communication between the second processor 1103 and the second memory 1104; when the second processor 1103 executes the running program stored in the second memory 1104, it implements the following message transmission method:

[0280] Send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of a first signal; receive a second message sent by the terminal based on the first information to meet a first requirement; the second message is used by the terminal to request message transmission from the network device; send a third message to the terminal; the third message includes second information; the second information is used to indicate the number of times message transmission is performed to the network device.

[0281] Further, the first message includes at least one of the following: the network device supports Msg5 retransmission; the SSB-RSRP threshold value for triggering Msg5 retransmission; candidate retransmission count information for Msg5 retransmission; and PRACH resource information.

[0282] Further, the first requirement includes at least one of the following: the value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; or, the value of the first information is a first value.

[0283] Furthermore, the second message includes: Msg1; and / or Msg3.

[0284] Furthermore, Msg1 is transmitted using a first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble resource and / or RO resource.

[0285] Furthermore, Msg1 is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

[0286] Furthermore, Msg3 is configured by adding a first field to the RRC message; the first field represents the request message transmission.

[0287] Furthermore, the third message includes: Msg2; and / or, Msg4; and / or, DCI.

[0288] Furthermore, Msg2 includes a first MCS bit field; a first bit in the first MCS bit field is used to indicate the number of message transmissions; and / or, Msg2 includes a first TPC command field; a second bit in the first TPC command field is used to indicate the number of message transmissions.

[0289] Furthermore, Msg4 includes UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

[0290] Furthermore, the DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions; and / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

[0291] This application provides a storage medium storing a computer program thereon. The computer-readable storage medium stores one or more programs, which can be executed by one or more processors. The computer program implements the message transmission method on the terminal side and / or the message transmission method on the network device side as described above.

[0292] Based on the above embodiments, this application provides a computer program product, including a computer program that can be executed by one or more processors, and the computer program implements the message transmission method on the terminal side and / or the message transmission method on the network device side as described above.

[0293] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0294] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause an image display device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0295] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A message transmission method, characterized in that, Applied to a terminal, the method includes: Receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal; Based on the first information, a second message is sent to the network device to meet the first requirement; the second message is used to request message transmission from the network device. Receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

2. The method according to claim 1, characterized in that, The first message includes at least one of the following: The network device supports repeated transmission of message 5Msg5; The SSB-RSRP threshold value of the synchronization signal block reference signal received power that triggers repeated transmission of Msg5; Msg5 repeat transmission candidate repeat transmission count information; Physical Random Access Channel (PRACH) resource information.

3. The method according to claim 1, characterized in that, The first requirement includes at least one of the following: The value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; Alternatively, the value of the first information may be a first value.

4. The method according to claim 1, characterized in that, The second message includes: Msg1; And / or Msg3.

5. The method according to claim 4, characterized in that: Msg1 is transmitted using the first PRACH resource; the first PRACH resource is determined by the terminal based on the preamble resource and / or the random access channel timing (RO) resource.

6. The method according to claim 4, characterized in that: Msg1 is transmitted using a random access channel and a RO bundle is used; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

7. The method according to claim 4, characterized in that: The Msg3 is configured by adding a first field to the Radio Resource Control (RRC) message; the first field represents the request message transmission.

8. The method according to claim 1, characterized in that, The third message includes: Msg2; And / or, Msg4; And / or, Downlink Control Information (DCI).

9. The method according to claim 8, characterized in that: Msg2 includes a first modulation and coding scheme bit field (MCS bit field); the first bit in the first MCS bit field is used to indicate the number of message transmissions. And / or, the Msg2 includes a first transmit power control command (TPC) field; the second bit in the first TPC command field is used to indicate the number of message transmissions.

10. The method according to claim 8, characterized in that: The Msg4 includes a UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

11. The method according to claim 8, characterized in that: The DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions. And / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

12. A message transmission method, characterized in that, Applied to network devices, the method includes: Send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal; The terminal receives a second message sent by the terminal based on the first information and meeting the first requirement; the second message is used by the terminal to request message transmission from the network device. A third message is sent to the terminal; the third message includes second information; the second information is used to indicate the number of times a message is transmitted to the network device.

13. The method according to claim 12, characterized in that, The first message includes at least one of the following: The network device supports Msg5 retransmission; The SSB-RSRP threshold that triggers Msg5 retransmission; Msg5 repeat transmission candidate repeat transmission count information; PRACH resource information.

14. The method according to claim 12, characterized in that, The first requirement includes at least one of the following: The value of the third information obtained by the terminal from measuring the first signal is less than the value of the first information; Alternatively, the value of the first information may be a first value.

15. The method according to claim 12, characterized in that, The second message includes: Msg1; And / or Msg3.

16. The method according to claim 15, characterized in that: Msg1 is transmitted using the first PRACH resource; the first PRACH resource is determined by the terminal based on the Preamble resource and / or RO resource.

17. The method according to claim 15, characterized in that: The Msg1 is sent using an RO bundle; the RO bundle is obtained by numbering or sorting a preset RO resource pool.

18. The method according to claim 15, characterized in that: Msg3 is configured by adding a first field to the RRC message; the first field represents the request message transmission.

19. The method according to claim 12, characterized in that, The third message includes: Msg2; And / or, Msg4; And / or, DCI.

20. The method according to claim 19, characterized in that: Msg2 includes a first MCS bit field; the first bit in the first MCS bit field is used to indicate the number of message transmissions; And / or, the Msg2 includes a first TPC command field; a second bit in the first TPC command field is used to indicate the number of message transmissions.

21. The method according to claim 19, characterized in that: The Msg4 includes the UE Contention Resolution Identity; the third bit in the UE Contention Resolution Identity is used to indicate the number of message transmissions.

22. The method according to claim 19, characterized in that: The DCI includes a second MCS bit field; the fourth bit in the second MCS bit field is used to indicate the number of message transmissions. And / or, the DCI includes a second TPC command field; the fifth bit in the second TPC command field is used to indicate the number of message transmissions.

23. A terminal, characterized in that, The terminal includes: A first receiving unit is configured to receive a first message sent by a network device; the first message includes at least first information; the first information characterizes the signal quality of a first signal. The first sending unit is configured to send a second message to the network device based on the first information satisfying the first requirement; the second message is used to request message transmission from the network device. The first receiving unit is further configured to receive a third message sent by the network device; the third message includes second information; the second information indicates the number of times a message is transmitted to the network device.

24. A network device, characterized in that, The network device includes: The second sending unit is configured to send a first message to the terminal; the first message includes at least first information; the first information characterizes the signal quality of the first signal. The second receiving unit is configured to receive a second message sent by the terminal based on the first information and meeting the first requirement; the second message is used by the terminal to request message transmission from the network device. The second sending unit is further configured to send a third message to the terminal; the third message includes second information; the second information is used to indicate the number of times a message is transmitted to the network device.

25. A terminal, characterized in that, The terminal includes: a first processor, a first memory, and a first communication bus; the first communication bus is used to realize the connection and communication between the first processor and the first memory; when the first processor executes the running program stored in the first memory, it implements the method as described in any one of claims 1-11.

26. A network device, characterized in that, The network device includes: a second processor, a second memory, and a second communication bus; the second communication bus is used to realize the connection and communication between the second processor and the second memory; when the second processor executes the running program stored in the second memory, it implements the method as described in any one of claims 12-22.

27. A storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by a first processor, implements the method as described in any one of claims 1-11, or, when executed by a second processor, implements the method as described in any one of claims 12-22.

28. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by the first processor, implements the method as described in any one of claims 1 to 11, or, when executed by the second processor, implements the method as described in any one of claims 12 to 22.

Images