Network signaling and user equipment (UE) behavior for truncated physical broadcast channel (PBCH) less than 5 MHz
By introducing indicators in the configuration signaling of the 5G NR system, the problem that the UE cannot identify and process the truncated SSB of the neighboring cell under the condition of bandwidth less than 5MHz is solved, and accurate SSB measurement and decoding are realized, improving the adaptability and efficiency of the system.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2026-03-20
AI Technical Summary
In 5G New Radio (NR) systems with bandwidth less than 5MHz, UEs face challenges in identifying SSB types and adjusting behavior when they need to measure and decode truncated synchronization signal blocks (SSBs) in neighboring cells. At the same time, the serving base station lacks a mechanism to notify the UE of the presence of truncated SSBs in neighboring cells.
By introducing an indicator in the configuration signaling to indicate the type of SSB, the UE can determine whether the SSB of a neighboring cell is truncated or full-size, and then adjust its behavior to perform correct measurements and decoding.
It effectively solves the problem of UE measuring and decoding neighboring cell SSBs under bandwidth-limited conditions, ensuring that UE can correctly identify and process truncated SSBs, and improving the accuracy and efficiency of measurement.
Smart Images

Figure CN121713612A_ABST
Abstract
Description
[0001] Cross-referencing
[0002] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 519,287, entitled “Effect on SBI less than 5 MHz,” filed August 14, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field
[0003] This disclosure generally relates to wireless communications, and more specifically, to techniques for handling truncated physical broadcast channels (PBCH) in wireless communication systems. Background Technology
[0004] The statements in this section provide only background information in relation to this disclosure and may not constitute prior art.
[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access technologies to support communication with multiple users by sharing available system resources. Examples of these multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.
[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband driven by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology. These improvements may also apply to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention
[0007] The following provides a simplified summary of one or more aspects to provide a basic understanding of them. This summary is not a comprehensive overview of all hypothetical aspects, nor is it intended to identify key or important elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description thereafter.
[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The UE receives a synchronization signal block (SSB) and configuration signaling from a base station, the configuration signaling including an indicator indicating the type of the SSB. The UE determines the type of the SSB based on the configuration signaling. The UE determines behavior corresponding to a specific scenario based on the type of the SSB.
[0009] To achieve the foregoing and related objectives, one or more aspects include the features described in detail below and specifically pointed out in the claims. The following description and drawings detail certain illustrative features of one or more aspects. However, these features merely indicate a few ways in which the principles of various aspects can be applied, and this description is intended to include all such aspects and their equivalents. Attached Figure Description
[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.
[0011] Figure 2 This is a diagram illustrating a base station communicating with a user equipment (UE) in an access network.
[0012] Figure 3 This example illustrates the logical architecture of a distributed access network.
[0013] Figure 4 This example illustrates the physical architecture of a distributed access network.
[0014] Figure 5 This is a diagram illustrating a time slot example centered on the downlink (DL).
[0015] Figure 6 This is a diagram illustrating an example of a time slot centered on the uplink (UL).
[0016] Figure 7 This diagram illustrates a scenario where a user equipment (UE) needs to measure neighboring cells for potential handover or cell reselection.
[0017] Figure 8(A) is a diagram illustrating a complete synchronization signal block (SSB).
[0018] Figure 8(B) is a diagram illustrating the truncated synchronization signal block (SSB).
[0019] Figure 9(A) illustrates a flowchart of processing different SSB types on the user equipment (UE) side.
[0020] Figure 9(B) illustrates a flowchart of processing different SSB types on the network side. Detailed Implementation
[0021] The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form, in order to avoid obscuring the concepts.
[0022] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.
[0023] For example, one or any combination of elements or any portion of elements can be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described herein. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0024] Accordingly, in one or more example aspects, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0025] Figure 1 is a schematic diagram illustrating one example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WW AN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 can include macro cells (high power cellular base stations) and / or small cells (low power cellular base stations). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells.
[0026] The base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through backhaul links 132 (e.g., an SI interface) The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 through backhaul links 184. In addition to other functions, the base stations 102 can perform one or more of the following functions: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with one another directly or indirectly (e.g., through the EPC 160 or core network 190) over backhaul links 134 (e.g., an X2 interface). The backhaul links 134 can be wired or wireless.
[0027] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macro cells can be known as a heterogeneous network. A heterogeneous network can also include Home Evolved Node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links can be through one or more carriers, according to the carrier aggregation
[0028] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use the DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication can be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
[0029] The wireless communications system can also include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 can perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
[0030] The small cells 102' can operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' can employ New Radio (NR) and use the same 5 GHz unlicensed frequency spectrum as Wi-Fi AP 150. The small cell 102' employing NR in an unlicensed frequency spectrum can increase the coverage of the access network and / or increase the capacity of the access network.
[0031] The base stations 102, whether a small cell 102' or a macrocell, can include an eNB, gNodeB (gNB), or other type of base station. Some base stations, such as a gNB 180, can communicate with user equipment's (UEs) 104 in a traditional sub-6 GHz spectrum as well as in millimeter wave (mmW) frequencies and / or near mmW frequencies. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 can be referred to as a millimeter wave base station. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the EHF range can be referred to as a millimeter wave. Near mmW can extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends from 3 GHz to 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band (e.g., 3 GHz - 300 GHz) has extremely high path loss and a short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
[0032] The base station 180 can transmit in one or more transmission directions 108a with a beamformed signal to the UE 104. The UE 104 can receive in one or more reception directions 108b the beamformed signal from the base station 180. The UE 104 can also transmit in one or more transmission directions beamformed signals to the base station 180. The base station 180 can receive in one or more reception directions the beamformed signals from the UE 104. The base station 180 / UE 104 can perform beam training to determine the best reception and transmission directions for the base station 180 / UE 104. The transmission and reception directions for the base station 180 can or can not be the same. The transmission and reception directions for the UE 104 can or can not be the same.
[0033] The Evolved Packet Core (EPC) 160 can include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 can be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 can include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS Bearer Services, and can be used to schedule MBMS transmissions. The MBMS Gateway 168 can be used to
[0034] The core network 190 can include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Location Management Function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 can be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the SMF 194 provides QoS flow and session management. All user Internet Protocol (IP) data packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 can include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and / or other IP services.
[0035] A base station can also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a Transmitter-Receiver Point (TRP), or other suitable terminology. A base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kiosk, medical devices, implants, sensors, actuators, displays, or any other similar functional device. Some of the UEs 104 can be referred to as Internet of Things (IoT) devices (e.g., parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 can also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or by some other suitable terminology.
[0036] Although the present disclosure can refer to the 5G New Radio (NR), the present disclosure can also be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other wireless / wireless access technologies.
[0037] Figure 2is a block diagram of a base station 210 communicating with user equipment (UE) 250 in an access network. In the downlink, IP packets from the Evolved Packet Core (EPC) 160 can be provided to a controller / processor 275. The controller / processor 275 implements layer 3 and layer 2 functionality. Layer 3 includes the radio resource control (RRC) layer, and layer 2 includes the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the medium access control (MAC) layer. The controller / processor 275 provides RRC layer functionality associated with, e.g., system information (SI) acquisition, RRC connections, and measurement configuration; PDCP layer functionality associated with, e.g., header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with, e.g., unacknowledged mode (UM), acknowledged mode (AM), and AM data transfer; and MAC layer functionality associated with, e.g., priority handling, scheduling, error detection, and priority handling.
[0038] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 216 handles mapping to signal constellation points and also processes the signal constellation points based on one or more modulation schemes, such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like. The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to a orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by the UE 250. Each spatial stream can then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX can modulate an RF carrier with a respective spatial stream for transmission.
[0039] At the UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality. The RX processor 256 can spatially process the information to recover any spatial streams designated for the UE 250. If multiple spatial streams are designated for the UE 250, they can be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions can be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to the controller / processor 259, which implements layer 3 and 2 functionality.
[0040] The controller / processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 can be referred to as a computer-readable medium. In the uplink, the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP data packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an acknowledgement (ACK) and / or negative acknowledgement (NACK) protocol to support HARQ operations.
[0041] Similar to the functionality of the downlink with the base station 210, the controller / processor 259 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with upper layer PDU transmission, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs into TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0042] Channel estimates derived by the channel estimator 258 from a reference signal or feedback transmitted by the base station 210 can be used by the TX processor 268 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 can be provided to different antenna 252 via separate transmitters 254TX. Each transmitter 254TX can modulate a carrier with a respective spatial stream for transmission. The uplink transmission can be processed at the base station 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218RX can receive a signal through its respective antenna 220. Each receiver 218RX can recover information modulated onto an RF carrier and provide the information to a RX processor 270.
[0043] The controller / processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 can be referred to as a computer-readable medium. In the uplink, the controller / processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the user equipment (UE) 250. IP packets from the controller / processor 275 can be provided to the Evolved Packet Core (EPC) 160. The controller / processor 275 is also responsible for error detection using an acknowledgement (ACK) and / or negative acknowledgement (NACK) protocol to support hybrid automatic repeat request (HARQ) operations.
[0044] New radio (NR) can refer to a radio that operates according to a new air interface (e.g., other than the one used in LTE) or fixed transport layer (e.g., other than the Internet Protocol (IP)). NR can use orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) in the uplink and downlink and can include support for half-duplex operation using time division duplex (TDD). NR can include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g., 80 MHz), millimeter wave (mmW) targeting high carrier frequency (e.g., 60 GHz), massive machine type communications (mMTC) targeting non-backward compatible MTC techniques, and / or mission critical targeting ultra reliable low-latency communications (URLLC) service.
[0045] A single component carrier bandwidth of 100 MHz can be supported. In one example, an NR resource block (RB) can span 12 subcarriers with a subcarrier bandwidth of 60 kHz with a duration of 0.25 ms, or a bandwidth of 30 kHz with a duration of 0.5 ms (similarly, a 15 kHz subcarrier spacing (SCS) is 50 MHz bandwidth for a 1 ms duration). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR time slots), with a length of 10 ms. Each time slot can indicate a link direction (i.e., downlink or uplink) for data transmission, and the link direction for each time slot can be dynamically switched. Each time slot can include downlink / uplink data as well as downlink / uplink control data. The uplink and downlink slots of NR can be as described in greater detail in Figure 5 and Figure 6 .
[0046] An NR radio access network (RAN) can include one central unit (CU) and multiple distributed units (DUs). An NR base station (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) can correspond to one or more base stations. An NR cell can be configured as an access cell (Acell) or a data only cell (Dcell). For example, a RAN (e.g., central unit or distributed unit) can configure a cell. A Dcell can be a cell used for carrier aggregation or dual connectivity, and can not be used for initial access, cell selection / reselection, or handover. In some cases, a Dcell can not transmit a synchronization signal (SS), in some cases, a Dcell can transmit a SS. An NR base station can transmit a downlink signal to a UE indicating a cell type. Based on the cell type indication, the UE can communicate with the NR base station. For example, the UE can determine, based on the indicated cell type, NR base stations to consider for cell selection, access, handover, and / or measurement.
[0047] Figure 3 An example logical architecture of a distributed RAN 300 is illustrated in accordance with aspects of the present disclosure. A 5G access node 306 can include an access node controller (ANC) 302. The ANC can be a central unit (CU) of a distributed RAN. The backhaul interface to the next generation core network (NG-CN) 304 can terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) 310 can terminate at the ANC. The ANC can include one or more TRPs 308 (which can also be referred to as base stations, NR base stations, Node Bs, 5G NBs, APs, or other terminology). As described above, a TRP can be used interchangeably with “cell.”
[0048] The TRPs 308 can be a distributed unit (DU). The TRPs can be connected to one ANC (ANC 302) or multiple ANCs (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and specific services ANC deployment, the TRP can be connected to multiple ANCs. The TRPs can include one or more antenna ports. The TRPs can be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic for the UEs.
[0049] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can be defined to support fronthauling solutions across different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The architecture can share features and / or components with LTE. According to aspects, the next generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share one common fronthaul for LTE and NR.
[0050] The architecture can enable cooperation among and / or within TRPs 308. For example, cooperation can be preset within a TRP and / or across TRPs by the ANC 302. According to aspects, no inter-TRP interface can be needed / present.
[0051] According to aspects, a dynamic configuration of split logical functions can be present within the architecture of the distributed RAN 300. The PDCP, RLC, and / or MAC protocols can be adaptably placed at the ANC or TRP.
[0052] Figure 4 An example physical architecture of a distributed RAN 400 is illustrated. A centralized core network unit (C-CU) 402 can host core network functions. The C-CU can be centrally deployed. The C-CU functionality can be offloaded (e.g., to advanced wireless services (AWS)) in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have a distributed deployment. The C-RU can be closer to the network edge. A distributed unit (DU) 406 can host one or more TRPs. The DU can be located at the network edge with radio frequency (RF) functionality.
[0053] Figure 5is a diagram 500 illustrating an example of a downlink (DL)-centered slot. The DL-centered slot can include a control portion 502. The control portion 502 can exist in the initial or beginning portion of the DL-centered slot. The control portion 502 can include various scheduling information and / or control information corresponding to various portions of the DL-centered slot. In some configurations, the control portion 502 can be a physical downlink control channel (PDCCH), as shown. The DL-centered slot can also include a DL data portion 504. The DL data portion 504 can sometimes be referred to as the payload of the DL-centered slot. The DL data portion 504 can include communication resources for communicating DL data from a scheduling entity (e.g., a user equipment (UE) or a base station (BS)) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 can be a physical downlink shared channel (PDSCH). Figure 5
[0054] The DL-centered slot can also include a common uplink (UL) portion 506. The common UL portion 506 can sometimes be referred to as an UL burst, a common UL burst, and / or various other suitable terminology. The common UL portion 506 can include feedback information corresponding to various other portions of the DL-centered slot. For example, the common UL portion 506 can include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information can include an acknowledgement (ACK) signal, a negative acknowledgement (NACK) signal, a hybrid automatic repeat request (HARQ) indicator, and / or various other suitable types of information. The common UL portion 506 can include additional or alternative information, such as information related to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information.
[0055] As shown in Figure 5 The end of the DL data portion 504 can be separated in time from the beginning of the common UL portion 506. This separation in time can sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terminology. This separation provides time for the switch from DL communication (e.g., reception operations by a subordinate entity (e.g., a UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., a UE)). Those of ordinary skill in the art will understand that the above is merely one example of a DL-centered slot, and alternative structures having similar features can exist without necessarily deviating from aspects described herein.
[0056] Figure 6 is a diagram 600 showing an example of an uplink (UL)-centric slot. The UL-centric slot can include a control portion 602. The control portion 602 can exist in the initial or beginning portion of the UL-centric slot. Figure 6 The control portion 602 in the diagram 700 can be similar to the control portion 502 described above with reference to the diagram 500. The UL-centric slot can also include a UL data portion 604. The UL data portion 604 can sometimes be referred to as the payload of the UL-centric slot. The UL portion can refer to the communication resources utilized for communicating UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion 602 can be a physical downlink control channel (PDCCH). Figure 5 As shown, the end of the control portion 602 can be separated in time from the beginning of the UL data portion 604. This time separation can sometimes be referred to as a gap, guard period, guard interval, and / or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operations by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric slot can also include a common UL portion 606.
[0057] The common UL portion 606 in the diagram 700 can be similar to the common UL portion 506 described above with reference to the diagram 600. The common UL portion 606 can additionally or alternatively include information related to channel quality indicators (CQI), sounding reference signals (SRS), and various other suitable types of information. Those of ordinary skill in the art will understand that the above is merely one example of an UL-centric slot, and alternative structures having similar features can exist without necessarily deviating from the aspects described herein. Figure 6 Figure 6 In certain circumstances, two or more subordinate entities (e.g., UEs) can communicate using sidelink signals. Real-world applications of such sidelink communications can include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and / or various other suitable applications. Generally, a sidelink signal can refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity can be utilized for scheduling and / or control purposes. In some examples, the sidelink signals can be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum). Figure 5
[0058]
[0059] Figure 7 FIG. 7 is a diagram 700 illustrating a scenario in which a UE needs to measure a neighbor cell for potential handover or cell reselection. In this example, a UE 704 is connected to a base station 702 on a cell 712. The UE 704 is also within the coverage of a neighbor cell 718 of a base station 708.
[0060] Implementing a truncated physical broadcast channel (PBCH) or a truncated synchronization signal block (SSB) in a 5G New Radio (NR) system with a bandwidth less than 5 MHz can introduce certain challenges. For example, the base station 708 of the neighbor cell 718 can be transmitting a truncated SSB that the UE 704 needs to measure and decode.
[0061] Traditionally, an SSB has a fixed size of 20 physical resource blocks (PRBs) in frequency and 4 orthogonal frequency-division multiplexing (OFDM) symbols in time. However, with the introduction of a truncated PBCH, the SSB can have fewer PRBs in the PBCH portion. This truncation presents several challenges for the UE 704 when measuring the neighbor cell 718: 1. The UE 704 can not know whether the SSB from the base station 708 is truncated or full size. 2. The UE 704 can need to adjust its behavior to measure and decode the truncated SSB. 3. The serving base station 702 can need a mechanism to inform the UE 704 of the presence of a truncated SSB in the neighbor cell.
[0062] FIG. 8(A) is a diagram illustrating the structure of a full synchronization signal block (SSB) 800 in a 5G New Radio (NR) system. In 5G NR, the SSB 800 occupies 20 physical resource blocks (PRBs) in the frequency domain and 4 orthogonal frequency-division multiplexing (OFDM) symbols in the time domain. This configuration is considered a full size SSB, traditionally used for bandwidths of 5 MHz and above.
[0063] The SSB includes several key components, each with a specific purpose in the synchronization and initial access procedure. A primary synchronization signal (PSS) 802 is located in the first OFDM symbol (symbol 0) of the SSB. The PSS 802 and its associated guard band 810 occupy approximately 12 PRBs in the center of the frequency range.
[0064] In the second OFDM symbol (symbol 1), there is a first instance of a physical broadcast channel (PBCH) 806. The PBCH 806 spans the entire 20 PRB bandwidth of the SSB, extending above and below the frequency range occupied by the PSS 802.
[0065] The third OFDM symbol (symbol 2) contains a Secondary Synchronization Signal (SSS) 804. Like the PSS 802, the SSS 804 and its guard band 810 occupy approximately 12 PRBs in the center of the frequency range.
[0066] The fourth and final OFDM symbol (symbol 3) of the SSB contains a second instance of the PBCH 808. Like the first instance, this PBCH 808 also spans the full 20 PRB bandwidth of the SSB.
[0067] The PBCH portion (806, 808, 812, 814) of the SSB extends beyond the bandwidth occupied by the PSS 802 and SSS 804. The full utilization of the 20 PRB bandwidth by the PBCH is a feature of the complete SSB.
[0068] Figure 8(B) is a diagram 800 illustrating a truncated SSB 850. In cases where the network bandwidth is limited, particularly in deployments where the bandwidth is less than 5 MHz, the entire SSB data cannot be transmitted over the network. In these cases, the SSB data is truncated, resulting in a truncated SSB 850.
[0069] In the truncated SSB 850, the PSS 852 is similar to the PSS 802 shown in Figure 8(A) and occupies approximately 12 physical resource blocks (PRBs) in the center of the frequency range, including its associated guard band. The SSS 854 is located in the third OFDM symbol (symbol 2) and also occupies approximately 12 PRBs in the center of the frequency range, similar to the SSS 804 in Figure 8(A).
[0070] However, the PBCH portion of the truncated SSB 850 is significantly modified compared to the complete SSB 800. The PBCH occupying the frequency bands above and below the frequency range covered by the SSS 854 is removed. The two separate PBCH instances (856, 858) located in symbols 1 and 3, respectively, are truncated compared to the PBCH (806, 808) shown in Figure 8(A). The upper and lower portions of the frequency locations of the PBCH (856, 858) that fall outside the frequency range covered by the SSS 854 are truncated, leaving only the middle portion.
[0071] Further, in this disclosure, the term “truncated SSB” can be used interchangeably with “truncated PBCH,” which occupies less than 20 PRBs in a truncated SSB. “Truncated PBCH” refers to a punctured PBCH. Thus, the term “truncated SSB” can be used interchangeably with “punctured SS / PBCH block,” where the punctured PBCH transmission bandwidth occupies 12 PRBs shown in FIG. 8(B) (856, 858). This reduction in PRB utilization is a feature of the truncated SSB 850 that distinguishes it from the full SSB 800.
[0072] The introduction of the truncated SSB 850 is to accommodate diverse network deployment needs, especially in bandwidth-constrained situations. By utilizing a reduced set of PRBs to transmit the SSB, the network can minimize the bandwidth occupied by the SSB without impacting the transmission of critical synchronization and broadcast information.
[0073] Traditionally, when the network configures the UE 704 through configuration signaling (possibly radio resource control (RRC) signaling), it specifies which SSB to measure without necessarily indicating the bandwidth of the SSB. Given that the SSB is traditionally fixed in size in terms of the number of PRBs and OFDM symbols, meaning uniform in bandwidth, the UE 704 typically performs a standard measurement procedure to read the information carried in the PBCH and PSS / SSS.
[0074] However, with the introduction of the bandwidth-reduced truncated SSB 850, which transmits fewer PRBs than the full SSB 800, the UE 704 is required to adjust its handling of the truncated SSB 850 accordingly. Specifically, based on the SSB type (full or truncated), the UE 704 needs to employ different approaches for measurement and decoding.
[0075] This adjustment presents several challenges for the UE 704 when measuring a neighboring cell, such as the cell 718 of the base station 708. First, the UE 704 can not know whether the SSB from the base station 708 is truncated or full. Second, the UE 704 needs to adjust its behavior to measure and decode the truncated SSB. Finally, the serving base station 702 needs a mechanism to inform the UE 704 of the existence of the truncated SSB in the neighboring cell.
[0076] To address these challenges, several proposals are made. When the UE 704 measures a neighboring cell with a truncated PBCH, its behavior should be different from that used for a full PBCH in an SSB. This can involve a longer evaluation period, increased latency, or following different requirements for the existing SSB and the truncated PBCH of the new SSB.
[0077] Further, when performing SSB Block Index (SBI) reading, the UE 704 should take into account the truncated PBCH in the truncated SSB. This can require the use of one or more truncated SSBs to accurately read the SBI. The UE 704 can also need to employ soft-combining techniques to decode the truncated PBCH using one or more truncated SSBs.
[0078] For radio resource management (RRM) measurements, the UE 704 can utilize the truncated PBCH of the truncated SSB to complete layer 1 and layer 3 measurements such as reference signal received power (RSRP), reference signal received quality (RSRQ), and signal to interference plus noise ratio (SINR).
[0079] To facilitate these adjustments, it is proposed that the network configure the UE 704 to indicate whether the PBCH in the SSB is truncated or not. This configuration can be provided through Measurement Object (MO) signaling, handover commands, or other RRC signaling mechanisms. The UE 704 would then be responsible for identifying whether the configured PBCH is full or truncated based on this information.
[0080] By implementing these proposals, the network and the UE can effectively handle the challenges posed by truncated SSBs in bandwidth-limited scenarios, thereby enabling efficient cell measurements and handovers in 5G NR systems with bandwidths less than 5 MHz.
[0081] More specifically, to address these challenges, the UE 704 can utilize several proposals to modify the behavior of the UE 704 when dealing with truncated physical broadcast channels (PBCH) in SSBs. These proposals aim to improve the accuracy and efficiency of the UE 704 in performing measurements in scenarios involving truncated SSBs.
[0082] In the first proposal, when a user equipment (UE) 704 measures a neighboring cell with a truncated physical broadcast channel (PBCH) (i.e., the PBCH occupies less than 20 physical resource blocks or PRBs), its behavior can differ from when measuring a cell with a full PBCH. This differentiation is necessary because the truncated PBCH contains less information, and different processing techniques can be required to accurately extract the required data.
[0083] The UE 704 can need to adjust its measurement procedures to accommodate the reduced bandwidth of the truncated PBCH. This adjustment can involve adjusting the measurement window, modifying the sampling rate, or employing different signal processing algorithms. The specific changes in behavior will depend on the exact nature of the truncation and the available information of the UE 704 about the truncated synchronization signal block (SSB) structure.
[0084] The second proposal focuses on the SSB Block Index (SBI) reading procedure when dealing with truncated PBCH. In this proposal, the UE 704 can perform SBI reading taking into account the reduced bandwidth of the truncated PBCH. The SBI can help the UE 704 locate and decode specific PBCH information, enabling it to acquire the necessary system information.
[0085] When reading the SBI from the truncated PBCH, the UE 704 can need to employ different decoding techniques or use multiple truncated SSBs to accurately extract the SBI information. This can involve using soft-combining techniques to aggregate information from multiple truncated PBCHs, thereby improving the reliability of the SBI reading procedure.
[0086] The third proposal involves handover scenarios for cells using truncated PBCH. In this proposal, the behavior of the UE 704 when performing handover to a cell using truncated PBCH should be different from when dealing with full PBCH. This differentiation is necessary because the handover procedure heavily relies on the information contained in the PBCH, which the truncated PBCH can not be able to provide all the information typically available in full PBCH.
[0087] The UE 704 can need to adjust its handover procedures to accommodate the limitations of the information available in the truncated PBCH. This can involve requesting additional information from the serving cell, using different criteria for handover decisions, or employing alternative methods to verify the handover suitability of the target cell.
[0088] The fourth proposal involves Radio Resource Management (RRM) measurements when dealing with truncated PBCH. In this proposal, the UE 704 can selectively measure or not measure the truncated PBCH during RRM measurements. This flexibility allows the UE 704 to adjust its measurement strategy depending on the specific situation and the quality of the received signal.
[0089] In cases where the truncated PBCH provides sufficient information for RRM measurements, the UE 704 can choose to include it in the measurements. However, in cases where the truncated PBCH does not significantly contribute to the accuracy of the RRM measurements or measuring it can introduce unnecessary complexity, the UE 704 can choose to exclude it from the measurements.
[0090] To facilitate these adaptive behaviors, it is proposed that the network should configure the UE 704 to indicate whether the PBCH in the SSB is truncated or not. This configuration can be provided through various signaling mechanisms, such as Measurement Object (MO) signaling, handover commands, or other Radio Resource Control (RRC) signaling.
[0091] MO signaling typically informs the UE 704 which neighboring cells it should measure. By including information about the PBCH truncation status in these cells, the network can cause the UE 704 to adjust its measurement behavior accordingly. Likewise, including this information in a handover command can help the UE 704 to prepare for an appropriate handover procedure using either truncated or complete PBCH according to the target cell.
[0092] The above proposals address scenarios where the UE 704 is already connected to a serving cell and performs measurements on neighboring cells. The initial access scenario, i.e. the case where the UE 704 first joins or attaches to a cell, is handled differently. During initial access, the location of the truncated SSB in the frequency domain is indicated using a sync raster mechanism, enabling the UE 704 to adjust its behavior accordingly.
[0093] A fifth proposal involves the network configuring the UE 704’s capabilities to provide a list of cells or carriers (e.g. N cells or carriers) using truncated PBCH. This configuration mechanism allows the network to provide the UE 704 with information about the SSB structure in neighboring cells. By informing the UE 704 which cells employ truncated PBCH, the network enables the UE 704 to adjust its measurement and decoding strategy accordingly.
[0094] The network can implement this configuration through various signaling mechanisms, such as measurement object (MO) signaling, handover commands, or other radio resource control (RRC) signaling. For example, when configuring a measurement object for the UE 704, the network can include an indicator or a specific field indicating whether the PBCH in the SSB of a particular cell is truncated or complete. This information is particularly useful when the network instructs the UE 704 to measure neighboring cells, as it allows the UE 704 to anticipate the SSB structure it will encounter.
[0095] Furthermore, in a sixth proposal, the network can extend its configuration capabilities to influence the UE’s behavior during radio resource management (RRM) measurements. Specifically, the network can instruct the UE 704 not to decode the PBCH when performing RRM measurements on certain cells in the list of truncated PBCH cells. Instead, the UE 704 will be instructed to focus solely on decoding the primary synchronization signal (PSS) and secondary synchronization signal (SSS).
[0096] This selective decoding approach can be beneficial when dealing with legacy UEs that can not be able to efficiently handle truncated PBCH. By instructing these legacy devices to focus on the PSS and SSS, which remain largely unchanged in truncated SSB structures, the network can still obtain valuable measurement data while avoiding potential complexities arising from truncated PBCH.
[0097] The seventh proposal relates to the cell reselection scenario. When a UE 704 decides to reselect to a target cell, it is suggested that the UE 704 should read the truncated PBCH of the target cell. The UE 704 acquires the necessary system information from the truncated PBCH before completing the cell reselection procedure.
[0098] To this end, the network can need to provide the UE 704 with additional guidance or parameters on how to interpret and process the truncated PBCH during cell reselection. This can involve specifying the location of the key information in the truncated PBCH, or providing instructions on how to combine information from multiple truncated SSBs if necessary.
[0099] In various embodiments, the UE 704 can exhibit different behaviors when processing the truncated physical broadcast channel (PBCH) within the synchronization signal block (SSB). These behaviors accommodate the reduced information content in the truncated PBCH while maintaining measurement accuracy and efficiency.
[0100] One aspect of the UE behavior relates to the evaluation period and latency of measuring the truncated SSB. Typically, the UE 704 needs to meet certain performance criteria by measuring a predetermined number of SSBs (e.g., X SSBs) within a normal evaluation period. However, when processing the truncated SSB, the UE 704 can need to extend this evaluation period to maintain the same level of accuracy. For example, the UE 704 can be instructed to measure X + 2 or X + 3 SSBs, effectively increasing the number of samples to compensate for the reduced information in each truncated SSB.
[0101] This extended evaluation period naturally leads to an increase in latency in the measurement process. In this context, latency can be understood as the delay required to complete cell detection, or more precisely, the measurement delay. The relationship between the evaluation period, latency, and measurement precision can be conceptualized as a triangle, where there is a trade-off between these three factors. For example, if the user equipment (UE) 704 maintains a normal evaluation period when measuring the truncated synchronization signal block (SSB), it can complete the process more quickly, but can do so at the expense of reduced precision. Conversely, choosing a longer evaluation period can improve precision, but at the expense of increased latency.
[0102] Another aspect of the UE’s behavior relates to its ability to read the SSB block index (SBI) from the truncated physical broadcast channel (PBCH). The truncation process inevitably leads to the loss of some information, as certain parts of the PBCH are not transmitted. Referring to FIG. 8(A) and FIG. 8(B), the upper and lower portions of the PBCH 812, 814 and PBCH 856, 858 are not transmitted in the truncated SSB 850. Therefore, the UE 704 must employ more advanced decoding techniques to successfully extract the SBI from this reduced set of information.
[0103] To address this challenge, the UE 704 can utilize one or more truncated SSBs to accurately read the SBI. This approach allows the UE 704 to aggregate information from multiple truncated PBCH instances, possibly recovering missing data through redundancy and error correction mechanisms. The UE 704 can also employ sophisticated decoding algorithms that enable extraction of necessary information from the truncated PBCH even in reduced datasets.
[0104] Under ideal conditions with minimal noise and excellent channel quality, the UE 704 should, in theory, be able to decode the truncated PBCH and extract the SBI from a single instance. However, real-world conditions often necessitate the use of multiple SSBs due to noise, interference, and suboptimal channel conditions. This requirement stems from the fundamental principles of channel coding and interleaving used during transmission.
[0105] Channel coding and interleaving techniques involve replicating and dispersing data bits to enhance robustness to errors. When truncation occurs, some of these replicated bits are lost, potentially degrading overall performance. However, if the signal-to-interference-plus-noise ratio (SINR) is sufficiently high, the UE 704 can still successfully decode the data and extract the SBI, albeit with potentially reduced efficiency compared to decoding a complete PBCH.
[0106] To further improve decoding performance, the UE 704 can employ soft-combining techniques when processing multiple truncated PBCHs. Soft-combining is a method that enhances the decoding process by intelligently fusing information from multiple signal instances. One example of a soft-combining technique is the use of Log-Likelihood Ratios (LLRs), which represent soft values that can be iteratively optimized during the channel decoding process.
[0107] The advantage of soft-combining lies in its ability to handle soft bits, which embody the decoder's probabilistic assessment of each transmitted bit, rather than relying solely on hard decisions. During the soft-combining process, these soft bits, typically represented as LLRs, are combined from various truncated PBCH receptions. This combination can be achieved through various algorithms, such as Maximum Ratio Combining (MRC), which assigns weights to contributions based on signal quality, or Equal Gain Combining (EGC), which treats all signals equally.
[0108] The aggregated LLRs provide a more robust estimate of the transmitted bits, effectively mitigating the effects of noise and interference. By employing soft-combining techniques, the UE 704 can more reliably decode the truncated PBCH signal, thereby enhancing its ability to extract critical system information under adverse conditions.
[0109] In addition to SBI extraction and decoding, the UE 704 can also adjust its behavior when performing various measurements on the truncated SSB. These measurements can include Layer 1 Reference Signal Received Power (L1-RSRP), Layer 3 Reference Signal Received Power (L3-RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference plus Noise Ratio (SINR). In performing these measurements, the UE 704 should utilize the truncated PBCH of the truncated SSB to accurately complete the measurements.
[0110] The truncated SSB contains less information than a full SSB. As such, the UE 704 adjusts its measurement algorithms and processing techniques to extract meaningful and accurate measurement results from the reduced dataset. This can involve modifying the measurement window, adjusting the sampling rate, or employing different signal processing algorithms optimized for truncated SSBs.
[0111] Furthermore, the UE 704 needs to be aware of the truncated nature of the SSB it is measuring. This awareness can be facilitated through network signaling mechanisms, such as Measurement Object (MO) signaling or handover commands. By receiving information about the SSB truncation status in neighboring cells, the UE 704 can pre-adjust its measurement and decoding strategies to optimize performance.
[0112] In scenarios where the network configures the UE 704 with a list of cells or carriers using truncated PBCH, the UE 704 is able to manage and apply different measurement and decoding strategies for each cell based on its SSB configuration. This flexibility allows the UE 704 to efficiently handle a mix of full and truncated SSBs in its vicinity.
[0113] Furthermore, the UE 704 should be prepared to handle scenarios where the network indicates that it does not decode PBCH when performing Radio Resource Management (RRM) measurements on certain cells with truncated PBCH. In such cases, the UE 704 will focus on decoding the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) and adjust its measurement procedures accordingly.
[0114] Finally, in cell reselection scenarios, the UE 704 must be able to read and interpret the truncated PBCH of the target cell. This involves extracting the necessary system information from the truncated PBCH to facilitate a smooth cell reselection process. The UE 704 can need to apply specialized decoding techniques or combine information from multiple truncated SSBs to obtain the complete set of system information required for cell reselection.
[0115] In various embodiments, the network (NW) facilitates the UE handling of truncated Physical Broadcast Channel (PBCH) within Synchronization Signal Blocks (SSBs). The NW implements multiple mechanisms to inform the UE 704 about the presence and characteristics of truncated PBCH in neighboring cells, enabling the UE 704 to adjust its measurement and decoding strategies accordingly.
[0116] One aspect of NW functionality involves configuring the UE 704 to indicate whether the PBCH within an SSB is truncated or not. This configuration can be achieved through various signaling mechanisms, including measurement object (MO) signaling, handover commands, or other radio resource control (RRC) signaling.
[0117] A measurement object (MO) is a parameter configured by the NW to guide the UE 704 on how to perform measurements. These parameters can include the type of signal to measure (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.), frequency, cell ID, measurement period, and other related information. The MO helps the UE 704 evaluate its current network environment and signal quality, thereby supporting network selection, cell reselection, and handover decisions. For example, in a 5G network, the UE 704 can measure signal quality on different frequency points according to the MO configured by the NW and select the best serving cell based on the measurement results.
[0118] Handover (HO) parameters or commands contain instructions that indicate when and how the UE 704 should switch from one serving cell to another. These parameters or commands can include the identification of the target cell, signal quality thresholds required for handover, handover preparation time, resource allocation information, and other related data. The role of HO parameters or commands is to optimize network performance and resource utilization while maintaining service continuity. With precise handover control, the network can reduce dropped call rates, increase data transmission rates, and reduce latency.
[0119] In MO or HO signaling, the network can include an indicator to specify whether the PBCH is truncated or not. This indicator allows the UE 704 to determine whether the SSB to be measured is 3 MHz or 5 MHz, thereby effectively identifying whether the configured SSB is a full SSB or a truncated SSB. For example, when configuring a measurement object for the UE 704, the network can include an indicator or a specific field to indicate whether the PBCH in the SSB of a particular cell is truncated or full-size.
[0120] As mentioned above, the network can configure the UE 704 with a list of one or more cells or carriers (e.g., N cells or carriers) that use truncated PBCH. This configuration mechanism allows the network to provide the UE 704 with comprehensive information about the SSB structure in neighboring cells. By informing the UE 704 which cells use truncated PBCH, the network enables the UE 704 to adjust its measurement and decoding strategies accordingly to accommodate each cell in its surroundings.
[0121] In addition, the network can extend its configuration capabilities to influence the behavior of the UE during Radio Resource Management (RRM) measurements. Specifically, the network can instruct the UE 704 to refrain from decoding the PBCH when performing RRM measurements on certain cells in the list of truncated PBCH cells. Instead, the UE 704 will be instructed to focus on decoding the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS). This selective decoding approach is beneficial when dealing with legacy UEs that can not be able to effectively process the truncated PBCH. By instructing these legacy devices to focus on the PSS and SSS, which remain largely unchanged in the truncated SSB structure, the network can still obtain valuable measurement data while avoiding the potential complications arising from the truncated PBCH.
[0122] While measurement objects and handover commands are common examples of such signaling, the network can employ other forms of RRC signaling to convey information about the truncated PBCH. This flexibility allows the network to adjust its signaling approach according to the specific requirements of different network deployments and UE capabilities.
[0123] In scenarios involving cell reselection, the network can provide the UE 704 with additional guidance or parameters on how to interpret and handle the truncated PBCH during the reselection process. This can involve specifying the location of key information in the truncated PBCH or, if necessary, providing instructions on how to combine information from multiple truncated SSBs.
[0124] The role of the network in managing the truncated PBCH is not limited to signaling. It can also coordinate the transmission of truncated SSBs across multiple cells to minimize interference and optimize overall network performance.
[0125] Figure 9(A) illustrates a flowchart 900 of the process of handling different SSB types at the UE side. This process involves the interaction between the network (NW) and the UE (e.g., UE 704) through a base station (e.g., base station 702).
[0126] At block 902, the UE 704 receives an SSB and a configuration signaling from the base station 702, which includes an indicator indicating the SSB type. This indicator can optimize the communication process as it defines the instructions used by the UE 704 in its measurement or handover tasks. In certain embodiments, the configuration signaling can include a measurement object or a handover parameter.
[0127] At block 904, the UE determines a type of the received SSB according to an indication of the configuration signaling. The SSB type is, for example, a full SSB or a truncated SSB. In certain embodiments, the configuration signaling can include a list of carrier frequencies of a New Radio (NR) carrier with truncated PBCH. In this case, if the UE 704 does not support a Global Synchronization Channel Number (GSCN) value related to a neighboring carrier frequency, it can choose to ignore the corresponding neighboring cell. In addition, the configuration signaling can indicate NR carriers to be measured by a cell supporting full SSB or truncated SSB transmission configuration in RRC IDLE or RRC INACTIVE state. The configuration signaling can also indicate NR carriers for reselection measurement reporting by a cell supporting full SSB or truncated SSB transmission configuration.
[0128] After determining the SSB type, at block 906, the UE 704 determines a behavior corresponding to a particular scenario according to the determined SSB type. The particular scenario can involve performing a measurement or a handover task.
[0129] For example, the particular scenario can include an active cell transmission scenario. In addition, the active cell transmission scenario can include a scenario of performing measurements on a serving cell. In this particular scenario, the behavior of the UE 704 can include various measurement instances, including but not limited to L1-RSRP, L3-RSRP, RSRQ, and SINR.
[0130] Alternatively, the particular scenario can also include a scenario of performing SBI reading, a scenario of performing RRM measurements, or a scenario of reselecting to a target cell, which correspond to different behaviors of the UE 704. For example, during RRM measurements, the UE 704 can skip decoding of PBCH on a particular cell in a list of cells with truncated PBCH.
[0131] The behavior of the UE 704 for the particular scenario depends on the type of the SSB. For example, if the SSB is of the truncated type, the UE 704 can perform an operation in a first evaluation period. In contrast, if the SSB is of the full type, the UE 704 can perform the same operation in a second evaluation period. Notably, the first evaluation period is longer than the second evaluation period. That is, more SSBs are included in the first evaluation period than in the second evaluation period. In addition, if the SSB is of the truncated type, the UE 704 can use multiple truncated SSBs to perform the operation corresponding to the particular scenario.
[0132] In certain embodiments, the UE 704 can use a soft-combining decoder to decode the truncated SSB. One example of the soft-combining technique can be LLR.
[0133] FIG. 9(B) illustrates a flowchart 950 of handling different SSB types at the network side. At block 952, the network determines the type of SSB according to the bandwidth. That is, if the bandwidth is sufficient, a full SSB can be used. On the other hand, if the bandwidth is limited, a truncated SSB will be used.
[0134] Then, at block 954, the network configures an indicator in the configuration signaling indicating the type of SSB. The type of SSB can include a truncated SSB or a full SSB. The truncated SSB can include a truncated PBCH occupying less than 20 PRBs. The network can also configure a list of cells whose PBCH is truncated.
[0135] In certain embodiments, the configuration signaling can include at least one of measurement object signaling, handover command, or RRC signaling. The configuration signaling can also include a list of carrier frequencies of new radio (NR) carriers with truncated PBCH.
[0136] Finally, at block 956, the NW transmits the SSB and the configuration signaling including the indicator indicating the type of SSB to the UE 704.
[0137] Further, the NW can configure the UE 704 to not decode the PBCH when performing radio resource management (RRM) measurements on cells with truncated PBCH, and configure the UE 704 to only decode the PSS and SSS of cells with truncated PBCH during the RRM measurements.
[0138] The foregoing description is intended to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the claims is not meant to limit the scope of that element but rather means that the claims can cover elements that are the same as that element or similar to that element. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of one or more of A, B, or C, and can include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination can contain one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," and the like can not be a substitute for the word "means." As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase "means for."
Claims
1. A wireless communication method for a user equipment, comprising: Receive a synchronization signal block from a base station and a configuration signaling including an indicator of a type of the synchronization signal block; The type of the synchronization signal block is determined based on the configuration signaling; and Based on the type of the synchronization signal block, a behavior corresponding to a specific scenario is determined.
2. The method of claim 1, wherein the specific scenario includes an active cell transmission scenario.
3. The method of claim 2, wherein the active cell transmission scenario includes a scenario in which a measurement is performed on a serving cell.
4. The method of claim 3, wherein the measurement includes the measurement of L1 reference signal received power, the measurement of L3 reference signal received power, the measurement of reference signal received quality, or the measurement of signal interference plus noise ratio.
5. The method of claim 1, wherein the specific scenario includes a scenario in which a synchronization signal block index read is performed.
6. The method of claim 1, wherein the specific scenario includes a scenario during handover to a cell.
7. The method of claim 1, wherein the specific scenario includes a scenario in which wireless resource management measurements are performed.
8. The method of claim 1, wherein the specific scenario includes a scenario of reselecting to a target cell.
9. The method of claim 1, wherein the type of the synchronization signal block includes a complete synchronization signal block and a truncated synchronization signal block.
10. The method of claim 9, wherein the configuration signaling includes a list of carrier frequencies having a new radio carrier that truncates the physical broadcast channel.
11. The method of claim 9, wherein the action comprises: When the type of the synchronization signal block is the truncated synchronization signal block, an operation corresponding to the specific scenario is performed within a first evaluation cycle; When the type of the synchronization signal block is the complete synchronization signal block, the same operation is performed within a second evaluation cycle; and The first evaluation period is longer than the second evaluation period.
12. The method of claim 11, wherein more synchronization signal blocks are included in the first evaluation period compared to the second evaluation period.
13. The method of claim 9, wherein the action comprises: When the type of the synchronization signal block is the truncated synchronization signal block, multiple truncated synchronization signal blocks are used to perform operations corresponding to the specific scenario.
14. The method of claim 9, wherein the user equipment uses a soft combiner decoder to decode the truncated synchronization signal block.
15. The method of claim 14, wherein the soft merging includes a log-likelihood ratio.
16. The method of claim 1, wherein during a radio resource management measurement, the user equipment skips decoding the physical broadcast channel on a specific cell in a list of cells where the physical broadcast channel is truncated.
17. The method of claim 1, wherein the configuration signaling includes a measurement object or a switching parameter.
18. A wireless communication method for a network, comprising: A type of a synchronization signal block is determined based on a bandwidth. A configuration signaling specifies an indicator that indicates the type of the synchronization signal block; and The synchronization signal block and the configuration signaling, including the indicator indicating the type of the synchronization signal block, are transmitted to a user equipment.
19. The method of claim 18, wherein the configuration signaling includes a list of carrier frequencies having a new radio carrier with a truncated physical broadcast channel.
20. The method of claim 18, wherein the configuration signaling includes at least one of measurement object signaling, handover command, or radio resource control signaling.
21. The method of claim 18, wherein the type of the synchronization signal block includes a truncated synchronization signal block or a complete synchronization signal block.
22. The method of claim 21, wherein the network configuration includes a list of cells in which physical broadcast channels are truncated.
23. The method of claim 21, wherein the truncated synchronization signal block includes a truncated physical broadcast channel occupying fewer than 20 physical resource blocks.
24. The method of claim 18, further comprising: The user equipment is configured not to decode the physical broadcast channel when performing the radio resource management measurement on a cell with a truncated physical broadcast channel.
25. The method of claim 24, further comprising: The user equipment is configured to decode only the primary synchronization signal and secondary synchronization signal of the cell having the truncated physical broadcast channel during the radio resource management measurement.
26. A device for wireless communication, the device being a user equipment, comprising: A memory; as well as At least one processor, coupled to the memory and configured as follows: Receive a synchronization signal block from a base station and a configuration signaling including an indicator of a type of the synchronization signal block; The type of the synchronization signal block is determined based on the configuration signaling; and Based on the type of the synchronization signal block, a behavior corresponding to a specific scenario is determined.