Resource allocation methods, resource selection methods, facilities, and storage media
The method and device optimize PRACH time-frequency resource allocation for RedCap UEs, enhancing their transmission performance to match normal NR UEs by configuring and transmitting resources tailored to their capabilities.
Patent Information
- Application Number
- KR1020237027779
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-01-15
- Filing Date
- 2021-12-16
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-12-16
AI Technical Summary
Reduced Capability UEs (RedCap UEs) perform worse than normal NR UEs in transmission and reception due to reduced bandwidth and antenna number, necessitating enhancements in uplink and downlink channels, and the base station needs to allocate time-frequency resources effectively to support RedCap UEs.
A method and device for configuring and transmitting PRACH time-frequency resources to RedCap UEs, allowing the base station to enhance subsequent UL and DL channels based on the UE type, along with a resource selection method and facility for RedCap UEs to utilize these resources.
Enhances the transmission performance of RedCap UEs to match that of normal NR UEs by optimizing resource allocation and selection, ensuring effective communication.
Smart Images

Figure 112023089977773-PCT00004_ABST
Abstract
Description
Technology Field
[0001] The present application relates to communication, for example, to a resource allocation method, a resource selection method, equipment, and a storage medium. Background Technology
[0002] New Radio (NR) systems offer greater configuration flexibility and wider application bandwidth compared to communication systems of related technologies. Consequently, terminals with higher capability requirements are needed to support NR. However, not all scenarios require support for high-performance terminals such as wearables, video surveillance, and industrial wireless sensors. In these scenarios, NR terminals with reduced capabilities can meet the requirements. These reduced capability terminals (Reduced Capability UEs, RedCap UEs) support small bandwidth and a small number of antennas.
[0003] Due to the reduction in bandwidth and the number of antennas, the RedCap UE performs worse than a normal NR UE in both transmission performance on the uplink channel and reception performance on the downlink channel. Therefore, in order for the RedCap UE to achieve the same transmission performance as an NR UE, certain enhancements must be made in the uplink (UL) and downlink (DL).
[0004] In the Initial Random Access Procedure, the base station does not know whether the UE is a RedCap UE. Accordingly, the UE must implicitly notify the base station of whether the current UE is a RedCap UE through Msg1 (PRACH Preambles) transmitted by the UE. Furthermore, after receiving the PRACH Preamble, the base station may choose whether to perform enhancement processing on the UL channel and DL channel later, depending on the type of UE. Therefore, how to allocate time frequency resources to a RedCap UE is a task that needs to be urgently addressed. The problem to be solved
[0005] In light of this, embodiments of the present application provide a resource allocation method, a resource selection method, an apparatus, and a storage medium for implementing the allocation of time frequency resources occupied by a first type of communication node. means of solving the problem
[0006] An embodiment of the present application provides a resource allocation method, said method, said method,
[0007] A step of configuring a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node; and
[0008] It includes the step of transmitting the above PRACH time frequency resource to the above first type communication node.
[0009] An embodiment of the present application provides a resource allocation device, said device, said device,
[0010] A configuration module that configures a PRACH time frequency resource occupied by a random access preamble of a physical random access channel (PRACH) corresponding to a first-type communication node; and
[0011] It includes a transmitter that transmits the above PRACH time frequency resource to the above first type communication node.
[0012] An embodiment of the present application provides a resource selection method, said method, said method,
[0013] A step of receiving a PRACH time frequency resource transmitted by a Type 4 communication node; and
[0014] It includes the step of selecting a PRACH time frequency resource occupied by the PRACH Preamble from the above PRACH time frequency resource.
[0015] An embodiment of the present application provides a resource selection device, said device, said device,
[0016] A receiver receiving a PRACH time frequency resource transmitted by a Type 4 communication node; and
[0017] It includes a selector that selects a PRACH time frequency resource occupied by the PRACH Preamble from the above PRACH time frequency resource.
[0018] An embodiment of the present application provides a communication facility, said communication facility comprising a communication module, a memory, and one or more processors;
[0019] The above communication module is configured to perform communication interaction between at least two communication nodes;
[0020] The above memory is configured to store one or more programs;
[0021] When the above one or more programs are executed by the above one or more processors, the above one or more processors are configured to implement a method according to any one embodiment.
[0022] An embodiment of the present application provides a storage medium, said storage medium has a computer program stored therein, and when said computer program is executed by a processor, a method according to any one embodiment is implemented. Brief explanation of the drawing
[0023] Figure 1 is a flowchart of a random access process provided by the relevant technology. Figure 2 is a schematic diagram of the fallback process of a 2-step RA type CBRA provided by the relevant technology. Figure 3 is a mapping relationship diagram between the SSB and the preamble provided by the relevant technology. FIG. 4 is a flowchart of a resource allocation method provided in an embodiment of the present application. FIG. 5 is a flowchart of a resource selection method provided in an embodiment of the present application. FIG. 6 is a schematic diagram of resource allocation provided in an embodiment of the present application. FIG. 7 is a schematic diagram of another resource allocation provided in an embodiment of the present application. FIG. 8 is a schematic diagram of another resource allocation provided in an embodiment of the present application. FIG. 9 is a structural block diagram of a resource allocation device provided in an embodiment of the present application. FIG. 10 is a structural block diagram of a resource selection device provided in an embodiment of the present application. FIG. 11 is a schematic diagram of the structure of a communication facility provided in an embodiment of the present application. Specific details for implementing the invention
[0024] Embodiments of the present application will be described in conjunction with the attached drawings below. Hereinafter, the present application will be described in conjunction with the embodiments and the attached drawings, and the examples presented are for the purpose of interpreting the present application and do not limit the scope of the present application.
[0025] In the NR system, two types of random access processes are supported: a 4-step RA type that transmits Msg1 and a 2-step RA type that transmits MsgA. Figure 1 is a flowchart of the random access process provided by the relevant technology. As shown in Figure 1, both types of RA processors support contention-based random access (CBRA) and contention-free random access (CFRA).
[0026] The network does not simultaneously configure CFRA resources of 4-step and 2-step RA types for the BandWidth Part (BWP). CFRA of the 2-step RA type supports only transitions.
[0027] Msg1 of the 4-step RA type consists of a random access preamble of the Physical Random Access Channel (PRACH). After transmitting Msg1, the UE monitors the network response within the configuration window. As illustrated in FIG. 1(c), for CFRA, the network allocates a dedicated preamble for Msg1 transmission, and after receiving a random access response from the network, the UE terminates the random access process. As illustrated in FIG. 1(a), for CBRA, after receiving the random access response, the UE transmits Msg3 using the UL accepted in the response and monitors the contention results. If the contention results are unsuccessful after transmitting or retransmitting Msg3, the UE returns to transmitting Msg1.
[0028] A MsgA of the 2-step RA type includes a Preamble of PRACH and a payload of PUSCH. After the transmission of MsgA, the UE monitors the network response within the configuration window. As illustrated in FIG. 1(d), for CFRA, dedicated Preamble and PUSCH resources are configured for the transmission of MsgA, and after receiving the network response, the UE terminates the random access process. As illustrated in FIG. 1(b), for CBRA, if the contention result is successful after receiving the network response, the UE terminates the random access process. FIG. 2 is a schematic diagram of the fallback process of a 2-step RA type CBRA provided in the relevant technology, and as illustrated in FIG. 2, upon receiving a fallback instruction from MsgB, the UE performs a transmission of Msg3 using the UL accepted in the fallback instruction and monitors the contention result. If the contention result is not successful after the transmission or retransmission of Msg3, the UE returns to the transmission of MsgA.
[0029] After performing multiple MsgA transmissions, if the random access process having a 2-step RA type is not completed, the UE can be configured and switched to a CBRA having a 4-step RA type.
[0030] Here, the mapping relationship between SSB and PRACH time frequency resources (Occasion) is as follows.
[0031] The SSB is an SS / PBCH block, which carries downlink synchronization signals (including the primary synchronization signal (PSS) and secondary synchronization signal (SSS)) and the PBCH (physical broadcast channel, which carries Master Information Block (MIB) information). Since NR supports multiple beam transmissions, the SSB also supports transmission in multiple beam directions, which, to put it simply, supports multiple SSBs being transmitted in a time-division manner.
[0032] A PRACH Occasion refers to a time-frequency resource corresponding to the transmission of a PRACH Preamble. Multiple PRACH Occasions may be included in the frequency domain at the same time. Additionally, it supports time-domain periodic transmission.
[0033] Since SSBs exist in NR, in the random access process, PRACH occasions and SSBs form a correspondence relationship, that is, one PRACH Occasion can correspond to one SSB or multiple SSBs, all configured by the base station. The upper layer parameter indicates the value of N, which indicates that N SSBs correspond to one PRACH occasion; in the case of contention-based random access, the upper layer parameter indicates N and R, which respectively indicate that N SSBs correspond to one PRACH occasion and each SSB corresponds to R preambles.
[0034] Figure 3 is a mapping relationship diagram between an SSB and a preamble provided by the relevant technology. As shown in Figure 3, taking the case where N=2 and R=24 as an example, N=2 indicates that 2 SSBs correspond to one PRACH occasion, R=24 indicates that 24 competing preambles correspond to one SSB, totalNumberOfRA-Preambles indicates the total number of preambles corresponding to an SSB, and one PRACH occasion corresponds to a total of 64 preambles.
[0035] Under the configuration of the number of SSBs within an SSB period, the configuration of PRACH time frequency resources, and the instructions of parameters N and R, the SSB and PRACH occasions can perform specific mapping in the order of first the frequency domain and then the time domain.
[0036] In one embodiment, FIG. 4 is a flowchart of a resource allocation method provided in an embodiment of the present application. This embodiment may be performed by a fourth type communication node. Here, the fourth type communication node may be a network side (e.g., a base station). As illustrated in FIG. 4, this embodiment includes steps (S110) through (S120).
[0037] Step (S110), configures a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node.
[0038] Step (S120), transmit the PRACH time frequency resource to the first type communication node.
[0039] In the embodiment, the first type communication node refers to a RedCap UE, and the second type communication node refers to an NR UE. In the embodiment, the fourth type communication node configures a PRACH time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node, and transmits the PRACH time frequency resource to the first type communication node so that the first type communication node performs PRACH Preamble transmission on the corresponding PRACH time frequency resource. In the embodiment, the first type communication node uploads a PRACH Preamble to the fourth type communication node using the PRACH time frequency resource corresponding to itself, and after the fourth type communication node receives the PRACH Preamble, it may select whether to perform enhancement processing on subsequent UL and DL channels according to the type of communication node. If the type of communication node is the first type communication node, enhancement processing is performed on the UL and DL channels to achieve the same transmission performance as the second type communication node. In one embodiment, the location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node is,
[0040] It includes at least one of: a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node; and a PRACH time frequency resource of a first-type communication node. In an embodiment, if the location where the PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first-type communication node is located includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node, it means that the PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first-type communication node and the PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node jointly use the same PRACH time frequency resource. In an embodiment, if a location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node includes the PRACH time frequency resource of the first type communication node, it means that the first type communication node and the second type communication node bear the transmission of the PRACH Preamble using their respective independent PRACH time frequency resources.
[0041] In one embodiment, where a location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is configured from a PRACH Preamble for a non-CBRA corresponding to the second type communication node.
[0042] In one embodiment, the step of configuring a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node is,
[0043] Indicating the starting index of the PRACH Preamble corresponding to the first type communication node through the first information;
[0044] Or, the start index of the PRACH Preamble corresponding to the first type communication node is the sum of the end index of the PRACH Preamble configured for the second type communication node and K; wherein K is an integer greater than or equal to 1.
[0045] In one embodiment, the termination index of the PRACH Preamble configured for the second type communication node is,
[0046] If Type 1 PRACH is supported, it is the end index of the Type 1 PRACH Preamble;
[0047] If supporting Type 2 PRACH, it includes one of the termination index of the Type 2 PRACH Preamble.
[0048] In the example, the first type PRACH means a 4-step PRACH; the second type PRACH means a 2-step PRACH; the first type PRACH Preamble means a 4-step PRACH Preamble, and the second type PRACH Preamble means a 2-step PRACH Preamble.
[0049] In one embodiment, when supporting Type 1 Msg3 and Type 2 Msg3,
[0050] If Type 1 PRACH is supported, the end index of the Type 1 PRACH Preamble is the end index of the Preamble corresponding to Type 1 Msg3;
[0051] If a second type PRACH is supported, the end index of the second type PRACH Preamble is the end index of the Preamble corresponding to the first type Msg3; one of which is included. In the embodiment, the first type Msg3 means Group B; and the second type Msg3 means Group A.
[0052] In one embodiment, when a first type communication node configures a first type PRACH, the step of configuring a time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node is:
[0053] It further includes indicating the number of PRACH Preambles corresponding to the first type communication node through the second information.
[0054] In one embodiment, when a first type communication node configures a first type PRACH and a second type PRACH, the step of configuring a time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node is:
[0055] Indicating the number of Type 1 PRACH Preambles corresponding to the Type 1 communication node through the second information;
[0056] It further includes indicating the number of Type 2 PRACH Preambles corresponding to the Type 1 communication node through the third information; wherein the start index of the Type 2 PRACH Preamble is the end index of the Type 1 PRACH Preamble configured for the second information plus 1. In the embodiment, the number of Type 1 PRACH Preambles means the number of 4-step PRACH Preambles; and the number of Type 2 PRACH Preambles means the number of 2-step PRACH Preambles.
[0057] In one embodiment, if the first type communication node supports the first type Msg3, the fourth information indicates the number of PRACH Preambles corresponding to the second type Msg3.
[0058] In one embodiment, if the first type communication node supports the first type Msg3, the number of PRACH Preambles corresponding to the second type Msg3 of the first type PRACH is indicated through the fourth information; and the number of PRACH Preambles corresponding to the second type Msg3 of the second type PRACH is indicated through the fifth information.
[0059] In one embodiment, when a first type communication node includes a first type terminal and a second type terminal, the step of configuring a time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node is:
[0060] Indicating the number of Type 1 PRACH Preambles corresponding to the Type 1 terminal through the 6th information;
[0061] Including indicating the number of first-type PRACH Preambles corresponding to the second-type terminal through the seventh information. In an embodiment, the characteristic of the first-type terminal is BW Reduction without Antenna Size Reduction, where the first-type terminal is configured with the bandwidth of Msg; the characteristic of the second-type terminal is BW Reduction with Antenna Size Reduction, where the second-type terminal is configured with the bandwidth of Msg3 and performs an enhancement design for the transmission of Msg.
[0062] In one embodiment, when a first type communication node supports a first type Msg3, the eighth information is used to indicate the number of PRACH Preambles corresponding to the second type Msg3 of the first type terminal; and the ninth information is used to indicate the number of PRACH Preambles corresponding to the second type Msg3 of the second type terminal.
[0063] In one embodiment, if the initial BWP configured for the first type communication node is greater than the operating bandwidth of the first type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is used by the first type communication node. In an embodiment, the initial BWP may be an initial uplink BWP or an initial downlink BWP. In the initial random access process, an uplink message (including Msg1 and Msg3) is transmitted from the initial uplink BWP; and in the initial random access process, a downlink message (including Msg2 and Msg4) is transmitted from the initial downlink BWP. In an embodiment, the operating bandwidth of the first type communication node may also be the maximum bandwidth supported by the first type communication node, the configured bandwidth of the first type communication node, the basic bandwidth of the first type communication node, or the preset bandwidth of the first type communication node.
[0064] In one embodiment, when the initial BWP configured for the first type communication node is less than or equal to the operating bandwidth of the first type communication node,
[0065] If the first type communication node is a first type communication node that supports or enables a Coverage Recovery (CR) function, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is the PRACH time frequency resource of the first type communication node;
[0066] In the case where the first type communication node is a first type communication node that does not support or enable the CR function, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is a PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; one of these is included. In an embodiment, the first type communication node that supports or enables the CR function may also be a first type communication node in which the Msg3 message supports the Coverage Recovery (CR) function; a first type communication node in which the Msg3 message supports the Repeat Transmission function; a first type communication node having an antenna size limitation capability; a first type communication node having a device size limitation capability; a first type communication node with limited coverage; or a first type communication node in which the downlink (Reference Signal Received Power, RSRP) measurement value is less than or equal to a preset threshold value. Here, the configuration method of the preset threshold value includes base station configuration; pre-configuration;
[0067] In one embodiment, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0068] PRACH time frequency resource of a Type 1 communication node;
[0069] It includes one of the PRACH time frequency resources jointly used by a Type 3 communication node and a Type 1 communication node, wherein the Type 3 communication node is a communication node that supports or enables a Coverage Enhancement (CE) function; and the jointly used PRACH time frequency resource is used by the Type 1 communication node and / or the Type 3 communication node to transmit a PRACH Preamble.
[0070] In one embodiment, if the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the Msg3 message carries instruction information of the communication node, and the instruction information of the communication node indicates that the communication node is the first type communication node or the third type communication node.
[0071] In one embodiment, if the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the size of the frequency domain resource occupied by the Msg3 message is less than or equal to the operating bandwidth of the first type communication node.
[0072] In one embodiment, signaling indicates the usage status of a first type communication node for a PRACH Preamble among PRACH time frequency resources corresponding to a second type communication node;
[0073] When signaling indicates that a Type 1 communication node uses a PRACH Preamble among the PRACH time frequency resources corresponding to a Type 2 communication node,
[0074] When a Type 1 communication node supports or enables CR, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the Type 1 communication node is the PRACH time frequency resource of the Type 1 communication node;
[0075] If the first type communication node does not support or enable CR, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; comprising at least one of these,
[0076] If the signaling indicates that the Type 1 communication node does not use the PRACH Preamble among the PRACH time frequency resources corresponding to the Type 2 communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the Type 1 communication node is the PRACH time frequency resource of the Type 1 communication node.
[0077] In an embodiment, signaling clearly indicates whether a first-type communication node can use a PRACH Preamble among the PRACH time frequency resources corresponding to a second-type communication node. In a situation where the signaling indicates that the first-type communication node can use a PRACH Preamble among the PRACH time frequency resources corresponding to the second-type communication node, if the first-type communication node supports or enables CR, the PRACH time frequency resources occupied by the PRACH Preamble corresponding to the first-type communication node can be used by the first-type communication node;
[0078] If the first type communication node does not support or enable CR, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node can be used by the first type communication node; at least one of these is included.
[0079] If the signaling indicates that the first type communication node cannot use the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node, the PRACH time frequency resources occupied by the PRACH Preamble corresponding to the first type communication node can be used by the first type communication node.
[0080] In one embodiment, FIG. 5 is a flowchart of a resource selection method provided in an embodiment of the present application. This embodiment is applied to a first type of communication node. As illustrated in FIG. 5, this embodiment includes steps (S210) to (S220).
[0081] Step (S210), receive the PRACH time frequency resource transmitted by the 4th type communication node.
[0082] Step (S220), select the PRACH time frequency resource occupied by the PRACH Preamble from the PRACH time frequency resource.
[0083] In one embodiment, the location where the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is located is,
[0084] It includes at least one of: a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node; and a PRACH time frequency resource of a first-type communication node.
[0085] In one embodiment, where a location having a PRACH time frequency resource occupied by a PRACH Preamble selected by a first type communication node includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is configured from a PRACH Preamble for non-contention-based random access (CBRA) corresponding to the second type communication node.
[0086] In one embodiment, if the initial bandwidth (BWP) configured for the first type communication node is greater than the operating bandwidth of the first type communication node, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node.
[0087] In one embodiment, when the initial BWP configured for the first type communication node is less than or equal to the operating bandwidth of the first type communication node,
[0088] If the first type communication node is a first type communication node that supports or enables a coverage recovery (CR) function, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node;
[0089] If the first type communication node is a first type communication node that does not support or enable the CR function, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is a PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; it includes one of these.
[0090] In one embodiment, signaling indicates the usage status of a first type communication node for a PRACH Preamble among PRACH time frequency resources corresponding to a second type communication node;
[0091] When signaling indicates that a Type 1 communication node uses a PRACH Preamble among the PRACH time frequency resources corresponding to a Type 2 communication node,
[0092] If the first type communication node supports or enables CR, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node;
[0093] If the first type communication node does not support or enable CR, the PRACH time frequency resource occupied by the PRACH Preamble selected by the second type communication node is the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; comprising at least one of the above.
[0094] If the signaling indicates that the first type communication node does not use the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node.
[0095] In one embodiment, a resource allocation process is described by taking as an example where one RO multiplexes the Preambles of two SSBs and configures a 4-step PRACH, and the first type of communication node is a RedCap UE and the second type of communication node is an NR UE. Here, RO refers to PRACH frequency domain resources (Occasions). FIG. 6 is a schematic diagram of resource allocation provided in an embodiment of the present application. As shown in FIG. 6, the location of the PRACH time domain resource occupied by the PRACH Preable corresponding to the RedCap UE in SSB0 and SSB1 is located in the PRACH time domain resource occupied by the PRACH Preamble corresponding to the NR UE. Specifically, the first information is Starting Preamble-RedCap-R17, the second information is ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17, and the fourth information is numberOfRA-PreamblesGroupA-RedCap-R17.
[0096] In the embodiment, ssb-perRACH-OccasionAndCB-PreamblesPerSSB is intended to configure the number of preambles configured for one SSB of the NR UE. Here, numberOfRA-PreamblesGroupA is intended to configure the number of preambles of Group A. In the embodiment, the time domain resource occupied by the PRACH preamble used by the RedCap UE is the CFRA preamble resource among the PRACH preambles used by the NR UE; Starting Preamble-RedCap-R17 indicates the starting index of the RedCap PRACH preamble. If the starting index of the RedCap PRACH preamble is not configured, it defaults to starting from the preamble end index + 1 configured for ssb-perRACH-OccasionAndCB-PreamblesPerSSB; ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17 is intended to indicate the number of PRACH preambles of the RedCap UE; If the RedCap UE supports Group B, numberOfRA-PreamblesGroupA-RedCap-R17 is intended to indicate the number of preambles corresponding to Group A.
[0097] In one embodiment, a resource allocation process is described by taking the example where one RO multiplexes the Preamble of two SSBs, configures a 4-step PRACH and a 2-step PRACH, and the first type of communication node is a RedCap UE and the second type of communication node is an NR UE. Here, RO refers to PRACH frequency domain resources (Occasions). FIG. 7 is a schematic diagram of another resource allocation provided in an embodiment of the present application. As shown in FIG. 7, the location where the PRACH time domain resource occupied by the PRACH Preable corresponding to the RedCap UE in SSB0 and SSB1 is located is the PRACH time domain resource occupied by the PRACH Preamble corresponding to the NR UE. Specifically, the first information is Starting Preamble-RedCap-R17, the second information is ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17, the third information is MsgA-CB-PreamblesPerSSB-PerSharedRO-r17, the fourth information is numberOfRA-PreamblesGroupA-RedCap-R17, and the fifth information is MsgA-numberOfRA-PreamblesGroupA-RedCap-R17.
[0098] In the example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB is intended to configure the number of 4-step RACH Preambles configured for one SSB among the NR UEs. Here, numberOfRA-PreamblesGroupA is intended to configure the number of Preambles for Group A. Here, MsgA-CB-PreamblesPerSSB-PerSharedRO-R16 is intended to configure the number of 2-step RACH Preambles configured for one SSB among the NR UEs. Here, numberOfRA-PreamblesGroupA-R16 is intended to configure the number of Preambles for Group A.
[0099] In the embodiment, the PRACH Preamble resource used by the RedCap UE occupies the Preamble resource of CFRA among the NR UE PRACH Preambles; and indicates the starting index of the RedCap PRACH Preamble through Starting Preamble-RedCap-R17. If the starting index of the RedCap PRACH Preamble is not configured, it starts by default from the Preamble end index + 1 configured for ssb-perRACH-OccasionAndCB-PreamblesPerSSB and MsgA-CB-PreamblesPerSSB-PerSharedRO-r16; ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17 is intended to indicate the number of 4-step PRACH Preambles of the RedCap UE; and MsgA-CB-PreamblesPerSSB-PerSharedRO-r17 is intended to indicate the number of 2-step PRACH Preambles of the RedCap UE; Additionally, the starting index of the 2-step PRACH Preamble of the RedCap UE is Preamble ending index+1 configured for ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17; and if the RedCap UE supports Group B, numberOfRA-PreamblesGroupA-RedCap-R17 is intended to indicate the number of Preambles corresponding to Group A of the 4-step RACH, and MsgA-numberOfRA-PreamblesGroupA-RedCap-R17 is intended to indicate the number of Preambles corresponding to Group A of the 2-step RACH.
[0100] In one embodiment, a resource allocation process is described by taking as an example a case where one RO multiplexes the Preamble of two SSBs, the first type communication node is a RedCapUE, the second type communication node is an NR UE, and a 4-step PRACH is configured. FIG. 8 is a schematic diagram of another resource allocation provided in an embodiment of the present application. As shown in FIG. 8, the RedCap UE and the NR UE each bear the transmission of the PRACH Preamble using independent PRACH Occasions; in the embodiment, only a 4-step RACH is configured and a 2-step RACH is not configured. However, this does not mean that a 2-step RACH is not supported in this scheme, and a scheme similar to the above can be adopted to support the Preamble configuration of a 2-step RACH.
[0101] In an embodiment, the 6th information is ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17-BWReduced, the 7th information is ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RedCap-R17-AntennaReduced, the 8th information is numberOfRA-PreamblesGroupA-RedCap-R17-BWReduced, and the 9th information is numberOfRA-PreamblesGroupA-RedCap-R17-AntennaReduced. In an embodiment, the 6th information is intended to indicate the number of 4-step PRACH Preambles of a Type 1 terminal (i.e., UE Type 1 RedCap); the 7th information is intended to indicate the number of 4-step PRACH Preambles of a Type 2 terminal (i.e., UE Type 2 RedCap);
[0102] If the RedCap UE supports Group B, the eighth information is to indicate the number of Group A PRACH Preambles of the UE Type 1 RedCap; and the ninth information is to indicate the number of Group A PRACH Preambles of the UE Type 2 RedCap.
[0103] In the description of the above embodiment, the first type communication node refers to a RedCap UE, and the second type communication node refers to an NR UE.
[0104] In one embodiment, FIG. 9 is a structural block diagram of a resource allocation device provided in an embodiment of the present application. This embodiment is executed by a fourth type communication node. Here, the fourth type communication node may be a network side (e.g., a base station). As illustrated in FIG. 9, this embodiment includes a configuration module (310) and a transmitter (320).
[0105] Here, the configuration module (310) configures a PRACH time frequency resource occupied by a physical random access channel (PRACH) random access preamble corresponding to a first type communication node;
[0106] The transmitter (320) transmits the PRACH time frequency resource to the first type communication node.
[0107] In one embodiment, the location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node is,
[0108] It includes at least one of: a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node; and a PRACH time frequency resource of a first-type communication node.
[0109] In one embodiment, where a location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type communication node includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is configured from a PRACH Preamble for non-contention-based random access (CBRA) corresponding to the second type communication node.
[0110] In one embodiment, configuring the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0111] Indicating the starting index of the PRACH Preamble corresponding to the first type communication node through the first information;
[0112] Or, the start index of the PRACH Preamble corresponding to the first type communication node is the sum of the end index of the PRACH Preamble configured for the second type communication node and K; wherein K is an integer greater than or equal to 1.
[0113] In one embodiment, the termination index of the PRACH Preamble configured for the second type communication node is,
[0114] If Type 1 PRACH is supported, it is the end index of the Type 1 PRACH Preamble;
[0115] If supporting Type 2 PRACH, it includes one of the termination index of the Type 2 PRACH Preamble.
[0116] In one embodiment, when supporting Type 1 Msg3 and Type 2 Msg3,
[0117] If Type 1 PRACH is supported, the end index of the Type 1 PRACH Preamble is the end index of the Preamble corresponding to Type 1 Msg3;
[0118] If Type 2 PRACH is supported, the end index of the Type 2 PRACH Preamble is the end index of the Preamble corresponding to Type 1 Msg3; it includes one of these.
[0119] In one embodiment, when a first type communication node configures a first type PRACH, configuring the time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0120] It further includes indicating the number of PRACH Preambles corresponding to the first type communication node through the second information.
[0121] In one embodiment, when a first type communication node configures a first type PRACH and a second type PRACH, configuring the time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0122] Indicating the number of Type 1 PRACH Preambles corresponding to the Type 1 communication node through the second information;
[0123] It further includes indicating the number of Type 2 PRACH Preambles corresponding to Type 1 communication nodes through the third information, wherein the start index of the Type 2 PRACH Preamble is the end index of the Type 1 PRACH Preamble configured for the second information plus 1.
[0124] In one embodiment, if the first type communication node supports the first type Msg3, the fourth information indicates the number of PRACH Preambles corresponding to the second type Msg3.
[0125] In one embodiment, if the first type communication node supports the first type Msg3, the number of PRACH Preambles corresponding to the second type Msg3 of the first type PRACH is indicated through the fourth information; and the number of PRACH Preambles corresponding to the second type Msg3 of the second type PRACH is indicated through the fifth information.
[0126] In one embodiment, when a first type communication node includes a first type terminal and a second type terminal, configuring the time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0127] Indicating the number of Type 1 PRACH Preambles corresponding to the Type 1 terminal through the 6th information;
[0128] Indicating the number of Type 1 PRACH Preambles corresponding to Type 2 terminals through the 7th information; includes.
[0129] In one embodiment, when a first type communication node supports a first type Msg3, the eighth information is used to indicate the number of PRACH Preambles corresponding to the second type Msg3 of the first type terminal; and the ninth information is used to indicate the number of PRACH Preambles corresponding to the second type Msg3 of the second type terminal.
[0130] In one embodiment, if the initial bandwidth (BWP) configured for the first type communication node is greater than the operating bandwidth of the first type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is used by the first type communication node.
[0131] In one embodiment, when the initial BWP configured for the first type communication node is less than or equal to the operating bandwidth of the first type communication node,
[0132] If the first type communication node is a first type communication node that supports or enables a CR function, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is used by the first type communication node;
[0133] If the first type communication node is a first type communication node that does not support or enable the CR function, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node is used by the first type communication node; one of these is included.
[0134] In one embodiment, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is,
[0135] PRACH time frequency resource of a Type 1 communication node;
[0136] A PRACH time frequency resource jointly used by a Type 3 communication node and a Type 1 communication node; comprising one of the following, wherein the Type 3 communication node is a communication node that supports or enables CE functions; and the jointly used PRACH time frequency resource is used by the Type 1 communication node and / or the Type 3 communication node to transmit a PRACH Preamble.
[0137] In one embodiment, if the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the Msg3 message carries instruction information of the communication node, and the instruction information of the communication node indicates that the communication node is the first type communication node or the third type communication node.
[0138] In one embodiment, if the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the size of the frequency domain resource occupied by the Msg3 message is less than or equal to the operating bandwidth of the first type communication node.
[0139] In one embodiment, signaling indicates the usage status of a first type communication node for a PRACH Preamble among PRACH time frequency resources corresponding to a second type communication node;
[0140] When signaling indicates that a Type 1 communication node uses a PRACH Preamble among the PRACH time frequency resources corresponding to a Type 2 communication node,
[0141] If the first type communication node supports or enables CR, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is used by the first type communication node;
[0142] If the first type communication node does not support or enable CR, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node is used by the first type communication node; comprising at least one of the above,
[0143] If the signaling indicates that the Type 1 communication node does not use the PRACH Preamble among the PRACH time frequency resources corresponding to the Type 2 communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the Type 1 communication node is used by the Type 1 communication node.
[0144] The resource allocation device provided in this embodiment is configured to implement the resource allocation method of the embodiment shown in FIG. 4, and since the implementation principle and technical effect of the resource allocation device provided in this embodiment are similar, they are not described further here.
[0145] In one embodiment, FIG. 10 is a structural block diagram of a resource selection device provided in an embodiment of the present application. This embodiment is executed by a first type of communication node. Here, the first type of communication node may be a terminal side. In an embodiment, the first type of communication node is a RedCap UE. As illustrated in FIG. 10, this embodiment includes a receiver (410) and a selector (420).
[0146] Here, the receiver (410) receives a PRACH time frequency resource transmitted by a fourth type communication node.
[0147] The selector (420) selects a PRACH time frequency resource occupied by the PRACH Preamble from the above PRACH time frequency resource.
[0148] In one embodiment, the location where the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is located is,
[0149] It includes at least one of: a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second-type communication node; and a PRACH time frequency resource of a first-type communication node.
[0150] In one embodiment, where the location having a PRACH time frequency resource occupied by a PRACH Preamble selected by the first type communication node includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to the second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node is composed of a PRACH Preamble for a non-CBRA corresponding to the second type communication node.
[0151] In one embodiment, if the initial BWP configured for the first type communication node is greater than the operating bandwidth of the first type communication node, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node.
[0152] In one embodiment, when the initial BWP configured for the first type communication node is smaller than or equal to the operating bandwidth of the first type communication node,
[0153] If the above-mentioned first-type communication node is a first-type communication node that supports or enables a CR function, the PRACH time frequency resource occupied by the PRACH Preamble selected by the above-mentioned first-type communication node is the PRACH time frequency resource of the above-mentioned first-type communication node;
[0154] If the first type communication node is a first type communication node that does not support or enable the CR function, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is a PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; it includes one of these.
[0155] In one embodiment, signaling indicates the usage status of the first type communication node for the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node;
[0156] If the above signaling indicates that the first type communication node uses the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node,
[0157] When the above-mentioned first-type communication node supports or enables CR, the PRACH time frequency resource occupied by the PRACH Preamble selected by the above-mentioned first-type communication node is the PRACH time frequency resource of the first-type communication node;
[0158] If the first type communication node does not support or enable CR, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node; comprising at least one of these.
[0159] If the above signaling indicates that the first type communication node does not use the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node, the PRACH time frequency resource occupied by the PRACH Preamble selected by the first type communication node is the PRACH time frequency resource of the first type communication node.
[0160] The resource selection device provided in this embodiment is configured to implement the resource selection method of the embodiment shown in FIG. 5, and since the implementation principle and technical effect of the resource selection device provided in this embodiment are similar, they are not described further here.
[0161] FIG. 11 is a schematic diagram of the structure of a communication facility provided in an embodiment of the present application. As illustrated in FIG. 11, the communication facility provided in the present application includes a processor (510), a memory (520), and a communication module (530). The number of processors (510) in the facility may be one or more, and FIG. 11 provides an example of a case where there is one processor (510). The number of memories (520) in the facility may be one or more, and FIG. 11 provides an example of a case where there is one memory (520). The processor (510), memory (520), and communication module (530) of the facility may be connected via a bus or other means, and FIG. 11 provides an example of a case where they are connected via a bus. In the above embodiment, the facility may be a network side (e.g., a base station).
[0162] Memory (520) is a computer-readable storage medium and can store software programs, computer-executable programs and modules, for example, program instructions / modules corresponding to the facility according to any embodiment of the present application (e.g., configuration modules of a resource allocation device and a transmitter). Memory (520) may include a program storage area and a data storage area, wherein the program storage area may store applications required for at least one function of the operating system; and the data storage area may store data generated as a result of using the facility. Additionally, memory (520) may include high-speed random access memory and may include non-volatile memory, for example, at least one magnetic disk memory element, a flash memory element, or other non-volatile solid-state memory element. In some examples, memory (520) may include memory installed remotely to the processor (510), such remote memory may be connected to the facility via a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile network, and combinations thereof.
[0163] The communication module (530) is configured to perform communication interactions between a first type communication node, a second type communication node, and other communication nodes. For example, other communication nodes may be a third communication node and / or a fourth communication node.
[0164] In the case where the communication facility is a Type 4 communication node, the provided facility is configured to perform the resource allocation method provided in any of the above embodiments and has corresponding functions and effects.
[0165] When the communication facility is a first-type communication node, the provided facility is configured to perform the resource selection method provided in any of the above embodiments and has corresponding functions and effects.
[0166] An embodiment of the present application further provides a storage medium comprising computer-executable instructions, and when the computer-executable instructions are executed by a computer processor, a resource allocation method applied to a fourth type of communication node is performed. The method comprises: configuring a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a first type of communication node; and transmitting the PRACH time frequency resource to the first type of communication node.
[0167] Embodiments of the present application further provide a storage medium comprising computer-executable instructions, and when the computer-executable instructions are executed by a computer processor, a resource selection method applied to a first type of communication node is performed. The method comprises: receiving a PRACH time frequency resource transmitted by a fourth type of communication node; and selecting a PRACH time frequency resource occupied by a PRACH Preamble from the PRACH time frequency resource. The storage medium comprising computer-executable instructions may be a non-transient computer-readable storage medium.
[0168] Those skilled in the art will understand that the term "user equipment" includes any suitable type of wireless user equipment, e.g., mobile phones, portable data processing devices, portable web browsers, or vehicle mobile terminals.
[0169] Generally, a plurality of embodiments of the present application may be implemented through hardware or dedicated circuits, software, logic, or any combination thereof. For example, in some forms, they may be implemented in hardware, and in other forms, they may be implemented in firmware or software executed by a controller, microprocessor, or other computing device, but the present application is not limited thereto.
[0170] Embodiments of the present application are implemented by a data processor of a mobile device executing computer program instructions, for example, through a processor entity or hardware or a combination of software and hardware. Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or target code written in any combination of one or more programming languages.
[0171] A block diagram of any logic flow in the drawings of the present application may indicate program steps, may indicate interconnected logic circuits, modules, and functions, or may indicate a combination of program steps and logic circuits, modules, and functions. A computer program may be stored in memory. Memory may be of any type suitable for the local technical environment and may be implemented by any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)). A computer-readable medium may include a non-transient storage medium. The data processor may be any type suitable for the local technology environment, and is, for example, but not limited to, general-purpose computers, dedicated computers, microprocessors, digital signal processing (DSP), application-specific integrated circuits (ASICs), field-programmable gate arrays (FGPAs), and processors based on multi-core processor architectures.
[0172] The foregoing describes preferred embodiments of the present application and is not intended to limit the application. Those skilled in the art may make various changes and variations to the present application. All modifications, equivalent substitutions, and improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.
Claims
Claim 1 A resource allocation method applied to a Type 4 communication node, comprising: a step of configuring a PRACH time frequency resource occupied by a physical random access channel (PRACH) random access preamble corresponding to a Type 1 communication node—wherein the PRACH time frequency resource occupied by the PRACH preamble corresponding to the Type 1 communication node includes at least one of a PRACH time frequency resource occupied by a PRACH preamble corresponding to a Type 2 communication node; and a PRACH time frequency resource jointly used by a Type 3 communication node and the Type 1 communication node—; and a step of transmitting the PRACH time frequency resource to the Type 1 communication node; characterized by comprising: a resource allocation method. Claim 2 In claim 1, where the location having a PRACH time frequency resource occupied by a PRACH Preamble corresponding to the first type of communication node includes a PRACH time frequency resource occupied by a PRACH Preamble corresponding to the second type of communication node, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type of communication node is a resource allocation method configured from a PRACH Preamble for non-contention-based random access (CFRA) corresponding to the second type of communication node. Claim 3 In claim 1, the step of configuring a PRACH time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node comprises: indicating a start index of the PRACH Preamble corresponding to the first type communication node through first information; or making the start index of the PRACH Preamble corresponding to the first type communication node the sum of the end index of the PRACH Preamble configured for the second type communication node and K; wherein K is an integer greater than or equal to 1, and the end index of the PRACH Preamble configured for the second type communication node comprises: when the PRACH supports the first type PRACH, the end index of the PRACH Preamble configured for the second type communication node is the end index of the first type PRACH Preamble; and when the PRACH supports the second type PRACH, the end index of the PRACH Preamble configured for the second type communication node is the end index of the second type PRACH Preamble. A resource allocation method comprising one of the following: when the first type communication node supports the first type Msg3, when the PRACH supports the first type PRACH, the end index of the first type PRACH Preamble is the end index of the Preamble corresponding to the first type Msg3; when the PRACH supports the second type PRACH, the end index of the second type PRACH Preamble is the end index of the Preamble corresponding to the first type Msg3. Claim 4 A resource allocation method according to claim 1, wherein when the first type communication node configures the first type PRACH, the step of configuring the time frequency resources occupied by the PRACH Preamble corresponding to the first type communication node further comprises indicating the number of PRACH Preambles corresponding to the first type communication node through second information, and when the first type communication node supports the first type Msg3, indicating the number of PRACH Preambles corresponding to the second type Msg3 through fourth information. Claim 5 A resource allocation method according to claim 1, wherein when a first type communication node configures a first type PRACH and a second type PRACH, the step of configuring a time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node comprises: indicating the number of first type PRACH Preambles corresponding to the first type communication node through second information; and indicating the number of second type PRACH Preambles corresponding to the first type communication node through third information; wherein, the start index of the second type PRACH Preamble is the sum of the end index of the first type PRACH Preamble configured for the second information and 1; and when the first type communication node supports a first type Msg3, indicating the number of PRACH Preambles corresponding to the second type Msg3 of the first type PRACH through fourth information; and indicating the number of PRACH Preambles corresponding to the second type Msg3 of the second type PRACH through fifth information. Claim 6 A resource allocation method according to claim 1, wherein, when the first type communication node includes a first type terminal and a second type terminal, the step of configuring a time frequency resource occupied by a PRACH Preamble corresponding to the first type communication node comprises: indicating the number of first type PRACH Preambles corresponding to the first type terminal through sixth information; indicating the number of first type PRACH Preambles corresponding to the second type terminal through seventh information; and, when the first type communication node supports a first type Msg3, indicating the number of PRACH Preambles corresponding to the second type Msg3 of the first type terminal using eighth information; and indicating the number of PRACH Preambles corresponding to the second type Msg3 of the second type terminal using ninth information. Claim 7 In claim 1, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node, and the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node further includes the PRACH time frequency resource of the first type communication node; and when the initial bandwidth (BWP) configured for the first type communication node is greater than the operating bandwidth of the first type communication node, the PRACH time frequency resource of the first type communication node is a resource allocation method used by the first type communication node. Claim 8 In claim 1, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node, and the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node further includes the PRACH time frequency resource of the first type communication node; wherein, when the initial BWP configured for the first type communication node is less than or equal to the operating bandwidth of the first type communication node, if the first type communication node is a first type communication node that supports or enables a coverage recovery (CR) function, the PRACH time frequency resource of the first type communication node is used by the first type communication node; and if the first type communication node is a first type communication node that does not support or enable a CR function, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node is used by the first type communication node. A resource allocation method including one of the following. Claim 9 In claim 1, the third type communication node is a communication node that supports or enables coverage enhancement (CE) functions; and the jointly used PRACH time frequency resource is a resource allocation method used by at least one of the first type communication node and the third type communication node to transmit a PRACH Preamble. Claim 10 In claim 9, a resource allocation method in which, when the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the method carries instruction information of the communication node through a Msg3 message, and the instruction information of the communication node indicates that the communication node is a first type communication node or a third type communication node. Claim 11 In claim 9, a resource allocation method in which, when the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes a PRACH time frequency resource jointly used by the third type communication node and the first type communication node, the size of the frequency domain resource occupied by the Msg3 message is smaller than or equal to the operating bandwidth of the first type communication node. Claim 12 In claim 1, the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node includes the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the second type communication node, and the PRACH time frequency resource occupied by the PRACH Preamble corresponding to the first type communication node further includes the PRACH time frequency resource of the first type communication node; signaling indicates the usage status of the first type communication node regarding the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node; when the signaling indicates that the first type communication node uses the PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node, if the first type communication node supports or enables CR, the PRACH time frequency resource of the first type communication node is used by the first type communication node; if the first type communication node does not support or enable CR, the A resource allocation method comprising at least one of the following: a PRACH time frequency resource occupied by a PRACH Preamble corresponding to a second type communication node that is used by the first type communication node; wherein, when the signaling indicates that the first type communication node does not use a PRACH Preamble among the PRACH time frequency resources corresponding to the second type communication node, the PRACH time frequency resource of the first type communication node is used by the first type communication node. Claim 13 A resource selection method applied to a first type communication node, comprising: receiving a physical random access channel (PRACH) time frequency resource transmitted by a fourth type communication node—wherein the PRACH time frequency resource is occupied by a PRACH preamble corresponding to the first type communication node and configured by the fourth type communication node, and the PRACH time frequency resource occupied by the PRACH preamble corresponding to the first type communication node includes a PRACH time frequency resource occupied by a PRACH preamble corresponding to the second type communication node; and at least one of a PRACH time frequency resource jointly used by a third type communication node and the first type communication node—; and selecting a PRACH time frequency resource occupied by the PRACH preamble from the PRACH time frequency resource. Claim 14 A communication facility comprising a communication module, a memory, and one or more processors; wherein the communication module is configured to perform communication interactions between a first type communication node, a second type communication node, and other communication nodes; wherein the memory is configured to store one or more programs; and wherein, when the one or more programs are executed by the one or more processors, the one or more processors enable the implementation of a method according to any one of claims 1 to 13. Claim 15 A storage medium in which a computer program is stored, wherein the storage medium implements a method according to any one of claims 1 to 13 when the computer program is executed by a processor. Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete
