Detailed Description
The technical scheme of the present application will be described in further detail with reference to the accompanying drawings, and it should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be arbitrarily combined with each other.
Example 1
Embodiment 1 illustrates a flow chart of a first information block, a second information block and a third information block according to an embodiment of the application, as shown in fig. 1. In fig. 1, each block represents a step. In particular, the order of steps in the blocks does not represent a particular chronological relationship between the individual steps.
In embodiment 1, the terminal 100 in the present application receives a first information block in step 101, the first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, receives a second information block in step 102, the second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein the first RO is one RO included in the first set of ROs occupying at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain, and the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set, the target SSB index set including SSB indices of the second set overlapping with at least one RO associated with the first RO in the time domain.
As an embodiment, the first information block includes part or all of the fields included in one SIB.
As an embodiment, the first information block is Cell Common (Cell Common).
As an embodiment, the first information block is cell specific (CELL SPECIFIC).
As an embodiment, the first information block is Group Common (Group Common).
As an embodiment, the first information block is user equipment specific (UE specific or UE decoded).
As an embodiment, the first information block is configured per subband (per subband).
As an embodiment, the first information block is configured Per bandwidth Part (Per BWP).
As an embodiment, the first information block includes some or all of the fields in IE "SBFDConfigDedicated-r 19".
As an embodiment, the first information block includes some or all of the fields in IE "SBFDConfigCommon-r 19".
As an embodiment, the first information block includes some or all of the fields in IE "SBFDConfig-r 19".
As an embodiment, the first information block includes some or all of the fields in IE "ServingCellConfigCommon".
As an embodiment, the first information block includes some or all of the fields in IE "CellGroupConfig".
As an embodiment, the first information block includes some or all of the fields in IE "SpCellConfig".
As an embodiment, the first information block includes some or all of the fields in IE "SCellConfig".
As an embodiment, the first information block includes some or all of the fields in IE "ServingCellConfigCommonSIB".
As an embodiment, the first information block includes some or all of the fields in IE "ServingCellConfig".
As an embodiment, the first information block includes some or all of the fields in IE "UplinkConfig".
As an embodiment, the first information block includes part or all of the fields in the IE "TDD-UL-DL-ConfigCommon".
As an embodiment, the first information block is used to configure SBFD (Subband non-overlapping Full Duplex, non-overlapping Subband full duplex) time slots or symbols.
As an embodiment, the first information block is used to configure a slot or symbol supporting full duplex.
As an embodiment, the first information block configures an uplink sub-band (UL subband) and a downlink sub-band (DL subband) of SBFD.
As an example, the number of possible symbol types for one symbol is equal to 2.
As an example, the number of possible symbol types for one symbol is greater than 2.
As an embodiment, the symbol type of one symbol is SBFD symbols or non-SBFD symbols.
As an embodiment, the symbol type of one symbol is a symbol configured with SBFD or a symbol not configured with SBFD.
As an embodiment, the symbol type of one symbol is a symbol in SBFD slots or a symbol in SBFD slots.
For one embodiment, the symbol type of one symbol is a symbol in which a subband of SBFD is configured in the time domain or a symbol in which a subband of SBFD is not configured in the time domain.
As an embodiment, the symbol type of one symbol is a time domain symbol supporting full duplex or a symbol not supporting full duplex.
As an example, the symbol type of one symbol is a symbol to which SBFD applies or a symbol to which SBFD does not apply.
As an embodiment, the symbol type of one symbol is a symbol that can be used for both uplink and downlink transmission or a symbol that cannot be used for both uplink and downlink transmission.
As an embodiment, the symbol type of one symbol is SBFD symbols or other types of symbols indicated as downlink by the TDD uplink-downlink configuration.
As an embodiment, the symbol type of one symbol is one of SBFD symbols indicated as downlink by TDD uplink and downlink configuration, SBFD symbols indicated as flexible by TDD uplink and downlink configuration, symbols indicated as uplink by TDD uplink and downlink configuration, non-SBFD symbols indicated as flexible by TDD uplink and downlink configuration, and non-SBFD symbols indicated as downlink by TDD uplink and downlink configuration.
As one embodiment, both downstream and flexible symbols are considered, expanding configuration flexibility.
As an embodiment, the symbol type of one symbol is SBFD symbols indicated as downlink by TDD uplink-downlink configuration or uplink or flexible symbols by TDD uplink-downlink configuration.
As an embodiment, only downstream symbols are considered, simplifying the system design.
As an embodiment, the symbol type of one symbol is one of T1 symbol types, said T1 being a positive integer greater than 1, said T1 symbol types being predefined or configurable. As an subsidiary embodiment of the above embodiment, said T1 symbol types include SBFD symbols and non-SBFD symbols. As an subsidiary embodiment of the above embodiment, said T1 symbol types include symbols in which the subbands of SBFD are configured in the time domain and symbols in which the subbands of SBFD are not configured in the time domain. As an subsidiary embodiment of the above embodiment, the T1 symbol types are symbols respectively corresponding to T1 TCI states. As an auxiliary embodiment of the foregoing embodiment, the T1 symbol types are symbols respectively corresponding to T1 radio frequency links. As an subsidiary embodiment of the above embodiment, the T1 symbol types are symbols respectively corresponding to T1 beams (beams). As an subsidiary embodiment of the above embodiment, the T1 symbol types are symbols respectively corresponding to T1 interference cancellation schemes. As an subsidiary embodiment of the above embodiment, the T1 symbol types are symbols respectively corresponding to T1 QCL relations. As an subsidiary embodiment to the above embodiment, said T1 is equal to 2. As an subsidiary embodiment to the above embodiment, said T1 is greater than 2. As an subsidiary embodiment to the above embodiment, said T1 symbol types depend on the capabilities of said terminal. As an subsidiary embodiment of the above embodiment, the terminal cannot be considered to have the same QCL parameters (or QCL hypotheses) in two time domain symbols respectively belonging to different symbol types among the T1 symbol types.
As one embodiment, symbols in the time domain are divided into a plurality of types, and a symbol type of one symbol is one of the plurality of types.
As an embodiment the technical feature that said first information block indicates the symbol type of at least one symbol comprises that all or part of a cell-specific (cell-specific) parameter comprised by said first information block indicates the symbol type of at least one symbol.
As an embodiment the technical feature that said first information block indicates a symbol type of at least one symbol comprises that the symbol type of at least one symbol depends on said first information block.
As an embodiment the technical feature that said first information block indicates the symbol type of the at least one symbol comprises that all or part of said first information block is used for indicating the symbol type of the at least one symbol either explicitly or implicitly.
As an embodiment the technical feature that said first information block indicates the symbol type of at least one symbol comprises that the time domain symbols indicated (or provided) by said first information block are one type of symbol and that the time domain symbols not indicated (or provided) by said first information block are another type of symbol.
As an embodiment the technical feature that the first information block indicates the symbol type of the at least one symbol comprises that the first information block indicates, either explicitly or implicitly, whether the symbol type of the at least one symbol is SBFD symbols or not SBFD symbols.
As an embodiment, the technical feature that the first information block indicates a symbol type of at least one symbol includes that the first information block indicates, either explicitly or implicitly, that the symbol type of at least one symbol is one of SBFD symbols indicated as downlink by TDD uplink-downlink configuration, SBFD symbols indicated as flexible by TDD uplink-downlink configuration, non-SBFD symbols indicated as downlink by TDD uplink-downlink configuration, non-SBFD symbols indicated as flexible by TDD uplink-downlink configuration, and symbols indicated as uplink by TDD uplink-downlink configuration.
As an embodiment, the target subband is a SBFD subband (full duplex subband).
As an embodiment, the target subband is a SBFD subband for uplink.
As an embodiment, the target subband is an uplink SBFD subband.
As an embodiment, the target subband is a subband that can be used for uplink transmission in downlink symbols or flexible symbols.
As an embodiment, the target sub-band comprises guard frequency domain resources (guard).
As an embodiment, the target sub-band does not include guard frequency domain resources.
As an embodiment, the target sub-band comprises contiguous frequency domain resources.
As an embodiment, one uplink BWP comprises all or part of the frequency domain resources in the target sub-band. As an attached embodiment of the foregoing embodiment, the target sub-band belongs to the uplink BWP, which can reuse the existing design to the greatest extent and reduce design complexity.
As an embodiment, the BWP of an uplink active includes all or part of the frequency domain resources in the target sub-band. As an auxiliary embodiment of the foregoing embodiment, the uplink active BWP includes a sub-band configuration where a portion of resources in the target sub-band may support a carrier level, so as to increase flexibility.
As an embodiment, in one time domain symbol, there is overlapping frequency domain resource between the target sub-band and the active uplink BWP.
As an embodiment, in one time domain symbol, there is no overlapping frequency domain resource between the target sub-band and the active uplink BWP.
As an embodiment, the boundary of RBs (Resource blocks) included in the target sub-band is aligned with the boundary of RBs in the uplink BWP. As an auxiliary embodiment of the embodiment, uplink resource fragments are avoided, and coverage is improved.
As an embodiment, the target sub-band is per (per) mathematical structure (numerology) or per sub-carrier spacing.
As an embodiment, the target sub-band is per (per) resource grid (resource grid). As an subsidiary embodiment of the above embodiment, configuring subbands per grid improves configuration flexibility.
As an embodiment, the target sub-band is per BWP. As an subsidiary embodiment of the above embodiment, configuring sub-bands per BWP ensures compatibility, reducing standard complexity.
As one embodiment, the boundary of the RB included in the target sub-band is aligned with the boundary of the RB in the downlink BWP. As an auxiliary embodiment of the embodiment, downlink resource fragments are avoided, and scheduling flexibility is ensured.
As an embodiment the technical feature that said first information block indicates a target sub-band comprises that all or part of said first information block comprises explicitly or implicitly indicating said target sub-band.
As an embodiment, the technical feature that the first information block indicates a target subband includes that the first information block indicates a starting RB (or lowest indexed RB) of the target subband.
As an embodiment, the technical feature that the first information block indicates a target subband includes that the first information block indicates the number of RBs included in the target subband.
As an embodiment, the technical feature that the first information block indicates a target sub-band includes that the first information block indicates an RIV (resource indicator value, resource indication value) corresponding to the target sub-band.
As an embodiment the technical feature that the first information block indicates a target sub-band comprises that the first information block indicates an RIV to which the target sub-band corresponds, the starting RB of the target sub-band and the number of consecutive RBs comprised being used for generating the corresponding RIV.
As an embodiment, the technical feature that the first information block indicates a target subband includes that the first information block indicates SLIV (START AND LENGTH indicator value, starting length indicator value) corresponding to the target subband.
As an embodiment, the technical feature that the first information block indicates a target subband includes that the first information block indicates SLIV corresponding to the target subband, and that a starting RB of the target subband and a number of included consecutive RBs are used to generate the corresponding SLIV.
As an embodiment the technical feature that said first information block indicates a target sub-band comprises that said first information block indicates at least one CRB (common resourceblock ) for one subcarrier spacing comprised by said target sub-band.
As an embodiment the technical feature that said first information block indicates a target sub-band comprises that said first information block indicates the number of CRBs spaced between the lowest indexed CRB comprised by said target sub-band and frequency point a (pointA) and the number of consecutive CRBs comprised by said target sub-band.
As an embodiment the technical feature that the first information block indicates a target sub-band comprises that all or part of the first information block comprises explicitly or implicitly indicates the number of CRBs for a reference sub-carrier interval and the number of consecutive CRBs for the reference sub-carrier interval that are spaced between the lowest indexed CRB and frequency point a (pointA) for the reference sub-carrier interval that are comprised by the target sub-band. As an subsidiary embodiment of the above embodiment, the reference subcarrier spacing is equal to the subcarrier spacing in a resource grid (uplink) of the uplink, and the benefits of doing so include avoiding resource fragmentation. As an additional embodiment of the above embodiment, the reference subcarrier spacing is equal to the subcarrier spacing in a downlink resource grid (resource grid), which has the advantage of improving scheduling flexibility. As an subsidiary embodiment of the above embodiment, said reference subcarrier spacing is related to a Frequency Range (FR). As an subsidiary embodiment to the above embodiments, said reference subcarrier spacing is predefined or configured. As an subsidiary embodiment of the above embodiment, the reference subcarrier spacing is the maximum of the subcarrier spacing for which the plurality of uplink resource grids are configured, respectively, which has the advantage of ensuring alignment with uplink resources. As an subsidiary embodiment of the above embodiment, the reference subcarrier spacing is the maximum of the subcarrier spacing for which the plurality of downlink resource grids are configured, respectively, which has the advantage of ensuring alignment with downlink resources. As an subsidiary embodiment of the above embodiment, the reference subcarrier spacing is the maximum value of the subcarrier spacing for all the configured resource grids respectively, and this has the advantage of ensuring that the uplink and downlink resources can be aligned.
As an embodiment the technical feature that said first information block indicates a target subband comprises that said first information block indicates M1 subbands from M1 resource grids, respectively, said M1 being a positive integer larger than 1, said target subband being one of said M1 subbands. As an subsidiary embodiment of the above embodiment, the M1 resource grids are M1 uplink resource grids, which has the advantage of avoiding fragmentation of uplink resources without increasing signaling overhead. As an subsidiary embodiment of the above embodiment, the M1 resource grids are M1 downlink resource grids, which has the advantage of avoiding fragmentation of downlink resources without increasing signaling overhead. As an adjunct to the above embodiment, the M1 resource grid includes both uplink and downlink resource grids, which has the advantage of considering both uplink and downlink resource allocation but adds some signalling overhead. As an subsidiary embodiment to the above embodiment, said M1 resource grids are configured.
As an embodiment, the second information block includes part or all of the fields included in one SIB.
As an embodiment, the second information block is Cell Common (Cell Common).
As an embodiment, the second information block is cell specific (CELL SPECIFIC).
As an embodiment, the second information block is Group Common (Group Common).
As an embodiment, the second information block is configured per subband (per subband).
As an embodiment, the second information block is configured per carrier (PER CARRIER).
As an embodiment, the second information block is configured Per bandwidth Part (Per BWP).
As an embodiment, the second information block includes part or all of the fields in the IE "SIB 1".
As an embodiment, the second information block includes some or all of the fields in IE "ServingCellConfigCommon".
As an embodiment, the second information block includes some or all of the fields in IE "ServingCellConfigCommonSIB".
As an embodiment, the second information block includes some or all of the fields in IE "UplinkConfigCommon".
As an embodiment, the second information block includes some or all of the fields in IE "UplinkConfigCommonSIB".
As an embodiment, the second information block includes some or all of the fields in the IE "BWP-UplinkCommon".
As an embodiment, the second information block includes part or all of the fields in the IE "RACH-ConfigCommon".
As an embodiment, the second information block includes part or all of the fields in the IE "RACH-ConfigGeneric".
As an embodiment, the second information block includes some or all of the fields in IE "SBFDConfigCommon-r 19".
As an embodiment, the second information block includes some or all of the fields in IE "SBFDConfig-r 19".
As an embodiment, the third information block includes part or all of the fields included in one SIB.
As an embodiment, the third information block is Cell Common (Cell Common).
As an embodiment, the third information block is cell specific (CELL SPECIFIC).
As an embodiment, the third information block is Group Common (Group Common).
As an embodiment, the third information block is configured per subband (per subband).
As an embodiment, the third information block is configured per carrier (PER CARRIER).
As an embodiment, the third information block is configured Per bandwidth Part (Per BWP).
As an embodiment, the third information block includes part or all of the fields in the IE "SIB 1".
As an embodiment, the third information block includes some or all of the fields in IE "ServingCellConfigCommon".
As an embodiment, the third information block includes some or all of the fields in IE "ServingCellConfigCommonSIB".
As an embodiment, the third information block includes some or all of the fields in IE "UplinkConfigCommon".
As an embodiment, the third information block includes some or all of the fields in IE "UplinkConfigCommonSIB".
As an embodiment, the third information block includes some or all of the fields in the IE "BWP-UplinkCommon".
As an embodiment, the third information block includes part or all of the fields in the IE "RACH-ConfigCommon".
As an embodiment, the third information block includes part or all of the fields in the IE "RACH-ConfigGeneric".
As one embodiment, the first RO set comprises a plurality of ROs.
As one embodiment, each RO in the first set of ROs is a Physical Random Access Channel (PRACH) opportunity (Occasion).
As an embodiment, each RO of the first set of ROs comprises an allocated or configured PRACH time-frequency resource.
As an embodiment, each RO of the first set of ROs comprises time-frequency resources occupied by one PRACH transmission.
As an embodiment, each two ROs in the first RO set are time division multiplexed.
As an embodiment, the presence of two ROs in the first RO set comprises the same time domain resource.
As an embodiment, the two ROs in the first RO set comprise different time domain resources.
As an embodiment, there are two PRACH opportunities for frequency division multiplexing (FDM, frequency division multiplexed) in the first RO set.
As an embodiment, each two ROs in the first RO set are for the same preamble (preamble) format. As an subsidiary embodiment to the above-described embodiment, this has the advantage of simple design.
As an embodiment, there are two ROs in the first RO set for different preamble formats. As an adjunct to the above embodiments, this has the advantage of enhancing flexibility.
As an embodiment, each RO in the first RO set occupies at least one SBFD symbols in the time domain.
As an embodiment, each RO in the first RO set occupies SBFD symbols only in the time domain.
As an embodiment, each RO in the first RO set occupies only SBFD symbols indicated as downlink by TDD uplink-downlink configuration or SBFD symbols indicated as flexible by TDD uplink-downlink configuration in the time domain.
As one embodiment, a partial RO present in the first RO set occupies both SBFD symbols and non-SBFD symbols in the time domain, the partial RO being configured by a base station.
As an embodiment, the second set of ROs comprises a plurality of ROs.
As one embodiment, each RO in the second set of ROs is a Physical Random Access Channel (PRACH) opportunity (Occasion).
As an embodiment, each RO of the second set of ROs comprises an allocated or configured PRACH time-frequency resource.
As an embodiment, each RO of the second set of ROs comprises time-frequency resources occupied by one PRACH transmission.
As an embodiment, each two ROs in the second RO set are time division multiplexed.
As an embodiment, each two ROs in the second RO set comprise the same time domain resource.
As an embodiment, each two ROs in the second RO set comprise different time domain resources.
As an embodiment, there are two PRACH opportunities for frequency division multiplexing (FDM, frequency division multiplexed) in the second RO set.
As one embodiment, each RO included in the second RO set is a legacy (legacy) RO.
As an embodiment, each RO included in the second RO set is a RO other than the first RO set.
As an embodiment, each RO included in the second RO set is a RO that does not overlap with a downlink indicated by the TDD uplink-downlink configuration.
As an embodiment, the second set of ROs is orthogonal to the first set of ROs.
As an embodiment, each two ROs in the second RO set are for the same preamble format. As an subsidiary embodiment to the above-described embodiment, this has the advantage of simple design.
As an embodiment, the preamble format for one RO of the first RO set is different from the preamble format for one RO of the second RO set. As an adjunct to the above embodiments, this has the benefit of increasing flexibility and optimizing the coverage performance in SBFD cases.
As an embodiment, the preamble format for each RO in the first RO set is the same as the preamble format for each RO in the second RO set. As an adjunct to the above embodiments, this has the advantage of simple design and reduced implementation complexity.
As an embodiment, each RO in the second RO set occupies only non-SBFD symbols in the time domain.
As an embodiment, each RO in the second RO set occupies only symbols in the time domain that are indicated as uplink or flexible by the TDD uplink configuration.
As an embodiment, each RO in the second RO set occupies a symbol indicated as uplink by TDD uplink configuration, a non-SBFD symbol indicated as flexible by TDD uplink configuration, or a SBFD symbol indicated as flexible by TDD uplink configuration in the time domain.
As an embodiment, all ROs included in the second RO set that overlap in the time domain and at least one SBFD symbol indicated as flexible by TDD uplink and downlink configuration belong to the target subband in the frequency domain.
As an embodiment "the second information block indicates the first set of ROs" comprises that part or all comprised by the second information block is used to indicate the first set of ROs either explicitly or implicitly.
As an embodiment "the second information block indicates a first set of ROs" comprises that the first set of ROs depends on the second information block.
As an embodiment "the second information block indicates a first set of ROs" comprises that the second information block is used to determine the first set of ROs.
As an embodiment, the "the second information block indicates the first set of ROs" comprises the second information block indicating time-frequency resources comprised by at least one RO of the first set of ROs.
As an embodiment, the "the second information block indicates the first set of ROs" comprises the second information block indicating the number of ROs in the first set of ROs that are frequency-divided in the same time domain resource.
As an embodiment, the "the second information block indicates the first RO set" comprises that the second information block indicates a starting frequency domain resource of the lowest PRACH opportunity in the frequency domain in the first RO set.
As an embodiment, "the second information block indicates a first set of ROs" comprises the second information block indicating a PRACH configuration index (configuration index) that configures the first set of ROs.
As an embodiment, the "the second information block indicates a first RO set" comprises that the second information block indicates a PRACH configuration index, and ROs located on full duplex symbols configured by the PRACH configuration index belong to the first RO set.
As an embodiment, the "the second information block indicates a first RO set" comprises that the second information block indicates a PRACH configuration index, and ROs configured by the PRACH configuration index that overlap with full duplex symbols indicated as downlink or flexible by TDD uplink and downlink configuration belong to the first RO set.
As an embodiment "the third information block indicates the second set of ROs" comprises that part or all comprised by the third information block is used to indicate the second set of ROs either explicitly or implicitly.
As an embodiment "the third information block indicates a second set of ROs" comprises that the second set of ROs depends on the third information block.
As an embodiment "the third information block indicates a second set of ROs" comprises that the third information block is used to determine the second set of ROs.
As an embodiment, the "the third information block indicates the second set of ROs" comprises the third information block indicating time-frequency resources comprised by at least one RO of the second set of ROs.
As an embodiment, the "the third information block indicates the second set of ROs" comprises the third information block indicating the number of ROs in the second set of ROs that are frequency-divided in the same time domain resource.
As an embodiment, the "the third information block indicates the second RO set" comprises that the third information block indicates a starting frequency domain resource of the lowest PRACH opportunity in the frequency domain in the second RO set.
As an embodiment, "the third information block indicates a second set of ROs" comprises the third information block indicating a PRACH configuration index (configuration index) that configures the second set of ROs.
As an embodiment, the "the third information block indicates a second RO set" comprises that the third information block indicates a PRACH configuration index, and ROs located on uplink or flexible symbols configured by the PRACH configuration index belong to the second RO set.
As an embodiment, the third information block indicates a second RO set, and the third information block indicates a PRACH configuration index, where ROs configured with a symbol indicated as uplink by TDD uplink configuration, a non-SBFD symbol indicated as flexible by TDD uplink configuration, or a SBFD symbol indicated as flexible by TDD uplink configuration have an overlap belong to the second RO set.
As an embodiment, the full duplex symbol is SBFD symbols.
As an example, the "full duplex" and the "SBFD" are equivalent or alternative.
As an embodiment, the full duplex symbol is an OFDM (Orthogonal Frequency Division Multiplexing ) symbol.
As an embodiment, the full duplex symbol is a time domain symbol configured with SBFD.
As an embodiment, the full duplex symbol is a symbol configured with SBFD subbands.
As an embodiment, the full duplex symbol is a time domain symbol supporting full duplex.
As an embodiment, the full duplex symbol is a time domain symbol to which SBFD is applied.
As an embodiment, the full duplex symbol is a time domain symbol capable of uplink and downlink transmission simultaneously.
As an embodiment, the full duplex symbol is a time domain symbol that can perform uplink transmission and downlink transmission at the network side (or the base station side) at the same time.
As an embodiment, the full duplex symbol is a time domain symbol capable of uplink transmission and downlink transmission at the network side (or the base station side) and the user equipment side simultaneously.
As an embodiment, the full duplex symbol is a time domain symbol indicated (or provided) by signaling of the configuration SBFD.
As an embodiment, the full duplex symbol is a symbol that can be transmitted uplink on a downlink symbol indicated by TDD uplink-downlink configuration.
As an embodiment, only downstream symbols are considered, simplifying the system design.
As an embodiment, the full duplex symbol is a symbol that can be transmitted uplink on a downlink or flexible symbol indicated by the TDD uplink-downlink configuration.
As an embodiment, the full duplex symbol is a symbol that is indicated as downlink by TDD uplink-downlink configuration and is configured (or indicated) as SBFD symbols, or a symbol that is indicated as flexible by TDD uplink-downlink configuration and is configured (or indicated) as SBFD symbols.
As an embodiment, the full duplex symbol is a symbol indicated by the TDD uplink-downlink configuration as downlink and indicated (or provided) by the first information block, or a symbol indicated by the TDD uplink-downlink configuration as flexible and indicated (or provided) by the first information block.
As an embodiment, only TDD uplink and downlink configuration is considered, simplifying design and reducing standard workload.
As one embodiment, both downstream and flexible symbols are considered, expanding configuration flexibility.
As an embodiment, the "the ROs in the first RO set occupy at least one full duplex symbol in the time domain" comprises each RO in the first RO set occupying at least one full duplex symbol in the time domain.
As an embodiment, the technical feature that the RO of the first RO set occupies at least one full duplex symbol in the time domain comprises that the RO of the first RO set occupies at least one full duplex symbol indicated by the first information block in the time domain.
In one embodiment, the technical feature "the ROs in the first RO set occupy at least one full duplex symbol in the time domain" comprises that the ROs in the first RO set are mapped into at least one full duplex symbol in the time domain.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set are located in full duplex symbols in the time domain.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set comprise at least one full duplex symbol in the time domain.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set overlap with at least one full duplex symbol in the time domain.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set all overlap between the time domain and the at least one full duplex symbol.
As an embodiment, the technical feature "the ROs in the first RO set occupy at least one full duplex symbol in the time domain" comprises that the ROs in the first RO set overlap in whole or in part between the time domain and the at least one full duplex symbol.
As an embodiment, the technical feature that the RO in the first RO set occupies at least one full duplex symbol in the time domain includes that the RO in the first RO set occupies at least one full duplex symbol in the time domain indicated as downlink by TDD uplink and downlink configuration.
As an embodiment, the technical feature that the RO in the first RO set occupies at least one full duplex symbol in the time domain includes that the RO in the first RO set occupies at least one full duplex symbol indicated as downlink or flexible by TDD uplink and downlink configuration in the time domain.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set have an overlap between a PRACH slot (slot) to which the time domain belongs and the at least one full duplex symbol.
As an embodiment, the technical feature that the ROs in the first RO set occupy at least one full duplex symbol in the time domain comprises that the ROs in the first RO set overlap between the time domain and a time slot comprising at least one full duplex symbol.
As an embodiment, the "first RO is one RO comprised by the first RO set" comprises that the first RO belongs to the first RO set.
As an embodiment, the "the first RO is one RO included in the first RO set" includes that the first RO is one of a plurality of ROs included in the first RO set.
As an embodiment, the "the first RO is one RO included in the first RO set" includes that the first RO is one of a plurality of ROs included in the first RO set that occupy at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in a time domain.
As an embodiment, the "the first RO is one RO included in the first RO set" includes that the first RO is any one of a plurality of ROs that occupy at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in a time domain included in the first RO set.
As one embodiment, the TDD uplink/downlink configuration is an uplink/downlink TDD configuration that is used to determine slot formats.
As an embodiment, the TDD uplink and downlink configuration at least includes configuration information indicating which symbols in a periodic time window are downlink symbols, which symbols are flexible symbols, and which symbols are uplink symbols.
As an embodiment, the TDD uplink and downlink configuration is a higher layer configuration including at least indication information of a link direction of a symbol.
As an embodiment, the TDD uplink and downlink configuration is an RRC layer configuration.
As an embodiment, the TDD uplink and downlink configuration is a higher layer configuration.
As an embodiment, the TDD uplink and downlink configuration further includes indication information of the employed subcarrier spacing.
As an embodiment, the TDD uplink and downlink configuration further includes indication information of the length of the employed periodic time window.
As an embodiment, the TDD uplink and downlink configuration includes some or all of the fields in the IE "TDD-UL-DL-ConfigCommon".
As an embodiment, the TDD uplink and downlink configuration includes some or all of the fields in the IE "TDD-UL-DL-ConfigDedicated".
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO occupies at least one full duplex symbol indicated by the first information block and indicated as flexible by TDD uplink and downlink configuration in the time domain.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO maps to at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO is located in the full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO includes at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO overlaps between the time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO overlaps all or part of the time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO has overlap between a PRACH slot (slot) to which the time domain belongs and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration.
As an embodiment, the technical feature that the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration in the time domain includes that the first RO overlaps between the time domain and a time slot including at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration.
As an embodiment, the SSB is a synchronization signal block (SSB, synchronization signal block).
As one embodiment, the SSB is a synchronization signal (synchronization signal).
As one embodiment, the SSB is a physical broadcast channel (PBCH, physical broadcast channel).
As one embodiment, the SSB includes a synchronization signal and a physical broadcast channel.
As an embodiment, the SSB is a synchronization signal physical broadcast channel block (SS (Synchronization Signal)/PBCH
(Physical Broadcast Channel)block)。
As an embodiment, the SSB is a 6G synchronization signal or a 6G physical broadcast channel.
As an example, the "SSB" and the "synchronized broadcast signal" are equivalent or alternative.
As one embodiment, the SSB index is a non-negative integer.
As one embodiment, the SSB Index is an Index (Index) of a synchronized broadcast block.
As one embodiment, the SSB index is an index of one synchronized broadcast block among a plurality of synchronized broadcast blocks.
As one embodiment, the SSB index indicates an index of a synchronized broadcast block.
As an embodiment, the SSB index associated with the first RO includes one SSB index.
As one embodiment, the SSB index associated with the first RO includes a plurality of SSB indexes.
As one embodiment, the number of SSB indexes associated with the first RO is 1.
As one embodiment, the number of SSB indexes associated with the first RO is greater than 1.
As one embodiment, the number of SSB indexes associated with the first RO is one of {1,2,4,8,16 }.
As an embodiment, the number of SSB indexes associated with the first RO is smaller than or equal to the value determined by the domain "SSB-PositionsInBurst", or the number of SSB indexes associated with the first RO is smaller than or equal to the number of bits corresponding to the domain "SSB-PositionsInBurst" and is 1.
As an embodiment, the number of SSB indices associated with the first RO depends on the second information block.
As an embodiment, the one field included in the second information block indicates the number of SSB indexes associated with the first RO.
As an embodiment, the field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block indicates the number of SSB indexes associated with the first RO, and the field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" indicates the number of SSBs corresponding to each RO.
As an embodiment, the field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block is used to determine (or is used to calculate) the number of SSB indices associated with the first RO.
As an embodiment, the number of SSB indexes associated with the first RO is N, and the N depends on a domain "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" included in the second information block.
As one embodiment, the second information block includes a field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" having a value of N, and when N is greater than 1, the number of SSB indexes associated with the first RO is N, and when N is less than or equal to 1, the number of SSB indexes associated with the first RO is 1.
As an embodiment, the SSB index associated with the first RO is the SSB index corresponding to (or mapped to) the first RO.
As one embodiment, the SSB index associated with the first RO is the SSB index associated to the first RO in an SSB-RO mapping cycle.
As one embodiment, the SSB index associated with the first RO is an SSB index associated with the first RO in an SSB-RO mapping cycle between a synchronization broadcast signal and the first RO set.
As an embodiment, the SSB index associated with the first RO indicates one SSB, a receive beam of which corresponds to a transmit beam of the first RO.
As an embodiment, the SSB index associated with the first RO indicates one SSB, and the receive spatial filter of the one SSB and the transmit spatial filter of the first RO have dissimilarity or correspondence.
As one embodiment, the target SSB index set includes only one SSB index.
As one embodiment, the target SSB index set includes a plurality of SSB indices.
As an embodiment, the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping the first RO in a time domain.
As one embodiment, the number of SSB indexes included in the target SSB index set is 1.
As one embodiment, the number of SSB indexes included in the target SSB index set is a positive integer greater than 1.
As an embodiment, the number of SSB indexes included in the target SSB index set is smaller than or equal to the value determined by the field "SSB-PositionsInBurst", or the number of SSB indexes included in the target SSB index set is smaller than or equal to the number of bits corresponding to the field "SSB-PositionsInBurst" and the value of the bits is 1.
As one embodiment, the third information block indicates a plurality of SSB indexes included in the target SSB index set.
As one embodiment, the plurality of fields included in the third information block are used to jointly determine (or are used to jointly calculate) the plurality of SSB indices included in the target SSB index set.
As an embodiment, the field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" and the field "msg1-FDM" included in the third information block are used to determine the SSB indices included in the target SSB index set together, where the field "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" indicates the number of SSBs corresponding to each RO, and the field "msg1-FDM" indicates the number of ROs that are frequency-division multiplexed.
As an embodiment, SSB indexes associated with at least one RO of the second RO set included in the target SSB index set and overlapping the first RO in the time domain depend on a domain "SSB-perRACH-OccasionAndCB-PreamblesPerSSB" and a domain "msg1-FDM" included in the third information block.
As an embodiment, the target SSB index set is a set of SSB indexes corresponding to (or mapped to) at least one RO overlapping the first RO in a time domain in the second RO set.
As one embodiment, the target SSB index set is a set of SSB indices associated in an SSB-RO mapping cycle to at least one of the second RO set and the first RO overlapping in the time domain.
As one embodiment, the target SSB index set is a set of SSB indexes associated to at least one RO overlapping the first RO in a time domain among the second RO set in an SSB-RO mapping cycle between a synchronization broadcast signal and the second RO set.
As an embodiment, each SSB index included in the target SSB index set is associated with at least one RO of the second RO set overlapping the first RO in the time domain.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO belongs to the target SSB index set.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO does not belong to the target SSB index set.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the target SSB index set completely includes the SSB index associated with the first RO.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the target SSB index set does not completely include the SSB index associated with the first RO.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO and the SSB index included in the target SSB index set are the same.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the SSB index associated with the first RO and the SSB index included in the target SSB index set are different.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the value of the remainder of the SSB index associated with the first RO for an integer greater than 1 is equal to one SSB index value included in the target SSB index set.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes that the value of the remainder of the SSB index associated with the first RO for an integer greater than 1 is not equal to any SSB index value included in the target SSB index set.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes a difference between the SSB index value associated with the first RO and a maximum SSB index value included in the target SSB index set.
As one embodiment, the relationship between the SSB index associated with the first RO and the target SSB index set includes a difference between the SSB index value associated with the first RO and a minimum SSB index value included in the target SSB index set.
As an embodiment, the technical characteristic that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the target SSB index set comprises that the relation between the SSB index associated with the first RO and the target SSB index set is used to determine (or judge) the validity of the first RO.
As an embodiment, the technical characteristic that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the set of target SSB indices comprises that the validity of the first RO relates to the relation between the SSB index associated with the first RO and the set of SSB indices.
As an embodiment, the technical characteristic that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the target SSB index set comprises whether the first RO depends effectively on the relation between the SSB index associated with the first RO and the target SSB index set.
As an embodiment, the technical feature that the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set comprises that the SSB index associated with the first RO belongs to one of a plurality of conditions under which the target SSB index set is valid for the first RO.
As an embodiment, the technical feature that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the target SSB index set comprises that the validity of the first RO depends on the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical characteristic that the validity of the first RO depends on the relation between the SSB index associated with the first RO and a target SSB index set comprises that it is a necessary condition that the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical feature that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the target SSB index set comprises that the condition that the first RO is valid comprises that the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical feature that the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set comprises that the SSB index associated with the first RO belongs to one of a plurality of conditions under which the target SSB index set is valid for the first RO.
As an embodiment, the technical characteristic that the validity of the first RO depends on the relation between the SSB index associated with the first RO and the target SSB index set comprises that the first RO is valid when the SSB index associated with the first RO belongs to the target SSB index set and that the first RO is invalid when the SSB index associated with the first RO does not belong to the target SSB index set.
As one embodiment, the technical characteristic that the validity of the first RO depends on the relationship between the SSB index associated with the first RO and a target SSB index set includes that the first RO is valid when the target SSB index set completely includes the SSB index associated with the first RO and that the first RO is invalid when the target SSB index set does not completely include the SSB index associated with the first RO.
As one embodiment, the technical characteristic that the validity of the first RO depends on the relationship between the SSB index associated with the first RO and the target SSB index set includes that the first RO is valid when the SSB index associated with the first RO and the SSB index included in the target SSB index set are the same, and that the first RO is invalid when the SSB index associated with the first RO and the SSB index included in the target SSB index set are different.
As an embodiment the technical feature "at least one RO of said second set of ROs overlapping said first RO in the time domain" comprises one RO of said second set of ROs overlapping said first RO in the time domain.
As an embodiment, the technical feature "at least one RO of the second RO set overlapping with the first RO in the time domain" includes a plurality of ROs of the second RO set overlapping with the first RO in the time domain.
As an embodiment, the technical feature "at least one RO of the second RO set overlapping the first RO in the time domain" comprises at least one RO of the second RO set located in the time domain on a time domain resource to which the first RO is mapped.
As an embodiment the technical feature "at least one RO of said second set of ROs that overlaps said first RO in the time domain" comprises at least one RO of said second set of ROs that overlaps said first RO in the time domain in whole or in part.
As an embodiment, the technical feature "at least one RO of the second RO set overlapping with the first RO in the time domain" includes at least one RO of the second RO set overlapping with the full duplex symbol indicated by TDD uplink and downlink configuration occupied by the first RO in the time domain.
As an embodiment, the technical feature "at least one RO of the second RO set overlapping with the first RO in the time domain" includes at least one RO of the second RO set overlapping with the first RO in the time domain in full or in part with at least one RO occupied by the first RO in the time domain indicated as flexible full duplex symbols by TDD uplink and downlink configuration.
As an embodiment, the technical feature "at least one RO of the second RO set overlapping with the first RO in the time domain" includes at least one RO of the second RO set overlapping with a PRACH slot (slot) to which the first RO belongs in the time domain.
As an embodiment the technical feature "at least one RO of said second set of ROs that overlaps said first RO in the time domain" comprises at least one RO of said second set of ROs that overlaps said first RO in the time domain and that overlaps said first RO frequency-division.
As an embodiment, the technical feature that the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain includes that the target SSB index set depends on SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain.
As an embodiment, the technical feature that the target SSB index set includes SSB indexes associated with at least one RO overlapping the first RO in the time domain in the second RO set includes that the target SSB index set is related to SSB indexes associated with at least one RO overlapping the first RO in the time domain in the second RO set.
As an embodiment, the technical feature that the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain includes that the target SSB index set is linearly related to SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain.
As an embodiment, the technical feature "the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain" includes that SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain are used to determine the target SSB index set.
As an embodiment, the technical feature "the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain" includes the target SSB index set including SSB indexes associated with each RO of the at least one RO of the second RO set overlapping with the first RO in the time domain.
As an embodiment, the technical feature that the target SSB index set includes SSB indexes associated with at least one RO of the second RO set overlapping with the first RO in the time domain includes that the target SSB index set is a set (or union) of SSB indexes associated with each RO of the at least one RO of the second RO set overlapping with the first RO in the time domain.
Example 2
Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the application, as shown in fig. 2.
Fig. 2 illustrates the network architecture of LTE (Long-Term Evolution), LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) and future 5G systems. The network architecture of LTE, LTE-a and future 5G systems is called EPS (Evolved PACKET SYSTEM ). The 5G NR or LTE network architecture may be referred to as 5GS (5G System)/EPS 200 or some other suitable terminology. The 5GS/EPS200 may include one or more UEs 201, one UE 241 in sidelink (Sidelink) communication with the UEs 201, ng-RAN (Next Generation Radio Access Network ) 202,5G-CN (5G Core Network,5G core network)/EPC (Evolved Packet Core ) 210, hss (Home Subscriber Server, home subscriber server)/UDM (Unified DATA MANAGEMENT) 220, and internet service 230. The 5GS/EPS200 may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown in fig. 2, the 5GS/EPS200 provides packet switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this disclosure may 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 termination towards the UE 201. The gNB 203 may 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 (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), TRP (TRANSMITTER RECEIVER Point), or some other suitable terminology. The gNB 203 provides the UE 201 with an access point to the 5G-CN/EPC 210. Examples of UEs 201 include a cellular telephone, a smart phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a laptop, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband physical network device, a machine-type communication device, a land vehicle, an automobile, a wearable device, or any other similar functional device. those of skill in the art may also refer to the 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 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 is connected to the 5G-CN/EPC 210 through an S1/NG interface. The 5G-CN/EPC 210 includes MME (Mobility MANAGEMENT ENTITY )/AMF (Authentication MANAGEMENT FIELD, authentication management domain)/SMF (Session Management Function ) 211, other MME/AMF/SMF 214, S-GW (SERVICE GATEWAY, serving Gateway)/UPF (User Plane Function ) 212, and P-GW (PACKET DATE 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. The MME/AMF/SMF 211 generally provides bearer and connection management. All user IP (Internet Protocol ) packets are transported through the S-GW/UPF 212, which S-GW/UPF 212 itself is connected to the P-GW/UPF 213. The P-GW provides UE IP address assignment as well as other functions. The P-GW/UPF 213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, internet, intranet, IMS (IP Multimedia Subsystem ) and packet-switched (PACKET SWITCHING) services.
As an embodiment, the UE201 corresponds to the terminal in the present application.
As an embodiment, the UE201 supports flexible duplex mode transmissions.
As an embodiment, the gNB (eNB) 201 corresponds to the base station in the present application.
As an embodiment, the gNB (eNB) 201 supports flexible duplex mode transmissions.
Example 3
Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to one embodiment of the present application, as shown in fig. 3.
Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300, and fig. 3 shows, in three layers, a radio protocol architecture for the control plane 300 for a terminal (RSU (Road Side Unit) and a base station (gNB, RSU in UE or V2X), or between two UEs, layer 1 (Layer 1, l 1), layer 2 (Layer 2, l 2) and Layer 3 (Layer 3, l 3) in the UE or V2X (Vehicle to Everything, car networking). L1 is the lowest layer and implements various PHY (PHYSICAL LAYER ) signal processing functions. L1 will be referred to herein as PHY 301. L2305 is above PHY 301, and is responsible for the link between a terminal and a base station, or between two UEs, through PHY 301. L2305 includes a MAC (Medium Access Control ) sublayer 302, an RLC (Radio Link Control, radio link layer control protocol) sublayer 303, and a PDCP (PACKET DATA Convergence Protocol ) sublayer 304, which terminate at the base station. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support for terminals between base stations. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat reQuest process number, hybrid automatic repeat request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the terminals. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control ) sublayer 306 in L3 in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the base station and the terminal. The radio protocol architecture of the user plane 350 includes layer 1 (L1) and layer 2 (L2), and the radio protocol architecture for the terminal and the base station in the user plane 350 is substantially the same for the PDCP sublayer 354 in the physical layer 351, L2355, the RLC sublayer 353 in the L2355 and the MAC sublayer 352 in the L2355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in L2355 in user plane 350 is an SDAP (SERVICE DATA Adaptation Protocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS (Quality of Service ) flows and data radio bearers (Data Radio Bearer, DRBs) to support diversity of traffic. Although not shown, the terminal may have several upper layers above L2355, including a network layer (e.g., IP (Internet Protocol, internet protocol) layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., remote UE, server, etc.).
As an embodiment, the radio protocol architecture in fig. 3 is applicable to the terminal in the present application.
As an embodiment, the radio protocol architecture in fig. 3 is applicable to the base station in the present application.
As an embodiment, the first information block in the present application is generated in the RRC306, the MAC302, the MAC352, the PHY301, or the PHY351.
As an embodiment, the second information block in the present application is generated in the RRC306, the MAC302, the MAC352, the PHY301, or the PHY351.
As an embodiment, the third information block in the present application is generated in the RRC306, the MAC302, the MAC352, the PHY301, or the PHY351.
As an embodiment, the first capability information block in the present application is generated in the RRC306, the MAC302, the MAC352, the PHY301, or the PHY351.
Example 4
Embodiment 4 shows a schematic diagram of a terminal and a base station according to an embodiment of the application, as shown in fig. 4.
A controller/processor 490, a data source/buffer 480, a receive processor 452, a transmitter/receiver 456 and a transmit processor 455 may be included in the terminal (450), the transmitter/receiver 456 including an antenna 460.
A controller/processor 440, a data source/buffer 430, a receive processor 412, a transmitter/receiver 416, and a transmit processor 415 may be included in the base station (410), with the transmitter/receiver 416 including an antenna 420.
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 the DL, the controller/processor 440 provides packet header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the terminal 450 based on various priority metrics. The controller/processor 440 is also responsible for HARQ operations, retransmission of lost packets, and higher layer signaling to the terminal 450. The high-level information carried by the first, second and third information blocks in the present application is generated at the controller/processor 440. The transmit processor 415 implements various signal processing functions for the L1 layer (i.e., physical layer), including encoding, interleaving, scrambling, modulation, power control/allocation, precoding, physical layer control signaling generation, etc., such as physical layer signals carrying a first information block, physical layer signals carrying a second information block, and physical layer signals carrying a third information block, are performed at the transmit processor 415. The generated modulation symbols are divided into parallel streams and each stream is mapped to a respective multicarrier subcarrier and/or multicarrier symbol and then transmitted as a radio frequency signal by transmit processor 415 via transmitter 416 to antenna 420. At the receiving end, each receiver 456 receives a radio frequency signal through its respective antenna 460, each receiver 456 recovers baseband information modulated onto a radio frequency carrier, and provides the baseband information to the receive processor 452. The reception processor 452 implements various signal reception processing functions of the L1 layer. The signal reception processing function includes demodulating, then descrambling, decoding and de-interleaving a physical layer signal carrying a first information block in the present application, a physical layer signal carrying a second information block in the present application, and a physical layer signal carrying a third information block based on various modulation schemes (e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK)) through multicarrier symbols in a multicarrier symbol stream to restore data or control transmitted by the base station 410 on a physical channel, and then providing the data and control signals to the controller/processor 490. The controller/processor 490 is responsible for L2 and above layers, and the controller/processor 490 interprets higher layer information. The method comprises the step of reading high-level information carried by the first information block, the second information block and the third information block. The controller/processor can be associated with a memory 480 that stores program codes and data. Memory 480 may be referred to as a computer-readable medium.
In Uplink (UL) transmission, similar to downlink transmission, the higher layer information carried by the higher layer information including the first capability information block of the present application is subjected to various signal transmission processing functions for the L1 layer (i.e., physical layer) by the transmission processor 455 after being generated by the controller/processor 490, and the physical layer signal carrying the first capability information block of the present application is mapped to the antenna 460 by the transmission processor 455 via the transmitter 456 to be transmitted in the form of a radio frequency signal. The receivers 416 receive the radio frequency signals through their respective antennas 420, each receiver 416 recovers baseband information modulated onto a 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 physical layer signals carrying the first capability information blocks of the present application, and then providing data and/or control signals to the controller/processor 440. Implementing the functions of the L2 layer at the controller/processor 440 includes interpreting high-level information, such as that carried by the first capability information block in the present application. The controller/processor can be associated with a buffer 430 that stores program code and data. The buffer 430 may be a computer readable medium.
As an embodiment, the terminal 450 apparatus comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the terminal 450 apparatus to at least receive a first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, receive a second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein a first RO is one RO included in the first set of ROs, the first RO occupying at least one full symbol indicated as flexible by an upstream-downstream configuration, the validity of the first RO is dependent on an overlapping relationship between an SSB index associated with the first RO and a target SSB index, the target set of ROs comprising at least one overlapping relationship between the SSB index and the first set of SSBs in the time domain.
As an embodiment, the terminal 450 apparatus comprises a memory storing a program of computer readable instructions which, when executed by at least one processor, generates an action comprising receiving a first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, receiving a second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein the first RO is one RO comprised by the first set of ROs, the first RO occupying at least one full duplex symbol indicated as flexible by a TDD uplink-downlink configuration, the validity of the first RO being dependent on a relationship between an SSB index associated with the first RO and a target SSB index set, the target SSB index set comprising at least one SSB index in the second set of ROs overlapping with the first RO.
The base station 410 apparatus, as one embodiment, includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the base station to perform a method of operating the base station. The base station 410 apparatus at least transmits a first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, transmits a second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein the first RO is one RO included in the first set of ROs occupying at least one full duplex symbol indicated as flexible by a TDD uplink-downlink configuration, and the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set including SSB indices associated with at least one RO overlapping the first RO in the time domain in the second set of ROs.
As an embodiment, the base station 410 comprises a memory storing a program of computer readable instructions that, when executed by at least one processor, generates actions comprising transmitting a first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, transmitting a second information block indicating a first set of ROs that occupy at least one full duplex symbol in the time domain, and a third information block indicating a second set of ROs that occupy at least one full duplex symbol in the time domain, wherein a first RO is one RO comprised by the first set of ROs that occupies at least one full duplex symbol indicated as flexible by a TDD uplink-downlink configuration, the validity of the first RO being dependent on a relationship between SSB indices associated with the first RO and a target SSB index set comprising at least one SSB index in the second set of ROs that overlap with the first RO.
As an embodiment, the terminal 450 is a User Equipment (UE).
As an embodiment, the terminal 450 is a user equipment supporting a flexible duplex mode transmission.
As an embodiment, the base station 410 is a base station device (gNB/eNB).
As an embodiment, the base station 410 is a base station device supporting a flexible duplex mode transmission.
As an example, a receiver 456 (comprising an antenna 460), a receive processor 452 and a controller/processor 490 are used for receiving said first information block in the present application.
As an example, a receiver 456 (comprising an antenna 460), a receiving processor 452 and a controller/processor 490 are used for receiving said second information block in the present application.
As an example, a receiver 456 (comprising an antenna 460), a receiving processor 452 and a controller/processor 490 are used for receiving said third information block in the present application.
As an example, a transmitter 456 (comprising an antenna 460), a transmit processor 455 and a controller/processor 490 are used to transmit said first capability information block in the present application.
As an example, a transmitter 416 (comprising an antenna 420), a transmit processor 415 and a controller/processor 440 are used for transmitting said first information block in the present application.
As an example, a transmitter 416 (comprising an antenna 420), a transmit processor 415 and a controller/processor 440 are used for transmitting said second information block in the present application.
As an example, a transmitter 416 (comprising an antenna 420), a transmit processor 415 and a controller/processor 440 are used for transmitting said third information block in the present application.
As an example, receiver 416 (including antenna 420), receive processor 412 and controller/processor 440 are used to receive the first capability information block in the present application.
Example 5
Embodiment 5 illustrates a flow chart of terminal and base station transmissions according to one embodiment of the application, as shown in fig. 5. In fig. 5, a base station N500 is a maintenance base station of a serving cell of a terminal U550. It is specifically explained that the order in this example does not limit the order of signal transmission and the order of implementation in the present application.
For the base station N500, a first information block is transmitted in step S501, a second information block is transmitted in step S502, a third information block is transmitted in step S503, and a first capability information block is received in step S504.
For terminal U550, a first information block is received in step S551, a second information block is received in step S552, a third information block is received in step S553, and a first capability information block is transmitted in step S554.
In embodiment 5, the first information block indicates a symbol type of at least one symbol, the first information block indicates a target sub-band, the second information block indicates a first RO set, the third information block indicates a second RO set, ROs in the first RO set occupy at least one full duplex symbol in a time domain, wherein the first RO is one RO included in the first RO set, the first RO occupies at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration, validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set, the target SSB index set includes an SSB index associated with at least one RO overlapping the first RO in the time domain in the second RO set, and the first capability information block indicates that a sender of the first capability information block supports a random access procedure in the full duplex symbol.
As an embodiment, the first information block is earlier than the second information block.
As an embodiment, the first information block is later than the second information block.
As an embodiment, the first information block is earlier than the third information block.
As an embodiment, the first information block is later than the third information block.
As an embodiment, the first information block is earlier than the first capability information block.
As an embodiment, the first information block is later than the first capability information block.
As an embodiment, the second information block is earlier than the third information block.
As an embodiment, the second information block is later than the third information block.
As an embodiment, the second block of information is earlier than the first block of capability information.
As an embodiment, the second information block is later than the first capability information block.
As an embodiment, the third information block is earlier than the first capability information block.
As an embodiment, the third information block is later than the first capability information block.
As an embodiment, the first information block and the second information block are transmitted over the same physical channel.
As an embodiment, the first information block and the second information block respectively include different IEs or fields included in the same IE.
As an embodiment, the first information block and the third information block are transmitted over the same physical channel.
As an embodiment, the first information block and the third information block respectively include different IEs or fields included in the same IE.
As an embodiment, the second information block and the third information block are transmitted over the same physical channel.
As an embodiment, the second information block and the third information block respectively include different IEs or fields included in the same IE.
As an embodiment, the first information block, the second information block and the third information block are transmitted over the same physical channel.
As an embodiment, the first information block, the second information block and the third information block respectively include different IEs or fields included in the same IE.
As an embodiment, the first capability information block is transmitted over an air interface or a wireless interface.
As an embodiment, the first capability information block includes all or part of higher layer signaling or physical layer signaling.
As an embodiment, the first capability information block includes all or part of RRC signaling, or the first capability information block includes all or part of MAC layer signaling.
As an embodiment, the first capability information block is transmitted through PUSCH or PUCCH (Physical Uplink Control Channel ).
As an embodiment, the first capability information block is used to indicate the capability of the terminal in the present application.
As an embodiment, the sender of the first capability information block is the terminal in the present application.
As an embodiment, the first Capability information block includes an IE "UE-NR-Capability".
As an embodiment, the first capability information block includes an IE "RF-Parameters", or the first capability information block includes an IE "BandNR".
As an embodiment, the first capability information block includes IE "BandCombinationList", or the first capability information block includes IE "BandCombination".
As an embodiment, the first capability information block includes an IE "Phy-Parameters".
As an embodiment, the first capability information block includes IE "FeatureSetUplink", or the first capability information block includes IE "FeatureSetUplinkPerCC".
As an embodiment, the first capability information block is applied only to TDD.
As an embodiment, the first capability information block is for SBFD devices.
As an embodiment, the first capability information block is per user equipment (per UE). As an additional embodiment of the above embodiment, the delivering (signal) the first capability information block per user equipment may reduce standard complexity.
As an embodiment, the first capability information block is band or band combination specific.
As an embodiment, the first capability information block is per band (perband). As an auxiliary embodiment of the above embodiment, the delivering of the first capability information block per frequency band may be optimized for different frequency bands, simplifying the product implementation.
As an embodiment, the first capability information block is combined per frequency band (per band combination). As an subsidiary embodiment of the above embodiment, delivering said first capability information block per band combination may be optimized for the band combination, balancing between standard complexity and product implementation complexity.
As an embodiment, the first capability information block has different parameter values between different Frequency Ranges (FR). As an auxiliary embodiment of the above embodiment, having different parameter values for different frequency ranges may optimize product implementation for the frequency ranges, improving flexibility.
As an embodiment, the first capability information block has the same parameter value between different frequency ranges. As an auxiliary embodiment of the above embodiment, having the same parameter value in different frequency ranges can support a uniform design, reducing standard complexity.
Example 6
Example 6 illustrates a schematic diagram of conditions under which the first RO is valid according to one embodiment of the present application, as shown in fig. 6. In fig. 6, each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources, respectively, and SSB indexes associated with the first RO belong to a target SSB index set, which is a condition that the first RO is valid.
In embodiment 6, mapping between the first RO and each RO included in the second RO set in the present application to non-overlapping time-frequency resources respectively and the SSB index associated with the first RO belongs to a target SSB index set is a condition that the first RO is valid.
As an embodiment, according to the fact that each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources respectively and the SSB index associated with the first RO belongs to the target SSB index set, the validity of the first RO is judged, the number of ROs on SBFD symbols is designed to the greatest extent while considering the limit of implementation, and the probability of successful PRACH transmission is improved.
As an embodiment, the technical feature that each RO included in the first RO and the second RO set is mapped to a non-overlapping time-frequency resource respectively includes that each RO included in the first RO and the second RO set occupies a non-overlapping time-frequency resource respectively.
As an embodiment, the technical feature that each RO included in the first RO and the second RO set is mapped to a non-overlapping time-frequency resource respectively includes that each RO included in the first RO and the second RO set is located on a non-overlapping time-frequency resource respectively.
As an embodiment, the technical feature that each RO comprised by the first RO and the second RO set is mapped to a non-overlapping time-frequency resource respectively comprises that each RO comprised by the first RO and the second RO set and the first RO overlap in the time domain is mapped to a non-overlapping frequency-domain resource respectively, or that each RO comprised by the first RO and the second RO set and the first RO overlap in the time domain is frequency-divided.
As an embodiment, the technical feature that "the time-frequency resources mapped to non-overlapping between the first RO and each RO included in the second RO set respectively" includes that the time-domain resources and the frequency-domain resources mapped by the first RO are not identical (or overlap) with at least one of the time-domain resources and the frequency-domain resources mapped by each RO included in the second RO set.
As an embodiment, the technical feature "the mapping between the first RO and each RO included in the second RO set to non-overlapping time-frequency resources respectively" includes that the time domain resources and the frequency domain resources mapped by the first RO are different (or overlap) from the time domain resources and the frequency domain resources mapped by each RO included in the second RO set, or that the time domain resources mapped by the first RO are the same (or overlap) from the time domain resources mapped by each RO included in the second RO set, but the frequency domain resources mapped by the first RO are different (or overlap) from the frequency domain resources mapped by each RO included in the second RO set, or that the frequency domain resources mapped by the first RO are the same (or overlap) from the frequency domain resources mapped by each RO included in the second RO set, but the time domain resources mapped by the first RO are different (or overlap) from the time domain resources mapped by each RO included in the second RO set.
As an embodiment, the technical feature that each RO comprised by the first RO and the second RO set is mapped to a non-overlapping time-frequency resource respectively comprises that each RO comprised by the first RO and the second RO set is orthogonal.
As an embodiment, the technical feature that each RO comprised by the first RO and the second RO set is mapped to a non-overlapping time-frequency resource respectively comprises that the first RO set and the second RO set are orthogonal.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set comprises that the target SSB index set comprises the SSB index associated with the first RO.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set comprises that the target SSB index set only comprises SSB indexes associated with the first RO.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set comprises that the SSB index associated with the first RO is a subset of the SSB indices comprised by the target SSB index set.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set includes that the value of the index included in the target SSB index set is the same as the value of the SSB index associated with the first RO.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set includes that the SSB index value associated with the first RO is the same as one SSB index in the target SSB index set.
As an embodiment, the technical feature that the SSB index associated with the first RO belongs to a target SSB index set includes that the SSB index values associated with the first RO are identical (or one-to-one) to the SSB index values in the target SSB index set.
As an embodiment, the technical feature that "the first RO and each RO comprised by the second RO set are mapped to non-overlapping time-frequency resources, respectively, and the SSB index associated with the first RO belongs to the target SSB index set is a condition that the first RO is valid" comprises that the first RO is valid depending on the non-overlapping time-frequency resources, respectively, and the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical feature that "the condition that each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources and that the SSB index associated with the first RO belongs to the target SSB index set is valid for the first RO" comprises that each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources and that the SSB index associated with the first RO belongs to the target SSB index set is used to determine (or judge) that the first RO is valid.
As an embodiment, the technical feature that "the first RO and each RO comprised by the second RO set are mapped to non-overlapping time-frequency resources respectively and that the SSB index associated with the first RO belongs to the target SSB index set is a condition that the first RO is valid" comprises that the first RO and each RO comprised by the second RO set are mapped to non-overlapping time-frequency resources respectively and that the SSB index associated with the first RO belongs to the target SSB index set is a necessary condition that the first RO is valid.
As an embodiment, the technical feature that "the SSB index associated with the first RO is mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set and the condition that the first RO is valid" comprises that the condition that the first RO is valid comprises that the first RO is mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical feature that "the SSB index associated with the first RO is mapped to non-overlapping time-frequency resources between each RO included in the first RO and the second RO set, respectively, and the SSB index associated with the first RO belongs to a target SSB index set is a condition that the first RO is valid" comprises that the SSB index associated with the first RO is mapped to non-overlapping time-frequency resources between each RO included in the first RO and the second RO set, respectively, and the SSB index associated with the first RO belongs to a target SSB index set, is one of a plurality of conditions that the first RO is valid.
As an embodiment, the technical feature that "the condition that each RO comprised by the first RO and the second RO set is mapped to non-overlapping time-frequency resources and that the SSB index associated with the first RO belongs to the target SSB index set is valid for the first RO" comprises that the first RO is valid depending on the mapping between each RO comprised by the first RO and the second RO set to non-overlapping time-frequency resources, the first RO is valid depending on the SSB index associated with the first RO belongs to the target SSB index set.
As an embodiment, the technical feature that "the condition that each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set is valid for the first RO" comprises that the first RO is valid when each RO included in the first RO and the second RO set is mapped to non-overlapping time-frequency resources and the SSB index associated with the first RO belongs to the target SSB index set.
Example 7
Embodiment 7 illustrates a schematic diagram of a second set of ROs according to an embodiment of the application, as shown in fig. 7. In fig. 7, the vertical axis represents the frequency domain, the horizontal axis represents the time domain, the bold-lined rectangle represents the target subband, the area between the two dotted lines represents the full duplex symbol indicated as flexible by the TDD uplink and downlink configuration, and the rectangular area filled with diagonal lines represents all ROs included in the second RO set that overlap with at least one full duplex symbol indicated as flexible by the TDD uplink and downlink configuration.
In embodiment 7, all ROs included in the second RO set in the present application and at least one RO indicated by TDD uplink and downlink configuration as overlapping full duplex symbols belong to the target subband in the frequency domain.
As an embodiment, all ROs, which are included in the second RO set and have overlapping, in the frequency domain, between the time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration are set to belong to the target sub-band, so that the influence of self-interference on the adjacent frequency band is considered, and the performance of random access and backward compatibility are ensured.
As an embodiment, the technical feature that all ROs in the time domain and at least one of the ROs indicated as being overlapped by the TDD uplink and downlink configuration by the second RO set include a plurality of ROs in the time domain and at least one of the ROs indicated as being overlapped by the TDD uplink and downlink configuration by the second RO set.
As an embodiment, the technical feature that all ROs that are included in the second RO set and at least one RO that are indicated as being overlapped by the TDD uplink and downlink configuration as a flexible full duplex symbol include each RO of a plurality of ROs that are included in the second RO set and at least one RO that are indicated as being overlapped by the TDD uplink and downlink configuration as a flexible full duplex symbol.
As an embodiment, the technical feature that "all ROs included in the second RO set that overlap in time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration" includes all ROs included in the second RO set that are located in time domain on at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration.
As an embodiment, the technical feature that "all of the time domains included in the second RO set and at least one RO indicated as being overlapped by the TDD uplink and downlink configuration as a flexible full duplex symbol" includes that all of the time domains included in the second RO set occupy (or are mapped to) at least one RO indicated as being overlapped by the TDD uplink and downlink configuration as a flexible full duplex symbol.
As an embodiment, the technical feature that "all ROs in the time domain and at least one of the ROs indicated as being overlapped by the TDD uplink and downlink configuration by the flexible full duplex symbol" included in the second RO set includes all ROs in the time domain and at least one of the ROs indicated as being overlapped by the TDD uplink and downlink configuration by the flexible full duplex symbol.
As an embodiment, the technical feature that all ROs included in the second RO set that overlap between the time domain and the time slot including at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration are included in the second RO set.
As an embodiment, the technical feature that all ROs in the time domain and at least one RO in the frequency domain indicated as overlapping by TDD uplink and downlink configuration for flexible full duplex symbols included in the second RO set belong to the target subband includes that all ROs in the time domain and at least one RO in the frequency domain indicated as overlapping by TDD uplink and downlink configuration for flexible full duplex symbols included in the second RO set are located in the target subband.
As an embodiment, the technical feature that all ROs in the time domain and at least one RO indicated as overlapping by TDD uplink and downlink configuration for the flexible full duplex symbol included in the second RO set in the frequency domain belong to the target subband includes that the target subband includes all frequency domain resources occupied by ROs in the time domain and at least one RO indicated as overlapping by TDD uplink and downlink configuration for the flexible full duplex symbol included in the second RO set.
Example 8
Embodiment 8 illustrates a schematic diagram of a first threshold according to one embodiment of the application, as shown in fig. 8. In fig. 8, the unfilled rectangle in each case represents one slot, "DL" represents a downlink symbol in which no full duplex symbol is configured, "UL" represents an uplink symbol in which the symbol in the slot is a full duplex symbol, "FD" represents a first RO, the gray filled small rectangle represents a first threshold value in case a represents a threshold value of a gap length from the downlink symbol to the full duplex symbol, the first threshold value in case B represents a threshold value of a gap length from the uplink symbol to the full duplex symbol, the first threshold value in case C represents a threshold value of a gap length from the full duplex symbol to the uplink symbol, and the first threshold value in case D represents a threshold value of a gap length from the full duplex symbol to the downlink symbol.
In embodiment 8, the validity of said first RO in the present application depends on the length of the interval between the time domain and adjacent non-full duplex symbols of said first RO being larger than a first threshold, said first threshold in the present application being configured or predefined and/or related to user equipment capabilities.
As an embodiment, when judging the validity of one RO, the conversion delay between the full duplex symbol and the non-full duplex symbol is considered, the successful transmission probability of the PRACH is improved, and meanwhile, the implementation limitation is considered, so that the implementation complexity of transmitting the PRACH on the full duplex symbol is reduced.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the start of the time domain and the start of the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the start of the time domain and the end of the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the end of the time domain and the start of the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the end of the time domain and the end of the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the time domain and the adjacent one of the non-full duplex symbols.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the time domain and any one of the adjacent non-full duplex symbols.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the PRACH slot to which the time domain belongs and the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length of the first RO between the time domain overlapping time slot and the adjacent non-full duplex symbol.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length between the last (last) non-full duplex symbol of the first RO in the starting sum of the time domain. As an subsidiary embodiment of the above embodiment, consider that the length of the interval between non-full duplex symbols and the preceding one satisfies the requirements of different coverage for transmission delay while guaranteeing the transition time between non-full duplex symbols to full duplex symbols.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is the interval length between the end of the time domain and the next (next) non-full duplex symbol. As an subsidiary embodiment of the above embodiment, the length of the interval between the considered and following non-full duplex symbols ensures the transition time between full duplex symbols to non-full duplex symbols, reducing implementation complexity.
As an embodiment, the length of the interval between the time domain and the adjacent non-full duplex symbol of the first RO is expressed in terms of absolute time length.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is expressed in terms of the number of symbols.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbols is expressed in terms of the number of symbols corresponding to the subcarrier interval of the preamble.
As an embodiment, the interval length of the first RO between the time domain and the adjacent non-full duplex symbol is expressed in terms of the number of symbols corresponding to the subcarrier interval of the active uplink BWP.
As an embodiment, the non-full duplex symbol is a non-SBFD symbol.
As an example, the "non-full duplex symbol" and the "non-SBFD symbol" are equivalent or alternative.
As an embodiment, the non-full duplex symbol is an OFDM (Orthogonal Frequency Division Multiplexing ) symbol.
As an embodiment, the non-full duplex symbol is a time domain symbol that is not configured SBFD.
As an embodiment, the non-full duplex symbol is a symbol that does not overlap with SBFD slots in the time domain.
As an embodiment, the non-full duplex symbol is a symbol that does not overlap with a full duplex symbol.
As one embodiment, the non-full duplex symbol is a time domain symbol that does not support full duplex.
As an embodiment, the non-full duplex symbol is a time domain symbol that can only be used for uplink or downlink transmission or guard interval.
As an embodiment, the non-full duplex symbol is a time domain symbol that is not indicated (or provided) by signaling of the configuration SBFD.
As an embodiment, the non-full duplex symbol is a time domain symbol not indicated (or provided) by the first information block.
As an embodiment, the non-full duplex symbol is a symbol that is indicated by the TDD uplink-downlink configuration as a downlink or flexible symbol and is not available for uplink transmission.
As an embodiment, the non-full duplex symbol is a symbol indicated as downlink by TDD uplink-downlink configuration and not available for uplink transmission.
As an embodiment, the non-full duplex symbol is a symbol indicated as uplink by TDD uplink-downlink configuration.
As an embodiment, the non-full duplex symbol is a symbol other than a full duplex symbol.
As one embodiment, the non-full duplex symbol is a time domain symbol that is not configured with the target subband.
As an embodiment, the adjacent non-full duplex symbol is the last non-full duplex symbol.
As an embodiment, the adjacent non-full duplex symbol is the next non-full duplex symbol.
As an embodiment, the adjacent non-full duplex symbol is the preceding non-full duplex symbol closest to the adjacent non-full duplex symbol.
As an embodiment, the adjacent non-full duplex symbol is the next nearest non-full duplex symbol.
As an embodiment, the adjacent non-full duplex symbol is a previous or next downlink symbol.
As an embodiment, the adjacent non-full duplex symbol is a symbol that is indicated as downlink by TDD uplink-downlink configuration, which is the last or next symbol.
As an embodiment, the adjacent non-full duplex symbol is the next or the last downstream symbol not indicated as a full duplex symbol.
As an embodiment, the adjacent non-full duplex symbol is a symbol that is not indicated as a full duplex symbol by the first information block and is indicated as downlink by TDD uplink-downlink configuration.
As an embodiment, the adjacent non-full duplex symbol is the last or next uplink symbol.
As an embodiment, the adjacent non-full duplex symbol is a symbol that is indicated as uplink by TDD uplink-downlink configuration, which is the last or next symbol.
As an embodiment, the first threshold is a non-negative integer.
As an embodiment, the first threshold may be a non-integer.
As an embodiment, the first threshold is in seconds or milliseconds.
As an embodiment, the first threshold represents the number of symbols.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval between the time domain and the adjacent non-full duplex symbols of the first RO being larger than a first threshold value comprises that the length of the interval between the time domain and the adjacent non-full duplex symbols of the first RO being larger than the first threshold value is used for determining or judging that the first RO is valid.
As an embodiment the technical feature that the validity of the first RO depends on the first RO being larger than a first threshold in length of the interval between time domain and adjacent non-full duplex symbols comprises that it is a requirement that the first RO is valid in length of the interval between time domain and adjacent non-full duplex symbols being larger than the first threshold.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval between the time domain and the adjacent non-full duplex symbols of the first RO being larger than a first threshold comprises that the condition that the first RO is valid comprises that the length of the interval between the time domain and the adjacent non-full duplex symbols of the first RO is not smaller than (or larger than) the first threshold.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full duplex symbols being larger than a first threshold value comprises that the validity of the first RO depends on the first RO starting at the time domain at least N1 symbols later than the adjacent non-full duplex symbols, N1 being the first threshold value.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full duplex symbols being larger than a first threshold value comprises that the validity of the first RO depends on the first RO being cut off in the time domain at least N2 symbols earlier than the adjacent non-full duplex symbols, N2 being the first threshold value.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval of the first RO between the time domain and adjacent non-full duplex symbols being larger than a first threshold value comprises that the first RO is valid when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval of the first RO between the frequency domain and at least one boundary of the uplink sub-band is not smaller than a configured or predefined threshold value and the first RO starts N1 symbols later in the time domain than adjacent non-full duplex symbols, N1 being the first threshold value.
As an embodiment, the technical feature that the validity of the first RO depends on the length of the interval of the first RO between the time domain and adjacent non-full duplex symbols being larger than a first threshold value comprises that the first RO is valid when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval of the first RO between the frequency domain and at least one boundary of the uplink sub-band is not smaller than a configured or predefined threshold value and the first PRACH opportunity is N2 symbols earlier at the end of the time domain than the adjacent non-full duplex symbols, N2 being the first threshold value.
As an embodiment the technical feature that the validity of the first RO depends on the length of the interval between the first RO in the time domain and the adjacent non-full duplex symbols being larger than a first threshold value comprises that the first RO is valid when the first RO belongs to an uplink sub-band in the frequency domain and the first RO starts N1 symbols later in the time domain than the adjacent non-full duplex symbols and the first RO ends N2 symbols earlier in the time domain than the adjacent non-full duplex symbols, N1 or N2 being the first threshold value, N1 being a non-negative integer, N2 being a non-negative integer.
As an embodiment, the technical feature that the validity of the first RO depends on the length of the interval of the first RO between the time domain and the adjacent non-full duplex symbols being larger than a first threshold value comprises that the first PRACH opportunity is valid when the first RO belongs to an uplink sub-band in the frequency domain and the frequency domain interval of the first RO between the frequency domain and at least one boundary of the uplink sub-band is not smaller than a configured or predefined threshold value and the first RO starts N1 symbols later in the time domain than the adjacent non-full duplex symbols and the first PRACH opportunity ends N2 symbols earlier in the time domain than the adjacent non-full duplex symbols, N1 or N2 being the first threshold value, N1 being a non-negative integer and N2 being a non-negative integer.
As an embodiment, the first threshold is configured or predefined.
As an embodiment, the first threshold is related to user equipment capability.
As an embodiment, the first threshold is configured and related to user equipment capabilities.
As an embodiment, the first threshold is configured to include higher layer signaling or higher layer parameters indicating the first threshold.
As an embodiment the first threshold is configured comprising that the first threshold depends on higher layer signaling or higher layer parameters.
As an embodiment the first threshold is configured to comprise that the first threshold depends on a subcarrier spacing, higher layer signaling or higher layer parameters indicate the subcarrier spacing on which the first threshold depends.
As an embodiment, the first threshold is configured to include higher layer signaling or higher layer parameters indicating whether the first threshold is equal to a value reported by user equipment capability.
As an embodiment, the first threshold is configured to include higher layer signaling or higher layer parameters indicating an offset value between the first threshold and a value reported by user equipment capability.
As an embodiment, the first threshold is configured to include calculating a parameter of the first threshold to include a first parameter value, the first parameter value being indicated by higher layer signaling or higher layer parameters.
As an embodiment the first threshold is configured to comprise that the first threshold is linearly related to a first parameter value, which is indicated by higher layer signaling or higher layer parameters.
As an embodiment the first threshold value is predefined comprising that the first threshold value is fixed.
As an embodiment the first threshold value is predefined comprising that the first threshold value is hard coded in a standard.
As an embodiment the first threshold value is predefined comprising that the relation between the first threshold value and the value of the further parameter is fixed.
As an embodiment the first threshold value is predefined comprising that the correspondence between the first threshold value and the subcarrier spacing is fixed.
As an embodiment the first threshold value is predefined comprising calculating a parameter of the first threshold value comprising a first parameter value, the first parameter value being a fixed value.
As an embodiment, the first threshold is related to user equipment capability and comprises the first threshold being equal to a value of a user equipment capability report.
As an embodiment, the first threshold is related to user equipment capability and comprises a value not smaller than a user equipment capability report.
As an embodiment, the first threshold is related to user equipment capability comprising calculating a parameter of the first threshold comprises a first parameter value, the first parameter value being equal to a value of a user equipment capability report.
As an embodiment, the first threshold value is related to the user equipment capability and comprises that the first threshold value is linearly related to a first parameter value, which is equal to a value of the user equipment capability report.
As an embodiment, the first threshold is related to the user equipment capability and also depends on whether the user equipment capability supports SBFD or whether the user equipment capability supports transmission of PRACH in a downlink full duplex symbol.
As an embodiment, the first threshold value of the network configuration may take into account the transition delay between different hardware or algorithm implementations of the network side when processing the full duplex symbol and the non-full duplex symbol, so as to ensure the effective operation of the self-interference cancellation of the network.
As an embodiment, the predefined first threshold may support setting a fixed, relatively large threshold, simplifying the design while ensuring that the network and user side switching and processing delays are met.
As an embodiment, the association of the first threshold and the capability of the user equipment can ensure that the conversion and processing delay of the user equipment are satisfied, and the implementation complexity of the user equipment is reduced.
As an embodiment, the first threshold is associated with the capability of the user equipment and is configured by the network at the same time, so that on the premise of ensuring that the conversion and processing delay of the user equipment are satisfied, different network sides are considered to realize at the same time, the setting of the first threshold is optimized, the effective PRACH opportunity of accidental injury is avoided, and the capacity of the PRACH is improved.
As an embodiment, the first threshold is equal to a large value compared between a first candidate interval and a second candidate interval, the first candidate interval being configured or related to a subcarrier spacing of a random access preamble, the second candidate interval being related to user equipment capability.
As an embodiment, the first threshold is equal to a large value compared between Ngap and a first capability value, ngap being related to the subcarrier spacing of the random access preamble, the first capability value being related to the user equipment capability.
Example 9
Embodiment 9 illustrates a schematic diagram of a second threshold according to one embodiment of the application, as shown in fig. 9. In fig. 9, the vertical axis represents the frequency domain, the bold line box rectangle represents the target subband, the diagonally filled rectangle represents the first RO, and the second threshold represents the threshold from the boundary of the target subband to the frequency interval within the target subband.
In embodiment 9, the validity of the first RO in the present application depends on the first RO belonging to the target subband in the frequency domain and the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target subband being not smaller than a second threshold, which in the present application is predefined or configured.
As an embodiment, the influence of self-interference on the adjacent frequency band is considered when judging the validity of one RO, so that the effective transmission of the PRACH is ensured, and the random access performance is improved.
As an embodiment, the technical feature that the first RO belongs to the target sub-band in the frequency domain includes that all frequency domain resources occupied by the first RO are located in the target sub-band.
As an embodiment, the technical feature that the first RO belongs to the target sub-band in the frequency domain includes that the target sub-band includes all frequency domain resources occupied by the first RO.
As an embodiment, the frequency domain interval of the first RO between the frequency domain and the at least one boundary of the target subband is the frequency domain interval between the lowest frequency (or lowest indexed subcarrier) of the first RO and the at least one boundary of the target subband.
As an embodiment, the frequency domain interval of the first RO between the frequency domain and the at least one boundary of the target subband is the frequency domain interval between the highest frequency (or highest indexed subcarrier) of the first RO and the at least one boundary of the target subband.
As an embodiment, the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is a frequency domain interval between the lowest frequency (or lowest indexed sub-carrier) of the first RO and the lowest frequency (or lowest indexed sub-carrier included) of the target sub-band.
As an embodiment, the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is a frequency domain interval between a highest frequency (or highest indexed sub-carrier) of the first RO and a highest frequency (or highest indexed sub-carrier included) of the target sub-band.
As an embodiment, the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band includes a frequency domain interval between the lowest frequency (or lowest indexed subcarrier) of the first RO and the lowest frequency (or lowest indexed subcarrier included) of the target sub-band and a frequency domain interval between the highest frequency (or highest indexed subcarrier) of the first RO and the highest frequency (or highest indexed subcarrier included) of the target sub-band.
As an embodiment the technical feature that the frequency domain spacing of the first RO between the frequency domain and the at least one boundary of the target sub-band is not smaller than a second threshold comprises that the frequency domain spacing of the first RO between the frequency domain and the at least one boundary of the target sub-band is larger than the second threshold.
As an embodiment, the technical feature that the frequency domain spacing of the first RO between the frequency domain and the at least one boundary of the target sub-band is not smaller than a second threshold value comprises that the frequency domain spacing of the first RO between the frequency domain and the at least one boundary of the target sub-band is larger than or equal to the second threshold value.
As an embodiment, the technical feature that the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is not smaller than a second threshold value comprises that the frequency domain interval of the first RO between all frequency resources (or all sub-carriers) included in the frequency domain and the lowest frequency (or the lowest indexed sub-carrier included) of the target sub-band is not smaller than the second threshold value.
As an embodiment, the technical feature that the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is not smaller than a second threshold value comprises that the frequency domain interval of the first RO between all frequency resources (or all sub-carriers) included in the frequency domain and the highest frequency (or the highest index sub-carrier included) of the target sub-band is not smaller than the second threshold value.
As an embodiment, the technical feature that the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is not smaller than a second threshold value comprises that the frequency domain interval of the first RO between all frequency resources (or all sub-carriers) included in the frequency domain and the lowest frequency (or the lowest indexed sub-carrier) included in the target sub-band is not smaller than the second threshold value, and that the frequency domain interval of the first RO between all frequency resources (or all sub-carriers) included in the frequency domain and the highest frequency (or the highest indexed sub-carrier) included in the target sub-band is not smaller than the second threshold value.
As an embodiment, the technical feature that the frequency domain interval of the first RO between the frequency domain and at least one boundary of the target sub-band is not smaller than a second threshold value comprises that the frequency domain interval between the highest frequency (or highest indexed sub-carrier) of the first RO and the highest frequency (or highest indexed sub-carrier included) of the target sub-band is not smaller than the second threshold value, and that the frequency domain interval between the lowest frequency (or lowest indexed sub-carrier) of the first RO and the lowest frequency (or lowest indexed sub-carrier included) of the target sub-band is not smaller than the second threshold value.
As an embodiment the technical feature that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and that the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than a second threshold comprises that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and that the validity of the first RO depends on the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than the second threshold.
As an embodiment the technical feature that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband being not smaller than a second threshold comprises that the first RO belonging to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband being not smaller than the second threshold is used for determining (or judging) that the first RO is valid.
As an embodiment the technical feature that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and that the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than a second threshold comprises that the first RO belonging to the target subband in the frequency domain and that the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than the second threshold is a requirement that the first RO is valid.
As an embodiment the technical feature that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and that the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than a second threshold comprises that the condition that the first RO validity comprises that the first RO belongs to the target subband in the frequency domain and that the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not smaller than the second threshold.
As an embodiment the technical feature that the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband being not smaller than a second threshold comprises that the first RO is valid when the first RO belongs to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband being not smaller than the second threshold.
As an embodiment, the second threshold is a non-negative integer.
As an embodiment, the second threshold may be a non-integer.
As an embodiment, the second threshold is in hertz or kilohertz.
As an embodiment, the second threshold represents the number of subcarriers.
As an embodiment, the second threshold is configured to include higher layer signaling or higher layer parameters indicating the second threshold.
As an embodiment the second threshold is configured comprising that the second threshold depends on higher layer signaling or higher layer parameters.
As an embodiment the second threshold is configured to comprise that the second threshold depends on a subcarrier spacing, higher layer signaling or higher layer parameters indicating the subcarrier spacing on which the second threshold depends.
As an embodiment, the second threshold is configured to include calculating a parameter of the second threshold including a second parameter value, the second parameter value being indicated by higher layer signaling or higher layer parameters.
As an embodiment the second threshold value is predefined comprising that the second threshold value is fixed.
As an embodiment the second threshold value is predefined comprising that the second threshold value is hard coded in a standard.
As an embodiment the second threshold value is predefined comprising that the relation between the second threshold value and the value of the further parameter is fixed.
As an embodiment the second threshold value is predefined comprising that the correspondence between the second threshold value and the subcarrier spacing is fixed.
As an embodiment the second threshold value is predefined comprising calculating a parameter of the second threshold value comprising a second parameter value, the second parameter value being a fixed value.
As an embodiment, the second threshold is related to a subcarrier spacing of the preamble.
As an embodiment, the second threshold is related to a subcarrier spacing of the target subband.
As an embodiment, the second threshold is related to a subcarrier spacing of BWP.
As an embodiment, the second threshold and the subcarrier spacing of the preamble are both related to the subcarrier spacing of the target subband.
Example 10
Embodiment 10 illustrates a schematic diagram of a first capability information block according to one embodiment of the present application, as shown in fig. 10. In fig. 10, the horizontal axis represents time, the cross-hatching filled rectangles represent full duplex symbols, the unfilled rectangular areas represent non-full duplex symbols, and the first capability information block indicates that the sender of the first capability information block supports a random access procedure in the full duplex symbols.
In embodiment 10, the first capability information block in the present application indicates that the sender of the first capability information block supports a random access procedure in a full duplex symbol.
As an embodiment, introducing the first capability information block indicates that the sender of the first capability information block supports the random access procedure in full duplex symbols, which increases flexibility and also increases robustness of the system.
As an embodiment, the technical feature that the first capability information block indicates that the sender of the first capability information block supports a random access procedure in a full duplex symbol comprises that the first capability information block indicates whether the sender of the first capability information block supports a random access procedure in a full duplex symbol.
As an embodiment the technical feature that the first capability information block indicates that the sender of the first capability information block supports a random access procedure in a full duplex symbol comprises that all or part of the first capability information block is used to indicate, either explicitly or implicitly, that the sender of the first capability information block supports a random access procedure in a full duplex symbol.
As an embodiment the technical feature that the first capability information block indicates that the sender of the first capability information block supports a random access procedure in full duplex symbols comprises that the sender of the first capability information block is a SBFD enabled device and that SBFD enabled device can perform a random access procedure on SBFD symbols.
As an embodiment the technical feature that said first capability information block indicates that the sender of said first capability information block supports a random access procedure in full duplex symbols comprises that a parameter or field comprised by said first capability information block is equal to a given value being used to indicate that the sender of said first capability information block supports a random access procedure in full duplex symbols.
As an embodiment the technical feature that the first capability information block indicates that the sender of the first capability information block supports a random access procedure in a full duplex symbol comprises that a field in the first capability information block indicating that the sender of the first capability information block supports a random access procedure in a full duplex symbol is included.
As an embodiment, the technical feature that the first capability information block indicates that the sender of the first capability information block supports a random access procedure in a full duplex symbol comprises that the first capability information block indicates that the sender of the first capability information block has the capability of random access in a full duplex symbol.
Example 11
Embodiment 11 illustrates a schematic diagram of mapping of a first RO set and a second RO set with a synchronized broadcast signal according to an embodiment of the present application, as shown in fig. 11. In fig. 11, each rectangle represents a transmission of a synchronous broadcast signal, wherein numerals #0, #1, and #2 represent index values of the synchronous broadcast signal, an upper dotted oval represents ROs in the first RO set, and a lower dotted oval represents ROs in the second RO set.
In embodiment 11, ROs in the first RO set and ROs in the second RO set in the present application are each mapped with a synchronized broadcast signal.
As an embodiment, for the split mapping between the ROs in the first RO set and the ROs in the second RO set and the synchronous broadcast signal, adverse effects on other users are avoided while the PRACH capacity is improved, and backward compatibility is ensured.
As an embodiment the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set each with the synchronized broadcast signal comprises that the ROs in the first RO set and ROs in the second RO set are mapped independently with the synchronized broadcast signal.
As an embodiment, the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal each comprises that ROs in the first RO set that are in the time domain on full duplex symbols and ROs in the second RO set that are in the time domain on non-full duplex symbols each are mapped with the synchronized broadcast signal.
As an embodiment, the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal each comprises that ROs in the first RO set that are located in the time domain on full duplex symbols indicated as downlink or flexible by TDD uplink and downlink configuration and ROs in the second RO set that are located in the time domain on non full duplex symbols or on full duplex symbols indicated as flexible by TDD uplink and downlink configuration each map with the synchronized broadcast signal.
As an embodiment the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal each comprises that the ROs in the first RO set and ROs in the second RO set are each mapped with the synchronized broadcast signal within a time window. As an adjunct to the above embodiment, this has the advantage of reducing standard workload by continuing with the existing design of association cycles (association period).
As an embodiment, the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal respectively comprises that ROs in the first RO set that are located in the time domain on full duplex symbols indicated as downlink or flexible by TDD uplink and downlink configuration and ROs in the second RO set that are located in the time domain on non full duplex symbols or on full duplex symbols indicated as flexible by TDD uplink and downlink configuration are each mapped with the synchronized broadcast signal within a time window. As an adjunct to the above embodiment, this has the advantage of reducing standard workload by continuing with the existing design of association cycles (association period).
As an embodiment, the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal respectively comprises that ROs in the first RO set that are located in the time domain on full duplex symbols indicated as downlink or flexible by TDD uplink and downlink configuration and ROs in the second RO set that are located in the time domain on non full duplex symbols or on full duplex symbols indicated as flexible by TDD uplink and downlink configuration are mapped with the synchronized broadcast signal respectively in respective time windows. As an adjunct to the above embodiments, the benefit of doing so is to employ a separate association period (association period) that increases flexibility and optimizes PRACH capacity performance.
As an embodiment the technical feature that the mapping of ROs in the first set of ROs and ROs in the second set of ROs each and the synchronized broadcast signal comprises that the mapping of ROs in the first set of ROs and synchronized broadcast signals and the mapping of ROs in the second set of ROs and synchronized broadcast signals do not affect each other.
As an embodiment the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal each comprises that the ROs in the first RO set and ROs in the second RO set are each mapped with an index of the synchronized broadcast signal.
As an embodiment, the technical feature that the mapping of ROs in the first RO set and ROs in the second RO set with the synchronized broadcast signal each comprises that the ROs in the first RO set and ROs in the second RO set are each mapped according to the same ordering rule and the index of the synchronized broadcast signal.
As an embodiment the technical feature that the mapping of ROs in the first RO set and the second RO set with the synchronized broadcast signal each comprises ordering the ROs in the first RO set and the ROs in the second RO set each independently and then mapping each with the synchronized broadcast signal.
As an embodiment the technical feature that the mapping of ROs in the first set of ROs and the second set of ROs each with the synchronized broadcast signal comprises that ROs in the first set of ROs are sequentially associated with the synchronized broadcast signal in a given order and that ROs in the second set of ROs are also sequentially associated with the synchronized broadcast signal in the given order.
As an embodiment, the technical features that the mapping of ROs in the first RO set and the second RO set with the synchronized broadcast signal includes that the synchronized broadcast block index and the ROs in the first RO set are sequentially mapped according to a mapping order of a preamble index in one RO, a frequency resource index of a frequency-divided RO, a time domain resource index of a time-divided RO in one PRACH slot, and finally an index of a PRACH slot, and that the synchronized broadcast block index and the ROs in the second RO set are sequentially mapped according to a mapping order of a preamble index in one RO, a frequency resource index of a frequency-divided RO, a time domain resource index of a time-divided RO in one PRACH slot, and finally an index of a PRACH slot.
As an embodiment, the technical feature that the mapping of ROs in the first RO set and the second RO set with the synchronized broadcast signal each comprises that the synchronized broadcast block maps sequentially according to an index of 0, 1..the synchronized broadcast block maps sequentially according to a frequency resource index of an RO in one RO, then a frequency resource index of an RO in frequency division, then a time domain resource index of an RO in one PRACH slot, and finally a mapping order of an index of a PRACH slot, and that the synchronized broadcast block maps sequentially according to an index of 0, 1..the synchronized broadcast block maps sequentially according to a frequency resource index of an RO in frequency division, then a time domain resource index of an RO in one PRACH slot, and finally a mapping order of an index of a PRACH slot.
Example 12
Embodiment 12 illustrates a block diagram of a processing apparatus for use in a terminal according to an embodiment of the present application, as shown in fig. 12. In fig. 12, a processing means 1200 in a terminal comprises a first receiver 1201 and a first transmitter 1202. The first receiver 1201 includes the transmitter/receiver 456 (including the antenna 460) of fig. 4 of the present application, the receive processor 452 and the controller/processor 490, and the first transmitter 1202 includes the transmitter/receiver 456 (including the antenna 460) of fig. 4 of the present application, the transmit processor 455 and the controller/processor 490.
In embodiment 12, a first receiver 1201 receives a first information block indicating a symbol type of at least one symbol, the first information block indicating a target subband, receives a second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein the first RO is one RO comprised in the first set of ROs occupying at least one full duplex symbol indicated as flexible by a TDD uplink-downlink configuration, the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set comprising SSB indices of the second set of ROs associated with at least one RO overlapping the first RO in the time domain.
As an embodiment, mapping between each RO included in the first RO and the second RO set to non-overlapping time-frequency resources respectively and SSB indices associated with the first RO belong to a target SSB index set is a condition that the first RO is valid.
As an embodiment, all ROs included in the second RO set that overlap in the time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration belong to the target subband in the frequency domain.
As an embodiment, the validity of the first RO depends on the length of the interval of the first RO between the time domain and adjacent non-full duplex symbols being larger than a first threshold, which is configured or predefined and/or related to user equipment capabilities.
As an embodiment, the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not less than a second threshold, the second threshold being predefined or configured.
As one embodiment, the first transmitter 1202 transmits a first capability information block indicating that the transmitter of the first capability information block supports a random access procedure in full duplex symbols.
As an embodiment, ROs in the first RO set and ROs in the second RO set are each mapped with a synchronization broadcast signal.
Example 13
Embodiment 13 illustrates a block diagram of a processing apparatus for use in a base station according to one embodiment of the present application, as shown in fig. 13. In fig. 13, a processing apparatus 1300 in a base station includes a second transmitter 1301 and a second receiver 1302. The second transmitter 1301 includes the transmitter/receiver 416 (including the antenna 460) of fig. 4 of the present application, the transmit processor 415 and the controller/processor 440, and the second receiver 1302 includes the transmitter/receiver 416 (including the antenna 460) of fig. 4 of the present application, the receive processor 412 and the controller/processor 440.
In embodiment 13, the second transmitter 1301 transmits a first information block indicating a symbol type of at least one symbol, the first information block indicating a target sub-band, transmits a second information block indicating a first set of ROs, and a third information block indicating a second set of ROs, the ROs in the first set of ROs occupying at least one full duplex symbol in the time domain, wherein the first RO is one RO included in the first set of ROs occupying at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration, the validity of the first RO depends on a relationship between an SSB index associated with the first RO and a target SSB index set including SSB indices associated with at least one RO overlapping the first RO in the time domain in the second set of ROs.
As an embodiment, mapping between each RO included in the first RO and the second RO set to non-overlapping time-frequency resources respectively and SSB indices associated with the first RO belong to a target SSB index set is a condition that the first RO is valid.
As an embodiment, all ROs included in the second RO set that overlap in the time domain and at least one full duplex symbol indicated as flexible by TDD uplink and downlink configuration belong to the target subband in the frequency domain.
As an embodiment, the validity of the first RO depends on the length of the interval of the first RO between the time domain and adjacent non-full duplex symbols being larger than a first threshold, which is configured or predefined and/or related to user equipment capabilities.
As an embodiment, the validity of the first RO depends on the first RO belonging to the target subband in the frequency domain and the frequency domain spacing of the first RO between the frequency domain and at least one boundary of the target subband is not less than a second threshold, the second threshold being predefined or configured.
As one embodiment, the second receiver 1302 receives a first capability information block indicating that a sender of the first capability information block supports a random access procedure in full duplex symbols.
As an embodiment, ROs in the first RO set and ROs in the second RO set are each mapped with a synchronization broadcast signal.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the present application is not limited to any specific combination of software and hardware. The terminal or the base station or the UE or the terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, an internet access card, low-power equipment, eMTC equipment, NB-IoT equipment, vehicle-mounted communication equipment, an aircraft, an airplane, an unmanned aerial vehicle, a remote control airplane, a testing device and a testing device. And (5) testing equipment such as instruments. The base station equipment or the base station or the network side equipment in the application comprises, but is not limited to, equipment such as a macro cell base station, a micro cell base station, a home base station, a relay base station, an eNB, a gNB, a transmission receiving node TRP, a relay satellite, a satellite base station, an air base station, a testing device, a testing instrument and the like.
It will be appreciated by those skilled in the art that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the presently disclosed embodiments are considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than by the foregoing description, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.