Method and device for node used for wireless communication

Abstract

The present application discloses a method and device for a node used for wireless communication. The method comprises: a node receives a first information block and a second information block, the first information block comprising multiple PRACH occasions, and the second information block indicating at least one full-duplex symbol. A first PRACH occasion is one of the multiple PRACH occasions indicated by the first information block, and the first PRACH occasion occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH occasion depends on a time interval between the first PRACH occasion and a first symbol being greater than a target interval, and the target interval is related to a subcarrier spacing of a random access preamble; and the first symbol is a downlink symbol indicated by a previous non-full-duplex TDD uplink and downlink configuration. The present application improves the random access capacity.

Description

A method and device in a node for wireless communication

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 20, 2024, with application number 202410325260.X and invention name “A method and device in a node for wireless communication”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] The application scenarios of future wireless communication systems are becoming increasingly diverse, and different scenarios place varying performance requirements on the systems. To meet the diverse performance demands of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) Plenary #72 decided to conduct research on New Radio (NR) (or 5G). The WI (Work Item) for New Radio (NR) technology was approved at 3GPP RAN #75, initiating standardization work on NR. The 3GPP RAN #86 Plenary decided to initiate work on the SI (Study Item) and WI (Work Item) for NR Rel-17, and the 3GPP RAN #94e Plenary approved the SI and WI for NR Rel-18. The 3GPP RAN #102 Plenary decided to initiate work on the SI and WI for NR Rel-19.

[0004] NR Rel-19 includes Wi-Fi that supports non-overlapping sub-band full duplex (SBFD). Non-overlapping sub-band full duplex is also one of the technologies that 6G may support. Summary of the Invention

[0005] In existing NR systems, spectrum resources are statically divided into FDD and TDD spectrum. For TDD spectrum, both base stations and user equipment operate in half-duplex mode. This half-duplex mode avoids self-interference and mitigates the impact of cross-link interference, but it also reduces resource utilization and increases latency. To address these issues, supporting flexible duplex modes in either TDD or FDD spectrum is a possible solution.

[0006] In response to 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, scenarios where the link direction changes, or other scenarios that support multi-level configuration of transmission directions, or base stations or user equipment with stronger capabilities, such as scenarios that support same-frequency full-duplex, or for different application scenarios, such as eMBB, URLLC, non-terrestrial networks, synaesthesia integrated networks, smart metasurfaces, and 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, and terahertz networks) or different application parameters can also help reduce hardware complexity and cost. In the absence of conflict, the embodiments and features in the embodiments of the device of the first node of the present application can be applied to the device of the second node, and vice versa.

[0007] The present application discloses a method in a first node for wireless communication, comprising:

[0008] receiving a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities and the second information block indicates at least one full-duplex symbol;

[0009] Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0010] As an embodiment, the validity of a PRACH (Physical Random Access Channel) opportunity is judged by determining that the time interval between the first PRACH opportunity and the downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration is greater than the target interval, thereby ensuring the PRACH transmission performance while supporting PRACH transmission in full-duplex symbols.

[0011] According to one aspect of the present application, the above method is characterized in that the target interval depends on the larger value compared between a first interval and a second interval, the first interval is related to the subcarrier spacing of the random access preamble, and the second interval is configured or predefined.

[0012] According to one aspect of the present application, the above method is characterized in that the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0013] According to one aspect of the present application, the above method is characterized in that the second information block indicates a target sub-band, and the target sub-band includes at least one resource block; the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0014] According to one aspect of the present application, the above method is characterized in that the second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet a first restriction condition, and the first restriction condition is related to the symbol type.

[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 the maximum number of conversions supported by the sender of the first capability information block, and the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions.

[0016] According to one aspect of the present application, the above method is characterized in that, among the multiple PRACH opportunities, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain are respectively mapped to synchronized broadcast signals.

[0017] The present application discloses a method in a second node for wireless communication, comprising:

[0018] Sending a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; and the second information block indicates at least one full-duplex symbol;

[0019] Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0020] According to one aspect of the present application, the above method is characterized in that the target interval depends on the larger value compared between a first interval and a second interval, the first interval is related to the subcarrier spacing of the random access preamble, and the second interval is configured or predefined.

[0021] According to one aspect of the present application, the above method is characterized in that the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0022] According to one aspect of the present application, the above method is characterized in that the second information block indicates a target sub-band, and the target sub-band includes at least one resource block; the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0023] According to one aspect of the present application, the above method is characterized in that the second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet a first restriction condition, and the first restriction condition is related to the symbol type.

[0024] 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 the maximum number of conversions supported by the sender of the first capability information block, and the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions.

[0025] According to one aspect of the present application, the above method is characterized in that, among the multiple PRACH opportunities, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain are respectively mapped to synchronized broadcast signals.

[0026] The present application discloses a device for a first node used for wireless communication, comprising:

[0027] A first receiver receives a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; and the second information block indicates at least one full-duplex symbol.

[0028] Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0029] The present application discloses a device for a second node used for wireless communication, comprising:

[0030] A second transmitter transmits a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; and the second information block indicates at least one full-duplex symbol.

[0031] Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

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

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

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

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

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

[0037] FIG1 shows a flow chart of a first information block and a second information block according to an embodiment of the present application;

[0038] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0039] FIG3 is a schematic diagram showing an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0040] FIG4 shows a schematic diagram of a first node device and a second node device according to an embodiment of the present application;

[0041] FIG5 shows a wireless signal transmission flow chart according to an embodiment of the present application;

[0042] FIG6 shows a schematic diagram of target spacing according to an embodiment of the present application;

[0043] FIG7 is a schematic diagram showing the relationship between the validity of the first PRACH opportunity and its location according to an embodiment of the present application;

[0044] FIG8 shows a schematic diagram of a target sub-band according to an embodiment of the present application;

[0045] FIG9 shows a schematic diagram of a first time domain resource according to an embodiment of the present application;

[0046] FIG10 shows a schematic diagram of a first capability information block according to an embodiment of the present application;

[0047] FIG11 shows a schematic diagram of mapping multiple PRACH opportunities and synchronized broadcast signals according to an embodiment of the present application;

[0048] FIG12 shows a structural block diagram of a processing device used in a first node according to an embodiment of the present application;

[0049] FIG13 shows a structural block diagram of a processing device used in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0050] 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 and features in the embodiments of the present application can be combined with each other in any way.

[0051] Example 1

[0052] Example 1 illustrates a flowchart 100 of a first information block and a second information block according to an embodiment of the present application, as shown in FIG1 . In FIG1 , each box represents a step. In particular, the order of the steps in the boxes does not represent a specific temporal relationship between the steps.

[0053] In embodiment 1, the first node in the present application receives a first receiver in step 101, receives a first information block and a second information block, wherein the first information block indicates multiple PRACH opportunities; the second information block indicates at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0054] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: all or part of the first information block explicitly or implicitly indicates the multiple PRACH opportunities.

[0055] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: the first information block is used to determine the multiple PRACH opportunities.

[0056] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: the first information block indicates the time-frequency resources included in at least one PRACH opportunity among the multiple PRACH opportunities.

[0057] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: the first information block indicates the number of frequency-divided PRACH opportunities in the same time domain resources among the multiple PRACH opportunities.

[0058] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: the first information block indicates the starting frequency domain resource of the lowest PRACH opportunity in the frequency domain among the multiple PRACH opportunities.

[0059] As an embodiment, the technical feature "the first information block indicates multiple PRACH opportunities" includes: the first information block indicates a PRACH configuration index (configuration index), and the PRACH configuration index indicated by the first information block configures the time domain resources of at least one PRACH opportunity of the multiple PRACH opportunities.

[0060] As an embodiment, any one of the multiple PRACH opportunities includes allocated or configured PRACH time-frequency resources.

[0061] As an embodiment, any one of the multiple PRACH opportunities is a PRACH time-frequency opportunity.

[0062] As an embodiment, any one of the multiple PRACH opportunities includes time-frequency resources occupied by one PRACH transmission.

[0063] As an embodiment, there are two frequency division multiplexed (FDM) PRACH opportunities among the multiple PRACH opportunities.

[0064] As an embodiment, any two PRACH opportunities among the multiple PRACH opportunities are time division multiplexed.

[0065] As an embodiment, any two PRACH opportunities among the multiple PRACH opportunities include the same time domain resources.

[0066] As an embodiment, there are two PRACH opportunities among the multiple PRACH opportunities that include different time domain resources.

[0067] As an embodiment, any two PRACH opportunities in the plurality of PRACH opportunities are for the same preamble format. As a subsidiary embodiment of the above embodiment, the advantage of this is that the design is simple.

[0068] As an embodiment, two PRACH opportunities in the plurality of PRACH opportunities are for different preamble formats. As a subsidiary embodiment of the above embodiment, the benefit of doing so is to enhance flexibility.

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

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

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

[0072] As an embodiment, a full-duplex symbol is a time-domain symbol in an SBFD time slot.

[0073] As an embodiment, a full-duplex symbol is a time-domain symbol in which the SBFD subband is configured in the time domain.

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

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

[0076] As an embodiment, a full-duplex symbol is a time domain symbol capable of simultaneous uplink transmission and downlink transmission.

[0077] As an embodiment, a 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).

[0078] As an embodiment, a 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] As an embodiment, a non-full-duplex symbol is a downlink or flexible symbol indicated by the TDD uplink and downlink configuration and is not usable for uplink transmission.

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

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

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

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

[0100] As an embodiment, the second information block indicating at least one full-duplex symbol includes: all or part of the second information block explicitly or implicitly indicating at least one full-duplex symbol.

[0101] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the second information block indicating only one full-duplex symbol.

[0102] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the second information block indicating multiple full-duplex symbols.

[0103] As an embodiment, the second information block indicates at least one full-duplex symbol, including: a position or index of at least one full-duplex symbol in the time domain depends on the second information block.

[0104] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the second information block indicating at least one symbol from a time window is a full-duplex symbol.

[0105] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the symbol indicated (or provided) by the second information block is a full-duplex symbol.

[0106] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the second information block indicating at least one downlink symbol indicated by the TDD uplink and downlink configuration as a full-duplex symbol.

[0107] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the symbol indicated (or provided) by the second information block and indicated as a downlink symbol by the TDD uplink and downlink configuration is a full-duplex symbol.

[0108] As an embodiment, the second information block indicating at least one full-duplex symbol includes: the symbol indicated (or provided) by the second information block and indicated by the TDD uplink and downlink configuration as a downlink or flexible symbol is a full-duplex symbol.

[0109] As an embodiment, the second information block indicates at least one full-duplex symbol, including: a symbol that is overlapped with the symbol indicated (or provided) by the second information block in the time domain is a full-duplex symbol.

[0110] As an embodiment, the second information block indicates at least one full-duplex symbol including: the symbol indicated as downlink by the TDD uplink and downlink configuration that fully or partially overlaps in the time domain with the symbol indicated (or provided) by the second information block is a full-duplex symbol.

[0111] As an embodiment, the second information block indicates that at least one full-duplex symbol includes: symbols indicated as downlink or flexible by the TDD uplink and downlink configuration that fully or partially overlap in the time domain with the symbols indicated (or provided) by the second information block are full-duplex symbols.

[0112] As an embodiment, the second information block indicates that at least one full-duplex symbol includes: a symbol indicated as downlink by the TDD uplink and downlink configuration and fully or partially overlapping with the symbol indicated (or provided) by the second information block in the time domain is a full-duplex symbol.

[0113] As an embodiment, the second information block indicates that at least one full-duplex symbol includes: a symbol indicated by the TDD uplink and downlink configuration as downlink or flexible and which fully or partially overlaps with the symbol indicated (or provided) by the second information block in the time domain is a full-duplex symbol.

[0114] In one embodiment, the second information block indicates at least one full-duplex symbol, including: the second information block indicates at least one symbol according to a reference subcarrier spacing, any one time-domain symbol indicated as downlink by the TDD uplink and downlink configuration that overlaps with the symbol indicated by the second information block is a full-duplex symbol, and the reference subcarrier spacing is predefined or configured by signaling. As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing being predefined means that the reference subcarrier spacing is fixed. As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing being predefined means that the reference subcarrier spacing is related to a frequency range (FR). As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing being predefined means that the reference subcarrier spacing is related to a band index. As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing being predefined means that the reference subcarrier spacing is equal to the subcarrier spacing of an initial downlink BWP (Bandwidth Part). As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing being predefined means that the reference subcarrier spacing is equal to the subcarrier spacing of an initial uplink BWP (Bandwidth Part). As a subsidiary embodiment of the above embodiment, the reference subcarrier spacing is equal to the subcarrier spacing indicated by the TDD uplink and downlink configuration.

[0115] As an embodiment, the second information block indicates at least one full-duplex symbol, including: the second information block indicates at least one full-duplex symbol from a periodic time window, the periodic time window includes multiple consecutive time domain symbols, and the time length of the periodic time window is related to the period length configured in the time slot format.

[0116] As an embodiment, the second information block indicates at least one full-duplex symbol, including: the second information block indicates whether at least one symbol is applicable or associated or corresponds or targets the target sub-band from a time window, and the full-duplex symbol is a symbol that is applicable or associated or corresponds or targets the target sub-band.

[0117] As an embodiment, the second information block indicates at least one full-duplex symbol including: the second information block includes a SLIV, and the starting full-duplex symbol in a periodic time window and the number of consecutive symbols included are used to generate the SLIV included in the second information block.

[0118] As an embodiment, the second information block indicates at least one full-duplex symbol including: the second information block includes a SLIV, the starting full-duplex symbol in a periodic time window and the number of consecutive symbols included are used to generate the SLIV included in the second information block, and the symbols among the included consecutive symbols that overlap with the downlink symbols or flexible symbols indicated by the TDD uplink and downlink configuration are full-duplex symbols.

[0119] As an embodiment, the second information block indicates at least one full-duplex symbol including: the second information block includes a SLIV for a reference subcarrier spacing, the starting full-duplex symbol for the reference subcarrier spacing in a periodic time window and the number of consecutive symbols included are used to generate the SLIV included in the second information block, and the symbols included in the consecutive symbols that overlap with the downlink symbols or flexible symbols indicated by the TDD uplink and downlink configuration are full-duplex symbols. As an auxiliary embodiment of the above embodiment, the reference subcarrier spacing is equal to the subcarrier spacing of the uplink BWP or the downlink BWP, or the reference subcarrier spacing is equal to the subcarrier spacing adopted by the time slot format configuration. As an auxiliary embodiment of the above embodiment, the reference subcarrier spacing is equal to the subcarrier spacing indicated by the TDD uplink and downlink configuration.

[0120] As an embodiment, indicating full-duplex symbols through SLIV reduces signaling overhead while maintaining a certain degree of configuration flexibility, and is well compatible with the restriction of no more than two transition points between full-duplex symbols and non-full-duplex symbols.

[0121] As an embodiment, the technical feature "the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block" includes: the first PRACH opportunity is any one of the multiple PRACH opportunities indicated by the first information block.

[0122] As an embodiment, the technical feature "the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block" includes: the first PRACH opportunity is a given PRACH opportunity among the multiple PRACH opportunities indicated by the first information block.

[0123] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity occupies at least one full-duplex symbol indicated by the second information block in the time domain.

[0124] In one embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity is mapped to at least one full-duplex symbol in the time domain.

[0125] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity is located in a full-duplex symbol in the time domain.

[0126] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity includes at least one full-duplex symbol in the time domain.

[0127] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity overlaps with at least one full-duplex symbol in the time domain.

[0128] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity completely overlaps between the time domain and at least one full-duplex symbol.

[0129] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity fully or partially overlaps between the time domain and at least one full-duplex symbol.

[0130] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity occupies at least one full-duplex symbol in the time domain that is indicated as a downlink by the TDD uplink and downlink configuration.

[0131] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity occupies at least one full-duplex symbol in the time domain that is indicated as a downlink or flexible full-duplex symbol by the TDD uplink and downlink configuration.

[0132] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: there is an overlap between the PRACH time slot (slot) to which the first PRACH opportunity belongs and at least one full-duplex symbol in the time domain.

[0133] As an embodiment, the technical feature "the first PRACH opportunity occupies at least one full-duplex symbol in the time domain" includes: the first PRACH opportunity overlaps in the time domain and a time slot including at least one full-duplex symbol.

[0134] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: whether the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval.

[0135] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: the time interval between the first PRACH opportunity and the first symbol being greater than the target interval is used to determine the validity of the first PRACH opportunity.

[0136] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: the validity of the first PRACH opportunity is related to the size relationship between the time interval between the first PRACH opportunity and the first symbol and the target interval.

[0137] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: the time interval between the first PRACH opportunity and the first symbol being greater than the target interval is a condition for the validity of the first PRACH opportunity.

[0138] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: the time interval between the first PRACH opportunity and the first symbol being greater than the target interval is a necessary condition for the validity of the first PRACH opportunity.

[0139] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: when the time interval between the first PRACH opportunity and the first symbol is greater than the target interval, the first PRACH opportunity is valid.

[0140] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval" includes: when the time interval between the first PRACH opportunity and the first symbol is not greater than (or less than or equal to) the target interval, the first PRACH opportunity is valid.

[0141] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the start of the first PRACH opportunity in the time domain and the start of the first symbol in the time domain.

[0142] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the start of the first PRACH opportunity in the time domain and the end of the first symbol in the time domain.

[0143] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the end of the first PRACH opportunity in the time domain and the start of the first symbol in the time domain.

[0144] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the end of the first PRACH opportunity in the time domain and the end of the first symbol in the time domain.

[0145] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the PRACH time slot to which the first PRACH opportunity belongs in the time domain and the first symbol.

[0146] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is the length of the interval between the time slot in which the first PRACH opportunity overlaps in the time domain and the first symbol.

[0147] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is expressed in absolute time length.

[0148] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is expressed in the number of symbols.

[0149] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is expressed as the number of symbols corresponding to the subcarrier spacing of the preamble.

[0150] As an embodiment, the time interval between the first PRACH opportunity and the first symbol is expressed as the number of symbols corresponding to the subcarrier spacing of the active uplink BWP.

[0151] As an embodiment, the value of the target interval is a non-negative integer.

[0152] As an embodiment, the value of the target interval may be a non-integer.

[0153] As an embodiment, the unit of the target interval is seconds or milliseconds.

[0154] As an embodiment, the target interval represents the number of symbols.

[0155] As an embodiment, the target interval is a transition time interval between downlink transmission and uplink transmission.

[0156] As an embodiment, the target interval is a transition time interval from a non-full-duplex symbol to a full-duplex symbol.

[0157] As an embodiment, the target interval is N gap .

[0158] As an embodiment, the target interval is a time interval for converting non-full-duplex downlink symbols to full-duplex symbols.

[0159] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: the target interval is related to the subcarrier spacing of the random access preamble corresponding to the first PRACH opportunity.

[0160] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: the target interval is related to the subcarrier spacing of the random access preamble transmitted on the first PRACH opportunity.

[0161] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: the target interval depends on the subcarrier spacing of the random access preamble corresponding to the first PRACH opportunity.

[0162] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: the subcarrier spacing of the random access preamble corresponding to the first PRACH opportunity is used to determine or calculate the target interval.

[0163] As an embodiment, the technical feature "the target interval is related to the subcarrier interval of the random access preamble" includes: the target interval and the subcarrier interval of the random access preamble are linearly correlated.

[0164] As an embodiment, the technical feature "the target interval is related to the subcarrier interval of the random access preamble" includes: there is a correspondence or mapping relationship between the target interval and the subcarrier interval of the random access preamble according to a predefined table.

[0165] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: according to the subcarrier spacing of the random access preamble, the target interval can be found in a predefined table.

[0166] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: a parameter used when calculating the target interval is related to the subcarrier spacing of the random access preamble.

[0167] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: a parameter included in the target interval is related to the subcarrier spacing of the random access preamble.

[0168] As an embodiment, the technical feature "the target interval is related to the subcarrier spacing of the random access preamble" includes: the first interval in this application is related to the subcarrier spacing of the random access preamble.

[0169] As an embodiment, the value of the target interval only considers the switching time from downlink to uplink or between reception and transmission, which simplifies system design and makes minor changes to the standard.

[0170] As an embodiment, the technical feature "the target interval is related to the subcarrier interval of the random access preamble" includes: the value of the target interval is equal to the sum of a first value and a second value, the first value is the value corresponding to the subcarrier interval of the random access preamble in a predefined table, and the second value is configured or predefined.

[0171] As an embodiment, the value of the target interval being equal to the sum of the first value and the second value can ensure sufficient receiving and transmitting switching time and switching time between full-duplex symbols and non-full-duplex symbols, reducing product implementation and standard complexity.

[0172] As an embodiment, the technical feature "the target interval is related to the subcarrier interval of the random access preamble" includes: the value of the target interval is equal to the larger value between the first value and the second value, the first value is the value corresponding to the subcarrier interval of the random access preamble in a predefined table, and the second value is configured or predefined.

[0173] As an embodiment, the value of the target interval is equal to the larger value between the first value and the second value, which minimizes the delay and improves resource utilization on the basis of ensuring the conversion time between receiving and sending and the conversion time between full-duplex symbols and non-full-duplex symbols.

[0174] As an embodiment, the technical feature "the target interval is related to the subcarrier interval of the random access preamble" includes: the value of the target interval is equal to the smaller value between a first value and a second value, the first value is the value corresponding to the subcarrier interval of the random access preamble in a predefined table, and the second value is configured or predefined.

[0175] As an embodiment, the TDD uplink / downlink configuration is an uplink / downlink TDD configuration used to determine a timeslot format.

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

[0177] 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.

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

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

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

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

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

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

[0184] As an embodiment, only “tdd-UL-DL-ConfigCommon” is considered, which simplifies the design and reduces the workload of standards.

[0185] As an embodiment, both "tdd-UL-DL-ConfigCommon" and "tdd-UL-DL-ConfigDedicated" are considered, and the existing design is used to the maximum extent to ensure compatibility.

[0186] As an embodiment, the downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration are downlink symbols that are not indicated by the second information block but are indicated by the TDD uplink and downlink configuration.

[0187] As an embodiment, the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration is a downlink symbol that is not indicated as a full-duplex symbol by the second information block but is indicated by the TDD uplink and downlink configuration.

[0188] As an embodiment, the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration is a downlink symbol that does not overlap with at least one symbol indicated by the second information block and is indicated by the TDD uplink and downlink configuration.

[0189] As an embodiment, the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration is a downlink symbol indicated by the TDD uplink and downlink configuration other than the at least one symbol indicated by the second information block.

[0190] As an embodiment, the downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration are symbols indicated as downlink by the TDD uplink and downlink configuration and cannot be used for uplink transmission.

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

[0192] As an embodiment, the technical feature "the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration" includes: the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration of the first PRACH opportunity in the time domain.

[0193] As an embodiment, the technical feature "the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration" includes: the first symbol is a downlink symbol indicated by the previous closest non-full-duplex TDD uplink and downlink configuration in the time domain of the first PRACH opportunity.

[0194] As an embodiment, the technical feature "the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration" includes: the first symbol is the latest or last downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0195] Example 2

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

[0197] Figure 2 illustrates the network architecture for LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), and future 5G systems. The network architecture for 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. The 5GS / EPS 200 may include one or more UEs 201, a UE 241 in sidelink communication with UE 201, a Next Generation Radio Access Network (NG-RAN) 202, a 5G-CN (5G Core Network) / EPC (Evolved Packet Core) 210, an HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS 200 may interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown in FIG2 , the 5GS / EPS 200 provides packet-switched services. However, those skilled in the art will readily appreciate that the various concepts presented throughout this disclosure can be extended to networks providing circuit-switched services. The NG-RAN 202 includes an NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol terminations towards the UE 201. The gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The 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 Transmitter Receiver Point (TRP), or some other appropriate terminology. The gNB 203 provides an access point to the 5G-CN / EPC 210 for the UE 201.Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband physical network device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. 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 terminology. The gNB 203 connects to the 5G-CN / EPC 210 via the S1 / NG interface. The 5G-CN / EPC 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that handles signaling between the UE 201 and the 5G-CN / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are routed through S-GW / UPF 212, which itself is connected to P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. P-GW / UPF 213 is connected to Internet Services 230. Internet Services 230 includes carrier-specific Internet Protocol services, specifically the Internet, intranet, IMS (IP Multimedia Subsystem), and packet switching services.

[0198] As an embodiment, the UE201 corresponds to the device of the first node in this application.

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

[0200] As an embodiment, the gNB (eNB) 201 corresponds to the second node device in this application.

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

[0202] Example 3

[0203] 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 FIG3 .

[0204] FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for a first node device (a UE or RSU (Road Side Unit) in a V2X (Vehicle to Everything) network, a vehicle-mounted device, or a vehicle-mounted communication module) and a second node device (a gNB, a UE or RSU in a V2X network, a vehicle-mounted device, or a vehicle-mounted communication module), or the control plane 300 between two UEs using three layers: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). L1 is the lowest layer and implements various PHY (Physical Layer) signal processing functions. L1 will be referred to herein as PHY 301. L2 305, located above PHY 301, is responsible for the link between the first and second node devices, or between two UEs, through PHY 301. L2 305 includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node device. 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 supports handover of the first node device between the second node devices. 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 the first node devices. 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 (ie, radio bearers) and configuring lower layers using RRC signaling between the second node device and the first node device.The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture for the first and second node devices in the user plane 350 is substantially identical to the corresponding layers and sublayers in the control plane 300, including the physical layer 351, the PDCP sublayer 354 in Layer 2 355, the RLC sublayer 353 in Layer 2 355, and the MAC sublayer 352 in Layer 2 355. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. Layer 2 355 in the user plane 350 also includes the Service Data Adaptation Protocol (SDAP) sublayer 356, which is responsible for mapping QoS (Quality of Service) flows to Data Radio Bearers (DRBs) to support service diversity. Although not shown, the first node device may have several upper layers above L2 355, 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.).

[0205] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node device in this application.

[0206] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node device in this application.

[0207] As an embodiment, the first node device is the device used for the first node in this application.

[0208] As an embodiment, the second node device is the device used for the second node in this application.

[0209] 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.

[0210] 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.

[0211] 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.

[0212] Example 4

[0213] Example 4 shows a schematic diagram of a first node device and a second node device according to an embodiment of the present application, as shown in FIG4 .

[0214] The first node device (450) may include a controller / processor 490, a data source / buffer 480, a receiving processor 452, a transmitter / receiver 456 and a transmitting processor 455, and the transmitter / receiver 456 includes an antenna 460.

[0215] The second node device ( 410 ) may include a controller / processor 440 , a data source / buffer 430 , a receiving processor 412 , a transmitter / receiver 416 and a transmitting processor 415 , wherein the transmitter / receiver 416 includes an antenna 420 .

[0216] In DL (Downlink), 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 first node device 450 based on various priority metrics. The controller / processor 440 is also responsible for HARQ operations, retransmission of lost packets, and high-layer signaling to the first node device 450. The high-layer information carried by the first information block and the second information block in this application is generated by the controller / processor 440. The transmit 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. For example, the physical layer signal carrying the first information block and the physical layer signal carrying the second information block are completed by the transmit processor 415. The generated modulated symbols are divided into parallel streams, and each stream is mapped to a corresponding multi-carrier subcarrier and / or multi-carrier symbol. The symbols are then mapped by the transmit processor 415 to the antenna 420 via the transmitter 416 and transmitted in the form of RF signals. At the receiving end, each receiver 456 receives the RF signal via its corresponding antenna 460, recovers the baseband information modulated onto the RF carrier, and provides the baseband information to the receive processor 452. The receive processor 452 implements various L1 layer signal reception processing functions. The signal reception processing functions include demodulating the physical layer signal carrying the first information block and the physical layer signal carrying the second information block based on various modulation schemes (e.g., binary phase shift keying (BPSK) and quadrature phase shift keying (QPSK)) in the multi-carrier symbol stream, followed by descrambling, decoding, and deinterleaving to recover the data or control signals transmitted by the second node device 410 on the physical channel. The data and control signals are then provided to the controller / processor 490. Controller / processor 490 is responsible for L2 and above layers. It interprets high-level information, including the high-level information carried in the first and second information blocks. The controller / processor may be associated with memory 480, which stores program code and data. Memory 480 may be referred to as a computer-readable medium.

[0217] During uplink (UL) transmission, similar to downlink transmission, higher-layer information, including the higher-layer information carried by the first capabilities information block in this application, is generated by the controller / processor 490 and then processed by the transmit processor 455 to perform various signal transmission processing functions for the L1 layer (i.e., physical layer). The physical layer signal carrying the first capabilities information block is mapped by the transmit processor 455 via the transmitter 456 to the antenna 460 for transmission as a radio frequency signal. Receivers 416 receive the radio frequency signal via their corresponding antennas 420. 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 performs various signal reception processing functions for the L1 layer (i.e., physical layer), including receiving and processing the physical layer signal carrying the first capabilities information block in this application, and then provides data and / or control signals to the controller / processor 440. The L2 layer functions implemented by the controller / processor 440 include interpreting higher-layer information, such as the higher-layer information carried by the first capabilities information block in this application. The controller / processor may be associated with a buffer 430 that stores program code and data. The buffer 430 may be a computer-readable medium.

[0218] As an embodiment, the first node device 450 apparatus 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 first node device 450 apparatus at least: receives a first information block and a second information block, the first information block indicating multiple PRACH opportunities; the second information block indicates at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0219] As an embodiment, the first node device 450 apparatus includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action including: receiving a first information block and a second information block, the first information block indicating a plurality of PRACH opportunities; the second information block indicating at least one full-duplex symbol; wherein the first PRACH opportunity is one of the plurality of PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than a target interval, the target interval being related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0220] As an embodiment, the second node device 410 apparatus 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. The second node device 410 apparatus at least: sends a first information block and a second information block, the first information block indicating a plurality of PRACH opportunities; the second information block indicating at least one full-duplex symbol; wherein the first PRACH opportunity is one of the plurality of PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than a target interval, the target interval being related to the subcarrier spacing of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0221] As an embodiment, the second node device 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 and a second information block, the first information block indicating multiple PRACH opportunities; the second information block indicating at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0222] As an embodiment, the first node device is the device used for the first node in this application.

[0223] As an embodiment, the first node device 450 is a user equipment (UE).

[0224] As an embodiment, the first node device 450 is a user equipment supporting flexible duplex mode transmission.

[0225] As an embodiment, the second node device is the device used for the second node in this application.

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

[0227] As an embodiment, the second node device 410 is a base station device that supports flexible duplex mode transmission.

[0228] 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 this application.

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

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

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

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

[0233] 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 this application.

[0234] Example 5

[0235] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG5 . In FIG5 , the second node N500 is the base station maintaining the serving cell of the first node U550. It should be noted that the sequence in this example does not limit the signal transmission sequence and implementation order in this application.

[0236] For the second node N500, a first information block is sent in step S501, a second information block is sent in step S502, and a first capability information block is received in step S503.

[0237] For the first node U550, the first information block is received in step S551, the second information block is received in step S552, and the first capability information block is sent in step S553.

[0238] In embodiment 5, the first information block indicates multiple PRACH opportunities; the second information block indicates at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration; the second information block indicates a target subband, and the target subband includes at least one resource block; the second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block.

[0239] As an embodiment, the first information block includes higher-layer information or higher-layer parameter configuration.

[0240] As an embodiment, the first information block includes one or more IEs (Information Elements) included in RRC (Radio Resource Control) layer signaling, or the first information block includes one or more fields (Field) included in RRC layer signaling. As a subsidiary embodiment of the above embodiment, the first information block including RRC layer information can reduce signaling overhead.

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

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

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

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

[0245] As an embodiment, the first information block is configured per subband. As a subsidiary embodiment of the above embodiment, configuring the first information block per subband can improve the configuration flexibility of PRACH opportunities in full-duplex mode.

[0246] As an embodiment, the first information block is configured for a carrier (per carrier). As a subsidiary embodiment of the above embodiment, per-carrier configuration can reduce complexity.

[0247] As an embodiment, the first information block is configured for SBFD.

[0248] As an embodiment, the first information block is configured for a bandwidth part (BWP) (Per BWP). As a subsidiary embodiment of the above embodiment, the existing design can be reused for BWP configuration to reduce standardization work.

[0249] As an embodiment, the first information block includes part or all of the fields in the IE "RACH-ConfigDedicated".

[0250] As an embodiment, the first information block includes the field "CFRA" or the field "CFRA-TwoStep-r16".

[0251] As an embodiment, the first information block includes part or all of the fields in the IE "rach-ConfigGeneric".

[0252] As an embodiment, the first information block includes part or all of the fields in the IE "SI-RequestConfig".

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

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

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

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

[0257] As an embodiment, the first information block includes part or all of the fields in the IE "RACH-ConfigGenericTwoStepRA".

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

[0259] As an embodiment, the first information block includes part or all of the fields in the IE "RACH-ConfigCommonTwoStepRA".

[0260] As an embodiment, the first information block includes part or all of the fields in the IE "SBFD-Config".

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

[0262] As an embodiment, the first information block includes part or all of the fields in a DCI format. As a subsidiary embodiment of the above embodiment, the first information block includes DCI to provide greater flexibility.

[0263] As an embodiment, the first information block is transmitted on a PDCCH (physical downlink control channel).

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

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

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

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

[0268] As an embodiment, the second information block includes higher-layer information or higher-layer parameter configuration.

[0269] As an embodiment, the second information block includes one or more IEs included in RRC layer signaling, or the second information block includes one or more fields included in RRC layer signaling. As a subsidiary embodiment of the above embodiment, the second information block including RRC layer information can reduce signaling overhead.

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

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

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

[0273] As an embodiment, the second information block is user equipment specific (UE specific or UE dedicated).

[0274] As an embodiment, the second information block is configured for a sub-band (per subband).

[0275] As an embodiment, the second information block is configured for a carrier (per carrier). As a subsidiary embodiment of the above embodiment, configuring SBFD per carrier reduces complexity.

[0276] As an embodiment, the second information block is configured for a bandwidth part (BWP) (per BWP). As a subsidiary embodiment of the above embodiment, configuring SBFD per BWP can reuse existing designs and reduce standardization work.

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

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

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

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

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

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

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

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

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

[0286] As an embodiment, the second information block includes part or all of the fields in DCI (downlink control information) format 2_N, where N is a non-negative integer.

[0287] As an embodiment, the second information block includes part or all of the fields in DCI format 2_10.

[0288] As an embodiment, the second information block includes part or all of the fields in a DCI format.As a subsidiary embodiment of the above embodiment, the second information block includes DCI to provide greater flexibility.

[0289] As an embodiment, the second information block is transmitted on a PDCCH (physical downlink control channel).

[0290] As an embodiment, the second information block configures a time slot or symbol of SBFD (Subband non-overlapping Full Duplex).

[0291] As an embodiment, the second information block configures at least one of an uplink subband (UL subband), a downlink subband (DL subband) or a guard band (guardband) of the SBFD.

[0292] As an embodiment, the second information block configuration supports time slots or symbols for full duplex.

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

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

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

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

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

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

[0299] 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.

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

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

[0302] As an embodiment, the sender of the first capability information block is the first node in this application or the device used for the first node in this application.

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

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

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

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

[0307] As an embodiment, the first capability information block includes IE “FeatureSetUplink”, or the first capability information block includes IE “FeatureSetUplinkPerCC”.

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

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

[0310] 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.

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

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

[0313] As an embodiment, the first capability information block is transmitted per band combination. As a subsidiary embodiment of the above embodiment, transmitting 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.

[0314] As an embodiment, the first capability information block has different parameter values ​​in different frequency ranges (FR). As a subsidiary embodiment of the above embodiment, having different parameter values ​​in different frequency ranges can optimize product implementation according to the frequency range and improve flexibility.

[0315] As an embodiment, the first capability information block has the same parameter value across different frequency ranges. As a subsidiary embodiment of the above embodiment, having the same parameter value across different frequency ranges can support a unified design and reduce standard complexity.

[0316] Example 6

[0317] Embodiment 6 illustrates a schematic diagram of a target interval according to an embodiment of the present application, as shown in FIG6. In FIG6, the target interval depends on the larger value between the first interval and the second interval.

[0318] In Example 6, the target interval in the present application depends on the larger value compared between the first interval and the second interval. The first interval in the present application is related to the subcarrier interval of the random access preamble, and the second interval in the present application is configured or predefined.

[0319] As an embodiment, the design of the target interval meets the transmission delay requirements of different coverage ranges while ensuring the conversion time between full-duplex symbols and non-full-duplex symbols, thereby improving the probability of successful PRACH transmission and reducing the implementation complexity of PRACH transmission on full-duplex symbols.

[0320] As an embodiment, the first interval is N gap .

[0321] As an embodiment, the value of the first interval is a non-negative integer.

[0322] As an embodiment, the value of the first interval may be a non-integer.

[0323] As an embodiment, the unit of the first interval is seconds or milliseconds.

[0324] As an embodiment, the first interval represents the number of symbols.

[0325] As an embodiment, the value of the second interval is a non-negative integer.

[0326] As an embodiment, the value of the second interval may be a non-integer.

[0327] As an embodiment, the unit of the second interval is seconds or milliseconds.

[0328] As an embodiment, the second interval represents the number of symbols.

[0329] As an embodiment, the second interval includes a transition time between a full-duplex symbol and a non-full-duplex symbol.

[0330] As an embodiment, the second interval depends on the self-interference processing capability of the base station and the switching delay of the user equipment.

[0331] As an embodiment, how to determine the second interval from a plurality of candidate values ​​or a range of candidate values ​​is implementation-dependent and has no fixed standard.

[0332] As an embodiment, the technical feature "the target interval depends on a larger value compared between the first interval and the second interval" includes: the value of the target interval depends on a larger value compared between the first interval and the second interval.

[0333] As an embodiment, the technical feature “the target interval depends on a larger value compared between the first interval and the second interval” includes: a larger value compared between the first interval and the second interval is used to determine or calculate the target interval.

[0334] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: the value of the target interval is related to the larger value compared between the first interval and the second interval.

[0335] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: the value of the target interval is equal to the larger value compared between the first interval and the second interval.

[0336] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: when the value of the first interval is greater than the value of the second interval, the value of the target interval is equal to the value of the first interval.

[0337] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: when the value of the first interval is not greater than the value of the second interval, the value of the target interval is equal to the value of the second interval.

[0338] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: the value of the target interval is linearly correlated with the larger value compared between the first interval and the second interval.

[0339] As an embodiment, the technical feature "the target interval depends on the larger value compared between the first interval and the second interval" includes: the value of the target interval is equal to the upper or lower value of the larger value compared between the first interval and the second interval.

[0340] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: the first interval is related to the subcarrier spacing of the random access preamble corresponding to the first PRACH opportunity.

[0341] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: the first interval is related to the subcarrier spacing of the random access preamble transmitted on the first PRACH opportunity.

[0342] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: the first interval depends on the subcarrier spacing of the random access preamble.

[0343] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: the subcarrier spacing of the random access preamble is used to determine or calculate the first interval.

[0344] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: the first interval and the subcarrier spacing of the random access preamble are linearly correlated.

[0345] As an embodiment, the technical feature "the first interval is related to the subcarrier interval of the random access preamble" includes: the correspondence between the first interval and the subcarrier interval of the random access preamble is one of one-to-one, many-to-one or many-to-many.

[0346] As an embodiment, the technical feature "the first interval is related to the subcarrier interval of the random access preamble" includes: there is a correspondence or mapping relationship between the first interval and the subcarrier interval of the random access preamble according to a predefined table.

[0347] As an embodiment, the technical feature "the first interval is related to the subcarrier spacing of the random access preamble" includes: according to the subcarrier spacing of the random access preamble, the first interval can be found in a predefined table.

[0348] As an embodiment, the second interval being configured or predefined includes: the second interval being fixed.

[0349] As an embodiment, the second interval being configured or predefined includes: the second interval being hard coded in the standard.

[0350] As an embodiment, the second interval is configured or predefined, including: higher layer signaling or higher layer parameters indicating the second interval.

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

[0352] As an embodiment, the second interval is configured or predefined, including: the second interval is indicated by the user equipment capability.

[0353] As an embodiment, the second interval is configured or predefined including: higher layer signaling or higher layer parameters indicating whether the second interval is equal to a value indicated (or reported) by the user equipment capability.

[0354] As an embodiment, the second interval is configured or predefined, including: the second interval is equal to the value indicated (or reported) by the user equipment capability.

[0355] As an embodiment, the second interval is configured or predefined and includes: a higher layer signaling or a higher layer parameter indicating an offset value between the second interval and a value indicated (or reported) by the user equipment capability.

[0356] As an embodiment, the second interval is configured or predefined, including: the second interval is not less than the value indicated (or reported) by the user equipment capability.

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

[0358] As an embodiment, the second interval is configured or predefined including: a parameter for calculating the second interval includes a first parameter value, and the first parameter value is equal to a value indicated (or reported) by the user equipment capability.

[0359] As an embodiment, the second interval is configured or predefined, including: the second interval is linearly related to the first parameter value, and higher layer signaling or higher layer parameters indicate the first parameter value.

[0360] As an embodiment, the second interval is configured or predefined including: the second interval is linearly related to the first parameter value, and the first parameter value is equal to the value indicated (or reported) by the user equipment capability.

[0361] Example 7

[0362] Embodiment 7 illustrates a schematic diagram of the relationship between the validity of the first PRACH opportunity and its location according to an embodiment of the present application, as shown in FIG7. In FIG7, the validity of the first PRACH opportunity depends on the first PRACH opportunity not being located before the synchronization broadcast signal in the PRACH time slot to which it belongs, and also depends on the first PRACH opportunity not being located before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs.

[0363] In Example 7, the validity of the first PRACH opportunity in the present application also depends on the fact that the first PRACH opportunity is not located before the synchronization broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0364] As an embodiment, the PRACH time slot to which the first PRACH opportunity belongs is a time slot that overlaps with the first PRACH opportunity.

[0365] As an embodiment, the PRACH time slot to which the first PRACH opportunity belongs is a time slot with a subcarrier spacing of the BWP to which the first PRACH opportunity belongs in the frequency domain that overlaps with the first PRACH opportunity.

[0366] As an embodiment, the PRACH time slot to which the first PRACH opportunity belongs is a time slot that includes the first PRACH opportunity in the time domain.

[0367] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal belonging to the same PRACH time slot in the time domain, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration belonging to the same PRACH time slot.

[0368] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not earlier than (not precedes) the synchronous broadcast signal in the PRACH time slot to which it belongs, nor is it earlier than (not precedes) the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0369] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is later than the synchronous broadcast signal in the PRACH time slot to which it belongs, and later than the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0370] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal or the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs" includes: when the first PRACH opportunity is not located before the synchronous broadcast signal or the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs, the first PRACH opportunity is valid.

[0371] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal and not located before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs" includes: when the first PRACH opportunity is not earlier than (not precedes) the synchronous broadcast signal and not earlier than (not precedes) the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs, the first PRACH opportunity is valid.

[0372] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: when the first (first) time domain symbol of the first PRACH opportunity is not earlier than (not precedes) the last (last) time domain symbol of the synchronous broadcast signal in the PRACH time slot to which it belongs, nor is it earlier than (not precedes) the last (last) downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, the first PRACH opportunity is valid.

[0373] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: when the first PRACH opportunity is later than (not precedes) the synchronous broadcast signal in the PRACH time slot to which it belongs, and is also later than (not precedes) the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, the first PRACH opportunity is valid.

[0374] As an embodiment, the technical feature "the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronous broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration" includes: when the first PRACH opportunity is earlier than (precede) the synchronous broadcast signal in the PRACH time slot to which it belongs, or the first PRACH opportunity is earlier than (precede) at least one of the downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration in the PRACH time slot to which it belongs, the first PRACH opportunity is invalid.

[0375] Example 8

[0376] Embodiment 8 illustrates a schematic diagram of a target sub-band according to an embodiment of the present application, as shown in FIG8. In FIG8, the vertical axis represents frequency, the rectangular area in a bold frame represents the target sub-band, and the rectangular area filled with slashes represents the first PRACH opportunity.

[0377] In Example 8, the second information block in the present application indicates a target sub-band, and the target sub-band in the present application includes at least one resource block; the validity of the first PRACH opportunity in the present application depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0378] As an embodiment, the validity judgment of a PRACH opportunity is made dependent on the relationship with the target sub-band, thereby ensuring effective transmission of the PRACH and improving random access performance.

[0379] As an embodiment, the target sub-band is a full duplex sub-band.

[0380] As an embodiment, the target sub-band is a full-duplex sub-band for uplink.

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

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

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

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

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

[0386] 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 maximize the reuse of existing designs and reduce design complexity.

[0387] 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.

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

[0389] 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.

[0390] 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.

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

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

[0393] 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.

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

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

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

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

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

[0399] As an embodiment, the technical feature "the second information block indicates the target sub-band" includes: the second 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.

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

[0401] As an embodiment, the technical feature "the second information block indicates the target sub-band" includes: the second 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.

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

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

[0404] As an embodiment, the technical feature "the second information block indicates the target sub-band" includes: all or part of the second 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 frequency point A, 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 benefit of doing so includes 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; 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 configured uplink resource grids; the advantage of doing so is that alignment with 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 configured downlink resource grids; the advantage of doing so is that alignment with 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 configured resource grids; the advantage of doing so is that alignment with both uplink and downlink resources is ensured.

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

[0406] As an embodiment, the resource block includes a physical resource block (PRB).

[0407] As an embodiment, the resource block includes a common resource block (CRB).

[0408] As an embodiment, the resource blocks include transmitted resource blocks.

[0409] As an embodiment, the resource block is a physical resource block.

[0410] As an embodiment, the resource block is a common resource block.

[0411] As an embodiment, the resource block is a transmission resource block.

[0412] As an embodiment, the technical feature "the target sub-band includes at least one resource block" includes: the target sub-band includes one resource block.

[0413] As an embodiment, the technical feature "the target sub-band includes at least one resource block" includes: the target sub-band includes multiple resource blocks.

[0414] As an embodiment, the technical feature "the target sub-band includes at least one resource block" includes: the target sub-band includes multiple consecutive resource blocks.

[0415] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: whether the first PRACH opportunity is valid depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0416] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the validity of the first PRACH opportunity depends on all frequency domain resources occupied by the first PRACH opportunity being located within the target sub-band.

[0417] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: the validity of the first PRACH opportunity depends on the target sub-band including all frequency domain resources occupied by the first PRACH opportunity.

[0418] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: whether the first PRACH opportunity is valid depends on the relationship between the first PRACH opportunity in the frequency domain and the target sub-band.

[0419] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: whether the first PRACH opportunity is valid is related to whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0420] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belonging to the target sub-band in the frequency domain is used to determine whether the first PRACH opportunity is valid.

[0421] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: when the first PRACH opportunity belongs to the target sub-band in the frequency domain, the first PRACH opportunity is valid.

[0422] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: when the first PRACH opportunity does not belong to the target sub-band in the frequency domain, the first PRACH opportunity is invalid.

[0423] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belonging to the target sub-band in the frequency domain is a condition for the first PRACH opportunity to be valid.

[0424] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belonging to the target sub-band in the frequency domain is a necessary condition for the first PRACH opportunity to be valid.

[0425] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belongs to the target sub-band in the frequency domain and the frequency domain interval between the first PRACH opportunity in the frequency domain and at least one boundary of the target sub-band is not less than a predefined or configured threshold, which is a condition for the validity of the first PRACH opportunity.

[0426] As an embodiment, the impact of self-interference on adjacent frequency bands is considered when determining the validity of a PRACH opportunity, thereby ensuring effective transmission of the PRACH and improving random access performance.

[0427] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belongs to the target sub-band in the frequency domain and the frequency domain interval between the lowest frequency (or the lowest-indexed subcarrier) of the first PRACH opportunity and the lowest frequency (or the included lowest-indexed subcarrier) of the target sub-band in the frequency domain is not less than a predefined or configured threshold, which is a condition for the validity of the first PRACH opportunity.

[0428] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belongs to the target sub-band in the frequency domain and the frequency domain interval between the highest frequency (or the highest-indexed subcarrier) of the first PRACH opportunity and the highest frequency (or the included highest-indexed subcarrier) of the target sub-band in the frequency domain is not less than a predefined or configured threshold, which is a condition for the validity of the first PRACH opportunity.

[0429] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on the first PRACH opportunity belonging to the target sub-band in the frequency domain" includes: the first PRACH opportunity belongs to the target sub-band in the frequency domain, the frequency domain interval between the lowest frequency (or the lowest indexed subcarrier) of the first PRACH opportunity and the lowest frequency (or the lowest indexed subcarrier) of the target sub-band in the frequency domain is not less than a predefined or configured threshold, and the frequency domain interval between the highest frequency (or the highest indexed subcarrier) of the first PRACH opportunity and the highest frequency (or the included highest indexed subcarrier) of the target sub-band in the frequency domain is not less than a predefined or configured threshold is a condition for the validity of the first PRACH opportunity.

[0430] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: the validity of the first PRACH opportunity depends on the relative position relationship between the first PRACH opportunity in the frequency domain and the target sub-band.

[0431] As an embodiment, the technical feature "the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain" includes: the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain and the position of the first PRACH opportunity in the target sub-band.

[0432] Example 9

[0433] Example 9 illustrates a schematic diagram of a first time domain resource according to an embodiment of the present application, as shown in Figure 9. In Figure 9, the horizontal axis represents the time domain, the rectangular area in the bold frame represents the first time domain resource, the rectangular area filled with slashes represents the start symbol included in the first time domain resource, and the rectangular area filled with cross lines represents the end symbol included in the first time domain resource.

[0434] In Example 9, the second information block in the present application indicates a first time domain resource, and the first time domain resource in the present application includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet the first restriction condition, and the first restriction condition in the present application is related to the symbol type.

[0435] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates the first time domain resource.

[0436] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates at least one time domain symbol included in the first time domain resource.

[0437] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates the starting time domain symbol included in the first time domain resource.

[0438] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates the end time domain symbol included in the first time domain resource.

[0439] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates the number of time domain symbols included in the first time domain resource.

[0440] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: a higher layer mind or a higher layer parameter indicates multiple candidate time domain resources, and all or part of the second information block explicitly or implicitly indicates the first time domain resource from the multiple candidate time domain resources.

[0441] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates the time slot of at least one time domain symbol included in the first time domain resource.

[0442] As an embodiment, the technical feature "the second information block indicates the first time domain resource" includes: all or part of the second information block explicitly or implicitly indicates a SLIV (start length indicator value), and the index of the start symbol included in the first time domain resource and the number of symbols included in the first time domain resource are used to generate the SLIV.

[0443] As an embodiment, the starting symbol included in the first time domain resource is a time domain symbol with the smallest index (or index value) among the at least one time domain symbol included in the first time domain resource.

[0444] As an embodiment, the starting symbol included in the first time domain resource is the earliest time domain symbol indicated as full-duplex by the second information block among the at least one time domain symbol included in the first time domain resource.

[0445] As an embodiment, the starting symbol included in the first time domain resource is a time domain symbol with a largest index (or index value) among at least one time domain symbol included in the first time domain resource.

[0446] As an embodiment, the starting symbol included in the first time domain resource is the time domain symbol that is indicated as full-duplex by the second information block at the latest among the at least one time domain symbol included in the first time domain resource.

[0447] As an embodiment, the first time domain resource includes only one time domain symbol.

[0448] As an embodiment, the first time domain resource includes multiple time domain symbols.

[0449] As an embodiment, any symbol included in the first time domain resource is an OFDM symbol.

[0450] As an embodiment, the first time domain resource is a time window including at least one time domain symbol.

[0451] As an embodiment, the first time domain resources include continuous time domain symbols.

[0452] As an embodiment, the first time domain resource includes periodic time domain symbols.

[0453] As an embodiment, the first time domain resource includes non-periodic time domain symbols.

[0454] As an embodiment, the symbol types of all time domain symbols included in the first time domain resources are the same.

[0455] As an embodiment, the first time domain resources include time domain symbols of different symbol types.

[0456] As an embodiment, all time domain symbols included in the first time domain resources are SBFD symbols.

[0457] As an embodiment, the first time-domain symbol set includes only SBFD symbols, which can simplify the design and ensure performance.

[0458] As an embodiment, the symbol type of any time domain symbol included in the first time domain resource is one of a full-duplex symbol and a non-full-duplex symbol.

[0459] As an embodiment, all time domain symbols included in the first time domain resources are symbols indicated as SBFD symbols by the second information block.

[0460] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource only includes at least one full-duplex symbol.

[0461] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource includes at least one full-duplex symbol indicated by the second information block.

[0462] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource only includes at least one full-duplex symbol indicated by the second information block.

[0463] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource includes the time domain symbol occupied (or mapped or overlapped) by at least one full-duplex symbol indicated by the second information block.

[0464] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the set of time domain symbols occupied (mapped or overlapped) by at least one full-duplex symbol indicated by the second information block is the first time domain resource.

[0465] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the at least one full-duplex symbol indicated by the second information block occupies (or maps) all time domain symbols in the first time domain resource.

[0466] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource includes at least one full-duplex symbol indicated by the second information block and two non-full-duplex symbols adjacent to the at least one full-duplex symbol indicated by the second information block.

[0467] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the first time domain resource includes at least one full-duplex symbol indicated by the second information block, a non-full-duplex symbol closest to the at least one full-duplex symbol indicated by the second information block, and a non-full-duplex symbol closest to the at least one full-duplex symbol indicated by the second information block.

[0468] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: the number of time domain symbols included in the first time domain resource is equal to the number of time domain symbols occupied (or mapped or overlapped) by at least one full-duplex symbol indicated by the second information block plus 2.

[0469] As an embodiment, the technical feature "the first time domain resource includes at least one full-duplex symbol" includes: at least one full-duplex symbol occupies (or maps) part of the time domain symbols in the first time domain resource.

[0470] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: indicating that the second information block of the first time domain resource needs to ensure that the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition.

[0471] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: the user equipment expects (expect) or assumes (assume) that the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition.

[0472] As an embodiment, the technical feature "the start symbol included in the first time domain resource and the end symbol included in the first time domain resource satisfy the first restriction condition" includes: the user equipment does not expect (expect) or assume (assume) that the start symbol included in the first time domain resource and the end symbol included in the first time domain resource violate the first restriction condition.

[0473] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfying the first restriction condition is one of the necessary conditions for the validity of the first time domain resource.

[0474] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the condition for the validity of the first time domain resource includes that the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition.

[0475] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the validity of the first time domain resource depends on whether the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition.

[0476] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition and are used to determine the validity of the first time domain resource.

[0477] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: when the previous symbol of the starting symbol included in the first time domain resource is a downlink symbol indicated by a non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a downlink symbol indicated by a non-full-duplex TDD uplink and downlink configuration, the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource do not satisfy the first restriction condition.

[0478] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0479] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0480] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0481] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0482] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource meet the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0483] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0484] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: the previous symbol of the starting symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0485] As an embodiment, the technical feature "the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource satisfy the first restriction condition" includes: when the starting symbol included in the first time domain resource is a downlink symbol indicated by a non-full-duplex TDD uplink and downlink configuration and the ending symbol included in the first time domain resource is a downlink symbol indicated by a non-full-duplex TDD uplink and downlink configuration, the starting symbol included in the first time domain resource and the ending symbol included in the first time domain resource do not satisfy the first restriction condition.

[0486] As an embodiment, the first restriction condition is predefined.

[0487] As an embodiment, the first restriction condition is configurable.

[0488] As an embodiment, the first restriction condition is a default one.

[0489] As an embodiment, the first restriction condition is configured on the network side.

[0490] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition depends on the symbol type.

[0491] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the symbol type is used to determine the first restriction condition.

[0492] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the symbol type in the first restriction condition includes one of a full-duplex symbol and a non-full-duplex symbol.

[0493] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes at least one of the uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, and the flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0494] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes at least one of the downlink symbol indicated by the full-duplex TDD uplink and downlink configuration, the flexible symbol indicated by the full-duplex TDD uplink and downlink configuration, the uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration, and the flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0495] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0496] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0497] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0498] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0499] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0500] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0501] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the starting symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration and the next symbol of the ending symbol included in the first time domain resource is an uplink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0502] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the previous symbol of the start symbol included in the first time domain resource and the next symbol of the end symbol included in the first time domain resource cannot both be downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration.

[0503] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition does not include the situation where the previous symbol of the start symbol included in the first time domain resource and the next symbol of the end symbol included in the first time domain resource are both downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration.

[0504] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the previous symbol of the start symbol included in the first time domain resource and the next symbol of the end symbol included in the first time domain resource are both downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration, which are inconsistent with (or exclusive of) the first restriction condition.

[0505] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the number of downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration, in which the previous symbol of the start symbol included in the first time domain resource and the next symbol of the end symbol included in the first time domain resource in the first restriction condition are no more than 1.

[0506] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the previous symbol of the start symbol included in the first time domain resource in the first restriction condition and the next symbol of the end symbol included in the first time domain resource are downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration, and the number of symbols is 0 or 1.

[0507] As an embodiment, the technical feature "the first restriction condition is related to the symbol type" includes: the first restriction condition includes that the start symbol included in the first time domain resource and the end symbol included in the first time domain resource cannot both be downlink symbols indicated by the non-full-duplex TDD uplink and downlink configuration.

[0508] Example 10

[0509] Embodiment 10 illustrates a schematic diagram of a first capability information block according to the present application, as shown in FIG10. In FIG10, the first capability information block indicates the maximum number of conversions supported, which depends on the number of uplink and downlink conversions and the number of symbol conversions.

[0510] In embodiment 10, the first capability information block in this application indicates the maximum number of conversions supported by the sender of the first capability information block. The maximum number of conversions in this application depends on the number of uplink and downlink conversions and the number of symbol conversions.

[0511] As an embodiment, a new information block is introduced to indicate the maximum number of conversions supported, thereby increasing flexibility and improving the robustness of the system.

[0512] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: part or all of the first capability information block is used to explicitly or implicitly indicate the maximum number of conversions supported by the sender of the first capability information block.

[0513] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: the sender of the first capability information block is a device that supports SBFD, and the maximum number of conversions of the device that supports SBFD depends on the first capability information block.

[0514] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: a parameter or field included in the first capability information block is used to indicate the maximum number of conversions supported by the sender of the first capability information block.

[0515] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: part or all of the first capability information block is used to display or implicitly indicate the maximum number of conversions supported by the sender of the first capability information block within a certain time period.

[0516] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: part or all of the first capability information block is used to display or implicitly indicate the maximum conversion capability supported by the sender of the first capability information block.

[0517] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: part or all of the first capability information block is used to explicitly or implicitly indicate that the number of conversions of the sender of the first capability information block cannot exceed the maximum number of conversions supported.

[0518] As an embodiment, the technical feature "the first capability information block indicates the maximum number of conversions supported by the sender of the first capability information block" includes: part or all of the first capability information block is used to explicitly or implicitly indicate that the sender of the first capability information block does not support (or does not expect) more than the maximum number of conversions supported.

[0519] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the maximum number of conversions is related to the number of uplink and downlink conversions and the number of symbol conversions.

[0520] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the number of uplink and downlink conversions and the number of symbol conversions are used to determine (or calculate) the maximum number of conversions.

[0521] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions within a certain time period.

[0522] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the value of the maximum number of conversions depends on the value of the number of uplink and downlink conversions and the value of the symbol conversion number within a certain time period.

[0523] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the maximum number of conversions is equal to the sum of the maximum number of conversions and the number of symbol conversions within a certain time period.

[0524] As an embodiment, the technical feature "the maximum number of conversions depends on the uplink and downlink conversions and the symbol conversions" includes: the maximum number of conversions is equal to the larger value of the maximum number of conversions and the symbol conversions within a certain time period.

[0525] As an embodiment, the technical feature "the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions" includes: the maximum number of conversions is equal to the sum of the maximum number of conversions and the number of symbol conversions within a certain time period minus a first value, and the first value is the number of times the uplink and downlink conversions and symbol conversions overlap within a certain time period, or the first value is the number of times the uplink and downlink conversions and symbol conversions occur simultaneously within a certain time period.

[0526] As an embodiment, the number of uplink and downlink conversions is a non-negative integer.

[0527] As an embodiment, the number of uplink and downlink conversions is the number of conversions from downlink reception to uplink transmission.

[0528] As an embodiment, the number of uplink and downlink conversions is the number of conversions from downlink reception to uplink transmission within a certain time period.

[0529] As an embodiment, within a certain time period, when the first time domain symbol of two adjacent time domain symbols is used for downlink reception and the second time domain symbol of two adjacent time domain symbols is used for uplink transmission, the uplink-downlink conversion count is increased by one.

[0530] As an embodiment, within a certain time period, when the next non-guard interval time domain symbol of a downlink symbol indicated by any non-full-duplex TDD uplink and downlink configuration is used for uplink transmission, the value of the uplink and downlink conversion count is increased by one. As a subsidiary embodiment of this embodiment, the guard interval time domain symbol refers to the flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration. As a subsidiary embodiment of this embodiment, the non-guard interval time domain symbol refers to a time domain symbol that is not a flexible symbol indicated by the non-full-duplex TDD uplink and downlink configuration. As a subsidiary embodiment of this embodiment, when the next non-guard interval time domain symbol of a downlink symbol indicated by any non-full-duplex TDD uplink and downlink configuration is the uplink symbol indicated by the TDD uplink and downlink configuration, the value of the uplink and downlink conversion count is increased by one. As a subsidiary embodiment of this embodiment, when the next non-guard interval time domain symbol of a downlink symbol indicated by any non-full-duplex TDD uplink and downlink configuration is the downlink symbol indicated by the full-duplex TDD uplink and downlink configuration, the value of the uplink and downlink conversion count is increased by one. As a subsidiary embodiment of this embodiment, when the time domain symbol of the next non-protection interval of the downlink symbol indicated by any non-full-duplex TDD uplink and downlink configuration is a flexible symbol indicated by the full-duplex TDD uplink and downlink configuration, the uplink and downlink conversion count value is increased by one.

[0531] As an embodiment, within a certain time period, when the previous non-guard interval time domain symbol of any time domain symbol used for uplink transmission is used for downlink transmission, the value of the uplink-downlink conversion count is increased by one. As a subsidiary embodiment of this embodiment, the guard interval time domain symbol refers to a flexible symbol indicated by a non-full-duplex TDD uplink-downlink configuration. As a subsidiary embodiment of this embodiment, the non-guard interval time domain symbol refers to a time domain symbol that is not a flexible symbol indicated by a non-full-duplex TDD uplink-downlink configuration. As an subsidiary embodiment of this embodiment, the any time domain symbol used for uplink transmission is an uplink symbol indicated by the TDD uplink-downlink configuration. As an subsidiary embodiment of this embodiment, the any time domain symbol used for uplink transmission is a downlink symbol indicated by a full-duplex TDD uplink-downlink configuration. As an subsidiary embodiment of this embodiment, the any time domain symbol used for uplink transmission is a flexible symbol indicated by a full-duplex TDD uplink-downlink configuration. As a subsidiary embodiment of this embodiment, any one of the time domain symbols used for uplink transmission is one of the uplink symbols indicated by the TDD uplink and downlink configuration, the downlink symbols indicated by the TDD uplink and downlink configuration, or the flexible symbols indicated by the full-duplex TDD uplink and downlink configuration.

[0532] As an embodiment, the number of sign conversions is a non-negative integer.

[0533] As an embodiment, the number of symbol conversions is no more than 2 within a certain time period.

[0534] As an embodiment, the number of symbol conversions depends on the time domain position of at least one full-duplex symbol indicated by the second information block.

[0535] As an embodiment, the number of symbol conversions is the number of conversions between full-duplex symbols and non-full-duplex symbols within a certain time period.

[0536] As an embodiment, the number of symbol conversions depends on the number of times full-duplex symbols are converted into non-full-duplex symbols and the number of times non-full-duplex symbols are converted into full-duplex symbols within a certain time period.

[0537] As an embodiment, the number of symbol conversions is the sum of the number of times full-duplex symbols are converted into non-full-duplex symbols and the number of times non-full-duplex symbols are converted into full-duplex symbols within a certain time period.

[0538] As an embodiment, within a certain time period, when the symbol type of the time domain symbol is converted from a full-duplex symbol to a non-full-duplex symbol, or from a non-full-duplex symbol to a full-duplex symbol, the value of the symbol conversion times is increased by one.

[0539] As an embodiment, within a certain time period, when the symbol types of two adjacent time-domain symbols are the same, the value of the number of symbol conversions remains unchanged. As a subsidiary embodiment of this embodiment, the symbol types of the two adjacent time-domain symbols are both full-duplex symbols. As a subsidiary embodiment of this embodiment, the symbol types of the two adjacent time-domain symbols are both non-full-duplex symbols.

[0540] In one embodiment, the number of symbol transitions is the number of transition points within a certain time period. As a subsidiary embodiment of this embodiment, the symbol types of two adjacent time-domain symbols at the transition point are different. As a subsidiary embodiment of this embodiment, the symbol types of the time-domain symbol preceding the transition point and the time-domain symbol following the transition point are different.

[0541] Example 11

[0542] Embodiment 11 illustrates a schematic diagram of mapping multiple PRACH opportunities and synchronized broadcast signals according to an embodiment of the present application, as shown in FIG11. As shown in FIG11, each rectangle represents a transmission of a synchronized broadcast signal, the number therein represents the index value of the synchronized broadcast signal, the upper dotted oval represents a PRACH opportunity located in a full-duplex symbol, and the lower dotted oval represents a PRACH opportunity located in a non-full-duplex symbol.

[0543] In embodiment 11, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain among the multiple PRACH opportunities in the present application are respectively mapped to synchronized broadcast signals.

[0544] As an embodiment, PRACH opportunities and synchronous broadcast signals in full-duplex symbols and non-full-duplex symbols are mapped separately, thereby improving PRACH capacity while avoiding adverse effects on other users and ensuring backward compatibility.

[0545] As an embodiment, the synchronous broadcast signal is a synchronization signal.

[0546] As an embodiment, the synchronization broadcast signal is a physical broadcast channel (PBCH).

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

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

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

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

[0551] As an embodiment, the PRACH opportunity located in the full-duplex symbol includes: PRACH opportunities in which all occupied (or mapped) time domain resources are located in the full-duplex symbol.

[0552] As an embodiment, the PRACH opportunities located in the full-duplex symbol include: all occupied (or mapped) time domain resources and PRACH opportunities that overlap between the full-duplex symbols.

[0553] As an embodiment, the PRACH opportunity located in the full-duplex symbol includes: a PRACH opportunity that only occupies the full-duplex symbol in the time domain.

[0554] As an embodiment, the PRACH opportunity located in the full-duplex symbol includes: a PRACH opportunity located in a downlink symbol or a flexible symbol indicated by a full-duplex TDD uplink and downlink configuration.

[0555] As an embodiment, the PRACH opportunity located in the non-full-duplex symbol includes: PRACH opportunities in which all occupied (or mapped) time domain resources are located in the non-full-duplex symbol.

[0556] As an embodiment, the PRACH opportunities located in the non-full-duplex symbols include: all occupied (or mapped) time domain resources and PRACH opportunities that overlap between the non-full-duplex symbols.

[0557] As an embodiment, the PRACH opportunity located in the non-full-duplex symbol includes: a PRACH opportunity that only occupies the non-full-duplex symbol in the time domain.

[0558] As an embodiment, the PRACH opportunity located in the non-full-duplex symbol includes: a PRACH opportunity located in an uplink symbol or a flexible symbol indicated by a non-full-duplex TDD uplink / downlink configuration.

[0559] As an embodiment, the technical feature of "PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are respectively mapped to synchronized broadcast signals" includes: PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are independently mapped to synchronized broadcast signals.

[0560] As an embodiment, the technical feature of "PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are each mapped to a synchronized broadcast signal" includes: PRACH opportunities in the multiple PRACH opportunities that are located in downlink or flexible symbols indicated by the full-duplex TDD uplink and downlink configuration in the time domain and PRACH opportunities in flexible or uplink symbols indicated by the non-full-duplex TDD uplink and downlink configuration are each mapped to a synchronized broadcast signal.

[0561] As an embodiment, the technical feature "PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols and PRACH opportunities in non-full-duplex symbols in the time domain are each mapped to a synchronized broadcast signal" includes: PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols and PRACH opportunities in non-full-duplex symbols in the time domain are each mapped to a synchronized broadcast signal within a time window. As a subsidiary embodiment of the above embodiment, the advantage of doing so is that the existing association period design is retained, reducing the standard workload.

[0562] As an embodiment, the technical feature "PRACH opportunities in the time domain located in full-duplex symbols and PRACH opportunities in non-full-duplex symbols among the multiple PRACH opportunities are respectively mapped to synchronized broadcast signals" includes: PRACH opportunities in the time domain located in downlink or flexible symbols indicated by the full-duplex TDD uplink and downlink configuration and PRACH opportunities in the flexible or uplink symbols indicated by the non-full-duplex TDD uplink and downlink configuration among the multiple PRACH opportunities are respectively mapped to synchronized broadcast signals in their respective time windows. As an auxiliary embodiment of the above embodiment, the benefit of doing so is that an independent association period is adopted for the PRACH opportunities in the downlink full-duplex symbols, thereby improving flexibility and optimizing PRACH capacity performance.

[0563] As an embodiment, the technical feature of "the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the PRACH opportunities that are located in non-full-duplex symbols are respectively mapped to the synchronous broadcast signal" includes: the mapping of the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the synchronous broadcast signal and the mapping of the PRACH opportunities located in non-full-duplex symbols and the synchronous broadcast signal do not affect each other.

[0564] As an embodiment, the technical feature of "the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the PRACH opportunities that are located in non-full-duplex symbols are each mapped to the synchronous broadcast signal" includes: the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the PRACH opportunities that are located in non-full-duplex symbols are each mapped to the index of the synchronous broadcast signal.

[0565] As an embodiment, the technical feature of "PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are each mapped to a synchronized broadcast signal" includes: PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are each mapped according to the same sorting rules and the index of the synchronized broadcast signal.

[0566] As an embodiment, the technical feature of "the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the PRACH opportunities that are located in non-full-duplex symbols are each mapped to a synchronized broadcast signal" includes: the PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and the PRACH opportunities that are located in non-full-duplex symbols are each independently sorted and then mapped to a synchronized broadcast signal.

[0567] As an embodiment, the technical feature of "PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain and PRACH opportunities located in non-full-duplex symbols are respectively mapped to the synchronous broadcast signal" includes: PRACH opportunities in the multiple PRACH opportunities that are located in full-duplex symbols in the time domain are associated with the synchronous broadcast signal in sequence according to a given order, and PRACH opportunities located in non-full-duplex symbols are also associated with the synchronous broadcast signal in sequence according to a given order.

[0568] As an embodiment, the technical feature of "the PRACH opportunities in the multiple PRACH opportunities that are located in the full-duplex symbol in the time domain and the PRACH opportunities that are located in the non-full-duplex symbol are respectively mapped to the synchronous broadcast signal" includes: the synchronous broadcast block index and the PRACH opportunities that are located in the full-duplex symbol in the time domain are mapped in sequence according to the mapping order of first the leading index in a PRACH opportunity, then the frequency resource index of the frequency-divided PRACH opportunity, then the time domain resource index of the time-divided PRACH opportunity in a PRACH time slot, and finally the index of the PRACH time slot; the synchronous broadcast block index and the PRACH opportunities that are located in the non-full-duplex symbol are mapped in sequence according to the mapping order of first the leading index in a PRACH opportunity, then the frequency resource index of the frequency-divided PRACH opportunity, then the time domain resource index of the time-divided PRACH opportunity in a PRACH time slot, and finally the index of the PRACH time slot.

[0569] As an embodiment, the technical feature of "the PRACH opportunities in the multiple PRACH opportunities that are located in the full-duplex symbol in the time domain and the PRACH opportunities that are located in the non-full-duplex symbol are respectively mapped to the synchronous broadcast signal" includes: the synchronous broadcast blocks are mapped in sequence according to the indexes of 0, 1... and the PRACH opportunities that are located in the full-duplex symbol in the time domain in the order of first the leading index in a PRACH opportunity, then the frequency resource index of the frequency-divided PRACH opportunity, then the time domain resource index of the time-divided PRACH opportunity in a PRACH time slot, and finally the index of the PRACH time slot; the synchronous broadcast blocks are mapped in sequence according to the indexes of 0, 1... and the PRACH opportunities that are located in the non-full-duplex symbol in the order of first the leading index in a PRACH opportunity, then the frequency resource index of the frequency-divided PRACH opportunity, then the time domain resource index of the time-divided PRACH opportunity in a PRACH time slot, and finally the index of the PRACH time slot.

[0570] Example 12

[0571] Embodiment 12 illustrates a structural block diagram of a processing device in a first node according to an embodiment, as shown in FIG12 . In FIG12 , the processing device 1200 in the first node includes a first receiver 1201 and a first transmitter 1202. The first receiver 1201 includes the transmitter / receiver 456 (including the antenna 460), the receive processor 452, and the controller / processor 490 in FIG4 of this application; the first transmitter 1202 includes the transmitter / receiver 456 (including the antenna 460), the transmit processor 455, and the controller / processor 490 in FIG4 of this application.

[0572] In embodiment 12, the first receiver 1201 receives a first information block and a second information block, the first information block indicating multiple PRACH opportunities; the second information block indicating at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0573] As an embodiment, the target interval depends on a larger value compared between a first interval and a second interval, wherein the first interval is related to the subcarrier spacing of the random access preamble and the second interval is configured or predefined.

[0574] As an embodiment, the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronization broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0575] As an embodiment, the second information block indicates a target sub-band, and the target sub-band includes at least one resource block; the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0576] As an embodiment, the second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet a first restriction condition, and the first restriction condition is related to the symbol type.

[0577] As an embodiment, the first transmitter 1202 sends a first capability information block, where the first capability information block indicates a maximum number of conversions supported by the sender of the first capability information block, where the maximum number of conversions depends on the number of uplink and downlink conversions and the number of symbol conversions.

[0578] As an embodiment, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain among the multiple PRACH opportunities are respectively mapped to the synchronous broadcast signal.

[0579] Example 13

[0580] Embodiment 13 illustrates a structural block diagram of a processing device in a second node according to an embodiment, as shown in FIG13 . In FIG13 , the processing device 1300 in the second node includes a second transmitter 1301 and a second receiver 1302. The second transmitter 1301 includes the transmitter / receiver 416 (including the antenna 460), the transmit processor 415, and the controller / processor 440 in FIG4 of this application; the second receiver 1302 includes the transmitter / receiver 416 (including the antenna 460), the receive processor 412, and the controller / processor 440 in FIG4 of this application.

[0581] In embodiment 13, the second transmitter 1301 sends a first information block and a second information block, wherein the first information block indicates multiple PRACH opportunities; the second information block indicates at least one full-duplex symbol; wherein the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

[0582] As an embodiment, the target interval depends on a larger value compared between a first interval and a second interval, wherein the first interval is related to the subcarrier spacing of the random access preamble and the second interval is configured or predefined.

[0583] As an embodiment, the validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before the synchronization broadcast signal in the PRACH time slot to which it belongs, nor before the downlink symbol indicated by the non-full-duplex TDD uplink and downlink configuration.

[0584] As an embodiment, the second information block indicates a target sub-band, and the target sub-band includes at least one resource block; the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

[0585] As an embodiment, the second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet a first restriction condition, and the first restriction condition is related to the symbol type.

[0586] As an embodiment, the second receiver 1302 receives a first capability information block, where the first capability information block indicates a maximum number of conversions supported by a sender of the first capability information block, where the maximum number of conversions depends on an uplink and downlink number of conversions and a symbol number of conversions.

[0587] As an embodiment, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain among the multiple PRACH opportunities are respectively mapped to the synchronous broadcast signal.

[0588] Those skilled in the art will appreciate that all or part of the steps in the above method can be performed 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, the various module units in the above embodiment can be implemented in the form of hardware or software functional modules. This application is not limited to any specific combination of software and hardware. The first node or second node or UE or terminal in this application includes but is not limited to mobile phones, tablets, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft, test equipment, test instruments, and other equipment. The base station equipment or base station or network-side equipment in this application includes but is not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, eNBs, gNBs, transmission and reception nodes (TRPs), relay satellites, satellite base stations, aerial base stations, test equipment, test instruments, and other equipment.

[0589] Those skilled in the art will appreciate that the present invention may be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should be considered in all respects as illustrative and not restrictive. The scope of the invention is determined by the appended claims, not the foregoing description, and all modifications that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node used for wireless communication, characterized in that: include: a first receiver configured to receive a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; The second information block indicates at least one full-duplex symbol; Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

2. The first node according to claim 1, wherein: The target interval depends on a larger value compared between a first interval and a second interval, wherein the first interval is related to the subcarrier spacing of the random access preamble and the second interval is configured or predefined.

3. The first node according to any one of claims 1 or 2, characterized in that The validity of the first PRACH opportunity also depends on the fact that the first PRACH opportunity is not located before a synchronization broadcast signal in the PRACH time slot to which it belongs, nor is it located before a downlink symbol indicated by a non-full-duplex TDD uplink and downlink configuration.

4. The first node according to any one of claims 1 to 3, characterized in that: The second information block indicates a target sub-band, and the target sub-band includes at least one resource block; the validity of the first PRACH opportunity depends on whether the first PRACH opportunity belongs to the target sub-band in the frequency domain.

5. The first node according to any one of claims 1 to 4, characterized in that: The second information block indicates a first time domain resource, and the first time domain resource includes at least one full-duplex symbol; the start symbol included in the first time domain resource and the end symbol included in the first time domain resource meet a first restriction condition, and the first restriction condition is related to the symbol type.

6. The first node according to any one of claims 1 to 5, characterized in that: The system comprises a first transmitter, which sends a first capability information block, wherein the first capability information block indicates a maximum number of conversions supported by the sender of the first capability information block, and the maximum number of conversions depends on an uplink and downlink conversion number and a symbol conversion number.

7. The first node according to any one of claims 1 to 6, characterized in that: Among the multiple PRACH opportunities, the PRACH opportunities located in full-duplex symbols and the PRACH opportunities located in non-full-duplex symbols in the time domain are respectively mapped to the synchronous broadcast signal.

8. A second node used for wireless communication, characterized in that: include: a second transmitter transmitting a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; The second information block indicates at least one full-duplex symbol; Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

9. A method in a first node for wireless communication, characterized in that: include: receiving a first information block and a second information block, the first information block indicating a plurality of PRACH opportunities; The second information block indicates at least one full-duplex symbol; Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

10. A method used in a second node of wireless communication, characterized in that: include: sending a first information block and a second information block, wherein the first information block indicates a plurality of PRACH opportunities; The second information block indicates at least one full-duplex symbol; Among them, the first PRACH opportunity is one of the multiple PRACH opportunities indicated by the first information block, and the first PRACH opportunity occupies at least one full-duplex symbol in the time domain; the validity of the first PRACH opportunity depends on the time interval between the first PRACH opportunity and the first symbol being greater than the target interval, and the target interval is related to the subcarrier interval of the random access preamble; the first symbol is a downlink symbol indicated by the previous non-full-duplex TDD uplink and downlink configuration.

Images