Method and apparatus in communication node for wireless communication

Abstract

Disclosed are a method and apparatus in a communication node for wireless communication, the communication node receiving a first information block, the first information block indicating a symbol type of at least one symbol, the first information block indicating a target sub-band; a communication node receives a second information block and a third information block, the second information block indicating a first RO set, the third information block indicating a second RO set, ROs in the first RO set occupying at least one full duplex symbol in a time domain; wherein the first RO is one RO included in the first RO set, and the first RO occupies at least one full duplex symbol which is indicated to be flexible by TDD uplink and downlink configuration in a time domain; the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set, and the target SSB index set comprises an SSB index associated with at least one RO which is overlapped with the first RO in a time domain in the second RO set. The random access performance is improved.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and more particularly to a transmission scheme and device for flexible transmission direction configuration in wireless communication. Background Art

[0002] The application scenarios of future wireless communication systems are becoming more and more diversified, and different application scenarios have different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio technology (NR, New Radio) (or 5G), and the WI (Work Item, Work Item) of the new radio technology (NR, New Radio) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR was started. At the 3GPP RAN #86 plenary meeting, it was decided to start the SI (Study Item, Study Item) and WI (Work Item, Work Item) of NR Rel-17, and at the 3GPP RAN #94e plenary meeting, the SI and WI of NR Rel-18 were established. At the 3GPP RAN #102 plenary meeting, it was decided to start the SI and WI of NR Rel-19.

[0003] NR Rel-19 includes WI that supports non-overlapping sub-band full-duplex (SBFD, Subband non-overlapping Full Duplex). Non-overlapping sub-band full-duplex is also one of the technologies potentially supported by 6G. Summary of the invention

[0004] In the existing NR system, spectrum resources are statically divided into FDD spectrum and TDD spectrum. For TDD spectrum, both base stations and user equipment work in half-duplex mode. This half-duplex mode avoids self-interference and can alleviate the impact of cross-link interference, but it also brings about a decrease in resource utilization and an increase in latency. To address these problems, supporting flexible duplex modes on TDD spectrum or FDD spectrum has become a possible solution.

[0005] In view of the problem of random access configuration in supporting flexible duplex mode, the present application discloses a solution. It should be noted that in the description of the present application, the flexible duplex mode is only used as a typical application scenario or example; the present application is also applicable to 6G networks or other scenarios facing similar problems (for example, there are scenarios where the link direction changes, or other scenarios that support multi-level configuration of the transmission direction, or base stations or user equipment with stronger capabilities, such as supporting the same-frequency full-duplex scenario, or for different application scenarios, such as eMBB, URLLC, non-terrestrial networks, synaesthesia integrated networks, smart metasurfaces, terahertz networks, similar technical effects can also be achieved. In addition, the use of a unified solution for different scenarios (including but not limited to eMBB, URLLC, non-terrestrial networks, synaesthesia integrated networks, smart metasurfaces, terahertz networks) or different application parameters also helps to reduce hardware complexity and cost. In the absence of conflict, the embodiments of the terminal in the present application and the features in the embodiments can be applied to the base station in the present application, and vice versa.

[0006] The present application discloses a method used in a terminal, characterized by comprising:

[0007] receiving a first information block, the first information block indicating a symbol type of at least one symbol, the first information block indicating a target sub-band;

[0008] receiving a second information block and a third information block, wherein the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain;

[0009] Among them, the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0010] As an embodiment, the validity of the first RO is judged according to the relationship between the SSB index associated with the first RO and the target SSB index set, which takes into account the limitations of the analog beam implementation and improves the probability of successful PRACH transmission.

[0011] According to one aspect of the present application, the above method is characterized in that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the validity of the first RO.

[0012] According to one aspect of the present application, the method is characterized in that all ROs included in the second RO set that overlap in the time domain with at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band.

[0013] According to one aspect of the present application, the above method is characterized in that the effectiveness of the first RO depends on the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than a first threshold, and the first threshold is configured or predefined and / or related to the user equipment capability.

[0014] According to one aspect of the present application, the above method is characterized in that the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

[0015] According to one aspect of the present application, the above method is characterized in that a first capability information block is sent, wherein the first capability information block indicates that the sender of the first capability information block supports a random access process in a full-duplex symbol.

[0016] According to one aspect of the present application, the above method is characterized in that the ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

[0017] The present application discloses a terminal, characterized in that the terminal comprises: one or more processors and a memory;

[0018] The memory is coupled to the one or more processors, and the memory is used to store computer program codes, wherein the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the terminal to execute the above method.

[0019] The present application discloses a method used in a base station, characterized by comprising:

[0020] Sending a first information block, wherein the first information block indicates a symbol type of at least one symbol, and the first information block indicates a target sub-band;

[0021] Sending a second information block and a third information block, wherein the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain;

[0022] Among them, the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0023] According to one aspect of the present application, the above method is characterized in that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the validity of the first RO.

[0024] According to one aspect of the present application, the method is characterized in that all ROs included in the second RO set that overlap in the time domain with at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band.

[0025] According to one aspect of the present application, the above method is characterized in that the effectiveness of the first RO depends on the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than a first threshold, and the first threshold is configured or predefined and / or related to the user equipment capability.

[0026] According to one aspect of the present application, the above method is characterized in that the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

[0027] According to one aspect of the present application, the above method is characterized in that a first capability information block is received, wherein the first capability information block indicates that the sender of the first capability information block supports a random access process in full-duplex symbols.

[0028] According to one aspect of the present application, the above method is characterized in that the ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

[0029] The present application discloses a base station, characterized in that the base station comprises: one or more processors and a memory;

[0030] The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the base station to execute the above method.

[0031] As an embodiment, the present application has the following advantages but is not limited to:

[0032] Supports random access in full-duplex scenarios, which can further increase uplink coverage and reduce transmission delay;

[0033] Improving transmission reliability and robustness helps adapt to changing scenarios;

[0034] Reduce resource waste and redundancy and lower network costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0036] Figure 1 A flow chart showing a first information block, a second information block and a third information block according to an embodiment of the present application;

[0037] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0038] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0039] Figure 4 A schematic diagram of a terminal and a base station according to an embodiment of the present application is shown;

[0040] Figure 5 A flow chart showing transmission between a terminal and a base station according to an embodiment of the present application is shown;

[0041] Figure 6 A schematic diagram showing a condition under which a first RO is effective according to an embodiment of the present application;

[0042] Figure 7 A schematic diagram of a second RO set according to an embodiment of the present application is shown;

[0043] Figure 8 A schematic diagram showing a first threshold according to an embodiment of the present application is shown;

[0044] Fig. 9 A schematic diagram showing a second threshold according to an embodiment of the present application is shown;

[0045] Fig.10 A schematic diagram showing a first capability information block according to an embodiment of the present application is shown;

[0046] Fig.11 A schematic diagram showing mapping of a first RO set and a second RO set to a synchronous broadcast signal according to an embodiment of the present application is shown;

[0047] Fig.12 A structural block diagram of a processing device used in a terminal according to an embodiment of the present application is shown;

[0048] Fig.13 A structural block diagram of a processing device used in a base station according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0050] Example 1

[0051] Embodiment 1 illustrates a flowchart of a first information block, a second information block, and a third information block according to an embodiment of the present application, as shown in the attached figure. Figure 1 As shown in the attached Figure 1 In the example, each box represents a step. In particular, the order of the steps in the box does not represent a specific time sequence between the steps.

[0052] In Example 1, the terminal 100 in the present application receives a first information block in step 101, the first information block indicates the symbol type of at least one symbol, and the first information block indicates a target sub-band; the terminal in the present application receives a second information block and a third information block in step 102, the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0053] As an embodiment, the first information block includes part or all of the fields included in a SIB.

[0054] As an embodiment, the first information block is cell common (Cell Common).

[0055] As an embodiment, the first information block is cell specific.

[0056] As an embodiment, the first information block is group common.

[0057] As an embodiment, the first information block is user equipment specific (UE specific or UEdedicated).

[0058] As an embodiment, the first information block is configured per subband (per subband).

[0059] As an embodiment, the first information block is configured per bandwidth part (BWP, bandwidth Part) (Per BWP).

[0060] As an embodiment, the first information block includes part or all of the fields in IE "SBFDConfigDedicated-r19".

[0061] As an embodiment, the first information block includes part or all of the fields in IE "SBFDConfigCommon-r19".

[0062] As an embodiment, the first information block includes part or all of the fields in IE "SBFDConfig-r19".

[0063] As an embodiment, the first information block includes part or all of the fields in the IE "ServingCellConfigCommon".

[0064] As an embodiment, the first information block includes part or all of the fields in the IE "CellGroupConfig".

[0065] As an embodiment, the first information block includes part or all of the fields in IE "SpCellConfig".

[0066] As an embodiment, the first information block includes part or all of the fields in the IE "SCellConfig".

[0067] As an embodiment, the first information block includes part or all of the fields in the IE "ServingCellConfigCommonSIB".

[0068] As an embodiment, the first information block includes part or all of the fields in the IE "ServingCellConfig".

[0069] As an embodiment, the first information block includes part or all of the fields in IE "UplinkConfig".

[0070] As an embodiment, the first information block includes part or all of the fields in IE "TDD-UL-DL-ConfigCommon".

[0071] As an embodiment, the first information block is used to configure SBFD (Subband non-overlapping Full Duplex) time slots or symbols.

[0072] As an embodiment, the first information block is used to configure a time slot or symbol supporting full-duplex.

[0073] As an embodiment, the first information block configures an uplink subband (UL subband) and a downlink subband (DL subband) of the SBFD.

[0074] As an embodiment, the number of possible symbol types for a symbol is equal to two.

[0075] As an embodiment, the number of possible symbol types for a symbol is greater than two.

[0076] As an embodiment, the symbol type of a symbol is a SBFD symbol or a non-SBFD symbol.

[0077] As an embodiment, the symbol type of a symbol is a symbol configured with SBFD or a symbol not configured with SBFD.

[0078] As an embodiment, the symbol type of a symbol is a symbol in a SBFD time slot or a symbol in a non-SBFD time slot.

[0079] As an embodiment, the symbol type of a symbol is a symbol in which a subband of SBFD is configured in the time domain or a symbol in which a subband of SBFD is not configured in the time domain.

[0080] As an embodiment, the symbol type of a symbol is a time domain symbol supporting full duplex or a symbol not supporting full duplex.

[0081] As an embodiment, the symbol type of a symbol is a symbol to which SBFD is applicable or a symbol to which SBFD is not applicable.

[0082] As an embodiment, the symbol type of a symbol is a symbol that can be used for uplink transmission and downlink transmission at the same time or a symbol that cannot be used for uplink transmission and downlink transmission at the same time.

[0083] As an embodiment, the symbol type of a symbol is a SBFD symbol or other types of symbols indicated as downlink by TDD uplink and downlink configuration.

[0084] As an embodiment, the symbol type of a symbol is one of an SBFD symbol indicated as downlink by the TDD uplink and downlink configuration, an SBFD symbol indicated as flexible by the TDD uplink and downlink configuration, a symbol indicated as uplink by the TDD uplink and downlink configuration, a non-SBFD symbol indicated as flexible by the TDD uplink and downlink configuration, and a non-SBFD symbol indicated as downlink by the TDD uplink and downlink configuration.

[0085] As an embodiment, both downlink and flexible symbols are considered to expand configuration flexibility.

[0086] As an embodiment, the symbol type of a symbol is a SBFD symbol indicated as a downlink symbol by the TDD uplink and downlink configuration or is an uplink or flexible symbol indicated as a downlink symbol by the TDD uplink and downlink configuration.

[0087] As an embodiment, only downlink symbols are considered, which simplifies system design.

[0088] As an embodiment, the symbol type of a symbol is one of T1 symbol types, T1 is a positive integer greater than 1, and the T1 symbol types are predefined or configurable. As an auxiliary embodiment of the above embodiment, the T1 symbol types include SBFD symbols and non-SBFD symbols. As an auxiliary embodiment of the above embodiment, the T1 symbol types include symbols configured in the time domain for the SBFD subband and symbols not configured in the time domain for the SBFD subband. As an auxiliary embodiment of the above embodiment, the T1 symbol types are symbols corresponding to T1 TCI states respectively. As an auxiliary embodiment of the above embodiment, the T1 symbol types are symbols corresponding to T1 radio frequency links respectively. As an auxiliary embodiment of the above embodiment, the T1 symbol types are symbols corresponding to T1 beams respectively. As an auxiliary embodiment of the above embodiment, the T1 symbol types are symbols corresponding to T1 interference elimination schemes respectively. As an auxiliary embodiment of the above embodiment, the T1 symbol types are symbols corresponding to T1 QCL relationships respectively. As an auxiliary embodiment of the above embodiment, T1 is equal to 2. As a subsidiary embodiment of the above embodiment, the T1 is greater than 2. As a subsidiary embodiment of the above embodiment, the T1 symbol types depend on the capability of the terminal. As a subsidiary embodiment of the above embodiment, the terminal cannot assume that two time domain symbols belonging to different symbol types in the T1 symbol types have the same QCL parameter (or QCL assumption).

[0089] As an embodiment, symbols in the time domain are divided into multiple types, and the symbol type of a symbol is one of the multiple types.

[0090] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: all or part of the cell-specific parameters included in the first information block indicate the symbol type of at least one symbol.

[0091] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: the symbol type of at least one symbol depends on the first information block.

[0092] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: all or part of the first information block is used to explicitly or implicitly indicate the symbol type of at least one symbol.

[0093] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: the time domain symbol indicated (or provided) by the first information block is one type of symbol, and the time domain symbol not indicated (or provided) by the first information block is another type of symbol.

[0094] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: the first information block explicitly or implicitly indicates whether the symbol type of at least one symbol is a SBFD symbol or a non-SBFD symbol.

[0095] As an embodiment, the technical feature "the first information block indicates the symbol type of at least one symbol" includes: the first information block explicitly or implicitly indicates that the symbol type of at least one symbol is one of an SBFD symbol indicated as downlink by the TDD uplink and downlink configuration, a flexible SBFD symbol indicated as downlink by the TDD uplink and downlink configuration, a non-SBFD symbol indicated as downlink by the TDD uplink and downlink configuration, a flexible non-SBFD symbol indicated as uplink by the TDD uplink and downlink configuration, and a symbol indicated as uplink by the TDD uplink and downlink configuration.

[0096] As an embodiment, the target sub-band is a SBFD sub-band (full duplex subband).

[0097] As an embodiment, the target sub-frequency band is a SBFD sub-frequency band used for uplink.

[0098] As an embodiment, the target sub-frequency band is an uplink SBFD sub-frequency band.

[0099] As an embodiment, the target sub-frequency band is a sub-frequency band that can be used for uplink transmission in a downlink symbol or a flexible symbol.

[0100] As an embodiment, the target sub-frequency band includes guard frequency domain resources (guard).

[0101] As an embodiment, the target sub-band does not include protection frequency domain resources.

[0102] As an embodiment, the target sub-band includes continuous frequency domain resources.

[0103] As an embodiment, an uplink BWP includes all or part of the frequency domain resources in the target sub-band. As a subsidiary embodiment of the above embodiment, the target sub-band belongs to the uplink BWP, which can reuse the existing design to the greatest extent and reduce the design complexity.

[0104] As an embodiment, an uplink active BWP includes all or part of the frequency domain resources in the target sub-band. As a subsidiary embodiment of the above embodiment, the uplink active BWP includes part of the resources in the target sub-band to support carrier-level sub-band configuration and increase flexibility.

[0105] As an embodiment, in a time domain symbol, there are overlapping frequency domain resources between the target sub-band and the active uplink BWP.

[0106] As an embodiment, in a time domain symbol, there are no overlapping frequency domain resources between the target sub-band and the active uplink BWP.

[0107] As an embodiment, the boundary of the RB (Resource Block) included in the target sub-band is aligned with the boundary of the RB in the uplink BWP. As a subsidiary embodiment of the above embodiment, uplink resource fragmentation is avoided and coverage is improved.

[0108] As an embodiment, the target sub-band is spaced per numerology or per sub-carrier.

[0109] As an embodiment, the target sub-band is per resource grid. As a subsidiary embodiment of the above embodiment, configuring the sub-band per grid improves configuration flexibility.

[0110] As an embodiment, the target sub-band is per BWP. As a subsidiary embodiment of the above embodiment, configuring the sub-band per BWP ensures compatibility and reduces standard complexity.

[0111] As an embodiment, the boundary of the RB included in the target sub-band is aligned with the boundary of the RB in the downlink BWP. As a subsidiary embodiment of the above embodiment, downlink resource fragmentation is avoided and scheduling flexibility is guaranteed.

[0112] As an embodiment, the technical feature "the first information block indicates a target sub-frequency band" includes: all or part of the first information block explicitly or implicitly indicates the target sub-frequency band.

[0113] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates the starting RB (or the lowest indexed RB) of the target sub-band.

[0114] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates the number of RBs included in the target sub-band.

[0115] As an embodiment, the technical feature "the first information block indicates the target sub-frequency band" includes: the first information block indicates the RIV (resource indicator value) corresponding to the target sub-frequency band.

[0116] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates the RIV corresponding to the target sub-band, and the starting RB of the target sub-band and the number of consecutive RBs included are used to generate the corresponding RIV.

[0117] As an embodiment, the technical feature "the first information block indicates the target sub-frequency band" includes: the first information block indicates the SLIV (start and length indicator value) corresponding to the target sub-frequency band.

[0118] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates the SLIV corresponding to the target sub-band, and the starting RB of the target sub-band and the number of consecutive RBs included are used to generate the corresponding SLIV.

[0119] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates at least one CRB (common resource block) for one subcarrier spacing included in the target sub-band.

[0120] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates the number of CRBs between the lowest indexed CRB included in the target sub-band and frequency point A (pointA) and the number of continuous CRBs included in the target sub-band.

[0121] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: all or part of the first information block explicitly or implicitly indicates the number of CRBs for the reference sub-carrier spacing and the interval between the lowest index of the CRB for the reference sub-carrier spacing included in the target sub-band and the frequency point A (pointA), and the number of consecutive CRBs for the reference sub-carrier spacing included in the target sub-band. As an auxiliary embodiment of the above embodiment, the reference sub-carrier spacing is equal to the sub-carrier spacing in an uplink resource grid; the benefits of doing so include avoiding resource fragmentation. As an auxiliary embodiment of the above embodiment, the reference sub-carrier spacing is equal to the sub-carrier spacing in a downlink resource grid, and the benefit of doing so is to improve scheduling flexibility. As an auxiliary embodiment of the above embodiment, the reference sub-carrier spacing is related to the frequency range (FR). As an auxiliary embodiment of the above embodiment, the reference sub-carrier spacing is predefined or configured. As an auxiliary embodiment of the above embodiment, the reference subcarrier spacing is the maximum value among the subcarrier spacings respectively targeted by the multiple uplink resource grids configured; the advantage of this is that the alignment with the uplink resources is ensured. As an auxiliary embodiment of the above embodiment, the reference subcarrier spacing is the maximum value among the subcarrier spacings respectively targeted by the multiple downlink resource grids configured; the advantage of this is that the alignment with the downlink resources is ensured. As an auxiliary embodiment of the above embodiment, the reference subcarrier spacing is the maximum value among the subcarrier spacings respectively targeted by all the configured resource grids; the advantage of this is that the alignment with both the uplink and downlink resources is ensured.

[0122] As an embodiment, the technical feature "the first information block indicates the target sub-band" includes: the first information block indicates M1 sub-bands from M1 resource grids respectively, M1 is a positive integer greater than 1, and the target sub-band is one of the M1 sub-bands. As an auxiliary embodiment of the above embodiment, the M1 resource grids are M1 uplink resource grids; the advantage of this is that the fragmentation of uplink resources is avoided while not increasing signaling overhead. As an auxiliary embodiment of the above embodiment, the M1 resource grids are M1 downlink resource grids; the advantage of this is that the fragmentation of downlink resources is avoided while not increasing signaling overhead. As an auxiliary embodiment of the above embodiment, the M1 resource grids include both uplink resource grids and downlink resource grids; the advantage of this is that uplink and downlink resource allocation is considered at the same time but some signaling overhead will be increased. As an auxiliary embodiment of the above embodiment, the M1 resource grids are configured.

[0123] As an embodiment, the second information block includes part or all of the fields included in a SIB.

[0124] As an embodiment, the second information block is cell common (Cell Common).

[0125] As an embodiment, the second information block is cell specific.

[0126] As an embodiment, the second information block is group common.

[0127] As an embodiment, the second information block is configured per subband.

[0128] As an embodiment, the second information block is configured per carrier (per carrier).

[0129] As an embodiment, the second information block is configured per bandwidth part (BWP, bandwidth Part) (Per BWP).

[0130] As an embodiment, the second information block includes part or all of the fields in IE "SIB1".

[0131] As an embodiment, the second information block includes part or all of the fields in the IE "ServingCellConfigCommon".

[0132] As an embodiment, the second information block includes part or all of the fields in the IE "ServingCellConfigCommonSIB".

[0133] As an embodiment, the second information block includes part or all of the fields in IE "UplinkConfigCommon".

[0134] As an embodiment, the second information block includes part or all of the fields in the IE "UplinkConfigCommonSIB".

[0135] As an embodiment, the second information block includes part or all of the fields in IE "BWP-UplinkCommon".

[0136] As an embodiment, the second information block includes part or all of the fields in IE "RACH-ConfigCommon".

[0137] As an embodiment, the second information block includes part or all of the fields in IE "RACH-ConfigGeneric".

[0138] As an embodiment, the second information block includes part or all of the fields in IE "SBFDConfigCommon-r19".

[0139] As an embodiment, the second information block includes part or all of the fields in IE "SBFDConfig-r19".

[0140] As an embodiment, the third information block includes part or all of the fields included in a SIB.

[0141] As an embodiment, the third information block is cell common (Cell Common).

[0142] As an embodiment, the third information block is cell specific.

[0143] As an embodiment, the third information block is group common.

[0144] As an embodiment, the third information block is configured per subband (per subband).

[0145] As an embodiment, the third information block is configured per carrier (per carrier).

[0146] As an embodiment, the third information block is configured per bandwidth part (BWP, bandwidth Part) (Per BWP).

[0147] As an embodiment, the third information block includes part or all of the fields in IE "SIB1".

[0148] As an embodiment, the third information block includes part or all of the fields in the IE "ServingCellConfigCommon".

[0149] As an embodiment, the third information block includes part or all of the fields in the IE "ServingCellConfigCommonSIB".

[0150] As an embodiment, the third information block includes part or all of the fields in the IE "UplinkConfigCommon".

[0151] As an embodiment, the third information block includes part or all of the fields in the IE "UplinkConfigCommonSIB".

[0152] As an embodiment, the third information block includes part or all of the fields in IE "BWP-UplinkCommon".

[0153] As an embodiment, the third information block includes part or all of the fields in IE "RACH-ConfigCommon".

[0154] As an embodiment, the third information block includes part or all of the fields in IE "RACH-ConfigGeneric".

[0155] As an embodiment, the first RO set includes multiple ROs.

[0156] As an embodiment, each RO in the first RO set is a PRACH (Physical Random Access Channel) Occasion.

[0157] As an embodiment, each RO in the first RO set includes allocated or configured PRACH time-frequency resources.

[0158] As an embodiment, each RO in the first RO set includes time-frequency resources occupied by one PRACH transmission.

[0159] As an embodiment, every two ROs in the first RO set are time division multiplexed.

[0160] As an embodiment, there are two ROs in the first RO set that include the same time domain resources.

[0161] As an embodiment, there are two ROs in the first RO set including different time domain resources.

[0162] As an embodiment, there are two frequency division multiplexed (FDM) PRACH opportunities in the first RO set.

[0163] As an embodiment, every two ROs in the first RO set are for the same preamble format. As a subsidiary embodiment of the above embodiment, the advantage of doing so is that the design is simple.

[0164] As an embodiment, there are two ROs in the first RO set for different preamble formats. As a subsidiary embodiment of the above embodiment, the benefit of doing so is to enhance flexibility.

[0165] As an embodiment, each RO in the first RO set occupies at least one SBFD symbol in the time domain.

[0166] As an embodiment, each RO in the first RO set only occupies SBFD symbols in the time domain.

[0167] As an embodiment, each RO in the first RO set occupies only SBFD symbols indicated as downlink by the TDD uplink and downlink configuration or SBFD symbols indicated as flexible by the TDD uplink and downlink configuration in the time domain.

[0168] As an embodiment, some ROs in the first RO set occupy both SBFD symbols and non-SBFD symbols in the time domain, and the some ROs are configured by the base station.

[0169] As an embodiment, the second RO set includes multiple ROs.

[0170] As an embodiment, each RO in the second RO set is a PRACH (Physical Random Access Channel) Occasion.

[0171] As an embodiment, each RO in the second RO set includes allocated or configured PRACH time-frequency resources.

[0172] As an embodiment, each RO in the second RO set includes time-frequency resources occupied by one PRACH transmission.

[0173] As an embodiment, every two ROs in the second RO set are time division multiplexed.

[0174] As an embodiment, every two ROs in the second RO set include the same time domain resources.

[0175] As an embodiment, every two ROs in the second RO set include different time domain resources.

[0176] As an embodiment, there are two frequency division multiplexed (FDM) PRACH opportunities in the second RO set.

[0177] As an embodiment, each RO included in the second RO set is a legacy RO.

[0178] As an embodiment, each RO included in the second RO set is an RO outside the first RO set.

[0179] As an embodiment, each RO included in the second RO set is an RO that has no overlap with the downlink indicated by the TDD uplink and downlink configuration.

[0180] As an embodiment, the second RO set is orthogonal to the first RO set.

[0181] As an embodiment, every two ROs in the second RO set are for the same preamble format. As a subsidiary embodiment of the above embodiment, the advantage of doing so is that the design is simple.

[0182] As an embodiment, the preamble format for one RO in the first RO set is different from the preamble format for one RO in the second RO set. As a subsidiary embodiment of the above embodiment, the benefit of doing so is to increase flexibility and optimize coverage performance in the SBFD case.

[0183] As an embodiment, the preamble format for each RO in the first RO set is the same as the preamble format for each RO in the second RO set. As a subsidiary embodiment of the above embodiment, the advantage of doing so is that the design is simple and the complexity of implementation is reduced.

[0184] As an embodiment, each RO in the second RO set occupies only non-SBFD symbols in the time domain.

[0185] As an embodiment, each RO in the second RO set occupies only symbols indicated as uplink or flexible by the TDD uplink configuration in the time domain.

[0186] As an embodiment, each RO in the second RO set occupies in the time domain a symbol indicated as uplink by the TDD uplink configuration, a flexible non-SBFD symbol indicated as flexible by the TDD uplink configuration, or a flexible SBFD symbol indicated as flexible by the TDD uplink configuration.

[0187] As an embodiment, all ROs included in the second RO set that overlap in the time domain with at least one SBFD symbol indicated as flexible by the TDD uplink and downlink configuration belong to the target sub-band in the frequency domain.

[0188] As an embodiment, “the second information block indicates the first RO set” includes: part or all of the second information block is used to explicitly or implicitly indicate the first RO set.

[0189] As an embodiment, “the second information block indicates the first RO set” includes: the first RO set depends on the second information block.

[0190] As an embodiment, “the second information block indicates a first RO set” includes: the second information block is used to determine the first RO set.

[0191] As an embodiment, "the second information block indicates the first RO set" includes: the second information block indicates the time-frequency resources included in at least one RO in the first RO set.

[0192] As an embodiment, "the second information block indicates the first RO set" includes: the second information block indicates the number of ROs in the first RO set that are frequency-divided in the same time domain resources.

[0193] As an embodiment, "the second information block indicates the first RO set" includes: the second information block indicates the starting frequency domain resource of the lowest PRACH opportunity in the frequency domain in the first RO set.

[0194] As an embodiment, "the second information block indicates the first RO set" includes: the second information block indicates a PRACH configuration index (configuration index), and the PRACH configuration index configures the first RO set.

[0195] As an embodiment, "the second information block indicates a first RO set" includes: the second information block indicates a PRACH configuration index, and the RO located on the full-duplex symbol configured by the PRACH configuration index belongs to the first RO set.

[0196] As an embodiment, "the second information block indicates a first RO set" includes: the second information block indicates a PRACH configuration index, and the RO configured by the PRACH configuration index that overlaps with the downlink or flexible full-duplex symbol indicated by the TDD uplink and downlink configuration belongs to the first RO set.

[0197] As an embodiment, “the third information block indicates the second RO set” includes: part or all of the third information block is used to explicitly or implicitly indicate the second RO set.

[0198] As an embodiment, "the third information block indicates a second RO set" includes: the second RO set depends on the third information block.

[0199] As an embodiment, “the third information block indicates the second RO set” includes: the third information block is used to determine the second RO set.

[0200] As an embodiment, "the third information block indicates the second RO set" includes: the third information block indicates the time-frequency resources included in at least one RO in the second RO set.

[0201] As an embodiment, "the third information block indicates the second RO set" includes: the third information block indicates the number of ROs in the second RO set that are frequency-divided in the same time domain resources.

[0202] As an embodiment, "the third information block indicates the second RO set" includes: the third information block indicates the starting frequency domain resource of the lowest PRACH opportunity in the frequency domain in the second RO set.

[0203] As an embodiment, "the third information block indicates the second RO set" includes: the third information block indicates a PRACH configuration index (configuration index), and the PRACH configuration index configures the second RO set.

[0204] As an embodiment, "the third information block indicates the second RO set" includes: the third information block indicates a PRACH configuration index, and the RO located on the uplink or flexible symbol configured by the PRACH configuration index belongs to the second RO set.

[0205] As an embodiment, "the third information block indicates a second RO set" includes: the third information block indicates a PRACH configuration index, and the RO configured by the PRACH configuration index that overlaps with the symbol indicated as uplink by the TDD uplink configuration, the non-SBFD symbol indicated as flexible by the TDD uplink configuration, or the SBFD symbol indicated as flexible by the TDD uplink configuration belongs to the second RO set.

[0206] As an embodiment, the full-duplex symbol is a SBFD symbol.

[0207] As an embodiment, the “full-duplex” and the “SBFD” are equivalent or interchangeable.

[0208] As an embodiment, the full-duplex symbol is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0209] As an embodiment, the full-duplex symbol is a time domain symbol configured with SBFD.

[0210] As an embodiment, the full-duplex symbol is a symbol configured with a SBFD sub-band.

[0211] As an embodiment, the full-duplex symbol is a time domain symbol supporting full-duplex.

[0212] As an embodiment, the full-duplex symbol is a time domain symbol applicable to SBFD.

[0213] As an embodiment, the full-duplex symbol is a time domain symbol capable of simultaneously performing uplink transmission and downlink transmission.

[0214] As an embodiment, the full-duplex symbol is a time domain symbol that can simultaneously perform uplink transmission and downlink transmission on the network side (or base station side).

[0215] As an embodiment, the full-duplex symbol is a time domain symbol that can simultaneously perform uplink transmission and downlink transmission on both the network side (or base station side) and the user equipment side.

[0216] As an embodiment, the full-duplex symbol is a time domain symbol indicated (or provided) by signaling for configuring SBFD.

[0217] As an embodiment, the full-duplex symbol is a symbol that can be used for uplink transmission on the downlink symbol indicated by the TDD uplink and downlink configuration.

[0218] As an embodiment, only downlink symbols are considered, which simplifies system design.

[0219] As an embodiment, the full-duplex symbol is a symbol that can be used for uplink transmission on a downlink or flexible symbol indicated by a TDD uplink and downlink configuration.

[0220] As an embodiment, the full-duplex symbol is a symbol indicated as downlink by the TDD uplink and downlink configuration and configured (or indicated) as a SBFD symbol, or a symbol indicated as flexible by the TDD uplink and downlink configuration and configured (or indicated) as a SBFD symbol.

[0221] As an embodiment, the full-duplex symbol is a symbol indicated as downlink by the TDD uplink and downlink configuration and indicated (or provided) by the first information block, or a symbol indicated as flexible by the TDD uplink and downlink configuration and indicated (or provided) by the first information block.

[0222] As an embodiment, only TDD uplink and downlink configurations are considered, which simplifies the design and reduces the workload of standards.

[0223] As an embodiment, both downlink and flexible symbols are considered, thereby expanding configuration flexibility.

[0224] As an embodiment, "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: each RO in the first RO set occupies at least one full-duplex symbol in the time domain.

[0225] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set occupy at least one full-duplex symbol indicated by the first information block in the time domain.

[0226] In one embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: the ROs in the first RO set are mapped to at least one full-duplex symbol in the time domain.

[0227] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: the ROs in the first RO set are located in the full-duplex symbol in the time domain.

[0228] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: the ROs in the first RO set include at least one full-duplex symbol in the time domain.

[0229] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set overlap with at least one full-duplex symbol in the time domain.

[0230] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set are completely overlapped between the time domain and at least one full-duplex symbol.

[0231] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set fully or partially overlap between the time domain and at least one full-duplex symbol.

[0232] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set occupy at least one full-duplex symbol in the time domain indicated as a downlink by the TDD uplink and downlink configuration.

[0233] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set occupy at least one full-duplex symbol in the time domain indicated as downlink or flexible by the TDD uplink and downlink configuration.

[0234] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: there is overlap between the PRACH time slot (slot) to which the ROs in the first RO set belong and at least one full-duplex symbol in the time domain.

[0235] As an embodiment, the technical feature "ROs in the first RO set occupy at least one full-duplex symbol in the time domain" includes: ROs in the first RO set overlap in the time domain and a time slot including at least one full-duplex symbol.

[0236] As an embodiment, “the first RO is an RO included in the first RO set” includes: the first RO belongs to the first RO set.

[0237] As an embodiment, “the first RO is an RO included in the first RO set” includes: the first RO is one of a plurality of ROs included in the first RO set.

[0238] As an embodiment, "the first RO is an RO included in the first RO set" includes: the first RO is one of a plurality of ROs included in the first RO set and occupying at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain.

[0239] As an embodiment, "the first RO is an RO included in the first RO set" includes: the first RO is any one of the multiple ROs included in the first RO set that occupies at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the time domain.

[0240] As an embodiment, the TDD uplink / downlink configuration is an uplink / downlink TDD configuration used to determine a time slot format.

[0241] As an embodiment, the TDD uplink and downlink configuration at least includes configuration information indicating which symbols in a periodic time window are downlink symbols, which symbols are flexible symbols, and which symbols are uplink symbols.

[0242] As an embodiment, the TDD uplink and downlink configuration is a higher-layer configuration that at least includes indication information of the link direction of the symbol.

[0243] As an embodiment, the TDD uplink and downlink configuration is an RRC layer configuration.

[0244] As an embodiment, the TDD uplink and downlink configuration is a higher layer configuration.

[0245] As an embodiment, the TDD uplink and downlink configuration also includes indication information of the adopted subcarrier spacing.

[0246] As an embodiment, the TDD uplink and downlink configuration also includes indication information of the length of the adopted periodic time window.

[0247] As an embodiment, the TDD uplink and downlink configuration includes part or all of the fields in the IE "tdd-UL-DL-ConfigCommon".

[0248] As an embodiment, the TDD uplink and downlink configuration includes part or all of the fields in the IE "tdd-UL-DL-ConfigDedicated".

[0249] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol in the time domain indicated as flexible by the TDD uplink and downlink configuration" includes: the first RO occupies at least one full-duplex symbol in the time domain indicated by the first information block and indicated as flexible by the TDD uplink and downlink configuration.

[0250] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO is mapped to at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain.

[0251] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO is located in the full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain.

[0252] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO includes at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain.

[0253] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO overlaps in the time domain with at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0254] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO fully or partially overlaps between the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0255] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: there is an overlap between the PRACH time slot to which the first RO belongs in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0256] As an embodiment, the technical feature "the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain" includes: the first RO overlaps in the time domain and includes at least one time slot indicated as flexible by the TDD uplink and downlink configuration.

[0257] As an embodiment, the SSB is a synchronization signal block (SSB).

[0258] As an embodiment, the SSB is a synchronization signal.

[0259] As an embodiment, the SSB is a physical broadcast channel (PBCH).

[0260] As an embodiment, the SSB includes a synchronization signal and a physical broadcast channel.

[0261] As an embodiment, the SSB is a synchronization signal physical broadcast channel block (SS (SynchronizationSignal) / PBCH

[0262] (Physical Broadcast Channel)block).

[0263] As an embodiment, the SSB is a 6G synchronization signal or a 6G physical broadcast channel.

[0264] As an embodiment, the "SSB" and the "Synchronous Broadcast Signal" are equivalent or interchangeable.

[0265] As an embodiment, the SSB index is a non-negative integer.

[0266] As an embodiment, the SSB index is the index (Index) of the synchronous broadcast block.

[0267] As an embodiment, the SSB index is an index of a synchronized broadcast block in multiple synchronized broadcast blocks.

[0268] As an embodiment, the SSB index indicates the index of the synchronization broadcast block.

[0269] As an embodiment, the SSB index associated with the first RO includes one SSB index.

[0270] As an embodiment, the SSB index associated with the first RO includes multiple SSB indexes.

[0271] As an embodiment, the number of SSB indexes associated with the first RO is 1.

[0272] As an embodiment, the number of SSB indexes associated with the first RO is greater than 1.

[0273] As an embodiment, the number of SSB indexes associated with the first RO is one of {1, 2, 4, 8, 16}.

[0274] As an embodiment, the number of SSB indexes associated with the first RO is less than or equal to the value determined by the field "ssb-PositionsInBurst", or the number of SSB indexes associated with the first RO is less than or equal to the number of bits corresponding to the field "ssb-PositionsInBurst" whose value is 1.

[0275] As an embodiment, the number of SSB indexes associated with the first RO depends on the second information block.

[0276] As an embodiment, a field included in the second information block indicates the number of SSB indexes associated with the first RO.

[0277] As an embodiment, the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block indicates the number of SSB indexes associated with the first RO, and the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" represents the number of SSBs corresponding to each RO.

[0278] As an embodiment, the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block is used to determine (or used to calculate) the number of SSB indexes associated with the first RO.

[0279] As an embodiment, the number of SSB indexes associated with the first RO is N, and N depends on the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block.

[0280] As an embodiment, the value of the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block is N. When N is greater than 1, the number of SSB indexes associated with the first RO is N; when N is less than or equal to 1, the number of SSB indexes associated with the first RO is 1.

[0281] As an embodiment, the SSB index associated with the first RO is the SSB index corresponding to (or mapped to) the first RO.

[0282] As an embodiment, the SSB index associated with the first RO is the SSB index associated with the first RO in an SSB-RO mapping loop.

[0283] As an embodiment, the SSB index associated with the first RO is an SSB index associated with the first RO in an SSB-RO mapping cycle between the synchronization broadcast signal and the first RO set.

[0284] As an embodiment, the SSB index associated with the first RO indicates an SSB, and the receiving beam of the SSB corresponds to the transmitting beam of the first RO.

[0285] As an embodiment, the SSB index associated with the first RO indicates an SSB, and the receiving spatial filter of the one SSB and the transmitting spatial filter of the first RO are mutually different or corresponding.

[0286] As an embodiment, the target SSB index set includes only one SSB index.

[0287] As an embodiment, the target SSB index set includes multiple SSB indexes.

[0288] As an embodiment, the target SSB index set includes an SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0289] As an embodiment, the number of SSB indexes included in the target SSB index set is 1.

[0290] As an embodiment, the number of SSB indexes included in the target SSB index set is a positive integer greater than 1.

[0291] As an embodiment, the number of SSB indexes included in the target SSB index set is less than or equal to the value determined by the field "ssb-PositionsInBurst", or the number of SSB indexes included in the target SSB index set is less than or equal to the number of bits corresponding to the field "ssb-PositionsInBurst" whose value is 1.

[0292] As an embodiment, the third information block indicates multiple SSB indexes included in the target SSB index set.

[0293] As an embodiment, the multiple fields included in the third information block are used to jointly determine (or are used to jointly calculate) the multiple SSB indexes included in the target SSB index set.

[0294] As an embodiment, the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" and the field "msg1-FDM" included in the third information block are used to jointly determine multiple SSB indexes included in the target SSB index set, the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" indicates the number of SSBs corresponding to each RO, and the field "msg1-FDM" indicates the number of frequency-division multiplexed ROs.

[0295] As an embodiment, the SSB index associated with at least one RO in the second RO set included in the target SSB index set that overlaps with the first RO in the time domain depends on the field "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" and the field "msg1-FDM" included in the third information block.

[0296] As an embodiment, the target SSB index set is a set of SSB indexes corresponding to (or mapped to) at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0297] As an embodiment, the target SSB index set is a set of SSB indexes of at least one RO in the second RO set that is associated in the SSB-RO mapping cycle and overlaps with the first RO in the time domain.

[0298] As an embodiment, the target SSB index set is a set of SSB indexes of at least one RO in the second RO set that is associated with the first RO in the time domain in the SSB-RO mapping cycle between the synchronization broadcast signal and the second RO set.

[0299] As an embodiment, each SSB index included in the target SSB index set is associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0300] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO belongs to the target SSB index set.

[0301] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO does not belong to the target SSB index set.

[0302] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the target SSB index set completely includes the SSB index associated with the first RO.

[0303] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the target SSB index set does not completely include the SSB index associated with the first RO.

[0304] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO is the same as the SSB index included in the target SSB index set.

[0305] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO and the SSB index included in the target SSB index set are different.

[0306] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the modulo value of the SSB index associated with the first RO with respect to an integer greater than 1 is equal to an SSB index value included in the target SSB index set.

[0307] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the modulo value of the SSB index associated with the first RO with respect to an integer greater than 1 is not equal to any SSB index value included in the target SSB index set.

[0308] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes the difference between the SSB index value associated with the first RO and the maximum SSB index value included in the target SSB index set.

[0309] As an embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes the difference between the SSB index value associated with the first RO and the minimum SSB index value included in the target SSB index set.

[0310] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the relationship between the SSB index associated with the first RO and the target SSB index set is used to determine (or judge) the validity of the first RO.

[0311] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the validity of the first RO is related to the relationship between the SSB index associated with the first RO and the SSB index set.

[0312] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: whether the first RO is valid depends on the relationship between the SSB index associated with the first RO and the target SSB index set.

[0313] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the SSB index associated with the first RO belongs to the target SSB index set is one of the multiple conditions for the validity of the first RO.

[0314] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the validity of the first RO depends on the SSB index associated with the first RO belonging to the target SSB index set.

[0315] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: it is a necessary condition for the validity of the first RO that the SSB index associated with the first RO belongs to the target SSB index set.

[0316] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the condition for the validity of the first RO includes that the SSB index associated with the first RO belongs to the target SSB index set.

[0317] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: the SSB index associated with the first RO belongs to the target SSB index set is one of the multiple conditions for the validity of the first RO.

[0318] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: when the SSB index associated with the first RO belongs to the target SSB index set, the first RO is valid; when the SSB index associated with the first RO does not belong to the target SSB index set, the first RO is invalid.

[0319] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: when the target SSB index set completely includes the SSB index associated with the first RO, the first RO is valid; when the target SSB index set does not completely include the SSB index associated with the first RO, the first RO is invalid.

[0320] As an embodiment, the technical feature "the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set" includes: when the SSB index associated with the first RO and the SSB index included in the target SSB index set are the same, the first RO is valid; when the SSB index associated with the first RO and the SSB index included in the target SSB index set are not the same, the first RO is invalid.

[0321] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: one RO in the second RO set overlaps with the first RO in the time domain.

[0322] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: multiple ROs in the second RO set overlap with the first RO in the time domain.

[0323] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set is located on the time domain resources mapped by the first RO in the time domain.

[0324] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set completely or partially overlaps with the first RO in the time domain.

[0325] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set overlaps with the first RO in the time domain and is indicated by the TDD uplink and downlink configuration as a flexible full-duplex symbol.

[0326] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set that is completely or partially overlapped with the first RO in the time domain and is indicated by the TDD uplink and downlink configuration as a flexible full-duplex symbol.

[0327] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set overlaps with the first RO in the PRACH time slot in the time domain.

[0328] As an embodiment, the technical feature "at least one RO in the second RO set overlaps with the first RO in the time domain" includes: at least one RO in the second RO set overlaps with the first RO in the time domain and is frequency-divided with the first RO.

[0329] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the target SSB index set depends on the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0330] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the target SSB index set is related to the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0331] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the target SSB index set is linearly related to the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0332] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain is used to determine the target SSB index set.

[0333] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the target SSB index set includes the SSB index associated with each RO in at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0334] As an embodiment, the technical feature "the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain" includes: the target SSB index set is a set (or union) of SSB indexes associated with each RO in at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0335] Example 2

[0336] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 shown.

[0337] Attached Figure 2The network architecture of LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), and future 5G systems is described. The network architecture of LTE, LTE-A, and future 5G systems is called EPS (Evolved Packet System). The 5G NR or LTE network architecture may be referred to as 5GS (5G System) / EPS200 or some other appropriate terminology. 5GS / EPS200 may include one or more UE201, a UE 241 communicating with UE 201 via a sidelink, NG-RAN (Next Generation Radio Access Network) 202, 5G-CN (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet service 230. 5GS / EPS200 may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. Figure 2As shown, the 5GS / EPS200 provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks that provide circuit-switched services. NG-RAN 202 includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (Transmitter Receiver Point), or some other suitable term. gNB 203 provides an access point to 5G-CN / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, Personal Digital Assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband physical network devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. gNB 203 is connected to 5G-CN / EPC 210 via S1 / NG interface. 5G-CN / EPC 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212 and P-GW (Packet Data Network Gateway) / UPF 213.MME / AMF / SMF 211 is a control node that handles signaling between UE 201 and 5G-CN / EPC 210. In general, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF 212, and S-GW / UPF 212 itself is connected to P-GW / UPF 213. P-GW provides UE IP address allocation and other functions. P-GW / UPF 213 is connected to Internet services 230. Internet services 230 include operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet switching services.

[0338] As an embodiment, the UE201 corresponds to the terminal in this application.

[0339] As an embodiment, the UE 201 supports transmission in a flexible duplex mode.

[0340] As an embodiment, the gNB (eNB) 201 corresponds to the base station in this application.

[0341] As an embodiment, the gNB (eNB) 201 supports transmission in flexible duplex mode.

[0342] Example 3

[0343] Embodiment 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in the attached figure. Figure 3 shown.

[0344] Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a terminal (RSU (RoadSide Unit) in UE or V2X (Vehicle to Everything), vehicle-mounted equipment or vehicle-mounted communication module) and a base station (gNB, RSU in UE or V2X, vehicle-mounted equipment or vehicle-mounted communication module), or between two UEs is shown in three layers: Layer 1 (Layer 1, L1), Layer 2 (Layer 2, L2) and Layer 3 (Layer 3, L3). L1 is the lowest layer and implements various PHY (PHYsical layer) signal processing functions. L1 will be referred to as PHY 301 in this article. L2305 is above PHY 301 and is responsible for the link between the terminal and the base station, or between two UEs through PHY 301. L2305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the base station. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of terminals between base stations. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat reQuest process number). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between terminals. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling between the base station and the terminal to configure the lower layer. The radio protocol architecture of the user plane 350 includes layer 1 (L1) and layer 2 (L2). The radio protocol architecture for the terminal and the base station in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in L2355, the RLC sublayer 353 in L2355, and the MAC sublayer 352 in L2355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.L2355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support the diversity of services. Although not shown, the terminal may have several upper layers above L2355, including a network layer (e.g., an IP (Internet Protocol) layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0345] As an example, Figure 3 The wireless protocol architecture in is applicable to the terminal described in this application.

[0346] As an example, Figure 3 The wireless protocol architecture in is applicable to the base station described in this application.

[0347] As an embodiment, the first information block in the present application is generated in the RRC306, or MAC302, or MAC352, or the PHY301, or PHY351.

[0348] As an embodiment, the second information block in the present application is generated in the RRC306, or MAC302, or MAC352, or the PHY301, or PHY351.

[0349] As an embodiment, the third information block in the present application is generated in the RRC306, or MAC302, or MAC352, or the PHY301, or PHY351.

[0350] As an embodiment, the first capability information block in the present application is generated in the RRC306, or MAC302, or MAC352, or the PHY301, or PHY351.

[0351] Example 4

[0352] Embodiment 4 shows a schematic diagram of a terminal and a base station according to an embodiment of the present application, as shown in the attached Figure 4 shown.

[0353] The terminal (450) may include a controller / processor 490, a data source / buffer 480, a receive processor 452, a transmitter / receiver 456 and a transmit processor 455, the transmitter / receiver 456 including an antenna 460.

[0354] The base station (410) may include a controller / processor 440, a data source / buffer 430, a receive processor 412, a transmitter / receiver 416 and a transmit processor 415, wherein the transmitter / receiver 416 includes an antenna 420.

[0355] In DL (Downlink), the upper layer packets are provided to the controller / processor 440. The controller / processor 440 implements the functions of the L2 layer and above. In DL, the controller / processor 440 provides packet header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the terminal 450 based on various priority metrics. The controller / processor 440 is also responsible for HARQ operations, retransmission of lost packets, and high-level signaling to the terminal 450. The high-level information carried by the first information block, the second information block, and the third information block in the present application is generated in the controller / processor 440. The transmission processor 415 implements various signal processing functions for the L1 layer (i.e., the physical layer), including coding, interleaving, scrambling, modulation, power control / allocation, precoding, and physical layer control signaling generation, such as the physical layer signal carrying the first information block, the physical layer signal carrying the second information block, and the physical layer signal carrying the third information block are completed in the transmission processor 415. The generated modulation symbols are divided into parallel streams and each stream is mapped to a corresponding multi-carrier subcarrier and / or multi-carrier symbol, and then mapped to the antenna 420 by the transmit processor 415 via the transmitter 416 and transmitted in the form of a radio frequency signal. At the receiving end, each receiver 456 receives the radio frequency signal through its corresponding antenna 460, and each receiver 456 recovers the baseband information modulated onto the radio frequency carrier and provides the baseband information to the receive processor 452. The receive processor 452 implements various signal reception processing functions of the L1 layer. The signal reception processing function includes demodulating the physical layer signal carrying the first information block in the present application, the physical layer signal carrying the second information block in the present application, and the physical layer signal carrying the third information block based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK)) through the multi-carrier symbols in the multi-carrier symbol stream, and then descrambling, decoding and deinterleaving to recover the data or control transmitted by the base station 410 on the physical channel, and then providing the data and control signals to the controller / processor 490. The controller / processor 490 is responsible for the L2 layer and above, and the controller / processor 490 interprets the high-level information. This includes interpreting the high-level information carried by the first information block, the second information block, and the third information block. The controller / processor may be associated with a memory 480 that stores program codes and data. The memory 480 may be referred to as a computer-readable medium.

[0356] In uplink (UL) transmission, similar to downlink transmission, high-layer information including high-layer information carried by the first capability information block in the present application is generated by the controller / processor 490 and then implemented by the transmit processor 455 for various signal transmission processing functions of the L1 layer (i.e., physical layer). The physical layer signal carrying the first capability information block in the present application is mapped by the transmit processor 455 to the antenna 460 via the transmitter 456 and transmitted in the form of a radio frequency signal. The receiver 416 receives the radio frequency signal through its corresponding antenna 420, and each receiver 416 recovers the baseband information modulated onto the radio frequency carrier and provides the baseband information to the receive processor 412. The receive processor 412 implements various signal reception processing functions for the L1 layer (i.e., physical layer), including receiving and processing the physical layer signal carrying the first capability information block in the present application, and then providing data and / or control signals to the controller / processor 440. The functions of the L2 layer implemented in the controller / processor 440 include interpreting high-layer information such as the high-layer information carried by the first capability information block in the present application. The controller / processor may be associated with a cache 430 that stores program codes and data. The cache 430 may be a computer readable medium.

[0357] As an embodiment, the terminal 450 device includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the terminal 450 device at least: receives a first information block, the first information block indicates the symbol type of at least one symbol, and the first information block indicates a target sub-band; receives a second information block and a third information block, the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0358] As an embodiment, the terminal 450 device includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first information block, the first information block indicating the symbol type of at least one symbol, the first information block indicating a target sub-band; receiving a second information block and a third information block, the second information block indicating a first RO set, the third information block indicating a second RO set, the ROs in the first RO set occupying at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, the target SSB index set including the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0359] As an embodiment, the base station 410 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The base station 410 device at least: sends a first information block, the first information block indicates the symbol type of at least one symbol, and the first information block indicates a target sub-band; sends a second information block and a third information block, the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0360] As an embodiment, the base station 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first information block, the first information block indicating the symbol type of at least one symbol, the first information block indicating a target sub-band; sending a second information block and a third information block, the second information block indicating a first RO set, the third information block indicating a second RO set, the ROs in the first RO set occupying at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, the target SSB index set including the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0361] As an embodiment, the terminal 450 is a user equipment (UE).

[0362] As an embodiment, the terminal 450 is a user equipment supporting transmission in a flexible duplex mode.

[0363] As an embodiment, the base station 410 is a base station device (gNB / eNB).

[0364] As an embodiment, the base station 410 is a base station device supporting transmission in a flexible duplex mode.

[0365] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the first information block in the present application.

[0366] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the second information block in the present application.

[0367] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the third information block in the present application.

[0368] As an embodiment, the transmitter 456 (including the antenna 460), the transmission processor 455 and the controller / processor 490 are used to send the first capability information block in the present application.

[0369] As an embodiment, the transmitter 416 (including the antenna 420), the transmission processor 415 and the controller / processor 440 are used to send the first information block in the present application.

[0370] As an embodiment, the transmitter 416 (including the antenna 420), the transmission processor 415 and the controller / processor 440 are used to send the second information block in the present application.

[0371] As an embodiment, the transmitter 416 (including the antenna 420), the transmission processor 415 and the controller / processor 440 are used to send the third information block in the present application.

[0372] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the first capability information block in the present application.

[0373] Example 5

[0374] Embodiment 5 illustrates a flow chart of terminal and base station transmission according to an embodiment of the present application, as shown in the attached Figure 5 As shown in the attached Figure 5 In the example, base station N500 is a base station maintaining the serving cell of terminal U550. It should be noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0375] for Base Station N500 , sending a first information block in step S501, sending a second information block in step S502, sending a third information block in step S503, and receiving a first capability information block in step S504.

[0376] for Terminal U550 , receiving the first information block in step S551, receiving the second information block in step S552, receiving the third information block in step S553, and sending the first capability information block in step S554.

[0377] In embodiment 5, the first information block indicates the symbol type of at least one symbol, and the first information block indicates a target sub-band; the second information block indicates a first RO set, and the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain; the first capability information block indicates that the sender of the first capability information block supports the random access process in full-duplex symbols.

[0378] As an embodiment, the first information block is earlier than the second information block.

[0379] As an embodiment, the first information block is later than the second information block.

[0380] As an embodiment, the first information block is earlier than the third information block.

[0381] As an embodiment, the first information block is later than the third information block.

[0382] As an embodiment, the first information block is earlier than the first capability information block.

[0383] As an embodiment, the first information block is later than the first capability information block.

[0384] As an embodiment, the second information block is earlier than the third information block.

[0385] As an embodiment, the second information block is later than the third information block.

[0386] As an embodiment, the second information block is earlier than the first capability information block.

[0387] As an embodiment, the second information block is later than the first capability information block.

[0388] As an embodiment, the third information block is earlier than the first capability information block.

[0389] As an embodiment, the third information block is later than the first capability information block.

[0390] As an embodiment, the first information block and the second information block are transmitted through the same physical channel.

[0391] As an embodiment, the first information block and the second information block respectively include different IEs or fields included in the same IE.

[0392] As an embodiment, the first information block and the third information block are transmitted through the same physical channel.

[0393] As an embodiment, the first information block and the third information block respectively include different IEs or fields included in the same IE.

[0394] As an embodiment, the second information block and the third information block are transmitted through the same physical channel.

[0395] As an embodiment, the second information block and the third information block respectively include different IEs or fields included in the same IE.

[0396] As an embodiment, the first information block, the second information block and the third information block are transmitted through the same physical channel.

[0397] As an embodiment, the first information block, the second information block and the third information block respectively include different IEs or fields included in the same IE.

[0398] As an embodiment, the first capability information block is transmitted via an air interface or a wireless interface.

[0399] As an embodiment, the first capability information block includes all or part of high-layer signaling or physical layer signaling.

[0400] As an embodiment, the first capability information block includes all or part of the RRC signaling, or the first capability information block includes all or part of the MAC layer signaling.

[0401] As an embodiment, the first capability information block is transmitted via PUSCH or PUCCH (Physical Uplink Control Channel).

[0402] As an embodiment, the first capability information block is used to indicate the capability of the terminal in this application.

[0403] As an embodiment, the sender of the first capability information block is the terminal in this application.

[0404] As an embodiment, the first capability information block includes IE "UE-NR-Capability".

[0405] As an embodiment, the first capability information block includes IE "RF-Parameters", or the first capability information block includes IE "BandNR".

[0406] As an embodiment, the first capability information block includes IE "BandCombinationList", or the first capability information block includes IE "BandCombination".

[0407] As an embodiment, the first capability information block includes IE "Phy-Parameters".

[0408] As an embodiment, the first capability information block includes IE "FeatureSetUplink", or the first capability information block includes IE "FeatureSetUplinkPerCC".

[0409] As an embodiment, the first capability information block is only applied to TDD.

[0410] As an embodiment, the first capability information block is for a SBFD device.

[0411] As an embodiment, the first capability information block is per user equipment (per UE). As a subsidiary embodiment of the above embodiment, signaling the first capability information block per user equipment can reduce standard complexity.

[0412] As an embodiment, the first capability information block is frequency band or frequency band combination specific.

[0413] As an embodiment, the first capability information block is per band. As a subsidiary embodiment of the above embodiment, the transmission of the first capability information block per band can be optimized for different bands, thus simplifying product implementation.

[0414] As an embodiment, the first capability information block is per band combination. As a subsidiary embodiment of the above embodiment, the transmission of the first capability information block per band combination can be optimized for the band combination to achieve a balance between standard complexity and product implementation complexity.

[0415] As an embodiment, the first capability information block has different parameter values ​​between different frequency ranges (FR). As a subsidiary embodiment of the above embodiment, different frequency ranges have different parameter values ​​to optimize product implementation for the frequency range and improve flexibility.

[0416] As an embodiment, the first capability information block has the same parameter value between different frequency ranges. As a subsidiary embodiment of the above embodiment, different frequency ranges have the same parameter value to support a unified design and reduce standard complexity.

[0417] Example 6

[0418] Example 6 illustrates a schematic diagram of the conditions under which the first RO is effective according to an embodiment of the present application, as shown in the attached figure. Figure 6 As shown in the attached Figure 6 In the present invention, each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the first RO to be valid.

[0419] In Embodiment 6, the first RO in the present application and each RO included in the second RO set are respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the first RO to be valid.

[0420] As an embodiment, the validity of the first RO is judged based on the fact that each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources respectively and the SSB index associated with the first RO belongs to the target SSB index set. While taking into account the implementation limitations, the number of ROs on the SBFD symbol is designed to the maximum extent, thereby improving the probability of successful PRACH transmission.

[0421] As an embodiment, the technical feature "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources" includes: each RO included in the first RO and the second RO set occupies non-overlapping time-frequency resources respectively.

[0422] As an embodiment, the technical feature "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources" includes: each RO included in the first RO and the second RO set is respectively located on non-overlapping time-frequency resources.

[0423] As an embodiment, the technical feature of "each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources respectively" includes: each RO in the first RO and the second RO set that overlaps with the first RO in the time domain is mapped to non-overlapping frequency domain resources respectively, or each RO in the first RO and the second RO set that overlaps with the first RO in the time domain is frequency divided.

[0424] As an embodiment, the technical feature "each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources respectively" includes: the time domain resources and frequency domain resources mapped by the first RO are different from (or overlap with) at least one of the time domain resources and frequency domain resources mapped by each RO included in the second RO set.

[0425] As an embodiment, the technical feature "the first RO and each RO included in the second RO set are respectively mapped to non-overlapping time-frequency resources" includes: the time domain resources and frequency domain resources mapped by the first RO are different from (or overlap with) the time domain resources and frequency domain resources mapped by each RO included in the second RO set; or the time domain resources mapped by the first RO are the same (or overlap with) the time domain resources mapped by each RO included in the second RO set, but the frequency domain resources mapped by the first RO are different (or overlap with) the frequency domain resources mapped by each RO included in the second RO set; or the frequency domain resources mapped by the first RO are the same (or overlap with) the frequency domain resources mapped by each RO included in the second RO set, but the time domain resources mapped by the first RO are different (or overlap with) the time domain resources mapped by each RO included in the second RO set.

[0426] As an embodiment, the technical feature of "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources" includes: each RO included in the first RO and the second RO set is orthogonal.

[0427] As an embodiment, the technical feature of "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources" includes: the first RO set and the second RO set are orthogonal.

[0428] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the target SSB index set includes the SSB index associated with the first RO.

[0429] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the target SSB index set only includes the SSB index associated with the first RO.

[0430] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the SSB index associated with the first RO is a subset of the SSB index included in the target SSB index set.

[0431] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the value of the index included in the target SSB index set is the same as the value of the SSB index associated with the first RO.

[0432] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the SSB index value associated with the first RO is the same as the value of an SSB index in the target SSB index set.

[0433] As an embodiment, the technical feature "the SSB index associated with the first RO belongs to the target SSB index set" includes: the multiple SSB index values ​​associated with the first RO are the same as (or one-to-one correspond to) the values ​​of the multiple SSB indexes in the target SSB index set.

[0434] As an embodiment, the technical feature "the condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set" includes: the validity of the first RO depends on that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.

[0435] As an embodiment, the technical feature "the condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set" includes: the condition that the first RO and each RO included in the second RO set are respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set is used to determine (or judge) that the first RO is valid.

[0436] As an embodiment, the technical feature "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the validity of the first RO" includes: each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a necessary condition for the validity of the first RO.

[0437] As an embodiment, the technical feature "the condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set" includes: the condition that the first RO is valid includes that the first RO and each RO included in the second RO set are respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.

[0438] As an embodiment, the technical feature "each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the first RO to be valid" includes: each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is one of the multiple conditions for the first RO to be valid.

[0439] As an embodiment, the technical feature "the condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set" includes: the validity of the first RO depends on that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources, and the validity of the first RO also depends on that the SSB index associated with the first RO belongs to the target SSB index set.

[0440] As an embodiment, the technical feature "the condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set" includes: when the first RO and each RO included in the second RO set are respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, the first RO is valid.

[0441] Example 7

[0442] Embodiment 7 illustrates a schematic diagram of a second RO set according to an embodiment of the present application, as shown in the attached figure. Figure 7 As shown in the attached Figure 7In the figure, the vertical axis represents the frequency domain, the horizontal axis represents the time domain, the thick-line rectangle represents the target sub-band, the area between the two dotted lines represents the flexible full-duplex symbol indicated by the TDD uplink and downlink configuration, and the rectangular area filled with slashes represents all ROs included in the second RO set that overlap with at least one flexible full-duplex symbol in the time domain indicated by the TDD uplink and downlink configuration.

[0443] In Embodiment 7, all ROs included in the second RO set in the present application that overlap in the time domain with at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band.

[0444] As an embodiment, all ROs included in the second RO set that overlap in the time domain and at least one RO indicated as flexible full-duplex symbol by the TDD uplink and downlink configuration are set to belong to the target sub-band in the frequency domain, taking into account the impact of self-interference on adjacent frequency bands, thereby ensuring the performance of random access and backward compatibility.

[0445] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration" includes: multiple ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0446] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration" includes: each RO of the multiple ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0447] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration" includes: all ROs included in the second RO set that are located in the time domain on at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0448] As an embodiment, the technical feature "all ROs included in the second RO set that overlap with at least one RO in the time domain and indicated as flexible full-duplex symbol by the TDD uplink and downlink configuration" includes: all ROs included in the second RO set that occupy (or map to) at least one RO in the time domain that is indicated as flexible full-duplex symbol by the TDD uplink and downlink configuration.

[0449] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration" includes: all ROs included in the second RO set that completely or partially overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0450] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration" includes: all ROs included in the second RO set that overlap in the time domain and between time slots including at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration.

[0451] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one RO indicated as flexible full-duplex symbol by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band" includes: all ROs included in the second RO set that overlap in the time domain and at least one RO indicated as flexible full-duplex symbol by the TDD uplink and downlink configuration in the frequency domain are located within the target sub-band.

[0452] As an embodiment, the technical feature "all ROs included in the second RO set that overlap in the time domain and at least one RO indicated as a flexible full-duplex symbol by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band" includes: the target sub-band includes the frequency domain resources occupied by all ROs included in the second RO set that overlap in the time domain and at least one RO indicated as a flexible full-duplex symbol by the TDD uplink and downlink configuration.

[0453] Example 8

[0454] Embodiment 8 illustrates a schematic diagram of a first threshold value according to an embodiment of the present application, as shown in the attached figure. Figure 8 As shown in the attached Figure 8 In each case, the unfilled rectangle represents a time slot, "DL" represents that the symbol in the time slot is a downlink symbol without full-duplex symbol configured, "UL" represents that the symbol in the time slot is an uplink symbol, "FD" represents that the symbol in the time slot is a full-duplex symbol, and the small rectangle filled with gray represents the first RO; in case A, the first threshold represents the threshold of the interval length from the downlink symbol to the full-duplex symbol, in case B, the first threshold represents the threshold of the interval length from the uplink symbol to the full-duplex symbol, in case C, the first threshold represents the threshold of the interval length from the full-duplex symbol to the uplink symbol, and in case D, the first threshold represents the threshold of the interval length from the full-duplex symbol to the downlink symbol.

[0455] In Embodiment 8, the validity of the first RO in the present application depends on that the interval length between the first RO in the time domain and adjacent non-full-duplex symbols is greater than a first threshold, and the first threshold in the present application is configured or predefined and / or related to the user equipment capability.

[0456] As an embodiment, the conversion delay between full-duplex symbols and non-full-duplex symbols is considered when judging the validity of an RO, which improves the probability of successful transmission of PRACH while taking into account the implementation limitations, thereby reducing the implementation complexity of transmitting PRACH on full-duplex symbols.

[0457] As an embodiment, the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol is the interval length between the start of the first RO in the time domain and the start of an adjacent non-full-duplex symbol.

[0458] As an embodiment, the interval length between the first RO in the time domain and the adjacent non-full-duplex symbol is the interval length between the start of the first RO in the time domain and the end of the adjacent non-full-duplex symbol.

[0459] As an embodiment, the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol is the interval length between the end of the first RO in the time domain and the start of an adjacent non-full-duplex symbol.

[0460] As an embodiment, the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol is the interval length between the end of the first RO in the time domain and an end of an adjacent non-full-duplex symbol.

[0461] As an embodiment, the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol is the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol.

[0462] As an embodiment, the interval length between the first RO in the time domain and an adjacent non-full-duplex symbol is the interval length between the first RO in the time domain and any adjacent non-full-duplex symbol.

[0463] As an embodiment, the interval length between the first RO in the time domain and adjacent non-full-duplex symbols is the interval length between the PRACH time slot to which the first RO belongs and adjacent non-full-duplex symbols in the time domain.

[0464] As an embodiment, the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is the interval length between the time slot where the first RO overlaps and adjacent non-full-duplex symbols in the time domain.

[0465] As an embodiment, the interval length between the first RO and the adjacent non-full-duplex symbol in the time domain is the interval length between the start of the first RO and the last non-full-duplex symbol in the time domain. As a subsidiary embodiment of the above embodiment, the interval length between the first RO and the last non-full-duplex symbol is considered to meet the requirements of different coverage ranges on transmission delay while ensuring the conversion time between the non-full-duplex symbol and the full-duplex symbol.

[0466] As an embodiment, the interval length between the first RO in the time domain and the adjacent non-full-duplex symbol is the interval length between the end of the first RO in the time domain and the next non-full-duplex symbol. As a subsidiary embodiment of the above embodiment, the interval length between the non-full-duplex symbol after and after is considered to ensure the conversion time between the full-duplex symbol and the non-full-duplex symbol, thereby reducing the implementation complexity.

[0467] As an embodiment, the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is expressed as an absolute time length.

[0468] As an embodiment, the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is expressed in the number of symbols.

[0469] As an embodiment, the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is represented by the number of symbols corresponding to the subcarrier interval of a preamble.

[0470] As an embodiment, the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is expressed as the number of symbols corresponding to the subcarrier spacing of the active uplink BWP.

[0471] As an embodiment, the non-full-duplex symbol is a non-SBFD symbol.

[0472] As an embodiment, the “non-full-duplex symbol” and the “non-SBFD symbol” are equivalent or interchangeable.

[0473] As an embodiment, the non-full-duplex symbol is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0474] As an embodiment, the non-full-duplex symbol is a time domain symbol that is not configured with SBFD.

[0475] As an embodiment, the non-full-duplex symbol is a symbol that does not overlap with the SBFD time slot in the time domain.

[0476] As an embodiment, the non-full-duplex symbol is a symbol that does not overlap with the full-duplex symbol.

[0477] As an embodiment, the non-full-duplex symbol is a time domain symbol that does not support full-duplex.

[0478] As an embodiment, the non-full-duplex symbol is a time domain symbol that can only be used for uplink transmission or downlink transmission or protection interval.

[0479] As an embodiment, the non-full-duplex symbol is a time domain symbol that is not indicated (or provided) by signaling for configuring SBFD.

[0480] As an embodiment, the non-full-duplex symbol is a time domain symbol that is not indicated (or provided) by the first information block.

[0481] As an embodiment, the non-full-duplex symbol is a symbol indicated as a downlink or flexible symbol by the TDD uplink and downlink configuration and cannot be used for uplink transmission.

[0482] As an embodiment, the non-full-duplex symbol is a symbol indicated as a downlink symbol by the TDD uplink and downlink configuration and cannot be used for uplink transmission.

[0483] As an embodiment, the non-full-duplex symbol is a symbol indicated as uplink by TDD uplink and downlink configuration.

[0484] As an embodiment, the non-full-duplex symbol is a symbol other than the full-duplex symbol.

[0485] As an embodiment, the non-full-duplex symbol is a time domain symbol that is not configured with the target sub-frequency band.

[0486] As an embodiment, the adjacent non-full-duplex symbol is the previous non-full-duplex symbol.

[0487] As an embodiment, the adjacent non-full-duplex symbol is the next non-full-duplex symbol.

[0488] As an embodiment, the adjacent non-full-duplex symbol is a previous non-full-duplex symbol that is closest to the adjacent non-full-duplex symbol.

[0489] As an embodiment, the adjacent non-full-duplex symbol is a subsequent non-full-duplex symbol that is closest to the adjacent non-full-duplex symbol.

[0490] As an embodiment, the adjacent non-full-duplex symbol is the previous or next downlink symbol.

[0491] As an embodiment, the adjacent non-full-duplex symbol is the previous or next symbol indicated as downlink by the TDD uplink and downlink configuration.

[0492] As an embodiment, the adjacent non-full-duplex symbol is a previous or next downlink symbol that is not indicated as a full-duplex symbol.

[0493] As an embodiment, the adjacent non-full-duplex symbol is the previous or next symbol that is not indicated as a full-duplex symbol by the first information block and is indicated as a downlink symbol by the TDD uplink and downlink configuration.

[0494] As an embodiment, the adjacent non-full-duplex symbol is a previous or next uplink symbol.

[0495] As an embodiment, the adjacent non-full-duplex symbol is the previous or next symbol indicated as uplink by the TDD uplink and downlink configuration.

[0496] As an embodiment, the first threshold is a non-negative integer.

[0497] As an embodiment, the first threshold may be a non-integer.

[0498] As an embodiment, the unit of the first threshold is seconds or milliseconds.

[0499] As an embodiment, the first threshold represents the number of symbols.

[0500] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than a first threshold" includes: the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than the first threshold is used to determine or judge that the first RO is valid.

[0501] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than a first threshold" includes: the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than the first threshold is a necessary condition for the first RO to be valid.

[0502] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols being greater than a first threshold" includes: the condition that the first RO is valid includes that the length of the interval between the first RO in the time domain and adjacent non-full-duplex symbols is not less than (or greater than) the first threshold.

[0503] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full-duplex symbol being greater than a first threshold" includes: the validity of the first RO depends on the start of the first RO in the time domain being at least N1 symbols later than the adjacent non-full-duplex symbol, and N1 is the first threshold.

[0504] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full-duplex symbol being greater than a first threshold" includes: the validity of the first RO depends on the cutoff of the first RO in the time domain being at least N2 symbols earlier than the adjacent non-full-duplex symbol, and N2 is the first threshold.

[0505] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO and the adjacent non-full-duplex symbols in the time domain being greater than a first threshold" includes: when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the uplink sub-band in the frequency domain is not less than a configured or predefined threshold and the start of the first RO in the time domain is N1 symbols later than the adjacent non-full-duplex symbol, the first RO is valid, and N1 is the first threshold.

[0506] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO and adjacent non-full-duplex symbols in the time domain being greater than a first threshold" includes: when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the uplink sub-band in the frequency domain is not less than a configured or predefined threshold and the end of the first PRACH opportunity in the time domain is N2 symbols earlier than the adjacent non-full-duplex symbol, the first RO is valid, and N2 is the first threshold.

[0507] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full-duplex symbols is greater than the first threshold" includes: when the first RO belongs to an uplink sub-band in the frequency domain and the start of the first RO in the time domain is N1 symbols later than the adjacent non-full-duplex symbol and the end of the first RO in the time domain is N2 symbols earlier than the adjacent non-full-duplex symbol, the first RO is valid, N1 or N2 is the first threshold, N1 is a non-negative integer, and N2 is a non-negative integer.

[0508] As an embodiment, the technical feature "the validity of the first RO depends on the length of the interval between the first RO and the adjacent non-full-duplex symbols in the time domain being greater than a first threshold" includes: when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the uplink sub-band in the frequency domain is not less than a configured or predefined threshold and the start of the first RO in the time domain is N1 symbols later than the adjacent non-full-duplex symbol and the end of the first PRACH opportunity in the time domain is N2 symbols earlier than the adjacent non-full-duplex symbol, the first PRACH opportunity is valid, N1 or N2 is the first threshold, N1 is a non-negative integer, and N2 is a non-negative integer.

[0509] As an embodiment, the first threshold is configured or predefined.

[0510] As an embodiment, the first threshold is related to the capability of the user equipment.

[0511] As an embodiment, the first threshold is configurable and related to the user equipment capability.

[0512] As an embodiment, the first threshold is configured including: higher layer signaling or higher layer parameters indicating the first threshold.

[0513] As an embodiment, the first threshold is configured including: the first threshold depends on higher layer signaling or higher layer parameters.

[0514] As an embodiment, the first threshold is configured to include: the first threshold depends on the subcarrier spacing, and higher layer signaling or higher layer parameters indicate the subcarrier spacing on which the first threshold depends.

[0515] As an embodiment, the first threshold is configured to include: higher layer signaling or higher layer parameters indicating whether the first threshold is equal to the value reported by the user equipment capability.

[0516] As an embodiment, the first threshold is configured to include: higher layer signaling or higher layer parameters indicating an offset value between the first threshold and a value reported by the user equipment capability.

[0517] As an embodiment, the first threshold is configured including: a parameter for calculating the first threshold includes a first parameter value, and a higher layer signaling or a higher layer parameter indicates the first parameter value.

[0518] As an embodiment, the first threshold is configured to include: the first threshold is linearly related to a first parameter value, and a higher layer signaling or a higher layer parameter indicates the first parameter value.

[0519] As an embodiment, the first threshold being predefined includes: the first threshold being fixed.

[0520] As an embodiment, the first threshold being predefined includes: the first threshold being hard coded in the standard.

[0521] As an embodiment, the first threshold being predefined includes: a relationship between the first threshold and a value of another parameter is fixed.

[0522] As an embodiment, the first threshold is predefined including: the corresponding relationship between the first threshold and the subcarrier spacing is fixed.

[0523] As an embodiment, the first threshold is predefined including: a parameter for calculating the first threshold includes a first parameter value, and the first parameter value is a fixed value.

[0524] As an embodiment, the first threshold value is related to the user equipment capability and includes: the first threshold value is equal to the value reported by the user equipment capability.

[0525] As an embodiment, the first threshold value is related to the user equipment capability and includes: the first threshold value is not less than the value reported by the user equipment capability.

[0526] As an embodiment, the first threshold is related to the user equipment capability and includes: parameters for calculating the first threshold include a first parameter value, and the first parameter value is equal to the value reported by the user equipment capability.

[0527] As an embodiment, the first threshold value is related to the user equipment capability, including: the first threshold value is linearly correlated with a first parameter value, and the first parameter value is equal to the value reported by the user equipment capability.

[0528] As an embodiment, the first threshold is related to the user equipment capability and also depends on whether the user equipment capability supports SBFD or whether the user equipment capability supports transmission of PRACH in downlink full-duplex symbols.

[0529] As an embodiment, the network configures the first threshold to take into account the conversion delay between different hardware or algorithm implementations when processing full-duplex symbols and non-full-duplex symbols on the network side, thereby ensuring effective operation of self-interference elimination of the network.

[0530] As an embodiment, the predefined first threshold may support setting a fixed relatively large threshold, thereby simplifying the design while ensuring that the conversion and processing delays on the network and user sides are met.

[0531] As an embodiment, associating the first threshold with the user equipment capability can ensure that the conversion and processing delay of the user equipment are met, thereby reducing the implementation complexity of the user equipment.

[0532] As an embodiment, the first threshold is associated with the user equipment capability and is configured by the network at the same time, so as to ensure that the conversion and processing delay of the user equipment are met, while taking into account different network side implementations, thereby optimizing the setting of the first threshold, avoiding accidental damage to valid PRACH opportunities, and improving the capacity of PRACH.

[0533] As an embodiment, the first threshold is equal to a larger value compared between a first candidate interval and a second candidate interval, the first candidate interval is configured or related to the subcarrier interval of the random access preamble, and the second candidate interval is related to the user equipment capability.

[0534] As an embodiment, the first threshold is equal to the larger value of Ngap and the first capability value, Ngap is related to the subcarrier spacing of the random access preamble, and the first capability value is related to the user equipment capability.

[0535] Example 9

[0536] Embodiment 9 illustrates a schematic diagram of a second threshold value according to an embodiment of the present application, as shown in the attached figure. Fig. 9 As shown in the attached Fig. 9 In FIG. 8 , the vertical axis represents the frequency domain, the thick-line rectangle represents the target sub-band, the rectangle filled with oblique lines represents the first RO, and the second threshold represents the threshold of the frequency interval from the boundary of the target sub-band to the target sub-band.

[0537] In Embodiment 9, the validity of the first RO in the present application depends on that the first RO belongs to the target sub-band in the frequency domain and that the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold in the present application is predefined or configured.

[0538] As an embodiment, the effect of self-interference on adjacent frequency bands is considered when judging the validity of an RO, thereby ensuring effective transmission of the PRACH and improving random access performance.

[0539] As an embodiment, the technical feature “the first RO belongs to the target sub-frequency band in the frequency domain” includes: all frequency domain resources occupied by the first RO are located in the target sub-frequency band.

[0540] As an embodiment, the technical feature "the first RO belongs to the target sub-frequency band in the frequency domain" includes: the target sub-frequency band includes all frequency domain resources occupied by the first RO.

[0541] As an embodiment, the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is the frequency domain interval between the lowest frequency (or the lowest indexed subcarrier) of the first RO and at least one boundary of the target sub-band.

[0542] As an embodiment, the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is the frequency domain interval between the highest frequency (or the highest indexed sub-carrier) of the first RO and at least one boundary of the target sub-band.

[0543] As an embodiment, the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is the frequency domain interval between the lowest frequency (or the lowest indexed sub-carrier) of the first RO and the lowest frequency (or the included lowest indexed sub-carrier) of the target sub-band.

[0544] As an embodiment, the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is the frequency domain interval between the highest frequency (or the highest indexed sub-carrier) of the first RO and the highest frequency (or the included highest indexed sub-carrier) of the target sub-band.

[0545] As an embodiment, the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band includes the frequency domain interval between the lowest frequency (or the lowest indexed subcarrier) of the first RO and the lowest frequency (or the included lowest indexed subcarrier) of the target sub-band and the frequency domain interval between the highest frequency (or the highest indexed subcarrier) of the first RO and the highest frequency (or the included highest indexed subcarrier) of the target sub-band.

[0546] As an embodiment, the technical feature "the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is greater than the second threshold.

[0547] As an embodiment, the technical feature "the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is not less than a second threshold" includes: the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is greater than or equal to the second threshold.

[0548] As an embodiment, the technical feature "the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the frequency domain interval between all frequency resources (or all sub-carriers) included in the first RO in the frequency domain and the lowest frequency (or the lowest indexed sub-carrier included) of the target sub-band is not less than the second threshold.

[0549] As an embodiment, the technical feature "the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is not less than a second threshold" includes: the frequency domain interval between all frequency resources (or all sub-carriers) included in the first RO in the frequency domain and the highest frequency (or the highest indexed sub-carrier included) of the target sub-band is not less than the second threshold.

[0550] As an embodiment, the technical feature "the frequency domain interval between the first RO in the frequency domain and at least one boundary of the target sub-band is not less than a second threshold" includes: the frequency domain interval between all frequency resources (or all sub-carriers) included in the frequency domain of the first RO and the lowest frequency of the target sub-band (or the lowest indexed sub-carrier included) is not less than the second threshold; the frequency domain interval between all frequency resources (or all sub-carriers) included in the frequency domain of the first RO and the highest frequency (or the highest indexed sub-carrier included) of the target sub-band is not less than the second threshold.

[0551] As an embodiment, the technical feature "the frequency domain interval between the first RO and at least one boundary of the target subband in the frequency domain is not less than a second threshold" includes: the frequency domain interval between the highest frequency (or the highest indexed subcarrier) of the first RO and the highest frequency (or the included highest indexed subcarrier) of the target subband is not less than the second threshold; the frequency domain interval between the lowest frequency (or the lowest indexed subcarrier) of the first RO and the lowest frequency (or the included lowest indexed subcarrier) of the target subband is not less than the second threshold.

[0552] As an embodiment, the technical feature "the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain, and the validity of the first RO depends on that the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than the second threshold.

[0553] As an embodiment, the technical feature "the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than the second threshold is used to determine (or judge) that the first RO is valid.

[0554] As an embodiment, the technical feature "the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than the second threshold, which is a necessary condition for the validity of the first RO.

[0555] As an embodiment, the technical feature "the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: the condition for the validity of the first RO includes that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than the second threshold.

[0556] As an embodiment, the technical feature "the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold" includes: when the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than the second threshold, the first RO is valid.

[0557] As an embodiment, the second threshold is a non-negative integer.

[0558] As an embodiment, the second threshold may be a non-integer.

[0559] As an embodiment, the unit of the second threshold is Hertz or kilohertz.

[0560] As an embodiment, the second threshold represents the number of subcarriers.

[0561] As an embodiment, the second threshold is configured including: higher layer signaling or higher layer parameters indicating the second threshold.

[0562] As an embodiment, the second threshold is configured including: the second threshold depends on higher layer signaling or higher layer parameters.

[0563] As an embodiment, the second threshold is configured to include: the second threshold depends on the subcarrier spacing, and higher layer signaling or higher layer parameters indicate the subcarrier spacing on which the second threshold depends.

[0564] As an embodiment, the second threshold is configured including: parameters for calculating the second threshold include a second parameter value, and higher layer signaling or a higher layer parameter indicates the second parameter value.

[0565] As an embodiment, the second threshold being predefined includes: the second threshold being fixed.

[0566] As an embodiment, the second threshold being predefined includes: the second threshold being hard coded in the standard.

[0567] As an embodiment, the second threshold being predefined includes: a relationship between the second threshold and a value of another parameter is fixed.

[0568] As an embodiment, the second threshold is predefined including: the corresponding relationship between the second threshold and the subcarrier spacing is fixed.

[0569] As an embodiment, the second threshold is predefined, including: a parameter for calculating the second threshold includes a second parameter value, and the second parameter value is a fixed value.

[0570] As an embodiment, the second threshold is related to the subcarrier spacing of the leading edge.

[0571] As an embodiment, the second threshold is related to the subcarrier spacing of the target sub-band.

[0572] As an embodiment, the second threshold is related to the subcarrier spacing of the BWP.

[0573] As an embodiment, the second threshold and the leading subcarrier spacing are related to the subcarrier spacing of the target sub-band.

[0574] Example 10

[0575] Embodiment 10 illustrates a schematic diagram of a first capability information block according to an embodiment of the present application, as shown in the attached Fig.10 As shown in the attached Fig.10In the figure, the horizontal axis represents time, the cross-line filled rectangle represents a full-duplex symbol, the unfilled rectangular area represents a non-full-duplex symbol, and the first capability information block indicates that the sender of the first capability information block supports the random access process in the full-duplex symbol.

[0576] In embodiment 10, the first capability information block in the present application indicates that the sender of the first capability information block supports a random access procedure in full-duplex symbols.

[0577] As an embodiment, the first capability information block is introduced to indicate that the sender of the first capability information block supports the random access process in full-duplex symbols, which increases flexibility and improves the robustness of the system.

[0578] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access procedure in full-duplex symbols" includes: the first capability information block indicates whether the sender of the first capability information block supports the random access procedure in full-duplex symbols.

[0579] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access procedure in full-duplex symbols" includes: all or part of the first capability information block is used to explicitly or implicitly indicate that the sender of the first capability information block supports the random access procedure in full-duplex symbols.

[0580] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access process in the full-duplex symbol" includes: the sender of the first capability information block is a device supporting SBFD, and the device supporting SBFD can perform a random access process on the SBFD symbol.

[0581] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access procedure in full-duplex symbols" includes: a parameter or field included in the first capability information block is equal to a given value used to indicate that the sender of the first capability information block supports the random access procedure in full-duplex symbols.

[0582] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access procedure in full-duplex symbols" includes: the first capability information block includes a field indicating that the sender of the first capability information block supports the random access procedure in full-duplex symbols.

[0583] As an embodiment, the technical feature "the first capability information block indicates that the sender of the first capability information block supports the random access process in full-duplex symbols" includes: the first capability information block indicates that the sender of the first capability information block has the ability of random access in full-duplex symbols.

[0584] Embodiment 11

[0585] Embodiment 11 illustrates a schematic diagram of mapping the first RO set and the second RO set to the synchronous broadcast signal according to an embodiment of the present application, as shown in the attached figure. Fig.11 As shown in the attached Fig.11 As shown, each rectangle represents a transmission of a synchronous broadcast signal, wherein the numbers #0, #1 and #2 represent index values ​​of the synchronous broadcast signal, the upper dotted ellipse represents the RO in the first RO set, and the lower dotted ellipse represents the RO in the second RO set.

[0586] In Embodiment 11, the ROs in the first RO set and the ROs in the second RO set in the present application are respectively mapped to a synchronous broadcast signal.

[0587] As an embodiment, the ROs in the first RO set and the ROs in the second RO set are mapped separately to the synchronous broadcast signal, thereby improving the PRACH capacity while avoiding adverse effects on other users and ensuring backward compatibility.

[0588] As an embodiment, the technical feature of "ROs in the first RO set and ROs in the second RO set are respectively mapped to a synchronous broadcast signal" includes: ROs in the first RO set and ROs in the second RO set are independently mapped to a synchronous broadcast signal.

[0589] As an embodiment, the technical feature "the ROs in the first RO set and the ROs in the second RO set are respectively mapped to the synchronized broadcast signal" includes: the ROs in the first RO set that are located on the full-duplex symbols in the time domain and the ROs in the second RO set that are located on the non-full-duplex symbols in the time domain are respectively mapped to the synchronized broadcast signal.

[0590] As an embodiment, the technical feature "the ROs in the first RO set and the ROs in the second RO set are respectively mapped to the synchronized broadcast signal" includes: the ROs in the first RO set that are located in the time domain on the downlink or flexible full-duplex symbols indicated by the TDD uplink and downlink configuration and the ROs in the second RO set that are located in the time domain on the non-full-duplex symbols or in the time domain on the flexible full-duplex symbols indicated by the TDD uplink and downlink configuration are respectively mapped to the synchronized broadcast signal.

[0591] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are respectively mapped to a synchronous broadcast signal" includes: ROs in the first RO set and ROs in the second RO set are respectively mapped to a synchronous broadcast signal within a time window. As a subsidiary embodiment of the above embodiment, the advantage of doing so is to continue to use the existing design of the association period and reduce the standard workload.

[0592] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are respectively mapped to the synchronous broadcast signal" includes: ROs in the first RO set located in the time domain on the downlink or flexible full-duplex symbol indicated by the TDD uplink and downlink configuration and ROs in the second RO set located in the time domain on the non-full-duplex symbol or in the time domain on the flexible full-duplex symbol indicated by the TDD uplink and downlink configuration are respectively mapped to the synchronous broadcast signal within a time window. As a subsidiary embodiment of the above embodiment, the advantage of doing so is to continue to use the existing design of the association period and reduce the standard workload.

[0593] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are respectively mapped to the synchronous broadcast signal" includes: ROs in the first RO set located in the time domain on the full-duplex symbol indicated as downlink or flexible by the TDD uplink and downlink configuration and ROs in the second RO set located in the time domain on the non-full-duplex symbol or in the time domain on the full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration are respectively mapped to the synchronous broadcast signal in their respective time windows. As a subsidiary embodiment of the above embodiment, the advantage of doing so is that an independent association period is adopted to improve flexibility and optimize PRACH capacity performance.

[0594] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are respectively mapped to synchronized broadcast signals" includes: the mapping of ROs in the first RO set and synchronized broadcast signals does not affect the mapping of ROs in the second RO set and synchronized broadcast signals.

[0595] As an embodiment, the technical feature of "ROs in the first RO set and ROs in the second RO set are respectively mapped to a synchronous broadcast signal" includes: ROs in the first RO set and ROs in the second RO set are respectively mapped to an index of a synchronous broadcast signal.

[0596] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are each mapped to a synchronous broadcast signal" includes: ROs in the first RO set and ROs in the second RO set are each mapped according to the same sorting rule and index of the synchronous broadcast signal.

[0597] As an embodiment, the technical feature "ROs in the first RO set and ROs in the second RO set are respectively mapped to a synchronous broadcast signal" includes: the ROs in the first RO set and the ROs in the second RO set are respectively sorted independently, and then respectively mapped to a synchronous broadcast signal.

[0598] As an embodiment, the technical feature "the ROs in the first RO set and the ROs in the second RO set are respectively mapped to the synchronized broadcast signal" includes: the ROs in the first RO set are associated with the synchronized broadcast signal in sequence according to a given order, and the ROs in the second RO set are also associated with the synchronized broadcast signal in sequence according to a given order.

[0599] As an embodiment, the technical feature "the ROs in the first RO set and the ROs in the second RO set are respectively mapped to the synchronized broadcast signal" includes: the synchronized broadcast block index and the RO in the first RO set are mapped in sequence according to the mapping order of first the leading index in one RO, then the frequency resource index of the frequency-divided RO, then the time domain resource index of the time-divided RO in a PRACH time slot, and finally the index of the PRACH time slot; the synchronized broadcast block index and the RO in the second RO set are mapped in sequence according to the mapping order of first the leading index in one RO, then the frequency resource index of the frequency-divided RO, then the time domain resource index of the time-divided RO in a PRACH time slot, and finally the index of the PRACH time slot.

[0600] As an embodiment, the technical feature "the ROs in the first RO set and the ROs in the second RO set are respectively mapped to the synchronized broadcast signals" includes: the synchronized broadcast blocks are mapped in sequence according to the indexes of 0, 1... and the ROs in the first RO set according to the mapping order of first the leading index in an RO, then the frequency resource index of the frequency-divided RO, then the time domain resource index of the time-divided RO in a PRACH time slot, and finally the index of the PRACH time slot; the synchronized broadcast blocks are mapped in sequence according to the indexes of 0, 1... and the ROs in the second RO set according to the mapping order of first the leading index in an RO, then the frequency resource index of the frequency-divided RO, then the time domain resource index of the time-divided RO in a PRACH time slot, and finally the index of the PRACH time slot.

[0601] Example 12

[0602] Embodiment 12 illustrates a structural block diagram of a processing device used in a terminal according to an embodiment of the present application, as shown in the attached Fig.12 As shown in the attached Fig.12 In the embodiment, the processing device 1200 in the terminal includes a first receiver 1201 and a first transmitter 1202. The first receiver 1201 includes the Figure 4 The transmitter / receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 in the present application; the first transmitter 1202 includes Figure 4 The transmitter / receiver 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490.

[0603] In Example 12, a first receiver 1201 receives a first information block, wherein the first information block indicates a symbol type of at least one symbol, and the first information block indicates a target sub-band; receives a second information block and a third information block, wherein the second information block indicates a first RO set, and the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0604] As an embodiment, each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the first RO to be valid.

[0605] As an embodiment, all ROs included in the second RO set that overlap in the time domain with at least one RO indicated as a flexible full-duplex symbol by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band.

[0606] As an embodiment, the validity of the first RO depends on that the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is greater than a first threshold, and the first threshold is configured or predefined and / or related to user equipment capabilities.

[0607] As an embodiment, the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

[0608] As an embodiment, the first transmitter 1202 sends a first capability information block, wherein the first capability information block indicates that a sender of the first capability information block supports a random access procedure in a full-duplex symbol.

[0609] As an embodiment, the ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

[0610] Embodiment 13

[0611] Embodiment 13 illustrates a structural block diagram of a processing device used in a base station according to an embodiment of the present application, as shown in the attached figure. Fig.13 As shown in the attached Fig.13 In the present application, the processing device 1300 in the base station includes a second transmitter 1301 and a second receiver 1302. The second transmitter 1301 includes Figure 4 The transmitter / receiver 416 (including the antenna 460), the transmission processor 415 and the controller / processor 440 in the second receiver 1302 include the attached Figure 4 The transmitter / receiver 416 (including the antenna 460), the receiving processor 412 and the controller / processor 440 in the embodiment.

[0612] In Example 13, the second transmitter 1301 sends a first information block, wherein the first information block indicates a symbol type of at least one symbol, and the first information block indicates a target sub-band; sends a second information block and a third information block, wherein the second information block indicates a first RO set, and the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; wherein the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

[0613] As an embodiment, each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set, which is a condition for the first RO to be valid.

[0614] As an embodiment, all ROs included in the second RO set that overlap in the time domain with at least one RO indicated as a flexible full-duplex symbol by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-band.

[0615] As an embodiment, the validity of the first RO depends on that the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is greater than a first threshold, and the first threshold is configured or predefined and / or related to user equipment capabilities.

[0616] As an embodiment, the validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and the frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

[0617] As an embodiment, the second receiver 1302 receives a first capability information block, wherein the first capability information block indicates that a sender of the first capability information block supports a random access procedure in full-duplex symbols.

[0618] As an embodiment, the ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

[0619] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The terminal or base station or UE or terminal in the present application includes but is not limited to mobile phones, tablet computers, notebooks, Internet cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft, test devices, test equipment. Equipment, test instruments and other equipment. The base station equipment or base station or network side equipment in the present application includes but is not limited to macrocellular base stations, microcellular base stations, home base stations, relay base stations, eNBs, gNBs, transmission and reception nodes TRPs, relay satellites, satellite base stations, air base stations, test devices, test equipment, test instruments and other equipment.

[0620] It should be understood by those skilled in the art that the present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A method used in a terminal, characterized in that: include: receiving a first information block, the first information block indicating a symbol type of at least one symbol, the first information block indicating a target sub-band; receiving a second information block and a third information block, wherein the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; Among them, the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

2. The method according to claim 1, characterized in that: The condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.

3. The method according to claim 1 or 2, characterized in that All ROs included in the second RO set that overlap in the time domain with at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-frequency band.

4. The method according to any one of claims 1 to 3, characterized in that: The validity of the first RO depends on that the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is greater than a first threshold, where the first threshold is configured or predefined and / or related to the user equipment capability.

5. The method according to any one of claims 1 to 4, characterized in that: The validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and a frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

6. The method according to any one of claims 1 to 5, characterized in that: A first capability information block is sent, wherein the first capability information block indicates that a sender of the first capability information block supports a random access procedure in full-duplex symbols.

7. The method according to any one of claims 1 to 6, characterized in that: The ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

8. A terminal, characterized in that: The terminal includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the terminal to execute the method described in any one of claims 1-7.

9. A method used in a base station, characterized in that: include: Sending a first information block, wherein the first information block indicates a symbol type of at least one symbol, and the first information block indicates a target sub-band; Sending a second information block and a third information block, wherein the second information block indicates a first RO set, the third information block indicates a second RO set, and the ROs in the first RO set occupy at least one full-duplex symbol in the time domain; Among them, the first RO is an RO included in the first RO set, and the first RO occupies at least one full-duplex symbol indicated as flexible by the TDD uplink and downlink configuration in the time domain; the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set, and the target SSB index set includes the SSB index associated with at least one RO in the second RO set that overlaps with the first RO in the time domain.

10. The method according to claim 9, characterized in that The condition that the first RO is valid is that each RO included in the first RO and the second RO set is respectively mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.

11. The method according to claim 9 or 10, characterized in that All ROs included in the second RO set that overlap in the time domain with at least one flexible full-duplex symbol indicated by the TDD uplink and downlink configuration in the frequency domain belong to the target sub-frequency band.

12. The method according to any one of claims 9 to 11, characterized in that: The validity of the first RO depends on that the interval length between the first RO and adjacent non-full-duplex symbols in the time domain is greater than a first threshold, where the first threshold is configured or predefined and / or related to the user equipment capability.

13. The method according to any one of claims 9 to 12, characterized in that: The validity of the first RO depends on that the first RO belongs to the target sub-band in the frequency domain and a frequency domain interval between the first RO and at least one boundary of the target sub-band in the frequency domain is not less than a second threshold, and the second threshold is predefined or configured.

14. The method according to any one of claims 9 to 13, characterized in that: A first capability information block is received, the first capability information block indicating that a sender of the first capability information block supports a random access procedure in full-duplex symbols.

15. The method according to any one of claims 9 to 14, characterized in that: The ROs in the first RO set and the ROs in the second RO set are respectively mapped to a synchronous broadcast signal.

16. A base station, characterized in that: The base station comprises: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code comprises computer instructions, and the one or more processors call the computer instructions so that the base station executes the method as described in any one of claims 9-15.

Images