Extensible physical broadcast channel

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. A network entity sends a broadcast channel message to a user equipment (UE) as part of a synchronization signal block (SSB) transmission. This broadcast channel message may indicate a time timing for space search relative to the corresponding SSB timing based on a time offset. Additionally or alternatively, the broadcast channel message may indicate a frequency position of a random access channel timing relative to the frequency position of the SSB based on a frequency offset, and the UE may send a request for additional system information via the random access channel timing. In some examples, the broadcast channel message may include an presence indicator indicating the presence of an additional broadcast channel message, which may include additional information. In some cases, the presence indicator may indicate resources, content, or both for the additional broadcast channel message.

Description

Technical Field

[0001] The following discussion pertains to wireless communications, including the Scalable Physical Broadcast Channel (PBCH). Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources, such as time, frequency, and power. Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM).

[0003] A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as user equipment (UE). In some examples, the UE may receive broadcast messages that indicate information associated with the network. Summary of the Invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses supporting Scalable Physical Broadcast Channel (PBCH). For example, the described techniques enable network entities to send broadcast messages to a UE as part of a Synchronization Signal Block (SSB) transmission, the broadcast message indicating a timing for space search relative to the corresponding SSB timing. For example, the timing for space search transmission can be indicated as a symbol offset relative to the next SSB transmission. By indicating a relative indication of the search space relative to an absolute position indicating space search transmission, the payload size of the broadcast message can be reduced. Additionally or alternatively, to further reduce the payload size, the broadcast message can indicate the frequency position of the Random Access Channel (RACH) timing relative to the frequency position of the SSB. In some examples, to indicate information that might have been omitted from the broadcast message due to payload size reduction, the broadcast message can implement scalable payload techniques. For example, a first broadcast message may include an presence indicator indicating the presence of a second broadcast message, which may include additional information. Thus, the UE can decode additional broadcast resources to obtain the additional information while reducing the payload size of the individual broadcast message.

[0005] A method for wireless communication by a UE is described. The method may include: receiving an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the beginning of a search space; monitoring search space transmissions via the search space during a second timing period corresponding to the time offset indicated in the PBCH message; and receiving the search space transmissions via the second timing period.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code such that the UE: receives an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the beginning of a search space; monitors search space transmissions via the search space during a second timing period corresponding to the time offset indicated in the PBCH message; and receives search space transmissions via the second timing period.

[0007] Another UE for wireless communication is described. The UE may include: means for receiving an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the beginning of a search space; means for monitoring search space transmissions via the search space during a second timing period corresponding to the time offset indicated in the PBCH message; and means for receiving search space transmissions via the second timing period.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive an SSB including a PBCH message during a first time window, the PBCH message indicating a time offset relative to the start of the SSB to identify the beginning of a search space; monitor search space transmissions via the search space during a second time window corresponding to the time offset indicated in the PBCH message; and receive the search space transmissions via the second time window.

[0009] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving a second synchronization signal block that includes a second PBCH message, wherein the first identifier of the SSB is the same as the second identifier of the second synchronization signal block, and wherein the payload of the second PBCH message may be the same as the payload of the PBCH message.

[0010] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for: receiving first data included in a PBCH message and second data included in a second PBCH message; and combining the first data and the second data to obtain a payload of a PBCH message, wherein the monitoring search space transmits a payload that may be based on the PBCH message.

[0011] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the time offset indicates one or more symbols between the start of the search space transmission and the start of the SSB.

[0012] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the start of the search space transmission and the start of the SSB occur within the same time slot, and the time offset can be indicated via at least four bits of the PBCH message.

[0013] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the time offset relative to the start of the SSB is used to identify the start of the previous search space transmission.

[0014] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the time offset relative to the start of the SSB is used to identify the start of an upcoming search space transmission.

[0015] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the time offset identifier may be the start of the search space transmission that is closest to the start of the SSB in the time domain.

[0016] A method for wireless communication by a UE is described. The method may include: receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; transmitting a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and receiving a message indicating the system information based on the transmission request.

[0017] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: receive an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; transmit a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and receive a message indicating system information based on the transmission request.

[0018] Another UE for wireless communication is described. This UE may include: components for receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB that identifies a random access opportunity; components for transmitting a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and components for receiving a message indicating system information based on the transmission request.

[0019] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; transmit a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and receive a message indicating the system information based on the transmission request.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of a first frequency resource and the start of a second frequency resource.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the frequency offset also includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource, and a subcarrier offset indicating the number of subcarriers between that number of uplink resource blocks and the start of the second frequency resource.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the resource block offset indicates the difference between the resource block identifier of a first uplink resource block and the resource block identifier of a second uplink resource block, and the first uplink resource block includes the start of a first frequency resource, and the second uplink resource block includes the start of a second frequency resource.

[0023] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, resource block offsets may be indicated via a first set of bits in a PBCH message, and subcarrier offsets may be indicated via a second set of bits in a PBCH message, the second set of bits following the first set of bits.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the frequency offset may be based on a first subcarrier spacing of the uplink bandwidth portion associated with the random access timing or a second subcarrier spacing associated with the SSB.

[0025] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, the frequency offset may be based on the larger of the first subcarrier spacing and the second subcarrier spacing or the smaller of the first subcarrier spacing and the second subcarrier spacing.

[0026] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving an SSB may include operations, features, components, or instructions for the following actions: receiving an SSB that includes a PBCH message that also indicates a time offset relative to the start of the SSB to identify the start of a random access opportunity, wherein the transmission request may be based on the time offset.

[0027] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, the PBCH message also indicates one or more additional frequency offsets, each of the one or more additional frequency offsets identifying a corresponding frequency resource relative to a second frequency resource, and each corresponding frequency resource corresponding to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0028] A method for wireless communication by a UE is described. The method may include: receiving an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; receiving the second PBCH message based on the presence indicator; and communicating one or more messages to a network entity based on the first PBCH message and the second PBCH message.

[0029] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: receive an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; receive the second PBCH message based on the presence indicator; and communicate one or more messages to a network entity based on the first PBCH message and the second PBCH message.

[0030] Another UE for wireless communication is described. This UE may include: components for receiving an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; components for receiving the second PBCH message based on the presence indicator; and components for communicating one or more messages to a network entity based on the first PBCH message and the second PBCH message.

[0031] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive an SSB including a first PBCH message, the first PBCH message including an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; receive the second PBCH message based on the presence indicator; and communicate one or more messages to a network entity based on the first PBCH message and the second PBCH message.

[0032] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the value of the first identifier associated with the first PBCH message may be less than the value of the second identifier associated with the second PBCH message.

[0033] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the first PBCH message includes a master information block that includes an presence indicator.

[0034] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the first PBCH message includes a demodulation reference signal that includes an presence indicator.

[0035] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving a second PBCH message may include operations, features, components, or instructions for the following actions: receiving a second PBCH message including a second presence indicator that indicates the presence of a third PBCH message.

[0036] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving a third PBCH message based on a second presence indicator, wherein one or more messages communicated with a network entity may be based on receiving the third PBCH message.

[0037] In some examples of the methods described herein, the UE, and the non-transitory computer-readable medium, an indicator also indicates the resources used to receive the second PBCH message.

[0038] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, resources may be selected from a set of candidate resources associated with the first PBCH message.

[0039] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for the following actions: indicating resources including: indicating frequency domain resource assignments, time domain resource assignments, modulation and decoding schemes, redundancy versions, virtual resource block to physical resource block mappings, or combinations thereof associated with resources.

[0040] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, an indicator also indicates the content associated with the second PBCH message.

[0041] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the content may be selected from a set of candidate content associated with the second PBCH message.

[0042] A method for wireless communication by a network entity is described. The method may include: outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of a search space transmission; and outputting a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0043] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: output an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of a search space transmission; and output a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0044] Another network entity for wireless communication is described. This network entity may include: components for outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of search space transmission; and components for outputting search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0045] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of a search space transmission; and output the search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0046] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: outputting a second synchronization signal block that includes a second PBCH message, wherein the first identifier of the SSB is the same as the second identifier of the second synchronization signal block, and wherein the payload of the second PBCH message may be the same as the payload of the PBCH message.

[0047] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the time offset indicates one or more symbols between the start of the search space transmission and the start of the SSB.

[0048] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the start of the search space transmission and the start of the SSB occur within the same time slot, and the time offset can be indicated via at least four bits of the PBCH message.

[0049] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the time offset relative to the start of the SSB is used to identify the start of the previous search space transmission.

[0050] In the methods described herein, network entities, and some examples of nontransitory computer-readable media, the time offset relative to the start of the SSB is used to identify the start of an upcoming search space transmission.

[0051] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the time offset identifier may be the start of the search space sent in the time domain that is closest to the start of the SSB.

[0052] A method for wireless communication by a network entity is described. The method may include: outputting a Service Serving SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; obtaining a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and outputting a message indicating the system information based on the transmission request.

[0053] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: output an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; obtain a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and output a message indicating the system information based on the transmission request.

[0054] Another network entity for wireless communication is described. This network entity may include: components for outputting an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB to identify a random access opportunity; components for obtaining a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and components for outputting a message indicating system information based on the transmission request.

[0055] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource used for the SSB to identify a random access opportunity; obtain a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and output a message indicating the system information based on the transmission request.

[0056] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of a first frequency resource and the start of a second frequency resource.

[0057] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the frequency offset also includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource, and a subcarrier offset indicating the number of subcarriers between that number of uplink resource blocks and the start of the second frequency resource.

[0058] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource block offset indicates the difference between the resource block identifier of a first uplink resource block and the resource block identifier of a second uplink resource block, and the first uplink resource block includes the start of a first frequency resource, and the second uplink resource block includes the start of a second frequency resource.

[0059] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, resource block offsets may be indicated via a first set of bits in a PBCH message, and subcarrier offsets may be indicated via a second set of bits in a PBCH message, which follows the first set of bits.

[0060] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the frequency offset may be based on a first subcarrier spacing of the uplink bandwidth portion associated with the random access timing or a second subcarrier spacing associated with the SSB.

[0061] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the frequency offset may be based on the larger of the first subcarrier spacing and the second subcarrier spacing, or the smaller of the first subcarrier spacing and the second subcarrier spacing.

[0062] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending an SSB may include operations, features, components, or instructions for the following actions: outputting an SSB that includes a PBCH message, the PBCH message also indicating a time offset relative to the start of the SSB to identify the start of the random access opportunity, wherein the transmission request may be based on the time offset.

[0063] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the PBCH message also indicates one or more additional frequency offsets, each of the one or more additional frequency offsets identifying a corresponding frequency resource relative to a second frequency resource, and each corresponding frequency resource corresponding to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0064] A method for wireless communication by a network entity is described. The method may include: outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; outputting the second PBCH message based on the presence indicator; and conveying one or more messages to a UE based on the first PBCH message and the second PBCH message.

[0065] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: output an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; output the second PBCH message based on the presence indicator; and communicate one or more messages to a UE based on the first PBCH message and the second PBCH message.

[0066] Another network entity for wireless communication is described. This network entity may include: components for outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; components for outputting the second PBCH message based on the presence indicator; and components for communicating one or more messages to a UE based on the first PBCH message and the second PBCH message.

[0067] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; output the second PBCH message based on the presence indicator; and communicate one or more messages to a UE based on the first PBCH message and the second PBCH message.

[0068] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the value of the first identifier associated with the first PBCH message may be less than the value of the second identifier associated with the second PBCH message.

[0069] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first PBCH message includes a master information block that includes an presence indicator.

[0070] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the first PBCH message includes a demodulation reference signal that includes an presence indicator.

[0071] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting a second PBCH message may include operations, features, components, or instructions for the following actions: outputting a second PBCH message including a second presence indicator that indicates the presence of a third PBCH message.

[0072] The methods described herein, network entities, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for outputting a third PBCH message based on a second presence indicator, wherein one or more messages can be communicated with a network entity based on receiving the third PBCH message.

[0073] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the presence indicator also indicates the resources used to receive the second PBCH message.

[0074] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, resources may be selected from a set of candidate resources associated with the first PBCH message.

[0075] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: indicating resources including: indicating frequency domain resource assignments, time domain resource assignments, modulation and decoding schemes, redundant versions, virtual resource block to physical resource block mappings, or combinations thereof associated with resources.

[0076] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, an indicator also indicates the content associated with the second PBCH message.

[0077] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the content may be selected from a set of candidate content associated with the second PBCH message. Attached Figure Description

[0078] Figure 1 An example of a wireless communication system supporting a Scalable Physical Broadcast Channel (PBCH) according to one or more aspects of this disclosure is shown.

[0079] Figure 2 An example of a wireless communication system supporting a scalable PBCH is shown in accordance with one or more aspects of this disclosure.

[0080] Figures 3A to 5B An example of a signaling diagram supporting scalable PBCH is shown according to one or more aspects of this disclosure.

[0081] Figure 6 An example of a process flow supporting scalable PBCH is shown in accordance with one or more aspects of this disclosure.

[0082] Figure 7 and Figure 8 A block diagram of a device supporting a scalable PBCH according to one or more aspects of this disclosure is shown.

[0083] Figure 9 A block diagram of a communication manager supporting scalable PBCH is shown, according to one or more aspects of this disclosure.

[0084] Figure 10 A diagram of a system including a device supporting a scalable PBCH is shown according to one or more aspects of this disclosure.

[0085] Figure 11 and Figure 12 A block diagram of a device supporting a scalable PBCH according to one or more aspects of this disclosure is shown.

[0086] Figure 13A block diagram of a communication manager supporting scalable PBCH is shown, according to one or more aspects of this disclosure.

[0087] Figure 14 A diagram of a system including a device supporting a scalable PBCH is shown according to one or more aspects of this disclosure.

[0088] Figures 15 to 20 A flowchart illustrating a method for supporting scalable PBCH according to one or more aspects of this disclosure is shown. Detailed Implementation

[0089] In some systems, network entities may perform synchronization signal block (SSB) transmissions, which may include information for establishing communication between the UE and the network entity. For example, an SSB may include a primary synchronization signal, a secondary synchronization signal, and one or more physical broadcast channels (PBCHs) that assist the UE in obtaining timing information, cell identifiers, and other information for communication performed by the UE. To reduce power consumption at both the UE and the network entity, the overhead associated with SSB transmission can be reduced by decreasing the total number of symbols associated with the SSB. However, in some cases, this may result in a reduction in the payload size used for PBCH transmission, potentially limiting the information that can be included within the PBCH transmission. One or more techniques described herein provide methods for conveying information within PBCH transmissions.

[0090] According to the examples described herein, a network entity may send a broadcast message (e.g., a PBCH transmission) to the UE as part of an SSB transmission. Such a broadcast message may indicate the timing of the space search relative to the corresponding SSB timing. For example, the network entity may indicate the timing of the space search as a symbol offset relative to the next SSB transmission. By indicating a relative indication of the space search relative to the absolute position indicating the space search transmission, the payload size of the PBCH can be reduced. Additionally or alternatively, to further reduce the payload size, the broadcast message may indicate the frequency position of the RACH timing relative to the frequency position of the SSB. In some examples, to indicate information that may have been omitted from the broadcast message due to the reduced payload size, the network entity may implement scalable payload indication techniques. For example, the first broadcast message may include an presence indicator indicating the presence of a second broadcast message, which may include additional information. Therefore, the UE can obtain additional information while reducing the payload size of the individual broadcast message, thereby reducing transmission overhead and power consumption for both the UE and the network entity.

[0091] The aspects of this disclosure are first described in the context of a wireless communication system. Additionally, the aspects of this disclosure are illustrated in the context of signaling diagrams and process flows. The aspects of this disclosure are further illustrated by means of apparatus diagrams, system diagrams, and flowcharts relating to a scalable PBCH, and are further described with reference to these diagrams.

[0092] Figure 1 An example of a wireless communication system 100 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0093] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0094] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0095] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0096] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0097] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0098] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0099] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0100] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0101] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the scalable PBCH as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0102] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0103] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0104] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0105] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing (SCS) may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0106] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which This can represent the supported SCS, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resource can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0107] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the SCS. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a sampling period of 1 (units). The duration of a symbol period may depend on the SCS or the operating frequency band.

[0108] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0109] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0110] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0111] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0112] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0113] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0114] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0115] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0116] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0117] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0118] In some systems, network entity 105 may perform SSB transmission, which may include information for UE 115 to establish communication with network entity 105. For example, an SSB including a primary synchronization signal, a secondary synchronization signal, and a PBCH may assist UE 115 in obtaining timing information, cell identifiers, and other information for communication performed by UE 115. To reduce power consumption at both UE 115 and network entity 105, the overhead associated with SSB transmission can be reduced by decreasing the total number of symbols associated with the SSB. However, in some cases, this may result in a reduction in the payload size for the PBCH, potentially limiting the information that can be included within the PBCH. Therefore, defining more efficient techniques for conveying information within the PBCH may be beneficial.

[0119] According to the example described herein, network entity 105 may send a broadcast message (e.g., a PBCH message) to UE 115 as part of an SSB transmission. This broadcast message may indicate the timing of a space search relative to the corresponding SSB timing. For example, the timing of the space search may be indicated as a symbol offset relative to the next SSB transmission. By indicating a relative indication of the space search relative to the absolute position indicating the space search transmission, the payload size of the PBCH can be reduced. Additionally or alternatively, to further reduce the payload size, the broadcast message may indicate the frequency position of the RACH timing relative to the frequency position of the SSB. In some examples, to indicate information that may have been omitted from the broadcast message due to the reduced payload size, the network entity may implement scalable payload techniques. For example, the first broadcast message may include an presence indicator indicating the presence of a second broadcast message, which may include additional information. Therefore, UE 115 can obtain the additional information while reducing the payload size of the individual broadcast messages, thereby reducing the transmission overhead and power consumption of both UE 115 and network entity 105.

[0120] Figure 2 An example of a wireless communication system 200 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. The wireless communication system 200 illustrates communication between a UE 115-a and a network entity 105-a, which may be as referenced herein. Figure 1 Examples of the corresponding devices described.

[0121] In some systems, network entity 105-a may perform an SSB transmission, which may include information for UE 115-a to establish communication with network entity 105-a. For example, the SSB may include a primary synchronization signal, a secondary synchronization signal, and a PBCH, and may indicate system information for UE 115-a to perform communication with network entity 105-a. In some examples, the information to be indicated to UE 115-a via the SSB may include at least scheduling information associated with search space transmission (e.g., search space zero (SS0) transmission) and control resource set transmission (e.g., default control resource set, such as CORESET0). This information may also include scheduling information associated with any remaining system information and may indicate to UE 115-a whether the remaining system information is available for on-demand delivery or periodic delivery. In some cases, to allow UE 115-a to request on-demand delivery of additional system information, the SSB may also indicate RACH resources for UE 115-a to send on-demand system information requests. Therefore, UE 115-a may request network entity 105-a to send system information that may have been previously omitted from the SSB.

[0122] In some examples, it may be desirable to reduce power consumption at UE 115-a and network entity 105-a. To achieve this, transmission overhead associated with SSB transmission can be reduced by decreasing the total number of symbols associated with the SSB. However, in some cases, this may result in a smaller payload size for the PBCH, potentially limiting the information that can be included within the PBCH. Therefore, defining more efficient techniques for conveying information within the PBCH may be beneficial.

[0123] In some examples, information that may be included in PBCH transmissions (e.g., via the Master Information Block (MIB)) may include a default downlink parameter set, configurations associated with a control resource set (e.g., CORESET0), and configurations associated with a search space (e.g., search space zero). In some examples, system information scheduling information may be indicated via an SSB (such as via the MIB or Residual Minimal System Information (RMSI)). This system information scheduling information may include a delivery type (e.g., on-demand or periodic), a transmission window per system information block (SIB) for periodic transmissions, and RACH resources for requesting on-demand transmissions.

[0124] In some cases, PBCH transmission may additionally include information associated with frame timing (e.g., SFN, half-frame indicator, and SSB identifier), grid offset (e.g., for cell definition SSB (CD-SSB)), and information associated with cell prohibition and co-frequency reselection permission. Additionally or alternatively, the SSB may (e.g., transmitted via RMSI) broadcast configurations for public service cells, timers and constants, emergency support, Unified Access Control (UAC) prohibition information, and non-critical extensions.

[0125] In some examples, network entity 105-a may alternatively send this information on demand based on a request from UE 115-a. Similarly, network entity 105-a may send information associated with cell selection (e.g., quality thresholds for cell selection), information associated with cell access (e.g., Public Land Mobile Network (PLMN) list, whether the cell is reserved for specific UE 115, type allocation code, RAN area code, cell identifier), and information associated with connection establishment failure control (e.g., counters and timers for determining failure and retry behavior) based on a request from the UE for on-demand delivery of information. In some cases, network entity 105-a may include information associated with the pre-demodulation reference signal via a default lookup table (e.g., a Time Domain Resource Allocation (TDRA) table).

[0126] Therefore, PBCH transmission may include at least information associated with search space transmission (e.g., search space zero transmission) and control resource set transmission (e.g., CORESET0 transmission), and it may be beneficial to include configuration of RACH resources for UE 115-a to request on-demand delivery of system information. However, indicating this information within PBCH transmission may use a relatively large number of bits. In some cases, for example, signaling search space transmission resources may use 21 bits (e.g., 10 bits for SFN, six bits for SSB identifier, one bit for half-frame indicator, and four bits for search space configuration). In some examples, to allow UE 115-a to determine RACH resources, PBCH may indicate a reference point (e.g., point A), uplink carrier position, uplink initial bandwidth portion position, and the frequency start of the first RACH timing. Therefore, techniques for indicating this information while reducing the payload size of PBCH transmission may be desirable, which could reduce overhead and power consumption at UE 115-a and network entity 105-a.

[0127] According to the example described herein, network entity 105-a may transmit SSB 205. SSB 205 may include a primary synchronization signal, a secondary synchronization signal, and one or more PBCH messages (e.g., broadcast messages). In some examples, the PBCH message of SSB 205 may indicate a time offset 220 to indicate the timing for the search space (e.g., search space zero). The time offset 220 may indicate the timing for the search space relative to the timing for the corresponding SSB timing (e.g., SSB 205 or another SSB 205). For example, the timing for the search space may be indicated as a symbol offset relative to the next SSB transmission. Therefore, UE 115-a may receive search space transmission 210 from network entity 105-a based on time offset 220. By using a relative indication of the search space relative to the absolute position indicating the search space transmission, the payload size of the PBCH message can be reduced, thereby reducing transmission overhead. This document references Figure 3A and Figure 3B The indication of the search space based on a time offset of 220 is described in further detail.

[0128] In some examples, a PBCH message (e.g., or another PBCH message associated with SSB 205) may indicate a frequency offset 220 to indicate the frequency position of the RACH timing (e.g., for UE 115-a to send a request for additional system information). For example, frequency offset 220 may indicate the frequency position of the RACH timing relative to the frequency position associated with SSB 205. In some examples, frequency offset 220 may include a subcarrier offset indicating the number of subcarriers between the start of the frequency position of the RACH timing and the start of the frequency position of SSB 205. Additionally or alternatively, frequency offset 220 may include a resource block offset indicating the number of resource blocks between the start of the frequency position of the RACH timing and the start of the frequency position of SSB 205. Thus, UE 115-a may send an uplink message 215 via the RACH timing, which may request network entity 105-a to send an indication of additional system information. (References herein) Figure 4 The indication of frequency timing for RACH timing based on a frequency offset of 225 is described in further detail.

[0129] In some examples, to indicate information that may have been omitted from the first PBCH message of SSB 205 due to a reduction in payload size, the first PBCH message may include an presence indicator 230 indicating the presence of a second PBCH message. For example, UE 115-a may receive a first PBCH message including presence indicator 230. UE 115-a may then monitor for a second PBCH message based on presence indicator 230. In some examples, the second PBCH message may include another presence indicator 230 that indicates the presence of a third PBCH message, and so on. In some cases, presence indicator 230 may indicate resources used for the second PBCH message (e.g., time resources, frequency resources, or both), content associated with the second PBCH message (e.g., an indication of system information indicated by the second PBCH message), or both. (References herein) Figure 5A and Figure 5B The indication of the additional PBCH message based on the presence indicator 230 is described in further detail.

[0130] By implementing time offset 220, frequency offset 225, and presence indicator 230, the payload associated with SSB 205 can be reduced, while UE 115-a can still obtain system information from network entity 105-a. Therefore, the transmission overhead associated with communication between UE 115-a and network entity 105-a can be reduced, thereby improving power savings for both UE 115-a and network entity 105-a.

[0131] Figure 3A and Figure 3B Examples of signaling diagrams 300-a and 300-b supporting a scalable PBCH according to one or more aspects of this disclosure are shown. Signaling diagrams 300-a and 300-b illustrate the use of offset 315 (e.g., time offset) relative to the corresponding SSB 310 to indicate the timing for searching space 305, as referenced. Figure 1 and Figure 2 As described. In some examples, SSB 310 may include a primary synchronization signal 325 (e.g., PSS), a secondary synchronization signal 330 (e.g., SSS), and one or more PBCH transmissions (e.g., broadcast messages).

[0132] In some examples, reducing the payload of SSB transmission may be beneficial for reducing SSB overhead, improving SSB coverage, or both (e.g., for lightweight SSB procedures). However, in some cases, signaling search space transmission resources can be difficult and costly. For example, signaling resources for search space transmission in a first multiplexing mode (e.g., mode 1) may include signaling the SFN (e.g., which may use 10 bits), the SSB identifier (e.g., which may use six bits), the half-frame indicator (e.g., which may use one bit), and the search space configuration (e.g., which may use four bits). Similarly, signaling resources in a second or third multiplexing mode (e.g., mode 2 or mode 3) (which may be associated with a fixed start symbol position for each SSB identifier) ​​may involve signaling at least the SSB identifier. Therefore, signaling resources for search space transmission in a relative manner may be beneficial, especially for reducing the overhead associated with the first multiplexing mode.

[0133] According to the examples described herein, an offset of 315 (e.g., a time offset, for example, to UE 115) can be used to indicate the timing of the first search space 305-a (e.g., search space zero (SS0)) corresponding to the first SSB 310-a. In some examples, the offset 315 can indicate the start (e.g., a start symbol) of the timing for the first search space 305-a relative to the start (e.g., a start symbol) of the first SSB 310-a. See reference... Figure 2 As described, offset 315 can be indicated via a PBCH (e.g., a broadcast message) associated with the first SSB 310-a (e.g., or a previous SSB transmission), and offset 315 can be indicated as the number of symbols or another number (e.g., milliseconds). Compared to indicating detailed frame timing, indicating the start of the timing opportunity for the first search space 305-a relative to the first SSB 310-a allows for the use of a relatively small number of bits to indicate the start of the timing opportunity.

[0134] In some cases, offset 315 can be constant across multiple SSB cycles. For example, offset 315 can be configured to be constant across SSB cycles associated with the same SSB identifier (e.g., SSB ID). For example, UE 115 can receive a PBCH via a first SSB 310-a, which can indicate offset 315. Therefore, UE 115 can determine the timing associated with the second search space 305-b relative to the timing for the corresponding second SSB 310-b (e.g., which can be periodically transmitted so that UE 115 knows the timing for the second SSB 310-b). Thus, UE 115 can receive search space transmissions via the second search space 305-b (e.g., second SS0) before the timing for the second SSB 310-b.

[0135] In some examples, if offset 315 remains constant between PBCH transmissions associated with the same SSB identifier, the content of each PBCH transmission can also be the same between PBCH transmissions. Thus, PBCH combination for UE 115 can be simplified relative to combination for PBCH transmissions with varying content, where UE 115 can evaluate different SFN assumptions to perform combination. In some cases, even if PBCH transmissions have different SSB identifiers, offset 315 can remain constant between PBCH transmissions, which can support combining PBCH transmissions with the same MIB associated with the same or different SIB identifiers.

[0136] In some examples, as depicted in signaling diagram 300-a, the offset 315 indicated by the PBCH of the first SSB 310-a may indicate the start of a previous (e.g., last) search space 305 (e.g., the first search space 305-a). In some other examples, the offset 315 may indicate the start of the next search space 305 or the start of the search space 305 that is closest in time to the start (e.g., or end) of the first SSB 310-a.

[0137] Signaling diagram 300-a illustrates an example where the timing for searching space 305 and the corresponding SSB 310 are in the same time slot 320. In some examples, such as when time slot 320 includes 14 symbols (e.g., symbols 0 to 13), four bits may be used (e.g., via a PBCH message) to indicate offset 315. In some cases, if the range of timing that may be used for searching space 305 is limited to a certain number of symbols from the start (e.g., the end) of SSB 310, the number of bits may be further limited. For example, the timing for searching space 305 may be limited to four symbols around the start or end of the corresponding SSB 310, and two bits may be used to indicate offset 315.

[0138] Signaling diagram 300-b illustrates examples of the timing for search space 305-c (e.g., SS0) and the corresponding SSB 310-c in different time slots 320. In these examples, the range of possible symbols between SSB 310-c and search space 305-c can depend on the SCS value. For example, for a 120 kHz SCS, the possible number of symbols between SSB 310-c and search space 305-c can be between one and 2240, which can be signaled using a 12-bit offset 315. This offset 315 can still be signaled using a smaller number of bits compared to (e.g., depending on SFN) an explicit indication of the timing for search space 305-c (which can use 21 bits).

[0139] In some examples, an offset of 315 (e.g., a different offset) can be used to signal the start of the RACH timing, similar to the manner described herein with respect to search space 305. For example, UE 115 may be configured (e.g., via SSB 310) to utilize the RACH timing for sending a request for system information to network entity 105. An offset of 315 relative to SSB 310 can be used to signal the start of the RACH timing in the time domain. In some examples, as referenced... Figure 4 In more detail, the frequency position can be used to signal the timing of RACH based on the frequency offset.

[0140] By using a relative indication of the timing of the search space 305 relative to the corresponding SSB 310, the payload size associated with the PBCH message of SSB 310 can be reduced, thereby reducing transmission overhead and improving SSB reliability.

[0141] Figure 4 An example of a signaling diagram 400 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Signaling diagram 400 illustrates the frequency timing for indicating resource block 410 (e.g., RB, uplink resource block) relative to the corresponding SSB resource block 405, as referenced... Figure 1 and Figure 2 As described.

[0142] In some examples, UE 115 may be configured to request system information from network entity 105 via a RACH timing for UE 115. For example, the RACH timing may occur within at least one of resource block 410-a, resource block 410-b, resource block 410-c, or resource block 410-d (e.g., within an uplink resource block). The RACH timing may be signaled via a corresponding SSB (e.g., via a PBCH message associated with the SSB), which may include one or more SSB resource blocks 405, such as SSB resource blocks 405-a, 405-b, and 405-c.

[0143] In some cases, in order to signal the frequency domain (e.g., frequency resources) of RACH timing, UE 115 may (e.g., via a system information block, such as SIB1) receive indications for the following: a reference point (e.g., point A, via...). absoluteFrequencyPointA Fields), uplink carrier location (e.g., via scs- SpecificCarrierList Fields), initial uplink bandwidth portion location (e.g., via initialUplinkBWP (field) and the start of the RACH timing set (e.g., via) msg1-FrequencyStart (Field). However, this could result in higher downlink overhead at UE 115 or network entity 105. Therefore, a technique for indicating the frequency location of RACH timing may be desired while reducing overhead.

[0144] According to the examples described herein, the frequency position of a RACH timing can be indicated relative to the frequency position of the corresponding SSB. For example, resource block offset 420 (e.g., it may be 4 bits) can be used to indicate the number of resource blocks between resource block 410 (which contains the start of the first RACH timing that is frequency-domain multiplexed) and the start of SSB resource block 405-a (e.g., the start of the corresponding SSB). In some cases, the number of resource blocks can be calculated based on the difference between the identifier associated with resource block 410 (e.g., resource block 410-a) and the identifier associated with the uplink resource block that contains (e.g., shares the frequency with) the start of the first SSB resource block 405 (e.g., resource block 405-a). In the example depicted in signaling diagram 400, resource block offset 420 may be a quantity of two (e.g., two resource blocks), which may be equivalent to the difference between the identifier of resource block 410-a and the identifier of resource block 410-c.

[0145] In some examples, subcarrier offset 415 relative to the corresponding SSB may also be used to indicate the frequency position of the RACH timing. For example, subcarrier offset 415-a (e.g., it may be 4 bits) may be the remaining offset between the frequency position indicated by resource block offset 420 and the start of SSB resource block 405-a. In some examples, subcarrier offset 415-a may be indicated as the number of subcarriers (e.g., subcarriers in the initial uplink bandwidth portion). For example, subcarrier offset 415-a may be the number of subcarriers remaining after subtracting resource block offset 420 from the total offset between the frequency start of the RACH timing and the start of the corresponding SSB.

[0146] In some cases, subcarrier offset 415 can be used to indicate the start of the frequency position of the RACH timing even without a corresponding resource block offset 420. For example, the UE can be indicated with subcarrier offset 415-b, which indicates the total number of subcarriers between the start of the frequency position of the RACH timing and the start of SSB resource block 405-a. In some examples, time offsets can be used to signal the start of the RACH timing in the time domain, as referenced herein. Figure 3A and Figure 3B As described.

[0147] In some examples, the resource block SCS associated with resource block offset 420, the subcarrier SCS associated with subcarrier offset 415, or both can be selected using the uplink initial bandwidth portion SCS, SSB SCS, the smaller of the two, or the larger of the two.

[0148] In some examples, the frequency positions of different channels, transmissions, or reference signals can be signaled in a manner similar to that described herein. For example, network entity 105 may use subcarrier offset 415, resource block offset 420, or both to signal the frequency positions associated with channel state information reference signals (e.g., tracking reference signals for idle UE 115), downlink shared channels (e.g., for broadcasting), uplink control channels (e.g., for feedback, such as for Hybrid Automatic Request (HARQ) acknowledgment (ACK)), uplink shared channels (e.g., for Msg3 / A), or probe reference signals (e.g., for uplink beamfinding prior to RRC connection), and the corresponding frequency positions may be indicated relative to the frequency position of the corresponding SSB (e.g., relative to the start of SSB resource block 405-a).

[0149] Therefore, by indicating the relative frequency positions of various channels or signals to UE 115, information broadcast to UE 115 via PBCH messages or other broadcasts can be reduced. This reduces downlink overhead at network entity 105 and UE 115.

[0150] Figure 5A and Figure 5B Examples of signaling diagrams 500-a and 500-b supporting a scalable PBCH according to one or more aspects of this disclosure are shown. Signaling diagrams 500-a and 500-b illustrate the use of an presence indicator 520 included within PBCH 505 to indicate the presence of an additional PBCH 505, which UE 115 can monitor to obtain additional system information. PBCH 505 may be part of an SSB transmission, which may include a primary synchronization signal 510 (e.g., PSS), a secondary synchronization signal 515 (e.g., SSS), and one or more PBCH 505s.

[0151] In some cases, PBCH 505-a may include system information that UE 115 can use to perform communications via the network. In some examples, PBCH 505-a may include information (e.g., minimum information) to support UE 115's communications within the network. However, additional system information that may be beneficial to UE 115 may be omitted from PBCH 505-a (e.g., due to payload size limitations of PBCH 505-a). For example, PBCH 505-a may include information associated with control resource sets (e.g., CORESET0) and search spaces (e.g., SS0). However, information associated with grid offsets for CD-SSB, information about cell prohibition (e.g., whether the current cell is prohibited for UE 115), information about frequency reselection permission (e.g., whether frequency reselection is allowed), RMSI downlink control channel repetition information, carrier frequency information associated with network entity 105 (e.g., for fast coarse frequency synchronization, for 2-port SSB configuration), or other information may be useful to UE 115. Therefore, it may be beneficial to define a technique for enabling the UE115 to obtain this information while keeping the PBCH 505-a relatively small payload size.

[0152] According to the examples described herein, PBCH 505-a may include an presence indicator 520-a indicating the presence of PBCH 505-b in order to indicate information that may have been omitted from PBCH 505-a. In some cases, PBCH 505-b may include an presence indicator 520-b indicating the presence of PBCH 505-c, and so on. In some examples, the content (e.g., system information) of each PBCH 505 may be defined based on a resource identifier (e.g., resource ID) associated with each PBCH 505. For example, the PBCH 505 with the lowest resource ID (e.g., PBCH 505-a) may include an presence indicator 520 indicating the presence of the PBCH 505 with the next highest resource ID, and so on in ascending order of resource ID. UE 115 can determine the content of each corresponding PBCH 505 based on ascending order (e.g., PBCH 505-a can be associated with control resource set and search space information, PBCH 505-b can be associated with other predetermined information, and so on).

[0153] In some examples, presence indicator 520-a can be indicated to UE 115 via the MIB of PBCH 505-a. Alternatively, presence indicator 520-a can be indicated via a demodulation reference signal associated with PBCH 505-a, and presence indicator 520-a can be encoded separately.

[0154] In some cases, as illustrated with respect to signaling diagram 500-b, presence indicator 520 may indicate resources (e.g., time resources, frequency resources, or both) for subsequent PBCH 505. For example, presence indicator 520-c included within PBCH 505-d may indicate resources for PBCH 505-e. In some examples, resources may be part of a set of candidate resources (e.g., time resources, frequency resources, time-frequency resources), such as resources 525-a, 525-b, 525-c, 525-d, 525-e, and 525-f. For example, presence indicator 520-c may indicate that PBCH 505-e will be transmitted via resource 525-b. PBCH 505-e may indicate that PBCH 505-f will be transmitted via resource 525-e.

[0155] In some examples, the set of candidate resources may be the same across PBCH 505. For example, both presence indicator 520-c and presence indicator 520-d may indicate a resource from one of resources 525-a, 525-b, 525-c, 525-d, 525-e, or 525-f. Alternatively, each PBCH 505 may be configured with different candidate resources. For example, presence indicator 520-c may indicate the resource selected from resources 525-a, 525-b, and 525-c for PBCH 505-e (e.g., indicated via two bits within PBCH 505-d). Then, the presence indicator 520-d can indicate the resource selected from resources 525-a, 525-b, 525-c, 525-d, 525-e, and 525-f for PBCH 505-f (e.g., indicated via 3 bits of PBCH 505-e).

[0156] Additionally or alternatively, resources, transmission parameters, or both can be flexibly scheduled for the next PBCH 505 by the previous PBCH 505. For example, PBCH 505-d may indicate the frequency domain resource allocation (FDRA), time domain resource allocation (e.g., using four bits), modulation and decoding scheme (e.g., using five bits), redundancy version (e.g., using two bits), virtual resource block to physical resource block (VRB to PRB) mapping (e.g., whether VRB to PRB mapping is performed, using one bit), or a combination thereof, associated with PBCH 505-e.

[0157] In some examples, the content associated with a subsequent PBCH 505 can be indicated via a preceding PBCH 505. For example, PBCH 505-a can (e.g., via presence indicator 520-a) indicate a bit value for PBCH 505-b corresponding to content from a set of candidate content. In some examples, the first candidate content can correspond to search space and control resource set information, the second candidate content can be associated with access information, the third candidate content can be associated with RMSI combinations, and the fourth candidate content can be associated with RACH configuration, but other content is also possible.

[0158] In some cases, the candidate content can remain unchanged between PBCH 505. For example, PBCH 505-a can indicate one candidate content from the common set of candidate content for PBCH 505-b, and PBCH 505-b can indicate another candidate content from the common set of candidate content for PBCH 505-c. Alternatively, the candidate content can vary depending on the order in which PBCH 505s are transmitted. For example, PBCH 505-a can be selected from two candidate contents that may be associated with PBCH 505-b (e.g., indicated using one bit), and PBCH 505-b can be selected from eight candidate contents that may be associated with PBCH 505-c (e.g., indicated using three bits).

[0159] Additionally or alternatively, the individual elements (e.g., information, fields) included in PBCH 505 can be flexibly scheduled by the prior PBCH 505. For example, PBCH 505-a can indicate a bitmap that indicates the presence of a specific element (e.g., information, field, or other element) to be indicated by PBCH 505-b.

[0160] Therefore, by indicating the presence of subsequent PBCH 505 in the preceding PBCH 505, the payload size of PBCH 505 can be reduced, which can improve the reliability of PBCH 505 transmission.

[0161] Figure 6 An example of a process flow 600 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Process flow 600 illustrates communication between a UE 115-c and a network entity 105-b, which may be as referenced herein. Figures 1 to 5B Examples of corresponding devices described. In some examples, additional steps may be added to process flow 600, or the steps depicted may be omitted. Additionally or alternatively, the steps shown in process flow 600 may be performed in a different order.

[0162] At 605, network entity 105-b may send a first broadcast channel message (e.g., PBCH) to UE 115-c as part of an SSB transmission. The first broadcast channel message may include a time offset (e.g., indicating one or more symbols) for identifying the time timing used for the space search relative to the time timing used for the corresponding SSB. For example, the time timing used for the space search may be indicated as a symbol offset relative to the next SSB transmission, a previous SSB transmission, the SSB transmission closest in time to that time timing, or the current SSB transmission.

[0163] At 610, UE 115-c can identify the time offset indicated in the first broadcast channel message. UE 115-c can determine the timing for searching the space for transmission based on the time offset.

[0164] At 615, UE 115-c can monitor the search space during a time-opportune period based on the time offset. Network entity 105-b can perform search space transmissions (e.g., SS0 transmissions) via the search space, and UE 115-c can receive search space transmissions based on the monitoring of the search space.

[0165] At 620, UE 115-c may identify the frequency offset indicated by network entity 105-b via a first broadcast channel message. The frequency offset may indicate the frequency position of the RACH timing relative to the frequency position associated with the SSB transmission. In some examples, the frequency offset may include a subcarrier offset indicating the number of subcarriers between the start of the frequency position of the RACH timing and the start of the frequency position of the SSB transmission. Additionally or alternatively, the frequency offset may include a resource block offset indicating the number of resource blocks between the start of the frequency position of the RACH timing and the start of the frequency position of the SSB transmission.

[0166] At 625, UE 115-c may optionally send a request for system information via RACH timing based on frequency offset. At 630, network entity 105-b may send a message indicating the requested system information based on receiving the request for system information from UE 115-c.

[0167] At 635, UE 115-c may optionally identify an presence indicator included in the first broadcast channel message. The presence indicator may indicate the presence of a second broadcast channel message to be sent by network entity 105-b. In some examples, the presence indicator may indicate resources (e.g., time resources, frequency resources, or both) used for the second broadcast channel message, content associated with the second broadcast channel message (e.g., a set of candidate content from the second broadcast channel message), or both.

[0168] At 640, UE 115-c can receive a second broadcast channel message based on a presence indicator. The second broadcast channel message can indicate additional system information that may have been omitted from the first broadcast channel message, thereby supporting a reduction in the payload size associated with the broadcast channel message. Therefore, broadcast channel overhead can be reduced, thereby improving the reliability of SSB transmission and reducing the power consumption of UE 115-c and network entity 105-b.

[0169] Figure 7A block diagram 700 of a device 705 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Device 705 may be an example of various aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0170] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Scalable PBCH). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0171] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with Scalable PBCH), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0172] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the scalable PBCH as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0173] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0174] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0175] In some examples, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated in combination with the receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0176] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving an SSB including a PBCH message during a first time window, the PBCH message indicating a time offset relative to the start of the SSB that identifies the beginning of the search space. The communication manager 720 may be capable of, configured to, or operable to support components for monitoring search space transmissions via the search space during a second time window corresponding to the time offset indicated in the PBCH message. The communication manager 720 may be capable of, configured to, or operable to support components for receiving search space transmissions via the second time window.

[0177] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource used for a random access opportunity. The communication manager 720 may be capable of, configured to, or operable to support components for transmitting a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The communication manager 720 may be capable of, configured to, or operable to support components for receiving a message indicating system information based on a transmission request.

[0178] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving an SSB including a first PBCH message that includes an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The communication manager 720 may be capable of, configured to, or operable to support components for receiving the second PBCH message based on the presence indicator. The communication manager 720 may be capable of, configured to, or operable to support components for communicating one or more messages with a network entity based on the first PBCH message and the second PBCH message.

[0179] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor otherwise coupled thereto) can support techniques to reduce the overhead associated with SSB transmission by implementing time offset, frequency offset and presence indicator, which can improve the reliability of SSB transmission and reduce the power consumption of the device.

[0180] Figure 8A block diagram 800 of a device 805 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Scalable PBCH). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0182] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with Scalable PBCH), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0183] Device 805 or its various components may be examples of parts used to perform various aspects of the scalable PBCH as described herein. For example, communication manager 820 may include broadcast manager 825, time offset manager 830, search space component 835, frequency offset manager 840, system information component 845, presence indicator manager 850, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0184] Communication manager 820 may support wireless communication according to examples disclosed herein. Broadcast manager 825 is capable of, configured to, or operable to support components for receiving an SSB including a PBCH message during a first time window, the PBCH message indicating a time offset relative to the start of the SSB that identifies the beginning of the search space. Time offset manager 830 is capable of, configured to, or operable to support components for monitoring search space transmissions via the search space during a second time window corresponding to the time offset indicated in the PBCH message. Search space component 835 is capable of, configured to, or operable to support components for receiving search space transmissions via the second time window.

[0185] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. The broadcast manager 825 is capable of, configured to, or operable to support components for receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource used for a random access opportunity. The frequency offset manager 840 is capable of, configured to, or operable to support components for transmitting a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The system information component 845 is capable of, configured to, or operable to support components for receiving a message indicating system information based on a transmission request.

[0186] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. The broadcast manager 825 is capable of, configured to, or operable to support components for receiving an SSB including a first PBCH message, the first PBCH message including an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The presence indicator manager 850 is capable of, configured to, or operable to support components for receiving the second PBCH message based on the presence indicator. The broadcast manager 825 is capable of, configured to, or operable to support components for communicating one or more messages to network entities based on the first PBCH message and the second PBCH message.

[0187] Figure 9A block diagram 900 is shown of a communication manager 920 supporting a scalable PBCH according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of the scalable PBCH as described herein. For example, the communication manager 920 may include a broadcast manager 925, a time offset manager 930, a search space component 935, a frequency offset manager 940, a system information component 945, a presence indicator manager 950, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0188] Communication manager 920 may support wireless communication according to examples disclosed herein. Broadcast manager 925 is capable of, configured to, or operable to support components for receiving an SSB including a PBCH message during a first time window, the PBCH message indicating a time offset relative to the start of the SSB that identifies the beginning of the search space. Time offset manager 930 is capable of, configured to, or operable to support components for monitoring search space transmissions via the search space during a second time window corresponding to the time offset indicated in the PBCH message. Search space component 935 is capable of, configured to, or operable to support components for receiving search space transmissions via the second time window.

[0189] In some examples, the broadcast manager 925 is capable of, configured to, or able to operate to support components for receiving a second SSB that includes a second PBCH message, the first identifier of which is the same as the second identifier of the second SSB, wherein the payload of the second PBCH message is the same as the payload of the PBCH message.

[0190] In some examples, the broadcast manager 925 is capable of, configured to, or operable to support components for receiving first data included in a PBCH message and second data included in a second PBCH message. In some examples, the broadcast manager 925 is capable of, configured to, or operable to support components for combining the first and second data to obtain the payload of the PBCH message, wherein the monitoring search space transmits a payload based on the PBCH message.

[0191] In some examples, the time offset indicates one or more symbols between the start of the search space transmission and the start of the synchronization block. In some examples, the start of the search space transmission and the start of the synchronization block occur within the same time slot. In some examples, the time offset is indicated via at least four bits of the PBCH message.

[0192] In some examples, the time offset relative to the start of the SSB identifies the start of a previous search space transmission. In some examples, the time offset relative to the start of the SSB identifies the start of an upcoming search space transmission. In some examples, the time offset identifies the start of the search space transmission that is closest to the start of the SSB in the time domain.

[0193] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. In some examples, the broadcast manager 925 is capable of, configured to, or operable to support components for receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource for a random access opportunity. The frequency offset manager 940 is capable of, configured to, or operable to support components for transmitting a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The system information component 945 is capable of, configured to, or operable to support components for receiving a message indicating system information based on a transmission request. In some examples, the frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of the first frequency resource and the start of the second frequency resource.

[0194] In some examples, the frequency offset also includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource. In some examples, the subcarrier offset indicates the number of subcarriers between that number of uplink resource blocks and the start of the second frequency resource.

[0195] In some examples, the resource block offset indicates the difference between the resource block identifier of the first uplink resource block and the resource block identifier of the second uplink resource block. In some examples, the first uplink resource block includes the start of a first frequency resource, and the second uplink resource block includes the start of a second frequency resource.

[0196] In some examples, the resource block offset is indicated by a first set of bits in the PBCH message, and the subcarrier offset is indicated by a second set of bits in the PBCH message, which follows the first set of bits.

[0197] In some examples, the frequency offset is based on a first SCS (Self-Content Class of Components) associated with the uplink bandwidth portion of the random access opportunity, or a second SCS associated with the SSB (Self-Content Class of Components). In other examples, the frequency offset is based on the larger of the first SCS and the second SCS, or the smaller of the first SCS and the second SCS.

[0198] In some examples, in order to support the reception of SSBs, the time offset manager 930 is capable of, can be configured to, or is able to operate to support components for receiving SSBs, including PBCH messages. The physical broadcast channel messages also indicate a time offset relative to the start of the SSB to identify the start of the random access opportunity, wherein the transmission request is based on the time offset.

[0199] In some examples, the PBCH message also indicates one or more additional frequency offsets, each of which identifies a corresponding frequency resource relative to a second frequency resource. In some examples, each corresponding frequency resource corresponds to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0200] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. In some examples, the broadcast manager 925 is capable of, configured to, or operable to support components for receiving an SSB including a first PBCH message that includes an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The presence indicator manager 950 is capable of, configured to, or operable to support components for receiving the second PBCH message based on the presence indicator. In some examples, the broadcast manager 925 is capable of, configured to, or operable to support components for communicating one or more messages to a network entity based on the first PBCH message and the second PBCH message.

[0201] In some examples, the value of the first identifier associated with the first PBCH message is less than the value of the second identifier associated with the second PBCH message.

[0202] In some examples, the first PBCH message includes a master information block that includes an presence indicator. In some examples, the first PBCH message includes a demodulation reference signal that includes an presence indicator.

[0203] In some examples, in order to support the reception of a second PBCH message, the presence indicator manager 950 is capable, configured, or operable to support components for receiving a second PBCH message including a second presence indicator that indicates the presence of a third PBCH message.

[0204] In some examples, the Presence Indicator Manager 950 is capable of, configured to, or able to operate to support components for receiving a third PBCH message based on a second Presence Indicator, wherein one or more messages are communicated with a network entity based on the receipt of the third PBCH message.

[0205] In some examples, the presence indicator also indicates the resource used to receive the second PBCH message. In some examples, the resource is selected from a set of candidate resources associated with the first PBCH message.

[0206] In some examples, the indicated resources include: frequency domain resource assignments, time domain resource assignments, modulation and decoding schemes, redundant versions, virtual resource block to physical resource block mappings, or combinations thereof, that are associated with the resources.

[0207] In some examples, the presence indicator also indicates the content associated with the second PBCH message. In some examples, the content is selected from a set of candidate content associated with the second PBCH message.

[0208] Figure 10 A diagram of a system 1000 including a device 1005 supporting a scalable PBCH, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1045).

[0209] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ®Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of one or more processors, such as at least one processor 1040. In some cases, a user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0210] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 as described herein, or via a wired or wireless link. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0211] At least one memory 1030 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1030 may store computer-readable, computer-executable (e.g., processor-executable) code 1035, including instructions that, when executed by at least one processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by at least one processor 1040, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0212] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., supporting scalable PBCH functions or tasks). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, wherein at least one processor 1040 and at least one memory 1030 are configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a machine (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or system of components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” may be used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1030 or otherwise.

[0213] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be, configured to, or operable to support components for receiving an SSB including a PBCH message during a first time window, the PBCH message indicating a time offset relative to the start of the SSB that identifies the beginning of the search space. The communication manager 1020 may be, configured to, or operable to support components for monitoring search space transmissions via the search space during a second time window corresponding to the time offset indicated in the PBCH message. The communication manager 1020 may be, configured to, or operable to support components for receiving search space transmissions via the second time window.

[0214] Additionally or alternatively, the communication manager 1020 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource for a random access opportunity. The communication manager 1020 may be capable of, configured to, or operable to support components for transmitting a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving a message indicating system information based on a transmission request.

[0215] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving an SSB including a first PBCH message, the first PBCH message including an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving the second PBCH message based on the presence indicator. The communication manager 1020 may be capable of, configured to, or operable to support components for communicating one or more messages with a network entity based on the first PBCH message and the second PBCH message.

[0216] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for reducing the overhead associated with SSB transmission by implementing time offsets, frequency offsets, and presence indicators, which can improve the reliability of SSB transmission and reduce the power consumption of the device.

[0217] In some examples, the communication manager 1020 may be configured to use or otherwise coordinate with the transceiver 1015, one or more antennas 1025, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by at least one processor 1040 to cause the device 1005 to perform various aspects of the scalable PBCH as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0218] Figure 11 A block diagram 1100 of a device 1105 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0219] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0220] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0221] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the scalable PBCH as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0222] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0223] Additionally or alternatively, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0224] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0225] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of a search space transmission. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0226] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for outputting an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource used for a random access opportunity. The communication manager 1120 may be capable of, configured to, or operable to support components for requesting system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting a message indicating system information based on a transmission request.

[0227] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting a second PBCH message based on the presence indicator. The communication manager 1120 may be capable of, configured to, or operable to support components for communicating one or more messages to the UE based on the first PBCH message and the second PBCH message.

[0228] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof, or at least one processor otherwise coupled thereto) can support techniques to reduce the overhead associated with SSB transmission by implementing time offsets, frequency offsets, and presence indicators, which can improve the reliability of SSB transmission and reduce the power consumption of the device.

[0229] Figure 12 A block diagram 1200 of a device 1205 supporting a scalable PBCH according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. Device 1205, or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220), may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0230] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0231] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0232] Device 1205 or its various components may be examples of parts used to perform various aspects of the scalable PBCH as described herein. For example, communication manager 1220 may include broadcast component 1225, time offset component 1230, frequency offset component 1235, system information component 1240, presence indicator component 1245, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0233] Communication manager 1220 may support wireless communication according to examples disclosed herein. Broadcast component 1225 is capable of, configured to, or operable to support components for outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the search space transmission. Time offset component 1230 is capable of, configured to, or operable to support components for outputting a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0234] Additionally or alternatively, the communication manager 1220 may support wireless communication according to examples disclosed herein. The broadcast component 1225 is capable of, configured to, or operable to support components for outputting an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource used for a random access opportunity. The frequency offset component 1235 is capable of, configured to, or operable to support components for obtaining a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The system information component 1240 is capable of, configured to, or operable to support components for outputting a message indicating system information based on a transmission request.

[0235] Additionally or alternatively, the communication manager 1220 may support wireless communication according to examples disclosed herein. The broadcast component 1225 is capable of, configured to, or operable to support components for outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The presence indicator component 1245 is capable of, configured to, or operable to support components for outputting a second PBCH message based on the presence indicator. The broadcast component 1225 is capable of, configured to, or operable to support components for communicating one or more messages to the UE based on the first PBCH message and the second PBCH message.

[0236] Figure 13 A block diagram 1300 is shown of a communication manager 1320 supporting a scalable PBCH according to one or more aspects of this disclosure. The communication manager 1320 may be an example of a communication manager 1120, a communication manager 1220, or aspects thereof as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of the scalable PBCH as described herein. For example, the communication manager 1320 may include a broadcast component 1325, a time offset component 1330, a frequency offset component 1335, a system information component 1340, a presence indicator component 1345, an identifier component 1350, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0237] Communication manager 1320 may support wireless communication according to examples disclosed herein. Broadcast component 1325 is capable of, configured to, or operable to support components for outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the search space transmission. Time offset component 1330 is capable of, configured to, or operable to support components for outputting a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0238] In some examples, the identifier component 1350 is capable of, configured to, or able to operate to support components for outputting a second SSB including a second PBCH message, wherein the first identifier of the SSB is the same as the second identifier of the second SSB, and the payload of the second PBCH message is the same as the payload of the PBCH message.

[0239] In some examples, the time offset indicates one or more symbols between the start of the search space transmission and the start of the synchronization block. In some examples, the start of the search space transmission and the start of the synchronization block occur within the same time slot. In some examples, the time offset is indicated via at least four bits of the PBCH message.

[0240] In some examples, the time offset relative to the start of the SSB identifies the start of a previous search space transmission. In some examples, the time offset relative to the start of the SSB identifies the start of an upcoming search space transmission. In some examples, the time offset identifies the start of the search space transmission that is closest to the start of the SSB in the time domain.

[0241] Additionally or alternatively, the communication manager 1320 may support wireless communication according to examples disclosed herein. In some examples, the broadcast component 1325 is capable of, configured to, or operable to support components for outputting an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource for a random access opportunity. The frequency offset component 1335 is capable of, configured to, or operable to support components for obtaining a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The system information component 1340 is capable of, configured to, or operable to support components for outputting a message indicating system information based on a transmission request.

[0242] In some examples, the frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of the first frequency resource and the start of the second frequency resource.

[0243] In some examples, the frequency offset also includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource. In some examples, the subcarrier offset indicates the number of subcarriers between that number of uplink resource blocks and the start of the second frequency resource.

[0244] In some examples, the resource block offset indicates the difference between the resource block identifier of the first uplink resource block and the resource block identifier of the second uplink resource block. In some examples, the first uplink resource block includes the start of a first frequency resource, and the second uplink resource block includes the start of a second frequency resource.

[0245] In some examples, the resource block offset is indicated by a first set of bits in the PBCH message, and the subcarrier offset is indicated by a second set of bits in the PBCH message, which follows the first set of bits.

[0246] In some examples, the frequency offset is based on a first SCS (Self-Content Class of Components) associated with the uplink bandwidth portion of the random access opportunity, or a second SCS associated with the SSB (Self-Content Class of Components). In other examples, the frequency offset is based on the larger of the first SCS and the second SCS, or the smaller of the first SCS and the second SCS.

[0247] In some examples, in order to support the transmission of SSBs, the time offset component 1330 is capable of being configured or can operate to support components for outputting SSBs including PBCH messages. The physical broadcast channel message also indicates a time offset relative to the start of the SSB to identify the start of the random access opportunity, wherein the transmission request is based on the time offset.

[0248] In some examples, the PBCH message also indicates one or more additional frequency offsets, each of which identifies a corresponding frequency resource relative to a second frequency resource. In some examples, each corresponding frequency resource corresponds to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0249] Additionally or alternatively, the communication manager 1320 may support wireless communication according to examples disclosed herein. In some examples, the broadcast component 1325 is capable of, configured to, or operable to support components for outputting an SSB including a first PBCH message that includes a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The presence indicator component 1345 is capable of, configured to, or operable to support components for outputting a second PBCH message based on the presence indicator. In some examples, the broadcast component 1325 is capable of, configured to, or operable to support components for communicating one or more messages to the UE based on the first PBCH message and the second PBCH message. In some examples, the value of a first identifier associated with the first PBCH message is less than the value of a second identifier associated with the second PBCH message.

[0250] In some examples, the first PBCH message includes a master information block that includes an presence indicator. In some examples, the first PBCH message includes a demodulation reference signal that includes an presence indicator.

[0251] In some examples, in order to support the output of a second PBCH message, the presence indicator component 1345 is capable of, configured to, or operable to support components for outputting a second PBCH message including a second presence indicator that indicates the presence of a third PBCH message.

[0252] In some examples, the presence indicator component 1345 is capable of, configured to, or able to operate to support components for outputting a third PBCH message based on a second presence indicator, wherein one or more messages are communicated with a network entity based on the receipt of the third PBCH message.

[0253] In some examples, the presence indicator also indicates the resource used to receive the second PBCH message. In some examples, the resource is selected from a set of candidate resources associated with the first PBCH message.

[0254] In some examples, the indicated resources include: frequency domain resource assignments, time domain resource assignments, modulation and decoding schemes, redundant versions, virtual resource block to physical resource block mappings, or combinations thereof, that are associated with the resources.

[0255] In some examples, the presence indicator also indicates the content associated with the second PBCH message. In some examples, the content is selected from a set of candidate content associated with the second PBCH message.

[0256] Figure 14A diagram of a system 1400 including a device 1405 supporting a scalable PBCH, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and enabling communication, such as a communication manager 1420, a transceiver 1410, an antenna 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

[0257] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0258] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable, computer-executable (e.g., processor-executable) code 1430 including instructions that, when executed by one or more processors of at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by a processor of at least one processor 1435, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may also include a BIOS, which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0259] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting a scalable PBCH). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more processors in at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1435 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1435) and memory circuitry (which may include at least one memory 1425)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1435 or a processing system including at least one processor 1435 may be configured, configured to be configured to, or be operable to cause the device 1405 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1425 or otherwise.

[0260] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

[0261] In some examples, the communication manager 1420 may manage aspects of communication with the core network 130, such as via one or more wired or wireless backhaul links. For example, the communication manager 1420 may manage the transfer of data communication with client devices, such as one or more UEs 115. In some examples, the communication manager 1420 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1420 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0262] The communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of a search space transmission. The communication manager 1420 may be capable of, configured to, or operable to support components for outputting a search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0263] Additionally or alternatively, the communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting an SSB including a PBCH message indicating a frequency offset relative to a second frequency resource for the SSB, identifying a first frequency resource for a random access opportunity. The communication manager 1420 may be capable of, configured to, or operable to support components for obtaining a request for system information via a first frequency resource corresponding to the frequency offset indicated in the PBCH message. The communication manager 1420 may be capable of, configured to, or operable to support components for outputting a message indicating system information based on a transmission request.

[0264] Additionally or alternatively, the communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message. The communication manager 1420 may be capable of, configured to, or operable to support components for outputting a second PBCH message based on the presence indicator. The communication manager 1420 may be capable of, configured to, or operable to support components for communicating one or more messages to the UE based on the first PBCH message and the second PBCH message.

[0265] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for reducing the overhead associated with SSB transmission by implementing time offsets, frequency offsets, and presence indicators, which can improve the reliability of SSB transmission and reduce the power consumption of the device.

[0266] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by one or more processors in at least one processor 1435 to cause the device 1405 to perform various aspects of the scalable PBCH as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0267] Figure 15 A flowchart illustrating a method 1500 for supporting a scalable PBCH according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0268] At 1505, the method may include receiving a synchronization signal block including a physical broadcast channel message during a first timing period, the physical broadcast channel message indicating a time offset relative to the start of the synchronization signal block to identify the start of the search space. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 9 The described broadcast manager 925 is used to execute this.

[0269] At 1510, the method may include monitoring search space transmissions via the search space during a second time timing corresponding to a time offset indicated in the physical broadcast channel message. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be derived from references... Figure 9 The described time offset manager 930 is used to perform this.

[0270] At 1515, the method may include receiving a search space transmission via a second time opportunity. The operation of block 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 9 The search space component 935 described is used to perform this.

[0271] Figure 16 A flowchart illustrating a method 1600 supporting a scalable PBCH according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0272] At 1605, the method may include receiving a synchronization signal block including a physical broadcast channel message indicating a frequency offset relative to a second frequency resource used for the synchronization signal block to identify a first frequency resource for random access timing. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 9 The described broadcast manager 925 is used to execute this.

[0273] At 1610, the method may include transmitting a request for system information via a first frequency resource corresponding to a frequency offset indicated in the physical broadcast channel message. The operation of block 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 9 The frequency offset manager 940 described is used to perform this.

[0274] At 1615, the method may include receiving a message indicating system information, at least in part, based on a sending request. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 9 The system information component 945 described is used to perform this.

[0275] Figure 17 A flowchart illustrating a method 1700 supporting a scalable PBCH according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be achieved by, as referenced... Figures 1 to 10The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0276] At 1705, the method may include receiving a synchronization signal block including a first physical broadcast channel message, the first physical broadcast channel message including an presence indicator indicating the presence of a second physical broadcast channel message associated with the first physical broadcast channel message. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be derived from references... Figure 9 The described broadcast manager 925 is used to execute this.

[0277] At 1710, the method may include receiving a second physical broadcast channel message based at least in part on an presence indicator. The operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 9 The described Existence Indicator Manager 950 is used to execute this.

[0278] At 1715, the method may include communicating one or more messages to a network entity based at least in part on a first physical broadcast channel message and a second physical broadcast channel message. The operation of block 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 9 The described broadcast manager 925 is used to execute this.

[0279] Figure 18 A flowchart illustrating a method 1800 supporting a scalable PBCH according to various aspects of this disclosure is shown. The operation of method 1800 can be implemented by a network entity or its components as described herein. For example, the operation of method 1800 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0280] At 1805, the method may include outputting a synchronization signal block during a first timing period, comprising a physical broadcast channel message indicating a time offset relative to the start of the search space transmission. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The broadcast component 1325 described herein shall be used to perform this action.

[0281] At 1810, the method may include outputting a search space transmission during a second time opportunity corresponding to the time offset indicated in the physical broadcast channel message. The operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 13 The described time offset component 1330 is used for execution.

[0282] Figure 19 A flowchart illustrating a method 1900 supporting a scalable PBCH according to various aspects of this disclosure is shown. The operation of method 1900 can be implemented by a network entity or its components as described herein. For example, the operation of method 1900 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0283] At 1905, the method may include outputting a synchronization signal block comprising a physical broadcast channel message indicating a frequency offset relative to a second frequency resource used for the synchronization signal block to identify a first frequency resource for random access timing. Operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to [reference needed]. Figure 13 The broadcast component 1325 described herein shall be used to perform this action.

[0284] At 1910, the method may include obtaining a request for system information via a first frequency resource corresponding to a frequency offset indicated in the physical broadcast channel message. The operation of block 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to [reference needed]. Figure 13 The frequency offset component 1335 described herein is used to perform this action.

[0285] At 1915, the method may include outputting a message indicating system information based on a sending request. The operation of block 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be provided by reference to [reference needed]. Figure 13 The system information component 1340 described herein shall be used to execute this.

[0286] Figure 20 A flowchart illustrating a method 2000 for supporting scalable physical broadcast channels according to various aspects of this disclosure is shown. The operation of method 2000 may be implemented by a network entity or its components as described herein. For example, the operation of method 2000 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0287] At 2005, the method may include outputting a synchronization signal block comprising a first physical broadcast channel message, the first physical broadcast channel message including an presence indicator indicating the presence of a second physical broadcast channel message associated with the first physical broadcast channel message. The operation of block 2005 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2005 may be provided by reference to [reference needed]. Figure 13 The broadcast component 1325 described herein shall be used to perform this action.

[0288] At 2010, the method may include outputting a second physical broadcast channel message based on an presence indicator. The operation of block 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2010 may be provided by reference to [reference needed]. Figure 13 The described presence indicator component 1345 is used for execution.

[0289] At 2015, the method may include communicating one or more messages to the UE based on a first physical broadcast channel message and a second physical broadcast channel message. The operation of block 2015 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2015 may be provided by reference to [reference needed]. Figure 13 The broadcast component 1325 described herein shall be used to perform this action.

[0290] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a user equipment, the method comprising: receiving an SSB including a PBCH message during a first time timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of a search space; monitoring search space transmissions via the search space during a second time timing period corresponding to the time offset indicated in the PBCH message; and receiving the search space transmissions via the second time timing period.

[0291] Aspect 2: According to the method of aspect 1, the method further includes: receiving a second SSB including a second PBCH message, wherein a first identifier of the SSB is the same as a second identifier of the second SSB, and wherein the payload of the second PBCH message is the same as the payload of the PBCH message.

[0292] Aspect 3: According to the method of aspect 2, the method further includes: receiving first data included in the PBCH message and second data included in a second PBCH message; and combining the first data and the second data to obtain the payload of the PBCH message, wherein the search space is monitored to transmit the payload at least in part based on the PBCH message.

[0293] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the time offset indicates one or more symbols between the start of the search space transmission and the start of the SSB.

[0294] Aspect 5: According to the method of aspect 4, wherein the start of the search space transmission and the start of the SSB occur in the same time slot, and the time offset is indicated by at least four bits of the PBCH message.

[0295] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the time offset is used to identify the start of a previous search space transmission relative to the start of the SSB.

[0296] Aspect 7: The method according to any one of Aspects 1 to 5, wherein the time offset is used to identify the start of an upcoming search space transmission relative to the start of the SSB.

[0297] Aspect 8: The method according to any one of Aspects 1 to 5, wherein the time offset identifier is the start sent in the search space closest to the start of the SSB in the time domain.

[0298] Aspect 9: A method for wireless communication by user equipment, the method comprising: receiving an SSB including a PBCH message, the PBCH message indicating a frequency offset relative to a second frequency resource for identifying a random access opportunity; transmitting a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and receiving a message indicating the system information based at least in part on transmitting the request.

[0299] Aspect 10: According to the method of aspect 9, the frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of the first frequency resource and the start of the second frequency resource.

[0300] Aspect 11: According to the method of aspect 10, the frequency offset further includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource; and the subcarrier offset indicates the number of subcarriers between the number of uplink resource blocks and the start of the second frequency resource.

[0301] Aspect 12: According to the method of aspect 11, wherein the resource block offset indicates the difference between the resource block identifier of the first uplink resource block and the resource block identifier of the second uplink resource block, and the first uplink resource block includes the start of the first frequency resource, and the second uplink resource block includes the start of the second frequency resource.

[0302] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the resource block offset is indicated by a first set of bits of the PBCH message, and the subcarrier offset is indicated by a second set of bits of the PBCH message, the second set of bits following the first set of bits.

[0303] Aspect 14: The method according to any one of Aspects 9 to 13, wherein the frequency offset is based at least in part on a first subcarrier spacing of an uplink bandwidth portion associated with the random access timing or a second subcarrier spacing associated with the SSB.

[0304] Aspect 15: The method according to aspect 14, wherein the frequency offset is based at least in part on the larger of the first subcarrier spacing and the second subcarrier spacing or the smaller of the first subcarrier spacing and the second subcarrier spacing.

[0305] Aspect 16: The method according to any one of Aspects 9 to 15, wherein receiving the SSB further comprises: receiving the SSB including the PBCH message, the PBCH message further indicating a time offset relative to the start of the SSB to identify the start of the random access timing, wherein sending the request is based at least in part on the time offset.

[0306] Aspect 17: The method according to any one of Aspects 9 to 16, wherein the PBCH message further indicates one or more additional frequency offsets, each of the one or more additional frequency offsets identifying a corresponding frequency resource relative to the second frequency resource, and each corresponding frequency resource corresponding to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0307] Aspect 18: A method for wireless communication by a user equipment, the method comprising: receiving an SSB including a first PBCH message, the first PBCH message including an presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; receiving the second PBCH message at least in part based on the presence indicator; and communicating one or more messages to a network entity at least in part based on the first PBCH message and the second PBCH message.

[0308] Aspect 19: According to the method of aspect 18, the value of the first identifier associated with the first PBCH message is less than the value of the second identifier associated with the second PBCH message.

[0309] Aspect 20: The method according to any one of Aspects 18 to 19, wherein the first PBCH message includes a master information block, the master information block including the presence indicator.

[0310] Aspect 21: The method according to any one of Aspects 18 to 19, wherein the first PBCH message includes a demodulation reference signal, the demodulation reference signal including the presence indicator.

[0311] Aspect 22: The method according to any one of aspects 18 to 21, wherein receiving the second PBCH message further comprises: receiving the second PBCH message including a second presence indicator, the second presence indicator indicating the presence of a third PBCH message.

[0312] Aspect 23: The method according to aspect 22, the method further comprising: receiving the third PBCH message at least in part based on the second presence indicator, wherein the communication of the one or more messages with the network entity is at least in part based on receiving the third PBCH message.

[0313] Aspect 24: The method according to any one of aspects 18 to 23, wherein the presence indicator further indicates a resource for receiving the second PBCH message.

[0314] Aspect 25: According to the method of aspect 24, wherein the resource is selected from a set of candidate resources associated with the first PBCH message.

[0315] Aspect 26: The method according to any one of Aspects 24 to 25, wherein indicating the resource includes: indicating frequency domain resource assignment, time domain resource assignment, modulation and decoding scheme, redundancy version, virtual resource block to physical resource block mapping, or a combination thereof associated with the resource.

[0316] Aspect 27: The method according to any one of aspects 18 to 26, wherein the presence indicator further indicates content associated with the second PBCH message.

[0317] Aspect 28: According to the method of aspect 27, the content is selected from a set of candidate content associated with the second PBCH message.

[0318] Aspect 29: A method for wireless communication by a network entity, the method comprising: outputting an SSB including a PBCH message during a first timing period, the PBCH message indicating a time offset relative to the start of the SSB to identify the start of a search space transmission; and outputting the search space transmission during a second timing period corresponding to the time offset indicated in the PBCH message.

[0319] Aspect 30: According to the method of aspect 29, the method further includes: outputting a second SSB including a second PBCH message, wherein a first identifier of the SSB is the same as a second identifier of the second SSB, and wherein the payload of the second PBCH message is the same as the payload of the PBCH message.

[0320] Aspect 31: The method according to any one of Aspects 29 to 30, wherein the time offset indicates one or more symbols between the start of the search space and the start of the SSB.

[0321] Aspect 32: According to the method of aspect 31, wherein the start of the search space transmission and the start of the SSB occur in the same time slot, and the time offset is indicated by at least four bits of the PBCH message.

[0322] Aspect 33: The method according to any one of aspects 29 to 32, wherein the time offset is used to identify the start of a previous search space transmission relative to the start of the SSB.

[0323] Aspect 34: The method according to any one of Aspects 29 to 32, wherein the time offset is used to identify the start of an upcoming search space transmission relative to the start of the SSB.

[0324] Aspect 35: The method according to any one of Aspects 29 to 32, wherein the time offset identifies the start of the search space transmission closest to the start of the SSB in the time domain.

[0325] Aspect 36: A method for wireless communication by a network entity, the method comprising: outputting an SSB including a PBCH message, the PBCH message indicating a frequency offset relative to a second frequency resource for identifying a random access opportunity; obtaining a request for system information via the first frequency resource corresponding to the frequency offset indicated in the PBCH message; and outputting a message indicating the system information based at least in part on sending the request.

[0326] Aspect 37: According to the method of aspect 36, the frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of the first frequency resource and the start of the second frequency resource.

[0327] Aspect 38: According to the method of aspect 37, the frequency offset further includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource; and the subcarrier offset indicates the number of subcarriers between the number of uplink resource blocks and the start of the second frequency resource.

[0328] Aspect 39: According to the method of aspect 38, wherein the resource block offset indicates the difference between the resource block identifier of the first uplink resource block and the resource block identifier of the second uplink resource block, and the first uplink resource block includes the start of the first frequency resource, and the second uplink resource block includes the start of the second frequency resource.

[0329] Aspect 40: The method according to any one of Aspects 38 to 39, wherein the resource block offset is indicated by a first set of bits of the PBCH message, and the subcarrier offset is indicated by a second set of bits of the PBCH message, the second set of bits following the first set of bits.

[0330] Aspect 41: The method according to any one of Aspects 36 to 40, wherein the frequency offset is based at least in part on a first subcarrier spacing of an uplink bandwidth portion associated with the random access timing or a second subcarrier spacing associated with the SSB.

[0331] Aspect 42: According to the method of aspect 41, the frequency offset is at least partially based on the larger of the first subcarrier spacing and the second subcarrier spacing or the smaller of the first subcarrier spacing and the second subcarrier spacing.

[0332] Aspect 43: The method according to any one of Aspects 36 to 42, wherein sending the SSB further comprises: outputting the SSB including the PBCH message, the PBCH message further indicating a time offset relative to the start of the SSB to identify the start of the random access timing, wherein sending the request is based at least in part on the time offset.

[0333] Aspect 44: The method according to any one of Aspects 36 to 43, wherein the PBCH message further indicates one or more additional frequency offsets, each of the one or more additional frequency offsets identifying a corresponding frequency resource relative to the second frequency resource, and each corresponding frequency resource corresponding to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

[0334] Aspect 45: A method for wireless communication by a network entity, the method comprising: outputting an SSB including a first PBCH message, the first PBCH message including a presence indicator indicating the presence of a second PBCH message associated with the first PBCH message; outputting the second PBCH message at least in part based on the presence indicator; and conveying one or more messages to a UE at least in part based on the first PBCH message and the second PBCH message.

[0335] Aspect 46: According to the method of aspect 45, the value of the first identifier associated with the first PBCH message is less than the value of the second identifier associated with the second PBCH message.

[0336] Aspect 47: The method according to any one of Aspects 45 to 46, wherein the first PBCH message includes a master information block, the master information block including the presence indicator.

[0337] Aspect 48: The method according to any one of Aspects 45 to 46, wherein the first PBCH message includes a demodulation reference signal, the demodulation reference signal including the presence indicator.

[0338] Aspect 49: The method according to any one of aspects 45 to 48, wherein outputting the second PBCH message further includes: outputting the second PBCH message including a second presence indicator, the second presence indicator indicating the presence of a third PBCH message.

[0339] Aspect 50: The method according to aspect 49, the method further comprising: outputting the third PBCH message at least in part based on the second presence indicator, wherein the communication of the one or more messages with the network entity is at least in part based on receiving the third PBCH message.

[0340] Aspect 51: The method according to any one of aspects 45 to 50, wherein the presence indicator further indicates a resource for receiving the second PBCH message.

[0341] Aspect 52: According to the method of aspect 51, wherein the resource is selected from a set of candidate resources associated with the first PBCH message.

[0342] Aspect 53: The method according to any one of Aspects 51 to 52, wherein indicating the resource includes: indicating frequency domain resource assignment, time domain resource assignment, modulation and decoding scheme, redundancy version, virtual resource block to physical resource block mapping, or a combination thereof associated with the resource.

[0343] Aspect 54: The method according to any one of aspects 45 to 53, wherein the presence indicator further indicates content associated with the second PBCH message.

[0344] Aspect 55: According to the method of aspect 54, the content is selected from a set of candidate content associated with the second PBCH message.

[0345] Aspect 56: A user equipment for wireless communication, the user equipment comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so as to cause the user equipment to perform a method according to any one of aspects 1 to 8.

[0346] Aspect 57: A user equipment for wireless communication, the user equipment comprising at least one component for performing the method according to any one of aspects 1 to 8.

[0347] Aspect 58: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 8.

[0348] Aspect 59: A user equipment for wireless communication, the user equipment comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so as to cause the user equipment to perform a method according to any one of aspects 9 to 17.

[0349] Aspect 60: A user equipment for wireless communication, the user equipment comprising at least one component for performing the method according to any one of aspects 9 to 17.

[0350] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 9 to 17.

[0351] Aspect 62: A user equipment for wireless communication, the user equipment comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so as to cause the user equipment to perform a method according to any one of aspects 18 to 28.

[0352] Aspect 63: A user equipment for wireless communication, the user equipment comprising at least one component for performing the method according to any one of aspects 18 to 28.

[0353] Aspect 64: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 18 to 28.

[0354] Aspect 65: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 29 to 35.

[0355] Aspect 66: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 29 to 35.

[0356] Aspect 67: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 29 to 35.

[0357] Aspect 68: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 36 to 44.

[0358] Aspect 69: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 36 to 44.

[0359] Aspect 70: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 36 to 44.

[0360] Aspect 71: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 45 to 55.

[0361] Aspect 72: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 45 to 55.

[0362] Aspect 73: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 45 to 55.

[0363] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0364] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0365] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0366] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0367] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0368] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0369] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0370] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "one or more components" in subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0371] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0372] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0373] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0374] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment, the user equipment comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to equip the user: During the first timing period, a synchronization signal block including a physical broadcast channel message is received, the physical broadcast channel message indicating a time offset relative to the start of the synchronization signal block to identify the start of the search space; Monitor search space transmissions via the search space during a second timing period corresponding to the time offset indicated in the physical broadcast channel message; as well as The search space is received via the second timing.

2. The user equipment of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the user equipment to: Receive a second synchronization signal block including a second physical broadcast channel message, wherein the first identifier of the synchronization signal block is the same as the second identifier of the second synchronization signal block, and wherein the payload of the second physical broadcast channel message is the same as the payload of the physical broadcast channel message.

3. The user equipment of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the user equipment to: Receive the first data included in the physical broadcast channel message and the second data included in the second physical broadcast channel message; and The first data and the second data are combined to obtain the payload of the physical broadcast channel message, wherein the search space transmission is monitored at least in part based on the payload of the physical broadcast channel message.

4. The user equipment of claim 1, wherein the time offset indicates one or more symbols between the start of the search space transmission and the start of the synchronization signal block.

5. The user equipment of claim 4, wherein the start of the search space transmission and the start of the synchronization signal block occur in the same time slot, and wherein the time offset is indicated by at least four bits of the physical broadcast channel message.

6. The user equipment of claim 1, wherein the time offset is used to identify the start of a previous search space transmission relative to the start of the synchronization signal block.

7. The user equipment of claim 1, wherein the time offset is used to identify the start of an upcoming search space transmission relative to the start of the synchronization signal block.

8. The user equipment of claim 1, wherein the time offset identifier is the start of the search space transmission closest to the start of the synchronization signal block in the time domain.

9. A user equipment, the user equipment comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to equip the user: Receive a synchronization signal block including a physical broadcast channel message, the physical broadcast channel message indicating a frequency offset relative to a second frequency resource used for the synchronization signal block to identify a first frequency resource for a random access timing; A request for system information is sent via the first frequency resource corresponding to the frequency offset indicated in the physical broadcast channel message; as well as The system receives messages indicating system information, at least in part, based on the request.

10. The user equipment of claim 9, wherein the frequency offset includes a subcarrier offset indicating the number of subcarriers between the start of the first frequency resource and the start of the second frequency resource.

11. The user equipment according to claim 10, wherein: The frequency offset also includes a resource block offset indicating the number of uplink resource blocks between the start of the first frequency resource and the start of the second frequency resource, and The subcarrier offset indicates the number of subcarriers between the number of uplink resource blocks and the start of the second frequency resource.

12. The user equipment of claim 11, wherein the resource block offset indicates the difference between the resource block identifier of the first uplink resource block and the resource block identifier of the second uplink resource block, and wherein the first uplink resource block includes the start of the first frequency resource, and the second uplink resource block includes the start of the second frequency resource.

13. The user equipment of claim 11, wherein the resource block offset is indicated by a first set of bits of the physical broadcast channel message, and the subcarrier offset is indicated by a second set of bits of the physical broadcast channel message, the second set of bits following the first set of bits.

14. The user equipment of claim 9, wherein the frequency offset is based at least in part on a first subcarrier interval of an uplink bandwidth portion associated with the random access timing or a second subcarrier interval associated with the synchronization signal block.

15. The user equipment of claim 14, wherein the frequency offset is based at least in part on the larger of the first subcarrier spacing and the second subcarrier spacing or the smaller of the first subcarrier spacing and the second subcarrier spacing.

16. The user equipment of claim 9, wherein, in order to receive the synchronization signal block, the one or more processors are further capable of operating individually or jointly to execute the code to cause the user equipment to: The synchronization signal block, which includes the physical broadcast channel message, is received. The physical broadcast channel message also indicates a time offset relative to the start of the synchronization signal block to identify the start of the random access opportunity, wherein the request is sent at least in part based on the time offset.

17. The user equipment of claim 9, wherein the physical broadcast channel message further indicates one or more additional frequency offsets, each of the one or more additional frequency offsets identifying a corresponding frequency resource relative to the second frequency resource, and wherein each corresponding frequency resource corresponds to at least one of a channel state information reference signal, a downlink data channel transmission, an uplink control channel transmission, an uplink data channel transmission, and a probe reference signal.

18. A user equipment, the user equipment comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to equip the user: Receive a synchronization signal block including a first physical broadcast channel message, the first physical broadcast channel message including an presence indicator indicating the presence of a second physical broadcast channel message associated with the first physical broadcast channel message; The second physical broadcast channel message is received at least in part based on the presence indicator; as well as One or more messages are communicated to network entities, at least in part, based on the first physical broadcast channel message and the second physical broadcast channel message.

19. The user equipment of claim 18, wherein the value of the first identifier associated with the first physical broadcast channel message is less than the value of the second identifier associated with the second physical broadcast channel message.

20. The user equipment of claim 18, wherein the first physical broadcast channel message includes a master information block, the master information block including the presence indicator.

21. The user equipment of claim 18, wherein the first physical broadcast channel message includes a demodulation reference signal, the demodulation reference signal including the presence indicator.

22. The user equipment of claim 18, wherein, in order to receive the second physical broadcast channel message, the one or more processors are further capable of operating individually or jointly to execute the code to cause the user equipment to: Receive a second physical broadcast channel message including a second presence indicator, the second presence indicator indicating the presence of a third physical broadcast channel message.

23. The user equipment of claim 22, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the user equipment to: The third physical broadcast channel message is received at least in part based on the second presence indicator, wherein one or more messages are communicated to the network entity at least in part based on the third physical broadcast channel message.

24. The user equipment of claim 18, wherein the presence indicator further indicates resources for receiving the second physical broadcast channel message.

25. The user equipment of claim 24, wherein the resource is selected from a set of candidate resources associated with the first physical broadcast channel message.

26. The user equipment of claim 24, wherein, in order to instruct the resource, the one or more processors are also capable of operating individually or jointly to execute the code to cause the network entity to: Indicates the frequency domain resource assignment, time domain resource assignment, modulation and decoding scheme, redundancy version, virtual resource block to physical resource block mapping, or a combination thereof associated with the resource.

27. The user equipment of claim 18, wherein the presence indicator further indicates content associated with the second physical broadcast channel message.

28. The user equipment of claim 27, wherein the content is selected from a set of candidate content associated with the second physical broadcast channel message.

29. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: During the first timing period, a synchronization signal block including a physical broadcast channel message is output, the physical broadcast channel message indicating a time offset relative to the start of the search space transmission; and The search space transmission is output during a second timing period corresponding to the time offset indicated in the physical broadcast channel message.

30. The network entity of claim 29, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The output includes a second synchronization signal block comprising a second physical broadcast channel message, wherein the first identifier of the synchronization signal block is the same as the second identifier of the second synchronization signal block, and wherein the payload of the second physical broadcast channel message is the same as the payload of the physical broadcast channel message.

Images