Random access processing method, related device and computer readable storage medium

Abstract

The application provides a random access processing method, related equipment and a computer readable storage medium. The method is applied to a terminal side device and comprises the following steps: the terminal side device determines a coverage level and an NPRACH format according to a SIB message and a downlink measurement result; the terminal side device transmits a random access request based on the coverage level and the NPRACH format; a network side device determines the coverage level and the NPRACH format of the terminal side device initiating the random access request when the network side device receives the random access request; the network side device transmits a random access response to the terminal side device, and the random access response carries the coverage level and the NPRACH format; and then the terminal side device receives the random access response, and judges whether the random access response is a target random access response according to the coverage level and the NPRACH format carried in the random access response. The embodiment of the application can shorten the random access period of the terminal side device, reduce the access delay, and improve the concurrency capacity.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a random access processing method, related equipment, and computer-readable storage medium. Background Technology

[0002] With the rapid development of communication technology, Narrow Band Internet of Things (NB-IoT) has been widely used due to its advantages such as low power consumption, wide coverage, low cost and large capacity.

[0003] Currently, in NB-IoT systems, terminal devices send random access requests through the Narrow Band Physical Random Access Channel (NPRACH). After receiving the random access request, the network device replies with a random access response within the random access time window, and the terminal device establishes a connection with the network device based on the random access response.

[0004] However, when terminal devices initiate random access on the same carrier at the same time, the network device will respond with a random access response to these terminal devices using the same Media Access Control (MAC) Protocol Data Unit (PDU). Considering the concurrency of terminal devices, the NPRACH resources of terminal devices are generally not allowed to conflict with the NPRACH resources of other terminal devices, resulting in a long random access period and low concurrency capacity. Summary of the Invention

[0005] This invention provides a random access processing method, related equipment, and computer-readable storage medium to solve the problems of long random access cycles and low concurrency capacity in the prior art.

[0006] In a first aspect, embodiments of the present invention provide a random access processing method, applied to a terminal-side device, the method comprising:

[0007] The coverage level and narrowband physical random access channel (NPRACH) format are determined based on the system information block (SIB) message and downlink measurement results.

[0008] Send a random access request based on the coverage level and NPRACH format;

[0009] Receive a random access response sent by a network-side device, the random access response carrying a coverage level and NPRACH format.

[0010] Secondly, embodiments of the present invention provide a random access processing method, applied to a network-side device, the method comprising:

[0011] Upon receiving a random access request from a terminal device, determine the coverage level and NPRACH format of the random access request initiated by the terminal device.

[0012] A random access response is sent to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0013] Thirdly, embodiments of the present invention provide a terminal-side device, the terminal-side device comprising:

[0014] The first determining module is used to determine the coverage level and the narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results.

[0015] The first sending module is used to send a random access request based on the coverage level and NPRACH format;

[0016] The receiving module is used to receive random access responses sent by network-side devices, wherein the random access responses carry coverage level and NPRACH format.

[0017] Fourthly, embodiments of the present invention provide a network-side device, the network-side device comprising:

[0018] The second determining module is used to determine the coverage level and NPRACH format of the random access request initiated by the terminal device when a random access request is received from the terminal device.

[0019] The second sending module is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0020] Fifthly, embodiments of the present invention provide a terminal-side device, including a transceiver and a processor.

[0021] The processor is configured to determine the coverage level and narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results.

[0022] The transceiver is configured to send a random access request based on the coverage level and NPRACH format; and receive a random access response sent by a network-side device, the random access response carrying the coverage level and NPRACH format.

[0023] Sixthly, embodiments of the present invention provide a network-side device, including a transceiver and a processor.

[0024] The processor is configured to determine the coverage level and NPRACH format of the random access request initiated by the terminal device upon receiving a random access request sent by the terminal device.

[0025] The transceiver is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0026] In a seventh aspect, embodiments of the present invention provide a terminal-side device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the random access processing method described in the first aspect.

[0027] Eighthly, embodiments of the present invention provide a network-side device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the random access processing method described in the second aspect above.

[0028] In a ninth aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the random access processing method described in the first aspect; or when the computer program is executed by a processor, it implements the steps of the random access processing method described in the second aspect.

[0029] In this embodiment of the invention, the terminal-side device determines the coverage level and the Narrowband Physical Random Access Channel (NPRACH) format based on the System Information Block (SIB) message and downlink measurement results; it then sends a random access request based on the coverage level and NPRACH format. Correspondingly, upon receiving the random access request from the terminal-side device, the network-side device determines the coverage level and NPRACH format of the random access request initiated by the terminal-side device; it then sends a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device; subsequently, the terminal-side device receives the random access response sent by the network-side device. Thus, when initiating a random access request via NPRACH, the terminal-side device does not need to consider resource collisions with higher coverage levels or resource conflicts between different NPRACH formats, thereby resolving resource contention by the terminal-side device, shortening the random access cycle of the terminal-side device, and improving concurrent capacity. Attached Figure Description

[0030] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is a schematic diagram of the interaction process for random access in an NB-IoT system;

[0032] Figure 2 This is a schematic diagram of the MAC PDU subheader;

[0033] Figure 3 This is a schematic diagram of the MAC RAR structure;

[0034] Figure 4 This is a diagram illustrating NPRACH's coverage level resources;

[0035] Figure 5 This is one of the flowcharts illustrating the random access processing method provided in this embodiment of the invention;

[0036] Figure 6 This is a schematic diagram of the overall process of random access processing;

[0037] Figure 7 This is a second flowchart illustrating the random access processing method provided in this embodiment of the invention.

[0038] Figure 8 This is a schematic diagram of the updated MAC RAR structure;

[0039] Figure 9 This is a concurrency diagram of NPRACH;

[0040] Figure 10 This is one of the structural schematic diagrams of the terminal-side device provided in the embodiments of the present invention;

[0041] Figure 11 This is one of the structural schematic diagrams of the network-side device provided in the embodiments of the present invention;

[0042] Figure 12 This is a second schematic diagram of the structure of the terminal-side device provided in the embodiments of the present invention;

[0043] Figure 13 This is the second schematic diagram of the network-side device provided in the embodiment of the present invention. Detailed Implementation

[0044] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0045] The communication concepts involved in the embodiments of the present invention will be explained below.

[0046] The embodiments of this invention can be applied to the Internet of Things (IoT), and more specifically, to narrowband IoT. The Internet of Things (IoT) is an extension and expansion of the Internet, connecting all things. It is a vast network that combines various information sensing devices with the Internet, enabling interconnection and interoperability between people, machines, and things anytime and anywhere.

[0047] NB-IoT is a low-power wide-area network technology standard. Based on Long Term Evolution (LTE), it's a narrowband IoT technology that supports low-power devices for cellular data connections over wide-area networks. It boasts advantages such as low power consumption, wide coverage, low cost, and high capacity. Furthermore, it occupies only 200kHz bandwidth per frequency point, supporting low-traffic data services.

[0048] NPRACH is mapped to the Random Access Channel (RACH). NPRACH is the channel used by terminal-side equipment to transmit RACH, and it is a single-carrier sequence.

[0049] A Random Access Response (RAR) is a response sent by the network-side device (base station) to the terminal-side device within a defined time window after receiving an NPRACH. The RAR carries a random access preamble (RAPID). Upon receiving the RAR, the terminal-side device compares the RAPID with the subcarrier positions transmitted in the NPRACH. If the two values ​​are equal, the terminal considers it to have received the target's RAR; otherwise, it considers the NPRACH transmission unsuccessful.

[0050] The following explains the random access method for the NB-IoT system.

[0051] An NB-IoT system may include terminal-side devices and network-side devices, see [link / reference] Figure 1 The diagram illustrates the interaction process for random access in an NB-IoT system, such as... Figure 1As shown, the terminal device can send a random access request via NPRACH. After receiving the random access request, the network device replies with a random access response within the random access time window. Furthermore, for terminal devices that initiate random access on the same carrier at the same time, the network device will reply with a random access response to these terminal devices in the same MAC PDU.

[0052] The existing RAR configuration method in MAC PDU is as follows:

[0053] A MAC PDU can contain a MAC header and zero or more MAC RARs. When a network-side device receives random access requests from multiple terminal-side devices at the same time, it can contain multiple MAC RARs.

[0054] A MAC header consists of one or more MAC PDU subheaders, see [link / reference]. Figure 2 The figure shows a schematic diagram of the MAC PDU subheader, as follows: Figure 2 As shown, the MAC PDU subheader contains E / T / RAPID. See also... Figure 3 The figure shows a schematic diagram of the MAC RAR structure, as follows: Figure 3 As shown, a MAC RAR contains R / Timing AdvanceCommand / UL Grant / ER / Temporary C-RNTI, where ER is an extended 2-bit RAPID.

[0055] After receiving the random access response, the terminal device will query the ER+RAPID field of each MAC PDU subheader. ER+RAPID has a total of 8 bits. Let PRID = ER+RAPID. If PRID is the same as the subcarrier position initiated by NPRACH, then the random access response is considered to have been successfully received.

[0056] In addition, there are three NPRACH formats in the NB-IoT system: NPRACH format 0, NPRACH format 1, and NPRACH format 2. NPRACH format 0 / 1 has a maximum of 48 subcarrier candidate positions, with a PRID value ranging from 0 to 47. NPRACH format 2 has a maximum of 144 subcarrier candidate positions, with a PRID value ranging from 0 to 143. When the terminal device receives a PRID value between 0 and 47, it cannot determine whether it is NPRACH format 0 / 1 or NPRACH format 2. Therefore, the 3GPP (3rd Generation Partnership Project) stipulates that NPRACH format 2 cannot overlap with NPRACH format 0 / 1 in the time domain configuration.

[0057] Each NPRACH format can be configured with 3 coverage levels. The configuration parameters for each coverage level are carried in the system broadcast and mainly include the following: 1) the number of NPRACH repetitions; 2) the time domain start position of NPRACH; 3) the frequency domain resources of NPRACH.

[0058] Each coverage level's NPRACH resources are configured independently, and it's possible that the time-domain start positions and frequency-domain resources of different coverage levels completely overlap. See [link to relevant documentation]. Figure 4 The diagram shows a schematic of NPRACH coverage level resources, such as... Figure 4 As shown, Res00 and Res10 conflict in both frequency and time domains, and Res02 ​​and Res11 conflict in both frequency and time domains. 3GPP stipulates that coverage level 0 cannot occupy Res00 and Res02, meaning that resources with lower coverage levels have lower priority than resources with higher coverage levels.

[0059] To avoid resource conflicts, the existing random access methods are as follows:

[0060] Before initiating random access, the terminal-side device obtains downlink measurement results based on the downlink received signal and determines the coverage level of the terminal-side device based on the downlink measurement results;

[0061] After the terminal device determines the coverage level, it can only initiate random access in the time-frequency domain resources corresponding to the coverage level. Considering the concurrency of the terminal device, the terminal device needs to determine whether the current NPRACH resource conflicts with the resource of the higher coverage level. If there is a conflict, the current resource needs to be discarded and the next resource needs to be found. This results in a long access cycle, low concurrency capacity, and easy resource conflict for the terminal device.

[0062] When the terminal device uses NPRACH format2, it cannot occupy the time domain resources of NPRACH format 0 / 1. This results in a long random access period, low concurrency capacity, and a tendency to cause resource conflicts.

[0063] Based on this, embodiments of the present invention provide a new random access processing method to resolve resource contention among terminal devices, thereby shortening the random access cycle of terminal devices and improving concurrent capacity.

[0064] The random access processing method provided in the embodiments of the present invention will be described below.

[0065] See Figure 5 The figure shows one of the flowcharts of the random access processing method provided in an embodiment of the present invention, such as... Figure 5 As shown, the method may include the following steps:

[0066] Step 501: Determine the coverage level and narrowband physical random access channel (NPRACH) format based on the System Information Block (SIB) message and downlink measurement results.

[0067] It should be noted that the random access processing method provided in this embodiment of the invention relates to the field of communication technology and can be widely applied in NB-IoT systems. This method can be executed by the terminal-side device of this embodiment.

[0068] In this step, before initiating a random access request, the terminal device determines the coverage level and NPRACH format based on the System Information Block (SIB) message and downlink measurement results.

[0069] SIB messages can be obtained in the following ways:

[0070] When the terminal device powers on, it searches for the network and obtains the physical cell identifier ID and downlink synchronization through the physical downlink synchronization signal; the physical downlink synchronization signal includes the primary synchronization signal and the secondary synchronization signal.

[0071] After the terminal-side device and the network-side device obtain downlink synchronization, the terminal-side device can read the system broadcast information of the network-side device, such as the Master Information Block (MIB) and other system broadcast information (SIB).

[0072] The SIB message can be the SIB2 message, and the SIB2 message can carry random access configuration information, which includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and the reference signal receiving power (RSRP) threshold of the coverage level, where N is a positive integer.

[0073] In an optional implementation, N can be 3, and the random access configuration information can include NPRACH format 0, NPRACH format 1, and NPRACH format 2. The RSRP threshold can include threshold P1 and threshold P2, where threshold P1 is greater than threshold P2, and there are 3 coverage levels.

[0074] The downlink measurement result can refer to the measured value obtained from the downlink measurement performed before random access.

[0075] Based on the random access configuration information and the downlink measurement result, the coverage level and NPRACH format for the terminal device to initiate a random access request can be determined. Specifically, the coverage level can be determined based on the magnitude relationship between the downlink measurement result and the RSRP threshold; then, based on the format support information of the terminal device, the NPRACH format can be selected from N NPRACH formats, or based on the determined coverage level and the format support information of the terminal device, the NPRACH format can be selected from N NPRACH formats, which is not specifically limited here.

[0076] In an optional implementation, let the downlink measurement result be P. If P ≥ P1, the terminal device selects coverage level 0. If P2 ≤ P < P1, the terminal device selects coverage level 1. If P < P2, the terminal device selects coverage level 2.

[0077] After that, the NPRACH format can be selected from N NPRACH formats by combining the determined coverage level and the format support information of the terminal device. Specifically, when the terminal device supports NPRACH format 2 and the time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, NPRACH format 2 is determined as the NPRACH format for initiating a random access request; when the terminal device supports NPRACH format 2 and the time-frequency domain resources of NPRACH format 2 are not configured at the determined coverage level, NPRACH format 0 or NPRACH format 1 is selected; when the terminal device does not support NPRACH format 2, NPRACH format 0 or NPRACH format 1 is selected.

[0078] In other words, when the terminal device does not support NPRACH format 2, it can only select NPRACH format 0 / 1. When the terminal device supports NPRACH format 2, if NPRACH format 2 resources are configured at a given coverage level, then NPRACH format 2 is selected; otherwise, NPRACH format 0 / 1 is selected.

[0079] Step 502: Send a random access request based on the coverage level and NPRACH format.

[0080] In this step, sending a random access request based on the determined coverage level and NPRACH format refers to initiating a random access request on the time-frequency domain resources divided by the coverage level and NPRACH format.

[0081] While the terminal-side device initiates a random access request to the network-side device on the time-frequency domain resources divided by the coverage level and NPRACH format, other terminal-side devices can also initiate random access requests to the network-side device at the same time on the same frequency band. Moreover, the random access requests initiated by each terminal-side device are independent of each other and do not affect each other.

[0082] Step 503: Receive a random access response sent by the network-side device, wherein the random access response carries the coverage level and NPRACH format.

[0083] Network-side devices can receive random access requests sent by various terminal-side devices and, within the random access time window, reply to these terminal-side devices with random access responses in the same MAC PDU.

[0084] To distinguish the NPRACH corresponding to each terminal device, the network device usually carries the detected NPRACH frequency domain location in the random access response. It can also carry the detected coverage level and NPRACH format, so that the terminal device can determine whether the random access response is a response to the random access request it initiated.

[0085] The detected coverage level can be coverage level 0, coverage level 1 or coverage level 2, and the detected NPRACH format can be NPRACH format 0, NPRACH format 1 or NPRACH format 2.

[0086] Correspondingly, the network-side equipment distinguishes the NPRACH of each terminal-side device by accurately detecting the NPRACH frequency domain location, coverage level, and NPRACH format of each terminal-side device, and carries it into the random access response accordingly. Each terminal-side device can then receive the random access response carrying this information.

[0087] After receiving the random access response, the terminal device can compare the coverage level, NPRACH format, and NPRACH frequency domain location carried in the random access response with the coverage level, NPRACH format, and NPRACH frequency domain location of the device that initiated the random access request to determine whether it is the random access response it expects.

[0088] Specifically, if the coverage level carried in the random access response is the same as the coverage level of the random access request, the NPRACH format carried in the random access response is the same as the NPRACH format of the random access request, and the NPRACH frequency domain position carried in the random access response is the same as the NPRACH frequency domain position of the random access request, then it is determined that the random access response is the random access response expected by the terminal device; otherwise, it is considered that the NPRACH was not successfully sent.

[0089] In practical applications, the MAC PDU received by the terminal device may include multiple MAC RARs. In this case, the terminal device can compare the coverage level, NPRACH format, and NPRACH frequency domain location carried in each MAC RAR with the coverage level, NPRACH format, and NPRACH frequency domain location of the random access request initiated by the terminal device. If they match, the corresponding MAC RAR is determined to be the random access response expected by the terminal device. If none of the multiple MAC RARs in the received MAC PDU match, it is determined that the NPRACH was not successfully transmitted.

[0090] Specifically, the matching of the coverage level, NPRACH format, and NPRACH frequency domain location carried in the MAC RAR with the coverage level, NPRACH format, and NPRACH frequency domain location of the random access request initiated by the terminal device can mean that the NPRACH frequency domain location carried in the MAC RAR is the same as the location of the NPRACH frequency domain resource of the random access request initiated by the terminal device, the coverage level carried in the MAC RAR is the same as the coverage level of the random access request initiated by the terminal device, and the NPRACH format carried in the MAC RAR is the same as the NPRACH format of the random access request initiated by the terminal device.

[0091] The following describes the overall flow of the random access processing method in this embodiment of the invention. See also: Figure 6 The figure shows a schematic diagram of the overall process of the random access processing method, such as... Figure 6 As shown, the overall process is as follows:

[0092] When the terminal device powers on, it searches for the network and obtains the physical cell identifier ID and downlink synchronization through the physical downlink synchronization signal; the physical downlink synchronization signal includes the primary synchronization signal and the secondary synchronization signal.

[0093] After the terminal-side device and the network-side device obtain downlink synchronization, the terminal-side device can read the system broadcast information of the network-side device, such as the Master Information Block (MIB) and other system broadcast information (SIB).

[0094] Terminal-side devices can obtain random access configuration information through SIB2 messages, which includes three NPRACH formats (NPRACH format 0, NPRACH format 1 and NPRACH format 2), time-frequency domain resources for different coverage levels, and RSRP threshold values ​​for coverage levels.

[0095] Then, the terminal-side device can determine the coverage level and NPRACH format for initiating a random access request based on the random access configuration information and downlink measurement results.

[0096] Terminal-side devices initiate random access requests on time-frequency domain resources divided by coverage level and NPRACH format.

[0097] The network-side device receives random access requests sent simultaneously by various network-side devices, determines the coverage level and NPRACH format of each terminal-side device's random access request, and includes these in the random access response. Simultaneously, the random access response may also carry the NPRACH frequency domain location detected by the network-side device.

[0098] The terminal device receives a random access response sent by the network device.

[0099] Terminal-side devices can view the coverage level, NPRACH format, and NPRACH frequency domain location carried in the random access response.

[0100] The terminal device compares the coverage level, NPRACH format, and NPRACH frequency domain position carried in the random access response with those of the device that initiated the random access request to determine if it is the expected random access response. Specifically, if the coverage level, NPRACH format, and NPRACH frequency domain position in the random access response are the same as those in the initial random access request, then the random access response is determined to be the expected random access response; otherwise, it is considered that the NPRACH was not successfully transmitted.

[0101] In this embodiment, the terminal-side device determines the coverage level and Narrowband Physical Random Access Channel (NPRACH) format based on the System Information Block (SIB) message and downlink measurement results; it then sends a random access request based on the coverage level and NPRACH format. Correspondingly, upon receiving the random access request from the terminal-side device, the network-side device determines the coverage level and NPRACH format used by the terminal-side device to initiate the request; it then sends a random access response to the terminal-side device, carrying the coverage level and NPRACH format determined by the network-side device. Subsequently, the terminal-side device receives the random access response from the network-side device. Thus, when initiating a random access request via NPRACH, the terminal-side device does not need to consider resource collisions with higher coverage levels or resource conflicts between different NPRACH formats, thereby resolving resource contention by the terminal-side device. This, in turn, shortens the random access cycle of the terminal-side device, reduces access latency, and improves concurrent capacity.

[0102] Optionally, step 501 specifically includes:

[0103] Obtain random access configuration information from SIB messages;

[0104] The coverage level and NPRACH format are determined based on the random access configuration information and the downlink measurement results.

[0105] The random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and reference signal received power (RSRP) threshold values ​​for the coverage level, where N is a positive integer.

[0106] In this embodiment, the SIB message can be an SIB2 message, which may carry random access configuration information. This random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and reference signal receiving power (RSRP) threshold values ​​for the coverage level, where N is a positive integer.

[0107] In one optional implementation, N can be 3, and the random access configuration information may include NPRACH format 0, NPRACH format 1, and NPRACH format 2. The RSRP threshold value may include a threshold value P1 and a threshold value P2, where the threshold value P1 is greater than the threshold value P2.

[0108] Correspondingly, random access configuration information can be obtained from the SIB2 message. Based on this random access configuration information and downlink measurement results, the coverage level and NPRACH format for the terminal device to initiate a random access request can be determined. Specifically, the coverage level can be determined based on the relationship between the downlink measurement results and the RSRP threshold value. Then, an NPRACH format can be selected from N NPRACH formats based on the format support information of the terminal device, or it can be selected from N NPRACH formats based on the determined coverage level and the format support information of the terminal device; no specific limitation is made here.

[0109] In this embodiment, random access configuration information is obtained from SIB messages; the coverage level and NPRACH format are determined based on the random access configuration information and downlink measurement results; wherein, the random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and RSRP threshold values ​​for the coverage level. In this way, the coverage level and NPRACH format of the terminal device can be determined, and a random access request can be initiated on the corresponding time-frequency domain resources.

[0110] Optionally, determining the coverage level and NPRACH format based on the random access configuration information and the downlink measurement results includes:

[0111] The coverage level is determined based on the relationship between the downlink measurement results and the RSRP threshold value;

[0112] Based on the determined coverage level and the format support information of the terminal-side device, an NPRACH format for initiating a random access request is selected from the N NPRACH formats.

[0113] In this embodiment, the coverage level for a terminal device to initiate a random access request can be determined based on the relationship between downlink measurement results and RSRP threshold values.

[0114] In an optional embodiment, when the number of coverage levels is three, the number of RSRP threshold values is two, namely P1 and P2, where P1 > P2. Let the downlink measurement result be P. If P ≥ P1, the terminal device selects coverage level 0. If P2 ≤ P < P1, the terminal device selects coverage level 1. If P < P2, the terminal device selects coverage level 2.

[0115] After that, in combination with the determined coverage level and the format support information of the terminal device, an NPRACH format for initiating a random access request can be selected from N NPRACH formats.

[0116] In this embodiment, the coverage level is determined based on the magnitude relationship between the downlink measurement result and the RSRP threshold value; and an NPRACH format for initiating a random access request is selected from N NPRACH formats based on the determined coverage level and the format support information of the terminal device. In this way, the accuracy of NPRACH format selection can be improved.

[0117] Optionally, the N NPRACH formats include a first type of NPRACH format and a second type of NPRACH format. The first type of NPRACH format includes NPRACH format 2. The second type of NPRACH format includes NPRACH format 0 and NPRACH format 1. The selection of an NPRACH format for initiating a random access request from the N NPRACH formats based on the determined coverage level and the format support information of the terminal device includes:

[0118] When the terminal device supports NPRACH format 2 and the time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, NPRACH format  2 is determined as the NPRACH format for initiating a random access request;

[0119] When the terminal device supports NPRACH format 2 and the time-frequency domain resources of NPRACH format 2 are not configured at the determined coverage level, an NPRACH format for initiating a random access request is selected from the second type of NPRACH formats;

[0120] When the terminal device does not support NPRACH format 2, an NPRACH format for initiating a random access request is selected from the second type of NPRACH formats.

[0121] In this embodiment, an NPRACH format can be selected from N NPRACH formats by combining the determined coverage level and the format support information of the terminal device. Specifically, if the terminal device supports NPRACH format 2 and the time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, NPRACH format 2 is determined as the NPRACH format for initiating a random access request; if the terminal device supports NPRACH format 2 but the time-frequency domain resources of NPRACH format 2 are not configured at the determined coverage level, NPRACH format 0 or NPRACH format 1 is selected; if the terminal device does not support NPRACH format 2, NPRACH format 0 or NPRACH format 1 is selected.

[0122] In other words, when the terminal device does not support NPRACH format 2, it can only select NPRACH format 0 / 1. When the terminal device supports NPRACH format 2, if NPRACH format 2 resources are configured at a given coverage level, then NPRACH format 2 is selected; otherwise, NPRACH format 0 / 1 is selected.

[0123] In this way, the NPRACH format can be determined by combining the defined coverage level and the format support information of the terminal device.

[0124] See Figure 7 The figure shows a second schematic flowchart of the random access processing method provided in an embodiment of the present invention, as shown in the figure. Figure 7 As shown, the method may include the following steps:

[0125] Step 701: Upon receiving a random access request from a terminal device, determine the coverage level and NPRACH format of the random access request initiated by the terminal device.

[0126] Step 702: Send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0127] It should be noted that the random access processing method provided in this embodiment of the invention relates to the field of communication technology and can be widely applied in NB-IoT systems. This method can be executed by the network-side device of this embodiment.

[0128] In this embodiment, to accurately distinguish the NPRACH of each terminal device, the network-side device, upon receiving a random access request from a terminal device, can determine the coverage level and NPRACH format of the random access request initiated by that terminal device. Simultaneously, it can also determine the NPRACH frequency domain location of the random access request initiated by the terminal device.

[0129] The system includes the detected coverage level, NPRACH format, and NPRACH frequency domain location in the random access response, which is then sent to each terminal device via a MAC PDU. For details, see [link to details]. Figure 8 The diagram shows a schematic of the updated MAC RAR structure, as shown below. Figure 8 As shown, network-side devices can carry the detected NPRACH format and coverage level in the MAC RAR, occupying a total of 3 bits: 1 bit for NPRACH format indication and 2 bits for coverage level indication. The NPRACH frequency domain location remains within the RAPID field of the random access response.

[0130] The 1-bit NPRACH format indication information is located in the FOR field, where 0 indicates NPRACH format 0 / 1 and 1 indicates NPRACH format 2.

[0131] The 2-bit coverage level indication information is located in the CC field, where 0 indicates coverage level 0, 1 indicates coverage level 1, 2 indicates coverage level 2, and 3 is reserved.

[0132] Correspondingly, the terminal device can confirm whether it is its own RAR by checking the FOR, CC, RAPID, and ER fields in the random access response.

[0133] In this embodiment, upon receiving a random access request from a terminal device, the network-side device determines the coverage level and NPRACH format of the random access request initiated by the terminal device; it then sends a random access response to the terminal device, the random access response carrying the coverage level and NPRACH format determined by the network-side device. Thus, when initiating a random access request via NPRACH, the terminal device does not need to consider resource collisions with higher coverage levels or resource conflicts between different NPRACH formats, thereby resolving resource contention by the terminal device, shortening the random access cycle of the terminal device, and improving concurrency capacity.

[0134] Furthermore, existing reserved bits can be used to carry the FOR and CC fields without any additional overhead for the terminal device.

[0135] Optionally, step 701 specifically includes:

[0136] Determine the resource conflict between the terminal-side device and other terminal-side devices that initiate random access requests at the same time;

[0137] Based on the resource conflict, the coverage level and NPRACH format for the random access request initiated by the terminal device are determined.

[0138] In this embodiment, since multiple terminal devices may initiate random access requests on the same carrier at the same time, and each terminal device initiates random access requests independently and without affecting each other, the network device may receive multiple random access requests at the same time, and the time-frequency domain resources for these terminal devices to initiate random access requests may conflict.

[0139] In this scenario, resource conflicts between the terminal device and other terminal devices initiating random access requests simultaneously can be determined. Based on these resource conflicts, the coverage level and NPRACH format of the random access request initiated by the terminal device can be determined. Thus, resource conflicts can be detected by network-side devices, and the NPRACH of each terminal device can be accurately distinguished based on these conflicts. This allows terminal devices to initiate random access requests without considering resource conflicts with other terminal devices, thereby shortening the random access cycle and improving concurrency capacity.

[0140] When the resources of the terminal device do not conflict with those of other terminal devices that initiate random access requests at the same time, or when the network device only receives the random access request from the terminal device at a given time, the network device can directly determine the coverage level and NPRACH format based on the time-frequency domain resources that initiated the random access request.

[0141] Optionally, determining the coverage level and NPRACH format for the random access request initiated by the terminal device based on the resource conflict includes:

[0142] When time-frequency domain resources of the same NPRACH format with different coverage levels conflict, the coverage level is determined based on the number of times the NPRACH is repeated in the random access request initiated by the terminal device.

[0143] When time-frequency domain resources of different NPRACH formats conflict, the NPRACH format is determined based on the subcarrier interval of the random access request initiated by the terminal device.

[0144] In this embodiment, when time-frequency domain resources of different coverage levels conflict within the same NPRACH format, the network-side device can distinguish different NPRACHs by the number of repetitions at different coverage levels. For example... Figure 4 As shown, Res00 and Res10, as well as Res02 ​​and Res11, have different numbers of repetitions for different coverage levels.

[0145] When NPRACH format 0 / 1 conflicts with NPRACH format 2 in the time and frequency domain, network-side devices can distinguish between different NPRACHs by subcarrier spacing. See [link to relevant documentation]. Figure 9 The diagram illustrates the concurrency of NPRACH, as shown below. Figure 9 As shown, the subcarrier spacing is different for Res10 and Res20, as well as Res11 and Res21, in different NPRACH formats.

[0146] For example, such as Figure 9 As shown, Res00 and Res02 ​​of terminal device 1 conflict with Res10 and Res11 resources of terminal device 2, respectively. The network device can distinguish between terminal device 1 and terminal device 2 by the number of NPRACH repetitions, and then carries CC information in the RAR. For terminal device 1, both Res00 and Res02 ​​are valid resources. However, in the existing scheme, terminal device 1 cannot occupy Res00 and Res02, and can only initiate random access on Res01 and Res03. The fewer resources available for random access, the longer the terminal may take to access the network, thus reducing the terminal's performance.

[0147] Res10 and Res11 of terminal device 2 conflict with Res20 and Res21 of terminal device 3, respectively. The subcarrier spacing of the NPRACH initiated by terminal device 2 is 3.75kHz, while the subcarrier spacing of the NPRACH initiated by terminal device 3 is 1.25kHz. The network-side device can distinguish between terminal device 2 and terminal device 3 based on the subcarrier spacing and then carry FOR information in the RAR. For terminal device 2, Res10 and Res11 are both valid resources, and for terminal device 3, Res20 and Res21 are also valid resources. However, in the existing scheme, terminal device 3 cannot occupy Res20 and Res21.

[0148] In this embodiment, after the terminal device determines the coverage level and subcarrier spacing, it does not need to consider the impact of multiple coverages and multiple carrier spacings. The network device can distinguish different NPRACHs by retrieving the repetition count and subcarrier spacing of the NPRACH and reply with the corresponding information in the RAR. In this way, the terminal device can confirm whether it is its own RAR through the FOR, CC, RAPID and ER fields.

[0149] The relevant equipment provided in the embodiments of the present invention will be described below.

[0150] See Figure 10 The figure shows one of the structural schematic diagrams of the terminal-side device provided in an embodiment of the present invention. Figure 10 As shown, the terminal-side device 1000 includes:

[0151] The first determining module 1001 is used to determine the coverage level and the narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results.

[0152] The first sending module 1002 is used to send a random access request based on the coverage level and NPRACH format;

[0153] The receiving module 1003 is used to receive a random access response sent by a network-side device, wherein the random access response carries a coverage level and NPRACH format.

[0154] Optionally, the first determining module 1001 includes:

[0155] The acquisition unit is used to obtain random access configuration information from SIB messages;

[0156] The first determining unit is configured to determine the coverage level and NPRACH format based on the random access configuration information and the downlink measurement results;

[0157] The random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and reference signal received power (RSRP) threshold values ​​for the coverage level, where N is a positive integer.

[0158] Optionally, the first determining unit is specifically used for:

[0159] The coverage level is determined based on the relationship between the downlink measurement results and the RSRP threshold value;

[0160] Based on the determined coverage level and the format support information of the terminal-side device, an NPRACH format for initiating a random access request is selected from the N NPRACH formats.

[0161] Optionally, the N NPRACH formats include a first type of NPRACH format and a second type of NPRACH format, the first type of NPRACH format includes NPRACH format 2, and the second type of NPRACH format includes NPRACH format 0 and NPRACH format 1. The first determining unit is specifically used for:

[0162] If the terminal device supports NPRACH format 2 and time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, then NPRACH format 2 will be determined as the NPRACH format for initiating random access requests.

[0163] If the terminal device supports NPRACH format 2 and no time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, the NPRACH format for initiating a random access request shall be selected from the second type of NPRACH format.

[0164] If the terminal device does not support NPRACH format 2, the NPRACH format for initiating a random access request is selected from the second type of NPRACH format.

[0165] Terminal-side device 1000 can achieve Figure 5 The various processes implemented by the terminal-side device in the random access processing method embodiment shown are not described again here to avoid repetition.

[0166] See Figure 11 The figure shows one of the structural schematic diagrams of a network-side device provided in an embodiment of the present invention. Figure 11 As shown, the network-side device 1100 includes:

[0167] The second determining module 1101 is used to determine the coverage level and NPRACH format of the random access request initiated by the terminal side device when a random access request is received from the terminal side device.

[0168] The second sending module 1102 is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0169] Optionally, the second determining module includes:

[0170] The second determining unit is used to determine the resource conflict between the terminal-side device and other terminal-side devices that initiate random access requests at the same time.

[0171] The third determining unit is used to determine the coverage level and NPRACH format of the random access request initiated by the terminal device based on the resource conflict situation.

[0172] Optionally, the third determining unit is specifically used for:

[0173] When time-frequency domain resources of the same NPRACH format with different coverage levels conflict, the coverage level is determined based on the number of times the NPRACH is repeated in the random access request initiated by the terminal device.

[0174] When time-frequency domain resources of different NPRACH formats conflict, the NPRACH format is determined based on the subcarrier interval of the random access request initiated by the terminal device.

[0175] Network-side device 1100 can achieve Figure 7 The various processes implemented by the network-side device in the random access processing method embodiment shown are not described again here to avoid repetition.

[0176] This invention also provides a terminal-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the various processes of the above-described random access processing method embodiments for terminal-side devices and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0177] See Figure 12 The figure shows a second schematic diagram of the terminal-side device provided in an embodiment of the present invention, as shown in the figure. Figure 12 As shown, the terminal-side device includes a bus 1201, a transceiver 1202, an antenna 1203, a bus interface 1204, a processor 1205, and a memory 1206.

[0178] The processor 1205 is used to determine the coverage level and the narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results.

[0179] Transceiver 1202 is used to send a random access request based on the coverage level and NPRACH format; and to receive a random access response sent by a network-side device, the random access response carrying the coverage level and NPRACH format.

[0180] Optionally, the processor 1205 is further configured to obtain random access configuration information from the SIB message; and determine the coverage level and NPRACH format based on the random access configuration information and the downlink measurement results;

[0181] The random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and reference signal received power (RSRP) threshold values ​​for the coverage level, where N is a positive integer.

[0182] Optionally, the processor 1205 is further configured to determine the coverage level based on the relationship between the downlink measurement results and the RSRP threshold value; and select an NPRACH format for initiating a random access request from the N NPRACH formats based on the determined coverage level and the format support information of the terminal-side device.

[0183] Optionally, the N NPRACH formats include a first type of NPRACH format and a second type of NPRACH format. The first type of NPRACH format includes NPRACH format 2, and the second type of NPRACH format includes NPRACH format 0 and NPRACH format 1. The processor 1205 is further configured to: determine NPRACH format 2 as the NPRACH format for initiating a random access request when the terminal device supports NPRACH format 2 and time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level; select an NPRACH format for initiating a random access request from the second type of NPRACH formats when the terminal device supports NPRACH format 2 and time-frequency domain resources of NPRACH format 2 are not configured at the determined coverage level; and select an NPRACH format for initiating a random access request from the second type of NPRACH formats when the terminal device does not support NPRACH format 2.

[0184] exist Figure 12 In this document, a bus architecture (represented by bus 1201) is used. Bus 1201 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1205 and memory represented by memory 1206. Bus 1201 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1204 provides an interface between bus 1201 and transceiver 1202. Transceiver 1202 may be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1205 is transmitted over a wireless medium via antenna 1203, which further receives data and transmits it to processor 1205.

[0185] Processor 1205 is responsible for managing bus 1201 and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 1206 can be used to store data used by processor 1205 during operation.

[0186] Optionally, the processor 1205 can be a CPU, ASIC, FPGA, or CPLD.

[0187] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes described in the above-described embodiments of the random access processing method for terminal-side devices, achieving the same technical effects. To avoid repetition, these details are not repeated here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0188] This invention also provides a network-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the various processes of the above-described random access processing method embodiments for network-side devices and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0189] See Figure 13 The figure shows a second schematic diagram of the network-side device provided in an embodiment of the present invention, as shown in the figure. Figure 13 As shown, the network-side device includes a bus 1301, a transceiver 1302, an antenna 1303, a bus interface 1304, a processor 1305, and a memory 1306.

[0190] The processor 1305 is configured to determine the coverage level and NPRACH format of the random access request initiated by the terminal device upon receiving a random access request sent by the terminal device.

[0191] Transceiver 1302 is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

[0192] Optionally, the processor 1305 is further configured to determine the resource conflict between the terminal-side device and other terminal-side devices that initiate random access requests at the same time; and based on the resource conflict, determine the coverage level and NPRACH format of the random access request initiated by the terminal-side device.

[0193] Optionally, the processor 1305 is further configured to determine the coverage level based on the number of repetitions of the NPRACH initiating a random access request by the terminal device when time-frequency domain resources of the same NPRACH format with different coverage levels conflict; and to determine the NPRACH format based on the subcarrier spacing initiating a random access request by the terminal device when time-frequency domain resources of different NPRACH formats conflict.

[0194] exist Figure 13 In this document, a bus architecture (represented by bus 1301) is used. Bus 1301 can include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1305 and memory represented by memory 1306. Bus 1301 can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1304 provides an interface between bus 1301 and transceiver 1302. Transceiver 1302 can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1305 is transmitted over a wireless medium via antenna 1303, which further receives data and transmits it to processor 1305.

[0195] Processor 1305 manages bus 1301 and general processing, and also provides various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 1306 can be used to store data used by processor 1305 during operation.

[0196] Optionally, the processor 1305 can be a CPU, ASIC, FPGA, or CPLD.

[0197] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described random access processing method embodiments for network-side devices, achieving the same technical effects. To avoid repetition, further details are omitted here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0198] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0199] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0200] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0201] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0202] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0203] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0204] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A random access processing method, characterized in that, Applied to a terminal-side device, the method includes: The coverage level and narrowband physical random access channel (NPRACH) format are determined based on the system information block (SIB) message and downlink measurement results. Send a random access request based on the coverage level and NPRACH format; Receive a random access response sent by a network-side device, the random access response carrying a coverage level and NPRACH format.

2. The method according to claim 1, characterized in that, The determination of coverage level and narrowband physical random access channel (NPRACH) format based on System Information Block (SIB) messages and downlink measurement results includes: Obtain random access configuration information from SIB messages; The coverage level and NPRACH format are determined based on the random access configuration information and the downlink measurement results. The random access configuration information includes N NPRACH formats, time-frequency domain resources corresponding to different coverage levels, and reference signal received power (RSRP) threshold values ​​for the coverage level, where N is a positive integer.

3. The method according to claim 2, characterized in that, The step of determining the coverage level and NPRACH format based on the random access configuration information and the downlink measurement results includes: The coverage level is determined based on the relationship between the downlink measurement results and the RSRP threshold value; Based on the determined coverage level and the format support information of the terminal-side device, an NPRACH format for initiating a random access request is selected from the N NPRACH formats.

4. The method according to claim 3, characterized in that, The N NPRACH formats include a first type of NPRACH format and a second type of NPRACH format. The first type of NPRACH format includes NPRACH format 2, and the second type of NPRACH format includes NPRACH format 0 and NPRACH format 1. The step of selecting an NPRACH format for initiating a random access request from the N NPRACH formats based on a determined coverage level and the format support information of the terminal device includes: If the terminal device supports NPRACH format 2 and time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, then NPRACH format 2 will be determined as the NPRACH format for initiating random access requests. If the terminal device supports NPRACH format 2 and no time-frequency domain resources of NPRACH format 2 are configured at the determined coverage level, the NPRACH format for initiating a random access request shall be selected from the second type of NPRACH format. If the terminal device does not support NPRACH format 2, the NPRACH format for initiating a random access request is selected from the second type of NPRACH format.

5. A random access processing method, characterized in that, Applied to network-side devices, the method includes: Upon receiving a random access request from a terminal device, determine the coverage level and NPRACH format of the random access request initiated by the terminal device. A random access response is sent to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

6. The method according to claim 5, characterized in that, Determining the coverage level and NPRACH format of the random access request initiated by the terminal device includes: Determine the resource conflict between the terminal-side device and other terminal-side devices that initiate random access requests at the same time; Based on the resource conflict, the coverage level and NPRACH format for the random access request initiated by the terminal device are determined.

7. The method according to claim 6, characterized in that, The step of determining the coverage level and NPRACH format of the random access request initiated by the terminal device based on the resource conflict situation includes: When time-frequency domain resources of the same NPRACH format with different coverage levels conflict, the coverage level is determined based on the number of repetitions of the NPRACH initiating the random access request by the terminal device. When time-frequency domain resources of different NPRACH formats conflict, the NPRACH format is determined based on the subcarrier interval of the random access request initiated by the terminal device.

8. A terminal-side device, characterized in that, The terminal-side device includes: The first determining module is used to determine the coverage level and the narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results. The first sending module is used to send a random access request based on the coverage level and NPRACH format; The receiving module is used to receive random access responses sent by network-side devices, wherein the random access responses carry coverage level and NPRACH format.

9. A network-side device, characterized in that, The network-side device includes: The second determining module is used to determine the coverage level and NPRACH format of the random access request initiated by the terminal device when a random access request is received from the terminal device. The second sending module is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

10. A terminal-side device, characterized in that, Including transceivers and processors, The processor is configured to determine the coverage level and narrowband physical random access channel (NPRACH) format based on the system information block (SIB) message and downlink measurement results. The transceiver is configured to send a random access request based on the coverage level and NPRACH format; and receive a random access response sent by a network-side device, the random access response carrying the coverage level and NPRACH format.

11. A network-side device, characterized in that, Including transceivers and processors, The processor is configured to determine the coverage level and NPRACH format of the random access request initiated by the terminal device upon receiving a random access request sent by the terminal device. The transceiver is used to send a random access response to the terminal-side device, the random access response carrying the coverage level and NPRACH format determined by the network-side device.

12. A terminal-side device, comprising: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the random access processing method as described in any one of claims 1 to 4.

13. A network-side device, comprising: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the random access processing method as described in any one of claims 5 to 7.

14. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the random access processing method as described in any one of claims 1 to 4, or when executed by a processor, implements the steps of the random access processing method as described in any one of claims 5 to 7.

Images