WO2024087455A1 - Procédé et appareil pour améliorer la planification d'informations système - Google Patents

Procédé et appareil pour améliorer la planification d'informations système Download PDF

Info

Publication number
WO2024087455A1
WO2024087455A1 PCT/CN2023/080322 CN2023080322W WO2024087455A1 WO 2024087455 A1 WO2024087455 A1 WO 2024087455A1 CN 2023080322 W CN2023080322 W CN 2023080322W WO 2024087455 A1 WO2024087455 A1 WO 2024087455A1
Authority
WO
WIPO (PCT)
Prior art keywords
time domain
system information
information block
carrier
dci
Prior art date
Application number
PCT/CN2023/080322
Other languages
English (en)
Inventor
Yingying Li
Zhi YAN
Yuantao Zhang
Haiming Wang
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2023/080322 priority Critical patent/WO2024087455A1/fr
Publication of WO2024087455A1 publication Critical patent/WO2024087455A1/fr

Links

Definitions

  • Embodiments of the present disclosure generally relate to wireless communication technology, and more particularly to enhancement on system information scheduling.
  • Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcasts, and so on.
  • Wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power) .
  • Examples of wireless communication systems may include fourth generation (4G) systems, such as long-term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems, which may also be referred to as new radio (NR) systems.
  • 4G systems such as long-term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may also be referred to as new radio (NR) systems.
  • a user equipment may need to receive system information (e.g., a system information block (SIB) ) from a base station (BS) for subsequent communications with the BS.
  • system information e.g., a system information block (SIB)
  • BS base station
  • the UE may include a transceiver, and a processor coupled to the transceiver.
  • the processor may be configured to: receive, at a first time domain position, a first configuration for a first system information block of a first carrier, wherein the first configuration indicates at least one of following: a frequency domain resource assignment for the first system information block, a time domain resource assignment for the first system information block, a first time domain offset for scheduling the first system information block, an indicator indicating a time domain resource allocation table to be applied to the first system information block, or a second time domain offset associated with the first system information block; and receive a physical downlink shared channel (PDSCH) carrying the first system information block at a second time domain position based on the first configuration.
  • PDSCH physical downlink shared channel
  • the first configuration may be received in downlink control information (DCI) on a second carrier, and the DCI may schedule a second system information block of the second carrier.
  • DCI downlink control information
  • the DCI may include a field for indicating a multiplexing pattern between the first system information block and the second system information block.
  • the processor may be further configured to receive a first DCI for scheduling a second system information block of a second carrier on the second carrier in a control resource set (CORESET) .
  • the first DCI may indicate whether the second carrier carries the first system information block or not.
  • the processor may be further configured to: perform a physical downlink control channel (PDCCH) detection in one or more PDCCH candidates associated with the second system information block in the CORESET, wherein the first DCI is received in one of the one or more PDCCH candidates; and perform a PDCCH detection in one or more PDCCH candidates associated with the first system information block in the CORESET in the case that the first DCI indicates that the second carrier carries the first system information block.
  • PDCCH physical downlink control channel
  • the BS may include a transceiver, and a processor coupled to the transceiver.
  • the processor may be configured to: transmit, at a first time domain position, a first configuration for a first system information block of a first carrier, wherein the first configuration indicates at least one of following: a frequency domain resource assignment for the first system information block, a time domain resource assignment for the first system information block, a first time domain offset for scheduling the first system information block, an indicator indicating a time domain resource allocation table to be applied to the first system information block, or a second time domain offset associated with the first system information block; and transmit a physical downlink shared channel (PDSCH) carrying the first system information block at a second time domain position based on the first configuration.
  • PDSCH physical downlink shared channel
  • the second time domain position may be determined based on: the first time domain position and the first time domain offset; the first time domain position, the first time domain offset and a third time domain offset determined based on the time domain resource assignment; the first time domain position and a fourth time domain offset determined based on the time domain resource assignment and the time domain resource allocation table to be applied; the first time domain position and the second time domain offset; the first time domain position, the first time domain offset and a fifth time domain offset determined based on a time domain resource assignment for a second system information block of a second carrier; or the fifth time domain offset and the first time domain position.
  • the first configuration is transmitted on a second carrier in a second system information block of the second carrier; or wherein the first time domain offset is predefined.
  • the time domain resource allocation table to be applied is: selected from a plurality of predefined time domain resource allocation tables based on the indicator; predefined; determined based on a synchronization signal block (SSB) and control resource set (CORESET) multiplexing pattern of the second carrier; or the same as a time domain resource allocation table applied to the second system information block.
  • SSB synchronization signal block
  • CORESET control resource set
  • the processor may be further configured to transmit a second system information block for a second carrier on the second carrier at a third time domain position, wherein the second system information block may include a second configuration of a control resource set (CORESET) associate with the first system information block.
  • the processor may be further configured to transmit DCI including the first configuration on the first carrier or on the second carrier based on the second configuration.
  • the first configuration is transmitted in DCI on a second carrier, and the DCI schedules a second system information block of the second carrier.
  • At least one reserved bit in the DCI is used to indicate: the first time domain offset; the time domain resource assignment and the first time domain offset; or the frequency domain resource assignment.
  • the DCI may include a field for indicating a multiplexing pattern between the first system information block and the second system information block.
  • the processor may be further configured to transmit a first DCI for scheduling a second system information block of a second carrier on the second carrier in a CORESET.
  • the first DCI may indicate whether the second carrier carries the first system information block or not.
  • the first DCI in transmitted in one of one or more PDCCH candidates associated with the second system information block in the CORESET.
  • the processor may be further configured to transmit a second DCI for scheduling the first system information block on the second carrier in one of one or more PDCCH candidates associated with the first system information block in the CORESET in the case that the first DCI indicates that the second carrier carries the first system information block, and wherein the second DCI may include the first configuration.
  • cyclic redundancy checks (CRCs) of the first DCI and the second DCI are scrambled by different radio network temporary identifiers (RNTIs) .
  • RNTIs radio network temporary identifiers
  • the first configuration further indicates at least one of: a starting symbol associated with the first system information block or an allocation length associated with the first system information block.
  • Some embodiments of the present disclosure provide a method performed by a UE.
  • the method may include: receiving, at a first time domain position, a first configuration for a first system information block of a first carrier, wherein the first configuration indicates at least one of following: a frequency domain resource assignment for the first system information block, a time domain resource assignment for the first system information block, a first time domain offset for scheduling the first system information block, an indicator indicating a time domain resource allocation table to be applied to the first system information block, or a second time domain offset associated with the first system information block; and receiving a physical downlink shared channel (PDSCH) carrying the first system information block at a second time domain position based on the first configuration.
  • PDSCH physical downlink shared channel
  • Some embodiments of the present disclosure provide a method performed by a BS.
  • the method may include: transmitting, at a first time domain position, a first configuration for a first system information block of a first carrier, wherein the first configuration indicates at least one of following: a frequency domain resource assignment for the first system information block, a time domain resource assignment for the first system information block, a first time domain offset for scheduling the first system information block, an indicator indicating a time domain resource allocation table to be applied to the first system information block, or a second time domain offset associated with the first system information block; and transmitting a physical downlink shared channel (PDSCH) carrying the first system information block at a second time domain position based on the first configuration.
  • PDSCH physical downlink shared channel
  • the apparatus may include: at least one non-transitory computer-readable medium having stored thereon computer-executable instructions; at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry and the at least one transmitting circuitry, wherein the at least one non-transitory computer-readable medium and the computer executable instructions may be configured to, with the at least one processor, cause the apparatus to perform a method according to some embodiments of the present disclosure.
  • FIG. 1 illustrates a schematic diagram of a wireless communication system in accordance with some embodiments of the present disclosure
  • FIGS. 2-7 illustrate exemplary timing relationships between a system information block and its scheduling information in accordance with some embodiments of the present disclosure
  • FIGS. 8 and 9 illustrate flow charts of exemplary procedures of wireless communications in accordance with some embodiments of the present disclosure.
  • FIG. 10 illustrates a block diagram of an exemplary apparatus in accordance with some embodiments of the present disclosure.
  • FIG. 1 illustrates a schematic diagram of wireless communication system 100 in accordance with some embodiments of the present disclosure.
  • wireless communication system 100 may include some UEs 101 (e.g., UE 101a and UE 101b) and a base station (e.g., BS 102) . Although a specific number of UEs 101 and BS 102 is depicted in FIG. 1, it is contemplated that any number of UEs and BSs may be included in the wireless communication system 100.
  • the UE (s) 101 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the UE (s) 101 may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE (s) 101 includes wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE (s) 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • the UE (s) 101 may communicate with the BS 102 via uplink (UL) communication signals.
  • UL uplink
  • the BS 102 may be distributed over a geographical region.
  • the BS 102 may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art.
  • the BS 102 is generally a part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BSs 102.
  • the BS 102 may communicate with UE(s) 101 via downlink (DL) communication signals.
  • DL downlink
  • the wireless communication system 100 may be compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high-altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the wireless communication system 100 is compatible with 5G NR of the 3GPP protocol.
  • BS 102 may transmit data using an orthogonal frequency division multiple (OFDM) modulation scheme on the DL and the UE (s) 101 may transmit data on the UL using a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix-OFDM (CP-OFDM) scheme.
  • DFT-S-OFDM discrete Fourier transform-spread-orthogonal frequency division multiplexing
  • CP-OFDM cyclic prefix-OFDM
  • the wireless communication system 100 may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.
  • the BS 102 and UE (s) 101 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present disclosure, the BS 102 and UE (s) 101 may communicate over licensed spectrums, whereas in some other embodiments, the BS 102 and UE (s) 101 may communicate over unlicensed spectrums.
  • the present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
  • a synchronization signal block may include a primary synchronization signal (PSS) , a secondary synchronization signal (SSS) , and a physical broadcast channel (PBCH) .
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • PBCH physical broadcast channel
  • MIB Master information block
  • CORESET control resource set
  • the structure of an MIB may be defined as follows in 3GPP specifications:
  • the configuration information (e.g., pdcch-ConfigSIB1 as specified in 3GPP specifications) in the MIB can be used to determine, for example, a common CORESET (e.g., CORESET #0) , a common search space (e.g., Type0-PDCCH search space) and some necessary physical downlink control channel (PDCCH) parameters.
  • a common CORESET e.g., CORESET #0
  • a common search space e.g., Type0-PDCCH search space
  • PDCCH physical downlink control channel
  • the common search space can be determined from the four least significant bits (LSBs) of the above-mentioned configuration information (e.g., pdcch-ConfigSIB1) , depending on a multiplexing pattern of SSB and CORESET.
  • the common CORESET e.g., CORESET#0
  • MSBs most significant bits
  • Table 1 below shows an exemplary set of candidate configurations for a CORESET (e.g., CORESET#0) . It should be understood that Table 1 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • Each entry (or row) in Table 1 refers to a candidate configuration for a CORESET (e.g., CORESET#0) .
  • Each entry in Table 1 can be indicated by an index and include a set of parameters for the CORESET, including: an SSB and CORESET multiplexing pattern, the number of resource blocks (RBs) (e.g., denote as ) included in the CORESET, the number of symbols (e.g., denote as ) included in the CORESET, and an RB offset between the CORESET and the SSB.
  • the RB offset may denote the lowest physical resource block (PRB) in the frequency domain of the CORESET and a common resource block (CRB) overlapped with the lowest PRB in the frequency domain of the SSB.
  • PRB physical resource block
  • CRB common resource block
  • the UE may detect an SSB and may determine a CORESET (e.g., CORESET#0) based on the configuration information in the MIB.
  • the MIB may indicate an index from Table 1.
  • the UE can determine the configuration for the CORESET (e.g., CORESET#0) .
  • the UE may then monitor a PDCCH in the CORESET.
  • the UE may detect a PDCCH (e.g., carrying downlink control information (DCI) ) in the CORESET.
  • DCI downlink control information
  • the cyclic redundancy check (CRC) of the DCI may be scrambled by a radio network temporary identifier (RNTI) such as system information RNTI (SI-RNTI) .
  • RNTI radio network temporary identifier
  • SI-RNTI system information RNTI
  • the DCI may schedule system information of the cell (or the carrier) .
  • the DCI may schedule a physical downlink shared channel (PDSCH) which carries a system information block (e.g., system information block 1 (SIB1) ) .
  • SIB1 system information block 1
  • the DCI may include the following information for scheduling the system information block:
  • Frequency domain resource assignment which may include variable bits based on the size of the CORESET (e.g., CORESET#0) ;
  • Time domain resource assignment which may include 4 bits
  • a UE Based on the scheduling information in the DCI, a UE can determine the resource (s) assigned for the PDSCH and receive the PDSCH carrying the system information block based on the information in the DCI.
  • different time domain resource allocation tables may be applied for different multiplex pattern of SSB and CORESET.
  • the mapping relationship between the multiplex patterns of SSB and CORESET and the associated applicable time domain resource allocation tables may be predefined (e.g., in 3GPP specifications) , preconfigured or configured.
  • the time domain resource allocation tables may be predefined in 3GPP specifications, preconfigured, or configured.
  • Table 2 shows an exemplary mapping relationship between the multiplex pattern of SSB and CORESET and the associated applicable time domain resource allocation table. It should be understood that Table 2 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • the PDCCH search space is a Type0 common search space (e.g., the DCI is detected in CORESET#0)
  • the time domain resource allocation table to be applied can be “Default A for normal CP, ” “Default B, ” or “Default C, ” depending on the associated SSB and CORESET multiplexing pattern.
  • Table 3 shows an exemplary time domain resource allocation table. It should be understood that Table 3 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • “dmrs-typeA-Position” denotes demodulation reference signal (DMRS) position information.
  • DMRS demodulation reference signal
  • “dmrs-typeA-Position” indicates a symbol position at which a DMRS is transmitted within a slot.
  • “PDSCH mapping type” denotes a position of a DMRS in the scheduled resource region.
  • a DMRS may always be transmitted or received at a symbol position determined by “dmrs-typeA-Position” regardless of the assigned time domain resource.
  • the PDSCH mapping type is Type B
  • “dmrs-typeA-Position” information is not applicable.
  • a position of the DMRS may always be a first symbol of the assigned time domain resource.
  • K 0 denotes a slot offset between a DCI and the PDSCH scheduled by the DCI
  • S denotes a starting symbol of the PDSCH transmission
  • L denotes the length of PDSCH (in units of symbol) .
  • a UE can first determine a time domain resource allocation table (e.g., Table 3) to be applied for scheduling the PDSCH based on the SSB and CORESET multiplexing pattern (e.g., according to Table 2) , and then determine a time domain resource assignment for the PDSCH based on the time domain resource assignment field in the DCI, which may indicate an entry (or row) from the determined time domain resource allocation table.
  • the time domain resource assignment field in the DCI may indicate a specific row from Table 3 by indicating the corresponding row index. Then, the UE can determine the time domain resource assigned for the PDSCH transmission.
  • a synchronization signal (SS) burst set is a collection of multiple SSBs within a certain period. Each SSB may correspond to a beam direction in the same period. The number of SSBs in a period may be related to the SSB pattern. The number of actual transmitted SSBs may be determined by a bitmap of the SSB in the period.
  • An SS burst set (also referred to as SSB set) is transmitted towards UEs at regular intervals based on a periodicity set (e.g., 5, 10, 20, 40, 80, or 160 ms) , the periodicity of transmitting the SSB set is hereinafter also referred to as SSB set periodicity.
  • the PDCCH scheduling system information (e.g., SIB1) and the system information (e.g., SIB1) may be transmitted multiple times with different beam.
  • system information such as SIB1 may be transmitted on a downlink shared channel (DL-SCH) with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms.
  • the default transmission repetition periodicity of SIB1 may be 20 ms, but the actual transmission repetition periodicity may be up to the network implementation.
  • SIB1 repetition transmission period is 20 ms.
  • SIB1 transmission repetition period is the same as the SSB set periodicity.
  • Beam sweeping may be employed by a BS for cell coverage.
  • the SSBs are transmitted using subcarrier spacing (SCS) of 120kHz, and CORESET#0 and the PDSCHs carrying SIB1 are transmitted using SCS of 60kHz.
  • the BS may transmit a plurality of SSBs including SSB0 to SSB3 in different beam directions in the cell.
  • a SS burst set may include SSB0 to SSB3.
  • the plurality of SSBs or the SS burst set may include more SSBs, for example 64 SSBs in total, which are not shown in FIG. 2.
  • Different SSBs may include corresponding CORESET and search space configurations.
  • SSB0 may indicate configurations for Type0-PDCCH common search space (CSS) for SSB0 and a corresponding CORESET #0
  • SSB1 may indicate configurations for Type0-PDCCH CSS for SSB1 and a corresponding CORESET #0
  • SSB2 may indicate configurations for Type0-PDCCH CSS for SSB2 and a corresponding CORESET #0
  • SSB3 may indicate configurations for Type0-PDCCH CSS for SSB3 and a corresponding CORESET #0.
  • the BS may transmit a DCI therein which includes a time domain resource assignment field indicating a row index indicating the time domain resource allocated for a corresponding PDSCH.
  • the allocated time domain resources for the scheduled PDSCHs are respectively denoted as “Row index 1, ” “Row index 2, ” “Row index 4, ” and “Row index 5” in FIG. 2.
  • a UE can obtain system information (e.g., SIB1) of a cell (e.g., non-anchor cell/carrier) from another cell (e.g., anchor cell/carrier) .
  • SIB1 system information
  • a UE in either an RRC_IDLE or RRC_INACTIVE state can obtain system information for a cell from another cell. This may also be referred to as “system information-less operation” , “SIB-less operation” or “SIB1-less operation. ”
  • the system information may contain random access channel (RACH) configuration and other configurations that can be conceived of by persons skilled in the art.
  • RACH random access channel
  • the cell that carries system information of other cell (s) is referred to as an anchor cell; and a SIB1-less cell (or SIB-less cell, or system information-less cell) is referred to as a non-anchor cell or network energy saving (NES) cell.
  • NES network energy saving
  • SIB1 As an example of the system information, the present disclosure can also be applied to other types of system information.
  • the terms “cell” and “carrier” may be used interchangeably.
  • the scheduling mechanism for system information as described above may become problematic.
  • the time domain resource allocation may become problematic.
  • scheduling of the system information of a non-anchor carrier may need to consider the nature of the beam for the transmission of the system information.
  • scheduling the system information of a non-anchor carrier on an anchor carrier e.g., by the system information of the anchor carrier
  • the time location of the system information of the non-anchor carrier may need to consider the beam sweeping of the system information.
  • system information #0 For example, referring to FIG. 2, assuming that SSB0 and the associated system information of the anchor carrier (denoted as system information #0) is transmitted with a certain beam direction (denoted as beam direction #0) , the system information of the non-anchor carrier (denoted as system information #0’) scheduled by system information #0 may also need to be transmitted with beam direction #0.
  • system information #0’ cannot be transmitted in the current SSB set periodicity and may be transmitted in the next periodicity.
  • system information #0’ cannot be transmitted in the current SIB1 transmission repetition period and may be transmitted in the next SIB1 transmission repetition period.
  • Embodiments of the present disclosure propose solutions for enhancing system information scheduling.
  • the proposed solutions can at least solve the above-mentioned problems.
  • solutions for scheduling system information of a non-anchor carrier (s) are provided.
  • system information of a non-anchor carrier may be scheduled by system information of an anchor carrier.
  • system information of a non-anchor carrier and system information of an anchor carrier may be scheduled by separate PDCCHs in separate CORESETs and search spaces.
  • configuration information for the PDCCH which schedules the system information of a non-anchor carrier may be included in the system information of an anchor carrier.
  • system information of a non-anchor carrier and system information of an anchor carrier may be scheduled by the same or separate PDCCHs in the same CORESET and search space. More details on the embodiments of the present disclosure will be illustrated in the following text in combination with the appended drawings.
  • FIG. 8 illustrates a flow chart of exemplary procedure 800 of wireless communications in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 8.
  • the procedure may be performed by a UE, for example, UE 101 in FIG. 1.
  • a UE may receive, at a first time domain position, a first configuration for a first system information block of a first carrier.
  • the first carrier may be a non-anchor carrier.
  • the first configuration may be referred to as scheduling information for system information of a non-anchor carrier.
  • the UE may receive a PDSCH carrying the first system information block at a second time domain position based on the first configuration.
  • the first configuration and the PDSCH may be received on the first carrier (e.g., a non-anchor carrier) .
  • the first configuration and the PDSCH may be received on an anchor carrier.
  • the first configuration may indicate at least one of following: a frequency domain resource assignment for the first system information block; a time domain resource assignment for the first system information block; a first time domain offset for scheduling the first system information block; an indicator indicating a time domain resource allocation table to be applied to the first system information block; or a second time domain offset associated with the first system information block.
  • the first configuration may further indicate at least one of: a starting symbol associated with the first system information block or an allocation length associated with the first system information block.
  • the second time domain position may be determined based on: the first time domain position and the first time domain offset; the first time domain position, the first time domain offset and a third time domain offset determined based on the time domain resource assignment; the first time domain position and a fourth time domain offset determined based on the time domain resource assignment and the time domain resource allocation table to be applied; the first time domain position and the second time domain offset; the first time domain position, the first time domain offset and a fifth time domain offset determined based on a time domain resource assignment for a second system information block of a second carrier; or the fifth time domain offset and the first time domain position.
  • the first configuration may be received on a second carrier in a second system information block of the second carrier.
  • the second carrier may be an anchor carrier.
  • the first configuration may be included in SIB1 of the anchor carrier.
  • the first configuration may include at least one of the following parameters for scheduling the first system information block: (a) Frequency domain resource assignment; (b) Time domain resource assignment; (c) VRB-to-PRB mapping; (d) Modulation and coding scheme; or (e) Redundancy version.
  • parameter (b) may indicate an entry (or row) from a time domain resource allocation table, which may be the same as the time domain resource allocation table for scheduling the second system information block of the second carrier (e.g., SIB1 of the anchor carrier) or may be a separate table for scheduling the first system information block of the first carrier (e.g., SIB1 of the non-anchor carrier) .
  • the time domain resource allocation table for scheduling system information of an anchor carrier can be determined based on the SSB and CORESET multiplexing pattern of the anchor carrier.
  • the separate table can be implicitly or explicitly determined.
  • the first configuration may further indicate at least one of the following parameters for scheduling the first system information block: (f) a time domain offset (e.g., the first time domain offset as mentioned above) ; (g) a time domain resource allocation table to be applied (e.g., using an indicator to indicate the time domain resource allocation table to be applied to the first system information block) ; or (h) at least one of a time domain offset associated with the first system information block (e.g., the second time domain offset as mentioned above) , a starting symbol associated with the first system information block or an allocation length associated with the first system information block.
  • a time domain offset e.g., the first time domain offset as mentioned above
  • a time domain resource allocation table to be applied e.g., using an indicator to indicate the time domain resource allocation table to be applied to the first system information block
  • at least one of a time domain offset associated with the first system information block e.g., the second time domain offset as mentioned above
  • parameter (f) can be a slot offset.
  • the range value of parameter (f) may be the same as that of a radio resource control (RRC) configured time domain offset between a DCI and the scheduled PDSCH.
  • RRC radio resource control
  • the range value of parameter (f) may be integer [0 32].
  • the second time domain position may be determined based on the first time domain position and parameter (f) . In some embodiments, the second time domain position may be determined based on the first time domain position, parameter (f) and a third time domain offset determined based on parameter (b) .
  • parameter (b) can indicate a row of a time domain resource allocation table (which can, for example, determined based on the SSB and CORESET multiplexing pattern of the second carrier) .
  • the third time domain offset can be a K 0 value in the indicated row of the time domain resource allocation table.
  • the second time domain position may be determined based on the first time domain position and the time domain offset in parameter (h) .
  • a UE may receive a DCI in CORESET 311 (e.g., CORESET #0) on an anchor carrier.
  • the DCI may schedule a PDSCH carrying system information 331 (e.g., SIB1) of the anchor carrier.
  • system information 331 e.g., SIB1
  • the DCI may indicate time offset 351 (e.g., a K 0 value) from a time domain resource allocation table (denoted as Table #n1) .
  • Table #n1 can be determined based on a SSB and CORESET multiplexing pattern of the anchor carrier.
  • System information 331 may include scheduling information of system information 333 of a non-anchor carrier (or scheduling information of a PDSCH carrying system information 333) .
  • the scheduling information may include the first configuration as described above.
  • Time offset 353 may be determined based on the scheduling information.
  • system information 333 may be received in slot (n1+offset #n1) or slot (n1+offset #n1+K 0 ’) on, for example, the anchor carrier. That is, time offset 353 may be equal to offset #n1 or offset #n1+K 0 ’.
  • Offset #n1 can be determined based on parameter (f) and K 0 ’ can be determined based on parameter (b) .
  • parameter (b) may indicate row #n1 from the time domain resource allocation table (e.g., Table #n1) . The parameters in row #n1 may be applied to system information 333.
  • the value of K 0 ’ may be the slot offset value indicated in row #n1 (e.g., a K 0 value in Table 3) .
  • the starting symbol and length of the PDSCH carrying system information 333 is consistent with the corresponding parameters indicated in row #n1 (e.g., S and L in Table 3) .
  • the time domain resource allocation table to be applied to the system information of the non-anchor carrier can be decoupled from the multiplexing pattern of SSB and CORESET of the anchor carrier and can be determined with more flexibility.
  • the time domain resource allocation table to be applied to the first system information block may be separately configured or (pre) defined.
  • the second time domain position may be determined based on the first time domain position and a fourth time domain offset determined based on parameter (b) and the time domain resource allocation table to be applied to the first system information block.
  • the first configuration may include parameter (g) .
  • parameter (g) may be an indicator which indicates the time domain resource allocation table to be applied to the first system information block.
  • the time domain resource allocation table to be applied to the first system information block may be selected from a plurality of predefined time domain resource allocation tables (e.g., “Default A for normal CP, ” “Default B” and “Default C” as specified in 3GPP specifications) and parameter (g) may indicate one of the plurality of predefined time domain resource allocation tables.
  • the time domain resource allocation table to be applied to the first system information block may be predefined, for example, in a standard (s) .
  • the first configuration may not include parameter (g) .
  • one of “Default A for normal CP, ” “Default B” and “Default C” as specified in 3GPP specifications may be predefined as the time domain resource allocation table to be applied to the first system information block.
  • the time domain resource assignment for the first system information block may not be restricted to a certain time domain resource allocation table.
  • the first configuration may include parameter (h) .
  • the first configuration may directly indicate the time domain offset (e.g., a slot offset) between the scheduling information (i.e., the first configuration) and the corresponding PDSCH which carries the first system information block.
  • the first configuration may directly indicate the starting symbol and allocation length in the scheduled slot.
  • the time domain offset may indicate time offset 353.
  • parameter (f) may be predefined, for example, in a standard (s) .
  • the predefined offset can be based on the SSB set periodicity or the system information (e.g., SIB1) transmission repetition period.
  • the predefined offset can be 20ms for patterns 1, 2 and 3, or 20ms for pattern 1 and the same as the SSB set periodicity for patterns 2 and 3.
  • pattern 1/2/3 may refer to the multiplexing pattern of SSB and CORESET of the second carrier (e.g., the anchor carrier) .
  • the first configuration may include at least one of parameter (a) to parameter (e) .
  • the second time domain position may be determined based on the first time domain position and a predefined time domain offset (denoted as offset#n2) .
  • the second time domain position may be determined based on the first time domain position, offset#n2 and the third time domain offset determined based on parameter (b) .
  • system information 331 and 333 are transmitted with the same SCS and system information 331 is received in slot n1
  • system information 333 may be received in slot (n1+offset #n2) or slot (n1+offset #n2+K 0 ’) on, for example, the anchor carrier.
  • the timing relationship between the scheduling information of the system information of the non-anchor carrier and the scheduled PDSCH carrying the system information of the non-anchor carrier is not restricted to a specific table.
  • the UE may receive the scheduling information in a certain period, and then monitor the system information (e.g., SIB1) for the non-anchor carrier in the next period.
  • SIB1 system information
  • system information 431 of an anchor carrier may be transmitted using different beams (e.g., beam 1, beam 2, ...beam n, each corresponds to a different beam direction) with a periodicity P on the anchor carrier.
  • a UE may receive the scheduling information (e.g., the first configuration) of system information 433 of a non-anchor carrier on system information 431.
  • the time domain resource for system information 431 and system information 433 with the same beam direction may be the same.
  • the UE may receive a second system information block (e.g., SIB1) for a second carrier (e.g., anchor carrier) on the second carrier at a third time domain position.
  • the second system information block may include a second configuration of a CORESET associate with the first system information block.
  • the second configuration may configure a CORESET, a search space, and/or necessary PDCCH parameters associated with the first system information block in the second system information block for the second carrier.
  • the second configuration may include, for example, at least one of the following parameters:
  • SubCarrierSpacingCommon which may indicate the SCS to be used by the PDCCH carrying the scheduling information of the first system information block and the scheduled PDSCH carrying the first system information block;
  • DMRS demodulation reference signal
  • pdcch-ConfigSIB1 which may defined the CORESET, search space and/or necessary PDCCH parameters associated with the PDCCH carrying the scheduling information of the first system information block.
  • the UE may monitor a PDCCH on the first carrier or on the second carrier based on the second configuration.
  • the UE may receive a DCI including the first configuration (e.g., at least one of parameter (a) to parameter (e) ) on the PDCCH. That is, the DCI may include the scheduling information of the first system information block of the first carrier and may schedule a PDSCH carrying the first system information block of the first carrier. Then, as described with respect to operation 813, the UE may receive the PDSCH scheduled by the DCI on the first carrier or on the second carrier.
  • a UE may receive a DCI in CORESET 511a (e.g., CORESET #0) on an anchor carrier.
  • the DCI may schedule a PDSCH carrying system information 531a (e.g., SIB1) of the anchor carrier.
  • the DCI may indicate time offset 551a (e.g., a K 0 value) from a time domain resource allocation table (denoted as Table #n2) .
  • Table #n2 can be determined based on a SSB and CORESET multiplexing pattern of the anchor carrier.
  • System information 531a may configure a CORESET (e.g., CORESET 513a) to be monitored on the anchor carrier.
  • system information 531a may include the second configuration as described above.
  • Time offset 553a may be determined based on the second configuration.
  • the UE may receive another DCI in CORESET 513a on the anchor carrier.
  • This DCI may schedule a PDSCH carrying system information 533a (e.g., SIB1) of a non-anchor carrier.
  • the DCI may include the first configuration as described above.
  • Time offset 555a may be determined based on the first configuration.
  • the DCI may indicate time offset 555a from a time domain resource allocation table (denoted as Table #n3) .
  • Table #n2 and Table #n3 may be the same (e.g., determined based on the multiplexing pattern of an SSB and CORESET 511a of the anchor carrier) , or may be separately determined, predefined, or configured.
  • the UE may then receive system information 533a of the non-anchor carrier on the anchor carrier based on the scheduling information in the DCI.
  • a UE may receive a DCI in CORESET 511b (e.g., CORESET #0) on an anchor carrier (e.g., carrier #1) .
  • the DCI may schedule a PDSCH carrying system information 531b (e.g., SIB1) of carrier #1.
  • the DCI may indicate time offset 551b (e.g., a K 0 value) from a time domain resource allocation table (denoted as Table #n4) .
  • Table #n4 can be determined based on a SSB and CORESET multiplexing pattern of carrier #1.
  • System information 531b may configure a CORESET (e.g., CORESET 513b) to be monitored on a non-anchor carrier (e.g., carrier #2) .
  • system information 531b may include the second configuration as described above.
  • Time offset 553b may be determined based on the second configuration.
  • the UE may receive another DCI in CORESET 513b on carrier #2.
  • This DCI may schedule a PDSCH carrying system information 533b (e.g., SIB1) of carrier #2.
  • the DCI may include the first configuration as described above.
  • Time offset 555b may be determined based on the first configuration.
  • the DCI may indicate time offset 555b from a time domain resource allocation table (denoted as Table #n5) .
  • Table #n4 and Table #n5 may be the same or may be separately determined, predefined, or configured.
  • Table #n4 may be determined based on the multiplexing pattern of an SSB and CORESET 511b of carrier #1.
  • Table #n5 can be the same as Table #n4.
  • Table #n5 can be determined based on a SSB and CORESET (e.g. CORESET 513b) multiplexing pattern of carrier #2 or configured by RRC (e.g., the UE is in an RRC_CONNECTED state) .
  • the UE may then receive system information 533b of carrier #2 on carrier #2 based on the scheduling information in the DCI.
  • a UE may detect an SSB on an anchor carrier and may determine a CORESET on the anchor carrier based on the configuration information in the SSB.
  • This CORESET can be used to schedule system information of the anchor carrier (e.g., by a DCI detected in the CORESET) .
  • the CORESET can also be used to schedule system information of the non-anchor carrier.
  • a single PDCCH in the CORESET schedules the system information of the anchor and non-anchor carriers.
  • separate PDCCHs in the CORESET schedule the system information of the anchor and non-anchor carriers, respectively.
  • the first configuration may be received in a DCI on a second carrier (e.g., anchor carrier) .
  • the DCI may schedule a second system information block of the second carrier.
  • the DCI may also schedule the first system information block of the first carrier (e.g., non-anchor carrier) .
  • the DCI may be DCI format 1_0 with CRC scrambled by the SI-RNTI.
  • the DCI may additionally include some scheduling information (e.g., the first configuration) applied only to the first system information block.
  • the additional scheduling information (e.g., the first configuration) may include: the first time domain offset for the first system information block; the time domain resource assignment for the first system information block and the first time domain offset for the first system information block; or the frequency domain resource assignment for the first system information block.
  • at least one reserved bit in the DCI may be used to indicate the additional scheduling information.
  • the content of the additional scheduling information may be dependent on the multiplexing pattern of the system information of anchor and non-anchor carriers (e.g., the first and second system information blocks) .
  • the PDSCHs carrying the system information of anchor and non-anchor carriers are time division multiplexed (TDMed) .
  • TDMed time division multiplexed
  • the reserved bit (s) in the DCI can be used to indicate the first time domain offset for the first system information block.
  • the second time domain position may be determined based on the first time domain position, the first time domain offset and a fifth time domain offset determined based on a time domain resource assignment for the second system information block of the second carrier.
  • the DCI may indicate the time domain resource assignment for the second system information block.
  • the reserved bit (s) in the DCI can be used to indicate a time domain resource assignment for the first system information block and the first time domain offset for the first system information block.
  • the second time domain position may be determined based on the first time domain position, the first time domain offset and a third time domain offset determined based on the time domain resource assignment for the first system information block.
  • parameter (b) may be applied to the time domain resource assignment for the first system information block.
  • the time domain resource assignment for the first system information block can indicate a row of a time domain resource allocation table (which can be the same as the one applied to the second system information block, for example, determined based on the SSB and CORESET multiplexing pattern of the second carrier, or may be a separate table) .
  • the indicated row may include the third time domain offset.
  • a UE may receive DCI 671 in CORESET 611 (e.g., CORESET #0) on an anchor carrier.
  • DCI 671 may schedule a PDSCH carrying system information 631 (e.g., SIB1) of the anchor carrier.
  • system information 631 e.g., SIB1
  • DCI 671 may indicate time offset 651 (e.g., a K 0 value) from a time domain resource allocation table (denoted as Table #n6) .
  • Table #n6 can be determined based on a SSB and CORESET multiplexing pattern of the anchor carrier.
  • DCI 671 may indicate a time domain offset (denoted as offset #n3) for system information (e.g., system information 633) of a non-anchor carrier. Assuming that DCI 671 is received in slot n3, the UE can determine that system information 631 is scheduled in slot (n3+time offset 651) and system information 633 is scheduled in slot (n3+ time offset 651+ offset #n3) . That is, time offset 653 in FIG. 6 may be equal to (time offset 651+ offset #n3) .
  • the specific time domain resources for system information 633 in slot (n3+time offset 651+ offset #n3) can be determined according to the corresponding configuration for system information 631.
  • DCI 671 may indicate a row from Table #n6 which may include the starting symbol, the allocated length, and a DMRS position, which can be applied to both system information 631 and system information 633.
  • DCI 671 may indicate a time domain offset (denoted as offset #n4) and a time domain resource assignment for system information (e.g., system information 633) of a non-anchor carrier.
  • the time domain resource assignment for system information 633 in DCI 671 may indicate a row from a time domain resource allocation table (e.g., Table #n6 or a separate time domain resource allocation table for non-anchor carrier) .
  • the parameters in the indicated row may be applied to system information 633.
  • the indicated row may include time offset #n5.
  • the UE can determine that system information 631 is scheduled in slot (n3+time offset 651) and system information 633 is scheduled in slot (n3+ offset #n5+ offset #n4) . That is, time offset 653 in FIG. 6 may be equal to (offset #n5+ offset #n4) .
  • the specific time domain resources for system information 633 in slot (n3+ offset #n5+ offset #n4) can be determined according to the indicated row for system information 633 (e.g., complying with the starting symbol, the allocated length and the DMRS position in the indicated row) .
  • the PDSCHs carrying the system information of anchor and non-anchor carriers are frequency division multiplexed (FDMed) .
  • FDMed frequency division multiplexed
  • the reserved bit (s) in the DCI can be used to indicate the frequency domain resource assignment for the first system information block.
  • Other scheduling information of the first system information block may comply with that for the second system information block.
  • the first and second system information blocks may share the same time domain resources.
  • the second time domain position may be determined based on the first time domain position and the fifth time domain offset determined based on the time domain resource assignment for the second system information block of the second carrier.
  • the DCI may indicate the time domain resource assignment for the second system information block.
  • the DCI may include a field for indicating a multiplexing pattern between the first system information block and the second system information block. That is, multiplexing pattern (e.g., TDMed or FDMed) between the first system information block and the second system information block may be dynamically indicated and the additional scheduling information (e.g., in the reserved bit (s) of the DCI) may be dynamically interpreted according to the indicated multiplexing pattern.
  • multiplexing pattern e.g., TDMed or FDMed
  • additional scheduling information e.g., in the reserved bit (s) of the DCI
  • At least one reserved bit(s) in the DCI may indicate the first time domain offset for the first system information block, or indicate the time domain resource assignment for the first system information block and the first time domain offset for the first system information block.
  • at least one reserved bit (s) in the DCI may indicate the frequency domain resource assignment for the first system information block.
  • separate PDCCHs in the CORESET schedule the system information of the anchor and non-anchor carriers, respectively.
  • the UE may receive separate DCIs in a shared CORESET (e.g., CORESET #0 configured by the MIB) which separately schedule the system information of the anchor and non-anchor carriers.
  • a shared CORESET e.g., CORESET #0 configured by the MIB
  • the BS may configure more resources for the shared CORESET by the MIB.
  • the UE can detect two PDCCHs (i.e., two DCIs) respectively scheduling the system information for the anchor and non-anchor carriers in the CORESET.
  • the CORESET (e.g., CORESET#0) in which a PDCCH scheduling the system information is monitored may include one or more PDCCH candidates, wherein each PDCCH candidate may include one or more control resource elements (CCEs) on which a PDCCH may be transmitted or detected.
  • the number of CCEs included in a PDCCH candidate may be based on an aggregation level (AL) .
  • the maximum number of PDCCH candidates per CCE AL can be larger.
  • Table 4 illustrates an exemplary relationship between ALs and the maximum numbers of PDCCH candidates included in a CORESET. It should be understood that Table 4 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • the maximum number of PDCCH candidates in the third column may be enlarged (e.g., doubled) compared to the maximum number of PDCCH candidates in the second column.
  • the UE may receive a first DCI for scheduling a second system information block of a second carrier (e.g., anchor carrier) on the second carrier in a CORESET.
  • the first DCI may indicate whether the second carrier carries the first system information block of the first carrier (e.g., non-anchor carrier) or not.
  • a reserved bit in the first DCI may be used for such indication.
  • a bit value of “1” may indicate that the second carrier carries the first system information block and a bit value of “0” may indicate that the second carrier does not carry the first system information block; or vice versa.
  • the UE may in the case that the first DCI indicates that the second carrier carries the first system information block, receive a second DCI for scheduling the first system information block on the second carrier in the CORESET, wherein the second DCI may include the first configuration.
  • the CRCs of the first DCI and the second DCI may be scrambled by different RNTIs.
  • the UE may detect the first DCI with the CRC scrambled by a SI-RNTI.
  • the UE may then detect a PDSCH carrying the second system information block of the second carrier (e.g., SIB1 of the anchor carrier) based on the first DCI.
  • the UE may detect the second DCI with the CRC scrambled by a different RNTI (e.g., non-anchor carrier SI-RNTI (NSI-RNTI) ) , and detect a PDSCH carrying the first system information block of the first carrier (e.g., SIB1 of the non-anchor carrier) based on the second DCI.
  • a different RNTI e.g., non-anchor carrier SI-RNTI (NSI-RNTI)
  • the NSI-RNTI may be used for broadcasting system information for non-anchor carriers.
  • the second DCI may include scheduling information for the first system information block.
  • the second DCI may include at least one of parameters (a) - (e) as described above.
  • the second DCI may include the first configuration. That is, the second DCI may be received at the first time domain position.
  • the second DCI e.g., the first configuration
  • the second DCI may include the first time domain offset for scheduling the first system information block.
  • the first time domain offset may be indicated by at least one reserved bit in the second DCI.
  • the second time domain position may be determined based on the first time domain position and the first time domain offset indicated in the second DCI. For example, assuming that the UE receives the second DCI in slot n6 and denoting the first time domain offset as offset #n6, the UE may receive the first system information block in slot (n6+ offset #n6) .
  • the second time domain position may be determined based on the first time domain position, the first time domain offset and a third time domain offset determined based on a time domain resource assignment for the first system information block in the second DCI.
  • the above descriptions with respect to parameter (b) may be applied to the time domain resource assignment for the first system information block.
  • the time domain resource assignment in the second DCI can indicate a row of a time domain resource allocation table (which can be the same as the one applied to the second system information block, for example, determined based on the SSB and CORESET multiplexing pattern of the second carrier, or may be a separate table) .
  • the indicated row may include the third time domain offset.
  • the UE may receive the first system information block in slot (n6+ offset #n7+ offset #n8) .
  • the UE may perform PDCCH detection for the first and second DCIs according to the enlarged numbers of PDCCH candidates (e.g., new maximum number of PDCCH candidates in Table 4) .
  • the enlarged numbers of PDCCH candidates may include one or more PDCCH candidates associated with the first system information block and one or more PDCCH candidates associated with the second system information block.
  • the UE may perform PDCCH detection in one or more PDCCH candidates associated with the second system information block in the CORESET, wherein the first DCI is received in one of the one or more PDCCH candidates.
  • the UE may then perform PDCCH detection in one or more PDCCH candidates associated with the first system information block in the CORESET.
  • the resource of CORESET 711 includes 96 PRBs and 3 symbols as shown in the right part of FIG. 7.
  • Table 4 i.e., new maximum number of PDCCH candidates in Table 4
  • system information e.g., the second system information block
  • the UE may detect (or receive) DCI 771 with the CRC scrambled by SI-RNTI in one of the PDCCH candidates. DCI 771 may indicate time offset 751 and may schedule system information 731.
  • DCI 771 may include a field indicating whether the current carrier (i.e., anchor carrier) carries the system information of another carrier (e.g., non-anchor carrier) .
  • DCI 773 may indicate the first time domain offset as described above. For example, assuming that DCI 773 is detected (or received) in slot n8, time offset 753 may be based on slot n8 and the first time domain offset. For example, time offset 753 may be the first time domain offset.
  • DCI 773 may indicate the first time domain offset and the time domain resource assignment for the first system information block as described above.
  • DCI 773 may include a time domain resource assignment field indicating a row of a time domain resource allocation table. The indicated row may include an offset (denoted as offset #n9) .
  • offset #n9 an offset (denoted as offset #n9) .
  • time offset 753 may be based on slot n9, offset #n9 and the first time domain offset.
  • time offset 753 may be equal to (offset #n9 + the first time domain offset) .
  • FIG. 9 illustrates a flow chart of exemplary procedure 900 for wireless communications in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 9.
  • the procedure may be performed by a BS, for example, BS 102 in FIG. 1.
  • a BS may transmit, at a first time domain position, a first configuration for a first system information block of a first carrier.
  • the BS may transmit a PDSCH carrying the first system information block at a second time domain position based on the first configuration.
  • the first configuration may indicate at least one of following: a frequency domain resource assignment for the first system information block; a time domain resource assignment for the first system information block; a first time domain offset for scheduling the first system information block; an indicator indicating a time domain resource allocation table to be applied to the first system information block; or a second time domain offset associated with the first system information block.
  • the first configuration may further indicate at least one of: a starting symbol associated with the first system information block or an allocation length associated with the first system information block.
  • the methods for determining the second time domain position in the forgoing embodiments may apply here.
  • the second time domain position may be determined based on:the first time domain position and the first time domain offset; the first time domain position, the first time domain offset and a third time domain offset determined based on the time domain resource assignment; the first time domain position and a fourth time domain offset determined based on the time domain resource assignment and the time domain resource allocation table to be applied; the first time domain position and the second time domain offset; the first time domain position, the first time domain offset and a fifth time domain offset determined based on a time domain resource assignment for a second system information block of a second carrier; or the fifth time domain offset and the first time domain position.
  • the descriptions regarding the third, fourth, fifth time domain offset, the second system information block, and the second carrier in the forgoing embodiments may apply here.
  • the first configuration may be transmitted on a second carrier in a second system information block of the second carrier.
  • the first time domain offset may be predefined.
  • the time domain resource allocation table to be applied may be: selected from a plurality of predefined time domain resource allocation tables based on the indicator; predefined; determined based on an SSB and CORESET multiplexing pattern of the second carrier; or the same as a time domain resource allocation table applied to the second system information block.
  • the BS may transmit a second system information block for a second carrier on the second carrier at a third time domain position, wherein the second system information block may include a second configuration of a CORESET associate with the first system information block.
  • the BS may transmit DCI including the first configuration on the first carrier or on the second carrier based on the second configuration.
  • the first configuration may be transmitted in a DCI on a second carrier, and the DCI may schedule a second system information block of the second carrier.
  • At least one reserved bit in the DCI may be used to indicate: the first time domain offset; the time domain resource assignment and the first time domain offset; or the frequency domain resource assignment.
  • the DCI may include a field for indicating a multiplexing pattern between the first system information block and the second system information block.
  • the BS may transmit a first DCI for scheduling a second system information block of a second carrier on the second carrier in a CORESET.
  • the first DCI may indicate (e.g., using a reserved bit in the first DCI) whether the second carrier carries the first system information block or not.
  • the first DCI in transmitted in one of one or more PDCCH candidates associated with the second system information block in the CORESET.
  • the BS may transmit a second DCI for scheduling the first system information block on the second carrier in one of one or more PDCCH candidates associated with the first system information block in the CORESET in the case that the first DCI indicates that the second carrier carries the first system information block, and wherein the second DCI may include the first configuration.
  • the descriptions regarding the first and second DCIs in the forgoing embodiments may apply here.
  • the descriptions regarding the PDCCH candidates associated with the first and second system information blocks in the forgoing embodiments may apply here.
  • CRCs of the first DCI and the second DCI may be scrambled by different RNTIs.
  • FIG. 10 illustrates a block diagram of exemplary apparatus 1000 according to some embodiments of the present disclosure.
  • the apparatus 1000 may include at least one processor 1006 and at least one transceiver 1002 coupled to the processor 1006.
  • the apparatus 1000 may be a UE or a BS.
  • the transceiver 1002 may be divided into two devices, such as a receiving circuitry and a transmitting circuitry.
  • the apparatus 1000 may further include an input device, a memory, and/or other components.
  • the apparatus 1000 may be a UE.
  • the transceiver 1002 and the processor 1006 may interact with each other so as to perform the operations with respect to the UE described in FIGS. 1-9.
  • the apparatus 1000 may be a BS.
  • the transceiver 1002 and the processor 1006 may interact with each other so as to perform the operations with respect to the BS described in FIGS. 1-9.
  • the apparatus 1000 may further include at least one non-transitory computer-readable medium.
  • the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause the processor 1006 to implement the method with respect to the UE as described above.
  • the computer-executable instructions when executed, cause the processor 1006 interacting with transceiver 1002 to perform the operations with respect to the UE described in FIGS. 1-9.
  • the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause the processor 1006 to implement the method with respect to the BS as described above.
  • the computer-executable instructions when executed, cause the processor 1006 interacting with transceiver 1002 to perform the operations with respect to the BS described in FIGS. 1-9.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • the operations or steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the term “having” and the like, as used herein, are defined as "including.
  • Expressions such as “A and/or B” or “at least one of A and B” may include any and all combinations of words enumerated along with the expression.
  • the expression “A and/or B” or “at least one of A and B” may include A, B, or both A and B.
  • the wording "the first, " “the second” or the like is only used to clearly illustrate the embodiments of the present disclosure, but is not used to limit the substance of the present disclosure.

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés et des appareils pour améliorer la planification d'informations système. Selon certains modes de réalisation de la divulgation, un UE peut : recevoir, à une première position de domaine temporel, une première configuration pour un premier bloc d'informations système d'une première porteuse ; et recevoir un canal partagé de liaison descendante physique (PDSCH) transportant le premier bloc d'informations système à une seconde position de domaine temporel sur la base de la première configuration.
PCT/CN2023/080322 2023-03-08 2023-03-08 Procédé et appareil pour améliorer la planification d'informations système WO2024087455A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/080322 WO2024087455A1 (fr) 2023-03-08 2023-03-08 Procédé et appareil pour améliorer la planification d'informations système

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/080322 WO2024087455A1 (fr) 2023-03-08 2023-03-08 Procédé et appareil pour améliorer la planification d'informations système

Publications (1)

Publication Number Publication Date
WO2024087455A1 true WO2024087455A1 (fr) 2024-05-02

Family

ID=90829830

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/080322 WO2024087455A1 (fr) 2023-03-08 2023-03-08 Procédé et appareil pour améliorer la planification d'informations système

Country Status (1)

Country Link
WO (1) WO2024087455A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021207672A1 (fr) * 2020-04-10 2021-10-14 Qualcomm Incorporated Détermination de tci et de qcl pour des coreset dynamiques
CN113545144A (zh) * 2019-08-08 2021-10-22 Oppo广东移动通信有限公司 增强物理下行链路控制信道的传输和接收方法及装置
US20220141690A1 (en) * 2019-07-15 2022-05-05 Vivo Mobile Communication Co.,Ltd. Transmission method and communication device
WO2022127701A1 (fr) * 2020-12-17 2022-06-23 维沃移动通信有限公司 Procédé et appareil de transmission pdsch, et dispositif électronique

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220141690A1 (en) * 2019-07-15 2022-05-05 Vivo Mobile Communication Co.,Ltd. Transmission method and communication device
CN113545144A (zh) * 2019-08-08 2021-10-22 Oppo广东移动通信有限公司 增强物理下行链路控制信道的传输和接收方法及装置
WO2021207672A1 (fr) * 2020-04-10 2021-10-14 Qualcomm Incorporated Détermination de tci et de qcl pour des coreset dynamiques
WO2022127701A1 (fr) * 2020-12-17 2022-06-23 维沃移动通信有限公司 Procédé et appareil de transmission pdsch, et dispositif électronique

Similar Documents

Publication Publication Date Title
US11864088B2 (en) Method and apparatus for broadcasting synchronization signals and system information in a new type carrier
CN111742510B (zh) 无线通信系统中发送上行链路控制信息的方法及使用其的装置
EP2903334B1 (fr) Procédé et dispositif de transmission d'informations
CN113692059B (zh) 无线通信系统中的方法和设备
EP2941072B1 (fr) Procédé d'envoi et de réception d'informations système, station de base et équipement utilisateur
RU2536816C2 (ru) Обеспечение канала управления и сигнализация
KR101635864B1 (ko) 다중 반송파 시스템에서 제어채널을 모니터링하는 장치 및 방법
CN109600844B (zh) 确定时频资源的方法及装置
EP4236223A2 (fr) Systèmes et procédés pour système à structures physiques multiples
CN110741591A (zh) 在减少的延迟操作中用于下行链路控制物理结构的方法和设备
US20220256487A1 (en) Rate matching indication method and apparatus, and device and storage medium
US20220394601A1 (en) Method and apparatus for wireless communication
WO2024087455A1 (fr) Procédé et appareil pour améliorer la planification d'informations système
US20230413081A1 (en) Method and apparatus for enhanced physical downlink control channel (pdcch) monitoring on overlapping pdcch monitoring occasions
US20240015769A1 (en) Method and apparatus for multicast transmission
WO2022067641A1 (fr) Procédé et appareil pour l'ordonnancement et la transmission dans les sens montant et descendant
WO2024082502A1 (fr) Procédés et appareils de détermination d'ensemble de ressources de commande poinçonnées
WO2024082477A1 (fr) Procédés et appareils d'indication de ressource dans un scénario en duplex intégral sans chevauchement de sous-bandes
WO2023130461A1 (fr) Procédé et appareil de détermination de livre de codes harq-ack semi-statique pour multidiffusion
WO2023050448A1 (fr) Procédé et appareil pour détermination de taille de charge utile dci commune à un groupe
WO2023168700A1 (fr) Procédé et appareil de commutation d'état de précodage de transformée pour un pusch
WO2024020851A1 (fr) Procédé et appareil d'indication d'attribution de ressources de domaine temporel pour des pssch planifiés par une sci unique
US20230388092A1 (en) Method and apparatus for frequency domain resource allocation for downlink transmissions
WO2024000476A1 (fr) Procédé et appareil de transmission sur liaison latérale à base de groupes sur un spectre sans licence
WO2022056844A1 (fr) Procédé et appareil pour transmissions multiples programmées par un seul format dci