System information block scheduling for low power wide area network

Abstract

System information block scheduling for low power wide area network may be provided A method for system information block scheduling for low power wide area network may include receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The method may include receiving, from the network entity, the system information block according to the determined system information block scheduling configuration.

Description

SYSTEM INFORMATION BLOCK SCHEDULING FOR LOW POWER WIDE AREA NETWORKCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of US provisional application No. 63 / 714,381 , filed October 31 , 2024. The content of which are hereby incorporated by reference in their entirety.TECHNICAL FIELD:

[0002] Some exemplary embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) or sixth generation (6G) new radio (NR) access technology, or other communications systems. For example, certain exemplary embodiments may relate to implementing system information block scheduling for low power wide area network.BACKGROUND:

[0003] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology, and / or sixth generation (6G) radio access technology. 5G and 6G wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology are mostly based on new radio (NR) technology, but the 5G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra- robust, low-latency connectivity and massive networking to support the Internet of Things (loT).SUMMARY:

[0004] Various exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may be also caused to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The system information blockscheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus may further be caused to receive, from the network entity, a system information block according to the determined system information block scheduling configuration.

[0005] Certain exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to determine a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may also be caused to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus may further be caused to transmit, to the user device, a system information block according to the determined type of system information block scheduling.

[0006] Some exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may also be caused to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block and receive, from the network entity, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined system information block scheduling configuration.

[0007] Various exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to determine a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may also be caused to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration, and transmit, to the user device, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined type of system information block scheduling.

[0008] Certain exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may also be caused to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and receive, from the network entity, the system information block according to the determined system information block scheduling configuration.

[0009] Some exemplary embodiments may provide an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to determine a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus may also be caused to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The apparatus may further be caused to transmit, to the user device, a system information block according to the system information block scheduling configuration.

[0010] Various exemplary embodiments may provide a method comprising receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method also comprises determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The method may further comprise receiving, from the network entity, a system information block according to the determined system information block scheduling configuration.

[0011] Certain exemplary embodiments may provide a method comprising determining a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also comprise transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The system information block scheduling configuration may compriseinformation associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The method may further comprise transmitting, to the user device, a system information block according to the determined type of system information block scheduling.

[0012] Some exemplary embodiments may provide a method comprising receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also comprise determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and receiving, from the network entity, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined system information block scheduling configuration.

[0013] Various exemplary embodiments may provide a method comprising determining a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also comprise transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration, and transmitting, to the user device, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined type of system information block scheduling.

[0014] Certain exemplary embodiments may provide a method comprising receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and receiving, from the network entity, the system information block according to the determined system information block scheduling configuration.

[0015] Some exemplary embodiments may provide a method comprising determining a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system informationblock scheduling configuration. The method may further include transmitting, to the user device, a system information block according to the system information block scheduling configuration.

[0016] Certain exemplary embodiments may provide a non-transitory computer-readable storage medium comprising computer-executable instructions that, when executed by an apparatus, cause the apparatus to perform any one or more of the methods described herein.

[0017] Some exemplary embodiments may provide one or more computer programs comprising instructions stored thereon for performing one or more of the methods described herein.

[0018] Various exemplary embodiments may provide one or more apparatuses comprising one or more circuitry configured to perform one or more of the methods described herein.

[0019] Certain exemplary embodiments may provide one or more apparatuses comprising one or more means configured for performing one or more of the methods described herein.BRIEF DESCRIPTION OF THE DRAWINGS:

[0020] For proper understanding of exemplary embodiments, reference should be made to the accompanying drawings, as follows:

[0021] FIG. 1 illustrates an example graphical representation of system information block (SIB) transmissions;

[0022] FIG. 2 illustrates an example graphical representation of SIB transmissions with dynamic scheduling;

[0023] FIG. 3 illustrates an example of a graphical representation of timing configurations for network-based selection of SIB scheduling type, according to certain exemplary embodiments;

[0024] FIG. 4 illustrates an example of a graphical representation of SIB transmissions for coverage enhancement, according to some exemplary embodiments;

[0025] FIG. 5 illustrates an example of a graphical representation of SIB transmissions without frequency hopping, according to various exemplary embodiments;

[0026] FIG. 6 illustrates an example of a graphical representation of SIB transmissions with frequency hopping, according to some exemplary embodiments;

[0027] FIG. 7 illustrates an example of a signal diagram, according to certain exemplary embodiments;

[0028] FIG. 8 illustrates an example of a flow diagram of a method, according to various exemplary embodiments;

[0029] FIG. 9 illustrates an example of a flow diagram of an additional method, according to certain exemplary embodiments;

[0030] FIG. 10 illustrates an example of a flow diagram of a further method, according to some exemplary embodiments;

[0031] FIG. 11 illustrates an example of a flow diagram of another method, according to certain exemplaryembodiments;

[0032] FIG. 12 illustrates an example of a flow diagram of a method, according to some exemplary embodiments;

[0033] FIG. 13 illustrates an example of a flow diagram of a further method, according to certain exemplary embodiments; and

[0034] FIG. 14 illustrates a set of apparatuses, according to various exemplary embodiments.DETAILED DESCRIPTION:

[0035] It will be readily understood that the components of certain exemplary embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some exemplary embodiments of systems, methods, apparatuses, and non-transitory computer program products for implementing system information block scheduling for low power wide area network. Although the devices discussed below and shown in the figures refer to 6G / 5G or Next Generation NodeB (gNB) devices and UE devices, this disclosure is not limited to only gNBs and UEs.

[0036] It may be readily understood that the components of certain exemplary embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Different reference designations from multiple figures may be used out of sequence in the description, to refer to a same element to illustrate their features or functions. If desired, the different functions or procedures discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain exemplary embodiments, and not in limitation thereof.

[0037] 3rdGeneration Partnership Project (3GPP) may provide specifications for implementing system information block scheduling for communication connections over a network. A communication connection may be initiated between devices, such as a UE and a network entity, such as a base station, gNB, etc., through a random access (RA) procedure by employing a physical random access channel (PRACH). A contention-based RACH may be, for example, a 2-step or 4-step RACH.

[0038] A system information blocks (SIBs) may provide various types of information from the network to a network device, such as a UE. One example of an SIB is system information block #1 (SIB1), which may provide information related to evaluating whether a UE is allowed to access a cell and may define the scheduling of system information. SIB1 may also provide radio resource configuration information for one or more, or all, UEs in a cell and additional information for unified access control. SIB1 may provide information for the UE to accessthe network, such as, for example, cell parameters, random access parameters, access baring, scheduling for other SIBs, and the like.

[0039] Low power wide area (LPWA) network may be used to support Internet of Things (loT) devices. The LPWA network may include one or more characteristics, including, for example, low device complexity and / or cost, low device power consumption enabling increased battery life (e.g., greater than 10 years), enhanced coverage relative to broadband services (e.g., up to 20-25 dB enhanced coverage), support for massive scale number of devices, delay tolerant data transmission (e.g., up to 10 seconds to transmit a data packet), and / or infrequent data transmissions.

[0040] In NR and / or 6G, SIB1 may be dynamically scheduled via downlink control information (DCI), such as via a physical downlink control channel (PDCCH) in a search space configured for a control resource set (CORESET), such as CORESETO. Dynamic scheduling may be used to provide scheduling flexibility in term of SIB1 transmission frequency, resource utilization, and overhead. In CORESETO, the search space may indicate one or more locations where the UE is to attempt to locate a control information transmitted within the timefrequency resources defined by the CORESETO. The configuration of CORESETO and search space may be provided to the UE in a master information block (MIB). An example of the configuration and search space in the MIB may be as follows:

[0041] FIG. 1 illustrates an example graphical representation of SIB1 transmissions over a certain transmission periodicity. SIB1 may have a transmission periodicity by which SIB1 may be transmitted from the network entity to the UE on a physical downlink shared channel (PDSCH) with a periodicity of, for example, 160ms and one or more SIB1 repetitions can be transmitted within this period. The UE may then combine multiple copies (repetitions) of SIB1 transmission within the 160ms time period or boundary to assist in decoding of SIB1. However, the UE first needs to decode the PDCCH scheduling each SIB1 PDSCH transmission before the UEcan combine the PDSCHs since the PDSCHs can be scheduled in different resources relative to the corresponding PDCCH.

[0042] In certain applications, such as in LTE-M and narrow band (NB) loT, a different SIB1 (SIB1-BR and SIB1- NB, respectively) may be transmitted from the SIB1 used by the broadband UE. These SIB1s may be transmitted on the PDSCH (or narrowband PDSCH) and scheduled via MIB. This scheduling approach may be used when both SIB1-BR and SIB1-NB need to support coverage enhancement, such as up to 20 dB beyond the coverage of LTE / NR. The UE may combine multiple copies of SIB1 transmission within the boundary without having to first decode the PDCCH that would have been needed in case of dynamic scheduling. An example of SIB1-NB scheduling via MIB-NB may be as follows:

[0043] In NR networks, when SIB1 is scheduled dynamically, each PDSCH transmission would require a DCI sent on the PDCCH and a PDCCH configuration (CORESETO and SearchSpaceZero) may be given in the MIB. In eMTC / NB-loT, SIB1 may be scheduled via MIB with a portion of the scheduling information pre-defined in a specification (e.g., 3GPP specification). For example, in eMTC, the MIB may provide a transport block size (TBS) and a number of repetitions of SIB1. The time location may be determined based on, for example, number of repetitions, cell ID, and / or system frame number. The frequency location may be determined based on, for example, system bandwidth, cell ID, and / or system frame number.

[0044] FIG. 2 illustrates an example graphical representation of SIB1 transmissions with dynamic scheduling in enhanced coverage applications in LPWA networks. For 5G or 6G LPWA, a common SIB1 may be used for both eMBB and LPWA / loT UE. The common SIB1 may need to support coverage enhancement, such as of up to 20dB beyond the coverage of 5G / 6G eMBB. To reduce the PDSCH overhead required by SIB1 , the LPWA UE may combine multiple copies of SIB1 transmission within the SIB1 periodicity to assist in decoding of SIB1 . For example, the gNB may transmit SIB1 16 times within 160ms period and the UE may then combine these 16 copies for coverage enhancement. However, if each SIB1 is scheduled dynamically, each PDSCH transmission would require a DCI sent on the PDCCH and each PDCCH may need to reach up to 20 dB coverage enhancement using repetitions. For example, each PDCCH may use 64 repetitions to support 20 dB coverage enhancement, which may result in undesirably high PDCCH overhead.

[0045] SIB1 scheduling via MIB may eliminate the need for PDCCH. However, SIB1 scheduling flexibility may be limited since SIB1 scheduling would need to be fixed at least within the SIB1 periodicity because a coverage limited UE would need to accumulate several copies of the SSB1 before decoding the MIB so the content of the MIB cannot change, and there may be only a limited number of available bits in the MIB for SIB1 scheduling. For example, in NR, only 8 bits may be available in the MIB for SIB1 scheduling as compared to approximately 40 bits in DCI.

[0046] Various exemplary embodiments may recognize that it is desirable to allow the network to efficiently schedule SIB1 to both eMBB and LPWA UEs in the same cell and to support coverage enhancement in the cell. Various exemplary embodiments may provide technological advantages to provide for this efficient scheduling of SIB1 by indicating in the MIB whether SIB1 is dynamically scheduled via PDCCH with a CORESET configuration provided in the MIB or is scheduled directly in the MIB and the MIB also provides information about SIB1 scheduling.

[0047] Certain exemplary embodiments may provide that a field in the MIB (e.g., a bit) may indicate how SIB1 is scheduled, such as whether SIB1 is dynamically scheduled via PDCCH with CORESET configuration provided in MIB or scheduled directly via the MIB. For example, the MIB may contain one or more of SIBISchedulingType and / or SIB1 Schedulinginfo fields. The field SIBISchedulingType may indicate how SIB1 is scheduled, while the field SIB1 Schedulinginfo may indicate SIB1 scheduling information. Alternately, another field may be used to indicate how SIB1 is scheduled. For example, the field SIBISchedulingType may be omitted and instead one value in field Schedulinginfol may be used to indicate that SIB1 is scheduled via the MIB with scheduling information provided in field Schedulinglnfo2.

[0048] Some exemplary embodiments may provide that the network, such as a gNB, may select the manner in which SIB1 scheduling is performed based on a supported coverage enhancement (CE) level of the cell. For example, SIB1 scheduling via PDCCH may be used for small CE level, which may be a CE level below a set threshold value, and / or SI B1 scheduling may be performed directly via the MIB for large CE levels, such as equal to or greater than the set threshold value. Determining the manner of SIB1 scheduling may be based on, for example, an indication by the UE, UE energy saving configuration(s), timing patterns, and / or the like. Thenetwork may determine whether to use dynamic scheduling via DCI or scheduling directly via MIB, and the corresponding SIB1 scheduling configuration (e.g., TBS, modulation and coding scheme (MCS), number of repetitions, radio resources, and / or PDCCH configuration and repetitions for dynamic scheduling, including aggregation level). The SIB1 scheduling configuration may be based on the supported maximum CE level of the cell and accounting for network energy saving settings.

[0049] FIG. 3 illustrates an example of a graphical representation of timing configurations for network-based selection of SIB1 scheduling type, according to certain exemplary embodiments. The network may decide whether to activate dynamic scheduling via DCI or scheduling directly via MIB based on one or more time configurations or timing patterns, which provide time periods when each SIB1 scheduling type and configuration is provided. The selected time configuration may be decided based on a deployment scenario, history activity, a machine learning (ML) model inference, and / or network energy saving target. Based on the timing indicated in the selected time configuration, the network (e.g., gNB) may inform that UE in advance about when the network will be providing SIB1 with support for each CE level.

[0050] Multiple time configurations may also be provided, which may be the time periods when each of SIB1 scheduling methods / types is supported. The multiple time configurations may be predefined (e.g., in specified tables or via 3GPP specifications), and the network may indicate in the MIB which the time configuration the network is using and should be employed by the UE. Alternatively, the network may directly indicate the timing for when SIB1 supporting a certain CE level may be provided. For example, the MIB may indicate that SIB1 is scheduled with support to CE level 2 and may be provided in x subframes ahead, relative to a subframe when the indication is given. Based on indicated timing, the UE may determine whether or not to stay in a power saving mode (e.g., idle mode) until a next time when SIB1 will be scheduled in accordance with its CE level. For example, the UE may determine to stay in a power saving mode until SIB1 is scheduled via MIB and with a number of repetitions above a certain threshold value, if the UE has a relatively high CE level, as defined relative to a CE threshold level. Certain exemplary embodiments may provide that both eMBB and LPWA UEs may follow the SIB1 scheduling type indicated in the MIB.

[0051] Various exemplary embodiments may provide that a variation in which the SIB1 scheduling information is different for different synchronization signal blocks (SSBs) starting locations or SSB positions in a burst of SSBs, which are SSB positions corresponding to different beams. In the burst of SSBs each SSB may correspond to a beam. The UE may select the SIB1 scheduling information corresponding to a best SSB (best beam), which may be defined as a beam or SSB having a highest performance metric(s) relative to any or all other SSBs available to the UE. The beam having a highest performance metrics among the performance metrics of the plurality of beams may be the best beam. The SSB having a highest performance metrics among the performance metrics of the plurality of SSBs may be a best SSB. The best SSB may be tied, connected, orlinked to the best beam. SIB1 scheduling information may be different for different SSB starting locations or SSB positions in a burst. For example, with three SSBs in a burst (SSBO, SSB1 , SSB2), the MIB from SSBO may indicate SIB1 is transmitted every 20ms on subframes where a system frame number (SFN) mod 160 = 0, and the MIB from SSBO may indicate SIB1 is transmitted every 20ms on subframes where SFN mod 160 = 5. “mod” may refer to a modulus operation, which may provide different time offsets for when the SIB1 is transmitted. When, for example, the SFN changes every 10ms and when the SIB1 is transmitted with a periodicity of 20ms, the SIB1 may be scheduled with: SFN mod 160 = 0, then SIB1 is transmitted at 0, 20, 40, 60, 80, 100 ms, etc., and SFN mod 160 = 5, then SIB1 is transmitted at 50, 70, 90, 110, 130 ms, etc.

[0052] Certain exemplary embodiments may provide that the MIB may include one or more fields or bits which indicate how an SIB1 is scheduled, such as whether the SIB1 is dynamically scheduled via PDCCH with a CORESET configuration provided in MIB or whether the SIB1 is scheduled directly in the MIB. For example, the MIB may contain the SIBISchedulingType and SIB1 -Schedulinginfo fields. The field SIBISchedulingType may indicate how the SIB1 is scheduled, and the field SIB1 -Schedulinginfo may indicate the SIB1 scheduling information. An example of SIB1 scheduling via the MIB may be as follows:_

[0053] Various exemplary embodiments may provide that when the field SIBISchedulingType = 0, which indicates SIB1 is dynamically scheduled via PDCCH, the field SIB1 -Schedulinginfo may indicate information about CORESET 0 and search space 0. For example, Schedulinginfol may provide a CORESET 0 configuration and Schedulinglnfo2 may provide a search space 0 configuration. Additional configuration information in SIB1- Schedulinglnfo, such as in Schedulinglnfo2, may indicate the support for SIB1 CE. When SIB1 CE is supported, successive SIB1 transmissions may be transmitted as repetitions of SIB1 that may be combined for CE by the UE. The number of repetitions may be indicated, for example, in Schedulinginfol.

[0054] FIG. 4 illustrates an example of a graphical representation of SIB1 transmissions for coverage enhancement with PDCCH repetition, according to various exemplary embodiments. The dynamic schedulingof the SIB1 via PDCCH may use the PDCCH to schedule the first SIB1 transmission within an interval of the repetitions of SIB1, wherein the PDCCH may itself be repeated within a predetermined extended CORESET region. For example, additional PDCCH repetitions may be transmitted for the PDCCH associated with only the first SIB1 transmission. The PDCCH repetitions may be combined by the UE for decoding the DCI, which provides SIB1 scheduling information. The SIB1 scheduling information may be used for combining the SIB1 repetitions and decoding the SIB1 content. The UE may start combining SIB1 repetitions after decoding the DCI, including after combining the PDCCH repetitions. In some exemplary embodiments, reception of the first SIB1 repetition may be skipped by the UE. The content of the SIB1 may be the same for all the repetitions. The PDCCH repetitions in the extended CORESET may span across frequency and / or time. The extended CORESET region may be predetermined, such as defined in a specification (e.g., 3GPP specification) or signaled in SIB1 -Schedulinginfo (e.g., in Schedulinginfol). The PDCCH repetition pattern may be predetermined. For a UE that does not require coverage enhancement, PDCCH and PDSCH decoding for SIB1 may be independent of whether SIB1 coverage enhancement is supported.

[0055] Certain exemplary embodiments may provide that when SIBISchedulingType = 1, the field SIB1 Schedulinginfo may alternatively provide the SIB1 scheduling information. For example, Schedulinginfol can provide MCS (or the TBS) and number of repetitions, while Scheduling! nfo2 can provide PDSCH timefrequency resource. The SIB1 content is the same for all the repetitions. However, different redundancy versions may be transmitted, which may be either predetermined in the specifications or signaled in SI B1 -Schedulinginfo, e.g., in Schedulinginfol .

[0056] FIG. 5 illustrates an example of a graphical representation of SIB1 transmissions for coverage enhancement scheduled by the MIB without frequency hopping, according to various exemplary embodiments. As shown in FIG. 5, some exemplary embodiments may provide that the same frequency resource may be assigned for all SIB1 repetitions.

[0057] FIG. 6 illustrates an example of a graphical representation of SIB1 transmissions for coverage enhancement scheduled by the MIB with frequency hopping, according to some exemplary embodiments. As shown in FIG. 6, some exemplary embodiments may provide that the repetitions of SIB1 may be hopped in frequency, where a hopping pattern may be either predetermined (e.g., defined in a 3GPP specification) or signaled in the field SIB1 -Schedulinginfo, such as in Schedulinglnfo2.

[0058] Certain exemplary embodiments may provide a variation of this configuration in which another field may be used to indicate how SIB1 is scheduled. For example, the field SIBISchedulingType may not be needed. Instead, one value in Schedulinginfol may be used to indicate that SIB1 is scheduled via the MIB and the scheduling information may be provided in Schedulinglnfo2. An example of SIB1 scheduling in this variation may be as follows:

[0059] Various exemplary embodiments may provide that when Schedulinginfol = 0, which may be defined as corresponding to dynamically scheduling SIB1 via PDCCH, the field SIB1Schedulinglnfo2 may indicate information about CORESET 0 and search space 0. For example, the most significant bits (MSBs) may provide CORESET 0 configuration, and the least significant bits may provide search space 0 configuration. The MSB is a well-known in the technology as one or more of the leftmost bit(s) and the LSB is well-known in the technology as one or more of the rightmost bit(s) in a binary number, byte, or binary-coded data element. When Schedulinginfol = 1, the field SIB1Schedulinglnfo2 may instead provide SIB1 scheduling information. For example, Schedulinginfol may provide MCS or the TBS and the number of repetitions and PDSCH timefrequency resource by, for example, pointing to an index of a table with predefined combinations of these parameters.

[0060] Some exemplary embodiments may provide that the network, such as a gNB, may select the manner in which SIB1 scheduling is performed based on a supported CE level of the cell. For example, SIB1 scheduling via PDCCH may be used for small CE level, which may be a CE level below a set threshold value, and / or SIB1 scheduling may be performed directly via the MIB for large CE levels, such as equal to or greater than the set threshold value. Both eMBB and LPWA UEs may follow the SIB1 scheduling type indicated in the MIB. In an implementation for a eMBB UE or for a LPWA UE in low CE level, when the MIB indicates that the SIB1 is scheduled via MIB (e.g., for the support of large CE levels), the UE may perform the reception of a subset of SIB repetitions sufficient for UEs in good coverage, and may enter or remain in a power saving state for the remaining repetitions.

[0061] Certain exemplary embodiments may provide that in an implementation of a LPWA UE, when the SIB1 is indicated to be dynamically scheduled and there is no indication of support of large CE levels, the UE may determine to enter or stay in a power saving state. The UE may enter or stay in the power saving state when the UE has determined to be in a large CE level and may stay in the power saving state at least until the nextMIB period, or until a certain time limit which the network may set or change the SIB1 scheduling type. In another implementation of LPWA UE, the SIB1 may be indicated to be dynamically scheduled and an indication of support of large CE levels may be provided. The UE may enter or stay in a power saving state until the start of the next SIB1 repetition interval.

[0062] Some exemplary embodiments may provide another variation in which SIB1 scheduling information may be different for different SSB starting locations or SSB positions in a burst, which may correspond to different beams. The UE may select the SIB1 scheduling information corresponding to the best SSB or beam. Further, the scheduling type for SIB1 may be different for different SSBs or beams. For example, a PDCCH-based SIB1 scheduling in some or a subset of beams may be used where low CE levels are supported, and MIB-based SIB1 scheduling may be used on other or another subset of beams which support coverage for LPWA UEs in relatively larger CE levels.

[0063] FIG. 7 illustrates an example of a signal diagram, according to certain exemplary embodiments. The signal diagram shows signaling between a UE 701 and a gNB 702. At 710, the gNB 702 may determine SIB1 scheduling type, such as such as dynamic scheduling via DCI or scheduling directly via MIB. At 720, the gNB 702 may determine SIB1 scheduling information when the SIB1 scheduled directly via the MIB. At 730, the gNB 702 may generate and transmit an MIB to the UE 701. The MIB may include, for example, at least a SIB1 scheduling type, such as field SIBISchedulingType, and an associated scheduling configuration, such as scheduling information as indicated in the field SIBI-Schedulinglnfo.

[0064] At 740, the UE 701 may determine a best beam based on an SSB. The best beam may be defined as a beam or SSB having a highest performance metric(s) relative to any or all other beams available to the UE. At 750, the UE 701 may determine an SIB1 scheduling configuration information based on the determined best beam. At 760, the gNB 702 may transmit a first repetition of SIB1 , and at 770, the gNB 702 may transmit a remainder of one or a plurality of repetitions of SIB1. At 780, the UE 701 may combine the multiple instances (repetitions or transmissions) of the SIB1 transmissions.

[0065] Various exemplary embodiments may provide technological advantages to allow the network to determine and inform the manner of SIB1 scheduling, which may provide an effective and efficient flexibility in the network or communication configuration and decreased or relatively low overhead.

[0066] FIG. 8 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 8 may be performed by a user device in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 8 may be performed by a user device or user equipment, such as a UE, similar to apparatus 1410 illustrated in FIG. 14.

[0067] According to various exemplary embodiments, the method of FIG. 8 may include, at 810, receiving, from a network entity, such as a gNB, a master information block comprising an indication of a type of systeminformation block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include, at 820, determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The method may further include, at 830, receiving, from the network entity, a system information block according to the determined system information block scheduling configuration.

[0068] Certain exemplary embodiments may provide the indication of the type of system information block scheduling is different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block of at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block. The physical downlink control channel may be transmitted, by the network entity, using one or more repetitions, which are received by the UE. The repetitions of the physical downlink control channel may not be contiguous in time.

[0069] Some exemplary embodiments may provide that, when the type of system information block scheduling is direct scheduling via the master information block, the master information block may comprise scheduling information directly indicating scheduling for receiving the system information block. When the type of system information block scheduling comprises scheduling via downlink control information, the information associated with time-frequency resources for receiving the repetitions of the system information block may be determined based on corresponding downlink control information indications. When the type of system information block scheduling comprises direct scheduling via the master information block, the information associated with the time-frequency resources for receiving repetitions of the system information block may be determined based on a configuration received in the master information block. The information associated with the time-frequency resources may include at least one of scheduling information associated with the time-frequency resources for receiving repetitions of the system information block or the time-frequency resources for receiving repetitions of the system information block. The system information block scheduling may be configured for receiving repetitions of the system information block. The repetitions of the system information block may not be contiguous in time.

[0070] Various exemplary embodiments may provide that the master information block comprises at least oneof: a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The scheduling information may include at least one of: an indication of modulation and coding scheme, an indication of transport block size, a repetition number of the system information block, or timefrequency resources of the system information block. The scheduling information may include an index of a table with combinations of at least two of parameters. The parameters may include at least one the indication of modulation and coding scheme, the indication of transport block size, the repetition number of the system information block, or the time-frequency resources of the system information block. The method may also include determining and selecting the at least one selected beam from a plurality of beams based on the at least one selected beam having a highest performance metrics among the performance metrics of the plurality of beams. The method may further include determining and selecting the at least one selected synchronization signal block from a plurality of synchronization signal blocks based on the at least one selected synchronization signal block having a highest performance metrics among the performance metrics of the plurality of synchronization signal blocks.

[0071] Certain exemplary embodiments may provide that the method further includes operating in a power saving state for one or more repetitions of the system information block based on at least a coverage enhancement level of a cell in which the apparatus is located. Different preambles or sequences may be associated with each of the types of system information block scheduling. Repetitions of the system information block may all be received in the same frequency resources or are hopped in frequency according to a pattern. The method also includes receiving, an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level. A plurality of time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided. The master information block may indicate that system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may further include based on an indicated timing, determining to stay in a power saving mode until a next time period when the system information block will be scheduled in accordance with a coverage enhancement level.

[0072] FIG. 9 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 9 may be performed by a network element / entity, or a group of multiple network entities in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 9 may be performed by a network node or network entity, such as a gNB, similar to apparatus 1420 illustrated in FIG. 14.

[0073] According to various exemplary embodiments, the method of FIG. 9 may include, at 910, determining a type of system information block scheduling. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include, at 920, transmitting, to a UE, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The system information block scheduling configuration may include information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The method may further include, at 930, transmitting, to the UE, a system information block according to the determined type of system information block scheduling.

[0074] Certain exemplary embodiments may provide that the indication of the type of system information block scheduling is different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block at the at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block. The physical downlink control channel may be transmitted using one or more repetitions. The repetitions of the physical downlink control channel may not be contiguous in time.

[0075] Various exemplary embodiments may provide that when the type of system information block scheduling is direct scheduling via the master information block, the master information block may include scheduling information directly indicating scheduling for receiving the system information block. The information associated with the time-frequency resources may include at least one of scheduling information associated with the timefrequency resources for transmitting repetitions of the system information block, or the time-frequency resources for transmitting repetitions of the system information block. The type of system information block scheduling may be determined based on at least a coverage enhancement level of a cell in which the user device is located. When the coverage enhancement level of the cell is below a threshold value, the type of system information block scheduling may be determined to be scheduling via downlink control information. When the coverage enhancement level of the cell is at or above a threshold value, the type of system information block scheduling may be determined to be direct scheduling via a configuration included in the master information block. The system information block scheduling may be configured for transmitting repetitions of the system information block. The repetitions of the system information block may not be contiguous in time.

[0076] Some exemplary embodiments may provide that the master information block comprises at least one of:a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The repetitions of the system information block may be transmitted using the same frequency resource. The repetitions of the system information block may be transmitted by frequency hopping and a pattern of the frequency hopping may be at least one of predetermined or signalled, to the UE, in the information associated with the system information block scheduling configuration. Different preambles or sequences may be associated with each of the types of system information block scheduling. The method may also include transmitting, to the UE, an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level. A plurality of time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided. The master information block may indicate that system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may further include determining which of the types of system information block scheduling to activate based on time configurations or timing patterns for time periods when each of the types of system information block scheduling and the system information block scheduling configuration is to be provided to the user device.

[0077] FIG. 10 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 10 may be performed by a user device in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 10 may be performed by a user device or user equipment, such as a UE, similar to apparatus 1410 illustrated in FIG. 14.

[0078] According to various exemplary embodiments, the method of FIG. 10 may include, at 1010, receiving, from a network entity, such as a gNB, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include, at 1020, determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The method may further include, at 1030, receiving, from the network entity, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined system information block scheduling configuration.

[0079] Certain exemplary embodiments may provide that the at least one of the frequency hopping pattern or timing pattern is at least one of predetermined, signalled in the master information block, or predefined in a specification. The same frequency resource may be assigned for each repetition of the system information block.The indication of the type of system information block scheduling may be different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block of at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block. The physical downlink control channel may be transmitted, by the network entity, using one or more repetitions, which are received by the UE. The repetitions of the physical downlink control channel may not be contiguous in time.

[0080] Various exemplary embodiments may provide that when the type of system information block scheduling is direct scheduling via the master information block, the master information block may include scheduling information directly indicating scheduling for receiving repetitions of the system information block. The system information block scheduling may be configured for receiving repetitions of the system information block. The system information block scheduling configuration may include information associated with time-frequency resources for receiving system information block repetitions based on the type of system information block scheduling. When the type of system information block scheduling comprises scheduling via downlink control information, the information associated with the time-frequency resources for receiving the repetitions of the system information block may be determined based on corresponding downlink control information indications. When the type of system information block scheduling comprises direct scheduling via the master information block, the information associated with the time-frequency resources for receiving the repetitions of the system information block may be determined based on a configuration received in the master information block.

[0081] Some exemplary embodiments may provide that the information associated with the time-frequency resources may include at least one of scheduling information associated with the time-frequency resources for receiving repetitions of the system information block, or the time-frequency resources for receiving repetitions of the system information block. The repetitions of the system information block may not be contiguous in time. The master information block may include at least one of a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The scheduling information may include at least one of: an indication of modulation and coding scheme, an indication of transport block size, a repetition number of the system information block, or time-frequency resources of the system information block. The scheduling information may include an index of a table with combinations of at least two of parameters. The parameters may include at least one the indication of modulation and coding scheme, the indication of transportblock size, the repetition number of the system information block, or the time-frequency resources of the system information block.

[0082] Certain exemplary embodiments may provide that the method includes determining and selecting the at least one selected beam from a plurality of beams based on the at least one selected beam having a highest performance metrics among the performance metrics of the plurality of beams, or determining and selecting the at least one selected synchronization signal block from a plurality of synchronization signal blocks based on the at least one selected synchronization signal block having a highest performance metrics among the performance metrics of the plurality of synchronization signal blocks. The method also may also include operating in a power saving state for one or more repetitions of the system information block based on at least a coverage enhancement level of a cell in which the apparatus is located. Different preambles or sequences may be associated with each of the types of system information block scheduling. The method may further include receiving an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level. A plurality of time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided. The master information block may indicate that the system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may include, based on an indicated timing, determining to stay in a power saving mode until a next time period when the system information block will be scheduled in accordance with a coverage enhancement level.

[0083] FIG. 11 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 11 may be performed by a network element / entity, or a group of multiple network entities in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 11 may be performed by a network node or network entity, such as a gNB, similar to apparatus 1420 illustrated in FIG. 14.

[0084] According to various exemplary embodiments, the method of FIG. 11 may include, at 1110, determining a type of system information block scheduling. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include, at 1120, transmitting, to a UE, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration, and at 1130, transmitting, to the UE, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined type of system information block scheduling.

[0085] Certain exemplary embodiments may provide the at least one of the frequency hopping pattern or timing pattern is at least one of predetermined, signalled in the master information block, or predefined in a specification. The same frequency resource may be assigned for each repetition of the system information block. The indication of the type of system information block scheduling may be different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block of at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block. The physical downlink control channel may be transmitted using one or more repetitions. The repetitions of the physical downlink control channel may not be contiguous in time.

[0086] Some exemplary embodiments may provide that when the type of system information block scheduling is direct scheduling via the master information block, the master information block may include scheduling information directly indicating scheduling for receiving repetitions of the system information block. The information associated with the time-frequency resources may include at least one of scheduling information associated with the time-frequency resources for transmitting repetitions of the system information block, or the time-frequency resources for transmitting repetitions of the system information block. The type of system information block scheduling may be determined based on at least a coverage enhancement level of a cell in which the user device is located. When the coverage enhancement level of the cell is below a threshold value, the type of system information block scheduling may be determined to be scheduling via downlink control information. When the coverage enhancement level of the cell is at or above a threshold value, the type of system information block scheduling may be determined to be direct scheduling via a configuration included in the master information block. The system information block scheduling may be configured for transmitting repetitions of the system information block. The repetitions of the system information block may not be contiguous in time.

[0087] Various exemplary embodiments may provide that the master information block comprises at least one of: a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The repetitions of the system information block may be transmitted using the same frequency resource. Different preambles or sequences may be associated with each of the types of system information block scheduling. The method may also include transmitting an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level. A plurality of1 time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided. The master information block may indicate that system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may further include determining which of the types of system information block scheduling to activate based on time configurations or timing patterns for time periods when each of the types of system information block scheduling and the system information block scheduling configuration is to be provided to the user device.

[0088] FIG. 12 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 12 may be performed by a user device in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 12 may be performed by a user device or user equipment, such as a UE, similar to apparatus 1410 illustrated in FIG. 14.

[0089] According to various exemplary embodiments, the method of FIG. 12 may include, at 1210, receiving, from a network entity, such as a gNB, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may also include, at 1220, determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and at 1230, receiving, from the network entity, the system information block according to the determined system information block scheduling configuration.

[0090] Certain exemplary embodiments may provide that a first system information block received of repetitions of the system information block comprises a plurality of repetitions of a physical downlink control channel and the remaining repetitions of the system information block are received without the physical downlink control channel. When the coverage enhancement for the system information block is supported, successive system information block transmissions may be repetitions that are to be combined for the coverage enhancement. The number of successive system information block transmissions may be indicated in the master information block. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel, and the physical downlink control channel that schedules a first system information block transmission within a time interval may be repeated within a predetermined extended control resource set region. Repetitions of the physical downlink control channel in the extended control resource set may span across both frequency and time. The extended control resource set region may be predetermined by being defined in at least one of a specification or signalled in the masterinformation block.

[0091] Various exemplary embodiments may provide that a repetition pattern of the repetitions of the physical downlink control channel are at least one of predetermined, signalled in the master information block, or predefined in a specification (e.g., 3GPP specification). A content of the system information block may be the same for all repetitions. Different redundancy versions of the system information block may be received, which are at least one of predetermined in a specification (e.g., 3GPP specification) or signalled in the master information block. The method may also include combining repetitions of the system information block and a plurality of repetitions of a physical downlink control channel in a first system information block for decoding the system information block. The indication of the type of system information block scheduling may be different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block of at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block.

[0092] Some exemplary embodiments may provide that the physical downlink control channel is transmitted, by the network, using one or more repetitions, which are received by the UE. The one or more repetitions of the physical downlink control channel may not be contiguous in time. When the type of system information block scheduling is direct scheduling via the master information block, the master information block may include scheduling information directly indicating scheduling for the system information block. The system information block scheduling configuration may include information associated with time-frequency resources for receiving system information block repetitions based on the type of system information block scheduling. When the type of system information block scheduling comprises scheduling via downlink control information, the information associated with the time-frequency resources for receiving the repetitions of the system information block may be determined based on corresponding downlink control information indications. When the type of system information block scheduling comprises direct scheduling via the master information block, information associated with the time-frequency resources for receiving the repetitions of the system information block may be determined based on a configuration received in the master information block.

[0093] Various exemplary embodiments may provide that the information associated with the time-frequency resources comprises at least one of scheduling information associated with the time-frequency resources for receiving repetitions of the system information block, or the time-frequency resources for receiving repetitions of the system information block. The system information block scheduling may be configured for receivingrepetitions of the system information block. The repetitions of the system information block may not be contiguous in time. The master information block may include at least one of a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The scheduling information may include at least one of: an indication of modulation and coding scheme, an indication of transport block size, a repetition number of the system information block, or time-frequency resources of the system information block. The scheduling information may include an index of a table with combinations of at least two of parameters. The parameters may include at least one of the indication of modulation and coding scheme, the indication of transport block size, the repetition number of the system information block, or the time-frequency resources of the system information block.

[0094] Certain exemplary embodiment may provide that the method includes determining and selecting at least one beam from a plurality of beams for the system information block scheduling based on the at least one selected beam having a highest performance metric among performance metrics of the plurality of beams, or determining and selecting the at least one selected synchronization signal block from a plurality of synchronization signal blocks based on the at least one selected synchronization signal block having a highest performance metrics among the performance metrics of the plurality of synchronization signal blocks. The method may also include operating in a power saving state for one or more of the repetitions of the system information block based on at least a coverage enhancement level of a cell in which the apparatus is located. Different preambles or sequences may be associated with each of the types of system information block scheduling. Repetitions of the system information block may all be received in the same frequency resources or are hopped in frequency according to a predetermined pattern. The method may further include receiving an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level.

[0095] Some exemplary embodiments may provide that a plurality of time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided, wherein the master information block indicates that system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may also include, based on an indicated timing, determining to stay in a power saving mode until a next time period when the system information block will be scheduled in accordance with a coverage enhancement level.

[0096] FIG. 13 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 13 may be performed by a network element / entity, or a group ofmultiple network entities in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an exemplary embodiment, the method of FIG. 13 may be performed by a network node or network entity, such as a gNB, similar to apparatus 1420 illustrated in FIG. 14.

[0097] According to various exemplary embodiments, the method of FIG. 13 may include, at 1310, determining a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may include at least one of scheduling via downlink control information or direct scheduling via the master information block. The method may include, at 1320, transmitting, to a UE, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The method may further include, at 1330, transmitting, to the UE, a system information block according to the system information block scheduling configuration.

[0098] Certain exemplary embodiments may provide that a first system information block transmitted in repetitions of the system information block comprises a plurality of repetitions of a physical downlink control channel and the remaining repetitions of the system information block are transmitted without the physical downlink control channel. When the coverage enhancement for the system information block is supported, successive system information block transmissions may be repetitions that are to be combined for the coverage enhancement. The number of successive system information block transmissions may be indicated in the master information block. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel, and the physical downlink control channel that schedules a first system information block transmission within a time interval may be repeated within a predetermined extended control resource set region. Repetitions of the physical downlink control channel in the extended control resource set may span across both frequency and time. The extended control resource set region may be predetermined by being defined in at least one of a specification (e.g., 3GPP specification) or signalled in the master information block.

[0099] Various exemplary embodiments may provide that a repetition pattern of the repetitions of the physical downlink control channel are at least one of predetermined, signalled in the master information block, or predefined in a specification (e.g., 3GPP specification). A content of the system information block may be the same for all repetitions. Different redundancy versions of the system information block may be received, which are at least one of predetermined in a specification (e.g., 3GPP specification) or signalled in the master information block. The indication of the type of system information block scheduling may be different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams. The master information block may be included in a synchronization signal block of at least one synchronization signal block startingposition or position in the burst or the at least one of the plurality of beams. When the type of system information block scheduling is scheduling via downlink control information, the system information block may be scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block. The physical downlink control channel may be transmitted using one or more repetitions. The repetitions of the physical downlink control channel may not be contiguous in time.

[0100] Some exemplary embodiments may provide that when the type of system information block scheduling is direct scheduling via the master information block, the master information block may include scheduling information directly indicating scheduling for receiving the system information block. The information associated with the time-frequency resources may include at least one of scheduling information associated with the timefrequency resources for transmitting repetitions of the system information block, or the time-frequency resources for transmitting repetitions of the system information block. The type of system information block scheduling may be determined based on at least a coverage enhancement level of a cell in which the user device is located. When the coverage enhancement level of the cell is below a threshold value, the type of system information block scheduling may be determined to be scheduling via downlink control information. When the coverage enhancement level of the cell is at or above a threshold value, the type of system information block scheduling may be determined to be direct scheduling via a configuration included in the master information block.

[0101] Various exemplary embodiments may provide that the system information block scheduling is configured for transmitting repetitions of the system information block. The repetitions of the system information block may not be contiguous in time. The master information block may include at least one of a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field. The repetitions of the system information block may be transmitted using the same frequency resource. The repetitions of the system information block may be transmitted by frequency hopping, and a pattern of the frequency hopping may be at least one of predetermined or signalled, to the UE, in the information associated with the system information block scheduling configuration. Different preambles or sequences may be associated with each of the types of system information block scheduling. The method may also include transmitting an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level. A plurality of time periods when each of the types of system information block scheduling is supported may be an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided. The master information block may indicate that a system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided. The method may further include determining which of the types of system information block scheduling to activate based on time configurationsor timing patterns for time periods when each of the types of system information block scheduling and the system information block scheduling configuration is to be provided to the UE.

[0102] FIG. 14 illustrates apparatuses 1410 and 1420 according to various exemplary embodiments. In the various exemplary embodiments, the apparatus 1410 may be an element in a network or associated with such a network, such as mobile device, user device, or other type of user equipment. UE 101 may be an example of apparatus 1410 according to various exemplary embodiments as discussed above. It should be noted that one of ordinary skill in the art would understand that apparatus 1410 may include components or features not shown in FIG. 14. Further, apparatus 1420 may be an element in a network or associated with such a network, such as a base station, gNB, and the like. gNB 102 may be an example of apparatus 1420 according to various exemplary embodiments as discussed above. It should be noted that one of ordinary skill in the art would understand that apparatus 1420 may include components or features not shown in FIG. 14.

[0103] According to various exemplary embodiments, the apparatuses 1410 and / or 1420 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some exemplary embodiments, apparatuses 1410 and / or 1420 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-loT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies.

[0104] As illustrated in the example of FIG. 14, apparatuses 1410 and / or 1420 may include or be coupled to processors 1412 and 1422, respectively, for processing information and executing instructions or operations. Processors 1412 and 1422 may be any type of general or specific purpose processor. In fact, processors 1412 and 1422 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 1412 (1422) for each of apparatuses 1410 and / or 1420 is shown in FIG. 14, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain exemplary embodiments, apparatuses 1410 and / or 1420 may include two or more processors that may form a multiprocessor system (for example, in this case processors 1412 and 1422 may represent a multiprocessor) that may support multiprocessing. According to certain exemplary embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster).

[0105] Processors 1412 and 1422 may perform functions associated with the operation of apparatuses 1410 and / or 1420, respectively, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 1410 and / or 1420, including processes illustrated in FIGs. 3-13.

[0106] Apparatuses 1410 and / or 1420 may further include or be coupled to memory 1414 and / or 1424 (internal or external), respectively, which may be coupled to processors 1412 and 1422, respectively, for storing information and instructions that may be executed by processors 1412 and 1422. Memory 1414 (memory 1424) may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memory 1414 (memory 1424) can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 1414 and memory 1424 may include program instructions or computer program code that, when executed by processors 1412 and 1422, enable the apparatuses 1410 and / or 1420 to perform tasks as described herein.

[0107] In certain exemplary embodiments, apparatuses 1410 and / or 1420 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 1412 and 1422 and / or apparatuses 1410 and / or 1420 to perform any of the methods illustrated in FIGs. 3-13.

[0108] In some exemplary embodiments, apparatuses 1410 and / or 1420 may also include or be coupled to one or more antennas 1415 and 1425, respectively, for receiving a downlink signal and for transmitting via an uplink from apparatuses 1410 and / or 1420. Apparatuses 1410 and / or 1420 may further include transceivers 1416 and 1426, respectively, configured to transmit and receive information. The transceivers 1416 and 1426 may also include a radio interface (for example, a modem) respectively coupled to the antennas 1415 and 1425. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-loT, Bluetooth, BT-LE, NFC, RFID, UWB, or the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters or the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, or the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0109] For instance, transceivers 1416 and 1426 may be respectively configured to modulate information on to a carrier waveform for transmission by the antenna(s) 1415 and 1425, and demodulate information received via the antenna(s) 1415 and 1425 for further processing by other elements of apparatuses 1410 and / or 1420. In other exemplary embodiments, transceivers 1416 and 1426 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some exemplary embodiments, apparatuses 1410 and / or 1420 may include an input and / or output device (I / O device). In certain exemplary embodiments, apparatuses 1410and / or 1420 may further include a user interface, such as a graphical user interface or touchscreen.

[0110] In certain exemplary embodiments, memory 1414 and memory 1424 store software modules that provide functionality when executed by processors 1412 and 1422, respectively. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 1410 and / or 1420. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 1410 and / or 1420. The components of apparatuses 1410 and / or 1420 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain exemplary embodiments, apparatus 1410 may optionally be configured to communicate with apparatus 1420 via a wireless or wired communications link 1430 according to any radio access technology, such as NR.

[0111] According to certain exemplary embodiments, processors 1412 and 1422, and memory 1414 and 1424 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some exemplary embodiments, transceivers 1416 and 1426 may be included in or may form a part of transceiving circuitry.

[0112] For instance, in certain exemplary embodiments, the apparatus 1410 may be controlled by the memory 1414 and the processor 1412 to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also be controlled to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus 1410 may further be controlled to receive, from the network entity, a system information block according to the determined system information block scheduling configuration.

[0113] In various exemplary embodiments, the apparatus 1420 may be controlled by the memory 1424 and the processor 1422 to determine a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also be controlled to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus 1420 may further be controlled to transmit, to the user device, a system information block according to the determined type of system information block scheduling.

[0114] In some additional exemplary embodiments, the apparatus 1410 may be controlled by the memory 1414and the processor 1412 to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also be controlled to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block and receive, from the network entity, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined system information block scheduling configuration.

[0115] In certain additional exemplary embodiments, the apparatus 1420 may be controlled by the memory 1424 and the processor 1422 to determine a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also be controlled to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration, and transmit, to the user device, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined type of system information block scheduling.

[0116] In various other exemplary embodiments, the apparatus 1410 may be controlled by the memory 1414 and the processor 1412 to receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also be controlled to determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The apparatus 1410 may further be controlled to receive, from the network entity, the system information block according to the determined system information block scheduling configuration.

[0117] In certain other exemplary embodiments, the apparatus 1420 may be controlled by the memory 1424 and the processor 1422 to determine a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also be controlled to transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The apparatus 1420 may further be controlled to transmit, to the user device, a system information block according to the system information block scheduling configuration.

[0118] In some exemplary embodiments, an apparatus (e.g., apparatus 1410 and / or apparatus 1420) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0119] In various exemplary embodiments, the apparatus 1410 may include means for receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also include means for determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus 1410 may further include means for receiving, from the network entity, a system information block according to the determined system information block scheduling configuration.

[0120] In some exemplary embodiments, the apparatus 1420 may include means for determining a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also include means for transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The system information block scheduling configuration may comprise information associated with time-frequency resources for receiving system information block based on the type of system information block scheduling. The apparatus 1420 may further include means for transmitting, to the user device, a system information block according to the determined type of system information block scheduling.

[0121] In certain additional exemplary embodiments, the apparatus 1410 may include means for receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also include means for determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and means for receiving, from the network entity, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined system information block scheduling configuration.

[0122] In some additional exemplary embodiments, the apparatus 1420 may include means for determining atype of system information block scheduling. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also include means for transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration, and means for transmitting, to the user device, a system information block via at least one of a frequency hopping pattern or a timing pattern according to the determined type of system information block scheduling.

[0123] In various other exemplary embodiments, the apparatus 1410 may include means for receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1410 may also include means for determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block, and means for receiving, from the network entity, the system information block according to the determined system information block scheduling configuration.

[0124] In certain other exemplary embodiments, the apparatus 1420 may include means for determining a type of system information block scheduling and information indicating support for coverage enhancement of a system information block. The type of system information block scheduling may comprise at least one of scheduling via downlink control information or direct scheduling via the master information block. The apparatus 1420 may also include means for transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration. The apparatus 1420 may further include means for transmitting, to the user device, a system information block according to the system information block scheduling configuration.

[0125] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (for example, analog and / or digital circuitry), combinations of hardware circuits and software, combinations of analog and / or digital hardware circuits with software / firmware, any portions of hardware processor(s) with software, including digital signal processors, that work together to cause an apparatus (for example, apparatus 1410 and / or 1420) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor or multiple processors, or portion of a hardware circuit or processor, and the accompanying software and / or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0126] A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some exemplary embodiments. The one or more computerexecutable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain exemplary embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0127] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0128] In other exemplary embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (for example, apparatuses 1410 and / or 1420), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another exemplary embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0129] According to certain exemplary embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0130] The features, structures, or characteristics of exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments. Further, the terms “cell”, “node”, “gNB”, or other similarlanguage throughout this specification may be used interchangeably.

[0131] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0132] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these exemplary embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of exemplary embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and / or fourth generation (4G) and / or sixth (6G) technology.

[0133] Partial Glossary:

[0134] 3GPP 3rd Generation Partnership Project

[0135] 5G 5th Generation

[0136] CE Coverage Enhancement

[0137] DCI Downlink Control Information

[0138] DL Downlink

[0139] EMBB Enhanced Mobile Broadband

[0140] gNB 5G or Next Generation NodeB

[0141] loT Internet of things

[0142] LPWA Low Power Wide Area

[0143] LTE Long Term Evolution

[0144] MCS Modulation and Coding Scheme

[0145] MIB Master Information Block

[0146] ML Machine Learning

[0147] NB-loT Narrowband Internet of Things

[0148] NR New Radio

[0149] NW Network

[0150] PBCH Physical Broadcast Channel

[0151] PDCCH Physical Downlink Control Channel

[0152] PDSCH Physical Downlink Data Channel

[0153] PRACH Physical Random Access Channel

[0154] RACH Random Access Channel

[0155] RRC Radio Resource Control

[0156] SFN System Frame Number

[0157] SIB System Information Block

[0158] SSB Synchronization Signal Block

[0159] TBS Transport Block Size

[0160] UE User Equipment

[0161] UL Uplink

Claims

36WE CLAIM:1 . An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block, wherein the type of system information block scheduling comprises at least one of scheduling via downlink control information or direct scheduling via the master information block; determine a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block; and receive, from the network entity, the system information block according to the determined system information block scheduling configuration.

2. The apparatus according to claim 1 , wherein a first system information block received of repetitions of the system information block comprises a plurality of repetitions of a physical downlink control channel and the remaining repetitions of the system information block are received without the physical downlink control channel.

3. The apparatus according to claim 1 or claim 2, wherein, when the coverage enhancement for the system information block is supported, successive system information block transmissions are repetitions that are to be combined for the coverage enhancement, wherein the number of successive system information block transmissions is indicated in the master information block.

4. The apparatus according to any one of claims 1-3, wherein when the type of system information block scheduling is scheduling via downlink control information, the system information block is scheduled via a physical downlink control channel, and the physical downlink control channel that schedules a first system information block transmission within a time interval is repeated within a predetermined extended control resource set region.

5. The apparatus according to claim 4, wherein repetitions of the physical downlink control channel in the extended control resource set span across both frequency and time, wherein the extended control resource set region is predetermined by being defined in at least one of a specification or signalled in the master information37 block; or wherein a repetition pattern of the repetitions of the physical downlink control channel are at least one of predetermined, signalled in the master information block, or predefined in a specification.

6. The apparatus according to any one of claims 1 -5, wherein a content of the system information block is the same for all repetitions, wherein different redundancy versions of the system information block are received, which are at least one of predetermined in a specification or signalled in the master information block.

7. The apparatus according to any one of claims 1-6, wherein the stored instructions, when executed by the at least one processor, further cause the apparatus at least to: combine repetitions of the system information block and a plurality of repetitions of a physical downlink control channel in a first system information block for decoding the system information block.

8. The apparatus according to any one of claims 1-7, wherein the indication of the type of system information block scheduling is different for at least two of a plurality of synchronization signal block starting positions or for at least one of a plurality of synchronization signal block positions in a burst or for at least one of a plurality of beams, wherein the master information block is included in a synchronization signal block of at least one synchronization signal block starting position or position in the burst or the at least one of the plurality of beams.

9. The apparatus according to claims 1-8, wherein when the type of system information block scheduling is scheduling via downlink control information, the system information block is scheduled via a physical downlink control channel with a control resource set configuration and search space configuration provided in the master information block; or wherein when the type of system information block scheduling is direct scheduling via the master information block, the master information block comprises scheduling information directly indicating scheduling for the system information block.

10. The apparatus according to claim 9, wherein the physical downlink control channel is transmitted, by the network, using one or more repetitions, which are received by the apparatus, wherein the one or more repetitions of the physical downlink control channel are not contiguous in time.

11. The apparatus according to any one of claims 1-10, wherein the system information block scheduling configuration comprises information associated with time-frequency resources for receiving system informationblock repetitions based on the type of system information block scheduling.

12. The apparatus according to claim 11 , wherein when the type of system information block scheduling comprises scheduling via downlink control information, the information associated with the time-frequency resources for receiving the repetitions of the system information block are determined based on corresponding downlink control information indications; or wherein when the type of system information block scheduling comprises direct scheduling via the master information block, information associated with the time-frequency resources for receiving the repetitions of the system information block are determined based on a configuration received in the master information block.

13. The apparatus according to any one of claims 1-12, wherein the information associated with the timefrequency resources comprises at least one of: scheduling information associated with the time-frequency resources for receiving repetitions of the system information block; or the time-frequency resources for receiving repetitions of the system information block.

14. The apparatus according to any one of claims 1-13, wherein the system information block scheduling is configured for receiving repetitions of the system information block, wherein the repetitions of the system information block are not contiguous in time; or wherein repetitions of the system information block are all received in the same frequency resources or are hopped in frequency according to a predetermined pattern.

15. The apparatus according to any one of claims 1-14, wherein the master information block comprises at least one of a first field comprising the indication of the type of system information block scheduling or a second field comprising scheduling information corresponding to the type of system information block scheduling indicated in the first field.

16. The apparatus according to claim 15, wherein the scheduling information further comprises at least one of: an indication of modulation and coding scheme, an indication of transport block size, a repetition number of the system information block, or time-frequency resources of the system information block, an index of a table with combinations of at least two parameters, wherein the parameters comprise at least one of: the indication of modulation and coding scheme, theindication of transport block size, the repetition number of the system information block, or the time-frequency resources of the system information block.

17. The apparatus according to any one of claims 1-16, wherein the stored instructions, when executed by the at least one processor, further cause the apparatus at least to: determine and select at least one beam from a plurality of beams for the system information block scheduling based on the at least one selected beam having a highest performance metric among performance metrics of the plurality of beams; or determine and select the at least one selected synchronization signal block from a plurality of synchronization signal blocks based on the at least one selected synchronization signal block having a highest performance metrics among the performance metrics of the plurality of synchronization signal blocks.

18. The apparatus according to any one of claims 1-17, wherein the stored instructions, when executed by the at least one processor, further cause the apparatus to perform at least one of: operate in a power saving state for one or more of the repetitions of the system information block based on at least a coverage enhancement level of a cell in which the apparatus is located; receive an indication or information on when the network entity will provide the system information block with support for each coverage enhancement level; or based on an indicated timing, determine to stay in a power saving mode until a next time period when the system information block will be scheduled in accordance with a coverage enhancement level.

19. The apparatus according to any one of claims 1-18, wherein different preambles or sequences are associated with each of the types of system information block scheduling.

20. The apparatus according to any one of claims 1-19, wherein a plurality of time periods when each of the types of system information block scheduling is supported is: an indication in the master information block indicates which time period is utilized, or directly indicated when the system information block supporting a certain coverage enhancement level is to be provided, wherein the master information block indicates that system information block is to be provided in a certain number of future subframes relative to a subframe in which the indication is provided.21 . An apparatus comprising: at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine a type of system information block scheduling and information indicating support for coverage enhancement of a system information block, wherein the type of system information block scheduling comprises at least one of scheduling via downlink control information or direct scheduling via the master information block; transmit, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration; and transmit, to the user device, a system information block according to the system information block scheduling configuration.

22. The apparatus according to claim 21 , wherein a first system information block transmitted in repetitions of the system information block comprises a plurality of repetitions of a physical downlink control channel and the remaining repetitions of the system information block are transmitted without the physical downlink control channel.

23. The apparatus according to claim 21 or claim 22, wherein, when the coverage enhancement for the system information block is supported, successive system information block transmissions are repetitions that are to be combined for the coverage enhancement, wherein the number of successive system information block transmissions is indicated in the master information block.

24. The apparatus according to any one of claims 21-23, wherein when the type of system information block scheduling is scheduling via downlink control information, the system information block is scheduled via a physical downlink control channel, and the physical downlink control channel that schedules a first system information block transmission within a time interval is repeated within a predetermined extended control resource set region.

25. The apparatus according to claim 24, wherein repetitions of the physical downlink control channel in the extended control resource set span across both frequency and time, wherein the extended control resource set region is predetermined by being defined in at least one of a specification or signalled in the master information block, wherein a repetition pattern of the repetitions of the physical downlink control channel are at least one of predetermined, signalled in the master information block, or predefined in a specification.4126. A method, comprising: receiving, from a network entity, a master information block comprising an indication of a type of system information block scheduling and information indicating support for coverage enhancement of a system information block, wherein the type of system information block scheduling comprises at least one of scheduling via downlink control information or direct scheduling via the master information block; determining a system information block scheduling configuration based on the type of system information block scheduling indicated in the master information block; and receiving, from the network entity, the system information block according to the determined system information block scheduling configuration.

27. A method, comprising: determining a type of system information block scheduling and information indicating support for coverage enhancement of a system information block, wherein the type of system information block scheduling comprises at least one of scheduling via downlink control information or direct scheduling via the master information block; transmitting, to a user device, a master information block comprising at least one of an indication of the determined type of system information block scheduling or information associated with a system information block scheduling configuration; and transmitting, to the user device, a system information block according to the system information block scheduling configuration.

Images