Systems and methods for synchronization signal block enhancement
The introduction of a new SSB pattern with interleaved bursts and multiple periodicities addresses the limitations of current SSB designs in satellite communications, enhancing coverage and efficiency for networks with a large number of beams and uneven load distributions.
Patent Information
- Application Number
- PCT/CN2023/128581
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-10-31
- Publication Date
- 2025-05-08
AI Technical Summary
Current synchronization signal block (SSB) designs are inadequate for supporting a large number of beams in satellite communication networks, particularly in scenarios where the beam number exceeds 64, and uneven load distribution across beams leads to inefficient power utilization.
The proposed solution involves a new SSB pattern with interleaved SSB bursts, allowing for more than 64 beams to be supported, and a method for indicating multiple SSB periodicities to optimize signal transmission based on varying load conditions.
This approach enhances SSB coverage and efficiency in satellite communication networks by supporting a larger number of beams and adapting to uneven load distributions, thereby improving overall network performance.
Smart Images

Figure CN2023128581_08052025_PF_FP_ABST
Abstract
Description
SYSTEMS AND METHODS FOR SYNCHRONIZATION SIGNAL BLOCK ENHANCEMENTTECHNICAL FIELD
[0001] The disclosure relates generally to wireless communications, including but not limited to systems and methods for synchronization signal block (SSB) enhancement.BACKGROUND
[0002] The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) . The 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) . In order to facilitate the enablement of different data services and requirements, the elements of the 5GC, also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need. Communication via satellite is one of the typical scenarios of the non-terrestrial networks in 3GPP standardization. In addition, satellites will play an increasingly key part in providing coverage and resilience in 6G.SUMMARY
[0003] The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
[0004] At least one aspect is directed to a system, method, apparatus, or a computer-readable medium of the following. A wireless communication device (e.g., a user equipment (UE) ) may receive a signaling (e.g., a system information block (SIB) signaling or a radio resource control (RRC) signaling) . The wireless communication device may determine, according to the signaling, at least one of: a periodicity of a synchronization signal block (SSB) pattern; a burst offset of the SSB pattern; or a burst number (e.g., SSB burst #) of the SSB pattern. In some embodiments, the SSB pattern may include a plurality of interleaved SSB bursts. At least one of the plurality of interleaved SSB bursts may include different information from another. The signaling may include at least one of: a system information block (SIB) signaling or a radio resource control (RRC) signaling.
[0005] In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-burstNumber) of the SSB pattern via the signaling. The wireless communication device may determine a number of SSB bursts in one of the periodicity according to the configuration information. In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-PositionsInBurst) of a SSB burst (e.g., the last SSB burst) via the signaling. The wireless communication device may determine a number of SSBs (e.g., the actual transmitted SSBs) in the SSB burst according to the configuration information. In some embodiments, the wireless communication device may receive configuration information (e.g., a list of ssb-PositionsInBurst) of the SSB pattern via the signaling. The wireless communication device may determine a number of SSBs in each SSB burst of the SSB pattern according to the configuration information.
[0006] In some embodiments, the SSB pattern may include a plurality of SSB groups. Each of the SSB groups may have a different periodicity from that of another. The wireless communication device may receive configuration information (e.g., one or more SSB indexes) of the plurality of SSB groups via the signaling. The wireless communication device may determine a boundary of the plurality of SSB groups according to the configuration information. The configuration information may include at least one SSB index.
[0007] In some embodiments, the wireless communication device may receive configuration information (e.g., a bitmap) of the plurality of SSB groups via the signaling. The wireless communication device may determine a number of SSB groups according to the configuration information. The configuration information may include a bitmap. In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-periodicityServingCell or a scaling factor) of the plurality of SSB groups via the signaling. The wireless communication device may determine a periodicity of each of the SSB groups according to the configuration information. The configuration information may include at least one scaling factor for the periodicity.
[0008] In some embodiments, a wireless communication node (e.g., a base station (BS) ) may send a signaling (e.g., a system information block (SIB) signaling or a radio resource control (RRC) signaling) to a wireless communication device (e.g., a user equipment (UE) ) . The wireless communication device may determine, according to the signaling, at least one of: a periodicity of a synchronization signal block (SSB) pattern; a burst offset of the SSB pattern; or a burst number of the SSB pattern.BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0010] FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure;
[0011] FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure;
[0012] FIG. 3 illustrates an example beam layout for a 5G / communication system, in accordance with some embodiments of the present disclosure;
[0013] FIG. 4 illustrates an example implementation structure for synchronization signal block (SSB) enhancement, in accordance with some embodiments of the present disclosure;
[0014] FIG. 5 illustrates an example synchronization signal block (SSB) pattern for SSB enhancement, in accordance with some embodiments of the present disclosure;
[0015] FIG. 6 illustrates an example synchronization signal block (SSB) pattern for SSB enhancement, in accordance with some embodiments of the present disclosure; and
[0016] FIG. 7 illustrates a flow diagram of an example method for synchronization signal block (SSB) enhancement, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION
[0017] 1. Mobile Communication Technology and Environment
[0018] FIG. 1 illustrates an example wireless communication network, and / or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100. ” Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In FIG. 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
[0019] For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118 / 124 may be further divided into sub-frames 120 / 127 which may include data symbols 122 / 128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communications, in accordance with various embodiments of the present solution.
[0020] FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
[0021] System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) . The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
[0022] As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
[0023] In accordance with some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
[0024] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212 / 232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
[0025] In accordance with various embodiments, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some embodiments, the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
[0026] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
[0027] The network communication module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and / or arranged to perform the specified operation or function.
[0028] The Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols. The OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
[0029] Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
[0030] 2. Systems and Methods for Synchronization Signal Block (SSB) Enhancement
[0031] To enhance the utilization of new radio (NR) access technologies, establishing 5G connectivity via satellites and / or airborne vehicles is a useful application. New radio –non-terrestrial network (NR-NTN) and IoT-NTN can be supported with a synchronization signal block (SSB) . To be more specific, the supported SSB number can be {4, 8, 64} for example.
[0032] Two options for beam layout can be supported. As shown in FIG. 3, a satellite cell may include multiple beams, and each beam can be associated with a dedicated frequency band (e.g., BWP#x) to facilitate a frequency reuse scheme. SSBs can be transmitted in the initial BWP#0, which can differ from the BWP#x used by data transmission. In option 1, the SSBs (in BWP#0) can be transmitted in a narrow beam, which may have the same beam footprint as the BWP#x beams. The SSBs can be transmitted in a time division multiplexing (TDM) manner, where the beam for BWP#0 sweeps across footprints of all beams. In option 2, the beam layout can be hierarchical. The SSBs in initial BWP#0 can be transmitted in an umbrella beam that covers the union of multiple beams (as shown in FIG. 3, where all beams are included in the union) . Option 1 allows SSBs (and other common channels) to be simultaneously transmitted with the same beam configuration parameters as data transmission on dedicated BWPs, e.g., antenna gain and frequency offset compensation. Therefore, the option 1 may have a better coverage of SSBs compared to the option 2.
[0033] In NTN scenarios, the beam number of a satellite may probably exceed 64 due to following reasons: (a) The beam area is limited by a physical random access channel (PRACH) design. For example, a low earth orbit (LEO) satellite with a 600 km orbit height can cover a circular area with a radius of ~1000 km. To reuse the PRACH design for the terrestrial networks, a beam can support a maximum radius of 100 km. As a result, the beam number can be about 100. The larger the satellite's orbital height, the more beams are required for its coverage. (b) The beam area may be limited by link budget and transmission power of the satellite. Unlike terrestrial BSs, the transmitted power of a satellite BS can be limited by solar cells. Furthermore, to combat the high path loss in satellite communications, directional antenna with very narrow beam may be employed to meet the link budget.
[0034] To support a satellite cell with more than 64 beams, the current SSB design is not enough. To address this issue, the present disclosure proposes a new SSB pattern. In addition, uneven load is quite common in a very large satellite cell and the same SSB periodicity for all beams may not be efficient considering the power limitation of the satellite payload. Therefore, the present disclosure also introduces a method for SSB transmission with multiple periodicities. FIG. 4 illustrates an example implementation structure for synchronization signal block (SSB) enhancement, in accordance with some embodiments of the present disclosure.
[0035] An SSB for a terrestrial network (TN) can be directly reused, which is introduced below.
[0036] 1. Cases: Different cases may have different subcarrier spacings (SCSs) , and these SCSs can be applicable for various frequency bands. The number of supported SSB indexes can be {4, 8, 64} based on the SSB case. Under these conditions, the UE may assume that SSBs transmitted with the same block index on the same center frequency location are quasi co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and, when applicable, spatial Rx parameters. When the same synchronization signal block (SSB) index is used, it is considered quasi co-located (QCLed) . When using the same beam layout, it is possible that 64 SSB indexes may not be sufficient. Additional methods are required to indicate the time-multiplexing of the same SSB index (e.g., to transmit the same SSB index using different beams at different times) .
[0037] 2. Periodicity configuration: The NR SSB can be transmitted periodically. A UE can be provided, per serving cell and based on ssb-periodicityServingCell, a half frame periodicity for receiving SSBs from the serving cell. If the UE is not configured with a specific half-frame periodicity for receiving SSBs, the UE may assume a default periodicity of half a frame, which can be equivalent to 5 milliseconds (ms) . The UE may assume that this periodicity is the same for all SSBs within the serving cell. For initial cell selection, the UE may assume that half-frames including SSBs occur with a periodicity of 2 frames, equivalent to 20 ms. Due to the extensive coverage area of the satellite, it is highly probable that some regions may have a dense concentration of UE, while others may have a sparse concentration of UE. In such cases, it may be beneficial to assign a smaller SSB periodicity to the dense UE areas, which can provide more associated system information (SI) and RACH occasion (RO) , effectively meeting the requirements of high-load areas. However, the issue here is that not all SSBs have the same periodicity. The present disclosure provides a method for indicating multiple SSB periodicities.
[0038] 3. Signaling: The SSB configurations can be provided in both a cell specific signaling and a UE specific signaling. For example, ssb-periodicityServingCell can be provided in system information block (SIB) signaling (e.g., SIB1 (cell specific signaling) ) and / or a radio resource control (RRC) signaling (e.g., RRCSetup / RRCReconfiguration (UE specific signaling) ) .
[0039] Implementation Example 1: SSB enhancement for the same beam layout for SSB (BWP#0) and data (BWP#x)
[0040] Option 1 in FIG. 3 allows SSBs (and other common channels) to be simultaneously transmitted with the same beam configuration parameters as data transmission on dedicated BWPs. Compared with option 2 in FIG. 3, the antenna gain is larger due to narrower beam. In addition, beam hopping can be naturally utilized in SSB transmission to deal with the power limitation of a satellite payload. Therefore, a better coverage of SSBs can be expected. However, the data beam number may exceed 64, and the current SSB indexes are not enough to distinguish all the data beams. To solve this problem, a method is proposed below.
[0041] (1) SSB pattern
[0042] An SSB burst may occupy 5 ms, in which up to 64 SSBs can be accommodated. If the beam number in a satellite cell exceeds 64, an SSB pattern with interleaved SSB bursts can be used to support more than 64 beams. An example is illustrated in FIG. 5. If the satellite cell has 256 beams, 4 (=256 / 64) SSB bursts can be transmitted in 20 ms. Each SSB burst may use 5 ms and may include 64 SSBs with indexes of #0~#63. The periodicity of each SSB burst can be 20 ms. The 4 SSB bursts can be transmitted with an interleaved pattern. In some embodiments, at least one of the interleaved SSB bursts may include different information from another. The SSB burst offsets (named SsbBurstOffset) in the 20 ms periodicity can be {0, 5, 10, 15} ms, respectively. With this SSB pattern with interleaved SSB bursts, more than 64 beams can be supported in a cell. FIG. 5 illustrates an example synchronization signal block (SSB) pattern with interleaved SSB bursts, in accordance with some embodiments of the present disclosure.
[0043] (2) Quasi co location (QCL) rule
[0044] Since the same SSB indexes can be used in different SSB bursts, the UE may not assume that SSB transmitted with the same block index on the same center frequency location are quasi co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and, when applicable, spatial Rx parameters. Instead, the UE may receive a signaling. The UE may determine a periodicity of a synchronization signal block (SSB) pattern and a burst offset of the SSB pattern according to the signaling. The UE may determine a burst number (e.g., SSB burst #) of the SSB pattern according to the periodicity and the burst offset. For example, the UE may obtain the SSB periodicity and may determine the ssbBurstOffset of the received SSB burst. The SSB with the same block index and the same ssbBurstOffset on the same center frequency location can be assumed as quasi co-located. In such a way, the more than 64 beams can be distinguished using the combination {SSB index, ssbBurstOffset} .
[0045] (3) Signaling
[0046] For initial cell selection, a UE may assume that the SSB bursts occur with a predefined periodicity. For example, the predefined periodicity can be 20 ms. For a satellite cell, the beam number can be very large (e.g., hundreds or even thousands) . Therefore, the predefined periodicity for NTN may be set as a larger value than 20 ms, which can be implicitly known from the serving network type (e.g., TN or NTN) .
[0047] For each serving cell, a UE can be provided a periodicity of 5 milliseconds (ms) for the SSB burst (by ssb-periodicityServingCell) . To support the SSB pattern with interleaved SSB bursts, the number of SSB bursts in one periodicity can be determined by the UE to facilitate SSB measurement. There can be following methods.
[0048] ①The number of SSB bursts in one periodicity can be provided to the UEs by a parameter (e.g., named ssb-burstNumber) . The parameter can be carried by a cell specific signaling (e.g., SIB19) or a UE specific signaling (e.g., RRCSetup or RRCReconfiguration) . Taking the example in FIG. 5, the SSB burst #m may have an offset of ssbBurstOffset = (m -1) *5 ms. The maximum value of ssb-burstNumber can be determined by ssb-periodicityServingCell / 5.
[0049] ②The step of ssbBurstOffset can be provided to the UEs by a parameter (e.g., named ssb-burstOffsetStep (in the same unit of ssb-periodicityServingCell) ) . The number of SSB bursts in one periodicity can be determined as ssb-periodicityServingCell / ssb-burstOffsetStep. Taking the example in FIG. 5, the number of SSB bursts may equal to 4 (=20 / 5) .
[0050] ③The number of SSB bursts can be indicated using a bitmap. The bitmap size can be determined by ssb-periodicityServingCell / ssb-burstOffsetStep, in which the ssb-burstOffsetStep can be a predefined value if not configured. For example, if ssb-periodicityServingCell = 20 ms and ssb-burstOffsetStep = 5 ms, a bitmap of 4 (=20 / 5) bits can be used. Each bit can be associated with an SSB burst in a sequential order. Taking the example in FIG. 5, the bitmap can be “1111” , in which a bit set as “1” means a corresponding SSB burst is transmitted. If an SSB burst is not transmitted, the corresponding bit can be set as “0” . The number of SSB bursts is the number of “1” sin the bitmap. The transmitted SSB bursts location can be also provided by the bitmap.
[0051] In a practical satellite cell, the beam number may not always be an integral multiple of 64. For example, if a satellite cell has 169 beams (e.g., a 8-tier beam layout) and each SSB burst may have 64 SSBs, the number of SSB bursts can be 3 (=ceiling (169 / 64) ) . In such case, the number of SSB bursts can be provided by the ssb-burstNumber. The actual transmitted SSBs can be provided by ssb-PositionsInBurst, which is carried in a SIB1 or a UE specific RRC signaling and is utilized for downlink rate matching. If more than one SSB bursts are transmitted, the actual transmitted SSBs in each SSB burst can be indicated. There can be following methods.
[0052] ① In some embodiments, the UE may receive configuration information (e.g., ssb-PositionsInBurst) of a SSB burst (e.g., the last SSB burst) via the signaling from a wireless communication node. The UE may determine a number of SSBs (e.g., the actual transmitted SSBs) in the SSB burst according to the configuration information. For example, the ssb-PositionsInBurst can be used to indicate the actual transmitted SSBs in the last SSB burst. The UE can assume that all the SSBs in the SSB bursts other than the last SSB burst are actually transmitted. The benefit is that the original signaling can be reused with reinterpretation, and no extra signaling cost is involved.
[0053] ②In some embodiments, the UE may receive configuration information (e.g., a list of ssb-PositionsInBurst) of the SSB pattern via the signaling from a wireless communication node. The UE may determine a number of SSBs in each SSB burst of the SSB pattern according to the configuration information. For example, a list of ssb-PositionsInBurst can be provided to the UE via a cell specific and / or a UE specific signaling. The number of ssb-PositionsInBurst in the list may equal to ssb-burstNumber. Each ssb-PositionsInBurst in the list can be sequentially associated with each SSB burst in the SSB bursts in one periodicity.
[0054] Implementation Example 2: Multiple SSB periodicity for uneven loaded beams
[0055] Since a satellite’s coverage is generally very large, multiple beams with beam hopping can be used to deal with the power limitation of a satellite payload. In the same satellite’s coverage, different load among beams can be common. In such scenarios, it is advantageous to employ a smaller SSB periodicity for the area with high load (or, higher UE density) , and a larger SSB periodicity for the area with low load (or, lower UE density) .
[0056] (1) Multiple periodicity
[0057] The same SSB periodicity can be used for all SSBs in the serving cell. Therefore, some enhancement can be adopted to better serve the scenario with uneven loaded beams. Without loss of generality, a satellite cell with 64 SSBs using 2 periodicity is illustrated in FIG. 6.
[0058] In some embodiments, the SSB pattern may include a plurality of SSB groups. Each of the SSB groups may have a different periodicity from that of another. In one scenario, where the high-load area is served by synchronization signal blocks (SSB) #0~#31 with a periodicity of 10 ms, and the low-load area is served by SSB #32~#63 with a periodicity of 20 ms, all SSBs can be divided into multiple groups. A periodicity can be indicated for each SSB group by a wireless communication node (e.g., a base station (BS) ) . FIG. 6 illustrates an example synchronization signal block (SSB) pattern with multiple periodicities, in accordance with some embodiments of the present disclosure.
[0059] (2) Signaling
[0060] A UE can be provided per serving cell by ssb-periodicityServingCell a periodicity of the 5ms SSB burst for the serving cell. To support the multiple SSB periodicity, the SSBs need to be divided into groups. There are following ways.
[0061] ① The UE may receive configuration information (e.g., one or more SSB indexes) of the plurality of SSB groups via the signaling from a wireless communication node. The UE may determine a boundary of the plurality of SSB groups according to the configuration information. The configuration information may include at least one SSB index. For example, one or more SSB indexes can be used to indicate the boundary of SSB groups. In the example in FIG. 6, an SSB index of 31 (the last SSB index of its group) or 32 (the first SSB index of its group) can be indicated, which means SSB #0~#31 is a group and SSB #32~#63 is another group. The number of SSB groups (named ssb-GroupNumber) may equal to the number of indicated SSB indexes (named ssb-IndexBoundaryNumber) plus one, e.g., ssb-GroupNumber = ssb-IndexBoundaryNumber + 1.
[0062] ② The UE may receive configuration information (e.g., a bitmap) of the plurality of SSB groups via the signaling from a wireless communication node. The UE may determine a number of SSB groups according to the configuration information. The configuration information may include a bitmap. For example, if two groups are used, a bitmap can be used to indicate the group of each SSB. In the example in FIG. 6, a bitmap with 64 bits can be used. In the bitmap, the #0~#31 bits are set as 0 and the #32~#63 bits are set as 1. In some embodiments, if multiple groups are used, the group indication for each SSB can be multiple bits.
[0063] ③ The UE may receive configuration information (e.g., multiple SSB lists) of the plurality of SSB groups via the signaling from a wireless communication node. The UE may determine an index of each SSB of the plurality of SSB groups according to the configuration information. The configuration information may include at least one SSB list. For example, multiple SSB lists can be used to indicate the SSB indexes in each group. In the example in FIG. 6, two lists can be used. The first one can be {0, 1, ..., 31} , and the second one can be {32, 33, ..., 63} .
[0064] In some embodiments, for each SSB group, different periodicity can be used. There can be following methods.
[0065] ① The UE may receive configuration information (e.g., ssb-periodicityServingCell or a scaling factor) of the plurality of SSB groups via the signaling. The UE may determine a periodicity of each of the SSB groups according to the configuration information. The configuration information may include at least one scaling factor for the periodicity. For example, a UE can be provided / sent / configured an ssb-periodicityServingCell and one or more scaling factor for the ssb-periodicityServingCell. In the example in FIG. 6, an ssb-periodicityServingCell of 10 ms and a scaling factor of 2 can be indicated. The ssb-periodicityServingCell of 10 ms can be applicable to the first SSB group including SSB #0~#31. The periodicity applicable to the second SSB group including SSB #32~#63 is 20 ms (= ssb-periodicityServingCell *scaling factor = 10 ms *2) . The number of SSB periodicity scaling factors (named ssb-PeriodicityScalingFactorNumber) can equal to ssb-GroupNumber or ssb-GroupNumber-1. If ssb-PeriodicityScalingFactorNumber = ssb-GroupNumber, each of the scaling factors can be used by the SSB groups in a sequential order. If ssb-PeriodicityScalingFactorNumber = ssb-GroupNumber-1, each of the scaling factors can be used by the SSB groups (without the first group) in a sequential order.
[0066] ② A UE can be provided multiple ssb-periodicityServingCell values. In the example in FIG. 6, two ssb-periodicityServingCell values of (10ms, 20ms) can be indicated. Each of the ssb-periodicityServingCell values can be used by the SSB groups in a sequential order.
[0067] It should be understood that one or more features from the above / following implementation examples are not exclusive to the specific implementation examples, but can be combined in any manner (e.g., in any priority and / or order, concurrently or otherwise) .
[0068] FIG. 7 illustrates a flow diagram of a method 700 for synchronization signal block (SSB) enhancement. The method 700 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGs. 1–6. In overview, the method 700 may be performed by a wireless communication device (e.g., a UE) , in some embodiments. Additional, fewer, or different operations may be performed in the method 700 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.
[0069] A wireless communication device (e.g., a user equipment (UE) ) may receive a signaling (e.g., a system information block (SIB) signaling or a radio resource control (RRC) signaling) . The wireless communication device may determine, according to (or using / from) the signaling, at least one of: a periodicity of a synchronization signal block (SSB) pattern; a burst offset of the SSB pattern; or a burst number (e.g., SSB burst #) of the SSB pattern. In some embodiments, the SSB pattern may include a plurality of interleaved SSB bursts. At least one of the plurality of interleaved SSB bursts may include different information from another. The signaling may include at least one of: a system information block (SIB) signaling or a radio resource control (RRC) signaling.
[0070] In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-burstNumber) of the SSB pattern via the signaling. The wireless communication device may determine a number of SSB bursts in one of the periodicity according to the configuration information. In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-PositionsInBurst) of a SSB burst (e.g., the last SSB burst) via the signaling. The wireless communication device may determine a number of SSBs (e.g., the actual transmitted SSBs) in the SSB burst according to the configuration information. In some embodiments, the wireless communication device may receive configuration information (e.g., a list of ssb-PositionsInBurst) of the SSB pattern via the signaling. The wireless communication device may determine a number of SSBs in each SSB burst of the SSB pattern according to the configuration information.
[0071] In some embodiments, the SSB pattern may include a plurality of SSB groups. Each of the SSB groups may have a different periodicity from that of another. The wireless communication device may receive configuration information (e.g., one or more SSB indexes) of the plurality of SSB groups via the signaling. The wireless communication device may determine a boundary of the plurality of SSB groups according to the configuration information. The configuration information may include at least one SSB index.
[0072] In some embodiments, the wireless communication device may receive configuration information (e.g., a bitmap) of the plurality of SSB groups via the signaling. The wireless communication device may determine a number of SSB groups according to the configuration information. The configuration information may include a bitmap. In some embodiments, the wireless communication device may receive configuration information (e.g., ssb-periodicityServingCell or a scaling factor) of the plurality of SSB groups via the signaling. The wireless communication device may determine a periodicity of each of the SSB groups according to the configuration information. The configuration information may include at least one scaling factor for the periodicity.
[0073] In some embodiments, a wireless communication node (e.g., a base station (BS) ) may send a signaling (e.g., a system information block (SIB) signaling or a radio resource control (RRC) signaling) to a wireless communication device (e.g., a user equipment (UE) ) . The wireless communication device may determine, according to the signaling, at least one of: a periodicity of a synchronization signal block (SSB) pattern; a burst offset of the SSB pattern; or a burst number of the SSB pattern.
[0074] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.
[0075] It is also understood that any reference to an element herein using a designation such as "first, " "second, " and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
[0076] Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0077] A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.
[0078] Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and / or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
[0079] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A 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 include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
[0080] In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
[0081] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
[0082] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
Claims
1.A method comprising:receiving, by a wireless communication device, a signaling;determining, by the wireless communication device according to the signaling, at least one of:a periodicity of a synchronization signal block (SSB) pattern;a burst offset of the SSB pattern; ora burst number of the SSB pattern.2.The method of claim 1, wherein the SSB pattern includes a plurality of interleaved SSB bursts.3.The method of claim 2, wherein at least one of the plurality of interleaved SSB bursts includes different information from another.4.The method of claim 1, wherein the signaling includes at least one of: a system information block (SIB) signaling or a radio resource control (RRC) signaling.5.The method of claim 1, comprising:receiving, by the wireless communication device, configuration information of the SSB pattern via the signaling; anddetermining, by the wireless communication device, a number of SSB bursts in one of the periodicity according to the configuration information.6.The method of claim 1, comprising:receiving, by the wireless communication device, configuration information of a SSB burst via the signaling; anddetermining, by the wireless communication device, a number of SSBs in the SSB burst according to the configuration information.7.The method of claim 1, comprising:receiving, by the wireless communication device, configuration information of the SSB pattern via the signaling; anddetermining, by the wireless communication device, a number of SSBs in each SSB burst of the SSB pattern according to the configuration information.8.The method of claim 1, wherein the SSB pattern includes a plurality of SSB groups, and each of the SSB groups has a different periodicity from that of another.9.The method of claim 8, comprising:receiving, by the wireless communication device, configuration information of the plurality of SSB groups via the signaling; anddetermining, by the wireless communication device, a boundary of the plurality of SSB groups according to the configuration information,wherein the configuration information includes at least one SSB index.10.The method of claim 8, comprising:receiving, by the wireless communication device, configuration information of the plurality of SSB groups via the signaling; anddetermining, by the wireless communication device, a number of SSB groups according to the configuration information,wherein the configuration information includes a bitmap.11.The method of claim 8, comprising:receiving, by the wireless communication device, configuration information of the plurality of SSB groups via the signaling; anddetermining, by the wireless communication device, a periodicity of each of the SSB groups according to the configuration information.12.The method of claim 11, wherein the configuration information includes at least one scaling factor for the periodicity.13.A method comprising:sending, by a wireless communication node to a wireless communication device, a signaling,wherein the wireless communication device determines, according to the signaling, at least one of:a periodicity of a synchronization signal block (SSB) pattern;a burst offset of the SSB pattern; ora burst number of the SSB pattern.14.A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-13.15.An apparatus comprising:at least one processor configured to implement the method of any one of claims 1-13.
Citation Information
Patent Citations
Synchronization signal block (SSB) transmission method, terminal equipment and network equipment
CN113973364A
Shared spectrum synchronization design
US20190037481A1
Irregular SSB beam pattern for network energy saving
WO2023130445A1