Method for transmitting and receiving SS / PBCH, and device therefor

By determining Point A based on the frequency offset after puncturing in reduced bandwidth scenarios, the method addresses the challenges of resource allocation and signaling in next-generation mobile communication systems, enhancing the reliability and efficiency of SS/PBCH transmission and reception in NR systems.

WO2024237518A1PCT designated stage expired Publication Date: 2024-11-21LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/005597
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-09-27
Filing Date
2024-04-25
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The challenge in next-generation mobile communication systems is to support explosive data traffic, high transmission rates, a large number of connected devices, very low end-to-end latency, and high energy efficiency, while existing systems face issues with resource shortages and the need for advanced technologies like dual connectivity, massive MIMO, and ultra-wideband, particularly in scenarios where the maximum bandwidth is reduced, such as 3 MHz, leading to uncertainty in determining Point A for resource allocation in SS/PBCH transmission.

Method used

A method is proposed to determine Point A based on the frequency offset between the lowest subcarrier of the lowest resource block overlapping with the SS/PBCH block after puncturing, ensuring reliable frequency resource allocation and signaling, even in narrowband scenarios, by defining Point A after puncturing, which clarifies the position of frequency resources and enhances the reliability of channel bandwidth allocation.

Benefits of technology

This approach resolves the uncertainty in frequency resource allocation, ensures reliable signaling, and expands the use cases for the NR system by addressing narrowband terminal/spectrum scenarios, improving the efficiency and reliability of SS/PBCH transmission and reception.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024005597_21112024_PF_FP_ABST
    Figure KR2024005597_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by means of a terminal, according to one embodiment of the present specification, comprises the steps of: receiving an SS / PBCH block; and receiving configuration information including information related to Point A. On the basis of the information related to Point A, a frequency offset between i) Point A and ii) the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block is determined. The lowest subcarrier of the lowest resource block overlaps the SS / PBCH block after puncturing.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for transmitting and receiving SS / PBCH

[0001] This specification relates to a method and device for transmitting and receiving SS / PBCH.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] To efficiently support diverse use cases in 5G from a cost / complexity perspective, newly introduced terminal types may have reduced maximum bandwidths. For example, the maximum bandwidth may be reduced to 3MHz.

[0005] If the maximum bandwidth is reduced (e.g., 3 MHz), the terminal may not be able to receive the entire SSB. To prevent this, SSBs can be transmitted in punctured resource regions. Meanwhile, Point A, which serves as a common reference point for resource block grids, can be obtained based on the lowest subcarrier of the lowest resource block overlapping the SSB.

[0006] As described above, when puncturing is performed, it may be ambiguous how Point A should be determined / acquired. Specifically, it may be ambiguous whether Point A is defined based on the resource block / subcarrier overlapping the SSB before puncturing, or based on the resource block / subcarrier overlapping the SSB after puncturing.

[0007] The purpose of this specification is to propose a method to solve the above-mentioned problems.

[0008] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification pertains from the description below.

[0009] A method performed by a terminal according to one embodiment of the present disclosure includes the steps of receiving a Synchronization Signal / Physical Broadcast CHannel (SS / PBCH) block and receiving configuration information including information related to Point A.

[0010] Based on the above information related to Point A, a frequency offset between i) the Point A and ii) the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block is determined.

[0011] The time-frequency structure associated with the above SS / PBCH block is based on puncturing. The lowest subcarrier of the lowest resource block is characterized in that it overlaps with the SS / PBCH block after the puncturing.

[0012] After the above puncturing, the SS / PBCH block may include 12 or 15 resource blocks.

[0013] The above 12 resource blocks may be the remaining resource blocks excluding the subcarriers based on subcarrier numbers 0 to 47 and 192 to 239 among the subcarriers based on subcarrier numbers 0 to 239 within four OFDM (Orthogonal Frequency Division Multiplexing) symbols.

[0014] The channel bandwidth associated with cell search based on the above SS / PBCH block may be less than 5 MHz.

[0015] A resource block can be defined as 12 consecutive subcarriers in the frequency domain. The common reference point of the resource block grids can be based on Point A above.

[0016] After the above puncturing, the SS / PBCH block can be used by the terminal for initial cell selection.

[0017] Common Resource Blocks (CRBs) may be numbered upward from 0 in the frequency domain. The center of subcarrier 0 of CRB 0 may coincide with Point A above.

[0018] The lowest resource block may be a CRB that overlaps with subcarrier 0 of the lowest resource block of the SS / PBCH block after the puncturing.

[0019] Physical Resource Blocks (PRBs) can be defined within a bandwidth part (BWP) based on a subset of the above CRBs.

[0020] The CRB number associated with the PRB number can be determined based on the sum of i) the PRB number and ii) the CRB number at which the BWP starts based on the CRB 0.

[0021] The above method may further include a step of receiving information related to the SS / PBCH block.

[0022] The above information related to the above SS / PBCH block can be received based on broadcast signaling.

[0023] The information related to the SS / PBCH block may include information on at least one of i) the number of resource blocks related to the SS / PBCH block after the puncturing and / or ii) locations related to the resource blocks.

[0024] Based on the fact that the information related to the SS / PBCH block is received before the puncturing, the number of resource blocks related to the SS / PBCH block after the puncturing can be determined based on a default setting.

[0025] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.

[0026] The instructions are characterized in that, based on being executed by the one or more processors, the one or more processors are set to perform all steps of any one of the methods.

[0027] A device according to another embodiment of the present disclosure comprises one or more memories and one or more processors functionally connected to the one or more memories.

[0028] Said one or more memories are characterized in that they store instructions that cause said one or more processors to perform all steps of any one of said methods based on what is executed by said one or more processors.

[0029] In another embodiment of the present disclosure, one or more non-transitory computer-readable media store instructions, the instructions being executable by one or more processors, characterized in that they cause the one or more processors to perform all steps of any one of the methods.

[0030] A method performed by a base station according to another embodiment of the present disclosure includes the steps of transmitting a Synchronization Signal / Physical Broadcast CHannel (SS / PBCH) block and transmitting configuration information including information related to Point A.

[0031] Based on the above information related to Point A, a frequency offset between i) the Point A and ii) the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block is determined.

[0032] The time-frequency structure associated with the above SS / PBCH block is based on puncturing. The lowest subcarrier of the lowest resource block is characterized in that it overlaps with the SS / PBCH block after the puncturing.

[0033] A base station operating in a wireless communication system according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and storing instructions.

[0034] The instructions are characterized in that they are executed by the one or more processors, and the one or more processors are set to perform all steps of the method.

[0035] According to an embodiment of the present specification, Point A, a common reference point for resource block grids, is defined based on the SS / PBCH block after puncturing. Therefore, the ambiguity in the criteria for identifying frequency resources used by terminals supporting channel bandwidths below 5 MHz can be resolved.

[0036] Additionally, based on puncturing, it is possible to prevent the use of different criteria (different Point As) for determining the location of frequency resources in the channel bandwidth where SS / PBCH blocks are transmitted. This ensures the reliability of frequency resource allocation and signaling based on the allocated frequency resources.

[0037] Additionally, it can contribute to expanding the use cases of NR systems by resolving issues that may arise when supporting narrowband terminal / spectrum scenarios.

[0038] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.

[0039] Figure 1 shows an example of a frame structure in an NR system.

[0040] Figure 2 shows an example of a resource grid in NR.

[0041] Figure 3 illustrates physical channels and general signal transmission used in a 3GPP system.

[0042] FIG. 4 is a drawing illustrating an SSB structure to which the method proposed in this specification can be applied.

[0043] Figure 5 illustrates the transmission of a synchronization signal block (SSB) to which the method proposed in this specification can be applied.

[0044] FIG. 6 is a flowchart illustrating DL signal / channel reception in an initial connection process to which a method according to an embodiment of the present specification can be applied.

[0045] FIG. 7 illustrates the time-frequency structure of SSB according to one embodiment of the present specification.

[0046] FIG. 8 illustrates a frequency resource region for PBCH transmission and reception according to one embodiment of the present specification.

[0047] FIG. 9 illustrates a frequency resource region for PBCH transmission and reception according to another embodiment of the present specification.

[0048] FIG. 10 illustrates an application method of a frequency resource area for PBCH transmission and reception according to one embodiment of the present specification.

[0049] FIG. 11 illustrates an application method of a frequency resource area for PBCH transmission and reception according to another embodiment of the present specification.

[0050] Figure 12 is a drawing illustrating Point A according to the conventional method.

[0051] Figure 13 is a drawing illustrating Point A according to an embodiment of the present specification.

[0052] FIG. 14 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.

[0053] FIG. 15 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0054] FIG. 16 is a drawing showing the configuration of the first device and the second device according to an embodiment of the present specification.

[0055] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0056] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0057] For clarity, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​this specification is not limited thereto. LTE refers to technology after 3GPP TS 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system.

[0058] For background information, terminology, abbreviations, etc. used in the description of this specification, reference may be made to standard documents published prior to this specification. For example, reference may be made to the following documents:

[0059] 3GPP NR

[0060] - 3GPP TS 38.211: Physical channels and modulation

[0061] - 3GPP TS 38.212: Multiplexing and channel coding

[0062] - 3GPP TS 38.213: Physical layer procedures for control

[0063] - 3GPP TS 38.214: Physical layer procedures for data

[0064] - 3GPP TS 38.215: Physical layer measurements

[0065] - 3GPP TS 38.300: NR and NG-RAN Overall Description

[0066] - 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and in RRC inactive state

[0067] - 3GPP TS 38.321: Medium Access Control (MAC) protocol

[0068] - 3GPP TS 38.322: Radio Link Control (RLC) protocol

[0069] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0070] - 3GPP TS 38.331: Radio Resource Control (RRC) protocol

[0071] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0072] - 3GPP TS 37.340: Multi-connectivity; Overall description

[0073] - 3GPP TS 23.287: Application layer support for V2X services; Functional architecture and information flows

[0074] - 3GPP TS 23.501: System Architecture for the 5G System

[0075] - 3GPP TS 23.502: Procedures for the 5G System

[0076] - 3GPP TS 23.503: Policy and Charging Control Framework for the 5G System; Stage 2

[0077] - 3GPP TS 24.501: Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

[0078] - 3GPP TS 24.502: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks

[0079] - 3GPP TS 24.526: User Equipment (UE) policies for 5G System (5GS); Stage 3

[0080] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology is emerging. Furthermore, massive MTC (Machine Type Communications), which connects multiple devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communication. Furthermore, communication system design that considers reliability- and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation radio access technologies such as eMBB (enhanced mobile broadband communication), MMTC (massive MTC), and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed, and for convenience, these technologies are referred to as NR in this specification. NR is an expression that represents an example of 5G radio access technology (RAT).

[0081] A new RAT system, including NR, uses OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, terminals operating under different numerologies can coexist within a single cell.

[0082] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0083] NR (New Rat) Numerology and Frame Structure

[0084] In NR systems, multiple numerologies can be supported. Here, the numerologies can be defined by subcarrier spacing and CP (Cyclic Prefix) overhead. In this case, multiple subcarrier spacings are defined by the basic subcarrier spacing as an integer N (or, ) can be derived by scaling. Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band.

[0085] Additionally, the NR system can support various frame structures according to multiple numerologies.

[0086] Below, we examine the OFDM (Orthogonal Frequency Division Multiplexing) numerology and frame structure that can be considered in NR systems.

[0087] The multiple OFDM numerologies supported in the NR system can be defined as shown in Table 1. μ and cyclic prefix for the bandwidth part are obtained from the RRC parameters provided by the BS.

[0088]

[0089] NR supports multiple numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0090] The NR frequency band is defined by two types of frequency ranges: FR1 and FR2. FR1 is the sub-6GHz range, while FR2 is the above-6GHz range, which can refer to millimeter wave (mmW) frequencies.

[0091] Table 2 below illustrates the definition of NR frequency bands.

[0092]

[0093] With regard to the frame structure in the NR system, the sizes of the various fields in the time domain are is expressed as a multiple of the time unit. Here, And, is. Downlink and uplink transmissions are It consists of a radio frame having a period of . Here, each radio frame is It consists of 10 subframes with a duration of . In this case, there may be one set of frames for the uplink and one set of frames for the downlink.

[0094] Transmission of uplink frame number i from a terminal (User Equipment, UE) is earlier than the start of the corresponding downlink frame from that terminal. You have to start earlier.

[0095] Numerology Regarding slots, slots are located within a subframe. are numbered in increasing order within a wireless frame. are numbered in increasing order. One slot is It consists of consecutive OFDM symbols, is determined by the numerology and slot configuration used. In a subframe, the slot The start of an OFDM symbol in the same subframe It is aligned chronologically with the beginning of the .

[0096] Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be utilized.

[0097] Table 3 shows the number of OFDM symbols per slot in normal CP. ), number of slots per wireless frame ( ), number of slots per subframe ( ), and Table 3 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0098]

[0099]

[0100] Figure 1 illustrates an example of a frame structure in an NR system. Figure 1 is provided solely for convenience of explanation and does not limit the scope of the present specification.

[0101] In the case of Table 4, as an example when μ=2, that is, when the subcarrier spacing (SCS) is 60 kHz, referring to Table 3, 1 subframe (or frame) can include 4 slots, and 1 subframe={1,2,4} slots illustrated in FIG. 1 are an example, and the number of slot(s) that can be included in 1 subframe can be defined as in Table 3.

[0102] Additionally, a mini-slot may consist of 2, 4 or 7 symbols, or may consist of more or fewer symbols.

[0103] In relation to physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts can be considered.

[0104] Below, we will look specifically at the above physical resources that can be considered in the NR system.

[0105] Figure 2 shows an example of a resource grid supported in NR.

[0106] Referring to Figure 2, for each subcarrier spacing setting and carrier, N size,μ grid *N RB sc Dog subcarriers and A resource grid of OFDM symbols is defined, where N size,μ grid is indicated by RRC signaling from BS. N size,μ grid The subcarrier spacing setting μ can vary between uplink and downlink as well.

[0107] Numerology One resource grid can be configured for each antenna port p. Numerology Each element of the resource grid for antenna port p is referred to as a resource element and has an index pair is uniquely identified by. Here, is the index in the frequency domain, refers to the position of a symbol within a subframe. When referring to a resource element in a slot, an index pair This is used. Here, am.

[0108] Numerology and resource elements for antenna port p is a complex value . In cases where there is no risk of confusion or where a specific antenna port or numerology is not specified, the indices p and can be dropped, resulting in a complex value or This can be. Also, the physical resource block is in the frequency domain. It is defined as consecutive subcarriers.

[0109] Considering that the UE may not be able to support the wide bandwidth supported by the NR system at one time, the UE may be configured to operate in a part of the frequency bandwidth of the cell (hereinafter, bandwidth part (BWP)).

[0110] The resource blocks of the NR system include physical resource blocks defined within the bandwidth part and common resource blocks numbered upward from 0 in the frequency domain for the subcarrier spacing setting μ.

[0111] Point A serves as a common reference point of the resource block grid and can be obtained as follows.

[0112] - offsetToPointA for PCell downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection, expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2;

[0113] - absoluteFrequencyPointA represents the frequency-position of point A expressed as ARFCN (absolute radio-frequency channel number).

[0114] Common resource blocks set subcarrier spacing In the frequency domain, the numbers are numbered from 0 upwards.

[0115] Setting the subcarrier spacing The center of subcarrier 0 of common resource block 0 coincides with 'point A'. Common resource block number in the frequency domain and subcarrier spacing setting The resource elements (k,l) for can be given as in the mathematical expression 1 below.

[0116]

[0117] Here, Is It can be defined relative to point A to correspond to a subcarrier centered around this point A. The physical resource blocks are numbered from 0 within the bandwidth part (BWP). are numbered up to, is the number of BWP. Physical resource block in BWP i and common resource blocks The relationship between them can be given by the mathematical expression 2 below.

[0118]

[0119] Here, may be a common resource block where BWP starts relative to common resource block 0.

[0120] Bandwidth part (BWP)

[0121] In NR systems, up to 400 MHz can be supported per carrier. If a UE operating on such a wideband carrier always operates with its radio frequency (RF) module turned on for the entire carrier, the UE battery consumption may increase. Alternatively, when considering multiple use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating within a single wideband carrier, different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within the carrier. Alternatively, each UE may have different capabilities for maximum bandwidth. Considering this, the BS may instruct the UE to operate only in a portion of the bandwidth of the wideband carrier, not the entire bandwidth, and this portion of bandwidth is called a bandwidth part (BWP). In the frequency domain, a BWP is the numerology μ within the bandwidth part i on the carrier. i A subset of contiguous common resource blocks defined for which one numerology (e.g., subcarrier spacing, CP length, slot / mini-slot duration) can be set.

[0122] Meanwhile, the BS can configure one or more BWPs within a single carrier assigned to the UE. Alternatively, if a specific BWP is overloaded with UEs, some UEs can be moved to other BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the overall bandwidth can be excluded and both BWPs on both sides of the cell can be configured within the same slot. That is, the BS can configure at least one DL / UL BWP for a UE associated with a wideband carrier, and can activate at least one DL / UL BWP among the configured DL / UL BWP(s) at a specific point in time (by L1 signaling, which is a physical layer control signal, a MAC control element (CE), which is a MAC layer control signal, or RRC signaling, etc.) and instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, or RRC signaling, etc.), or can set a timer value so that the UE switches to the determined DL / UL BWP when the timer expires. An activated DL / UL BWP is specifically referred to as an active DL / UL BWP. The UE may not receive configuration for a DL / UL BWP in situations such as when the UE is in the initial access process or before the RRC connection of the UE is set up. In this situation, the DL / UL BWP assumed by the UE is called the initial active DL / UL BWP.

[0123] Physical channels and general signal transmission

[0124] Figure 3 illustrates the physical channels and typical signal transmission used in 3GPP systems. In a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0125] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S301). To this end, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell ID. Afterwards, the terminal can receive a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a Downlink Reference Signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0126] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S302).

[0127] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (S303 to S306). To this end, the terminal may transmit a specific sequence as a preamble via a physical random access channel (PRACH) (S303 and S305) and receive a response message (RAR (Random Access Response) message) to the preamble via a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure may additionally be performed (S306).

[0128] A terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S307) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S308) as a general uplink / downlink signal transmission procedure. In particular, the terminal can receive downlink control information (DCI) via PDCCH.

[0129] A UE monitors a set of PDCCH candidates in monitoring opportunities set in one or more control element sets (CORESETs) on a serving cell according to the corresponding search space configurations. The set of PDCCH candidates to be monitored by the UE is defined in terms of search space sets, and the search space set can be a common search space set or a UE-specific search space set. A CORESET consists of a set of (physical) resource blocks having a time duration of 1 to 3 OFDM symbols. The network can configure the UE to have multiple CORESETs. The UE monitors PDCCH candidates in one or more search space sets. Here, monitoring means attempting to decode the PDCCH candidate(s) in the search space. If the UE successfully decodes one of the PDCCH candidates in the search space, the UE determines that the PDCCH has been detected in the corresponding PDCCH candidate, and performs PDSCH reception or PUSCH transmission based on the DCI in the detected PDCCH.

[0130] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. Here, the DCI on the PDCCH includes a downlink assignment (i.e., a DL grant) that includes at least modulation and coding format and resource allocation information related to a downlink shared channel, or an uplink grant that includes modulation and coding format and resource allocation information related to an uplink shared channel. The DCI has different formats depending on its intended use.

[0131] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station may include downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. The terminal may transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0132] SSB (Synchronization Signal Block) transmission and related operations

[0133] Figure 4 is a diagram illustrating an SSB structure to which the method proposed in this specification can be applied. Based on SSB, the UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurements, etc. SSB is used interchangeably with the SS / PBCH (Synchronization Signal / Physical Broadcast channel) block.

[0134] Referring to Figure 4, SSB is composed of PSS, SSS, and PBCH. SSB is composed of four consecutive OFDM symbols, and PSS, PBCH, SSS / PBCH, and PBCH are transmitted for each OFDM symbol. PSS and SSS are each composed of one OFDM symbol and 127 subcarriers, and PBCH is composed of three OFDM symbols and 576 subcarriers.

[0135] Polar coding and Quadrature Phase Shift Keying (QPSK) are applied to the PBCH. Each OFDM symbol consists of a data RE and a Demodulation Reference Signal (DMRS) RE. There are three DMRS REs per RB, and three data REs are located between the DMRS REs.

[0136] Figure 5 illustrates the transmission of a synchronization signal block (SSB) to which the method proposed in this specification can be applied.

[0137] SSB is transmitted periodically according to the SSB periodicity. The basic SSB period assumed by the UE during initial cell search is defined as 20ms. After cell access, the SSB period can be set by the network (e.g., base station) to one of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. An SSB burst set is configured at the beginning of the SSB period. An SSB burst set consists of a 5ms time window (i.e., half-frame), and an SSB can be transmitted at most L times within the SSB burst set. The maximum number of SSB transmissions L can be given as follows depending on the frequency band of the carrier. One slot contains at most two SSBs.

[0138] - For frequency range up to 3 GHz, L = 4

[0139] - For frequency range from 3GHz to 6 GHz, L = 8

[0140] - For frequency range from 6 GHz to 52.6 GHz, L = 64

[0141] The temporal position of an SSB candidate within an SS burst set can be defined as follows according to the SCS. The temporal position of an SSB candidate is indexed from 0 to L-1 in temporal order within the SSB burst set (i.e., half-frame) (SSB index).

[0142] Multiple SSBs can be transmitted within the carrier frequency span. The physical layer cell identifiers of these SSBs need not be unique, and different SSBs can have different physical layer cell identifiers.

[0143] A UE can acquire DL synchronization by detecting an SSB. Based on the detected SSB (time) index, the UE can identify the structure of the SSB burst set, thereby detecting symbol / slot / half-frame boundaries. The frame / half-frame number to which the detected SSB belongs can be identified using the system frame number (SFN) information and half-frame indication information.

[0144] The above-mentioned content can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical characteristics of the methods proposed in this specification. The methods described below are distinguished for convenience of explanation, and it is understood that certain components of one method may be substituted for or combined with other methods.

[0145] Technical terms used in this specification

[0146] UE: User Equipment

[0147] SSB: Synchronization Signal Block

[0148] MIB: Master Information Block

[0149] RMSI: Remaining Minimum System Information

[0150] FR1: Frequency Range 1. Refers to the frequency range below 6 GHz (e.g., 450 MHz to 6000 MHz).

[0151] FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) range above 24 GHz (e.g., 24250 MHz to 52600 MHz).

[0152] BW: Bandwidth

[0153] BWP: Bandwidth Part

[0154] RNTI: Radio Network Temporary Identifier

[0155] CRC: Cyclic Redundancy Check

[0156] SIB: System Information Block

[0157] SIB1: SIB1 for NR devices = RMSI (Remaining Minimum System Information). Broadcasts information necessary for NR terminals to access cells.

[0158] CORESET (COntrol REsource SET): Time / frequency resource for NR terminals to attempt candidate PDCCH decoding

[0159] CORESET#0: CORESET for Type0-PDCCH CSS set for NR devices (configured in MIB)

[0160] Type0-PDCCH CSS set: a search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0161] MO: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0162] SIB1-R: (additional) SIB1 for reduced capability NR devices. May be limited to cases where it is generated as a separate TB from SIB1 and transmitted on a separate PDSCH.

[0163] CORESET#0-R: CORESET#0 for reduced capability NR devices

[0164] Type0-PDCCH-R CSS set: a search space set in which an redcap UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0165] MO-R: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0166] Cell defining SSB (CD-SSB): SSB containing RMSI scheduling information among NR SSBs

[0167] Non-cell defining SSB (non-CD-SSB): An SSB placed in the NR sync raster but not containing RMSI scheduling information for the corresponding cell for measurement purposes. However, it may contain information indicating the location of the cell defining SSB.

[0168] SCS: subcarrier spacing

[0169] SI-RNTI: System Information Radio-Network Temporary Identifier

[0170] Camp on: "Camp on" is the UE state in which the UE stays on a cell and is ready to initiate a potential dedicated service or to receive an ongoing broadcast service.

[0171] TB: Transport Block

[0172] RSA (Redcap standalone): Redcap device 또는 service만 지원하는 cell.

[0173] SIB1(-R)-PDSCH: SIB1(-R)을 전송하는 PDSCH

[0174] SIB1(-R)-DCI: SIB1(-R)-PDSCH를 scheduling하는 DCI. DCI format 1_0 with CRC scrambled by SI-RNTI.

[0175] SIB1(-R)-PDCCH: SIB1(-R)-DCI를 전송하는 PDCCH

[0176] FDRA: Frequency Domain Resource Allocation

[0177] TDRA: Time Domain Resource Allocation (Time Domain Resource Assignment)

[0178] RA: Random Access

[0179] MSGA: preamble and payload transmissions of the random access procedure for 2-step RA type.

[0180] MSGB: response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.

[0181] RO-N: normal UE 4-step RACH and 2-step RACH(if configured)를 위한 RO(RACH Occasion)

[0182] RO-N1, RO-N2: When a separate RO is set for normal UE 2-step RACH, it is divided into RO-N1 (4-step) and RO-N2 (2-step).

[0183] RO-R: RO (RACH Occasion) set separately from RO-N for redcap UE 4-step RACH and 2-step RACH (if configured)

[0184] RO-R1, RO-R2: When separate ROs are set for redcap UE 2-step RACH, they are distinguished as RO-R1 (4-step) and RO-R2 (2-step).

[0185] PG-R: MsgA-Preambles Group for redcap UEs

[0186] RAR: Random Access Response

[0187] RAR window: the time window to monitor RA response(s)

[0188] FH: Frequency Hopping

[0189] iBWP: initial BWP

[0190] iBWP-DL(-UL): initial DL(UL) BWP

[0191] iBWP-DL(-UL)-R: (separate) initial DL(UL) BWP for RedCap

[0192] CS: Cyclic shift

[0193] NB: Narrowband

[0194] TO: Traffic Offloading

[0195] mTC; Massive Machine Type Communications

[0196] eMBB: enhanced Mobile Broadband Communication

[0197] URLLC: Ultra-Reliable and Low Latency Communication

[0198] RedCap: Reduced Capability

[0199] eRedCap: enhanced RedCap

[0200] FDD: Frequency Division Duplex

[0201] HD-FDD: Half-Duplex-FDD

[0202] DRX: Discontinuous Reception

[0203] RRC: Radio Resource Control

[0204] RRM: Radio Resource Management

[0205] IWSN: Industrial Wireless Sensor Network

[0206] LPWA: Low Power Wide Area

[0207] RB: Resource Block

[0208] CCE: Control Channel Element

[0209] AL: Aggregation Level

[0210] PRG: Physical Resource-block Group

[0211] DFT-s-OFDM: DFT-spread OFDM

[0212] PBCH: Physical Broadcast Channel

[0213] A-PBCH: Additional PBCH

[0214] BD: blind detection

[0215] EPRE: Energy Per RE

[0216] SNR: Signal-to-Noise Ratio

[0217] TDM: Time Division Multiplexing

[0218] DMRS: DeModulation Reference Signal

[0219] TDD: Time Division Duplex

[0220] In this specification, '()' can be interpreted as either excluding the contents within () or including the contents within the parentheses.

[0221] In this specification, ' / ' may mean including all of the contents separated by / (and) or including only some of the contents separated by / (or).

[0222] 5G wireless communication systems are characterized by their ability to effectively support use cases such as mMTC, eMBB, and URLLC compared to previous generations (e.g., LTE, GSM). Due to these advantages, 5G wireless communication systems are expected to create new use cases while gradually replacing previous-generation wireless communication systems for various use cases.

[0223] The improved low latency, high reliability, massive connection, and other features of the 5G wireless communication system can be applied to use cases (hereinafter referred to as NB use cases) previously supported by narrowband (NB), as follows.

[0224] [Examples of narrowband-based use cases (NB use cases)]

[0225] i) Railway mobile communication

[0226] ii) Utility / infrastructure network

[0227] iii) Wireless communications for public safety

[0228] These NB use cases were previously supported in the sub-1 GHz frequency band with a bandwidth of approximately 3 MHz using previous-generation wireless communication systems. Similarly, when trying to support the above NB use cases with a 5G wireless communication system, for example, it can be supported with a similar frequency bandwidth (approximately 3 MHz to less than 5 MHz) in the same (sub-1 GHz) frequency band. However, since the minimum channel BW supported by the current 5G NR standard is 5 MHz, to achieve this, a channel bandwidth of less than 5 MHz must first be supported.

[0229] [Examples of 5G NR frequency bands for supporting NB use cases (TS38.101-1)]

[0230] NB use cases can be supported in the following NR operating frequency bands defined in the NR standard TS38.101-1.

[0231]

[0232] Table 5 shows the UL / DL operating bands defined by NR operating bands in Frequency Range 1 (FR1).

[0233] [Example of defining a channel BW of less than 5 MHz to support NB use cases]

[0234] Table 6 shows the maximum number of RBs (N) that can be set for each UE channel BW. RB) is an example. According to Table 6, in order to support NB use cases based on 5G NR, 3 MHz UE channel BW and the maximum number of RBs that can be set at this time (N RB )(15) is defined, and the resource utilization ratio (or RU)(%) at this time is defined.

[0235]

[0236] In addition, for the newly defined 3 MHz UE channel BW, considering interference between adjacent channels and resource utilization, other N RB It is also possible to define and use values.

[0237]

[0238] For example, channel BW / N RB The same value can be applied to both DL and UL. For example, channel BW / N can be applied separately / independently to DL and UL. RB can be set / supported. The method according to the second example can be applied to the following situations: Both DL and UL should consider adjacent channel interference and resource utilization to maximize channel BW / N. RB Supports values ​​of N RB It can be used when you want to apply additional conditions for DFT precoding to UL only when determining the value.

[0239] FIG. 6 is a flowchart illustrating DL signal / channel reception during the initial connection process to which a method according to an embodiment of the present disclosure may be applied. Referring to FIG. 6 , a 5G NR terminal may receive DL signals / channels in the order of S610 to S640 during the initial connection process. The specific details of the initial connection process are identical to those described in FIGS. 3 to 5 , and thus, redundant descriptions are omitted.

[0240] Conventional NR terminals can receive CORESET#0 information via the MIB (Master Information Block) transmitted via the PBCH and receive initial DL signals / channels via the CORESET#0 frequency band during the initial connection process. However, considering the channel BWs exemplified in Tables 6 and 7 and the CORESET#0 bandwidths supported by the NR standard, the operation according to the conventional method described above may be inefficient in narrowband.

[0241] This specification proposes the following methods to support transmission and reception of DL broadcast signals / channels for initial access in narrowband.

[0242] In this specification, the terms narrowband, narrowband, and NB can be interpreted and applied interchangeably. In addition, channel BW, NRB, allowed / supported transmission BW, (punctured / non-punctured) PBCH BW, and maximum transmission BW can also be interpreted and applied interchangeably.

[0243] In this specification, broadcast signaling includes system information including SIB1, MIB, PBCH payload generated in the PHY layer in addition to MIB, and signaling methods using PBCH scrambling sequence and PBCH DMRS sequence initialization information.

[0244] In this specification, broadcast signaling may include cases where existing bits / fields are defined or interpreted differently. For example, in cases where some of the signaling methods using MIB, PBCH payload generated in the PHY layer in addition to MIB, PBCH scrambling sequence, and PBCH DMRS sequence initialization information that were previously used for broadcast signaling no longer require signaling, this may include cases where the corresponding bits / fields are newly defined and signaled. For example, in a narrowband frequency band that only supports 15 kHz SCS, this may include using subCarrierSpacingCommon in MIB (1 bit, {15 kHz, 30 kHz}) for other 1-bit broadcast signaling purposes. In addition, if PBCH / SIB1 / SIB1-scheduling DCI transmission for new terminals is possible without affecting legacy terminals due to frequency bands, dedicated spectrum, dedicated sync raster, etc., the above-described broadcast signaling may include a method of signaling by newly defining or interpreting differently bits / fields that were previously used for broadcast signaling purposes for legacy terminals.

[0245] PBCH transmission and reception method

[0246] In order to support reception of NR DL broadcast signals in a narrowband having a bandwidth of < 5 MHz, a subset of PBCH transmission RBs (Resource Blocks) may be transmitted. In this specification, 'transmitting a subset of PBCH transmission RBs' may mean 'transmitting the corresponding PBCH based on a subset of RBs allocated to the PBCH.'

[0247] In this specification, PBCH transmission RB may refer to RBs associated with the PBCH or RBs allocated to the PBCH in the time-frequency structure of the SS / PBCH (e.g., FIG. 7). In this specification, 'PBCH transmission RB subset' may refer to a portion of RBs associated with the PBCH or a portion of RBs allocated to the PBCH.

[0248] In this specification, PSS / SSS transmission RB may mean RBs related to PSS / SSS or RBs allocated to PSS / SSS in the time-frequency structure of SS / PBCH (e.g., FIG. 7).

[0249] In this specification, a Resource Block (RB) may be interpreted / replaced with a Physical Resource Block (PRB) or a Common Resource Block (CRB).

[0250] Figure 7 illustrates the time-frequency structure of SSB according to one embodiment of the present specification. As an example, the time / frequency structure of SSB may be defined in the NR standard.

[0251] Specifically, FIG. 7 additionally displays the number of REs / RBs for each domain in the time / frequency structure of FIG. 4. Referring to FIG. 7, the frequency domain (bandwidth) for PSS and SSS consists of 127 resource elements (REs). The frequency domain (bandwidth) for PBCH consists of 20 resource blocks (RBs) (= 144 REs) or 4 resource blocks (4 RBs) (= 48 REs).

[0252] For example, N RB = In order to support PBCH transmission and reception in a 3 MHz channel BW defined as 15 PRBs, the base station may need to transmit at least 5 PBCH transmission RBs by excluding or puncturing them among the PBCH consisting of 20 PRBs. In other words, a subset of up to 15 PBCH transmission RBs may be transmitted among the total 20 PBCH transmission RBs. In addition, in order to achieve the same level of synchronization and measurement performance as a conventional NR terminal, the PSS / SSS transmission RBs may be transmitted in their entirety. In this case, the minimum PBCH transmission RBs may be 12 RBs including PSS / SSS.

[0253] In this specification, a "punctured" PBCH or PBCH transmission RB subset refers to the PBCH actually transmitted after puncturing a portion of the PBCH transmission RBs. Therefore, the terms "punctured PBCH" and "PBCH transmission RB subset" can be interpreted and applied interchangeably.

[0254] As in the example above, N RB= In a 3 MHz channel BW defined as 15 PRBs, the base station / terminal can configure the PBCH transmission RB subset to 12 PRBs to 15 PRBs. Hereinafter, methods for configuring the PBCH transmission RB subset to 12 PRBs and 15 PRBs, respectively, are described in detail.

[0255] [Method #P1]

[0256] A method of configuring a PBCH transmission RB subset with 12 PRBs including PSS / SSS may be considered.

[0257] Method #P1 configures the PBCH transmission RB subset with only 12 PRBs including PSS / SSS. That is, the PBCH transmission RB subset can be configured with a minimum RB subset that includes the entire PSS / SSS (e.g., FIG. 8). Method #P1 can be useful when defining a single punctured PBCH or PBCH transmission RB subset and applying it to various narrowband channel BWs.

[0258] FIG. 8 illustrates a frequency resource region for PBCH transmission and reception according to one embodiment of the present specification. Specifically, FIG. 8 illustrates a PBCH transmission RB subset based on method #P1.

[0259] [Method #P2]

[0260] A method of configuring a PBCH transmission RB subset with 15 PRBs including PSS / SSS may be considered.

[0261] Method #P2 is a case where the PBCH transmission RB subset is configured with 15 PRBs including PSS / SSS.

[0262] The PBCH transmission RB subset (i.e., detailed configuration of 15 PRBs) according to the present embodiment can be determined based on one of the methods (#P2-1 to #P2-4).

[0263] Method #P2-1: Center 12 PRB (for PSS / SSS) + lower 3 PRB

[0264] Method #P2-2: Center 12 PRB (for PSS / SSS) + higher 3 PRB

[0265] Method #P2-3: Center 12 PRB (for PSS / SSS) + lower 2 PRB + higher 1 PRB

[0266] Method #P2-4: Center 12 PRB (for PSS / SSS) + higher 2 PRB + lower 1 PRB

[0267] Due to the nature of PBCH RE mapping, prioritizing lower RBs among PBCH transmission RBs may have a small performance advantage. Therefore, all other conditions being equal, Method #P2-1 may have an advantage over Method #P2-2 in terms of PBCH reception performance. Furthermore, Method #P2-3 may have an advantage over Method #P2-4 in terms of PBCH reception performance.

[0268] In addition, Method #P2-1 and Method #P2-2 may be affected in terms of sync performance and measurement performance in situations where adjacent channel / frequency interference exists because the PSS / SSS is exposed to the band edge. If such interference is expected to affect the performance, Method #P2-3 or Method #2-4 may be considered. Method #P2-3 or Method #2-4 may be intended to protect against adjacent channel / frequency band interference by placing the PSS / SSS further inside the channel BW. This will be described below with reference to FIG. 9.

[0269] FIG. 9 illustrates a frequency resource region for PBCH transmission and reception according to another embodiment of the present specification.

[0270] Figure 9 (a) illustrates method #P2-1. In this case, the PBCH transmission RB subset may include Center 12 PRBs (for PSS / SSS) + lower 3 PRBs.

[0271] Figure 9 (b) illustrates method #P2-3. In this case, the PBCH transmission RB subset may include Center 12 PRBs (for PSS / SSS) + lower 2 PRBs + higher 1 PRB.

[0272] The maximum transmission BW defined in the narrowband is N RB In this case, the PBCH transmission RB subset based on Method #P2-3 / Method #P2-4 can be determined as follows.

[0273] Method #P2-3: Center 12 PRB + lower ceil[(N RB -12) / 2] PRB + upper floor[(N RB -12) / 2] PRB

[0274] Method #P2-4: Center 12 PRB + lower floor[(N RB -12) / 2] PRB + upper ceil[(N RB -12) / 2] PRB.

[0275] The methods for determining the PBCH transmission RB subset described above can be implemented / applied as follows.

[0276] For example, one of the methods for determining a PBCH transmission RB subset can be fixedly applied to all narrowband frequency bands.

[0277] For example, methods for determining PBCH transmission RB subsets can be defined / applied for each narrowband frequency band. In other words, among the methods for determining PBCH transmission RB subsets, methods applicable to each narrowband frequency band can be predefined. As a specific example, a table indicating methods for determining PBCH transmission RB subsets applicable to each narrowband frequency band can be predefined.

[0278] For example, methods for determining a PBCH transmission RB subset can be distinguished through a dedicated sync raster. In other words, a method for determining a PBCH transmission RB subset can be determined based on a dedicated sync raster.

[0279] For example, the base station may determine one of the methods for determining the PBCH transmission RB subset and configure / instruct the terminal through broadcast signaling.

[0280] Based on a combination of the above-described examples, a method(s) for determining a PBCH transmission RB subset can be determined / applied / instructed.

[0281] [Method #1]

[0282] A method of applying the same punctured PBCH to all narrowband frequency bands may be considered.

[0283] According to method #1, the punctured PBCH determined by methods such as method #P1, method #P2, etc. is applied to all narrowband frequency bands. For example, a punctured PBCH consisting of 12 PRBs (simply, a 12-RB PBCH) can be defined based on method #P1. The 12-RB PBCH can be equally applied to both narrowbands with a channel BW of 12 PRBs and narrowbands with a channel BW of 15 PRBs.

[0284] This may offer a complexity advantage, as the base station / terminal only needs to support a single punctured PBCH. However, PBCH performance may be somewhat lower compared to supporting a PBCH with more than 12 PRBs (e.g., 15 PRBs). This is explained with reference to Figure 10.

[0285] Figure 10 illustrates a method of applying frequency resource domains for PBCH transmission and reception according to one embodiment of the present specification. Figure 10 (a) shows that a 12-RB PBCH defined based on method #P1 is applied to a narrowband with a channel BW of 12 PRBs. Figure 10 (b) shows that a 12-RB PBCH defined based on method #P1 is applied to a narrowband with a channel BW of 15 PRBs.

[0286] [Method #2]

[0287] A method of defining multiple punctured PBCHs and applying them to each narrowband (or carrier BW) can be considered.

[0288] According to method #2, multiple punctured PBCHs are defined by methods such as method #P1, method #P2, etc., and each of the multiple punctured PBCHs is applied to a narrowband or a carrier BW.

[0289] For example, a 12-RB PBCH and a 15-RB PBCH can be defined based on Method #P1 and Method #P2, respectively. The 12-RB PBCH can be applied when the narrowband channel BW is smaller than 15 PRBs. The 15-RB PBCH can be applied when the narrowband channel BW is greater than or equal to 15 PRBs. Since Method #2 must support a plurality of punctured PBCHs compared to Method #1, the complexity of the base station / terminal may increase. On the other hand, since a PBCH RB subset suitable for the narrowband channel BW is applied, there may be an advantage in terms of PBCH performance. This will be described below with reference to FIG. 11.

[0290] Figure 11 illustrates a method of applying frequency resource domains for PBCH transmission and reception according to another embodiment of the present specification. Figure 11 (a) shows that a 12-RB PBCH defined based on method #P1 is applied to a narrowband with a channel BW of 12 PRBs. Figure 11 (b) shows that a 15-RB PBCH defined based on method #P2 is applied to a narrowband with a channel BW of 15 PRBs.

[0291] [Method #A]

[0292] A method to support punctured PBCH based on network configuration may be considered.

[0293] In order to flexibly support Method #1 and Method #2 by base station selection, the following operations / configurations may be applied. The punctured PBCH applied according to the narrowband frequency band or carrier BW may not be fixed, but may be determined based on default settings and / or base station instructions. Specifically, a "default" punctured PBCH that the terminal basically assumes when receiving SSB in a narrowband may be defined. The punctured PBCH information applied by the base station in the actual narrowband frequency band or carrier BW may be indicated to the terminal through broadcast signaling. For example, if the channel BW is 15 PRB, a 12-RB PBCH may be defined as the default punctured PBCH. The base station may indicate the 12-RB PBCH or the 15-RB PBCH to the terminal based on broadcast signaling.

[0294] For the above purpose, the information indicated via the base station's broadcast signaling may be information related to a punctured PBCH transmitted in the corresponding narrowband frequency band or carrier BW. In this case, network-configurable punctured PBCHs (or punctured PBCHs supported by the standard) are predefined, and one of the predefined punctured PBCHs may be indicated via broadcast signaling.

[0295] Alternatively, the punctured PBCH information transmitted for the above purpose by broadcast signaling may be information indicating additional PBCH transmission RE / RB(s) transmitted in addition to the default punctured PBCH assumed by the terminal prior to broadcast signaling. For example, it may be assumed that the default punctured PBCH is a 12-RB PBCH and the actually transmitted punctured PBCH is a 15-RB PBCH. The punctured PBCH information transmitted based on the broadcast signaling may indicate an additional punctured PBCH transmission RB value of 3.

[0296] Additionally, the broadcast signaling information (punctured PBCH information) may include information regarding the location where the additional punctured PBCH transmission RB(s) are transmitted. In this case, in the above example, the broadcast signaling information (punctured PBCH information) may include i) additional punctured PBCH RB value 3 and ii) information indicating the location associated with the additional punctured PBCH transmission RB(s). For example, the information indicating the location may indicate whether the punctured PBCH is transmitted adjacent to the smallest RB index or the largest RB index.

[0297] In the case of Method #A, the terminal can receive the PBCH assuming the default punctured PBCH in all narrowband frequency bands or narrowband frequency bands predefined in the standard. If the terminal obtains additional or actual transmitted punctured PBCH information through broadcast signaling, the terminal can receive the punctured PBCH based on the broadcast signaling information.

[0298] In Method #A, information such as CORESET#0 BW, initial DL BWP, etc. can be transmitted by indicating a punctured PBCH through broadcast signaling. In addition, CORESET#0 BW, initial DL BWP, etc. can be determined by the punctured PBCH indicated through broadcast signaling in Method #A. For example, a punctured PBCH indicated based on Method #A can be applied as CORESET#0 BW and / or initial DL BWP.

[0299] New terminals supporting narrowband operation may be required to support all punctured PBCH(s) defined / introduced for narrowband base station / terminal operation. For example, if the 12-RB PBCH and 15-RB PBCH are supported, new terminals supporting narrowband operation may be required to support both the 12-RB PBCH and the 15-RB PBCH.

[0300] Alternatively, new terminals supporting narrowband operation may be permitted to optionally support punctured PBCH(s) defined / introduced for narrowband base station / terminal operation. For example, the aforementioned default punctured PBCH is mandatory, and additionally supported punctured PBCH(s) may be optional. These terminal requirements may be defined for each narrowband frequency band.

[0301] With respect to frequency resource domains, operations / settings are defined based on the following Table 8.

[0302]

[0303] This is explained with reference to Fig. 12.

[0304] Fig. 12 is a diagram illustrating Point A according to the conventional method. Specifically, Fig. 12 illustrates offsetToPointA based on Table 8. Referring to Fig. 12, offsetToPoint A represents a frequency offset between Point A and the lowest subcarrier (subcarrier 0) of the lowest resource block (CRB #8) overlapping with the SS / PBCH block. is the lowest numbered subcarrier (subcarrier 0) of the SS / PBCH block and the common resource block ( ) represents the subcarrier offset between subcarrier 0 and subcarrier 0. Here, the common resource block ( ) can be obtained from offsetToPointA. That is, the common resource block ( ) may be the lowest resource block overlapping with the SS / PBCH block based on offsetToPointA.

[0305] may be indicated by the ssb-SubcarrierOffset parameter within the system information block (e.g., MIB). For example, can be indicated by an integer between 0 and 15. If the ssb-SubcarrierOffset parameter is not set, can be derived from the frequency difference between SS / PBCH block and Point A.

[0306] As previously proposed [Method #P1: Configuring a PBCH transmission RB subset with 12 PRBs including PSS / SSS] or [Method #P2: Configuring a PBCH transmission RB subset with 15 PRBs including PSS / SSS], it may be assumed that not all SSBs are received due to PBCH puncturing. In this case, Point A may be determined as follows.

[0307] The terminal can determine the offsetToPointA for the PCell downlink to acquire Point A based on the SSB. The SSB can be based on i) the (actual) received SSB (SS / PBCH block) / (actual) transmitted SSB (SS / PBCH block) and / or ii) the punctured SSB (SS / PBCH block) / the SSB after puncturing (SS / PBCH block) (if SSB / PBCH puncturing is applied).

[0308] Based on the above SSB (SS / PBCH block), point A can be obtained as follows.

[0309] - offsetToPointA for PCell downlink represents the frequency offset between the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection and Point A, expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2;

[0310] - For other cases, absoluteFrequencyPointA represents the frequency-location of point A expressed as ARFCN (absolute radio-frequency channel number).

[0311] Alternatively, in this case, the previously defined operation for acquiring point A of the terminal can be modified as shown in Table 9 below.

[0312]

[0313] This is explained with reference to Fig. 13.

[0314] Fig. 13 is a diagram illustrating Point A according to an embodiment of the present specification. Descriptions overlapping with Table 8 and Fig. 12 are omitted. Referring to Fig. 13, the SS / PBCH block after puncturing may be composed of 12 resource blocks. According to the embodiment of the present specification, offsetToPoint A represents a frequency offset between Point A and the lowest subcarrier (subcarrier 0) of the lowest resource block (CRB #12) overlapping with the SS / PBCH block after puncturing.

[0315] In the above, puncturing can be applied / interpreted as truncation.

[0316] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of method #P1, method #P2, method #1, method #2, and method #A) can be processed by the device of FIG. 16 described below (e.g., processor (110, 210) of FIG. 16).

[0317] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of method #P1, method #P2, method #1, method #2, and method #A) may be stored in a memory (e.g., 140, 240 of FIG. 16) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 16).

[0318] The embodiments described below are specifically described with reference to FIGS. 14 and 15 in terms of terminal / base station operation. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.

[0319] FIG. 14 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.

[0320] Referring to FIG. 14, a method performed by a terminal according to one embodiment of the present specification includes an SS / PBCH block receiving step (S1410) and a setting information receiving step (S1420) including information related to Point A.

[0321] In S1410, the terminal receives a signal / physical broadcast channel block (Synchronization Signal / Physical Broadcast CHannel, SS / PBCH, block) from the base station.

[0322] For example, the SS / PBCH block may be a post-puncturing SS / PBCH block based on at least one of the embodiments described above.

[0323] At S1420, the terminal receives configuration information including information related to Point A from the base station.

[0324] For example, information related to the above Point A may mean the offsetToPointA parameter.

[0325] The time-frequency structure of the above SS / PBCH block, Point A, may be based on at least one of the above-described Method #P1, Method #P2, Method #1, Method #2, or Method #A. Embodiments related thereto are described in detail below.

[0326] In one embodiment, based on the information related to Point A (e.g., offsetToPointA parameter), a frequency offset between i) the Point A and ii) a lowest subcarrier of a lowest resource block overlapping with the SS / PBCH block may be determined. A time-frequency structure (e.g., see FIGS. 8 to 11 and 13) related to the SS / PBCH block may be based on puncturing. The lowest subcarrier of the lowest resource block may overlap with the SS / PBCH block after the puncturing.

[0327] In one embodiment, after the puncturing, the SS / PBCH block may include 12 or 15 resource blocks.

[0328] The above 12 resource blocks may be the remaining resource blocks excluding 8 resource blocks among 20 resource blocks based on the time-frequency structure of the existing SS / PBCH (e.g., FIG. 7). Specifically, the above 12 resource blocks may be the remaining resource blocks excluding subcarriers based on subcarrier numbers 0 to 47 and 192 to 239 among subcarriers based on subcarrier numbers 0 to 239 within 4 OFDM (Orthogonal Frequency Division Multiplexing) symbols.

[0329] The channel bandwidth associated with cell search based on the above SS / PBCH block may be less than 5 MHz. For example, the channel bandwidth may be 3 MHz.

[0330] Common resource blocks / physical resource blocks and resource block grids can be defined / determined based on the above Point A. This is described in detail below.

[0331] For example, a resource block may be defined as 12 consecutive subcarriers in the frequency domain. The common reference point of the resource block grids may be based on Point A.

[0332] For example, Common Resource Blocks (CRBs) may be numbered upward from 0 in the frequency domain. The center of subcarrier 0 of CRB 0 may coincide with Point A. The lowest resource block may be a CRB (e.g., CRB#12 in FIG. 13) that overlaps subcarrier 0 of the lowest resource block of the SS / PBCH block after the puncturing.

[0333] For example, Physical Resource Blocks (PRBs) may be defined within a bandwidth part (BWP) based on a subset of the CRBs (e.g., a portion of consecutive CRBs). A CRB number associated with a PRB number may be determined based on the sum of i) the PRB number and ii) the CRB number at which the BWP starts with respect to CRB 0. As a specific example, if the BWP starts at CRB 2, the CRB number associated with PRB 3 may be 5. That is, a resource block may be identified / designated as a CRB or a PRB. Specifically, a resource block may be identified based on a CRB number, and if the resource block is within a bandwidth part (BWP), it may be identified based on a PRB number.

[0334] In one embodiment, the SS / PBCH block after the puncturing can be used by the terminal for initial cell selection.

[0335] In one embodiment, the configuration information may be received based on broadcast signaling. Specifically, the configuration information may be information based on a System Information Block (SIB) (e.g., SIB1). As a specific example, the configuration information may be based on a FrequencyInfoDL-SIB parameter based on SIB1. The FrequencyInfoDL-SIB parameter may include the offsetToPointA parameter. More specifically, the SIB1 may include a ServingCellConfigCommonSIB parameter, the ServingCellConfigCommonSIB parameter may include a DownlinkConfigCommonSIB parameter, and the DownlinkConfigCommonSIB parameter may include the FrequencyInfoDL-SIB parameter.

[0336] The above method may further include a step of receiving information related to the SS / PBCH block. In this step, the terminal may receive information related to the SS / PBCH block from the base station. This embodiment may be based on method #A. The information related to the SS / PBCH block may be received based on broadcast signaling.

[0337] For example, the information related to the SS / PBCH block may include information on at least one of i) the number of resource blocks related to the SS / PBCH block after the puncturing (e.g., 12, 15, or the number of RBs (3) on which the SS / PBCH is transmitted in addition to the default number of RBs (12)) and / or ii) locations related to the resource blocks (e.g., the SS / PBCH block frequency location or the frequency location of an additional RB).

[0338] For example, based on the fact that the information related to the SS / PBCH block is received before the puncturing, the number of resource blocks related to the SS / PBCH block after the puncturing may be determined based on a default setting. As a specific example, based on the default setting, the number of resource blocks related to the SS / PBCH block after the puncturing may be determined to be 12. The terminal may receive the SS / PBCH block within 12 resource blocks from the base station.

[0339] The operations based on the steps S1410 to S1420 and the SS / PBCH block related information reception can be implemented by the device of FIG. 16. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operations based on the steps S1410 to S1420 and the SS / PBCH block related information reception.

[0340] The embodiments described below are specifically described in terms of base station operation.

[0341] The steps S1510 to S1520 and the SS / PBCH block-related information transmission described below correspond to the steps S1410 to S1420 and the SS / PBCH block-related information reception described in FIG. 14. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below may be replaced with the description / example of FIG. 14 corresponding to the corresponding operation.

[0342] FIG. 15 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0343] Referring to FIG. 15, a method performed by a base station according to another embodiment of the present specification includes an SS / PBCH block transmission step (S1510) and a configuration information transmission step (S1520) including information related to Point A.

[0344] In S1510, the base station transmits a signal / physical broadcast channel block (Synchronization Signal / Physical Broadcast CHannel, SS / PBCH, block) to the terminal.

[0345] In S1520, the base station transmits configuration information including information related to Point A to the terminal.

[0346] The above method may further include a step of transmitting information related to the SS / PBCH block. In the step, the base station may transmit information related to the SS / PBCH block to the terminal.

[0347] The operations based on the steps S1510 to S1520 and the SS / PBCH block related information transmission can be implemented by the device of FIG. 16. For example, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operations based on the steps S1510 to S1520 and the SS / PBCH block related information transmission.

[0348] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 16.

[0349] FIG. 16 is a drawing showing the configuration of the first device and the second device according to an embodiment of the present specification.

[0350] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0351] The processor (110) performs baseband-related signal processing and may include a higher layer processing unit (111) and a physical layer processing unit (115). The higher layer processing unit (111) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0352] The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), and software, an operating system, applications, etc. related to the operation of the first device (100), and may also include components such as a buffer.

[0353] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0354] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0355] The processor (210) performs baseband-related signal processing and may include a higher layer processing unit (211) and a physical layer processing unit (215). The higher layer processing unit (211) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0356] The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software, an operating system, applications, etc. related to the operation of the second device (200), and may also include components such as a buffer.

[0357] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0358] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.

[0359] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.

[0360] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names.

[0361] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

Claims

1. In a method performed by a terminal, A step of receiving a Synchronization Signal / Physical Broadcast CHannel (SS / PBCH, block); and A step of receiving setup information including information related to Point A; including, Based on the information related to the above Point A, a frequency offset is determined between i) the Point A and ii) the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block, The time-frequency structure associated with the above SS / PBCH block is based on puncturing, A method characterized in that the lowest subcarrier of the lowest resource block overlaps with the SS / PBCH block after the puncturing.

2. In paragraph 1, A method characterized in that after the puncturing, the SS / PBCH block includes 12 or 15 resource blocks.

3. In paragraph 2, A method characterized in that the above 12 resource blocks are resource blocks excluding subcarriers based on subcarrier numbers 0 to 47 and 192 to 239 among subcarriers based on subcarrier numbers 0 to 239 within four OFDM (Orthogonal Frequency Division Multiplexing) symbols.

4. In paragraph 3, A method characterized in that a channel bandwidth related to cell search based on the above SS / PBCH block is smaller than 5 MHz.

5. In paragraph 1, One resource block is defined as 12 consecutive subcarriers in the frequency domain. A method characterized in that a common reference point of resource block grids is based on the above Point A.

6. In paragraph 1, A method characterized in that after the puncturing, the SS / PBCH block is used by the terminal for initial cell selection.

7. In paragraph 1, Common Resource Blocks (CRBs) are numbered upward from 0 in the frequency domain. A method characterized in that the center of subcarrier 0 of CRB 0 coincides with Point A.

8. In paragraph 7, A method characterized in that the lowest resource block is a CRB overlapping with subcarrier 0 of the lowest resource block of the SS / PBCH block after the puncturing.

9. In paragraph 7, A method characterized in that physical resource blocks (PRBs) are defined within a bandwidth part (BWP) based on a subset of the above CRBs.

10. In paragraph 9, A method characterized in that the CRB number associated with the PRB number is determined based on the sum of i) the PRB number and ii) the CRB number at which the BWP starts based on the CRB 0.

11. In paragraph 1, Further comprising a step of receiving information related to the SS / PBCH block; A method characterized in that the information related to the SS / PBCH block is received based on broadcast signaling.

12. In paragraph 11, A method characterized in that the information related to the SS / PBCH block includes information on at least one of i) the number of resource blocks related to the SS / PBCH block after the puncturing and / or ii) locations related to the resource blocks.

13. In paragraph 11, A method characterized in that the number of resource blocks related to the SS / PBCH block after the puncturing is determined based on a default setting, based on the fact that the information related to the SS / PBCH block is received before the puncturing.

14. At the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 13, based on being executed by the one or more processors.

15. A device comprising one or more memories and one or more processors functionally connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said one or more processors to perform all steps of a method according to any one of claims 1 to 13, based on being executed by said one or more processors.

16. In one or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media characterized in that the instructions executable by one or more processors cause the one or more processors to perform all steps of the method according to any one of claims 1 to 13.

17. In a method performed by a base station, A step of transmitting a Synchronization Signal / Physical Broadcast CHannel (SS / PBCH, block); and A step of transmitting setup information including information related to Point A; including, Based on the information related to the above Point A, a frequency offset is determined between i) the Point A and ii) the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block, The time-frequency structure associated with the above SS / PBCH block is based on puncturing, A method characterized in that the lowest subcarrier of the lowest resource block overlaps with the SS / PBCH block after the puncturing.

18. In a base station operating in a wireless communication system, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to claim 17, based on the instructions being executed by the one or more processors.

Citation Information

Patent Citations

  • Aerosol Generating Apparatus

    KR1020210021687A

  • Randomized search space for downlink control channel

    US20190082422A1

  • User equipment and base station apparatus

    US20220182212A1

  • Improving performance for cellular communication with reduced bandwidth

    WO2023041172A1

Cited By

  • Communication method, communication device, and communication system

    WO2026156653A1