TW201804844A - Systems and methods for synchronization, network information acquisition, and beam measurement in beam-centric networks - Google Patents

Abstract

Systems and methods for beam synchronization and/or network information acquisition are set forth. Beam synchronization and/or network information acquisition may be initiated by a beam (e.g., by a base station via a beam) and/or by a wireless transmit/receive unit (WTRU). Beam synchronization may be periodic and/or aperiodic.

Description

Synchronization, network information acquisition and beam measurement system and method in beam-centered network

CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application Serial No. No. No. No. No

In next-generation mobile communication systems, applications using technologies such as Enhanced Mobile Broadband (eMBB), Large Scale Machine Type Communication (mMTC), and/or Ultra-Reliable Low Latency Communication (URLLC) can be supported. A wide range of spectrum bands can be used in any of a variety of deployment scenarios, such as bands ranging from 700 MHz to 80 GHz or any subset thereof. In this deployment scenario, one or both of the licensed and unlicensed spectrums can be used. In next generation mobile communication systems, it may be desirable to, for example, minimize the presence of always-on signals and/or adapt to the beamforming network architecture.

Systems and methods for beam synchronization are disclosed. A WTRU may receive the beam, determine if the signal is in the beam, and transmit a request for the signal to the base station. The request may include an indication of the beam and an indication of the signal characteristics. Determining whether the signal is in the beam may include determining that the beam component of the beam is signaled to the WTRU, determining the beam type of the beam, and/or determining the beam component of the beam. The beam component can be a sync component, a broadcast component, and/or a reference component. The signal characteristics can be synchronization features, broadcast features, measurement reference signal (MRS) features, and/or combinations of these features. A base station that such a WTRU may communicate may include one or more next generation Node Bs (gNBs).

The illustrative examples are described in detail below with reference to the various drawings. While the present invention provides a detailed example of possible implementations, it should be noted that these examples are intended to be non-limiting examples and are not intended to limit the scope of the invention in any way.

FIG. 1A is a diagram of an example communication system 100 in which one or more of the disclosed examples can be implemented. Communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. Communication system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA). Single carrier FDMA (SC-FDMA) and the like.

As shown in FIG. 1A, communication system 100 can include a wireless transmit/receive unit (WTRU), such as WTRUs 102a, 102b, 102c and/or 102d (generally or collectively referred to as WTRU 102), a radio access network (RAN) 103. /104/105, core network 106/107/109, public switched telephone network (PSTN) 108, internet 110 and other networks 112, but it will be understood that the disclosed examples encompass any number of WTRUs, bases Taiwan, network and/or network components. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in wireless communication. As an example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals, and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, individuals Digital assistants (PDAs), smart phones, laptops, small laptops, personal computers, wireless sensors, consumer electronics, and more.

The communication system 100 can also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b can be configured to have a wireless interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (eg, core network 106/ Any type of device of 107/109, Internet 110, and/or network 112). For example, the base stations 114a, 114b may be base transceiver stations (BTS), node B, eNodeB, home node B, home eNodeB, website controller, access point (AP), wireless router, next generation node B (gNB) and so on. Although base stations 114a, 114b are each depicted as a single component, it will be understood that base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 103/104/105, which may also include other bases such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. Station and/or network elements (not shown). Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown). Cells can also be divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Thus, in some examples, base station 114a may include three transceivers, such as one for each sector of the cell. In another example, base station 114a may use multiple input multiple output (MIMO) technology, and thus multiple transceivers may be used for each sector of a cell.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via the null planes 115/116/117, which may be any suitable wireless communication link ( For example, radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The null intermediaries 115/116/117 can be established using any suitable radio access technology (RAT).

More specifically, as previously discussed, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 103/104/105 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA ( WCDMA) to establish an empty intermediate plane 115/116/117. 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).

In another example, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or Advanced LTE (LTE-A) to establish an empty intermediate plane 115/116/117.

In other examples, base station 114a and WTRUs 102a, 102b, 102c may implement such as IEEE 802.16 (eg, Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1x, CDMA2000 EV-DO, Temporary Standard 2000 (IS-2000). , Temporary Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate Evolution (EDGE) for GSM, Radio Technology such as GSM EDGE (GERAN) .

For example, the base station 114b in FIG. 1A can be a wireless router, a home Node B, a home eNodeB, or an access point, and any suitable RAT can be used for facilitating in, for example, a business location, a home, a vehicle. Wireless connection to a local area such as a campus. In some examples, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another example, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, base station 114b and WTRUs 102c, 102d may use cell-based RATs (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish picocells or femtocells ( Femtocell). As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Therefore, the base station 114b does not have to access the Internet 110 via the core network 106/107/109.

The RAN 103/104/105 can communicate with a core network 106/107/109, which can be configured to provide voice, data, application, and/or Voice over Internet Protocol (VoIP) services to the WTRU 102a. Any type of network of one or more of 102b, 102c, 102d. For example, the core network 106/107/109 can provide call control, billing services, mobile location based services, prepaid calling, internet connectivity, video distribution, etc., and/or perform advanced security functions such as users. verification. Although not shown in FIG. 1A, it is to be understood that the RAN 103/104/105 and/or the core network 106/107/109 may communicate directly or indirectly with other RANs, which may be used with the RAN 103/ 104/105 the same RAT or a different RAT. For example, in addition to being connected to the RAN 103/104/105, which may employ E-UTRA radio technology, the core network 106/107/109 may also be in communication with another RAN (not shown) that uses the GSM radio technology.

The core network 106/107/109 can also be used 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). Internet 110 may include a global system of interconnected computer networks and devices that use a common communication protocol such as TCP in a Transmission Control Protocol (TCP)/Internet Protocol (IP) Internet Protocol Suite, User Profile Agreement (UDP) and IP. Network 112 may include a wired or wireless communication network that is owned and/or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs that may use the same RAT as RAN 103/104/105 or a different RAT.

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 may be configured to communicate with different wireless networks over different wireless links. Multiple transceivers for communication. For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that uses a cell-based radio technology and with a base station 114b that uses an IEEE 802 radio technology.

FIG. 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, global positioning system (GPS) chipset 136, and other peripheral devices 138. It is to be understood that the WTRU 102 may include any sub-combination of the above-described elements while remaining consistent with the examples. Moreover, the examples encompass nodes represented by base stations 114a and 114b and/or base stations 114a and 114b (such as, but not limited to, transceiver stations (BTS), Node B, website controllers, access points (APs), home node B Evolved Home Node B (eNode B), Home Evolved Node B (HeNB or HeNodeB), Home Evolved Node B Gateway and Proxy Node, etc.) may include those described in FIG. 1B and described herein. Some or all of the components.

The processor 118 can 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 the DSP core, a controller, Microcontrollers, Dedicated Integrated Circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), state machine, etc. The processor 118 can perform signal encoding, 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 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although processor 118 and transceiver 120 are depicted in FIG. 1B as separate components, it will be appreciated that processor 118 and transceiver 120 can be integrated together into an electronic package or wafer.

The transmit/receive element 122 can be configured to transmit signals to or from the base station (e.g., base station 114a) via the null planes 115/116/117. For example, in some examples, transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another example, the transmit/receive element 122 can be a transmitter/detector configured to transmit and/or receive, for example, IR, UV, or visible light signals. In yet another example, the transmit/receive element 122 can be configured to transmit and receive both RF signals and optical signals. It is to be understood that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Moreover, although the transmit/receive element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in some examples, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the null intermediaries 115/116/117.

The transceiver 120 can be configured to modulate signals that can be transmitted by the transmit/receive element 122 and is configured to demodulate signals that are receivable by the transmit/receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), And user input data can be received from speaker/microphone 124, keypad 126, and/or display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 can also output user profiles to the speaker/microphone 124, the keypad 126, and/or the display/trackpad 128. In addition, processor 118 can access information from any type of suitable memory and store the data in any type of suitable memory, such as non-removable memory 130 and/or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other examples, processor 118 may access data from memory that is not physically located on WTRU 102, such as a server or a home computer (not shown), and store data in the memory.

The processor 118 can receive power from the power source 134 and can be configured to distribute power to other components in the WTRU 102 and/or to control power to other elements in the WTRU 102. Power source 134 can be any device suitable for powering WTRU 102. For example, the power source 134 may include one or more dry cells (nickel cadmium (NiCd), nickel zinc (NiZn), nickel hydrogen (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to a GPS chipset 136 that may be configured to provide location information (eg, longitude and latitude) regarding the current location of the WTRU 102. The WTRU 102 may receive location information from or to replace the GPS chipset 136 information from the base station (e.g., base station 114a, 114b) via the nulling plane 115/116/117, and/or based on two or more neighboring bases. The timing of the signal received by the station determines its position. It is to be understood that the WTRU 102 can obtain location information by any suitable location determination implementation while remaining consistent with the examples.

The processor 118 can also be coupled to other peripheral devices 138, which can include one or more software and/or hardware modules that provide additional features, functionality, and/or wireless or wired connections. For example, peripheral device 138 may include an accelerometer, an electronic compass (e-compass), a satellite transceiver, a digital camera (for photo or video), a universal serial bus (USB) port, a vibrating device, a television transceiver, and a hands free Headphones, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, Internet browsers, and more.

Figure 1C is a system diagram of the RAN 103 and core network 106 in accordance with the illustrated example. As described above, the RAN 103 can communicate with the WTRUs 102a, 102b, 102c over the null plane 115 using UTRA radio technology. The RAN 103 can also communicate with the core network 106. As shown in FIG. 1C, RAN 103 may include Node Bs 140a, 140b, 140c, where Node Bs 140a, 140b, 140c may each include one or more of communicating with WTRUs 102a, 102b, 102c over null intermediaries 115 transceiver. Each of the Node Bs 140a, 140b, 140c can be associated with a special unit (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It should be understood that the RAN 103 may include any number of Node Bs and RNCs while remaining consistent with the examples.

As shown in FIG. 1C, Node Bs 140a, 140b can communicate with RNC 142a. Additionally, Node B 140c can communicate with RNC 142b. Node Bs 140a, 140b, 140c can communicate with corresponding RNCs 142a, 142b via the Iub interface. The RNCs 142a, 142b can communicate with each other through the Iur interface. Each of the RNCs 142a, 142b can be configured to control a corresponding Node B 140a, 140b, 140c to which it is connected. In addition, each of the RNCs 142a, 142b can be configured to implement or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc. Wait.

The core network 106 shown in FIG. 1C 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. While each of the above elements is described as being part of the core network 106, it should be understood that any of these elements may be owned and/or operated by entities other than the core network operator.

The RNC 142a in the RAN 103 can be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 can be connected to the MGW 144. MSC 146 and MGW 144 may provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices.

The RNC 142a in the RAN 103 can also be connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 can be connected to the GGSN 150. The SGSN 148 and GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to a packet switched network (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and the IP enabled devices.

As noted above, the core network 106 can also be connected to other networks 112, where the other networks 112 can include other wired or wireless networks that are owned and/or operated by other service providers.

FIG. 1D is a system diagram of the RAN 104 and core network 107 according to an example. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c over the null plane 116 using E-UTRA radio technology. The RAN 104 can also communicate with the core network 107.

The RAN 104 may include eNodeBs 160a, 160b, 160c, although it should be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with the examples. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers that communicate with the WTRUs 102a, 102b, 102c over the null plane 116. In some examples, eNodeBs 160a, 160b, 160c may use MIMO technology. Thus, for example, the eNodeB 160a can use multiple antennas to transmit wireless signals to and receive wireless information from the WTRU 102a.

Each of the eNodeBs 160a, 160b, 160c may be associated with a special cell (not shown) and may be configured to handle radio resource management in uplink (UL) and/or downlink (DL) Decisions, handover decisions, user schedules, and more. As shown in FIG. 1D, the eNodeBs 160a, 160b, 160c can communicate with each other through the X2 interface.

The core network 107 shown in FIG. 1D may include an active management gateway (MME) 162, a service gateway 164, and a packet data network (PDN) gateway 166. While each of the above elements is described as being part of core network 107, it should be understood that any of these elements can be owned and/or operated by entities other than the core network operator.

The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 through the S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating the users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular service gateway during initial attachment of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide control plane functionality for handover between the RAN 104 and a RAN (not shown) that uses other radio technologies, such as GSM or WCDMA.

Service gateway 164 may be connected to each of eNodeBs 160a, 160b, 160c in RAN 104 via an S1 interface. The service gateway 164 can typically route and forward user data packets to the WTRUs 102a, 102b, 102c, or route and forward user data packets from the WTRUs 102a, 102b, 102c. The service gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when the downlink data is available to the WTRUs 102a, 102b, 102c, managing and storing context for the WTRUs 102a, 102b, 102c and many more.

The service gateway 164 may also be connected to a PDN gateway 166 that may provide the WTRUs 102a, 102b, 102c with access to a packet switched network (e.g., the Internet 110) to facilitate the WTRUs 102a, 102b. Communication between 102c and the IP enabling device.

The core network 107 can facilitate communication with other networks. For example, core network 107 may provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, core network 107 may include or may be in communication with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that interfaces between core network 107 and PSTN 108. In addition, core network 107 can provide WTRUs 102a, 102b, 102c with access to network 112, which can include other wired or wireless networks that are owned and/or operated by other service providers.

Figure 1E is a system diagram of the RAN 105 and core network 109 according to an example. The RAN 105 may be an Access Service Network (ASN) that communicates with the WTRUs 102a, 102b, 102c over the null plane 117 using an IEEE 802.16 radio technology. As will be discussed further below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, RAN 105, and core network 109 may be defined as reference points.

As shown in FIG. 1E, the RAN 105 may include base stations 180a, 180b, 180c and ASN gateway 182, although it should be understood that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the examples. . Each of the base stations 180a, 180b, 180c can be associated with a particular cell (not shown) in the RAN 105, and each can include one or more of communicating with the WTRUs 102a, 102b, 102c over the null plane 117. Transceivers. In some examples, base stations 180a, 180b, 180c may use MIMO technology. Thus, for example, base station 180a can use multiple antennas to transmit wireless signals to, and receive wireless signals from, WTRU 102a. 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 can act as a traffic aggregation point and can be responsible for paging the user profile cache, routing to the core network 109, and the like.

The null interfacing plane 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an Rl reference point that implements the IEEE 802.16 specification. Additionally, each of the WTRUs 102a, 102b, 102c can 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 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and/or mobility management.

The communication link between each of the base stations 180a, 180b, 180c can be defined as an R8 reference point that includes a protocol for facilitating WTRU handover and data transfer between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point. The R6 reference point may include an agreement for facilitating action management based on action events associated with each of the WTRUs 102a, 102b, 102c.

As shown in FIG. 1E, the RAN 105 can be connected to the core network 109. The communication link between the RAN 105 and the core network 109 can be defined, for example, as an R3 reference point that includes protocols for facilitating data transfer and action 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 is described as being part of core network 109, it should be understood that any of these elements can be owned and/or operated by entities other than the core network operator.

The MIP-HA may be responsible for IP address management and may cause the WTRUs 102a, 102b, 102c to roam between different ASNs and/or different core networks. The MIP-HA 184 can provide the WTRUs 102a, 102b, 102c with access to a packet switched network (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 can be responsible for user authentication and support for user services. Gateway 188 can facilitate interworking with other networks. For example, gateway 188 can provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices. In addition, gateway 188 can provide access to network 112 to WTRUs 102a, 102b, 102c, which can include other wired or wireless networks that are owned and/or operated by other service providers.

Although not shown in FIG. 1E, the RAN 105 can be connected to other ASNs and the core network 109 can be connected to other core networks. The communication link between the RAN 105 and other ASNs may be defined as an R4 reference point, which may include an agreement for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and other ASNs. The communication link between the core network 109 and other core networks may be defined as an R5 reference point (not shown), which may be included to facilitate the connection between the local core network and the visited core network. Agreement for interworking.

Multi-antenna techniques such as Multiple Input Multiple Output (MIMO) transmission, Single Input Multiple Output (SIMO), and Multiple Input Single Output (MISO) techniques can be used in telecommunications systems (eg, sub-6 GHz transmissions). Different MIMO technologies can provide different advantages, such as diversity gain, multiplex gain, beamforming, array gain, and the like. In a system in which one or more user terminals (UTs) communicate with a central node, the use of multi-user MIMO (MU-MIMO) may for example facilitate the aggregation of identical and/or overlapping resources in the time and/or frequency domain. Multiple streams are streamed to different UTs (eg, simultaneously) to increase system throughput. Using single-user MIMO (SU-MIMO) can facilitate the central node to stream multiple data streams to the same UT.

Since the propagation characteristics at millimeter wave frequencies are different compared to the propagation characteristics of the sub-6 GHz frequency, multi-antenna transmission at millimeter wave frequencies may be different from sub-6 GHz multi-antenna technology. Millimeter wave due to the possibility of a base station (eg, a base transceiver station (BTS) or gNB) and/or a WTRU with a limited number of radio frequency (RF) chains (eg, compared to the RF chain associated with the antenna elements) Multi-antenna transmission at frequencies may or may not be different from sub-6 GHz multi-antenna technology. The precoding at millimeter wave frequencies can be a mixture of digits, analogs, and/or digits and/or analogs.

Digital precoding can be accurate. Digital precoding can be combined with equalization. Digital precoding can be enabled for single user (SU), multi-user (MU), and/or multi-element precoding. Digital precoding is similar to precoding that can be used in systems that support sub-6 GHz transmission, such as IEEE 802.11n systems, 3GPP LTE systems, and other systems that may be more advanced than IEEE 802.11n systems and 3GPP LTE systems. In millimeter wave frequencies, the presence of a limited number of RF chains (e.g., as compared to RF chains associated with antenna elements) and/or the sparse nature of the channels may increase the complexity of using digital beamforming.

Analog Beamforming Overcoming the limitations associated with a limited number of RF chains available in millimeter wave frequencies can be overcome by using one or more analog phase shifters on the antenna elements (e.g., on each antenna element). One or more analog phase shifters may be used in an IEEE 802.11ad system, for example, during a sector level scanning procedure (eg, which may identify a "best" sector), during a beam refinement process (eg, it may be fine During the period of the antenna beam and/or during the beam tracking process (eg, it may adjust one or more sub-beams over time to accommodate changes in the channel).

In an example, analog beamforming can be used in an IEEE 802.15.3 system. A binary search beam training algorithm that can use a layered multi-resolution beamforming codebook can be used. Analog beamforming can be limited to single stream transmission.

In the hybrid beamforming paradigm, the precoder can be divided between an analog domain and a digital domain. Each such domain has an associated precoding and/or combining matrix each having a different structural constraint, such as a constant modulus constraint for a combining matrix in the analog domain. An example of a hybrid beamforming design can represent a compromise between hardware complexity and system performance. For example, hybrid beamforming can achieve digital precoding performance due to the sparse nature of the channel and/or due to support for multiple users and/or multiple streams of multiplexing. Hybrid beamforming may be limited by the number of RF chains. In millimeter wave systems, a limited number of RF chains may not be a problem because millimeter wave channels may be sparse in the angular domain.

Systems using higher frequency bands can be designed to accommodate the propagation characteristics of such higher frequency bands. As the frequency increases, such as due to walls and/or objects, the channel may experience higher path loss and/or a more abrupt change in the average signal level. Successful transmission through the object may be reduced and the reflection may be amplified.

Beamforming (eg, analog, digital, hybrid) can assist in overcoming the path loss and/or penetration loss of some or all of the channels (eg, not only the data channels). The network design can be a beam-centric design (eg, relative to cell-based design). In a beam-centric design, coverage can be provided by a beam (e.g., as opposed to a cell). In a beam-centric design, one or more channels and/or signals may be beamformed. To ensure a uniform network design at some or all frequencies, a beam-centric design can be used at lower frequencies, where, for example, the beam may be as wide as the sector.

In a beam-centric network, one or more WTRUs that may not be connected to the network may be associated with one or more beams. The messaging can be used to facilitate one or more of the following: synchronization, beam acquisition, beam identification, and/or acquisition of network information to facilitate association of such one or more WTRUs with one or more beams. Such one or more beams may be self-contained, may be standalone beams, and/or may be aggregated beams.

Self-contained transmissions from different beams can be separated. Such transmissions can come from different physical base stations. In a beam-centric network, one or more WTRUs may each be associated with multiple beams. Such one or more WTRUs may receive simultaneous transmissions from two or more independent beams (eg, where each of these independent beams may be from one or more base stations). The example methods and systems can facilitate separating information received from each of the plurality of independent beams at the WTRU.

Figure 2 shows an example scenario 200 using beam-centric communication. For the purposes of the example, beam-centric communication is overlaid on a cell-centric system. Cells 211, 212, 213 may represent cells that may be implemented in a cell-centric system (shown in shaded hexagons). Each of the base stations 221, 222, 223 can transmit four beams (shown in short dashed lines). The centrally located base station 231 can transmit twelve beams (indicated by long dashed lines).

A beam-centric architecture can be implemented on the communication system. In such a system, a WTRU may be associated with a set of beams. Each beam in such a set can be formed on the same base station or on a different base station. In an example system, a WTRU may connect to a base station that is geographically further than another base station. For example, if a beam from a geographically farther base station may be stronger than a beam from a geographically closer base station, such a WTRU may be connected to a geographically farther base station.

FIG. 3 illustrates an example scenario 300 in which the WTRU 310 receives a control beam 320 from a base station 325 and receives a control beam 330 from a base station 335. Base station 335 can be geographically closer to WTRU 310 than base station 325. Control beam 320 may be stronger than control beam 330, although base station 335 is geographically closer to WTRU 310 than base station 325. The WTRU 310 may be connected to a base station with a stronger signal regardless of the geographic distance from the associated base station. For example, the WTRU 310 may be connected to the base station 325 because the beam 320 may be stronger than the beam 330 even though the base station 335 is geographically closer to the WTRU 310 than the base station 325.

The channels and/or signals can be beamformed. The beams used for such channels and/or signals may be self-contained beams, self-contained beams, and/or aggregated beams. The self-contained and/or self-contained beam may comprise a single beam having one or more beamformed synchronization channels, beamformed broadcast channels, beamformed downlink/uplink data channels, and/or beamformed downlinks / Winding control channel.

Multiple aggregated beams can transmit a subset of the available channels. For example, multiple aggregated beams can be transmitted by one or more base stations. The aggregation channels can be separated by direction, beamwidth, frequency, and/or power. The aggregation channels may also or instead be separated by the channel type and/or the type of signal each of the aggregation channels is allowed to carry.

Figure 4 shows an example scenario 400 in which the aggregated beams can be separated by beamwidth. Beam 430 may be a control beam transmitted by base station 425. Data beam 440 may also be transmitted by base station 425. The WTRU 410 may receive one or both of the beams 430 and 440. Control beam 430 can be transmitted using a different beamwidth than the beamwidth used to transmit data beam 440.

Figure 5 shows an example scenario 500 in which the aggregated beams can be separated by frequency. Beam 530 may be a control beam transmitted by base station 525. Data beam 540 can also be transmitted by base station 525. The WTRU 510 can receive one or both of the beams 530 and 540. Control beam 530 can be transmitted using a first frequency that is different than the frequency used to transmit data beam 540.

Figure 6 shows an example scenario 600 in which the control beam is transmitted by a different base station than the base station that may transmit the data beam. Beam 630 may be a data beam transmitted by base station 635. Beam 620 can be a control beam that can be transmitted by base station 625. The WTRU 610 may receive beams 620 and 630, such as base station 625 and base station 635, from different base stations.

The base station may transmit one or more main beams, which may include one or more beamformed synchronization channels, one or more beamformed broadcast channels, and/or one or more beamformed uplink/lower chain control channels . The base station may also or instead transmit one or more auxiliary beams, which may include one or more beamformed synchronization channels and/or one or more beamformed uplink/downlink data channels.

The main beam can be transmitted using a beamwidth greater than the beamwidth for one or more secondary beams. Using a larger beamwidth than the beamwidth for one or more auxiliary beams for the primary beam can facilitate a greater number of WTRUs decoding information and can prevent duplication.

Transmitting one or more aggregated auxiliary beams using a smaller beamwidth than the one used to transmit the main beam may increase the link budget and/or may facilitate direct target information transfer between the base station and the WTRU. The beam may be determined based on one or more network specific parameters and/or one or more WTRU specific parameters. In an example, a larger beamwidth beam may be determined based on one or more network specific parameters, while a smaller beamwidth beam may be determined based on one or more WTRU specific parameters.

The main beam may be transmitted at a lower frequency than one or more associated auxiliary beams, for example, to reduce the effects of propagation loss and/or to ensure that the link budget can be turned off using less beamforming. For example, beamformers with lower gains (eg, beamformers with wider beamwidths) may be used due to operation at lower frequencies and/or to meet link budgets for transmission. For example, where there is more bandwidth and/or less interference, one or more aggregated auxiliary beams may be transmitted at a higher frequency relative to the main beam.

The transmission can be beam based. The aggregated beam can be (eg, physically) located at another base station. The loadback between multiple base stations can be used or not used. The use of backloading may depend, for example, on the particular transmission scheme that may be used.

In an example, a WTRU may be associated with multiple beams simultaneously and/or connected to multiple beams. The beam associated with the WTRU may be a beam with which the WTRU may be synchronized and/or a beam that the WTRU may be monitoring. The connected beam can be a beam that the WTRU can decode. The connected beam may be a beam with which the WRTU may be synchronized and/or may be a beam with a broadcast channel that the WTRU may have decoded. The WRTU may be capable of transmitting and/or receiving data on the connected beams. The interaction of the beams at the WTRU (e.g., the WTRU at the boundary) may use more management resources than the resources used for the interaction of the beams at the cell boundaries. The WTRU and/or base station may determine beam handover (e.g., in an active scenario) and/or may determine whether to use multi-beam and/or multi-string streaming.

The WTRU may seamlessly hand over between beams in an environment that may be active and/or changing, such as by allowing multiple associated beams. Such a WTRU may hand over from one discrete beam to another discrete beam. Such a WTRU may aggregate multiple beams, for example, where each such aggregated beam may have a relatively large beamwidth and/or a relatively low frequency beam that may be used as an anchor beam. Such an anchor beam may be a beam to which one or more WRTUs may be connected, and in some examples may be always connected. For example, one or more WRTUs can be connected to the base station via an anchor beam. The WTRU may use one or more beamwidth beams and/or one or more high frequency beams to provide data transmission (eg, high throughput data transmission) and/or as a layer of action (eg, in order for the WRTU to act within the system) When promoting high throughput connections).

The WTRU may acquire, determine, and/or store a list (and/or indication thereof) of candidate beams that the WTRU uses for handover. In some examples, such a WTRU may continuously monitor the strength of each candidate beam. Such WTRUs can use this strength information in a variety of ways. For example, such a WTRU may switch beams (eg, autonomously) based on its own determination. Alternatively or additionally, such a WTRU may send a list and/or information of candidate beams associated with such candidate beams to, for example, an anchor that may provide such a list and/or information to one or more anchor beam engineers Beam (for example, to the base station). This information can be used to determine whether to switch the beam and, if a handover is determined, to determine the beam to switch to.

The network (e.g., base station) can switch beams, e.g., based on a list of candidate beams and/or candidate beam information (e.g., candidate beam strength information). For example, an anchor beam in a beam-centric network can act as a base station operating in a beam-centric network. The handover can be a soft handover or a hard handover. In hard handoff, the WTRU may drop one beam when it picks up another beam. In soft handoff, the WTRU may connect to multiple beams simultaneously, and for example, switch between beams without dropping the beam, and may reduce the chance of dropping the call.

The WTRU or base station may determine to use multiple beams and/or multiple streams of transmission. A beam-centric network can facilitate multiple streams of multiple beams and/or multiple beams from multiple beams. For example, the beams may be independent and/or self-contained, and the WTRU may have each of such beams that are scheduled independently by the base station or jointly scheduled by multiple base stations. Beams can be gathered. A beam such as one of a set of aggregated beams can be used as a control beam. Such control beams may indicate resources on other beams that may be used by the WTRU (eg, for uplink/downlink transmission).

The WTRU may measure the active channel (e.g., in the uplink) and/or from (e.g., in the downlink) to, for example, perform beam tracking for handover and/or multi-beam transmission. The Sounding Reference Signal (SRS) may be transmitted by the WTRU to the base station, such as in the uplink. The location, granularity, and/or periodicity of the SRS can be determined and/or set to limit the burden and/or limit interference to other beams in one or more networks. A beam reference signal (BRS) and/or a measurement reference signal (MRS) may be transmitted from the beam in the downlink to one or more WTRUs associated with the beam. For example, the BRS can be periodically transmitted to one or more of the WTRUs in such a beam. The BRS can be transmitted to a particular WTRU.

The BRS can identify the quality of the channel and/or can be associated with a single stream. BRS can facilitate multiple streams and/or multiple measurements. The BRS and/or MRS may be selected from any reference signal associated with a particular beam-based channel, such as a reference signal associated with one or more of the following: a downlink NR-PDCCH, an NR broadcast channel And / or NR-PDSCH.

Beam identification (beam ID) can be assigned to a beam, such as each beam in the system. The beam ID can be independent of the physical array or base station. One or more WTRUs may be associated with one or more beams based on, for example, energy. A WTRU may be connected to multiple beams, for example, where the beams are transmitted from different base stations.

In an example, a hybrid beam ID/cell ID tag can be implemented. In an example, the beam ID can be identified in addition to the identification of the cell ID of the physical array or base station. In an example, the process can be part of a phase of a new radio (NR) normalization process (eg, the first phase).

The WTRU synchronization may use acquisition of time, frequency, and/or beam (e.g., spatial direction). A beam-specific synchronization sequence and/or a set of synchronization sequences can be assigned to the beam (e.g., each beam). A WTRU that detects an available signal can synchronize with a signal and/or a group of signals. Such a WTRU may acquire timing and/or frequency synchronization (e.g., based on a synchronization process) and/or may transmit a signal and/or a beam ID of a beam of the set of signals.

Synchronization and/or network acquisition may be performed using, for example, periodic beam synchronization using broadcast channels and/or beam initiated network information acquisition. Synchronization and/or network acquisition may be performed using aperiodic and/or random beam synchronization and/or beam initiated network information acquisition. Synchronization and/or network acquisition may be performed using beam initiated synchronization of network information acquisition initiated by the WTRU. Synchronization and/or network acquisition may be performed using WTRU-initiated synchronization with WTRU-initiated network information acquisition.

The base station may be scanned by a beam (e.g., periodically) such that one or more WTRUs that may not have been connected to the network are synchronized with such a network. For example, the base station can use synchronization sequences and/or measurements of such networks using BRS to facilitate such WTRU-to-network connections.

For synchronization, one or more WTRUs may configure their respective receive antennas to use a maximum beamwidth (eg, an omin beam pattern or a quasi-full beam pattern). Once the beam has been identified, such one or more WTRUs may further refine the beamwidth of their respective receive antennas. For beam measurements, such one or more WTRUs may utilize the received antenna pattern.

In the case where periodic beam-initiated synchronization may be in use, or may be in the case of periodic BRS, one or more synchronization signals and/or BRS may be transmitted regardless of whether there is data to be transmitted.

Figure 7 shows a scenario 700 in which N beams can be transmitted by each transmission point of the exemplary network. Each beam (eg, each of beams 1-N) may include one or more beam synchronization sequences.

The period and/or frequency of one or more beam scans may be based on the network and/or may be based on or associated with one or more features. Such features may include the period and/or frequency of the beam scan, which may occur at network reservation intervals that are separated by data transmission. FIG. 8 illustrates an exemplary scenario 800 in which synchronization and broadcast signals may be transmitted in a reserved time interval 810 and data transmissions may be transmitted in time interval 820. Such an interval can be determined statically or dynamically. For example, the static interval can be based on criteria, and/or the dynamic interval can be based on a process or algorithm as set forth in the standard. In other examples, the interval may be static and/or dynamic based on the system burden. Intervals can be determined statically and/or dynamically using any criteria, and all such standards are encompassed within the scope of the present disclosure.

The beams can be packetized and/or transmitted together. FIG. 9 illustrates an exemplary scenario 900 in which a BRS and/or synchronization signal may be transmitted in a reserved time interval 910 at intervals of data transmissions transmitted in interval 920. The base station can simultaneously form multiple beams, and the synchronization signals and/or BRS (e.g., BRS and/or synchronization signals in interval 910) can be transmitted simultaneously.

Signals of one or more beams can be transmitted separately. Figure 10 shows an exemplary scenario 1000 in which the signals for each beam can be transmitted separately. As shown in FIG. 10, the signal for each of the beams 1, 2, 3, 4 can be transmitted in interval 1010 along with the data transmission transmitted at interval 1020. In an example, any beam (eg, any of beams 1, 2, 3, 4 in FIG. 10) may be used during a data interval (eg, any of the data intervals 1020 in FIG. 10). In one example, the messaging can be transmitted simultaneously with the data transmission. In an example (eg, as shown in FIG. 10), periodic restrictions may require periodic data accesses on the beam.

The period and frequency of one or more beam sweeps can be coordinated between multiple physical base stations, which can reduce interference due to overlapping beams. One or more beam scans may be transmitted with additional beamformed channels, and/or such beam scans may be sent even when no additional beamformed channels are transmitted. One or more beam scans can be transmitted independently on each aggregated beam. One or more beam scans can be sent on a single beam for all aggregated beams. The number of beams and beamwidth can be based on a standardized set of beams. Alternatively, the number of beams and beamwidth may depend on the implementation.

Figure 11 shows an exemplary scenario 1100 with four beams. At each of the intervals 1101, 1102, 1103, 1104, periodic synchronization may occur for the respective beams (eg, b1, b2, b3, b4). Data transfer can occur at any of the data intervals 1120. Scenario 1100 shows an example of using a separate periodic synchronization channel/BRS. In scenario 1100, data transfer latency can be reduced. In scenario 1100, the channel acquisition latency can be increased. Any beam can be used during the data interval (eg, data interval 1120).

Messaging can occur simultaneously with data transfer. Periodic restrictions may cause data access on the beam to occur periodically. FIG. 12 illustrates an example scenario 1200 showing an interval 1210 that may include one or more of periodic synchronization, broadcast, and/or data transmission. For example, to reduce interference due to overlapping beams, the period and/or frequency of beam scanning can be coordinated between multiple physical base stations. The period and/or frequency of the beam scan can be sent with additional beamformed channels. The period and/or frequency of the beam scan can be transmitted, for example when no additional beamformed channels are to be transmitted.

The period and/or frequency of the beam scan may be transmitted independently on each of the one or more beams of a set of aggregated beams. The period and/or frequency of the beam scan may be transmitted on a single beam for one or more of the set of aggregated beams. The number of beams and/or beamwidth may be based on a set of beams (eg, a standardized set of beams). The number of beams and/or beamwidth may depend on the implementation.

The base station can transmit each beam sequentially. The base station can transmit one or more beams in parallel. The base station can transmit beam groups sequentially. Multiple sync/BRS processes can be set at the same time, for example, in the example of using group signal/beam transmission. Signal transmissions (such as dedicated signals) can be interleaved to reduce data transmission latency.

An exemplary scenario 1300 is shown in FIG. 13 showing four example beams and/or four example signal processes. As shown in FIG. 13, the dedicated signals 1301, 1302, 1303, 1304 may be interleaved. In the example, as a result of the interleaving of the signals 1301, 1302, 1303, 1304, the data intervals 1311, 1312, 1313, 1314 may be interleaved. of.

The network may classify one or more beams as idle beams (eg, beams of WTRUs that do not have synchronization and/or connectivity) or connected beams (eg, in such a manner that the WTRU is capable of transmitting and/or receiving data) Or multiple WTRUs perform synchronization and/or connected beams). The connected beams may transmit synchronization, broadcast, and/or BRS signals at periodic intervals that are different from the periodicity of the idle beams. Additional categories of beams can be defined (eg, beams that can be directed to a high mobility region rather than a low mobility region). Additional periodicity can be defined for the class of the beam. For example, a low (eg, relatively low) periodicity can be used to signal a high mobility beam with a signal.

The periodic beam processing and system may use transmission of at least one of a synchronization signal, a broadcast signal, and/or a BRS. In one example, the base station may transmit one or more synchronization signals and/or one or more BRSs in a non-periodic and/or random manner to reduce the amount of interference and/or increase the efficiency of the network. Transmitting one or more synchronization signals and/or BRSs in a non-periodic and/or random manner may reduce the amount of interference in the network and/or may increase the energy efficiency of the network.

In an example, the base station may simultaneously transmit one or more synchronization sequences and/or BRSs with the transmitted schedule data and/or one or more control beams. A WTRU located within the beamwidth of a data transmission may acquire and/or measure a beam.

Figure 14 shows an exemplary scenario 1400 showing an example of aperiodic synchronous messaging. Beams 1, 2, 1 in scan 1, beam 2, 2, 1 in scan 2 and/or beams 4, 2, 4 in scan 3 can be transmitted with the beamformed data. The beams 3, 4 in scan 1, the beams 3, 4 in scan 2, and the beams 1, 3 in scan 3 can be transmitted without data.

In an example where the data may not be scheduled in the beam, an unconnected WTRU (eg, may wish to connect) may not be able to connect to the beam. In an example, beams transmitted from various different base stations may overlap and may provide an improved opportunity for such unconnected WTRUs to connect to the beam. The base station may transmit one or more beams that may include one or more synchronization sequences and/or BRSs at certain points in time, for example, only (eg, without data and/or control beams) to facilitate the WTRU's service. Within the beamwidth of the beam.

Examples of systems and methods that can be used to schedule undocumented beams include periodic scheduling in which beams that may not be delivered can be transmitted after a period of time. Other examples include the use of a proportional fair approach in which the extent can be used to determine when each beam can be transmitted. Other examples include determining a scheduling priority based at least in part on one or more beam types that can be associated with each of the plurality of beams. Such beam types may be considered when determining scheduling priorities (eg, scheduled beams, beams that are connected but not scheduled, idle beams).

In an example where the data may not be scheduled in the beam, an unconnected WTRU (eg, may wish to connect) may not be able to connect to the beam. To address this situation, the base station can transmit one or more synchronization signals, each of which can use a relatively large beamwidth beam. Where the WTRU can connect to the base station and can feed back information to such a base station, the base station can schedule a smaller beamwidth beam that will be directed to the WTRU.

A connected WTRU looking to perform measurements on a beam may not be able to perform such measurements on such a beam. Various methods may be used to enable synchronization, network information acquisition (e.g., via broadcast channels) and/or measurements of WTRUs that may not be scheduled in the beam, e.g., in the absence of data on the beam, and/or beams It may not be a random schedule. These methods include the methods described herein.

Figure 15 shows an exemplary scenario 1500 representing example synchronization and/or network acquisition messaging, e.g., utilizing schedule data 1501 on connected beams. The non-scheduled beam may use the interval 1502 and may be transmitted periodically (eg, the beam size is not the same or variable).

Figure 16 shows an exemplary scenario 1600 of an exemplary use of a BRS that uses scheduled data on connected beams at intervals 1601. The non-scheduled beam may be transmitted periodically at interval 1602.

Figure 17 shows an exemplary scenario 1700 for exemplary use of random beamforming with data, broadcast, and/or synchronization signals, such as at interval 1701. Interval 1702 can be used for random broadcast and/or synchronous messaging.

Figure 18 shows an exemplary scenario 1800 in which random beamforming can be used with BRS for measurement. The interval 1801 can be used for random data and/or can be used for one or more BRSs, which in one example can be transmitted simultaneously with the data transmitted in the interval 1801. Interval 1802 can be used for BRS transmission.

Methods for synchronization, network information acquisition, data transmission, and/or channel measurement can be performed when one or more beams can be scheduled and/or transmitted. In an example, such a method can be similar to the periodic method as set forth herein. Alternatively or additionally, the base station may schedule one or more beams randomly or pseudo-randomly within the network and may transmit one or more synchronization signals, broadcast signals, and/or BRS signals.

The network may first schedule the beams using a periodic method (eg, as set forth herein). Such a network can then schedule the beams using aperiodic methods and/or random methods, such as when such networks become more populated.

A method of using beam-originated synchronization with a WTRU-initiated broadcast may be implemented in an example. In the aperiodic paradigm, broadcast channel information can be transmitted, regardless of whether such information is expected. For example, broadcast channel information can be transmitted regardless of whether there is a WTRU that can use such information for updates, associations, and/or profiles on a particular beam.

In an example, the base station can transmit synchronization information and/or broadcast information only to one or more connected beams. In an example, the BTA can transmit synchronization information and/or broadcast information to one or more connected beams that can be used to transmit beamformed channels (eg, data, control, etc.) and / Or it may be identified as having one or more WTRUs connected to one or more such beams.

The idle beam can be used to transmit one or more synchronization signals. In an example, the idle beam can be used to transmit one or more synchronization signals.

One or more connected beams may be used to transmit broadcast information (e.g., only when it is desired to communicate system information changes to one or more WTRUs). If the WTRU synchronizes to an updated beam that may not have broadcast information and/or may require system information for the network, the WTRU may explicitly (e.g., from the base station) request broadcast information associated with the beam.

The uplink random access channel can be monitored by the base station. Such a channel may be referred to as a beam-based random access channel (BBRACH). A WTRU may have little or no information about a system that may include BBRACH or no such information. Such a WTRU may select BBRACH based on energy detection and/or non-coherent detection of signals derived from the base station ID.

The BBRACH may have a fixed bandwidth, which in an example may correspond to a bandwidth associated with a Beam Primary Synchronization Sequence (BPSS) and/or a bandwidth associated with a Beam Assisted Synchronization Sequence (BSSS).

The BBRACH can be used as a signal communication channel and/or a contention channel that can provide the base station with the possibility that such a base station can transmit broadcast information on a beam (e.g., a particular beam). If such a base station receives a relatively large amount of energy (e.g., based on its ID) and/or positive detection on such a BBRACH, the base station may schedule the beam and/or may transmit broadcast information at the BBRACH.

The base station may transmit one or more synchronization signals on the beam of the WTRU that has no data and is not connected (e.g., only on the beam), which may enable the WTRU to synchronize with the associated channel. The WTRU may synchronize with the primary beam synchronization signal and the secondary beam synchronization signal.

Once it is determined that there may be no broadcast information, the WTRU may send a signal on the broadcast request random access channel. In a sample cycle scenario, such a signal can be located anywhere in the beam when such a beam returns. In an example aperiodic scenario, such a signal may be after the PSSS and/or the secondary synchronization sequence (SSS) and before the associated beam ends. In an example, if a base station receives a relatively large amount of energy (e.g., based on its ID) and/or positive detection on such a channel, the base station can schedule the beam and can transmit broadcast information on the channel. Otherwise, such a base station can act to the next beam in the beam sequence.

The uplink random access channel can be associated with a fixed set of parameters. Such parameters may include bandwidth, such as the bandwidth of BPSS and/or BSSS. The uplink random access channel can be used as a communication channel and/or a contention channel that can provide signals to the base station, which can enable such base stations to transmit broadcast information, for example, on a particular beam.

The beam can determine that it can send additional information (eg, instead of identifying a particular WTRU). The base station may schedule the beams and/or may transmit broadcast information on the channels, for example, if such base stations receive a relatively large amount of energy (e.g., beam-based ID) and/or positive detection on the channel. The WTRU may send a signal derived from the ID of the beam. If the beam receives a signal that may not be based on its ID, the beam can ignore the signal. Such a signal may not be used for this beam. If such a beam receives energy (eg, based on the ID of the beam), the base station can schedule the beam and/or transmit broadcast information on the channel.

The base station can transmit synchronization and/or broadcast information and/or BRS (eg, only) to the connected beams. Such connected beams may include one or more beams that may be used to transmit beamformed channels. Such channels may include, for example, data, control information, and the like. The beams thus connected may include one or more beams that may be identified as having one or more WTRUs connected to respective beams.

No information can be sent on the idle beam. The idle beam can be cycled through. For example, in the case of four beams, beam 1 and/or beam 2 may be connected, while beam 3 and/or beam 4 may not be connected. The base station may transmit synchronization information and/or broadcast information and/or BRS (eg, only) via beam 1 and/or beam 2. In an example, the base station may switch to beam 3 and/or beam 4 without transmitting synchronization information and/or broadcast information and/or BRS (eg, only) through beam 3 or beam 4. Beam 3 and/or beam 4 may be in a listening mode in which beam 3 and/or beam 4 is listening (eg, the base station is listening through beam 3 and/or beam 4) to determine (eg, any) whether the WTRU is transmitting information. If beam 3 and/or beam 4 receive energy, beam 3 and/or beam 4 may be activated and/or may be started (eg, by one or more base stations) for transmitting information/synchronization/BRS.

In an example, a primary beam synchronization signal (PBSS) (eg, PBSS only) may be transmitted on one or more idle beams. A beam with data (eg, a beam with only data) may have synchronization information and/or broadcast information and/or BRS. For idle beams, the WTRU may request signals (eg, auxiliary beam synchronization signals (SBSS), broadcast signals, and/or measurement signals) to be transmitted in the BBRACH. Identification of the BBRACH signal may result in the transmission of one or more (eg, three) signal types, such as those described herein.

The BBRACH signal can distinguish between multiple options, such as sending an SBSS signal (eg, transmitting only), transmitting a PBSS/SBSS/broadcast signal, and/or transmitting a BRS. Such BBRACH signals can distinguish between signal types such as the signal types set forth herein. The sequence can request the desired beam ID. The base station can respond with a synchronization sequence on the beam (e.g., on the appropriate beam).

The association with the beam may be based on the detection of the primary and/or principal beam synchronization sequences transmitted by the beam. Such a synchronization sequence can be used for timing detection and/or acquisition of an initial physical layer beam identifier.

The beam may also or alternatively emit an auxiliary beam synchronization sequence and/or a non-primary beam synchronization sequence. Auxiliary and/or non-primary beam synchronization sequences may be used for radio frame identification, full beam index identification, beam scanning sequence identification (eg, where the beam may be located in the beam scanning period), cyclic prefix length detection, and/or dual Type identification.

The position of the auxiliary beam synchronization sequence relative to the main beam synchronization sequence (eg, blindly) may be used to indicate the number of beams in the scan and/or the index of the periodicity and/or beam (eg, current beam) in the periodic beam scan. . The distance between the auxiliary beam synchronization sequence and the main beam synchronization sequence may be less than the coherence time, for example, allowing coherent detection of the auxiliary beam synchronization signal (SBSS).

The WTRU may identify the broadcast channel mode in which the beam is located, whereby the WTRU may not waste or waste relatively little power attempt to decode broadcast channels that may not be available. The WTRU may identify the broadcast channel mode in which the beam is located, whereby the WTRU may be aware of transmitting a signal to the BBRACH for requesting a broadcast channel from the beam.

When synchronizing, a broadcast channel can be used to send information to the WTRU (eg, higher priority information). Examples of higher priority information may include a frame number (eg, if not blindly acquired). A beam (e.g., each beam) may send to the WTRU (e.g., may be transmitted by the base station using a beam) a broadcast channel with associated information (e.g., send a separate broadcast channel with minimal correlation information to the WTRU).

The periodicity of the broadcast channel transmission may be different from the periodicity of the synchronization sequence. Figure 19 shows a scenario 1900 showing an example of periodic synchronization of broadcast network information with different periodicities. As shown in Fig. 19, each of the scans 1-6 may include N beams. Referring to the legend of Fig. 19, scan 1 and scan 4 of scenario 1900 may include beams that may contain synchronization information and broadcast information. Scans 2, 3, 5, and 6 may include, for example, beams that only contain synchronization information (eg, no broadcast information).

The information that can be transmitted in the broadcast channel can include one or more of the following: frame number (eg, if not blindly acquired), number of antennas, transmission bandwidth, one or more allowed beam aggregation types ( For example, beamwidth based, frequency based, etc.) and/or hybrid automatic repeat request (HARQ) channel types (eg, dedicated, instant, etc.).

For example, the WTRU may connect to the primary control beam when acquiring information in the broadcast channel. The beamformed control channel and/or data channel can be transmitted to/from the WTRU on the primary control beam. The beamformed control channel can be transmitted to/from the WTRU. The data channels may be transmitted to/from the WTRU on the aggregated beam in the same or different directions/beamwidths and/or at the same or different (eg, higher) frequencies.

Information from the primary beam can be used to facilitate the base station and/or WTRU to acquire one or more auxiliary beams, such as in an implementation that uses one or more aggregated beams. For example, the direction of the main beam of the first frequency can be used to assist in synchronizing the bunched beams of the second different frequency. The direction of the main beam having the first beamwidth may be used by the base station to identify, for example, a beam to be transmitted during the synchronization process for one or more auxiliary beams and/or for further refining the beamwidth during transmission.

The network may facilitate receive beamforming training at the WTRU, for example, to enable the WTRU to identify a receive beam (eg, a "best" receive beam) for a particular network beam. The network may facilitate receive beamforming training at the WTRU, for example, using beam repetition for WTRU receive beamforming.

To facilitate WTRU receive beamforming, the WTRU may scan its receive beam, for example, based on the periodicity of the transmit beam that the WTRU has identified as a good beam (eg, the "best" beam). The WTRU may select a good beam (e.g., "best" beam) from the receive beam, for example, once the transmit beam can be identified. This process may be transparent to the base station.

The WTRU may feed back information to the base station and/or request the base station to switch to training mode in which the WTRU repeatedly transmits information over the requested beam for a period of time, for example, to facilitate the receive beamforming process. Such a WTRU may estimate one or more receive beams to determine a selected receive beam (eg, a "best" receive beam) that is used as a network beam. Such a WTRU may request a selected receive beam (e.g., a "best" receive beam) on a random access channel. Alternatively or additionally, the WTRU may send a beam refinement request in the scheduling request (eg, it may include a desired number of receive beams to train).

The feedback provided by the WTRU may be analog or digital. The WTRU may feed back an index indicating the beam position in the periodic beam scan, for example, where the feedback may be analogous. The WTRU may reward the beam index that has been estimated during the synchronization process. The WTRU may reward a beam identifier that may be based on a predefined codebook.

Once the WTRU has been connected to the beam, beamforming up/down chain control and/or uplink/downlink data transmission can begin. Multi-layer transmission can be used in systems that can support beamforming transmission.

Figure 20 illustrates an exemplary method 2000 for performing periodic beam synchronization and/or beam initiated network information acquisition in an example. Method 2000 can include functionality that can be used similar to that used in the examples described, for example, with reference to FIG. All of the functions described with respect to method 2000, as well as any other methods described herein, are optional, and implementations using a subset of any of the functions described with respect to any of the methods described herein and/or any combination may be used. All such implementations are encompassed within the scope of the disclosure.

At block 2005, periodic beam scanning may be performed, for example, by a base station (e.g., gNB) at a network reservation time interval, which may be spaced at intervals available for data transmission. Either or both of these time intervals may be fixed according to, for example, a standard. Either or both of these time intervals may be dynamic and may be determined based on system load in some examples.

At block 2010, the PBSS may be transmitted at the beam or by a beam, such as by a base station. At block 2015, the SBSS may be transmitted at or by such a beam, such as by a base station. At block 2020, broadcast information may be transmitted at or by such a beam, such as by a base station.

At block 2025, synchronization and/or network information acquisition may be performed, for example, by the WTRU. At block 2030, such a WTRU may send a random access signal and/or an authorization request for receiving beam training to the beam. For example, feedback and/or receive beamforming requests can be sent. In some examples, any of the functions of blocks 2030 and/or 2035 may not be performed. In such an example, method 2000 can proceed from block 2025 to block 2040.

At block 2035, the beam may be repeated a number of times ("N") to facilitate beam training. For example, the base station may repeat one or more beams multiple times to facilitate training of the WTRU (eg, receive beam training).

At block 2040, beam-centric scheduling and/or transmission may be performed, for example, by a base station. Method 2000 can continue by returning to block 2005.

Figure 21 illustrates an exemplary method 2100 that may be used in an example to perform aperiodic beam synchronization and/or beam initiated network information acquisition. Method 2100 can include functionality that can be used similar to that used in the examples described, for example, with reference to FIG. All of the functions described in relation to method 2100, as well as any other methods described herein, are optional, and implementations using a subset of any of the functions described with respect to any of the methods described herein and/or any combination may be used. All such implementations are encompassed within the scope of the disclosure.

At block 2105, data transmission at the first beam or by the first beam may be performed, such as by a base station (e.g., gNB). At block 2110, the PBSS may be transmitted in such a first beam or by such a first beam, such as by a base station. At block 2115, the SBSS may be transmitted at such a first beam or by such a first beam, such as by a base station. At block 2120, the broadcast information can be transmitted at such a first beam or by such a first beam, such as by a base station. As shown in 2181, such a first beam can be scheduled to transmit data.

At block 2125, data transmission at or at the second beam may be performed, such as by a base station. At block 2130, the PBSS may be transmitted at such a second beam or by such a second beam, such as by a base station. At block 2135, the SBSS may be transmitted at such a second beam or by such a second beam, such as by a base station. At block 2140, the broadcast information can be transmitted at the second beam or by the second beam, such as by a base station. As shown in 2182, such a second beam can be scheduled to transmit data.

At block 2145, synchronization and/or network information acquisition may be performed, for example, by the WTRU. At block 2170, such a WTRU may send a random access signal and/or an authorization request for receiving beam training to the beam. For example, feedback and/or receive beamforming requests can be sent. In some examples, any of the functions of blocks 2170 and/or 2175 may not be performed. In such an example, method 2100 can proceed from block 2145 to block 2150.

At block 2175, the beam can be trained in receive beam training by some number of repetitions ("N"). For example, the base station may repeat one or more beams multiple times to facilitate training of the WTRU (eg, receive beam training).

At block 2150, the PBSS may be transmitted at the third beam or by a third beam, such as by a base station. At block 2155, the SBSS may be transmitted at such a third beam or by such a third beam, such as by a base station. At block 2160, the broadcast information can be transmitted at such a third beam or by such a third beam, such as by a base station. As indicated by 2183, such a third beam may have no scheduling data for transmission.

At block 2165, beam-centric scheduling and/or transmission can be performed, for example, by the base station. Note that each of the first beam, the second beam, and the third beam described with respect to FIG. 21 may be different from each of the other beams described with respect to FIG.

FIG. 22 illustrates an exemplary method 2200 that may be used in an example to perform periodic beam synchronization and/or WTRU-initiated network information acquisition. Method 2200 can include functionality that can be similar to that described elsewhere herein. All of the functions described with respect to method 2200, as well as any other methods described herein, are optional, and implementations using a subset of any of the functions described with respect to any of the methods described herein and/or any combination may be used. All such implementations are encompassed within the scope of the disclosure.

At block 2205, periodic beam scanning can be performed, for example, by a base station (e.g., gNB). At block 2210, the PBSS can be transmitted at the beam or by a beam, such as by a base station. At block 2215, the SBSS may be transmitted at such a beam or by such a beam, such as by a base station.

At block 2220, synchronization and/or network information acquisition may be performed, for example, by the WTRU. At block 2225, such a WTRU may transmit random access signals (e.g., new and/or different random access signals) for broadcast to, for example, a beam and/or base station. At block 2230, the broadcast can be sent, for example, by a beam and/or base station. At block 2235, such a WTRU may acquire a broadcast channel, such as a broadcast channel that may be sent at block 2230. In some examples, any of the functions of blocks 2220-2235 may not be performed. In such an example, method 2200 can proceed from block 2235 to block 2240 or block 2250.

At block 2240, such a WTRU may send a random access signal and/or an authorization request for receiving beam training to the beam. For example, feedback and/or receive beamforming requests can be sent. In some examples, any of the functions of blocks 2240 and/or 2245 may not be performed. In such an example, method 2200 can proceed from block 2215 or block 2235 to block 2250.

At block 2245, the beam may be repeated a number of times ("N") to facilitate receive beam training. For example, the base station may repeat one or more beams multiple times to facilitate training of the WTRU (eg, receive beam training).

At block 2250, beam-centric scheduling and/or transmission can be performed, for example, by a base station. Method 2200 can continue by returning to block 2205.

FIG. 23 illustrates an exemplary method 2300 that may be used in an example to perform aperiodic beam synchronization and/or WTRU-initiated network information acquisition. Method 2300 can include functionality that can be similar to the functionality described elsewhere herein. All of the functions described with respect to method 2300, as well as any other methods described herein, are optional, and implementations using a subset of any of the functions described with respect to any of the methods described herein and/or any combination may be used. All such implementations are encompassed within the scope of the disclosure.

At block 2305, data transmission at the first beam or by the first beam may be performed, such as by a base station (e.g., gNB). At block 2310, the PBSS may be transmitted at such a first beam or by such a first beam, such as by a base station. At block 2315, the SBSS may be transmitted at such a first beam or by such a first beam, such as by a base station. As shown in 2381, such a first beam can be scheduled to transmit data.

At block 2320, data transmission at or at the second beam may be performed, such as by a base station (e.g., gNB). At block 2325, the PBSS may be transmitted at such a second beam or by such a second beam, such as by a base station. At block 2330, the SBSS can be transmitted by such a second beam, such as by a base station. As shown in 2382, such a second beam can be scheduled to transmit data.

At block 2335, the WTRU may synchronize with the third beam. At block 2340, such a WTRU may transmit random access signals (e.g., new and/or different random access signals) for broadcast to, for example, a beam and/or base station. At block 2345, the broadcast can be sent, for example, by a beam and/or base station. At block 2350, such a WTRU may acquire a broadcast channel, such as a broadcast channel that may be sent at block 2345. In some examples, any of the functions of blocks 2335-2350 may not be performed. In such an example, method 2300 can proceed from block 2330 to block 2355 or block 2365.

At block 2355, such a WTRU may send a random access signal and/or an authorization request for receiving beam training to the beam. For example, feedback and/or receive beamforming requests can be sent. In some examples, either of the functions of blocks 2355 and/or 2360 may not be performed. In such an example, method 2300 can proceed from block 2350 or 2330 to block 2365.

At block 2360, the beam may be repeated a number of times ("N") to facilitate receive beam training. For example, the base station may repeat one or more beams multiple times to facilitate training of the WTRU (eg, receive beam training).

At block 2365, the PBSS may be transmitted in the fourth beam or by the fourth beam, such as by a base station. At block 2370, the SBSS may be transmitted in such a fourth beam or by such a fourth beam, such as by a base station. As shown in 2383, such a fourth beam may have no scheduling data for transmission.

At block 2375, beam-centric scheduling and/or transmission can be performed, for example, by the base station. Note that each of the first beam, the second beam, the third beam, and the fourth beam described with respect to FIG. 23 may be different from each of the other beams described with respect to FIG.

Figure 24 illustrates an exemplary method 2400 that may be used in an example to perform aperiodic beam synchronization and/or WTRU initiated network information acquisition. Method 2400 can include functionality that can be similar to that described elsewhere herein. All of the functions described with respect to method 2400, as well as any other methods described herein, are optional, and implementations using subsets and/or any combination of any of the functions described with respect to any of the methods described herein can be used. All such implementations are encompassed within the scope of the disclosure.

At block 2405, data transmission at or at the first beam may be performed, such as by a base station (e.g., gNB). At block 2410, the PBSS may be transmitted at such a first beam or by such a first beam, such as by a base station. At block 2415, the SBSS may be transmitted at such a first beam or by such a first beam, such as by a base station. As shown in 2481, such a first beam can be scheduled to transmit data.

At block 2420, data transmission at or at the second beam may be performed, such as by a base station (e.g., gNB). At block 2425, the PBSS may be transmitted at such a second beam or by such a second beam, such as by a base station. At 2430, the SBSS can be transmitted at such a second beam or by such a second beam, such as by a base station. As shown in 2482, such a second beam can be scheduled to transmit data.

At block 2435, the WTRU may synchronize with the third beam. At block 2440, such a WTRU may transmit random access signals (e.g., new and/or different random access signals) for broadcast to, for example, a beam and/or base station. At block 2445, the broadcast channel can be transmitted, for example, by a beam and/or base station. At block 2450, such a WTRU may acquire a broadcast channel, such as a broadcast channel that may be sent at block 2445. In some examples, any of the functions of blocks 2435-2450 may not be performed. In such an example, method 2300 can proceed from block 2430 to block 2455 or block 2465.

At block 2455, such a WTRU may send a random access signal and/or an authorization request for receiving beam training to the beam. For example, feedback and/or receive beamforming requests can be sent. In some examples, any of the functions of blocks 2455 and/or 2460 may not be performed. In such an example, method 2400 can proceed from block 2430 or block 2450 to block 2465.

At block 2460, the beam may be repeated a number of times ("N") to facilitate receive beam training. For example, the base station may repeat one or more beams multiple times to facilitate training of the WTRU (eg, receive beam training).

At block 2465, the fourth beam can be transmitted, for example, by the base station. Such a fourth beam can be in a "dummy" mode. As shown in 2843, such a fourth beam may not be scheduled for transmission of data.

At block 2470, the WTRU may transmit a signal on the BBRACH. At block 2475, the PBSS and/or SBSS may be transmitted at the fourth beam or by a fourth beam, such as by a base station. At block 2490, such a fourth beam can transmit a broadcast channel. At block 2493, the WTRU may acquire a broadcast channel, such as a broadcast channel that may be sent at block 2490. In some examples, any of the functions of blocks 2470-2493 may not be performed. In such an example, method 2400 can proceed from block 2465 to block 2495.

At block 2495, beam-centric scheduling and/or transmission can be performed, for example, by the base station. Note that each of the first beam, the second beam, the third beam, and the fourth beam described with respect to FIG. 24 may be different from each of the other beams described with respect to FIG.

Multi-beam and/or multi-string streaming may be facilitated by enabling beam splitting at the WTRU in downlink transmission and/or by enabling separate transmissions for beam decoding in uplink transmission. In an example, the beams may be independent (eg, completely independent) and/or self-contained. Where backhaul and/or centralized RANs may be used, the beams may or may not be independent (eg, completely independent) and/or self-contained.

The beam acquisition and/or synchronization process and system may include aspects of a WTRU such as identifiable and/or synchronized to multiple beams (e.g., using one or more synchronization techniques as set forth herein). The WTRU may send a scheduling request associated with the first beam for receiving beamforming training. The first beam may be repeated and/or repeatedly transmitted (e.g., by a base station) a first number ("N") times to facilitate receive beam training by the WTRU. The WTRU may send a scheduling request associated with the second beam for beamforming training. The second beam may be repeated and/or repeatedly transmitted (e.g., by a base station) a second number (e.g., "N-1") times to facilitate receive beam training of the WTRU. The first receive beam and the second receive beam may be self-contained beams and may be differentiated (eg, different) beams.

A WTRU may create multiple independent streams, for example, where such streams may be from different beams or associated with different beams. Such a WTRU may generate one or more traffic requests that may be sent to each of the first beam and the second beam. Such a WTRU may also or instead send a feedback indicating the availability and/or identity of the first beam to the second beam, and/or vice versa.

Beams (e.g., base stations that use beams) may be scheduled to and/or from the WTRU's traffic independently and/or simultaneously in the examples. Transmission to a beam (eg, a single beam) can include multiple layers. A beam (e.g., a base station using a beam) and/or a WTRU may initiate multi-beam and/or multi-layer transmission.

Figure 25 illustrates an exemplary method 2500 that can be used in an example to perform multi-beam and/or multi-string streaming. Method 2500 can include functionality that can be similar to that described elsewhere herein. All of the functions described with respect to method 2500, as well as any other methods described herein, are optional, and implementations using subsets and/or any combination of any of the functions described with respect to any of the methods described herein can be used. All such implementations are encompassed within the scope of the disclosure.

At block 2505, the WTRU may identify synchronization and/or broadcast information associated with the first beam. At block 2510, such a WTRU may transmit a receive beam training request to a first beam (e.g., a base station associated with the first beam). At block 2515, the WTRU may determine a preferred or "best" beam for the first beam.

At block 2520, the WTRU may identify synchronization and/or broadcast information associated with the second beam. At block 2525, such a WTRU may transmit a receive beam training request to a second beam (e.g., a base station associated with the second beam). At block 2530, the WTRU may determine a preferred or "best" beam for the second beam.

At block 2535, the WTRU may create multiple independent streams from each of the multiple beams or at each of the multiple beams. For example, the WTRU may create separate streams at each of the first beam and the second beam.

At block 2540, the WTRU may feed back presence and/or identity information that may be associated with one or more beams. For example, the WTRU may feed back presence and/or identity information associated with one or more beams other than the first and second beams. Alternatively or additionally, the WTRU may feed back presence and/or identity information that may be associated with the first and/or second beam.

At block 2545, the WTRU may transmit such beams independently and/or simultaneously.

WTRU-to-WTRU communication (e.g., device-to-device communication (D2D), such as 3GPP D2D communication) may be performed. For example, a WTRU performing WTRU-to-WTRU communication may perform one or more functions similar to one or more functions that may be performed by a base station, such as using beam execution. For example, periodic beam synchronization and/or network information acquisition may be initiated by one or more WTRUs. Aperiodic beam synchronization and/or network information acquisition may be initiated by one or more WTRUs.

Although the features and elements of the present disclosure are described above in terms of specific combinations, the features or elements described in the present disclosure may be used alone or without or without the other features and elements described in the disclosure. Various other combinations of features and elements disclosed herein or elsewhere are used. Although the features and/or elements described herein may be contemplated for new radios (NRs) and/or other examples, it should be understood that the features and/or elements described herein are not limited to these scenarios and may be applicable to Other technologies and wireless systems.

The example processes described above can be implemented in a computer program, software or firmware executed by a computer or processor, where the computer program, software or firmware is embodied in a computer readable storage medium. Examples of computer readable media include, but are not limited to, electronic signals (transmitted over wired or wireless connections) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor memory devices, magnetic media (such as but not limited to internals) Hard disk or removable disk), magneto-optical media, and optical media such as CD-ROMs and digital versatile discs (DVDs). A software-related processor can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, gNB, RNC, and/or any host computer

BBRACH‧‧‧ Beam Basic Random Access Channel
BRS‧‧ beam reference signal
Iub, IuCS, IuPS, iur, S1, X2‧‧ interface
R1, R3, R6, R8‧‧‧ reference points
PBSS‧‧‧ main beam sync signal
SBSS‧‧‧Auxiliary Beam Synchronization Signal
100‧‧‧Communication system
102, 102a, 102b, 102c, 102d, 310, 410, 510, 610 ‧ ‧ WTRU
103, 104, 105‧‧‧ Radio Access Network (RAN)
106, 107, 109‧‧‧ core network
108‧‧‧Public Switched Telephone Network (PSTN)
110‧‧‧Internet
112‧‧‧Other networks
114a, 114b, 180a, 180b, 180c, 221, 222, 223, 231, 325, 335, 425, 525, 625, 635 ‧ ‧ base station
115, 116, 117‧‧ ‧ empty mediation
118‧‧‧Processor
120‧‧‧ transceiver
122‧‧‧Transmission/receiving components
124‧‧‧Speaker/Microphone
126‧‧‧Keypad
128‧‧‧Display/Touchpad
130‧‧‧ Non-removable memory
132‧‧‧Removable memory
134‧‧‧Power supply
136‧‧‧Global Positioning System (GPS) chipset
138‧‧‧ Peripherals
140a, 140b, 140c‧‧‧ Node B
142a, 142b‧‧‧ Radio Network Controller (RNC)
144‧‧‧Media Gateway (MGW)
146‧‧‧Mobile Exchange Center (MSC)
148‧‧‧Serving GPRS Support Node (SGSN)
150‧‧‧Gateway GPRS Support Node (GGSN)
160a, 160b, 160c‧‧‧e Node B
162‧‧‧Action Management Gateway (MME)
164‧‧‧ service gateway
166‧‧‧ Packet Data Network (PDN) Gateway
182‧‧‧Access Service Network (ASN) Gateway
184‧‧‧Action IP Local Agent (MIP-HA)
186‧‧‧Verification, Authorization, Accounting (AAA) Server
188‧‧ ‧ gateway
200, 300, 400, 500, 600, 700, 1200‧‧‧ sample scenarios
211, 212, 213‧‧ ‧ cells
320, 330, 430, 440, 530, 540, 620, 630‧‧ beams
700‧‧‧Scenario
800, 900, 1000, 1100, 1300, 1400, 1500, 1600, 1700, 1800, 1900‧‧‧ exemplary scenes
810, 820, 910, 920‧‧ ‧ intervals
1010, 1020, 1101, 1102, 1103, 1104, 1210, 1502, 1601, 1602, 1701, 1702, 1801, 1802‧‧
1120, 1311, 1312, 1313, 1314‧‧‧ data interval
1301, 1302, 1303, 1304‧‧‧ signals
1501‧‧‧ Schedule Information
2000, 2100, 2200, 2300, 2400, 2500‧‧‧ methods

Figure 1A is a system diagram of an example communication system. FIG. 1B is a system diagram of an exemplary wireless transmit/receive unit (WTRU) that can be used in a communication system, such as the example communication system shown in FIG. 1A. 1C is a system diagram of an example radio access network and/or an exemplary core network that can be used in a communication system, such as in the example communication system shown in FIG. 1A. Figure 1D is a system diagram of another example radio access network and/or example core network that may be used in a communication system, such as the example communication system shown in Figure 1A. Figure 1E is a system diagram of another exemplary radio access network and/or exemplary core network that may be used in a communication system, such as the example communication system shown in Figure 1A. Figure 2 shows an example beam-centric communication system for an example of a super-impose on a cell-centric system. Figure 3 shows an example beam-centric system and an example WTRU. Figure 4 shows an example of a concentrated beam separated by beamwidth. Figure 5 shows an example of a concentrated beam separated by frequency. Figure 6 shows an example of multi-beam transmission. Figure 7 shows an example of beam transmission that may include one or more beam synchronization sequences. Figure 8 shows an example of a reserved time interval that can be used to synchronize and/or broadcast signals and can be spaced by data transmission. Figure 9 shows an example of a reserved time interval that can be used for beam reference signals (BRS) and that can be spaced by data transmission. Figure 10 shows an example of a network with four beams and a packet of periodic synchronization channels/BRS. Figure 11 shows an example of a network with four beams and a separate periodic synchronization channel/BRS. Figure 12 shows an example of periodic synchronization, broadcast, and/or data transmission. Figure 13 shows an example of an interlaced signal. Figure 14 shows an example of aperiodic synchronous communication. Figure 15 shows an example of synchronization and/or network acquisition messaging. Figure 16 shows an example of BRS messaging with scheduled data on the connected beams. Figure 17 shows an example of random beamforming with data, broadcast and/or sync signals. Figure 18 shows an example of random beamforming with BRS for measurement. Figure 19 shows an exemplary time interval that can be used with periodic synchronization of broadcast network information. Figure 20 shows an exemplary process for periodic beam synchronization and/or beam initiated network information acquisition. Figure 21 shows an exemplary process for aperiodic beam synchronization and/or beam initiated network information acquisition. Figure 22 illustrates an exemplary process for periodic beam synchronization and/or WTRU initiated network information acquisition. Figure 23 illustrates an exemplary process for aperiodic beam synchronization and/or WTRU initiated network information acquisition. Figure 24 illustrates an exemplary process for aperiodic and WTRU initiated beam synchronization and/or WTRU initiated network information acquisition. Figure 25 shows an exemplary process for multi-beam and/or multi-string streaming.

200‧‧‧example scene

211, 212, 213‧‧ ‧ cells

221, 222, 223, 231‧‧‧ base stations

Claims (15)

A method of beam synchronization performed by a WTRU, the method comprising: receiving a beam; determining whether a signal is in the beam; transmitting a request for the signal to a base station, wherein the request includes An indication of the beam and an indication of a signal characteristic. The method of claim 1, wherein determining whether the signal includes in the beam comprises determining that a beam component of the beam is signaled to the WTRU. The method of claim 2, wherein the beam component comprises at least one of: a synchronization component, a broadcast component, or a reference component. The method of claim 1, wherein determining whether the signal includes a beam component of the beam in the beam. The method of claim 4, wherein the beam component comprises at least one of: a synchronization component, a broadcast component, or a reference component. The method of claim 1, wherein the signal characteristic is one of: synchronization, broadcast, measurement reference signal (MRS), and any combination thereof. The method of claim 1, wherein determining whether the signal includes a beam type determining the beam in the beam. The method of claim 1, wherein the base station is a next generation Node B (gNB). A wireless transmit/receive unit (WTRU), comprising: a transceiver configured to: receive a beam and transmit a request for a signal to a base station; and a processor configured to: determine whether the signal is In the beam, and generating the request for the signal, wherein the request includes an indication of the beam and an indication of a signal characteristic. The WTRU of claim 9, wherein the processor is configured to determine whether the signal is in the beam by determining that a beam component of the beam is signaled. The WTRU as claimed in claim 10, wherein the beam component comprises at least one of: a synchronization component, a broadcast component, or a reference component. The WTRU of claim 9, wherein the processor is configured to determine whether the signal is in the beam by determining a beam component of the beam. The WTRU as claimed in claim 12, wherein the beam component comprises at least one of: a synchronization component, a broadcast component, or a reference component. The WTRU as claimed in claim 9, wherein the signal characteristic is one of: synchronization, broadcast, measurement reference signal (MRS), and any combination thereof. The WTRU as claimed in claim 9, wherein the base station is a next generation Node B (gNB).