Physical downlink control channel (PDCCH) repetition for system information transmission in wireless networks

Abstract

Methods, systems, and computer-readable media are disclosed to perform operations including receiving a physical broadcast channel (PBCH) from a wireless network, the physical broadcast channel (PBCH) including a first indication of whether a physical downlink control channel (PDCCH) repetition is configured for system information block 1 (SIB1) signaling; receiving one or more PDCCHs from the wireless network based on the first indication, wherein the one or more PDCCHs include scheduling information for a physical downlink shared channel (PDSCH) carrying the SIB1; receiving a PDSCH carrying SIB1 from the wireless network based on the scheduling information; and at least one of configuring signaling for transmission to the wireless network according to SIB1, or receiving signaling from the wireless network according to SIB1.

Description

Background Technology

[0001] Wireless communication networks provide an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephone, data (e.g., voice, audio, and / or video data), messaging, and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user equipment using wireless network protocols, such as those described in various telecommunications standards issued by the 3rd Generation Partnership Project (3GPP). Example wireless communication networks include Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal Frequency Division Multiple Access (OFDMA) networks, Long Term Evolution (LTE), and 5G New Radio (5G NR). Wireless communication networks use technologies such as OFDM, Multiple-Input Multiple-Output (MIMO), Advanced Channel Decoding, Massive MIMO, beamforming, and / or other features to facilitate mobile broadband services. Summary of the Invention

[0002] According to one aspect of this disclosure, a method includes: receiving a physical broadcast channel (PBCH) from a wireless network, the PBCH including a first indication of whether a physical downlink control channel (PDCCH) repetition is configured for System Information Block 1 (SIB1) signaling; receiving one or more PDCCHs from the wireless network based on the first indication, wherein the one or more PDCCHs include scheduling information for a physical downlink shared channel (PDSCH) carrying SIB1; receiving the PDSCH carrying SIB1 from the wireless network based on the scheduling information; and at least one of the following: (i) configuring signaling for transmission to the wireless network according to the SIB1, or (ii) receiving signaling from the wireless network according to the SIB1.

[0003] Specific implementations of this aspect may include one or more of the following features.

[0004] In some specific implementations, the scheduling information may include a second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying SIB1 and a third indication of the search space (SS) for each of the one or more PDCCHs carrying SIB1.

[0005] In some implementations, the first indication can be signaled by a bit in the Master Information Block (MIB) of the PBCH.

[0006] In some implementations, the first indication can be signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0007] In some implementations, the first indication may be signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein these two bits additionally indicate the number of PDCCH repetitions used for SIB1 signaling.

[0008] In some implementations, the two bits may additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with PDCCH repetition, whether the Common Space Search (SS) is associated with PDCCH repetition, or at least one of the temporal or frequency relationships between PDCCH repetitions.

[0009] In some specific implementations, receiving one or more PDCCHs may include: determining that the PBCH indicates that the PDCCH is repeatedly not configured for SIB1; and receiving a single PDCCH based on a first indication, wherein the single PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0010] In some specific implementations, receiving one or more PDCCHs may include: determining that the PBCH indicates that the PDCCH is repeatedly configured for SIB1; and receiving at least a first PDCCH and a second PDCCH based on a first indication, wherein each of the first PDCCH and the second PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0011] In some specific implementations, the method may further include: determining that the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces; and determining the offset between the search spaces of the first PDCCH and the second PDCCH.

[0012] In some specific implementations, the offset can be a predetermined offset.

[0013] In some implementations, the offset can be configured by the wireless network.

[0014] In some specific implementations, the method may further include: determining that the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESET); and determining the offset between the CORESET of the first PDCCH and the second PDCCH.

[0015] In some specific implementations, the offset can be a predetermined offset.

[0016] In some implementations, the offset can be configured by the wireless network.

[0017] In some specific implementations, the method may also include determining a PDSCH quasi-co-location (QCL) assumption for at least one of the CORESETs that are the first PDCCH and the second PDCCH.

[0018] In some specific implementations, the method may also include determining the PDSCH quasi-co-location (QCL) assumption by performing at least one of the following: determining the same PDSCH QCL assumption as the higher frequency CORESET from the first PDCCH and the second PDCCH; or determining the same PDSCH QCL assumption as the lower frequency CORESET from the first PDCCH and the second PDCCH.

[0019] In some specific implementations, the method may further include: determining that the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESET); determining a first offset between the CORESET of the first PDCCH and the second PDCCH; and determining a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0020] In some specific implementations, the method may also include determining the PDSCH quasi-co-location (QCL) hypothesis based on at least one of the CORESETs of the first PDCCH and the second PDCCH.

[0021] In some specific implementations, the method may further include determining the PDSCH quasi-co-location (QCL) hypothesis by performing at least one of the following: determining the same PDSCH QCL hypothesis as the higher frequency CORESET from the first PDCCH and the second PDCCH; determining the same PDSCH QCL hypothesis as the lower frequency CORESET from the first PDCCH and the second PDCCH; determining the same PDSCH QCL hypothesis as the CORESET associated with a search space that is an earlier search space in the search spaces from the first PDCCH and the second PDCCH; or determining the same PDSCH QCL hypothesis as the CORESET associated with a search space that is a later search space in the search spaces from the first PDCCH and the second PDCCH.

[0022] In some specific implementations, the method may further include: receiving from the wireless network an additional indication as to whether the PDCCH repetition is configured to signal at least one of the following: SIB1 other than the SIB1, a random access channel (RACH), or a paging message; and receiving from the wireless network one or more additional PDCCHs based on the additional indication, wherein the one or more additional PDCCHs include scheduling information for an additional PDSCH carrying at least one of the following: SIB1 other than the SIB1, a RACH, or a paging message.

[0023] In some implementations, additional instructions may include explicit configuration of one or more additional search spaces for one or more additional PDCCHs.

[0024] In some implementations, one or more additional search spaces for one or more additional PDCCHs can be implicitly configured.

[0025] In some implementations, additional instructions may be signaled by at least one of the following: SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0026] In some specific implementations, this method is performed by the user equipment (UE).

[0027] In some implementations, this method may be executed by one or more baseband processors.

[0028] In another aspect, a method includes: generating a physical broadcast channel (PBCH) for transmission to a user equipment (UE), the PBCH including a first indication of whether a physical downlink control channel (PDCCH) repetition is configured for System Information Block 1 (SIB1) signaling; generating one or more PDCCHs for transmission to the UE according to the first indication, wherein the one or more PDCCHs include scheduling information for a physical downlink shared channel (PDSCH) carrying SIB1; generating a PDSCH carrying SIB1 for transmission to the UE according to the scheduling information; and at least one of the following: configuring signaling for transmission to the UE according to SIB1, or receiving signaling from the UE according to SIB1.

[0029] Specific implementations of this aspect may include one or more of the following features.

[0030] In some specific implementations, the scheduling information may include: a second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying SIB1; and a third indication of the search space (SS) for each of the one or more PDCCHs carrying SIB1.

[0031] In some implementations, the first indication can be signaled by a bit in the Master Information Block (MIB) of the PBCH.

[0032] In some implementations, the first indication can be signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0033] In some implementations, the first indication may be signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein these two bits additionally indicate the number of PDCCH repetitions used for SIB1 signaling.

[0034] In some implementations, the two bits may additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with PDCCH repetition, whether the Common Space Search (SS) is associated with PDCCH repetition, or at least one of the temporal or frequency relationships between PDCCH repetitions.

[0035] In some implementations, the PBCH may indicate that the PDCCH repeat is not configured for SIB1. Generating one or more PDCCHs for transmission may include generating a single PDCCH for transmission, wherein the single PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0036] In some specific implementations, the PBCH may indicate that the PDCCH is repeatedly configured for SIB1. Generating one or more PDCCHs for transmission may include generating at least a first PDCCH and a second PDCCH for transmission based on a first indication, wherein each of the first PDCCH and the second PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0037] In some specific implementations, the first PDCCH and the second PDCCH may have a common control resource set (CORESET) and different corresponding search spaces, and the method may also include configuring the offset between the search spaces of the first PDCCH and the second PDCCH.

[0038] In some specific implementations, the first PDCCH and the second PDCCH may have a common search space and different corresponding control resource sets (CORESET), and the method may also include configuring the offset between the CORESET of the first PDCCH and the second PDCCH.

[0039] In some specific implementations, the first PDCCH and the second PDCCH may have different corresponding search spaces and different corresponding control resource sets (CORESET), and the method may further include at least one of the following: configuring a first offset between the CORESET of the first PDCCH and the second PDCCH; or configuring a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0040] In some specific implementations, the method may further include: generating an additional indication of whether the PDCCH repeat is configured to signal at least one of the following for transmission to the UE: SIB1 other than the SIB1, the Random Access Channel (RACH), or a paging message; and generating one or more additional PDCCHs for transmission to the UE based on the additional indication, wherein the one or more additional PDCCHs include scheduling information for an additional PDSCH carrying at least one of the following: SIB1 other than the SIB1, the RACH, or a paging message.

[0041] In some implementations, additional instructions may include explicit configuration of one or more additional search spaces for one or more additional PDCCHs.

[0042] In some implementations, one or more additional search spaces for one or more additional PDCCHs can be implicitly configured.

[0043] In some implementations, additional instructions may be signaled by at least one of the following: SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0044] In some specific implementations, this method can be executed by the base station.

[0045] In some implementations, this method may be executed by one or more baseband processors.

[0046] In another aspect, a system includes one or more computers and one or more storage devices having instructions stored thereon that, when executed by the one or more computers, are operable to cause the one or more computers to perform any of the methods or operations described herein.

[0047] On the other hand, a non-transitory computer storage medium is encoded with instructions that, when executed by one or more computers, cause those computers to perform any of the methods or operations described herein.

[0048] In another aspect, an apparatus includes processing circuitry configured to perform any of the methods or operations described herein.

[0049] On the other hand, one or more baseband processors are configured to perform any of the methods or operations described herein.

[0050] Details of one or more embodiments of these systems and methods are set forth in the following figures and description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, figures, and claims. Attached Figure Description

[0051] Figure 1 Examples of wireless networks based on some specific implementations are shown.

[0052] Figure 2 An example control channel element (CCE) is shown for two search space sets of a pair of links for the physical downlink control channel (PDCCH).

[0053] Figure 3 An example procedure for sending system information (such as System Information Block 1 (SIB1)) from the network to the User Equipment (UE) is shown.

[0054] Figure 4 An example of a linked PDCCH according to one implementation scheme is shown.

[0055] Figure 5 An example of a linked PDCCH according to another implementation is shown.

[0056] Figure 6 An example of a linked PDCCH according to another implementation is shown.

[0057] Figure 7 An example procedure for sending additional system information from the network to the user equipment (UE) is shown.

[0058] Figure 8A The flowchart illustrates example methods based on some specific implementations.

[0059] Figure 8B A flowchart illustrating another example method based on some specific implementations is shown.

[0060] Figure 9 Example UEs based on some specific implementations are shown.

[0061] Figure 10 Example access nodes are shown according to some specific implementations. Detailed Implementation

[0062] Typically, the Physical Downlink Control Channel (PDCCH) is used to schedule the transmission of system information in a wireless network (such as a terrestrial network (TN) and / or a non-terrestrial network (NTN) (e.g., a network with one or more orbiting satellites). As an example, a network (e.g., via a base station, gNodeB (gNB), etc.) can configure a User Equipment (UE) to monitor one or more PDCCHs that include scheduling information for transmitting system information (e.g., System Information Block 1, SIB1) carried in one or more Physical Downlink Shared Channels (PDSCHs). Based on the scheduling information, the UE monitors the scheduled PDSCHs, obtains the system information contained therein, and exchanges data with the wireless network according to the system information.

[0063] In some implementations, the wireless network and the UE can be configured to support the use of PDCCH repetition to transmit system information. This can be beneficial, for example, in improving the reliability of communication between the wireless network and the UE (e.g., improving the reliability of the UE obtaining system information from the wireless network compared to a scenario where only a single PDCCH is used to provide scheduling information to the UE). For example, the wireless network can be configured to send multiple PDCCHs to the UE, where each of these PDCCHs includes a corresponding instance of scheduling information for a specific PDSCH carrying SIB1 and / or other system information. Based on the scheduling information, the UE can monitor the scheduled PDSCH and obtain SIB1 and / or other system information included therein.

[0064] Figure 1 A wireless network 100 according to some specific implementation is illustrated. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing the UE 102's access to the network via the base station 104.

[0065] In some implementations, Wireless Network 100 may be a non-standalone (NSA) network combining Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. For example, Wireless Network 100 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. In some other implementations, Wireless Network 100 may be a standalone (SA) network combining only 5G NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)), IEEE 802.11 technologies (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc. While this document may use terminology commonly associated with 5G NR to describe the aspects, the aspects of this disclosure can be applied to other systems, such as 3G, 4G, and / or systems beyond 5G (e.g., 6G).

[0066] In wireless network 100, UE 102 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, machine-type device (such as a smart meter or dedicated device for healthcare), intelligent transportation system, or any other wireless device. In network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via air interface 108 within the base station service area provided by base station 104. In some implementations, this wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area can be divided into several sectors associated with one or more specific antennas. Such sectors can be physically associated with one or more fixed antennas, or can be assigned to physical areas with one or more tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a specific sector.

[0067] UE 102 includes control circuitry 110 coupled to transmitting circuitry 112 and receiving circuitry 114. Transmitting circuitry 112 and receiving circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmitting circuitry 112 and receiving circuitry 114 may be adapted to transmit and receive data respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0068] In various specific implementations, aspects of the transmitting circuit 112, receiving circuit 114, and control circuit 110 may be integrated in various ways to implement the operations described herein. Control circuit 110 may be adapted to or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. For example, control circuit 110 may be configured to obtain system information (e.g., SIB1 and / or other system information) using scheduling information repeatedly received from the network via the PDCCH.

[0069] Transmitting circuit 112 can perform the various operations described in this specification. Additionally, transmitting circuit 112 can transmit using multiple multiplexed uplink physical channels. These multiple uplink physical channels can be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. Transmitting circuit 112 can be configured to receive block data from control circuit 110 for transmission across air interface 108.

[0070] Receiver circuit 114 can perform the various operations described in this specification. Additionally, receiver circuit 114 can receive multiple multiplexed downlink physical channels from air interface 108 and relay these physical channels to control circuit 110. These multiple downlink physical channels can be multiplexed, for example, according to TDM or FDM and carrier aggregation. Transmitter circuit 112 and receiver circuit 114 can respectively transmit and receive structured control data and content data (e.g., messages, images, video, etc.) within data blocks carried by the physical channels.

[0071] Figure 1 Base station 104 is also illustrated. In some implementations, base station 104 may be a 5G radio access network (RAN), a next-generation RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN (such as UTRAN). As used herein, the term "5GRAN" and the like may refer to base station 104 operating in an NR or 5G wireless network 100, and the term "E-UTRAN" and the like may refer to base station 104 operating in an LTE or 4G wireless network 100. UE 102 utilizes connections (or channels) 106A and 106B, each connection including a physical communication interface or layer.

[0072] The base station 104 circuitry may include control circuitry 116 coupled to transmitting circuitry 118 and receiving circuitry 120. Transmitting circuitry 118 and receiving circuitry 120 may each be coupled to one or more antennas, which may be used for communication via air interface 108. Transmitting circuitry 118 and receiving circuitry 120 may be adapted to transmit and receive data to and from any UE connected to base station 104, respectively. Receiving circuitry 120 may receive multiple uplink physical channels from one or more UEs, including UE 102.

[0073] exist Figure 1 In this implementation, one or more channels 106A, 106B are exemplified as air interfaces for communication coupling and may conform to cellular communication protocols such as UMTS, 3GPP LTE, LTE-A, LTE-U (LTE-U), 5G, NR, NR-U, and / or any other communication protocols. In a specific implementation, UE 102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0074] Typically, the PDCCH is used to schedule the transmission of system information in wireless networks (such as cellular networks over TN and / or NTN). For example, see [reference]. Figure 1 The wireless network 100 (e.g., via base station 104) can configure the UE 102 to monitor one or more PDCCHs, which include scheduling information for transmitting system information (e.g., SIB1) carried in one or more PDSCHs. Based on the scheduling information, the UE 102 monitors the scheduled PDSCHs, obtains the system information included therein, and exchanges data with the base station 104 according to the system information.

[0075] In some specific implementations, base station 104 and UE 102 may be configured to support the use of PDCCH repetition to transmit system information. This can be beneficial, for example, in improving the reliability of communication between base station 104 and UE 102 (e.g., improving the reliability of UE 102 obtaining system information from base station 104 compared to a scenario where only a single PDCCH is used to provide scheduling information to UE 102). This may be particularly beneficial in the context of NTN, where base station 104 (e.g., an orbiting satellite) is power-constrained and has limited transmit power capabilities (e.g., compared to terrestrial base stations).

[0076] For example, base station 104 can be configured to send multiple PDCCHs to UE 102, wherein each of these PDCCHs includes a corresponding instance of scheduling information for a specific PDSCH carrying SIB1 and / or other system information. Based on the scheduling information, UE 102 can monitor the scheduled PDSCHs and obtain SIB1 and / or other system information included therein.

[0077] Typically, PDCCH provides scheduling information based on different types or formats, depending on the specific implementation.

[0078] As an example, the PDCCH can be a set of type 0PDCCH CSS (common search space) (e.g., DCI format 1_0 with cyclic redundancy check (CRC) scrambled by the System Information Radio Network Temporary Identifier (SI-RNTI)). The Master Information Block (MIB) may include pdcch-ConfigSIB1, which includes controlResourceSetZero and searchSpaceZero. Furthermore, SIB1 may include PDCCH-ConfigCommon, which includes searchSpaceSIB1 and searchSpaceZero.

[0079] As another example, PDCCH can be a type 0A PDCCH CSS set (e.g., a DCI format 1_0 with a CRC scrambled by SI-RNTI). SIB1 may include PDCCH-ConfigCommon, which includes SearchSpaceOtherSystemInformation.

[0080] Furthermore, a pair of PDCCHs (e.g., two repeating PDCCHs) can be transmitted from two linked search space (SS) sets using Time Division Multiplexing (TDM) and / or Frequency Division Multiplexing (FDM). The link between the two SS sets can be configured by the network, for example, via Radio Resource Control (RRC). Additionally, the SS sets of the two links can be associated with the same or different control resource sets (CORESETs). For example, a pair of PDCCHs can share the same SS set (e.g., transmitted at the same time) or have different corresponding SS sets (e.g., transmitted at different corresponding times). Furthermore, the pair of PDCCHs can share the same CORESET (e.g., transmitted using the same one or more frequencies) or have different corresponding CORESETs (e.g., transmitted using different corresponding frequencies).

[0081] Furthermore, a pair of PDCCH candidates in the two SS sets have the same aggregation level (AL) and the same PDCCH candidate index. For example, Figure 2Control channel elements (CCEs) for two SS sets, “SS1” (202a) and “SS2” (202b), each with an AL of 4, are shown. In this example, the CCEs comprise pairs of four distinct links to PDCCH candidates (e.g., each PDCCH candidate spans four corresponding CCEs).

[0082] As described above, base station 104 and UE 102 can be configured to support the use of PDCCH repetition to transmit system information.

[0083] Figure 3 An example procedure 300 for transmitting system information (e.g., SIB1) from a network (e.g., via a base station) to a UE is shown. As an example, procedure 300 may at least partially utilize reference [reference / ... Figure 1 The base station 104 and UE 102 described herein shall be used to perform this action.

[0084] According to procedure 300, the network (e.g., via base station 102) transmits a Physical Broadcast Channel (PBCH) (302) indicating the PDCCH repetition configuration for SIB1 signaling. As an example, the PBCH may indicate whether PDCCH repetition is configured (e.g., whether multiple PDCCHs are scheduled for transmission to UE 102, where each PDCCH includes scheduling information for a PDSCH carrying SIB1). Furthermore, if PDCCH repetition is configured, the PBCH may also indicate the number of configured PDCCH repetitions (e.g., two, four, eight, sixteen, or any other number of PDCCH repetitions). Additionally, if PDCCH repetition is configured, the PBCH may also indicate the time and / or frequency relationships between PDCCH repetitions.

[0085] Furthermore, the network (e.g., via base station 102) sends one or more PDCCHs (304) to UE 102 according to the PDCCH repetition configuration. For example, if PDCCH repetition is configured, base station 104 may send two or more PDCCHs to UE 102, where each PDCCH includes a corresponding instance of scheduling information for a PDSCH carrying SIB1. As another example, if PDCCH repetition is not configured, base station 104 may send a single PDCCH to UE 102, where the PDCCH includes scheduling information for a PDSCH carrying SIB1. UE 102 obtains the scheduling information from the PDCCHs and monitors the transmission of the scheduled PDSCHs.

[0086] The network (e.g., via base station 102) sends a PDSCH carrying SIB1 to UE 102 according to scheduling information (306). UE 102 monitors the scheduled PDSCH and determines the SIB1 carried in the scheduled PDSCH (308).

[0087] Furthermore, UE 102 and the network exchange data with each other based on SIB1 (310). As an example, SIB1 may include information that allows UE 102 to determine whether to grant it access to a specific cell of the network. Additionally, SIB1 may include scheduling information for other System Information Blocks (SIBs) and / or RRC information, such as time and / or constants, for sending data to and / or receiving data from the network. Based on the information included in SIB1, UE 102 may encode data and send it to the network and / or receive data from and decode it.

[0088] As described above, the network (e.g., via base station 104) can signal to UE 102 to reconfigure the PDCCH for SIB1 signaling. Various signaling techniques can be used.

[0089] For example, in a legacy system, the MIB (e.g., sent to UE 102 in the PBCH) can be configured to include a "spare" bit that is not used for any signaling. An example syntax for a legacy MIB is shown below:

[0090] This spare bit can be used to indicate whether PDCCH repeat is configured for SIB1 transmission. For example, a value of 0 can signal or imply that PDCCH repeat is not configured, while a value of 1 can signal or imply that PDCCH repeat is configured. In addition, legacy UEs can assume that PDCCH repeat is not configured (e.g., because legacy UEs can be configured to suppress reading the spare bit in the MIB).

[0091] As another example, the physical layer (PHY) payload of the PBCH can be used to signal the PDCCH to repeat the configuration.

[0092] For example, in a conventional FR1-NTN system, the PHY payload of the PBCH can be configured to include "reserved" bits that are not used for any signaling. and in It is the i-th bit in the PBCH payload and It is the payload size of the transport block delivered to Layer 1.

[0093] In some specific implementations, only one of these reserved bits may be used to indicate that the PDCCH configuration is repeated. For example, This can indicate that no PDCCH duplication is configured for SIB1 transmission, while This indicates that PDCCH repetition is configured for SIB1 transmission. In this example, the bit... It can be kept as a reserved bit.

[0094] In some implementations, two of these reserved bits can be used to indicate that the PDCCH configuration is repeated. For example, It can be used to indicate the number of PDCCH repetitions. As an example, (0,0) can indicate a repetition count of 1 (no repetition), (0,1) can indicate a PDCCH repetition count of 2, (1,0) can indicate a repetition count of 4, and (1,1) can indicate a repetition count of 8.

[0095] In some specific implementations, This can be used to indicate the CORESET and search space associated with the PDCCH (e.g., CORESET#0 and search space #0). As an example, (0,0) can indicate no PDCCH repetition. Furthermore, (0,1) can indicate that two CORESET#0s (e.g., CORESET#0 and CORESET#0A) are configured with a predefined frequency gap and a common SS set between them. Additionally, (1,0) can indicate that a single CORESET#0 is configured with two linked SS sets (e.g., SS#0 and SS#0A). Furthermore, (1,1) can indicate that two CORESET#0s (e.g., CORESET#0 and CORESET#0A) are configured with separate SS sets.

[0096] As another example, (0,0) can indicate no PDCCH repetition. Furthermore, (0,1) can indicate a single CORESET#0 of a search space set with two links, where the gap is one time slot. Additionally, (1,0) can indicate a single CORESET#0 of an SS set with two links, where the gap is three symbols in the same time slot.

[0097] In some specific implementations, both the spare bit in the MIB and the PHY payload of the PBCH can be used to indicate the PDCCH reconfiguration for SIB1 signaling.

[0098] As described above, a pair of linked PDCCHs (e.g., two PDCCH repetitions for the same scheduling information of a PDSCH carrying SIB1) may share the same SS set (e.g., transmitted at the same time) or have different corresponding SS sets (e.g., transmitted at different corresponding times). Furthermore, the pair of linked PDCCHs may share the same CORESET (e.g., transmitted using the same one or more frequencies) or have different corresponding CORESETs (e.g., transmitted using different corresponding frequencies).

[0099] As an example, Figure 4The first case is illustrated, where a pair of linked PDCCHs have the same CORESET (e.g., CORESET#0) but different corresponding SS sets (e.g., SS#0 and SS#0C). This is referred to as a PDCCH with a common CORESET that has two linked SS sets. In this example, the two linked SS sets have the same PDCCH monitoring periodicity but different corresponding PDCCH monitoring offsets (e.g., in two consecutive time slots or in consecutive symbols within the same time slot).

[0100] In some specific implementations, the first SS set (e.g., SS#0) may follow existing pre-configurations and instructions via MIB (e.g., MIB / pdcch-ConfigSIB1 / searchSpaceZero).

[0101] Furthermore, the second SS set (e.g., SS#0C) may have most of the same settings as the first SS set (e.g., SS#0). However, different settings may be used for PDCCH monitoring timing (e.g., the offset values ​​in the parameters monitoringSlotPeriodicityAndOffset and / or monitoringSymbols withSlot).

[0102] In some implementations, the temporal relationship between two SS sets can be predefined and fixed. For example, SS sets can be separated by a predetermined number (e.g., one) of time slots. As another example, SS sets can be separated within the same time slot by a predetermined number (e.g., three) of symbols.

[0103] In some implementations, several options for time relationships can be pre-configured, and one of these options can be selected based on a PBCH indication (e.g., using a multi-bit indication, as described above).

[0104] In some implementations, the first SS set (e.g., SS#0) may appear before the second SS set (e.g., SS#0C). In some implementations, the first SS set (e.g., SS#0) may appear after the second SS set (e.g., SS#0C).

[0105] As another example, Figure 5The second case is illustrated, where a pair of linked PDCCH 502a and PDCCH 502b have different corresponding FDM-separated CORESETs (e.g., CORESET#0 and CORESET#0A) but share the same SS set (e.g., SS#0). This is referred to as a PDCCH with two linked CORESETs and a common SS set. In this example, the two linked CORESETs have the same settings relative to the demodulation reference signal (DMRS) scrambling sequence initialization, the number of consecutive symbols, the number of resource blocks (RBs), the CCE to research element group (REG) mapping, the transmit configuration indicator (TCI) status, tci-PresentInDCI, etc. Furthermore, the first CORESET (e.g., CORESET#0) may follow existing pre-configurations and indications via the MIB (e.g., MIB / pdcch-ConfigSIB1 / controlResourceSetZero).

[0106] In some specific implementations, the second CORESET (e.g., CORESET#0A) may have largely the same settings as the first CORESET (e.g., CORESET#0). However, different sets of RBs may be used for each.

[0107] In some specific implementations, the frequency positional relationship between two CORESETs can be predetermined and fixed. For example, CORESETs can be separated from each other by a predetermined number of RBs (e.g., one RB).

[0108] In some implementations, several options for frequency relationships can be pre-configured, and one of these options can be selected based on a PBCH indication (e.g., using a multi-bit indication, as described above).

[0109] Typically, each CORESET can be configured with a configured TCI state (e.g., a specific beam orientation). In some implementations, if the Downlink Control Information (DCI) does not explicitly indicate the PDSCH TCI state, it can be assumed that the PDSCH beam (TCI state) is the same as the CORESET beam (TCI state). In this case, it can be assumed that the PDSCH performs QCL with the PDCCH in the CORESET. In some implementations, if the TCI field is not present in the Downlink Control Information (DCI) and the scheduling offset is equal to or greater than timeDurationForQCL, the PDSCH quasi-co-location (QCL) assumption can be determined based on the first CORESET (e.g., CORESET#0), the second CORESET (e.g., CORESET#0A), and / or the PDSCH candidates at lower (or higher) frequencies.

[0110] As another example, Figure 6 A third case is illustrated, in which a pair of linked PDCCHs 602a and 602b have different corresponding CORESETs (e.g., CORESET#0 and CORESET#0A) and different corresponding SS sets (e.g., SS#0 and SS#0C). This is referred to as a PDCCH with two linked CORESETs and two linked SS sets. Here, the first SS set (e.g., SS#0) is associated with the first CORESET (e.g., CORESET#0), and the second SS set (e.g., SS#0C) is associated with the second CORESET (e.g., CORESET#0A).

[0111] The first CORESET (e.g., CORESET#0) and the second SS set (e.g., SS#0) may follow existing pre-configurations and instructions via MIBs (e.g., MIB / pdcch-ConfigSIB1 / searchSpaceZero and MIB / pdcch-ConfigSIB1 / controlResourceSetZero, respectively).

[0112] For reference Figure 5 The second scenario described determines the configuration of the second CORESET (e.g., CORESET#0A). Furthermore, references can be made to... Figure 4 The first use case described determines the configuration of the first SS set (e.g., SS#0C).

[0113] Furthermore, the DCI 1_0 field of the Time Domain Resource Assignment (TDRA) can be interpreted differently depending on the specific implementation.

[0114] For example, in some implementations, the indicated K0 value can be determined based on a later SS set, making sufficient processing time available.

[0115] As another example, multiple copies of the PDSCH carrying SIB1 can be sent (e.g., one PDSCH for a legacy UE and one PDSCH for a UE configured for repeated PDCCH reception).

[0116] As another example, two SS sets can always be configured in the same time slot.

[0117] In some specific implementations, if the TCI field is not present in the downlink control information (DCI) and the scheduling offset is equal to or greater than timeDurationForQCL, the PDSCH quasi-co-location (QCL) assumption can be determined based on the first CORESET (e.g., CORESET#0), the second CORESET (e.g., CORESET#0A), PDSCH candidates at lower (or higher) frequencies, and / or PDSCH candidates with later (or earlier) monitoring timing.

[0118] In some specific implementations, PDCCH repetition can also be used to signal scheduling information for PDSCHs carrying additional information beyond SIB1. For example, PDCCH repetition can also be used to signal scheduling information for PDSCHs carrying other SIBs, random access channels (RACH), and / or paging messages.

[0119] In some implementations, SIB1 can be used to explicitly configure additional search spaces for other SIBs, RACHs, and paging PDCCHs (e.g., via SIB1 / PDCCH-ConfigCommon). For example, the total number of common search spaces can be expanded from 4 to 8. As an example:

[0120] PDCCH-ConfigCommon::=SEQUENCE{

[0121] commonSearchSpaceList SEQUENCE(SIZE(1..8))OF SearchSpace

[0122] In addition, searchSpaceOtherSystemInformation, pagingSearchSpace, and ra-SearchSpace can have a list of searchSpaceId (e.g., a list of two), where the two corresponding search spaces have the same searchspacelinkingId value.

[0123] In addition, searchSpaceSIB1 may also have a list of searchSpaceId (e.g., a list of two), where the two corresponding search spaces have the same searchspacelinkingId value.

[0124] In some implementations, additional search spaces for other SIBs, RACHs, and paging PDCCHs can be implicitly configured.

[0125] For example, the relationship between the additional search space and the search space configured in PDCCH-ConfigCommon can be predefined or preconfigured (e.g., the start symbol position in monitoringSymbolsWithinSlot of the additional search space can be predefined or preconfigured).

[0126] In addition, the PHY payload of SIB1, MIB and / or PBCH may indicate the repetition of PDCCH for SIB1, other SIBs, RA and paging (e.g. as described above).

[0127] For example, Figure 7 An example procedure 700 is shown for sending additional system information (e.g., other SIBs, RACH, paging messages, etc.) from a network (e.g., via a base station) to a UE. This is for example and for reference only. Figure 3 The described process 300 is an alternative or supplement to process 700, which may at least partially utilize the reference. Figure 1 The base station 104 and UE 102 described herein shall be used to perform this action.

[0128] According to procedure 700, the network (e.g., via base station 102) sends SIB1 with PDCCH-configCommon to support PDCCH repetition for other SIBs, RACH, paging messages, etc. (702). As an example, procedure 300 can be used to obtain SIB1 (e.g., by obtaining SIB1 from a PDSCH scheduled by one or more PDCCHs).

[0129] Furthermore, the network (e.g., via base station 102) sends one or more PDCCHs (704) to UE 102 according to SIB1. For example, if PDCCH repetition is configured for other types of system information, base station 104 may send two or more PDCCHs to UE 102, where each PDCCH includes a corresponding instance of scheduling information for a PDSCH carrying other system information. As another example, if PDCCH repetition is not configured, base station 104 may send a single PDCCH to UE 102, where the PDCCH includes scheduling information for a PDSCH carrying other system information. UE 102 obtains the scheduling information from the PDCCHs and monitors the transmission of the scheduled PDSCHs.

[0130] The network (e.g., via base station 102) sends a PDSCH (706) to UE 102 carrying other system information (e.g., other SIBs, RACH, paging messages, etc.) according to scheduling information. UE 102 monitors the scheduled PDSCH and determines the other system information carried in the scheduled PDSCH (708).

[0131] Figure 8A A flowchart illustrating an example method 800 according to some specific implementation is provided. For clarity, the following description generally describes method 800 within the context of the other figures in this specification. For example, method 800 may be derived from… Figure 1 The method is executed by UE 102. It should be understood that method 800 may be executed, for example, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware. In some specific implementations, the steps of method 800 may run in parallel, in combination, in a loop, or in any order.

[0132] According to method 800, the system receives a physical broadcast channel (PBCH) from a wireless network, the physical broadcast channel (PBCH) including a first indication of whether the physical downlink control channel (PDCCH) repetition is configured for system information block 1 (SIB1) signaling; (802).

[0133] In some implementations, the first indication can be signaled by a bit in the Master Information Block (MIB) of the PBCH.

[0134] In some implementations, the first indication can be signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0135] In some implementations, the initial indication can be signaled by two bits in the physical layer (PHY) payload of the PBCH. Additionally, these two bits also indicate the number of PDCCH repetitions used for SIB1 signaling.

[0136] In some implementations, the two bits may additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with PDCCH repetition, whether the Common Space Search (SS) is associated with PDCCH repetition, or at least one of the temporal or frequency relationships between PDCCH repetitions.

[0137] The system receives one or more PDCCHs (804) from the wireless network based on a first indication. The one or more PDCCHs include scheduling information for the Physical Downlink Shared Channel (PDSCH) carrying SIB1.

[0138] In some specific implementations, the scheduling information may include a second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying SIB1. Furthermore, the scheduling information may include a third indication of the search space (SS) for each of the one or more PDCCHs carrying SIB1.

[0139] In some implementations, receiving one or more PDCCHs may include determining that a PBCH indicating that a PDCCH has been repeatedly not configured for SIB1, and receiving a single PDCCH based on that first indication. The single PDCCH may carry scheduling information for a PDSCH carrying SIB1.

[0140] In some implementations, receiving one or more PDCCHs may include determining that a PBCH indicating that a PDCCH is repeatedly configured for SIB1, and receiving at least a first PDCCH and a second PDCCH based on that first indication. Each of the first PDCCH and the second PDCCH may carry scheduling information for a PDSCH carrying SIB1.

[0141] The system receives PDSCH(806) carrying SIB1 from the wireless network based on scheduling information.

[0142] The system performs at least one of the following: (i) configuring signaling according to SIB1 for transmission to the wireless network; or (ii) receiving signaling from the wireless network according to SIB1 (808).

[0143] In some implementations, method 800 may further include determining that the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces, and determining an offset between the search spaces of the first PDCCH and the second PDCCH. In some implementations, the offset may be a predetermined offset. In some implementations, the offset may be configured by the wireless network.

[0144] In some implementations, method 800 may further include determining that the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESETs), and determining an offset between the CORESETs of the first PDCCH and the second PDCCH. In some implementations, the offset may be a predetermined offset. In some implementations, the offset may be configured by the wireless network.

[0145] In some specific implementations, method 800 may also include determining the PDSCH quasi-co-location (QCL) assumption for at least one of the CORESETs that are the first PDCCH and the second PDCCH.

[0146] In some specific implementations, method 800 may further include determining the PDSCH quasi-co-location (QCL) assumption by performing at least one of the following: determining the same PDSCH QCL assumption as the higher frequency CORESET from the first PDCCH and the second PDCCH; or determining the same PDSCH QCL assumption as the lower frequency CORESET from the first PDCCH and the second PDCCH.

[0147] In some specific implementations, method 800 may further include: determining that the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESET); determining a first offset between the CORESET of the first PDCCH and the second PDCCH; and determining a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0148] In some specific implementations, method 800 may also include determining the PDSCH quasi-co-location (QCL) hypothesis based on at least one of the CORESETs of the first PDCCH and the second PDCCH.

[0149] In some specific implementations, method 800 may further include determining the PDSCH quasi-co-location (QCL) hypothesis by performing at least one of the following: determining the same PDSCH QCL hypothesis as the higher frequency CORESET from the first PDCCH and the second PDCCH; determining the same PDSCH QCL hypothesis as the lower frequency CORESET from the first PDCCH and the second PDCCH; determining the same PDSCH QCL hypothesis as the CORESET associated with a search space that is an earlier search space in the search spaces from the first PDCCH and the second PDCCH; or determining the same PDSCH QCL hypothesis as the CORESET associated with a search space that is a later search space in the search spaces from the first PDCCH and the second PDCCH.

[0150] In some implementations, method 800 may further include: receiving from the wireless network an additional indication as to whether the PDCCH is repeatedly configured to signal at least one of the following: an SIB1 other than the SIB1, a random access channel (RACH), or a paging message; and receiving one or more additional PDCCHs from the wireless network based on the additional indication. The one or more additional PDCCHs may include scheduling information for an additional PDSCH carrying at least one of the following: an SIB1 other than the SIB1, a RACH, or a paging message.

[0151] In some implementations, additional instructions may include explicit configuration of one or more additional search spaces for one or more additional PDCCHs.

[0152] In some implementations, one or more additional search spaces for one or more additional PDCCHs can be implicitly configured.

[0153] In some implementations, additional instructions may be signaled by at least one of the following: SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0154] In some specific implementations, method 800 may be performed at least in part by the user equipment (UE).

[0155] In some implementations, the method may be executed at least in part by one or more baseband processors.

[0156] Figure 8B A flowchart illustrating an example method 820 according to some specific implementation is provided. For clarity, the following description generally describes method 820 within the context of the other figures in this specification. For example, method 820 may be derived from… Figure 1 The method is executed by base station 104. It should be understood that method 820 may be executed, for example, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware. In some specific implementations, the steps of method 800 may run in parallel, in combination, in cycles, or in any order.

[0157] According to method 820, the system generates a physical broadcast channel (PBCH) for transmission to user equipment (UE), the physical broadcast channel (PBCH) including a first indication (822) of whether the physical downlink control channel (PDCCH) repeat is configured for system information block 1 (SIB1) signaling.

[0158] In some implementations, the first indication can be signaled by a bit in the Master Information Block (MIB) of the PBCH.

[0159] In some implementations, the first indication can be signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0160] In some implementations, the initial indication can be signaled by two bits in the physical layer (PHY) payload of the PBCH. These two bits may additionally indicate the number of PDCCH repetitions used for SIB1 signaling.

[0161] In some implementations, the two bits may additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with PDCCH repetition, whether the Common Space Search (SS) is associated with PDCCH repetition, or at least one of the temporal or frequency relationships between PDCCH repetitions.

[0162] The system generates one or more PDCCHs according to the first instruction for transmission to the UE (824). The one or more PDCCHs include scheduling information (824) for the Physical Downlink Shared Channel (PDSCH) carrying SIB1.

[0163] In some specific implementations, the scheduling information may include a second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying SIB1. Furthermore, the scheduling information may include a third indication of the search space (SS) for each of the one or more PDCCHs carrying SIB1.

[0164] In some implementations, the PBCH may indicate that the PDCCH repeat is not configured for SIB1. Generating one or more PDCCHs for transmission may include generating a single PDCCH for transmission, wherein the single PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0165] In some specific implementations, the PBCH may indicate that the PDCCH is repeatedly configured for SIB1. Generating one or more PDCCHs for transmission may include generating at least a first PDCCH and a second PDCCH for transmission based on a first indication, wherein each of the first PDCCH and the second PDCCH carries scheduling information for the PDSCH carrying SIB1.

[0166] The system generates a PDSCH carrying SIB1 based on the scheduling information for transmission to the UE (826).

[0167] The system performs at least one of the following: (i) configuring signaling according to SIB1 for transmission to the UE; or (ii) receiving signaling from the UE according to the SIB1 (828).

[0168] In some specific implementations, the first PDCCH and the second PDCCH may have a common control resource set (CORESET) and different corresponding search spaces. Furthermore, the system can configure the offset between the search spaces of the first PDCCH and the second PDCCH.

[0169] In some specific implementations, the first PDCCH and the second PDCCH may have a common search space and different corresponding control resource sets (CORESET). In addition, the system can configure the offset between the CORESET of the first PDCCH and the second PDCCH.

[0170] In some specific implementations, the first PDCCH and the second PDCCH may have different corresponding search spaces and different corresponding control resource sets (CORESET). In addition, the system may perform at least one of the following: (ii) configuring a first offset between the CORESETs of the first PDCCH and the second PDCCH; or (ii) configuring a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0171] In some implementations, method 820 may further include: generating an additional indication of whether the PDCCH repetition is configured to signal at least one of the following for transmission to the UE: an SIB1 other than the SIB1, a random access channel (RACH), or a paging message. Furthermore, method 820 may include generating one or more additional PDCCHs for transmission to the UE based on the additional indication. The one or more additional PDCCHs may include scheduling information for an additional PDSCH carrying at least one of the following: an SIB1 other than the SIB1, a RACH, or a paging message.

[0172] In some implementations, additional instructions may include explicit configuration of one or more additional search spaces for one or more additional PDCCHs.

[0173] In some implementations, one or more additional search spaces for one or more additional PDCCHs can be implicitly configured.

[0174] In some implementations, additional instructions may be signaled by at least one of the following: SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0175] In some implementations, method 820 may be performed at least in part by the base station.

[0176] In some implementations, method 820 may be executed at least in part by one or more baseband processors.

[0177] Figure 8A and Figure 8B The example methods 800 and 820 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 8A and Figure 8B (Not shown in the image), these steps can be performed in the order shown or in a different order.

[0178] Figure 9 Example UE 900 is illustrated according to some specific implementations. UE 900 may be similar to Figure 1 The UE 102 is essentially interchangeable with it.

[0179] UE 900 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, pressure sensors, thermometers, motion sensors, accelerometers, stock sensors, voltmeters / ammeters, etc.), video devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0180] UE 900 may include a processor 902, RF interface circuitry 904, memory / storage device 906, user interface 908, sensor 910, drive circuitry 912, power management integrated circuit (PMIC) 914, one or more antennas 916, and battery 918. The components of UE 900 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 9 The block diagram is intended to show a simplified view of some of the components of the UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0181] The components of UE 900 can be coupled to various other components via one or more interconnects 920, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0182] Processor 902 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 922A, central processing unit circuitry (CPU) 922B, and graphics processing unit circuitry (GPU) 922C. Processor 902 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 906) to cause UE 900 to perform the operations described herein.

[0183] In some implementations, the baseband processor circuit 922A can access the communication protocol stack 924 in the memory / storage device 906 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuit 922A can access the communication protocol stack to perform user plane functions at the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Serving Data Adaptation Protocol (SDAP) layer, and PDU layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access strata. In some implementations, PHY layer operations may be additionally / optionally performed by components of the RF interface circuit 904. The baseband processor circuit 922A can generate or process baseband signals or waveforms carrying information in a 3GPP-compatible network. In some specific implementations, the waveform used for NR can be based on Cyclic Prefix Orthogonal Frequency Division Multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and Discrete Fourier Transform Extended OFDM "DFT-S-OFDM" in the uplink.

[0184] Memory / storage device 906 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 924) that can be executed by one or more processors in processor 902 to cause UE 900 to perform the various operations described herein. Memory / storage device 906 includes any type of volatile or non-volatile memory that can be distributed throughout UE 900. In some specific embodiments, some memory / storage devices 906 may be located on processor 902 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 906 may be located external to processor 902 but accessible via a memory interface. Memory / storage device 906 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0185] The RF interface circuitry 904 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 900 to communicate with other devices via a radio access network. The RF interface circuitry 904 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0186] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 916 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 902.

[0187] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal via a power amplifier before it is radiated across the air interface via antenna 916. In various specific implementations, the RF interface circuitry 904 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0188] Antenna 916 may include one or more antenna elements to convert electrical signals into radio waves for travel through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 916 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 916 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 916 may have one or more panels designed for a specific frequency band including the frequency bands in FR1 or FR2.

[0189] User interface 908 includes various input / output (I / O) devices designed to enable users to interact with UE 900. User interface 908 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a headset. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 900.

[0190] Sensor 910 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0191] The driving circuitry 912 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 900. The driving circuitry 912 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 900. For example, the driving circuitry 912 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of a sensor 910 and controlling and allowing access to the sensor 910; a driver for acquiring actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0192] The PMIC 914 manages the power supplied to various components of the UE 900. Specifically, relative to the processor 902, the PMIC 914 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0193] In some implementations, the PMIC 914 may control or otherwise become part of various power-saving mechanisms of the UE 900. The battery 918 may power the UE 900, but in some examples, the UE 900 may be installed in a fixed location and may have a power source coupled to the grid. The battery 918 may be a lithium-ion battery, a metal-air battery (such as zinc-air, aluminum-air, lithium-air, etc.). In some implementations, such as in vehicle-based applications, the battery 918 may be a typical lead-acid automotive battery.

[0194] Figure 10An example access node 1000 (e.g., a base station or gNB) according to some specific implementation is illustrated. Access node 1000 may be similar to and substantially interchangeable with base station 104. Access node 1000 may include processor 1002, RF interface circuitry 1004, core network (CN) interface circuitry 1006, memory / storage device circuitry 1008, and one or more antennas 1010.

[0195] Components of access node 1000 can be coupled to various other components via one or more interconnects 1012. Processor 1002, RF interface circuitry 1004, memory / storage device circuitry 1008 (including communication protocol stack 1014), antenna 1010, and interconnects 1012 can be analogous to those of other components. Figure 10 Similar named components are shown and described. For example, processor 1002 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1016A, central processing unit circuitry (CPU) 1016B, and graphics processing unit circuitry (GPU) 1016C.

[0196] The CN interface circuit 1006 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from access node 1000 via fiber optic or wireless backhaul. The CN interface circuit 1006 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1006 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0197] As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and can include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to an access node 1000 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node," etc., can refer to an access node 1000 (e.g., an eNB) operating in an LTE or 4G system. Depending on various specific implementations, the access node 1000 can be implemented as one or more of the following: dedicated physical equipment such as a macro cell base station, and / or a low-power (LP) base station for providing a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macro cell, such as a femtocell, picocell, or other similar cell.

[0198] In some specific implementations, all or part of the access node 1000 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 1000 may be a "roadside unit" or act as a "roadside unit". The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented or be implemented by a suitable RAN node or a UE that is camped (or relatively camped) thereon, wherein an RSU implemented or be implemented by a UE may be referred to as a "UE-type RSU", an RSU implemented or be implemented by an eNB may be referred to as an "eNB-type RSU", an RSU implemented or be implemented by a gNB may be referred to as a "gNB-type RSU", and so on.

[0199] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0200] For one or more embodiments, at least one component of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described below. As another example, circuitry associated with one or more of the UEs, base stations, network elements, etc., described above in conjunction with the foregoing figures may be configured to operate according to one or more examples shown in the Examples section below.

[0201] Example

[0202] Further exemplary implementations are provided in the following sections.

[0203] Implementation A1 includes a method comprising: receiving a Physical Broadcast Channel (PBCH) from a wireless network, the PBCH including a first indication of whether a Physical Downlink Control Channel (PDCCH) repetition is configured for System Information Block 1 (SIB1) signaling; receiving one or more PDCCHs from the wireless network based on the first indication, wherein the one or more PDCCHs include scheduling information for a Physical Downlink Shared Channel (PDSCH) carrying SIB1; receiving a PDSCH carrying SIB1 from the wireless network based on the scheduling information; and at least one of the following: configuring signaling according to SIB1 for transmission to the wireless network, or receiving signaling from the wireless network according to SIB1.

[0204] Example A2 includes the method according to Example A1. Furthermore, the scheduling information includes:

[0205] A second instruction for the control resource set (CORESET) of each of the one or more PDCCHs carrying the SIB1; and a third instruction for the search space (SS) of each of the one or more PDCCHs carrying the SIB1.

[0206] Example A3 includes the method described according to Example A1 or A2. Furthermore, the first indication is signaled by bits in the Master Information Block (MIB) of the PBCH.

[0207] Example A4 includes the method according to any one of Examples A1 to A3. Furthermore, the first indication is signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0208] Example A5 includes the method according to any one of Examples A1 to A4. Furthermore, the first indication is signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein the two bits additionally indicate the number of PDCCH repetitions for SIB1 signaling.

[0209] Example A6 includes the method according to any one of Examples A1 to A5. Furthermore, the two bits additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with the PDCCH repetition, whether the Common Space Search (SS) is associated with the PDCCH repetition, or at least one of the temporal or frequency relationships between the PDCCH repetitions.

[0210] Example A7 includes the method according to any one of Examples A1 to A6. Furthermore, receiving the one or more PDCCHs includes: determining that the PBCH indicates that the PDCCH is repeatedly not configured for SIB1; and receiving a single PDCCH based on the first indication, wherein the single PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

[0211] Example A8 includes the method according to any one of Examples A1 to A7. Furthermore, receiving one or more PDCCHs includes: determining that the PBCH indicates that the PDCCH is repeatedly configured for SIB1; and receiving at least a first PDCCH and a second PDCCH based on the first indication, wherein each of the first PDCCH and the second PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

[0212] Example A9 includes the method according to any one of Examples A1 to A8. Furthermore, the method includes: determining that the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces; and determining an offset between the search spaces of the first PDCCH and the second PDCCH.

[0213] Example A10 includes the method according to any one of Examples A1 to A9. Furthermore, the offset is a predetermined offset.

[0214] Example A11 includes the method according to any one of Examples A1 to A10. Furthermore, the offset is configured by the wireless network.

[0215] Example A12 includes the method according to any one of Examples A1 to A11. Furthermore, the method includes determining that the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESETs), and determining the offset between the CORESETs of the first PDCCH and the second PDCCH.

[0216] Example A13 includes the method according to any one of Examples A1 to A12. Furthermore, the offset is a predetermined offset.

[0217] Example A14 includes the method described according to Example A13. Furthermore, the offset is configured by the wireless network.

[0218] Example A15 includes the method according to any one of Examples A1 to A14. Furthermore, the method includes determining a PDSCH quasi-co-location (QCL) assumption for at least one of the CORESETs that are the first PDCCH and the second PDCCH.

[0219] Example A16 includes the method according to any one of Examples A1 to A15. Furthermore, the method includes determining a PDSCH quasi-co-location (QCL) hypothesis by performing at least one of the following: determining a PDSCH QCL hypothesis that is the same as the higher frequency CORESET from the first PDCCH and the second PDCCH; or determining a PDSCH QCL hypothesis that is the same as the lower frequency CORESET from the first PDCCH and the second PDCCH.

[0220] Example A17 includes the method according to any one of Examples A1 to A16. Furthermore, the method includes: determining that the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESETs); determining a first offset between the CORESETs of the first PDCCH and the second PDCCH; and determining a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0221] Example A18 includes the method according to any one of Examples A1 to A17. Furthermore, the method includes determining a PDSCH quasi-co-location (QCL) assumption based on at least one of the CORESETs of the first PDCCH and the second PDCCH.

[0222] Example A19 includes the method according to any one of Examples A1 to A18. Furthermore, the method includes determining a PDSCH quasi-co-location (QCL) hypothesis by performing at least one of the following: determining a PDSCH QCL hypothesis identical to a higher frequency CORESET from the first PDCCH and the second PDCCH; determining a PDSCH QCL hypothesis identical to a lower frequency CORESET from the first PDCCH and the second PDCCH; determining a PDSCH QCL hypothesis identical to a CORESET associated with an earlier search space from the search spaces of the first PDCCH and the second PDCCH; or determining a PDSCH QCL hypothesis identical to a CORESET associated with a later search space from the search spaces of the first PDCCH and the second PDCCH.

[0223] Example A20 includes the method according to any one of Examples A1 to A19. Furthermore, the method includes: receiving from a wireless network an additional indication as to whether a PDCCH repetition is configured to signal at least one of: an SIB1 other than the SIB1, a Random Access Channel (RACH), or a paging message; and receiving from the wireless network one or more additional PDCCHs based on the additional indication, wherein the one or more additional PDCCHs include scheduling information for an additional PDSCH carrying at least one of: the SIB1 other than the SIB1, the RACH, or the paging message.

[0224] Example A21 includes the method according to any one of Examples A1 to A20. Furthermore, the additional instructions include an explicit configuration of one or more additional search spaces for the one or more additional PDCCHs.

[0225] Example A22 includes the method according to any one of Examples A1 to A21. Furthermore, the one or more additional search spaces of the one or more additional PDCCHs are implicitly configured.

[0226] Example A23 includes the method according to any one of Examples A1 to A22. Furthermore, the additional indication is signaled by at least one of the following: the SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0227] Example A24 includes the method according to any one of Examples A1 to A23. Furthermore, the method is performed by a user equipment (UE).

[0228] Example A25 includes the method described according to Examples A1 to A23. Furthermore, the method is executed by one or more baseband processors.

[0229] Implementation B1 includes a method comprising: generating a Physical Broadcast Channel (PBCH) for transmission to a User Equipment (UE), the PBCH including a first indication of whether a Physical Downlink Control Channel (PDCCH) repetition is configured for System Information Block 1 (SIB1) signaling; generating one or more PDCCHs for transmission to the UE based on the first indication, wherein the one or more PDCCHs include scheduling information for a Physical Downlink Shared Channel (PDSCH) carrying SIB1; generating the PDSCH carrying the SIB1 for transmission to the UE based on the scheduling information; and at least one of the following: configuring signaling for transmission to the UE based on SIB1, or receiving signaling from the UE based on SIB1.

[0230] Example B2 includes the method according to Example B1. Furthermore, the scheduling information includes: a second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying the SIB1; and a third indication of the search space (SS) for each of the one or more PDCCHs carrying the SIB1.

[0231] Example B3 includes the method described according to Example B1 or B2. Furthermore, the first indication is signaled by bits in the Master Information Block (MIB) of the PBCH.

[0232] Example B4 includes the method according to any one of Examples B1 to B3. Furthermore, the first indication is signaled by a bit in the physical layer (PHY) payload of the PBCH.

[0233] Example B5 includes the method according to any one of Examples B1 to B4. Furthermore, the first indication is signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein the two bits additionally indicate the number of PDCCH repetitions for SIB1 signaling.

[0234] Example B6 includes the method according to any one of Examples B1 to B5. Furthermore, the two bits additionally indicate at least one of the following: whether the Common Control Resource Set (CORESET) is associated with the PDCCH repetition, whether the Common Space Search (SS) is associated with the PDCCH repetition, or at least one of the temporal or frequency relationships between the PDCCH repetitions.

[0235] Example B7 includes the method according to any one of Examples B1 to B6. Furthermore, the PBCH indicates that the PDCCH repeat is not configured for SIB1, and wherein generating the one or more PDCCHs for transmission includes generating a single PDCCH for transmission, wherein the single PDCCH carries the scheduling information for the PDSCH carrying SIB1.

[0236] Example B8 includes the method according to any one of Examples B1 to B7. Furthermore, the PBCH indicates that the PDCCH is repeatedly configured for SIB1, and wherein generating the one or more PDCCHs for transmission includes generating a first PDCCH and a second PDCCH for transmission based on the first indication, wherein each of the first PDCCH and the second PDCCH carries the scheduling information for the PDSCH carrying SIB1.

[0237] Example B9 includes the method according to any one of Examples B1 to B8. Furthermore, the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces, and the method further includes configuring an offset between the search spaces of the first PDCCH and the second PDCCH.

[0238] Example B10 includes the method according to any one of Examples B1 to B9. Furthermore, the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESETs), wherein the method further includes configuring an offset between the CORESETs of the first PDCCH and the second PDCCH.

[0239] Example B11 includes the method according to any one of Examples B1 to B10. Furthermore, the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESETs), and the method further includes at least one of: configuring a first offset between the CORESETs of the first PDCCH and the second PDCCH; or configuring a second offset between the search spaces of the first PDCCH and the second PDCCH.

[0240] Example B12 includes the method according to any one of Examples B1 to B11. Furthermore, the method includes: generating an additional indication of whether a PDCCH repetition is configured to signal at least one of the following for transmission to the UE: SIB1 other than SIB1, a random access channel (RACH), or a paging message; and generating one or more additional PDCCHs according to the additional indication for transmission to the UE, wherein the one or more additional PDCCHs include scheduling information for carrying an additional PDSCH of at least one of the following: SIB1 other than SIB1, the RACH, or the paging message.

[0241] Example B13 includes the method according to any one of Examples B1 to B12. Furthermore, the additional instructions include an explicit configuration of one or more additional search spaces for the one or more additional PDCCHs.

[0242] Example B14 includes the method according to any one of Examples B1 to B13. Furthermore, the one or more additional search spaces of the one or more additional PDCCHs are implicitly configured.

[0243] Example B15 includes the method according to any one of Examples B1 to B14. Furthermore, the additional indication is signaled by at least one of the following: the SIB1, the Master Information Block (MIB), or the PBCH Physical Layer (PHY) payload.

[0244] Example B16 includes the method according to any one of Examples B1 to B15. Furthermore, the method is performed by a base station.

[0245] Example B17 includes the method according to any one of Examples B1 to B15. Furthermore, the method is executed by one or more baseband processors.

[0246] Embodiment C1 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described or associated with any of Embodiments A1 to A23 or B1 to B15, or any other methods or processes described herein.

[0247] Embodiment D1 may include an apparatus comprising logic components, modules, and / or circuitry (e.g., processing circuitry) for performing one or more elements of the methods described or associated with any of Embodiments A1 to A23 or B1 to B15, or any other methods or processes described herein.

[0248] Example E1 may include the methods, techniques or processes, or parts or components thereof, as described or associated with any of Examples A1 to A23 or B1 to B15.

[0249] Embodiment F1 may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Embodiments A1 to A23 or B1 to B15.

[0250] Example G1 may include signals, or portions thereof, as described or associated with any of Examples A1 to A23 or B1 to B15.

[0251] Embodiment H1 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Embodiments A1 to A23. The operation or action performed by the instructions executed by the processing element may include the method according to any one of Embodiments A1 to A23 or B1 to B15.

[0252] Example I1 may include methods for communicating in a wireless network as shown and described herein.

[0253] Embodiment J1 may include a system for providing wireless communication as shown and described herein. Operations or actions performed by said system may include methods according to any one of embodiments A1 to A23 or B1 to B15.

[0254] Example K1 may include a device for providing wireless communication as shown and described herein. The operations or actions performed by said device may include the method according to any one of Examples A1 to A23 or B1 to B15.

[0255] The previously described embodiments A1 to A23 or B1 to B15 can be implemented using the following: a computer-implemented method; a non-transitory computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled to a hardware processor configured to perform the computer-implemented method or instructions stored on the non-transitory computer-readable medium.

[0256] A system (e.g., a base station, a device including one or more baseband processors, etc.) may be configured to perform a specific operation or action by means of software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform actions in operation. The operation or action performed by the system may include the method according to any one of embodiments A1 to A23 or B1 to B15.

[0257] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0258] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

[0259] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. A method, the method comprising: Receives a Physical Broadcast Channel (PBCH) from a wireless network, the Physical Broadcast Channel (PBCH) including a first indication of whether the Physical Downlink Control Channel (PDCCH) repetition is configured for System Information Block 1 (SIB1) signaling; Based on the first indication, one or more PDCCHs are received from the wireless network, wherein the one or more PDCCHs include scheduling information for the Physical Downlink Shared Channel (PDSCH) carrying SIB1; Based on the scheduling information, receive the PDSCH carrying the SIB1 from the wireless network; as well as At least one of the following: Configure signaling for transmission to the wireless network according to the SIB1, or receive signaling from the wireless network according to the SIB1.

2. The method according to claim 1, wherein the scheduling information includes: A second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying the SIB1, and A third indication of the search space (SS) for each of the one or more PDCCHs carrying the SIB1.

3. The method of claim 1, wherein the first indication is signaled by a bit in the Master Information Block (MIB) of the PBCH.

4. The method of claim 1, wherein the first indication is signaled by a bit in the physical layer (PHY) payload of the PBCH.

5. The method of claim 1, wherein the first indication is signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein the two bits additionally indicate the number of PDCCH repetitions for SIB1 signaling.

6. The method of claim 5, wherein the two bits additionally indicate at least one of the following: Whether the Common Control Resource Set (CORESET) is repeatedly associated with the PDCCH, whether the Common Space Search (SS) is repeatedly associated with the PDCCH, or At least one of the time relationship or frequency relationship between the PDCCH repetitions.

7. The method of claim 1, wherein receiving the one or more PDCCHs comprises: The system determines that the PBCH indicates that the PDCCH is repeatedly not configured for SIB1, and receives a single PDCCH based on the first indication, wherein the single PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

8. The method of claim 1, wherein receiving the one or more PDCCHs comprises: The PBCH indicates that the PDCCH is repeatedly configured for SIB1, and at least the first PDCCH and the second PDCCH are received based on the first indication, wherein each of the first PDCCH and the second PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

9. The method according to claim 8, further comprising: It is determined that the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces, and Determine the offset between the search spaces of the first PDCCH and the second PDCCH.

10. The method of claim 9, wherein the offset is a predetermined offset.

11. The method of claim 9, wherein the offset is configured by the wireless network.

12. The method according to claim 8, further comprising: It is determined that the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESET), and Determine the offset between the CORESET of the first PDCCH and the second PDCCH.

13. The method of claim 12, wherein the offset is a predetermined offset.

14. The method of claim 12, wherein the offset is configured by the wireless network.

15. The method of claim 12, further comprising determining a PDSCH quasi-co-location (QCL) assumption for at least one of the CORESETs of the first PDCCH and the second PDCCH.

16. The method of claim 12, further comprising determining the PDSCH quasi-co-location (QCL) assumption by performing at least one of the following: Determine the same PDSCH QCL hypothesis as the higher frequency CORESET from the first PDCCH and the second PDCCH, or determine the same PDSCH QCL hypothesis as the lower frequency CORESET from the first PDCCH and the second PDCCH.

17. The method according to claim 8, further comprising: It is determined that the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESET). Determine the first offset between the CORESET of the first PDCCH and the second PDCCH, and Determine a second offset between the search spaces of the first PDCCH and the second PDCCH.

18. The method of claim 17, further comprising determining a PDSCH quasi-co-location (QCL) hypothesis based on at least one of the CORESETs of the first PDCCH and the second PDCCH.

19. The method of claim 17, further comprising determining the PDSCH quasi-co-location (QCL) assumption by performing at least one of the following: Determine the PDSCH QCL assumption that is the same as the higher frequency CORESET from the first PDCCH and the second PDCCH. Determine the PDSCH QCL assumption as being the same as the lower frequency CORESET from the first PDCCH and the second PDCCH. Determine the same PDSCH QCL assumption as CORESET, whereby CORESET is associated with a search space that is an earlier search space from the search spaces of the first PDCCH and the second PDCCH, or Determine the same PDSCH QCL assumption as CORESET, which is associated with a search space that is a later search space from the search spaces of the first PDCCH and the second PDCCH.

20. The method according to claim 1, further comprising: Whether receiving PDCCH repetitions from a wireless network is configured to provide additional indication for signaling at least one of the following: SIB1 other than the aforementioned SIB1, Random Access Channel (RACH), or Paging messages, and Based on the additional indication, one or more additional PDCCHs are received from the wireless network, wherein the one or more additional PDCCHs include scheduling information for additional PDSCHs carrying at least one of the following: SIB1 other than the one mentioned above, The RACH, or The paging message.

21. The method of claim 20, wherein the additional indication includes an explicit configuration of one or more additional search spaces of the one or more additional PDCCHs.

22. The method of claim 20, wherein the one or more additional search spaces of the one or more additional PDCCHs are implicitly configured.

23. The method of claim 20, wherein the additional indication is signaled by at least one of: The SIB1, Master Information Block (MIB), or PBCH physical layer (PHY) payload.

24. The method of claim 1, wherein the method is performed by a user equipment (UE).

25. The method of claim 1, wherein the method is executed by one or more baseband processors.

26. A system comprising one or more computers and one or more storage devices thereon storing instructions which, when executed by the one or more computers, are operable to cause the one or more computers to perform the method according to any one of claims 1 to 23.

27. A non-transitory computer storage medium encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform the method according to any one of claims 1 to 23.

28. An apparatus comprising a processing circuit configured to perform the method according to any one of claims 1 to 23.

29. One or more baseband processors configured to perform the method according to any one of claims 1 to 23.

30. A method comprising: A physical broadcast channel (PBCH) is generated for transmission to user equipment (UE), the physical broadcast channel (PBCH) including a first indication of whether the physical downlink control channel (PDCCH) repeat is configured for System Information Block 1 (SIB1) signaling; One or more PDCCHs are generated according to the first instruction for transmission to the UE, wherein the one or more PDCCHs include scheduling information for the Physical Downlink Shared Channel (PDSCH) carrying SIB1; The PDSCH carrying the SIB1 is generated based on the scheduling information for transmission to the UE; as well as At least one of the following: Configure signaling according to SIB1 for transmission to the UE, or The signaling is received from the UE according to the SIB1.

31. The method of claim 30, wherein the scheduling information includes: A second indication of the control resource set (CORESET) for each of the one or more PDCCHs carrying the SIB1, and A third indication of the search space (SS) for each of the one or more PDCCHs carrying the SIB1.

32. The method of claim 30, wherein the first indication is signaled by a bit in the Master Information Block (MIB) of the PBCH.

33. The method of claim 30, wherein the first indication is signaled by a bit in the physical layer (PHY) payload of the PBCH.

34. The method of claim 30, wherein the first indication is signaled by two bits in the physical layer (PHY) payload of the PBCH, wherein the two bits additionally indicate the number of PDCCH repetitions for SIB1 signaling.

35. The method of claim 34, wherein the two bits additionally indicate at least one of the following: Whether the Common Control Resource Set (CORESET) is repeatedly associated with the PDCCH. Is the Public Space Search (SS) repeatedly associated with the PDCCH, or At least one of the time relationship or frequency relationship between the PDCCH repetitions.

36. The method of claim 30, wherein the PBCH indicating that the PDCCH repeat is not configured for SIB1, and Generating one or more PDCCHs for transmission includes generating a single PDCCH for transmission, wherein the single PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

37. The method of claim 30, wherein the PBCH instructs the PDCCH to be repeatedly configured for SIB1, and The generation of the one or more PDCCHs for transmission includes generating a first PDCCH and a second PDCCH for transmission based on the first indication, wherein each of the first PDCCH and the second PDCCH carries the scheduling information for the PDSCH carrying the SIB1.

38. The method of claim 30, wherein the first PDCCH and the second PDCCH have a common control resource set (CORESET) and different corresponding search spaces, and The method further includes configuring an offset between the search spaces of the first PDCCH and the second PDCCH.

39. The method of claim 30, wherein the first PDCCH and the second PDCCH have a common search space and different corresponding control resource sets (CORESET), wherein the method further comprises configuring an offset between the CORESET of the first PDCCH and the second PDCCH.

40. The method of claim 30, wherein the first PDCCH and the second PDCCH have different corresponding search spaces and different corresponding control resource sets (CORESET), and The method further includes at least one of the following: Configure a first offset between the CORESET of the first PDCCH and the second PDCCH, or Configure a second offset between the search spaces of the first PDCCH and the second PDCCH.

41. The method according to claim 30, further comprising: Whether the generation of PDCCH repetition is configured to signal at least one of the following additional indications for transmission to the UE: SIB1 other than the aforementioned SIB1, Random Access Channel (RACH), or Paging messages, and One or more additional PDCCHs are generated according to the additional indication for transmission to the UE, wherein the one or more additional PDCCHs include scheduling information for an additional PDSCH carrying at least one of the following: SIB1 other than the one mentioned above, The RACH, or The paging message.

42. The method of claim 41, wherein the additional indication includes an explicit configuration of one or more additional search spaces of the one or more additional PDCCHs.

43. The method of claim 41, wherein the one or more additional search spaces of the one or more additional PDCCHs are implicitly configured.

44. The method of claim 41, wherein the additional indication is signaled by at least one of: The SIB1, Master Information Block (MIB), or PBCH physical layer (PHY) payload.

45. The method of claim 30, wherein the method is performed by a base station.

46. ​​The method of claim 30, wherein the method is performed by one or more baseband processors.

47. A system comprising one or more computers and one or more storage devices thereon storing instructions which, when executed by the one or more computers, are operable to cause the one or more computers to perform the method according to any one of claims 40 to 44.

48. A non-transitory computer storage medium encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform the method according to any one of claims 30 to 44.

49. An apparatus comprising a processing circuit configured to perform the method according to any one of claims 30 to 44.

50. One or more baseband processors, said baseband processors being configured to perform the method according to any one of claims 30 to 44.

Images