Systems, methods, and devices for initial access signaling in wireless communication network

By adjusting the transmission method and number of synchronization signal blocks by the base station in the wireless communication network, the problem of blocked control frame transmission in the high-frequency band is solved, and more efficient signaling synchronization is achieved.

CN119095187APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411470118.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-09-24
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In wireless communication networks, especially in high frequency bands, control frame transmission is easily over-hindered due to too many synchronization signal blocks (SSBs), resulting in limited signaling synchronization process and difficult to meet the 10% control frame transmission margin standard.

Method used

The base station adjusts the transmission mode and number of SSBs by indicating whether the discovery burst transmission window (DBTW) is enabled or disabled, whether the LBT is enabled or disabled, and the number and activity of synchronized signal blocks to avoid excessive obstruction. These indications may be provided by specific fields and bitmaps in the main information block (MIB) or system information block (SIB).

Benefits of technology

By adjusting the transmission method and number of SSBs, the control frame transmission is not overly hindered by too many SSBs, and the 10% control frame transmission margin standard is met, which improves the efficiency and reliability of signaling synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095187A_ABST
    Figure CN119095187A_ABST
Patent Text Reader

Abstract

The present disclosure relates to systems, methods, and devices for initial access signaling in a wireless communication network. The techniques described herein may enable a base station and user equipment (UE) to implement initial access related signaling, which may change the number of synchronization signal blocks (SSBs) transmitted by the base station to better ensure that control frame transmissions (e.g., 120 kHz (kHz) subcarrier spacing (SCS) transmissions) are not excessively blocked by the SSBs. A base station may indicate whether a discovery burst transmission window (DBTW) is enabled or disabled, whether a listen before talk (LBT) is enabled or disabled, and whether a transmission corresponds to a licensed band, an unlicensed band, or a combination thereof. The base station may also indicate a number of candidate SSBs for each DBTW and / or which SSB / SSB groups in each discovery burst (DB) are active (e.g., actual transmission).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Division Statement

[0002] This application is a divisional application of the Chinese invention patent application with the application date of September 24, 2021, the invention name of "System, method and device for initial access signaling in a wireless communication network" and the application number of 202180006660.9. Technical Field

[0003] The present disclosure relates to wireless communication networks, including techniques for systems and devices for managing wireless communication networks. Background Art

[0004] A wireless communication network may include user equipment (UE) (e.g., smart phones, tablet computers, etc.) capable of communicating with base stations and other network nodes. Aspects of a wireless communication network include the manner, conditions, scenarios, and procedures by which wireless devices connect to each other and otherwise communicate with each other. This may involve issues related to how wireless devices may initially become aware of each other and synchronize with each other to prepare for additional communications (such as access procedures, establishing connections, etc.). Summary of the invention

[0005] Some embodiments of the present application provide a baseband processor, comprising: a memory configured to store instructions; and one or more processors, which, when executing the instructions, are configured to: transmit the time domain positions of multiple transmitted SSBs within a synchronization signal block (SSB) burst; and perform synchronization using the multiple transmitted SSBs, wherein the time domain positions of the multiple transmitted SSBs are indicated by a first bitmap indicating at least one transmitted SSB group and a second bitmap indicating the time domain positions of the multiple transmitted SSBs in the at least one SSB group.

[0006] Some embodiments of the present application also provide a user equipment (UE), comprising: a memory and one or more processors, wherein the one or more processors are configured to, when executing instructions stored in the memory, enable the UE to: receive an indication of the time domain positions of multiple transmitted SSBs within a synchronization signal block (SSB) burst from a base station of a wireless communication network; receive the multiple transmitted SSBs from the base station; and perform synchronization with the base station based on the multiple transmitted SSBs, wherein the time domain positions of the multiple transmitted SSBs are indicated by the SSB position field of the service cell configuration included in the system information block type 1 (SIB1).

[0007] Some embodiments of the present application also provide a method, comprising: receiving an indication of the time domain positions of multiple transmitted SSBs within a synchronization signal block (SSB) burst from a base station of a wireless communication network; receiving the multiple transmitted SSBs from the base station; and performing synchronization with the base station based on the multiple transmitted SSBs, wherein the time domain positions of the multiple transmitted SSBs are indicated by a first bitmap indicating at least one transmitted SSB group and a second bitmap indicating the time domain positions of the multiple transmitted SSBs in at least one SSB group. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The present disclosure will be easily understood and implemented through the specific embodiments and the accompanying drawings. Similar reference numerals may designate similar features and structural elements. The accompanying drawings and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc. of the present disclosure, and references to "an" or "one" aspect, implementation, etc. may not necessarily refer to the same aspect, implementation, etc., and may mean at least one, one or more, etc.

[0009] Figure 1 is a diagram of examples of frame, slot, and symbol structures with synchronization signal block (SSB) locations for 120 kilohertz (kHz) subcarrier spacing (SCS) and 240 kHz SCS.

[0010] Figure 2 is a diagram of an example of a frame, slot, and symbol structure with SSB locations for 480 kHz SCS and 960 kHz SCS.

[0011] Figure 3 is a diagram of an example network according to one or more implementations described herein.

[0012] Figure 4 is a diagram of an exemplary overview of initial access signaling in a wireless communication network according to one or more implementations described herein.

[0013] Figure 5 is a diagram of an example of a process for initial access signaling in a wireless communication network.

[0014] Figure 6 is used to jointly signal whether DBTW is enabled or disabled and Figure 1 is an example of a table of parameters.

[0015] Figure 7 is used to jointly signal whether DBTW is enabled or disabled and Figure 1 is an example of a table of parameters.

[0016] Figure 8is a diagram of an example of a monitoring opportunity (MO) based on whether an indication is provided as to whether DBTW is enabled or disabled.

[0017] Fig. 9 is a diagram of an example of a table for indicating a licensed band or an unlicensed band based on a scrambling sequence.

[0018] Figures 10 to 12 is a diagram of examples for indicating active SSBs and / or active SSB groups for DBTW.

[0019] Fig.13 is a diagram of an example of components of a device according to one or more implementations described herein.

[0020] Fig.14 is a diagram of an exemplary interface of a baseband circuit according to one or more implementations described herein. DETAILED DESCRIPTION

[0021] The following detailed description refers to the accompanying drawings. Similar reference numerals in different drawings may identify the same or similar features, elements, operations, etc. In addition, the present disclosure is not limited to the following description, as other specific implementations may be utilized, and structural or logical changes may be made without departing from the scope of the present disclosure.

[0022] A wireless communication network may include user equipment (UE) capable of wireless communication with base stations and other network nodes. These devices and communications may implement different types of radio access technologies (RATs), which may involve fourth generation (4G) or long term evolution (LTE) technology of the 3rd Generation Partnership Project (3GPP), fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, etc. Basic aspects of implementing such technologies may include initial access signaling and signal synchronization.

[0023] Signal synchronization may include the process by which a UE obtains the time and frequency for communicating with and accessing a wireless network. Two types of synchronization may be included: one for downlink (DL) synchronization and the other for uplink (UL) synchronization. For DL ​​synchronization, the UE may detect frame boundaries and symbol boundaries based on a synchronization signal block (SSB) from the network. The SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH), which may be used for signal synchronization. For uplink synchronization, the UE may determine an appropriate time period for transmitting data. Because a base station may communicate with multiple UEs simultaneously, the network may be configured to ensure that the UL signal arrives at the network at the appropriate time for random access channel (RACH) procedures and other information changes.

[0024] In 5G, signals may be organized into frames, each consisting of 10 milliseconds (ms). A frame may include 10 subframes of 1 ms each, and each subframe may include multiple slots, which may depend on the subcarrier spacing (SCS). For example, a subframe may include 8 slots with a subcarrier spacing (SCS) of 120 kilohertz (kHz), 16 slots with an SCS of 240kHz, and the like. Each slot may include 14 orthogonal frequency division multiplexing (OFDM) symbols indexed from 0-13. A synchronization signal (SS) burst or SSB burst may include multiple SSBs, and each SSB may span 4 OFDM symbols, with 1 symbol for PSS, 1 symbol for SSS, and 2 symbols for PBCH. The SSBs may be grouped into the first 5 ms of the SSB burst.

[0025] Figure 1 1 is a diagram of an example 100 of a frame, slot, symbol structure with candidate SSB positions for 120kHz SCS and 240kHz SCS. An SSB burst may include up to (L) 64 SSBs per half frame. In a 120kHz SCS scenario, the starting symbol position of each SSB may include [4,8,16,20]+28n, where n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, and 18. In a 240kHz SCS scenario, the starting symbol position of each SSB may include [8,12,16,20,32,36,40,44]+56n, where n=0, 1, 2, 3, 5, 6, 7, and 8. Figure 2 2 is a diagram of an example 200 of a frame, slot, symbol structure with SSB start positions for 480kHz SCS and 960kHz SCS. The first symbol of a candidate SSB for 480kHz SCS and 960kHz SCS may have symbol index [2,9]+14n (where index 0 corresponds to the first symbol of the first slot in a half-frame). Figure 1 As described above, under 480kHz SCS and 960kHz SCS, an SSB burst may include up to 64 SSBs in a half frame.

[0026] While in some frequency bands (such as the 5 GHz or 6 GHz bands), there is a limit on the number of control transmissions in higher frequency bands (such as the 52.6 GHz band or above), there is no limit on the number of control transmissions within an observation period, but rather a limit on the total duration of the control transmissions. For example, without implementing listen-before-talk (LBT), up to a 10% margin for control frame transmissions in these frequency bands is allowed or acceptable within a 100 ms observation period. And while, for example, 480 kHz SCS and 960 kHz SCS may meet this 10% criterion in higher frequency bands (assuming 64 SSBs and a periodicity of 20 ms), 120 kHz SCS may not meet this criterion due to, for example, the larger portion of symbols allocated to the 64 SSBs per time slot. In other words, broadcasting 64 SSBs per SSB burst under a 120 kHz SCS may cause control frame transmissions to be overly blocked due to the 64 SSBs. Furthermore, since the 10% control frame transmission standard is applicable to scenarios involving LBT requirements, and since some wireless communication networks (e.g., networks in certain countries) may always require LBT, addressing whether and how LBT applies to a particular wireless communication network is an ideal feature for satisfying the 10% transmission blocked standard.

[0027] The techniques described herein may enable a base station and a UE to implement initial access-related signaling, which may vary the number of SSBs transmitted by the base station to better ensure that control frame transmissions (e.g., 120kHz SCS transmissions) are not overly blocked by too many SSBs. These techniques include a variety of ways in which a base station may indicate whether a discovery burst transmission window (DBTW) is enabled or disabled for one or more SCSs, whether LBT is enabled or disabled, whether transmissions are applied to licensed or unlicensed bands, the number of SSBs per DBTW, and / or which SSBs / SSB groups are actually active (e.g., actual transmissions) in each discovery burst (DB). As described below with reference to the accompanying drawings, the base station may indicate this information implicitly or explicitly based on, for example, one or two bits of an existing information element (IE) (e.g., subCarrierSpacingCommon IE, controlResourceSetZero IE, etc.), a parameter (e.g., Parameter, where N is the number of SSBs associated with the quasi co-location (QCL)) and / or a bitmap corresponding to one or more existing fields (e.g., groupPresence field, inOneGroup field, etc.) of a master information block (MIB) or a system information block (SIB).

[0028] DBTW may include the duration and manner in which the base station may transmit the DB (e.g., the duration that the UE may expect the base station to transmit the DB). The DB may include a DL transmission burst that includes one or more signals and / or channels confined within a window and associated with a communication period (also known as a duty cycle). The DB may include any combination of the following items: 1) one or more transmissions transmitted by a base station that includes a PSS, SSS, a cell-specific reference signal (CRS) and may include a non-zero power channel state information (CSI) reference signal (CSI-RS); and 2) one or more transmissions transmitted by a base station that includes an SS / PBCH block consisting of a PSS, SSS, PBCH, and a demodulation reference signal (DM-RS). The transmission may also include a control resource set (CORESET) for a physical DL control channel (PDCCH) that schedules a physical downlink shared channel (PDSCH) with a system information block 1 (SIB1) and a PDSCH carrying SIB1 and / or a non-zero power CSI reference signal (CSI-RS).

[0029] Figure 3 300 according to one or more implementations described herein. The exemplary network 300 may include UE 310-1, UE 310-2, etc. (collectively referred to as "UE 310", and individually referred to as "UE 310"), a radio access network (RAN) 320, a core network (CN) 330, an application server 340, an external network 350, and satellites 360-1, satellite 360-2, etc. (collectively referred to as "satellite 360" and individually referred to as "satellite 360"). As shown, the network 300 may include a non-terrestrial network (NTN) including one or more satellites 360 (e.g., one or more satellites of a global navigation satellite system (GNSS)) that communicate with the UE 310 and the RAN 320.

[0030] The systems and devices of the exemplary network 300 may operate in accordance with one or more communication standards, such as the 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., Long Term Evolution (LTE)), and / or 5th generation (5G) (e.g., New Radio (NR)) communication standards of the 3rd Generation Partnership Project (3GPP). Additionally or alternatively, one or more of the systems and devices of the exemplary network 300 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., the 6th generation (6G) standard, the 7th generation (7G) standard, etc.), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., Wireless Metropolitan Area Network (WMAN), Worldwide Interoperability for Microwave Access (WiMAX), etc.), etc.), and the like.

[0031] As shown, UE 310 may include a smart phone (e.g., a handheld touch screen mobile computing device capable of connecting to one or more wireless communication networks). Additionally or alternatively, UE 310 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld terminal, etc. In some specific implementations, UE 310 may include an Internet of Things (IoT) device (or IoT UE), which may include a network access layer designed for low-power IoT applications that utilize transient UE connections. Additionally or alternatively, IoT UE may utilize one or more types of technologies, such as machine-to-machine (M2M) communication or machine-type communication (MTC) (e.g., exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximity services (ProSe) or device-to-device (D2D) communication, sensor networks or IoT networks, etc. Depending on the scenario, the M2M or MTC data exchange may be a machine-initiated exchange, and the IoT network may include utilizing transient connections to interconnect IoT UEs (which may include uniquely identifiable embedded computing devices within the Internet infrastructure). In some scenarios, the IoT UE may execute background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0032] UE 310 may communicate with RAN 320 and establish a connection therewith (e.g., communicatively coupled), which may involve one or more radio channels 314-1 and 314-2, each of which may include a physical communication interface / layer. In some implementations, the UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a UE capable of multiple reception and transmission (Rx / Tx) may use resources provided by different network nodes (e.g., 322-1 and 322-2), which may be connected via a non-ideal backhaul (e.g., where one of the network nodes provides NR access and the other network node provides E-UTRA for LTE or NR access for 5G). In such a scenario, one network node may operate as a master node (MN) and the other node as a secondary node (SN). The MN and the SN may be connected via a network interface, and at least the MN may be connected to CN 330. In addition, at least one of the MN or the SN may operate with shared spectrum channel access, and the functionality specified for the UE 310 may be used for an integrated access and backhaul mobile terminal (IAB-MT). Similar to the UE 301, the IAB-MT may access the network using one network node or using two different nodes with an enhanced dual connectivity (EN-DC) architecture, a new air interface dual connectivity (NR-DC) architecture, etc. In some implementations, a base station (as described herein) may be an example of a network node 322.

[0033] As shown, UE 310 may also or alternatively connect to access point (AP) 316 via connection interface 318, which may include an air interface that enables UE 310 to communicatively couple with AP 316. AP 316 may include a wireless local area network (WLAN), a WLAN node, a WLAN termination point, etc. Connection 318 may include a local wireless connection, such as a connection that complies with any IEEE 702.11 protocol, and AP 316 may include a wireless fidelity router or other AP. Figure 3310 , but AP 316 may be connected to another network (e.g., the Internet) without being connected to RAN 320 or CN 330. In some scenarios, UE 310, RAN 320, and AP 316 may be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE WLAN radio level (LWIP) technology integrated with IPsec tunneling. LWA may involve UE 310 in RRC_CONNECTED state being configured by RAN 320 to utilize radio resources of LTE and WLAN. LWIP may involve UE 310 using WLAN radio resources (e.g., connection interface 318) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) transmitted via connection interface 318. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0034] The RAN 320 may include one or more RAN nodes 322-1 and 322-2 (collectively, RAN nodes 322, and individually, RAN nodes 322) that enable channels 314-1 and 314-2 to be established between the UE 310 and the RAN 320. The RAN node 322 may include a network access point configured to provide a radio baseband function for data and / or voice connections between a user and a network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, as an example, the RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, an NR base station, a next generation eNB (gNB), etc.). The RAN node 322 may include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., a ground access point). In some scenarios, the RAN node 322 may be a dedicated physical device, such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell. As described below, in some implementations, the satellite 360 ​​may operate as a base station (e.g., a RAN node 322) relative to the UE 310. Thus, references herein to a base station, a RAN node 322, etc. may relate to implementations in which the base station, the RAN node 322, etc. are terrestrial network nodes, and also to implementations in which the base station, the RAN node 322, etc. are non-terrestrial network nodes (e.g., a satellite 360).

[0035] Some or all of the RAN nodes 322 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these specific implementations, the CRAN or vBBUP may implement: RAN functional partitioning, such as a packet data convergence protocol (PDCP) partitioning, where the radio resource control (RRC) and PDCP layers may be operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities may be operated by individual RAN nodes 322; a media access control (MAC) / physical (PHY) layer partitioning, where the RRC, PDCP, radio link control (RLC), and MAC layers may be operated by the CRAN / vBBUP, and the PHY layer may be operated by individual RAN nodes 322; or a "lower PHY" partitioning, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer may be operated by the CRAN / vBBUP, and the lower portions of the PHY layer may be operated by individual RAN nodes 322. The virtualization framework may allow idle processor cores of the RAN node 322 to execute or perform other virtualized applications.

[0036] In some implementations, the separate RAN nodes 322 may represent individual gNB distributed units (DUs) connected to a gNB control unit (CU) via respective F1 interfaces. In such implementations, the gNB-DU may include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU may be operated by a server (not shown) located in the RAN 320 or by a server pool (e.g., a server group configured to share resources) in a manner similar to a CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 322 may be a next generation eNB (i.e., gNB) that may provide Evolved Global Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminals to the UE 310 and may be connected to a 5G core network (5GC) 330 via an NG interface.

[0037] Any of the RAN nodes 322 may terminate the air interface protocol and may be the first point of contact for the UE 310. In some implementations, any of the RAN nodes 322 may perform various logical functions of the RAN 320, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management. The UE 310 may be configured to communicate with each other or with any of the RAN nodes 322 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0038] In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 322 to the UE 310, and similar techniques may be used for uplink transmissions. The grid may be a time-frequency grid (e.g., a resource grid or a time-frequency resource grid) that represents the physical resources for the downlink in each time slot. Such a time-frequency plane representation is common practice for OFDM systems, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block may include a set of resource elements (REs); in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0039] In addition, the RAN node 322 may be configured to wirelessly communicate with the UE 310 and / or with each other via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"), or a combination thereof. The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz band. In some implementations (e.g., a 5G NR implementation), a first frequency range (FR1) may include a frequency band from a spectrum of 410 MHz to 7125 MHz, and a second frequency range (FR2) may include a frequency band from 24.25 GHz to 52.6 GHz. The 5 GHz band, the 6 GHz band, and a band above 52.6 GHz (e.g., a 60 GHz band) may correspond to an unlicensed spectrum, but different band configurations may correspond to licensed or unlicensed spectrum.

[0040] Licensed spectrum may correspond to channels or frequency bands that are selected, reserved, regulated, etc. for certain types of wireless activities (e.g., wireless telecommunications network activities), while unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activities. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public sector organization (e.g., a government agency, a regulatory agency, etc.) or by a private sector organization involved in developing wireless communication standards and protocols, etc.

[0041] To operate in the unlicensed spectrum, the UE 310 and the RAN node 322 may operate using license assisted access (LAA), eLAA, feLAA, standalone unlicensed, and / or NR-U mechanisms. In these implementations, the UE 310 and the RAN node 322 may perform one or more known medium sensing operations or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed in accordance with a listen-before-talk (LBT) protocol.

[0042] The LAA mechanism can be built on the carrier aggregation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier (CC). In some cases, each CC may have a different bandwidth from other CCs. In a time division duplex (TDD) system, the number of CCs and the bandwidth of each CC may be the same for DL ​​and UL. CA also includes individual service cells to provide individual CCs. The coverage of the service cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary service cell or PCell can provide a primary component carrier (PCC) for both UL and DL, and can handle RRC and non-access stratum (NAS) related activities. Other service cells are called SCells, and each SCell can provide a single secondary component carrier (SCC) for both UL and DL. SCCs can be added and removed as needed, and changing PCCs may require UE 310 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by the PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH starting positions within the same subframe.

[0043] The PDSCH may carry user data and higher layer signaling to the UE 310. A physical downlink control channel (PDCCH) may carry information about, among other things, a transport format and resource allocation related to the PDSCH channel. The PDCCH may also inform the UE 310 about transport formats, resource allocations, and hybrid automatic repeat request (HARQ) information related to uplink shared channels. Typically, downlink scheduling (e.g., allocating control and shared channel resource blocks to the UE 310-2 within the cell) may be performed on any of the RAN nodes 322 based on channel quality information fed back from any of the UEs 310. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 310.

[0044] PDCCH uses control channel elements (CCE) to convey control information, where the number of CCEs (e.g., 6, etc.) can be composed of resource element groups (REGs), where REGs are defined as physical resource blocks (PRBs) in OFDM symbols. For example, before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quaternions, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, referred to as REGs. Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) may be defined in LTE.

[0045] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREGs. In some cases, an ECCE may have other numbers of EREGs.

[0046] The RAN nodes 322 may be configured to communicate with each other via an interface 323. In a specific implementation where the system is an LTE system, the interface 323 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes 322 (e.g., two or more eNBs / gNBs or a combination thereof) connected to an evolved packet core (EPC) or CN 330, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs or gNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the master eNB (MeNB) to the secondary eNB (SeNB); information about the successful in-sequence delivery of PDCP packet data units (PDUs) from the SeNB to the UE 310 for user data; information about PDCP PDUs that are not delivered to the UE 310; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. X2-C may provide intra-LTE access mobility functions (e.g., including context transfer from the source eNB to the target eNB, user plane transmission control, etc.), load management functions, and inter-cell interference coordination functions. In a 5G system, the interface between the RAN nodes 322 may be an Xn interface, and the interface between the RAN node 322 and the CN 330 may be an NG interface.

[0047] As shown, RAN 320 may be connected (e.g., communicatively coupled) to CN 330. CN 330 may include a plurality of network elements 332 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 310) connected to CN 330 via RAN 320. In some implementations, CN 330 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. The components of CN 330 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) may be used to virtualize any or all of the above network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 330 may be referred to as a network slice, and a logical instance of a portion of CN 330 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architecture and infrastructure can be used to virtualize one or more network functions onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0048] As shown, CN 330, application server 340 and external network 350 may be connected to each other via interfaces 334, 336 and 338, which may include IP network interfaces. Application server 340 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) that provide applications (e.g., universal mobile telecommunications system packet service (UMTS PS) domain, LTE PS data services, etc.) using IP bearer resources with CM 330. Application server 340 may also or alternatively be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.)) for UE 310 via CN 330. Similarly, external network 350 may include one or more of a variety of networks, including the Internet, thereby providing network access to various additional services, information, interconnectivity and other network features for mobile communication networks and UE 310.

[0049] As shown, exemplary network 300 may include an NTN that may include one or more satellites 360-1 and 360-2 (collectively, "satellites 360"). Satellites 360 may communicate with UE 310 via a serving link or wireless interface 362 and / or communicate with RAN 320 via a feeder link or wireless interface 364 (depicted individually as 364-1 and 364). In some implementations, satellite 360 ​​may operate as a passive or transparent network relay node with respect to communications between UE 310 and a terrestrial network (e.g., RAN 320). In some implementations, satellite 360 ​​may operate as an active or regenerative network node such that satellite 360 ​​may operate as a base station to UE 310 (e.g., as a gNB of RAN 320) with respect to communications between UE 310 and RAN 320. In some implementations, the satellites 360 can communicate with each other via a direct wireless interface (e.g., 366) or an indirect wireless interface (e.g., via the RAN 320 using interfaces 364-1 and 364-2).

[0050] Additionally or alternatively, satellite 360 ​​may include a GEO satellite, a LEO satellite, or another type of satellite. Satellite 360 ​​may also or alternatively relate to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS), a global positioning system (GPS), a global navigation satellite system (GLONASS), a BeiDou satellite navigation system (BDS), etc. In some implementations, satellite 360 ​​may operate as a base station (e.g., a RAN node 322) relative to UE 310. Thus, references herein to a base station, a RAN node 322, etc. may relate to implementations in which the base station, the RAN node 322, etc. are terrestrial network nodes, as well as implementations in which the base station, the RAN node 322, etc. are non-terrestrial network nodes (e.g., satellite 360).

[0051] Figure 4 4 is a diagram of an exemplary overview 400 of initial access signaling in a wireless communication network according to one or more implementations described herein. As shown, the base station 322 may transmit to the UE 310 an indication (at 1) of whether the DBTW is enabled or disabled for the base station 322. The DBTW may correspond to one or more SCS schemes, such as 120kHz SCS, 240kHz SCS, 480kHz SCS, and 960kHz SCS. The DBTW may include a duration and / or manner in which the UE 310 may expect to receive one or more SSBs in a discovery burst from the base station 322.

[0052] The base station 322 may also provide an indication to the UE 310 of which SSBs or multiple SSB candidates in the discovery burst are active (at 2). The candidate SSBs may include the maximum number of SSBs that the base station 322 can transmit; the active SSBs may include which SSBs the base station 322 actually transmits. The base station 322 may transmit a discovery burst of SSBs to the UE 310 (at 3). And the UE 310 may use the SSBs to determine the appropriate transmission timing for communicating with the base station 322 and participate in synchronization signaling (at 4). Synchronization signaling may include receiving additional DL information and / or providing UL information from the base station 322, including performing an attachment procedure, establishing one or more connections, registering with the network, etc.

[0053] Figure 5 5 is a diagram of an example of a process 500 for initial access signaling in a wireless communication network. The process 500 may be implemented by the base station 322. In some implementations, some or all of the process 500 may be implemented by one or more other systems or devices (including Figure 3 The process 500 may be performed by one or more devices in the device, such as UE 310. In addition, the process 500 may include Figure 5 The operations shown may be fewer, additional, differently ordered, and / or arranged than those shown. In some implementations, some or all of the operations of process 500 may be performed independently, sequentially, simultaneously, etc., with one or more of the other operations of process 500. Thus, the techniques described herein are not limited to Figure 3 310. In addition, although process 500 may be described primarily from the perspective of a specific device (e.g., base station 322), the techniques described herein also include corresponding or complementary operations performed by a corresponding device (e.g., UE 310). In addition, process 500 provides a brief example of operations that can be performed using the techniques described herein. Figure 5 Additional details of the operations presented in and additional and alternative features and operations.

[0054] As shown, process 500 may include determining whether DBTW is enabled or disabled (block 510). For example, base station 322 may determine whether DBTW is enabled or disabled for transmitting SSB to UE 310. In some implementations, base station 322 may determine whether DBTW is enabled or disabled for one, more than one, or all SSB SCSs (e.g., 120kHz SCS, 240kHz SCS, 480kHz SCS, 960kHz SCS, etc.). Base station 322 may also or alternatively determine whether DBTW is enabled or disabled, whether transmission of SSB to UE 310 is enabled or disabled, etc.

[0055] Process 500 may include determining whether LBT is enabled or disabled and / or the status of a licensed band and / or an unlicensed band (block 520). For example, base station 322 may determine whether LBT is enabled or disabled for one, more than one, or all SSB SCSs. Additionally or alternatively, base station 322 may determine the status of a licensed band and / or an unlicensed band corresponding to one, more than one, or all SSB CSCs. In some implementations, whether DBTW is enabled / disabled may depend on whether LBT is enabled / disabled, and whether LBT is enabled / disabled may depend on the status of a licensed band, an unlicensed band, or a combination thereof. For example, some wireless communication networks (e.g., networks of a particular company, country, etc.) may require LBT for all communications, regardless of whether the communication is via a licensed band or an unlicensed band. In contrast, other wireless communication networks may require, enable, etc. LBT only for certain communications, which may be based on whether the communication involves a licensed band, an unlicensed band, or a combination thereof. Additionally or alternatively, some wireless communication networks may enable or disable DBTW based on whether LBT is enabled or disabled.

[0056] Process 500 may include transmitting an indication of whether DBTW is enabled or disabled, whether LBT is enabled or disabled, and / or the status of a licensed band and / or an unlicensed band (block 530). For example, base station 322 may transmit an indication of whether DBTW is enabled or disabled, whether LBT is enabled or disabled, and / or the status of a licensed band and / or an unlicensed band to UE 310. As described herein, these types of information may be indicated implicitly (e.g., based on other information) or explicitly (e.g., based on a direct indication).

[0057] In some implementations, the indication of whether DBTW is enabled or disabled can be transmitted via one or more IEs (e.g., in subCarrierSpacingCommon IE, ssb-SubcarrierOffset, or controlResourceSetZero IE) and / or MIB or SIB (e.g., SIB1). In some implementations, the indication of whether DBTW is enabled or disabled can be transmitted with another type of information (such as For example, the base station 322 may use one or more IEs to indicate whether DBTW is enabled or disabled, and the UE 310 may determine based on these IEs whether DBTW is enabled or disabled. In some implementations, the indication of whether LBT is enabled or disabled may be transmitted via a MIB or SIB (e.g., SIB1), or by the UE 310 based on The value of the parameter and the maximum number of candidate SSBs MAX SSB(e.g., 64) is implicitly derived. For example, if The parameter value is less than MAX SSB Parameters, UE 310 may determine that LBT is enabled. Alternatively, if The parameter is greater than or equal to MAX SSB parameter, UE 310 may determine that LBT is disabled.

[0058] In some implementations, the indication of the status of the licensed band and / or the unlicensed band may be indicated via a MIB, a SIB (e.g., SIB1), and / or a scrambling sequence used to scramble cyclic redundancy check (CRC) bits of a common broadcast channel (PBCH). The size of the downlink control information (DCI) (e.g., DCI format 1_0) in a common search space (CSS) may be aligned between licensed and unlicensed operations to avoid increasing the number of DB attempts for the UE 310. In some implementations, the DCI format 1_0 CSS defined for unlicensed band communications may be reused as a DCI format 1_0 CCS for both licensed and unlicensed bands for frequency range 2-2 (FR2-2) transmissions.

[0059] Process 500 may also include determining which SSBs are active for the discovery burst (block 540). For example, base station 322 may determine which SSBs of the maximum number of SSBs (e.g., candidate SSBs) may actually be transmitted to UE 310. In some implementations, the active SSBs may be based on the SCS and / or The value of the parameter. The number of active SSBs can be any of 16, 32, 48, and / or 64. For example, for a 120kHz SCS, 16 or 32 SSBs can be active, while for a 240kHz SCS, 480kHz SCS, or 960kHz SCS, any of 16, 32, 48, or 64 SSBs can be active. In this way, the techniques described herein can be used to better ensure that control frame transmissions (e.g., 120kHz SCS transmissions) are not unduly blocked by finding too many SSBs in a burst.

[0060] Process 500 may include transmitting an indication of which SSBs are active and transmitting the SSBs (block 550). For example, base station 322 may transmit information indicating which SSBs are active to UE 310. In some implementations, base station 322 may indicate which SSBs are active via an IE or field (e.g., ssb-PositionsInBurst IE, groupPresence field, inOneGroup field, etc.), which may indicate which SSB groups are active and which SSBs in each group are active. In some implementations, base station 322 may indicate which SSBs are active by providing a UE 310-based indication of which SSBs are active. The value of the parameter applies the most significant bit (MSB) method to the bitmap.

[0061] Figure 6 is used to jointly signal whether DBTW is enabled or disabled and 600 of an example of a table of values ​​for the parameter. As shown, a one-bit indication is used to jointly signal whether DBTW is enabled and For this indication, the base station 322 may use a single bit from the MIB payload, such as the subCarrierSpacingCommon IE. A value of "1" may indicate that DBTW is enabled, and based on "1", the UE 310 may determine The value of the parameter is 16 or 32 (e.g., depending on which of 16 or 32 is predefined in a specific implementation or specification). A value of "0" may indicate that DBTW is disabled, and based on "0", UE 310 may determine The value of the parameter is 64 (for example, parameter). Therefore, DBTW and Parameters can be jointly signaled, by explicitly signaling DBTW and implicitly signaling parameter's value or vice versa.

[0062] Figure 7 is used to jointly signal whether the Discovery Burst Transfer Window (DBTW) is enabled or disabled and 700 of an example of a table of parameters. As shown, a two-bit indication can be used to jointly signal whether DBTW is enabled and The base station 322 may use, for example, a single bit of the subCarrierSpacingCommon IE and a single bit (eg, MSB) of the controlResourceSetZero IE (which may correspond to the pdcch-ConfigSIB1 IE of the MIB).

[0063] A value of "0" from the subCarrierSpacingCommon IE and a value of "0" from the controlResourceSetZero IE may indicate that DBTW is enabled and The value of the parameter is 16. A value of "0" from the subCarrierSpacingCommon IE and a value of "1" from the controlResourceSetZero IE may indicate that DBTW is enabled and The value of the parameter is 32. A value of "1" from the subCarrierSpacingCommon IE and a value of "0" from the controlResourceSetZero IE may indicate that DBTW is enabled and The value of the parameter is 32. And a value of "1" from the subCarrierSpacingCommon IE and a value of "1" from the controlResourceSetZero IE may indicate that DBTW is disabled and The value of the parameter is 64 (e.g., the maximum number of SSBs that may be active in a half-frame).

[0064] Therefore, the status of DBTW and The value of the parameter may be jointly signaled using a two-bit indicator. In some implementations, the base station 322 may also or alternatively use a single bit of the subCarrierSpacingCommon IE and a single bit (e.g., the least significant bit (LSB)) from the ssb-SubcarrierOffset IE or a reserved bit of the MIB payload for the two-bit indication. The parameter value can be 8, 16, 32, 64, instead of Figure 7 16, 32, 48 and 64 shown.

[0065] Figure 8 8 is a diagram of an example 800 of a monitoring opportunity (MO) based on whether an indication is provided as to whether DBTW is enabled or disabled. In some implementations, whether DBTW is enabled or disabled may be explicitly indicated in a SIB (such as SIB1). Additional information may be provided in the SIB for transmissions corresponding to frequency range 2-2 (FR2-2). For example, The value of the parameter may also or alternatively be provided in the SIB. In some implementations, the SIB may be used to indicate when there are no available bits in the MIB payload, when available or introduced. When the number of parameter values ​​is greater than the number that can be accommodated in the MIB payload, etc. The value of the parameter.

[0066] In some implementations, when, for example, the MIB payload does not have two bits to indicate DBTW and When both parameters are The four values ​​of the parameter (e.g., 16, 32, 48, and 64) may be predefined by a communication standard (e.g., a 3rd Generation Partnership Project (3GPP) standard). In such implementations, UE 310 may assume that DBTW is enabled. UE 310 may also use The minimum value (e.g., 16) in the predefined set of parameters is used to monitor Type 0-PDCCH to obtain SIB. Figure 8 As shown, example 800 may be provided assuming that the system is operating in a licensed band, where DBTW is disabled, and The parameter is predefined as one of 16, 32, 48, and 64. In such a scenario, UE 310 may assume The value of the parameter is 16 (e.g., the minimum value in the predefined set) for Type0-PDCCH monitoring, and thus only the MO of slot 2 is monitored for SIBs (at 810), and additional MOs are not monitored (at 820, 830, and 840). Type0-PDCCH monitoring may include monitoring a common search space, which may be a subset of the NR PDCCH search space used to transmit PDCCHs for SIBs (such as SIB1).

[0067] The base station 322 may also or alternatively use the SIB to provide an explicit indication of whether LBT is enabled or disabled. In other implementations, the base station 322 may implicitly indicate to the UE 310 whether LBT is enabled or disabled, so that the UE 310 can derive the status of LBT based on other information. In some implementations, the UE 310 may provide an explicit indication of whether LBT is enabled or disabled based on the SIB. Parameters and MAX SSB Parameter to export whether LBT is enabled / disabled. MAX SSB The parameter may indicate the maximum number of SSBs that can be transmitted in a discovery burst, which may be different from the number of SSBs actually transmitted. The parameter is less than MAX SSB parameter (e.g., 64), UE 310 may determine that LBT is enabled. Alternatively, if The parameter is greater than or equal to MAX SSB parameter (e.g., 64), the UE 310 may determine that LBT is disabled.

[0068] The base station 322 may also or alternatively use the SIB to provide an indication of a licensed band or an unlicensed band. In other specific implementations, the base station 322 may use the MIB to provide an indication of a licensed band or an unlicensed band. For example, a reserved bit of the MIB, a bit of the subCarrierSpacingCommon IE, etc. may be used. In other specific implementations, a scrambling sequence may be used to indicate a licensed band or an unlicensed band.

[0069] Fig. 9 900 is a diagram of an example of a table 900 for indicating a licensed band or an unlicensed band based on a scrambling sequence. As shown, the value of a bit (e.g., b(0)) can be mapped to one of two scrambling sequences (e.g., [W0, W1, W2, ..., W 23 ]). The possible values ​​(0 and 1) of the bit may indicate (e.g., be predefined to indicate) a licensed band or an unlicensed band, respectively. Thus, the base station 322 may select one of the scrambling sequences and use the selected scrambling sequence to scramble the CRC bits of the PBCH. Additionally, the UE 310 may determine which scrambling sequence has been used and determine whether a licensed band or an unlicensed band is applicable or indicated. Thus, in addition to the MIB or SIB, the scrambling sequence may also be used to indicate a licensed band or an unlicensed band.

[0070] Figures 10 to 12 1 is a diagram of examples 1000, 1100, and 1200 for indicating active SSBs and / or active SSB groups for DBTW. As shown, examples 1000, 1100, and 1200 may each include an inOneGroup field and a groupPresence field. Each field may include 8 bits ranging from LSB to MSB (b7, b6, b5, b4, b3, b2, b1, b0 and g7, g6, g5, g4, g3, g2, g1, g0).

[0071] As described herein, the base station 322 may use SIB1 to broadcast information about SSB transmissions within an SSB burst. For example, for frequency range 2-1 (FR2-1), 64 SSBs may be divided into 8 groups of 8 SSBs. SIB1 may include an inOneGroup field, which may include a bit string indicating which SSB within a group of SSBs is actually transmitted (or active). SIB1 may also include a groupPresence field, which includes a bit string indicating which SSB groups are active.

[0072] The presence of the groupPresence field in SIB1 may vary depending on the carrier frequency. For carrier frequencies less than 24 GHz, the groupPresence field does not exist. In other words, the groupPresence field only exists in frequency bands above 24 GHz (i.e., FR2). When the carrier frequency is higher than 24 GHz, an 8-bit groupPresence field may be used. The first leftmost bit may correspond to SSBs with index values ​​0-7, the second bit may correspond to SSBs with index values ​​8-15, and so on. A value of 0 in the bitmap may indicate that the SS / PBCH block (e.g., SSB) is not transmitted according to the inOneGroup field. A value of 1 in the bitmap may indicate that the SS / PBCH block (e.g., SSB) is transmitted according to the inOneGroup field.

[0073] Dedicated signaling may be used to indicate which SSBs are active. Different bitmap lengths may be supported for different frequency ranges. In some implementations, the bitmap of the ssb-PositionsInBurst field (for FR2-2) may have a length of 64 bits, regardless of the corresponding SIB1 may include the ssb-PositionsInBurst IE, which may include the inOneGroup field and the groupPresence field. In some implementations, a 64-bit bitmap may be used. The MSB indicates which SSB is active. For example, when When MSB(k) is greater than or equal to 1, UE 310 may determine that the SS / PBCH block SSB within the DBTW may be transmitted, where the candidate SSB index corresponds to a value equal to The SSB index of the MSB is minus 1 (e.g., k-1); and if If the MSB(k) is set to 0, the UE 310 may determine that the SSB is not transmitted. In addition, the UE 310 may expect or anticipate that 64 minus 64 in the 64-bit bitmap. The LSB is set to 0.

[0074] Examples 1000, 1100, and 1200 may include the following scenarios in which information is provided about when an indication An indication of which SSBs are actually transmitted when the number of SSBs transmitted is less than the maximum number of SSBs supported (e.g., 64). Referring to example 1000, MSB(k) may be equal to Divided by 8, the MSB of the groupPresence field in SIB1 can be used to indicate which SSB group is active. When k is equal to 32, k may be equal to the 4 MSBs (7-4) of the groupPresence field. In such a scenario, the 4 LSBs (3-0) of the groupPresence field may be reserved or unused, and the inOneGroup field may indicate which SSBs within a group of SSBs are actually transmitted.

[0075] In contrast, examples 1100 and 1200 may provide a more dependent For example, referring to example 1100, when When the bitmap is less than or equal to 16, the 8-bit string of the inOneGroup field and the groupPresence field can be aggregated or concatenated into a 16-bit string, which can be used to indicate which SSBs are active (without performing SSB grouping). The UE 310 can determine which SSBs are transmitted by the base station 322 based on the concatenated bitmap. Now referring to example 1200, when When greater than 16, the 8-bit string of the groupPresence field can be used to indicate which groups are active without change, and the inOneGroup field can be used to indicate which SSBs within the group are active, where the MSBs(k) can be equal to Divide by 8. Transmitting this information by base station 322 (as described in Examples 10-12) may better enable UE 310 to monitor the discovery burst transmission of the SSB to synchronize with base station 322.

[0076] Fig.13 1300 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 1300 may include at least an application circuit 1302, a baseband circuit 1304, an RF circuit 1306, a front-end module (FEM) circuit 1308, one or more antennas 1310, and a power management circuit (PMC) 1312 coupled together as shown. The components of the illustrated device 1300 may be included in a UE or a RAN node. In some implementations, the device 1300 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1302, but may include a processor / controller to process IP data received from a CN such as a 5GC or an evolved packet core (EPC)). In some implementations, the device 1300 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 1300, etc.) or an input / output (I / O) interface. In other implementations, the components described below may be included in more than one device (eg, the circuitry may be included solely in more than one device for a Cloud-RAN (C-RAN) implementation).

[0077] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 1300. In some specific implementations, the processor of the application circuit 1302 may process IP data packets received from the EPC.

[0078] The baseband circuit 1304 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1304 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 1306 and generate baseband signals for the transmit signal path of the RF circuit 1306. The baseband circuit 1304 may interact with the application circuit 1302 to generate and process baseband signals and control the operation of the RF circuit 1306. For example, in some specific implementations, the baseband circuit 1304 may include a 3G baseband processor 1304A, a 4G baseband processor 1304B, a 5G baseband processor 1304C, or other baseband processors 1304D for other existing generations, generations under development, or generations to be developed in the future (e.g., 2G, 6G, etc.). The baseband circuit 1304 (e.g., one or more baseband processors 1304A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 1306. In other implementations, some or all of the functionality of the baseband processors 1304A-D may be included in a module stored in the memory 1304G and executed via the central processing unit (CPU) 1304E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, the modulation / demodulation circuitry of the baseband circuitry 1304 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some implementations, the encoding / decoding circuitry of the baseband circuitry 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other aspects.

[0079] In some implementations, the baseband circuitry 1304 may include one or more audio digital signal processors (DSPs) 1304F. The audio DSP 1304F may include elements for compression / decompression and echo cancellation, and in other implementations may include other suitable processing elements. In some implementations, the components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some implementations, some or all of the components of the baseband circuitry 1304 and the application circuitry 1302 may be implemented together, such as, for example, on a system on a chip (SOC).

[0080] In some implementations, the baseband circuitry 1304 may provide communications compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 1304 may support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Implementations in which the baseband circuitry 1304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0081] RF circuit 1306 may communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various specific implementations, RF circuit 1306 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1306 may include a receive signal path, which may include circuits that down-convert RF signals received from FEM circuit 1308 and provide baseband signals to baseband circuit 1304. RF circuit 1306 may also include a transmit signal path, which may include circuits that up-convert baseband signals provided by baseband circuit 1304 and provide RF output signals to FEM circuit 1308 for transmission.

[0082] In some implementations, the receive signal path of the RF circuit 1306 may include a mixer circuit 1306A, an amplifier circuit 1306B, and a filter circuit 1306C. In some implementations, the transmit signal path of the RF circuit 1306 may include a filter circuit 1306C and the mixer circuit 1306A. The RF circuit 1306 may also include a synthesizer circuit 1306D for synthesizing the frequencies used by the mixer circuit 1306A of the receive signal path and the transmit signal path. In some implementations, the mixer circuit 1306A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1308 based on the synthesized frequency provided by the synthesizer circuit 1306D. The amplifier circuit 1306B may be configured to amplify the down-converted signal, and the filter circuit 1306C may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 1304 for further processing. In some implementations, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some implementations, the mixer circuit 1306A of the receive signal path may include a passive mixer, but the scope of the implementation is not limited in this respect.

[0083] In some implementations, the mixer circuit 1306A of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 1306D to generate an RF output signal for the FEM circuit 1308. The baseband signal can be provided by the baseband circuit 1304 and can be filtered by the filter circuit 1306C.

[0084] In some implementations, the mixer circuit 1306A of the receive signal path and the mixer circuit 1306A of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some implementations, the mixer circuit 1306A of the receive signal path and the mixer circuit 1306A of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some implementations, the mixer circuit 1306A of the receive signal path and the mixer circuit '1306A may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 1306A of the receive signal path and the mixer circuit 1306A of the transmit signal path may be configured for superheterodyne operation.

[0085] In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the implementation is not limited in this respect. In some alternative implementations, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative implementations, the RF circuit 1306 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1304 may include a digital baseband interface to communicate with the RF circuit 1306.

[0086] In some dual-mode implementations, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the implementations is not limited in this respect.

[0087] In some implementations, the synthesizer circuit 1306D can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, the synthesizer circuit 1306D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0088] The synthesizer circuit 1306D can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1306A of the RF circuit 1306. In some implementations, the synthesizer circuit 1306D can be a fractional-N / N+1 synthesizer.

[0089] In some implementations, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 1304 or the application circuit 1302 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1302.

[0090] The synthesizer circuit 1306D of the RF circuit 1306 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some implementations, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry output) to provide a fractional frequency division ratio. In some exemplary implementations, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these implementations, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0091] In some implementations, the synthesizer circuit 1306D can be configured to generate a carrier frequency as an output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some implementations, the output frequency can be an LO frequency (fLO). In some implementations, the RF circuit 1306 can include an IQ / polarity converter.

[0092] The FEM circuitry 1308 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1310, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1306 for further processing. The FEM circuitry 1308 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 1306 for transmission via one or more of the one or more antennas 1310. In various implementations, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 1306, only in the FEM circuitry 1308, or in both the RF circuitry 1306 and the FEM circuitry 1308.

[0093] In some implementations, the FEM circuit 1308 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1306). The transmit signal path of the FEM circuit 1308 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1306); and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 1310).

[0094] In some implementations, the PMC 1312 can manage the power provided to the baseband circuit 1304. Specifically, the PMC 1312 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1300 is capable of being powered by a battery, for example, when the device is included in a UE, the PMC 1312 can generally be included. The PMC 1312 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0095] Although Fig.13The PMC 1312 is shown coupled only to the baseband circuit 1304. However, in other implementations, the PMC 1312 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 1302, the RF circuit 1306, or the FEM circuit 1308) and perform similar power management operations.

[0096] In some implementations, the PMC 1312 can control or otherwise be part of various power saving mechanisms of the device 1300. For example, if the device 1300 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 1300 can be powered off for short time intervals, thereby saving power.

[0097] If there is no data traffic activity for an extended period of time, the device 1300 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1300 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 1300 may not receive data in this state; in order to receive data, it may transition back to the RRC_Connected state.

[0098] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0099] The processor of the application circuit 1302 and the processor of the baseband circuit 1304 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1304 can be used alone or in combination to perform the functions of layer 3, layer 2, or layer 1, and the processor of the baseband circuit 1304 can utilize data received from these layers (e.g., packet data) and further perform the functions of layer 4 (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layer). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0100] Fig.14is a diagram of an exemplary interface of a baseband circuit according to one or more specific implementations described herein. As discussed above, Fig.13 The baseband circuit 1304 may include processors 1304A-1304E and a memory 1304G utilized by the processors. Each of the processors 1304A-1304E may include a memory interface 1404A-1404E, respectively, for sending / receiving data to / from the memory 1304G.

[0101] The baseband circuit 1304 may also include: one or more interfaces to communicate with other circuits / devices, such as a memory interface 1412 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1304); an application circuit interface 1414 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1304); Fig.13 RF circuit interface 1416 (for example, for sending / receiving data to / from the application circuit 1302); Fig.13 an interface for sending / receiving data to / from a RF circuit 1306); a wireless hardware connection interface 1418 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 1420 (for example, an interface for sending / receiving power or control signals to / from PMC 1312).

[0102] Examples herein may include subject matter such as methods, components for performing actions or blocks of the methods, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with a memory (e.g., a processor, etc.), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described specific implementations and examples.

[0103] In embodiment 1, the embodiment may also include one or more embodiments of the embodiments described herein, and a base station may include: a memory; and one or more processors, wherein the one or more processors are configured to, when executing instructions stored in the memory, enable the base station to: determine whether a discovery burst transmission window (DBTW) is enabled or disabled for the base station, the DBTW including a duration for transmitting multiple synchronization signal blocks (SSBs); transmit an indication to a user equipment (UE) of whether the DBTW is enabled or disabled; and when the DBTW is enabled, transmit the multiple SSBs to the UE according to the DBTW.

[0104] In embodiment 2, the embodiment may also include one or more of the embodiments described herein, wherein the indication of whether the DBTW is enabled or disabled is related to The parameters are signaled jointly so that the The value of the parameter is based on whether the DBTW is enabled or disabled. In embodiment 3, the embodiment may also include one or more of the embodiments described herein, the indication of whether the DBTW is enabled or disabled includes a one-bit indication of the subCarrierSpacingCommon information element (IE) of the master information block (MIB), and the The value of the parameter is based on the one-bit indication. In embodiment 4, the embodiment may also include one or more of the embodiments described herein, the indication of whether the DBTW is enabled or disabled includes a two-bit indication, and a combination of different values ​​of the two-bit indication is configured or predefined in the specification to indicate: one of four predefined values ​​of the N_SSB^QCL parameter, and whether the DBTW is enabled or disabled.

[0105] In embodiment 5, the embodiment may also include one or more embodiments of the embodiments described herein, wherein the four predefined values ​​of one of the four predefined values ​​include 16, 32, 48 and 64. In embodiment 6, the embodiment may also include one or more embodiments of the embodiments described herein, wherein the first bit of the two-bit indication includes the subCarrierSpacingCommon IE, and the second bit of the two-bit indication includes one of the following items: the least significant bit (LSB) of the ssb-SubcarrierOffset IE, the most significant bit (MSB) of the controlResourceSetZero IE, or a reserved bit of the master information block (MIB). In embodiment 7, the embodiment may also include one or more embodiments of the embodiments described herein, using a system information block (SIB) to explicitly provide an indication of whether the DBTW is enabled or disabled. In embodiment 8, the embodiment may also include one or more embodiments of the embodiments described herein, using the SIB to indicate Parameters, The parameter includes one of four predefined values, including 16, 32, 48, and 64, and wherein the indication of whether the DBTW is enabled or disabled and the Parameters are configured to indicate to the UE a monitoring occasion (MO) of a common search space (CSS) for system information block (SIB) reception after receiving the indication of whether the DBTW is enabled or disabled.

[0106] In embodiment 9, the embodiment may also include one or more embodiments described herein, and the one or more processors are further configured to: transmit to the UE an indication of whether listen before talk (LBT) is enabled or disabled. In embodiment 10, the embodiment may also include one or more embodiments described herein, using the SIB to The value of the parameter and the maximum number of SSBs supported (MAX SSB ) parameter to implicitly indicate whether LBT is enabled or disabled. In embodiment 11, the embodiment may also include one or more embodiments of the embodiments described herein, and the SIB is configured to indicate a licensed radio spectrum signal or an unlicensed radio spectrum signal. In embodiment 12, the embodiment may also include one or more embodiments of the embodiments described herein, and the indication of whether LBT is enabled or disabled for unlicensed radio spectrum signals is explicitly provided via the subCarrierSpacingCommon field of the MIB. In embodiment 13, the embodiment may also include one or more embodiments of the embodiments described herein, and whether LBT is enabled or disabled is indicated by selecting a scrambling sequence from two predefined scrambling sequences to scramble the cyclic redundancy check (CRC) bits of the common broadcast channel (PBCH).

[0107] In embodiment 14, the embodiment may also include one or more of the embodiments described herein, wherein the one or more processors are further configured to: transmit information about which SSBs of the plurality of SSBs are active within the SSB burst based on a frequency range used to transmit the SSB. In embodiment 15, the embodiment may also include one or more of the embodiments described herein, wherein the one or more processors are further configured to: determine the number of active SSBs; and when the number of active SSBs is less than the maximum number of active SSBs, based on In embodiment 16, the embodiment may also include one or more embodiments described herein, wherein which of the multiple SSBs are active is indicated via the MSB number of a 64-bit bitmap information element (IE) in a dedicated radio resource control (RRC) signal for the UE, and the MSB number is determined as The value of the parameter.

[0108] In embodiment 17, the embodiment may also include one or more embodiments described herein, wherein which of the multiple SSBs are active is indicated via the number of MSBs of the 8-bit bitmap groupPresence field in SIB1, and the number of MSBs is based on The value of the parameter is determined by dividing by 8. In embodiment 18, the embodiment may also include one or more embodiments described herein, when When the value of the parameter is less than or equal to 16, which of the multiple SSBs are active is indicated using a bitmap via the concatenation of 8 bits of the inOneGroup field and 8 bits of the groupPresence field in SIB1. In embodiment 19, the embodiment may also include one or more embodiments described herein, when the When the parameter is greater than 16, which of the multiple SSBs are active is indicated by: the 8 bits of the groupPresence field in SIB1, indicating that at least one SSB group is active; and the MSB of the 8 bits of the inOneGroup field in SIB1, indicating an active SSB within the at least one SSB group, and the MSB of the 8 bits of the inOneGroup field is based on the The parameter value is determined by dividing it by 8.

[0109] In embodiment 20, the embodiment may also include one or more embodiments of the embodiments described herein, and a user equipment (UE) may include: a memory; and one or more processors, wherein the one or more processors are configured to, when executing instructions stored in the memory, enable the UE to: receive an indication of whether a discovery burst transmission window (DBTW) is enabled or disabled for a base station of a wireless communication network, wherein the DBTW includes transmission of multiple synchronization signal blocks (SSBs); and when the DBTW is enabled, receive at least one of the multiple SSBs from the base station according to the DBTW; and synchronize signaling with the base station based on the at least one SSB.

[0110] In embodiment 21, the embodiment may also include one or more embodiments of the embodiments described herein, and a baseband processor of a base station may include a circuit, which is configured to: determine whether a discovery burst transmission window (DBTW) is enabled or disabled for the base station, the DBTW including a duration for transmitting multiple synchronization signal blocks (SSBs); transmit an indication to a user equipment (UE) whether the DBTW is enabled or disabled; and when the DBTW is enabled, transmit the multiple SSBs to the UE according to the DBTW.

[0111] In embodiment 22, the embodiment may also include one or more embodiments of the embodiments described herein, and a baseband processor of a UE may include a circuit, which is configured to: receive an indication of whether a discovery burst transmission window (DBTW) is enabled or disabled for a base station of a wireless communication network, and the DBTW includes the transmission of multiple synchronization signal blocks (SSBs); and when the DBTW is enabled, receive at least one SSB of the multiple SSBs from the base station according to the DBTW; and synchronize signaling with the base station based on the at least one SSB.

[0112] The above description of illustrative examples, implementations, aspects, etc. of the subject disclosure (including what is described in the Abstract) is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific examples, implementations, aspects, etc. are described herein for illustrative purposes, various modifications are contemplated within the scope of such examples, implementations, aspects, etc., as can be appreciated by those skilled in the relevant art.

[0113] In this regard, although the subject matter disclosed in the present invention has been described in conjunction with various examples, implementations, aspects, etc. and corresponding figures, it should be understood that other similar aspects may be used or modifications and additions may be made to the disclosed subject matter, where applicable, to perform the same, similar, alternative or alternative functions of the subject matter without departing from the subject matter. Therefore, the disclosed subject matter should not be limited to any single example, implementation or aspect described herein, but should be interpreted in accordance with the breadth and scope of the following claims.

[0114] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified functions of the components (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a plurality of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

[0115] As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" used in the present application and the appended claims should generally be interpreted as meaning "one or more" unless otherwise specified or clear from the context to be directed to the singular form. In addition, to the extent that the terms "including", "comprising", "having", "having", "with", or variations thereof are used in the detailed description and claims, such terms are intended to be included in a manner similar to the term "comprising". In addition, where one or more numbered items (e.g., "first X", "second X", etc.) are discussed, generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0116] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A baseband processor, comprising: a memory configured to store instructions; as well as One or more processors, which, when executing the instructions, are configured to: Transmit the time domain positions of a plurality of transmitted synchronization signal blocks (SSBs) within a SSB burst; as well as performing synchronization using the plurality of transmitted SSBs, Wherein the time domain positions of the plurality of transmitted SSBs are indicated by a first bitmap indicating at least one transmitted SSB group and a second bitmap indicating the time domain positions of the plurality of transmitted SSBs in the at least one SSB group.

2. The baseband processor of claim 1 , wherein the one or more processors are further configured to: A maximum number of transmitted SSBs within the SSB burst is transmitted, wherein the number of the plurality of transmitted SSBs is less than the maximum number of transmitted SSBs.

3. The baseband processor of claim 2, wherein the maximum number of transmitted SSBs is determined based on an operating frequency range and based on an operating status of a licensed band and / or an unlicensed band.

4. The baseband processor of claim 3, wherein the one or more processors are further configured to: A discovery burst transmission window (DBTW) is determined for the operating state of the unlicensed frequency band, wherein the plurality of transmitted SSBs are within the DBTW.

5. The baseband processor of claim 4, wherein the indication of the DBTW is signaled jointly with the maximum number of transmitted SSBs.

6. The baseband processor of claim 2, wherein subcarrier spacing (SCS) information is mapped to a value of the maximum number of transmitted SSBs.

7. The baseband processor of claim 1, wherein the first bitmap is included in a groupPresence field and the second bitmap is included in an inOneGroup field, and wherein both the groupPresence field and the inOneGroup field are included in an SSB position field of a serving cell configuration, wherein the serving cell configuration is included in SIB1.

8. The baseband processor of claim 1, wherein the first bitmap and the second bitmap each have 8 bits and are used starting from a most significant bit (MSB).

9. The baseband processor of claim 1, wherein the time domain positions of the plurality of transmitted SSBs are indicated by a number of MSBs of the first bitmap, the number of MSBs of the first bitmap being determined based on a maximum number of transmitted SSBs within the SSB burst.

10. The baseband processor of claim 1, wherein the time domain positions of the plurality of transmitted SSBs are indicated by a number of MSBs of the first bitmap, the number of MSBs of the first bitmap being determined based on a maximum number of transmitted SSBs within the SSB burst divided by 8.

11. The baseband processor according to claim 1, wherein: When the maximum number of transmitted SSBs within the SSB burst is less than or equal to 16, the time domain positions of the multiple transmitted SSBs are indicated using a concatenated bitmap of 8 bits of the first bitmap and 8 bits of the second bitmap.

12. The baseband processor of claim 1, wherein: When the maximum number of transmitted SSBs in the SSB burst is greater than 16, The time domain positions of the plurality of transmitted SSBs are indicated via the MSB numbers of the 8 bits of the first bitmap and the 8 bits of the second bitmap.

13. A user equipment (UE), comprising: Memory; as well as one or more processors, wherein the one or more processors are configured to, when executing instructions stored in the memory, cause the UE to: receiving, from a base station of a wireless communication network, an indication of a time domain location of a plurality of transmitted synchronization signal blocks (SSBs) within a burst of SSBs; receiving the plurality of transmitted SSBs from the base station; as well as performing synchronization with the base station based on the plurality of transmitted SSBs, The time domain positions of the multiple transmitted SSBs are indicated by the SSB position field of the serving cell configuration included in the system information block type 1 (SIB1).

14. The UE of claim 13, wherein the one or more processors are further configured to cause the UE to: receiving a maximum number of transmitted SSBs within the SSB burst from the base station, wherein the number of the plurality of transmitted SSBs is less than the maximum number of transmitted SSBs, Wherein the maximum number of transmitted SSBs is determined based on an operating frequency range and an operating status based on a licensed frequency band and / or an unlicensed frequency band.

15. The UE of claim 14, wherein the one or more processors are further configured to cause the UE to: A discovery burst transmission window (DBTW) is received from the base station for the operating state of the unlicensed band, wherein the plurality of transmitted SSBs are within the DBTW.

16. The UE of claim 15, wherein the indication of the DBTW is signaled jointly with an indication of the maximum number of transmitted SSBs and subcarrier spacing (SCS) information.

17. The UE of claim 13, wherein the SSB position field comprises a first bitmap indicating at least one transmitted SSB group, and a second bitmap indicating a transmitted SSB within the at least one SSB group.

18. The UE of claim 17, wherein the first bitmap is included in a groupPresence field, and the second bitmap is included in an inOneGroup field, and wherein the groupPresence field and the inOneGroup field each have 8 bits and are used starting from a most significant bit (MSB).

19. The UE of claim 17, wherein the time domain positions of the plurality of transmitted SSBs are indicated by a number of MSBs of the second bitmap, the number of MSBs of the second bitmap being determined based on a maximum number of transmitted SSBs within the SSB burst.

20. A method comprising: receiving, from a base station of a wireless communication network, an indication of a time domain location of a plurality of transmitted synchronization signal blocks (SSBs) within a burst of SSBs; receiving the plurality of transmitted SSBs from the base station; as well as performing synchronization with the base station based on the plurality of transmitted SSBs, Wherein the time domain positions of the plurality of transmitted SSBs are indicated by a first bitmap indicating at least one transmitted SSB group and a second bitmap indicating the time domain positions of the plurality of transmitted SSBs in at least one SSB group.