Random access method and device, terminal and network side equipment

Abstract

The invention discloses a random access method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the random access method comprises the steps that the terminal receives a target message sent by the network side equipment, and the target message carries physical random access channel transmission opportunity RO scheduling information; the terminal determines a target RO based on the RO scheduling information, and performs random access based on the target RO; wherein the target message comprises at least one of the following items: a random access response message; paging related messages; and public downlink control information (DCI).

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a random access method, apparatus, terminal, and network-side device. Background Art

[0002] In related technologies, during the random access process of a terminal, there is the following random backoff mechanism: If the random access channel is congested, the network side will send a backoff indication of the longest waiting time T to the terminal; if the terminal does not receive a response to the preamble it sent in the random access response reception window or the terminal determines that the random access contention resolution fails, the terminal will, according to the backoff indication, equally probably select a duration Twait between 0 and the longest waiting time T, and after waiting for the duration Twait, the terminal initiates the next random access attempt. However, the above random backoff mechanism may cause the terminal to wait for a long time before initiating the next random access attempt. Summary of the Invention

[0003] Embodiments of this application provide a random access method, apparatus, terminal, and network-side device, which can solve the problem that the terminal waits for a long time before initiating the next random access attempt.

[0004] In a first aspect, a random access method is provided, including:

[0005] The terminal receives a target message sent by a network-side device, and the target message carries physical random access channel transmission opportunity RO scheduling information;

[0006] The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO;

[0007] Wherein, the target message includes at least one of the following:

[0008] Random access response message;

[0009] Paging-related message;

[0010] Common downlink control information DCI.

[0011] In a second aspect, a random access method is provided, including:

[0012] The network-side device sends a target message to the terminal, and the target message carries physical random access channel transmission opportunity RO scheduling information; the RO scheduling information is used for random access;

[0013] Wherein, the target message includes at least one of the following:

[0014] Random access response message;

[0015] Paging-related messages;

[0016] Common DCI.

[0017] In a third aspect, a random access device is provided. The terminal includes the random access device, and the device includes:

[0018] A first receiving module, configured to receive a target message sent by a network-side device, where the target message carries physical random access channel transmission opportunity (RO) scheduling information;

[0019] An access module, configured to determine a target RO based on the RO scheduling information, and perform random access based on the target RO;

[0020] Wherein, the target message includes at least one of the following:

[0021] Random access response message;

[0022] Paging-related messages;

[0023] Common downlink control information (DCI).

[0024] In a fourth aspect, a random access device is provided. The network-side device includes the random access device, and the device includes:

[0025] A sending module, configured to send a target message to a terminal, where the target message carries physical random access channel transmission opportunity (RO) scheduling information; the RO scheduling information is used for random access;

[0026] Wherein, the target message includes at least one of the following:

[0027] Random access response message;

[0028] Paging-related messages;

[0029] Common DCI.

[0030] In a fifth aspect, a terminal is provided. The terminal includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0031] In a sixth aspect, a network-side device is provided. The network-side device includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0032] In a seventh aspect, a terminal is provided, including a processor and a communication interface. Wherein,

[0033] The communication interface is configured to: receive a target message sent by a network-side device, where the target message carries physical random access channel transmission opportunity (RO) scheduling information;

[0034] The processor is configured to: determine a target RO based on the RO scheduling information, and perform random access based on the target RO;

[0035] Wherein, the target message includes at least one of the following:

[0036] Random access response message;

[0037] Paging-related message;

[0038] Common downlink control information (DCI).

[0039] In an eighth aspect, a network-side device is provided, including a processor and a communication interface. Wherein, the communication interface is configured to:

[0040] Send a target message to a terminal, where the target message carries physical random access channel transmission opportunity (RO) scheduling information; the RO scheduling information is used for random access;

[0041] Wherein, the target message includes at least one of the following:

[0042] Random access response message;

[0043] Paging-related message;

[0044] Common DCI.

[0045] In a ninth aspect, a random access system is provided, including: a terminal and a network-side device. The terminal can be used to execute the steps of the method described in the first aspect, and the network-side device can be used to execute the steps of the method described in the second aspect.

[0046] In a tenth aspect, a readable storage medium is provided. A program or instructions are stored on the readable storage medium, and when the program or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0047] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the method described in the first aspect, or implement the method described in the second aspect.

[0048] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or to implement the steps of the method described in the second aspect.

[0049] In an embodiment of the present application, a terminal receives a target message sent by a network-side device. The target message carries physical random access channel transmission opportunity RO scheduling information. The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO. Among them, the target message includes at least one of the following: a random access response message; a paging-related message; a common downlink control information DCI. In this way, the network-side device carries the RO scheduling information through at least one of the random access response message, the paging-related message, and the DCI. Through this RO scheduling information, more ROs can be dynamically scheduled for the terminal to perform random access, thereby being able to shorten the waiting duration for the terminal to initiate a random access attempt. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;

[0051] Figure 2 is one of the schematic diagrams of a random access process in the related art;

[0052] Figure 3 is a schematic diagram of the format of a RAR message in the related art;

[0053] Figure 4 is a schematic diagram of the format of a MAC RAR unit in the related art;

[0054] Figure 5 is a schematic diagram of the format of a MAC sub-header in the related art;

[0055] Figure 6 is another schematic diagram of a random access process in the related art;

[0056] Figure 7 is one of the schematic diagrams of the association relationship between an RO and an SSB in the related art;

[0057] Figure 8 is another schematic diagram of the association relationship between an RO and an SSB in the related art;

[0058] Figure 9 is one of the flowcharts of a random access method provided by an embodiment of the present application;

[0059] Figure 10It is the second flowchart of a random access method provided by an embodiment of the present application;

[0060] Figure 11 It is one of the schematic diagrams of the format of a MAC sub - header provided by an embodiment of the present application;

[0061] Figure 12 It is the second schematic diagram of the format of a MAC sub - header provided by an embodiment of the present application;

[0062] Figure 13 It is one of the schematic diagrams of the association relationship between an RO and an SSB provided by an embodiment of the present application;

[0063] Figure 14 It is the second schematic diagram of the association relationship between an RO and an SSB provided by an embodiment of the present application;

[0064] Figure 15 It is the third schematic diagram of the association relationship between an RO and an SSB provided by an embodiment of the present application;

[0065] Figure 16 It is one of the structural diagrams of a random access device provided by an embodiment of the present application;

[0066] Figure 17 It is the second structural diagram of a random access device provided by an embodiment of the present application;

[0067] Figure 18 It is the schematic diagram of the structure of a communication device provided by an embodiment of the present application;

[0068] Figure 19 It is the schematic diagram of the structure of a terminal provided by an embodiment of the present application;

[0069] Figure 20 It is the schematic diagram of the structure of a network - side device provided by an embodiment of the present application. Detailed implementation manners

[0070] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0071] The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described herein. The objects distinguished by "first" and "second" are usually of the same category, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in the description and claims means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The term "indication" in the description and claims of this application can be either an explicit indication or an implicit indication. Among them, an explicit indication can be understood as that the sender clearly informs the receiver of the operation or request result to be executed in the sent indication; an implicit indication can be understood as that the receiver makes a judgment based on the indication sent by the sender and determines the operation or request result to be executed according to the judgment result.

[0072] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and 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 the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and uses NR terms in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0073] Figure 1Block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle user equipment (VUE), a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device 12 can also be referred to as a radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit.The access network device 12 may include a base station, a Wireless Local Area Network (WLAN) access point, or a Wireless Fidelity (WiFi) node, etc. The base station may be referred to as Node B, Evolved Node B (eNB), access point, Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B, home evolved Node B, Transmitting Receiving Point (TRP), or some other suitable term in the art. 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 the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0074] The core network device may include, but is not limited to, at least one of the following: core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0075] For ease of understanding, some content related to the embodiments of this application will be described below:

[0076] 1. 4-step Random Access Channel (RACH) process

[0077] 1.1 4-step random access process

[0078] The 4-step random access process is as Figure 2 shown.

[0079] The process of contention-based random access is mainly divided into four steps:

[0080] Msg1: The terminal selects a random access resource and uses this random access resource to send the selected random access signal to the base station.

[0081] It should be noted that the terminal independently selects the time-frequency resources (i.e., RO) and preambles for sending Msg1 from a set of random access resources broadcast by the network side; therefore, there is a possibility of Msg1 collision, that is, multiple terminals select related ROs to send the same preamble.

[0082] After the terminal sends Msg1, it calculates the identification information for the network side to schedule Msg2 (such as the Random Access Radio Network Temporary Identity (RA-RNTI)) based on the time and frequency positions of the sent Msg1. After the terminal sends Msg1, it listens to the downlink channel within a pre-configured time window (such as the Random Access Response window (RAR window)) to obtain the feedback information Msg2 from the network side.

[0083] Msg2: The base station sends a random access response to the terminal. The random access response includes: Msg1 identification information (such as RAPID); uplink timing advance information (such as the Timing Advance Command); uplink transmission authorization information (such as the Uplink (UL) Grant); backoff information (such as the Backoff Indicator); temporary terminal identification information (such as the Temporary Cell RNTI (C-RNTI)). If the terminal does not receive the Random Access Preamble IDentifier (RAPID) corresponding to the Msg1 it sent until the end of the RAR window, it is considered that the RAR reception fails. Among them, there are two cases:

[0084] (1) The User Equipment (UE, i.e., the terminal) does not receive the RAR message during the RAR window.

[0085] (2) The UE receives the RAR message during the RAR window, but the RAR message does not contain the RAPID corresponding to the Msg1 it sent.

[0086] If the second case occurs and the RAR Message contains fallback information, the UE determines the time to perform a RACH attempt again according to the indication of the fallback information. If it is the first case, or the second case and the RAR Message received by the UE does not contain fallback information, the UE may perform the next random access attempt at the moment of the next available Physical Random Access Channel transmission opportunity (PRACH transmission Occasion or PRACH Occasion, RO).

[0087] Msg3: If the UE successfully receives the RAR, the terminal sends an uplink transmission on the UL grant specified in Msg2. The content of the Msg3 uplink transmission is different for different random access reasons. For example, for initial access, the Msg3 transmission is a Radio Resource Control (RRC) connection establishment request.

[0088] Msg4: The contention resolution message, based on which the terminal can determine whether the random access is successful.

[0089] The terminal starts a contention resolution timer when sending Msg3 or after sending Msg3. If Msg4 is not successfully received until the contention resolution timer expires, the UE considers that Msg4 reception fails.

[0090] After Msg4 reception fails, the UE may initiate the next RACH attempt. If the UE received fallback information when receiving Msg2, the UE determines the time to initiate the next RACH attempt based on the fallback information.

[0091] 1.2. Medium Access Control (MAC) Protocol Data Unit (PDU) (i.e., Random Access Response)

[0092] In the 4-step random access procedure, the format of the RACH message (Msg) 2 (such as the RAR message) is as Figure 3 shown.

[0093] The RAR message contains two formats of sub-PDUs (subPDUs) and padding:

[0094] Type A1:

[0095] The sub-PDU containing the BI: Only contains a 1-byte sub-header for carrying RACH fallback information;

[0096] Type A2:

[0097] subPDUs containing RAPID: They can be divided into two types. One is the format containing only a 1-byte sub-header, and the other is the format containing a 1-byte sub-header and a MAC RAR unit; this type of subPDU is used to carry the response to the detected preamble.

[0098] Padding: It contains all padding bits inside.

[0099] The RAR message contains at least one of the A1 type subPDU or the A2 type subPDU, and may contain Padding.

[0100] The format of the MAC subheader of the A1 type subPDU is: E / T / R / R / BI; the format of the subheader of the A2 type subPDU is: E / T / RAPID.

[0101] Among them, the meanings of the respective indication fields (or fields) in the MAC subheader of the A1 / A2 subPDU are as follows:

[0102] E: If the E field (or domain) is set to 1, this subPDU is not the last subPDU of the RAR message, that is, there are other subPDUs following; if the E field is set to 0, this subPDU is the last subPDU, and if there are other remaining bits in the RAR message after this subPDU, the remaining bits are padding. Specifically, the E extension field is a flag indicating whether the MAC subPDU including this MAC subheader is the last MAC subPDU in the MAC PDU. The E field is set to 1 to indicate that there is at least another MAC subPDU following. The E field is set to 0 to indicate that the MAC subPDU including this MAC subheader is the last MAC subPDU in the MAC PDU (The Extension field is a flag indicating if the MACsubPDU including this MAC subheader is the last MAC subPDU or not in the MACPDU.The E field is set to 1 to indicate at least another MAC subPDUfollows.The E field is set to 0 to indicate that the MAC subPDU includingthis MAC subheader is the last MAC subPDU in the MAC PDU).

[0103] T: 0 indicates that this subPDU MAC subheader contains a BI field, and 1 indicates that this subPDU MAC subheader contains a RAPID field. Specifically, the T-type field is a flag indicating whether the MAC subheader contains a Random Access Preamble ID or a Backoff Indicator. The T field is set to 0 to indicate the presence of a Backoff Indicator field in the subheader (BI). The T field is set to 1 to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID).

[0104] R: Reserved bit, set to 0.

[0105] BI: The Backoff Indicator field is used to indicate the overload condition of the cell. The length is 4 bits. The size of the BI field is 4 bits.

[0106] RAPID: The Random Access Preamble IDentifier (RAPID) field is used to indicate the index information of the random access preamble detected / received by the cell, with a length of 6 bits. If the RAPID in the MAC subheader of a MAC subPDU corresponds to one of the random access preambles configured for SI request, the MAC RAR unit is not included in the MAC subPDU (The size of the RAPID field is 6bits.If the RAPID in the MACsubheader of a MAC subPDU corresponds to one of the Random Access Preamblesconfigured for SI request,MAC RAR is not included in the MAC subPDU).

[0107] For a MAC subheader containing E / T / RAPID, if the corresponding MAC RAR, the format of its corresponding MAC RAR unit is as Figure 4 shown.

[0108] In current practical applications, the total length of the MAC RAR unit is always 7 bytes.

[0109] For a MAC subheader containing E / T / R / R / BI, its subheader format is as Figure 5 shown.

[0110] Among them, the value range of the BI field is 16 numbers from 0 to 15, and each value number of the BI field corresponds to a backoff time length.

[0111] 1.3. Backoff Parameter values

[0112] The values of the Backoff parameter are shown in Table 1.

[0113] Table 1: Backoff Parameter values

[0114]

[0115] If the UE receives a Random Access Response message within the RAR window and the MAC subPDU corresponding to the BackoffIndicator is included therein, the UE sets the local variable PREAMBLE_BACKOFF according to the received Backoff Indicator.

[0116] If the UE receives a Random Access Response message within the RAR window and the MAC subPDU corresponding to the BackoffIndicator is not included therein, the UE sets the local variable PREAMBLE_BACKOFF to 0 ms.

[0117] If the random access is not successfully completed, the UE randomly selects a backoff value based on a uniform distribution between 0 and PREAMBLE_BACKOFF ms; after waiting for the selected backoff value, the UE re-performs the Random Access resource selection process, that is, starts the next RACH attempt.

[0118] 2. 2-Step RACH Process

[0119] As Figure 6 shown, the 2-step RACH process includes the following steps:

[0120] Step (1): The network side configures the configuration information for two-step random access for the UE, such as including: the transmission resource information corresponding to MsgA.

[0121] Step (2): The UE triggers the 2-step RACH process and sends the request message (MsgA) to the network side, such as by sending through the Physical Uplink Shared Channel (PUSCH) and preamble. When sending MsgA or after sending MsgA, the UE starts the timer msgB-ResponseWindow and listens for MsgB. The duration of the timer msgB-ResponseWindow is pre-configured by the network.

[0122] Step (3): The network side sends the confirmation message (MsgB) to the UE. If the UE fails to receive MsgB, the UE re-sends Msg1 or re-sends MsgA or sends Msg3, which is specifically determined according to the situation where the UE fails to receive MsgB. Among them, failing to receive MsgB means that within the msgB-ResponseWindow, the UE does not receive the contention resolution identifier (Identifier, ID) corresponding to its own sent MsgA.

[0123] 3. Mapping Rule of Synchronization Signal Block (SSB) to RO in 5G NR

[0124] The configuration parameters of the Physical Random Access Channel (PRACH) resources and SSB-RO are configured in System Information Block (SIB) 1. In NR, a cell can configure multiple Frequency Division Multiplexing (FDM) Physical Random Access Channel transmission opportunities (PRACH transmission occasion or PRACH Occasion, RO) at the time-domain position for transmitting PRACH. At a certain moment, the number of ROs that can perform FDM can be: {1, 2, 4, 8}, which is configured and determined by the higher-layer parameter Msg1-FDM.

[0125] The random access preamble can only be transmitted on the time-domain resources configured by the parameter PRACHConfigurationIndex and the frequency-domain resources configured by the parameter Msg1-FDM. The PRACH frequency-domain resource n RA ∈{0, 1, …, M - 1}, where M is equal to the higher-layer parameter Msg1-FDM. At the initial access, the PRACH frequency-domain resource n RA is numbered in ascending order starting from the RO resource with the lowest frequency within the initial active uplink bandwidth part, otherwise, the PRACH frequency-domain resource n RA is numbered in ascending order starting from the RO resource with the lowest frequency within the active uplink bandwidth part. For example, in Figure 7 when the number of ROs for FDM at a certain moment is 8 (Msg1-FDM = 8), the RO resources are numbered as RO#0 to RO#7 in ascending order of frequency.

[0126] In NR, there is an association relationship between the RO and the actually transmitted Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block, SSB). The RO is associated with the SSB in the order of frequency domain (from low frequency to high frequency) first and then time domain. One SSB may be associated with multiple consecutive ROs, or multiple SSBs may be associated with one RO (in this case, different SSBs correspond to different Preambles), which is configured by the network through the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. Exemplarily, the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is as follows:

[0127]

[0128]

[0129] For example, oneEighth means that one SSB is associated with 8 consecutive ROs, and eight means that 8 SSBs are associated with one RO. {n4, n8, n12,...} represents the number of Preambles associated with each SSB on one RO. For example, the value n4 means that the number of Preambles associated with each SSB on one RO is 4, and n8 means that the number of Preambles associated with each SSB on one RO is 4.

[0130] After all SSBs are associated with ROs in one round, it constitutes an SSB-RO mapping cycle. The association period of one SSB to RO may contain one or more SSB-RO mapping cycles. The association pattern period of one SSB to RO may contain one or more SSB-RO association periods. The mapping of SSB to RO is repeated with the association pattern period as the cycle, and the maximum association pattern period is 160 ms.

[0131] Generally, the base station can use different beams to transmit different SSBs, where the number of SSBs is configured through the ssb-PositionsInBurst parameter. For FR2, the maximum number of SSBs is 64. The UE selects the RO or the combination of RO and preamble associated with the SSB with good signal according to the intensity of the received downlink beam or SSB, and sends Msg1. In this way, the network can determine the SSB selected by the UE according to the RO or the combination of RO and preamble of the received Preamble, and send Msg2 on the downlink beam corresponding to the SSB to ensure the reception quality of the downlink signal.

[0132] Taking Figure 7 as an example, the number of ROs of FDM at a moment is 8, and the number of actually transmitted SSBs is 4, namely SSB#0, SSB#1, SSB#2, SSB#3, and each SSB is associated with 2 ROs. If the UE determines to send a PRACH / Msg1 on the RO corresponding to SSB#0, then the UE selects one RO from RO#0 and RO#1 to send the PRACH.

[0133] Taking Figure 8 as an example, the number of ROs of FDM at a moment is 2, and the number of actually transmitted SSBs is 8, namely SSB#0, SSB#1, ……, SSB#7, and every 2 SSBs are associated with 1 RO. When multiple SSBs share one RO, the Preamble sets associated with these multiple SSBs are different, that is, the same Preamble cannot belong to the Preamble sets associated with different SSBs at the same time: Taking the RO#0 in Figure 8 as an example, RO#0 has a total of 60 Preambles, among which the preambles with indexes 0 to 29 are associated with SSB#0, and the preambles with indexes 30 to 59 are associated with SSB#1.

[0134] It should be noted that Figure 8 each square in

[0135] represents one RO, and the SSB marked in the square refers to the SSB associated with this RO. Before the UE sends a PRACH, it first selects an SSB with an RSRP higher than the threshold according to the received reference signal received power (RSRP) of the beam (such as an SSB); if the RSRPs of multiple SSBs are higher than the threshold, the terminal can select any SSB with an RSRP higher than the threshold; when there is no SSB with an RSRP higher than the threshold, the UE selects an SSB based on the implementation.

[0136] Based on the configuration of the network (NW), the UE obtains the corresponding relationship between the SSB and the RO. After selecting an SSB, the RO corresponding to the selected SSB is used as the RO for sending the PRACH / Preamble / Msg1. If the selected SSB is associated with multiple ROs, the terminal can select one of them to send the PRACH / Preamble / Msg1.

[0137] For example: in the example shown in Figure 7 , assuming the UE selects SSB#1, the UE can select one from RO#2 and RO#3 to send the PRACH / Msg1; in Figure 8In the example shown, if the UE selects SSB#1, the UE can select the available RO closest to the current time among the ROs associated with SSB#1 (such as RO#0 or 4) to send PRACH / Msg1. In the selected RO, the UE selects a preamble from the preamble set associated with the selected SSB to send PRACH. As Figure 8 In the case where one RO is associated with 2 SSBs, in the available preamble set associated with the SSB in one RO, the preambles will be divided into two subsets, each subset corresponding to one SSB. The UE will select a certain preamble sequence from the preamble subset corresponding to the selected SSB for sending PRACH / Msg1.

[0138] Next, in conjunction with the accompanying drawings, the random access method, device, terminal, and network-side device provided by the embodiments of the present application will be described in detail through some embodiments and their application scenarios.

[0139] See Figure 9 , Figure 9 is a flowchart of a random access method provided by an embodiment of the present application. As Figure 9 shown, the random access method includes the following steps:

[0140] Step 101, the terminal receives a target message sent by the network-side device, and the target message carries physical random access channel transmission opportunity RO scheduling information;

[0141] Step 102, the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO;

[0142] Among them, the target message includes at least one of the following:

[0143] Random access response message;

[0144] Paging-related message;

[0145] Common downlink control information (Downlink Control Information, DCI).

[0146] Among them, the RO scheduling information may include one or more of the following combinations: the first configuration information of the RO, the time domain or frequency domain position information of the RO, the repetition period information of the RO, the effective duration information of the RO, or the first indication information, etc. This embodiment does not limit this. Any information that can be used to schedule the RO can be used as the RO scheduling information. Among them, the first indication information is used to indicate whether the RO is effective. The effective duration information can indicate the duration for which the RO is considered available.

[0147] Among them, the RO corresponding to the RO scheduling information can be used to determine the target RO. The terminal can determine the target RO according to the RO corresponding to the RO scheduling information and perform random access based on the target RO.

[0148] Among them, the RO corresponding to the RO scheduling information can be understood as a dynamic RO. The dynamic RO can also be described as an additional RO, or a flexible RO, or a dynamic RO. The dynamic RO is different from the legacy RO (that is, the RO not scheduled by the target message) and is a newly introduced RO, that is, the RO scheduled by the target message.

[0149] Among them, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, which may include: the terminal determines the target RO based on the RO scheduling information and the second configuration information carried in the system information and performs random access based on the target RO; or, the terminal selects an RO from the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information, and the terminal performs random access based on the selected target RO; or, the terminal selects an RO from the RO corresponding to the RO scheduling information, and the terminal performs random access based on the selected target RO; and so on. This embodiment does not limit this. The RO corresponding to the third configuration information may be a legacy RO, and the legacy RO may refer to a non-dynamic RO.

[0150] In one implementation, the terminal selects an RO from the legacy RO and the flexible RO (that is, the RO corresponding to the RO scheduling information) for the next random access attempt; or the terminal only selects an RO from the flexible RO for the next random access attempt.

[0151] In one implementation, the random access response message may be MsgB of 2-step RACH.

[0152] In one implementation, the random access response message may be Msg2 of 4-step RACH.

[0153] In one implementation, the configuration information of the additional RO, or the flexible RO, or the dynamic RO may be carried in the random access response message; if the terminal's random access attempt fails and the configuration information of the additional RO, or the flexible RO, or the dynamic RO is saved, the terminal applies the additional RO, or the flexible RO, or the dynamic RO for the next random access attempt.

[0154] In one implementation, part of the configuration information of the flexible RO (i.e., the RO corresponding to the RO scheduling information) can be broadcast in the system information, and part of it can be carried in the random access response message; the terminal that receives the configuration information in the random access response message can combine the configuration information of the flexible RO in the system information to determine the configuration of the flexible RO.

[0155] In one implementation, the paging-related messages may include paging scheduling signaling, paging messages, paging indication signals, paging wake-up signals, low-power wake-up signals, or paging short messages, etc. Any message related to the paging process can be understood as a paging-related message.

[0156] In one implementation, part of the configuration information of the flexible RO (i.e., the RO corresponding to the RO scheduling information) can be broadcast in the system information, and part of it can be carried in the paging-related message; the terminal that receives the configuration information in the paging-related message can combine the configuration information of the flexible RO in the system information to determine the configuration of the flexible RO.

[0157] In one implementation, taking the target message as the random access response message as an example, if the terminal does not detect a matching random access response message until the random access response time window ends; then the terminal applies the dynamically scheduled RO (i.e., the RO corresponding to the RO scheduling information) to perform subsequent random access attempts; if the terminal detects a matching random access response message, it continues the subsequent process. For example: in the 4-step RACH process, the subsequent process is to send RACH Msg3; in the 2-step RACH process, the random access process ends, and the UE performs subsequent operations.

[0158] In one implementation, taking the target message as the paging-related message as an example, when the terminal receives a paging message, if the paging message indicates that it is being paged; then the terminal uses the RO scheduling information carried in the paging message for random access.

[0159] In one implementation, taking the target message as the common DCI as an example, a new downlink scheduling ID X can be defined, and the network side uses downlink scheduling signaling to indicate the scheduling ID X: this scheduling signaling is used to indicate the resource information of the dynamically scheduled RO (i.e., the RO corresponding to the RO scheduling information).

[0160] In one implementation, part of the configuration information of the flexible RO (i.e., the RO corresponding to the RO scheduling information) can be broadcast in the system information, and part can be carried by the common DCI; the terminal that receives the configuration information in the common DCI can combine the configuration information of the flexible RO in the system information to determine the configuration of the flexible RO.

[0161] It should be noted that in the case where the target message is a random access response message, the embodiments of the present application can solve the problem in the related art that when the random backoff mechanism causes congestion, the delay of the terminal's next random access attempt becomes longer. In the random access process of the related art, if the RACH channel is congested, the network side will send a Backoff indication of the longest waiting time T; the terminal will, according to the Backoff indication, equally probably select a duration Twait between 0 and the longest waiting time T, and after waiting for the duration Twait, the terminal can initiate the next random access attempt. Since different terminals select different Twait, the RACH congestion problem is alleviated. However, this random backoff mechanism will cause the delay of the terminal's next random access attempt to become longer. In the embodiments of the present application, the terminal listens for the random access response message (such as Msg2 or MsgB) within the time window for listening for the random access response. If there is RO scheduling information of the dynamic RO in the random access response message, the terminal applies this RO to perform subsequent random access attempts. The embodiments of the present application can improve the RACH channel congestion while shortening the delay of the terminal's random access attempt and enhancing the user experience.

[0162] In the embodiments of the present application, the terminal receives a target message sent by a network side device, and the target message carries physical random access channel transmission opportunity RO scheduling information; the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO; wherein, the target message includes at least one of the following: a random access response message; a paging-related message; a common downlink control information DCI. In this way, the network side device carries the RO scheduling information through at least one of the random access response message, the paging-related message, and the DCI. Through this RO scheduling information, more ROs can be dynamically scheduled for the terminal to perform random access, thereby shortening the waiting duration for the terminal to initiate a random access attempt.

[0163] Optionally, the RO scheduling information includes at least one of the following:

[0164] The first configuration information of the RO;

[0165] The time position information of the RO;

[0166] The frequency position information of the RO;

[0167] The repetition period information of the RO;

[0168] The effective duration information of the RO;

[0169] The first indication information for indicating whether the RO is effective.

[0170] Among them, the first configuration information of the RO may include at least one of the following: the correspondence between the Preamble and the beam, the prach root sequence number, the RSRP threshold for selecting the beam, etc.

[0171] In one implementation, the mapping relationship between the RO and the downlink beam information (such as SSB) can be determined through the first configuration information of the RO in the RO scheduling information, and the RO for sending the preamble can be determined according to the downlink beam where the terminal is located or selected. The time-frequency position of this RO can be determined by the time-frequency position information of the RO in the RO scheduling information, or can be pre-configured or predefined by the protocol. The determined RO for sending the preamble is the RO corresponding to the RO scheduling information.

[0172] In one implementation, the time-frequency position of the RO can be determined through the time position information or frequency position information of the RO in the RO scheduling information. The RO for sending the preamble is determined according to the mapping relationship between the RO and the downlink beam information (such as SSB), the time-frequency position of the RO, and the downlink beam where the terminal is located or selected. The mapping relationship between the Preamble and the downlink beam information (such as SSB) can be determined by the first configuration information of the RO in the RO scheduling information, and the terminal determines the preamble to be sent based on the downlink beam where it is located or selected. The determined RO for sending the preamble is the RO corresponding to the RO scheduling information.

[0173] In one implementation, the RO scheduling information may include the effective duration information of the RO. The terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, which may include that within the effective time corresponding to the effective duration information of the RO, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO.

[0174] In one implementation, the RO scheduling information may include the first indication information. The terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, which may include that when the first indication information indicates that the target RO is effective, the terminal performs random access based on the target RO.

[0175] In this embodiment, the terminal can determine a target RO based on at least one of the first configuration information of the RO, the time or frequency position information of the RO, the repetition period information of the RO, the effective duration information of the RO, and the first indication information, and perform random access based on the target RO, so that the number of optional ROs available for the terminal to perform random access can be increased, the probability of RACH collision can be reduced, and the waiting duration for the terminal to initiate a random access attempt can be shortened.

[0176] Optionally, the target message includes a random access response message. The terminal determines a target RO based on the RO scheduling information, and performs random access based on the target RO, including:

[0177] When the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information, and sends a next random access preamble based on the target RO.

[0178] Among them, random access failure may refer to the situation where the random access response is not received successfully and the random access procedure is not completed. There are the following two situations where the random access response is not received successfully: the random access procedure is not completed or the random access procedure is completed but not successfully. When the terminal determines that the random access response is not received successfully and the random access procedure is not completed, the terminal can continue to send the next random access preamble (for example: when the maximum number of RACH attempts has not been reached).

[0179] In this embodiment, when the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information carried in the random access response message, and sends a next random access preamble based on the target RO. Thus, the network side can schedule more ROs through the random access response message for the terminals with random access failures to perform random access in a short time, avoiding introducing a long waiting time (backoff) for another RACH attempt.

[0180] Optionally, after the terminal receives the target message sent by the network side device, the method further includes:

[0181] The terminal stores the RO scheduling information;

[0182] When the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information, and sends a next random access preamble based on the target RO, including:

[0183] When it is determined at the terminal that random access fails, if the terminal stores RO scheduling information, the terminal determines a target RO based on the stored RO scheduling information and performs the next random access preamble transmission based on the target RO.

[0184] Wherein, the terminal stores the RO scheduling information, for example, stores all or part of the parameters carried by the RO scheduling information.

[0185] Wherein, the terminal can determine a random access response time window and receive a random access response message within the random access response time window; if the received random access response message contains RO scheduling information, the terminal stores the RO scheduling information.

[0186] In addition, if until the end of the random access response time window, the terminal does not detect a random access response message that matches the preamble identifier sent by the terminal, the terminal determines a target RO based on the stored RO scheduling information and performs the next random access preamble transmission based on the target RO.

[0187] In one implementation, if within the random access response time window, the terminal receives a random access response message that does not contain RO scheduling information, the terminal clears the stored RO scheduling information.

[0188] In one implementation, when the RO scheduling information includes effective duration information, the terminal starts timing when receiving the RO scheduling information; when the effective time corresponding to the effective duration information expires, the terminal can delete the stored RO scheduling information; if during the timing, the terminal receives new RO scheduling information, it re-times according to the new effective duration information.

[0189] In one implementation, after the terminal successfully completes random access (such as successfully receiving Msg4 in the 4-step RACH process), the terminal clears or releases the randomly accessed resources dynamically scheduled by the network side, for example, clears the stored RO scheduling information.

[0190] In this implementation, when it is determined at the terminal that random access fails, if the terminal stores RO scheduling information, the terminal determines a target RO based on the stored RO scheduling information and performs the next random access preamble transmission based on the target RO. In this way, by storing the RO scheduling information, the terminal can, when a random access attempt is needed, determine the target RO through the stored RO scheduling information and send a random access preamble, enabling the terminal that fails in random access to perform a random access attempt in a short time.

[0191] Optionally, the terminal determines that random access fails, including at least one of the following:

[0192] If the terminal does not detect a random access response message containing a match for the preamble identifier transmitted by the terminal in the random access response message corresponding to the random access response time window, the terminal determines that the random access fails;

[0193] If the terminal fails to resolve the contention successfully, the terminal determines that the random access fails.

[0194] Among them, the random access response time window may refer to the ra-ResponseWindow configured in RACH ConfigCommon (ra-ResponseWindow configured in RACH-ConfigCommon). Failing to detect a random access response message containing a match for the preamble identifier (Preamble_INDEX) transmitted by the terminal can be understood as not receiving a random access response containing a random access preamble identifier that matches the transmitted Preamble_INDEX (theRandom Access Response containing Random Access Preamble identifiers thatmatches the transmitted PREAMBLE_INDEX has not been received).

[0195] Optionally, the method further includes:

[0196] The terminal receives system information, and the system information carries second configuration information of the target RO;

[0197] The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including:

[0198] The terminal determines the target RO based on the RO scheduling information and the second configuration information, and performs random access based on the target RO.

[0199] Among them, the second configuration information of the target RO may include at least one of the following: the correspondence between the preamble and the beam, the prach root sequence number, the RSRP threshold for selecting the beam, etc.

[0200] It should be noted that the terminal can obtain partial configuration of the target RO through system information broadcast by the cell, and combine it with the RO scheduling information included in the target message to determine the time-frequency position of the target RO, the generation parameters of the preamble sequence, etc.

[0201] In this embodiment, the terminal determines the target RO based on the RO scheduling information and the second configuration information, and performs random access based on the target RO. As a result, part of the configuration of the target RO can be carried by the system information, reducing the complexity of the RO scheduling information, supporting the indication of the target RO using less-bit RO scheduling information in combination with the system information, and saving signaling overhead.

[0202] Optionally, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, including:

[0203] The terminal selects an RO from among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried by the system information;

[0204] The terminal performs random access based on the selected target RO.

[0205] Among them, the RO corresponding to the third configuration information carried by the system information may refer to the RO configured by the third configuration information carried by the system information. The RO corresponding to this third configuration information may also be described as a non-dynamic RO configured by the system information, or a non-dynamic RO broadcast in the system information.

[0206] In one embodiment, within the effective time corresponding to the effective duration information of the RO in the RO scheduling information, the terminal selects an RO from among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried by the system information; the terminal performs random access based on the selected target RO.

[0207] It should be noted that the RO corresponding to the third configuration information carried by the system information can be understood as a non-dynamic RO. Within the effective time corresponding to the effective duration information of the RO, the terminal considers that the non-dynamic RO broadcast in the system information and the dynamic RO scheduled by the target message can both be used for the random access process.

[0208] In this embodiment, the terminal selects an RO from among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried by the system information; the terminal performs random access based on the selected target RO. In this way, by selecting an RO for random access from among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried by the system information, more ROs can be dynamically scheduled for the terminal to perform random access, thereby being able to shorten the waiting duration for the terminal to initiate a random access attempt.

[0209] Optionally, the selected RO is the next RO closest to the current time among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information.

[0210] Among them, the current time may refer to the time when the RO is selected.

[0211] In this embodiment, when the terminal makes a new random access resource selection, the terminal selects the RO with the most recent time for random access; regardless of whether it belongs to the non-dynamic RO broadcast in the system information or the dynamic RO scheduled by the target message.

[0212] Optionally, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, including:

[0213] The terminal selects an RO from the ROs corresponding to the RO scheduling information.

[0214] The terminal performs random access based on the selected target RO.

[0215] It should be noted that the terminal that receives the RO scheduling information can consider the non-dynamic RO broadcast in the system information as invalid or not available, that is, only the RO scheduled by the target message can be used for the random access process.

[0216] In this embodiment, the terminal selects an RO from the ROs corresponding to the RO scheduling information; the terminal performs random access based on the selected target RO. In this way, the terminal that receives the RO scheduling information and the terminal that does not receive the RO scheduling information will use different RO resources for random access, reducing the random access load on the non-dynamic scheduled RO resources.

[0217] Optionally, the terminal selects an RO from the ROs corresponding to the RO scheduling information, including:

[0218] Within the effective time corresponding to the effective duration information of the ROs corresponding to the RO scheduling information, the terminal selects an RO from the ROs corresponding to the RO scheduling information.

[0219] In one embodiment, within the effective time corresponding to the effective duration information of the ROs corresponding to the RO scheduling information, the terminal only selects an RO from the ROs corresponding to the RO scheduling information.

[0220] In this embodiment, within the effective time corresponding to the effective duration information of the RO, the terminal that receives the RO scheduling information can consider the non-dynamic RO broadcast in the system information as invalid, that is, only the RO scheduled by the target message can be used for the random access process.

[0221] Optionally, the target message includes a target media access control (MAC) sub-header or a target MAC control element (CE), and the target MAC sub-header or target MAC CE carries the RO scheduling information.

[0222] It should be noted that the target MAC sub-header or target MAC CE can be a newly introduced MAC sub-header or MAC CE; or it can be a MAC sub-header or MAC CE obtained by enhancing or expanding an existing MAC sub-header or MAC CE.

[0223] Optionally, the target MAC sub-header or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC sub-header or target MAC CE.

[0224] Among them, the terminal can determine whether the received MAC sub-header or MAC CE is the target MAC sub-header or target MAC CE carrying the RO scheduling information through the second indication information.

[0225] In this embodiment, the target MAC sub-header or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC sub-header or target MAC CE, so that the terminal can quickly determine the MAC sub-header or MAC CE carrying the RO scheduling information through the second indication information.

[0226] Optionally, the RO scheduling information includes third indication information, and the third indication information is used to indicate at least one RO that is effective in the RO corresponding to the third configuration information carried in the system information.

[0227] Among them, the target RO can be the RO that is effective in the RO corresponding to the third configuration information carried in the system information indicated by the third indication information.

[0228] Among them, the RO corresponding to the third configuration information carried in the system information can refer to the RO configured by the third configuration information carried in the system information. The RO corresponding to this third configuration information can also be described as a non-dynamic RO configured by the system information, or a non-dynamic RO broadcast in the system information.

[0229] In one embodiment, the third indication information can be a dynamic RO configuration field, which is used to provide the configuration of the dynamic RO. This third indication information can be associated with the RO configuration provided in the system information. For example, the system information carries N sets of dynamic RO configurations (N >= 1), and the third indication information indicates the number of the currently effective configuration, and the effective configuration indicated by the third indication information is the configuration of the target RO.

[0230] In one implementation, the third indication information indicates to start or deactivate the RO configured by the third configuration information carried in the system information. For example, a one-bit third indication information is used to indicate to start or deactivate the RO configured by the third configuration information; or multiple-bit third indication information is used to indicate the proportion of the ROs configured by the third configuration information to be enabled, such as enabling 0%, 50%, 25%, 75%, 100% of the ROs configured by the third configuration information.

[0231] In one implementation, the third indication information may further indicate the effective duration information of the target RO.

[0232] It should be noted that the third indication information may be composed of multiple parts for carrying different information. For example, the third indication information may also be used to indicate the time or frequency resource configuration of the target RO, the configuration number of the time or frequency resource configuration, or the effective duration configuration, etc.

[0233] In this implementation, the RO scheduling information includes the third indication information, and the third indication information is used to indicate at least one effective RO among the ROs corresponding to the third configuration information carried in the system information, so that the target RO can be indicated by using less-bit RO scheduling information in combination with the system information, saving signaling overhead.

[0234] Optionally, the paging-related message includes at least one of the following:

[0235] Paging scheduling signaling; paging message; paging indication signal; paging wake-up signal; low-power wake-up signal; paging short message.

[0236] Optionally, the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information are respectively mapped to the synchronization signal block SSB.

[0237] It should be noted that the RO corresponding to the third configuration information carried in the system information and the dynamically scheduled RO are respectively mapped to the SSB. If the network side sends the RO scheduling information, the dynamically scheduled target RO will not change the mapping relationship between the RO corresponding to the third configuration information carried in the system information and the SSB. The RO corresponding to the third configuration information carried in the system information can be understood as a traditional (legacy) RO.

[0238] In this implementation, the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information are respectively mapped to the synchronization signal block SSB. In this way, regardless of whether the network side sends the RO scheduling information, the mapping relationship between the RO corresponding to the third configuration information carried in the system information and the SSB will not change, avoiding the network side being unable to uniquely determine the SSB based on the preamble sent by the terminal on the RO.

[0239] Optionally, the target message includes a common DCI, the common DCI carries RO scheduling information, the RO scheduling information includes a scheduling identifier, and the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including:

[0240] The terminal determines the target RO based on the RO corresponding to the scheduling identifier and performs random access based on the target RO.

[0241] Wherein, the RO corresponding to the scheduling identifier may include one or more ROs, and the terminal may select an RO from the ROs corresponding to the scheduling identifier and perform random access based on the selected target RO. Exemplarily, the target RO may be the next RO closest to the current time among the ROs corresponding to the scheduling identifier.

[0242] In one implementation, a scheduling identifier (such as scheduling ID X) can be agreed upon by protocol for RO scheduling. When the network sends a common DCI and the common DCI indicates that the scheduled ID is X, the terminal that receives the common DCI determines the target RO according to the indication in the common DCI.

[0243] In this implementation, the terminal performs random access based on the RO corresponding to the scheduling identifier carried in the common DCI, so that the network side can schedule more ROs through the common DCI for the terminals with random access failures to perform random access in a short time, avoiding introducing a long waiting time for a re-RACH attempt.

[0244] Optionally, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO, including:

[0245] In the case where it is determined that the terminal is a target type of terminal, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO;

[0246] Wherein, the terminal determines whether the terminal is the target type of terminal based on at least one of the following:

[0247] The random access times of the terminal; the preamble transmission power of the terminal; the received signal strength indication (RSSI) of the serving cell measured by the terminal; the reference signal received quality (RSRQ) of the serving cell measured by the terminal; the radio resource control (RRC) state of the terminal; the capability or type of the terminal; the service trigger type for the terminal to perform random access.

[0248] Among them, the terminal of the target type can be a terminal with specific characteristics.

[0249] In one implementation, the terminal of the target type may include at least one of the following:

[0250] A terminal with a RACH attempt count lower than a certain threshold;

[0251] A terminal with a RACH attempt count equal to or higher than a certain threshold;

[0252] A terminal with a preamble transmission power lower than a certain threshold;

[0253] A terminal with a preamble transmission power equal to or higher than a certain threshold;

[0254] A terminal that measures the RSSI / RSRQ of the serving cell lower than a certain threshold;

[0255] A terminal that measures the RSSI / RSRQ of the serving cell equal to or higher than a certain threshold;

[0256] A terminal in a specific RRC state, such as an idle state or an inactive state or a connected state terminal;

[0257] A terminal supporting specific capabilities, such as a terminal supporting access to satellites (such as a Non-Terrestrial Network (NTN)), a terminal supporting the Reduced Capability (RedCap) feature, etc.;

[0258] A terminal for which the RACH is triggered by a specific service type, for example: data, signaling, etc.

[0259] In this implementation, in the case where it is determined that the terminal is a terminal of the target type, the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO. In this way, only the terminal of the target type is allowed to determine the target RO based on the RO scheduling information and perform random access based on the target RO, providing more ROs for the terminal of the target type to perform random access, thereby being able to shorten the waiting duration for the terminal of the target type to initiate a random access attempt.

[0260] See Figure 10 , Figure 10 is a flowchart of a random access method provided by an embodiment of the present application. As Figure 10 shown, the random access method includes the following steps:

[0261] Step 201: The network-side device sends a target message to the terminal, where the target message carries physical random access channel transmission opportunity (RO) scheduling information; the RO scheduling information is used for random access.

[0262] Among them, the target message includes at least one of the following:

[0263] Random access response message;

[0264] Paging-related message;

[0265] Common DCI.

[0266] Among them, the RO scheduling information is used to determine the target RO, and the target RO is used for the random access of the terminal.

[0267] It should be noted that, as the implementation manner of the network-side device corresponding to the embodiment shown in Figure 9 , the specific implementation manner can refer to the relevant description of the embodiment shown in Figure 9 . To avoid repeated description, this embodiment will not be elaborated here.

[0268] The random access method provided by the embodiments of the present application will be described below through several specific embodiments:

[0269] In the following embodiments, the scheduling information of the dynamic RO can also be described as the RO scheduling information.

[0270] Embodiment 1:

[0271] In this embodiment, the random access method includes the following process:

[0272] (11). The UE sends the selected Preamble on the selected RO;

[0273] (12). The UE determines the random access response time window based on the time-frequency position of the RO used in step (11); and receives the random access response message within the random access response time window. If the received RAR response message contains the scheduling information of the dynamic RO, the UE saves the scheduling information of the dynamic RO.

[0274] Optionally, the scheduling information of the dynamic RO includes:

[0275] The time-frequency position information of the dynamic RO or the indication information of whether the dynamic RO is available, etc.;

[0276] The configuration information of the RO, such as the correspondence between the Preamble and the beam, the prach root sequence number, the RSRP threshold for beam selection, etc.;

[0277] The available duration information or the repetition period information of the dynamic RO, etc.

[0278] Optionally, if the received RAR response message does not contain the scheduling information of the dynamic RO, the UE clears the saved scheduling information of the dynamic RO.

[0279] (13) If the UE does not detect a response message matching the transmitted Preamble until the end of the random access response time window, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts.

[0280] Optionally, the UE obtains part of the configuration of the dynamic RO through the cell broadcast message, combines it with the scheduling information of the dynamic RO included in the random access response message, and determines the time-frequency position of the available dynamic RO and the generation parameters of the Preamble sequence, etc.

[0281] Embodiment 2:

[0282] In this embodiment, the random access method includes the following process:

[0283] Step (21): The same as step (11) of Embodiment 1;

[0284] Step (22): The same as step (12) of Embodiment 1

[0285] Step (23): If the UE successfully receives Msg2 and sends Msg3, and fails when receiving Msg4 (i.e., the contention resolution is unsuccessful); if the UE has saved the scheduling information of the dynamic RO, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts.

[0286] Embodiment 3:

[0287] In this embodiment, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts, where the UE applying the scheduling information of the dynamic RO for subsequent random access attempts includes: within the effective time of the scheduling information of the dynamic RO, the UE considers that both the non-dynamic RO broadcast in the system information and the dynamic RO scheduled by Msg2 can be used for the random access process.

[0288] When the UE performs a new random access resource selection, the UE selects the RO with the most recent time for random access; regardless of whether it belongs to the non-dynamic RO or the dynamic RO scheduled by Msg2.

[0289] Embodiment 4:

[0290] In this embodiment, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts. Among them, the UE applying the scheduling information of the dynamic RO for subsequent random access attempts includes: within the effective time of the scheduling information of the dynamic RO, the UE that has received the scheduling information of the dynamic RO considers the non-dynamic RO broadcast in the system information invalid, that is, only the dynamic RO scheduled by Msg2 can be used for the random access process.

[0291] In this way, the terminals that have received the scheduling information of the dynamic RO and the terminals that have not received the scheduling information of the dynamic RO will use different RO resources for random access. This reduces the random access load on the non-dynamic scheduled RO resources.

[0292] Embodiment Five:

[0293] In this embodiment, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts, where

[0294] the scheduling information of the dynamic RO is carried by the MAC sub-header or MAC CE. An implementation manner of a MAC sub-header carrying the scheduling information of the dynamic RO is as Figure 11 shown.

[0295] In the MAC sub-header, an indication field T is included to indicate that this MAC sub-header carries the scheduling information of the dynamic RO.

[0296] In the MAC sub-header, a dynamic RO configuration field is carried to provide the configuration of the dynamic RO. This configuration can be associated with the configuration provided in the system information: for example, N sets of dynamic RO configurations (N >= 1) are carried in the system information, and the dynamic RO configuration field indicates the number of the currently effective configuration; the dynamic RO configuration field can also carry the effective duration of the dynamic RO configuration.

[0297] It should be noted that the dynamic RO configuration field can be composed of multiple parts to carry different information, such as all or part of the information of the time-frequency resource configuration, or the configuration number, effective duration configuration, etc.

[0298] When the dynamic RO configuration field carries the effective duration configuration, the UE starts timing when it receives this configuration; when the effective time expires, the UE deletes the saved dynamic RO configuration; if the UE receives a new dynamic RO configuration during the timing period, it re-times according to the new effective duration configuration.

[0299] The UE applying the scheduling information of the dynamic RO for subsequent random access attempts also includes: after the UE successfully completes random access (such as successfully receiving Msg4 of the 4-step RACH process), the UE clears or releases the randomly accessed resources dynamically scheduled by the network side. For example, the UE clears the scheduling information of the dynamic RO saved in step (12) of Embodiment One.

[0300] Embodiment Six:

[0301] In this embodiment, the UE applies the scheduling information of the dynamic RO for subsequent random access attempts, where

[0302] the scheduling information of the dynamic RO is carried by the MAC sub-header or MAC CE.

[0303] The dynamic RO configuration field can use the Rbit in the existing MAC sub-header to carry, such as the Rbit in the MAC sub-header of BI.

[0304] For example: One Rbit indicates starting or deactivating the dynamic RO (such as flexible RO) configured in the system information; or multiple Rbits indicate the enabling ratio: such as enabling 0%, 50%, 25%, 75%, 100% of the flexible RO configured in the system information.

[0305] An implementation manner of a MAC sub-header carrying the scheduling information of the dynamic RO is as Figure 12 shown.

[0306] Embodiment Seven:

[0307] In this embodiment, the traditional (legacy) RO and the dynamically scheduled RO are respectively mapped to the SSB. If the network side dynamically schedules the RO (for example, activates the flexible RO), the dynamically scheduled RO will not change the mapping relationship between the legacy RO and the SSB.

[0308] Exemplarily, the mapping relationship between the legacy RO and the SSB is as Figure 13 shown. If the legacy RO and the dynamically scheduled RO are not respectively mapped to the SSB, as Figure 14 shown, it will cause the mapping relationship between the legacy RO and the SSB to change, and the dynamic RO is within the dashed box.

[0309] Since UE1 that does not receive Msg2 does not know whether the network side dynamically schedules the RO; therefore, when it is under the coverage of SSB#2, it will select RO1 to send the preamble corresponding to SSB#2 according to Figure 13 ; while UE2 that has received Msg2 knows that the network side dynamically schedules the RO. Assuming that UE2 can use the legacy RO or the dynamically scheduled RO, therefore, when it is under the coverage of SSB#4, it will select according to Figure 14Select RO1 to send the preamble corresponding to SSB#4. When the network side receives the preamble from RO1, it cannot determine whether the received preamble corresponds to SSB#2 or SSB#4. Therefore, the legacy RO and the dynamically scheduled RO are mapped to the SSBs respectively, that is, regardless of whether the network side schedules the dynamic RO, the mapping relationship between the legacy RO and the SSB remains unchanged. In this way, the network side can uniquely determine the SSB where the UE is located according to the received Msg1. By way of example, the mapping relationship between the legacy RO and the SSB and the mapping relationship between the dynamically scheduled RO and the SSB are as Figure 15 shown.

[0310] In other words, the mapping relationship between the legacy RO and the SSB and the mapping relationship between the dynamically scheduled RO and the SSB are independent of each other; when the UE determines the mapping relationship between the legacy RO and the SSB, it is assumed that the dynamically scheduled RO is not configured or scheduled; similarly, when the UE determines the mapping relationship between the dynamically scheduled RO and the SSB, it is assumed that the legacy RO is not configured.

[0311] Embodiment Eight:

[0312] In this embodiment, in addition to in the random access response message, the configuration information of the dynamic RO can also be notified to the UE during the paging process. The signaling or message carrying the configuration information of the dynamic RO includes but is not limited to: paging scheduling signaling (paging DCI) or paging message, paging early indication (PEI), paging wake-up signal, low-power wake-up signal, paging short message, etc.; because the paged terminal needs to initiate a RACH process to access the network. Therefore, if the UE parses one of the above paging-related signaling and finds that the configuration information of the dynamic RO in the paging-related signaling indicates that the dynamic RO is scheduled, the UE can use the dynamic RO for random access.

[0313] In addition, the UE can periodically monitor paging messages to determine whether it is paged. If the paging message itself or the paging scheduling signaling corresponding to the paging message indicates that the dynamic RO is scheduled, even if the UE itself is not paged, it can record the configuration information of the dynamic RO and use the dynamic RO to initiate paging when paging is initiated next time. If the paging message itself or the paging scheduling signaling corresponding to the paging message does not indicate that the dynamic RO is scheduled, the UE deletes the saved configuration information of the dynamic RO. Optionally, the configuration information of the dynamic RO saved by the UE is valid for a certain period of time. If the validity period of the configuration information of the dynamic RO expires, the UE deletes the saved configuration information of the dynamic RO.

[0314] Embodiment Nine:

[0315] In this embodiment, in addition to in the random access response message, the scheduling information of the dynamic RO can also be carried in the common DCI; for example, the protocol stipulates a scheduling ID X for the scheduling of this dynamic RO. When the network sends scheduling signaling (such as DCI), and the scheduling signaling indicates that the scheduled ID is X, the UE that receives the scheduling signaling determines the RO dynamically scheduled by the network side according to the indication in the scheduling signaling.

[0316] Embodiment Ten:

[0317] In this embodiment, the dynamically scheduled RO can be applicable only to UEs with specific characteristics, such as:

[0318] The UE with specific characteristics can include at least one of the following:

[0319] UEs with the number of RACH attempts lower than, equal to, or higher than a certain threshold;

[0320] UEs with the preamble transmission power lower than, equal to, or higher than a certain threshold;

[0321] UEs that measure the RSSI / RSRQ of the serving cell lower than, equal to, or higher than a certain threshold;

[0322] UEs in a specific RRC state, such as idle state or inactive state or connected state UEs;

[0323] UEs that support specific capabilities, such as UEs that support access to satellites (such as Non-Terrestrial Network (NTN)), UEs that support the Reduced Capability (RedCap) feature, etc.;

[0324] UEs for which RACH is triggered by a specific service type, such as: data, signaling, etc.

[0325] It should be noted that for the configuration information of the terminal to which the dynamically scheduled RO applies, the network side can configure it for the terminal through system information; or it can notify the terminal through a dynamic scheduling signaling, and the dynamic scheduling signaling includes at least one of the following: Msg2, MsgB, paging message, DCI for ID X.

[0326] In the related art, when congestion occurs in the random access channel, the network side configures a longer Backoff time to discretize the time for the terminal to initiate random access again, reducing the RACH load; however, it will introduce a longer waiting time for the next RACH attempt, reducing the user experience. In the embodiments of the present application, when congestion occurs in the random access channel, the network side dynamically schedules more random access opportunities (i.e., RO) through a random access response message (such as Msg2 or Msg B), for terminals that have failed or been unsuccessful in random access to perform random access in a short time, avoiding the introduction of a longer waiting time for the next RACH attempt.

[0327] In the embodiments of the present application, the Msg2 or Msg B is used to carry information related to the dynamic random access opportunity, supporting on-demand scheduling, that is, the scheduling information is only sent when the network side detects RACH congestion; at the same time, it can ensure that the information related to the dynamic random access opportunity is only received by the terminals that need to perform random access re-attempts; avoiding disturbing other terminals that do not need to know this information.

[0328] For the random access method provided by the embodiments of the present application, the execution subject can be a random access device. In the embodiments of the present application, taking the random access device executing the random access method as an example, the random access device provided by the embodiments of the present application is described.

[0329] Please refer to Figure 16 , Figure 16 which is a structural diagram of a random access device provided by the embodiments of the present application. The terminal includes the random access device, as Figure 16 shown, the random access device 300 includes:

[0330] A first receiving module 301, configured to receive a target message sent by a network side device, where the target message carries physical random access channel transmission opportunity RO scheduling information;

[0331] An access module, configured to determine a target RO based on the RO scheduling information and perform random access based on the target RO;

[0332] Wherein, the target message includes at least one of the following:

[0333] Random access response message;

[0334] Paging related message;

[0335] Common Downlink Control Information DCI.

[0336] Optionally, the RO scheduling information includes at least one of the following:

[0337] The first configuration information of the RO;

[0338] The time position information of the RO;

[0339] The frequency position information of the RO;

[0340] The repetition period information of the RO;

[0341] The effective duration information of the RO;

[0342] The first indication information for indicating whether the RO is effective.

[0343] Optionally, the target message includes a random access response message, and the access module is specifically configured to:

[0344] When the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information and sends a preamble for the next random access based on the target RO.

[0345] Optionally, the device further includes:

[0346] A storage module for storing the RO scheduling information;

[0347] The access module is specifically configured to:

[0348] When the terminal determines that the random access fails, if the terminal stores the RO scheduling information, the terminal determines a target RO based on the stored RO scheduling information and sends a preamble for the next random access based on the target RO.

[0349] Optionally, the terminal determines that the random access fails, including at least one of the following:

[0350] If the terminal does not detect a random access response message containing a match for the preamble identifier sent by the terminal in the random access response message corresponding to the random access response time window, the terminal determines that the random access fails;

[0351] If the terminal fails to resolve the contention, the terminal determines that the random access fails.

[0352] Optionally, the device further includes:

[0353] A second receiving module for receiving system information, where the system information carries the second configuration information of the target RO;

[0354] The access module is specifically configured to:

[0355] Determine the target RO based on the RO scheduling information and the second configuration information, and perform random access based on the target RO.

[0356] Optionally, the access module is specifically configured to:

[0357] Select an RO from the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried in the system information;

[0358] Perform random access based on the selected target RO.

[0359] Optionally, the target RO is the next RO closest to the current time among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information.

[0360] Optionally, the access module is specifically configured to:

[0361] Select an RO from the ROs corresponding to the RO scheduling information;

[0362] Perform random access based on the selected target RO.

[0363] Optionally, the access module is specifically configured to:

[0364] Select an RO from the ROs corresponding to the RO scheduling information within the effective time corresponding to the effective duration information of the ROs corresponding to the RO scheduling information;

[0365] Perform random access based on the selected target RO.

[0366] Optionally, the target message includes a target media access control (MAC) sub-header or a target MAC control element (CE), and the target MAC sub-header or target MAC CE carries the RO scheduling information.

[0367] Optionally, the target MAC sub-header or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC sub-header or target MAC CE.

[0368] Optionally, the RO scheduling information includes third indication information, and the third indication information is used to indicate at least one RO that is effective among the ROs corresponding to the third configuration information carried in the system information.

[0369] Optionally, the paging-related message includes at least one of the following:

[0370] Paging scheduling signaling; paging message; paging indication signal; paging wake-up signal; low-power wake-up signal; paging short message.

[0371] Optionally, the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information are respectively mapped to the synchronization signal block SSB.

[0372] Optionally, the target message includes a common DCI, the common DCI carries RO scheduling information, and the RO scheduling information includes a scheduling identifier. Specifically, the access module is configured to:

[0373] Determine a target RO based on the RO corresponding to the scheduling identifier, and perform random access based on the target RO.

[0374] Optionally, the access module is specifically configured to:

[0375] In the case of determining that the terminal is a terminal of a target type, determine a target RO based on the RO scheduling information, and perform random access based on the target RO;

[0376] Wherein, the terminal determines whether the terminal is a terminal of the target type based on at least one of the following:

[0377] The number of random access attempts of the terminal; the preamble transmission power of the terminal; the received signal strength indication RSSI of the serving cell measured by the terminal; the reference signal received quality RSRQ of the serving cell measured by the terminal; the radio resource control RRC state of the terminal; the capability or type of the terminal; the service trigger type for which the terminal performs random access.

[0378] The random access device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0379] The random access device provided in the embodiments of the present application can implement Figure 9 Each process implemented by the method embodiment, and achieves the same technical effect. To avoid repetition, it will not be elaborated here.

[0380] Please refer to Figure 17 , Figure 17 is a structural diagram of a random access device provided in an embodiment of the present application. The network side device includes the random access device. As Figure 17 shown, the random access device 400 includes:

[0381] A sending module 401, configured to send a target message to a terminal, where the target message carries physical random access channel transmission opportunity (RO) scheduling information; the RO scheduling information is used for random access;

[0382] Wherein, the target message includes at least one of the following:

[0383] A random access response message;

[0384] A paging-related message;

[0385] A common DCI.

[0386] The random access device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0387] The random access device provided in the embodiments of the present application can implement Figure 10 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described here again.

[0388] Optionally, as Figure 18 shown, the embodiments of the present application further provide a communication device 500, including a processor 501 and a memory 502. A program or instruction that can run on the processor 501 is stored on the memory 502. For example, when the communication device 500 is a terminal, when the program or instruction is executed by the processor 501, each step of the above-mentioned random access method embodiments applied to the terminal is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again. When the communication device 500 is a network-side device, when the program or instruction is executed by the processor 501, each step of the above-mentioned random access method embodiments applied to the network-side device is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again.

[0389] The embodiments of the present application further provide a terminal, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instruction to implement the steps in the method embodiments as Figure 9 shown. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiments. Each implementation process and implementation manner of the above method embodiments can be applied to this terminal embodiment, and the same technical effects can be achieved.

[0390] Specifically, Figure 19Schematic diagram of the hardware structure of a terminal according to an embodiment of the present application.

[0391] The terminal 600 includes, but is not limited to, at least some components such as a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, and a processor 610.

[0392] Those skilled in the art can understand that the terminal 600 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 610 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 19 The terminal structure shown does not limit 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.

[0393] It should be understood that in the embodiment of the present application, the input unit 604 may include a Graphics Processing Unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes the image data of static pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. The other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0394] In the embodiment of the present application, after receiving downlink data from a network side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network side device. Generally, the radio frequency unit 601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0395] The memory 609 can be used to store software programs or instructions and various data. The memory 609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area can store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 609 can include volatile memory or non-volatile memory, or the memory 609 can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synch link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 609 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0396] The processor 610 may include one or more processing units; optionally, the processor 610 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor 610 either.

[0397] Among them, the radio frequency unit 601 is used for: receiving a target message sent by a network-side device, where the target message carries physical random access channel transmission opportunity RO scheduling information;

[0398] The processor 610 is used for: determining a target RO based on the RO scheduling information, and performing random access based on the target RO;

[0399] Among them, the target message includes at least one of the following:

[0400] Random access response message;

[0401] Paging-related message;

[0402] Common downlink control information DCI.

[0403] Optionally, the RO scheduling information includes at least one of the following:

[0404] The first configuration information of the RO;

[0405] The time position information of the RO;

[0406] The frequency position information of the RO;

[0407] The repetition period information of the RO;

[0408] The effective duration information of the RO;

[0409] The first indication information for indicating whether the RO is effective.

[0410] Optionally, the target message includes a random access response message, and the processor 610 is specifically configured to:

[0411] When the terminal determines that the random access fails, determine a target RO based on the RO scheduling information, and perform the next random access preamble transmission based on the target RO.

[0412] Optionally, the processor 610 is further configured to: store the RO scheduling information;

[0413] The processor 610 is specifically further configured to:

[0414] When the terminal determines that the random access fails, if the terminal stores RO scheduling information, determine a target RO based on the stored RO scheduling information, and perform the next random access preamble transmission based on the target RO.

[0415] Optionally, the terminal determines that the random access fails, including at least one of the following:

[0416] If the terminal does not detect a random access response message containing a match with the preamble identifier sent by the terminal in the random access response message corresponding to the random access response time window, determine that the random access fails;

[0417] If the terminal fails to resolve the contention, the terminal determines that the random access fails.

[0418] Optionally, the radio frequency unit 601 is further configured to: receive system information, where the system information carries second configuration information of the target RO;

[0419] The processor 610 is specifically configured to:

[0420] Determine the target RO based on the RO scheduling information and the second configuration information, and perform random access based on the target RO.

[0421] Optionally, the processor 610 is specifically configured to:

[0422] Select an RO from the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried in the system information;

[0423] Perform random access based on the selected target RO.

[0424] Optionally, the target RO is the next RO closest to the current time among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information.

[0425] Optionally, the processor 610 is specifically configured to:

[0426] Select an RO from the ROs corresponding to the RO scheduling information;

[0427] Perform random access based on the selected target RO.

[0428] Optionally, the processor 610 is specifically configured to:

[0429] Select an RO from the ROs corresponding to the RO scheduling information within the effective time corresponding to the effective duration information of the ROs corresponding to the RO scheduling information;

[0430] Perform random access based on the selected target RO.

[0431] Optionally, the target message includes a target media access control (MAC) sub-header or a target MAC control element (CE), and the target MAC sub-header or target MAC CE carries the RO scheduling information.

[0432] Optionally, the target MAC sub-header or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC sub-header or target MAC CE.

[0433] Optionally, the RO scheduling information includes third indication information, and the third indication information is used to indicate at least one RO that is effective among the ROs corresponding to the third configuration information carried in the system information.

[0434] Optionally, the paging-related message includes at least one of the following:

[0435] Paging scheduling signaling; paging message; paging indication signal; paging wake-up signal; low-power wake-up signal; paging short message.

[0436] Optionally, the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information are respectively mapped to the synchronization signal block SSB.

[0437] Optionally, the target message includes a common DCI, the common DCI carries RO scheduling information, and the RO scheduling information includes a scheduling identifier. The processor 610 is specifically configured to:

[0438] Determine a target RO based on the RO corresponding to the scheduling identifier, and perform random access based on the target RO.

[0439] Optionally, the processor 610 is specifically configured to:

[0440] When it is determined that the terminal is a target type of terminal, determine a target RO based on the RO scheduling information, and perform random access based on the target RO;

[0441] Wherein, the terminal determines whether the terminal is the target type of terminal based on at least one of the following:

[0442] The number of random access attempts of the terminal; the preamble transmission power of the terminal; the received signal strength indication RSSI of the serving cell measured by the terminal; the reference signal received quality RSRQ of the serving cell measured by the terminal; the radio resource control RRC state of the terminal; the capability or type of the terminal; the service trigger type for the terminal to perform random access.

[0443] It can be understood that the implementation processes of the various implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiment Figure 5 and achieve the same or corresponding technical effects. To avoid repetition, it will not be elaborated here.

[0444] Specifically, the terminal in the embodiment of the present application further includes: instructions or programs stored in the memory 609 and executable on the processor 610. The processor 610 calls the instructions or programs in the memory 609 to execute Figure 16 the methods executed by the respective modules shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0445] The embodiment of the present application further provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement as Figure 10Steps of the method embodiments shown. This network-side device embodiment corresponds to the above-described random access method embodiments applied to network-side devices. Each implementation process and implementation manner of the above method embodiments can be applied to this network-side device embodiment and can achieve the same technical effects.

[0446] Specifically, an embodiment of the present application further provides a network-side device. As Figure 20 shown, the network-side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information through the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be sent and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and then sends it out through the antenna 701.

[0447] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 703, and the baseband device 703 includes a baseband processor.

[0448] The baseband device 703 may include, for example, at least one baseband board, and a plurality of chips are provided on the baseband board. As Figure 20 shown, one of the chips is, for example, a baseband processor, which is connected to the memory 705 through a bus interface to call the program in the memory 705 and execute the network device operations shown in the above method embodiments.

[0449] The network-side device may further include a network interface 706, and this interface is, for example, a Common Public Radio Interface (CPRI).

[0450] Specifically, the network-side device 700 of the embodiment of the present application further includes: instructions or programs stored on the memory 705 and executable on the processor 704. The processor 704 calls the instructions or programs in the memory 705 to execute Figure 17 the methods executed by the modules shown and achieve the same technical effects. To avoid repetition, they will not be elaborated here.

[0451] An embodiment of the present application further provides a readable storage medium. Programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, each process of the above-described random access method embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0452] Among them, the processor 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 disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0453] Another embodiment of the present application 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 each process of the above embodiment of the random access method, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

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

[0455] Another embodiment of the present application provides a computer program / program product. The computer program / program product is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the above embodiment of the random access method, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0456] The embodiments of the present application further provide a random access system, including: a terminal and a network-side device. The terminal can be used to execute the steps of the random access method applied to the terminal as described above, and the network-side device can be used to execute the steps of the random access method applied to the network-side device as described above.

[0457] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0458] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0459] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A random access method, characterized in that, it includes: The terminal receives a target message sent by a network-side device, and the target message carries physical random access channel transmission opportunity RO scheduling information; The terminal determines a target RO based on the RO scheduling information, and performs random access based on the target RO; Wherein, the target message includes at least one of the following: Random access response message; Paging-related message; Common downlink control information DCI.

2. The method according to claim 1, characterized in that, The RO scheduling information includes at least one of the following: The first configuration information of the RO; The time position information of the RO; The frequency position information of the RO; The repetition period information of the RO; The effective duration information of the RO; The first indication information for indicating whether the RO is effective.

3. The method according to claim 1 or 2, characterized in that, The target message includes a random access response message. The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: When the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information and sends a preamble for the next random access based on the target RO.

4. The method according to claim 3, characterized in that, After the terminal receives the target message sent by the network-side device, the method further includes: The terminal stores the RO scheduling information; When the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information and sends a preamble for the next random access based on the target RO, including: When the terminal determines that the random access fails, if the terminal stores the RO scheduling information, the terminal determines a target RO based on the stored RO scheduling information and sends a preamble for the next random access based on the target RO.

5. The method according to claim 4, characterized in that, The terminal determines that the random access fails, including at least one of the following: If the terminal does not detect a random access response message containing a match with the preamble identifier sent by the terminal in the random access response message corresponding to the random access response time window, the terminal determines that the random access fails; If the terminal fails to resolve the contention successfully, the terminal determines that the random access fails.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The terminal receives system information, and the system information carries the second configuration information of the target RO; The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: The terminal determines the target RO based on the RO scheduling information and the second configuration information, and performs random access based on the target RO.

7. The method according to any one of claims 1-6, characterized in that, The terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: The terminal selects an RO from among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried in the system information. The terminal performs random access based on the selected target RO.

8. The method according to claim 7, wherein, the target RO is the next RO closest to the current time among the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information.

9. The method according to any one of claims 1-6, wherein, the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: the terminal selects an RO from among the ROs corresponding to the RO scheduling information; the terminal performs random access based on the selected target RO.

10. The method according to claim 9, wherein, the terminal selects an RO from among the ROs corresponding to the RO scheduling information, including: within the effective time corresponding to the effective duration information of the ROs corresponding to the RO scheduling information, the terminal selects an RO from among the ROs corresponding to the RO scheduling information.

11. The method according to any one of claims 1-10, wherein, the target message includes a target media access control (MAC) sub-header or a target MAC control element (CE), and the target MAC sub-header or target MAC CE carries the RO scheduling information.

12. The method according to claim 11, wherein, the target MAC sub-header or target MAC CE carries second indication information for indicating the type of the target MAC sub-header or target MAC CE.

13. The method according to any one of claims 1-12, wherein, the RO scheduling information includes third indication information for indicating at least one RO that is effective among the ROs corresponding to the third configuration information carried in the system information.

14. The method according to any one of claims 1-13, wherein, the paging-related message includes at least one of the following: paging scheduling signaling; paging message; paging indication signal; paging wake-up signal; low-power wake-up signal; paging short message.

15. The method according to any one of claims 1-14, wherein, the ROs corresponding to the RO scheduling information and the ROs corresponding to the third configuration information carried in the system information are respectively mapped to synchronization signal blocks (SSBs).

16. The method according to any one of claims 1-15, wherein, the target message includes a common downlink control information (DCI), the common DCI carries the RO scheduling information, the RO scheduling information includes a scheduling identifier, and the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: the terminal determines the target RO based on the RO corresponding to the scheduling identifier and performs random access based on the target RO.

17. The method according to any one of claims 1-16, wherein, the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO, including: When it is determined that the terminal is a terminal of a target type, the terminal determines a target RO based on the RO scheduling information and performs random access based on the target RO; wherein, the terminal determines whether the terminal is a terminal of the target type based on at least one of the following: the number of random access attempts of the terminal; the preamble transmission power of the terminal; the received signal strength indication RSSI of the serving cell measured by the terminal; the reference signal received quality RSRQ of the serving cell measured by the terminal; the radio resource control RRC state of the terminal; the capability or type of the terminal; the service trigger type for the terminal to perform random access.

18. A random access method, characterized in that, it includes: The network side device sends a target message to the terminal, and the target message carries physical random access channel transmission opportunity RO scheduling information; the RO scheduling information is used for random access; wherein, the target message includes at least one of the following: random access response message; paging related message; common DCI.

19. A random access device, characterized in that, The terminal includes the random access device, and the device includes: a first receiving module, configured to receive a target message sent by a network side device, where the target message carries physical random access channel transmission opportunity RO scheduling information; an access module, configured to determine a target RO based on the RO scheduling information and perform random access based on the target RO; wherein, the target message includes at least one of the following: random access response message; paging related message; common downlink control information DCI.

20. A random access device, characterized in that, The network side device includes the random access device, and the device includes: a sending module, configured to send a target message to the terminal, where the target message carries physical random access channel transmission opportunity RO scheduling information; the RO scheduling information is used for random access; wherein, the target message includes at least one of the following: random access response message; paging related message; common DCI.

21. A terminal, characterized in that, It includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the random access method according to any one of claims 1-17 are implemented.

22. A network side device, characterized in that, It includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the random access method according to claim 18 are implemented.

23. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps of the random access method according to any one of claims 1-17, or to implement the steps of the random access method according to claim 18.

24. A readable storage medium, characterized in that, The program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, it implements the steps of the random access method described in any one of claims 1-17, or implements the steps of the random access method described in claim 18.

Images