Resource configuration method and apparatus, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a resource configuration method and apparatus, and a terminal and a network-side device. The resource configuration method in the embodiments of the present application comprises: a terminal receiving first configuration information sent by a network-side device; and on the basis of the first configuration information, the terminal determining a sub-band in an enhanced duplex mode, wherein the first configuration information comprises at least one of the following: the period of the enhanced duplex mode; the width of the sub-band; a starting frequency domain position of the sub-band; the sizes of guard bands between the sub-band and other bandwidths, the other bandwidths being bandwidths other than the sub-band among bandwidths configured in the enhanced duplex mode; the attribute of the sub-band, the attribute being related to a transmission direction; and a slot mode of the sub-band configured within the period of the enhanced duplex mode.

Description

Resource allocation methods, devices, terminals and network-side equipment

[0001] Cross-references to related applications

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

[0003] This application belongs to the field of communication technology, specifically relating to a resource allocation method, apparatus, terminal, and network-side equipment. Background Technology

[0004] In mobile communication systems, to adapt to diverse scenarios and service requirements, full-duplex enhancement technologies have been implemented. In New Radio (NR) systems, configuring full-duplex operation can significantly improve the latency and coverage performance of Time Division Duplex (TDD) systems. Currently, enhanced duplex mode primarily considers connected terminals and a mode where the network supports full-duplex and the terminal supports half-duplex. Resource configuration for terminals in other states under enhanced duplex mode is unclear, impacting the transmission performance of these terminals.

[0005] Summary of the Invention

[0006] This application provides a resource allocation method, apparatus, terminal, and network-side device, which can solve the problem of unclear resource allocation of terminals in enhanced duplex mode in related technologies.

[0007] Firstly, a resource allocation method is provided, executed by the terminal, including:

[0008] The terminal receives the first configuration information sent by the network-side device;

[0009] The terminal determines the subband in enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following:

[0010] The period of the enhanced duplex mode;

[0011] The width of the sub-band;

[0012] The starting frequency domain position of the sub-band;

[0013] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0014] The subband has attributes that are related to the transmission direction;

[0015] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0016] Secondly, a resource allocation method is provided, executed by a network-side device, including:

[0017] The network-side device sends first configuration information to the terminal. The first configuration information is used to determine the subband in the enhanced duplex mode, wherein the first configuration information includes at least one of the following:

[0018] The period of the enhanced duplex mode;

[0019] The width of the sub-band;

[0020] The starting frequency domain position of the sub-band;

[0021] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0022] The subband has attributes that are related to the transmission direction;

[0023] The enhanced duplex mode is configured with a time slot pattern for the sub-band within its cycle.

[0024] Thirdly, a resource allocation device is provided, comprising:

[0025] The receiving module is used to receive the first configuration information sent by the network-side device;

[0026] The determining module is configured to determine the sub-band in enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following:

[0027] The period of the enhanced duplex mode;

[0028] The width of the sub-band;

[0029] The starting frequency domain position of the sub-band;

[0030] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0031] The subband has attributes that are related to the transmission direction;

[0032] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0033] Fourthly, a resource allocation device is provided, comprising:

[0034] The sending module is configured to send first configuration information to the terminal, the first configuration information being used to determine subbands in enhanced duplex mode, wherein the first configuration information includes at least one of the following:

[0035] The period of the enhanced duplex mode;

[0036] The width of the sub-band;

[0037] The starting frequency domain position of the sub-band;

[0038] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0039] The subband has attributes that are related to the transmission direction;

[0040] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0041] Fifthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0042] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive first configuration information sent by a network-side device, and the processor is configured to determine a subband in an enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following: the period of the enhanced duplex mode; the width of the subband; the starting frequency domain position of the subband; the guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband; the attributes of the subband, the attributes being related to the transmission direction; and the time slot mode of the subband configured within the period of the enhanced duplex mode.

[0043] In a seventh aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0044] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first configuration information to a terminal, the first configuration information being used to determine a subband in an enhanced duplex mode, wherein the first configuration information includes at least one of the following: the period of the enhanced duplex mode; the width of the subband; the starting frequency domain position of the subband; the guard band size between the subband and other bandwidths, the other bandwidths being the bandwidths configured in the enhanced duplex mode excluding the subband; the attributes of the subband, the attributes being related to the transmission direction; and the time slot mode of the subband configured within the period of the enhanced duplex mode.

[0045] A ninth aspect provides a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0046] In a tenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second aspect.

[0047] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0049] In this embodiment of the application, the network-side device sends first configuration information, and the terminal can determine the sub-band in the enhanced duplex mode according to the first configuration information. This defines how to configure the frequency domain resources on the terminal side in the enhanced duplex mode, so that the terminal can flexibly use the duplex mode and effectively improve the transmission flexibility and transmission performance of the terminal. Attached Figure Description

[0050] Figure 1a is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0051] Figure 1b is one of the schematic diagrams of an SSB mapping to RO that can be applied to an embodiment of this application;

[0052] Figure 1c is a second schematic diagram of an SSB mapping to RO that can be applied to an embodiment of this application;

[0053] Figure 1d is one of the schematic diagrams of determining RO groups applicable to the embodiments of this application;

[0054] Figure 1e is a second schematic diagram of a method for determining RO groups that can be applied to an embodiment of this application;

[0055] Figure 1f is a schematic diagram of one of the full-duplex scenarios that can be applied to the embodiments of this application;

[0056] Figure 1g is a second schematic diagram of a full-duplex scenario applicable to the embodiments of this application;

[0057] Figure 1h is one of the schematic diagrams of a transmission time slot applicable to an embodiment of this application;

[0058] Figure 1i is a second schematic diagram of a transmission time slot applicable to an embodiment of this application;

[0059] Figure 2 is a flowchart of a resource allocation method provided in an embodiment of this application;

[0060] Figure 3 is a flowchart of another resource allocation method provided in an embodiment of this application;

[0061] Figure 4 is a structural diagram of a resource allocation device provided in an embodiment of this application;

[0062] Figure 5 is a structural diagram of another resource allocation device provided in an embodiment of this application;

[0063] Figure 6 is a structural diagram of a communication device provided in an embodiment of this application;

[0064] Figure 7 is a structural diagram of a terminal provided in an embodiment of this application;

[0065] Figure 8 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0066] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0067] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0068] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

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

[0070] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The base station may be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmission Reception Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0071] Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0072] To better understand, the relevant concepts and principles that may be involved in the embodiments of this application are explained below.

[0073] Random access procedure:

[0074] In related technologies, the random access procedure can be either a contention-based random access procedure or a non-contention-based random access procedure. The random access procedure can be a four-step random access procedure (also called a Type-1 random access procedure) or a two-step random access procedure (also called a Type-2 random access procedure).

[0075] In the contention-based 4-step Random Access Channel (RACH) procedure, the User Equipment (UE) first sends Message 1 (msg1) to the network, containing a preamble. Upon detecting the preamble, the network sends Message 2 (msg2) / Random Access Response (RAR) message, containing the number of the detected preamble and the uplink radio resources allocated to the UE for sending Message 3 (msg3). Upon receiving msg2, the UE confirms that at least one of the preamble numbers carried in msg2 matches the number of its own preamble. Then, according to the resources indicated by the RAR, the UE sends msg3 containing contention resolution information. Upon receiving msg3, the network sends Message 4 (msg4) containing contention resolution information. Upon receiving msg4, the UE confirms that the resolution information matches what it sent in msg3, thus completing the 4-step random access procedure.

[0076] The network includes uplink (UL) grant information in the RAR to indicate MSG3 Physical Uplink Shared Channel (PUSCH) scheduling information, and also includes information such as the Random Access Procedure Preamble ID (RAPID), Temporary Cell Radio Network Temporary Identifier (TC-RNTI), and Timing Advance (TA). If the network does not receive the MSG3 PUSCH, it can schedule a retransmission of the MSG3 PUSCH in the Physical Downlink Control Channel (PDCCH) scrambled with TC-RNTI.

[0077] In a contention-based random access procedure, different UEs randomly select a preamble for transmission. This means different UEs might select the same preamble to send on the same time-frequency radio resource (Random Access Occasion (RO) resource), a situation known as UE preamble conflict. In this case, different UEs will receive the same RAR (Range Access Registry). At this point, different UEs will transmit the MSG3 PUSCH according to the scheduling information in the RAR UL grant. Since related technologies do not support repeated transmission of MSG3 PUSCH, the network can only resolve one UE-transmitted PUSCH (containing contention resolution information) on a single MSG3 PUSCH scheduling resource. Therefore, the network will include the contention resolution information received in MSG3 in MSG4. If the contention resolution information received by the UE in MSG4 matches the contention resolution information sent by the UE in MSG3 PUSCH, the UE considers the contention resolution successful. If they do not match, the contention resolution is considered unsuccessful.

[0078] If contention resolution fails, the UE will reselect RACH transmission resources to transmit via the Physical Random Access Channel (PRACH) for the next random access attempt.

[0079] In NR Release 16 (Rel-16), a two-step random access procedure (2-step RACH) was introduced. The first step is for the UE to send message A (MsgA) to the network. Upon receiving MsgA, the network sends message B (MsgB) to the UE. If the UE does not receive MsgB within a certain time, it increments a counter counting the number of MsgA transmissions and retransmits MsgA. If the counter reaches a certain threshold, the UE switches from the 2-step random access procedure to the 4-step random access procedure. MsgA includes a MsgA preamble and a MsgA PUSCH. The preamble is sent on the Resource Object (RO) used for 2-step RACH, and the PUSCH is sent on the MsgA PUSCH resource associated with the MsgA preamble and RO. MsgA PUSCH resources are a set of PUSCH resources configured relative to each PRACH slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0080] Selection of random access resources and mapping of synchronization signal and PBCH block (SSB) to RO:

[0081] In NR, a cell can configure multiple Frequency Division Multiplex (FDM) Physical Random Access Channel (RO) transmission occasions (or PRACH Occasions) at a single PRACH transmission time domain location. For simplicity, these are referred to as ROs. At any given time, the number of ROs available for FDM can be {1, 2, 4, 8}. As shown in Figure 1b, at any given time, there are 8 RO resources distributed across different frequencies.

[0082] The random access preamble can only be transmitted on the time-domain resources (i.e., RO resources) configured by the PRACH configuration index parameter, while the random access preamble can only be transmitted on the frequency-domain resources configured by the prach-FDM parameter. The PRACH frequency-domain resource n... RA ∈{0,1,...,M-1}, where M equals the higher-layer parameter prach-FDM. At initial access, the PRACH frequency domain resources n RA The RO resources are numbered in ascending order, starting from the lowest frequency RO resource within the initial active uplink bandwidth part. Otherwise, the PRACH frequency domain resources are numbered in ascending order, starting from the lowest frequency RO resource within the active uplink bandwidth part. As shown in Figure 1b, the RO resources are numbered sequentially from low to high frequency as RO#0 to RO#7.

[0083] In NR, there is an association between the RO (Redirect Base) and the actual SSB (Secure Base Signal) being transmitted. One SSB may be associated with multiple ROs, or multiple SSBs may be associated with one RO (in which case, different SSBs correspond to different Preamble codes). Typically, the base station can use different beams to transmit different SSBs. The corresponding UE transmits a Preamble on the RO associated with the SSB. Thus, based on the strength of the received downlink beam / SSB, the UE selects the RO / "RO and Preamble combination" associated with the SSB with the best signal and transmits msg1. In this way, the network can determine the SSB selected by the UE based on the received Preamble's RO / "RO and Preamble combination" and transmit msg2 on the downlink beam corresponding to the SSB to ensure the quality of downlink signal reception.

[0084] Taking Figure 1b as an example, the number of ROs in FDM at a given time is 8, and the number of SSBs actually transmitted is 4, namely SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with 2 ROs. If the UE determines to send PRACH / msg1 / Preamble on the RO corresponding to SSB#0, then the UE selects one RO from RO#0 and RO#1 to send PRACH.

[0085] Taking Figure 1c as an example, the number of ROs in an FDM at a given time is 2, and the number of SSBs actually transmitted is 8, namely SSB#0, SSB#1, ..., SSB#7, with each pair of SSBs associated with one RO. When multiple SSBs share a single RO, the preamble sets associated with these multiple SSBs are different; that is, the same preamble cannot simultaneously belong to different preamble sets associated with different SSBs. For example, in Figure 1c, RO#0 has 60 preambles associated with SSBs, of which preambles with indices 0 to 29 are associated with SSB#0, and preambles with indices 30 to 59 are associated with SSB#1.

[0086] Before sending PRACH, the UE first performs resource selection. First, based on the Reference Signal Received Power (RSRP) of the received beam / SSB, the UE selects an SSB with an RSRP higher than a threshold. If multiple SSBs have RSRPs higher than the threshold, the terminal can select any SSB with an RSRP higher than the threshold. If there is no SSB with an RSRP higher than the threshold, the UE selects an SSB based on implementation.

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

[0088] For example, in the example shown in Figure 1b, assuming the UE selects SSB#1, the UE can choose one of RO#2 and RO#3 to send PRACH / Preamble; in the example shown in Figure 1c, if the UE selects SSB#1, the UE can choose the RO (RO#0 or RO#4) associated with SSB#1 that is the closest available RO to the current time to send PRACH / Preamble.

[0089] Within the selected RO, the UE selects a preamble from the preamble set associated with the selected SSB for PRACH transmission. As shown in Figure 1c, if one RO is associated with two SSBs, then the available preamble set associated with each SSB in one RO will be divided into two subsets, each corresponding to one SSB. The UE will select a preamble sequence from the preamble subset corresponding to the selected SSB for PRACH transmission.

[0090] In 5G technology, the following rules are used to resolve conflicts between PRACH and other signals or TDD configurations:

[0091] If, after an integer number of SS / PBCH block (SSB) indexes are mapped to PRACH timing mapping cycles within an association period, a set of PRACH occasions or PRACH sequences is not mapped to an SS / PBCH block index (SSB index), then no SS / PBCH block index is mapped to a PRACH occasion or PRACH sequence. These PRACH resources will not be available for PRACH transmission.

[0092] The associated pattern period consists of one or more associated periods and is determined such that the pattern between PRACH occasions and SS / PBCH block indexes repeats at most once every 160 milliseconds. PRACH occasions (if any) not associated with SS / PBCH block indexes after an integer number of associated periods are not used for PRACH transmission.

[0093] A MsgA PUSCH occasion is valid if it does not overlap in time and frequency with any valid PRACH occasions associated with Type I or Type II random access procedures. This means that when PRACH and MsgA PUSCH resources overlap, PRACH is transmitted instead of MsgA PUSCH.

[0094] For operation on a single carrier in an unpaired spectrum (Time Division Duplex, TDD), if the UE is configured by a higher layer to receive PDCCH, Physical downlink shared channel (PDSCH), Channel State Information Reference Signal (CSI-RS), or Downlink Positioning Reference Signal (DL-PRS) in a set of symbols within a slot, then if the UE does not detect a Downlink Control Information (DCI) format in at least one symbol in this set of symbols that instructs the UE to transmit PUSCH, Physical Uplink Control Channel (PUCCH), PRACH, or Sounding Reference Signal (SRS), the UE will receive PDCCH, PDSCH, CSI-RS, or DL-PRS; otherwise, the UE will not receive PDCCH, PDSCH, CSI-RS, or DL-PRS.

[0095] For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH in a set of symbols within a time slot, and the UE detects a DCI format instructing the UE to receive CSI-RS or PDSCH from a subset of that set of symbols, then:

[0096] If the UE does not have the capability for partial cancellation, then if the time interval between the first symbol in the set (a set of symbols for transmitting SRS, PUCCH, PUSCH, or PRACH) and the last symbol in the DCI-formatted control resource set (CORESET) detected by the UE does not exceed T... proc,2 If the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in that set, then the UE will cancel the PRACH transmission, or decide to cancel the actual duplicate transmission of PUCCH, PUSCH, or PUSCH according to the relevant protocol.

[0097] If the UE has the capability of partial cancellation, then if the time interval between a portion of the symbols in the set (a set of symbols transmitting SRS, PUCCH, PUSCH, or PRACH) and the last symbol of the DCI format CORESET detected by the UE does not exceed T... proc,2 If the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH on this part of the symbols, the UE cancels the PRACH transmission or, according to the relevant protocol, cancels the actual duplicate transmission of PUCCH, PUSCH, or PUSCH.

[0098] PRACH repeat:

[0099] In 3GPP NR Rel-18, PRACH repetition was introduced. For PRACH repetition, the UE needs to repeatedly transmit the preamble on multiple Returnable Arrays (ROs) at different time-domain locations associated with the same Service SSB. The number of PRACH repetitions can be {2, 4, 8}. After determining the number of PRACH repetitions, the UE needs to determine the RO set, where the number of valid ROs equals the number of PRACH repetitions.

[0100] Assuming the PRACH repetition count is N1, the overall determination rule for RO groups within the time window X is as follows: First, determine the starting RO of the first RO group, then determine the remaining N-1 ROs of the first RO group. Then, determine the starting ROs and their remaining ROs for the other RO groups sequentially. The remaining N1-1 ROs of each RO group are those associated with the starting RO, belonging to the same SSB, at the same frequency location, and sharing the same Preamble set. After the first RO group is determined, the determination of the remaining RO groups depends on whether a time offset is configured.

[0101] If no time offset is configured, for each SSB, the first valid RO within the time window X is used as the starting RO of the first RO group, and the first RO group is determined based on the starting RO. Then, for the other ROs excluding the previous RO group, the starting ROs of subsequent RO groups are determined within the time window X in ascending order of frequency domain position followed by time domain position, and the subsequent RO groups are further determined. For example, in Figure 1d, assuming the PRACH repetition count is 2, for SSB#0, the RO group can be determined as shown in Figure 1d.

[0102] If a time offset is configured, for each SSB, the first valid RO found within the time window X in the order of frequency domain first, then time domain is used as the starting RO of the first RO group. Then, the first RO group is determined based on the starting RO. Next, the starting ROs of subsequent RO groups are determined on the remaining ROs (excluding the previous RO group) in the order of frequency domain first, then time domain. For the same SSB, the starting RO of the nth RO group at the same frequency position is the RO that is time offset from the starting RO of the (n-1)th RO group at that frequency position. The time offset is defined as the number of valid ROs associated with the same SSB in the time domain. For example, in Figure 1e below, assuming the PRACH repetition count is 2 and the time offset = 3, for SSB#0, the RO groups can be determined as shown in Figure 1e.

[0103] Enhanced duplex mode:

[0104] In 5G mobile communication systems, enhancement technologies have been implemented to adapt to diverse scenarios and service requirements for full-duplex communication. Key 5G scenarios include Enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communications (URLLC), and Massive Machine-Type Communication (mMTC). These scenarios place demands on the system to achieve high reliability, low latency, high bandwidth, and wide coverage.

[0105] In NR, configuring full-duplex operation can significantly improve the latency and coverage performance of TDD systems.

[0106] Subbands non-overlapping full duplex: can improve transmission delay and enhance coverage.

[0107] For a DL slot (configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), the network configures the DL bandwidth part (BWP) for the UE. For a UL slot, the network configures the UL BWP for the UE.

[0108] For the full duplex scenario, as shown in Figure 1f, the following cases are possible:

[0109] Case 1: Configure DL BWP for slot 1;

[0110] Case 2: Configure DL BWP and UL subband (slot 2).

[0111] For a UL slot (configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), as shown in Figure 1g, the following cases are possible:

[0112] Case 3: Configure UL BWP with time slot 4;

[0113] Case 2: Configure UL BWP and DL subband, i.e., 5 slots.

[0114] For Subband non-overlapping Full Duplex (SBFD) operation, an SBFD subband consists of one Resource Block (RB) or a continuous set of RBs with the same transmission direction.

[0115] The time unit (e.g., slot or symbol) used by the base station (the next generation Node B, gNB) for SBFD operation can be referred to as the SBFD time unit (e.g., slot or symbol).

[0116] Please refer to Figure 1h. For Rel-15, the base station and UE can only transmit or receive at any given time.

[0117] For Rel-18 gNB side full duplex, gNB can transmit and receive simultaneously, while UE side can only use half duplex mode, that is, can only transmit or receive at a time.

[0118] For full-duplex on the UE side, the gNB and UE can send and receive simultaneously.

[0119] For full-duplex UE-side applications, a larger guard band (GB) (greater than the GB of the base station FD) may be required to suppress self-interference, as shown in Figure 1i.

[0120] For a communication device, simultaneous UL reception and DL transmission can cause self-interference. To ensure transmission in the direction of interference, the communication device needs to have self-interference cancellation capabilities, such as reserving a guard band between the receive and transmit bands. However, this will reduce the throughput of the UE.

[0121] Current duplex enhancements primarily consider connected UEs, with the network side supporting full-duplex and the UE side supporting half-duplex.

[0122] To improve the flexibility of UE duplex mode usage in idle and inactive states, enhanced duplex mode can be configured in the UE's idle / inactive state or dynamically configured during the random access phase. This requires considering how to configure an enhanced duplex mode suitable for the cell level, whether PRACH transmission can be performed on the newly configured subband, and how to configure the various PRACH resource types introduced as a result. Additionally, it's necessary to consider how to determine the RO group for repeated PRACH transmissions, etc.

[0123] The resource configuration method, apparatus, and related equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0124] Please refer to Figure 2, which is a flowchart of a resource configuration method provided in an embodiment of this application. The method is applied to a terminal. As shown in Figure 2, the method includes the following steps:

[0125] Step 201: The terminal receives the first configuration information sent by the network-side device.

[0126] The first configuration information is used to determine the subband in the enhanced duplex mode. In this embodiment, the enhanced duplex mode may be SBFD mode, or a mode in which the network side supports full duplex and the UE side supports half duplex, or other duplex modes that are different from Time Division Duplex (TDD) or Frequency Division Duplex (FDD).

[0127] Step 202: The terminal determines the subband in the enhanced duplex mode based on the first configuration information.

[0128] The first configuration information includes at least one of the following:

[0129] The period of the enhanced duplex mode;

[0130] The width of the sub-band;

[0131] The starting frequency domain position of the sub-band, for example, the starting physical resource block (PRB);

[0132] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0133] The attributes of the subband are related to the transmission direction, such as being a downlink subband of an uplink time slot or an uplink subband of a downlink time slot.

[0134] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0135] For example, the network-side device may configure the starting frequency domain position of the sub-band in the enhanced duplex mode through the first configuration information, so that the terminal can determine the sub-band in the enhanced duplex mode based on the first configuration information; or, the first configuration information sent by the network-side device may also include the width of the sub-band, so that the terminal can determine the specific frequency domain position of the sub-band in the enhanced duplex mode based on the width of the sub-band and the starting frequency domain position of the sub-band.

[0136] Alternatively, the first configuration information may also include the period of the enhanced duplex mode and the starting frequency domain position of the sub-band. Based on the first configuration information, the terminal can determine in which time units the enhanced duplex mode is, and the frequency domain position of the sub-band in the enhanced duplex mode.

[0137] Alternatively, the first configuration information may include the starting frequency domain position of the sub-band in enhanced duplex mode and the guard band size between the sub-band and other bandwidths, so that the terminal can determine the frequency domain position of the sub-band and other bandwidths in enhanced duplex mode based on the first configuration information.

[0138] For example, the first configuration information may include the time slot mode of the subbands configured within the period of the enhanced duplex mode. For instance, the network-side device can configure a certain mode or indicate a mode from a set of time slot modes specified by the network-side device to determine which time slots within the period of the enhanced duplex mode will be configured with corresponding subbands. Thus, the terminal can determine the subbands in the enhanced duplex mode based on the first configuration information. Alternatively, the time slots of the subbands in the enhanced duplex mode configured by the first configuration information may be all downlink time slots or all uplink time slots, or a subset of uplink time slots or a subset of downlink time slots may be determined according to a certain mode.

[0139] It is understood that the specific information content included in the first configuration information may also be other possible situations, which will not be listed in detail in the embodiments of this application.

[0140] In this embodiment of the application, the network-side device sends the aforementioned first configuration information, thereby enabling the terminal to determine the sub-band in the enhanced duplex mode based on the first configuration information. This defines how to configure the frequency domain resources on the terminal side in the enhanced duplex mode, allowing the terminal to flexibly use the duplex mode and effectively improve the terminal's transmission flexibility and transmission performance.

[0141] It should be noted that the embodiments of this application do not limit the state of the terminal. For example, the terminal can be a terminal in all states, including a connected UE, an idle UE, an inactive UE, etc. For example, the network-side device can broadcast the first configuration information, and then the terminals that receive the first configuration information can determine the sub-band in the enhanced duplex mode based on the first configuration information, effectively improving the transmission performance of the terminal.

[0142] Alternatively, in this embodiment, the terminal is in an idle or inactive state, allowing the idle or inactive terminal to determine the subband in the enhanced duplex mode based on the first configuration information. This enables the enhanced duplex mode to be configured even when the terminal is in an idle or inactive state, allowing the terminal to flexibly use the duplex mode in these states and improving the transmission performance of the idle or inactive terminal.

[0143] Optionally, if the first configuration information includes the guard band size between the sub-band and other bandwidths, the terminal satisfies any one of the following:

[0144] The terminal is in SBFD mode;

[0145] The terminal is in half-duplex (HD) mode.

[0146] It should be noted that for network-side (gNB) SBFD time slots, the guard band size between the subband and other bandwidths configured by the network-side device may be different when the terminal performs SBFD and when the terminal performs HD. In this case, it can be configured separately for these two modes.

[0147] Optionally, the first configuration information is sent via at least one of the following:

[0148] System messages, for example, could be additional system message fields introduced in System Information Block (SIB) 1 to indicate the first configuration information;

[0149] Terminal-specific messages;

[0150] Physical Downlink Control Channel (PDCCH);

[0151] Physical Random Access Channel (PRACH) configuration;

[0152] A dedicated configuration table is used to specify the first configuration information. The dedicated configuration table may be a network-side device configuration or a protocol definition.

[0153] For example, the first configuration information can be sent via a terminal-dedicated message. For instance, for an inactive terminal, after the terminal enters Radio Resource Control (RRC) release mode, the first configuration information can be configured in the RRC release message to schedule some channels on subbands with additional enhanced duplex mode configuration, reducing transmission latency. As another example, during a higher-layer triggered Contention-Free Random Access (CFRA) process, the first configuration information can be configured in the corresponding higher-layer signaling to place some signal transmissions on subbands with additional enhanced duplex mode configuration, reducing latency; the higher-layer signaling can be a handover command, Beam Failure Recovery (BFR) configuration, etc.

[0154] Alternatively, the first configuration information can also be sent via PDCCH. For example, during the PDCCH command (ordered) CFRA process, the first configuration information can be sent via the corresponding PDCCH command.

[0155] Alternatively, the first configuration information can also be transmitted through PRACH configuration. For example, the uplink subband in the downlink time slot is determined by the RO appearing in the downlink time slot, which serves as the subband in the enhanced duplex mode; or, for example, the PRB occupied by the corresponding RO on all downlink time slots that appear in the RO configuration is considered to be configured as an uplink subband, and the RO is considered to be valid.

[0156] Optionally, the PRACH configuration includes a PRACH configuration table, which includes the first configuration information. For example, a column of information can be added to the PRACH configuration table to indicate which time slots will have the configuration of the subband in the enhanced duplex mode, the size of the subband, and its frequency domain position, etc. This column of information added to the PRACH configuration table is also the first configuration information.

[0157] In this embodiment of the application, the first configuration information may include the guard band size between the sub-band and other bandwidths in the enhanced duplex mode. Optionally, the guard band between the sub-band and other bandwidths is determined based on at least one of the following:

[0158] The protective band configured in the PRACH configuration table;

[0159] At least one RO.

[0160] In other words, the guard band between the subband and other bandwidths can be configured in the PRACH configuration table, or at least one RO can be used as the guard band between the subband and other bandwidths.

[0161] Optionally, the at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

[0162] Optionally, when the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following:

[0163] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission;

[0164] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition;

[0165] The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

[0166] Optionally, the first condition includes at least one of the following:

[0167] Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value. For example, if the time interval or frequency domain interval between RO and SSB is less than or equal to the preset value, then RO is used for actual PRACH transmission.

[0168] Whether there is an SSB or other downlink common channel or signal being transmitted on the other bandwidths. For example, if there is an SSB or other downlink common channel or signal being transmitted on the other bandwidths, then the RO is used for actual PRACH transmission.

[0169] Whether the terminal receives SSB or other downlink common channels or signals on the other bandwidth. For example, if the terminal receives SSB or other downlink common channels or signals on the other bandwidth, then the RO is used for actual PRACH transmission.

[0170] It should be noted that SSB and SS / PBCH block can be used interchangeably, and SSB can also be any signal module that contains at least a synchronization signal and / or a downlink broadcast channel.

[0171] In this embodiment of the application, the method may further include:

[0172] The terminal receives second configuration information sent by the network-side device. The second configuration information is used to configure at least one RO type, and the at least one RO type includes at least one of the following:

[0173] RO exists in the uplink time slot;

[0174] ROs exist on time slots with flexible symbols;

[0175] RO exists in the uplink subband of the downlink time slot;

[0176] There is no RO on the uplink subband of the downlink time slot.

[0177] In this embodiment, the network-side device configures at least one RO type using second configuration information, thereby enabling the terminal to determine at least one RO type in enhanced duplex mode based on the second configuration information. The solution provided in this embodiment defines and clarifies the configuration method of RO resources in enhanced duplex mode, which helps to improve the transmission performance of the terminal.

[0178] Optionally, in the case where the at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no SSB on the downlink time slot, or there is an SSB on the downlink time slot.

[0179] Optionally, the at least one RO type can be configured via any of the following:

[0180] Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources;

[0181] A public PRACH configuration resource, through which different RO types are configured.

[0182] For example, one or more RO types can be configured using independent PRACH configuration resources. For instance, PRACH resources on the uplink subband can be configured using PRACH configuration resource 1; and PRACH resources not on the uplink subband can be configured using PRACH configuration resource 2.

[0183] Alternatively, one or more RO types can be configured through a common PRACH configuration resource. For example, two different types of ROs can be configured using the same PRACH configuration resource (i.e., a common PRACH configuration resource): PRACH resources on the uplink subband and PRACH resources not on the uplink subband.

[0184] In this embodiment, two configuration methods for the RO type are effectively defined, making the configuration of the RO type more flexible.

[0185] Optionally, in the case of PRACH repetition, the method further includes:

[0186] The terminal determines an RO group from the at least one RO type based on the second configuration information to determine resources for at least one PRACH transmission; wherein the determination of the RO group satisfies at least one of the following:

[0187] The RO group includes different RO types;

[0188] The RO group includes the same RO type;

[0189] The RO types included in the RO group are mapped to the same downlink reference signal;

[0190] The RO types included in the RO group are mapped to different downlink reference signals.

[0191] Understandably, the second configuration information is used to configure at least one RO type. After receiving the second configuration information sent by the network-side device, the terminal can determine the RO group from the configured at least one RO type based on the second configuration information. The RO group may refer to a set of RO types that includes multiple RO types (which may be the same or different).

[0192] For example, the RO group determined by the terminal may include different RO types, such as ROs existing in the uplink time slot and ROs existing in the uplink subband of the downlink time slot, etc.

[0193] Alternatively, the RO groups determined by the terminal must include the same RO type. For example, both RO groups included in the RO group are ROs existing on the uplink time slot; or, for example, the terminal determines multiple RO groups, all of which include ROs existing on the uplink time slot.

[0194] Alternatively, the RO types included in the RO group determined by the terminal may be mapped to the same downlink reference signal, or they may be mapped to different downlink reference signals. For example, the RO group determined by the terminal may include ROs existing in uplink time slots and ROs existing in time slots with flexible symbols. Both of these RO types are mapped to the same downlink reference signal, or the two RO types may be mapped to different downlink reference signals. The downlink reference signal includes, but is not limited to, SSB, Channel State Information Reference Signal (CSI-RS), etc.

[0195] In this embodiment of the application, in the enhanced duplex mode, it is also necessary to define the mapping method from the reference signal to the RO.

[0196] Optionally, in the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following:

[0197] Different RO types or RO resources are individually associated with SSB;

[0198] At least two different RO types or RO resources must be associated with the SSB together;

[0199] In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

[0200] For example, different RO types or RO resources can be associated with an SSB separately, rather than simultaneously. In this case, an SSB may be associated with multiple types of ROs more quickly. For instance, some ROs may be in the subband and some may be in the normal uplink bandwidth. In this case, the ROs that are associated with the same SSB in the subband and uplink bandwidth and are closer or more compact in time can be selected to determine the PRACH transmission resources. This is beneficial for completing multiple PRACH transmissions or PRACH repetitions with low latency.

[0201] Alternatively, different RO types or RO resources can be associated with the SSB together. In other words, different RO types or RO resources can be associated with the SSB at the same time. In this case, it is not necessary to distinguish between different types of ROs to complete the association with the SSB, which can reduce the complexity of the association from SSB to RO.

[0202] Furthermore, if an RO overlaps with an SSB in the time domain, then the RO and the SSB are not associated. For example, if an RO on a certain subband has an SSB on the same Orthogonal Frequency Division Multiplexing (OFDM) symbol, the RO can be considered invalid, and the RO will not be associated with the SSB, thus reducing interference to the SSB.

[0203] In this embodiment of the application, the relationship between SSB and RO also requires the determination of various corresponding periods or windows.

[0204] Optionally, when the RO type or RO resource is associated with the SSB, for example, different RO types or RO resources are associated with the SSB individually, or different RO types or RO resources are associated with the SSB together, the method further includes:

[0205] The terminal determines a first time period or a first window, the first window including a determination window for the PRACH group, and the first time period including at least one of the following:

[0206] The SSB to RO mapping cycle;

[0207] The SSB to RO association period;

[0208] The SSB to RO association pattern period.

[0209] Optionally, the terminal may determine the first time period or the first window itself, or it may determine it based on an instruction from the network-side device. Specifically, in the case of repeated PRACH, the terminal needs to determine the determination window for the PRACH group, which is the first window.

[0210] In this embodiment of the application, under enhanced duplex mode, for SSB-RO association, the terminal can determine the SSB-RO mapping period, the SSB-RO association period, or the SSB-RO association mode period, thereby effectively determining the timing information of the SSB-RO association. This helps the terminal determine the timing of random access to the channel, thus improving the terminal's transmission performance. Furthermore, for PRACH repetition, the terminal determines the determination window for the PRACH group, which helps the terminal determine when to perform PRACH transmission, thereby improving the terminal's transmission performance.

[0211] Optionally, the first time period or the first window is determined by at least one of the following:

[0212] The first time period or first window is determined according to different RO types or RO resources;

[0213] A common first time period or first window is determined based on at least two different RO types or RO resources;

[0214] The period is determined based on the enhanced duplex mode.

[0215] For example, for different RO types or RO resources, their respective first time periods or first windows are determined. For instance, taking the first time period as an example, for an RO existing in an uplink time slot, the terminal determines its corresponding first time period (i.e., the mapping period from SSB to the RO, the association period from SSB to the RO, or the association mode period from SSB to the RO); for an RO existing in a time slot with flexible symbols, the terminal determines the first time period corresponding to that type of RO, and so on. Further examples are not provided here. This allows the terminal to flexibly determine the corresponding first time period or first window for different RO types or RO resources.

[0216] Alternatively, for different RO types or RO resources, a common first time period or first window can be defined. For example, all RO types or RO resources can correspond to the same first time period or first window. For instance, if the mapping (association) from SSB to RO is performed independently for each RO type, i.e., different RO types or RO resources are associated with the SSB individually, the maximum value of the time period determined based on all RO types can be used as the first time period, meaning that ultimately all RO types correspond to this first time period. As another example, if the mapping (association) from SSB to RO is performed together for all RO types, i.e., different RO types or RO resources are associated with the SSB together, all RO types or RO resources jointly determine a common time period or window, i.e., the first time period or first window.

[0217] Alternatively, the first time period or the first window may be determined based on the period of the enhanced duplex mode, for example, the first time period or the first window may be less than the period of the enhanced duplex mode.

[0218] In this embodiment of the application, under the enhanced duplex mode, the mapping period from SSB to RO, the association period from SSB to RO, the association mode period from SSB to RO, or the determination method of the determination window of the PRACH group are clearly defined for the association between SSB and RO. This helps to reduce the latency of random access of the terminal and improve the transmission performance of the terminal.

[0219] Please refer to Figure 3, which is a flowchart of another resource configuration method provided in an embodiment of this application. The method is applied to a network-side device. As shown in Figure 3, the method includes the following steps:

[0220] Step 301: The network-side device sends first configuration information to the terminal. The first configuration information is used to determine the subband in the enhanced duplex mode. The first configuration information includes at least one of the following:

[0221] The period of the enhanced duplex mode;

[0222] The width of the sub-band;

[0223] The starting frequency domain position of the sub-band;

[0224] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0225] The subband has attributes that are related to the transmission direction;

[0226] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0227] Optionally, if the first configuration information includes the guard band size between the sub-band and other bandwidths, the terminal satisfies any one of the following:

[0228] The terminal is in SBFD mode;

[0229] The terminal is in HD mode.

[0230] Optionally, the first configuration information is sent via at least one of the following:

[0231] System message;

[0232] Terminal-specific messages;

[0233] Physical Downlink Control Channel (PDCCH);

[0234] Physical Random Access Channel (PRACH) configuration;

[0235] A dedicated configuration table is used to specify the first configuration information.

[0236] Optionally, the PRACH configuration includes a PRACH configuration table, which includes the first configuration information.

[0237] Optionally, the guard band between the sub-band and other bandwidths is determined based on at least one of the following:

[0238] The protective band configured in the PRACH configuration table;

[0239] At least one random access channel (RO) opportunity.

[0240] Optionally, the at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

[0241] Optionally, when the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following:

[0242] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission;

[0243] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition;

[0244] The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

[0245] Optionally, the first condition includes at least one of the following:

[0246] Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value;

[0247] Are there any SSBs or other downlink common channels or signals being transmitted on the other bandwidths?

[0248] Whether the terminal receives SSB or other downlink common channels or signals on the other bandwidths.

[0249] Optionally, the method further includes:

[0250] The network-side device sends second configuration information to the terminal, the second configuration information being used to configure at least one RO type, the at least one RO type including at least one of the following:

[0251] RO exists in the uplink time slot;

[0252] RO exists in time slots with flexible symbols;

[0253] RO exists in the uplink subband of the downlink time slot;

[0254] There is no RO on the uplink subband of the downlink time slot.

[0255] Optionally, if the at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no synchronization signal block (SSB) on the downlink time slot, or there is an SSB on the downlink time slot.

[0256] Optionally, the at least one RO type can be configured via any of the following:

[0257] Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources;

[0258] A public PRACH configuration resource, through which different RO types are configured.

[0259] Optionally, in the case of PRACH repetition, the method further includes:

[0260] The network-side device determines an RO group from the at least one RO type to determine resources for at least one PRACH transmission, wherein the determination of the RO group satisfies at least one of the following:

[0261] The RO group includes different RO types;

[0262] The RO group includes the same RO type;

[0263] The RO types included in the RO group are mapped to the same downlink reference signal;

[0264] The RO types included in the RO group are mapped to different downlink reference signals.

[0265] Optionally, in the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following:

[0266] Different RO types or RO resources are individually associated with SSB;

[0267] At least two different RO types or RO resources must be associated with the SSB together;

[0268] In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

[0269] Optionally, if the RO type or RO resource is associated with an SSB, the method further includes:

[0270] The network-side device determines a first time period or a first window, the first window including a PRACH group determination window, and the first time period including at least one of the following:

[0271] The mapping period from SSB to RO;

[0272] The correlation cycle from SSB to RO;

[0273] The association pattern cycle from SSB to RO.

[0274] Optionally, the first time period or the first window is determined by at least one of the following:

[0275] The first time period or first window is determined according to different RO types or RO resources;

[0276] A common first time period or first window is determined based on at least two different RO types or RO resources;

[0277] The period is determined based on the enhanced duplex mode.

[0278] In this embodiment of the application, the network-side device sends the aforementioned first configuration information, thereby enabling the terminal to determine the sub-band in the enhanced duplex mode based on the first configuration information. This defines how to configure the frequency domain resources on the terminal side in the enhanced duplex mode, allowing the terminal to flexibly use the duplex mode and effectively improve the terminal's transmission flexibility and transmission performance.

[0279] It should be noted that the resource configuration method for network-side devices provided in this application corresponds to the method for terminal-side devices described above. The relevant concepts and specific processes involved in this application can be referred to the descriptions in the terminal-side method embodiments described above. To avoid repetition, this embodiment will not elaborate further.

[0280] The resource configuration method provided in this application can be executed by a resource configuration device. This application uses the example of a resource configuration device executing the resource configuration method to illustrate the resource configuration device provided in this application.

[0281] Please refer to Figure 4, which is a structural diagram of a resource allocation device provided in an embodiment of this application. As shown in Figure 4, the resource allocation device 400 includes:

[0282] Receiver module 401 is used to receive first configuration information sent by the network-side device;

[0283] The determining module 402 is configured to determine the sub-band in the enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following:

[0284] The period of the enhanced duplex mode;

[0285] The width of the sub-band;

[0286] The starting frequency domain position of the sub-band;

[0287] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0288] The subband has attributes that are related to the transmission direction;

[0289] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0290] Optionally, if the first configuration information includes the guard band size between the sub-band and other bandwidths, the device satisfies any one of the following:

[0291] The device is in sub-band full-duplex SBFD mode;

[0292] The device is in half-duplex HD mode.

[0293] Optionally, the first configuration information is sent via at least one of the following:

[0294] System message;

[0295] Terminal-specific messages;

[0296] Physical Downlink Control Channel (PDCCH);

[0297] Physical Random Access Channel (PRACH) configuration;

[0298] A dedicated configuration table is used to specify the first configuration information.

[0299] Optionally, the PRACH configuration includes a PRACH configuration table, which includes the first configuration information.

[0300] Optionally, the guard band between the sub-band and other bandwidths is determined based on at least one of the following:

[0301] The protective band configured in the PRACH configuration table;

[0302] At least one random access channel (RO) opportunity.

[0303] Optionally, the at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

[0304] Optionally, when the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following:

[0305] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission;

[0306] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition;

[0307] The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

[0308] Optionally, the first condition includes at least one of the following:

[0309] Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value;

[0310] Are there any SSBs or other downlink common channels or signals being transmitted on the other bandwidths?

[0311] Whether the device receives SSB or other downlink common channels or signals on the other bandwidth.

[0312] Optionally, the receiving module 401 is further configured to:

[0313] The system receives second configuration information sent by a network-side device. This second configuration information is used to configure at least one RO type, and the at least one RO type includes at least one of the following:

[0314] RO exists in the uplink time slot;

[0315] RO exists in time slots with flexible symbols;

[0316] RO exists in the uplink subband of the downlink time slot;

[0317] There is no RO on the uplink subband of the downlink time slot.

[0318] Optionally, if the at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no synchronization signal block (SSB) on the downlink time slot, or there is an SSB on the downlink time slot.

[0319] Optionally, the at least one RO type can be configured via any of the following:

[0320] Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources;

[0321] A public PRACH configuration resource, through which different RO types are configured.

[0322] Optionally, in the case of repeated PRACH, the determining module 402 is further configured to:

[0323] Based on the second configuration information, an RO group is determined from the at least one RO type to determine the resources for at least one PRACH transmission, wherein the determination of the RO group satisfies at least one of the following:

[0324] The RO group includes different RO types;

[0325] The RO group includes the same RO type;

[0326] The RO types included in the RO group are mapped to the same downlink reference signal;

[0327] The RO types included in the RO group are mapped to different downlink reference signals.

[0328] Optionally, in the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following:

[0329] Different RO types or RO resources are individually associated with SSB;

[0330] At least two different RO types or RO resources must be associated with the SSB together;

[0331] In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

[0332] Optionally, when the RO type or RO resource is associated with an SSB, the determining module 402 is further configured to:

[0333] A first time period or a first window is determined, the first window including the determination window of the PRACH group, and the first time period includes at least one of the following:

[0334] The mapping period from SSB to RO;

[0335] The correlation cycle from SSB to RO;

[0336] The association pattern cycle from SSB to RO.

[0337] Optionally, the first time period or the first window is determined by at least one of the following:

[0338] The first time period or first window is determined according to different RO types or RO resources;

[0339] A common first time period or first window is determined based on at least two different RO types or RO resources;

[0340] The period is determined based on the enhanced duplex mode.

[0341] Optionally, the device is an idle or inactive terminal.

[0342] In this embodiment, the device can determine the sub-band in the enhanced duplex mode based on the first configuration information, thereby defining how to configure the frequency domain resources in the enhanced duplex mode. This allows the device to flexibly use the duplex mode, effectively improving the transmission flexibility and performance of the device.

[0343] The resource configuration device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0344] The resource configuration device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0345] Please refer to Figure 5, which is a structural diagram of another resource allocation device provided in an embodiment of this application. As shown in Figure 5, the resource allocation device 500 includes:

[0346] The sending module 501 is configured to send first configuration information to the terminal, the first configuration information being used to determine the subband in the enhanced duplex mode, wherein the first configuration information includes at least one of the following:

[0347] The period of the enhanced duplex mode;

[0348] The width of the sub-band;

[0349] The starting frequency domain position of the sub-band;

[0350] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0351] The subband has attributes that are related to the transmission direction;

[0352] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0353] Optionally, if the first configuration information includes the guard band size between the sub-band and other bandwidths, the terminal satisfies any one of the following:

[0354] The terminal is in sub-band full-duplex SBFD mode;

[0355] The terminal is in half-duplex HD mode.

[0356] Optionally, the first configuration information is sent via at least one of the following:

[0357] System message;

[0358] Terminal-specific messages;

[0359] Physical Downlink Control Channel (PDCCH);

[0360] Physical Random Access Channel (PRACH) configuration;

[0361] A dedicated configuration table is used to specify the first configuration information.

[0362] Optionally, the PRACH configuration includes a PRACH configuration table, which includes the first configuration information.

[0363] Optionally, the guard band between the sub-band and other bandwidths is determined based on at least one of the following:

[0364] The protective band configured in the PRACH configuration table;

[0365] At least one random access channel (RO) opportunity.

[0366] Optionally, the at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

[0367] Optionally, when the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following:

[0368] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission;

[0369] The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition;

[0370] The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

[0371] Optionally, the first condition includes at least one of the following:

[0372] Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value;

[0373] Are there any SSBs or other downlink common channels or signals being transmitted on the other bandwidths?

[0374] Whether the terminal receives SSB or other downlink common channels or signals on the other bandwidths.

[0375] Optionally, the sending module 501 is further configured to:

[0376] Send second configuration information to the terminal, the second configuration information being used to configure at least one RO type, the at least one RO type including at least one of the following:

[0377] RO exists in the uplink time slot;

[0378] RO exists in time slots with flexible symbols;

[0379] RO exists in the uplink subband of the downlink time slot;

[0380] There is no RO on the uplink subband of the downlink time slot.

[0381] Optionally, if the at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no synchronization signal block (SSB) on the downlink time slot, or there is an SSB on the downlink time slot.

[0382] Optionally, the at least one RO type can be configured via any of the following:

[0383] Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources;

[0384] A public PRACH configuration resource, through which different RO types are configured.

[0385] Optionally, in the case of PRACH repetition, the device further includes:

[0386] A determining module is configured to determine an RO group from the at least one RO type to determine at least one resource for a PRACH transmission, wherein the determination of the RO group satisfies at least one of the following:

[0387] The RO group includes different RO types;

[0388] The RO group includes the same RO type;

[0389] The RO types included in the RO group are mapped to the same downlink reference signal;

[0390] The RO types included in the RO group are mapped to different downlink reference signals.

[0391] Optionally, in the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following:

[0392] Different RO types or RO resources are individually associated with SSB;

[0393] At least two different RO types or RO resources must be associated with the SSB together;

[0394] In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

[0395] Optionally, when the RO type or RO resource is associated with an SSB, the determining module is further configured to:

[0396] A first time period or a first window is determined, the first window including the determination window of the PRACH group, and the first time period includes at least one of the following:

[0397] The mapping period from SSB to RO;

[0398] The correlation cycle from SSB to RO;

[0399] The association pattern cycle from SSB to RO.

[0400] Optionally, the first time period or the first window is determined by at least one of the following:

[0401] The first time period or first window is determined according to different RO types or RO resources;

[0402] A common first time period or first window is determined based on at least two different RO types or RO resources;

[0403] The period is determined based on the enhanced duplex mode.

[0404] The resource configuration device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0405] As shown in Figure 6, this application embodiment also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores programs or instructions that can run on the processor 601. For example, when the communication device 600 is a terminal, the program or instructions executed by the processor 601 implement the various steps of the method embodiment in Figure 2 above, and achieve the same technical effect. When the communication device 600 is a network-side device, the program or instructions executed by the processor 601 implement the various steps of the method embodiment in Figure 3 above, and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0406] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, FIG7 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0407] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0408] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. The terminal structure shown in Figure 7 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0409] It should be understood that, in this embodiment, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0410] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low-noise amplifier, duplexer, etc.

[0411] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0412] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0413] The radio frequency unit 701 is used to receive the first configuration information sent by the network side device;

[0414] Processor 710 is configured to determine a subband in enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following:

[0415] The period of the enhanced duplex mode;

[0416] The width of the sub-band;

[0417] The starting frequency domain position of the sub-band;

[0418] The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband;

[0419] The subband has attributes that are related to the transmission direction;

[0420] The enhanced duplex mode is configured with a time slot pattern for the sub-band within a specified period.

[0421] In this embodiment of the application, the terminal can determine the sub-band in the enhanced duplex mode according to the first configuration information, thereby defining how to configure the frequency domain resources on the terminal side in the enhanced duplex mode, so that the terminal can flexibly use the duplex mode and effectively improve the transmission flexibility and transmission performance of the terminal.

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

[0423] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG3. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0424] Specifically, this application embodiment also provides a network-side device. As shown in FIG8, the network-side device 800 includes: an antenna 81, a radio frequency (RF) device 82, a baseband device 83, a processor 84, and a memory 85. The antenna 81 is connected to the RF device 82. In the uplink direction, the RF device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be transmitted and sends it to the RF device 82, which then processes the received information and transmits it through the antenna 81.

[0425] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 83, which includes a baseband processor.

[0426] The baseband device 83 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG8. One of the chips is, for example, a baseband processor, which is connected to the memory 85 via a bus interface to call the program in the memory 85 and execute the network device operation shown in the above method embodiment.

[0427] The network-side device may also include a network interface 86, such as a Common Public Radio Interface (CPRI).

[0428] Specifically, the network-side device 800 in this application embodiment further includes: instructions or programs stored in memory 85 and executable on processor 84. Processor 84 calls the instructions or programs in memory 85 to execute the methods executed by each module shown in FIG5 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0429] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the method embodiment described in FIG2 or FIG3, and achieve the same technical effect. To avoid repetition, they will not be described again here.

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

[0431] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the method embodiment described in FIG2 above, or to implement the various processes of the method embodiment described in FIG3 above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0433] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the method embodiment described in FIG2 above, or to implement the various processes of the method embodiment described in FIG3 above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0434] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the resource configuration method described above, and the network-side device can be used to execute the steps of the resource configuration method described above.

[0435] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

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

[0437] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A resource allocation method, comprising: The terminal receives the first configuration information sent by the network-side device; The terminal determines the subband in enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following: The period of the enhanced duplex mode; The width of the sub-band; The starting frequency domain position of the sub-band; The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband; The subband has attributes that are related to the transmission direction; The enhanced duplex mode is configured with a time slot pattern for the sub-band within its cycle.

2. The method of claim 1, wherein, When the first configuration information includes the guard band size between the sub-band and other bandwidths, the terminal satisfies any one of the following: The terminal is in sub-band full-duplex SBFD mode; The terminal is in half-duplex HD mode.

3. The method of claim 1 or 2, wherein, The first configuration information is sent via at least one of the following: System message; Terminal-specific messages; Physical Downlink Control Channel (PDCCH); Physical Random Access Channel (PRACH) configuration; A dedicated configuration table is used to specify the first configuration information.

4. The method of claim 3, wherein, The PRACH configuration includes a PRACH configuration table, which includes the first configuration information.

5. The method of claim 4, wherein, The guard band between the sub-band and other bandwidths is determined based on at least one of the following: The protective band configured in the PRACH configuration table; At least one random access channel (RO) opportunity.

6. The method of claim 5, wherein, The at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

7. The method of claim 5, wherein, When the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following: The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission; The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition; The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

8. The method of claim 7, wherein, The first condition includes at least one of the following: Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value; Are there any SSBs or other downlink common channels or signals being transmitted on the other bandwidths? Whether the terminal receives SSB or other downlink common channels or signals on the other bandwidths.

9. The method according to any one of claims 1-8, further comprising: The terminal receives second configuration information sent by the network-side device. The second configuration information is used to configure at least one RO type, and the at least one RO type includes at least one of the following: RO exists in the uplink time slot; RO exists in time slots with flexible symbols; RO exists in the uplink subband of the downlink time slot; There is no RO on the uplink subband of the downlink time slot.

10. The method of claim 9, wherein, In the case where at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no synchronization signal block (SSB) on the downlink time slot, or there is an SSB on the downlink time slot.

11. The method of claim 9, wherein, The at least one RO type is configured through any one of the following: Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources; A public PRACH configuration resource, through which different RO types are configured.

12. The method of claim 9, wherein, In the case of PRACH repetition, the method further includes: The terminal determines an RO group from the at least one RO type based on the second configuration information to determine at least one PRACH transmission resource, wherein the determination of the RO group satisfies at least one of the following: The RO group includes different RO types; The RO group includes the same RO type; The RO types included in the RO group are mapped to the same downlink reference signal; The RO types included in the RO group are mapped to different downlink reference signals.

13. The method of any one of claims 1-12, wherein, In the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following: Different RO types or RO resources are individually associated with SSB; At least two different RO types or RO resources must be associated with the SSB together; In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

14. The method of claim 13, wherein, When the RO type or RO resource is associated with an SSB, the method further includes: The terminal determines a first time period or a first window, the first window including a determination window for the PRACH group, and the first time period including at least one of the following: The mapping period from SSB to RO; The correlation cycle from SSB to RO; The association pattern cycle from SSB to RO.

15. The method of claim 14, wherein, The first time period or the first window is determined by at least one of the following: The first time period or first window is determined according to different RO types or RO resources; A common first time period or first window is determined based on at least two different RO types or RO resources; The period is determined based on the enhanced duplex mode.

16. The method of any one of claims 1-15, wherein, The terminal is an idle or inactive terminal.

17. A resource allocation method, comprising: The network-side device sends first configuration information to the terminal. The first configuration information is used to determine the subband in the enhanced duplex mode, wherein the first configuration information includes at least one of the following: The period of the enhanced duplex mode; The width of the sub-band; The starting frequency domain position of the sub-band; The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband; The subband has attributes that are related to the transmission direction; The enhanced duplex mode is configured with a time slot pattern for the sub-band within its cycle.

18. The method of claim 17, wherein, When the first configuration information includes the guard band size between the sub-band and other bandwidths, the terminal satisfies any one of the following: The terminal is in sub-band full-duplex SBFD mode; The terminal is in half-duplex HD mode.

19. The method of claim 17 or 18, wherein, The first configuration information is sent via at least one of the following: System message; Terminal-specific messages; Physical Downlink Control Channel (PDCCH); Physical Random Access Channel (PRACH) configuration; A dedicated configuration table is used to specify the first configuration information.

20. The method of claim 19, wherein, The PRACH configuration includes a PRACH configuration table, which includes the first configuration information.

21. The method of claim 20, wherein, The guard band between the sub-band and other bandwidths is determined based on at least one of the following: The protective band configured in the PRACH configuration table; At least one random access channel (RO) opportunity.

22. The method of claim 21, wherein, The at least one RO is at least one RO of the bandwidth edge occupied by PRACH.

23. The method of claim 21, wherein, When the guard band between the sub-band and other bandwidths is determined based on the at least one RO, the RO satisfies any one of the following: The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but not for actual PRACH transmission; The RO is a valid RO, and the RO can be used to implement SSB to RO mapping, but whether the RO is used for actual PRACH transmission depends on the first condition; The RO is not a valid RO, and the RO is not used to implement the SSB to RO mapping.

24. The method of claim 23, wherein, The first condition includes at least one of the following: Whether the time interval or frequency domain interval between RO and SSB is less than or equal to a preset value; Are there any SSBs or other downlink common channels or signals being transmitted on the other bandwidths? Whether the terminal receives SSB or other downlink common channels or signals on the other bandwidths.

25. The method according to any one of claims 17-24, further comprising: The network-side device sends second configuration information to the terminal, the second configuration information being used to configure at least one RO type, the at least one RO type including at least one of the following: RO exists in the uplink time slot; RO exists in time slots with flexible symbols; RO exists in the uplink subband of the downlink time slot; There is no RO on the uplink subband of the downlink time slot.

26. The method of claim 25, wherein, In the case where at least one RO type includes an RO present on an uplink subband of a downlink time slot, there is no synchronization signal block (SSB) on the downlink time slot, or there is an SSB on the downlink time slot.

27. The method of claim 25, wherein, The at least one RO type is configured through any one of the following: Independent PRACH configuration resources, wherein different RO types are configured through different independent PRACH configuration resources; A public PRACH configuration resource, through which different RO types are configured.

28. The method of claim 25, wherein, In the case of PRACH repetition, the method further includes: The network-side device determines an RO group from the at least one RO type to determine resources for at least one PRACH transmission, wherein the determination of the RO group satisfies at least one of the following: The RO group includes different RO types; The RO group includes the same RO type; The RO types included in the RO group are mapped to the same downlink reference signal; The RO types included in the RO group are mapped to different downlink reference signals.

29. The method of any one of claims 1-28, wherein, In the enhanced duplex mode, the correlation between the reference signal and the RO satisfies at least one of the following: Different RO types or RO resources are individually associated with SSB; At least two different RO types or RO resources must be associated with the SSB together; In the case where the time domains of RO and SSB overlap, the RO and SSB are not associated.

30. The method of claim 29, wherein, When the RO type or RO resource is associated with an SSB, the method further includes: The network-side device determines a first time period or a first window, the first window including a PRACH group determination window, and the first time period including at least one of the following: The mapping period from SSB to RO; The correlation cycle from SSB to RO; The association pattern cycle from SSB to RO.

31. The method of claim 30, wherein, The first time period or the first window is determined by at least one of the following: The first time period or first window is determined according to different RO types or RO resources; A common first time period or first window is determined based on at least two different RO types or RO resources; The period is determined based on the enhanced duplex mode.

32. A resource allocation device, comprising: The receiving module is used to receive the first configuration information sent by the network-side device; The determining module is configured to determine the sub-band in enhanced duplex mode based on the first configuration information, wherein the first configuration information includes at least one of the following: The period of the enhanced duplex mode; The width of the sub-band; The starting frequency domain position of the sub-band; The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband; The subband has attributes that are related to the transmission direction; The enhanced duplex mode is configured with a time slot pattern for the sub-band within its cycle.

33. A resource allocation device, comprising: The sending module is configured to send first configuration information to the terminal, the first configuration information being used to determine subbands in enhanced duplex mode, wherein the first configuration information includes at least one of the following: The period of the enhanced duplex mode; The width of the sub-band; The starting frequency domain position of the sub-band; The guard band size between the subband and other bandwidths, wherein the other bandwidths are the bandwidths configured in the enhanced duplex mode other than the subband; The subband has attributes that are related to the transmission direction; The enhanced duplex mode is configured with a time slot pattern for the sub-band within its cycle.

34. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the resource allocation method as described in any one of claims 1-16.

35. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the resource configuration method as described in any one of claims 17-31. 36.A readable storage medium, on which a program or instructions are stored, the program or instructions are executed by a processor to implement the steps of the resource configuration method in any one of claims 1-16, or implement the steps of the resource configuration method in any one of claims 17-31.

Images