Configuration of PDCCH

Abstract

Example embodiments of the present disclosure relate to apparatuses, methods, and computer-readable storage media for configuration of a physical control channel (PDCCH). In a method, a first device receives a master information block (MIB) message from a second device. At least one bit in the MIB message indicates at least one configuration associated with a plurality of repetitions of the PDCCH transmission. Based on the at least one configuration, the first device monitors a plurality of repetitions of PDCCH transmissions from the second device.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to apparatus, methods, and computer-readable storage media for configuration of a physical control channel (PDCCH). Background Art

[0002] In the 3rd Generation Partnership Project (3GPP) Release 18 (Rel-18), the solution developed by New Radio (NR) coverage enhancement is applied to NTN, and potential issues and enhancements are identified, taking into account the characteristics of non-terrestrial networks (NTNs), including large propagation delays and satellite mobility. In the preliminary study phase, the coverage performance of different uplink (UL) and downlink (DL) channels is evaluated, and the bottleneck channels are identified. Such identification results in the following goals for NTN: specify physical uplink control channel (PUCCH) enhancements for message 4 (Msg4) hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (e.g., repetition), and study demodulation reference signal (DMRS) bundling for physical uplink shared channel (PUSCH) taking into account NTN details (e.g., time-frequency pre-compensation), and if necessary, specify enhancements to Release 17 (Rel-17) procedures. It is proposed that the scope of Msg4 HARQ-ACK can be extended to cover the case of PUCCH transmission for HARQ-ACK when dedicated PUCCH resources have not been configured (where only the target UE supports PUCCH repetition). Some DL channels also need enhancement. Summary of the invention

[0003] In a first aspect of the present disclosure, a first device is provided. The first device includes at least one processor; and at least one memory, the at least one memory storing instructions, the instructions when executed by the at least one processor, causing the first device to at least: receive a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates that at least one configuration is associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and based on the at least one configuration, monitor multiple repetitions of the PDCCH transmission from the second device.

[0004] In a second aspect of the present disclosure, a second device is provided. The second device includes: at least one processor; and at least one memory, wherein the at least one memory stores instructions, and when the instructions are executed by the at least one processor, the second device at least: sends a MIB message to a first device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a PDCCH transmission; and based on the at least one configuration, sends multiple repetitions of the PDCCH transmission to the first device.

[0005] In a third aspect of the present disclosure, a method is provided. The method includes receiving a MIB message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of PDCCH transmission; and based on the at least one configuration, monitoring multiple repetitions of PDCCH transmission from the second device.

[0006] In a fourth aspect of the present disclosure, a method is provided. The method includes: sending a MIB message to a first device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of PDCCH transmission; and sending multiple repetitions of PDCCH transmission to the first device based on the at least one configuration.

[0007] In a fifth aspect of the present disclosure, a first device is provided. The first device includes: a component for receiving a MIB message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a PDCCH transmission; and a component for monitoring the multiple repetitions of the PDCCH transmission from the second device based on the at least one configuration.

[0008] In a sixth aspect of the present disclosure, a second device is provided. The second device includes: a component for sending a MIB message to a first device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a PDCCH transmission; and a component for sending multiple repetitions of a PDCCH transmission to the first device based on the at least one configuration.

[0009] In a seventh aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and the instructions are used to cause a device to at least execute the method according to the third aspect or the fourth aspect.

[0010] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0012] Figure 1 An example communication environment is shown in which example embodiments of the present disclosure can be implemented;

[0013] Figure 2 A signaling diagram illustrating an example communication process according to some example embodiments of the present disclosure;

[0014] Figure 3An example process of PDCCH repetition configuration according to some example embodiments of the present disclosure is shown;

[0015] Figure 4 A flowchart illustrating an example method of PDCCH configuration according to some example embodiments of the present disclosure;

[0016] Figure 5 A flowchart illustrating another example method of PDCCH configuration according to some example embodiments of the present disclosure;

[0017] Figure 6 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0018] Figure 7 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

[0019] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0020] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for the purpose of illustration, and help those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. In addition to the embodiments described below, the embodiments described herein can be implemented in various ways.

[0021] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0022] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, whether or not explicitly described, it is considered within the knowledge of those skilled in the art that such feature, structure, or characteristic may be affected in conjunction with other embodiments.

[0023] It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0024] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, refer to at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0025] As used herein, unless explicitly stated, performing a step "in response to A" does not indicate that the step is performed immediately after "A" occurs, but may include one or more intermediate steps.

[0026] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to also include the plural forms. It will be further understood that when used herein, the terms "include", "comprise", "have", "have", "include" and / or "include" specify the presence of features, elements and / or parts, etc., but do not exclude the presence or addition of one or more other features, elements, parts and / or combinations thereof.

[0027] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0028] (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuits) and

[0029] (b) a combination of hardware circuitry and software such as (where applicable):

[0030] (i) a combination of analog and / or digital hardware circuits and software / firmware and

[0031] (ii) a hardware processor and software (including a digital signal processor), any portion of software and memory, which work together to enable a device (such as a mobile phone or server) to perform various functions and (c) a hardware circuit and / or processor, such as a microprocessor or a portion of a microprocessor, which requires software (e.g. firmware) to operate, but the software may be absent when not required for operation.

[0032] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0033] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocol and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there are of course future types of communication technologies and systems that can implement the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned system.

[0034] As used herein, the term "network device" refers to the following node in a communication network, via which a terminal device accesses the network and receives services from it. A network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, an integrated access and backhaul (IAB) node, a low-power node such as a femto station, a micro station, a non-terrestrial network (NTN) or non-terrestrial network equipment, such as satellite network equipment, a low earth orbit (LEO) satellite and a geosynchronous orbit (GEO) satellite, an aircraft network device, etc., depending on the terminology and technology applied. In some example embodiments, a radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. An IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a UE toward a parent node, and a DU portion of an IAB node behaves similarly to a base station toward a next-hop IAB node.

[0035] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback facility, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a wireless user terminal equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automatic processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) part of an IAB node (eg, a relay node).In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0036] As used herein, the terms "resource", "transmission resource", "resource block", "physical resource block" (PRB), "uplink resource" or "downlink resource" may refer to any resource used to perform communication, for example, communication between a terminal device and a network device, such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other resource supporting communication. In the following, unless explicitly stated, resources in the frequency domain and the time domain will be used as examples of transmission resources for describing some example embodiments of the present disclosure. It should be noted that the example embodiments of the present disclosure are also applicable to other resources in other domains.

[0037] As mentioned above, in Rel-18, coverage enhancement for NTN is mainly focused on UL enhancements, such as enhancements to Msg4 HARQ-ACK and enhancements to the DMRS bundling framework for PUSCH. However, some DL channels also need to be enhanced. When satellite power limitations are considered (due to, for example, regulatory requirements or power splitting between satellite beams), channels related to initial access need to be enhanced for downlink coverage enhancement. Such channels may include the Physical Downlink Control Channel (PDCCH), the Physical Downlink Shared Channel (PDSCH) for Message 2 (Msg2), and the PDSCH for Msg4. For example, when considering power flux density (PFD) limitations or more generally limitations on satellite output power, coverage enhancement for PDCCH is needed to improve channel performance.

[0038] To improve coverage, the following approaches may be considered: (a) reducing interference and noise contributions, (b) increasing transmission power, and (c) increasing energy per bit (by reducing the payload or transmitting over a longer time). However, approach (a) is not relevant to PDCCH enhancement, and approach (b) is not feasible due to PFD limitations. Approach (c) may be achieved by introducing repetitions of the channel to be enhanced. For example, to improve the physical layer performance of the channel, a larger amount of resources may be allocated to data or control channel transmissions for a specific number of bits (in the case of data and / or control channels). This is achieved by repeating the transmission of the payload data multiple times so that the receiver has the possibility to combine the received signals and improve the reliability of the demodulated and decoded bits.

[0039] In Rel-17, repetition of UE-specific search space (USS) PDCCH has been specified for multiple transmission and reception point (TRP) features, and such a mechanism can be extended for NTN, at least for PDCCH in radio resource control (RRC) connected mode. However, the repetition feature does not apply to PDCCH in initial access, and in particular not to configured Type0-PDCCH. In an enhancement of the coverage of Type0-PDCCH, Type0-PDCCH can be repeated multiple times in the same or different time slots, allowing the UE to combine the received Type0-PDCCH transmissions.

[0040] However, in order to be able to combine multiple Type0-PDCCH repetitions, it is beneficial for the UE to at least know whether the gNB is transmitting and preferably how many repetitions the gNB has sent, and therefore possibly determine the time span of the Type0-PDCCH repetitions. Therefore, there is a need for a configuration method for Type0-PDCCH with repetitions.

[0041] The exemplary embodiments of the present disclosure propose a configuration scheme for PDCCH coverage enhancement. This scheme uses at least one bit in a master information block (MIB) message to indicate PDCCH coverage enhancement, such as PDCCH repetition, a larger aggregation level of PDCCH (i.e., aggregation level 32), extended PDCCH resources, etc. In some embodiments, one or more fields or bits in the MIB may be used or repurposed to convey the configuration of PDCCH repetition.

[0042] In this way, the receiver (such as a UE) can know that it is operating under a specific deployment of PDCCH coverage enhancement (such as PDCCH repetition). Some additional operations, such as monitoring of PDCCH repetition, can be implemented under this deployment. Therefore, PDCCH coverage enhancement can be implemented effectively and efficiently.

[0043] It should be noted that although the proposed solution is derived from the NTN scenario, the solution proposed in this article can be generally applied to any deployment scenario. In the following, some example embodiments will be described using PDCCH repetition as an example implementation of PDCCH coverage enhancement, while the example embodiments in this article can be generally applied to any other implementation of PDCCH coverage enhancement. In addition, some example embodiments will be described using Type0-PDCCH as an example implementation of PDCCH, while the example embodiments in this article can be generally applied to any other type of PDCCH.

[0044] Figure 1 An example communication environment 100 is shown in which example embodiments of the present disclosure can be implemented.

[0045] In a communication environment 100, a plurality of communication devices including a first device 110 and a second device 120 can communicate with each other. In an example, the first device 110 can operate as a terminal device, such as a UE, and the second device 120 can operate as a network device, such as a gNB. The second device 120 can serve a coverage area, referred to as a cell 125. The first device 110 can access a communication network via the cell 125.

[0046] In some example embodiments, the third device 130 may also be deployed in the communication environment 100, which may communicate with both the first device 110 and the second device 120. In an example, the third device 130 may operate as another terminal device. In some example embodiments, the first device 110, the second device 120, and the third device 130 may be configured to implement beamforming technology and communicate with each other via multiple beams.

[0047] Hereinafter, for the purpose of illustration, some example embodiments are described in the case where the first device 110 operates as a terminal device and the second device 120 operates as a network device. However, in some example embodiments, the operations described with respect to the terminal device may be implemented at a network device or other device, and the operations described with respect to the network device may be implemented at a terminal device or other device.

[0048] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is referred to as DL, and the link from the first device 110 to the second device 120 is referred to as UL. In the DL, the second device 120 is a Tx device (or a transmitter), and the first device 110 is an Rx device (or a receiver). In the UL, the first device 110 is a Tx device (or a transmitter), and the second device 120 is an Rx device (or a receiver). If both the first device 110 and the second device 120 are terminal devices, the link between the first device 110 and the second device 120 is referred to as a sidelink (SL). In the SL, one of the first device 110 and the second device 120 is a Tx device (or a transmitter), and the other of the first device 110 and the second device 120 is an Rx device (or a receiver).

[0049] The communication in the communication environment 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), etc., wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. In addition, the communication can utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or developed in the future.

[0050] It should be understood that the number of devices and their connections are shown for illustration purposes only. Figure 1 Communication environment 100 may include any suitable number of devices configured to implement example embodiments of the present disclosure.

[0051] In some example embodiments, during a cell search, a UE (which may be an example implementation of the third device 130) may determine a control resource set (CORESET) and a search space (e.g., a time domain location) for Type0-PDCCH from a MIB message from a gNB (which may be an example implementation of the second device 120).

[0052] The MIB is carried by a physical channel called the Physical Broadcast Channel (PBCH), and the PBCH is part of the SS / PBCH Block (SSB). The SSB carries the PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal), and the PBCH.

[0053] MIB messages can be defined as follows:

[0054]

[0055] The field cellBarred indicates whether the cell is barred. This field may be ignored by an Integrated Access Backhaul Mobile Terminal (IAB-MT). This field may also be ignored for connections to NTN.

[0056] The field ssb-SubcarrierOffset indicates the frequency domain offset between the synchronization signal and physical broadcast channel (PBCH) block (SS / PBCH block or SSB) and the total resource block grid in subcarrier numbers. This field corresponds to k SSB Or k_ssb. The value range of this field can be extended by an additional most significant bit (MSB) encoded within the physical broadcast channel (PBCH). This field can indicate that the cell does not provide system information block 1 (SIB1) and therefore there is no CORESET (also called CORESET#0 or CORESET 0) for the Type0-PDCCH common search space (CSS) set configured in the MIB. In this case, the field pdcch-ConfigSIB1 can indicate in units of global synchronization channel number (GSCN) where the UE can or cannot find the frequency location of the SS / PBCH with the control resource set and search space for SIB1. The parameters pdcch-ConfigSIB1 and k_ssb used to determine whether CORESET 0 exists and for determining the time-frequency location of CORESET0 and Type0-PDCCH monitoring opportunities are transmitted via MIB messages.

[0057] CORESET0 is a specific type of CORESET that carries PDCCH / DCI for SIB1. Resource allocation for CORESET0 (i.e., time domain and frequency domain resource allocation) is configured by MIB (i.e., carried in PBCH in SSB). Other types of CORESET are configured by, for example, SIB or RRCSetup / RRCReconfiguration, but CORESET0 cannot be configured by SIB or other RRC messages because it should be known before SIB or other RRC messages are detected. The starting position of CORESET0 in the frequency domain can be defined with reference to the SSB position.

[0058] When an SS / PBCH block is detected, the UE may obtain the value from fields such as ssb-SubcarrierOffset (or k SSB The MIB parameter k_ssb or k_ssb) determines that a CORESET (i.e., CORESET0) for a Type0-PDCCH CSS set exists. For example, if for frequency range 1 (FR1), k SSB <24 or if for frequency range 2 (FR2), k SSB <12, the UE can determine that CORESET0 exists. If for FR1, k SSB >23 or if targeting FR2, k SSB >11, the UE can determine that CORESET0 does not exist. In other words, based on the value of k_ssb, the UE can understand whether CORESET0 exists for a certain SSB.

[0059] For example, if the UE determines from the MIB message that CORESET0 exists, the UE can determine the number of consecutive resource blocks and the number of consecutive symbols for CORESET0 from the controlResourceSetZero field in the pdcch-ConfigSIB1, and also determine the PDCCH monitoring opportunity from the searchSpaceZero in the pdcch-ConfigSIB1.

[0060] If the UE detects the first SS / PBCH block and determines that the CORESET for the Type0-PDCCH CSS set does not exist, and for FR1, 24≤k SSB ≤29 or for FR2, 12≤k SSB ≤13, the UE may determine the nearest global synchronization channel number (GSCN) of the second SS / PBCH block (in the corresponding frequency direction) that has a setting of 1 for the associated Type0-PDCCH CSS set. CORESET. is the GSCN of the first SS / PBCH block in FR1 and frequency range 2-1 (FR2-1) In frequency range 2-2 (FR2-2) and is the GSCN offset. If the UE detects a second SS / PBCH block and the second SS / PBCH block does not provide a CORESET for a Type0-PDCCH CSS set, the UE may ignore the information related to the GSCN of the SS / PBCH block position for performing a cell search. The first SS / PBCH block and the second SS / PBCH block (or SSB) refer to SSBs in different frequency positions (GSCN) for the same SSB index. In other words, if the UE evaluates that CORESET0 does not exist for the first SSB (k_ssb>23 in FR1), the UE may use the k_ssb and pdcch-ConfigSIB1 values ​​to determine the second frequency position where an SSB with an associated CORESET0 exists. However, if the second SSB does not actually have an associated CORESET0 (k_ssb of the second SSB is still greater than 23), the UE may ignore the information given by k_ssb>23 and pdcch-ConfigSIB1.

[0061] If the UE detects an SS / PBCH block and determines that the CORESET for the Type0-PDCCH CSS set does not exist, and for FR1, k SSB =31 or for FR2, k SSB =15, the UE can determine whether it is within the range of GSCN or within the range of GSCN There is no SS / PBCH block (SSB) with an associated Type0-PDCCH CSS set. and Determined by controlResourceSetZero and SearchSpaceZero in pdcch-ConfigSIB1 respectively. If the GSCN range is The UE may then determine that there is no information for the second SS / PBCH block having the CORESET for the associated Type0-PDCCH CSS set on the detected SS / PBCH block.

[0062] Table 1 shows the k SSB and the combination of controlResourceSet and ZerosearchSpaceZero in pdcch-ConfigSIB1 and for FR1 The mapping between:

[0063] Table 1

[0064]

[0065] In some example embodiments, PDCCH repetition is enabled between the first device 110 and the second device 120 via a MIB message. At least one configuration associated with PDCCH repetition is sent by the second device 120 to the first device 110 via at least one bit of the MIB message. Figure 2 Discuss some example implementations.

[0066] Figure 2 A signaling diagram illustrating an example communication process 200 between a first device 110 and a second device 120 according to some example embodiments of the present disclosure is shown.

[0067] like Figure 2 As shown, the second device 120 may send (210) a MIB message to the first device 110. At least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a PDCCH transmission (also referred to as PDCCH repetitions). Therefore, the first device 110 may receive (220) a MIB message indicating at least one configuration. In the example embodiment where the PDCCH is a Type 0-PDCCH, the at least one configuration may include a configuration with a repeated Type 0-PDCCH.

[0068] In some example embodiments, at least one configuration associated with PDCCH repetition may include a repetition factor for multiple repetitions. In some example embodiments, at least one configuration may include an indication that multiple repetitions are supported. Such an indication may be a trigger that specifies a repetition frame.

[0069] In some example embodiments, at least one configuration associated with PDCCH repetitions may include information regarding a starting PDCCH monitoring occasion for a plurality of repetitions.Alternatively or additionally, at least one configuration may include a periodicity of a starting PDCCH monitoring occasion for a plurality of repetitions.

[0070] At least one configuration may be indicated via the use, multiplexing and / or repurposing of a bit or field of a MIB message. In an example, at least one idle bit may be used or repurposed to convey at least one configuration. In another example, a set of bits (referred to as a "first bit set") for indicating whether a cell is barred, such as a field cellBarred, may be used or repurposed to convey a configuration.

[0071] In some example embodiments, the idle bit and the first bit set for indicating whether the cell is barred can be used together to convey the configuration associated with the PDCCH repetition. In an example, the combination of two fields (e.g., the idle bit field and the field cellBarred) can generate code points associated with different repetition factors. Table 2 shows an example mapping between Type0-PDCCH repetition factors and such code points.

[0072] Table 2

[0073] The code point generated by combining the two fields Type0-PDCCH repetition factor 00 1 01 2 10 4 11 8

[0074] It should be understood that the code points shown in Table 2 are merely illustrative and not limiting. Any form of mapping or correspondence may exist between the combination of the idle bit and the first bit set and the configuration associated with the PDCCH repetition. In addition, in an embodiment, only the idle bit or only the field cellBarred may be used to indicate a configuration, such as a repetition factor. For example, the idle bit may take the value 0 or 1, which may be mapped to a certain number of repetitions, respectively, or may trigger a specified repetition frame.

[0075] In some example embodiments, the first device 110 may determine mapping information between at least one configuration and at least one bit in the MIB message. The mapping information may be implemented, for example, in the form of a table, such as shown in Table 2. Based on the mapping information, the first device 110 may determine at least one configuration. For example, in the case where Table 2 is used to indicate the mapping information, the repetition factor may be determined by the first device 110 via a corresponding code point, such as a code point that is a combination of two bits in Table 2.

[0076] The mapping information may be predefined, for example, in the 3GPP standard.Alternatively or additionally, when the first device 110 is in an RRC connected state, the first device 110 may receive the mapping information from the second device 120, for example, via a radio resource control (RRC) message.

[0077] In some example embodiments, at least one configuration associated with PDCCH repetition may be indicated via a set of bits (referred to as a second set of bits) of a MIB message for indicating a subcarrier offset between an SSB (referred to as a first SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, such as a field ssb-SubcarrierOffset (i.e., k_ssb). For example, one or more specific entries of the field ssb-SubcarrierOffset may be used for configuration.

[0078] In some example embodiments, the second set of bits may have a value for indicating to the first device 110 at least one configuration for PDCCH transmission associated with the first SSB or another SSB (referred to as the second SSB). In an example, the value may be from a range of values. The range of values ​​may include values ​​between 24 and 29 in FR1 or values ​​between 12 and 13 in FR2. For a third device 130 that may operate as a non-PDCCH repetition supporting UE or a legacy UE, a value from the range of values ​​may indicate that no PDCCH is associated with the first SSB.

[0079] Taking the field ssb-SubcarrierOffset (indicated as k_ssb) as an example of a second bit set, a value of k_ssb between 24 and 29 for FR1 and a value of k_ssb between 12 and 13 for FR2 may be used by the second device 120 to indicate a second SSB that may have an associated CORESET0 configured with repetition. The frequency position of the second SSB may be determined by the first device 110 via the mapping in Table 1. The first SSB and the second SSB refer to SSBs in different frequency positions (GSCN) for the same SSB index. In an example, specific entries in the MIB message of the first SSB for k_ssb between 24 and 29 for FR1 (e.g., k_ssb=24) and k_ssb between 12 and 13 for FR2 (e.g., k_ssb=12) may be used to indicate to the first device 110 that such a first SSB does not have an associated CORESET0, but the second SSB has an associated CORESET0 configured with repetitions, where the repetition factor (or number of repetitions) is determined by the first device 110 via a standard specification.

[0080] In some embodiments, a value of k_ssb between 24 and 29 for FR1 and a value of k_ssb between 12 and 13 for FR2 may be used by the second device 120 to indicate a second SSB that may have an associated CORESET0 configured with a certain number of repetitions. In an example, an entry k_ssb=24 may be used to indicate to the first device 110 that such a first SSB does not have an associated CORESET0, but the second SSB has an associated CORESET0 configured with 2 repetitions (i.e., a repetition factor equal to 2). In an example, an entry k_ssb=25 may be used to indicate to the first device 110 that such a first SSB does not have an associated CORESET0, but the second SSB has an associated CORESET0 configured with 4 repetitions (i.e., a repetition factor equal to 4).

[0081] In some other embodiments, a specific entry in the MIB message for the first SSB of k_ssb between 24 and 29 for FR1 (e.g., k_ssb=24) and k_ssb between 12 and 13 for FR2 (e.g., k_ssb=12) can be used to indicate to the first device 110 that such a first SSB can have an associated CORESET0 configured with repetition. In this case, a UE with PDCCH repetition capability can interpret the value of k_ssb differently from a legacy UE. For example, for a UE with PDCCH repetition capability, the value means that the SSB is associated with CORESET0 configured with repetition. In this case, the second device 120 sends Type0-PDCCH according to the associated CORESET0 anyway. Other UEs can instead look at other SSB frequency locations (GSCN) for CORESET0, for example, as defined in the Rel-18 specification.

[0082] In some embodiments, a value of k_ssb between 24 and 29 for FR1 and a value of k_ssb between 12 and 13 for FR2 may be used by the second device 120 to indicate that the first SSB may have an associated CORESET0 configured with a particular number of repetitions. In an example, an entry k_ssb=24 may be used to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 2 repetitions (i.e., a repetition factor equal to 2). In an example, an entry k_ssb=25 may be used to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 4 repetitions (i.e., a repetition factor equal to 4).

[0083] In some example embodiments, the value of the second set of bits is a reserved value, such as 30 in FR1 or 14 in FR2, to indicate to the first device 110 that the PDCCH transmission associated with the first SSB is configured with multiple repetitions. For example, an entry k_ssb=30 for FR1 and an entry k_ssb=14 for FR2 in the MIB message of the first SSB may be used to indicate to the first device 110 that such a first SSB has an associated CORESET0 configured with repetitions. In this case, the repetition factor (or number of repetitions) may be determined by the first device 110 via a standard specification. In this case, the repetition factor (or number of repetitions) may be indicated to the first device 110 via at least one bit of the field pdcch-ConfigSIB1.

[0084] In some example embodiments, where the value of k_ssb is used to convey information about whether CORESET0 of the first SSB or the second SSB is configured with repetitions, the subcarrier offset between the first SSB and the reference resource block grid (necessary information for reception of CORESET0) may be equal to the value of the second bit set, such as k_ssb. In an example, in an embodiment where the entry k_ssb=24 is used to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 2 repetitions, k_ssb=24 may be used not only to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 2 repetitions, but may also be used to indicate that the subcarrier offset between the first SSB and the reference resource block grid is equal to 24 subcarriers.

[0085] In some example embodiments, the subcarrier offset may be associated with a value and a predetermined offset, e.g., equal to k_ssb minus an offset. In an example, in an embodiment where the entry k_ssb=24 is used to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 2 repetitions, k_ssb=24 may be used not only to indicate to the first device 110 that the first SSB has an associated CORESET0 configured with 2 repetitions, but may also indicate that the subcarrier offset between the first SSB and the reference resource block grid is equal to 24 subcarriers minus an offset in units of subcarriers. The offset may transpose values ​​of k_ssb greater than 23 within a k_ssb range between 0 and 23. In an example, the offset may be equal to 11 subcarriers, such that the subcarrier offset between the first SSB and the reference resource block grid is equal to 13 subcarriers. Alternatively or additionally, the subcarrier offset may be predefined, e.g., as a specified value. For example, the first device 110 may determine that the frequency domain offset between the SSB and the overall resource block grid (which may be transmitted to the third device 130 as a legacy UE via the value of k_ssb) is equal to k_ssb or equal to k_ssb minus the offset. In some example embodiments, the subcarrier offset may be equal to a specified value (e.g., 0).

[0086] In some example embodiments, the value of the second set of bits may indicate to the first device 110 that the SSB with the CORESET for the associated PDCCH configured with repetition is within the frequency range of the GSCN value. In an example, the value of the second set of bits may be 31 in FR1 or 15 in FR2. The value may indicate to the third device 130, which may operate as a legacy UE, that the SSB with the CORESET for the associated PDCCH is not present in the range of the GSCN.

[0087] As an example, the entry k_ssb=31 for FR1 and the entry k_ssb=15 for FR2 in the MIB message of the first SSB are used to indicate to the first device 110 that the first device 110 can find the In this case, the repetition factor (or number of repetitions) may be determined by the first device 110 via a standard specification. In this case, the repetition factor (or number of repetitions) may be determined by the first device 110 via a range The frequency position within the range in which the SSB with the associated CORESET0 configured with repetition is found is determined.

[0088] In some example embodiments, at least one configuration associated with the PDCCH repetition may be indicated via a set of bits of a MIB message (referred to as a third bit set) for indicating a CORESET, a common search space, and PDCCH parameters or for indicating a frequency location where an SSB with SIB1 can or cannot be found, such as a field pdcch-ConfigSIB1. In an example, at least one bit of the third bit set, such as a field pdcch-ConfigSIB1, may be used or repurposed to indicate the number of PDCCH repetitions.

[0089] In some example embodiments, a combination of at least one idle bit, a first set of bits (such as field cellBarred), a second set of bits (such as field k_ssb), and a third set of bits may be used to indicate where a CORESET0 having repetitions is located (e.g., associated with which SSB), and to determine the number of PDCCH repetitions for such CORESET0.

[0090] In some example embodiments, the repurposed or multiplexed bits in the MIB message may be valid for UEs with PDCCH repetition capability. Non-capable UEs (Rel-19 or Rel-18 UEs without PDCCH repetition capability) may ignore the configuration and still operate in a traditional manner, e.g., without repetition of Type0-PDCCH.

[0091] In some example embodiments, the configuration of PDCCH (such as Type 0-PDCCH) repetition may be applied to a frequency band used for NTN or an NTN frequency band. In this case, PDCCH repetition is performed via access to a specific frequency band in an NTN scenario.

[0092] like Figure 2As shown, after the second device 120 sends (210) a MIB message to the first device 110 to indicate at least one configuration associated with PDCCH repetition, the second device 120 may send (230) PDCCH repetition to the first device 110 based on the at least one configuration. Accordingly, the first device 110 may monitor (240) the PDCCH repetition from the second device 120 based on the at least one configuration.

[0093] In some example embodiments, during reception and decoding of PDCCH repetitions, first device 110 may combine the repetitions prior to decoding. In some other example embodiments, first device 110 may rely on channel variations over time to decode a single PDCCH repetition.

[0094] Figure 3 An example process 300 for PDCCH repetition configuration according to some example embodiments of the present disclosure is shown. In this example, UE 305 is an example implementation of first device 110, and gNB 310 is an example implementation of second device 120.

[0095] In process 300, at 312, UE 305 may receive a configuration of a repetition factor from gNB 310 via MIB, for example, one of the factors [1, 2, 4, 8]. The UE may then know that repetition is enabled and obtain the repetition factor, for example Figure 3 4 in the example.

[0096] In an example, the configuration of the repetition factor may be conveyed by a combination of an idle field and a cellBarred field in the MIB. For example, the idle field may be replaced by the field "Type0-PDCCH repetition", and the field may take a value of 0 or 1. The cell-Barred field may be unchanged, but repurposed so that a value of "barred" indicates a bit value of 1, and a value of "notBarred" indicates a bit value of 0. These two bits may be put together to generate a code point corresponding to the Type0-PDCCH repetition factor, as shown in Table 2 above.

[0097] An example of a MIB is shown below.

[0098] MIB::=SEQUENCE{

[0099] systemFrameNumber BIT STRING(SIZE(6)),

[0100] subCarrierSpacingCommon ENUMERATED{scs15or60,scs30or120},

[0101] ssb-SubcarrierOffset INTEGER(0..15),

[0102] dmrs-TypeA-Position ENUMERATED{pos2,pos3},

[0103] pdcch-ConfigSIB1 PDCCH-ConfigSIB1,

[0104] cellBarred ENUMERATED{barred,notBarred},

[0105] intraFreqReselection ENUMERATED{allowed,notAllowed},

[0106] Type0-PDCCH repetitions BIT STRING(SIZE(1))

[0107] }UE 305 can also know the frequency domain resources from controlResourceSetZero and the time domain resources from SearchSpaceZero from the field pdcch-ConfigSIB1. Then, UE 305 can start monitoring repetition.

[0108] like Figure 3 As shown, at 314, 316, 318, 320, 322, 324, 326, and 328, the gNB 310 may transmit the PDCCH and PDSCH in the repetition occasions of the slots and frames indicated by the system frame number (SFN). Thus, the UE 305 may monitor each repetition occasion and detect DCI 1_0 scheduling SIB1 after combining the Type0-PDCCH repetitions. The UE 305 may perform blind decoding for the Type0-PDCCH transmissions and repetitions.

[0109] In another example, the configuration of Type0-PDCCH repetition received (312) via the MIB may be carried in the field ssb-SubcarrierOffset in FR1. In this case, the MIB for the first SSB may be used to indicate to the UE 305 via the reserved entry k_ssb=30 that such first SSB has an associated CORESET0 configured with repetition. Thus, a non-capable UE (not shown) may assume that a CORESET0 associated with such a first SSB does not exist, while a UE with PDCCH repetition capability, such as the UE 305, may determine that the detected SSB has an associated CORESET0 with repetition.

[0110] In an example, the UE 305 can determine from the specification that the frequency domain offset between the first SSB and the overall resource block grid in the number of subcarriers is equal to a specified value (e.g., 0 subcarriers, which means that the overall resource block grid and the first SSB are aligned in frequency). In addition, considering that pdcch-ConfigSIB1 has a size of 8 bits, divided into 4 bits for controlResourceSetZero and 4 bits for SearchSpaceZero, the UE 305 can determine two pieces of information via the field pdcch-ConfigSIB1 in the MIB of the first SSB. In an example, the first 2 MSBs of controlResourceSetZero indicate the number of Type0-PDCCH repetitions, and the remaining 2 bits of controlResourceSetZero are used to determine the number of consecutive resource blocks and the number of consecutive symbols of CORESET0. In another example, the 2 MSBs of SearchSpaceZero indicate the number of Type0-PDCCH repetitions. Then, the UE 305 can start monitoring the PDCCH repetitions at 314.

[0111] Any type of combination of idle bits and the first set of bits, the second set of bits, and the third set of bits may be used to indicate the configuration to the UE 305 .

[0112] Example Method

[0113] Figure 4 4 is a flow chart showing an example method 400 for PDCCH configuration according to some example embodiments of the present disclosure. The method 400 may be performed as follows: Figure 1 For the purpose of discussion, reference will be made to the first device 110 shown. Figure 1 The method 400 is described from the perspective of the first device 110 .

[0114] At block 410, the first device 110 receives a MIB message from the second device 120. At least one bit in the MIB message indicates at least one configuration associated with multiple repetitions of a PDCCH transmission. At block 420, based on the at least one configuration, the first device 110 monitors multiple repetitions of a PDCCH transmission from the second device 120.

[0115] In some example embodiments, at least one configuration may include at least one of: a repetition factor for the multiple repetitions; an indication that the multiple repetitions are enabled; information about a starting PDCCH monitoring opportunity for the multiple repetitions; or a period of a starting PDCCH monitoring opportunity for the multiple repetitions.

[0116] In some example embodiments, the first device 110 may determine mapping information between at least one configuration and at least one bit in the MIB message.

[0117] In some example embodiments, at least one bit in the MIB message may include at least one of: at least one idle bit; a first set of bits for indicating whether the cell is prohibited; a second set of bits for indicating a subcarrier offset between the first SSB and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or a third set of bits for indicating CORESET, common search space, and PDCCH parameters, or for indicating a frequency location where an SSB with SIB1 can or cannot be found.

[0118] In some example embodiments, a combination of at least one idle bit and the first set of bits may be used to indicate at least one configuration.

[0119] In some example embodiments, the second set of bits may include a value for indicating to the first apparatus 110 at least one configuration for PDCCH transmission associated with the first SSB or the second SSB.

[0120] In some example embodiments, the value may be from a range of values, the range of values ​​being used to indicate at least one configuration to the first apparatus 110. The value from the range of values ​​may indicate to the third apparatus 130 that no PDCCH is associated with the first SSB. In some example embodiments, the value may be between 24 and 29 in FR1 or between 12 and 13 in FR2.

[0121] In some example embodiments, the value of the second set of bits may be 30 in FR1 or 14 in FR2.

[0122] In some example embodiments, the subcarrier offset between the first SSB and the reference resource block grid may be predefined or associated with a value of the second set of bits and a predetermined offset.

[0123] In some example embodiments, the value of the second bit set may indicate to the first device 110 that the SSB with the CORESET for the associated PDCCH configured with repetition is in the range of the GSCN. The value may indicate to the third device 130 that the SSB with the CORESET for the associated PDCCH does not exist in the range of the GSCN. In some example embodiments, the value may be 31 in FR1 or 15 in FR2.

[0124] In some example embodiments, at least one bit in the third set of bits may be used to indicate a number of repetitions of a PDCCH transmission.

[0125] In some example embodiments, the PDCCH may include a Type 0-PDCCH.

[0126] In some example embodiments, PDCCH transmission may be performed in a frequency band used for NTN.

[0127] Figure 5 1 is a flow chart showing an example method 500 for PDCCH configuration according to some example embodiments of the present disclosure. The method 500 may be performed as follows: Figure 1 For the purpose of discussion, reference will be made to Figure 1 The method 500 is described from the perspective of the second device 120 .

[0128] At block 510, the second device 120 sends a MIB message to the first device 110. At least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a PDCCH transmission. At block 520, the second device 120 sends multiple repetitions of a PDCCH transmission to the first device 110 based on the at least one configuration.

[0129] In some example embodiments, at least one configuration may include at least one of: a repetition factor for the multiple repetitions; an indication that the multiple repetitions are enabled; information about a starting PDCCH monitoring opportunity for the multiple repetitions; or a period of a starting PDCCH monitoring opportunity for the multiple repetitions.

[0130] In some example embodiments, the second device 120 may determine mapping information between at least one configuration and at least one bit in the MIB message.

[0131] In some example embodiments, at least one bit in the MIB message may include at least one of: at least one idle bit; a first set of bits for indicating whether the cell is prohibited; a second set of bits for indicating a subcarrier offset between a first SSB and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH; or a third set of bits for indicating a CORESET, a common search space, and PDCCH parameters, or for indicating a frequency location where an SSB with SIB1 can or cannot be found.

[0132] In some example embodiments, a combination of at least one idle bit and the first set of bits may be used to indicate at least one configuration.

[0133] In some example embodiments, the second set of bits may include a value for indicating to the first apparatus 110 at least one configuration for PDCCH transmission associated with the first SSB or the second SSB.

[0134] In some example embodiments, the value may be from a range of values, the range of values ​​being used to indicate at least one configuration to the first apparatus 110. The value from the range of values ​​may indicate to the third apparatus 130 that no PDCCH is associated with the first SSB. In some example embodiments, the value may be between 24 and 29 in FR1 or between 12 and 13 in FR2.

[0135] In some example embodiments, the value of the second set of bits may be 30 in FR1 or 14 in FR2.

[0136] In some example embodiments, the subcarrier offset between the first SSB and the reference resource block grid may be predefined or associated with a value of the second set of bits and a predetermined offset.

[0137] In some example embodiments, the value of the second bit set may indicate to the first device 110 that the SSB with the CORESET for the associated PDCCH configured with repetition is in the range of the GSCN. The value may indicate to the third device 130 that the SSB with the CORESET for the associated PDCCH does not exist in the range of the GSCN. In some example embodiments, the value may be 31 in FR1 or 15 in FR2.

[0138] In some example embodiments, at least one bit in the third set of bits may be reused to indicate a repetition number of a PDCCH transmission.

[0139] References Figures 1 to 3 All operations and features described in relation to the first device 110 and the second device 120 are equally applicable to the methods 400 and 500 and have similar effects. For the purpose of simplicity, the details will be omitted.

[0140] Example devices, equipment, and media

[0141] In some example embodiments, a first device (eg, Figure 1 The first device 110 in the method 400 may include components for performing the corresponding operations of the method 400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module. The first device may be implemented as or included in Figure 1 In the first device 110.

[0142] In some example embodiments, a first device includes: a component for receiving a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and a component for monitoring the multiple repetitions of the PDCCH transmission from the second device based on the at least one configuration.

[0143] In some example embodiments, at least one configuration includes at least one of: a repetition factor for the multiple repetitions; an indication that the multiple repetitions are enabled; information about a starting PDCCH monitoring occasion for the multiple repetitions; or a periodicity of a starting PDCCH monitoring occasion for the multiple repetitions.

[0144] In some example embodiments, the first apparatus further comprises means for determining mapping information between at least one configuration and at least one bit in the MIB message.

[0145] In some example embodiments, at least one bit in the MIB message includes at least one of: at least one idle bit, a first set of bits for indicating whether the cell is prohibited, a second set of bits for indicating a subcarrier offset between a first synchronization signal and physical broadcast channel (PBCH) block (SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or a third set of bits for indicating a CORESET, a common search space, and PDCCH parameters, or for indicating a frequency location where an SSB with SIB1 can or cannot be found.

[0146] In some example embodiments, a combination of the at least one idle bit and the first set of bits indicates at least one configuration.

[0147] In some example embodiments, the second set of bits includes a value for indicating to the first apparatus at least one configuration for PDCCH transmission associated with the first SSB or the second SSB.

[0148] In some example embodiments, the value is from a range of values, the range of values ​​being used to indicate at least one configuration to the first apparatus, wherein the value from the range of values ​​indicates to the third apparatus that no PDCCH is associated with the first SSB.

[0149] In some example embodiments, the value is between 24 and 29 in frequency range 1 or between 12 and 13 in frequency range 2.

[0150] In some example embodiments, the value of the second set of bits is 30 in frequency range 1 or 14 in frequency range 2.

[0151] In some example embodiments, the subcarrier offset between the first SSB and the reference resource block grid is predefined or associated with a value of the second set of bits and a predetermined offset.

[0152] In some example embodiments, the value of the second bit set indicates to the first device that the SSB having a CORESET for an associated PDCCH configured with repetitions is in a range of global synchronization channel numbers (GSCN), wherein the value indicates to the third device that the SSB having a CORESET for the associated PDCCH is not present in the range of GSCN.

[0153] In some example embodiments, the value is 31 in frequency range 1 or 15 in frequency range 2.

[0154] In some example embodiments, at least one bit in the third set of bits indicates a number of repetitions of the PDCCH transmission.

[0155] In some example embodiments, the PDCCH comprises a Type 0-PDCCH.

[0156] In some example embodiments, the PDCCH transmission is performed in a frequency band for a non-terrestrial network (NTN).

[0157] In some example embodiments, the first apparatus further comprises means for performing the method 400 or other operations in some example embodiments of the first apparatus 110. In some example embodiments, the apparatus comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the first apparatus.

[0158] In some example embodiments, a second device (eg, Figure 1 The second device 120 in the method 500 may include components for performing the corresponding operations of the method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module. The second device may be implemented as or included in Figure 1 In the second device 120.

[0159] In some example embodiments, the second device includes: a component for sending a master information block (MIB) message to the first device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and a component for sending multiple repetitions of the PDCCH transmission to the first device based on the at least one configuration.

[0160] In some example embodiments, at least one configuration includes at least one of: a repetition factor for the multiple repetitions; an indication that the multiple repetitions are enabled; information about a starting PDCCH monitoring occasion for the multiple repetitions; or a periodicity of a starting PDCCH monitoring occasion for the multiple repetitions.

[0161] In some example embodiments, the second apparatus further comprises means for determining mapping information between at least one configuration and at least one bit in the MIB message.

[0162] In some example embodiments, at least one bit in the MIB message includes at least one of: at least one idle bit, a first set of bits for indicating whether the cell is prohibited, a second set of bits for indicating a subcarrier offset between a first synchronization signal and physical broadcast channel (PBCH) block (SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or a third set of bits for indicating a CORESET, a common search space, and PDCCH parameters, or for indicating a frequency location where an SSB with SIB1 can or cannot be found.

[0163] In some example embodiments, a combination of the at least one idle bit and the first set of bits indicates at least one configuration.

[0164] In some example embodiments, the second set of bits includes a value for indicating to the first apparatus at least one configuration for PDCCH transmission associated with the first SSB or the second SSB.

[0165] In some example embodiments, the value is from a range of values, the range of values ​​being used to indicate at least one configuration to the first apparatus, wherein the value from the range of values ​​indicates to the third apparatus that no PDCCH is associated with the first SSB.

[0166] In some example embodiments, the value is between 24 and 29 in frequency range 1 or between 12 and 13 in frequency range 2.

[0167] In some example embodiments, the value of the second set of bits is 30 in frequency range 1 or 14 in frequency range 2.

[0168] In some example embodiments, the subcarrier offset between the first SSB and the reference resource block grid is predefined or associated with a value of the second set of bits and a predetermined offset.

[0169] In some example embodiments, the value of the second bit set indicates to the first device that the SSB having a CORESET for an associated PDCCH configured with repetitions is in a range of global synchronization channel numbers (GSCN), wherein the value indicates to the third device that the SSB having a CORESET for the associated PDCCH is not present in the range of GSCN.

[0170] In some example embodiments, the value is 31 in frequency range 1 or 15 in frequency range 2.

[0171] In some example embodiments, at least one bit in the third set of bits is reused to indicate a number of repetitions of the PDCCH transmission.

[0172] In some example embodiments, the second apparatus further comprises means for performing the method 500 or other operations in some example embodiments of the second apparatus 120. In some example embodiments, the apparatus comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the second apparatus.

[0173] Figure 6 6 is a simplified block diagram of a device 600 suitable for implementing an example embodiment of the present disclosure. The device 600 may be provided to implement a communication device, such as Figure 1 The first device 110 or the second device 120 shown in FIG. As shown in the figure, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.

[0174] The communication module 640 is used for two-way communication. The communication module 640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communicating with other network elements. In some example embodiments, the communication module 640 may include at least one antenna.

[0175] Processor 610 may be of any type suitable for the local technology network, and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 600 may have multiple processors, such as application specific integrated circuit chips, which are time-slaved to a clock synchronized with a main processor.

[0176] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that will not persist during a power outage.

[0177] The computer program 630 includes computer executable instructions executed by the associated processor 610. The instructions of the program 630 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 630 may be stored in a memory, such as ROM 624. The processor 610 may perform any suitable actions and processes by loading the program 630 into the RAM 622.

[0178] The exemplary embodiments of the present disclosure may be implemented by a program 630 so that the device 600 may execute a program according to the present disclosure. Figures 1 to 5 Any process of the present disclosure discussed. Example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0179] In some example embodiments, the program 630 may be tangibly embodied in a computer-readable medium, which may be included in the device 600 (such as in the memory 620) or in other storage devices accessible by the device 600. The device 600 may load the program 630 from the computer-readable medium to the RAM 622 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein is a limitation of the medium itself (i.e., tangible, not a signal), not a limitation on data storage persistence (e.g., RAM versus ROM).

[0180] Figure 7 An example of a computer readable medium 700 is shown, which may be in the form of a CD, DVD or other optical storage disk. The computer readable medium 700 has a program 630 stored thereon.

[0181] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or illustrated and described using some other graphical representations, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0182] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer-readable medium (such as, non-volatile computer-readable medium). The computer program product includes computer executable instructions, such as those computer executable instructions executed in a device on a target physical or virtual processor included in a program module, to perform any method as described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0183] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller in a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0184] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0185] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0186] In addition, although operations are depicted in a particular order, this should not be construed as requiring such operations to be performed in the particular order shown or in a sequential order, or performing all illustrated operations, to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specified in a particular embodiment. Unless expressly stated, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless expressly stated, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0187] Although the present disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

[0188] In some aspects, a first apparatus for communication is provided, comprising: at least one processor; and

[0189] At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: receive a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and based on the at least one configuration, monitor the multiple repetitions of the PDCCH transmission from the second device.

[0190] In some embodiments, the at least one configuration includes at least one of: a repetition factor of the multiple repetitions; an indication that the multiple repetitions are enabled; information about a starting PDCCH monitoring opportunity for the multiple repetitions; or a period of the starting PDCCH monitoring opportunity for the multiple repetitions.

[0191] In some embodiments, the at least one memory and the at least one processor further cause the first device to: determine mapping information between the at least one configuration and the at least one bit in the MIB message.

[0192] In some embodiments, the at least one bit in the MIB message includes at least one of the following: at least one idle bit, a first bit set for indicating whether the cell is prohibited, a second bit set for indicating a subcarrier offset between a first synchronization signal and physical broadcast channel (PBCH) block (SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or a third bit set for indicating a CORESET, a common search space and PDCCH parameters, or for indicating a frequency location where an SSB with a system information block 1 (SIB1) can or cannot be found.

[0193] In some embodiments, a combination of the at least one idle bit and the first set of bits indicates the at least one configuration.

[0194] In some embodiments, the second set of bits includes a value for indicating to the first device that the at least one configuration is for PDCCH transmission associated with the first SSB or the second SSB.

[0195] In some embodiments, the value is from a range of values, the range of values ​​being used to indicate the at least one configuration to the first device, wherein the value from the range of values ​​indicates to a third device that no PDCCH is associated with the first SSB.

[0196] In some embodiments, the value is between 24 and 29 in frequency range 1 or between 12 and 13 in frequency range 2.

[0197] In some embodiments, the value of the second set of bits is 30 in frequency range 1 or 14 in frequency range 2.

[0198] In some embodiments, said subcarrier offset between said first SSB and said reference resource block grid is predefined or associated with said value of said second set of bits and a predetermined offset.

[0199] In some embodiments, the value of the second bit set indicates to the first device that an SSB having a CORESET for an associated PDCCH configured with repetitions is in a range of global synchronization channel numbers (GSCN), wherein the value indicates to a third device that an SSB having a CORESET for an associated PDCCH is not present in the range of the GSCN.

[0200] In some embodiments, the value is 31 in frequency range 1 or 15 in frequency range 2.

[0201] In some embodiments, at least one bit in said third set of bits indicates said number of repetitions of said PDCCH transmission.

[0202] In some embodiments, the PDCCH comprises Type0-PDCCH.

[0203] In some embodiments, the PDCCH transmission is performed in a frequency band for a non-terrestrial network (NTN).

[0204] In some aspects, provided is a second apparatus for communicating, comprising: at least one processor; and

[0205] At least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: send a master information block (MIB) message to the first device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and send the multiple repetitions of the PDCCH transmission to the first device based on the at least one configuration.

[0206] In some embodiments, at least one configuration includes at least one of: a repetition factor of the plurality of repetitions; an indication that the plurality of repetitions are enabled; information about a starting PDCCH monitoring opportunity for the plurality of repetitions; or a period of the starting PDCCH monitoring opportunity for the plurality of repetitions.

[0207] In some embodiments, the at least one memory and the at least one processor further cause the second device to: determine mapping information between the at least one configuration and the at least one bit in the MIB message.

[0208] In some embodiments, the at least one bit in the MIB message includes at least one of the following: at least one idle bit, a first bit set for indicating whether the cell is prohibited, a second bit set for indicating a subcarrier offset between a first synchronization signal and physical broadcast channel (PBCH) block (SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or a third bit set for indicating a CORESET, a common search space and PDCCH parameters, or for indicating a frequency location where an SSB with a system information block (SIB1) can or cannot be found.

[0209] In some embodiments, a combination of the at least one idle bit and the first set of bits indicates the at least one configuration.

[0210] In some embodiments, the second set of bits includes a value for indicating to the first device that the at least one configuration is for PDCCH transmission associated with the first SSB or the second SSB.

[0211] In some embodiments, the value is from a range of values, the range of values ​​being used to indicate the at least one configuration to the first device, wherein the value from the range of values ​​indicates to a third device that no PDCCH is associated with the first SSB.

[0212] In some embodiments, the value is between 24 and 29 in frequency range 1 or between 12 and 13 in frequency range 2.

[0213] In some embodiments, the value of the second set of bits is 30 in frequency range 1 or 14 in frequency range 2.

[0214] In some embodiments, said subcarrier offset between said first SSB and said reference resource block grid is predefined or associated with said value of said second set of bits and a predetermined offset.

[0215] In some embodiments, the value of the second bit set indicates to the first device that an SSB having a CORESET for an associated PDCCH configured with repetitions is in a range of global synchronization channel numbers (GSCN), wherein the value indicates to a third device that an SSB having a CORESET for an associated PDCCH is not present in the range of the GSCN.

[0216] In some embodiments, the value is 31 in frequency range 1 or 15 in frequency range 2.

[0217] In some embodiments, at least one bit in said third set of bits is reused to indicate said number of repetitions of said PDCCH transmission.

[0218] In some aspects, a method for communication is provided, comprising: receiving a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and based on the at least one configuration, monitoring the multiple repetitions of the PDCCH transmission from the second device.

[0219] In some aspects, a method for communication is provided, comprising: sending a master information block (MIB) message to a first device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and based on the at least one configuration, sending the multiple repetitions of the PDCCH transmission to the first device.

[0220] In some aspects, a first device for communication is provided, comprising: a component for receiving a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and a component for monitoring the multiple repetitions of the PDCCH transmission from the second device based on the at least one configuration.

[0221] In some aspects, a second device is provided, comprising: a component for sending a master information block (MIB) message to a first device, wherein at least one bit in the MIB message indicates at least one configuration, and the at least one configuration is associated with multiple repetitions of a physical downlink control channel (PDCCH) transmission; and a component for sending the multiple repetitions of the PDCCH transmission to the first device based on the at least one configuration.

[0222] In some aspects, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to perform the method according to some aspects of the present disclosure.

Claims

1. A first device for communication, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receiving a master information block (MIB) message from a second device, wherein at least one bit in the MIB message indicates at least one configuration, the at least one configuration being associated with a plurality of repetitions of a physical downlink control channel (PDCCH) transmission; as well as Based on the at least one configuration, the plurality of repetitions of the PDCCH transmission from the second apparatus are monitored.

2. The first device of claim 1, wherein the at least one configuration comprises at least one of the following: a repetition factor of the plurality of repetitions; an indication that the plurality of repetitions are enabled; information about starting PDCCH monitoring occasions for the plurality of repetitions; or A period of the plurality of repeated starting PDCCH monitoring opportunities.

3. The first device according to any one of claims 1 to 2, wherein the at least one memory and the at least one processor further cause the first device to: Determine mapping information between the at least one configuration and the at least one bit in the MIB message.

4. The first device according to any one of claims 1 to 2, wherein the at least one bit in the MIB message comprises at least one of the following: At least one spare bit, The first bit set is used to indicate whether the cell is prohibited. a second set of bits for indicating a subcarrier offset between a first synchronization signal and physical broadcast channel (PBCH) block (SSB) and a reference resource block grid, or for indicating whether the first SSB has a CORESET for an associated PDCCH, or The third bit set is used to indicate CORESET, common search space and PDCCH parameters, or to indicate the frequency location where the SSB with system information block 1 (SIB1) can or cannot be found. 5 . The first apparatus of claim 4 , wherein a combination of the at least one idle bit and the first set of bits indicates the at least one configuration.

6. The first device of claim 4, wherein the second set of bits comprises a value for indicating to the first device that the at least one configuration is for PDCCH transmission associated with the first SSB or the second SSB.

7. A first device according to claim 6, wherein the value is from a range of values, and the range of values ​​is used to indicate the at least one configuration to the first device, wherein the value from the range of values ​​indicates to a third device that no PDCCH is associated with the first SSB. 8 . The first device of claim 7 , wherein the value is between 24 and 29 in frequency range 1 or between 12 and 13 in frequency range 2. 9 . 9 . The first device of claim 6 , wherein the value of the second bit set is 30 in frequency range 1 or 14 in frequency range 2. 10 .

10. The first device according to any one of claims 6 to 9, wherein the subcarrier offset between the first SSB and the reference resource block grid is predefined or associated with the value of the second bit set and a predetermined offset.

Images