Information repeated transmission method and device and storage medium

Abstract

The invention relates to an information repeated transmission method and device and a storage medium. The information repeated transmission method of the user terminal UE comprises the following steps: the UE executes physical uplink shared channel PUSCH repeated transmission, the PUSCH is scheduled by a DCI format 0 of downlink control information DCI, and the cyclic redundancy check CRC of the DCI is scrambled by a cell radio network temporary identifier C-RNTI, wherein the number of times of repeated transmission of the PUSCH is determined based on the DCI indication or based on the number of times of repeated transmission of Msg3 in a random access process.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and in particular to a method, apparatus, and storage medium for repeatedly transmitting a radio resource control connection establishment completion message during a random access procedure. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) introduced repeated transmission of Msg3 in Rel-17 and repeated transmission of the Physical Random Access Channel (PRACH) in Rel-18. Thanks to the improved coverage performance of these channels, the success rate of random access for users within the cell has been correspondingly improved.

[0003] However, during random access in mobile communication, when the user equipment (UE) connects to the network side, a radio resource control (RRC) connection needs to be established. The relevant signaling procedures are as follows: Figure 1 As shown in the diagram, UE 10 sends signaling 13, i.e., the RRCSetupRequest message (Message 3), to network 20 requesting the establishment of an RRC connection. Network 20 returns signaling 14, i.e., the RRCSetup message (Message 4), regarding the RRC establishment. After successful random access, UE 10 needs to transmit the RRCSetupComplete message (Message 5) to network 20 to successfully complete the RRC connection establishment, and the UE enters the RRC_CONNECTED state.

[0004] Msg5 is sent by the UE to the network side as an uplink transmission. The logical channel is the Dedicated Control Channel (DCCH). According to protocol TS 38.321, the DCCH is mapped to the Uplink Shared Channel (UL-SCH). Protocol TS 38.212 shows that the UL-SCH is carried at the physical layer by the Physical Uplink Shared Channel (PUSCH). Protocols TR 38.822 / TS 38.331 indicate that the repetition capability of the PUSCH requires user reporting. Therefore, when scheduling the transmission of Msg5, the network side can only use the Downlink Control Information (DCI) in DCI format 0_0 for scheduling. The Cyclic Redundancy Check (CRC) of this DCI is scrambled using the Cell-Radio Network Temporary Identifier (C-RNTI). According to the current protocol TS38.214, DCI 0_0 with CRC scrambled by C-RNTI, which serves as a dynamic indicator for DCI, cannot schedule repeated PUSCH transmissions. Therefore, the current protocol does not support repeated PUSCH transmissions carrying Msg5. That is, although UE 10 completes random access, network 20 cannot receive the RRCSetupComplete message, potentially causing problems with RRC connection establishment. Summary of the Invention

[0005] A brief overview of this disclosure is given below to provide a basic understanding of some aspects of it. However, it should be understood that this overview is not an exhaustive summary of this disclosure. It is not intended to identify key or essential parts of this disclosure, nor is it intended to limit the scope of this disclosure. Its purpose is merely to present certain concepts of this disclosure in a simplified form as a prelude to the more detailed description that follows.

[0006] According to a first aspect of this disclosure, a method for retransmitting information repeatedly by a user terminal (UE) is provided, comprising: the UE performing repeated transmission of a Physical Uplink Shared Channel (PUSCH), wherein the PUSCH is scheduled by a Downlink Control Information (DCI) in DCI format 0_0, and the Cyclic Redundancy Check (CRC) of the DCI is scrambled by a Cell Radio Network Temporary Identifier (C-RNTI), wherein the number of repeated transmissions of the PUSCH is determined based on the DCI indication or based on the number of repeated transmissions of Msg3 during the random access process.

[0007] According to a second aspect of this disclosure, a user terminal (UE) device is provided, including a processor; and a memory storing computer-executable instructions that, when executed by the processor, cause the processor to implement the information repetition method as described in the first aspect.

[0008] According to a third aspect of this disclosure, a non-transitory computer-readable storage medium is provided, the non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to implement the information retransmission method as described above.

[0009] According to a fourth aspect of this disclosure, a computer program product is provided, including computer-executable instructions that, when executed by a processor, cause the processor to implement the information repetition method as described above.

[0010] The above overview is provided to summarize some exemplary embodiments to provide a basic understanding of the aspects of the subject matter described herein. Therefore, the features described above are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, taken in conjunction with the accompanying drawings. Attached Figure Description

[0011] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The accompanying drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. The above and other objects and advantages of this disclosure will be further described below with reference to specific embodiments and the accompanying drawings. In the drawings, the same or corresponding technical features or components will be represented by the same or corresponding reference numerals.

[0012] Figure 1 A schematic diagram of the signaling flow during a typical random access procedure is shown.

[0013] Figure 2 A flowchart of an information retransmission method according to an embodiment of the present disclosure is shown;

[0014] Figure 3 A schematic block diagram is shown illustrating the implementation of a UE request for repeated PUSCH transmission in an information retransmission method according to an embodiment of the present disclosure.

[0015] Figure 4 A schematic diagram of the structure of a user terminal device for implementing an information retransmission method according to an embodiment of the present disclosure is shown;

[0016] Figure 5 An exemplary configuration diagram of a computing device according to an embodiment of the present disclosure is shown.

[0017] It should be understood that the accompanying drawings and their detailed description are not intended to limit the embodiments to the specific forms disclosed, but rather are intended to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the claims. Detailed Implementation

[0018] Exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings. For clarity and brevity, not all features of the embodiments are described in the specification. However, it should be understood that many implementation-specific settings must be made in carrying out the embodiments to achieve the developer's specific goals, such as complying with constraints related to the device and business, and these constraints may vary depending on the implementation. Furthermore, it should be understood that while development work can be very complex and time-consuming, such development work is merely a routine task for those skilled in the art who benefit from the present disclosure.

[0019] It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0020] Those skilled in the art will understand that the terms "first," "second," etc., in the embodiments of this disclosure are only used to distinguish different steps, devices, or modules, and do not represent any specific technical meaning, nor do they indicate a necessary logical order between them.

[0021] It should also be understood that in the embodiments disclosed herein, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0022] It should also be understood that any component, data or structure mentioned in the embodiments of this disclosure can generally be understood as one or more unless expressly defined or given to the contrary in the context.

[0023] Furthermore, the term "and / or" in this disclosure is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this disclosure generally indicates that the preceding and following related objects have an "or" relationship.

[0024] It should also be understood that the description of the various embodiments in this disclosure emphasizes the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described in detail.

[0025] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0026] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0027] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0028] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0029] Furthermore, to avoid obscuring this disclosure with unnecessary detail, only processing steps and / or apparatus structures closely related to at least the solutions according to this disclosure are shown in the accompanying drawings, while other details not closely related to this disclosure are omitted. It should also be noted that similar reference numerals and letters in the drawings indicate similar items, and therefore once an item is defined in one drawing, it need not be discussed again in subsequent drawings.

[0030] The embodiments disclosed herein can be applied to electronic devices such as terminal devices, computer systems, and servers, and can operate together with a wide range of other general-purpose or special-purpose computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments, and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, and servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments including any of the above systems, etc.

[0031] Electronic devices such as terminal devices, computer systems, and servers can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Typically, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer systems / servers can be implemented in distributed cloud computing environments, where tasks are executed by remote processing devices linked through communication networks. In distributed cloud computing environments, program modules can reside on local or remote computing system storage media, including storage devices.

[0032] A User Equipment (UE), also known as a terminal device, is a device with wireless transceiver capabilities that can communicate with one or more core networks (CNs) via access network devices in a Radio Access Network (RAN). It can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; on water, such as on ships; and in the air, such as on airplanes, balloons, or satellites. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes, etc.

[0033] After successful random access in mobile communication, the UE needs to send Msg5 (RRCSetupComplete) to the network. This message is scheduled by DCI 0_0 with CRC scrambled by C-RNTI, but currently, repeated transmission of PUSCH scheduled by this DCI is not supported. In other words, even if the user successfully completes the random access process, the network may not receive Msg5, affecting the validity of the RRC connection establishment.

[0034] To address this issue, this disclosure proposes a PUSCH retransmission method for carrying RRC connection establishment completion messages, and simultaneously supports flexible configuration of the number of retransmissions. By taking the transmission status of previous uplink signals as a reference, the retransmission number configuration is made more reasonable, thereby maximizing uplink resource utilization efficiency, reducing congestion probability, and improving the success rate of RRC connection establishment.

[0035] Specifically, first refer to Figure 2 The document illustrates a flowchart of an information retransmission method 2000 according to an embodiment of the present disclosure. Specifically, the user terminal (UE) performs PUSCH retransmission, where the PUSCH is scheduled by DCI format 0_0 and the DCI's CRC is scrambled by C-RNTI. Before the random access procedure is completed and communication between the UE and the network side begins, the UE has not yet reported its capability information, and whether Msg5 can be retransmitted is currently unknown. To address this issue, in a non-limiting embodiment, the UE requests retransmission of the Physical Uplink Shared Channel (PUSCH) carrying Msg5 (i.e., the RRCSetupComplete message) in step S201; thus, in step S202, the UE performs PUSCH retransmission according to the number of PUSCH retransmissions configured by the network side.

[0036] Figure 3 A detailed schematic block diagram illustrating the implementation of the UE request for repeated PUSCH transmission in the above-described information retransmission method is shown. Figure 2 Correspondingly, the UE requests repeated transmission of PUSCH in step S301, and determines the number of repeated transmissions of PUSCH in step S302 (including S302-1 or S302-2).

[0037] In some embodiments, the UE requests PUSCH retransmission via one of methods 3001 to 3005. Specifically, method 3001 requests PUSCH retransmission for Msg5 in response to the UE's request for retransmission of Msg3 (i.e., the RRCSetupRequest message), which is the PUSCH scheduled by the uplink grant (ULgrant) of the Random Access Response (RAR). Generally, during random access, the bit payload of Msg5 is larger than that of Msg3, and if Msg3 requires retransmission, Msg5 will also require retransmission. Therefore, the PUSCH retransmission for Msg5 can be determined by referring to the retransmission scenario of Msg3.

[0038] Alternatively, mode 3002 requests a PUSCH retransmission of Msg5 in response to a PRACH retransmission by the UE, wherein the PRACH retransmission is equivalent to a retransmission of the Random Access Preamble message (i.e., Msg1), or a PRACH retransmission with a repetitive preamble. Alternatively, mode 3003 may include conditions that satisfy both 3001 and 3002.

[0039] Alternatively, in mode 3004, in response to the reference signal received power (RSRP) of the downlink reference signal being lower than a first threshold, that is, the UE of the downlink reference signal requests repeated transmission of PUSCH through a separately designated random access channel (RACH) resource. Here, the downlink reference signal is a downlink path loss reference signal, and the first threshold can be configured by RRC.

[0040] Alternatively, in method 3005, a request is made to repeat the PUSCH of Msg5 in response to a specified information carried in the PUSCH of Msg3. Specifically, the specified information may include a request for repeating the PUSCH carried in the Logical Channel Identifier (LCID) of the Medium Access Control Protocol Data Unit (MACPCU) in the PUSCH of Msg3.

[0041] Based on one of the aforementioned methods, the UE requests repeated transmission of the PUSCH in step S301, and can then determine the number of repeated transmissions of the PUSCH based on different indication information. In some embodiments, as shown in step S302-1, the number of repeated transmissions of the PUSCH is indicated by the DCI. Specifically, as shown in mode 3211, the Modulation and Coding Scheme (MCS) field of the DCI indicates the number of repeated transmissions of the PUSCH. More specifically, the first number of bits from the most significant bit of the MCS field indicates the number of repeated transmissions of the PUSCH, while the other bits of the MCS field are used to indicate the MCS index. Generally, the MCS field consists of 5 bits, and the first number can be 1 to 2 bits. It should be understood that using the MCS field of the DCI to indicate the number of repeated transmissions is a reinterpretation of the MCS field, sacrificing the precision of the first number of bits to achieve the function of indicating the number of repeated transmissions. This first number of bits corresponds to a first code point, and the number of repeated transmissions of the PUSCH can be determined based on this first code point.

[0042] Furthermore, the number of PUSCH retransmissions can be configured by a first higher-layer parameter associated with RRC. In a non-limiting embodiment, in response to the first higher-layer parameter not being configured, the number of PUSCH retransmissions is a pre-configured value; that is, when no corresponding restrictions or requirements are imposed on PUSCH retransmissions in the RRC connection, PUSCH retransmissions are performed according to the default number. Alternatively, the value of the PUSCH retransmission count can be configured by a higher-layer parameter, and the configured value can be the number of PUSCH retransmissions, or expressed as the difference between the number of PUSCH retransmissions and the number of Msg3 retransmissions during the random access process.

[0043] In one non-limiting embodiment, the first higher-layer parameter is configured with a value of {1, 2, 4, 8}, and this value represents the number of repeated transmissions. For example, if the MCS field uses 2 bits (starting from the most significant bit) to indicate the number of PUSCH repeated transmissions, then bit 00 determines the number of repeated transmissions as 1, bit 01 determines the number of repeated transmissions as 2, and so on. In another non-limiting embodiment, the first higher-layer parameter is configured with a value of {0, 2, 4, 8}, and this value represents the first difference between the number of repeated transmissions and the number of repeated transmissions of Msg3 by the UE during the random access process, and the number of repeated transmissions of Msg3 by the UE is 2. Taking the two bits starting from the most significant bit of the MCS field that indicate the number of repetitions of PUSCH as an example, bit 00 determines the first difference to be 0, and the number of repetitions is 2+0=2; bit 01 determines the first difference to be 2, and the number of repetitions is 2+2=4; bit 10 determines the first difference to be 4, and the number of repetitions is 2+4=6; and bit 11 determines the first difference to be 8, and the number of repetitions is 2+8=10.

[0044] Accordingly, the second number of bits from the least significant bit in the MCS field indicates the MCS index. The second number of bits from the least significant bit corresponds to the second code point, and the MCS index is determined based on the second code point. Similarly, the value of the MCS index is configured by higher-level parameters, and if the higher-level parameters are not configured, the value of the MCS index is a pre-configured value.

[0045] Additionally or alternatively, as shown in method 3212, another way for DCI to indicate the number of PUSCH retransmissions is to add an operation that enables PUSCH retransmissions from the network side. Specifically, whether the number of PUSCH retransmissions is indicated by DCI is determined based on a second higher-layer parameter associated with RRC. In some embodiments, the second higher-layer parameter is configured by RRC as an enumeration type ENUMERATED, with a value indicating that the PUSCH retransmissions are enabled, determining that the number of PUSCH retransmissions is indicated by DCI. In a non-limiting embodiment, the value of the second higher-layer parameter is enabled. Specifically, when the value of the second higher-layer parameter is enabled, or when the second higher-layer parameter otherwise indicates that PUSCH retransmissions are enabled, the number of PUSCH retransmissions is determined to be indicated by DCI. In this case, reference can be made to the aforementioned method 3211, such as indicating the number of PUSCH retransmissions based on a number of bits from the most significant bit of the MCS field of DCI. On the other hand, when the second higher layer parameter is not configured, the number of PUSCH retransmissions is determined to be 1; or when the second higher layer parameter is a second value used to indicate that PUSCH retransmissions are not enabled on the network side, it is determined that PUSCH retransmissions will not be performed, and in this case, the MCS field of the DCI only indicates the MCS index.

[0046] In other embodiments, as shown in step S302-2, the number of repetitions of the PUSCH is determined based on the number of repetitions of Msg3. Specifically, as shown in mode 3221, the number of repetitions of the PUSCH of Msg5 is equal to the number of repetitions of Msg3; alternatively, the number of repetitions of the PUSCH is equal to the number of repetitions of Msg3 plus a second difference, wherein the second difference can be configured by a third higher-layer parameter.

[0047] Additionally or alternatively, as shown in method 3222, another way to determine the number of PUSCH retransmissions for Msg5 by the number of retransmissions for Msg3 is to add a network-side operation to enable PUSCH retransmission. Specifically, it is determined whether the number of PUSCH retransmissions for Msg5 is determined by the number of retransmissions for Msg3 based on a fourth higher-layer parameter. In some embodiments, the fourth higher-layer parameter is configured by RRC as an enumeration type ENUMERATED, and its value is a first value used to indicate that the PUSCH retransmission is enabled. The number of PUSCH retransmissions is determined by the number of retransmissions for Msg3. In a non-limiting embodiment, the value of the fourth higher-layer parameter is enabled. Specifically, when the value of the fourth higher-layer parameter is enabled, or when the fourth higher-layer parameter otherwise indicates that PUSCH retransmission is enabled, the number of PUSCH retransmissions is determined to be equal to the number of Msg3 retransmissions during the random access process by the UE. In this case, reference can be made to the aforementioned method 3221, such as determining whether the number of PUSCH retransmissions is equal to the number of Msg3 retransmissions or is increased by the number of times the second difference is added. On the other hand, when the fourth higher layer parameter is not configured, the number of PUSCH repeated transmissions is determined to be 1; or when the fourth higher layer parameter is used to indicate that PUSCH repeated transmission is not enabled on the network side, PUSCH repeated transmission is determined not to be performed.

[0048] In some alternative embodiments, the fourth higher-layer parameter is an enumeration type ENUMERATED, whose value can include several integer values ​​representing the difference between the number of PUSCH retransmissions and the number of Msg3 retransmissions. When the fourth higher-layer parameter is configured on the network side, the number of PUSCH retransmissions is determined to be the sum of the number of Msg3 retransmissions and the third difference. Similarly, when the fourth higher-layer parameter is not configured on the network side, the number of PUSCH retransmissions is determined to be 1; or it is determined that no PUSCH retransmissions will be performed.

[0049] Furthermore, Figure 4 A schematic diagram of the structure of a user terminal device (UE) 4000 for implementing the information retransmission method of this disclosure. The UE 4000 may include a processor 4010 and a memory 4020 storing computer-executable instructions. When executed by the processor 4010, the computer-executable instructions cause the processor 4010 to perform actions such as... Figure 2 The illustrated information repetition transmission method 2000. Generally, processor 4010 may be the central processing unit (CPU) of UE 4000, which may be any type of general-purpose processor, or it may be a processor specifically designed for NTN configuration parameter tuning, such as an application-specific integrated circuit (“ASIC”). Memory 4020 may include various computer-readable media accessible by processor 4010.

[0050] Figure 5 An exemplary configuration diagram of a computing device according to embodiments of the present disclosure is shown. As previously described, similar to Figure 4 The UE that can be used to execute the information repetition transmission method of this disclosure includes a processor 501 and a memory 502 / 503. In some embodiments, the memory 502 may be a read-only memory (ROM), and the memory 503 may be a random access memory (RAM).

[0051] Processor 501 can be any type of processor and may include, but is not limited to, one or more general-purpose processors or special-purpose processors (such as dedicated processing chips). Processor 501 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of this disclosure. Memory 503 may include high-speed RAM and may also include non-volatile memory, such as at least one disk storage device; it may be a memory array or may be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0052] In some embodiments, the memory 503 stores computer-executable instructions that, when executed by the processor 501, enable the processor 501 to perform the information retransmission method as described above.

[0053] Furthermore, the UE may also include an input / output interface 505 connected to the processor 501 via a bus 504, wherein the memories 502 and 503 are connected to the bus 504.

[0054] Bus 504 may include, but is not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0055] In some embodiments, the input / output interface 505 is connected to the following units: an input unit 506 configured with input devices such as a keyboard and mouse for user input of operation commands; an output unit 507 that outputs images of the processing operation screen and processing results to a display device; a storage unit 508 including a hard disk drive for storing programs and various data; and a communication unit 509 including a local area network adapter and performing communication processing via a network such as the Internet. Additionally, a driver 510 is also connected, which reads data from and writes data to the removable storage medium 511. It should be understood that the illustrated UE structure is merely an example; in practice, the UE may include other functional units or components, or be customized according to user needs, etc.

[0056] In addition to the methods and apparatus described above, embodiments of this disclosure may also be computer program products comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps of the methods according to various embodiments of this disclosure as described in the "Exemplary Methods" section above.

[0057] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0058] Furthermore, embodiments of this disclosure may also be computer-readable storage media having computer program instructions stored thereon, which, when executed by a processor, cause the processor to perform the steps in the methods according to various embodiments of this disclosure described in the "Exemplary Methods" section above.

[0059] The aforementioned computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0060] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0061] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For system embodiments, since they largely correspond to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0062] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0063] The methods and apparatus of this disclosure may be implemented in many ways. For example, they may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the methods is for illustrative purposes only, and the steps of the methods of this disclosure are not limited to the order specifically described above unless otherwise specifically stated. Furthermore, in some embodiments, this disclosure may also be implemented as a program recorded on a recording medium, the program including machine-readable instructions for implementing the methods according to this disclosure. Thus, this disclosure also covers recording media storing programs for performing the methods according to this disclosure.

[0064] It should also be noted that in the apparatus, devices, and methods of this disclosure, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions to this disclosure.

[0065] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0066] The above description has been given for illustrative and descriptive purposes. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although several exemplary aspects and embodiments have been discussed above, those skilled in the art will understand that the above embodiments are illustrative only and do not limit the scope of this disclosure. Those skilled in the art will understand that the above embodiments can be combined, modified, or replaced without departing from the scope and spirit of this disclosure.

Claims

1. A method for repeatedly transmitting information in a user terminal (UE), comprising: The UE performs repeated transmissions of the Physical Uplink Shared Channel (PUSCH), which is scheduled by the DCI format 0_0 of the Downlink Control Information (DCI), and the Cyclic Redundancy Check (CRC) of the DCI is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI). The number of times the PUSCH is repeatedly transmitted is determined based on the DCI indication or the number of times message 3 Msg3 is repeatedly transmitted during the random access process.

2. The information retransmission method according to claim 1, wherein the UE requests the PUSCH retransmission in response to one or more of the following conditions: The UE requests Msg3 to be transmitted again; and The UE performs repeated transmissions of the Physical Random Access Channel (PRACH).

3. The information retransmission method according to claim 1, wherein in response to the reference signal received power RSRP of the downlink reference signal being lower than a first threshold, the UE requests the PUSCH retransmission through a designated random access channel RACH resource.

4. The information retransmission method according to claim 1, wherein in response to the UE carrying specified information in the PUSCH of Msg3, the UE requests the PUSCH to be retransmitted.

5. The information retransmission method according to claim 1, wherein the number of retransmissions of the PUSCH based on the DCI includes indication by the modulation and coding scheme (MCS) field of the DCI.

6. The information retransmission method according to claim 5, wherein the number of retransmissions of the PUSCH is indicated by a first number of bits from the most significant bit of the MCS field, and the MCS index is indicated by the other bits of the MCS field or a second number of bits from the least significant bit of the MCS field.

7. The information retransmission method according to claim 6, wherein the first number of bit pairs are applied to a first code point for determining the number of retransmissions of the PUSCH, and the second number of bit pairs are applied to a second code point for determining the MCS index.

8. The information retransmission method according to claim 6 or 7, wherein the number of retransmissions of the PUSCH is configured by a first higher layer parameter. The first high-level parameter is a parameter configured by RRC, and If the first higher-layer parameter is not configured, the number of repeated transmissions of the PUSCH is the pre-configured value.

9. The information retransmission method according to claim 8, wherein the value configured for the first higher layer parameter is the number of retransmissions of the PUSCH, or represents a first difference between the number of retransmissions of the PUSCH and the number of retransmissions of Msg3 of the UE.

10. The information retransmission method according to claim 1, wherein the number of retransmissions of the PUSCH is determined based on a second higher-layer parameter as indicated by the DCI, wherein the second higher-layer parameter is a parameter configured by the RRC.

11. The information retransmission method of claim 10, wherein, in response to a second higher-layer parameter being a first value indicating that the PUSCH retransmission is enabled, the number of retransmissions of the PUSCH is determined by the DCI.

12. The information repetition transmission method according to claim 11, wherein the modulation and coding scheme MCS field of the DCI indicates the number of repetitions of the PUSCH by a first number of bits starting from the most significant bit.

13. The information retransmission method according to claim 10, wherein in response to the second higher layer parameter not being configured, the number of retransmissions of the PUSCH is determined to be 1.

14. The information retransmission method of claim 10, wherein in response to a second higher layer parameter being a second value indicating that the PUSCH retransmission is not enabled, it is determined that the PUSCH retransmission is not performed, and the modulation and coding scheme (MCS) field of the DCI only indicates the MCS index.

15. The information retransmission method according to claim 2, wherein the number of retransmissions of PUSCH is determined by the number of retransmissions of Msg3.

16. The information retransmission method according to claim 15, wherein the number of retransmissions of PUSCH is equal to the number of retransmissions of Msg3, or equal to the sum of the number of retransmissions of Msg3 and the second difference configured by the third higher layer parameter.

17. The information retransmission method according to claim 2, wherein the number of retransmissions of the PUSCH is determined based on a fourth higher-layer parameter associated with RRC, and whether the number of retransmissions of Msg3 is determined.

18. The information retransmission method according to claim 17, wherein in response to a fourth higher layer parameter being a first value indicating that the PUSCH retransmission is enabled, the number of retransmissions of the PUSCH is determined to be equal to the number of retransmissions of Msg3.

19. The information retransmission method according to claim 17, wherein in response to the fourth higher layer parameter being the third difference, the number of repetitions of the PUSCH is determined to be equal to the sum of the number of retransmissions of Msg3 and the third difference.

20. The information retransmission method according to claim 17, wherein in response to the fourth higher layer parameter not being configured, the number of retransmissions of the PUSCH is determined to be 1.

21. The information retransmission method of claim 17, wherein in response to a fourth higher layer parameter being a second value indicating that the PUSCH retransmission is not enabled, it is determined that the PUSCH retransmission is not performed.

22. A user terminal (UE) device, comprising: processor; as well as A memory storing computer-executable instructions that, when executed by the processor, cause the processor to implement the information retransmission method as described in any one of claims 1 to 21.

23. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to implement the information retransmission method as described in any one of claims 1 to 21.

24. A computer program product comprising computer-executable instructions that, when executed by a processor, cause the processor to implement the information repetition method as described in any one of claims 1 to 21.

Images