Method and apparatus for transmitting and receiving random access signals

Abstract

The present invention provides a method and apparatus for transmitting and receiving a random access signal. The receiving method includes: a first node transmitting resource configuration information to a second node; and the first node receiving the random access signal transmitted by the second node based on the resource configuration information, wherein the resource configuration information is used to instruct the second node to transmit the random access signal during a valid random access opportunity. The present invention solves the problem of determining the validity of random access opportunities in the related art, thereby achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and avoiding unnecessary interference and power consumption.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a method and device for sending and receiving a random access signal. Background Art

[0002] The next-generation mobile communication system (New Radio, NR) allows for more flexible network configurations and the existence of new types of network nodes than 2G, 3G, and 4G systems. The new type of node, the Integrated Access and Backhaul Node (IAB), which integrates the backhaul link with the normal NR access link, can provide more flexible coverage and networking than single cellular coverage and will be a key component of future mobile communication networks.

[0003] For next-generation mobile communication systems using IAB nodes, they can be considered both ordinary UEs and base stations for other UEs to access. However, in half-duplex mode, IAB nodes cannot transmit and receive simultaneously. Furthermore, their deployment location, antenna configuration, and mobility differ significantly from those of ordinary UEs, placing certain restrictions and requirements on the configuration of random access resources. Furthermore, the redundant connections of IAB nodes and the resource configuration of IAB node DUs also affect random access resource allocation. Therefore, determining the effectiveness of random access opportunities, reducing useless signal transmission, and avoiding unnecessary interference and power consumption, as well as allocating random access resources, are key challenges that need to be addressed.

[0004] With respect to the above technical problems, no effective solutions have been proposed in the relevant technologies. Summary of the Invention

[0005] The embodiments of the present invention provide a method and apparatus for sending and receiving a random access signal, so as to at least solve the problem of determining the validity of a random access opportunity in the related art.

[0006] According to one embodiment of the present invention, a method for receiving a random access signal is provided, comprising: a first node sending resource configuration information to a second node; and the first node receiving the random access signal sent by the second node according to the resource configuration information, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity.

[0007] According to another embodiment of the present invention, a method for sending a random access signal is provided, including: a second node receiving resource configuration information sent by a first node; the second node determining the validity of a random access opportunity based on the resource configuration information; and the second node sending a random access signal to the first node at a valid random access opportunity.

[0008] According to another embodiment of the present invention, a random access signal receiving device is provided, including: a first sending module, configured to send resource configuration information to a second node; and a first receiving module, configured to receive the random access signal sent by the second node according to the resource configuration information, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity.

[0009] According to another embodiment of the present invention, a device for sending a random access signal is provided, including: a second receiving module for receiving resource configuration information sent by a first node; a determination module for determining the validity of a random access opportunity based on the resource configuration information; and a second sending module for sending a random access signal to the first node at a valid random access opportunity.

[0010] According to yet another embodiment of the present invention, a storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0011] According to another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

[0012] Through the present invention, a node sends resource configuration information to a second node, and the first node receives a random access signal sent by the second node based on the resource configuration information. This allows the first and second nodes to determine the validity of random access opportunities based on the resource configuration information. The second node sends a random access signal within a valid random access opportunity, and the first node receives a random access signal within a valid random access opportunity. Therefore, the problem of determining the validity of random access opportunities existing in the related art can be solved, achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and thus avoiding unnecessary interference and power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0014] Figure 1 This is a hardware structure block diagram of a mobile terminal for a method for receiving a random access signal according to an embodiment of the present invention;

[0015] Figure 2 is a flowchart of a method for receiving a random access signal according to an embodiment of the present invention;

[0016] Figure 3 This is a schematic diagram of the IAB network architecture;

[0017] Figure 4 is a schematic diagram of the structure of a MAC PDU according to an embodiment of the present invention;

[0018] Figure 5 is a schematic diagram of a reserved bit included in a MAC PDU according to an optional embodiment of the present invention;

[0019] Figure 6 is a flowchart of a method for sending a random access signal according to an embodiment of the present invention;

[0020] Figure 7 is a structural block diagram of a random access signal receiving apparatus according to an embodiment of the present invention;

[0021] Figure 8 4 is a structural block diagram of a random access signal sending apparatus according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0023] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0024] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 FIG. 1 is a hardware structure block diagram of a mobile terminal for a method for receiving a random access signal according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal 10 may include one or more ( Figure 1 Only one is shown in the figure) processor 102 (processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data. Optionally, the mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0025] The memory 104 can be used to store computer programs, such as software programs and modules of application software, such as the computer program corresponding to the random access signal receiving method in the embodiment of the present invention. The processor 102 executes the computer program stored in the memory 104 to execute various functional applications and data processing, thereby implementing the above-mentioned method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories may be connected to the mobile terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0026] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the telecommunications provider of the mobile terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0027] In this embodiment, a method for receiving a random access signal is provided. Figure 2 is a flow chart of a method for receiving a random access signal according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0028] Step S202: The first node sends resource configuration information to the second node;

[0029] Step S204: The first node receives a random access signal sent by the second node according to the resource configuration information, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity.

[0030] Through the above steps, the first node transmits resource configuration information to the second node, and the first node receives the random access signal transmitted by the second node based on the resource configuration information. This achieves the purpose of the first and second nodes determining the validity of random access opportunities based on the resource configuration information. The second node transmits the random access signal within a valid random access opportunity, and the first node receives the random access signal within a valid random access opportunity. Therefore, the problem of determining the validity of random access opportunities existing in the related art can be solved, achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and thus avoiding unnecessary interference and power consumption.

[0031] Optionally, the execution subject of the above steps may be a first node (eg, a parent IAB node in an IAB node, a donor IAB, an IAB node DU, a base station), etc., but is not limited thereto.

[0032] In this embodiment, the first node may be a Donor IAB DU, or a parent IAB node DU, or a base station, and the second node may be an IAB node, or an IAB node MT, or a relay station, or a terminal.

[0033] In this embodiment, the IAB node can be regarded as a terminal (UE) or a base station accessed by other UEs or IAB nodes. Figure 3 This is a schematic diagram of the IAB network architecture, such as Figure 3 As shown in the figure, a node with a wired connection to the core network is called a donor IAB. A donor IAB is wirelessly connected to one or more IAB nodes and provides wireless access functions for UEs. There is no direct link between the IAB node and the core network. The interaction between the IAB node and the core network requires one or more forwardings and is ultimately achieved with the help of the donor IAB. The IAB node has two functions: 1) Distributed Unit (DU) function, that is, the IAB node provides wireless access functions for UE or child IAB node like a base station; 2) Mobile Terminal (MT) function, that is, IAB nodes are controlled and scheduled by the donor IAB or upper-layer IAB node (i.e., parent IAB node) like UE.

[0034] The links between donor IAB and IAB nodes and the links between IAB nodes are collectively referred to as backhaul links (BL), and the links between IAB nodes and UEs are called access links (AL). Considering that the IAB network supports multiple hops (for example, for the subordinate nodes of IAB node3, it takes 4 hops to connect to the donor IAB, and the interaction with the core network is completed through the donor IAB), in order to describe the links more clearly, specifically, for a specific IAB node, the link between the IAB node and its parent node, that is, the parent IAB node (which may be an ordinary IAB node or a donor IAB) is called the parent backhaul link (parent BL), the link between the IAB node and its child node (child IAB node) is called the child backhaul link (child BL), and the link between the IAB node and an ordinary UE is called the child access link (child AL). In order to ensure the robustness of the parent backhaul link, the IAB network supports redundant connections. For example, an IAB node may have one or more potential parent nodes in addition to the current parent node, such as Figure 3 As shown, there is a wireless connection between IABnode4 and the donor IAB node, and there is also a potential wireless connection with IAB node1.

[0035] This embodiment can be applied to the transmission of random access signals between IAB nodes. In half-duplex operation, an IAB node cannot transmit and receive simultaneously. For example, when IAB node 2MT sends a random access preamble to IAB node 1, it cannot simultaneously receive a random access preamble sent by child IAB node 3 or child UEs. Furthermore, the deployment location, antenna configuration, and mobility of IAB nodes differ significantly from those of ordinary UEs, placing certain restrictions and requirements on the configuration of random access resources. Furthermore, the redundant connections of IAB nodes and the resource configuration of IAB node DUs also affect the configuration of random access resources. Therefore, random access resources, i.e., resource configuration information, can be configured for the IAB node.

[0036] Furthermore, in NR Release 15, the frequency domain configuration of random access resources is implemented by providing a starting frequency and a random access opportunity (PRACH occasion, RO) for frequency domain multiplexing. The time domain configuration of random access resources is presented in a table format, with different tables corresponding to different frequency bands and duplex modes. Each table contains 256 configurations, with configuration indexes ranging from 0 to 255. During actual configuration, the base station only needs to provide a single configuration index. For example, for TDD systems in frequency bands above 6 GHz (i.e., FR2 and unpaired spectrum), the random access time domain resource configuration is shown in Table 1. (Due to the large number of rows in the table, only some configurations are shown here.)

[0037] Table 1:

[0038]

[0039] The meanings of the columns in Table 1 are as follows:

[0040] Column 1 PRACH Config.Index: PRACH configuration index;

[0041] Column 2 Preamble format: random access format;

[0042] Column 3 (including x and y): x is the PRACH configuration period, ranging from 1 to 16, in units of radio frames, i.e., the PRACH configuration period is 10x milliseconds; y is the remainder of the system frame number (SFN) modulo x, which physically means the radio frame within the PRACH configuration period in which there will be a PRACH timeslot or PRACH opportunity. For example, y = 0 is the first radio frame, and y = 0 is the second radio frame.

[0043] Column 4: Slot number: The timeslot containing the ROs. For frequency bands below 6 GHz (i.e., FR1), it is the Subframe number.

[0044] Column 5 Starting symbol: The starting symbol number of the RO in the PRACH time slot (0 to 13).

[0045] Column 6 Number of PRACH slots within a 60kHz slot: When the PRACH subcarrier spacing is 120kHz, whether the PRACH time slot is the second time slot within the 60kHz slot (parameter is 1), or whether both time slots within the 60kHz slot are PRACH time slots (parameter is 2).

[0046] Column 7 Number (#) of time-domain PRACH occasions within a PRACH slot: the number of time-domain ROs within a PRACH time slot.

[0047] The eighth column, PRACH duration, indicates the number of OFDM symbols occupied by each random access format. For example, A1 is 2 symbols, and C2 is 6 symbols. The sequence in C2 occupies 4 symbols, and the rest are CP and GP. For the long random access format (sequence length 839), the value is uniformly set to 0, which has no practical physical meaning.

[0048] In an optional embodiment, considering that the IAB node needs to meet the half-duplex constraint, that is, it cannot transmit and receive simultaneously, the resource configuration information of the IAB node may include at least one of the following: a configuration index of a physical random access channel (PRACH), frequency domain resources of the PRACH, a mapping relationship between synchronization signal blocks (SSBs) and random access opportunities (ROs), a starting logical root sequence index and a cyclic shift (Ncs), a configuration period scaling factor (S) of the PRACH, an offset (y_offset) based on a radio frame, an offset (sf_offset) based on a subframe, an offset (s_offset) based on a time slot, a time slot number, a subframe number, an unavailable resource configuration, and an available resource configuration.

[0049] In this embodiment, the resource configuration information must meet the following conditions: For an IAB node, the PRACH resources configured on its parent backhaul link and child links (including the child access link and child backhaul link) must be time division multiplexed (TDM), that is, orthogonal in the time domain. In other words, the PRACH resources used by the IAB node MT to transmit preambles are orthogonal in the time domain to the PRACH resources used by the IAB node DU to receive preambles (i.e., the PRACH resources used by child UEs and child IAB nodes to transmit preambles).

[0050] The coverage characteristics and mobility of IAB nodes are different from those of ordinary UEs. As a special combination of base stations and terminals, the deployment location of IAB nodes is very different from that of ordinary terminals. For example, IAB nodes are often fixed under eaves and hung much higher than ordinary terminals to facilitate the establishment of a direct line of sight with donor IAB or parent IAB nodes. For example, IAB nodes often have more antennas than ordinary terminals. For example, IAB nodes may need to be placed farther away from IAB donors or parent IAB nodes than ordinary terminals (e.g. Figure 3 In addition, IAB nodes are usually located in fixed positions, which means that the channel conditions are relatively stable. Therefore, IAB nodes can be configured with a larger PRACH configuration period, that is, the x in the third column of the PRACH configuration table can be larger.

[0051] Different random access formats support different coverage ranges, mobility speeds, and resistance to penetration loss. Therefore, ordinary UEs and IAB nodes have different requirements for PRACH resources. An IAB node or donor IAB needs to configure different PRACH resources for child UEs and child IAB nodes, including configuring PRACH configuration indexes, PRACH frequency domain resources, the mapping relationship between SSBs and valid random access opportunities (ROs), and preambles (including the starting logical root sequence index, cyclic shift Ncs, and other parameters used to generate the preamble sequence).

[0052] To reduce complexity, the PRACH time domain resource configuration for IAB nodes can be simply extended based on the PRACH configuration table for UEs in NR Release 15, including:

[0053] The PRACH configuration period x in the extended PRACH configuration table, assuming the scaling factor is S, the extended PRACH configuration period is S*x.

[0054] The offset y_offset of the radio frame containing ROs relative to the PRACH configuration table, and / or the offset sb_offset of the subframe containing ROs relative to the PRACH configuration table, and the offset s_offset of the time slot containing ROs.

[0055] The extended PRACH configuration period serves as the PRACH configuration period of IAB nodes, and the offset radio frame or subframe or time slot serves as the subframe or time slot containing ROs of IAB nodes; or the extended PRACH configuration period serves as the PRACH configuration period of IABnodes, and the Parent IAB node can directly configure the slot number to replace the slot number indicated by the PRACH configuration index. The replaced slot number is a set of time slot numbers containing ROs; or the extended PRACH configuration period serves as the PRACH configuration period of IAB nodes, and the Parent IAB node can directly configure the subframenumber to replace the subframe number indicated by the PRACH configuration index. The replaced subframe number is a set of subframe numbers containing ROs.

[0056] You can configure the slot number or subframe number in any of the following ways:

[0057] Method 1: Predefine multiple groups of configurations, each group of configurations corresponds to a time slot index set or a subframe index set, each group of configurations has an index, and the configuration index is provided to the IAB node MT.

[0058] Method 2: Use bitmap indication. For example, the slot number or subframe number corresponding to the bit value 1 is used to replace the slot number or subframe number indicated by the PRACH configuration index.

[0059] Among them, for FR1, the length of the bitmap is the number of subframes contained in the radio frame, and for FR2, the length of the bitmap is the number of time slots with a 60kHz subcarrier spacing contained in the radio frame; or, for all frequency bands, the length of the bitmap is the number of time slots with a 60kHz subcarrier spacing contained in the radio frame. For FR1, only some bits are valid, such as the lower 10 bits or the upper 10 bits.

[0060] If the PRACH resource configurations of UEs and IAB nodes are different, IAB nodes can determine whether a cell can provide services for IAB nodes based on the PRACH resource configuration of the cell during initial access or handover, thereby avoiding selecting a cell that cannot provide services for IAB nodes.

[0061] Because UEs and IAB nodes have different PRACH resource configurations, UEs may not be able to know the PRACH resources of IAB nodes. Therefore, if the Random Access Responses (RARs) of UEs and IAB nodes are reused, even if the UE and IAB node use different PRACH resources, only one of them can successfully perform random access. For example, a UE and an IAB node MT use the same PRACH time-frequency resources, but different random access formats and preamble sequences (but the sequence index range is 0 to 64). That is, the starting root sequence index and cyclic shift of the preamble sequence generated by the IAB node are different from those of ordinary terminals. In this case, the expectation is that ordinary terminals and IAB terminals (IAB node MT) can simultaneously successfully access the same PRACH time-frequency resources and preamble sequence identifier. However, the existing mechanism causes the UE and IAB node to correspond to the same RAR, and at most one of them can successfully perform random access. For example, the PRACH resources of a UE and an IAB node start at the same time domain position but are orthogonal in the frequency domain (i.e., using FDM). Since both frequency domain resource indices start at 0, for example, a standard terminal multiplexes 8 resources in the frequency domain, while an IAB node multiplexes 4 resources, their corresponding frequency domain resource indices range from 0 to 7 and 0 to 4, respectively. Therefore, even if their RACH resources do not overlap, their calculated RA-RNTIs may be the same. If both use the same preamble sequence identifier, they will be associated with the same RAR, and at most only one of them can successfully access the network. This not only increases the random access latency for standard or IAB terminals but also generates unnecessary interference during subsequent random access procedures. Therefore, it is necessary to distinguish the RARs of UEs and IAB nodes. For example, IAB nodes can use a different RA-RNTI calculation formula than UEs, or use a reserved field in the MAC (Media Access Control) RAR (Random Access Response) to indicate the MAC RAR of the IAB terminal (IAB node MT).

[0062] The RA-RNTI is used to scramble a cyclic redundancy check (CRC) of a PDCCH corresponding to a random access response.

[0063] In an optional embodiment, the frequency domain resources of the PRACH include: the starting frequency of the PRACH resources; the number of PRACHs multiplexed in the frequency domain. In this embodiment, the starting frequency of the PRACH resources can be determined in one of the following ways: the first node determines the starting frequency of the PRACH resources based on the activated uplink bandwidth BWP; the first node determines the starting frequency of the PRACH resources based on the offset of the starting physical resource block PRB of the initial access PRACH frequency domain resources of the terminal device; the first node determines the starting frequency of the PRACH resources based on the offset of the ending PRB of the initial access PRACH frequency domain resources of the terminal device;

[0064] In this embodiment, the starting frequency can be defined based on the activated uplink bandwidth part (BWP), or based on the offset of the starting PRB or ending PRB relative to the PRACH frequency domain resource initially accessed by the UEs. For example, the starting frequency is the offset relative to the first physical resource block (PRB) of the activated uplink BWP, that is, the offset relative to PRB0. Alternatively, the starting frequency is the offset of the first PRB or the offset of the last PRB relative to the PRACH frequency domain resource initially accessed by the UEs.

[0065] Optionally, the PRB corresponds to the subcarrier spacing corresponding to the activated uplink BWP.

[0066] Optionally, the default value of the start frequency is PRB0 of the activated uplink BWP.

[0067] Optionally, the activated uplink BWP is an initially activated uplink BWP in an initial access phase or an activated uplink BWP after initial access.

[0068] The starting logical root sequence index and the cyclic shift Ncs are used to generate the IAB nodes dedicated preamble.

[0069] Optionally, a portion of the 64 preambles used for random access of UEs may also be designated as dedicated preambles for IABnodes.

[0070] The number of IAB nodes is less than that of UEs, so the total number of preambles dedicated to IAB nodes can be less than 64, such as 8, 16, or 32.

[0071] In an optional embodiment, the offset y_offset of the radio frame includes: an offset relative to a preset parameter y in a preset resource configuration table of the PRACH, where the preset parameter y refers to a radio frame index including a PRACH occasion within a PRACH configuration period, and the preset parameter y is used to indicate a radio frame including a PRACH occasion within the PRACH configuration period.

[0072] Wherein, y_offset may be an offset relative to the parameter y in the PRACH configuration table, or a quantity used to replace the parameter y.

[0073] Assume that the maximum of the IAB PRACH configuration period is Tmax frames. The SFN containing ROs satisfies:

[0074] mod(SFN,x*S)=mod(y+y_offset,x*S), where 0≤y_offset<Tmax or 0≤y_offset<x*S. Or,

[0075] mod(SFN,min{x*S,Tmax})=mod(y+y_offset,min{x*S,Tmax}), where 0≤y_offset<Tmax or 0≤y_offset<x*S or 0≤y_offset<min{x*S,Tmax}.

[0076] Wherein, the subframe-based offset sf_offset is an offset relative to the subframe number subframenumber in the PRACH configuration table.

[0077] Wherein, the slot-based offset s_offset is an offset relative to the slot number slot number in the PRACH configuration table.

[0078] According to the existing protocol, the slot / subframe number is the number within a radio frame (10 ms), each subframe is 1 ms, and the slot number is relative to the 60 kHz subcarrier spacing. Since a radio frame contains 10 subframes, the subframe number after offsetting sf_offset and the value range of sf_offset are as follows:

[0079] SF_number=mod(sf_number+sf_offset,10), where 0≤sf_offset<10;

[0080] Among them, sf_number represents the subframe number corresponding to the Rel-15PRACH configuration index, and SF_number represents the subframe number after the offset sf_offset.

[0081] Because a wireless frame contains 40 60kHz slots, the slot number after the offset s_offset and the value range of s_offset are as follows:

[0082] S_number = mod(s_number + s_offset, 40), where 0 ≤ s_offset < 40;

[0083] Among them, s_number represents the slot number corresponding to the Rel-15PRACH configuration index, and S_number represents the subframe number after the offset s_offset.

[0084] For each PRACH configuration index, a PRACH configuration period scaling factor S is configured separately; or, for the entire PRACH configuration table, one PRACH configuration period scaling factor is configured.

[0085] If the following parameters are not configured for IAB nodes (IAB terminals): PRACH configuration index, PRACH frequency domain resources, mapping relationship between SSB and valid ROs, any one or any combination of preambles, or any other parameters related to PRACH resources are not configured for IAB nodes, the IAB nodes reuse the corresponding parameters in the PRACH resource configuration of UEs.

[0086] The IAB nodes determine the PRACH resource according to the PRACH configuration index and the PRACH frequency domain resource, in combination with at least one of the scaling factor S, the offset y_offset, the offset s_offset, and the offset sf_offset.

[0087] Optionally, for the scaling factor S, offset y_offset, offset s_offset, offset sf_offset, if not configured, the default value is 0.

[0088] In an optional embodiment, in addition to the above parameters, the parent IAB node further needs to provide the following at least one PRACH-related parameter for the IAB nodes: the total number of available random access preambles, the total number of contention-based preambles corresponding to each SSB, the total number of contention-based preambles in group A corresponding to each SSB, the transmission block size threshold for selecting a preamble group, the path loss calculation parameter for selecting a preamble group, the subcarrier spacing used for the random access signal (msg1), the SSB reception power threshold that the selected SSB and the corresponding PRACH resources need to meet, power-related parameters, restriction set configuration, precoding of msg3, etc.

[0089] In an optional embodiment, the subframe number includes: the subframe number indicated by the PRACH configuration index in the preset resource configuration table for replacing the PRACH, where the replaced subframe number is an index set including ROs subframes. The slot number includes: the slot number indicated by the PRACH configuration index in the preset resource configuration table for replacing the PRACH, where the replaced slot number is an index set including ROs slots.

[0090] In the above embodiment, it is assumed that the maximum PRACH configuration period of the IAB nodes is Tmax system frames. Optionally, Tmax is one of 16, 32, 64, 128, 256. The scaling factor S = 2 k , where k is a non-negative integer, that is, S is a non-negative integer power of 2, and its maximum value depends on the maximum value of the PRACH configuration period of the IAB nodes.

[0091] For each PRACH configuration index, the maximum value of S depends on the maximum value Tmax of the PRACH configuration period of the IAB nodes and the x value in the PRACH configuration index. For example, the maximum value of S is Tmax divided by x.

[0092] For the IAB nodes, the system frame number SFN containing ROs can be determined according to the following several methods:

[0093] Method 1: SFN satisfies mod(SFN, S * x) = mod(y + y_offset, S * x), where y_offset is an integer, and 0 ≤ y_offset < Tmax or 0 ≤ y_offset < S * x or 0 ≤ y_offset < min{x * S, Tmax}.

[0094] Method 2: y = y_offset, that is, directly replace the parameter y in the configuration table, that is, SFN satisfies mod(SFN, x * S) = y_offset, where y_offset is an integer, and 0 ≤ y_offset < S * x.

[0095] 3) If the PRACH configuration index y contains multiple values, then y_offset is the first value y1 of parameter y, and the other values in parameter y are the difference between the corresponding value and y1 in the PRACH configuration table + y_offset. For example, if y = {y1, y2} in the PRACH configuration table, then y = {y_offset, y_offset + y2 - y1} can be obtained from y_offset. Otherwise, y = y_offset. Where y_offset is an integer and 0 ≤ y_offset <S*x;

[0096] Where y is parameter y in the PRACH configuration table.

[0097] It should be noted that if S*x>Tmax, then S*x=Tmax, otherwise the above formula remains unchanged.

[0098] Considering that in NR R15, for FR1, each PRACH configuration index corresponds to a y value, that is, all ROs are contained in one frame within the PRACH configuration period; for the FR2 frequency band, there is usually only one y value, and the y corresponding to a few configurations is {1,2}. Considering that the channel conditions between IAB nodes are relatively stable, there is no need to configure multiple frames to contain ROs within a PRACH configuration period. Therefore, method 2 is a simpler and more intuitive y_offset solution.

[0099] In an optional embodiment, different PRACH frequency domain index numbers may be used or the PRACH frequency domain index numbers may be offset to calculate the RA-RNTI.

[0100] In existing protocols, the maximum number of PRACHs multiplexed by a UE in the frequency domain is 8, and the index number f_id is an integer in the range of 0≤f_id<8. Therefore, the PRACH indexes multiplexed by an IAB node in the frequency domain can be numbered starting from 8. Assuming that the maximum number of PRACHs multiplexed by an IAB node in the frequency domain is Nprach, the value of Nprach can be predefined and the RA-RNTI value is less than 65519. Then, the PRACH index number multiplexed by an IAB node in the frequency domain is an integer in the range of 8≤f_id<8+Nprach.

[0101] In order to distinguish it from the UE's RA-RNTI (Random Access RNTI, RNTI: Radio Network Temporary Identifier), therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH transmitting the random access preamble is calculated by the following formula:

[0102] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×(8 + Nprach)×ul_carrier_id Formula 1;

[0103] Where, s_id is the index of the first OFDM symbol of the given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of the given PRACH within the system frame (0 ≤ t_id < 80), f_id is the index of the given PRACH in the frequency domain (8 ≤ f_id < 8 + Nprach), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier)

[0104] In addition, there is another way that the PRACH indexes multiplexed by the IAB node in the frequency domain are numbered starting from 0, and f_id in the RA-RNTI calculation formula for IAB nodes is offset by 8. Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH transmitting the random access preamble is calculated by the following formula:

[0105] RA-RNTI = 1 + s_id + 14×t_id + 14×80×(f_id + 8) + 14×80×(8 + Nprach)×ul_carrier_id Formula 2;

[0106] Where, s_id is the index of the first OFDM symbol of the given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of the given PRACH within the system frame (0 ≤ t_id < 80), f_id is the index of the given PRACH in the frequency domain (0 ≤ f_id < Nprach), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier).

[0107] Optionally, if Nprach = 8, then the above two Formulas 1 and 2 are respectively:

[0108] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×16×ul_carrier_id.

[0109] RA-RNTI=1+s_id+14×t_id+14×80×(f_id+8)+14×80×16×ul_carrier_id

[0110] In an optional embodiment, different time slot indices or time slot index offsets may be used to calculate the RA-RNTI.

[0111] The time slot indexes of IAB nodes in a radio frame are numbered starting from 80, that is, the first time slot index in a radio frame is 80, the second is 81, and so on.

[0112] Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH that transmits the random access preamble is calculated using the following formula:

[0113] RA-RNTI=1+s_id+14×t_id+14×160×f_id+14×160×8×ul_carrier_id

[0114] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (80≤t_id<160), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0115] In addition, another method is to number the time slot indexes of IAB nodes in the radio frame starting from 0, and offset the t_id in the RA-RNTI calculation formula of IAB nodes by 80.

[0116] Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH that transmits the random access preamble is calculated using the following formula:

[0117] RA-RNTI=1+s_id+14×(t_id+80)+14×160×f_id+14×160×8×ul_carrier_id

[0118] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is used to indicate the uplink carrier for transmitting the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0119] In an optional embodiment, the RA-RNTI corresponding to the PRACH transmitting the random access preamble may also be calculated using the following formula:

[0120] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×identifier

[0121] Among them, s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), ul_carrier_id is used to indicate the uplink carrier for transmitting the random access preamble code (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier), and identifier is used to indicate whether the RA-RNTI calculation formula is for a normal terminal or an IAB node. For a normal terminal, identifier is 0, and for an IAB node, identifier is 1.

[0122] In an optional embodiment, for an IAB terminal (IAB node MT), the RA-RNTI corresponding to the PRACH transmitting the random access preamble is calculated using the following formula:

[0123] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

[0124] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is used to indicate the uplink carrier for transmitting the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0125] For a normal terminal, the RA-RNTI corresponding to the PRACH for transmitting a random access preamble is calculated by the following formula:

[0126] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0127] Where s_id is the index of the first OFDM symbol of the given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of the given PRACH within a system frame (0 ≤ t_id < 80), f_id is the index of the given PRACH in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier).

[0128] In an optional embodiment, for an IAB node, the RA-RNTI corresponding to the PRACH for transmitting a random access preamble is calculated by the following formula:

[0129] RA-RNTI = 1 + s_id + s×t_id + s×t×f_id + s×t×f×ul_carrier_id + s×t×f×2; or,

[0130] RA-RNTI = 1 + s_id + s×t_id + s×t×f_id + s×t×f×ul_carrier_id;

[0131] Where s_id is the index of the first OFDM symbol of the given PRACH (s0 ≤ s_id < s), t_id is the index of the first time slot of the given PRACH within a system frame (t0 ≤ t_id < t), f_id is the index of the given PRACH in the frequency domain (f0 ≤ f_id < f), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier).

[0132] Where the OFDM symbols within a time slot are numbered starting from s0, that is, the index of the first OFDM symbol within the time slot is s0, the second is s0 + 1, and so on;

[0133] Where the time slot indices within a radio frame are numbered starting from t0, that is, the index of the first time slot within the radio frame is t0, the second is t1, and so on; the time slot indices within a radio frame are numbered starting from t0, that is, the index of the first time slot within the radio frame is t0, the second is t0 + 1, and so on;

[0134] Among them, the PRACH index in the frequency domain is numbered starting from f0, that is, starting from the low frequency. The PRACH index of the first PRACH resource in the frequency domain is f0, the second is f0+1, and so on.

[0135] Among them, the values of s0, t0, f0, s, t, and f need to be predefined, for example, s0=0, t0=0, f0=0, s=14, t=80, f=8; or s0=14, t0=0, f0=0, s=28, t=80, f=8; or s0=0, t0=80, f0=0, s=14, t=160, f=8; or s0=0, t0=0, f0=8, s=14, t=80, f=16.

[0136] In an optional embodiment, a reserved field in the MAC RAR is used to indicate a dedicated MAC RAR for IAB nodes.

[0137] In NR Rel-15, as Figure 4 As shown in Figure 1, a MAC PDU contains one or more MAC subPDUs and optional padding. Each MAC subPDU consists of one of the following:

[0138] -BI only: only the MAC subheader with Backoff indication;

[0139] -RAPID (Random Access Preamble Identifier) only: MAC subheader with RAPID only (i.e., confirmation of system information request);

[0140] -RAPID and RAR: MAC header with RAPID and MAC RAR.

[0141] If the MAC PDU contains BI only, the BI only is located at the beginning of the MAC PDU. RAPID only and RAPID and RAR can be placed anywhere between the BI only and the padding in the MAC PDU.

[0142] like Figure 5 As shown, the reserved bit R in the MAC RAR can be used to indicate whether the MAC RAR is the MAC RAR of the IAB nodes. For example, R=0 indicates that it is not the MAC RAR of the IAB nodes, and R=1 indicates that it is the MAC RAR of the IAB nodes, and vice versa.

[0143] Each MAC RAR corresponds to a subheader, which contains a RAPID. The subheader and MAC RAR form a MAC subPDU. If the RAPID corresponding to the random access signal sent by a common terminal (UE) is the same as the RAPID corresponding to the random access signal sent by IAB nodes in the MAC PDU, the MAC subPDU for the common terminal should be before the MAC subPDU for the IAB nodes. For example, if the MAC subPDU corresponding to the terminal is the nth, then the MAC subPDU corresponding to the IAB nodes is the n+kth, where k is a positive integer.

[0144] When the PRACH time-frequency resources for sending preamble signals of ordinary terminals and IAB terminals are the same, and the preamble index is the same, the RA-RNTI of ordinary terminals and IAB terminals are the same, and the RAPID of ordinary terminals and IAB terminals are also the same, their MAC RARs will be multiplexed in one MAC PDU. In order for the IAB terminal to distinguish its own MAC RAR, the reserved bit R in the MAC RAR can be used to indicate whether the MAC RAR is the MAC RAR of the IAB terminal. In order to prevent the ordinary terminal from mistakenly detecting the MAC RAR of the IAB terminal, the MAC subPDU of the ordinary terminal should be in front of the MACsubPDU of the IAB terminal in the MAC PDU.

[0145] Because ordinary terminals cannot identify R, this can prevent ordinary terminals from mistaking the MAC RAR of the IAB terminal as their own, causing access failure and also affecting the initial access of the IAB terminal.

[0146] It should be noted that in the calculation formulas of all RA-RNTIs in the above examples, for random access formats 0, 1, 2 and 3 (i.e., long format with a preamble length of 839), s_id and t_id are determined according to the subcarrier spacing of the activated uplink BWP where the PRACH resource is located. For random access formats A1 / B1, A2 / B2, A3 / B3, A1, A2, A3, B1, B4, C0, C2 (i.e., short format with a preamble length of 139), s_id and t_id are determined according to the subcarrier spacing of the activated uplink BWP where the PRACH resource is located, or according to the subcarrier spacing of the PRACH, which needs to be pre-defined by the protocol.

[0147] Optionally, for random access formats A1 / B1, A2 / B2, A3 / B3, A1, A2, A3, B1, B4, C0, C2 (i.e., preamble length is 139 short format), s_id and t_id are determined according to the subcarrier spacing of PRACH.

[0148] In an optional embodiment, the validity of the random access opportunity may be determined by one of the following methods:

[0149] In the case where the first node does not provide the uplink and downlink configuration of time division duplex for the second node, the random access opportunity is valid if the random access opportunity meets the following conditions: the random access opportunity is not before the SSB in the time slot of the PRACH, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0150] In the case where the first node provides a time division duplex uplink and downlink configuration for the second node, the random access opportunity is valid if the random access opportunity meets one of the following conditions: the random access opportunity is within the uplink symbol and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0151] The specific resources include at least one of the following: resources indicated by an unavailable resource configuration, resources that cannot be used by the second node, hard resources of the base station unit of the second node, hard resources used by the base station unit of the second node for transmitting important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources used by the base station unit of the second node for transmitting important signals or channels;

[0152] Important signals or channels include at least one of the following: SSB, system information, PRACH, URLLC signals or channels.

[0153] In this embodiment, the IAB node has two functional units, the MT and the DU. The MT is the unit in the IAB node that acts as a UE. Therefore, the resource types of the MT are the same as those of a regular UE, including downlink time resources (D), uplink time resources (U), and flexible time resources (F). F can be flexibly used as an uplink or downlink resource. For the DU, its resource types are: D, U, F, and unavailable time resources (NA). NA refers to resources that the DU cannot use. Each D, U, and F has the following two attributes: hard and soft. Hard refers to resources that are always available to the DU. The availability of soft resources can be further indicated explicitly or implicitly. Therefore, the resources for the DU include the following seven types: hardD, softD, hardU, softL, hardF, softF, and NA.

[0154] The IAB node DU resource configuration needs to consider the compromise between configuration flexibility and bit overhead. Since the IAB node DU is to provide services for ordinary UEs, the DU resource configuration may also be restricted by the common TDD uplink and downlink configuration (e.g., TDD-UL-DL-ConfigurationCommon) mode of Release 15. Therefore, for an IAB node, since the PRACH time domain resource configuration is selected from a table and the selection is also affected by the common TDD uplink and downlink configuration, the NA resources of the parent IAB node DU may overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain. In addition, for an IAB node, it is very likely that the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain. In this case, a relevant solution is needed to enable the IAB node to work under half-duplex constraints.

[0155] In addition, the IAB node may need to randomly access other IAB nodes other than the current parent IAB node, which we call potential parent IAB nodes for the convenience of description. Figure 3In addition to randomly accessing the donor IAB (i.e., parent IAB node), IAB node4 may also need to randomly access IAB node1, for example, to maintain basic synchronization with IABnode1 so that it can quickly switch to IAB node1 when the link quality between IAB node4 and donor IAB is poor. Alternatively, IAB node4 may need to perform random access to IAB node1 and switch to IAB node1. That is, IAB node1 is a potential parent IAB node for IAB node4. However, the PRACH resources configured by the parent IAB node and the potential parent IABnode for the IAB node MT may be different. Therefore, even if the PRACH resources configured by the parent IAB node for the IAB nodeMT and the hard resources of the IAB node DU do not overlap in the time domain, it is difficult to simultaneously ensure that the PRACH resources configured by one or more potential parent IAB nodes for the IAB node MT and the hard resources of the IAB node DU are orthogonal in the time domain. In this case, a relevant solution is also needed to enable the IAB node to operate under half-duplex constraints.

[0156] The random access opportunity obtained based on the PRACH resource configuration may be invalid. For example, the random access opportunity overlaps with the downlink signal SSB in the time domain. Due to half-duplex or interference limitations, the parent IAB node cannot receive the uplink random access signal when sending the SSB. Therefore, the terminal (UE or IAB node MT) does not need to send the uplink random access signal. Therefore, it is necessary to formulate a criterion for judging the validity of the random access opportunity. Otherwise, not only will interference be generated, but the transmitting and receiving ends of the random access signal will also have inconsistent understandings of the mapping between the SSB and the random access opportunity, resulting in random access failure.

[0157] In an optional embodiment, the rules for determining the validity of the random access opportunity are as follows:

[0158] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0159] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the terminal, the random access opportunity in the PRACH time slot is valid if it does not precede the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol.

[0160] If time division duplex uplink and downlink configuration is provided for the terminal, the random access opportunity is valid if it is within the uplink symbol; or, the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol; or, the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol; or, the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol.

[0161] According to the above mechanism, the valid random access opportunity obtained may not be available to the IAB terminal. Therefore, it is necessary to enhance the existing random access validity judgment mechanism, or further judge the availability of the valid random access opportunity judged by the existing mechanism.

[0162] The PRACH time slot refers to a time slot including a PRACH opportunity corresponding to the PRACH subcarrier spacing.

[0163] In an optional embodiment, the unavailable resource configuration provided by the parent IAB node for the IAB nodes is used to indicate time resources that the IAB node MT cannot use, that is, unavailable resources for the IAB node MT. If the PRACH resources configured by the parent IAB nodes for the IAB node MT overlap with the unavailable resources in the time domain, the random access opportunities that overlap with the unavailable resources in the time domain are invalid, that is, the IAB node MT cannot use the random access opportunities that overlap with the unavailable resources in the time domain.

[0164] The PRACH resource may be a common PRACH resource configured by a system message, or a dedicated PRACH resource configured by a dedicated RRC signaling.

[0165] Unavailable resources are either continuous-time resources or discrete-time resources.

[0166] Optionally, the unavailable resources may include at least one of the following: unavailable resources of the parent IAB node DU, a subset of the unavailable resources of the parent IAB node DU, unavailable resources of the potential parent IAB node DU, a subset of the unavailable resources of the potential parent IAB node DU, hard resources of the child IAB node DU of the parent IAB node, hard UL resources of the child IAB node DU of the parent IAB node, and unusable PRACH resources. The determination of the unavailable resources depends on the implementation of the parent IAB node DU.

[0167] Optionally, the child IAB node DU and the IAB node MT are located in the same IAB node.

[0168] Optionally, the unavailable resources are continuous time resources or discrete time resources within each radio frame.

[0169] Optionally, the method of indicating unavailable resources in each wireless frame is any one of the following: 1. the k1th to k2th subframes or time slots; 2. the last M1 subframes or time slots; 3. the last M2 even-numbered subframes or time slots; 4. the last M3 odd-numbered subframes or time slots; 5. indication by a resource indicator value (RIV); 6. bitmap, where the bitmap length is the number of subframes or time slots contained in the wireless frame, and it is pre-agreed whether 0 or 1 in the bitmap represents unavailable resources; 7. grouping of resources in the wireless frame, and using the bitmap of the grouped resources to indicate that one or more groups are unavailable resources.

[0170] The RIV is determined based on the number N of subframes or time slots contained in the radio frame, the starting subframe or time slot Tstart of unavailable resources, and the number L of consecutive subframes or time slots:

[0171] If (L-1) <floor(N / 2),

[0172] Then RIV=N(L-1)+Tstart,

[0173] Otherwise, RIV = N(N-L+1)+(N-1-Tstart)

[0174] Among them, k1, k2, M1, M2, and M3 are integers less than or equal to N.

[0175] Optionally, the unavailable resource is a periodically unavailable continuous-time resource or a discrete-time resource.

[0176] Optionally, the unavailable resource configuration includes a period, a bitmap, or a RIV. The bitmap is used to indicate that one or more subframes or time slots within the period are unavailable resources as 0 or 1. The length of the bitmap is the number of subframes or time slots contained in the period. It is pre-agreed whether 0 or 1 in the bitmap indicates unavailable resources. For example, it is agreed that 0 in the bitmap indicates unavailable resources. The RIV indicates that one or more consecutive subframes or time slots starting from the starting subframe or time slot are unavailable resources. The RIV calculation method is the same as the indication within the radio frame.

[0177] Optionally, the unavailable resource configuration includes at least one of the following parameters: a period, an offset O within the period, and a duration t, wherein the granularity of the offset O within the period and the duration t is a subframe or a PRACH time slot.

[0178] Optionally, for the above cycles, the starting position of the first cycle is aligned with the starting position of radio frame 0.

[0179] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0180] For unpaired spectrum (time division duplex), the effectiveness of random access timing is also related to the time division duplex uplink and downlink configuration and the time domain position of SSB.

[0181] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource in the time domain.

[0182] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the first resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the first resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the first resource in the time domain.

[0183] The first resource is a resource indicated by the unavailable resource configuration, which the IAB node MT can obtain from the unavailable resource configuration provided by the parent IABnode for the IAB nodes.

[0184] In an optional embodiment, the parent IAB node provides an available resource configuration for the IAB node, which indicates the time resources that the IAB node MT can use, i.e., the IAB node MT available resources. If the random access opportunity configured by the parent IAB node for the IAB node MT is within the available resources, the random access opportunity is valid, i.e., the IAB node MT can use the random access opportunity within the available resources.

[0185] Available resources are either continuous-time resources or discrete-time resources.

[0186] Optionally, the available resources are any one or any combination of the following: available resources of the parent IAB node DU, a subset of the available resources of the parent IAB node DU, available resources of the potential parent IAB node DU, a subset of the available resources of the potential parent IAB node DU, unavailable resources NA of the child IAB node DU of the Parent IAB node, soft D resources of the child IAB node DU of the Parent IAB node, soft U resources of the child IAB node DU of the Parent IAB node, hard D resources of the child IAB node DU of the Parent IAB node, hard F resources of the child IAB node DU of the Parent IAB node, soft F resources of the child IAB node DU of the Parent IAB node, and usable PRACH resources. The determination of the available resources depends on the implementation of the parent IAB node DU.

[0187] Optionally, the child IAB node DU and the IAB node MT are located in the same IAB node.

[0188] The method for indicating available resources is similar to the method for indicating unavailable resources, and will not be described in detail here.

[0189] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0190] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it does not precede the SSB in the PRACH time slot and the random access opportunity starting point is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the available resources.

[0191] If time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity is within the available resources; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the available resources; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the available resources; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the available resources.

[0192] The available resources are resources indicated by the available resource configuration.

[0193] In an optional embodiment, the validity of the random access opportunity may also be determined in the following manner:

[0194] For an IAB node, the hard resources of the IAB node DU are resources that can be used by the DU, that is, the resources that can be used by the sub-links (including sub-access links and sub-backhaul links) of the IAB node. If the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, then due to half-duplex limitations, the IABnode MT and the DU may not be able to use the overlapping resources at the same time. Therefore, one way to deal with this is: if the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, then the random access opportunity that overlaps with the DU's hard resources in the time domain is invalid, that is, the IAB node MT cannot use the random access opportunity that overlaps with the DU's hard resources in the time domain to send a preamble signal.

[0195] However, for the IAB node that supports frequency division multiplexing (FDM) and space division multiplexing (SDM), the IAB node MT and IABnode DU can send or receive at the same time. Therefore, if the hard resource is hard DL or hard F, the IAB node MT and IAB node DU can send at the same time, so the IAB node MT can consider that the random access opportunity that overlaps with the hard DL or hard F of the DU in the time domain is still valid. Therefore, for the IAB node that supports frequency division multiplexing (FDM) and space division multiplexing (SDM), the validity of the random access opportunity can also be judged as follows: If the hard UL of the IAB node DU overlaps with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, the random access opportunity that overlaps with the hard UL of the DU in the time domain is invalid.

[0196] Since the resource configuration of the IAB node DU is obtained only after the IAB node MT completes initial access, the IAB node MT cannot obtain the resource configuration of the IAB node DU during initial access. Therefore, the resource configuration of the IAB node DU can be used only for determining the validity of dedicated PRACH resources, or it can also be used to determine the validity of public PRACH resources after the IAB node MT initially accesses.

[0197] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0198] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the second resource in the time domain.

[0199] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the second resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the second resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the second resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the second resource in the time domain.

[0200] The second resource is a hard resource of the IAB node DU, or a hard resource used by the IAB node DU for transmitting important signals or channels, or a hard UL resource of the IAB node DU, or a hard UL resource used by the IAB node DU for transmitting important signals or channels.

[0201] Among them, the important signal or channel is any one or any combination of the following: SSB, system information, PRACH, URLLC-related signals or channels.

[0202] The time division duplex uplink and downlink configuration may be a common time division duplex uplink and downlink configuration, or a common time division duplex uplink and downlink configuration and a dedicated time division duplex uplink and downlink configuration.

[0203] Since the parent IAB node DU knows the resource configuration of the IAB node DU, the parent IAB node DU and the IAB node MT have the same judgment results on the validity of the random access opportunity, which will prevent the problem of inconsistent judgment results affecting the random access performance.

[0204] In an optional embodiment, the validity of the random access opportunity may also be determined based on the hard resource and unavailable resource configuration of the DU:

[0205] The parent IAB node provides an unavailable resource configuration for the IAB node, which is used to indicate time resources that the IAB node MT cannot use, i.e., unavailable resources for the IAB node MT. If the PRACH resources configured by the parent IAB node for the IAB node MT overlap with the unavailable resources in the time domain, the random access opportunities that overlap with the unavailable resources in the time domain are invalid, i.e., the IAB node MT cannot use the random access opportunities that overlap with the unavailable resources in the time domain.

[0206] In addition, the IAB node MT can further determine the validity of the random access opportunity in combination with the resource configuration of the IAB node DU.

[0207] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0208] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain.

[0209] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the first resource and the second resource in the time domain; or, the random access opportunity is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, or at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain.

[0210] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if the random access opportunity is within the uplink symbol and the random access opportunity does not overlap with the first resource and the second resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain; or, the random access opportunity is not before the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain.

[0211] The first resource is an IAB node MT unavailable resource, which is provided by an unavailable resource configuration provided by a parent IAB node for IAB nodes.

[0212] The second resource is a hard resource of the IAB node DU, or a hard resource used by the IAB node DU for important signal or channel transmission, or a hard UL resource of the IAB node DU, or a hard UL resource used by the IAB node DU for important signal or channel transmission.

[0213] Among them, the important signal or channel is any one or any combination of the following: SSB, system information, PRACH, URLLC-related signals or channels.

[0214] The time division duplex uplink and downlink configuration may be a common time division duplex uplink and downlink configuration, or a common time division duplex uplink and downlink configuration and a dedicated time division duplex uplink and downlink configuration.

[0215] In an optional embodiment, the validity of the random access opportunity may be determined according to an existing mechanism, and whether a valid random access opportunity is available may be determined based on unavailable resources:

[0216] Whether each random access opportunity is valid is determined based on existing rules for determining the validity of random access opportunities. For each valid random access opportunity, if the valid random access opportunity does not overlap with unavailable resources in the time domain, the valid random access opportunity is available; otherwise, it is unavailable.

[0217] The unavailable resources are resources indicated by the unavailable resource configuration.

[0218] In an optional embodiment, the validity of the random access opportunity may be determined according to an existing mechanism, and whether a valid random access opportunity is available may be determined based on available resources:

[0219] Whether each random access opportunity is valid is determined based on existing rules for determining the validity of random access opportunities. For each valid random access opportunity, if the valid random access opportunity is within available resources, the valid random access opportunity is available; otherwise, it is unavailable.

[0220] The available resources are resources indicated by the available resource configuration.

[0221] In an optional embodiment, the validity of the random access opportunity can also be determined according to the existing mechanism, and the valid random access opportunity can be further determined whether it overlaps with unavailable resources in the time domain. If there is no overlap, the random access opportunity is valid.

[0222] The unavailable resource is a resource indicated by the unavailable resource configuration; or the first resource and / or the second resource in the above embodiment.

[0223] In an optional embodiment, the validity of the random access opportunity can also be determined according to the existing mechanism, and the valid random access opportunity can be further determined whether it is within the available resources. If it is within the available resources, the random access opportunity is valid, otherwise it is invalid.

[0224] The available resources are resources indicated by the available resource configuration.

[0225] Only valid random access opportunities or available random access opportunities can be used to transmit random access signals.

[0226] In an optional embodiment, to address the issue of random access formats spanning radio frames after subframe or time slot offsets in the configuration table, s_offset may be applied to the entire configuration table. According to existing protocols, the duration of each random access format is shown in Table 2, where OS is an OFDM symbol. For formats 1 and 2, the duration exceeds 1ms. Since the subframe number is only the starting subframe of the PRACH occasion, if s_offset should be applied to the entire configuration table, the preamble may span radio frames.

[0227] For example, in FR1TDD PRACH configuration index 30, each RACH occasion (RO) occupies three subframes 7, 8, and 9 in the time domain. If s_offset = 1, then after the offset, each RO occupies subframes 8 and 9 in the time domain and subframe 0 of the next radio frame. Index 36 has a similar problem.

[0228] In the FR1TDD PRACH configuration of Rel-15, the starting subframe of the PRACH resource in format 1 has only one value 7. Therefore, for s_offset = 1, 2, the RO after the offset spans frames;

[0229] The starting subframe of the PRACH resource in format 2 has only one value 6. Therefore, for s_offset = 1, 2, 3, the RO after the offset spans frames.

[0230] Problems caused by RO crossing frames:

[0231] When the UL / DL configuration of the NR system needs to be aligned with the LTE TDD UL / DL configuration, the subframe 0 of the NR TDD should be a DL subframe, so the RO is invalid and may result in no available RACH resources;

[0232] Cross-frame RO may affect the orthogonality of the PRACH resources of the parent backhaul link and the child link in the time domain. That is, if the RO crosses frames, the RACH resources of the parent backhaul link and the child link in different frames may overlap in the time domain.

[0233] You can use any of the following methods to solve the RO cross-frame problem:

[0234] 1. Define the rules for whether ROs are valid for IAB nodes. For example, ROs that cross frames are invalid.

[0235] 2. When the ROs of format 1 and format 2 cross frames after the offset, the time domain orthogonality of the PRACH resources of the parent backhaul link and the child link is determined at the slot granularity, because the PRACH resources may not be orthogonal even if the frames are different.

[0236] 3. Definition rule: If the offset causes the ROs corresponding to format 1 / 2 to cross frames, then the s_offset is invalid for the subframe number of format 1 / format 2, that is, s_offset = 0; otherwise, s_offset is valid.

[0237] 4. For format 1 and format 2, configure subframe-based s_offset separately and set the appropriate s_offset.

[0238] 5. Configure s_offset for each index separately and configure the appropriate s_offset.

[0239] Table 2: Duration of random access format:

[0240] Format <![CDATA[L RA ]]> <![CDATA[Δf RA ]]> duration 0 839 1.25kHz 1ms 1 839 1.25kHz 3ms 2 839 1.25kHz 3.5ms 3 839 5kHz 1ms A1 139 <![CDATA[15·2 μ kHz]]> 2OSs A2 139 <![CDATA[15·2 μ kHz]]> 4OSs A3 139 <![CDATA[15·2 μ kHz]]> 6OSs B1 139 <![CDATA[15·2 μ kHz]]> 2OSs B2 139 <![CDATA[15·2 μ kHz]]> 4OSs B3 139 <![CDATA[15·2 μ kHz]]> 6OSs B4 139 <![CDATA[15·2 μ kHz]]> 12OSs C0 139 <![CDATA[15·2 μ kHz]]> 2OSs C2 139 <![CDATA[15·2 μ kHz]]> 6OSs

[0241] In the above embodiment, the PRACH resource of the IAB node can be sent using system information common to IAB nodes, such as IAB-SIB1, and the protocol predefines an IAB-SI-RNTI dedicated to the IAB node for scrambling the CRC of the scheduling system information PDCCH.

[0242] In the above embodiments, an IAB node sometimes refers to an IAB terminal (IAB node MT) for communicating with a parent node, and sometimes refers to an IAB base station (IAB node DU) for communicating with a child node. The specific IAB node can be distinguished based on the context.

[0243] The value of Ngap is the same as the value of Ngap in the random access time slot validity judgment of a common terminal.

[0244] The IAB node MT and the IAB node DU appearing in the same embodiment or the same example are two units of the same IAB node.

[0245] A random access opportunity that overlaps with an SSB or downlink symbol in the time domain is also invalid. That is, the validity of the random access opportunity must also be such that the random access opportunity does not overlap with an SSB or downlink symbol in the time domain.

[0246] It should be noted that in all the above embodiments and examples, the mapping relationship between SSBs and valid random access opportunities is determined according to the existing mechanism.

[0247] In summary, determining the validity of random access opportunities based on the unavailable resource configuration and the resource configuration of the IAB node DU can more rationally determine the validity of random access opportunities, reduce useless signal transmission, and avoid unnecessary interference and power consumption. This also provides a method for distinguishing random access responses from ordinary UEs and IAB nodes, resolving the problem of multiplexing random access responses from UEs and IAB nodes, where only one UE and IAB node can successfully access the random access even if they use different PRACH resources.

[0248] This embodiment provides a method for sending a random access signal. Figure 6 is a flow chart of a method for sending a random access signal according to an embodiment of the present invention. Figure 6 As shown, the process includes the following steps:

[0249] Step S602: The second node receives resource configuration information sent by the first node;

[0250] Step S604: The second node determines the validity of the random access opportunity based on the resource configuration information;

[0251] Step S606: The second node sends a random access signal to the first node at a valid random access opportunity.

[0252] Through the above steps, since the second node receives the resource configuration information sent by the first node, the second node determines the validity of the random access opportunity based on the resource configuration information, and the second node sends a random access signal to the first node during a valid random access opportunity. This achieves the purpose of the first and second nodes determining the validity of the random access opportunity based on the resource configuration information. The second node sends the random access signal during a valid random access opportunity, and the first node receives the random access signal during a valid random access opportunity. Therefore, the problem of determining the validity of random access opportunities existing in the related art can be solved, achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and avoiding unnecessary interference and power consumption.

[0253] Optionally, the execution entity of the above steps may be a second node (eg, an IAB node), etc., but is not limited thereto.

[0254] In this embodiment, the first node may be a Donor IAB DU or a parent IAB node DU, and the second node may be an IAB node.

[0255] In this embodiment, the IAB node can be regarded as a common terminal (UE) or a base station accessed by other UEs. Figure 3 This is a schematic diagram of the IAB network architecture, such as Figure 3 As shown in the figure, a node with a wired connection to the core network is called a donor IAB. A donor IAB is wirelessly connected to one or more IAB nodes and provides wireless access functions for UEs. There is no direct link between the IAB node and the core network. The interaction between the IAB node and the core network requires one or more forwardings and is ultimately achieved with the help of the donor IAB. The IAB node has two functions: 1) Distributed Unit (DU) function, that is, the IAB node provides wireless access functions for UE or child IAB node like a base station; 2) Mobile Terminal (MT) function, that is, IAB nodes are controlled and scheduled by the donor IAB or upper-layer IAB node like UE.

[0256] The links between donor IAB and IAB nodes and the links between IAB nodes are collectively referred to as backhaul links (BL), and the links between IAB nodes and UEs are called access links (AL). Considering that the IAB network supports multiple hops (for example, for the subordinate nodes of IAB node3, it takes 4 hops to connect to the donor IAB, and the interaction with the core network is completed through the donor IAB), in order to describe the links more clearly, specifically, for a specific IAB node, the link between the IAB node and its parent node, that is, the parent IAB node (which may be an ordinary IAB node or a donor IAB) is called the parent backhaul link (parent BL), the link between the IAB node and its child node (child IAB node) is called the child backhaul link (child BL), and the link between the IAB node and the UE is called the child access link (child AL). In order to ensure the robustness of the parent backhaul link, the IAB network supports redundant connections. For example, in addition to the current parent node, an IAB node may have one or more potential parent nodes, such as Figure 3 As shown, IAB node4 has a wireless connection with the donor IAB node, and also has a potential wireless connection with IAB node1.

[0257] This embodiment can be applied to the transmission of random signals between IAB nodes. In half-duplex operation, an IAB node cannot transmit and receive simultaneously. For example, when IAB node 2MT sends a random access preamble to IAB node 1, it cannot simultaneously receive a random access preamble sent by child IAB node 3 or child UEs. Furthermore, the deployment location, antenna configuration, and mobility of IAB nodes differ significantly from those of ordinary UEs, placing certain restrictions and requirements on the configuration of random access resources. Furthermore, the redundant connections of IAB nodes and the resource configuration of IAB node DUs also affect the configuration of random access resources. Therefore, random access resources, i.e., resource configuration information, can be configured for the IAB node.

[0258] Furthermore, in NR Release 15, random access resource configuration is achieved by providing a starting frequency and a frequency-domain multiplexing random access opportunity (PRACH occasion, RO). Random access resource configuration is presented in a table format, with different tables corresponding to different frequency bands and duplex modes. Each table contains 256 configurations, indexed from 0 to 255. During actual configuration, the base station only needs to provide a single configuration index. For example, for TDD systems in frequency bands above 6 GHz (i.e., FR2 and unpaired spectrum), the random access time domain resource configuration is shown in Table 1. (Due to the large number of rows in the table, only some configurations are shown here.)

[0259] Table 1:

[0260]

[0261] The meanings of the columns in Table 1 are as follows:

[0262] Column 1 PRACH Config.Index: configuration index;

[0263] The second column Preamble format: random access format;

[0264] Column 3 (including x and y): x is the PRACH configuration period, ranging from 1 to 16, in units of radio frames, i.e., the PRACH configuration period is 10x milliseconds; y is the remainder of the system frame number (SFN) modulo x, which physically means the radio frame within the PRACH configuration period in which there will be a PRACH timeslot or PRACH opportunity. For example, y = 0 is the first radio frame, and y = 0 is the second radio frame.

[0265] Column 4: Slot number: The timeslot containing the ROs. For frequency bands below 6 GHz (i.e., FR1), it is the Subframe number.

[0266] Column 5 Starting symbol: The starting symbol number of the RO in the PRACH time slot (0 to 13).

[0267] Column 6 Number of PRACH slots within a 60kHz slot: When the PRACH subcarrier spacing is 120kHz, whether the PRACH time slot is the second time slot within the 60kHz slot (parameter is 1), or whether both time slots within the 60kHz slot are PRACH time slots (parameter is 2).

[0268] Column 7 Number (#) of time-domain PRACH occasions within a PRACH slot: the number of time-domain ROs within a PRACH time slot.

[0269] The eighth column, PRACH duration, indicates the number of OFDM symbols occupied by each random access format. For example, A1 is 2 symbols, and C2 is 6 symbols. The sequence in C2 occupies 4 symbols, and the rest are CP and GP. For the long random access format (sequence length 839), the value is uniformly set to 0, which has no practical physical meaning.

[0270] In an optional embodiment, considering that the IAB node needs to meet the half-duplex constraint, that is, it cannot transmit and receive simultaneously, the resource configuration information of the IAB node may include at least one of the following: a configuration index of the physical random access channel PRACH, frequency domain resources of the PRACH, a mapping relationship between synchronization signal blocks SSB and RACH occasions ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a radio frame, a time slot number, a subframe number, and unavailable resource configuration.

[0271] In this embodiment, the resource configuration information must meet the following conditions: For an IAB node, the PRACH resources configured on its parent backhaul link and child links (including the child access link and child backhaul link) must be time division multiplexed (TDM), that is, orthogonal in the time domain. In other words, the PRACH resources used by the IAB node MT to transmit preambles are orthogonal in the time domain to the PRACH resources used by the IAB node DU to receive preambles (i.e., the PRACH resources used by child UEs and child IAB nodes to transmit preambles).

[0272] The coverage characteristics and mobility of IAB nodes are different from those of ordinary UEs. As a special combination of base stations and terminals, the deployment location of IAB nodes is very different from that of ordinary terminals. For example, IAB nodes are often fixed under eaves and hung much higher than ordinary terminals to facilitate the establishment of a direct line of sight with donor IAB or parent IAB nodes. For example, IAB nodes often have more antennas than ordinary terminals. For example, IAB nodes may need to be placed farther away from IAB donors or parent IAB nodes than ordinary terminals (e.g. Figure 3 In addition, IAB nodes are usually located in fixed positions, which means that the channel conditions are relatively stable. Therefore, IAB nodes can be configured with a larger PRACH configuration period, that is, the x in the third column of the PRACH configuration table can be larger.

[0273] Different random access formats support different coverage ranges, mobility speeds, and resistance to penetration loss. Therefore, ordinary UEs and IAB nodes have different requirements for PRACH resources. An IAB node or donor IAB needs to configure different PRACH resources for child UEs and child IAB nodes, including configuring PRACH configuration indexes, PRACH frequency domain resources, the mapping relationship between SSBs and valid random access opportunities (ROs), and preambles (including the starting logical root sequence index, cyclic shift Ncs, and other parameters used to generate the preamble sequence).

[0274] To reduce complexity, the PRACH time domain resource configuration for IAB nodes can be simply extended based on the PRACH configuration table for UEs in NR Release 15, including:

[0275] The PRACH configuration period x in the extended PRACH configuration table, assuming the scaling factor is S, the extended PRACH configuration period is S*x.

[0276] The offset y_offset of the radio frame containing ROs relative to the PRACH configuration table, and / or the offset sb_offset of the subframe containing ROs relative to the PRACH configuration table, and the offset s_offset of the time slot containing ROs.

[0277] The extended PRACH configuration period serves as the PRACH configuration period of IAB nodes, and the offset radio frame, subframe, or time slot serves as the subframe or time slot containing ROs of IAB nodes. Alternatively, the extended PRACH configuration period serves as the PRACH configuration period of IAB nodes, and the Parent IAB node can directly configure the slot number or subframe number to replace the slot number or subframe number indicated by the PRACH configuration index. The replaced slot number or subframe number is the time slot number or subframe number containing ROs.

[0278] You can configure the slot number or subframe number in any of the following ways:

[0279] Method 1: Predefine multiple groups of configurations, each group of configurations corresponds to a time slot index set or a subframe index set, each group of configurations has an index, and the configuration index is provided to the IAB node MT.

[0280] Method 2: Use bitmap indication. For example, the slot number or subframe number corresponding to the bit value 1 is used to replace the slot number or subframe number indicated by the PRACH configuration index.

[0281] Among them, for FR1, the length of the bitmap is the number of subframes contained in the radio frame, and for FR2, the length of the bitmap is the number of time slots with a 60kHz subcarrier spacing contained in the radio frame; or, for all frequency bands, the length of the bitmap is the number of time slots with a 60kHz subcarrier spacing contained in the radio frame. For FR1, only some bits are valid, such as the lower 10 bits or the upper 10 bits.

[0282] If the PRACH resource configurations of UEs and IAB nodes are different, IAB nodes can determine whether a cell can provide services for IAB nodes based on the PRACH resource configuration of the cell during initial access or handover, thereby avoiding selecting a cell that cannot provide services for IAB nodes.

[0283] Because UEs and IAB nodes have different PRACH resource configurations, UEs may not be able to know the PRACH resources of IAB nodes. Therefore, if the Random Access Responses (RARs) of UEs and IAB nodes are reused, even if the UE and IAB node use different PRACH resources, only one of them can successfully perform random access. For example, a UE and an IAB node MT use the same PRACH time-frequency resources, but different random access formats and preamble sequences (but the sequence index range is 0 to 64). That is, the starting root sequence index and cyclic shift of the preamble sequence generated by the IAB node are different from those of ordinary terminals. In this case, the expectation is that ordinary terminals and IAB terminals (IAB node MT) can simultaneously successfully access the same PRACH time-frequency resources and preamble sequence identifier. However, the existing mechanism causes the UE and IAB node to correspond to the same RAR, and at most one of them can successfully perform random access. For example, the PRACH resources of the UE and IAB node have the same starting position in the time domain but are orthogonal in the frequency domain (i.e., FDM). Since both frequency domain resource indices start at 0, for example, a standard terminal multiplexes 8 resources in the frequency domain and an IAB node multiplexes 4 resources, their corresponding frequency domain resource indices range from 0 to 7 and 0 to 4, respectively. Therefore, even if their RACH resources do not overlap, the calculated RA-RNTI may be the same. If the preamble sequence identifiers used by both are the same, they will correspond to the same RAR, and at most only one of them can successfully access the network. This not only increases the random access latency for standard or IAB terminals but also generates unnecessary interference in subsequent random access processes. Therefore, it is necessary to distinguish the RARs of UEs and IAB nodes. For example, IAB nodes can use a different RA-RNTI calculation formula than UEs, or use a reserved field in the MAC RAR to indicate the MAC RAR of the IAB terminal.

[0284] The RA-RNTI is used to scramble a cyclic redundancy check (CRC) of a PDCCH corresponding to a random access response.

[0285] In an optional embodiment, the frequency domain resources of the PRACH include: the starting frequency of the PRACH resources; the number of PRACHs multiplexed in the frequency domain. In this embodiment, the starting frequency of the PRACH resources can be determined in one of the following ways: the first node determines the starting frequency of the PRACH resources based on the activated uplink bandwidth BWP; the first node determines the starting frequency of the PRACH resources based on the offset of the starting physical resource block PRB of the initial access PRACH frequency domain resources of the terminal device; the first node determines the starting frequency of the PRACH resources based on the offset of the ending PRB of the initial access PRACH frequency domain resources of the terminal device;

[0286] In this embodiment, the starting frequency can be defined based on the activated uplink bandwidth part (BWP), or based on the offset of the starting PRB or ending PRB relative to the PRACH frequency domain resource initially accessed by the UEs. For example, the starting frequency is the offset relative to the first physical resource block (PRB) of the activated uplink BWP, that is, the offset relative to PRB0. Alternatively, the starting frequency is the offset of the first PRB or the offset of the last PRB relative to the PRACH frequency domain resource initially accessed by the UEs.

[0287] Optionally, the PRB corresponds to the subcarrier spacing corresponding to the activated uplink BWP.

[0288] Optionally, the default value of the start frequency is PRB0 of the activated uplink BWP.

[0289] Optionally, the activated uplink BWP is an initially activated uplink BWP in an initial access phase or an activated uplink BWP after initial access.

[0290] The starting logical root sequence index and the cyclic shift Ncs are used to generate the IAB nodes dedicated preamble.

[0291] Optionally, a portion of the 64 preambles used for random access of UEs may also be designated as dedicated preambles for IABnodes.

[0292] The number of IAB nodes is less than that of UEs, so the total number of preambles dedicated to IAB nodes can be less than 64, such as 8, 16, or 32.

[0293] In an optional embodiment, the offset y_offset of the wireless frame includes: an offset relative to a preset parameter y in a preset resource configuration table of the PRACH, where the preset parameter y refers to a wireless frame index including a PRACH occasion within a PRACH configuration period, and the preset parameter y is used to indicate a wireless frame number including a PRACH occasion within a PRACH configuration period.

[0294] Wherein, y_offset may be an offset relative to the parameter y in the PRACH configuration table, or a quantity used to replace the parameter y.

[0295] Assume that the maximum of the IAB PRACH configuration period is Tmax frames. The SFN containing ROs satisfies:

[0296] mod(SFN, x*S) = mod(y + y_offset, x*S), where 0 ≤ y_offset < Tmax or 0 ≤ y_offset < x*S. Or,

[0297] mod(SFN, min{x*S, Tmax}) = mod(y + y_offset, min{x*S, Tmax}), where 0 ≤ y_offset < Tmax or 0 ≤ y_offset < x*S or 0 ≤ y_offset < min{x*S, Tmax}.

[0298] Wherein, the subframe-based offset sf_offset is an offset relative to the subframe number subframenumber in the PRACH configuration table.

[0299] Wherein, the slot-based offset s_offset is an offset relative to the slot number slot number in the PRACH configuration table.

[0300] According to the existing protocol, the slot / subframe number is a number within a wireless frame (10 ms), each subframe is 1 ms, and the slot number is relative to a 60 kHz subcarrier spacing. Since a wireless frame contains 10 subframes, the subframe number after offset sf_offset and the value range of sf_offset are as follows:

[0301] SF_number = mod(sf_number + sf_offset, 10), where 0 ≤ sf_offset < 10;

[0302] Among them, sf_number represents the subframe number corresponding to the Rel-15PRACH configuration index, and SF_number represents the subframe number after the offset sf_offset.

[0303] Because a wireless frame contains 40 60kHz slots, the slot number after the offset s_offset and the value range of s_offset are as follows:

[0304] S_number = mod(s_number + s_offset, 40), where 0 ≤ s_offset < 40;

[0305] Among them, s_number represents the slot number corresponding to the Rel-15PRACH configuration index, and S_number represents the subframe number after the offset s_offset.

[0306] For each PRACH configuration index, a PRACH configuration period scaling factor S is configured separately; or, for the entire PRACH configuration table, one PRACH configuration period scaling factor is configured.

[0307] If the following parameters are not configured for IAB nodes (IAB terminals): PRACH configuration index, PRACH frequency domain resources, mapping relationship between SSB and valid ROs, any one or any combination of preambles, or any other parameters related to PRACH resources are not configured for IAB nodes, the IAB nodes reuse the corresponding parameters in the PRACH resource configuration of UEs.

[0308] The IAB nodes determine the PRACH resource according to the PRACH configuration index and the PRACH frequency domain resource, in combination with at least one of the scaling factor S, the offset y_offset, the offset s_offset, and the offset sf_offset.

[0309] Optionally, for the scaling factor S, offset y_offset, offset s_offset, offset sf_offset, if not configured, the default value is 0.

[0310] In an optional embodiment, in addition to the above parameters, the IAB nodes may also receive at least one of the following PRACH-related parameters provided by the parent IAB node: the total number of available random access preambles, the total number of contention-based preambles corresponding to each SSB, the total number of contention-based preambles in group A corresponding to each SSB, the transport block size threshold for selecting a preamble group, the path loss calculation parameter for selecting a preamble group, the subcarrier spacing used for the random access signal (msg1), the SSB reception power threshold that the selected SSB and the corresponding PRACH resources need to meet, power-related parameters, restriction set configuration, precoding of msg3, etc.

[0311] In an optional embodiment, the subframe number includes: the subframe number indicated by the PRACH configuration index in the preset resource configuration table for replacing the PRACH, where the replaced subframe number is a set of indices including the ROs subframes. The slot number includes: the slot number indicated by the PRACH configuration index in the preset resource configuration table for replacing the PRACH, where the replaced slot number is a set of indices including the ROs slots.

[0312] In the above embodiment, it is assumed that the maximum PRACH configuration period of the IAB nodes is Tmax system frames. Optionally, Tmax is one of 16, 32, 64, 128, 256. The scaling factor S = 2^k, where k is a non-negative integer, and its maximum value depends on the maximum value of the PRACH configuration period of the IAB nodes.

[0313] For each PRACH configuration index, the maximum value of S depends on the maximum value Tmax of the PRACH configuration period of the IAB nodes and the x value in the PRACH configuration index. For example, the maximum value of S is Tmax divided by x.

[0314] For the IAB nodes, the system frame number SFN containing ROs can be determined according to the following several methods:

[0315] Method 1: SFN satisfies mod(SFN, S * x) = mod(y + y_offset, S * x), where y_offset is an integer, and 0 ≤ y_offset < Tmax or 0 ≤ y_offset < S * x or 0 ≤ y_offset < min{x * S, Tmax}.

[0316] Method 2: y = y_offset, that is, directly replace the parameter y in the configuration table, that is, SFN satisfies mod(SFN, x * S) = y_offset, where y_offset is an integer, and 0 ≤ y_offset < S * x.

[0317] 3) If the PRACH configuration index y contains multiple values, then y_offset is the first value y1 of parameter y, and the other values in parameter y are the difference between the corresponding value and y1 in the PRACH configuration table + y_offset. For example, if y = {y1, y2} in the PRACH configuration table, then y = {y_offset, y_offset + y2 - y1} can be obtained from y_offset. Otherwise, y = y_offset. Where y_offset is an integer and 0 ≤ y_offset <S*x;

[0318] Where y is parameter y in the PRACH configuration table.

[0319] It should be noted that if S*x>Tmax, then S*x=Tmax, otherwise the above formula remains unchanged.

[0320] Considering that in NR R15, for FR1, each PRACH configuration index corresponds to a y value, that is, all ROs are contained in one frame within the PRACH configuration period; for the FR2 frequency band, there is usually only one y value, and the y corresponding to a few configurations is {1,2}. Considering that the channel conditions between IAB nodes are relatively stable, there is no need to configure multiple frames to contain ROs within a PRACH configuration period. Therefore, method 2 is a simpler and more intuitive y_offset solution.

[0321] In an optional embodiment, different PRACH frequency domain index numbers may be used or the PRACH frequency domain index numbers may be offset to calculate the RA-RNTI.

[0322] In existing protocols, the maximum number of PRACHs multiplexed by a UE in the frequency domain is 8, and the index number f_id is an integer in the range of 0≤f_id<8. Therefore, the PRACH indexes multiplexed by an IAB node in the frequency domain can be numbered starting from 8. Assuming that the maximum number of PRACHs multiplexed by an IAB node in the frequency domain is Nprach, the value of Nprach can be predefined and the RA-RNTI value is less than 65519. Then, the PRACH index number multiplexed by an IAB node in the frequency domain is an integer in the range of 8≤f_id<8+Nprach.

[0323] In order to distinguish it from the UE's RA-RNTI (Random Access RNTI, RNTI: Radio Network Temporary Identifier), for IAB nodes, the RA-RNTI corresponding to the PRACH for transmitting the random access preamble is calculated by the following formula:

[0324] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×(8 + Nprach)×ul_carrier_id Formula 1;

[0325] where s_id is the index of the first OFDM symbol of the given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of the given PRACH within the system frame (0 ≤ t_id < 80), f_id is the index of the given PRACH in the frequency domain (8 ≤ f_id < 8 + Nprach), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier).

[0326] In addition, there is another way to number the PRACH indices multiplexed by the IAB node in the frequency domain starting from 0, and offset f_id by 8 in the RA-RNTI calculation formula for IAB nodes. Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH for transmitting the random access preamble is calculated by the following formula:

[0327] RA-RNTI = 1 + s_id + 14×t_id + 14×80×(f_id + 8) + 14×80×(8 + Nprach)×ul_carrier_id Formula 2;

[0328] where s_id is the index of the first OFDM symbol of the given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of the given PRACH within the system frame (0 ≤ t_id < 80), f_id is the index of the given PRACH in the frequency domain (0 ≤ f_id < Nprach), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 represents the normal uplink carrier, 1 represents the supplementary uplink carrier).

[0329] Optionally, if Nprach = 8, the above two Formulas 1 and 2 are respectively:

[0330] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×16×ul_carrier_id.

[0331] RA-RNTI=1+s_id+14×t_id+14×80×(f_id+8)+14×80×16×ul_carrier_id

[0332] In an optional embodiment, different time slot indices or time slot index offsets may be used to calculate the RA-RNTI.

[0333] The time slot indexes of IAB nodes in a radio frame are numbered starting from 80, that is, the first time slot index in a radio frame is 80, the second is 81, and so on.

[0334] Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH that transmits the random access preamble is calculated using the following formula:

[0335] RA-RNTI=1+s_id+14×t_id+14×160×f_id+14×160×8×ul_carrier_id

[0336] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (80≤t_id<160), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0337] In addition, another method is to number the time slot indexes of IAB nodes in the radio frame starting from 0, and offset the t_id in the RA-RNTI calculation formula of IAB nodes by 80.

[0338] Therefore, for IAB nodes, the RA-RNTI corresponding to the PRACH that transmits the random access preamble is calculated using the following formula:

[0339] RA-RNTI=1+s_id+14×(t_id+80)+14×160×f_id+14×160×8×ul_carrier_id

[0340] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0341] In an optional embodiment, the RA-RNTI corresponding to the PRACH transmitting the random access preamble may also be calculated using the following formula:

[0342] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×identifier

[0343] Among them, s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), ul_carrier_id is used to indicate the uplink carrier for transmitting the random access preamble code (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier), and identifier is used to indicate whether the RA-RNTI calculation formula is for a normal terminal or an IAB node. For a normal terminal, identifier is 0, and for an IAB node, identifier is 1.

[0344] In an optional embodiment, for an IAB terminal (IAB node MT), the RA-RNTI corresponding to the PRACH transmitting the random access preamble is calculated using the following formula:

[0345] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

[0346] Where s_id is the first OFDM symbol index of a given PRACH (0≤s_id<14), t_id is the first time slot index of a given PRACH in the system frame (0≤t_id<80), f_id is the PRACH index given in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to indicate the transmission of the random access preamble (0 indicates a normal uplink carrier, 1 indicates a supplementary uplink carrier).

[0347] For a normal terminal, the RA-RNTI corresponding to the PRACH that transmits a random access preamble is calculated by the following formula:

[0348] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0349] Where s_id is the index of the first OFDM symbol of a given PRACH (0 ≤ s_id < 14), t_id is the index of the first time slot of a given PRACH within a system frame (0 ≤ t_id < 80), f_id is the index of a given PRACH in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the uplink carrier used to indicate the transmission of a random access preamble (0 represents a normal uplink carrier, and 1 represents a supplementary uplink carrier).

[0350] In an optional embodiment, for an IAB node, the RA-RNTI corresponding to the PRACH that transmits a random access preamble is calculated by the following formula:

[0351] RA-RNTI = 1 + s_id + s×t_id + s×t×f_id + s×t×f×ul_carrier_id + s×t×f×2; or,

[0352] RA-RNTI = 1 + s_id + s×t_id + s×t×f_id + s×t×f×ul_carrier_id;

[0353] Where s_id is the index of the first OFDM symbol of a given PRACH (s0 ≤ s_id < s), t_id is the index of the first time slot of a given PRACH within a system frame (t0 ≤ t_id < t), f_id is the index of a given PRACH in the frequency domain (f0 ≤ f_id < f), and ul_carrier_id is the uplink carrier used to indicate the transmission of a random access preamble (0 represents a normal uplink carrier, and 1 represents a supplementary uplink carrier).

[0354] Among them, the OFDM symbols within a time slot are numbered starting from s0, that is, the index of the first OFDM symbol within the time slot is s0, the second is s0 + 1, and so on;

[0355] Among them, the time slot indices within a radio frame are numbered starting from t0, that is, the index of the first time slot within the radio frame is t0, the second is t1, and so on; the time slot indices within a radio frame are numbered starting from t0, that is, the index of the first time slot within the radio frame is t0, the second is t0 + 1, and so on;

[0356] Among them, the PRACH index in the frequency domain is numbered starting from f0, that is, starting from the low frequency. The PRACH index of the first PRACH resource in the frequency domain is f0, the second is f0+1, and so on.

[0357] Among them, the values of s0, t0, f0, s, t, and f need to be predefined, for example, s0=0, t0=0, f0=0, s=14, t=80, f=8; or s0=14, t0=0, f0=0, s=28, t=80, f=8; or s0=0, t0=80, f0=0, s=14, t=160, f=8; or s0=0, t0=0, f0=8, s=14, t=80, f=16.

[0358] In an optional embodiment, a reserved field in the MAC RAR is used to indicate a dedicated MAC RAR for IAB nodes.

[0359] In NR Rel-15, as Figure 4 As shown in Figure 1, a MAC PDU contains one or more MAC subPDUs and optional padding. Each MAC subPDU consists of one of the following:

[0360] -BI only: only the MAC subheader with Backoff indication;

[0361] -RAPID (Random Access Preamble Identifier) only: MAC subheader with RAPID only (i.e., confirmation of system information request);

[0362] -RAPID and RAR: MAC header with RAPID and MAC RAR.

[0363] If the MAC PDU contains BI only, the BI only is located at the beginning of the MAC PDU. RAPID only and RAPID and RAR can be placed anywhere between the BI only and the padding in the MAC PDU.

[0364] like Figure 5 As shown, the reserved bit R in the MAC RAR can be used to indicate whether the MAC RAR is the MAC RAR of the IAB nodes. For example, R=0 indicates that it is not the MAC RAR of the IAB nodes, and R=1 indicates that it is the MAC RAR of the IAB nodes.

[0365] Each MAC RAR corresponds to a subheader, which contains a RAPID. The subheader and MAC RAR form a MAC subPDU. If the RAPID corresponding to the random access signal sent by a common terminal (UE) is the same as the RAPID corresponding to the random access signal sent by IAB nodes in the MAC PDU, the MAC subPDU for the common terminal should be before the MAC subPDU for the IAB nodes. For example, if the MAC subPDU corresponding to the terminal is the nth, then the MAC subPDU corresponding to the IAB nodes is the n+kth, where k is a positive integer.

[0366] When the PRACH time-frequency resources for sending preamble signals of ordinary terminals and IAB terminals are the same, and the preamble index is the same, the RA-RNTI of ordinary terminals and IAB terminals are the same, and the RAPID of ordinary terminals and IAB terminals are also the same, their MAC RARs will be multiplexed in one MAC PDU. In order for the IAB terminal to distinguish its own MAC RAR, the reserved bit R in the MAC RAR can be used to indicate whether the MAC RAR is the MAC RAR of the IAB terminal. In order to prevent the ordinary terminal from mistakenly detecting the MAC RAR of the IAB terminal, the MAC subPDU of the ordinary terminal should be in front of the MACsubPDU of the IAB terminal in the MAC PDU.

[0367] Because ordinary terminals cannot identify R, this can prevent ordinary terminals from mistaking the MAC RAR of the IAB terminal as their own, causing access failure and also affecting the initial access of the IAB terminal.

[0368] It should be noted that in the calculation formulas of all RA-RNTIs in the above examples, for random access formats 0, 1, 2 and 3 (i.e., long format with a preamble length of 839), s_id and t_id are determined according to the subcarrier spacing of the activated uplink BWP where the PRACH resource is located. For random access formats A1 / B1, A2 / B2, A3 / B3, A1, A2, A3, B1, B4, C0, C2 (i.e., short format with a preamble length of 139), s_id and t_id are determined according to the subcarrier spacing of the activated uplink BWP where the PRACH resource is located, or according to the subcarrier spacing of the PRACH, which needs to be pre-defined by the protocol.

[0369] Optionally, for random access formats A1 / B1, A2 / B2, A3 / B3, A1, A2, A3, B1, B4, C0, C2 (i.e., preamble length is 139 short format), s_id and t_id are determined according to the subcarrier spacing of PRACH.

[0370] In an optional embodiment, the validity of the random access opportunity may be determined by one of the following methods:

[0371] In the case where the first node does not provide the uplink and downlink configuration of time division duplex for the second node, the random access opportunity is valid if the random access opportunity meets the following conditions: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0372] In the case where the first node provides the uplink and downlink configuration of time division duplex for the second node, the random access opportunity is valid if the random access opportunity meets one of the following conditions: the random access opportunity is within the uplink symbol and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0373] The specific resources include at least one of the following: resources that cannot be used by the second node, hard resources of the base station unit of the second node, hard resources used by the base station unit of the second node for transmitting important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources used by the base station unit of the second node for transmitting important signals or channels;

[0374] Important signals or channels include at least one of the following: SSB, system information, PRACH, URLLC signals or channels.

[0375] In this embodiment, the IAB node has two functional units, the MT and the DU. The MT is the unit in the IAB node that acts as a UE. Therefore, the resource types of the MT are the same as those of a regular UE, including downlink time resources (D), uplink time resources (U), and flexible time resources (F). F can be flexibly used as an uplink or downlink resource. For the DU, its resource types are: D, U, F, and unavailable time resources (NA). NA refers to resources that the DU cannot use. Each D, U, and F has the following two attributes: hard and soft. Hard refers to resources that are always available to the DU. The availability of soft resources can be further indicated explicitly or implicitly. Therefore, the resources for the DU include the following seven types: hardD, softD, hardU, softL, hardF, softF, and NA.

[0376] The IAB node DU resource configuration needs to consider the compromise between configuration flexibility and bit overhead. Since the IAB node DU is to provide services for ordinary UEs, the DU resource configuration may also be restricted by the common TDD uplink and downlink configuration (e.g., TDD-UL-DL-ConfigurationCommon) mode of Release 15. Therefore, for an IAB node, since the PRACH time domain resource configuration is selected from a table and the selection is also affected by the common TDD uplink and downlink configuration, the NA resources of the parent IAB node DU may overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain. In addition, for an IAB node, it is very likely that the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain. In this case, a relevant solution is needed to enable the IAB node to work under half-duplex constraints.

[0377] In addition, the IAB node may need to randomly access other IAB nodes other than the current parent IAB node, which we call potential parent IAB nodes for the convenience of description. Figure 3In addition to randomly accessing the donor IAB (i.e., parent IAB node), IAB node4 may also need to randomly access IAB node1, for example, to maintain basic synchronization with IABnode1 so that it can quickly switch to IAB node1 when the link quality between IAB node4 and donor IAB is poor. Alternatively, IAB node4 may need to perform random access to IAB node1 and switch to IAB node1. That is, IAB node1 is a potential parent IAB node for IAB node4. However, the PRACH resources configured by the parent IAB node and the potential parent IABnode for the IAB node MT may be different. Therefore, even if the PRACH resources configured by the parent IAB node for the IAB nodeMT and the hard resources of the IAB node DU do not overlap in the time domain, it is difficult to simultaneously ensure that the PRACH resources configured by one or more potential parent IAB nodes for the IAB node MT and the hard resources of the IAB node DU are orthogonal in the time domain. In this case, a relevant solution is also needed to enable the IAB node to operate under half-duplex constraints.

[0378] The random access opportunity obtained based on the PRACH resource configuration may be invalid. For example, the random access opportunity overlaps with the downlink signal SSB in the time domain. Due to half-duplex or interference limitations, the parent IAB node cannot receive the uplink random access signal when sending the SSB. Therefore, the terminal (UE or IAB node MT) does not need to send the uplink random access signal. Therefore, it is necessary to formulate a criterion for judging the validity of the random access opportunity. Otherwise, not only will interference be generated, but the transmitting and receiving ends of the random access signal will also have inconsistent understandings of the mapping between the SSB and the random access opportunity, resulting in random access failure.

[0379] In an optional embodiment, the unavailable resource configuration provided by the parent IAB node for the IAB nodes is used to indicate time resources that the IAB node MT cannot use, that is, unavailable resources for the IAB node MT. If the PRACH resources configured by the parent IAB nodes for the IAB node MT overlap with the unavailable resources in the time domain, the random access opportunities that overlap with the unavailable resources in the time domain are invalid, that is, the IAB node MT cannot use the random access opportunities that overlap with the unavailable resources in the time domain.

[0380] The PRACH resource may be a common PRACH resource configured by a system message, or a dedicated PRACH resource configured by a dedicated RRC signaling.

[0381] Unavailable resources are either continuous-time resources or discrete-time resources.

[0382] Optionally, the unavailable resources are at least one of the following: unavailable resources of the parent IAB node DU, a subset of the unavailable resources of the parent IAB node DU, unavailable resources of the potential parent IAB node DU, a subset of the unavailable resources of the potential parent IAB node DU, hard resources of the child IAB node DU of the Parent IAB node, hard UL resources of the child IAB node DU of the Parent IAB node, and unusable PRACH resources. The determination of the unavailable resources depends on the implementation of the parent IAB node DU.

[0383] Optionally, the unavailable resources are continuous time resources or discrete time resources within each radio frame.

[0384] Optionally, the method of indicating unavailable resources in each wireless frame is any one of the following: 1. the k1th to k2th subframes or time slots; 2. the last M1 subframes or time slots; 3. the last M2 even-numbered subframes or time slots; 4. the last M3 odd-numbered subframes or time slots; 5. indication by a resource indicator value (RIV); 6. bitmap, where the bitmap length is the number of subframes or time slots contained in the wireless frame, and it is pre-agreed whether 0 or 1 in the bitmap represents unavailable resources; 7. grouping of resources in the wireless frame, and using the bitmap of the grouped resources to indicate that one or more groups are unavailable resources.

[0385] The RIV is determined based on the number N of subframes or time slots contained in the radio frame, the starting subframe or time slot Tstart of unavailable resources, and the number L of consecutive subframes or time slots:

[0386] If (L-1) <floor(N / 2),

[0387] Then RIV=N(L-1)+Tstart,

[0388] Otherwise, RIV = N(N-L+1)+(N-1-Tstart)

[0389] Among them, k1, k2, M1, M2, and M3 are integers less than or equal to N.

[0390] Optionally, the unavailable resource is a periodically unavailable continuous-time resource or a discrete-time resource.

[0391] Optionally, the unavailable resource configuration includes a period, a bitmap, or a RIV. The bitmap is used to indicate that one or more subframes or time slots within the period are unavailable resources as 0 or 1. The length of the bitmap is the number of subframes or time slots contained in the period. It is pre-agreed whether 0 or 1 in the bitmap indicates unavailable resources. For example, it is agreed that 0 in the bitmap indicates unavailable resources. The RIV indicates that one or more consecutive subframes or time slots starting from the starting subframe or time slot are unavailable resources. The RIV calculation method is the same as the indication within the radio frame.

[0392] Optionally, the unavailable resource configuration includes at least one of the following parameters: a period, an offset O within the period, and a duration t, wherein the granularity of the offset O within the period and the duration t is a subframe or a PRACH time slot.

[0393] Optionally, for the above cycles, the starting position of the first cycle is aligned with the starting position of radio frame 0.

[0394] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0395] For unpaired spectrum (time division duplex), the effectiveness of random access timing is also related to the time division duplex uplink and downlink configuration and the time domain position of SSB.

[0396] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource in the time domain.

[0397] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the first resource in the time domain; or, the random access opportunity is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, or at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource in the time domain.

[0398] The first resource is an unavailable resource of the IAB node MT, which can be obtained from the unavailable resource configuration provided by the parent IABnode for IAB nodes.

[0399] In an optional embodiment, the validity of the random access opportunity may also be determined in the following manner:

[0400] For an IAB node, the hard resources of the IAB node DU are resources that can be used by the DU, that is, the resources that can be used by the sub-links (including sub-access links and sub-backhaul links) of the IAB node. If the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, then due to half-duplex limitations, the IABnode MT and the DU may not be able to use the overlapping resources at the same time. Therefore, one way to deal with this is: if the hard resources of the IAB node DU overlap with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, then the random access opportunity that overlaps with the DU's hard resources in the time domain is invalid, that is, the IAB node MT cannot use the random access opportunity that overlaps with the DU's hard resources in the time domain to send a preamble signal.

[0401] However, for the IAB node that supports frequency division multiplexing (FDM) and space division multiplexing (SDM), the IAB node MT and IABnode DU can send or receive at the same time. Therefore, if the hard resource is hard DL or hard F, the IAB node MT and IAB node DU can send at the same time, so the IAB node MT can consider that the random access opportunity that overlaps with the hard DL or hard F of the DU in the time domain is still valid. Therefore, for the IAB node that supports frequency division multiplexing (FDM) and space division multiplexing (SDM), the validity of the random access opportunity can also be judged as follows: If the hard UL of the IAB node DU overlaps with the PRACH resources configured by the parent IAB node for the IAB node MT in the time domain, the random access opportunity that overlaps with the hard UL of the DU in the time domain is invalid.

[0402] Since the resource configuration of the IAB node DU is obtained only after the IAB node MT completes initial access, the IAB node MT cannot obtain the resource configuration of the IAB node DU during initial access. Therefore, the resource configuration of the IAB node DU can be used only for determining the validity of dedicated PRACH resources, or it can also be used to determine the validity of public PRACH resources after the IAB node MT initially accesses.

[0403] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0404] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the second resource in the time domain.

[0405] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the second resource in the time domain; or, the random access opportunity is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, or at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the second resource in the time domain.

[0406] The second resource is a hard resource of the IAB node DU, or a hard resource used by the IAB node DU for transmitting important signals or channels, or a hard UL resource of the IAB node DU, or a hard UL resource used by the IAB node DU for transmitting important signals or channels.

[0407] Among them, the important signal or channel is any one or any combination of the following: SSB, system information, PRACH, URLLC-related signals or channels.

[0408] The time division duplex uplink and downlink configuration may be a common time division duplex uplink and downlink configuration, or a common time division duplex uplink and downlink configuration and a dedicated time division duplex uplink and downlink configuration.

[0409] Since the parent IAB node DU knows the resource configuration of the IAB node DU, the parent IAB node DU and the IAB node MT have the same judgment results on the validity of the random access opportunity, which will prevent the problem of inconsistent judgment results affecting the random access performance.

[0410] In an optional embodiment, the validity of the random access opportunity may also be determined based on the hard resource and unavailable resource configuration of the DU:

[0411] The parent IAB node provides an unavailable resource configuration for the IAB node, which is used to indicate time resources that the IAB node MT cannot use, i.e., unavailable resources for the IAB node MT. If the PRACH resources configured by the parent IAB node for the IAB node MT overlap with the unavailable resources in the time domain, the random access opportunities that overlap with the unavailable resources in the time domain are invalid, i.e., the IAB node MT cannot use the random access opportunities that overlap with the unavailable resources in the time domain.

[0412] In addition, the IAB node MT can further determine the validity of the random access opportunity in combination with the resource configuration of the IAB node DU.

[0413] For paired spectrum (Frequency Division Duplex), all random access slots are valid.

[0414] For unpaired spectrum, if time division duplex uplink and downlink configuration is not provided for the IAB node MT, the random access opportunity is valid if it is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain.

[0415] If a time division duplex uplink and downlink configuration is provided for the IAB node MT, the random access opportunity is valid if it is within the uplink symbol and the random access opportunity does not overlap with the first resource and the second resource in the time domain; or, the random access opportunity is not in front of the SSB in the PRACH time slot and the starting point of the random access opportunity is at least Ngap symbols after the last downlink symbol, or at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the first resource and the second resource in the time domain.

[0416] The first resource is an IAB node MT unavailable resource, which is provided by an unavailable resource configuration provided by a parent IAB node for IAB nodes.

[0417] The second resource is a hard resource of the IAB node DU, or a hard resource used by the IAB node DU for important signal or channel transmission, or a hard UL resource of the IAB node DU, or a hard UL resource used by the IAB node DU for important signal or channel transmission.

[0418] Among them, the important signal or channel is any one or any combination of the following: SSB, system information, PRACH, URLLC-related signals or channels.

[0419] The time division duplex uplink and downlink configuration may be a common time division duplex uplink and downlink configuration, or a common time division duplex uplink and downlink configuration and a dedicated time division duplex uplink and downlink configuration.

[0420] In an optional embodiment, to address the issue of random access formats spanning radio frames after subframe or time slot offsets in the configuration table, s_offset may be applied to the entire configuration table. According to existing protocols, the duration of each random access format is shown in Table 2, where OS is an OFDM symbol. For formats 1 and 2, the duration exceeds 1ms. Since the subframe number is only the starting subframe of the PRACH occasion, if s_offset should be applied to the entire configuration table, the preamble may span radio frames.

[0421] For example, in FR1TDD PRACH configuration index 30, each RACH occasion (RO) occupies three subframes 7, 8, and 9 in the time domain. If s_offset = 1, then after the offset, each RO occupies subframes 8 and 9 in the time domain and subframe 0 of the next radio frame. Index 36 has a similar problem.

[0422] In the FR1TDD PRACH configuration of Rel-15, the starting subframe of the PRACH resource in format 1 has only one value 7. Therefore, for s_offset = 1, 2, the RO after the offset spans frames;

[0423] The starting subframe of the PRACH resource in format 2 has only one value 6. Therefore, for s_offset = 1, 2, 3, the RO after the offset spans frames.

[0424] Problems caused by RO crossing frames:

[0425] When the UL / DL configuration of the NR system needs to be aligned with the LTE TDD UL / DL configuration, the subframe 0 of the NR TDD should be a DL subframe, so the RO is invalid and may result in no available RACH resources;

[0426] Cross-frame RO may affect the orthogonality of the PRACH resources of the parent backhaul link and the child link in the time domain. That is, if the RO crosses frames, the RACH resources of the parent backhaul link and the child link in different frames may overlap in the time domain.

[0427] You can use any of the following methods to solve the RO cross-frame problem:

[0428] 1. Define the rules for whether ROs are valid for IAB nodes. For example, ROs that cross frames are invalid.

[0429] 2. When the ROs of format 1 and format 2 cross frames after the offset, the time domain orthogonality of the PRACH resources of the parent backhaul link and the child link is determined at the slot granularity, because the PRACH resources may not be orthogonal even if the frames are different.

[0430] 3. Definition rule: If the offset causes the ROs corresponding to format 1 / 2 to cross frames, then the s_offset is invalid for the subframe number of format 1 / format 2, that is, s_offset = 0; otherwise, s_offset is valid.

[0431] 4. For format 1 and format 2, configure subframe-based s_offset separately and set the appropriate s_offset.

[0432] 5. Configure s_offset for each index separately and configure the appropriate s_offset.

[0433] Table 2: Duration of random access format:

[0434] Format <![CDATA[L RA ]]> <![CDATA[Δf RA ]]> duration 0 839 1.25kHz 1ms 1 839 1.25kHz 3ms 2 839 1.25kHz 3.5ms 3 839 5kHz 1ms A1 139 <![CDATA[15·2 μ kHz]]> 2OSs A2 139 <![CDATA[15·2 μ kHz]]> 4OSs A3 139 <![CDATA[15·2 μ kHz]]> 6OSs B1 139 <![CDATA[15·2 μ kHz]]> 2OSs B2 139 <![CDATA[15·2 μ kHz]]> 4OSs B3 139 <![CDATA[15·2 μ kHz]]> 6OSs B4 139 <![CDATA[15·2 μ kHz]]> 12OSs C0 139 <![CDATA[15·2 μ kHz]]> 2OSs C2 139 <![CDATA[15·2 μ kHz]]> 6OSs

[0435] In the above embodiment, the PRACH resource of the IAB node can be sent using system information common to IAB nodes, such as IAB-SIB1, and the protocol predefines an IAB-SI-RNTI dedicated to the IAB node for scrambling the CRC of the scheduling system information PDCCH.

[0436] In the above embodiments, an IAB node sometimes refers to an IAB terminal (IAB node MT) for communicating with a parent node, and sometimes refers to an IAB base station (IAB node DU) for communicating with a child node. The specific IAB node can be distinguished based on the context.

[0437] The value of Ngap is the same as the value of Ngap in the random access time slot validity judgment of a common terminal.

[0438] In summary, determining the validity of random access opportunities based on the unavailable resource configuration and the resource configuration of the IAB node DU can more rationally determine the validity of random access opportunities, reduce useless signal transmission, and avoid unnecessary interference and power consumption. This also provides a method for distinguishing random access responses from ordinary UEs and IAB nodes, resolving the problem of multiplexing random access responses from UEs and IAB nodes, where only one UE and IAB node can successfully access the random access even if they use different PRACH resources.

[0439] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0440] This embodiment also provides a device for receiving a random access signal, which is used to implement the above-mentioned embodiments and preferred implementations. Details already described will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented using software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0441] Figure 7 is a structural block diagram of a random access signal receiving apparatus according to an embodiment of the present invention. Figure 7 As shown, the device includes: a first sending module 72 and a first receiving module 74. The device is described in detail below:

[0442] A first sending module 72, configured to send resource configuration information to the second node;

[0443] The first receiving module 74 is connected to the first sending module 72 and is configured to receive a random access signal sent by the second node according to the resource configuration information, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity.

[0444] Through the above module, the first node sends resource configuration information to the second node, and the first node receives the random access signal sent by the second node based on the resource configuration information. This achieves the purpose of the first and second nodes determining the validity of random access opportunities based on the resource configuration information. The second node sends the random access signal within a valid random access opportunity, and the first node receives the random access signal within a valid random access opportunity. Therefore, the problem of determining the validity of random access opportunities existing in the related art can be solved, achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and avoiding unnecessary interference and power consumption.

[0445] In an optional embodiment, the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, frequency domain resources of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a wireless frame, a time slot number, a subframe number, unavailable resource configuration, and available resource configuration.

[0446] In an optional embodiment, the frequency domain resources of the PRACH include: the starting frequency of the PRACH resources; and the number of frequency domain multiplexed PRACHs.

[0447] In an optional embodiment, the starting frequency of the PRACH resources is determined in one of the following ways: the first node determines the starting frequency of the PRACH resources based on the activated uplink bandwidth BWP; the first node determines the starting frequency of the PRACH resources based on the offset of the starting physical resource block PRB of the initial access PRACH frequency domain resources of the terminal device; the first node determines the starting frequency of the PRACH resources based on the offset of the ending PRB of the initial access PRACH frequency domain resources of the terminal device.

[0448] In an optional embodiment, the offset y_offset of the radio frame includes: an offset relative to a preset parameter y in a preset resource configuration table of the PRACH, wherein the preset parameter y refers to an index of a radio frame containing a PRACH opportunity within a PRACH configuration period.

[0449] In an optional embodiment, the radio frame number SFN where the random access occasion is located satisfies one of the following formulas: mod(SFN, min{x*S, Tmax}) = mod(y + y_offset, min{x*S, Tmax}), where y_offset is an integer and 0 ≤ y_offset < Tmax; mod(SFN, x*S) = y_offset, where y_offset is an integer and 0 ≤ y_offset < x*S; where x and y are parameters in the preset resource configuration table of the PRACH, and Tmax is the maximum value of the configuration period of the PRACH allowed by the second node.

[0450] In an optional embodiment, after the first node receives the random access signal sent by the second node according to the resource configuration information, the first node sends a random access response to the second node, where the cyclic redundancy check CRC of the physical downlink control channel PDCCH corresponding to the random access response is scrambled with the RA-RNTI; the RA-RNTI corresponds to the PRACH that transmits the random access signal, and the calculation formula of the RA-RNTI includes: RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id + 14×80×8×2; s_id is the symbol index of the first orthogonal frequency division multiplexing OFDM of the PRACH, 0 ≤ s_id < 14; t_id is the slot index of the first slot of the PRACH, 0 ≤ t_id < 80; f_id is the frequency domain index of the PRACH, 0 ≤ f_id < 8; ul_carrier_id is the uplink carrier used to indicate that the PRACH transmits the random access signal.

[0451] In an optional embodiment, after the first node receives the random access signal sent by the second node according to the resource configuration information, the first node sends a random access response to the second node, where the reserved field of the MAC-RAR in the random access response indicates that the MAC-RAR is the MAC-RAR of the second node.

[0452] In an optional embodiment, each MAC-RAR corresponds to a sub-header, and the sub-header includes a random access preamble identifier RAPID; the sub-header and the MAC-RAR form a media access control protocol data unit MAC subPDU; when the RAPID corresponding to the random access signal sent by the terminal device in the media access control protocol data unit MAC-PDU is the same as the RAPID corresponding to the random access signal sent by the second node, the MAC subPDU of the terminal device is in front of the MAC subPDU of the second node.

[0453] In an optional embodiment, the subframe number includes: a subframe number indicated by a PRACH configuration index in a preset resource configuration table for replacing the PRACH, wherein the replaced subframe number is an index set including an ROs subframe.

[0454] In an optional embodiment, the time slot number includes: a time slot number indicated by a PRACH configuration index in a preset resource configuration table for replacing the PRACH, wherein the replaced time slot number is an index set including an ROs time slot.

[0455] In an optional embodiment, before the first node receives the random access signal sent by the second node according to the resource configuration information, it also includes: the first node determines the validity of the random access opportunity, wherein the first node determines the validity of the random access opportunity including one of the following: when the first node does not provide the uplink and downlink configuration of time division duplex for the second node, the random access opportunity is valid if the random access opportunity meets the following conditions: the random access opportunity is not in front of the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB reception symbol, and the random access opportunity does not overlap with the specific resource in the time domain; when the first node provides the uplink and downlink configuration of time division duplex for the second node, the random access opportunity is valid if the random access opportunity meets one of the following conditions: the random access opportunity is in the uplink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not in the PRACH time slot The random access opportunity is in front of the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not in front of the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not in front of the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; wherein the specific resources include at least one of the following: resources that the second node cannot use, hard resources of the base station unit of the second node, hard resources used by the base station unit of the second node to transmit important signals or channels, and hard resources of the base station unit of the second node. UL resources, hard UL resources used by the base station unit of the second node to transmit important signals or channels; important signals or channels include at least one of the following: SSB, system information, PRACH, URLLC signals or channels.

[0456] In an optional embodiment, before the first node receives the random access signal sent by the second node according to the resource configuration information, the method further includes: the first node determining the validity of the random access opportunity, wherein the first node determining the validity of the random access opportunity includes one of the following:

[0457] If no time division duplex uplink and downlink configuration is provided for the second node at the first node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource;

[0458] When the first node provides the uplink and downlink configuration of time division duplex for the second node, and the random access opportunity in the PRACH time slot meets one of the following conditions, the random access opportunity is valid: the random access opportunity is within the uplink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access starting point is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource;

[0459] The specific resources include at least one of the following: resources indicated by the available resource configuration, non-hard resources of the base station unit of the second node, non-hard UL resources of the base station unit of the second node, and unavailable resources of the base station unit of the second node.

[0460] Figure 8 is a structural block diagram of a device for sending a random access signal according to an embodiment of the present invention. Figure 8 As shown, the device includes: a second receiving module 82, a determining module 84 and a second sending module 86. The device is described in detail below:

[0461] A second receiving module 82, configured to receive resource configuration information sent by the first node;

[0462] a determination module 84, connected to the second receiving module 82, configured to determine the validity of the random access opportunity based on the resource configuration information;

[0463] The second sending module 86 is connected to the above-mentioned determining module 84, and is configured to send a random access signal to the first node in a valid random access opportunity.

[0464] Through the above module, since the second node receives resource configuration information sent by the first node, the second node determines the validity of the random access opportunity based on the resource configuration information, and the second node sends a random access signal to the first node during a valid random access opportunity. This achieves the purpose of the first and second nodes determining the validity of the random access opportunity based on the resource configuration information. The second node sends the random access signal during a valid random access opportunity, and the first node receives the random access signal during a valid random access opportunity. Therefore, the problem of determining the validity of random access opportunities existing in the related art can be solved, achieving a more reasonable determination of the validity of random access opportunities, reducing the transmission of useless signals, and avoiding unnecessary interference and power consumption.

[0465] In an optional embodiment, the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, frequency domain resources of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a wireless frame, a time slot number, a subframe number, unavailable resource configuration, and available resource configuration.

[0466] In an optional embodiment, the frequency domain resources of the PRACH include: the starting frequency of the PRACH resources; and the number of frequency domain multiplexed PRACHs.

[0467] In an optional embodiment, the starting frequency of the PRACH resource is determined by one of the following information: the activated uplink bandwidth BWP; the offset of the starting physical resource block PRB of the terminal device's initial access PRACH frequency domain resources; the offset of the ending PRB of the terminal device's initial access PRACH frequency domain resources.

[0468] In an optional embodiment, the offset y_offset of the radio frame includes: an offset relative to a preset parameter y in a preset resource configuration table of the PRACH, wherein the preset parameter y refers to an index of a radio frame containing a PRACH opportunity within a PRACH configuration period.

[0469] In an optional embodiment, the radio frame number SFN where the random access opportunity is located satisfies one of the following formulas: mod(SFN, min{x*S, Tmax}) = mod(y + y_offset, min{x*S, Tmax}), where y_offset is an integer and 0 ≤ y_offset < Tmax; mod(SFN, x*S) = y_offset, where y_offset is an integer and 0 ≤ y_offset < x*S; where x and y are parameters in the preset resource configuration table of the PRACH, and Tmax is the maximum value of the configuration period of the PRACH allowed by the second node.

[0470] In an optional embodiment, after the second node sends a random access signal to the first node at a valid random access opportunity, the second node receives the random access response sent by the first node and descrambles the cyclic redundancy check CRC of the physical downlink control channel PDCCH corresponding to the random access response with the RA-RNTI; the RA-RNTI corresponds to the PRACH that transmits the random access signal, and the calculation formula of the RA-RNTI includes: RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id + 14×80×8×2; s_id is the symbol index of the first orthogonal frequency division multiplexing OFDM of the PRACH, 0 ≤ s_id < 14; t_id is the slot index of the first slot of the PRACH, 0 ≤ t_id < 80; f_id is the frequency domain index of the PRACH, 0 ≤ f_id < 8; ul_carrier_id is the uplink carrier used to indicate that the PRACH transmits the random access signal.

[0471] In an optional embodiment, after the second node sends a random access signal to the first node at a valid random access opportunity, the second node receives the random access response sent by the first node and determines whether the MAC-RAR is the MAC-RAR of the second node according to the reserved field of the MAC-RAR in the random access response.

[0472] In an optional embodiment, each MAC-RAR corresponds to a sub-header, and the sub-header includes a random access preamble identifier RAPID; the sub-header and the MAC-RAR form a media access control sub-protocol data unit MAC subPDU; when the RAPID corresponding to the random access signal sent by the terminal device in the media access control protocol data unit MAC-PDU is the same as the RAPID corresponding to the random access signal sent by the second node, the MAC subPDU of the terminal device is in front of the MAC subPDU of the second node.

[0473] In an optional embodiment, the subframe number includes: a subframe number indicated by a PRACH configuration index in a preset resource configuration table for replacing the PRACH, wherein the replaced subframe number is an index set including an ROs subframe.

[0474] In an optional embodiment, the time slot number includes: a time slot number indicated by a PRACH configuration index in a preset resource configuration table for replacing the PRACH, wherein the replaced time slot number is an index set including an ROs time slot.

[0475] In an optional embodiment, when the first node does not provide the uplink and downlink configuration of time division duplex for the second node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0476] When the first node provides a time division duplex uplink and downlink configuration for the second node, and the random access opportunity in the PRACH time slot meets one of the following conditions, the random access opportunity is valid: the random access opportunity is within the uplink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with the specific resource in the time domain;

[0477] The specific resources include at least one of the following: resources indicated by an unavailable resource configuration, hard resources of the base station unit of the second node, hard resources of the base station unit of the second node used for transmitting important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources of the base station unit of the second node used for transmitting important signals or channels;

[0478] Important signals or channels include at least one of the following: SSB, system information, PRACH, URLLC signals or channels.

[0479] In an optional embodiment, before the second node sends the random access signal to the first node in a valid random access opportunity, the method further includes: the second node determining the validity of the random access opportunity, wherein the second node determining the validity of the random access opportunity includes one of the following:

[0480] If no time division duplex uplink and downlink configuration is provided for the second node at the first node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource;

[0481] When the first node provides the uplink and downlink configuration of time division duplex for the second node, and the random access opportunity in the PRACH time slot meets one of the following conditions, the random access opportunity is valid: the random access opportunity is within the uplink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access starting point is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource;

[0482] The specific resources include at least one of the following: resources indicated by the available resource configuration, non-hard resources of the base station unit of the second node, non-hard UL resources of the base station unit of the second node, and unavailable resources of the base station unit of the second node;

[0483] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0484] An embodiment of the present invention further provides a storage medium storing a computer program, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0485] Optionally, in this embodiment, the above-mentioned storage medium may be configured to store a computer program for executing the above steps.

[0486] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0487] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0488] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0489] Optionally, in this embodiment, the processor may be configured to execute the above steps through a computer program.

[0490] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0491] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, centralized on a single computing device, or distributed across a network of multiple computing devices. Alternatively, they can be implemented using program code executable by a computing device, which can then be stored in a storage device and executed by the computing device. In some cases, the steps shown or described can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0492] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A method for receiving a random access signal, characterized in that: include: The first node sends resource configuration information to the second node; The first node receives, according to the resource configuration information, a random access signal sent by the second node, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity; wherein the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, a frequency domain resource of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a radio frame, a time slot number, a subframe number, an unavailable resource configuration, and an available resource configuration; Before the first node receives the random access signal sent by the second node according to the resource configuration information, it also includes: the first node determines the validity of the random access opportunity, wherein the first node determines the validity of the random access opportunity including: for paired spectrum, the random access opportunity is valid; for unpaired spectrum, when the first node does not provide time division duplex uplink and downlink configuration for the second node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not in front of the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB reception symbol, and the random access opportunity does not overlap with specific resources in the time domain, wherein the specific resources include at least one of the following: resources indicated by the unavailable resource configuration, hard resources of the base station unit of the second node, hard resources of the base station unit of the second node used to transmit important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources of the base station unit of the second node used to transmit important signals or channels.

2. The method according to claim 1, characterized in that The frequency domain resources of the PRACH include: The starting frequency of the PRACH resource; The number of the PRACHs multiplexed in the frequency domain.

3. The method according to claim 2, characterized in that The starting frequency of the PRACH resource is determined by one of the following methods: The first node determines a starting frequency of the PRACH resource based on an activated uplink bandwidth BWP; The first node determines the starting frequency of the PRACH resource based on the offset of the starting physical resource block PRB of the initial access PRACH frequency domain resource of the terminal device; The first node determines the starting frequency of the PRACH resource based on the offset of the ending PRB of the initial access PRACH frequency domain resource of the terminal device.

4. The method according to claim 1, wherein The offset y_offset of the radio frame includes: The offset relative to the preset parameter y in the preset resource configuration table of the PRACH, wherein the preset parameter y refers to the radio frame index containing the PRACH opportunity within the PRACH configuration period.

5. The method according to claim 4, characterized in that The radio frame number SFN where the random access opportunity is located satisfies one of the following formulas: mod(SFN, min{x * S , Tmax}) = mod(y + y_offset, min{x * S , Tmax}), where y_offset is an integer and 0≤y_offset <Tmax; mod(SFN, x * S) = y_offset, where y_offset is an integer and 0≤y_offset <x * S; The x and y are parameters in the preset resource configuration table of the PRACH, and the Tmax is the maximum value of the configuration period of the PRACH allowed by the second node.

6. The method according to claim 1, characterized in that After the first node receives the random access signal sent by the second node according to the resource configuration information, the method further includes: The first node sends a random access response to the second node, wherein a cyclic redundancy check (CRC) of a physical downlink control channel (PDCCH) corresponding to the random access response is scrambled using a random access radio network temporary identifier (RA-RNTI); The RA-RNTI corresponds to the PRACH that transmits the random access signal, and the calculation formula of the RA-RNTI includes: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id +14×80×8×2; The s_id is the first orthogonal frequency division multiplexing (OFDM) symbol index of the PRACH, 0≤s_id<14; the t_id is the first time slot index of the PRACH, 0≤t_id<80; the f_id is the frequency domain index of the PRACH, 0≤f_id<8; the ul_carrier_id is used to indicate the uplink carrier of the PRACH transmitting the random access signal.

7. The method according to claim 1, characterized in that After the first node receives the random access signal sent by the second node according to the resource configuration information, the method further includes: The first node sends a random access response to the second node, wherein a reserved field of a medium access response MAC-RAR in the random access response indicates that the MAC-RAR is the MAC-RAR of the second node.

8. The method according to claim 7, characterized in that Each of the MAC-RARs corresponds to a subheader, and the subheader includes a random access preamble identifier RAPID; The sub-header and the MAC-RAR constitute a media access control sub-protocol data unit MAC subPDU; When the RAPID corresponding to the random access signal sent by the terminal device in the media access control protocol data unit MAC-PDU is the same as the RAPID corresponding to the random access signal sent by the second node, the MAC subPDU of the terminal device is in front of the MAC subPDU of the second node.

9. The method according to claim 1, characterized in that The subframe number includes: Used to replace the subframe number indicated by the PRACH configuration index in the preset resource configuration table of the PRACH, wherein the replaced subframe number is an index set including the ROs subframe.

10. The method according to claim 1, characterized in that The time slot number includes: Used to replace the time slot number indicated by the PRACH configuration index in the preset resource configuration table of the PRACH, wherein the replaced time slot number is an index set including the ROs time slot.

11. The method according to claim 1, wherein Before the first node receives the random access signal sent by the second node according to the resource configuration information, the method further includes: the first node determining validity of the random access opportunity, wherein the first node determining validity of the random access opportunity includes one of the following: If the first node provides the second node with a time division duplex uplink and downlink configuration, and a random access opportunity in a PRACH time slot satisfies one of the following conditions, the random access opportunity is valid: the random access opportunity is within an uplink symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with a specific resource in the time domain. The specific resource includes at least one of the following: a resource indicated by the unavailable resource configuration, a hard resource of the base station unit of the second node, a hard resource used by the base station unit of the second node to transmit an important signal or channel, a hard UL resource of the base station unit of the second node, and a hard UL resource used by the base station unit of the second node to transmit an important signal or channel; The important signal or channel includes at least one of the following: SSB, system information, PRACH, URLLC signal or channel.

12. The method according to claim 1, characterized in that Before the first node receives the random access signal sent by the second node according to the resource configuration information, the method further includes: the first node determining validity of the random access opportunity, wherein the first node determining validity of the random access opportunity includes one of the following: If the first node does not provide the second node with a time division duplex uplink and downlink configuration, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; When the first node provides the second node with a time division duplex uplink and downlink configuration, and the random access opportunity in the PRACH time slot meets one of the following conditions, the random access opportunity is valid: the random access opportunity is within the uplink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; The specific resources include at least one of the following: resources indicated by the available resource configuration, non-hard resources of the base station unit of the second node, non-hard UL resources of the base station unit of the second node, and unavailable resources of the base station unit of the second node.

13. A method for sending a random access signal, characterized in that: include: The second node receives the resource configuration information sent by the first node; The second node determines the validity of the random access opportunity based on the resource configuration information; The second node sends a random access signal to the first node at a valid random access opportunity; wherein the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, a frequency domain resource of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a radio frame, a time slot number, a subframe number, an unavailable resource configuration, and an available resource configuration; Before the second node sends a random access signal to the first node under a valid random access opportunity, the second node also includes: the second node determines the validity of the random access opportunity, wherein the second node determines the validity of the random access opportunity including: for paired spectrum, the random access opportunity is valid; for unpaired spectrum, when the first node does not provide time division duplex uplink and downlink configuration for the second node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not in front of the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB reception symbol, and the random access opportunity does not overlap with specific resources in the time domain, wherein the specific resources include at least one of the following: resources indicated by the unavailable resource configuration, hard resources of the base station unit of the second node, hard resources of the base station unit of the second node used to transmit important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources of the base station unit of the second node used to transmit important signals or channels.

14. The method according to claim 13, characterized in that The frequency domain resources of the PRACH include: The starting frequency of the PRACH resource; The number of the PRACHs multiplexed in the frequency domain.

15. The method according to claim 14, characterized in that The starting frequency of the PRACH resource is determined by one of the following information: Activated uplink bandwidth BWP; The offset of the starting physical resource block (PRB) of the terminal device's initial access PRACH frequency domain resource; The offset of the ending PRB of the initial access PRACH frequency domain resource of the terminal device.

16. The method according to claim 13, characterized in that The offset y_offset of the radio frame includes: The offset relative to the preset parameter y in the preset resource configuration table of the PRACH, wherein the preset parameter y refers to the radio frame index containing the PRACH opportunity within the PRACH configuration period.

17. The method according to claim 16, characterized in that The radio frame number SFN where the random access opportunity is located satisfies one of the following formulas: mod(SFN, min{x * S , Tmax}) = mod(y + y_offset, min{x * S , Tmax}), where y_offset is an integer and 0≤y_offset <Tmax; mod(SFN, x * S) = y_offset, where y_offset is an integer and 0≤y_offset <x * S; The x and y are parameters in the preset resource configuration table of the PRACH, and the Tmax is the maximum value of the configuration period of the PRACH allowed by the second node.

18. The method according to claim 13, characterized in that After the second node sends a random access signal to the first node in a valid random access opportunity, the method further includes: The second node receives the random access response sent by the first node, and descrambles a cyclic redundancy check (CRC) of a physical downlink control channel (PDCCH) corresponding to the random access response using the RA-RNTI; The RA-RNTI corresponds to the PRACH that transmits the random access signal, and the calculation formula of the RA-RNTI includes: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id +14×80×8×2; The s_id is the first orthogonal frequency division multiplexing (OFDM) symbol index of the PRACH, 0≤s_id<14; the t_id is the first time slot index of the PRACH, 0≤t_id<80; the f_id is the frequency domain index of the PRACH, 0≤f_id<8; the ul_carrier_id is used to indicate the uplink carrier of the PRACH transmitting the random access signal.

19. The method according to claim 13, wherein After the second node sends a random access signal to the first node in a valid random access opportunity, the method further includes: The second node receives the random access response sent by the first node, and determines whether the MAC-RAR is the MAC-RAR of the second node according to the reserved field of the MAC-RAR in the random access response.

20. The method according to claim 19, characterized in that Each of the MAC-RARs corresponds to a subheader, and the subheader includes a random access preamble identifier RAPID; The sub-header and the MAC-RAR constitute a media access control sub-protocol data unit MAC subPDU; When the RAPID corresponding to the random access signal sent by the terminal device in the media access control protocol data unit MAC-PDU is the same as the RAPID corresponding to the random access signal sent by the second node, the MAC subPDU of the terminal device is in front of the MAC subPDU of the second node.

21. The method according to claim 13, wherein The subframe number includes: Used to replace the subframe number indicated by the PRACH configuration index in the preset resource configuration table of the PRACH, wherein the replaced subframe number is an index set including the ROs subframe.

22. The method according to claim 13, wherein The time slot number includes: Used to replace the time slot number indicated by the PRACH configuration index in the preset resource configuration table of the PRACH, wherein the replaced time slot number is an index set including the ROs time slot.

23. The method according to claim 13, wherein Before the second node sends the random access signal to the first node in a valid random access opportunity, the method further includes: the second node determining the validity of the random access opportunity, wherein the second node determining the validity of the random access opportunity includes one of the following: If the first node provides the second node with a time division duplex uplink and downlink configuration, and a random access opportunity in a PRACH time slot satisfies one of the following conditions, the random access opportunity is valid: the random access opportunity is within an uplink symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, and the starting point of the random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with a specific resource in the time domain; the random access opportunity is not before an SSB in the PRACH time slot, the starting point of the random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity does not overlap with a specific resource in the time domain; The specific resource includes at least one of the following: a resource indicated by the unavailable resource configuration, a hard resource of the base station unit of the second node, a hard resource used by the base station unit of the second node to transmit an important signal or channel, a hard UL resource of the base station unit of the second node, and a hard UL resource used by the base station unit of the second node to transmit an important signal or channel; The important signal or channel includes at least one of the following: SSB, system information, PRACH, URLLC signal or channel.

24. The method according to claim 13, wherein Before the second node sends the random access signal to the first node in a valid random access opportunity, the method further includes: the second node determining the validity of the random access opportunity, wherein the second node determining the validity of the random access opportunity includes one of the following: If the first node does not provide the uplink and downlink configuration of time division duplex for the second node, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not before the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; When the first node provides the second node with a time division duplex uplink and downlink configuration, and the random access opportunity in the PRACH time slot satisfies one of the following conditions, the random access opportunity is valid: the random access opportunity is within the uplink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last downlink symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; the random access opportunity is not before the SSB in the PRACH time slot, and the starting point of random access is at least Ngap symbols after the last SSB received symbol, and the random access opportunity is within the specific resource; The specific resources include at least one of the following: resources indicated by the available resource configuration, non-hard resources of the base station unit of the second node, non-hard UL resources of the base station unit of the second node, and unavailable resources of the base station unit of the second node.

25. A random access signal receiving device, characterized in that: include: A first sending module, configured to send resource configuration information to the second node; A first receiving module is configured to receive, according to the resource configuration information, a random access signal sent by the second node, wherein the resource configuration information is used to instruct the second node to send the random access signal at a valid random access opportunity; wherein the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, a frequency domain resource of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a radio frame, a timeslot number, a subframe number, an unavailable resource configuration, and an available resource configuration; The device is also used to determine the validity of the random access opportunity before receiving the random access signal sent by the second node according to the resource configuration information, wherein determining the validity of the random access opportunity includes: for paired spectrum, the random access opportunity is valid; for unpaired spectrum, the random access opportunity is valid when no time division duplex uplink and downlink configuration is provided for the second node and the random access opportunity in the PRACH time slot meets the following conditions: the random access opportunity is not in front of the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB reception symbol, and the random access opportunity does not overlap with specific resources in the time domain, wherein the specific resources include at least one of the following: resources indicated by the unavailable resource configuration, hard resources of the base station unit of the second node, hard resources of the base station unit of the second node used to transmit important signals or channels, hard UL resources of the base station unit of the second node, and hard UL resources of the base station unit of the second node used to transmit important signals or channels.

26. A random access signal transmitting device, characterized in that: include: A second receiving module, configured to receive resource configuration information sent by the first node; a determination module, configured to determine the validity of the random access opportunity based on the resource configuration information; A second sending module is configured to send a random access signal to the first node at a valid random access opportunity; wherein the resource configuration information includes at least one of the following: a configuration index of a physical random access channel PRACH, a frequency domain resource of the PRACH, a mapping relationship between a synchronization signal block SSB and a random access opportunity ROs, a starting logical root sequence index and a cyclic shift Ncs, a configuration period scaling factor S of the PRACH, an offset y_offset based on a radio frame, a timeslot number, a subframe number, an unavailable resource configuration, and an available resource configuration; The sending device is also used to judge the validity of the random access opportunity before sending a random access signal to the first node under a valid random access opportunity, wherein judging the validity of the random access opportunity includes: for paired spectrum, the random access opportunity is valid; for unpaired spectrum, when the first node does not provide time division duplex uplink and downlink configuration, and the random access opportunity in the PRACH time slot meets the following conditions, the random access opportunity is valid: the random access opportunity is not in front of the SSB in the PRACH time slot, the starting point of the random access opportunity is at least Ngap symbols after the last SSB reception symbol, and the random access opportunity does not overlap with specific resources in the time domain, wherein the specific resources include at least one of the following: resources indicated by the unavailable resource configuration, hard resources of the base station unit of the sending device, hard resources used by the base station unit of the sending device to transmit important signals or channels, hard UL resources of the base station unit of the sending device, and hard UL resources used by the base station unit of the sending device to transmit important signals or channels.

27. A storage medium, characterized in that The storage medium stores a computer program, wherein the computer program is configured to execute the method described in any one of claims 1 to 12 when run, or the computer program is configured to execute the method described in any one of claims 13 to 24 when run.

28. An electronic device comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to run the computer program to perform the method described in any one of claims 1 to 12, or the processor is configured to run the computer program to perform the method described in any one of claims 13 to 24.

Images