WO2018045092A1 - On-demand system information block (sib) transmission - Google Patents

Abstract

Devices and methods of on-demand system information block (SIB) transmission are generally described. A user equipment (UE) can be configured to determine a beam index during a beam sweeping procedure, based on a signal quality metric associated with a received synchronization signal. The UE can encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence. The RACH preamble sequence can include a system information request. The UE can decode system information configuration received in response to the system information request. The UE can initiate a RACH process using another RACH preamble sequence, based on the received system information configuration. The encoded RACH preamble sequence with the system information request can be transmitted multiple times using the preferred beam index.

Description

ON-DEMAND SYSTEM INFORMATION BLOCK (SIB)

TRANSMISSION

PRIORITY CLAIM

[0001] This application claims the benefit of priority to PCT Patent Application Serial No. PCT/CN2016/097588, filed August 31, 2016, and entitled "SYSTEM AND METHOD FOR ON-DEMAND SIB

TRANSMISSION FOR BEAMFORMED SYSTEM," and PCT Patent Application Serial No. PCT/CN2016/ 102540, filed October 19, 2016, and entitled "FIFTH GENERATION (5G) PAGING TRANSMISSION WITH GUARD INTERVAL- DISCRETE FOURIER TRANSFORM SPREAD ORTHOGONAL FREQUENCY DIVISION MULTIPLEXING (GI-DFT- S-OFDM)," which applications are incorporated herein by reference in their entireties.

[0002] Aspects pertain to wireless communications. Some aspects relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including new radio (NR) networks. Other aspects are directed to on- demand system information block (SIB) transmission. Other aspects are directed to paging transmission with guard interval Discrete Fourier Transform (DFT) spread Orthogonal Frequency Division Multiplexing (GI- DFT-S-OFDM).

[0003] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. With the increase in different types of devices communicating with various network devices, usage of 3GPP LTE systems has increased. The penetration of mobile devices (user equipment or UEs) in modem society has continued to drive demand for a wide variety of networked devices in a number of disparate environments. The use of networked UEs using 3GPP LTE systems has increased in all areas of home and work life. Fifth generation (5G) wireless systems are forthcoming, and are expected to enable even greater speed, connectivity, and usability. Improved communication techniques, therefore, will be essential in further developing 5G wireless technologies.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments.

[0006] FIG. IB is a simplified diagram of a next generation wireless network in accordance with some embodiments.

[0007] FIG. 2 illustrates example components of a device 200 in accordance with some embodiments,

[0008] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments,

[0009] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments.

[0010] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments.

[0011] FIG. 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine- readable storage medium) and perform any one or more of the

methodologies discussed herein. [0012] FIG. 7 illustrates examples of multiple beam transmission in accordance with some embodiments.

[0013] FIG. 8 illustrates example information flow for on-demand system information transmission in accordance with some embodiments.

[0014] FIG. 9A and FIG. 9B illustrate example subframes for transmission of a system information request in accordance with some embodiments.

[0015] FIG. lOA and FIG. 10B illustrate example paging transmissions within a subframe in accordance with some embodiments.

[0016] FIG. HA and FIG. 1 IB illustrate example multiple paging occasions within a subframe in accordance with some embodiments.

[0017] FIG. 12 illustrates an example aggregated DMRS

transmission with paging occasions in accordance with some embodiments.

[0018] FIG. 13A and FIG. 13B illustrate transmission of beam refinement reference signals (BRRS) with paging occasions in accordance with some embodiments.

[0019] FIG. 14A, FIG. 14B, and FIG. 14C illustrate example repeated paging transmissions within a single subframe in accordance with some embodiments.

[0020] FIG. 15 illustrates an example subframe with repeated transmission of PDCCH and paging messages in accordance with some embodiments.

[0021] FIG. 16, FIG. 17, and FIG. 18 are flow diagrams illustrating example functionalities for on-demand system information transmission in accordance with some embodiments.

[0022] FIG. 19 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (STA), or a user equipment (UE), in accordance with some embodiments. DETAILED DESCRIPTION

[0023] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments.

Embodiments set forth in the claims encompass all available equivalents of those claims.

[0024] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile

Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3 GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000

(CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile

Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel, 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3 GPP Rel, 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17), 3 GPP Rel. 18 (3rd Generation Partnership Project Release 18), 3GPP 5G, 3GPP LTE Extra, LTE- Advanced Pro, LTE Licensed- Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th

Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS ( G)), Total Access Communication

System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile

Telephony), High capacity version of NTT (Nippon Telegraph and

Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex,

DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WIDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee,

Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. 1 ad, IEEE 802. 1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP LTE based or IEEE 802. 1 Ip and other) Vehicle-to- Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent- Transport- Systems and others, etc.

[0025] Embodiments described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as LSA ^;=: Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System in 3.55-3.7 GHz and further frequencies). Applicable spectaim bands include IMT (International Mobile Telecommunications) spectrum (including 450 - 470 MHz, 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, etc). Note that some bands are limited to specific region(s) and/or countries), 1MT- advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27,5 - 28.35 GHz, 29. 1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0026] Embodiments described herein can also implement a hierarchical application of the scheme is possible, e.g. by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g. with highest priority to tier- 1 users, followed by tier-2, then tier-3, etc. users, etc.

[0027] Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC- OFDM, filter bank-based multicarrier (FBMC), OFDM A, etc.) and in particular 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0028] LTE and LTE-Advanced are standards for wireless communications of high-speed data for user equipment (UE) such as mobile telephones. In LTE-Advanced and various wireless systems, carrier aggregation is a technology where multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0029] The explosive wireless traffic growth leads to a need of rate improvement. With mature physical layer techniques, further improvement in the spectral efficiency will be marginal. On the other hand, the scarcity of licensed spectrum in low frequency bands results in a deficit in the data rate boost. Thus, there are emerging interests in the operation of LTE systems in the unlicensed spectrum. As a result, an important enhancement for LTE in 3 GPP Release 13 has been to enable its operation in the unlicensed spectrum via Licensed-Assisted Access (LAA), which expands the system bandwidth by utilizing the flexible carrier aggregation (CA) framework introduced by the LTE-Advanced system. Rel-13 LAA system focuses on the design of DL operation on unlicensed spectrum via CA, while Rel-14 enhanced LAA (eLAA) system focuses on the design of UL operation on unlicensed spectrum via CA. Further enhanced operation of LTE systems in the unlicensed spectrum is expected in future releases and 5G systems. Potential LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC- based LAA, and the standalone LTE system in the unlicensed spectnmi, where LTE-based technology solely operates in unlicensed spectrum without requiring an "anchor" in the licensed spectrum, called MulteFire. MulteFire, combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments, is envisioned as a significantly important technology component to meet the ever-increasing wireless traffic.

[00301 The next generation wireless communication system, 5G, will provide access to information and sharing of data anywhere, anytime by various users and applications, 5G is expected to be a unified network / system that targets to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different sendees and applications. In general, 5G will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. 5G will enable everything connected by wireless and deliver fast, rich contents and services.

[0031] For mid-band (carrier frequency between 6GHz and 30GHz) and high-band (carrier frequency beyond 3()GHz), beamforming is one key technology to improve the signal quality and reduce the inter user interference by directing the narrow radiate beaming toward the target users. For mid and high-band system, the path loss caused by weather like rain, fog, or object block, can severely deteriorate the signal strength and damage the performance of the communications. Beamforming gain can compensate the path loss, and thereby improve coverage range.

[0032] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 100 is shown to include a user equipment (UE) 101 and a UE 02. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[0033] In some embodiments, any of the UEs 101 and 102 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to- machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Sendee (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet

infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

[0034] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110 - the RAN 1 10 may be, for example, an Evolved Universal Mobile

Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA ), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer

(discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term

Q Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (Nil) protocol, and the like.

[0035] In this aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0036] The UE 102 is shown to be configured to access an access point (/VI³) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802. 1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0037] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs feNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 1 0 may include one or more RAN nodes for providing maeroceils, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to maeroceils), e.g., low power (LP) RAN node 112.

[0038] Any of the RAN nodes 1 1 1 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 11 1 and 1 12 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer

management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 1 1 1 and/or 112 can be a new generation node-B (gNB), an eveloved node-B (eNB) or another type of RAN node.

[0039] In accordance with some embodiments, the UEs 101 and

102 can be configured to communicate using Orthogonal Frequency- Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 11 and 1 12 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0040] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 11 1 and 1 12 to the UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain phy sical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0041] The physical downlink shared channel (PDSCH) may carry- user data and higher-layer signaling to the UEs 101 and 102. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.

Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 111 and 1 12 based on channel quality information fed back from any of the UEs 101 and 02. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

[0042] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interieaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8),

[0043] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations. 0044 The RAN 1 10 is show to be communicatively coupled to a core network (CN) 120 via an S I interface 1 13. In embodiments, the CN

120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this aspect, the S I interface 1 13 is split into two parts: the S l-U interface 1 14, which carries traffic data between the RAN nodes 1 1 1 and 1 2 and the serving gateway (S-GW) 122, and the S I -mobility management entity (MME) interface 1 15, which is a signaling interface between the RAN nodes 1 1 1 and 1 12 and MMEs 121.

[0045] In this aspect, the CN 120 comprises the MMEs 121, the S- GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming,

authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0046] The S-GW 122 may terminate the S I interface 1 13 towards the RAN 1 10, and routes data packets between the RAN 1 10 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0047] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 123 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Sendees (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be

communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice- over-Internet Protocol (VoIP) sessions, PTT sessions, group

communication sessions, social networking services, etc.) for the IJEs 101 and 102 via the CN 120.

[0048] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging

Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H- PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new sendee flow and select the appropriate Quality of Sendee (QoS) and charging parameters. The PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.

[0049] In an example, any of the nodes 11 1 or 112 can be configured to communicate to the IJEs 101/102 (e.g., dynamically) an antenna panel selection and a receive (Rx) beam selection that should be used by the UE for data reception on a physical downlink shared channel (PDSCH) as well as for channel state information reference signal (CSI- RS) measurements and channel state information (CSI) calculation. [0050] In an exampl e, any of the nodes 11 1 or 112 can be configured to communicate to the UEs 101/102 (e.g., dynamically) an antenna panel selection and a transmit (Tx) beam selection that should be used by the LIE for data transmission on a physical uplink shared channel (PUSCH) as well as for sounding reference signal (SRS) transmission.

[0051] In accordance with some embodiments, the UEs 101 and

102, the e Bs 111 and 1 12, and the AP 106 can be configured to operate in a LAA, eLAA, MulteFire or another communication environment using licensed and/or unlicensed spectrum (e.g., the 5 GHz Industrial, Scientific and Medical (ISM) band).

[0052] In an example embodiment, the downlink signal from the eNBs 1 1 1 and 112 to the UEs 101 and 102 may be transmitted with ransmit (TX) beamforming. Different TX beams may be used to transmit UE- specific signals to different UEs. However, common system information, such as Master Information Block (MIB), System Information Block 1 (SIBl) and SIB2, can be communicated to the UEs. In order to guarantee that all active UEs can receive this common system information, the eNBs 111 and 112 can be configured to transmit this information during multiple symbols using different TX beams. Additionally, the system information can be transmitted periodically, which can result in high overhead, especially for the cell with few or static UEs.

[0053] In LTE system, the UE can be configured to detect MIB,

SIBl and SIB2 before starting the random access procedure (RACH). While MIB has limited bits, typically less than 40bits, combined information of SIBl and SIB2 can be quite large. In this regard, the transmission of SIBl and SIB 2 using multiple TX beams or a single quasi- omni beam transmission with time repetition for coverage boosting, can result in a high system overhead. In an example embodiment, in order to reduce overhead and enable lean system design, on-demand system information transmission can be performed, which can include on-demand system information transmission four wider or narrow beam transmission scenarios. More specifically, on-demand system information request 191 can be communicated to the eNBs 111 or 112, The eNBs 1 1 1 or 1 12 can communicate the system information 192 back to the UE 101 in response to the request 191. A more detailed description of on-demand system information transmission is provided herein below in reference to FIG. 8 - FIG. 9B.

[0054] In some embodiments, beamforming procedure and the reference signals used for achieving it can vary for different physical control and data channels. For mmWave cellular systems, Hybrid antenna architectures (HA A), that have smaller number of Radio Frequency (RF) chains than the number of physical antennas, can be used due to their hardware complexity as well as economic efficiencies. Beam-forming procedure for HAA can include two components that can be tracked either independently or jointly or iteratively depending on the resources and the constraints - analog beam forming or tracking and digital beam forming or tracking. The analog beam-forming can include mostly wideband operations due to the hardware constraints of the HAA, while the digital beamforming can include narrowband operations.

[0055] In some embodiments, paging can be an essential function to enable standalone operation. Due to the broadcasting nature of paging message transmission, efficient and reliable paging channel design in mid- high band pose new design challenge. In reference to FIG. LA, a paging message 190 can originate from the CN 120 (e.g. at the MME 121) and can be communicated to the eNBs 111 and 112, which in turn can send a paging message 190 to the UE 101. In some embodiments, different paging transmission structures and techniques can be used to further improve the frequency efficiency and/or guarantee the coverage area of paging. More specifically, the following techniques (which are discussed in greater detail in reference to FIGS. 10A-15) can be used for improving paging transmission: Omni transmission of paging information from cells within a tracking area code (TAC); finer paging occasion granularity based on slot or mini slot; enhanced paging structure for enhanced coverage area, e.g. receive (RX) beam refinement model and repeated transmission;

enhanced P-RNTI PDCCH design; and adjusting guard interval (GI) duration in paging slots or mini-slots. [0056] FIG. IB is a simplified diagram of a next generation wireless network in accordance with some embodiments. The wireless network may be similar to that shown in FIG. 1 A but may contain components associated with a 5G network. The wireless network may contain, among other elements not shown, a RAN 110 coupled to the core network 120 (as well as to the Internet which can connect the core network 120 with other core networks 120). In some embodiments, the RAN 110 and the core network 120 may be a next generation (5G) 3 GPP RAN and 5G core network, respectively. The RAN 1 10 may include an upper layer of a new generation node-B (gNB) (also referred to as a new radio (NR) base station (BS) (ULNRBS)) 140 and multiple lower layers of different gNBs (NR. BS (LLNRBS)) 111. The LLNRBSs 1 1 1 can be connected to the ULNRBS 140 via a Z interface. The Z interface can be open or proprietary. In some examples, the LLNRBS 111 can be referred to as a transmission-reception point (TRP). If the Z interface is proprietary, then the ULNRBS 140 and the LLNRBS 111 may be provided by the same vendor. The LLNRBS 1 1 1 can be connected by a Y interface, which may be equivalent to the LTE X2 interface. The ULNRBS 140 may be connected to the core network 120 through the SI interface 113.

[0057] As used herein, the term circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some

embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Aspects described herein may be implemented into a system using any suitably configured hardware or software.

[0058] FIG. 2 illustrates example components of a device 200 in accordance with some embodiments. In some embodiments, the device 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 coupled together at least as shown. The components of the illustrated device 200 may be included in a UE or a RAN node. In some

embodiments, the device 200 may include less elements (e.g., a RAN node may not utilize application circuitry 202, and instead include a

processor/controller to process IP data received from an EPC). In some embodiments, the device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN)

implementations).

[0059] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 200. In some embodiments, processors of application circuitry 202 may process IP data packets received from an EPC.

[0060] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 may include a third generation (3G) baseband processor 204 A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processor(s) 204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functionality of baseband processors 204A-D may be included in modules stored in the memory 20 G and executed via a Central Processing Unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments,

modulation/demodulation circuitry of the baseband circuitry 204 may include Fast -Fourier Transform (FFT), precoding, or constellation mapping demapping functionality. In some embodiments,

encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other aspects.

[0061] In some embodiments, the baseband circuitry 204 may include one or more audio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F may be include elements for

compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 may be

implemented together such as, for example, on a system on a chip (SOC). [0062] In some embodiments, the baseband circuitry 204 may provide for communication compatible with one or more radio

technologies. For example, in some embodiments, the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (EUTRA ) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0063] RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.

[0064] In some embodiments, the receive signal path of the RF circuitry 206 may include mixer circuitry 206A, amplifier circuitry 206B and filter circuitry 206C. In some embodiments, the transmit signal path of the RF circuitry 206 may include filter circuitry 206C and mixer circuitry 206A. RF circuitry 206 may also include synthesizer circuitry 206D for synthesizing a frequency for use by the mixer circuitry 206 A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206 A of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206D. The amplifier circuitry 206B may be configured to amplify the down-converted signals and the filter circuitry 206C may be a low-pass filter (LPF) or bandpass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 204 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 206A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0065] In some embodiments, the mixer circuitry 206A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206D to generate RF output signals for the FEM circuitry 208. The baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206C.

[0066] In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206 A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 206 A of the receive signal path and the mixer circuitry 206A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206 A of the receive signal path and the mixer circuitry 206A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 206 A of the receive signal path and the mixer circuitry 206 A of the transmit signal path may be configured for super-heterodyne operation.

[0067] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to- analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.

[0068] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0069] In some embodiments, the synthesizer circuitry 206D may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 206D may be a delta-si gma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0070] The synthesizer circuitry 206D may be configured to synthesize an output frequency for use by the mixer circuitry 206 A of the RF circuitry 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 206D may be a fractional N/N+l synthesizer.

[0071] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement- Divider control input may be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 202.

[0072] Synthesizer circuitry 206D of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carr out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle,

[0073] In some embodiments, synthesizer circuitry 206D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 206 may include an IQ/polar converter.

[0074] FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210. In various embodiments, the amplification through the transmit signal paths or the receive signal paths may be done solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

[0075] In some embodiments, the FEM circuitry 208 may include a TX''RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210). [0076] In some embodiments, the PMC 212 may manage power provided to the baseband circuitry 204. In particular, the PMC 212 may control power-source selection, voltage scaling, battery charging, or DC-to- DC conversion. The PMC 212 may often be included when the device 200 is capable of being powered by a batten,', for example, when the device is included in a UE. The PMC 212 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics,

[0077] While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204. However, in other embodiments, the PMC 212 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.

[0078] In some embodiments, the PMC 212 may control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 200 may power down for brief intervals of time and thus save power,

[0079] If there is no data traffi c activity for an extended period of time, then the device 200 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 200 may transition back to RRC_Connected state in order to receive data.

[0080] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable. [0081] Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein. Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0082] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 204 of FIG. 2 may comprise processors 204A-204E and a memory 204G utilized by said processors. Each of the processors 2G4A-2Q4E may include a memory interface, 304A-304E, respectively, to send/receive data to/from the memory 204G.

[0083] The baseband circuitry 204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 316 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG . 2), a wireless hardware connectivity interface 318 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth© Low Energy), Wi-Fi® components, and other

communication components), and a power management interface 320 (e.g., an interface to send/receive power or control signals to/from the PMC 212). [0084] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane

400 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 1 1 1 (or alternatively, the RAN node 112), and the MME 121.

[0085] The PHY layer 40 may transmit or receive information used by the MAC layer 402 over one or more air interfaces. The PHY layer

401 may further perform link adaptation or adaptive modulation and coding (AMC), power control, ceil search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 405. The PHY layer 401 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing,

[0086] The MAC layer 402 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0087] The RLC layer 403 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 403 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 403 may also execute re-segmentation of RLC data PDUs for A : data transfers, reorder RLC data PDUs for UM and A : data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[0088] The PDCP layer 404 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[0089] The main services and functions of the RRC layer 405 may include broadcast of system information (e.g., included in Master

Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the LIE and E-UTRA (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and

measurement configuration for IJE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures,

[0090] The UE 101 and the RAN node 1 1 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer 404, and the RRC layer 405.

[0091] The non-access stratum (NAS) protocols 406 form the highest stratum of the control plane between the UE 101 and the MME 121. The NAS protocols 406 support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 123, [0092] The S I Application Protocol (Sl-AP) layer 415 may support the functions of the SI interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node 1 I 1 and the CN 120. The Sl-AP layer services may comprise two groups: UE- associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and

configuration transfer.

[0093] The Stream Control Transmission Protocol (SCTP) layer

(alternatively referred to as the SCTP/IP layer) 414 may ensure reliable delivery of signaling messages between the RAN node 1 I 1 and the MME 121 based, in part, on the IP protocol, supported by the IP layer 413. The L2 layer 412 and the LI layer 411 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0094] The RAN node 11 1 and the MME 121 may utilize an S 1 -

MME interface to exchange control plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and the S 1 - AP layer 415.

[0095] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 500 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 1 1 1 (or alternatively, the RAN node 112), the S-GW 122, and the P-GW 123. The user plane 500 may utilize at least some of the same protocol layers as the control plane 400, For example, the UE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, and the PDCP layer 404,

[0096] The General Packet Radio Service (GPRS) Tunneling

Protocol for the user plane (GTP-U) layer 504 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 111 and the S-GW 122 may utilize an Sl -U interface to exchange user plane data via a protocol stack comprising the LI layer 41 , the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. The S-GW 122 and the P-GW 123 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 411 , the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. As discussed above with respect to FIG. 4, NAS protocols support the mobility of the UE 101 and the session management procedures to establish and maintain IP

connectivity between the UE 101 and the P-GW 123.

[0097] FIG. 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine- readable storage medium) and perform any one or more of the

methodologies discussed herein. Specifically, FIG. 6 shows a

diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600

[0098] The processors 610 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 612 and a processor 614. [0099] The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The

memory storage devices 620 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[00100] The communication resources 630 may include

interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components,

[00101] Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processors cache memory), the memory/storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606, Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media.

[00102] FIG. 7 illustrates examples of multiple beam transmission in accordance with some embodiments. Although the example scenarios 700 and 750 depicted in FIG . 7 may illustrate some embodiments of techniques disclosed herein, it will be understood that embodiments are not limited by example scenarios 700 and 750. Embodiments are not limited to the number or type of components shown in FIG. 7 and are also not limited to the number or arrangement of transmitted beams shown in FIG. 7.

[00103] In example scenario 700, the e B 111 may transmit a signal on multiple beams 705-720, any or all of which may be received at the UE 102. It should be noted that the number of beams or transmission angles as shown are not limiting. As the beams 705-720 may be directional, transmitted energy from the beams 705-720 may be concentrated in the direction shown. Therefore, the UE 102 may not necessarily receive a significant amount of energy from beams 705 and 710 in some cases, due to the relative location of the UE 102.

[00104] UE 102 may receive a significant amount of energy from the beams 715 and 720 as shown. As an example, the beams 705-720 may be transmitted using different reference signals, and the UE 102 may determine channel- state information (CSI) feedback or other information for beams 715 and 720. In some embodiments, each of beams 705-420 are configured as CSI reference signals (CSI-RS). In related embodiments, the CSI-RS signal is a part of the discovery reference si gnaling (DRS) configuration. The DRS configuration may serve to inform the UE 102 about the physical resources (e.g., subframes, subcarriers) on which the CSI-RS signal will be found. In related embodiments, the UE 102 is further informed about any scrambling sequences that are to be applied for CSI-RS.

[00105] In an example, up to 2 MIMO layers may be transmitted within each beam by using different polarizations. More than 2 MIMO layers may be transmitted by using multiple beams. In an example, the UE is configured to discover the available beams and report those discovered beams to the eNB prior to the MIMO data transmissions using suitable reporting messaging. Based on the reporting messaging, the eNB 104 may determine suitable beam directions for the MIMO layers to be used for data communications with the UE 102. In various embodiments, there may be up to 2, 4, 8, 16, 32, or more MIMO layers, depending on the number of MIMO layers that are supported by the eNB 111 and UE 102. In a given scenario, the number of MIMO layers that may actually be used will depend on the quality of the signaling recei ved at the UE 102, and the availability of reflected beams arriving at diverse angles at the UE 02 such that the UE 102 may discriminate the data carried on the separate beams. In an example, the eNB 1 1 1 can communicate control signal messaging (e.g., downlink control information, or DCI) with an antenna panel selection and a beam index selection for the UE to use when receiving data (e.g., via PDSCH) or transmitting data (e.g., via PUSCH).

[00106] In the example scenario 750, the UE 102 may determine angles or other information (such as CSI feedback/report, including beam index, precoder, channel-quality indicator (CQI) or other) for the beams 765 and 770. The UE 102 may also determine such information when received at other angles, such as the illustrated beams 775 and 780. The beams 775 and 780 are demarcated using a dotted line configuration to indicate that they may not necessarily be transmitted at those angles, but that the UE 102 may determine the beam directions of beams 775 and 780 using such techniques as receive beam-forming, as receive directions. This situation may occur, for example, when a transmitted beam reflects from an object in the vicinity of the UE 102, and arrives at the UE 102 according to its reflected, rather than incident, angle.

[00107] In an example, antenna switching in an LTE communication system supports spatial diversity schemes at the UE. The antenna switching can be applied at the UE transmitter (i.e. for uplink

communications) and/or at the UE receiver (i.e. for downlink

communication). In the antenna switching in the receiving mode, the UE does not process the signals received by all receiving antennas. Instead, the UE can dynamically use the antenna subset that have optimal instantaneous link conditions to the eNB transmitter, and only processes the signals received by those antennas. This technique can enable the receiver to employ smaller number of transceiver units (TXRUs) or radio frequency (RF) chains. Similarly, in transmit antenna switching, the UE transmitter employs smaller number of TXRUs or RF chains than the available number of antennas. For example, for typical uplink implementation of LTE, the UE can be equipped with two antenna elements for the receiving mode (i.e., for downlink communications) and only one antenna element in transmitting mode (i.e., for uplink communications). The smaller number of Tx antenna elements is used to reduce the hardware cost and achieve greater energy efficiency at the UEs. Different number of transmit and receive antennas in this case makes the antenna switching in the uplink an attractive technology to support diversity schemes in a cost efficient manner.

[00108] FIG. 8 illustrates example information flow 800 for on- demand system information transmission in accordance with some embodiments. Referring to FIG. 8, the communication flow 800 can take place between an example eNB 802 and a UE 804. At the initial access stage 806, eNB 802 can transmit primary synchronization signal (PSS) multiple times to enable UE receiver beam sweeping to obtain approximate time/frequency information as well as a UE receive (RX) beam index. In some embodiments, the UE can perform signal quality measurements on the received synchronization signals in order to determine an optimal beam index. The UE 804 can then use the RX beam index to receive the secondary synchronization signal (SSS) and a physical broadcast channel (PBCFI), which allows the UE to obtain the cyclic prefix length or default guard interval (GI) length, physical cell ID (PCI) information, system frame number (SFN) information, carrier information, the power control factor, as well as other information carried by the PSS and SSS signals.

[00109] At 808, the UE 804 can utilize the same beam index to transmit a system information request to the eNB 802. In an example embodiment, a particular RACH sequence of a plurality of available RACH sequences on specific resource blocks (RBs) can be reserved and defined for purposes of communicating the system information request. The UE 804 can be configured to transmit this particular RACH sequence with the specific RBs without SIB2 information. Similar to an RACH transmission, the system information (SI) request can be repeated over multiple symbols, to enable the eNB 802 to preform receive beam sweeping to receive the SI request using an RX eNB beam. [00110] Λί 810, after receiving the SI request, the eNB 802 can be configured to transmit the essential system information (e.g., SIB 3 and SIB2) to the requesting UE using the eNB beam index determined based on the received SI request at 808. The SIB1 and SIB2 information can be transmitted over a physical downlink shared channel (PDSCH), with a system information radio network temporary identifier (SI-RNTI). The SIB1 information can include Public Land Mobile Network Identity (PLMN-ID) information, physical cell identity (PCI) information, and cell frequency band indicator. The SIB2 information can include random access channel (RACH) parameters, idle mode paging configurations, physical uplink control channel (PUCCH) configurations, physical uplink shared channel (PUSCH) configurations, uplink power control and sounding reference signal configurations, and uplink carrier frequency information.

[00111] At 810, UE 804 can receive SIB 1/SIB2 using the RX beam estimated from the beam sweep during the PSS reception at 806. Once the UE 804 receives the SIB1/SIB2 from the eNB 802, at 812, UE 804 can proceed with normal RACH procedure.

[00112] In this regard, instead of always-on, periodic, and TX beam swept broadcasting of system information, eNB 802 can be configured to transmit the system information when it is requested. Additionally, the UE 804 can be configured to use a specific TX beam (e.g., a RACH sequence) trained for the requesting UE, thus saving the overhead for system information broadcasting, especially for a small cell with fewer UEs trying to perform initial access.

[00113] In some embodiments, a dedicated sequence other than a RACH sequence) can be used to communicate the system information request at 808. For example, a Zadoff-Chu (ZC) sequence can be used to communicate the system information request, where the ZC sequence can be generated based on a physical ceil ID (PCI).

[00114] In some embodiments, one dedicated sequence from a plurality of available xPRACH sequences can be reserved to trigger the SI request at 808. [00115] FIG. 9A and FIG. 9B illustrate example subframes for transmission of a system information request in accordance with some embodiments. In an example embodiment, to save the overhead of communicating the SI request, the dedicated sequence for SI trigger can be transmitted without duplication, as illustrated in FIG. 9 A. Referring to FIG. 9A, there is illustrated a diagram 900 A of an example sub frame 908, which can be used to communicate the system information request at 808. As seen in FIG. 9A, a single SI request sequence 902 can be transmitted within slots 906 of subframe 908. The SI request sequence 902 can be followed by PUSCH or PRACH data. After the SI request is received, the eNB can be configured to utilize a quasi-omni beam to detect and receive the SI request. Since more than one UE may transmit the SI request at the same time, utilizing a quasi-omni beam (e.g., a wider beam that can be used to receive signals from multiple directions) for SI request reception and SI configuration, instead of a UE specific beam, can ensure that multiple UEs can share the SI configuration concurrently. After the UE receives the system information configuration, duplicated xPRACH can be transmitted for UE specific beam training at the eNB side.

[00116] Referring to FIG. 9B, diagram 900B illustrates a subframe 916 which can be used for communicating multiple SI requests. More specifically, subframe 916 can include multiple SI request sequences 910A, 910B, and 910C. Each of the SI requests can be communicated within a single slot, such as slot 914. In this regard, by performing a duplicated transmission of the SI request, the communication link quality of the SI request as well as the detection probability can be improved, enabling beam training at the eNB side. After beam training has completed at the eNB side, the eNB and UE sides are paired, transmission of PUSCH or PRACH data 912 can take place.

[00117] In some embodiments, a window for SI configuration can be pre-defined, where the SI configuration within the window can be continuously transmitted by the eNB, so that the UE can employ incremental redundancy to combine the received SI. In instances when the UE fails to detect the SI configuration, a new SI request can be triggered for the next attempt.

[00118] In some embodiments, the window for SI confirmation can be pre-defined or configured by higher layer signaling, and the xPRACH information for initial access can be considered as an SI confirmation. In instances when the window expires, the e^'NB can be configured to retransmit the SI. In some embodiments, the size of the SI configuration windows can be larger than the size of the SI confirmation window. Hence, if the SI configuration window expires, the eNB w can be configured not to transmit SI until it receives a new SI request.

[00119] In some embodiments, the time/frequency resource for SI trigger can be predefined or be generated based on PCI to avoid inter-ceil interference. The duplicated beam formed synchronous signals can be transmitted by the eNB through one or multiple panels in either FDM or TDM fashion. The UE can be configured to train its receiving beam, and may select one preferred TX beam.

[00120] In some embodiments, one single resource, with respect to the time/frequency/code domain resource, can be reserved for

communicating the SI request. Regardless of which TX beam the UE has selected as a preferred beam, the SI request can be communicated based on the single resource. The SI configuration can be transmitted with the same beam pattern as synchronous signals within the configured SI transmission window. The UE can then receive the SI information for chase combining, until it correctly receives the SI configuration.

[00121] In some embodiments, multiple resources, with respect to the time/frequency/code domain resources, can be reserved for the SI trigger transmission. In some embodiments, one SI resource can be associated to one or multiple synchronous signals. After receipt of the synchronization signals, besides beam training, the UE can select one preferred TX beam, and send the SI request at the corresponding resource, and then the eNB can be configured to transmit the SI configuration based on the corresponding beams associated to this resource. [00122] In some embodiments, paging messages (e.g., 190) can be generated by the MME 121 and send through multiple cells within the same tracking area (e.g cells associated with the eNBs 1 1 1 and 112). In some embodiments, the paging message 190 can include paging information associated with one or more UEs. In this regard, a paging message can be sent using a different beamforming weight than the beamforming weight used for a unicast PDSCH message. In some embodiments, the paging message 190 can be communicated to the UEs 101 and 02 using different techniques. For example, each eNB can perform beam scanning to obtain a transmit beam, and the paging message can be communicated in multiple directions to ensure omni coverage. In some embodiments, each of the eNBs can communicate the paging message 190 using a quasi-omni beam (e.g., a single transmission using a wider beam in order to cover multiple directions).

[00123] In mid-band (carrier frequency between 6 GHz and 30 GHz) and high-band (carrier frequency beyond 30 GHz), wider subcarrier spacing can be used to improve the error vector magnitude (EVM) due to phase noise. In some embodiments, 1ms subframe can be used to provide the timing reference, while a scheduling unit of slot or mini-slot within the subframe can be used. In high-band communications, taking the subcarrier spacing of 480kHz as an example, the number of OFDM symbols (or slots) within a 1ms subframe may reach 480 symbols. From multiplexing with PDSCH point of view, due to different TX beamforming used, it can be efficient to time division multiplex (TDM) paging message with unicast PDSCH. In reference to UE power consumption, defining a short paging occasion (PO) based on slot or mini-slot can provide UE power saving.

[00124] In an example embodiment, the paging message can be transmitted within a slot (or mini slot) in one subframe, so as to improve the efficiency and save the UE power. In instances when fewer antenna panels are equipped at the eNB side, constraining one specific signal into slot/mini slot can release the constraint from the beam forming point view. On the other hand, the alignment of different eNBs to transmit the paging in a single frequency network (SFN) fashion can be localized to a slot/mini- slot instead of a whole subframe.

[00125] FIG. lOA and FIG. 10B illustrate example paging transmissions within a subframe in accordance with some embodiments. Referring to FIG. I OA, there is illustrated an example paging transmission lOOO.A, which can include transmission of subframes 1002 and 1004 with a paging signal at the end of the subframes. The transmission of subframe 1002 can start with a physical downlink control channel (PDCCH) 1006 followed by a paging occasion with paging duration 1018. The paging occasion can include a demodulation reference signal (DMRS) 1008 and a paging signal 1010. Similarly, the transmission of subframe 1004 can start with PDCCH 1012 followed by a paging occasion that includes DMRS 014 and a paging signal 10 6.

[00126] Referring to FIG. 10B, there is illustrated an example paging transmission 1000B, which can include transmission of subframes 1020 and 1022 with a paging signal at the beginning of the subframes. The transmission of subframe 1020 can start with a PDCCH 1024 followed by a paging occasion with paging duration 036. The paging occasion can include a DMRS 026 and a paging signal 028. Similarly, the

transmission of subframe 1022 can start with PDCCH 1030 followed by a paging occasion that includes DMRS 1032 and a paging signal 1034.

[00127] In some embodiments, the paging duration 1018 spans

Npaging number of slots/mini-slots within a subframe, based on the definition of RANI frame structure. In some embodiments, the paging duration Npaging can be pre-defined or transmitted by higher layer signaling, such as master Information Block signaling (xMIB), System Information Block signaling (xSIB), or radio resource control (RRC) signaling.

[00128] In some embodiments, the starting slot/mini-slots index can be pre-defined or configured by the eNB through higher layer signaling or dynamically configured by downlink control information (DCI). As illustrated in FIG. 10A and FIG. 10B, the paging message can be transmitted at either the front or the end portion of the slot or mini slots. In some embodiments, one paging occasion can include frame, subframe, and slot/mini-slot. In some embodiments, multiple paging occasion can be transmitted within one subframe, and an example is illustrated in FIG. 1 1 A and FIG. 1 I B.

[00129] FIG. 11 A and FIG. 1 IB illustrate example multiple paging occasions within a subframe in accordance with some embodiments. In some embodiments and as illustrated in FIG. 1 LA, the paging occasions can be configured for transmission back-to-back, concatenated with each other within a single subframe, where each paging occasion contains both DMRS and paging data. Referring to FIG. 1 1 A, there is illustrated an example subframe 1 102 with concatenated paging occasions. More specifically, subframe 1102 includes paging messages 1 106, 1110, 1114, and 1118, with a corresponding DMRS preceding each paging message (e.g., DMRSs 1 104, 1108, 1 1 12, and 1 116, respectively).

[00130] Referring to FIG. 1 IB, there is illustrated an example subframe 1118 with multiple paging occasions separated by gaps. More specifically, subframe 1 1 18 includes paging messages 1122, 1 126, and 1130, with a corresponding DMRS preceding each paging message (e.g., DMRSs 1 120, 1124, and 1 128, respectively).

[00131] FIG. 1 I B further indicates the starting OFDM symbol for the first paging transmission 1122 at the slot or mini slot as 1 134 (or NO). The starting slot NO can be configured by the eNB through higher layer signaling, or can be pre-defined as a fixed number. The paging duration 1132 can include the duration of the DMRS 1120 and the duration of the paging message 1122. The gap between the paging message (e.g., 1 122) and the DMRS of the subsequent paging occasion (e.g., DMRS 1 124) can be indicated as 1136 (or Ngap). The next paging occasion can starts at the (NO + Ngap) slot or mini slot. In some embodiments, multiple paging occasions can evenly span within one subframe, where the slot or mini slot gap duration (e.g., Ngap) can be is configured by higher layer signaling or pre-defined. In some embodiments, the total number of paging occasions within one subframe can be configured by the eNB through higher layer signaling or can be pre-defined. [00132] FIG. 12 illustrates an example aggregated DMRS transmission with paging occasions in accordance with some embodiments. In some embodiments, multiple eNBs within the same tracking area can be configured to transmit the paging information with quasi-omni direction in a single frequency network (SFN) configuration. A single UE can be configured to select one preferred Rx beam to receive the paging information to improve the link quality. In some embodiments and as illustrated in FIG. 12, multiple DMRS symbols can be assigned at the beginning of paging occasions, which can enable the UE to refine the synchronous information, and refine the Rx beam based on the multiple DMRS. As seen in FIG. 12, subframe 1200 includes multiple DMRS configured at the front of the paging content. More specifically, DMRSs 1202, 1204, 1206, and 1208 are configured prior to the paging messages 1210, 1212, 1214, and 1216.

[00133] In some embodiments, the subframe for paging transmission can include at least one beam refinement reference signal (BRRS), which can be inserted at the beginning of the subframe. The BRRS is transmitted by multiple eNBs (e.g., in a single frequency network (SFN) fashion), and can be used by the UE to refine the RX beam. In some embodiments, multiple paging entries can share one DMRS for channel estimation to reduce the overhead. In some embodiments, each paging entry can be transmitted with one DMRS for accurate channel estimation.

[00134] FIG. 13A and FIG. 13B illustrate transmission of beam refinement reference signals (BRRS) with paging occasions in accordance with some embodiments. Referring to FIG. 13 A, subframe 1300 A can include one or more BRRS (e.g., 1302 and 1304), which can be transmitted before the paging occasions. More specifically, BRRS 1302 and 1304 can be transmitted prior to the DMRS 1306 associated with the first paging message 1308. Subsequent paging messages 1310, 1312, and 1314 can be transmitted after the first paging message 1308,

[00135] Referring to FIG. 13B, subframe 1300B can include one or more BRRS (e.g., 1316 and 1318), which can be transmitted before the paging occasions. In some embodiments, each paging message can be preceded by a DMRS for channel estimation. BRRS 1316 and 1318 can be transmitted prior to the DMRS 1320 associated with the first paging message 1322. Subsequent paging messages 1326, 1330, and 1334 can be preceded by DMRS 1324, 1328, and 1332 and can be transmitted after the first paging message 1308.

[00136] In some embodiments, the time/frequency /code resource for

BRRS can be configured by the eNB through higher layer signaling. In some embodiments, to guarantee the coverage area of paging, paging messages can be transmitted in a repeated fashion, as seen in FIGS. 14A- 14C.

[00137] FIG. 14A, FIG. 14B, and FIG. 14C illustrate example repeated paging transmissions within a single subframe in accordance with some embodiments. Referring to FIG. 14A, there is illustrated a subframe 1402 with a repeated transmission of a paging message. More specifically, the same paging message can be transmitted at paging occasions 1406,

1410, 1414, and 1418. Each paging message transmission can be preceded by a DMRS, such as 1404, 1408, 1412, and 1416.

[00138] Referring to FIG. 14B, there is illustrated a subframe 1420 with a repeated transmission of a paging message. More specifically, the same paging message can be transmitted at paging occasions 1424, 1426, 1428, and 1430. The first paging message transmission (e.g., 1424) can be preceded by a DMRS 1422.

[00139] Referring to FIG. I4C, there is illustrated a subframe 1432 with a repeated transmission of a paging message. More specifically, the same paging message can be transmitted at paging occasions 1440, 1442, 1444, and 1446. The paging message transmission can be preceded by multiple DMRS transmissions, such as 1434, 1436, 1438, and 1440.

[00140] In some embodiments, the number of repetitions of the paging message can be configured by eNB through higher layer signaling. In some embodiments, the number of DMRS repetitions can be either the same or different as the repetition times of the paging data. In this regard, the repetition times of the DMRS and the paging data can be configured jointly or separately. In some embodiments, multiple repeated paging occasions can be multiplexed within one subframe.

[00141] In some embodiments, the PDCCH can be repeatedly transmitted within multiple OFDM symbols of a subframe, by multiple e Bs in a single frequency network (SFN) fashion (i.e., transmissions by multiple eNBs at the same frequency). FIG. 15 illustrates an example subframe with repeated transmission of PDCCH and paging messages in accordance with some embodiments. Referring to FIG. 15, subframe 500 can include an initial transmission of multiple BRRSs (e.g., 1502, 1504, and 1506), Multiple PDCCH symbols (e.g., 1510, 1512, 1514, and 1516) can share the same DMRS (e.g., 1508) to reduce the overhead. The BRRS signals (e.g., 1502-1506) can be inserted before the PDCCH transmissions, so that the PDCCH transmissions can be received based on the refined RX beam after BRRS reception. The combined duration of PDCCH

transmissions can be indicated as rep.pdcch 1526, and can be configured by higher layer signaling. Multiple paging transmissions (e.g., 1520 and 1522) can take place after the DMRS 1518.

[00142] In some embodiments, Ngap OFDM symbols (1524) can be inserted between the BRRS transmissions and the PDCCH transmissions for digital signal processing. In some embodiments, the gap 1 524 can be 0. In some embodiments, to align the slot or mini slots boundary, the duration of the BRRS transmissions and the PDCCH transmissions can be an integral times of slot or mini slots. In some embodiments, the repetition times for PDCCH and PDSCH carrying paging information can be either different or the same.

[00143] In some embodiments, if multiple paging occasions are configured within one subframe, they can be configured by a single PDCCH. In this PDCCH, a bit map can be transmitted, where one bit corresponds to one paging entry. For instance, if four entries are transmitted within one subframe (as in FIG. 15), then 4-bit length bit map can be configured within the DCL The bitmap "0 0 1 1" can be interpreted to indicate that the second and the third paging entries are transmitted. [00144] In some embodiments, the paging message can be transmitted using a quasi-omni beam transmission from multiple ceils, which forms a single frequency network (SFN), and longer delay spread can be expected. In some embodiments, due to guard interval discrete Fourier transform spread orthogonal frequency division multiplexing (GI- DFT-S-OFDM) waveform, the guard interval (GI) length can be adjusted within one or multiple slots/mini-slots without affecting the subframe boundary. In some embodiments, the GI length can be configured together with the paging occasion configuration (e.g., through higher layer signaling),

[00145] FIG. 16, FIG. 17, and FIG. 18 are flow diagrams illustrating example functionalities for on-demand system information transmission in accordance with some embodiments. Referring to FIG. 16, the example method 1600 can start at 1602, when a beam index is determined during a beam sweeping procedure, based on a signal quality metric associated with a received synchronization signal (e.g., at 806). At 1604, a random access procedure (RACH) preamble sequence can be encoded for directional transmission based on the beam index (e.g., at 808). The RACH preamble sequence can include a system information request. At 1606, system information configuration received in response to the system information request can be decoded (e.g., at 810). At 1608, a RACH process can be initiated (e.g., at 812), using at least another RACH preamble sequence, based on the received system information configuration.

[00146] Referring to FIG. 17, the example method 1700 can start at 1702, when a received random access procedure (RACH) preamble sequence can be decoded. For example, eNB 802 can receive the RA CH preamble sequence, which can include a system information request (e.g., as seen at 808). At 1704, a beam index used to receive the RACH preamble sequence can be derived (e.g., by the eNB 802). At 1706, system information configuration can be encoded in response to the system information request. The system information configuration can be transmitted (e.g., by the eNB 802 at step 810) using the derived beam index. At 1708, at least another received RACH preamble sequence can be decoded at the eNB 802 (e.g., at step 812). The at least another RACH preamble sequence can be based on the system information configuration and can be used to initiate a RACH process.

[00147] Referring to FIG. 18, the example method 1800 can start at 1802, when a beam sweeping procedure is performed using a beam refinement reference signal (BRRS) within a received subframe, to determine a beam index. For example, the UE 101 can receive subframe 1300 A and can perform a beam sweeping procedure using the BRRS 1302 and 1304. At 1804, in response to decoding a paging signal within the received subframe, the UE can be configured to encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence. The RACH preamble sequence can include a system information request. At 1806, system information configuration received in response to the system information request can be decoded (e.g., the system information configuration received at 810). At 808, a RACH process can be initiated using at least another RACH preamble sequence, based on the received system information configuration.

[00148] FIG. 19 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), an access point (AP), a wireless station (STA), or a user equipment (UE), in accordance with some embodiments. In alternative embodiments, the communication device 1900 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 1900 may operate in the capacity of a server communication device, a client communication device, or both in server-client network environments. In an example, the communication device 1900 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment. The communication device 1900 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single communication device is illustrated, the term "communication device" shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a sendee (SaaS), other computer cluster configurations.

[00149] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a communication device readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[00150] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. [00151] Communication device (e.g., LIE) 1900 may include a hardware processor 1902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1904 and a static memory 1906, some or all of which may communicate with each other via an interlink (e.g., bus) 1908. The communication device 1900 may further include a display unit 1910, an alphanumeric input device 1912 (e.g., a keyboard), and a user interface (UI) navigation device 1914 (e.g., a mouse). In an example, the display unit 1910, input device 1912 and UI navigation device 1914 may be a touch screen display. The communication device 1900 may additionally include a storage device (e.g., drive unit) 1916, a signal generation device 1918 (e.g., a speaker), a network interface device 1920, and one or more sensors 1921, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 1900 may include an output controller 1928, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[00152] The storage device 1916 may include a communication device readable medium 1922 on which is stored one or more sets of data structures or instructions 1924 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1924 may also reside, completely or at least partially, within the main memory 1904, within static memory 1906, or within the hardware processor 1902 during execution thereof by the communication device 1900. In an example, one or any combination of the hardware processor 1902, the main memory 1904, the static memory 1906, or the storage device 1916 may constitute communication device readable media,

[00153] While the communication device readable medium 1922 is illustrated as a single medium, the term "communication device readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 1924, [00154] The term "communication device readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 1900 and that cause the communication device 1900 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of communication device readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory- devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device readable media may include non-transitory communication device readable media. In some examples, communication device readable media may include communication device readable media that is not a transitory propagating signal ,

[00155] The instructions 1924 may further be transmitted or received over a communications network 1926 using a transmission medium via the network interface device 1920 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol ( TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 1920 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1926. In an example, the network interface device 1920 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISQ) techniques. In some examples, the network interface device 1920 may wirelessly communicate using Multiple User MIMO techniques. The term

"transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 1900, and includes digital or analog

communications signals or other intangible medium to facilitate communication of such software.

[00156] Additional notes and examples:

[00157] Example 1 is an apparatus of a user equipment (UE), the apparatus comprising: processing circuitry, the processing circuitry configured to: determine a beam index during a beam sweeping procedure, based on a signal quality metric associated with a received synchronization signal; encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request; decode system

information configuration received in response to the system information request, and initiate a RACH process using another RACH preamble sequence, based on the received system information configuration, and memory configured to store the system information configuration.

[00158] In Example 2, the subject matter of Example 1 includes, wherein the encoded RACH preamble sequence with the system

information request is transmitted multiple times using the preferred beam index.

[00159] In Example 3, the subject matter of Examples 1-2 includes, wherein the processing circuitry is configured to: decode higher layer signaling identifying the RACH preamble sequence from a plurality of available RACH preambles sequences, as reserved for encoding the system information request.

[001 0] In Example 4, the subject matter of Example 3 includes, wherein the higher layer signaling identifies one or more resource blocks (RBs) within the RACH preamble sequence for encoding the system information request.

[001 1] In Example 5, the subject matter of Examples 1-4 includes, wherein the system information configuration comprises one or more of a master information block (MIB), a system information block 1 (SIB l), and a system information block 2 (SIB2).

[00162] In Example 6, the subject matter of Example 5 includes, wherein the MIB comprises: downlink channel bandwidth; Physical Hybrid- ARQ Indicator Channel (PHICH) configuration information; and system frame number (SFN) information.

[00163] In Example 7, the subject matter of Examples 5-6 includes, wherein the SIB l comprises: Public Land Mobile Network Identity

(PLMN-ID) information; physical cell identity (PCI) information; and cell frequency band indicator.

[00164] In Example 8, the subject matter of Examples 5-7 includes, wherein the SIB2 comprises: random access channel (RACH) parameters; idle mode paging configurations; physical uplink control channel (PUCCH) configurations; physical uplink shared channel (PUSCH) configurations; uplink power control and sounding reference signal configurations; and uplink carrier frequency information.

[00165] In Example 9, the subject matter of Examples 1-8 includes, wherein the RACH preamble sequence is a Zadoff-Chu (ZC) sequence, the ZC sequence generated based on physical cell identity information.

[00166] In Example 10, the subject matter of Examples 1-9 includes, transceiver circuitry coupled to the processing circuitry; and, one or more antennas coupled to the transceiver circuitry,

[00167] In Example 1 1, the subject matter of Example 10 includes, wherein the transceiver circuitry is configured to transmit the RACH preamble sequence with the system information request without

duplication. [00168] In Example 12, the subject matter of Examples 10-11 includes, wherein the transceiver circuitry is configured to transmit the RACH preamble sequence with the system information request with duplication within a single subframe.

[00169] In Example 13, the subject matter of Examples 1-12 includes, wherein the processing circuitry is configured to: decode higher layer signaling indicating a time/frequency resource for the system information request; and encode the RACH preamble sequence for directional transmission using the indicated time/frequency resource.

[00170] In Example 14, the subject matter of Examples 1-13 includes, wherein the processing circuitry is configured to: decode downlink control information (DO) including a frame index, a subframe index, and a slot index associated with a paging occasion; and decode a paging signal received during the paging occasion.

[00171] Example 15 is an apparatus of a Node-B (NB), the apparatus comprising: memory; and processing circuitry, configured to: decode a received random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request; derive a beam index used to receive the RACH preamble sequence, encode system information configuration in response to the system information request, the system information configuration for transmission using the derived beam index; and decode another received RACH preamble sequence, the another RACH preamble sequence based on the system information configuration and initiating a RACH process.

[00172] In Example 16, the subject matter of Example 15 includes, wherein the processing circuitry is configured to: encode a synchronization signal for multiple transmissions to enable a beam sweeping procedure at a user equipment (UE), wherein the beam index is selected during the beam sweeping procedure.

[00173] In Example 17, the subject matter of Example 16 includes, wherein the synchronization signal comprises one or both of a primary synchronization signal (PSS) and a secondary synchronization signal (SS;

[00174] In Example 18, the subject matter of Examples 15-17 includes, wherein the system information configuration comprises one or more of a master information block (ΜΪΒ), a system information block 1 (SIBl), and a system information block 2 (SIB2).

[00175] In Example 19, the subject matter of Examples 15-18 includes, wherein the RACH preamble sequence is received using a quasi- omni beam.

[00176] In Example 20, the subject matter of Examples 15-19 includes, wherein the processing circuitry is configured to: decode multiple received versions of the RACH preamble sequence to derive the beam index.

[00177] In Example 21 , the subject matter of Examples 15-20 includes, wherein the processing circuitry is configured to: encode the system information configuration for multiple transmissions using the derived beam index during a pre-defined timing window.

[00178] In Example 22, the subject matter of Examples 15-21 includes, wherein the processing circuitry is configured to: upon failure to receive the another RACH preamble sequence, encode the system information configuration for re-transmission using the derived beam index.

[00179] In Example 23, the subject matter of Examples 15-22 includes, wherein the processing circuitry is configured to: encode a paging message for transmission within a cell of the NB using a quasi-omni beam.

[00180] In Example 24, the subject matter of Example 23 includes, wherein the processing circuitry is configured to: encode the paging message for transmission over Npaging number of slots within a subframe, wherein Npaging is an integer greater than I that is pre-defined by higher layer signaling.

[00181] In Example 25, the subject matter of Example 24 includes, wherein the higher layer signaling is one of: master information block (MIB) signaling; system information block (SIB) signaling; or radio resource control (RRC) signaling.

[00182] In Example 26, the subject matter of Examples 23-25 includes, wherein the processing circuitry is configured to: encode the paging message for a single transmission within a slot of a physical downlink shared channel (PDSCH) subframe. [00183] In Example 27, the subject matter of Examples 23-26 includes, wherein the processing circuitry is configured to: encode the paging message for multiple transmissions within a slot of a physical downlink shared channel (PDSCH) subframe using different transmit beams.

[00184] In Example 28, the subject matter of Examples 23-27 includes, wherein the processing circuitry is configured to: encode multiple paging messages for transmissions within corresponding multiple slots of a physical downlink shared channel (PDSCH) subframe using the quasi-omni beam, the multiple paging messages for a plurality of UEs within the cell of the B.

[00185] In Example 29, the subject matter of Example 28 includes, wherein the processing circuitry is configured to: encode a single demodulation reference signal (DMRS) for transmission before the multiple paging messages.

[00186] In Example 30, the subject matter of Examples 28-29 includes, wherein the processing circuitry is configured to: encode a demodulation reference signal (DIviRS) for transmission before each of the multiple paging messages.

[00187] In Example 31, the subject matter of Examples 23-30 includes, wherein the processing circuitry is configured to: encode multiple demodulation reference signals (DMRSs) for transmission before the paging message, the multiple DMRSs and the paging message for transmission within a single subframe of a physical downlink shared channel (PDSCH),

[00188] In Example 32, the subject matter of Examples 23-31 includes, wherein the processing circuitry is configured to: encode multiple beam refinement reference signals (BRRSs) for transmission before the paging message, the multiple BRRSs and the paging message for transmission within a single subframe of a physical downlink shared channel (PDSCH).

[00189] In Example 33, the subject matter of Example 32 includes, wherein the processing circuitry is configured to: encode a single demodulation reference signal (DMRS) for transmission with the multiple BRRSs and the paging message within the single subframe of the PDSCH.

[00190] In Example 34, the subject matter of Example 33 includes, wherein the multiple BRRSs originate from the NB and at least another NB, and are encoded for transmission in a single frequency network (SFN) fashion.

[00191] In Example 35, the subject matter of Examples 33-34 includes, wherein the single DMRS is encoded for transmission with multiple paging messages.

[00192] In Example 36, the subject matter of Examples 33 -35 includes, wherein the processing circuitry is configured to: encode a physical downlink control channel (PDCCH) for transmission with the multiple BRRSs and the paging message within the single subframe of the PDSCH.

[00193] In Example 37, the subject matter of Example 36 includes, wherein the PDCCH comprises downlink control information (DCI) indicating downlink resource assignment for the paging message.

[00194] In Example 38, the subject matter of Examples 36-37 includes, wherein the single subframe includes at least another PDCCH associated with at least another NB, the PDCCH and the at least another PDCCH encoded for transmission in a single frequency network (SFN) fashion.

[00195] In Example 39, the subject matter of Examples 15-38 includes, wherein the NB is one of a Next Generation Node-B (gNB) or an Evolved Node-B (eNB),

[00196] Example 40 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the instructions to configure the one or more processors to cause the UE to: perform a beam sweeping procedure using a beam refinement reference signal (BRRS) within a received subframe, to determine a beam index: in response to decoding a paging signal within the received subframe, encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request; decode system information configuration received in response to the system information request; and initiate a RACH process using another RACH preamble sequence, based on the received system information configuration.

[00197] In Example 41, the subject matter of Example 40 includes, wherein the instructions further cause the UE to: decode a demodulation reference signal (DMRS) within the subframe, the DMRS for estimating a physical downlink shared channel (PDSCH) associated with the paging signal.

[00198] In Example 42, the subject matter of Examples 40- 1 includes, wherein the instructions further cause the UE to: transmit the RACH preamble sequence with the system information request without duplication.

[00199] In Example 43, the subject matter of Examples 40-42 includes, wherein the instructions further cause the UE to: transmit the RACH preamble sequence with the system information request with duplication within a single subframe.

[00200] Example 44 is an apparatus of a user equipment (UE), the apparatus comprising: means for determining a beam index during a beam sweeping procedure, based on a signal quality metric associated with a received synchronization signal; means for encoding for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request, means for decoding system information configuration received in response to the system information request; and means for initiating a RACH process using another RACH preamble sequence, based on the received system information configuration.

[00201] In Example 45, the subject matter of Example 44 includes, wherein the encoded RACH preamble sequence with the system

information request is transmitted multiple times using the preferred beam index.

[00202] In Example 46, the subject matter of Examples 44- 5 includes, wherein the apparatus further comprises: means for decoding higher layer signaling identifying the RACH preamble sequence from a plurality of available RACH preambles sequences, as reserved for encoding the system information request.

[00203] In Example 47, the subject matter of Example 46 includes, wherein the higher layer signaling identifies one or more resource blocks (RBs) within the RACH preamble sequence for encoding the system information request.

[00204] In Example 48, the subject matter of Examples 44-47 includes, wherein the system information configuration comprises one or more of a master information block (MIB), a system information block 1 (SIB1), and a system information block 2 (SIB2).

[00205] Example 49 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-48.

[00206] Example 50 is an apparatus comprising means to implement of any of Examples 1-48.

[00207] Example 51 is a system to implement of any of Examples 1-

48.

[00208] Example 52 is a method to implement of any of Examples 1-48.

[00209] Although an aspect has been described with reference to specific example aspects, it will be evident that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific aspects in which the subject matter may be practiced. The aspects illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other aspects may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00210] Such aspects of the inventive subject matter may be referred to herein, individually and/or collectively, merely for convenience and without intending to voluntarily limit the scope of this application to any single aspect or inventive concept if more than one is in fact disclosed. Thus, although specific aspects have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific aspects shown. This disclosure is intended to cover any and all adaptations or variations of various aspects. Combinations of the above aspects, and other aspects not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[00211] The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single aspect for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed aspects require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed aspect. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate aspect.

Claims

What is claimed is:

1. An apparatus of a user equipment (UE), the apparatus comprising: processing circuitry, the processing circuitry configured to:

determine a beam index during a beam sweeping procedure, based on a signal quality metric associated with a received synchronization signal ;

encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence, the

RACH preamble sequence including a system information request; decode system information configuration received in response to the system information request; and

initiate a RACH process using another RACH preamble sequence, based on the received system information configuration; and

memory configured to store the system information configuration.

2. The apparatus of claim 1, wherein the encoded RACH preamble sequence with the system information request is transmitted multiple times using the preferred beam index.

3. The apparatus of any of claim s 1-2, wherein the processing circuitry is configured to:

decode higher layer signaling identifying the RACH preamble sequence from a plurality of available RACH preambles sequences, as reserved for encoding the system information request.

4. The apparatus of claim 3, wherein the higher layer signaling identifies one or more resource blocks (RBs) within the RACH preamble sequence for encoding the system information request.

5. The apparatus of any of claims 1-2, wherein the system information configuration comprises one or more of a master information block (MIB), a system information block 1 (SIBl), and a system information block 2 (SIB2).

6. The apparatus of claim 5, wherein the MIB comprises:

downlink channel bandwidth;

Physical Hybrid-ARQ Indicator Channel (PHICH) configuration information; and

system frame number (SFN) information.

The apparatus of claim 5, wherein the SIB l comprises:

Public Land Mobile Network Identity (PLMN-ID) information; physical cell identity (PCI) information, and

cell frequency band indicator.

8, The apparatus of claim 5, wherein the SIB 2 comprises:

random access channel (RACH) parameters;

idle mode paging configurations;

physical uplink control channel (PUCCH) configurations;

physical uplink shared channel (PUSCH) configurations;

uplink power control and sounding reference signal configurations; and

uplink carrier frequency information.

9. The apparatus of claim 1, wherein the RACH preamble sequence is a ZadofF-Chu (ZC) sequence, the ZC sequence generated based on physical cell identity information.

10. The apparatus of claim 1 , further comprising transceiver circuitry coupled to the processing circuitry; and, one or more antennas coupled to the transceiver circuitry.

1 1. The apparatus of claim 10, wherein the transceiver circuitry is configured to transmit the RACH preamble sequence with the system information request without duplication,

12. The apparatus of any of claims 10-11, wherein the transceiver circuitry is configured to transmit the RACH preamble sequence with the system information request with duplication within a single subframe,

13. An apparatus of a Node-B (NB), the apparatus comprising:

processing circuitry, configured to:

decode a received random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request;

derive a beam index used to receive the RACH preamble sequence;

encode system information configuration in response to the system information request, the system information configuration for transmission using the derived beam index; and

decode another received RACH preamble sequence, the another RACH preamble sequence based on the system information configuration and initiating a RACH process, and

memory configured to store the beam index.

14. The apparatus of claim 13, wherein the processing circuitry is configured to:

encode a synchronization signal for multiple transmissions to enable a beam sweeping procedure at a user equipment (UE), wherein the beam index is selected during the beam sweeping procedure.

15. The apparatus of claim 14, wherein the synchronization signal comprises one or both of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).

16. The apparatus of any of claims 14-15, wherein the system information configuration comprises one or more of a master information block (MIB), a system information block 1 (SIB1), and a system information block 2 (SIB2). 7. The apparatus of any of claims 14-15, wherein the RACH preamble sequence is received using a quasi-omni beam.

18. The apparatus of any of claims 14-15, wherein the processing circuitry is configured to:

decode multiple received versions of the RACH preamble sequence to derive the beam index.

19. The apparatus of claim 13, wherein the processing circuitry is configured to:

encode the system information configuration for multiple transmissions using the derived beam index during a pre-defined timing window.

20. The apparatus of claim 13, wherein the processing circuitry is configured to:

upon failure to receive the another RACH preamble sequence, encode the system information configuration for re-transmission using the derived beam index.

21. The apparatus of claim 3, wherein the processing circuitry is configured to:

encode a paging message for transmission within a cell of the NB quasi-omni beam.

22. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the instructions to configure the one or more processors to cause the UE to:

perform a beam sweeping procedure using a beam refinement reference signal (BRRS) within a received subframe, to determine a beam index;

in response to decoding a paging signal within the received subframe, encode for directional transmission based on the beam index, a random access procedure (RACH) preamble sequence, the RACH preamble sequence including a system information request;

decode system information configuration received in response to the system information request; and

initiate a RACH process using another RACH preamble sequence, based on the received system information configuration.

23. The non-transitory computer-readable storage medium of claim 22, wherein the instructions further cause the UE to:

decode a demodulation reference signal (DMRS) within the subframe, the DMRS for estimating a physical downlink shared channel (PDSCH) associated with the paging signal,

24. The non-transitor computer-readable storage medium of any of claims 22-23, wherein the instructions further cause the UE to:

transmit the RACH preamble sequence with the system information request without duplication,

25. The non-transitor computer-readable storage medium of any of claims 22-23, wherein the instructions further cause the UE to:

transmit the RACH preamble sequence with the system information request with duplication within a single subframe.