SSB transmission mechanism in NR-U
By introducing SSB transmission timing configuration and flexible indexing order in NR-U, the problem of unreliable SSB transmission in NR-U is solved, ensuring that the UE can reliably detect SSB and achieve synchronization and information acquisition.
Patent Information
- Application Number
- CN202411347945.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-05-10
- Filing Date
- 2019-05-09
- Publication Date
- 2024-11-15
AI Technical Summary
In NR-U, base stations (gNBs) may experience unreliable transmission of synchronization signals and physical broadcast channels (SSBs) due to the unavailability of unlicensed spectrum, affecting user equipment (UE) synchronization and information acquisition.
By introducing SSB Transmission Timing Configuration (STTC) in NR-U, SSBs are transmitted after a successful Listen-Before-Speak (LBT) test. This is combined with LBT checks and channel availability determination, and the ability to slide or shift the SSB transmission position within the STTC, using a flexible indexing order and opportunistic transmission mechanism to improve SSB reliability.
This improves the transmission reliability of SSBs, ensuring that UEs can reliably detect SSBs and enabling synchronization and information acquisition in unlicensed spectrum.
Smart Images

Figure CN118972971A_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with application date of May 9, 2019, application number 201980031509.3, and invention name “SSB sending mechanism in NR-U”.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims the benefit of priority to U.S. Provisional Application No. 62 / 669,613, filed on May 20, 2018, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0004] The present application is directed to a mechanism for sending synchronization signals and physical broadcast channel (SSB) in new radio unlicensed (NR-U). Background Art
[0005] In NR, SSB carries essential signals and information such as the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS) and Physical Broadcast Channel (PBCH). These are used by the UE to acquire synchronization and the Master Information Block (MIB) in both the initial cell search and connected state. If the UE cannot detect the SSB, then the UE will have serious problems and will not be able to operate in the NR system.
[0006] In NR-U, the gNB may not be able to send SSB burst sets at predefined / configured locations. This may be due to LBT failure (channel unavailable). This causes problems for UE to detect SSB.
[0007] What is desired in the art is a mechanism for improving the reliability of SSB transmission in NR-U. Summary of the invention
[0008] This summary is provided to introduce selected concepts in a simplified form, which are further described in the detailed description below. This summary is not intended to limit the scope of the claimed subject matter. This application for a SSB transmission mechanism in NR-U largely satisfies the aforementioned needs.
[0009] One aspect of the present application is directed to an apparatus including a non-transitory memory including instructions stored thereon for monitoring SSBs from a network node. The apparatus also includes a processor operably coupled to the non-transitory memory and configured to execute a set of instructions. The instructions include configuring the device for an SSB transmission timing configuration (STTC). The instructions also include monitoring the STTC for the SSB. The instructions further include determining a first SSB in a first time slot of a subframe in a scheduled SSB transmission in the STTC that has been sent at a first scheduling position, wherein the transmission of the first SSB is based on a successful listen-before-talk (LBT) confirmation of an available channel before the scheduled SSB transmission in the STTC.
[0010] Another aspect of the present application is directed to an apparatus including a non-transitory memory including instructions stored thereon for sending an SSB. The apparatus also includes a processor operably coupled to the non-transitory memory and configured to execute a set of instructions. The instructions include performing an LBT check on a channel. The instructions also include determining availability of the channel based on the LBT check, wherein the availability is established in a first time slot of a subframe prior to the scheduled SSB transmission in an STTC at a first scheduling position. The instructions further include sending a first SSB in a first time slot during the scheduled SSB transmission in the STTC at the first scheduling position.
[0011] There has thus been outlined, rather broadly, certain embodiments of the invention in order that the detailed description thereof may be better understood, and in order that the present contribution to the art may be better appreciated. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to promote a more robust understanding of the present application, reference is now made to the accompanying drawings, in which like elements are referenced with like reference numerals. These drawings should not be construed as limiting the present application, but are intended to be exemplary only.
[0013] Figure 1A An exemplary communication system according to an embodiment of the present application is shown.
[0014] Figure 1B An exemplary device configured for wireless communication according to an embodiment of the present application is shown.
[0015] Figure 1C A system diagram showing a radio access network and a core network according to an embodiment of the present application is shown.
[0016] Figure 1D A system diagram showing a radio access network and a core network according to another embodiment of the present application.
[0017] Figure 1EA system diagram showing a radio access network and a core network according to yet another embodiment of the present application.
[0018] Figure 1F The embodiment according to the present application is shown in FIG. Figure 1A , 1C , 1D, and 1E are block diagrams of exemplary computing systems that communicate with one or more networks.
[0019] Figures 2A-2D Shown is the LAA deployment scenario.
[0020] Figure 3A -B shows the SSB transmitted via a subset of SSB bursts in NR-U.
[0021] Figure 4 An STTC according to one aspect of the present application is shown.
[0022] Figure 5 Shown is bonded SSB transmission at predefined / configured locations according to one aspect of the present application.
[0023] Figure 6 A bonded SSB transmission sliding in STTC according to one aspect of the present application is shown.
[0024] Figure 7 A reserved signal assisted bonded SSB transmission sliding in STTC according to one aspect of the present application is shown.
[0025] Figure 8 A bonded SSB transmission with sliding one SSB position in the STTC according to one aspect of the present application is shown.
[0026] Fig. 9 SSB transmission repeated in the frequency domain according to one aspect of the present application is shown.
[0027] Fig.10 An RMSI CORESET is shown being FDMed with SSB in the same time slot according to one aspect of the present application.
[0028] Fig.11 An RMSICORESET is shown being TDMed and FDMed with SSB in the same time slot according to one aspect of the present application.
[0029] Fig.12 The process of monitoring and receiving bound SSB transmissions in NR-U according to one aspect of the present application is shown.
[0030] Fig.13 An unbound SSB transmission according to one aspect of the present application is shown.
[0031] Fig.14 An unbound SSB transmission utilizing opportunistic transmission within an STTC according to one aspect of the present application is shown.
[0032] Fig.15 An unbound SSB transmission utilizing a configuration opportunity transmission according to one aspect of the present application is shown.
[0033] Fig.16 An unbound SSB transmission utilizing STTC and configuration opportunity transmission according to one aspect of the present application is shown.
[0034] Fig.17 A process for monitoring and receiving opportunistically transmitted SSB transmissions in NR-U according to one aspect of the present application is shown.
[0035] Fig.18 SSB transmission using a dedicated STTC according to one aspect of the present application is shown.
[0036] Fig.19 A process for monitoring and receiving dedicated SSB transmissions utilizing STTC according to one aspect of the present application is shown.
[0037] Fig. 20 SSB transmission using a flexible index order according to one aspect of the present application is shown.
[0038] Fig.21 A process of monitoring and receiving SSB transmissions utilizing a flexible index order according to one aspect of the present application is shown.
[0039] Fig.22A -C shows the impact of SSB shift on RACH resources according to one aspect of the present application.
[0040] Fig.23 The effect of SSB shifting on FDMed resources according to one aspect of the present application is shown. DETAILED DESCRIPTION
[0041] The detailed description of the exemplary embodiments will be discussed with reference to various figures, embodiments and aspects herein. Although the description provides detailed examples of possible implementations, it should be understood that these details are intended to be examples and therefore do not limit the scope of the present application.
[0042] References in this specification to "one embodiment," "an embodiment," "one or more embodiments," "an aspect," etc., mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the present disclosure. Furthermore, the term "embodiment" in various places in the specification does not necessarily refer to the same embodiment. That is, various features described may be exhibited by some embodiments and not by other embodiments.
[0043] According to one aspect of the present application, a mechanism and process for gNB to send SSB in NR-U is contemplated. In another aspect of the present application, a mechanism and process for UE to detect SSB in NR-U is contemplated. In one embodiment, several SSB transmissions can be bundled together. If the bundle cannot be sent at the configured position due to LBT failure, the bundle can be shifted within the configured transmission window.
[0044] In another embodiment, beam-based LBT can be performed for each SSB. The SSB for which LBT succeeds will be transmitted. For failed LBT, the gNB can perform another round of LBT to determine whether the related SSB can be transmitted.
[0045] In yet another embodiment, the SSB transmissions may be performed continuously (ie, one after another). A window is applied to each SSB transmission to improve reliability.
[0046] In yet another embodiment, the order of indexes carried by the SSBs may be flexible. The SSBs may be transmitted at any SSB position within an SSB burst transmission through successful beam-based LBT.
[0047] It is further contemplated in the present application that the gNB may indicate the offset of the SSB shift to the UE through one of the following exemplary schemes:
[0048] (i) Payload via PBCH;
[0049] (ii) via PBCH DMRS;
[0050] (iii) Combining the PBCH payload and the PBCH DMRS;
[0051] (iv) by spreading code; and
[0052] (v) Through RMSI.
[0053] Definitions and Acronyms
[0054] Provided below in Table 1 are definitions of terms and phrases commonly used in this application.
[0055]
[0056]
[0057]
[0058] Table 1
[0059] General structure
[0060] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport network, and service capabilities - including codec operation, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has begun work on the standardization of the next generation of cellular technology, referred to as NR, also known as "5G". The development of the 3GPP NR standard is expected to include the definition of the next generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 6 GHz and the provision of new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new non-backward compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with different needs. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access (e.g., indoor applications and hotspots). In particular, UMB is expected to share a common design framework with sub-6 GHz flexible radio access, and specific design optimizations with cmWave and mmWave.
[0061] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide range of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, 50+Mbps everywhere, ultra-low-cost broadband access, mobile broadband in vehicles), essential communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and interworking, energy conservation), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications within these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, cloud-based wireless office, first responder connectivity, car ecalls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, perceptual Internet, and virtual reality, to name a few. This article considers all of these use cases and others.
[0062] Figure 1AAn embodiment of an example communication system 100 is shown in which the methods and apparatus described and claimed herein may be embodied. As shown, the example communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d (which may be generally or collectively referred to as WTRUs 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be appreciated that the present disclosure contemplates any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e Figure 1A -E is depicted as a handheld wireless communication device, it is understood that considering the wide variety of use cases of 5G wireless communications, each WTRU may include or be embodied in any type of device or apparatus configured to send and / or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronic product, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, an industrial equipment, a drone, a vehicle (such as a car, a truck, a train, or an airplane), etc.
[0063] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a may be any type of device configured to wirelessly connect to at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The base station 114b may be any type of device configured to wirelessly connect to at least one of the RRHs (remote radio heads) 118a, 118b and / or TRPs (transmit and receive points) 119a, 119b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The RRHs 118a, 118b may be any type of device configured to wirelessly connect with at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The TRPs 119a, 119b may be any type of device configured to wirelessly connect with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTSs), Node-Bs, eNode Bs, Home Node Bs, Home eNode Bs, site controllers, access points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0064] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a may be configured to send and / or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The base station 114b may be configured to send and / or receive wired and / or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may therefore utilize multiple transceivers for each sector of the cell.
[0065] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).
[0066] The base station 114b may communicate with one or more of the RRHs 118a, 118b and / or TRPs 119a, 119b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).
[0067] The RRHs 118a, 118b and / or TRPs 119a, 119b may communicate with one or more of the WTRUs 102c, 102d over an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).
[0068] More specifically, as described above, the communication system 100 may be a multiple-access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 103 / 104 / 105, or the RRHs 118a, 118b and TRPs 119a, 119b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).
[0069] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interface 115 / 116 / 117 may implement 3GPP NR technology.
[0070] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 103 / 104 / 105, or the RRHs 118a, 118b and the TRPs 119a, 119b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b, may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95, Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0071] Figure 1A The base station 114c in the example may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area (such as a business place, a home, a vehicle, a campus, etc.). In an embodiment, the base station 114c and the WTRU 102e may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell. Figure 1A As shown, base station 114b may have a direct connection to the Internet 110. Thus, base station 114c may not need to access the Internet 110 via core network 106 / 107 / 109.
[0072] The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.
[0073] Although not in Figure 1AAs shown in the figure, it will be appreciated that the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or employing a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b, which may be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
[0074] The core network 106 / 107 / 109 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may use the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT.
[0075] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 1A The WTRU 102e shown in FIG. 1 may be configured to communicate with the base station 114a that may employ a cellular-based radio technology, and with the base station 114c that may employ an IEEE 802 radio technology.
[0076] Figure 1B 1 is a block diagram of an example apparatus or device (such as, for example, WTRU 102) configured for wireless communication in accordance with the embodiments illustrated herein. Figure 1BAs shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements and remain consistent with the embodiment. Moreover, the embodiments contemplate that the base stations 114a and 114b, and / or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home Node-B, an evolved home Node-B (eNodeB), a home evolved Node-B (HeNB), a home evolved Node-B gateway, and a proxy node, etc.) may include Figure 1B Some or all of the elements depicted in and described herein.
[0077] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0078] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interface 115 / 116 / 117. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, although Figure 1AAlthough transmission / reception is not shown, it will be appreciated that the RAN 103 / 104 / 105 and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or that employ a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105, which may be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM radio technology.
[0079] The core network 106 / 107 / 109 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may use the same RAT as the RAN 103 / 104 / 105 or a different RAT.
[0080] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 1A The WTRU 102c shown in FIG. 1 may be configured to communicate with the base station 114a using a cellular-based radio technology, and may communicate with the base station 114b using an IEEE 802 radio technology.
[0081] Figure 1B 1 is a block diagram of an example apparatus or device, such as, for example, WTRU 102, configured for wireless communication in accordance with the embodiments illustrated herein. Figure 1BAs shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements and remain consistent with the embodiment. Moreover, the embodiments contemplate that the base stations 114a and 114b, and / or the nodes that the base stations 114a and 114b may represent, such as but not limited to a transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home Node-B, an evolved home Node-B (eNodeB), a home evolved Node-B (HeNB), a home evolved Node-B gateway, and a proxy node, etc., may include Figure 1B Some or all of the elements depicted in and described herein.
[0082] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a microprocessor associated with a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0083] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, for example, the transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0084] In addition, despite the Figure 1B 102 as a single element, however, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.
[0085] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode functionality. Thus, for example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs such as UTRA and IEEE 802.11.
[0086] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable device, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In an embodiment, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0087] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.
[0088] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method, consistent with the embodiments.
[0089] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.
[0090] The WTRU 102 may be embodied in other devices or equipment, such as sensors, consumer electronics, wearable devices such as smart watches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains, or airplanes). The WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces (such as an interconnect interface that may include one of the peripheral devices 138).
[0091] Figure 1C 1 is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. Figure 1CAs shown, the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
[0092] like Figure 1C As shown, Node-B 140a, 140b can be in communication with RNC 142a. In addition, Node-B 140c can be in communication with RNC 142b. Node-B 140a, 140b, 140c can communicate with each RNC 142a, 142b via Iub interface. RNC 142a, 142b can be in communication with each other via Iur interface. Each of RNC 142a, 142b can be configured to control each Node-B 140a, 140b, 140c to which it is connected. In addition, each of RNC 142a, 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, switching control, macro diversity, security functions, data encryption, etc.
[0093] Figure 1C The illustrated core network 106 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0094] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
[0095] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0096] As described above, core network 106 may also be connected to networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0097] Figure 1D 1 is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.
[0098] Although the eNode-Bs may include 160a, 160b, 160c, it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
[0099] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink and / or downlink, etc. Figure 1D As shown, eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0100] Figure 1D The illustrated core network 107 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements are depicted as being part of the core network 107, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0101] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
[0102] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0103] The serving gateway 164 may also be connected to a PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0104] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 107 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0105] Figure 1E1 is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As will be discussed further below, the communication links between the different functional entities in the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
[0106] like Figure 1E As shown, although the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, it will be appreciated that the RAN 105 may include any number of base stations and ASN gateways and remain consistent with the embodiments. Each base station 180a, 180b, 180c may be associated with a particular cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In an embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, for example, the base station 180a may use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handover triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 182 may act as a traffic aggregation point and may be responsible for paging, caching of user profiles, routing to the core network 109, etc.
[0107] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.
[0108] The communication link between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point, which includes protocols for facilitating WTRU handovers and data transfer between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.
[0109] like Figure 1E As shown, the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, which includes, for example, protocols for facilitating data transmission and mobility management capabilities. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. Although each of the above elements are depicted as part of the core network 109, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0110] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communication devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.
[0111] Although not in Figure 1E102a, 102b, 102c between the RAN 105 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference point, which may include protocols for facilitating interworking between home core networks and visited core networks.
[0112] Described in this article and Figure 1A , 1C The core network entities shown in 1D and 1E are identified by names given to those entities in certain existing 3GPP specifications, but it is understood that those entities and functions may be identified by other names in the future, and that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Therefore, the descriptions in the following are provided by way of example only. Figure 1A , 1B , 1C, 1D and 1E, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or defined in the future.
[0113] Figure 1F is a block diagram of an exemplary computing system 90 in which the Figure 1A , 1C, 1D and 1E, such as certain nodes or functional entities in the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110 or other networks 112. The computing system 90 may include a computer or a server and may be primarily controlled by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within the processor 91 to enable the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. Coprocessor 81 is an optional processor distinct from main processor 91 that may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatus disclosed herein.
[0114] In operation, processor 91 fetches, decodes, and executes instructions, and transfers information to and from other resources, via the computing system's primary data transfer path, system bus 80. Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.
[0115] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes circuits that allow information to be stored and restored. ROM 93 generally contains stored data that cannot be easily modified. The data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address conversion function that converts a virtual address to a physical address when executing an instruction. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, the program cannot access memory within the virtual address space of another process.
[0116] Additionally, computing system 90 may include a peripheral device controller 83 that is responsible for communicating instructions from processor 91 to peripheral devices such as printer 94 , keyboard 84 , mouse 95 , and disk drive 85 .
[0117] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Figure 1F An example of a GUI is shown in FIG. Display 86 may be implemented by a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. Display controller 96 includes the electronic components required to generate a video signal sent to display 86.
[0118] Furthermore, computing system 90 may include communications circuitry, such as, for example, a network adapter 97, which may be used to connect computing system 90 to an external communications network, such as Figure 1A , 1B , RAN 103 / 104 / 105 in 1C, 1D and 1E, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112 to enable computing system 90 to communicate with other nodes or functional entities of those networks. Communication circuitry alone or in combination with processor 91 may be used to perform the sending and receiving steps of certain devices, nodes, or functional entities described herein.
[0119] It is understood that any or all of the devices, systems, methods, and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor such as processor 118 or 91, causes the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer executable instructions, which are executed on a processor of a device or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media for storing information implemented in any non-transitory (e.g., tangible or physical) method or technology, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disk storage, cassettes, tapes, disk storage or other magnetic storage devices, or any other tangible or physical medium that can be used to store the desired information and can be accessed by a computing system.
[0120] Unlicensed spectrum in LTE
[0121] As specified in 3GPP TS 36.213 physical layer procedures for Release 13 and Release 14, the target of Licensed Assisted Access (LAA) is carrier aggregation (CA) operation in which one or more low-power secondary cells (SCells) operate in unlicensed spectrum at sub 6 GHz. LAA deployment scenarios include scenarios with and without macro coverage, outdoor and indoor small cell deployments, and co-location and non-co-location between licensed and unlicensed carriers (with ideal backhaul), such as Figure 2A -D as shown.
[0122] Figure 2A Scenario 1 of FIG. 1 depicts carrier aggregation between a licensed macro cell (F1) and an unlicensed small cell (F3). Figure 2B Scenario 2 of FIG. 1 depicts carrier aggregation between a licensed small cell (F2) and an unlicensed small cell (F3) in the absence of macro cell coverage. Subsequently, Figure 2C Scenario 3 of FIG. 5 depicts carrier aggregation between a licensed macro cell (F1), a licensed small cell (F2), and an unlicensed small cell (F3).
[0123] further, Figure 2DScenario 4 of FIG. 4 depicts a licensed macro cell (F1), a licensed small cell (F2), and an unlicensed small cell (F3). Scenario 4 includes carrier aggregation between the licensed small cell (F2) and the unlicensed small cell (F3). If there is an ideal backhaul between the macro cell and the small cell, carrier aggregation may exist between the macro cell (F1), the licensed small cell (F2), and the unlicensed small cell (F3). If dual connectivity is enabled, dual connectivity may exist between the macro cell and the small cell.
[0124] Because the unlicensed band can be used by different deployments specified by different standards, several regulatory requirements are imposed to ensure fair coexistence between all incumbent users. For example, these regulatory requirements include restrictions on transmit power masks, transmit bandwidth, interference with weather radars, etc.
[0125] In addition, another major requirement is the channel access process. For example, the LBT process is defined as a mechanism by which a device applies a clear channel assessment (CCA) check before using a channel. CCA uses energy detection to determine the presence or absence of other signals on the channel. In turn, this determines whether the channel is occupied or idle, respectively. European and Japanese regulations authorize the use of LBT in unlicensed bands. In addition to regulatory requirements, carrier sensing via LBT is a way to fairly share unlicensed spectrum. Therefore, it is important for fair and friendly operation in unlicensed spectrum within a single global solution framework.
[0126] In Release 14, several channel access procedures were introduced, which are performed by the eNB and UE for downlink (DL) and UL transmissions respectively. The main channel access procedures are described in Section 15 of TS 36.213 Release 14.
[0127] Unlicensed spectrum in NR
[0128] In mmWave, there is a wide range of unlicensed spectrum that can be further exploited to achieve higher data rates than those achieved when operating in sub-6GHz bands. Therefore, RAN#76 introduced a new type of SI for NR-based unlicensed spectrum access. The main goals of the current SI include studying the different physical channels and processes in NR-U and how to modify them. The goals also include introducing new physical channels or processes to meet NR-U challenges. This explains the reason for operating in mmWave, which deploys narrow beams for transmission and reception in bands above 6GHZ up to 52.6GHz or even above 52.6GHz. The process of enhancing coexistence between NR-U and other technologies operating in unlicensed (such as Wi-Fi devices, LTE-based LAA devices, other NR-U devices, etc.) and meeting regulatory requirements is currently being studied.
[0129] High priority synchronization information and discovery reference signals
[0130] According to one aspect of the application in NR, SSB allows the UE to obtain synchronization related information, frame boundaries, etc. In NR-U, UEs in different services (e.g., NR, WIFI) share the same unlicensed spectrum. Therefore, the UE and the gNB perform LBT to ensure that the channel is not occupied before transmission. This feature introduces uncertainty into periodic or semi-persistent scheduled transmissions such as SSB transmissions. Considering the importance of SSB in cell search, synchronization, etc., it is envisioned that SSB transmissions can be classified as high priority in channel access priority registration with no backoff time or with the smallest backoff time among all channel access backoff times.
[0131] In an embodiment, SSB will have a higher probability to have a smaller maximum channel occupancy time (MCOT) T mcot For example, for channel access priority level 1 in LAA, T mcot = 2ms. In NR, SSB is sent in SSB bursts that can last up to 5ms. The entire SSB burst may not fit in the T of priority level 1. mcot , for example, subcarrier spacing case A and case D. Therefore, it is envisaged that in NR-U, the SSB burst set can be divided into several subsets and sent in several subsets to meet T mcot Requirement. Figure 3A The example shown in -B uses subcarrier spacing case A in NR. The subcarrier spacing is 15Khz, while the carrier frequency is 3GHz≤f≤6GHz. In this case, the entire SSB burst set contains the number of subcarriers that cannot be filled into T mcot The gNB may divide the SSB burst set into two SSB burst subsets, and the duration of each SSB burst subset is less than 2ms. The gNB performs LBT and sends the first subset and repeats the process for the second subset.
[0132] Alternatively, the gNB may divide the SSB burst set into a finer granularity, such as 4 subsets, where each subset contains 2 SSBs. It is envisioned that each subset may contain one or more SSB bursts. The periodicity of the SSB burst subset may be the same as the periodicity of the SSB burst set. Once the SSB burst subset is determined, it may be sent in one of the following exemplary ways:
[0133] In the first approach, the UE can be configured by the gNB to receive multiple SSB burst subsets in one radio frame. Figure 3AAn example of this approach is shown in . In this case, the UE may be configured to monitor all SSB burst subsets at one time.
[0134] In the second approach, the UE may be configured by the gNB to receive subsets of SSB bursts in different radio frames. Figure 3B An example of this approach is shown in . In this case, the UE may be configured to monitor different SSB burst subsets at different times.
[0135] The entire SSB burst set can be filled to T mcot In the case of subcarrier spacing cases B, C, and E, the SSB burst set may also be divided into multiple SSB burst subsets and transmitted. For example, the gNB may transmit the SSB burst subsets in a shorter time than T after LBT. mcot The channel occupancy duration is used to send a subset of SSB bursts.
[0136] STTC
[0137] According to yet another embodiment, in order to further enhance the reliability of SSB transmission, it is contemplated that SSB burst sets / subsets may be transmitted in STTC (SSB Transmission Timing Configuration). Figure 4 An example depiction is provided in . The duration of the STTC may be preconfigured or specified. Alternatively, it may be configured / signaled by the gNB via RRC signaling and / or MAC CE. For example, the UE may be configured by the RRC message SSB_Tansmission_Timing_duration indicating the duration of the STTC, which may be 5ms, 8ms, etc. Within one STTC, multiple LBTs may be performed. An SSB burst set / subset may be sent after a successful LBT, and one or more SSB burst sets / subsets may be sent within one STTC. In an alternative embodiment, the UE may monitor the SSB multiple times within the configured STTC to detect the transmitted SSB, rather than monitoring the SSB only at one fixed position in time.
[0138] STC burst set / subset sliding within STTC
[0139] According to yet another aspect of the application in NR, multiple SSBs are bundled in a SS burst set. The SS burst set is transmitted at a predefined / configured location. In NR-U, the gNB performs LBT before the SSB burst transmission. SSB transmissions can still be bundled together. Figure 5 An example of a successful LBT for sending a bound SSB at a predefined / configured location is shown in FIG.
[0140] according to Figure 5In this example, omnidirectional LBT or beam-based directional LBT can be performed prior to the configured SSB transmission. With successful LBT on omnidirectional or all directional beams, the SSB can be transmitted as an SSB burst set at predefined / configured locations. If the gNB is able to occupy the channel for this duration, no additional LBT is required during the SSB burst set transmission. It is envisioned that the bundled SSB transmission can be shifted in the STTC. In this case, while the SSB index order is not changed within the bundled SSB transmission (e.g., SSB#0, SSB#1, SSB#2, SSB#3), the SSB#0 position can be changed within the radio frame. Multiple LBTs can be performed by the gNB within the STTC. LBT can be performed by one of the following exemplary options:
[0141] Option 1: The gNB may perform LBT just before the possible SSB transmission positions with one attempt. The possible SSB transmission positions may be determined based on the resolution of the offset. The offset may be predefined in the specification (spec) or may be configured in the STTC. Possible position of SSBi = specified SSBi position + j*slot, where j is the iteration of LBT processing after the initial LBT failure of SSBi. Assume that SSB 0 is configured to be transmitted at symbol 4 of slot 1. If the offset is the number of slots, the first possible SSB transmission position of SSB 0 is at symbol 4 of slot 1, and the second possible SSB transmission position of SSB 0 is at symbol 4 of slot 2, and so on. If LBT is successful, the gNB will send the shifted SSB. If LBT fails, the gNB may perform LBT before the next possible SSB transmission position. Figure 6 This option is illustrated in Figure 1. The gNB can perform 25μs LBT at symbol 3 of slot 0 without backoff time. LBT can be omnidirectional LBT or beam-based directional LBT. If it fails, the gNB can perform 25μs LBT at symbol 3 of slot 1 without backoff time. If LBT succeeds in slot 1, the bundled SSB can be sent starting from symbol 4 of slot 1 to symbol 9 of slot 2.
[0142] Option 2: The gNB may perform LBT with multiple attempts before the possible SSB transmission position. The possible SSB transmission position may be determined based on the resolution of an offset that may be predefined in the specification or may be configured in the STTC. Possible position of SSBi = specified SSBi position + j*timeslot, where j is the iteration of LBT processing after the initial LBT failure of SSBi. If LBT succeeds earlier than the possible SSB transmission position, a reservation signal will be sent to occupy the channel and the SSB will be transmitted at the possible SSB transmission position. Figure 7An exemplary diagram is shown in FIG. The gNB can perform LBT of 25 μs at symbol 3 of slot 0 without backoff time. The LBT can be omnidirectional LBT or beam-based directional LBT. If it fails, the gNB can continue to perform LBT. If LBT succeeds at symbol 0 of slot 1, a reservation signal can be sent to maintain the channel that can last for several symbols. Note that due to the limitation of MCOT, the reservation signal cannot be of arbitrary length. Finally, the bound SSB can be sent starting from symbol 4 of slot 1 to symbol 9 of slot 2.
[0143] In an embodiment, the bundled SSB transmission is shifted in the STTC. In this scenario, a fixed offset Δ is introduced from the radio frame boundary to all SSBs. For example, the offset can be Figure 6 and Figure 7 The number of time slots shown. In this case, Δ = k time slots, where k = 0, 1, 2, ..., K-1.
[0144] In an alternative embodiment, the offset may be the number of SSB positions. The possible SSB transmission positions may be determined based on the resolution of the offset and may be predefined in the specification or may be configured in the STTC. Assume that SSB0 is configured to be transmitted at symbol 4 of slot 1. If the offset is the number of SSB positions, then after an initial LBT failure for SSB 0, the first possible SSB transmission position determined by the offset resolution and iterations of the LBT process is at symbol 8 of slot 0. The second possible SSB transmission position for SSB 0 is at symbol 4 of slot 1, and so on. Figure 8 An exemplary embodiment is shown in FIG. LBT may fail at symbol 3 of slot 0, but succeed at symbol 7 of slot 0. In this scenario, the bonded SSB may be shifted by one SSB position and sent. In other words, SSB 0 is sent where SSB 1 should be sent, SSB 1 is sent where SSB 2 should be sent, and so on. The offset will be the SSB index difference between the scheduled SSB index and the SSB index actually sent.
[0145] exist Figure 8 In the example shown, the offset is equal to 1. The offset is a logical value that the UE needs to map to a physical location based on a specific SSB configuration. In this example, the reservation signal is not used after the initial LBT failure, and LBT is performed just before the possible SSB transmission location determined by the offset resolution and the iteration of the LBT process. In an alternative embodiment, the reservation signal can be used for this solution.
[0146] In another case, when the SSB bundling is shifted, the SSB index order can be changed within the bundled SSB transmission. For example, the SSB index order can be cyclically shifted, for example, the cyclically shifted SSB index order can be SSB#1, SSB#2, SSB#3, SSB#0.
[0147] According to an embodiment, in order to determine the frame boundary, the UE needs to know the information of the SSB block index and the offset Δ. Figure 8 An example of the offset Δ is shown in FIG. 1 . In order to obtain information about the offset, the UE may indicate the value of the offset Δ using one of the following options:
[0148] Option 1: The value of the offset Δ can be indicated by the PBCH payload. For example, the PBCH of all beams can carry the same payload and indicate the offset from the frame boundary (2 bits for 4 positions). For example, if there are 4 or 8 SSBs in the SSB burst set transmission, the reserved PBCH payload bits Can be used to indicate the offset Δ. The UE can determine the frame boundary using the information of the SSB block index and the offset Δ. Alternatively, some additional field can be added to the PBCH to convey the value of the offset Δ.
[0149] Option 1a: The offset Δ can be indicated by applying a mask to the CRC bits of the PBCH payload. The UE decodes the PBCH and applies different masks to the CRC. The mask that makes the CRC checksum successful is used to indicate the offset Δ.
[0150] Option 2: The value of the offset Δ may be indicated by the PBCH DMRS. The PBCH DMRS may be initialized by the offset Δ. An example is provided below:
[0151]
[0152] When the UE detects the PBCH DMRS through blind cross-correlation, the offset value is determined based on the PBCH DMRS sequence.
[0153] Option 3: The value of the offset Δ may be indicated jointly by the PBCH DMRS and the PBCH payload. For example, assuming that 3 bits are required to indicate the offset Δ, two MSBs may be indicated in the PBCH payload. The PBCH DMRS may indicate the LSB by using a different sequence initialized by one LSB of the offset.
[0154] Option 4: This is based on the requirement of channel occupancy in the frequency of the unlicensed band. In NR-U, SSB can be repeated in the frequency domain and sent on the same beam to meet the requirement. Fig. 9 An exemplary embodiment is depicted in FIG.
[0155] In NR, PBCH DMRS is used for blind detection of up to 3 LSB bits of the SSB index. If the offset Δ also has to be indicated, the number of blind decodings increases and the PBCH DMRS may not be robust enough. It is envisaged that SSB repetition may be advantageously employed to indicate the offset Δ.
[0156] If the SSB is repeated, a spreading code may be applied to the PBCH DMRS. Different spreading codes may be used for different SSBs, for example, the PBCH DMRS of SSB 1 may be spread with [1 1 1 1], the PBCH DMRS of SSB 2 may be spread with [1 1 -1-1], the PBCH DMRS of SSB 3 may be spread with [1 -1 1 -1], etc. The value of the offset Δ may be implicitly indicated by the spreading code. For example, when Δ=1, the PBCH DMRS of the SSB is spread with [1 1 1 1], when Δ=2, the PBCH DMRS of the SSB is spread with [1 1 -1-1], etc.
[0157] Option 5: The value of the offset Δ may be indicated by the RMSIPDCCH or RMSIPDSCH. In NR-U, the RMSI CORESET and / or RMSIPDSCH may be sent in the same time slot associated with the transmitted SSB. For example, the RMSI CORESET and SSB may be as follows: Fig.10 As shown, the RMSI PDCCH is FDMed in the same time slot. A new field can be added to the RMSIPDCCH to carry the SSB offset value Δ. When the UE detects an SSB, it can decode the RMSIPDCCH sent in the same time slot to determine the offset by which the SSB can be shifted. Therefore, the UE can determine the frame boundary. The UE can determine the location of the RMSIPDCCH by some rules predefined in the specification or by the RMSI-PDCCH-Config message configured in the MIB. The UE can determine the PDCCH monitoring timing from the k least significant bits of the RMSI-PDCCH-Config. If both M and O provided by the k least significant bits of the RMSI-PDCCH-Config are equal to 0, the RMSI CORESET can be FDMed with the SSB in the same time slot.
[0158] In an alternative embodiment, the RSMI CORESET may be as follows Fig.11As shown, TDM is performed with SSB in the same time slot. For example, SSB 0 is sent from symbol 4 to symbol 7. The corresponding RMSI CORESET and / or PDSCH can be sent from symbol 8 to symbol 9. In the frequency domain, the RBs used to send RMSI CORESET / PDSCH and SSB can be different as shown; TDM and FDM. In an alternative embodiment, the same RB can be used to send RMSI CORESET / PDSCH and SSB.
[0159] In yet another embodiment, the gNB may perform LBT one beam at a time. For example, starting with SSB 0, the gNB first performs LBT on SSB 0. If SSB 0 is transmitted, the gNB transmits SSB 0 and performs LBT on the next SSB (e.g., SSB 1). If SSB 0 cannot be transmitted, the remaining SSB bursts (SSB 0, SSB 1, SSB 2, SSB 3) are shifted and the gNB performs LBT on SSB 0 at the next time opportunity. If SSB 0 is transmitted at time opportunity k, but SSB 1 cannot be transmitted at time opportunity k+1. The remaining SSB bursts (SSB 1, SSB 2, SSB 3) are shifted and the gNB performs LBT on SSB 1 at the next time opportunity (time opportunity k+2). This process is repeated until all SSBs in the burst are transmitted or the STTC window expires.
[0160] For initial cell selection of a UE in an idle or inactive state, it is envisaged to assume a certain fixed STTC, for example, the UE may assume that the duration of the STTC is 5ms, as predefined in the specification. The UE may determine the frame boundary based on the predefined STTC, the detected SSB transmission offset Δ, etc.
[0161] For a UE in a connected state, the UE may be configured with STTC through one or more of RRC signaling, MAC CE, etc. The UE may determine the frame boundary based on the SSB index, the detected SSB transmission offset Δ, etc. Fig.12 An example of a process for monitoring and receiving bound SSB transmissions is shown in FIG.
[0162] SSB burst set / subset transmission using opportunistic transmission
[0163] According to another aspect of the present application in NR-U, it is contemplated that SSB transmissions may not be bundled, for example, the gNB may perform beam-based directional LBT on all beams before scheduling SSB transmissions. For beams with successful LBT, the corresponding SSB will be transmitted. For beams with LBT failures, the gNB may skip the transmission of the corresponding SSB. This Fig.13. The gNB performs beam-based directional LBT. It may perform LBT on all 4 beams before slot 0 of subframe 0. Alternatively, it may perform LBT on beam 0 and beam 1 before slot 0 of subframe 0. It may perform LBT on beam 2 and beam 3 before slot 1 of subframe 0. Only LBT for beams 0 and 3 is successful. Therefore, only SSB#0 and SSB#3 are transmitted at the scheduled position. At the same time, SSB#1 and SSB#2 are discarded.
[0164] Considering the importance of SSB transmission in NR system, dropped SSB transmission may be serious. To improve the reliability of SSB transmission, in addition to scheduled SSB transmission, the UE may be configured with opportunistic SSB transmission to monitor dropped SSB transmission due to LBT failure, for example, dropping SSB#1 and SSB#2 due to beam-based LBT failure in scheduled SSB transmission. Then, the gNB may perform beam-based directional LBT on the dropped SSBs before the configured opportunistic SSB transmission. If the beam-based LBT succeeds, the corresponding SSB will be sent during the configured opportunistic SSB transmission. The LBT may be an LBT without backoff time or an LBT with a contention window (such as channel access priority level 1). Regardless of the SSB sent in the opportunistic SSB transmission, the resources may not be used for other transmissions. In doing so, if no SSB is sent, the opportunistic resource may be empty. The UE may always assume that the data is rate matched near the opportunistic resource. Within one opportunistic SSB transmission, multiple SSBs may be sent after the corresponding LBT succeeds. Alternatively, opportunistic SSB transmissions may be beam specific, e.g., each SSB is configured with a dedicated opportunistic SSB transmission configuration. Opportunistic SSB transmissions may be configured with one of the following options:
[0165] Option 1: The UE may be configured to monitor for opportunistic SSB transmissions within the STTC after a scheduled SSB transmission. Fig.14 An example embodiment is shown in FIG. 1 . In this example, opportunistic SSB transmissions are beam specific, and both SSB 1 and SSB 2 fail in the scheduled transmissions. A successful LBT for SSB 1 is performed at symbol 7 of slot 2. SSB 1 is transmitted from symbol 8 to symbol 11 in the configured slot 2. A successful LBT for SSB 2 is performed at symbol 1 of slot 3. SSB 1 is then transmitted from symbol 2 to symbol 5 in slot 3.
[0166] In this case, an SSB-specific offset Δ may be introduced to each SSB from the frame boundary SSB,i The UE can indicate the SSB specific offset Δ SSB,i and SSB index information to determine the frame boundary.
[0167] Option 2: The UE may not be configured with STTC. The UE may be configured to monitor the opportunistic SSB transmission opportunity between two scheduled SSB transmissions. Fig.15 An exemplary embodiment is shown in FIG. Both SSB 1 and SSB 2 fail in the scheduled transmission. LBT of SSB 1 and SSB 2 is performed at symbol 7 of slot k. Within an opportunistic SSB transmission opportunity, one LBT and transmission attempt may be performed. Alternatively, STTC may be configured where multiple LBT and transmission attempts may be performed. If STTC is configured, an SSB offset Δ may be employed by the UE. SSB,i or Δ to determine the frame boundary.
[0168] Option 3: The UE can be configured with STTC. The UE can also be configured with two STTC opportunistic SSB transmission timings. Fig.16 An exemplary embodiment is shown in . Within an STTC, if an SSB is not sent at the scheduled position due to LBT failure, it can be shifted (e.g., sent in opportunity transmission a or opportunity transmission b, etc.). Between two STTCs, the UE can be configured with SSB transmission timings, i.e., sent in opportunity transmission timing 1, opportunity transmission timing 2, etc. The gNB can perform Class 1 or Class 4 LBT before each opportunity transmission timing. If the channel is idle, the gNB will send the SSB within the opportunity transmission timing. If the channel is not idle, the gNB will skip the opportunity transmission timing. For each opportunity transmission timing, the same SSB can be sent, for example, in both opportunity transmission timing 1 and opportunity transmission timing 2, the gNB can perform LBT and attempt to send all 4 SSBs (SSB 0, SSB 1, SSB 2, SSB 3). In an alternative embodiment, different SSBs can be sent in different opportunity transmission timings, for example, in opportunity transmission timing 1, the gNB can perform LBT and attempt to send SSB 0 and SSB 1. In opportunity transmission 2, the gNB can perform LBT and attempt to send SSB 2 and SSB 3.
[0169] According to another embodiment, for initial cell selection, a UE in an idle or inactive state may assume a fixed STTC, for example, a duration predefined in the specification. The UE may send an offset Δ or Δ based on the predefined STTC, the detected SSB, SSB,i etc. to determine the frame boundaries.
[0170] For a UE in a connected state, the STTC may be configured for the UE through one or more of RRC signaling and MAC CE. The UE may send an offset Δ or Δ based on the predefined / configured STTC, the detected SSB, SSB,i etc. to determine the frame boundaries. Fig.17An example of the process of monitoring and receiving SSB transmissions that are sent opportunistically is shown in FIG.
[0171] SSB transmission using dedicated STTC
[0172] According to yet another aspect of the present application, it is contemplated that the UE may be configured to monitor a dedicated STTC for each SSB or every two SSBs. Fig.18 An example is shown in FIG.
[0173] Within one SSB burst set transmission period (e.g. 20ms), the STTC can be configured for every two SSBs sent in one time slot (rather than a whole burst or half a burst). Assuming a 15KHz digital scheme and 4ms, SSB 0 and SSB 1 can be sent in any of the 4 time slots. SSB 2 and SSB 3 can then slide across 4 time slots within their STTC. The STTC can be continuous, for example starting from 0ms, 4ms, 8ms, etc. Alternatively, the STTC can be non-continuous, for example starting from 0ms, 5ms, 10ms, etc. Within each STTC, the offset Δ of the SSB transmission needs to be indicated to the UE to determine the frame boundary.
[0174] For initial cell selection, a UE in idle or inactive state may assume a fixed STTC, for example, a duration and time position as predefined in the specification. The UE may determine the frame boundary based on the predefined STTC, SSB transmission offset Δ, etc.
[0175] For a UE in a connected state, the STTC may be configured for the UE through one or more of RRC signaling and MAC CE. The UE may determine the frame boundary based on the configured STTC, SSB transmission offset Δ, etc.
[0176] exist Fig.19 An exemplary process for monitoring and receiving dedicated SSB transmissions using STTC is provided in . The UE may repeat the process for different SSBs in differently configured STTCs.
[0177] SSB burst set / subset transmission with flexible index order
[0178] In yet a further aspect of the present application, in NR, SSBs are transmitted at fixed SSB positions, for example, SSB#0 is transmitted at SSB position 0, and SSB#1 is transmitted at SSB position 1. Therefore, within the SSB transmission, the order of SSB indexes is fixed, for example, SSB#0, SSB#1, SSB#2, SSB#3.
[0179] In NR-U, it is envisioned that the UE can be configured to utilize SSB transmissions with flexible order indexing. For example, the SSB index order can be different within a burst. The same SSB can be sent at different SSB positions within an SSB burst set / subset transmission. Fig. 20 An exemplary embodiment is shown in FIG.
[0180] The gNB may perform beam-based directional LBT on all beams before slot 0 of subframe 0. If the channel of the scheduled SSB is available, the gNB may send the scheduled SSB at the scheduled position, for example, if the channel is available for SSB 1, SSB 1 is sent at SSB position 1. If the channel of the scheduled SSB is not available and the channels of other SSBs are available, the gNB may send the available SSB at that position, for example, if the channel of SSB 0 is not available and the channel of SSB 2 is available, SSB 2 may be sent at SSB position 0. For the SSB that has been transmitted, the gNB will not perform beam-based LBT on the beam in the remaining LBT opportunities within one SSB burst set / subset transmission. When multiple untransmitted SSB channels are available for one SSB position, the SSB that missed its scheduled SSB position may have a higher transmission priority. For example, SSB 2 cannot be sent at SSB position 2 due to LBT failure. When channels for SSB 0 and SSB 4 are available. SSB 0 may be sent at SSB position 2. If some SSBs cannot be transmitted within the MCOT, the gNB may drop these beams. Alternatively, STTC may be configured for the failed SSBs and opportunistic transmissions may be performed.
[0181] To determine where the SSB is actually sent, the UE may provide an offset value Δ for each SSB. SSB,i The offset value can be negative. If so, an additional bit may be needed to indicate whether the value is positive or negative.
[0182] In an alternative embodiment, the SSB position index information may be carried by the PBCH DMRS and the PBCH payload. For example, if there are 64 SSBs in the SSB burst set transmission, the PBCH payload bits It can be the 6th, 5th, and 4th bits of the SSB position index. The PBCH DMRS can be initialized by the SSB position index as
[0183]
[0184] in,
[0185] For L max =4,n hf is the number of the half-frame in which the PBCH is in the frame (for the first half-frame n in the frame hf= 0, and for the second half frame n in the frame hf =1) is sent, and i SSB,location These are the two least significant bits of the SSB block position index.
[0186] For L max =8 or L max =64,n hf =0 and i SSB,location Are the three least significant bits of the SSB block position index.
[0187] In this case, the PBCH payload may be different for the same SSB index in different SSB transmissions. The UE may use the SSB block position index to determine the frame boundary. In addition, if STTC is used to enhance SSB transmission, for initial cell selection, a UE in an idle or inactive state may assume a certain fixed STTC, for example, a duration predefined in the specification. The UE may determine the frame boundary based on a predefined STTC, a detected SSB transmission offset Δ, an SSB block position index, etc. For a UE in a connected state, the STTC may be configured for the UE through one or more of RRC signaling and MAC CE. The UE may determine the frame boundary based on a predefined / configured STTC, a detected SSB transmission offset Δ, an SSB position index, etc. In Fig.21 An exemplary embodiment of a process for monitoring and receiving SSB transmissions utilizing a flexible index order is shown in FIG.
[0188] The solution proposed for indicating the offset Δ can also be applied here to indicate the SSB block position index.
[0189] Impact of DRS / SSB sliding on configuration and scheduling in STTC
[0190] According to yet another aspect of the present application, when STTC is used for SSB transmission, the SSB transmission may be shifted in the timing window. If the SSB transmission is shifted, it may overlap with other configurations or scheduling (such as semi-persistent scheduling or PRACH resources). In this scenario, the following options are envisioned:
[0191] Option 1: When the UE detects that the SSB transmission is shifted, the UE may assume that other configurations and / or scheduling are not shifted. Fig.22A Examples of the impact of SSB shift on PRACH resources are exemplarily shown in Figures 1 and 2. These diagrams show a scenario where SSB 0 is transmitted at the scheduled position. The timing difference between the SSB 0 transmission and the corresponding PRACH resource is denoted as offset k. Fig. 22BA scenario is shown where the SSB 0 transmission is shifted by Δ due to LBT failure at the scheduled position. The PRACH resources are not shifted. As a result, the timing difference between the SSB transmission and the corresponding PRACH resource becomes k-Δ.
[0192] If k-Δ is less than the time required for the UE to switch from D1 to UL, the UE can discard the PRACH. The UE can first determine the frame boundary using the obtained SSB index and the SSB transmission offset Δ. Then, regardless of whether the SSB transmission is shifted, the UE can perform the PRACH procedure at the configured RACH resource (same position). If the UE misses the first PRACH resource due to SSB shift, the UE can perform the RACH procedure at the next available PRACH resource. The same principle can also apply to paging indication (PI), semi-permanent resources, etc. If the SSB overlaps with other transmissions (such as other reference signals or data) due to shifting, the other transmissions can be discarded and punctured by the SSB, or rate matched near the SSB.
[0193] Option 2: When the UE detects that the SSB transmission has been shifted, the UE may assume that other configurations and / or scheduling have been shifted, respectively. Fig. 22C An exemplary embodiment depicting the effect of SSB shifting on PRACH resources is shown in FIG. When SSB 0 is transmitted at a scheduled position shifted by Δ due to LBT failure, the PRACH resources may also be shifted. For example, the PRACH resources are also shifted by Δ. In doing so, the timing difference between the reception of SSB 0 and the PRACH resources does not change, for example, and remains the offset k.
[0194] When PRACH is shifted, it can follow one of the following alternatives:
[0195] Alternative 1: The shift of PRACH can be implicitly indicated by the shift of SSB transmission. When the UE determines that the SSB transmission is shifted and determines the SSB transmission offset Δ, the UE can automatically apply the same offset to the timing position of the PRACH process. After the UE determines the configured RACH resources through the higher layer parameter PRACHConfigurationIndex, the UE can perform the PRACH process with the additional offset instead of the configured position. For example, if the configured PRACH resource is at timing t, the UE can send message 1 at position t+Δ.
[0196] Alternative 2: The shift of PRACH can be explicitly indicated. For example, the higher layer parameter PRACHConfigurationOffset can be used to indicate how much offset the UE should add to the PRACH resource timing position. The value of PRACHConfigurationOffset and the value of the SSB transmission offset Δ can be the same or different. Assuming PRACHConfigurationOffset is set to Δ' and the configured PRACH resource is at timing t, the UE can send message 1 at position t+Δ'.
[0197] The same idea can also be applied to paging indication (PI), semi-persistent resources, etc. If the SSB overlaps with other transmissions (such as other reference signals or data) due to shifting, the other transmissions can be dropped and punctured by the SSB, or rate matched around the SSB.
[0198] This solution works well for FDM configurations with SSB. Fig.23 An example is shown in . If RMSI is FDM-transmitted together with SSB, then if SSB is shifted, RMSI will shift accordingly.
[0199] According to the present disclosure, it is understood that any or all of the systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a machine (such as a computer, a server, an M2M terminal device, an M2M gateway device, a transfer device, etc.), executes and / or implements the systems, methods and processes described herein. Specifically, any of the above steps, operations or functions may be implemented in the form of such computer executable instructions. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disk storage, cassettes, tapes, disk storage or other magnetic storage devices, or any other physical medium that can be used to store the desired information and can be accessed by a computer.
[0200] According to another aspect of the present application, a non-transitory computer-readable or executable storage medium for storing computer-readable or executable instructions is disclosed. The medium may include one or more computer-executable instructions such as those disclosed above in multiple call flows. The computer-executable instructions may be stored in a memory and executed by the above Figure 1C and 1FThe method is executed by a processor disclosed in and is employed in a device including a node (such as, for example, end-user equipment).
[0201] Although the present system and method have been described in terms of what are currently considered to be specific aspects, the present application is not necessarily limited to the disclosed aspects. It is intended to cover various modifications and similar arrangements included within the spirit and scope of the claims, the scope of which should be consistent with the broadest interpretation to include all such modifications and similar structures. The present disclosure includes any and all aspects of the following claims.
Claims
1. A wireless transmit / receive unit WTRU, comprising a processor and a memory, wherein the processor and the memory are configured to: receiving at least one synchronization signal and an SSB transmission included in a physical broadcast channel SSB burst, wherein the at least one SSB transmission included in the SSB burst is received during an SSB transmission timing configuration STTC duration, wherein under the condition that the STTC duration for explicit signaling is received from a network node in a radio resource control RRC message, the length of the STTC duration is determined based on the duration of the explicit signaling, and in the case that the STTC duration for explicit signaling is not received from the network node through RRC signaling, the length of the STTC duration is determined to be a predefined length of 5 ms; receiving a physical broadcast channel (PBCH) demodulation reference signal (DMRS) and a PBCH payload included in the at least one SSB transmission; and Based on the PBCH payload and the initialization sequence of the PBCH DMRS, the position of at least one SSB transmission in the SSB burst is determined.
2. The WTRU of claim 1 , wherein the processor and the memory are configured to: The frame boundary is determined based on the location of at least one SSB transmission within the SSB burst.
3. The WTRU of claim 1 , wherein the WTRU is configured to receive a duration of display signaling for operating in new radio unlicensed NR-U spectrum operation.
4. The WTRU of claim 1 , wherein: The WTRU is configured to determine a most significant bit (MSB) associated with a position of the at least one SSB transmission within the SSB burst based on the PBCH payload, and to determine a least significant bit (LSB) associated with a position of the at least one SSB transmission within the SSB burst based on an initialization sequence of the PBCH DMRS.
5. The WTRU of claim 1 , wherein the reception of at least one SSB transmission indicates a successful listen-before-talk (LBT) operation.
6. A method implemented by a wireless transmit / receive unit WTRU, the method comprising: receiving at least one synchronization signal and an SSB transmission included in a physical broadcast channel SSB burst, wherein the at least one SSB transmission included in the SSB burst is received during an SSB transmission timing configuration STTC duration, wherein under the condition that the STTC duration for explicit signaling is received from a network node in a radio resource control RRC message, the length of the STTC duration is determined based on the duration of the explicit signaling, and in the case that the STTC duration for explicit signaling is not received from the network node through RRC signaling, the length of the STTC duration is determined to be a predefined length of 5 ms; receiving a physical broadcast channel (PBCH) demodulation reference signal (DMRS) and a PBCH payload included in the at least one SSB transmission; as well as Based on the PBCH payload and the initialization sequence of the PBCH DMRS, the position of at least one SSB transmission in the SSB burst is determined.
7. The method according to claim 6, further comprising: The frame boundary is determined based on the location of at least one SSB transmission within the SSB burst.
8. The method of claim 6, wherein the WTRU receives a duration of explicit signaling for operating in new radio unlicensed NR-U spectrum operation.
9. The method of claim 6, wherein the WTRU determines a most significant bit (MSB) associated with the position of the at least one SSB transmission within the SSB burst based on the PBCH payload, and determines a least significant bit (LSB) associated with the position of the at least one SSB transmission within the SSB burst based on an initialization sequence of the PBCH DMRS.
10. The method of claim 6, wherein the receipt of the at least one SSB transmission indicates a successful listen-before-talk (LBT) operation.
11. A wireless transmission / reception unit, comprising a processor and a memory, wherein the processor and the memory are configured to: a non-transitory memory including instructions stored thereon for monitoring synchronization signal blocks (SSBs) in an unlicensed spectrum; as well as A processor, operatively coupled to the non-transitory memory, is configured to execute the following instructions: Determine the length of the SSB transmission timing window, wherein under the condition that the SSB transmission timing configuration STTC is received from the network node, the length of the SSB transmission timing window is determined based on the received STTC, and under the condition that the STTC is not received from the network node, the SSB transmission timing window is determined to be a predefined length of 5 ms; According to the SSB sending timing window, the SSB is monitored based on the STTC; receiving at least one SSB in the SSB transmission timing window; Receive physical broadcast channel PBCH demodulation reference signal DMRS and PBCH payload; Determine an offset based on the PBCH DMRS and the PBCH payload; and The frame boundary is determined based on information indicating the offset of the received SSB.
12. The wireless transmit / receive unit of claim 11, wherein the processor is further configured to execute instructions for determining a second SSB in the STTC at a second scheduling position from the SSB. 13 . The wireless transmission / reception unit according to claim 11 , wherein the information is indicated via a physical broadcast channel (PBCH), a payload of the PBCH, and an initialization of a PBCH demodulation reference signal (DMRS) sequence.
14. The wireless transmit / receive unit according to claim 11, wherein the duration of the STTC is configured through radio resource control (RRC) signaling.
15. The wireless transmit / receive unit according to claim 13, wherein the processor is further configured to execute the following instructions: Receive the SSB index sent by the SSB in the STTC.
16. The wireless transmit / receive unit of claim 15, wherein the SSB index is based on one or more of a payload of a physical broadcast channel and a physical broadcast channel demodulation reference signal, and The processor is further configured to execute instructions for determining a radio frame boundary based on the offset and the SSB block index.
17. The wireless transmit / receive unit according to claim 13, wherein the STTC is fixed for an initial cell selection of the network node.
18. The wireless transmit / receive unit of claim 13, wherein the processor is further configured to execute instructions for determining a radio frame boundary based on the offset and an SSB block index.
19. The wireless transmit / receive unit of claim 13, wherein the available channels are in an unlicensed spectrum.
20. A method implemented by a wireless transmitting / receiving unit, the method comprising: Determine the length of the SSB transmission timing window, wherein under the condition that the SSB transmission timing configuration STTC is received from the network node, the length of the SSB transmission timing window is determined based on the received STTC, and under the condition that the STTC is not received from the network node, the SSB transmission timing window is determined to be a predefined length of 5 ms; According to the SSB sending timing window, the SSB is monitored based on the STTC; receiving at least one SSB in the SSB transmission timing window; Receive physical broadcast channel PBCH demodulation reference signal DMRS and PBCH payload; Determine an offset based on the PBCH DMRS and the PBCH payload; and The frame boundary is determined based on information indicating the offset of the received SSB.
21. The method according to claim 20, further comprising: A second SSB in the STTC at a second scheduling position is determined from the SSB.
22. The method according to claim 20, wherein the information is indicated via a physical broadcast channel (PBCH), a payload of the PBCH, and an initialization of a PBCH demodulation reference signal (DMRS) sequence.
23. The method according to claim 20, wherein the duration of the STTC is configured through radio resource control (RRC) signaling.
24. The method of claim 22, further comprising: Receive the SSB index sent by the SSB in the STTC.
25. The method of claim 24, wherein the SSB index is based on one or more of a payload of a physical broadcast channel and a physical broadcast channel demodulation reference signal, and the method further comprises: A radio frame boundary is determined based on the offset and the SSB block index.
26. The method of claim 22, wherein the STTC is fixed for initial cell selection by the network node.
27. The method of claim 22, further comprising: A radio frame boundary is determined based on the offset and the SSB block index.
28. The method of claim 22, wherein the available channels are in an unlicensed spectrum.
29. A wireless transmit / receive unit WTRU, comprising: A processor and a memory, wherein the processor and the memory are configured to: Determine the length of the SSB transmission timing window, wherein under the condition that the SSB transmission timing configuration STTC is received from the network node, the length of the SSB transmission timing window is determined based on the received STTC, and under the condition that the STTC is not received from the network node, the SSB transmission timing window is determined to be a predefined length of 5 ms; According to the SSB sending timing window, the SSB is monitored based on the STTC; receiving at least one SSB in the SSB transmission timing window; Receive physical broadcast channel PBCH demodulation reference signal DMRS and PBCH payload; Determine an offset based on the PBCH DMRS and the PBCH payload; and The frame boundary is determined based on information indicating the offset of the received SSB.
30. The WTRU of claim 29, wherein the information is indicated via a physical broadcast channel (PBCH), a payload of the PBCH, and an initialization of a PBCH demodulation reference signal (DMRS) sequence.
31. A wireless transmit / receive unit WTRU, comprising a processor and a memory, wherein the processor and the memory are configured to: Receive SSB block index and offset; Determining a frame boundary based on information indicating an offset and an SSB block index, wherein the offset is indicated by applying a first mask to cyclic redundancy check (CRC) bits of a PBCH payload; and The PBCH payload is decoded and a second mask is applied to the CRC.
32. A wireless transmit / receive unit WTRU, comprising a processor and a memory, wherein the processor and the memory are configured to: Receive SSB block index and offset; determining a frame boundary based on information indicating an offset and an SSB block index, wherein the offset is indicated by the remaining minimum system information RMSIPDCCH or RMSIPDSCH, and Send RMSIPDCCH or RMSIPDSCH associated with the SSB block index.
