Random access method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses a random access method and apparatus, a terminal, and a network side device. The random access method of embodiments of the present application comprises: a terminal receives a target message sent by a network side device, the target message carrying physical random access channel transmission occasion (RO) scheduling information; and the terminal determines a target RO on the basis of the RO scheduling information, and performs random access on the basis of the target RO, wherein the target message comprises at least one of the following: a random access response message; a paging-related message; and common downlink control information (DCI).

Description

Random access method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202311567554.5 filed in China on November 22, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a random access method, apparatus, terminal and network-side equipment. Background Art

[0004] In the related art, during the random access process of a terminal, there is a random backoff mechanism as follows: if congestion occurs in the random access channel, the network side will send a backoff indication to the terminal, indicating a maximum waiting time T; if the terminal does not receive a response to the preamble code (preamble) sent by itself in the random access response receiving window or the terminal determines that the random access contention resolution has failed, the terminal selects a duration Twait with equal probability between 0 and the maximum waiting time T according to the Backoff indication. After waiting for the duration Twait, the terminal initiates the next random access attempt. However, the above random backoff mechanism will cause the terminal to wait for a long time before initiating the next random access attempt. Summary of the Invention

[0005] The embodiments of the present application provide a random access method, apparatus, terminal, and network-side device, which can solve the problem that a terminal has to wait for a long time before initiating the next random access attempt.

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

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

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

[0009] The target message includes at least one of the following:

[0010] Random access response message;

[0011] Paging related messages;

[0012] Common downlink control information DCI.

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

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

[0015] The target message includes at least one of the following:

[0016] Random access response message;

[0017] Paging related messages;

[0018] Public DCI.

[0019] According to a third aspect, a random access device is provided. The terminal includes the random access device, and the device includes:

[0020] A first receiving module 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;

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

[0022] The target message includes at least one of the following:

[0023] Random access response message;

[0024] Paging related messages;

[0025] Common downlink control information DCI.

[0026] In a fourth aspect, a random access apparatus is provided, wherein a network-side device includes the random access apparatus, and the apparatus includes:

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

[0028] The target message includes at least one of the following:

[0029] Random access response message;

[0030] Paging related messages;

[0031] Public DCI.

[0032] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0033] In a sixth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0034] In a seventh aspect, a terminal is provided, comprising a processor and a communication interface, wherein:

[0035] The communication interface is used to: receive a target message sent by a network side device, wherein the target message carries physical random access channel transmission opportunity RO scheduling information;

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

[0037] The target message includes at least one of the following:

[0038] Random access response message;

[0039] Paging related messages;

[0040] Common downlink control information DCI.

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

[0042] Sending a target message to the terminal, the target message carrying physical random access channel transmission opportunity RO scheduling information; the RO scheduling information is used for random access;

[0043] The target message includes at least one of the following:

[0044] Random access response message;

[0045] Paging related messages;

[0046] Public DCI.

[0047] In a ninth aspect, a random access system is provided, comprising: a terminal and a network side device, wherein 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.

[0048] In the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.

[0049] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0050] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and 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.

[0051] In an embodiment of the present application, a terminal receives a target message sent by a network device, the target message carrying physical random access channel (RO) 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. The target message includes at least one of the following: a random access response message; a paging-related message; or common downlink control information (DCI). In this way, the network device carries the RO scheduling information through at least one of the random access response message, the paging-related message, and the DCI. This RO scheduling information can dynamically schedule more ROs for the terminal to perform random access, thereby shortening the waiting time for the terminal to initiate a random access attempt. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0053] FIG2 is a schematic diagram of a random access process in the related art;

[0054] FIG3 is a schematic diagram of a format of a RAR message in the related art;

[0055] FIG4 is a schematic diagram of a format of a MAC RAR unit in the related art;

[0056] FIG5 is a schematic diagram of a format of a MAC subheader in the related art;

[0057] FIG6 is a second schematic diagram of a random access process in the related art;

[0058] FIG7 is a schematic diagram of a correlation relationship between an RO and an SSB in the related art;

[0059] FIG8 is a second schematic diagram of the association relationship between an RO and an SSB in the related art;

[0060] FIG9 is a flowchart of a random access method according to an embodiment of the present application;

[0061] FIG10 is a second flowchart of a random access method provided in an embodiment of the present application;

[0062] FIG11 is a schematic diagram of a format of a MAC subheader according to an embodiment of the present application;

[0063] FIG12 is a second schematic diagram of a MAC subheader format provided in an embodiment of the present application;

[0064] FIG13 is a schematic diagram of one of the association relationships between an RO and an SSB provided in an embodiment of the present application;

[0065] FIG14 is a second schematic diagram of the association relationship between an RO and an SSB provided in an embodiment of the present application;

[0066] FIG15 is a third schematic diagram of the association relationship between an RO and an SSB provided in an embodiment of the present application;

[0067] FIG16 is a structural diagram of a random access device according to an embodiment of the present application;

[0068] FIG17 is a second structural diagram of a random access device provided in an embodiment of the present application;

[0069] FIG18 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0070] FIG19 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0071] Figure 20 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0073] The terms "first," "second," and so on, used in the specification and claims of this application are used to distinguish similar objects, not to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein. Furthermore, the objects distinguished by "first" and "second" generally refer to a class of objects and do not limit the number of objects. For example, the first object can be one or more. Furthermore, "or" in the specification and claims refers to at least one of the connected objects. For example, "A or B" encompasses three options: Option 1: includes A but not B; Option 2: includes B but not A; and Option 3: includes both A and B. The term "instruction" in the specification and claims of this application can be either an explicit instruction or an implicit instruction. An explicit instruction can be understood as an instruction in which the sender explicitly informs the recipient of the required operation or requested result. An implicit instruction can be understood as an instruction in which the recipient makes a judgment based on the sender's instruction and determines the required operation or requested result based on the judgment result.

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

[0075] FIG1 shows a block diagram of a wireless communication system applicable to embodiments of the present application. The wireless communication system includes a terminal 11 and a network-side device 12 . The terminal 11 may 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 (Wearable Device), a vehicle user equipment (VUE), a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, etc. The wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side device 12 may include an access network device or a core network device, wherein the access network device may 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 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 a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a transmitting and receiving point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0076] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0077] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

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

[0079] 1.1. 4-step random access process

[0080] The 4-step random access process is shown in Figure 2.

[0081] The process of contention random access is mainly divided into four steps:

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

[0083] It should be noted that the terminal selects the sending time-frequency resource (ie RO) and preamble code of Msg1 from a random access resource set broadcast by the network side; therefore, there is a possibility of Msg1 collision, that is, multiple terminals select related RO to send the same preamble code.

[0084] After sending Msg1, the terminal calculates the identification information (such as the Random Access Radio Network Temporary Identity (RA-RNTI)) for scheduling Msg2 on the network side based on the sending time and frequency of Msg1. After sending Msg1, the terminal monitors the downlink channel within a preconfigured time window (such as the Random Access Response window (RAR window)) to obtain feedback information Msg2 from the network side.

[0085] 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 Timing Advance Command); uplink transmission authorization information (such as Uplink (UL) Grant); backoff information (such as Backoff Indicator); and temporary terminal identification information (such as Temporary Cell RNTI (C-RNTI)). If the terminal does not receive the Random Access Preamble IDentifier (RAPID) corresponding to the Msg1 it sent before the end of the RAR window, it is considered that the RAR reception has failed. There are two cases:

[0086] (1) The user equipment (UE) does not receive a RAR message during the RAR window;

[0087] (2) During the RAR window, the UE receives a RAR Message, but the RAR Message does not contain the RAPID corresponding to the Msg1 it sent.

[0088] If the second case occurs and the RAR Message contains fallback information, the UE determines the time to make another RACH attempt based on the fallback information. If the first case occurs, or if the second case occurs and the RAR Message received by the UE does not contain fallback information, the UE may make the next random access attempt at the next available physical random access channel transmission opportunity (PRACH transmission Occasion or PRACH Occasion, RO).

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

[0090] Msg4: Contention resolution message. The terminal can determine whether random access is successful based on Msg4.

[0091] The terminal starts a contention resolution timer when or after sending Msg3. If Msg4 is not successfully received before the contention resolution timer times out, the UE considers that Msg4 reception has failed.

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

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

[0094] In the 4-step random access process, the format of RACH message (Msg) 2 (such as RAR message) is shown in FIG3 .

[0095] The RAR message contains two formats of subPDU and padding:

[0096] A1 Type:

[0097] SubPDU containing BI: contains only a 1-byte subheader, which is used to carry RACH fallback information;

[0098] A2 type:

[0099] SubPDUs containing RAPID can be divided into two types: one containing only a 1-byte subheader and the other containing a 1-byte subheader and a MAC RAR unit. This type of subPDU is used to carry a response to a detected preamble.

[0100] Padding: It contains all padding bits.

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

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

[0103] The meanings of the various indication fields (or fields) in the MAC subheader of the A1 / A2 subPDU are as follows:

[0104] E: If the E field (or domain) is set to 1, this subPDU is not the last subPDU in the RAR message, that is, there are other subPDUs behind it; if the E field is set to 0, this subPDU is the last subPDU. 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 one other MAC subPDU behind it. The Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU. The E field is set to 1 to indicate at least another MAC subPDU follows. 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.

[0105] 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).

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

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

[0108] 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 and is 6 bits long. 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 element is not included in the MAC subPDU.

[0109] For a MAC subheader containing E / T / RAPID, if the corresponding MAC RAR is used, the corresponding MAC RAR unit format is shown in FIG4 .

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

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

[0112] The BI field has 16 values ​​ranging from 0 to 15, and each BI field value number corresponds to a fallback time length.

[0113] 1.3. Backoff Parameter Values

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

[0115] Table 1: Backoff Parameter values

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

[0117] If the UE receives a Random Access Response message within the RAR window and it does not contain a MAC subPDU corresponding to the Backoff Indicator, the UE sets the local variable PREAMBLE_BACKOFF to 0ms;

[0118] If 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, it re-does the Random Access resource selection process, i.e., starts the next RACH attempt.

[0119] 2-Step RACH Process

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

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

[0122] Step (2): The UE triggers the 2-step RACH procedure and sends a request message (MsgA) to the network, for example, via the Physical Uplink Shared Channel (PUSCH) and a preamble. When or after sending MsgA, the UE starts the msgB-ResponseWindow timer and listens for MsgB. The duration of the msgB-ResponseWindow timer is preconfigured by the network.

[0123] Step (3): The network sends a confirmation message (MsgB) to the UE. If the UE fails to receive MsgB, the UE resends Msg1, resends MsgA, or sends Msg3, depending on the circumstances of the UE's failure to receive MsgB. Failure to receive MsgB means that the contention resolution identifier (ID) corresponding to the UE's own contention resolution identifier in the sent MsgA is not received within the msgB-ResponseWindow.

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

[0125] The configuration parameters for 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 multiplex (FDM) PRACH transmission occasions (PRACH Occasions, ROs) at a time location for a PRACH transmission. The number of ROs that can be FDMed at a time can be: {1, 2, 4, 8}, which is configured and determined by the higher-layer parameter Msg1-FDM.

[0126] 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. RA ∈{0,1,…,M-1}, where M is equal to the high-level parameter Msg1-FDM. At the time of initial access, the PRACH frequency domain resource n RA The PRACH frequency domain resource n is numbered in ascending order starting from the lowest frequency RO resource in the initial active uplink bandwidth part. Otherwise, the PRACH frequency domain resource n is RA The RO resources are numbered in ascending order starting from the lowest frequency RO resource in the active uplink bandwidth part. For example, in Figure 7, the number of FDM ROs at a time is 8 (Msg1-FDM=8), and the RO resources are numbered from RO#0 to RO#7 in ascending order of frequency.

[0127] In NR, there is an association between the RO and the actual synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) sent. The RO is associated with the SSB in the order of frequency domain (from low frequency to high frequency) 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. For example, the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is as follows:

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

[0129] After all SSBs have completed one round of association with the RO, an SSB-RO mapping cycle is formed. An SSB-RO association period may include one or more SSB-RO mapping cycles. An SSB-RO association pattern period may include one or more SSB-RO association periods. The SSB-RO mapping is repeated based on the association pattern period, and the maximum association pattern period is 160ms.

[0130] Typically, a base station can use different beams to transmit different SSBs. The number of SSBs is configured using the ssb-PositionsInBurst parameter. For FR2, the maximum number of SSBs is 64. Based on the strength of the received downlink beam or SSB, the UE selects the RO or RO and preamble combination associated with a high-signal SSB and sends Msg1. The network then determines the UE's selected SSB based on the RO or RO and preamble combination of the received preamble. Msg2 is then sent on the downlink beam corresponding to the SSB to ensure downlink signal reception quality.

[0131] Taking Figure 7 as an example, the number of FDM ROs at a given moment is 8, and the number of SSBs actually transmitted is 4, namely SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with two ROs. If the UE determines to send PRACH / Mg1 on the RO corresponding to SSB#0, the UE selects an RO between RO#0 and RO#1 to send the PRACH.

[0132] Taking Figure 8 as an example, the number of FDM ROs at a given moment is 2, and the number of SSBs actually transmitted is 8, namely SSB#0, SSB#1, ..., SSB#7, with one RO associated with every two SSBs. When multiple SSBs share a 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 RO#0 in Figure 8 as an example, RO#0 has a total of 60 preambles, of which preambles with indices 0 to 29 are associated with SSB#0, and preambles with indices 30 to 59 are associated with SSB#1.

[0133] It should be noted that each square in FIG8 represents an RO, and the SSB marked in the square refers to the SSB associated with this RO.

[0134] Before sending PRACH, the UE first selects an SSB with RSRP higher than a threshold based on the reference signal received power (RSRP) of the received beam (such as SSB). If the RSRP of multiple SSBs is higher than the threshold, the terminal can select any SSB with RSRP higher than the threshold. If there is no SSB with RSRP higher than the threshold, the UE selects an SSB based on the implementation.

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

[0136] For example: In the example shown in Figure 7, assuming that the UE selects SSB#1, the UE can select one from RO#2 and RO#3 to send PRACH / Msg1; in the example shown in Figure 8, if the UE selects SSB#1, the UE can select the available RO closest to the current time in the RO 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 shown in Figure 8, one RO is associated with two SSBs, so in the available preamble set associated with the SSB in one RO, the preamble will be divided into two subsets, each subset corresponding to one SSB. The UE will select a preamble sequence in the preamble subset corresponding to the selected SSB for sending PRACH / Msg1.

[0137] The random access method, apparatus, terminal, and network-side device provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0138] Referring to FIG. 9 , FIG. 9 is a flowchart of a random access method provided in an embodiment of the present application. As shown in FIG. 9 , the random access method includes the following steps:

[0139] Step 101: The terminal receives a target message sent by a network-side device, where the target message carries physical random access channel transmission opportunity (RO) scheduling information.

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

[0141] The target message includes at least one of the following:

[0142] Random access response message;

[0143] Paging related messages;

[0144] Public downlink control information (Downlink Control Information, DCI).

[0145] The RO scheduling information may include one or more of the following: first configuration information of the RO, time domain or frequency domain location information of the RO, repetition period information of the RO, validity duration information of the RO, or first indication information, etc. This embodiment is not limited to this. Any information that can be used to schedule the RO can be used as the RO scheduling information. The first indication information is used to indicate whether the RO is valid. The validity duration information can indicate the length of time the RO is considered available.

[0146] The RO corresponding to the RO scheduling information may be used to determine a target RO. The terminal may determine the target RO according to the RO corresponding to the RO scheduling information, and perform random access based on the target RO.

[0147] The RO corresponding to the RO scheduling information can be understood as a dynamic RO. A dynamic RO can also be described as an additional RO, a flexible RO, or a dynamic RO. A dynamic RO is a newly introduced RO that is different from a legacy RO (i.e., an RO that is not scheduled via a target message).

[0148] The terminal determining a target RO based on the RO scheduling information and performing random access based on the target RO may include: the terminal determining a target RO based on the RO scheduling information and second configuration information carried in the system information, and performing random access based on the target RO; or the terminal selecting an RO from an RO corresponding to the RO scheduling information and an RO corresponding to third configuration information carried in the system information, and performing random access based on the selected target RO; or the terminal selecting an RO from an RO corresponding to the RO scheduling information, and performing random access based on the selected target RO; and so on. This embodiment is not limited to this. The RO corresponding to the third configuration information may be a legacy RO, which may be a non-dynamic RO.

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

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

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

[0152] In one implementation, the configuration information of the additional RO, or flexible RO, or dynamic RO can 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 flexible RO, or dynamic RO is saved, the terminal applies the additional RO, or flexible RO, or dynamic RO for the next random access attempt.

[0153] 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 through the random access response message; the terminal that receives the configuration information in the random access response message can determine the configuration of the flexible RO in combination with the configuration information of the flexible RO in the system information.

[0154] In one embodiment, the paging-related message may include paging scheduling signaling, paging message, paging indication signal, paging wake-up signal, low-power wake-up signal or paging short message, etc. All messages related to the paging process can be understood as paging-related messages.

[0155] 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 through the paging-related message; the terminal that receives the configuration information in the paging-related message can determine the configuration of the flexible RO in combination with the configuration information of the flexible RO in the system information.

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

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

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

[0159] 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 through the public DCI; the terminal receiving the configuration information in the public DCI can determine the configuration of the flexible RO in combination with the configuration information of the flexible RO in the system information.

[0160] It should be noted that when the target message is a random access response message, the embodiments of the present application can address the problem in the related art where the random backoff mechanism causes a longer delay before the terminal attempts to make another random access attempt when congestion occurs. In the related art random access process, if the RACH channel is congested, the network sends a Backoff indication indicating a maximum waiting time T. Based on the Backoff indication, the terminal selects a duration Twait with equal probability between 0 and the maximum waiting time T. After waiting for Twait, the terminal can initiate the next random access attempt. Because different terminals select different Twait values, the RACH congestion problem is alleviated. This random backoff mechanism causes a longer delay before the terminal attempts to make another random access attempt. In the embodiments of the present application, the terminal listens for a random access response message (such as Msg2 or MsgB) within the random access response listening time window. If the random access response message contains RO scheduling information for a dynamic RO, the terminal applies the RO and makes a subsequent random access attempt. While improving RACH channel congestion, the embodiments of the present application can shorten the delay before the terminal attempts to make another random access attempt, thereby improving the user experience.

[0161] In an embodiment of the present application, a terminal receives a target message sent by a network device, the target message carrying physical random access channel (RO) 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. The target message includes at least one of the following: a random access response message; a paging-related message; or common downlink control information (DCI). In this way, the network device carries the RO scheduling information through at least one of the random access response message, the paging-related message, and the DCI. This RO scheduling information can dynamically schedule more ROs for the terminal to perform random access, thereby shortening the waiting time for the terminal to initiate a random access attempt.

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

[0163] First configuration information of the RO;

[0164] RO's time location information;

[0165] Frequency location information of RO;

[0166] RO repetition period information;

[0167] RO effective time information;

[0168] The first indication information is used to indicate whether the RO is valid.

[0169] The first configuration information of the RO may include at least one of the following: a correspondence between the Preamble and the beam, a prach root sequence number, an RSRP threshold for selecting the beam, and the like.

[0170] In one embodiment, the mapping relationship between the RO 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 RO for sending the preamble is determined according to the downlink beam in which the terminal is located or selected. The time-frequency position of the 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 RO determined for sending the preamble is the RO corresponding to the RO scheduling information.

[0171] In one embodiment, the time-frequency position of the RO can be determined by the time position information or frequency position information of the RO in the RO scheduling information, and the RO used to send the preamble is determined based on the mapping relationship between the RO and the downlink beam information (such as SSB) and the time-frequency position of the RO and the downlink beam in which 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 in which it is located or selected. The RO determined to send the preamble is the RO corresponding to the RO scheduling information.

[0172] In one embodiment, the RO scheduling information may include the effective duration information of the RO, and the terminal determines the target RO based on the RO scheduling information, and performs random access based on the target RO. This may include, 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.

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

[0174] In this implementation, the terminal can determine the target RO through at least one of the first configuration information of the RO, the time or frequency location information of the RO, the repetition period information of the RO, the validity duration information of the RO, and the first indication information, and perform random access based on the target RO, thereby increasing the number of optional ROs for random access by the terminal, reducing the probability of RACH collision, and shortening the waiting time for the terminal to initiate a random access attempt.

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

[0176] In the case that the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information, and transmits a next random access preamble based on the target RO.

[0177] Random access failure may refer to unsuccessful reception of a random access response (the Random Access Response reception is not successful) and the random access procedure is not completed. Unsuccessful reception of a random access response may occur in the following two situations: unsuccessful random access or unsuccessful random access. If the terminal determines that the random access response reception is unsuccessful and the random access is not completed, the terminal may continue to initiate the next random access preamble transmission (for example, if the maximum number of RACH attempts has not been reached).

[0178] In this implementation, when the terminal determines that random access has failed, the terminal determines a target RO based on the RO scheduling information carried in the random access response message, and sends the next random access preamble based on the target RO, so that the network side can schedule more ROs through the random access response message for the terminal that failed random access to perform random access in a short time, thereby avoiding the introduction of a long waiting time (backoff) for re-RACH attempts.

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

[0180] The terminal stores the RO scheduling information;

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

[0182] In the case that the terminal determines 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 transmits a next random access preamble based on the target RO.

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

[0184] The terminal may 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 includes RO scheduling information, the terminal stores the RO scheduling information.

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

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

[0187] In one embodiment, 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 the terminal receives new RO scheduling information during the timing period, the timing is restarted according to the new effective duration information.

[0188] In one implementation, after the terminal successfully completes random access (eg, successfully receives Msg4 of a 4-step RACH process), the terminal clears or releases the random access resources dynamically scheduled by the network side, for example, clears the stored RO scheduling information.

[0189] In this implementation, when the terminal determines that random access has failed, if the terminal stores RO scheduling information, the terminal determines a target RO based on the stored RO scheduling information, and sends the next random access preamble based on the target RO. In this way, by storing the RO scheduling information, the terminal can determine the target RO and send the random access preamble based on the stored RO scheduling information when a random access attempt is needed, so that the terminal that failed random access can make a random access attempt in a short time.

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

[0191] If the terminal does not detect a random access response message including a matching 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 has failed;

[0192] If the terminal contention resolution is unsuccessful, the terminal determines that the random access has failed.

[0193] The random access response time window may refer to the ra-ResponseWindow configured in RACH ConfigCommon. Failure to detect a random access response message containing a matching preamble identifier (Preamble_INDEX) sent by the terminal may be understood as not receiving a random access response containing a random access preamble identifier that matches the transmitted Preamble_INDEX (the Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE_INDEX has not been received).

[0194] Optionally, the method further includes:

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

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

[0197] 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.

[0198] The second configuration information of the target RO may include at least one of the following: a correspondence between a Preamble and a beam, a prach root sequence number, an RSRP threshold for selecting a beam, and the like.

[0199] It should be noted that the terminal can obtain part of the configuration of the target RO through the system information broadcast by the cell, and use it in combination with the RO scheduling information contained in the target message to determine the time-frequency position of the target RO and the generation parameters of the Preamble sequence.

[0200] In this implementation, 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, thereby being able to carry part of the configuration of the target RO through the system information, reducing the complexity of the RO scheduling information, supporting the use of RO scheduling information with fewer bits in combination with the system information to indicate the target RO, and saving signaling overhead.

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

[0202] 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;

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

[0204] The RO corresponding to the third configuration information carried in the system information may be the RO configured by the third configuration information carried in the system information. The RO corresponding to the third configuration information may also be described as a non-dynamic RO configured by the system information or a non-dynamic RO broadcasted in the system information.

[0205] 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 the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried in the system information; the terminal performs random access based on the selected target RO.

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

[0207] 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 in the system information; the terminal performs random access based on the selected target RO. In this way, 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 in the system information allows for dynamic scheduling of more ROs for random access by the terminal, thereby shortening the waiting time for the terminal to initiate a random access attempt.

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

[0209] The current time may refer to the time when the RO selection is performed.

[0210] In this embodiment, when the terminal performs a new random access resource selection, the terminal selects the RO with the latest time for random access, regardless of whether it is a non-dynamic RO broadcasted by system information or a dynamic RO scheduled by target message.

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

[0212] The terminal selects an RO from the ROs corresponding to the RO scheduling information;

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

[0214] It should be noted that the terminal receiving the RO scheduling information may consider that the non-dynamic RO broadcasted in the system information is invalid or unavailable, that is, only the RO scheduled by the target message may be used for the random access process.

[0215] In this implementation, 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 use different RO resources for random access, thereby reducing the random access load on the non-dynamically scheduled RO resources.

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

[0217] The terminal selects an RO from the ROs corresponding to the RO scheduling information within the effective time corresponding to the effective duration information of the RO corresponding to the RO scheduling information.

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

[0219] In this embodiment, within the validity period corresponding to the validity duration information of the RO, the terminal receiving the RO scheduling information may consider the non-dynamic RO broadcasted in the system information invalid, that is, only the RO scheduled by the target message may be used for the random access process.

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

[0221] It should be noted that the target MAC subheader or target MAC CE may be a newly introduced MAC subheader or MAC CE; or may be a MAC subheader or MAC CE obtained by enhancing or extending an existing MAC subheader or MAC CE.

[0222] Optionally, the target MAC subheader or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC subheader or target MAC CE.

[0223] The terminal may determine, through the second indication information, whether the received MAC subheader or MAC CE is a target MAC subheader or target MAC CE carrying RO scheduling information.

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

[0225] Optionally, the RO scheduling information includes third indication information, where the third indication information is used to indicate at least one valid RO among the ROs corresponding to the third configuration information carried in the system information.

[0226] The target RO may be a valid RO among the ROs corresponding to the third configuration information carried in the system information indicated by the third indication information.

[0227] The RO corresponding to the third configuration information carried in the system information may be the RO configured by the third configuration information carried in the system information. The RO corresponding to the third configuration information may also be described as a non-dynamic RO configured by the system information or a non-dynamic RO broadcasted in the system information.

[0228] In one embodiment, the third indication information may be a dynamic RO configuration field, used to provide the configuration of the dynamic RO. The third indication information may be associated with the RO configuration provided in the system information. For example, if the system information carries N sets of dynamic RO configurations (N>=1), 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.

[0229] In one embodiment, the third indication information indicates whether to start or stop the RO configured by the third configuration information carried by the system information. For example, one bit of third indication information is used to indicate whether to start or stop the RO configured by the third configuration information; or multiple bits of third indication information are used to indicate the proportion of the RO configured by the third configuration information enabled, such as enabling 0%, 50%, 25%, 75%, and 100% of the RO configured by the third configuration information.

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

[0231] It should be noted that the third indication information can be composed of multiple parts and used to carry different information. For example, the third indication information can 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.

[0232] In this embodiment, the RO scheduling information includes third indication information, which is used to indicate at least one valid RO among the ROs corresponding to the third configuration information carried by the system information, so that the RO scheduling information with fewer bits can be combined with the system information to indicate the target RO, saving signaling overhead.

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

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

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

[0236] It should be noted that the RO corresponding to the third configuration information carried in the system information and the dynamically scheduled RO are mapped to the SSB respectively. If the network side sends 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 legacy RO.

[0237] In this embodiment, the RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried by 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 by the system information and the SSB will not change, thereby avoiding the network side being unable to uniquely determine the SSB based on the preamble sent by the terminal on the RO.

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

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

[0240] 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 identifiers and perform random access based on the selected target RO. For example, the target RO may be the next RO closest to the current time among the ROs corresponding to the scheduling identifiers.

[0241] In one embodiment, a scheduling identifier (such as scheduling ID X) can be agreed upon by the protocol for RO scheduling. When the network sends a public DCI, and the public DCI indicates that the scheduled ID is X, the terminal receiving the public DCI determines the target RO according to the instruction in the public DCI.

[0242] In this implementation, the terminal performs random access based on the RO corresponding to the scheduling identifier carried by the public DCI, so that the network side can schedule more ROs through the public DCI for the terminals that fail random access to perform random access in a short time, avoiding the introduction of a long waiting time for re-RACH attempts.

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

[0244] In a 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;

[0245] The terminal determines whether the terminal is a terminal of the target type based on at least one of the following:

[0246] The number of random accesses performed by the terminal; the preamble transmit 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; and the service trigger type for random access performed by the terminal.

[0247] The target type of terminal may be a terminal with specific characteristics.

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

[0249] Terminals whose RACH attempts are below a certain threshold;

[0250] Terminals whose RACH attempts are equal to or higher than a certain threshold;

[0251] The terminal whose preamble transmission power is lower than a certain threshold;

[0252] Terminals whose preamble transmission power is equal to or higher than a certain threshold;

[0253] Terminals whose RSSI / RSRQ of the serving cell is below a certain threshold;

[0254] Terminals whose RSSI / RSRQ of the serving cell is equal to or higher than a certain threshold;

[0255] Terminals in specific RRC states, such as idle, inactive, or connected terminals;

[0256] Terminals that support specific capabilities, such as terminals that support satellite access (such as non-terrestrial networks (NTN)) and terminals that support reduced terminal capability (RedCap) features;

[0257] RACH is triggered by a terminal due to a specific service type, such as data, signaling, etc.

[0258] In this implementation, when it is determined that the terminal is a terminal of the target type, the terminal determines the target RO based on the RO scheduling information and performs random access based on the target RO. In this way, only terminals of the target type are 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 terminals of the target type to perform random access, thereby shortening the waiting time for the terminals of the target type to initiate random access attempts.

[0259] Referring to FIG. 10 , FIG. 10 is a flowchart of a random access method provided in an embodiment of the present application. As shown in FIG. 10 , the random access method includes the following steps:

[0260] Step 201: The network side device sends a target message to the terminal, wherein the target message carries physical random access channel transmission opportunity RO scheduling information; the RO scheduling information is used for random access;

[0261] The target message includes at least one of the following:

[0262] Random access response message;

[0263] Paging related messages;

[0264] Public DCI.

[0265] The RO scheduling information is used to determine a target RO, and the target RO is used for random access of the terminal.

[0266] It should be noted that this embodiment is an implementation of the network side device corresponding to the embodiment shown in Figure 9. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 9. To avoid repetition, this embodiment will not be repeated.

[0267] The random access method provided in the embodiments of the present application is described below through several specific embodiments:

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

[0269] Example 1:

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

[0271] (11) The UE sends the selected Preamble to the selected RO;

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

[0273] Optionally, the dynamic RO scheduling information includes:

[0274] Time-frequency location information of the dynamic RO or information indicating whether the dynamic RO is available;

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

[0276] The available duration or repetition period of dynamic RO, etc.

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

[0278] (13) If the UE does not detect a response message that matches the sent Preamble until the end of the random access response time window, the UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt.

[0279] Optionally, the UE obtains partial configuration of the dynamic RO through the cell broadcast message, and uses it in combination with the dynamic RO scheduling information contained in the random access response message to determine the time-frequency position of the available dynamic RO and the generation parameters of the Preamble sequence.

[0280] Example 2:

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

[0282] Step (21) is the same as step (11) in Example 1;

[0283] Step (22), same as step (12) in Example 1

[0284] Step (23): If the UE successfully receives Msg2 and sends Msg3, a failure occurs when receiving Msg4 (i.e., contention resolution is unsuccessful); if the UE saves the scheduling information of the dynamic RO, the UE applies the scheduling information of the dynamic RO to make subsequent random access attempts.

[0285] Example 3:

[0286] In this embodiment, the UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt, wherein the UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt including: within the effective time of the scheduling information of the dynamic RO, the UE considers that the non-dynamic RO broadcasted in the system information and the dynamic RO scheduled by Msg2 can both be used for the random access process.

[0287] When the UE performs a new random access resource selection, the UE selects the RO with the latest time for random access, regardless of whether it is a non-dynamic RO or a dynamic RO scheduled by Msg2.

[0288] Example 4:

[0289] In this embodiment, the UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt, wherein the UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt including: 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 that the non-dynamic RO broadcasted in the system information is invalid, that is, only the dynamic RO scheduled by Msg2 can be used for the random access process.

[0290] In this way, terminals that have received dynamic RO scheduling information and terminals that have not received dynamic RO scheduling information will use different RO resources for random access, thereby reducing the random access load on non-dynamically scheduled RO resources.

[0291] Embodiment 5:

[0292] In this embodiment, the UE applies the scheduling information of the dynamic RO to make subsequent random access attempts, wherein:

[0293] The scheduling information of the dynamic RO is carried by a MAC subheader or a MAC CE. An implementation method of a MAC subheader carrying the scheduling information of the dynamic RO is shown in FIG11 .

[0294] The MAC subheader includes an indication field T, indicating that the MAC subheader carries scheduling information of the dynamic RO.

[0295] The MAC subheader carries a dynamic RO configuration field for providing dynamic RO configuration. This configuration can be associated with the configuration provided in the system information: for example, if the system information carries N sets of dynamic RO configurations (N>=1), 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.

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

[0297] When the dynamic RO configuration field carries the effective duration configuration, the UE starts timing when it receives the 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, the timing is restarted according to the new effective duration configuration.

[0298] The UE applies the scheduling information of the dynamic RO to make a subsequent random access attempt, and further includes: after the UE successfully completes the random access (such as successfully receiving Msg4 of the 4-step RACH process), the UE clears or releases the random access resources dynamically scheduled by the network side, for example, clearing the scheduling information of the dynamic RO saved by the UE in step (12) of the first embodiment.

[0299] Example 6:

[0300] In this embodiment, the UE applies the scheduling information of the dynamic RO to make subsequent random access attempts, wherein:

[0301] The scheduling information of the dynamic RO is carried by the MAC subheader or MAC CE.

[0302] The dynamic RO configuration field can be carried using the Rbit in the existing MAC subheader, such as the Rbit in the MAC subheader of the BI.

[0303] For example, one Rbit indicates starting or stopping a dynamic RO (such as flexible RO) configured in the system information; or multiple Rbits indicate enabling ratios, such as enabling 0%, 50%, 25%, 75%, and 100% of the flexible RO configured in the system information.

[0304] FIG12 shows an implementation of a MAC subheader carrying scheduling information of a dynamic RO.

[0305] Embodiment seven:

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

[0307] For example, the mapping relationship between legacy RO and SSB is shown in FIG13 . If the legacy RO and the dynamically scheduled RO are not mapped to SSB separately, as shown in FIG14 , the mapping relationship between the legacy RO and SSB changes. The dotted box is the dynamic RO.

[0308] Because UE1, which did not receive Msg2, is unaware of whether the network has dynamically scheduled an RO, when it is covered by SSB#2, it selects RO1 to send the preamble corresponding to SSB#2, as shown in Figure 13. However, UE2, which receives Msg2, knows that the network has dynamically scheduled an RO. Assuming UE2 can use either a legacy RO or a dynamically scheduled RO, when it is covered by SSB#4, it selects RO1 to send the preamble corresponding to SSB#4, as shown in Figure 14. When the network receives the preamble from RO1, it cannot determine whether the received preamble corresponds to SSB#2 or SSB#4. Therefore, legacy ROs and dynamically scheduled ROs are mapped to SSBs separately. That is, the mapping between legacy ROs and SSBs remains unchanged regardless of whether the network has scheduled a dynamic RO. This allows the network to uniquely determine the SSB the UE is located in based on the received Msg1. For example, the mapping between legacy ROs and SSBs and the mapping between dynamically scheduled ROs and SSBs are shown in Figure 15.

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

[0310] Embodiment 8:

[0311] In this embodiment, in addition to being included in the random access response message, the configuration information of the dynamic RO can also be notified to the UE during the paging process. Signaling or messages carrying the configuration information of the dynamic RO include but are 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-mentioned 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.

[0312] In addition, the UE can periodically monitor paging messages to determine whether it has been 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 has not been paged, it can record the configuration information of the dynamic RO and use the dynamic RO to initiate paging the next time it initiates paging. 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.

[0313] Embodiment 9:

[0314] In this embodiment, in addition to being included in the random access response message, dynamic RO scheduling information can also be carried in common DCI. For example, the protocol specifies a scheduling ID X for dynamic RO scheduling. 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 based on the indication in the scheduling signaling.

[0315] Embodiment 10:

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

[0317] The UE with specific characteristics may include at least one of the following:

[0318] UEs whose RACH attempt count is lower than, equal to, or higher than a certain threshold;

[0319] UEs whose preamble transmission power is lower than, equal to, or higher than a certain threshold;

[0320] UEs whose RSSI / RSRQ of the serving cell is lower than, equal to, or higher than a certain threshold;

[0321] UEs in specific RRC states, such as idle, inactive, or connected UEs;

[0322] UEs that support specific capabilities, such as UEs that support satellite access (e.g., non-terrestrial networks (NTN)) and UEs that support reduced terminal capability (RedCap) features;

[0323] RACH is triggered by a specific service type, such as data, signaling, etc.

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

[0325] In related technologies, when the random access channel is congested, the network configures a longer backoff time to discretize the time it takes for a terminal to re-initiate random access, thereby reducing the RACH load. However, this introduces a longer wait time for re-RACH attempts, which reduces the user experience. In the embodiments of the present application, when the random access channel is congested, the network dynamically schedules more random access opportunities (i.e., ROs) through random access response messages (such as Msg2 or Msg B) for terminals that have unsuccessful or failed random access to perform random access in a short period of time, thereby avoiding the introduction of a longer wait time for re-RACH attempts.

[0326] The embodiment of the present application carries dynamic random access opportunity related information through Msg2 or Msg B to support on-demand scheduling, that is, the scheduling information is sent only when RACH congestion is detected on the network side; at the same time, it can ensure that the dynamic random access opportunity related information is only received by the terminal that needs to retry random access; avoiding interference with other terminals that do not need to know this information.

[0327] The random access method provided in the embodiment of the present application may be executed by a random access device. In the embodiment of the present application, the random access device performing the random access method is taken as an example to illustrate the random access device provided in the embodiment of the present application.

[0328] Please refer to FIG. 16 , which is a structural diagram of a random access device provided in an embodiment of the present application. A terminal includes the random access device. As shown in FIG. 16 , the random access device 300 includes:

[0329] The first receiving module 301 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;

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

[0331] The target message includes at least one of the following:

[0332] Random access response message;

[0333] Paging related messages;

[0334] Common downlink control information DCI.

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

[0336] First configuration information of the RO;

[0337] RO's time location information;

[0338] Frequency location information of RO;

[0339] RO repetition period information;

[0340] RO effective time information;

[0341] The first indication information is used to indicate whether the RO is valid.

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

[0343] In the case that the terminal determines that the random access fails, the terminal determines a target RO based on the RO scheduling information, and transmits a next random access preamble based on the target RO.

[0344] Optionally, the device further comprises:

[0345] A storage module, configured to store the RO scheduling information;

[0346] The access module is specifically used for:

[0347] In the case that the terminal determines 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 transmits a next random access preamble based on the target RO.

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

[0349] If the terminal does not detect a random access response message including a matching 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 has failed;

[0350] If the terminal contention resolution is unsuccessful, the terminal determines that the random access has failed.

[0351] Optionally, the device further comprises:

[0352] A second receiving module, configured to receive system information, where the system information carries second configuration information of the target RO;

[0353] The access module is specifically used for:

[0354] The target RO is determined based on the RO scheduling information and the second configuration information, and random access is performed based on the target RO.

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

[0356] Selecting 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;

[0357] Random access is performed based on the selected target RO.

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

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

[0360] Selecting an RO from the ROs corresponding to the RO scheduling information;

[0361] Random access is performed based on the selected target RO.

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

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

[0364] Random access is performed based on the selected target RO.

[0365] Optionally, the target message includes a target media access control MAC subheader or a target MAC control element CE, and the target MAC subheader or target MAC CE carries the RO scheduling information.

[0366] Optionally, the target MAC subheader or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC subheader or target MAC CE.

[0367] Optionally, the RO scheduling information includes third indication information, where the third indication information is used to indicate at least one valid RO among the ROs corresponding to the third configuration information carried in the system information.

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

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

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

[0371] Optionally, the target message includes public DCI, the public DCI carries RO scheduling information, the RO scheduling information includes a scheduling identifier, and the access module is specifically configured to:

[0372] A target RO is determined based on the RO corresponding to the scheduling identifier, and random access is performed based on the target RO.

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

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

[0375] The terminal determines whether the terminal is a terminal of the target type based on at least one of the following:

[0376] The number of random accesses 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 reception 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; and the service trigger type for random access by the terminal.

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

[0378] The random access device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 9 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0379] Please refer to FIG. 17 , which is a structural diagram of a random access device provided in an embodiment of the present application. A network-side device includes the random access device. As shown in FIG. 17 , the random access device 400 includes:

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

[0381] The target message includes at least one of the following:

[0382] Random access response message;

[0383] Paging related messages;

[0384] Public DCI.

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

[0386] The random access device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 10 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0387] Optionally, as shown in Figure 18, an embodiment of the present application further provides a communication device 500, including a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be run on the processor 501. For example, when the communication device 500 is a terminal, the program or instruction is executed by the processor 501 to implement the various steps of the above-mentioned random access method embodiment applied to the terminal, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 500 is a network side device, the program or instruction is executed by the processor 501 to implement the various steps of the above-mentioned random access method embodiment applied to the network side device, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0388] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiment shown in FIG9 . This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effects.

[0389] Specifically, Figure 19 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0390] The terminal 600 includes but is not limited to: 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 at least some of the components of the processor 610.

[0391] Those skilled in the art will appreciate that the terminal 600 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 610 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG19 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0392] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042, and the graphics processor 6041 processes the image data of a static picture or video 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 a touch panel 6071 and at least one of 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. 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 repeated here.

[0393] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 601 may transmit the data to the processor 610 for processing. Furthermore, the radio frequency unit 601 may send uplink data to the network-side device. Typically, 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, and the like.

[0394] 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, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 609 may include a volatile memory or a non-volatile memory, or the memory 609 may include both volatile and non-volatile memories. Among them, the non-volatile memory may 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 may 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 (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0395] Processor 610 may include one or more processing units. Optionally, processor 610 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 610.

[0396] The radio frequency unit 601 is configured to: receive a target message sent by a network side device, wherein the target message carries physical random access channel transmission opportunity RO scheduling information;

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

[0398] The target message includes at least one of the following:

[0399] Random access response message;

[0400] Paging related messages;

[0401] Common downlink control information DCI.

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

[0403] First configuration information of the RO;

[0404] RO's time location information;

[0405] Frequency location information of RO;

[0406] RO repetition period information;

[0407] RO effective time information;

[0408] The first indication information is used to indicate whether the RO is valid.

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

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

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

[0412] The processor 610 is further configured to:

[0413] In the case that the terminal determines 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 transmits a next random access preamble based on the target RO.

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

[0415] If the terminal does not detect a random access response message including a matching preamble identifier sent by the terminal in the random access response message corresponding to the random access response time window, determining that the random access has failed;

[0416] If the terminal contention resolution is unsuccessful, the terminal determines that the random access has failed.

[0417] 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;

[0418] The processor 610 is specifically configured to:

[0419] The target RO is determined based on the RO scheduling information and the second configuration information, and random access is performed based on the target RO.

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

[0421] Selecting 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;

[0422] Random access is performed based on the selected target RO.

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

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

[0425] Selecting an RO from the ROs corresponding to the RO scheduling information;

[0426] Random access is performed based on the selected target RO.

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

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

[0429] Random access is performed based on the selected target RO.

[0430] Optionally, the target message includes a target media access control MAC subheader or a target MAC control element CE, and the target MAC subheader or target MAC CE carries the RO scheduling information.

[0431] Optionally, the target MAC subheader or target MAC CE carries second indication information, and the second indication information is used to indicate the type of the target MAC subheader or target MAC CE.

[0432] Optionally, the RO scheduling information includes third indication information, where the third indication information is used to indicate at least one valid RO among the ROs corresponding to the third configuration information carried in the system information.

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

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

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

[0436] Optionally, the target message includes public DCI, the public DCI carries RO scheduling information, the RO scheduling information includes a scheduling identifier, and the processor 610 is specifically configured to:

[0437] A target RO is determined based on the RO corresponding to the scheduling identifier, and random access is performed based on the target RO.

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

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

[0440] The terminal determines whether the terminal is a terminal of the target type based on at least one of the following:

[0441] The number of random accesses 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 reception 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; and the service trigger type for random access by the terminal.

[0442] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment Figure 5, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0443] Specifically, the terminal of the embodiment of the present application also includes: instructions or programs stored in the memory 609 and can be run on the processor 610. The processor 610 calls the instructions or programs in the memory 609 to execute the method of execution of each module shown in Figure 16 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0444] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG10 . This network-side device embodiment corresponds to the above-mentioned random access method embodiment applied to the network-side device, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0445] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 20, 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. Antenna 701 is connected to radio frequency device 702. In the uplink direction, radio frequency device 702 receives information via antenna 701 and sends the received information to baseband device 703 for processing. In the downlink direction, baseband device 703 processes the information to be transmitted and sends it to radio frequency device 702. Radio frequency device 702 processes the received information and then sends it through antenna 701.

[0446] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 703 , which includes a baseband processor.

[0447] The baseband device 703 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 20, one of which 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 embodiment.

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

[0449] Specifically, the network side device 700 of the embodiment of the present application also includes: instructions or programs stored in the memory 705 and can be run on the processor 704. The processor 704 calls the instructions or programs in the memory 705 to execute the method of execution of each module shown in Figure 17 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0450] An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned random access method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here.

[0451] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0452] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned random access method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0453] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0454] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned random access method embodiment and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0455] An embodiment of the present application also provides a random access system, including: a terminal and a network side device, wherein 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.

[0456] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted 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 the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0458] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A random access method, comprising: The terminal receives a target message sent by a network side device, where 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; The target message includes at least one of the following: Random access response message; Paging related messages; Common downlink control information DCI.

2. The method according to claim 1, wherein: The RO scheduling information includes at least one of the following: First configuration information of the RO; Time location information of RO; Frequency location information of RO; RO repetition cycle information; RO effective time information; The first indication information is used to indicate whether the RO is effective.

3. The method according to claim 1 or 2, wherein: 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: In the case that 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 code based on the target RO.

4. The method according to claim 3, wherein: 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 random access fails, the terminal determines a target RO based on the RO scheduling information, and sends a next random access preamble code based on the target RO, including: In the case that the terminal determines 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 sends a next random access preamble based on the target RO.

5. The method according to claim 4, wherein: The terminal determines that random access fails, including at least one of the following: If the terminal does not detect a random access response message including a matching 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 contention resolution is unsuccessful, the terminal determines that random access has failed.

6. The method according to any one of claims 1 to 5, further comprising: The terminal receives system information, where the system information carries 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 to 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 the RO corresponding to the RO scheduling information and the RO 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 RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information.

9. The method according to any one of claims 1 to 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 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 the ROs corresponding to the RO scheduling information, including: The terminal selects an RO from the ROs corresponding to the RO scheduling information within the effective time corresponding to the effective duration information of the RO corresponding to the RO scheduling information.

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

12. The method according to claim 11, wherein: The target MAC subheader or the target MAC CE carries second indication information, where the second indication information is used to indicate a type of the target MAC subheader or the target MAC CE.

13. The method according to any one of claims 1 to 12, wherein: The RO scheduling information includes third indication information, and the third indication information is used to indicate at least one valid RO among the ROs corresponding to the third configuration information carried in the system information.

14. The method according to any one of claims 1 to 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 to 14, wherein: The RO corresponding to the RO scheduling information and the RO corresponding to the third configuration information carried by the system information are respectively mapped to the synchronization signal block SSB.

16. The method according to any one of claims 1 to 15, wherein: The target message includes a public DCI, the public DCI carries RO scheduling information, the RO scheduling information includes a scheduling identifier, 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 a 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 to 16, wherein: The terminal determines a target RO based on the RO scheduling information, and performs random access based on the target RO, including: 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; 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 accesses 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 reception 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; and the service trigger type for random access of the terminal.

18. A random access method, comprising: 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; The target message includes at least one of the following: Random access response message; Paging related messages; Public DCI.

19. A random access device, wherein a terminal comprises the random access device, the device comprising: A first receiving module is used 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; The target message includes at least one of the following: Random access response message; Paging related messages; Common downlink control information DCI.

20. A random access device, wherein a network side device comprises the random access device, the device comprising: A sending module, used to send a target message to the terminal, wherein the target message carries physical random access channel transmission opportunity RO scheduling information; The RO scheduling information is used for random access; The target message includes at least one of the following: Random access response message; Paging related messages; Public DCI.

21. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the random access method according to any one of claims 1 to 17 are implemented.

22. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and 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, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the random access method according to any one of claims 1 to 17, or to implement the steps of the random access method according to claim 18.

24. A readable storage medium storing a program or an instruction, wherein the program or the instruction, when executed by a processor, implements the steps of the random access method according to any one of claims 1 to 17, or implements the steps of the random access method according to claim 18.

Images