[go: up one dir, main page]

WO2025114999A1 - Appareil et procédé de communication de demandes de transmission de bloc de canal de diffusion physique/signal de synchronisation dans un système de communication sans fil - Google Patents

Appareil et procédé de communication de demandes de transmission de bloc de canal de diffusion physique/signal de synchronisation dans un système de communication sans fil Download PDF

Info

Publication number
WO2025114999A1
WO2025114999A1 PCT/IB2025/051331 IB2025051331W WO2025114999A1 WO 2025114999 A1 WO2025114999 A1 WO 2025114999A1 IB 2025051331 W IB2025051331 W IB 2025051331W WO 2025114999 A1 WO2025114999 A1 WO 2025114999A1
Authority
WO
WIPO (PCT)
Prior art keywords
serving cell
request
pbch block
processor
transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IB2025/051331
Other languages
English (en)
Inventor
Alexander Golitschek Edler Von Elbwart
Prateek Basu Mallick
Joachim Löhr
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Singapore Pte Ltd
Original Assignee
Lenovo Singapore Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Singapore Pte Ltd filed Critical Lenovo Singapore Pte Ltd
Publication of WO2025114999A1 publication Critical patent/WO2025114999A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others

Definitions

  • the present disclosure relates to wireless communications, and more specifically to configuring a synchronization signal (SS)Zphysical broadcast channel (PBCH) block transmission requests in a wireless communication system.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.
  • a UE may generate a request for at least one transmission of at least one SS/PBCH block based at least in part on a condition and transmit, to a first serving cell, control signaling that indicates the request for the at least one transmission of the at least one SS/PBCH block associated with a second serving cell.
  • Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
  • Figure 2 illustrates an example of a RACH procedure in accordance with aspects of the present disclosure.
  • Figure 3 illustrates an example of a time and frequency structure of a SS/PBCH block in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a procedure for master information block (MIB) and/or system information block (SIB) transmission flow in accordance with aspects of the present disclosure.
  • MIB master information block
  • SIB system information block
  • Figure 5 illustrates an example of a procedure for synchronization signal block (SSB)-based radio resource management (RRM) measurement timing configuration (SMTC) communications in accordance with aspects of the present disclosure.
  • SSB synchronization signal block
  • RRM radio resource management
  • SMTC measurement timing configuration
  • Figure 6 illustrates an example of a structure of a synchronization signal block (SSB) request medium access control (MAC) control element (CE) (MAC CE) in accordance with aspects of the present disclosure.
  • SSB synchronization signal block
  • MAC medium access control
  • CE control element
  • Figure 7 illustrates an example of a UE in accordance with aspects of the present disclosure.
  • Figure 8 illustrates an example of a processor in accordance with aspects of the present disclosure.
  • Figure 9 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.
  • Figure 10 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.
  • Figure 11 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.
  • Various aspects of the present disclosure relate to transmitting and/or receiving a request for SS/PBCH block transmissions a wireless communication system.
  • the SS/PBCH block transmissions may be requested on one serving cell, but may be for transmission of the SS/PBCH block on another serving cell.
  • the request may be transmitted from one device (e.g., UE), and the request may be received by another device (e.g., NE).
  • UE e.g., UE
  • NE another device
  • excessive data may be used for transmitting system information (e.g., SSBs, PBCH, SIB1), for example, the system information may be transmitted on a regular basis using excessive data, power, and other resources.
  • system information e.g., SSBs, PBCH, SIB1
  • FIG. 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a new radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • NR new radio
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology.
  • An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection.
  • an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area.
  • an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies.
  • an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN).
  • NTN non-terrestrial network
  • different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
  • the one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Intemet-of-Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
  • LoT Intemet-of-Things
  • LoE Intemet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a UE-to-UE interface (PC5 interface).
  • PC5 interface UE-to-UE interface
  • An NE 102 may support communications with the CN 106, or with another NE 102, or both.
  • an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface).
  • the NE 102 may communicate with each other directly.
  • the NE 102 may communicate with each other or indirectly (e.g., via the CN 106.
  • one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC).
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission -reception points (TRPs).
  • TRPs transmission -reception points
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)).
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
  • NAS non-access stratum
  • the CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface).
  • the packet data network may include an application server.
  • one or more UEs 104 may communicate with the application server.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102.
  • the CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session).
  • the PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).
  • the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications).
  • the NEs 102 and the UEs 104 may support different resource structures.
  • the NEs 102 and the UEs 104 may support different frame structures.
  • the NEs 102 and the UEs 104 may support a single frame structure.
  • the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures).
  • the NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames).
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols).
  • OFDM orthogonal frequency division multiplexing
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz).
  • FR1 410 MHz - 7.125 GHz
  • FR2 24.25 GHz - 52.6 GHz
  • FR3 7.125 GHz - 24.25 GHz
  • FR4 (52.6 GHz - 114.25 GHz
  • FR4a or FR4-1 52.6 GHz - 71 GHz
  • FR5 114.25 GHz - 300 GHz
  • the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data).
  • FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies).
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies).
  • a network may expend substantial energy in transmitting synchronization signal blocks (SSBs), physical broadcast channels (PBCHs) (e.g., containing a master information block (MIB) and/or a system information block (SIB) 1 (SIB1)).
  • SSBs synchronization signal blocks
  • PBCHs physical broadcast channels
  • MIB master information block
  • SIB1 system information block 1
  • the SIBs apart from SIB1 may be provided on demand. It may be desirable to save energy with respect to SSBs and SIB1. In one example, these may be provided on a need basis (e.g., on on-demand basis).
  • an anchor cell may be used as a proxy (e.g., for time-frequency synchronization, SIB1) for these.
  • procedures and/or signaling methods may be used to support on-demand SSB secondary cell (SCell) operation for UEs in a connected mode configured with carrier aggregation (CA), for both intra-band and inter-band CA.
  • SCell secondary cell
  • Such systems may specify triggering methods (e.g., select from a UE uplink wake-up-signal using an existing signal and/or channel, a cell on/off indication via backhaul, Scell activation and/or deactivation signaling, and so forth).
  • triggering methods e.g., select from a UE uplink wake-up-signal using an existing signal and/or channel, a cell on/off indication via backhaul, Scell activation and/or deactivation signaling, and so forth.
  • Different examples to establish signaling for a UE operating in CA to send a request for an on-demand SSB transmission on an SCell are described herein.
  • Emissions and energy consumption from different elements of a telecommunication system may adversely contribute to the climate. Further, the operating expenses to run a telecommunication service may be large. In telecom systems, a number of industry-specific factors rooted in countering rising network costs may shape efficiency efforts. There is a continued rise in mobile data traffic, estimated at 6.4 GB per user per month in 2019 and forecast to grow threefold on a per-user basis over the next five years. With the rise in mobile data traffic combined with the rising costs of the spectrum, capital investment, and ongoing radio access network (RAN) maintenance/upgrades, energy-saving measures in network operations may be necessary. 5G new radio (NR) may offer significant energy-efficiency improvements per gigabyte over previous generations of mobility. However, new 5G use cases and the adoption of mm Wave may require more sites and antennas. This may lead to a more efficient network that may paradoxically result in higher emissions without active intervention.
  • NR new radio
  • Network energy saving may be important for environmental sustainability, to reduce environmental impact (e.g., greenhouse gas emissions), and for operational cost savings.
  • environmental impact e.g., greenhouse gas emissions
  • operational cost savings e.g., energy savings.
  • 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications may require very high data rates (e.g., extended reality (XR)), networks may be denser, use more antennas, have larger bandwidths, and use more frequency bands.
  • XR extended reality
  • the environmental impact of 5G may need to be controlled, and network energy savings may need to be used.
  • the energy cost on mobile networks accounts for -23% of the total operator cost.
  • Most of the energy consumption may come from a radio access network and, in particular, from an active antenna unit (AAU), with data centers and fiber transport accounting for a smaller share.
  • AAU active antenna unit
  • the power consumption of radio access may be split into two parts: the dynamic part which is only consumed when data transmission and/or reception is ongoing, and the static part which is consumed all the time to maintain necessary operation of the radio access devices even when the data transmission and/or reception is not on -going.
  • a network energy consumption model may be used for a base station, key performance indicators (KPIs), an evaluation methodology, and to identify and study network energy savings techniques in targeted deployment scenarios.
  • KPIs key performance indicators
  • efficient operation may be determined dynamically and/or semi-statically and finer granularity adaptation of transmissions and/or receptions in one or more of network energy saving techniques in time, frequency, spatial, and power domains, with potential support/feedback from a UE, potential UE assistance information, and information exchange/coordination over network interfaces.
  • potential network energy consumption gains may be monitored and/or optimized, but also impact on network and user performance may be assessed and/or balanced (e.g., by looking at KPIs such as spectral efficiency, capacity, user perceived throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, service level agreement (SLA) assurance related KPIs, etc.).
  • KPIs such as spectral efficiency, capacity, user perceived throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, service level agreement (SLA) assurance related KPIs, etc.
  • the gNB 204 may transmit SSB/PBCH to the UE 202.
  • downlink synchronization may occur at the UE 202.
  • the gNB 204 may transmit SIB1 to the UE 202.
  • the UE may decode a control resource set (CORESET) 0 and/or the SIB1.
  • CORESET control resource set
  • UL synchronization and/or UL scheduling may occur.
  • a first message (e.g., preamble transmission) is transmitted.
  • the UE 202 selects a random access preamble from a set of predefined preambles. These preambles may be selected out of two categories: short preamble and long preamble format.
  • the UE 202 may also select a random sequence number for the preamble. After choosing the preamble and sequence number, the UE 202 transmits the preamble on a physical RACH (PRACH).
  • PRACH physical RACH
  • a second message (e.g., random access response (RAR)) may be transmitted.
  • the gNB 204 e.g., 5G base station
  • Msg2 may include several critical pieces of information, such as a time advance (TA) command for timing adjustment, a random access preamble ID (RAPID) matching the preamble sent by the UE 202, and an initial uplink grant for the UE 202.
  • TA time advance
  • RAPID random access preamble ID
  • the gNB 204 may also assign a temporary identifier called random access radio network temporary identifier (RA-RNTI) to the UE 202.
  • RA-RNTI random access radio network temporary identifier
  • a third message may be transmitted.
  • the UE 202 uses the initial uplink grant provided in Msg2, the UE 202 transmits Msg3 on a physical uplink shared channel (PUSCH).
  • Msg3 may be a PUSCH which may carry a certain RRC message (e.g., RrcRequest) or may be pure physical (PHY) data.
  • a fourth message (e.g., contention resolution) may be transmitted.
  • the gNB 204 may send Msg4 to the UE 202.
  • Msg4 may be MAC data which is for contention resolution.
  • the contention resolution message may contain the UE's identity, confirming that the gNB 204 has correctly identified the UE 202, and contention has been resolved.
  • the network may provide the UE 202 with cell radio network temporary identifier (C-RNTI).
  • C-RNTI cell radio network temporary identifier
  • cell search may be a procedure for a UE to acquire time and frequency synchronization with a cell and to detect a physical layer cell identity (ID) (PCI) of the cell.
  • ID physical layer cell identity
  • PCI physical layer cell identity
  • cell search operations which may be carried out when a UE is powered ON, mobility in connected mode, idle mode mobility (e.g., reselections), inter- RAT mobility to NR system etc., the UE uses NR synchronization signals and PBCH to derive necessary information required to access the cell.
  • synchronization signals may be defined for NR: primary synchronization signal (PSS) and secondary synchronization signal (SSS).
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • PBCH synchronization signal/physical broadcast channel
  • Synchronization signals may be used by a UE for reference signal received power (RSRP) and reference signal received quality (RSRQ) measurements.
  • RSRP reference signal received power
  • RSS reference signal received quality
  • FIG. 3 illustrates an example of a time and frequency structure 300 of a SS/PBCH block in accordance with aspects of the present disclosure.
  • the time and frequency structure 300 includes PSS 302, PBCH 304, and SSS 306.
  • the PSS 302, the SSS 306, and the PBCH 304 may always be together in consecutive OFDM symbols.
  • Each SS/PBCH block may occupy 4 OFDM symbols in the time domain and spread over 240 subcarriers (e.g., 20 resource blocks (RBs)) in the frequency domain.
  • the PSS 302 may occupy a first OFDM symbol and span 127 subcarriers.
  • the SSS 306 may be located in a third OFDM symbol and may span over 127 subcarriers. There may be 8 unused subcarriers below the SSS 306 and 9 unused subcarriers above the SSS 306.
  • SSB details in a time domain may be: each SS/PBCH block spans across 4
  • an SS/PBCH block is periodically transmitted with a periodicity of 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms, while longer SS/PBCH block periodicities enhances network energy performance, the shorter periodicities facilitate faster cell search for UEs, and a UE may assume a default periodicity of 20 ms during initial cell search or idle mode mobility.
  • An SS burst set may include a set of SS/PBCH blocks, where each SS/PBCH block may be transmitted on a different beam.
  • an SS burst set may include one or more SS/PBCH blocks, and SS/PBCH blocks in the SS burst set may be transmitted in a time-division multiplexing fashion.
  • An SS burst set may be confined to a 5 ms window and may either be located in a first-half or a second-half of a 10 ms radio frame.
  • the network may set a SS/PBCH block periodicity via radio resource control (RRC) parameter ssb-PeriodicityServingCell which may have values in the following range ⁇ 5ms, 10ms, 20ms, 40ms, 80ms, 160ms ⁇ .
  • RRC radio resource control
  • the maximum number of candidate SS/PBCH blocks (Lmax) within an SS burst set may depend on a carrier frequency/band as shown in Table 2.
  • SS/PBCH block within the SS burst set may depend upon a subcarrier spacing (SCS) and carrier frequency/band (e.g., as shown in Table 3).
  • SCS subcarrier spacing
  • Table 3 carrier frequency/band
  • the network When the network is not using beam forming, it may transmit only one SS/PBCH block and there may only be one SS/PBCH block starting position.
  • Figure 4 illustrates an example of a procedure 400 for MIB and/or SIB transmission flow in accordance with aspects of the present disclosure.
  • the procedure 400 may implement, or be implemented by, aspects of the wireless communication system 100 as described with reference to Figure 1.
  • the procedure 400 may include a UE 402 which may be an example of a UE 104 as described herein.
  • the procedure 400 may also include a gNB 404 which may be an example of a NE 102 as described herein.
  • the operations between the UE 202 and the gNB 204 may be transmitted in a different order than the example order shown, or the operations performed by the UE 202 and the gNB 204 may be performed in different orders or at different times. Some operations may also be omitted from the procedure 400, and other operations may be added to the procedure 400.
  • a MIB is transmitted.
  • a SIB1 is transmitted.
  • periodic system information messages are transmitted.
  • a system information request may be transmitted.
  • on request system information messages may be transmitted.
  • an MIB may be: transmitted over BCH and/or PBCH - it should be noted that PBCH is transmitted as a part of SSB so it may be beneficial to understand SSB as much as possible, transmitted with the periodicity of 80 ms and within this 80 ms repetitive transmission may happen, for initial cell selection - the UE 402 may assume that half frames with SS/PBCH blocks occur with a periodicity of 2 frames, and/or include parameters that are required to decode SIB1.
  • Table 4 shows one example of an MIB.
  • subCarrierSpacingCommon may indicate the SCS for SIB1, Msg2 and/or Msg4 for initial access and system information (Sl)-messages.
  • ssb-subcarrierOffset may correspond to k ssb which may indicate a frequency domain offset between SSB and an overall resource block grid in a number of subcarriers. If k ssb requires a value higher than 15, it may be represented by a combination of a PBCH data field and ssb-subcarrierOffset.
  • dmrs-TypeA -Position may indicate a position of a first downlink (DL) DM-RS.
  • pdcchConfigSIBl may be used to determine a bandwidth for physical downlink control channel (PDCCH)ZSIB, a common ControlResourceSet (CORESET), a common search space, and necessary PDCCH parameters. This may correspond to RMSI-PDCCH- Config.
  • Certain embodiments found herein may define signaling transmitted by a UE to indicate a request for an on-demand SSB transmission by a network.
  • SSB may be used to refer to an SS/PBCH block herein.
  • an SS/PBCH block may include 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SS/PBCH block, where PSS, SSS, and PBCH with associated DM-RS are mapped to symbols.
  • a UE requesting an on-demand SSB transmission on an SCell transmits a RACH preamble (e.g. a PRACH signal), on the PCell or on an active SCell to the network (e.g., to a gNB).
  • a RACH preamble e.g. a PRACH signal
  • a UE selects a RACH preamble from a pool of preambles designated for a non-contention based RACH procedure.
  • the UE selects the RACH preamble from a pool of preambles configured to trigger an on-demand SSB transmission.
  • the pool of preambles may be configured by the network by a UE -specific configuration, and may contain one or more preambles, such as PRACH signals generated based on one or more cyclic shifts or root sequence indexes.
  • a RACH preamble is associated with an SCell identifier so that, depending for which SCell a UE intends to request SSB transmission, a preconfigured RACH preamble is transmited.
  • the UE may be configured with the association so that a first RACH preamble is associated with a first SCell (e.g., a first SCell index), a second RACH preamble is associated with a second SCell (e.g., a second SCell index), and so forth.
  • the association may be configured by the network by a UE -specific configuration. Consequently, a network element, such as a gNB receiving the RACH preamble, may identify which SCell the SSB request is intended for.
  • the UE receives a message from the network (e.g., RACH Msg 2) after transmiting a RACH preamble.
  • the message includes scheduling information for a subsequent uplink transmission (e.g., for a RACH Msg 3).
  • the UE may transmit SSB request assistance information as part of the subsequent uplink transmission.
  • the SSB request assistance information may include one or more of:
  • At least one SCell identifier (e.g., an SCell index) for which the UE is requesting SSB transmission;
  • C A number of SSB transmissions that is being requested, and optionally a time patern (e.g., a periodicity or offset between transmissions) if multiple SSB transmissions are being requested;
  • a time patern e.g., a periodicity or offset between transmissions
  • a time window (e.g., by a start time and an end time, or a start time and a duration) during which the UE is ready to receive the requested SSB transmission;
  • a periodicity after which the time window repeats The periodicity may be calculated from either the start or end of the time window;
  • G Whether a full SSB is requested or only part of an SSB (e.g., one or more of the following: PSS, SSS, PBCH, MIB, PBCH DM-RS, and PBCH payload); [0080] H.
  • the PBCH e.g., MIB + information conveyed by PBCH DM-RS) configuration (or parts thereof) for the SCell that is available at the UE;
  • the subcarrier spacing that the UE is requesting for the SSB transmission for an operating band allowing two subcarrier spacings - indicates whether a lower or higher of two subcarrier spacings is requested;
  • K Measurement values of the current serving cells for which the UE has received SSB recently (e.g., within a configured time prior to transmission and/or creation of the SSB request.
  • the UE transmits SSB request assistance information as part of a PUSCH transmission accompanying a RACH preamble transmission (e.g., RACH Msg A).
  • the SSB request assistance information may include one or more of:
  • An identifier or a flag to indicate that the RACH procedure includes or represents a request for an on-demand SSB transmission may be suitable where there is no specific RACH preamble predefined for a non-contention based RACH procedure (e.g. it is a general predefined RACH preamble for a non-contention based RACH procedure) or where a RACH preamble is selected for a contention-based RACH procedure;
  • At least one SCell identifier (e.g., an SCell index) for which the UE is requesting SSB transmission;
  • C A number of SSB transmissions that is being requested, and optionally a time pattern (e.g., a periodicity or offset between transmissions) if multiple SSB transmissions are being requested;
  • a time pattern e.g., a periodicity or offset between transmissions
  • a time window (e.g., by a start time and an end time, or a start time and a duration) during which the UE is ready to receive the requested SSB transmission;
  • F A periodicity after which the time window repeats.
  • the periodicity may be calculated from either the start or end of the time window;
  • G Whether a full SSB is requested or only part of an SSB (e.g., one or more of the following: PSS, SSS, PBCH, MIB, PBCH DM-RS, and PBCH payload);
  • the PBCH e g., MIB + information conveyed by PBCH DM-RS
  • PBCH DM-RS information conveyed by PBCH DM-RS
  • the subcarrier spacing that the UE is requesting for the SSB transmission for an operating band allowing two subcarrier spacings - indicates whether a lower or higher of two subcarrier spacings is requested;
  • K Measurement values of the current serving cells for which the UE has received SSB recently (e.g., within a configured time prior to transmission and/or creation of the SSB request.
  • MsgA-PUSCH is transmitted after a PRACH.
  • a UE may transmit a PUSCH, when applicable, after transmitting a PRACH.
  • the UE may encode a transport block provided for the PUSCH transmission using redundancy version number 0.
  • a UE may not transmit a PUSCH in a PUSCH occasion if the PUSCH occasion associated with a DM-RS resource is not mapped to a preamble of valid PRACH occasions or if the associated PRACH preamble is not transmitted.
  • a UE may transmit a PRACH preamble in a valid PRACH occasion if the PRACH preamble is not mapped to a valid PUSCH occasion.
  • a mapping between one or multiple PRACH preambles and a PUSCH occasion associated with a DM-RS resource may be per PUSCH configuration provided by MsgA-PUSCH-Re source.
  • a UE may determine time resources and frequency resources for PUSCH occasions in an active UL BWP from msgA-PUSCH-Config or separateMsgA-PUSCH- Config for the active UL BWP. If the active UL BWP is not the initial UL BWP and msgA-PUSCH-Config or separateMsgA-PUSCH-Config is not provided for the active UL BWP, the UE may use the msgA-PUSCH-Config or separateMsgA-PUSCH-Config provided for the initial UL BWP.
  • a UE may determine whether it requires MIB information based on whether a timer has expired, or a gNB may determine whether it needs to transmit MIB information based on whether a timer has expired.
  • the timer may be exemplarily of a MIBExpirationTimer and may resemble a duration for which a UE may assume that the information in MIB hasn’t changed since the latest reception of MIB for the serving cell, or may resemble a duration for which a gNB may assume that the UE’s information derived from MIB hasn’t changed since the latest transmission of MIB for the serving cell.
  • the UE may reset a timer to an initial value; upon transmission of a MIB, the gNB may reset a timer to an initial value.
  • the initial value may be predefined by a specification or may be configurable by a network element.
  • the initial value may be chosen from a set of multiples of a MIB (or generally, SSB) periodicity.
  • the periodicity of SSB transmissions may be set to one of the following values ⁇ 5ms, 10ms, 20ms, 40ms, 80ms, 160ms ⁇ by RRC parameter ssb-PeriodicityServingCell, so the initial value may be set to a multiple of one or more of these values.
  • a UE indicates a request for at least MIB if the last acquisition time of MIB for the SCell is longer than a preconfigured time, such as 80 ms.
  • the preconfigured value may be selected the same way as an initial value for a time-based implementation (e.g., from a set of multiples of a MIB (or generally, SSB) periodicity such as multiples of one of the following values ⁇ 5ms, 10ms, 20ms, 40ms, 80ms, 160ms ⁇ in 5G NR).
  • a UE requesting an on-demand SSB transmission on an SCell transmits a SSB request medium access control (MAC) control element (CE) (MAC CE) on a PCell or on an active SCell to the network (e.g., to a gNB).
  • MAC medium access control
  • CE control element
  • the MAC CE indicates the request with a specific LCID (e.g., as part in a corresponding MAC subheader associated with the MAC CE).
  • the UE may include SSB request assistance information as part of an SSB request MAC CE.
  • the SSB request assistance information may include one or more of the following:
  • a time window (e.g., by a start time and an end time, or a start time and a duration) during which the UE is ready to receive the requested SSB transmission;
  • E A periodicity after which the time window repeats.
  • the periodicity may be calculated from either the start or end of the time window;
  • SSB Whether a full SSB is requested or only part of the SSB (e.g., one or more of PSS, SSS, PBCH, MIB, PBCH associated DM-RS, PBCH payload);
  • the PBCH e.g., MIB + information conveyed by PBCH DM-RS
  • PBCH DM-RS PBCH DM-RS
  • a UE may determine whether it requires MIB information based on whether a timer has expired, or a gNB may determine whether it needs to transmit MIB information based on whether a timer has expired.
  • the timer may be exemplarily of a MIBExpirationTimer and may resemble a duration for which a UE may assume that the information in MIB hasn’t changed since the latest reception of MIB for the serving cell, or may resemble a duration for which a gNB may assume that the UE’s information derived from MIB hasn’t changed since the latest transmission of MIB for the serving cell.
  • the UE may reset a timer to an initial value; upon transmission of a MIB, the gNB may reset a timer to an initial value.
  • the initial value may be predefined by a specification or may be configurable by a network element.
  • the initial value may be chosen from a set of multiples of a MIB (or generally, SSB) periodicity.
  • the periodicity of SSB transmissions may be set to one of the following values ⁇ 5ms, 10ms, 20ms, 40ms, 80ms, 160ms ⁇ by RRC parameter ssb-PeriodicityServingCell, so the initial value may be set to a multiple of one or more of these values.
  • a UE may indicate a request for at least MIB if the last acquisition time of MIB for the SCell is longer than a preconfigured time, such as 80 ms.
  • the preconfigured value may be selected the same way as the initial value for a time-based implementation (e.g., from a set of multiples of a MIB (or generally, SSB) periodicity (e.g., multiples of one of the following values ⁇ 5ms, 10ms, 20ms, 40ms, 80ms, 160ms ⁇ in 5G NR).
  • start time and duration may be requested and configured as SSB-based RRM measurement timing configuration (SMTC) patterns with the following parameters:
  • Periodicity and offset of a measurement window in which to receive SS/PBCH blocks may be given as a number of subframes
  • C Duration of the measurement window in which to receive SS/PBCH blocks. It may be given as a number of subframes; and/or
  • the UE may request SSB transmission to enable configuration measurement timing configurations (e.g., timing occasions at which the UE proposes to measure SSBs).
  • the network may accept the same configuration as requested by the UE, or may use different values depending on an overall situation (e.g., how many UEs need SSB transmission).
  • Figure 5 illustrates an example of a procedure 500 for SMTC communications in accordance with aspects of the present disclosure.
  • the procedure 500 may implement, or be implemented by, aspects of the wireless communication system 100 as described with reference to Figure 1.
  • the procedure 500 may include a UE 502 which may be an example of a UE 104 as described herein.
  • the procedure 500 may also include a gNB 504 which may be an example of a NE 102 as described herein.
  • the operations between the UE 502 and the gNB 504 may be transmitted in a different order than the example order shown, or the operations performed by the UE 502 and the gNB 504 may be performed in different orders or at different times. Some operations may also be omitted from the procedure 500, and other operations may be added to the procedure 500.
  • the UE 502 may request SMTC. Then, at 508, the gNB 504 may transmit SMTC.
  • a priority of an SSB request MAC CE for logical channel prioritization may be higher than a priority of one or more of the following:
  • MAC CE for integrated access and backhaul (lAB)-mobile terminal (MT) a recommended beam indication, MAC CE for a desired IAB-MT power spectral density (PSD) range, or a MAC CE for a desired DL Tx power adjustment;
  • lAB integrated access and backhaul
  • MT mobile terminal
  • PSD power spectral density
  • a priority of an SSB request MAC CE for logical channel prioritization may be lower than a priority of one or more of the following:
  • a MAC CE for a positioning measurement gap activation and/or deactivation request is provided.
  • generation of a SSB request MAC CE may trigger a scheduling request (SR) or RACH procedure.
  • a new SSB request MAC CE may be associated with a SR configuration.
  • An SR configuration may include a set of physical uplink control channel (PUCCH) resources for the SR across different BWPs and cells.
  • PUCCH physical uplink control channel
  • at most one PUCCH resource for SR is configured per BWP for the SSB request MAC CE.
  • a dedicated SR configuration is configured for the SSB request MAC CE.
  • the SR configuration for a SSB request MAC CE may correspond to one or more logical channels.
  • a SR triggered for a SSB request MAC CE may be cancelled if the corresponding SSB request has been cancelled.
  • an SR triggered for an SSB request may be cancelled if a MAC PDU is transmitted and this PDU includes an SSB request MAC CE.
  • an SSB request MAC CE may correspond to a specific MAC subheader.
  • the MAC CE may have a fixed or variable size. In one example having a variable size, it may include one or more of the following fields:
  • F This field may indicate the presence of the octet containing an SCell index field and the presence of the octets containing Ci fields. If the F field is set to 1, the octet containing SCell index field may be present and the octets containing Ci fields may not be present. If the F field is set to 1, the octet containing the SCell index field may not be present and the octets containing Ci fields may be present;
  • SCell index This field may indicate the identity of the SCelllndex i for which the UE requests an SSB transmission.
  • the length of the field may be 5 bits;
  • Ci If there is an SCell configured for the MAC entity with SCelllndex i, this field may indicate whether SSB is requested for SCell with SCelllndex i.
  • the Ci field may be set to 1 to indicate that SSB for the SCell with SCelllndex i is requested.
  • the Ci field may be set to 0 to indicate that SSB for the SCell with SCelllndex i is not requested;
  • D. TX This field indicates how many SSB transmissions the UE is requesting.
  • the length of the field may be 3 bits;
  • E. MU This field may indicate, for operating bands supporting two subcarrier spacings, whether the lower or higher of the subcarrier spacings is requested.
  • the MU field may be set to 0 to indicate the lower of the two supported subcarrier spacings is requested.
  • the MU field may be set to 1 to indicate the higher of the two supported subcarrier spacings is requested.
  • the MAC entity may ignore the MU field;
  • F. SSB block ID This field may indicate an index of the SSB that the UE requests. If this field is set to 0, then no specific beam is requested. The length of the field may be 6 bits;
  • G. B This field may indicate the SSB content that is being requested.
  • the field may be set to 0 to indicate that only PSS and/or SSS is requested.
  • the field may be set to 1 to indicate that PSS, SSS, PBCH, and associated DM-RS are requested;
  • This field may indicate a SFN for the earliest frame when the UE is ready to receive the requested SSB transmission.
  • the length of the field may be 10 bits;
  • Duration This field may indicate for how many subframes the UE is ready to receive the requested SSB transmission.
  • the length of the field may be 2 bits; and/or
  • J. R A reserved bit that may be set to 0.
  • Figure 6 illustrates an example of a structure of an SSB request MAC CE 600 in accordance with aspects of the present disclosure.
  • Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure.
  • the UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708.
  • the processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
  • the processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • the processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, a field programmable gate array (FPGA), or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.
  • an intelligent hardware device e.g., a general-purpose processor, a DSP, a CPU, an ASIC, a field programmable gate array (FPGA), or any combination thereof.
  • the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702.
  • the processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.
  • the memory 704 may include volatile or non-volatile memory.
  • the memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704).
  • the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein.
  • the processor 702 coupled with the memory 704 may be configured to cause the UE 700 to generate a request for at least one transmission of at least one SS/PBCH block based at least in part on a condition.
  • the processor 702 coupled with the memory 704 may be configured to cause the UE 700 to transmit, to a first serving cell, control signaling that indicates the request for the at least one transmission of the at least one SS/PBCH block associated with a second serving cell.
  • the controller 706 may manage input and output signals for the UE 700.
  • the controller 706 may also manage peripherals not integrated into the UE 700.
  • the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems.
  • the controller 706 may be implemented as part of the processor 702.
  • the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708.
  • the transceiver 708 may represent a wireless transceiver.
  • the transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.
  • a receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 710 may include one or more antennas for receiving the signal over the air or wireless medium.
  • the receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal.
  • the receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets).
  • the transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM).
  • the transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • FIG. 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure.
  • the processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein.
  • the processor 800 may optionally include at least one memory 804, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic -logic units (ALUs) 806.
  • ALUs arithmetic -logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
  • the processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • flash memory phase change memory
  • PCM phase change memory
  • the controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to track memory address of instructions associated with the memory 804.
  • the controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to manage flow of data within the processor 800.
  • the controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.
  • ALUs arithmetic logic units
  • the memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).
  • caches e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).
  • the memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein.
  • the code may be stored in a non- transitory computer-readable medium such as system memory or another type of memory.
  • the controller 802 and/or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions.
  • the processor 800 and/or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein.
  • the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800).
  • the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800).
  • One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation.
  • the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 800 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 800 may be configured to or operable to support a means for: generating a request for at least one transmission of at least one SS/PBCH block based at least in part on a condition, and transmitting, to a first serving cell, control signaling that indicates the request for the at least one transmission of the at least one SS/PBCH block associated with a second serving cell.
  • FIG. 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure.
  • the NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908.
  • the processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
  • the processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-
  • the processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.
  • an intelligent hardware device e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof.
  • the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902.
  • the processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.
  • the processor 902 coupled with the memory 904 may be configured to cause the NE 900 to: receive, at a first serving cell, control signaling that indicates a request for at least one transmission of at least one SS/PBCH, and determine at least in part from the control signaling a second serving cell associated with the request.
  • the memory 904 may include volatile or non-volatile memory.
  • the memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904).
  • the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein.
  • the controller 906 may manage input and output signals for the NE 900.
  • the controller 906 may also manage peripherals not integrated into the NE 900.
  • the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems.
  • the controller 906 may be implemented as part of the processor 902.
  • the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908.
  • the transceiver 908 may represent a wireless transceiver.
  • the transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.
  • a receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium.
  • the receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal.
  • the receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets).
  • the transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM).
  • the transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • FIG. 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure.
  • the operations of the method 1000 may be implemented by a UE as described herein.
  • a UE 700 may execute a set of instructions to control the function elements of a processor to perform the described functions.
  • the method may include generating a request for at least one transmission of at least one SS/PBCH block based at least in part on a condition.
  • the operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a UE as described with reference to Figure 7.
  • the method may include transmitting, to a first serving cell, control signaling that indicates the request for the at least one transmission of the at least one SS/PBCH block associated with a second serving cell.
  • the operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a UE as described with reference to Figure 7.
  • FIG. 11 illustrates a flowchart of another method 1100 in accordance with aspects of the present disclosure.
  • the operations of the method 1100 may be implemented by a NE as described herein.
  • aNE 900 may execute a set of instructions to control the function elements of a processor to perform the described functions.
  • the method may include receiving, at a first serving cell, control signaling that indicates a request for at least one transmission of at least one SS/PBCH.
  • the operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 9.
  • the method may include determining at least in part from the control signaling a second serving cell associated with the request.
  • the operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 9. [0187] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent des procédés, des appareils et des dispositifs de communication sans fil. Un équipement utilisateur (UE) peut générer (1002) une demande pour au moins une transmission d'au moins un bloc SS/PBCH sur la base, au moins en partie, d'une condition. L'UE peut également transmettre (1004), à une première cellule de desserte, une signalisation de commande qui indique la demande pour ladite transmission dudit bloc SS/PBCH associé à une seconde cellule de desserte.
PCT/IB2025/051331 2024-02-09 2025-02-07 Appareil et procédé de communication de demandes de transmission de bloc de canal de diffusion physique/signal de synchronisation dans un système de communication sans fil Pending WO2025114999A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463552053P 2024-02-09 2024-02-09
US63/552,053 2024-02-09

Publications (1)

Publication Number Publication Date
WO2025114999A1 true WO2025114999A1 (fr) 2025-06-05

Family

ID=94732921

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/051331 Pending WO2025114999A1 (fr) 2024-02-09 2025-02-07 Appareil et procédé de communication de demandes de transmission de bloc de canal de diffusion physique/signal de synchronisation dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2025114999A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230328644A1 (en) * 2022-03-31 2023-10-12 Samsung Electronics Co., Ltd. Communication method, user equipment and base station
GB2619495A (en) * 2022-05-30 2023-12-13 Nec Corp Communication system
WO2024011389A1 (fr) * 2022-07-11 2024-01-18 Nokia Shanghai Bell Co., Ltd. Fourniture d'informations de système

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230328644A1 (en) * 2022-03-31 2023-10-12 Samsung Electronics Co., Ltd. Communication method, user equipment and base station
GB2619495A (en) * 2022-05-30 2023-12-13 Nec Corp Communication system
WO2024011389A1 (fr) * 2022-07-11 2024-01-18 Nokia Shanghai Bell Co., Ltd. Fourniture d'informations de système

Similar Documents

Publication Publication Date Title
WO2024217086A1 (fr) Procédés et appareil prenant en charge deux états de réglage de commande de puissance en boucle fermée séparés pour des transmissions de srs
WO2025150024A1 (fr) Gestion de trames de radiomessagerie pour des communications sans fil
EP4552370A2 (fr) Techniques de gestion d'interférence dans une opération de duplexage par répartition dans le temps dynamique
WO2025114999A1 (fr) Appareil et procédé de communication de demandes de transmission de bloc de canal de diffusion physique/signal de synchronisation dans un système de communication sans fil
WO2025114998A1 (fr) Appareil et procédé de communication de demandes de transmission de bloc de signal de synchronisation/canal de diffusion physique dans un système de communication sans fil
US20250203667A1 (en) Techniques for dynamic waveform switching during initial access
US20250280448A1 (en) Random access channel (rach) configurationsin asymmetric transmission and reception point (trp) deployments
US20250280447A1 (en) Random access in asymmetric transmission and reception point (trp) deployments
WO2024098837A1 (fr) Procédés et appareils pour un accès à de multiples canaux sur une liaison latérale
WO2025141554A1 (fr) Demande de transmission de bloc de signal de synchronisation/canal de diffusion physique dans un système de communication sans fil
WO2024239713A1 (fr) Procédé et appareil de prise en charge de communications en liaison montante
US20250317877A1 (en) On-demand system information block 1 (sib1) request
US20250280453A1 (en) Selection of resource sets for random access procedures
US20250351119A1 (en) Mapping paging resources to random access channel occasions
US20250126655A1 (en) Network-assisted cell selection for 2-step random access procedures
US20250220729A1 (en) Performing operations with multiple carriers in a wireless communications system
US20250317939A1 (en) On-demand sib1 transmission
WO2024109168A1 (fr) Procédés et appareils pour transmissions sur liaison latérale dans des spectres sans licence
US20250126548A1 (en) Network-assisted cell selection for 4-step random access procedures
WO2024193186A1 (fr) Procédé et appareil de transmission de données
WO2024174553A1 (fr) Répétition prach avec différents faisceaux
WO2024227367A1 (fr) Procédé et appareil de prise en charge de rapport d'informations d'état de canal
WO2024239695A1 (fr) Procédé et appareil de prise en charge de transmissions en liaison montante
US20250240827A1 (en) Cross-link interference (cli) aware physical random access (prach)transmission with sub-band full-duplex (sbfd)
WO2025236728A1 (fr) Procédés et appareils d'établissement de rapport de marge de puissance dans un système mimo massif sans cellule

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25707119

Country of ref document: EP

Kind code of ref document: A1