Random access method, device and storage medium

Abstract

The present disclosure relates to a random access method, apparatus, and storage medium. The random access method is applied to a terminal and includes: sending a message A including a physical uplink shared channel, where the message A further includes an early indication for indicating the terminal capabilities; and in response to a transmission failure of the physical uplink shared channel in the message A, re-reporting the corresponding terminal capabilities in the early indication. When there is a transmission failure of the physical uplink shared channel in the message A of the present disclosure, it is convenient for a network device to perform accurate scheduling based on the re-reported terminal capabilities.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular, to a random access method, apparatus, and storage medium. Background Art

[0002] In the related art, in order to support Internet of Things (IoT) services, two major technologies, namely Machine Type Communication (MTC) and Narrow band Internet of thing (NB-IoT), have been proposed. These two major technologies mainly target scenarios with low rate and high latency, such as meter reading, environmental monitoring, etc. Currently, NB-IoT can only support a maximum rate of several hundred k, and MTC can only support a maximum rate of several M. With the continuous development of IoT services, such as the popularization of services like video surveillance, smart home, wearable devices, and industrial sensing monitoring, etc. These services usually require a rate of dozens to 100 M, and at the same time have relatively high requirements for latency. Therefore, it is difficult for the MTC and NB-IoT technologies in the related art to meet the requirements. Thus, a new type of terminal is redesigned in the 5G New Radio (NR) to cover the requirements of mid-range IoT devices. In the current 3GPP standardization, this new type of terminal is called a low-capability terminal, sometimes also referred to as a Reduced capability UE, or a Redcap terminal, or simply NR-lite for short. This Redcap terminal is relative to ordinary terminals.

[0003] The Redcap terminal supports two-step random access (2-step Random Access Channel, 2-step RACH). In 2-step RACH, message A (Msg.A) is transmitted in the first step, and message B (Msg.B) is received in the second step. The Redcap terminal that supports 2-step RACH, in order to enable the network to identify the RedCap terminal type as soon as possible, also supports early indication in 2-step RACH, that is, in Msg.A, it notifies the network in a hidden or explicit manner that the terminal initiating random access is a RedCap terminal. Summary of the Invention

[0004] To overcome the problems existing in the related art, the present disclosure provides a random access method, apparatus, and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a random access method applied to a terminal is provided, including:

[0006] Transmit message A including a Physical Uplink Shared Channel (PUSCH), where the message A further includes an early indication for indicating the terminal capability; in response to the transmission failure of the PUSCH in the message A, re-report the corresponding terminal capability in the early indication.

[0007] In one implementation, the re-reporting the corresponding terminal capability in the early indication includes:

[0008] Transmit message 3, where the message 3 includes the corresponding terminal capability in the early indication.

[0009] In one implementation, the method further includes: determining a condition for allowing the terminal to include the terminal capability in message 3.

[0010] In one implementation, the condition for allowing the terminal to include the terminal capability in message 3 includes at least one of the following:

[0011] The terminal is configured to transmit terminal capability information based on message A of the Physical Uplink Shared Channel; receive first indication information sent by the network device for indicating support for including the terminal capability in message 3; and meet a predefined condition.

[0012] In one implementation, the predefined condition includes one or a combination of the following:

[0013] A low-capability terminal is configured with a separate initial uplink bandwidth part;

[0014] The initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts;

[0015] The bandwidth of the initial uplink bandwidth part configured by a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by a low-capability terminal;

[0016] The non-low-capability terminal and the low-capability terminal are configured with different Physical Uplink Control Channel (PUCCH) feedback resources.

[0017] In one implementation, the method further includes: receiving second indication information sent by the network device, and the second indication information includes an enabled flag bit, and the enabled flag bit enables the terminal to include the terminal capability of the terminal in message 3.

[0018] In one implementation, the transmitting message 3 includes:

[0019] Transmit message 3 based on first configuration information; the first configuration information is different from second configuration information, the first configuration information is used for the reporting of message 3 in the two-step random access procedure, and the second configuration information is used for the reporting of message 3 in the four-step random access procedure.

[0020] In one implementation, the sending of Message 3 includes: sending Message 3 with the terminal capability corresponding to the advance indication carried in the common control channel information field.

[0021] In one implementation, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capability.

[0022] According to a second aspect of the embodiments of the present disclosure, a random access method is provided, which is applied to a network device and includes:

[0023] Receiving Message A including a physical uplink shared channel, where the Message A further includes an advance indication for indicating the terminal capability; in response to the transmission failure of the physical uplink shared channel in the Message A, re-receiving the terminal capability corresponding to the advance indication.

[0024] In one implementation, the re-receiving the terminal capability corresponding to the advance indication includes: receiving Message 3, where the Message 3 includes the terminal capability corresponding to the advance indication.

[0025] In one implementation, the method further includes: determining a condition for allowing the terminal to include the terminal capability in Message 3.

[0026] In one implementation, the condition for allowing the terminal to include the terminal capability in Message 3 includes at least one of the following:

[0027] Configuring to send terminal capability information based on Message A of the physical uplink shared channel; and sending first indication information for indicating support for including the terminal capability in Message 3; and meeting a predefined condition.

[0028] In one implementation, the predefined condition includes one or a combination of the following:

[0029] The low-capability terminal is configured with a separate initial uplink bandwidth part; the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured by the non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by the low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0030] In one implementation, the method further includes: sending second indication information, and the second indication information includes an enabled flag bit, and the enabled flag bit enables to indicate that the terminal is allowed to include the terminal capability in Message 3.

[0031] In one implementation, the receiving of Message 3 includes: receiving Message 3 based on first configuration information; the first configuration information is different from second configuration information, the first configuration information is used for the receiving of Message 3 in a two-step random access procedure, and the second configuration information is used for the receiving of Message 3 in a four-step random access procedure.

[0032] In one implementation, the receiving of Message 3 includes: receiving Message 3 carried in a common control channel information field with the terminal capability corresponding to the advance indication.

[0033] In one implementation, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capability.

[0034] According to a third aspect of the embodiments of the present disclosure, a random access device is provided, including:

[0035] A sending unit, configured to send Message A including a physical uplink shared channel, where the Message A further includes an advance indication for indicating the terminal capability, and in response to a transmission failure of the physical uplink shared channel in the Message A, re-report the terminal capability corresponding to the advance indication.

[0036] In one implementation, the sending unit is configured to: send Message 3, and the Message 3 includes the terminal capability corresponding to the advance indication.

[0037] In one implementation, the random access device further includes a processing unit, and the processing unit is configured to determine a condition for allowing a terminal to include the terminal capability in Message 3.

[0038] In one implementation, the condition for allowing a terminal to include the terminal capability in Message 3 includes at least one of the following:

[0039] The terminal is configured to send terminal capability information based on Message A of the physical uplink shared channel; receives first indication information sent by a network device for indicating support for including the terminal capability in Message 3; and meets a predefined condition.

[0040] In one implementation, the predefined condition includes one or a combination of the following:

[0041] A low-capability terminal is configured with a separate initial uplink bandwidth part; the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured by a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by a low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0042] In one embodiment, the random access device further includes a receiving unit, which is configured to: receive second indication information sent by a network device, and the second indication information includes an enabled flag bit, and the enabled flag bit indicates that the terminal is allowed to include the terminal capability of the terminal in Message 3.

[0043] In one embodiment, the sending unit is configured to: send Message 3 based on first configuration information; the first configuration information is different from second configuration information, the first configuration information is used for reporting of Message 3 in a two-step random access procedure, and the second configuration information is used for reporting of Message 3 in a four-step random access procedure.

[0044] In one embodiment, the sending unit is configured to: send Message 3 in which the common control channel information field carries the corresponding terminal capability in the advance indication.

[0045] In one embodiment, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capability.

[0046] According to a fourth aspect of the embodiments of the present disclosure, a random access device is provided, including:

[0047] A receiving unit, configured to receive Message A including a physical uplink shared channel, and the Message A further includes an advance indication for indicating terminal capability, and in response to a transmission failure of the physical uplink shared channel in the Message A, re-receive the corresponding terminal capability in the advance indication.

[0048] In one embodiment, the receiving unit is configured to receive Message 3, and the Message 3 includes the corresponding terminal capability in the advance indication.

[0049] In one embodiment, the random access device further includes a processing unit, configured to: determine a condition for allowing a terminal to include terminal capability in Message 3.

[0050] In one embodiment, the condition for allowing a terminal to include terminal capability in Message 3 includes at least one of the following:

[0051] Terminal capability information is configured to be sent based on Message A of a physical uplink shared channel; first indication information for indicating support for including terminal capability in Message 3 is sent; and a predefined condition is satisfied.

[0052] In one embodiment, the predefined condition includes one or a combination of the following:

[0053] The low-capability terminal is configured with a separate initial uplink bandwidth portion; the initial uplink bandwidth portion shares random access resources with a plurality of initial uplink bandwidth portions; the bandwidth of the initial uplink bandwidth portion configured by the non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth portion configured by the low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0054] In one implementation, the random access device further includes a sending unit, the sending unit is configured to send second indication information, and the second indication information includes an enabled identification bit, and the enabled identification bit indicates that the terminal is allowed to include the terminal capability in Message 3.

[0055] In one implementation, the receiving unit receives Message 3 based on first configuration information; the first configuration information is different from the second configuration information, the first configuration information is used for receiving Message 3 in the two-step random access process, and the second configuration information is used for receiving Message 3 in the four-step random access process.

[0056] In one implementation, the receiving unit receives Message 3 in which the common control channel information field carries the corresponding terminal capability in the advance indication.

[0057] In one implementation, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capability.

[0058] According to a fifth aspect of the embodiments of the present disclosure, there is provided a random access device, including:

[0059] A processor;

[0060] A memory for storing processor-executable instructions;

[0061] Wherein, the processor is configured to: execute the random access method described in the first aspect or any one of the embodiments of the first aspect.

[0062] According to a sixth aspect of the embodiments of the present disclosure, there is provided a random access device, including:

[0063] A processor; a memory for storing processor-executable instructions;

[0064] Wherein, the processor is configured to: execute the random access method described in the second aspect or any one of the embodiments of the second aspect.

[0065] According to a seventh aspect of the embodiments of the present disclosure, there is provided a storage medium, in which instructions are stored, and when the instructions in the storage medium are executed by a processor of a terminal, the terminal is enabled to execute the random access method described in the first aspect or any one of the embodiments of the first aspect.

[0066] According to an eighth aspect of the embodiments of the present disclosure, there is provided a storage medium storing instructions that, when executed by a processor of a network device, enable the network device to perform the random access method described in the second aspect or any one of the implementation manners of the second aspect.

[0067] The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects: In the case where message A including an early indication of the terminal capability fails to be sent, the terminal capability included in the early indication is reported again, so that the network device can perform accurate scheduling based on the re-reported terminal capability.

[0068] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present disclosure and used together with the specification to explain the principles of the present disclosure.

[0070] Figure 1 is a schematic diagram of a wireless communication system shown according to an exemplary embodiment.

[0071] Figure 2 is a schematic diagram of a four-step random access process shown according to an exemplary embodiment.

[0072] Figure 3 is a schematic diagram of a two-step random access process shown according to an exemplary embodiment.

[0073] Figure 4 is a flowchart of a random access method shown according to an exemplary embodiment.

[0074] Figure 5 is a flowchart of a random access method shown according to an exemplary embodiment.

[0075] Figure 6 is a flowchart of a random access method shown according to an exemplary embodiment.

[0076] Figure 7 is a flowchart of a random access method shown according to an exemplary embodiment.

[0077] Figure 8 is a flowchart of a random access method shown according to an exemplary embodiment.

[0078] Figure 9 is a flowchart of a random access method shown according to an exemplary embodiment.

[0079] Figure 10 It is a block diagram of a random access device shown according to an exemplary embodiment.

[0080] Figure 11 It is a block diagram of a random access device shown according to an exemplary embodiment.

[0081] Figure 12 It is a block diagram of a device for random access shown according to an exemplary embodiment.

[0082] Figure 13 It is a block diagram of a device for random access shown according to an exemplary embodiment. Detailed implementation manners

[0083] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present disclosure.

[0084] The present disclosure provides a random access method, which can be applied to Figure 1 the wireless communication system shown, such as Figure 1 shown, the terminal accesses the network through network devices such as base stations, and the network devices and the core network complete the backhaul and forward transmission of data to perform various communication services.

[0085] It can be understood that a wireless communication system is a network that provides wireless communication functions. The wireless communication system can adopt different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single Carrier FDMA (SC-FDMA), Carrier Sense Multiple Access with Collision Avoidance. According to factors such as the capacity, rate, and latency of different networks, the network can be divided into 2G (generation) networks, 3G networks, 4G networks, or future evolved networks, such as 5G networks. 5G networks can also be referred to as New Radio (NR). For the convenience of description, the present disclosure sometimes abbreviates the wireless communication network as a network or a system. In the present disclosure, the network may include a Radio Access Network (RAN) and a Core Network (CN). The network includes network devices, which may be, for example, radio access network nodes, core network devices, etc. Among them, the radio access network node can also be called a base station. The network can provide network services for terminals through network devices. Different operators can provide different network services for terminals, or it can be understood that different operators correspond to different operator networks.

[0086] A terminal, which can also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and / or data connectivity to users. For example, the terminal can be a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminals are: smartphones, Pocket Personal Computers (PPCs), palmtop computers, Personal Digital Assistants (PDAs), laptop computers, tablet computers, wearable devices, or vehicle-mounted devices, etc.

[0087] When the terminal is preparing to access the network, it needs to complete random access. In related technologies, four-step random access and two-step random access (2-step RACH) are introduced. Figure 2 A schematic diagram of a four-step random access process is shown. Refer to Figure 4 As shown, the UE sends a contention-based PRACH preamble (Random Access Preamble), also known as Message 1 (Msg1). After detecting the preamble, the network device sends an RAR, also known as Message 2 (Msg2). The RAR includes the detected preamble ID, timing advance command, temporary cell radio network identifier (Cell Radio Network Temporary Identifier, C-RNTI) (TC-RNTI), and uplink grant scheduling for PUSCH transmission from the terminal, and performs scheduled transmission (ScheduledTransmission), which is called Msg3. The terminal sends Message 3 (Msg3) in response to the RAR including the identifier (ID) for contention resolution. When Msg3 is received, the network device sends a contention resolution message (ContentionResoluntion), also known as Message 4 (Msg4), using the contention resolution ID. The terminal receives Msg4, and if it finds its contention resolution ID, it will send an acknowledgement on the PUCCH, thus completing the four-step random access process.

[0088] The four-step random access process requires two round-trip cycles between the terminal and the network device, which not only increases the latency but also generates additional control signaling overhead. The motivation for 2-step RACH is to reduce latency and control signaling overhead by having a single round-trip cycle between the terminal and the network device. This is achieved by combining the preamble (Msg1) and the scheduled PUSCH transmission (Msg3) into a single message from the terminal, called Message A (MsgA). Then, by combining the random access response (Msg2) and the contention resolution message (Msg4) into a single message from the network device to the terminal, called Message B (MsgB). Figure 3 A schematic diagram of a 2-step RACH process is shown. In addition, for unlicensed spectrum, 2-step RACH can reduce the number of messages sent from the terminal and the network device, and reduce the number of listen before talk (LBT) attempts.

[0089] MsgA consists of a PRACH preamble and a PUSCH transmission, which are respectively referred to as MsgA-PRACH and MsgA-PUSCH. The MsgA-PRACH preamble is independent of the four-step RACH preamble, but can be transmitted in the same PRACH occasion (RO) as the four-step RACH preamble, or in a separate RO. The PUSCH transmission is organized into PUSCH occasions (POs) that span multiple symbols and physical resource blocks (PRBs), with an optional guard period and a guard band between consecutive paging occasions. Each PO consists of multiple DMRS ports and DMRS sequences, and each DMRS port / DMRS sequence pair is called a PUSCH resource unit (PRU). The 2-step RACH supports at least one-to-one and many-to-one mappings between the preamble and the PRU.

[0090] After the terminal sends MsgA, the terminal will obtain the random access response (MsgB) sent by the network device. Based on the result of the network device's detection and parsing of MsgA, there are the following three possible scenarios:

[0091] 1. The network device does not detect MsgA PRACH --> no response is sent back to the terminal --> the terminal retransmits MsgA or returns from Msg1 transmission to the four-step RACH.

[0092] 2. The network device detects the MsgA preamble but fails to successfully decode MsgA PUSCH --> the network device sends back a fallback RAR to the terminal with an uplink grant for a fast (random access preamble ID) and retransmission of MsgA PUSCH --> after receiving the fallback RAR, the terminal returns to the four-step RACH by sending Msg3 (retransmission of MsgA PUSCH).

[0093] 3. The network device detects MsgA and successfully decodes MsgA PUSCH --> the network device sends back a contention resolution ID to the terminal indicating successful reception of MsgA --> the two-step RACH process is successfully completed.

[0094] As described above, MsgB consists of a random access response and a contention resolution message. The random access response is sent when the network device detects a preamble but fails to successfully decode the corresponding PUSCH transmission. The contention resolution message is sent after the network device successfully decodes the PUSCH transmission. MsgB can include a fallback indication, a fallback RAR, or a success RAR. A single MsgB can include the winners of one or more terminals. The fallback RAR includes a random access preamble ID (RAPID): an uplink grant for retransmitting the MsgA PUSCH payload and a time-advance command. The success RAR consists of at least a contention resolution ID, a C-RNTI, and a Timing Advance (TA) command.

[0095] A new type of terminal designed in 5G NR: a low-capability terminal. The low-capability terminal is sometimes also referred to as a Reduced-capability UE, or a Redcap terminal, or simply an NR-lite. In the embodiments of the present disclosure, this new terminal is referred to as a Redcap terminal. The RedCap terminal supports 2-step RACH. At the same time, in order to enable the network device to quickly identify the type of the terminal as a RedCap terminal type, it also supports an early indication of the terminal capabilities in 2-step RACH. That is, in Msg.A, the terminal initiating random access is notified to the network in an implicit or explicit manner as a RedCap terminal.

[0096] Currently, MsgA PRACH and Msg.A PUSCH are included in the uplink information of 2-step RACH, and early indication based on these two pieces of information is under discussion. When early indication is based on Msg.A PUSCH, there may be a situation where the network device correctly detects Msg.A PRACH but fails to correctly demodulate Msg.A PUSCH. In the traditional method, the network device transmits a fallback RAR for the scheduling of Msg.3. The terminal can further transmit Msg.3 according to the network indication, and then the network device schedules Msg.4. However, RedCap terminals and non-RedCap terminals may have different PUCCH transmission methods and transmission positions. Therefore, when the terminal is configured with early indication based on Msg.A PUSCH, in the case of a failure in the Msg.A PUSCH transmission, how to enable the network device to accurately know the terminal type and perform accurate scheduling of the PUCCH is a problem that needs to be solved.

[0097] An embodiment of the present disclosure provides a random access method. When the terminal is configured with an early indication based on Msg.A PUSCH, if the transmission of Msg.A PUSCH fails, the terminal capabilities indicated in the early indication are reported again so that the network device can accurately know the terminal type.

[0098] Figure 4 is a flowchart of a random access method shown according to an exemplary embodiment. As Figure 4 shown, the random access method is used in a terminal and includes the following steps.

[0099] In step S11, a message A including PUSCH is sent, and the message A further includes an early indication for indicating terminal capabilities.

[0100] In an embodiment of the present disclosure, step S11 can be understood as the first step of 2-step RACH by the terminal based on the early indication of Msg.A PUSCH.

[0101] In step S12, in response to the failure of PUSCH transmission in message A, the corresponding terminal capabilities in the early indication are reported again.

[0102] The failure of PUSCH transmission in message A in an embodiment of the present disclosure can be understood as that when the terminal performs an early indication based on msg.A PUSCH, the network device correctly detects Msg.A PRACH but cannot correctly demodulate Msg.A PUSCH. Among them, the terminal can determine the failure of PUSCH transmission in message A based on fallback RAR.

[0103] Among them, it can be understood that the terminal capabilities involved in an embodiment of the present disclosure can be one or more of the communication capabilities that can determine the terminal type, such as the transceiver bandwidth, the number of transceiver antennas, the maximum number of bits of the transport block, and the processing time delay.

[0104] Furthermore, it can be understood that the terminal capabilities involved in an embodiment of the present disclosure can also be the terminal type. Those skilled in the art should understand the consistency of its meaning.

[0105] Furthermore, the terminal capabilities or terminal types involved in an embodiment of the present disclosure can include a first type of terminal and a second type of terminal.

[0106] In the embodiments of the present disclosure, the first type of terminal and the second type of terminal may have different capabilities. The different capabilities of the terminal may be one or more of the transceiver bandwidth, the number of transceiver antennas, the maximum number of bits of the transport block, and the processing time delay. For example, in one example, the first type of terminal may be a general terminal (non-Redcap terminal), and the second type of terminal may be a Redcap terminal.

[0107] In the related art, the terminal may transmit Message 3 based on fallbackRAR so that the network device schedules the transmission of Message 4 for PUCCH.

[0108] In one implementation, in the embodiments of the present disclosure, when the terminal determines that the PUSCH transmission in Message A fails, it may re-report the corresponding terminal capabilities in the early indication based on Message 3.

[0109] Figure 5 It is a flowchart of a random access method shown according to an exemplary embodiment. As Figure 5 shown, the random access method is used in a terminal and includes the following steps.

[0110] In step S21, send Message A including PUSCH, and Message A further includes an early indication for indicating the terminal capabilities.

[0111] In step S22, in response to the failure of PUSCH transmission in Message A, send Message 3, and Message 3 includes the corresponding terminal capabilities in the early indication.

[0112] In the embodiments of the present disclosure, when the terminal is configured with an early indication based on Msg.A PUSCH and supports the failure of Msg.A PUSCH transmission, and it is required that the terminal can continue to transmit Msg.3, report the terminal type or terminal capabilities in Msg.3.

[0113] In the embodiments of the present disclosure, when the terminal reports the terminal capabilities in Message 3, it is necessary to determine the conditions that allow the terminal to include the terminal capabilities in Message 3.

[0114] In Mode 1, when the terminal is configured to send terminal capability information in Message A based on PUSCH, it may be determined that the condition for allowing the terminal to include the terminal capabilities in Message 3 is met. In one example, the RedCap terminal is configured with an early indication based on Msg.A PUSCH, and the terminal is default allowed to re-report the terminal capabilities in Message 3. The terminal default puts the terminal capability information in Msg.3. It can also be understood that the terminal default determines that the network also supports the reporting of terminal capabilities based on Msg.3.

[0115] In Method 2, based on the configuration information of the network device, the conditions for allowing the terminal to include the terminal capabilities in Message 3 can be determined. For example, the network device may send indication information, hereinafter referred to as the first indication information. The first indication signaling may be, for example, broadcast signaling. The network device defines in the first indication information an information field for indicating whether to support reporting the terminal capabilities in Msg.3. The network device sends the first indication information to the terminal to indicate whether to allow the terminal to report the terminal capabilities in Msg.3. After receiving the first indication information sent by the network device for indicating support for including the terminal capabilities in Message 3, the terminal determines that the conditions for allowing the terminal to include the terminal capabilities in Message 3 are met.

[0116] In Method 3, based on predefined conditions, the conditions for allowing the terminal to include the terminal capabilities in Message 3 can be determined.

[0117] In one implementation, the predefined conditions include one or a combination of the following:

[0118] The low-capability terminal is configured with a separate initial uplink bandwidth part (initial UL BWP); the initial uplink bandwidth part shares random access resources with a plurality of legacy initial UL BWPs; the Non-RedCap's Initial UL BWP is greater than the bandwidth of the initial uplink bandwidth part of the RedCap terminal, such as the maximum UE BWP; the RedCap terminal and the Non-RedCap terminal are configured with different PUCCH feedback resources.

[0119] In the embodiments of the present disclosure, the terminal may determine, based on one or more of Method 1, Method 2, and Method 3, the conditions for allowing the terminal capabilities to be reported again in Msg.3.

[0120] In the random access method provided by the embodiments of the present disclosure, when the terminal determines that one or more of Method 1, Method 2, and Method 3 are satisfied, the terminal may send Message 3 including the terminal capabilities, so that when it is determined that the PUSCH transmission in Message A fails, the corresponding terminal capabilities in the early indication are reported again based on Message 3. This method can also be understood as that the terminal defaults to enabling the early indication based on Msg.3 as long as one or more of the above Method 1, Method 2, and Method 3 are satisfied. The early indication based on Msg.3 can also be understood as that when the terminal is configured with the early indication based on Msg.A PUSCH and supports the failure of Msg.A PUSCH transmission and requires the terminal to continue transmitting Msg.3, the terminal reports the terminal type or the terminal capabilities again in Msg.3.

[0121] Further, in the embodiments of the present disclosure, it may be indicated through the network whether the terminal re-reports the terminal type or terminal capabilities in Msg.3.

[0122] In one implementation, in the embodiments of the present disclosure, the network device may send indication signaling for enabling or disabling Message 3 (Msg.3 enable / disable) to the terminal, hereinafter referred to as the second indication information. Among them, an identification bit (flag) of Msg.3 enable / disable is set in the second indication information. The enabled identification bit indicates that the terminal is allowed to include the terminal capabilities of the terminal in Message 3. The disabled identification bit indicates that the terminal is not allowed to include the terminal capabilities of the terminal in Message 3.

[0123] Figure 6 is a flowchart of a random access method shown according to an exemplary embodiment, as Figure 6 shown, the random access method is used in a terminal and includes the following steps.

[0124] In step S31, the second indication information sent by the network device is received, and the enabled identification bit is included in the second indication information. The enabled identification bit indicates that the terminal is allowed to include the terminal capabilities of the terminal in Message 3.

[0125] In step S32, in response to the PUSCH transmission failure in Message A, Message 3 is sent, and the corresponding terminal capabilities in the advance indication are included in Message 3.

[0126] In one implementation, for the situations of the above-mentioned Method 1 and Method 3, the terminal is default required to include the terminal capabilities in Message 3, that is, the terminal expects this flag to be in the enabled state. Therefore, the identification bit in the second indication information can be understood to be default set to enabled so that the terminal can re-report the terminal capabilities based on Message 3 according to Method 1 and Method 3.

[0127] In another implementation, for Method 2, since the terminal needs to determine whether to include the terminal capabilities in Message 3 based on the network configuration. Therefore, for Method 2, the flag is in the enabled state, and only when the first indication information indicates that the terminal is allowed to include the terminal capabilities in Message 3, can the terminal re-report the terminal capabilities based on Message 3.

[0128] In an example, the terminal receives the second indication information sent by the network device, and the enabled identification bit is included in the second indication information. The enabled identification bit indicates that the terminal is allowed to include the terminal capabilities of the terminal in Message 3. The terminal receives the first indication information, and the first indication information indicates that the terminal is allowed to report the terminal capabilities in Msg.3. The terminal sends Message 3 and includes the terminal capabilities in Message 3.

[0129] In another example, the terminal receives second indication information sent by a network device, and the second indication information includes an enabled flag bit. The enabled flag bit indicates that the terminal is allowed to include its terminal capabilities in Message 3. The terminal receives first indication information indicating that the terminal is not allowed to report its terminal capabilities in Msg.3, and the terminal does not include its terminal capabilities in Message 3.

[0130] It can be understood that if the flag is in the disabled state, even if the terminal meets the conditions of the above-mentioned Method 1, Method 2, and Method 3, it is not allowed to transmit Msg.3 including the terminal capabilities.

[0131] The random access method provided by the embodiments of the present disclosure can be understood as a method for reporting terminal capabilities based on Msg.3 in 2-step RACH. Among them, the configuration information for reporting terminal capabilities based on Msg.3 in 2-step RACH (hereinafter referred to as the first configuration information) may be different from the configuration information for reporting terminal capabilities based on Msg.3 in 4-step RACH (hereinafter referred to as the second configuration information). For example, in 2-step RACH, the terminal may be allowed to report its terminal capabilities based on Msg.3, but in 4-step RACH, reporting terminal capabilities based on Msg.3 is not supported.

[0132] Figure 7 is a flowchart of a random access method shown according to an exemplary embodiment. The random access method can be executed alone or together with other embodiments. As Figure 7 shown, the random access method is used in a terminal and includes the following steps.

[0133] In step S41, based on the first configuration information, send Message 3 including the corresponding terminal capabilities in the early indication.

[0134] Among them, the first configuration information is different from the second configuration information. The first configuration information is used for reporting Message 3 in the two-step random access process, and the second configuration information is used for reporting Message 3 in the four-step random access process.

[0135] Furthermore, in the embodiments of the present disclosure, in 2-step RACH, when reporting terminal capabilities based on Message 3, the terminal capabilities can be carried by the common control channel (CCCH) of Message 3. That is, the terminal can send Message 3 with the terminal capabilities corresponding to the early indication carried in the CCCH field.

[0136] In one implementation, the CCCH domain carries a logical channel identify (LCID) dedicated to indicating the terminal capabilities. For example, the LCID dedicated to RedCap is carried in the CCCH domain in Msg.3 to report the terminal type.

[0137] For the random access method provided by the embodiments of the present disclosure, when the terminal is configured with an early indication based on Msg.A PUSCH in the 2-step RACH, but the RedCap terminal fails in the early indication, the terminal capabilities or the terminal type are reported again in Msg.3 so that the network device can accurately determine the terminal type and perform accurate transmission scheduling.

[0138] Based on the same concept, the embodiments of the present disclosure also provide a random access method executed by a network device.

[0139] Figure 8 is a flowchart of a random access method shown according to an exemplary embodiment. The random access method can be executed alone or together with other embodiments. As Figure 8 shown, the random access method is used in a network device and includes the following steps.

[0140] In step S51, a message A including a PUSCH is received, and the message A further includes an early indication for indicating the terminal capabilities.

[0141] In step S52, in response to the transmission failure of the PUSCH in the message A, the terminal capabilities corresponding to the early indication are received again.

[0142] In one implementation, receiving the terminal capabilities corresponding to the early indication again includes: receiving a message 3, where the message 3 includes the terminal capabilities corresponding to the early indication.

[0143] In the embodiments of the present disclosure, the network device needs to determine the conditions that allow the terminal to include the terminal capabilities in the message 3. When these conditions are met, the terminal capabilities corresponding to the early indication are received again through the message 3.

[0144] In one implementation, the conditions that allow the terminal to include the terminal capabilities in the message 3 include at least one of the following:

[0145] Configuring the message A based on the PUSCH to send the terminal capability information; and sending a first indication information for indicating support for including the terminal capabilities in the message 3; and meeting a predefined condition.

[0146] In one implementation, the predefined conditions include one or a combination of the following: a low-capability terminal is configured with a separate initial uplink bandwidth part; the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured for a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured for a low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0147] Figure 9 is a flowchart of a random access method shown according to an exemplary embodiment. The random access method can be executed alone or together with other embodiments. As Figure 9 shown, the random access method is used in a network device and includes the following steps.

[0148] In step S61, send second indication information, where the second indication information includes an enabled flag bit. The enabled flag bit indicates that the terminal is allowed to include the terminal capability in message 3, and the disabled flag bit indicates that the terminal is not allowed to include the terminal capability in message 3.

[0149] In one implementation, in the embodiments of the present disclosure, the second indication information sent by the network device includes an enabled flag bit to allow the terminal to include the terminal capability in message 3.

[0150] In one implementation, the random access method provided in the embodiments of the present disclosure can be understood as receiving the terminal capability based on Msg.3 in 2-step RACH. Among them, in 2-step RACH, receive Msg.3 including the terminal capability based on the first configuration information. Among them, the first configuration information is different from the second configuration information. The first configuration information is used for receiving message 3 in 2-step RACH, and the second configuration information is used for receiving message 3 in 4-step RACH.

[0151] Further, in the embodiments of the present disclosure, in 2-step RACH, when re-receiving the terminal capability based on message 3, the terminal capability can be carried in the CCCH domain of message 3. That is, message 3 carried in the CCCH domain has the corresponding terminal capability in the advance indication.

[0152] In one implementation, the CCCH domain carries an LCID dedicated to indicating the terminal capability. For example, receive and obtain the terminal capability or terminal type by carrying the RedCap-specific LCID in the CCCH domain of Msg.3.

[0153] It can be understood that the above-mentioned random access method provided in the embodiments of the present disclosure can be applied to Redcap terminals.

[0154] The random access method provided by the embodiments of the present disclosure, when the terminal is configured with an early indication based on Msg.A PUSCH in 2-step RACH, but in the case of the RedCap terminal failing the early indication, re-receives the terminal capabilities or terminal type in Msg.3, so that the network device can accurately determine the terminal type and perform accurate transmission scheduling.

[0155] It can be understood that the random access method provided by the embodiments of the present disclosure can be applied to the implementation scheme where the terminal and the network device interact to re-report the terminal capabilities based on Message 3.

[0156] It should be noted that those skilled in the art can understand that the various implementation manners / embodiments involved in the embodiments of the present disclosure can be used in conjunction with the foregoing embodiments, or can be used independently. Whether used alone or in conjunction with the foregoing embodiments, their implementation principles are similar. In the embodiments of the present disclosure, some embodiments are described in the implementation manner of being used together. Of course, those skilled in the art can understand that such illustrative examples are not limitations on the embodiments of the present disclosure.

[0157] Based on the same concept, the embodiments of the present disclosure also provide a random access device.

[0158] It can be understood that in order to implement the above functions, the random access device provided by the embodiments of the present disclosure includes the corresponding hardware structures and / or software modules for executing each function. Combining the units and algorithm steps of the examples disclosed in the embodiments of the present disclosure, the embodiments of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the manner of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of the present disclosure.

[0159] Figure 10 is a block diagram of a random access device shown according to an exemplary embodiment. Referring to Figure 10 , the random access device 100 can be provided as the terminal involved in the above embodiment, including a sending unit 101.

[0160] The sending unit 101 is configured to send Message A including PUSCH, and Message A further includes an early indication for indicating the terminal capabilities, and in response to the failure of the PUSCH transmission in Message A, re-report the corresponding terminal capabilities in the early indication.

[0161] In one implementation, the sending unit 101 is configured to: send Message 3, where Message 3 includes the corresponding terminal capabilities in the advance indication.

[0162] In one implementation, the random access device 100 further includes a processing unit 102, and the processing unit 102 is configured to determine the conditions that allow a terminal to include terminal capabilities in Message 3.

[0163] In one implementation, the conditions that allow a terminal to include terminal capabilities in Message 3 include at least one of the following:

[0164] The terminal is configured to send terminal capability information based on PUSCH-based Message A; receives first indication information sent by a network device for indicating support for including terminal capabilities in Message 3; and meets predefined conditions.

[0165] In one implementation, the predefined conditions include one or a combination of the following:

[0166] A low-capability terminal is configured with a separate initial uplink bandwidth part; the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured by a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by a low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0167] In one implementation, the random access device 100 further includes a receiving unit 103, and the receiving unit 103 is configured to: receive second indication information sent by a network device, and the second indication information includes an enabled flag bit, and the enabled flag bit indicates that a terminal is allowed to include the terminal capabilities of the terminal in Message 3.

[0168] In one implementation, the sending unit 101 is configured to: send Message 3 based on first configuration information; the first configuration information is different from the second configuration information, the first configuration information is used for the reporting of Message 3 in the two-step random access process, and the second configuration information is used for the reporting of Message 3 in the four-step random access process.

[0169] In one implementation, the sending unit 101 is configured to: send Message 3 with the corresponding terminal capabilities in the advance indication carried in the CCCH domain.

[0170] In one implementation, the CCCH domain carries an LCID dedicated to indicating terminal capabilities.

[0171] Figure 11 is a block diagram of a random access device shown according to an exemplary embodiment. Refer to Figure 11 , the random access device 200 may be provided as the network device involved in the above embodiment, including a receiving unit 201.

[0172] A receiving unit 201, configured to receive message A including a PUSCH, where message A further includes an advance indication for indicating terminal capabilities, and re-receive the corresponding terminal capabilities in the advance indication in response to a PUSCH transmission failure in message A.

[0173] In one implementation, the receiving unit 201 is configured to receive message 3, where message 3 includes the corresponding terminal capabilities in the advance indication.

[0174] In one implementation, the random access device 200 further includes a processing unit 202, configured to: determine a condition for allowing the terminal to include terminal capabilities in message 3.

[0175] In one implementation, the condition for allowing the terminal to include terminal capabilities in message 3 includes at least one of the following:

[0176] Configured to send terminal capability information based on PUSCH in message A; sent first indication information for indicating support for including terminal capabilities in message 3; and satisfied a predefined condition.

[0177] In one implementation, the predefined condition includes one or a combination of the following:

[0178] The low-capability terminal is configured with a separate initial uplink bandwidth part; the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured for the non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured for the low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different physical uplink control channel feedback resources.

[0179] In one implementation, the random access device 200 further includes a sending unit 203, where the sending unit 203 is configured to send second indication information, and the second indication information includes an enabled flag bit, and the enabled flag bit indicates that the terminal is allowed to include terminal capabilities in message 3.

[0180] In one implementation, the receiving unit 201 receives message 3 based on first configuration information; the first configuration information is different from the second configuration information, the first configuration information is used for receiving message 3 in a two-step random access process, and the second configuration information is used for receiving message 3 in a four-step random access process.

[0181] In one implementation, the receiving unit 201 receives message 3 with the corresponding terminal capabilities in the CCCH domain carried therein.

[0182] In one implementation, the CCCH domain carries an LCID dedicated to indicating terminal capabilities.

[0183] Regarding the device in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0184] Figure 12 FIG. 4 is a block diagram of a device 300 for random access according to an exemplary embodiment. For example, the device 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0185] Referring to Figure 12 , the device 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input / output (I / O) interface 312, a sensor component 314, and a communication component 316.

[0186] The processing component 302 generally controls the overall operation of the device 300, such as operations associated with display, telephone calls, data communication, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 302 may include one or more modules to facilitate the interaction between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate the interaction between the multimedia component 308 and the processing component 302.

[0187] The memory 304 is configured to store various types of data to support the operation of the device 300. Examples of such data include instructions for any application or method operating on the device 300, contact data, phone book data, messages, pictures, videos, etc. The memory 304 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk.

[0188] The power component 306 provides power to various components of the device 300. The power component 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 300.

[0189] The multimedia component 308 includes a screen that provides an output interface between the device 300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operations. In some embodiments, the multimedia component 308 includes a front camera and / or a rear camera. When the device 300 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0190] The audio component 310 is configured to output and / or input audio signals. For example, the audio component 310 includes a microphone (MIC) that is configured to receive external audio signals when the device 300 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 304 or transmitted via the communication component 316. In some embodiments, the audio component 310 further includes a speaker for outputting audio signals.

[0191] The I / O interface 312 provides an interface between the processing component 302 and a peripheral interface module, and the peripheral interface module can be a keyboard, a click wheel, buttons, etc. These buttons can include but are not limited to: a home button, a volume button, a power button, and a lock button.

[0192] The sensor component 314 includes one or more sensors for providing status assessments of various aspects of the device 300. For example, the sensor component 314 can detect the on / off state of the device 300, the relative positioning of components, such as the display and the keypad of the device 300. The sensor component 314 can also detect a change in the position of the device 300 or a component of the device 300, the presence or absence of user contact with the device 300, the orientation or acceleration / deceleration of the device 300, and the temperature change of the device 300. The sensor component 314 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 314 can also include a light sensor, such as a CMOS or a CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 314 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0193] The communication component 316 is configured to facilitate communication between the device 300 and other devices in a wired or wireless manner. The device 300 can access a communication standard-based wireless network, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 316 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0194] In an exemplary embodiment, the device 300 can be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above method.

[0195] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as the memory 304 including instructions, and the above instructions can be executed by the processor 320 of the device 300 to complete the above method. For example, the non-transitory computer-readable storage medium can be a ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0196] Figure 13 is a block diagram of a device 400 for random access shown according to an exemplary embodiment. For example, the device 400 can be provided as a network device. Referring to Figure 13 , the device 400 includes a processing component 422, which further includes one or more processors, and memory resources represented by the memory 432 for storing instructions executable by the processing component 422, such as application programs. The application programs stored in the memory 432 can include one or more modules each corresponding to a set of instructions. In addition, the processing component 422 is configured to execute instructions to perform the above method.

[0197] The device 400 may further include a power component 426 configured to perform power management of the device 400, a wired or wireless network interface 450 configured to connect the device 400 to a network, and an input / output (I / O) interface 458. The device 400 can operate based on an operating system stored in the memory 432, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.

[0198] In an exemplary embodiment, the apparatus 400 is applied to include: a processor; and a memory for storing processor-executable instructions. The processor is configured to execute the above-mentioned random access method.

[0199] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as the memory 432 including instructions. The above instructions can be executed by the processing component 422 of the apparatus 400 to complete the above method. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0200] It can be understood that in the present disclosure, "network" and "system" are sometimes used interchangeably, but those skilled in the art can understand their meanings. Further, it can be understood that in the present disclosure, "a plurality of" means two or more, and other quantifiers are similar thereto. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. The singular forms of "a", "the", and "said" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0201] Further, it can be understood that terms such as "first", "second", etc. are used to describe various information, but this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other and do not represent a specific order or importance. In fact, the expressions such as "first", "second", etc. can be used interchangeably completely. For example, without departing from the scope of the present disclosure, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

[0202] Further, it can be understood that although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood that it is required to perform these operations in the specific order shown or in a serial order, or to perform all the operations shown to obtain the desired result. In a specific environment, multi-tasking and parallel processing may be advantageous.

[0203] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include known common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure.

[0204] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A random access method, characterized in that, applied to a terminal, including: sending a message A including a Physical Uplink Shared Channel (PUSCH) to a network device, where the message A includes PUSCH information, and the PUSCH information includes an advance indication for indicating that the terminal is a terminal with reduced capabilities; receiving a message B sent by the network device, where the message B is used to indicate that the reception of the PUSCH information in the message A fails; determining a condition for allowing the terminal to include terminal capabilities in message 3; sending message 3 to the network device, where the message 3 includes the advance indication; receiving a message 4 sent by the network device, where the message 4 is scheduled by the network device for a terminal with reduced capabilities according to the advance indication; wherein the condition for allowing the terminal to include terminal capabilities in message 3 includes meeting a predefined condition, and the predefined condition includes that a low-capability terminal is configured with a separate initial uplink bandwidth part.

2. The random access method according to claim 1, characterized in that, the condition for allowing the terminal to include terminal capabilities in message 3 includes at least one of the following: the terminal is configured to send terminal capability information based on a message A of the Physical Uplink Shared Channel; receiving a first indication information sent by the network device for indicating support for including terminal capabilities in message 3.

3. The random access method according to claim 1, characterized in that, the predefined condition includes one or a combination of the following: the initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; the bandwidth of the initial uplink bandwidth part configured by a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by a low-capability terminal; the non-low-capability terminal and the low-capability terminal are configured with different Physical Uplink Control Channel (PUCCH) feedback resources.

4. The random access method according to any one of claims 1 to 3, characterized in that, the method further includes: receiving a second indication information sent by the network device, and the second indication information includes an enabled flag bit for confirming that the terminal is allowed to re-report terminal capabilities based on message 3, and the enabled flag bit indicates that the terminal is allowed to include the terminal capabilities of the terminal in message 3.

5. The random access method according to claim 1, characterized in that, sending message 3 includes: sending message 3 based on first configuration information; the first configuration information is different from second configuration information, the first configuration information is used for reporting message 3 in a two-step random access process, and the second configuration information is used for reporting message 3 in a four-step random access process.

6. The random access method according to claim 1, characterized in that, sending message 3 includes: sending message 3 with the terminal capabilities corresponding to the advance indication carried in the common control channel information field.

7. The random access method according to claim 6, characterized in that, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capabilities.

8. A random access method, characterized in that, applied to a network device, including: Receive message A including a Physical Uplink Shared Channel (PUSCH), where message A includes PUSCH information, and the PUSCH information includes an advance indication for indicating that the terminal is a terminal with reduced capabilities; Send message B to the terminal, where message B is used to indicate that the reception of the PUSCH information in message A fails; Determine the conditions for allowing the terminal to include terminal capabilities in message 3; Receive message 3, where message 3 includes the advance indication; Send message 4 to the terminal, where message 4 is scheduled by the network device for the terminal with reduced capabilities according to the advance indication; Wherein, the conditions for allowing the terminal to include terminal capabilities in message 3 include meeting predefined conditions, and the predefined conditions include that a low-capability terminal is configured with a separate initial uplink bandwidth part.

9. The random access method according to claim 8, characterized in that, the conditions for allowing the terminal to include terminal capabilities in message 3 include at least one of the following: configured to send terminal capability information in message A based on the Physical Uplink Shared Channel; and send first indication information for indicating support for including terminal capabilities in message 3.

10. The random access method according to claim 9, characterized in that, the predefined conditions include one or a combination of the following: The initial uplink bandwidth part shares random access resources with a plurality of initial uplink bandwidth parts; The bandwidth of the initial uplink bandwidth part configured by a non-low-capability terminal is greater than the bandwidth of the initial uplink bandwidth part configured by a low-capability terminal; The non-low-capability terminal and the low-capability terminal are configured with different Physical Uplink Control Channel feedback resources.

11. The random access method according to any one of claims 8 to 10, characterized in that, the method further includes: Send second indication information, and the second indication information includes an enabled flag bit, and the enabled flag bit indicates that the terminal is allowed to include terminal capabilities in message 3.

12. The random access method according to claim 8, characterized in that, the receiving message 3 includes: Receiving message 3 based on first configuration information; The first configuration information is different from the second configuration information. The first configuration information is used for receiving message 3 in a two-step random access process, and the second configuration information is used for receiving message 3 in a four-step random access process.

13. The random access method according to claim 8, characterized in that, the receiving message 3 includes: Receiving message 3 in which the common control channel information field carries the corresponding terminal capabilities in the advance indication.

14. The random access method according to claim 13, characterized in that, the common control channel information field carries a logical channel identifier dedicated to indicating the terminal capabilities.

15. A random access device, characterized in that, it includes: A sending unit, configured to send message A including a Physical Uplink Shared Channel to a network device, where message A includes PUSCH information, and the PUSCH information includes an advance indication for indicating that the terminal is a terminal with reduced capabilities; send message 3 to the network device, where message 3 includes the advance indication; A processing unit, configured to: determine a condition for allowing a terminal to include terminal capabilities in Message 3; A receiving unit, configured to receive Message B sent by the network device, where Message B is used to indicate that the PUSCH information reception in Message A fails; Receive Message 4 sent by the network device, where Message 4 is scheduled by the network device for a terminal with reduced capabilities according to the advance indication; Wherein, the condition for allowing the terminal to include terminal capabilities in Message 3 includes meeting a predefined condition, and the predefined condition includes that a low-capability terminal is configured with a separate initial uplink bandwidth part.

16. A random access device, Characterized in that, It includes: A receiving unit, configured to receive Message A including a Physical Uplink Shared Channel (PUSCH), where Message A includes PUSCH information, and the PUSCH information includes an advance indication for indicating that the terminal is a terminal with reduced capabilities; receive Message 3, where Message 3 includes the advance indication; A processing unit, configured to determine a condition for allowing a terminal to include terminal capabilities in Message 3; A sending unit, configured to send Message B to the terminal, where Message B is used to indicate that the PUSCH information reception in Message A fails; Send Message 4 to the terminal, where Message 4 is scheduled by the network device for a terminal with reduced capabilities according to the advance indication; Wherein, the condition for allowing the terminal to include terminal capabilities in Message 3 includes meeting a predefined condition, and the predefined condition includes that a low-capability terminal is configured with a separate initial uplink bandwidth part.

17. A random access device, Characterized in that, It includes: A processor; A memory for storing instructions executable by the processor; Wherein, the processor is configured to: execute the random access method according to any one of claims 1 to 7.

18. A random access device, Characterized in that, It includes: A processor; A memory for storing instructions executable by the processor; Wherein, the processor is configured to: execute the random access method according to any one of claims 8 to 14.

19. A storage medium, Characterized in that, Instructions are stored in the storage medium, and when the instructions in the storage medium are executed by a processor of a terminal, the terminal is enabled to execute the random access method according to any one of claims 1 to 7.

20. A storage medium, Characterized in that, Instructions are stored in the storage medium, and when the instructions in the storage medium are executed by a processor of a network device, the network device is enabled to execute the random access method according to any one of claims 8 to 14.

Images