Contention resolution method of random access procedure, terminal and network side device

Abstract

The application discloses a contention resolution method of a random access process, a terminal and a network side device, and belongs to the technical field of communication. The contention resolution method of the random access process comprises the following steps: a terminal determines a transceiving behavior according to the reception of a message 4 (Msg4); wherein the transceiving behavior comprises at least one of the following: performing message 3 (Msg3) repeated transmission; not performing Msg3 repeated transmission; determining a cell radio network temporary identifier (C-RNTI) or a temporary cell radio network temporary identifier (TC-RNTI) of the terminal.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a contention-based solution for a random access procedure, a terminal, and network-side equipment. Background Technology

[0002] In related technologies, there are contention-based and non-contention-based random access procedures. The contention-based random access procedure, also known as the 4-step Random Access Channel (RACH), involves the terminal first sending message 1Msg1 to the network, containing a pilot sequence preamble. Upon detecting the preamble, the network sends message 2Msg2, containing the corresponding Random Access Response (RAR) message. Upon receiving Msg2, the terminal sends message 3Msg3 according to the RAR's instructions. Upon receiving Msg3, the network sends message 4Msg4, containing a Contention Resolution Identity. Upon receiving Msg4, the terminal completes the 4-step random access process. The network includes uplink (UL) grant information in the RAR to indicate the scheduling information for the Msg3 Physical Uplink Shared Channel (PUSCH), and also includes information such as the Random Access Channel Pilot Sequence Identifier (RACH preamble ID, RAPID), the Temporary Cell Radio Network Temporary Identifier (TC-RNTI), and the Timing Advance (TA). If the network does not receive the Msg3 PUSCH, it can schedule a retransmission of the Msg3 PUSCH in the Physical Downlink Control Channel (PDCCH) scrambled with the TC-RNTI.

[0003] In a contention-based random access procedure, different terminals randomly select a preamble for transmission. This can lead to different terminals selecting the same preamble on the same resource, triggering a contention-based random access procedure. This situation can be understood as a preamble conflict. In this case, different terminals will receive the same RAR (Registered Access Request). At this point, different terminals will transmit the Msg3 PUSCH according to the scheduling information in the RAR UL grant. Since related technologies do not support repeated transmission of the Msg3 PUSCH, the network can only resolve the PUSCH sent by one terminal on a single Msg3 PUSCH scheduling resource. Therefore, the network will include a contention resolution ID in the Msg4 Physical Downlink Shared Channel (PDSCH) that matches the Common Control Channel (CCCH) Service Data Unit (SDU) sent by the terminal in the Msg3 PUSCH. If the match is found, the terminal considers the contention resolution successful and uses the TC-RNTI as its Cell Radio Network Temporary Identity (C-RNTI). If they do not match, the contention resolution is considered unsuccessful. If the contention resolution fails, the terminal will reselect the RACH transmission resource and transmit via the Physical Random Access Channel (PRACH) for the next random access attempt.

[0004] If the terminal supports repeated Msg3 transmissions, and / or the network indicates repeated Msg3 PUSCH transmissions, the terminal will perform repeated PUSCH transmissions at multiple times. This may cause the network to decode multiple Msg3 PUSCHs sent by the terminal, resulting in significant access latency. Therefore, optimizing the relevant random access procedures to reduce terminal access latency is a problem that needs to be addressed. Summary of the Invention

[0005] This application provides a solution to a contention problem in a random access procedure, a terminal, and a network-side device. It can solve the problem of how to optimize the relevant random access procedure to reduce terminal access latency when the terminal supports repeated transmission of Msg3 and / or the network indicates repeated transmission of Msg3 PUSCH.

[0006] Firstly, a contention-based solution for the random access procedure is provided, the method comprising:

[0007] The terminal determines the sending and receiving behavior based on the receipt of message 4Msg4;

[0008] The sending and receiving behavior includes at least one of the following: performing message 3 Msg3 retransmission; not performing Msg3 retransmission; determining the terminal's cell radio network temporary identifier C-RNTI or temporary cell radio network temporary identifier TC-RNTI.

[0009] Secondly, a contention-based solution for the random access procedure is provided, the method comprising:

[0010] The network-side device sends message 4Msg4 to the terminal so that the terminal can determine its sending and receiving behavior based on the receipt of Msg4;

[0011] Msg4 carries at least one of the following: Contention Resolution Identifier (ID); Cell Radio Network Temporary Identifier (C-RNTI); and first indication information.

[0012] The sending and receiving behavior includes at least one of the following: performing message 3 Msg3 retransmission; not performing Msg3 retransmission; determining the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier TC-RNTI.

[0013] Thirdly, a contention resolution apparatus for a random access procedure is provided, the apparatus comprising:

[0014] The first determining unit is used to determine the sending and receiving behavior based on the receipt of message 4Msg4;

[0015] The sending and receiving behavior includes at least one of the following: performing message 3 Msg3 retransmission; not performing Msg3 retransmission; determining the terminal's cell radio network temporary identifier C-RNTI or temporary cell radio network temporary identifier TC-RNTI.

[0016] Fourthly, a contention resolution apparatus for a random access procedure is provided, the apparatus comprising:

[0017] The first sending unit is used to send message 4Msg4 to the terminal so that the terminal can determine its sending and receiving behavior based on the receipt of Msg4.

[0018] Msg4 carries at least one of the following: Contention Resolution Identifier (ID); Cell Radio Network Temporary Identifier (C-RNTI); and first indication information.

[0019] The sending and receiving behavior includes at least one of the following: performing message 3 Msg3 retransmission; not performing Msg3 retransmission; determining the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier TC-RNTI.

[0020] Fifthly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0021] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to determine a receiving behavior based on the receipt of message 4Msg4; wherein the receiving behavior includes at least one of the following: performing message 3Msg3 retransmission; not performing Msg3 retransmission; determining the terminal's cell radio network temporary identifier C-RNTI or temporary cell radio network temporary identifier TC-RNTI.

[0022] In a seventh aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0023] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a message 4Msg4 to a terminal, so that the terminal determines its receiving behavior based on the receipt of the Msg4; wherein the Msg4 carries at least one of the following: a contention resolution identifier ID; a temporary cell radio network identifier C-RNTI; and first indication information; wherein the receiving behavior includes at least one of the following: performing message 3Msg3 retransmission; not performing Msg3 retransmission; and determining the terminal's C-RNTI or temporary cell radio network identifier TC-RNTI.

[0024] In a ninth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of a contention-solving method for a random access procedure as described in the first aspect, or implement the steps of a contention-solving method for a random access procedure as described in the second aspect.

[0025] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run programs or instructions to implement a contention-solving method for a random access procedure as described in the first aspect, or to implement a contention-solving method for a random access procedure as described in the second aspect.

[0026] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to implement the steps of the contention resolution method for the random access procedure as described in the first aspect, or to implement the steps of the contention resolution method for the random access procedure as described in the second aspect.

[0027] In this embodiment, the terminal determines whether to repeat the transmission of Msg3 and / or determines the terminal's C-RNTI or TC-RNTI based on the receipt of message 4Msg4, which can optimize the random access process, reduce access latency, and improve access efficiency. Attached Figure Description

[0028] Figure 1 This is a structural diagram of a wireless communication system applicable to embodiments of this application;

[0029] Figure 2 One of the flowcharts illustrating a contention-based solution for a random access procedure provided in an embodiment of this application;

[0030] Figure 3 A schematic diagram illustrating the stopping of repeated transmissions of Msg3 provided in an embodiment of this application;

[0031] Figure 4 A schematic diagram of a MAC Sub PDU format provided for an embodiment of this application;

[0032] Figure 5 A second schematic flowchart illustrating the contention resolution method for the random access procedure provided in this application embodiment;

[0033] Figure 6 One of the structural schematic diagrams of a contention resolution apparatus for a random access procedure provided in an embodiment of this application;

[0034] Figure 7 A second schematic diagram of the structure of the contention resolution device for the random access procedure provided in an embodiment of this application;

[0035] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0036] Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application;

[0037] Figure 10 This is a schematic diagram of the network-side device provided in an embodiment of this application. Detailed Implementation

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

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

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

[0041] Figure 1This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device, user terminal, or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0042] The following description, in conjunction with the accompanying drawings, details the contention-solving method for the random access procedure provided in this application through some embodiments and application scenarios.

[0043] Figure 2This is one of the flowcharts illustrating a contention-solving method for the random access procedure provided in an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0044] Step 200: The terminal determines the sending and receiving behavior based on the receipt of message 4Msg4;

[0045] The receiving and sending behavior includes at least one of the following:

[0046] Repeatedly transmit message 3Msg3;

[0047] Do not repeat Msg3 transmission;

[0048] Determine the temporary cell radio network identifier (C-RNTI) or temporary cell radio network identifier (TC-RNTI) of the terminal.

[0049] It should be noted that, in the embodiments of this application, Msg4 is the PDSCH and / or PDCCH for transmitting contention resolution messages. Here, the PDCCH is the PDCCH used for scheduling PDSCH, which is scrambled by TC-RNTI using Cyclic Redundancy Check (CRC).

[0050] In an enhanced random access procedure, the network can schedule N (N>=1) repeated transmissions of Msg3 PUSCH. The network may demodulate Msg3 sent by the first UE before the terminal completes the N repeated transmissions. Then the network can send Msg4 to the first UE, and after the first UE demodulates Msg4, the contention is successfully resolved.

[0051] However, since this random access procedure is a four-step process, multiple UEs may simultaneously send the same preamble. This means that after receiving the RAR, multiple UEs can repeatedly transmit Msg3 on the same resources. The network can demodulate multiple Msg3 retransmissions at different times, resulting in significant access latency due to receiving Msg3 messages from multiple UEs at different times. The reasons for this high access latency are as follows: First, while repeated Msg3 transmission improves transmission performance, the multiple transmissions themselves increase access latency. Furthermore, taking two UEs simultaneously sending the same preamble as an example, after receiving Msg4, the first UE successfully resolves the contention, while the second UE fails. For the second UE, according to the existing random access procedure, the second UE will restart the random access procedure from Msg1, leading to higher access latency. Additionally, since the relevant technology does not support stopping the repeated transmission of the remaining Msg3 PUSCH, and the second UE has already failed to resolve the contention, if the repeated transmission resources are unavailable, and the second UE cannot stop the repeated transmission and start a new random access procedure, access latency will also increase. Therefore, embodiments of this application provide a solution to the competition problem in the random access procedure and optimize the relevant random access process.

[0052] Optionally, the terminal determines whether contention resolution was successful based on the reception of Msg4, and then determines the sending and receiving behavior. This sending and receiving behavior includes whether to perform a repeated transmission of Msg3, and / or determining the terminal's C-RNTI or TC-RNTI.

[0053] It should be noted that in this application, Msg3 repeat transmission includes: repeat transmission of PUSCH scheduled by RAR UL grant, or retransmission of PDCCH scheduled by TC-RNTI scrambling.

[0054] For example, if the first UE stops retransmitting Msg3 after successfully resolving the contention, and the second UE fails to resolve the contention, it can continue to retransmit Msg3 PUSCH on the remaining M unfinished transmission resources in the N retransmissions.

[0055] Optionally, for terminals that fail to resolve contention, instead of restarting the random access attempt, the terminal can continue to access the network based on the current random access progress (i.e., based on the information provided by the existing RAR, including scheduling information, TA, TC-RNTI, etc.) until successful access, thus avoiding the access delay caused by retrying random access.

[0056] Optionally, for terminals that fail to resolve contention, the remaining unfinished Msg3 retransmissions can also be stopped, for example, when the network indicates that Msg3 retransmission resources are unavailable, or when the network instructs the terminal to stop the remaining unfinished Msg3 retransmissions, so that the terminal can restart a new random access attempt more quickly.

[0057] Figure 3 This is a schematic diagram illustrating how to stop repeated transmission of Msg3 as provided in an embodiment of this application.

[0058] In related technologies, if the contention is successfully resolved for the first UE, the TC-RNTI received in the RAR will be used as the first UE's C-RNTI. If the second UE needs to continue repeating the transmission of Msg3 and receiving subsequent Msg4, it still needs to listen based on the TC-RNTI, and therefore the TC-RNTI cannot be used as the first UE's C-RNTI. To optimize the above process, in this application, the terminal's sending and receiving behavior further includes: determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

[0059] Optionally, successful contention resolution means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

[0060] Optionally, a contention resolution failure means that the terminal detects that the contention resolution ID contained in the Msg4 PDSCH does not match the CCCH SDU sent by the terminal in the Msg3 PUSCH.

[0061] In this embodiment, the terminal determines whether to repeat the transmission of Msg3 and / or determines the terminal's C-RNTI or TC-RNTI based on the receipt of message 4Msg4, which can optimize the random access process, reduce access latency, and improve access efficiency.

[0062] Optionally, the sending and receiving behavior of the terminal can be predefined.

[0063] If the terminal receives Msg4 and the contention is successfully resolved, the sending and receiving behavior includes at least one of the following:

[0064] Do not continue with unfinished Msg3 retransmissions;

[0065] Clear the buffer for the Hybrid Automatic Retransmission Request (HARQ) corresponding to Msg3;

[0066] Ignore the uplink grant information (UL grant) of the Msg3 Physical Uplink Shared Channel (PUSCH);

[0067] If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior includes:

[0068] Continue the unfinished Msg3 retransmission.

[0069] Optionally, if Msg4 is received before the terminal completes N repeated Msg3 transmissions, and the contention is resolved successfully based on the information carried in Msg4, the terminal performs at least one of the following operations: does not continue the unfinished repeated Msg3 transmissions, clears the HARQ butffer corresponding to Msg3, or ignores the UL grant of Msg3PUSCH.

[0070] Understandably, if the HARQ butffer corresponding to Msg3 is cleared, the terminal cannot continue to perform repeated Msg3 transmissions; if the UL grant for Msg3 PUSCH is ignored, the terminal will not have Msg3 PUSCH transmission resources and will also be unable to continue to perform repeated Msg3 transmissions.

[0071] Optionally, if the terminal receives Msg4 before completing N repeated Msg3 transmissions, and determines that the contention resolution has failed based on the information carried in Msg4, the terminal continues the unfinished repeated Msg3 transmissions. That is, if the terminal determines that the contention resolution has failed based on the received Msg4, it continues the unfinished repeated Msg3 transmissions, thereby avoiding the access delay caused by retrying random access.

[0072] Optionally, the terminal determines the sending and receiving behavior based on network instructions.

[0073] The terminal determines the sending and receiving behavior based on the receipt of message 4Msg4, including:

[0074] If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior is determined according to the first instruction information;

[0075] Wherein, the first indication information is used to indicate at least one of the following:

[0076] Terminate repeated transmission of Msg3;

[0077] Do not terminate repeated transmission of Msg3;

[0078] Msg3 PUSCH transmission resources are available;

[0079] Msg3 PUSCH transmission resources are unavailable;

[0080] Clear the HARQ buffer corresponding to Msg3;

[0081] Do not clear the HARQ buffer corresponding to Msg3;

[0082] C-RNTI or TC-RNTI.

[0083] Optionally, if the terminal receives Msg4 and the contention resolution fails, the terminal determines the sending and receiving behavior according to the instructions of the network.

[0084] The network can instruct the terminal to terminate repeated Msg3 transmissions through the first indication information, so that the terminal can quickly retry random access and improve access efficiency.

[0085] The network can also instruct the terminal to continue the unfinished Msg3 retransmission through the first indication information, so that the terminal can continue to successfully access the network based on the current random access progress and avoid the access delay caused by retrying random access.

[0086] Among them, Msg3 PUSCH transmission resources are the Msg3 PUSCH transmission resources of the terminal after receiving Msg4.

[0087] Terminating Msg3 retransmission can be understood as stopping unfinished Msg3 retransmissions; not terminating Msg3 retransmissions can be understood as continuing unfinished Msg3 retransmissions.

[0088] Optionally, the first indication information can be used to indicate whether the terminal terminates the repeated transmission of Msg3, whether the Msg3PUSCH transmission resource is available, whether the HARQ buffer corresponding to Msg3 is cleared, and / or the terminal's C-RNTI or TC-RNTI.

[0089] Optionally, if the first indication information indicates termination of Msg3 retransmission, unavailability of Msg3 PUSCH transmission resources, and / or clearing of the HARQ buffer corresponding to Msg3, the terminal will not perform Msg3 retransmission.

[0090] Optionally, the terminal performs Msg3 retransmission when the first indication information indicates that Msg3 retransmission is not terminated, Msg3 PUSCH transmission resources are available, and / or the HARQ buffer corresponding to Msg3 is not cleared.

[0091] In this embodiment, the terminal determines whether the contention resolution is successful based on the receipt of message 4Msg4. If the contention resolution is unsuccessful, the terminal determines the sending and receiving behavior based on the first indication information. This can optimize the random access process, reduce access latency, and improve access efficiency.

[0092] Optionally, the first indication information is transmitted via Msg4 or the PDCCH of scheduling Msg4. That is, the first indication information is carried in the Msg4 PDSCH, or in the PDCCH of scheduling Msg4.

[0093] Optionally, if the first indication information is transmitted via the PDCCH of scheduling Msg4, the terminal's physical layer passes the first indication information to the terminal's Media Access Control (MAC) layer. Then, the terminal's MAC layer performs the sending and receiving actions.

[0094] For example, if the first indication information indicates the termination of Msg3 PUSCH retransmission, and this first indication information is used to schedule the TC-RNTI scrambled PDCCH transmission of Msg4, then the UE's MAC layer behavior includes at least one of the following: clearing the HARQ buffer, ignoring the UL grant of Msg3 transmission, or in other words, if the terminal performs these behaviors, then Msg3 PUSCH retransmission will no longer be performed.

[0095] Optionally, when the first indication information is transmitted via a Msg4 MAC Protocol Data Unit (PDU) or a MAC Sub-PDU, the terminal MAC layer transmits the first indication information to the terminal physical layer. Then, the terminal physical layer performs the receiving / sending action.

[0096] For example, the first indication information indicates the termination of Msg3 PUSCH repeated transmission. This first indication information is transmitted through the MAC PDU or MAC sub PDU of Msg4. The terminal MAC layer transmits the first indication information to the terminal physical layer, causing the terminal physical layer to stop the repeated transmission of Msg3 PUSCH.

[0097] Optionally, when the first indication information indicates that the Msg3 repeated transmission is terminated or the Msg3PUSCH transmission resource is unavailable, the sending and receiving behavior includes at least one of the following:

[0098] Stop Msg3 repetitive transmission;

[0099] Clear the HARQ buffer corresponding to Msg3;

[0100] Ignore Msg3 PUSCH's UL grant.

[0101] Optionally, when the first indication information indicates that the Msg3 retransmission is not terminated or that Msg3PUSCH transmission resources are available, the terminal's sending and receiving behavior includes:

[0102] The terminal continues to retransmit Msg3 based on the scheduling information of Msg3.

[0103] The scheduling information for Msg3 is transmitted via RAR UL grant or TC-RNTI scrambled PDCCH.

[0104] Optionally, based on the above embodiments, the method further includes:

[0105] After receiving Msg4 for a first preset time, the terminal executes the sending and receiving behavior.

[0106] Understandably, the terminal determines the sending / receiving behavior based on the reception of Msg4, and executes the sending / receiving behavior after a first preset time. For example, after receiving Msg4 for a first preset time T, the terminal may or may not perform the unfinished retransmission of Msg3.

[0107] The first preset time T can be in milliseconds, the number of symbols, or the number of slots.

[0108] Optionally, the terminal performs the receiving and sending action after receiving the first instruction information for a first preset time.

[0109] In related technologies, if the first terminal successfully resolves the contention issue, it will use the TC-RNTI received in the RAR as its C-RNTI. However, if the second terminal needs to continue retransmitting Msg3 and receiving subsequent Msg4 messages, it still needs to listen based on the TC-RNTI, so this TC-RNTI cannot be used as the first terminal's C-RNTI. One optimization is that for UEs that successfully resolve the contention issue, the C-RNTI is included in Msg4. The first terminal that successfully resolves the contention issue uses this new C-RNTI and discards the TC-RNTI received in the RAR. For the second terminal that fails to resolve the contention issue, it still uses the TC-RNTI to transmit Msg3 and receive subsequent Msg4 messages.

[0110] Optionally, the terminal determines C-RNTI / TC-RNTI based on whether Msg4 contains C-RNTI, and / or based on the first indication information.

[0111] Optionally, if the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes:

[0112] If the Msg4 contains a C-RNTI, the TC-RNTI received in the Random Access Response (RAR) is discarded, and the C-RNTI in the Msg4 is used as the C-RNTI of the terminal.

[0113] Alternatively, if the Msg4 does not contain a C-RNTI, the TC-RNTI received in the RAR may be used as the C-RNTI of the terminal.

[0114] It is understandable that the C-RNTI included in Msg4 is intended for the terminal that successfully resolves the contention. If a terminal receives Msg4 and successfully resolves the contention, and Msg4 contains a C-RNTI, then that C-RNTI is used as the C-RNTI for that successfully resolved terminal. Other terminals that fail to resolve the contention can then continue to use their TC-RNTI to listen to the PDCCH and receive the scheduled Msg4. In this way, both terminals that have successfully resolved the contention and those that have failed can receive Msg4 and successfully resolve the contention.

[0115] Optionally, if the terminal receives Msg4 and the contention resolution fails, the method further includes at least one of the following:

[0116] Continue to use the TC-RNTI received in RAR for PDCCH monitoring;

[0117] Continue running or restart the random access contention resolution timer (ra-Contention Resolution timer).

[0118] Optionally, if the terminal receives Msg4 and the contention resolution fails, and it is determined to continue the unfinished Msg3 retransmission, then the TC-RNTI received in RAR is used to continue listening for PDCCH, and / or the random access contention resolution timer ra-Contention Resolution timer is continued to run or restarted.

[0119] Optionally, if preset conditions are met, the TC-RNTI received in the RAR can continue to be used for PDCCH monitoring, and / or the random access contention resolution timer ra-Contention Resolutiontimer can continue to run or be restarted;

[0120] The preset conditions include at least one of the following:

[0121] Msg4 contains C-RNTI;

[0122] The first instruction message indicates that Msg3 retransmission should not be terminated;

[0123] The first indication message indicates that Msg3 PUSCH transmission resources are available;

[0124] The first instruction indicates that the HARQ buffer corresponding to Msg3 should not be cleared.

[0125] Optionally, if the MAC PDU or MAC Sub PDU received by the terminal contains a C-RNTI, which is a C-RNTI given by the network-side device to other terminals that have successfully resolved the contention, then the terminal determines that the TC-RNTI received in the RAR can still be used.

[0126] Optionally, if the terminal determines to continue the unfinished Msg3 retransmission based on the first indication information, that is, the first indication information indicates at least one of the following: the Msg3 retransmission is not terminated, the Msg3 PUSCH transmission resource is available, and the HARQ buffer corresponding to Msg3 is not cleared, then the terminal continues to use the TC-RNTI received in the RAR.

[0127] Optionally, if the terminal receives Msg4 and the contention resolution fails, and the above-mentioned preset conditions are not met, the terminal discards the TC-RNTI.

[0128] Figure 4 A schematic diagram of a MAC Sub PDU format provided in this application embodiment is shown below. Figure 4 As shown, in addition to the contention resolution ID, Msg4 also includes the terminal's C-RNTI.

[0129] Optionally, the MAC Sub PDU of Msg4 may include timing advance (TA) or transmission power control (TPC) commands, enabling the terminal to update these transmission parameters (such as uplink timing advance, transmit power, etc.) to obtain better uplink transmission performance.

[0130] Optionally, when the first indication information is transmitted via the PDCCH of scheduling Msg4, the first indication information is included in the first information field;

[0131] The first information domain includes at least one of the following: downlink assignment index (DAI), frequency domain resource allocation (FDRA), and modulation and coding scheme (MCS).

[0132] In the above embodiments, the Msg3 retransmission includes: physical uplink shared channel (PUSCH) retransmission scheduled by random access response (RAR UL grant), or retransmission scheduled by PDCCH scrambled by TC-RNTI.

[0133] It should be noted that the terminal behavior in the above embodiments is executed on the premise that the terminal has selected PRACH resources (including PRACH preamble, PRACH occasion, PRACH configuration) for requesting Msg3 repeated transmission. Preferably, it is further required that the terminal will only execute the behavior if the number of Msg3 PUSCH repeated transmissions scheduled by the network is greater than 1.

[0134] Otherwise, if the terminal does not select the aforementioned PRACH resource, or if the network does not schedule a repeat transmission of Msg3, the terminal will still not perform a repeat transmission of Msg3. That is, if Msg4 is successfully received, the terminal will clear the HARQ buffer regardless of whether contention resolution is successful. For terminals that successfully resolve contention, the UE uses the TC-RNTI as the C-RNTI; for terminals that fail to resolve contention, the UE discards the TC-RNTI.

[0135] The contention resolution method for random access provided in this application embodiment clarifies the specific contention resolution information indication method and the corresponding UE behavior. It can enable terminals that fail to resolve the contention to terminate the incomplete Msg3 retransmission in advance, or continue the incomplete Msg3 retransmission, without having to start random access again from PRACH(Msg1), thus reducing access latency.

[0136] Figure 5 The second schematic diagram of the contention resolution method for the random access procedure provided in the embodiments of this application is as follows: Figure 5 As shown, the method includes:

[0137] Step 500: The network-side device sends message 4Msg4 to the terminal so that the terminal can determine its sending and receiving behavior based on the receipt of Msg4.

[0138] Msg4 carries at least one of the following:

[0139] Race resolution identifier ID;

[0140] Temporary Identifier for Cellular Wireless Network (C-RNTI)

[0141] First instruction message;

[0142] The receiving and sending behavior includes at least one of the following:

[0143] Repeatedly transmit message 3Msg3;

[0144] Do not repeat Msg3 transmission;

[0145] Determine the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

[0146] Optionally, the network-side device sends Msg4 to the terminal, so that the terminal can determine whether to repeat the transmission of Msg3 based on the receipt of Msg4.

[0147] Optionally, Msg4 carries at least one of a contention resolution ID, a C-RNTI, and a first indication information.

[0148] Optionally, the contention resolution ID is used by the terminal to determine whether the contention resolution was successful.

[0149] Optionally, the C-RNTI is used as the terminal's C-RNTI when the contention is successfully resolved; and as the basis for the terminal to determine that the TC-RNTI received in the RAR can still be used when the contention is not resolved.

[0150] Optionally, the first indication information is used to indicate whether the terminal should perform Msg3 retransmission.

[0151] In this embodiment, the network-side device sends message 4Msg4 to the terminal. The Msg4 carries at least one of the following: contention resolution identifier ID, cell radio network temporary identifier C-RNTI, and first indication information, so that the terminal can determine whether to perform Msg3 retransmission and / or determine the terminal's C-RNTI or TC-RNTI based on the receipt of the Msg4. This can optimize the terminal's random access process, reduce access latency, and improve access efficiency.

[0152] Optionally, the first indication information is used to indicate at least one of the following:

[0153] Terminate repeated transmission of Msg3;

[0154] Do not terminate repeated transmission of Msg3;

[0155] Msg3 Physical Uplink Shared Channel (PUSCH) transmission resources are available;

[0156] Msg3 PUSCH transmission resources are unavailable;

[0157] Clear the HARQ buffer corresponding to Msg3;

[0158] Do not clear the HARQ buffer corresponding to Msg3;

[0159] C-RNTI or TC-RNTI.

[0160] Optionally, if the first indication information is not carried in Msg4, the method further includes:

[0161] The first indication information is transmitted via the Physical Downlink Control Channel (PDCCH) of Msg4.

[0162] In some alternative embodiments, the first indication information is transmitted via the physical downlink control channel (PDCCH) that schedules Msg4.

[0163] Optionally, if the Msg4 includes a C-RNTI, the C-RNTI is a C-RNTI configured by the network-side device for other terminals that have successfully resolved the contention.

[0164] Optionally, the contention resolution success means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

[0165] Optionally, if the first indication information is transmitted via the physical downlink control channel (PDCCH) that schedules Msg4, the first indication information is included in the first information field.

[0166] The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

[0167] Optionally, the Msg3 retransmission includes: PUSCH retransmission scheduled by the random access response RAR UL grant, or retransmission scheduled by the PDCCH scrambled by TC-RNTI.

[0168] For a better understanding of the embodiments of this application, please refer to the description in the foregoing embodiments with the terminal as the execution subject, which will not be repeated here.

[0169] The contention resolution method for the random access procedure provided in this application embodiment can enable terminals that fail to resolve the contention to terminate the incomplete Msg3 retransmission in advance, or continue the incomplete Msg3 retransmission, without having to start the random access process again from PRACH(Msg1), thereby reducing the latency of terminal access.

[0170] It should be noted that the contention resolution method for the random access procedure provided in this application embodiment can be executed by a contention resolution device for the random access procedure, or by a control module within that device for executing the contention resolution method for the random access procedure. This application embodiment uses the execution of the contention resolution method for the random access procedure by a contention resolution device for the random access procedure as an example to illustrate the contention resolution device for the random access procedure provided in this application embodiment.

[0171] Figure 6 This is one of the structural schematic diagrams of a contention resolution apparatus for a random access procedure provided in an embodiment of this application. For example... Figure 6 As shown, the contention resolution apparatus 600 for the random access procedure includes:

[0172] The first determining unit 610 is used to determine the sending and receiving behavior based on the receipt of message 4Msg4;

[0173] The receiving and sending behavior includes at least one of the following:

[0174] Repeatedly transmit message 3Msg3;

[0175] Do not repeat Msg3 transmission;

[0176] Determine the terminal's temporary cell radio network identifier (C-RNTI) or temporary cell radio network identifier (TC-RNTI).

[0177] In this embodiment, the device determines whether to perform Msg3 retransmission and / or determine the terminal's C-RNTI or TC-RNTI based on the receipt of message 4Msg4, which can optimize the random access process, reduce access latency, and improve access efficiency.

[0178] Optionally, if the terminal receives Msg4 and the contention is successfully resolved, the sending and receiving behavior includes at least one of the following:

[0179] Do not continue with unfinished Msg3 retransmissions;

[0180] Clear the HARQ buffer corresponding to Msg3;

[0181] Ignore the uplink grant information (UL grant) of the Msg3 Physical Uplink Shared Channel (PUSCH);

[0182] If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior includes:

[0183] Continue the unfinished Msg3 retransmission.

[0184] Optionally, the first determining unit 610 is configured to:

[0185] If the terminal receives Msg4 and the contention resolution fails, the receiving / sending behavior is determined according to the first instruction information;

[0186] Wherein, the first indication information is used to indicate at least one of the following:

[0187] Terminate repeated transmission of Msg3;

[0188] Do not terminate repeated transmission of Msg3;

[0189] Msg3 PUSCH transmission resources are available;

[0190] Msg3 PUSCH transmission resources are unavailable;

[0191] Clear the HARQ buffer corresponding to Msg3;

[0192] Do not clear the HARQ buffer corresponding to Msg3;

[0193] C-RNTI or TC-RNTI.

[0194] In this embodiment, the device determines whether contention resolution is successful based on the receipt of message 4Msg4. If contention resolution is unsuccessful, the device determines the sending and receiving behavior based on the first indication information. This can optimize the random access process, reduce access latency, and improve access efficiency.

[0195] Optionally, the first indication information is transmitted via Msg4 or the PDCCH of scheduling Msg4;

[0196] When the first indication information is transmitted via the PDCCH of schedule Msg4, the terminal physical layer transmits the first indication information to the terminal media access control (MAC) layer.

[0197] When the first indication information is transmitted via Msg4's MAC protocol data unit (PDU) or MAC sub-protocol data unit (subPDU), the terminal MAC layer transmits the first indication information to the terminal physical layer.

[0198] Optionally, when the first indication information indicates that the Msg3 repeated transmission is terminated or the Msg3PUSCH transmission resource is unavailable, the sending and receiving behavior includes at least one of the following:

[0199] Stop Msg3 repetitive transmission;

[0200] Clear the HARQ buffer corresponding to Msg3;

[0201] Ignore Msg3 PUSCH's UL grant.

[0202] Optionally, when the first indication information indicates that the Msg3 retransmission is not terminated or that Msg3PUSCH transmission resources are available, the sending and receiving behavior includes:

[0203] The Msg3 retransmission will continue based on the scheduling information of Msg3.

[0204] Optionally, it also includes:

[0205] The first execution unit is used to execute the sending and receiving behavior after receiving the Msg4 for a first preset time.

[0206] Optionally, if the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes:

[0207] If the Msg4 contains a C-RNTI, discard the TC-RNTI received in the Random Access Response (RAR) and use the C-RNTI in the Msg4 as the terminal's C-RNTI; or...

[0208] If the Msg4 does not contain a C-RNTI, the TC-RNTI received in the RAR is used as the C-RNTI of the terminal.

[0209] Optionally, if the terminal receives Msg4 and the contention resolution fails, the system further includes: a second execution unit, configured to:

[0210] Continue to use the TC-RNTI received in RAR for PDCCH monitoring;

[0211] Continue running or restart the random access contention resolution timer (ra-Contention Resolution timer).

[0212] Optionally, the second execution unit is configured to:

[0213] If the preset conditions are met, continue to use the TC-RNTI received in RAR to listen for PDCCH, and / or continue to run or restart the random access contention resolution timer ra-Contention Resolution timer;

[0214] The preset conditions include at least one of the following:

[0215] Msg4 contains C-RNTI;

[0216] The first instruction message indicates that Msg3 retransmission should not be terminated;

[0217] The first indication message indicates that Msg3 PUSCH transmission resources are available;

[0218] The first instruction indicates that the HARQ buffer corresponding to Msg3 should not be cleared.

[0219] Optionally, when the first indication information is transmitted via the PDCCH of scheduling Msg4, the first indication information is included in the first information field;

[0220] The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

[0221] Optionally, the Msg3 retransmission includes: physical uplink shared channel (PUSCH) retransmission scheduled by random access response (RAR UL grant), or retransmission scheduled by TC-RNTI scrambled PDCCH.

[0222] Optionally, the contention resolution success means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

[0223] Optionally, the contention resolution failure means that the terminal detects that the contention resolution ID contained in the Msg4 PDSCH does not match the CCCH SDU sent by the terminal in the Msg3 PUSCH.

[0224] In this embodiment, the specific contention resolution information indication method and the corresponding UE behavior are clearly defined. This allows terminals that fail to resolve contention to terminate the incomplete Msg3 retransmission in advance, or continue the incomplete Msg3 retransmission, without having to start random access from PRACH (Msg1) again, thus reducing access latency.

[0225] The contention resolution device for the random access procedure in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. This device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the specific type of terminal.

[0226] The contention resolution apparatus for the random access procedure provided in this application embodiment can achieve... Figures 2 to 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0227] Figure 7 This is a second schematic diagram of the structure of the contention resolution device for the random access procedure provided in an embodiment of this application. For example... Figure 7 As shown, the contention resolution apparatus 700 for the random access procedure includes:

[0228] The first sending unit 710 is used to send message 4Msg4 to the terminal so that the terminal can determine the sending and receiving behavior of the terminal based on the receipt of Msg4.

[0229] Msg4 carries at least one of the following:

[0230] Race resolution identifier ID;

[0231] Temporary Identifier for Cellular Wireless Network (C-RNTI)

[0232] First instruction message;

[0233] The receiving and sending behavior includes at least one of the following:

[0234] Repeatedly transmit message 3Msg3;

[0235] Do not repeat Msg3 transmission;

[0236] Determine the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

[0237] In this embodiment of the application, by sending message 4Msg4 to the terminal, wherein the Msg4 carries at least one of the following: contention resolution identifier ID, cell radio network temporary identifier C-RNTI, and first indication information, the terminal can determine whether to perform Msg3 retransmission and / or determine the terminal's C-RNTI or TC-RNTI based on the receipt of the Msg4, thereby optimizing the terminal random access process, reducing access latency, and improving access efficiency.

[0238] Optionally, the first indication information is used to indicate at least one of the following:

[0239] Terminate repeated transmission of Msg3;

[0240] Do not terminate repeated transmission of Msg3;

[0241] Msg3 Physical Uplink Shared Channel (PUSCH) transmission resources are available;

[0242] Msg3 PUSCH transmission resources are unavailable;

[0243] Clear the HARQ buffer corresponding to Msg3;

[0244] Do not clear the HARQ buffer corresponding to Msg3;

[0245] C-RNTI or TC-RNTI.

[0246] Optionally, if the first indication information is not carried in Msg4, the method further includes:

[0247] The second transmitting unit is used to transmit the first indication information through the physical downlink control channel (PDCCH) that schedules Msg4.

[0248] Optionally, if the Msg4 includes a C-RNTI, the C-RNTI is a C-RNTI configured by the network-side device for other terminals that have successfully resolved the contention.

[0249] Optionally, the first indication information is included in the first information field;

[0250] The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

[0251] Optionally, the Msg3 retransmission includes: PUSCH retransmission scheduled by the random access response RAR UL grant, or retransmission scheduled by the PDCCH scrambled by TC-RNTI.

[0252] The embodiments of this application enable terminals that fail to resolve contention to terminate the incomplete Msg3 retransmission in advance, or continue the incomplete Msg3 retransmission, without having to start random access again from PRACH(Msg1), thus reducing the latency of terminal access.

[0253] The contention resolution device for the random access procedure in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. This device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the specific type of terminal.

[0254] The contention resolution apparatus for the random access procedure provided in this application embodiment can achieve... Figure 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0255] Optional, such as Figure 8 As shown, this application embodiment also provides a communication device 800, including a processor 801, a memory 802, and a program or instructions stored in the memory 802 and executable on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions, when executed by the processor 801, implement various processes of the above-described random access procedure contention resolution method embodiment, and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions, when executed by the processor 801, implement various processes of the above-described random access procedure contention resolution method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0256] This application embodiment also provides a terminal, including a processor and a communication interface. The processor is used to determine the sending and receiving behavior based on the reception of message 4Msg4; wherein the sending and receiving behavior includes at least one of the following: performing repeated transmission of message 3Msg3; not performing repeated transmission of Msg3; and determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI). This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0257] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0258] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0259] It should be understood that, in this embodiment, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042. The GPU 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0260] In this embodiment, the radio frequency unit 901 receives downlink data from the network-side device and processes it for the processor 910; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0261] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0262] Processor 910 may include one or more processing units; optionally, processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0263] The processor 910 is used to determine the sending and receiving behavior based on the receipt of message 4Msg4;

[0264] The receiving and sending behavior includes at least one of the following:

[0265] Repeatedly transmit message 3Msg3;

[0266] Do not repeat Msg3 transmission;

[0267] Determine the terminal's temporary cell radio network identifier (C-RNTI) or temporary cell radio network identifier (TC-RNTI).

[0268] In this embodiment, the terminal determines whether to repeat the transmission of Msg3 and / or determines the terminal's C-RNTI or TC-RNTI based on the receipt of message 4Msg4, which can optimize the random access process, reduce access latency, and improve access efficiency.

[0269] Optionally, if the terminal receives Msg4 and the contention is successfully resolved, the sending and receiving behavior includes at least one of the following:

[0270] Do not continue with unfinished Msg3 retransmissions;

[0271] Clear the HARQ buffer corresponding to Msg3;

[0272] Ignore the uplink grant information (UL grant) of the Msg3 Physical Uplink Shared Channel (PUSCH);

[0273] If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior includes:

[0274] Continue the unfinished Msg3 retransmission.

[0275] Optionally, the processor 910 is also used for:

[0276] If the terminal receives Msg4 and the contention resolution fails, the receiving / sending behavior is determined according to the first instruction information;

[0277] Wherein, the first indication information is used to indicate at least one of the following:

[0278] Terminate repeated transmission of Msg3;

[0279] Do not terminate repeated transmission of Msg3;

[0280] Msg3 PUSCH transmission resources are available;

[0281] Msg3 PUSCH transmission resources are unavailable;

[0282] Clear the HARQ buffer corresponding to Msg3;

[0283] Do not clear the HARQ buffer corresponding to Msg3;

[0284] C-RNTI or TC-RNTI.

[0285] In this embodiment, the device determines whether contention resolution is successful based on the receipt of message 4Msg4. If contention resolution is unsuccessful, the device determines the sending and receiving behavior based on the first indication information. This can optimize the random access process, reduce access latency, and improve access efficiency.

[0286] Optionally, the first indication information is transmitted via Msg4 or the PDCCH of scheduling Msg4;

[0287] When the first indication information is transmitted via the PDCCH of schedule Msg4, the terminal physical layer transmits the first indication information to the terminal media access control (MAC) layer.

[0288] When the first indication information is transmitted via Msg4's MAC protocol data unit (PDU) or MAC sub-protocol data unit (subPDU), the terminal MAC layer transmits the first indication information to the terminal physical layer.

[0289] Optionally, when the first indication information indicates that the Msg3 repeated transmission is terminated or the Msg3PUSCH transmission resource is unavailable, the sending and receiving behavior includes at least one of the following:

[0290] Stop Msg3 repetitive transmission;

[0291] Clear the HARQ buffer corresponding to Msg3;

[0292] Ignore Msg3 PUSCH's UL grant.

[0293] Optionally, when the first indication information indicates that the Msg3 retransmission is not terminated or that Msg3PUSCH transmission resources are available, the sending and receiving behavior includes:

[0294] The Msg3 retransmission will continue based on the scheduling information of Msg3.

[0295] Optionally, the processor 910 is further configured to perform the receiving and sending behavior after receiving the Msg4 for a first preset time.

[0296] Optionally, if the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes:

[0297] If the Msg4 contains a C-RNTI, discard the TC-RNTI received in the Random Access Response (RAR) and use the C-RNTI in the Msg4 as the terminal's C-RNTI; or...

[0298] If the Msg4 does not contain a C-RNTI, the TC-RNTI received in the RAR is used as the C-RNTI of the terminal.

[0299] Optionally, if the terminal receives Msg4 and the contention resolution fails, the processor 910 is also used to:

[0300] Continue to use the TC-RNTI received in RAR for PDCCH monitoring;

[0301] Continue running or restart the random access contention resolution timer (ra-Contention Resolution timer).

[0302] Optionally, the processor 910 is also used for:

[0303] If the preset conditions are met, continue to use the TC-RNTI received in RAR to listen for PDCCH, and / or continue to run or restart the random access contention resolution timer ra-Contention Resolution timer;

[0304] The preset conditions include at least one of the following:

[0305] Msg4 contains C-RNTI;

[0306] The first instruction message indicates that Msg3 retransmission should not be terminated;

[0307] The first indication message indicates that Msg3 PUSCH transmission resources are available;

[0308] The first instruction indicates that the HARQ buffer corresponding to Msg3 should not be cleared.

[0309] Optionally, when the first indication information is transmitted via the PDCCH of scheduling Msg4, the first indication information is included in the first information field;

[0310] The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

[0311] Optionally, the Msg3 retransmission includes: physical uplink shared channel (PUSCH) retransmission scheduled by random access response (RAR UL grant), or retransmission scheduled by TC-RNTI scrambled PDCCH.

[0312] Optionally, the contention resolution success means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

[0313] Optionally, the contention resolution failure means that the terminal detects that the contention resolution ID contained in the Msg4 PDSCH does not match the CCCH SDU sent by the terminal in the Msg3 PUSCH.

[0314] In this embodiment, the specific contention resolution information indication method and the corresponding UE behavior are clearly defined. This allows terminals that fail to resolve contention to terminate the incomplete Msg3 retransmission in advance, or continue the incomplete Msg3 retransmission, without having to start random access from PRACH (Msg1) again, thus reducing access latency.

[0315] This application embodiment also provides a network-side device, including a processor and a communication interface. The communication interface is used to send message 4Msg4 to a terminal, so that the terminal determines its receiving behavior based on the receipt of Msg4. The Msg4 carries at least one of the following: a contention resolution identifier (ID); a temporary cell radio network identifier (C-RNTI); and first indication information. The receiving behavior includes at least one of the following: performing message 3Msg3 retransmission; not performing Msg3 retransmission; and determining the terminal's C-RNTI or temporary cell radio network identifier (TC-RNTI).

[0316] This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0317] Specifically, embodiments of this application also provide a network-side device. For example... Figure 10 As shown, the network device 1000 includes: an antenna 1001, a radio frequency (RF) device 1002, and a baseband device 1003. The antenna 1001 is connected to the RF device 1002. In the uplink direction, the RF device 1002 receives information through the antenna 1001 and transmits the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be transmitted and sends it to the RF device 1002. The RF device 1002 processes the received information and transmits it through the antenna 1001.

[0318] The aforementioned frequency band processing device can be located in the baseband device 1003. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1003, which includes a processor 1004 and a memory 1005.

[0319] The baseband device 1003 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 10 As shown, one of the chips, for example, is a processor 1004, which is connected to a memory 1005 to call the program in the memory 1005 and execute the network device operation shown in the above method embodiment.

[0320] The baseband device 1003 may also include a network interface 1006 for exchanging information with the radio frequency device 1002, such as a common public radio interface (CPRI).

[0321] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 1005 and executable on processor 1004, wherein processor 1004 calls the instructions or programs in memory 1005 to execute... Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0322] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described random access procedure contention resolution method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0323] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0324] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described random access process contention solution embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0326] 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. Without further limitations, 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. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0327] 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 application, in essence, or the part that contributes to the related technology, can be embodied in the form of a computer 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 a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0328] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A contention-based solution for a random access procedure, characterized in that, include: The terminal determines the sending and receiving behavior based on the receipt of message 4 Msg4; The receiving and sending behavior includes: determining the terminal's temporary cell radio network identifier (C-RNTI) or temporary cell radio network identifier (TC-RNTI); Wherein, when the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes: If the Msg4 contains a C-RNTI, the TC-RNTI received in the Random Access Response (RAR) is discarded, and the C-RNTI in the Msg4 is used as the C-RNTI of the terminal.

2. The contention resolution method for the random access procedure according to claim 1, characterized in that, The receiving and sending behavior also includes at least one of the following: Repeatedly transmit message 3 (Msg3); Msg3 is not retransmitted.

3. The contention resolution method for the random access procedure according to claim 2, characterized in that, If the terminal receives Msg4 and the contention is successfully resolved, the sending and receiving behavior includes at least one of the following: Do not continue with unfinished Msg3 retransmissions; Clear the HARQ buffer corresponding to Msg3; Ignore the uplink grant information (UL grant) of the Physical Uplink Shared Channel (PUSCH) for Msg3; If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior includes: Continue the unfinished Msg3 retransmission.

4. The contention resolution method for the random access procedure according to claim 1, characterized in that, The terminal determines the sending and receiving behavior based on the receipt of message 4 Msg4, including: If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior is determined based on the first instruction information; Wherein, the first indication information is used to indicate at least one of the following: Terminate repeated transmission of Msg3; Do not terminate repeated transmission of Msg3; Msg3 PUSCH transmission resources are available; Msg3 PUSCH transmission resources are unavailable; Clear the HARQ buffer corresponding to Msg3; Do not clear the HARQ buffer corresponding to Msg3; C-RNTI or TC-RNTI.

5. The contention resolution method for the random access procedure according to claim 4, characterized in that, The first indication information is transmitted via Msg4 or the PDCCH of scheduling Msg4; When the first indication information is transmitted via the PDCCH of schedule Msg4, the terminal physical layer transmits the first indication information to the terminal media access control (MAC) layer. When the first indication information is transmitted via Msg4's MAC Protocol Data Unit (PDU) or MAC Sub-Protocol Data Unit (subPDU), the terminal MAC layer transmits the first indication information to the terminal physical layer.

6. The contention resolution method for the random access procedure according to claim 4, characterized in that, When the first indication information indicates that the Msg3 repeated transmission is terminated or the Msg3 PUSCH transmission resource is unavailable, the sending and receiving behavior includes at least one of the following: Stop Msg3 repetitive transmission; Clear the HARQ buffer corresponding to Msg3; Ignore Msg3 PUSCH's UL grant.

7. The contention resolution method for the random access procedure according to claim 4, characterized in that, When the first indication information indicates that Msg3 repeated transmissions will not be terminated or that Msg3 PUSCH transmission resources are available, the sending and receiving behavior includes: The terminal continues to retransmit Msg3 based on the scheduling information of Msg3.

8. The contention resolution method for the random access procedure according to any one of claims 1-7, characterized in that, Also includes: After receiving Msg4 for a first preset time, the terminal executes the sending and receiving behavior.

9. The contention resolution method for the random access procedure according to claim 1, characterized in that, If the terminal receives Msg4 and the race condition is not resolved, the method further includes at least one of the following: Continue to use the TC-RNTI received in RAR for PDCCH monitoring; Continue running or restart the random access contention resolution timer (ra-Contention Resolution timer).

10. The contention resolution method for the random access procedure according to claim 9, characterized in that, If the preset conditions are met, continue to use the TC-RNTI received in RAR to listen for PDCCH, and / or continue to run or restart the random access contention resolution timer ra-Contention Resolution timer; The preset conditions include at least one of the following: Msg4 contains C-RNTI; The first instruction message indicates that Msg3 retransmission should not be terminated; The first indication message indicates that Msg3 PUSCH transmission resources are available; The first instruction indicates that the HARQ buffer corresponding to Msg3 should not be cleared.

11. The contention resolution method for the random access procedure according to claim 5, characterized in that, When the first indication information is transmitted via the PDCCH of schedule Msg4, the first indication information is included in the first information field; The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

12. The contention resolution method for the random access procedure according to any one of claims 2-7, characterized in that, The Msg3 retransmission includes: physical uplink shared channel (PUSCH) retransmission scheduled by random access response (RAR UL grant), or retransmission scheduled by PDCCH scrambled by TC-RNTI.

13. The contention resolution method for the random access procedure according to claim 1 or 3, characterized in that, The contention resolution success means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

14. The contention resolution method for the random access procedure according to claim 3, 4, or 9, characterized in that, The failure to resolve the contention means that the terminal detects a mismatch between the contention resolution ID contained in the Msg4 PDSCH and the CCCH SDU sent by the terminal in the Msg3 PUSCH.

15. A contention-based solution for a random access procedure, characterized in that, include: The network-side device sends message 4 Msg4 to the terminal, so that the terminal can determine its sending and receiving behavior based on the receipt of Msg4; Msg4 carries at least one of the following: Race resolution identifier ID; Temporary Identifier for Cellular Wireless Network (C-RNTI) First instruction message; The receiving and sending behavior includes: determining the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier (TC-RNTI); Wherein, when the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes: If the Msg4 contains a C-RNTI, the TC-RNTI received in the Random Access Response (RAR) is discarded, and the C-RNTI in the Msg4 is used as the C-RNTI of the terminal.

16. The contention resolution method for the random access procedure according to claim 15, characterized in that, The first indication information is used to indicate at least one of the following: Terminate repeated transmission of Msg3; Do not terminate repeated transmission of Msg3; Msg3 Physical Uplink Shared Channel (PUSCH) transmission resources are available; Msg3 PUSCH transmission resources are unavailable; Clear the HARQ buffer corresponding to Msg3; Do not clear the HARQ buffer corresponding to Msg3; C-RNTI or TC-RNTI.

17. The contention resolution method for the random access procedure according to claim 15, characterized in that, If the first indication information is not carried in Msg4, the method further includes: The first indication information is transmitted via the Physical Downlink Control Channel (PDCCH) of Msg4.

18. The contention resolution method for the random access procedure according to claim 17, characterized in that, The first indication information is contained in the first information field; The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

19. The contention resolution method for the random access procedure according to claim 15 or 16, characterized in that, The Msg3 retransmission includes: PUSCH retransmission scheduled by the random access response RAR UL grant, or PDCCH retransmission scrambled by TC-RNTI.

20. A contention resolution apparatus for a random access procedure, characterized in that, include: The first determining unit is used to determine the sending and receiving behavior based on the receipt of message 4 Msg4; The receiving and sending behavior includes: determining the terminal's temporary cell radio network identifier (C-RNTI) or temporary cell radio network identifier (TC-RNTI); Wherein, when the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes: If the Msg4 contains a C-RNTI, the TC-RNTI received in the Random Access Response (RAR) is discarded, and the C-RNTI in the Msg4 is used as the C-RNTI of the terminal.

21. The contention resolution apparatus for a random access procedure according to claim 20, characterized in that, The receiving and sending behavior also includes at least one of the following: Repeatedly transmit message 3 (Msg3); Msg3 is not retransmitted.

22. The contention resolution apparatus for a random access procedure according to claim 20, characterized in that, If the terminal receives Msg4 and the contention is successfully resolved, the sending and receiving behavior includes at least one of the following: Do not continue with unfinished Msg3 retransmissions; Clear the HARQ buffer corresponding to Msg3; Ignore the uplink grant information (UL grant) of the Physical Uplink Shared Channel (PUSCH) for Msg3; If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior includes: Continue the unfinished Msg3 retransmission.

23. The contention resolution apparatus for a random access procedure according to claim 20, characterized in that, The first determining unit is configured to: If the terminal receives Msg4 and the contention resolution fails, the sending and receiving behavior is determined based on the first instruction information; Wherein, the first indication information is used to indicate at least one of the following: Terminate repeated transmission of Msg3; Do not terminate repeated transmission of Msg3; Msg3 PUSCH transmission resources are available; Msg3 PUSCH transmission resources are unavailable; Clear the HARQ buffer corresponding to Msg3; Do not clear the HARQ buffer corresponding to Msg3; C-RNTI or TC-RNTI.

24. The contention resolution apparatus for a random access procedure according to claim 23, characterized in that, The first indication information is transmitted via Msg4 or the PDCCH of scheduling Msg4; When the first indication information is transmitted via the PDCCH of schedule Msg4, the terminal physical layer transmits the first indication information to the terminal media access control (MAC) layer. When the first indication information is transmitted via Msg4's MAC Protocol Data Unit (PDU) or MAC Sub-Protocol Data Unit (subPDU), the terminal MAC layer transmits the first indication information to the terminal physical layer.

25. The contention resolution apparatus for a random access procedure according to claim 23, characterized in that, When the first indication information indicates that the Msg3 repeated transmission is terminated or the Msg3 PUSCH transmission resource is unavailable, the sending and receiving behavior includes at least one of the following: Stop Msg3 repetitive transmission; Clear the HARQ buffer corresponding to Msg3; Ignore Msg3 PUSCH's UL grant.

26. The contention resolution apparatus for a random access procedure according to claim 23, characterized in that, When the first indication information indicates that the Msg3 retransmission is not terminated or that Msg3 PUSCH transmission resources are available, the sending and receiving behavior includes: The Msg3 retransmission will continue based on the scheduling information of Msg3.

27. The contention resolution apparatus for a random access procedure according to any one of claims 20-26, characterized in that, Also includes: The first execution unit is used to execute the receiving and sending behavior after receiving the Msg4 for a first preset time.

28. The contention resolution apparatus for a random access procedure according to claim 20, characterized in that, If the terminal receives Msg4 and the race condition is not resolved, the system also includes: a second execution unit, used for: Continue to use the TC-RNTI received in RAR for PDCCH monitoring; Continue running or restart the random access contention resolution timer (ra-Contention Resolution timer).

29. The contention resolution apparatus for a random access procedure according to claim 28, characterized in that, The second execution unit is used for: If the preset conditions are met, continue to use the TC-RNTI received in RAR to listen for PDCCH, and / or continue to run or restart the random access contention resolution timer ra-Contention Resolution timer; The preset conditions include at least one of the following: Msg4 contains C-RNTI; The first instruction message indicates that Msg3 retransmission should not be terminated; The first indication message indicates that Msg3 PUSCH transmission resources are available; The first instruction indicates that the HARQ buffer corresponding to Msg3 should not be cleared.

30. The contention resolution apparatus for a random access procedure according to claim 24, characterized in that, When the first indication information is transmitted via the PDCCH of schedule Msg4, the first indication information is included in the first information field; The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

31. The contention resolution apparatus for a random access procedure according to any one of claims 21-26, characterized in that, The Msg3 retransmission includes: physical uplink shared channel (PUSCH) retransmission scheduled by random access response (RAR UL grant), or retransmission scheduled by PDCCH scrambled by TC-RNTI.

32. The contention resolution apparatus for a random access procedure according to claim 20 or 22, characterized in that, The contention resolution success means that the terminal detects that the contention resolution identifier ID contained in the Msg4 PDSCH matches the common control channel (CCCH) service data unit (SDU) sent by the terminal in the Msg3 PUSCH.

33. The contention resolution apparatus for a random access procedure according to claim 22, 23 or 28, characterized in that, The failure to resolve the contention means that the terminal detects a mismatch between the contention resolution ID contained in the Msg4 PDSCH and the CCCH SDU sent by the terminal in the Msg3PUSCH.

34. A contention resolution apparatus for a random access procedure, characterized in that, include: The first sending unit is configured to send message 4 Msg4 to the terminal, so that the terminal can determine its sending and receiving behavior based on the receipt of Msg4; Msg4 carries at least one of the following: Race resolution identifier ID; Temporary Identifier for Cellular Wireless Network (C-RNTI) First instruction message; The receiving and issuing behavior includes: Determine the terminal's C-RNTI or Temporary Cell Radio Network Temporary Identifier (TC-RNTI); Wherein, when the terminal receives Msg4 and the contention is successfully resolved, determining the terminal's Cell Radio Network Temporary Identifier (C-RNTI) or Temporary Cell Radio Network Temporary Identifier (TC-RNTI) includes: If the Msg4 contains a C-RNTI, the TC-RNTI received in the Random Access Response (RAR) is discarded, and the C-RNTI in the Msg4 is used as the C-RNTI of the terminal.

35. The contention resolution apparatus for a random access procedure according to claim 34, characterized in that, The first indication information is used to indicate at least one of the following: Terminate repeated transmission of Msg3; Do not terminate repeated transmission of Msg3; Msg3 Physical Uplink Shared Channel (PUSCH) transmission resources are available; Msg3 PUSCH transmission resources are unavailable; Clear the HARQ buffer corresponding to Msg3; Do not clear the HARQ buffer corresponding to Msg3; C-RNTI or TC-RNTI.

36. The contention resolution apparatus for a random access procedure according to claim 34, characterized in that, If the first indication information is not carried in Msg4, the following is also included: The second transmitting unit is used to transmit the first indication information through the physical downlink control channel (PDCCH) that schedules Msg4.

37. The contention resolution apparatus for a random access procedure according to claim 36, characterized in that, The first indication information is contained in the first information field; The first information domain includes at least one of the following: downlink allocation index (DAI), frequency domain resource allocation (FDRA), and modulation and coding strategy (MCS).

38. The contention resolution apparatus for a random access procedure according to claim 34 or 35, characterized in that, The Msg3 retransmission includes: PUSCH retransmission scheduled by the random access response RAR UL grant, or PDCCH retransmission scrambled by TC-RNTI.

39. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the contention resolution method for the random access procedure as described in any one of claims 1 to 14.

40. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the contention resolution method for the random access procedure as described in any one of claims 15 to 19.

41. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the contention resolution method for the random access procedure as described in any one of claims 1 to 14, or implement the steps of the contention resolution method for the random access procedure as described in any one of claims 15 to 19.

Images