WO2022031692A1

WO2022031692A1 - Discovery reference signal beamforming randomization

Info

Publication number: WO2022031692A1
Application number: PCT/US2021/044325
Authority: WO
Inventors: Daewon Lee; Prerana Rane; Gang Xiong; Yingyang Li; Seunghee Han
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2020-08-04
Filing date: 2021-08-03
Publication date: 2022-02-10
Anticipated expiration: 2023-02-04

Abstract

Among other things, embodiments of the present disclosure may be directed to beamforming randomization of a discovery reference signal (e.g., synchronization signal block (SSB)) in a wireless cellular network. In one example, a physical beam index for an SSB is determined based on a randomization function, e.g., that uses one or more of a system frame number (SFN) of the SSB, a cell identity (ID), or a generated sequence. Other embodiments may be disclosed and claimed.

Description

DISCOVERY REFERENCE SIGNAL BEAMFORMING RANDOMIZATION

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/060,849, which was filed August 4, 2020.

FIELD

Various embodiments generally may relate to the field of wireless communications. BACKGROUND

In 3GPP Rel-16 NR (FR1), a synchronization signal comprises a primary synchronization signal (PSS), secondary synchronization signal (SSS), and Physical Broadcast channel (PBCH) forms the Synchronization Signal Block (SSB or SS/PBCH block). A discovery reference signal (DRS) transmission includes SSB, remaining minimum system information (RMSI), and an associated physical downlink control channel (PDCCH). A designated location within a designated slot is associated with a unique SSB index which allows the slot/frame timing information to be discovered from SSB index. Also, the beam information of a SSB is determined by a SSB index. Instead of providing an explicit indication of a specific beamforming used by the transmitter, beamforming information is implicitly provided with quasi-co-located (QCL) relationship indication between reference signals. If two reference signals have QCL relationship with respective to Doppler shift, Doppler spread, average channel delay, channel delay spread, and spatial Rx parameters, then the receiver may assume that the two reference signals were transmitted with the same beamforming, or transmitted with sufficiently similar beamforming such that same Rx beamforming could be utilized to receiver the two reference signals. Therefore, for the SSB case, QCL relationship exist between SSB with the same SSB index. For unlicensed band operation below 7 GHz, the QCL relationship exist between SSB with same modulus operated SSB index.

Additionally, the number of beams used per cell is indicated by Q with values {1, 2, 4, 8}. For NR system operations in high carrier frequency, it is expected that signals and channels are mostly transmitted and received using directive beamforming. If multiple cells transmit at the same time, and if the cells are synchronized, the transmission of SSB from multiple cell can collide with each other over the air. If the transmission is periodic, and base station (BS) uses the same beamforming for the SSBs that are transmitted in regular interval, then the inference observed by the receiver would be identical during the SSB transmission period (of multiple cells). That is, the beamformed signals that collide over the air does not change over time. This results in lack of interference randomization and potentially results in performance loss for certain UEs in the system.

Moreover, the SSBs have a fixed sequence of beam directions. A candidate SSB position will have the same beam index, and hence the same beamforming for all cells in the subframe, repeating across all subframes. The interference pattern between cells transmitting the SSB will be static since the beam directions of the SSB are identical for all cells and there will no diversity in the interference patterns between the cells.

BRIEF DESCRIPTION OF THE FIGURES

Figure 1 illustrates a beam index pattern for 3GPP Release 16 New Radio (NR) unlicensed (NR-U).

Figure 2A illustrates physical beam indices derived from the SSB candidate position, which are cyclic and contiguous, in accordance with various embodiments.

Figure 2B illustrates beam indices that are randomized and not dependent on SSB indices, in accordance with various embodiments.

Figure 3 illustrates a beam index pattern generated using (i+SFN+cell ID) mod Q, in accordance with various embodiments.

Figure 4 illustrates a linear feedback shift register of length 4, in accordance with various embodiments.

Figure 5 A illustrates using an overlapping window of bits to generate the random sequences, in accordance with various embodiments.

Figure 5B illustrates a beam index pattern generated with an overlapping window of bits using a length 4 m-sequence with a cell ID used for an initialization sequence, in accordance with various embodiments.

Figure 6 illustrates using a non-overlapping window of bits to generate the random sequences, in accordance with various embodiments.

Figure 7 illustrates a beam index pattern generated with a non-overlapping window of bits using a length 4 m-sequence with a cell ID used for an initialization sequence, in accordance with various embodiments.

Figure 8 illustrates a beam index pattern generated using a length 4 m-sequence with an initialization sequence equal to cell ID + system frame number (SFN), in accordance with various embodiments.

Figure 9 illustrates a sequence divided into chunks of 31 bits to derive the beam index, in accordance with various embodiments.

Figure 10 illustrates a beam index pattern generated using a length 31 Gold code with initialization sequence equal to cell ID, in accordance with various embodiments.

Figure 11 illustrates a beam index pattern generated using a length 16 Gold code with initialization sequence equal to cell ID, in accordance with various embodiments.

Figure 12 illustrates use of an initialization sequence = cell ID + SFN*(2¹⁰), resulting in the SFN being shifted by 11 bits such that it does not overlap with the cell ID, in accordance with various embodiments.

Figure 13 illustrates a beam index pattern generated using a length 31 Gold code with initialization sequence = cell ID + SFN*(2¹⁰), in accordance with various embodiments.

Figure 14 illustrates use of an initialization sequence = cell ID*2¹⁰ + SFN, shifting the cell ID by 10 bits, in accordance with various embodiments.

Figure 15 illustrates a beam index pattern generated using a length 31 Gold code with initialization sequence = cell ID*2¹⁰ + SFN, in accordance with various embodiments.

Figure 16 illustrates a beam index pattern generated using a hashing function with f(n) = (A0*cell ID) mod D, in accordance with various embodiments.

Figure 17 illustrates a beam index pattern generated using a hashing function with f(n) = (A0*(cell ID + SFN)) mod D, in accordance with various embodiments.

Figure 18 illustrates interference diversity between different cells across SFNs, in accordance with various embodiments.

Figure 19 illustrates interference diversity between same cells across SFNs, in accordance with various embodiments.

Figure 20 illustrates minimum interference diversity for each cell across SFNs, in accordance with various embodiments.

Figure 21 illustrates simulation results for interference diversity between different cells across SFNs, in accordance with various embodiments. The plots correspond to: number of cells = 1000, SFN = 40, Q = {4, 8, 64}.

Figure 22 illustrates simulation results for minimum interference diversity for each cell across SFNs, in accordance with various embodiments. The plots correspond to: number of cells = 1000, SFN = 40, Q = {4, 8, 64}.

Figure 23 illustrates randomized selection of candidate positions for transmitting the SSB, in accordance with various embodiments.

Figure 24 illustrates a network in accordance with various embodiments.

Figure 25 schematically illustrates a wireless network in accordance with various embodiments.

Figure 26 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.

Figures 27 and 28 illustrate example procedures for practicing the various embodiments discussed herein.

DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Various embodiments herein provide techniques to randomize beamforming used to transmit the SSB, such that the interference footprint during the SSB transmission duration can be randomized. In various embodiments, the beam directions of an SSB are randomized across the candidate SSB positions. The sequence of directions may be pseudo-randomly chosen from a total number of beams used in a cell. The beam pattern may also be randomized for the same cell and/or for neighboring cells across the subframes. In these ways, the interference between cells will be potentially minimized if the beam directions of the SSB are randomized.

I. EXAMPLE EMBODIMENTS

In Rel-16 NR-U, which was targeting system operations in below 7 GHz, the total number of candidate SSBs for 15 kHz and 30 kHz subcarrier spacing are 10 and 20 respectively. The number of beams per cell, Q, are limited to 1, 2, 4 or 8 beams. In FR2, up to 64 beams will be supported. In Rel-16 NR-U, the physical beam index is derived using (candidate SSB index) mod Q. The receiver may assume that SSB with same physical beam index are sent using the same beam or equivalently assume the SSBs have QCL relationship. The beam index for a candidate SSB position repeats for all cells within a subframe and across all subframes as shown in Figure 1.

To randomize and diversify interference from the cells, the beam directions for an SSB should be randomized. The physical beam index for each cell in each subframe can be determined using /(candidate SSB index, SFN, cell ID) mod Q. where function f(n) is the randomization function. The randomization function, f(n), may take cell-ID, system frame number (SFN) or a modular operation of SFN such as mod(SFN, Q), and/or candidate SSB position as an input to output randomizing value. In one example, the beam index can be determined as (candidate SSB index, f (SFN, cell ID)) mod Q.

As a further extension, when determining the physical beam index, partial or full information of SFN and/or cell ID may be used. For instance, first X LSB of SFN or Y MSB of SFN may be used in the equation to determine physical beam index, where X and Y are predefined in the specification.

I.A. Embodiment A: Randomize beam index

In Rel-16 NR-U, a UE 2408 (see e.g., Figure 24) assumes that SSBs with the same SSB index value (candidate SSB index) mod Q are QCL’d. The physical beam indices are derived from the SSB candidate position, which are cyclic and contiguous as shown by Figure 2A. The UE cannot assign a beam index to a candidate position. The UE 2408 can select Q contiguous beams to transmit the SSB. For example, the UE may select candidate positions 3, 4, 5, and 6, as shown in Figure 2A.

In embodiment A, the beam indices are randomized for each cell, as shown by Figure 2B.

LA.1. Embodiment 1 with f(n) = SFN + cell ID

Beam index for the SSB is derived using the formula (i+SFN+cell ID) mod Q, where i is the SSB index, SFN is the system frame number of the transmission instance of the SSB, and cell ID is the cell identification number associated with the AN 2408 (see e.g., Figure 24) that is transmitting the SSB. Figure 3 shows beam index patterns generated using (i+SFN+cell ID mod Q). The addition of the SFN and cell ID helps in randomizing the beam patterns for the cells, as shown in Figure 3. The tabulated entries in Figure 3 are the beam index for a {cell ID, SFN, and candidate SSB position, i} tuple.

LA.2. Embodiment 2 with f(n) generated using m-sequence

An m-sequence is a pseudorandom binary sequence generated using linear feedback shift registers. The output is dependent on the initialization sequence provided. Initializing the m- sequence using a cell ID results in a randomized beam pattern. Figure 4 illustrates a linear feedback shift register of length 4. The polynomial corresponding to Figure 4 is x⁴ + x + 1, but different polynomials can be associated with the linear feedback shift register. By modifying the length of the m-sequence, the initialization sequence and the sequence generated by a generating polynomial will result in different outputs.

The binary output of the m-sequence generator is converted into integer values have taking a set of binary values within a window and summing the multiplication of each binary value with a power of 2 series. For example, the conversion from binary sequence, bk, is performed by Xk=o b_fe2^fe or Xfc=o b_k2^N~¹~^k . The window used to convert binary sequences to integer value needed for the randomization function, can be overlapping (as shown in Figure 5A) or nonoverlapping (as shown in Figure 6). The window is taken from the m-sequence binary sequence output values. For example, the initialization value can be obtained from binary representation of the cell ID, and SFN value can determine the order of the window used to obtain the randomization value. In the example of Figure 5 A, when SFN is 0, bit sequence 0 to 3 are taken as the window from the output of the m-sequence. When SFN is 1, bit sequences 1 to 4 are taken from the output as the window. When window size is M, bit sequence (n) to (n + M - 1) are taken as window for binary to integer value conversion, where n is the SFN value. In the example of Figure 6, when SFN is 0, bit sequence 0 to 3 are taken as the window from the output of the m-sequence. When SFN is 1, bit sequences 4 to 7 are taken from the output as the window. When window size is M, bit sequence (n x M) to ((n+1) x M - 1) are taken as window for binary to integer value conversion, where n is the SFN value.

In the examples of Figures 5A-B and 6-8, a long sequence of bits of length 4 * number of subframes is generated. There are two options of obtaining the beam index. Figures 5B and 7 show the beam pattern generated using an initialization sequence = cell ID with a shift register of length 4. Figure 8 shows the beam pattern generated using an initialization sequence = cell ID + SFN with a shift register of length 4.

LA.3. Embodiment 3 with f(n) generated using Gold sequence

Gold sequences are generated using two m-sequences of the same length. The output of the Gold sequence is utilized to compute randomization values. One example of the Gold sequence, c(n), is defined as follows: c(n) = (x_x(n + AQ + x₂(n + N_c)~) mod 2 x_x(n + 31) = (x_x(n + 3) + x_t (n + 1)) mod 2 x₂(n + 31) = (x₂(n + 3) + x₂(n + 2) + x₂(n + 1) + x₂(n)) mod 2, where Nc = 1600, and n is the index of the output Gold sequence. The first m-sequence, xi(n), is initialized with xi(0)=l, and xi(k)=0, for k=l,2,... ,30. The second m-sequence, X2(n), is initialized with initialization value, Cinit, where

(i) ■ 2¹. Alternatively, the initialization can be derived by x₂(i) = c_init/2^l mod 2, i = 0,1,2, ••• ,30.

There are two methods for generating a randomization value using the Gold code. A first method involves generating a very large sequence of length, for example n*number of subframe bits with initialization value as cell ID. A beam index is derived by dividing the long sequence into (non-overlapping) chunks of length n and each chunk of binary sequence being converted into integer value. This allows generation of sequence of randomizing value using the cell ID as initiation. Selection of the randomizing value is done depending on SFN from the sequence of randomizing value. For example, for SFN mod 16 = 0, the first randomizing value from the sequence is selected and for SFN mod 16 = 1, the second randomizing value from the sequence is selected and so forth. Figure 10 and 11 show beam patterns obtained using chunk size of 31 and 16 sequences, respectively.

A second method for generating a randomization value using a Gold code involves generating a length-n sequence using initialization value that is computed by a combination of cell ID and SFN. For each cell ID and SFN, the length n binary sequence can be converted into integer value and used as the randomizing value. One example of how initialization value can be configured is placing SFN, which can be represented by 10-bits, and cell ID, which can be represented by 10 bits, such that they do not overlap within the 31 bits of initialization bit sequence. Example illustrations of this are shown by Figures 12 and 14. Figures 13 and 15 show randomization values generated using the initialization examples illustrated in Figures 12 and 14, respectively. The initialization value can be also configured as a function of candidate SSB position, cell ID and SFN as initialization sequence = i*2²⁰ + SFN * 2¹⁰ + cell ID or initialization sequence = SFN*2¹⁸ + cell ID*2⁸ + i.

LA.4. Embodiment 4 with f(n) generated using Hashing Function

A hashing function may be used to randomize the physical beam index for each SSB according to: f_n ⁼ C^o- f_n-i)^m°d D where f₀ 0. A_o = 39827, D = 65537, where n corresponds the n-th iteration of the hashing function, fo corresponds to the initialization value of the hashing function. The initialization of the hashing function can be configured as cell ID and n-th iterated hashing function value is used as the randomization value. The determination of the iteration index, n, can be done depending on SFN. For example, SFN mod 16 = 0, may use the 1^st iterated hashing function value, SFN mod 16 = 1, may use the 2^nd iterated hashing function value, and so forth. Alternatively, the initialization value can be computed as a combination of cell ID and SFN, for example, fo = cell ID + SFN. The resultant hashing function, fi, can be used as the randomizing value.

Figures 16 and 17 show beam patterns obtained using the hash function with f₀ = cell ID and f₀ = cell ID + SFN, respectively, and with Q = 4.

I. A.5. Simulation Results:

For simulation of the embodiments discussed herein, three metrics have been defined to compare the effectiveness of the randomization approaches.

Interference Diversity between different cells across SFN is the sum of all uniquely observable pairs of beam indices between cells across all subframes. A larger sum value indicates that the randomization method is more effective and provides more combinations of unique beam indices for different cells across the subframes. For example, consider cell 1 and cell 2 in SFN {0, 1, 2}, with Q = 4 as shown in Figure 18. Figure 18 shows beam index for each cell corresponding to different candidate SSB position, i, for SFN 0, 1, and 2. The box that encapsules cell 1 and cell 2 for SFN 0 are the interfering beam index for cell 1 and 2. The pair of the beam index for each candidate SSB position is the same for candidate SSB position 0 and position 4. Therefore, there are only 4 unique pair of beam index at between SFN 0 for cell 1 and SFN 0 for cell 2. The same exercise can be performed for SFN 1 for cell 1 SFN 0 for cell 2, and again for SFN 0 for cell 1 and SFN 1 for cell 2. The randomization method used in the example provides 12 unique combinations of beam indices (1, 2), (2, 3), (3, 0), (0, 1) , (1, 3), (2, 0), (3, 1), (0, 2), (2, 1), (3,2), (0,3), (1, 0) out of 16 possible combinations between cell 1 and cell 2.

Interference Diversity between same cells across SFN is the number of repeated beam index for the same cell across all subframes. An efficient randomization method will result in fewer beam repetitions of the same beam index for the same cell across all SFN. As an example, consider cell 1 and cell 2 in SFN {0, 1, 2}, with Q = 4 as shown in Figure 19. Figure 19 shows beam index for each cell corresponding to different candidate SSB position, i, for SFN 0, 1, and 2. The dotted circle that encapsules values for cell 1 are the beam index for cell 1. For the same candidate SSB position, only the same beam index appears for cell 1. Therefore, there are only three repetitions of each beam index across SFN 0, 1, and 2. Cell 1 has the same beam indices repeating across all SFN for all the candidate positions. Cell 2 has unique beams in SFN 0.

Minimum Interference Diversity for each cell across SFN is the smallest number of unique beam index pairs for each cell across for each SFN for any given candidate SSB position. A higher count of unique beam pairs indicates a more efficient randomization method. For example, consider cell 1 and cell 2 in SFN {0, 1, 2}, with Q = 4 as shown in Figure 20. Figure 20 shows beam index for each cell corresponding to different candidate SSB position, i, for SFN 0, 1, and 2. The box that encapsules cell 1 and cell 2 for SFN 0 are the interfering beam index for cell 1 and 2. The metric counts the pair of the beam index for each candidate SSB position for each SFN value. Therefore, there are only 2 unique pair of beam index at between cell 1 and cell 2 for SFN 0, 1, and 2 for each candidate SSB position. Assume the beam index for cell 1 to be fixed as beam {0}, cell 2 can have beam indices {0, 1, 2, 3} as possible values. The randomization method used in Figure 20, generates only 2 unique beams pairs {0, 1}, { 0, 2} out of the 4 possible combinations.

Through simulations for Interference Diversity between 1000 cells across 40 SFN, we have observed the following:

1. Beam index patterns generated using the gold code sequence and the hashing function with initialization value = cell ID provided the most unique randomized beam patterns across different cells for different values of Q {4, 8, 64}, as shown in Figure 21.

2. Interference Diversity did not vary between same cells across SFN based on the randomization methods.

3. Beam index patterns generated using the gold code sequence and the hashing function with initialization value = cell ID also provided the most unique beam pairs for each cell across SFN for different values of Q {4, 8, 64}, as shown in Figure 22. In Figures 21 and 22, the solutions used are as follows:

Solution 1 - Beam index derived using (i+sfh+cellid) mod Q

Solution 2 - Beam index derived using length -4 m-seq with Cinit = cell id (overlapping window)

Solution 3 - Beam index derived using length -4 m-seq with Cinit = cell id (non-overlapping window)

Solution 4 - Beam index derived using length-4 m-seq with Cinit = cell id + SFN

Solution 5 - Beam index derived using length-31 gold-seq with Cinit = cell id (31 bits)

Solution 6 - Beam index derived using length-31 gold-seq with Cinit = cell id (16 bits)

Solution 7 - Beam index derived using length-31 gold-seq with Cinit = cell id + SFN*2^A11

Solution 8 - Beam index derived using length-31 gold-seq with cinit = cell id*2^A10 + SFN

Solution 9 - Beam index derived using hashing function Cinit = (AO * cell id) mod D Solution 10 - Beam index derived using hashing function Cinit = (AO * cell id + SFN) mod D

I.B. Embodiment B: Randomize the selection of candidate position

Candidate SSB positions for a specific beam index can be repeated multiple times within a DRS transmission window, which is the time window in which base state is expected to transmit the SSB for different beams and UE 2408 (see e.g., Figure 24) to expect reception of SSBs. In this embodiment, an AN 2408 (see e.g., Figure 24) may select non-contiguous set of SSBs corresponding to set of beam indices. An example illustration is shown by Figure 23. In Figure 23, the AN 2408 (see e.g., Figure 24) transmits 4 SSBs corresponding to beam index {0,1, 2, 3} and selects candidate positions {3, 8, 9, 18} to transmit the corresponding SSBs. If the AN 2408 chooses different candidate positions (randomly) in each DRS transmission window, the time instances that UE 2408 would receive SSB with a specific beam can be randomized over time for different cells creating interference diversity overtime. For this embodiment, the AN 2408 should be only allowed to select 1 SSB candidate among multiple SSB candidates for an SSB with a specific beam index.

I.C. Decoupling the SSB index and physical beam index

As an alternative embodiment to allow ANs 2408 to randomize the beams used by the SSB in each DRS transmission instance would be to decouple the SSB candidate position from the SSB beam index. In the previous embodiments, there was a specific mapping between SSB candidate position and SSB beam index. In embodiment A, the mapping between SSB candidate position and SSB beam index was changed in each DRS transmission. In embodiment B, the AN 2408 selected different SSB candidate position (among multiple candidate positions), where the mapping between SSB candidate position and SSB beam index was fixed.

In this embodiment, the SSB candidate position index and SSB beam index are indicated separately and the mapping between the two is decoupled. By allowing any SSB beam index to be associated with any SSB candidate position via signaling, different ANs 2408 belong to different cells can choose a random (or random-like) mapping between SSB candidate position and SSB beam index freely in each DRS transmission instance. This requires that SSB candidate position information (in order to allow the UE 2402 to determine the frame boundaries and understand where the detected SSB he with respect to the absolute radio frame timing) to be indicated in SSB and also SSB beam index to be indicated in SSB as well.

II. SYSTEMS AND IMPLEMENTATIONS

Figures 24-26 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 24 illustrates a network 2400 in accordance with various embodiments. The network 2400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 2400 includes a UE 2402, which is any mobile or non-mobile computing device designed to communicate with a RAN 2404 via an over-the-air connection. The UE 2402 is communicatively coupled with the RAN 2404 by a Uu interface, which may be applicable to both LTE and NR systems. Examples of the UE 2402 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in-vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, Internet of Things (loT) device, and/or the like. The network 2400 may include a plurality of UEs 2402 coupled directly with one another via a D2D, ProSe, PC5, and/or sidelink interface. These UEs 2402 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. The UE 2402 may be the same or similar as the UEs discussed previously with respect to any of the previously described figures.

In some embodiments, the UE 2402 may additionally communicate with an AP 2406 via an over-the-air (OTA) connection. The AP 2406 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 2404. The connection between the UE 2402 and the AP 2406 may be consistent with any IEEE 802.11 protocol. Additionally, the UE 2402, RAN 2404, and AP 2406 may utilize cellular-WLAN aggregation/integration (e.g., LWA/LWIP). Cellular- WLAN aggregation may involve the UE 2402 being configured by the RAN 2404 to utilize both cellular radio resources and WLAN resources.

The RAN 2404 includes one or more access network nodes (ANs) 2408. The ANs 2408 terminate air-interface(s) for the UE 2402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/L1 protocols. In this manner, the AN 2408 enables data/voice connectivity between CN 2420 and the UE 2402. The ANs 2408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells; or some combination thereof. In these implementations, an AN 2408 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc. The ANs 2408 may be the same or similar as the RAN nodes and/or ANs discussed previously.

One example implementation is a “CU/DU split” architecture where the ANs 2408 are embodied as a gNB-Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e.g., 3GPP TS 38.401 V16.1.0 (2020- 03)). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU/DU split may include an ng-eNB-CU and one or more ng-eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively. The ANs 2408 employed as the CU may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other type of architectures, arrangements, and/or configurations can be used.

The plurality of ANs may be coupled with one another via an X2 interface (if the RAN 2404 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 2410) or an Xn interface (if the RAN 2404 is aNG-RAN 2414). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs 2408 of the RAN 2404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 2402 with an air interface for network access. The UE 2402 may be simultaneously connected with a plurality of cells provided by the same or different ANs 2408 of the RAN 2404. For example, the UE 2402 and RAN 2404 may use carrier aggregation to allow the UE 2402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN 2408 may be a master node that provides an MCG and a second AN 2408 may be secondary node that provides an SCG. The first/second ANs 2408 may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 2404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 2402 or AN 2408 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 2404 may be an E-UTRAN 2410 with one or more eNBs 2412. The an E-UTRAN 2410 provides an LTE air interface (Uu) with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 2404 may be an next generation (NG)-RAN 2414 with one or more gNB 2416 and/or on or more ng-eNB 2418. The gNB 2416 connects with 5G-enabled UEs 2402 using a 5G NR interface. The gNB 2416 connects with a 5GC 2440 through an NG interface, which includes an N2 interface or an N3 interface. The ng-eNB 2418 also connects with the 5GC 2440 through an NG interface, but may connect with a UE 2402 via the Uu interface. The gNB 2416 and the ng-eNB 2418 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG- U) interface, which carries traffic data between the nodes of the NG-RAN 2414 and a UPF 2448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 2414 and an AMF 2444 (e.g., N2 interface).

The NG-RAN 2414 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

The 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 2402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 2402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 2402 with different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 2402 and in some cases at the gNB 2416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 2404 is communicatively coupled to CN 2420 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 2402). The components of the CN 2420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 2420 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 2420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 2420 may be referred to as a network sub-slice.

The CN 2420 may be an LTE CN 2422 (also referred to as an Evolved Packet Core (EPC) 2422). The EPC 2422 may include MME 2424, SGW 2426, SGSN 2428, HSS 2430, PGW 2432, and PCRF 2434 coupled with one another over interfaces (or “reference points”) as shown. The NFs in the EPC 2422 are briefly introduced as follows.

The MME 2424 implements mobility management functions to track a current location of the UE 2402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 2426 terminates an SI interface toward the RAN 2410 and routes data packets between the RAN 2410 and the EPC 2422. The SGW 2426 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.

The SGSN 2428 tracks a location of the UE 2402 and performs security functions and access control. The SGSN 2428 also performs inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 2424; MME 2424 selection for handovers; etc. The S3 reference point between the MME 2424 and the SGSN 2428 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 2430 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 2430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 2430 and the MME 2424 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the EPC 2420.

The PGW 2432 may terminate an SGi interface toward a data network (DN) 2436 that may include an application (app)Zcontent server 2438. The PGW 2432 routes data packets between the EPC 2422 and the data network 2436. The PGW 2432 is communicatively coupled with the SGW 2426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 2432 may further include anode for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point may communicatively couple the PGW 2432 with the same or different data network 2436. The PGW 2432 may be communicatively coupled with a PCRF 2434 via a Gx reference point.

The PCRF 2434 is the policy and charging control element of the EPC 2422. The PCRF 2434 is communicatively coupled to the app/content server 2438 to determine appropriate QoS and charging parameters for service flows. The PCRF 2432 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

The CN 2420 may be a 5GC 2440 including an AUSF 2442, AMF 2444, SMF 2446, UPF 2448, NSSF 2450, NEF 2452, NRF 2454, PCF 2456, UDM 2458, and AF 2460 coupled with one another over various interfaces as shown. The NFs in the 5GC 2440 are briefly introduced as follows.

The AUSF 2442 stores data for authentication of UE 2402 and handle authentication-related functionality. The AUSF 2442 may facilitate a common authentication framework for various access types..

The AMF 2444 allows other functions of the 5GC 2440 to communicate with the UE 2402 and the RAN 2404 and to subscribe to notifications about mobility events with respect to the UE 2402. The AMF 2444 is also responsible for registration management (e.g., for registering UE 2402), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization. The AMF 2444 provides transport for SM messages between the UE 2402 and the SMF 2446, and acts as a transparent proxy for routing SM messages. AMF 2444 also provides transport for SMS messages between UE 2402 and an SMSF. AMF 2444 interacts with the AUSF 2442 and the UE 2402 to perform various security anchor and context management functions. Furthermore, AMF 2444 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 2404 and the AMF 2444. The AMF 2444 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.

AMF 2444 also supports NAS signaling with the UE 2402 over an N3IWF interface. The N3IWF provides access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 2404 and the AMF 2444 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 2414 and the 2448 for the user plane. As such, the AMF 2444 handles N2 signalling from the SMF 2446 and the AMF 2444 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay UL and DL control-plane NAS signalling between the UE 2402 and AMF 2444 via an Nl reference point between the UE 2402and the AMF 2444, and relay uplink and downlink user-plane packets between the UE 2402 and UPF 2448. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 2402. The AMF 2444 may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs 2444 and an N17 reference point between the AMF 2444 and a 5G-EIR (not shown by Figure 24).

The SMF 2446 is responsible for SM (e.g., session establishment, tunnel management between UPF 2448 and AN 2408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 2448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 2444 over N2 to AN 2408; and determining SSC mode of a session. SM refers to management of a PDU session, and a PDU session or “session” refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 2402 and the DN 2436.

The UPF 2448 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 2436, and a branching point to support multihomed PDU session. The UPF 2448 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering. UPF 2448 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 2450 selects a set of network slice instances serving the UE 2402. The NSSF 2450 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 2450 also determines an AMF set to be used to serve the UE 2402, or a list of candidate AMFs 2444 based on a suitable configuration and possibly by querying the NRF 2454. The selection of a set of network slice instances for the UE 2402 may be triggered by the AMF 2444 with which the UE 2402 is registered by interacting with the NSSF 2450; this may lead to a change of AMF 2444. The NSSF 2450 interacts with the AMF 2444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).

The NEF 2452 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 2460, edge computing or fog computing systems (e.g., edge compute node 2436x, etc. In such embodiments, the NEF 2452 may authenticate, authorize, or throttle the AFs. NEF 2452 may also translate information exchanged with the AF 2460 and information exchanged with internal network functions. For example, the NEF 2452 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 2452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 2452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 2452 to other NFs and AFs, or used for other purposes such as analytics.

The NRF 2454 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 2454 also maintains information of available NF instances and their supported services. The NRF 2454 also supports service discovery functions, wherein the NRF 2454 receives NF Discovery Request from NF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.

The PCF 2456 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 2456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 2458. In addition to communicating with functions over reference points as shown, the PCF 2456 exhibit an Npcf service-based interface.

The UDM 2458 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 2402. For example, subscription data may be communicated via an N8 reference point between the UDM 2458 and the AMF 2444. The UDM 2458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 2458 and the PCF 2456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 2402) for the NEF 2452. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 2458, PCF 2456, and NEF 2452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 2458 may exhibit the Nudm service-based interface.

AF 2460 provides application influence on traffic routing, provide access to NEF 2452, and interact with the policy framework for policy control. The AF 2460 may influence UPF 2448 (re)selection and traffic routing. Based on operator deployment, when AF 2460 is considered to be a trusted entity, the network operator may permit AF 2460 to interact directly with relevant NFs. Additionally, the AF 2460 may be used for edge computing implementations,

The 5GC 2440 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 2402 is attached to the network. This may reduce latency and load on the network. In edge computing implementations, the 5GC 2440 may select a UPF 2448 close to the UE 2402 and execute traffic steering from the UPF 2448 to DN 2436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 2460, which allows the AF 2460 to influence UPF (re)selection and traffic routing. The data network (DN) 2436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)Zcontent server 2438. The DN 2436 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. In this embodiment, the server 2438 can be coupled to an IMS via an S-CSCF or the I-CSCF. In some implementations, the DN 2436 may represent one or more local area DNs (LADNs), which are DNs 2436 (or DN names (DNNs)) that is/are accessible by a UE 2402 in one or more specific areas. Outside of these specific areas, the UE 2402 is not able to access the LADN/DN 2436.

Additionally or alternatively, the DN 2436 may be an Edge DN 2436, which is a (local) Data Network that supports the architecture for enabling edge applications. In these embodiments, the app server 2438 may represent the physical hardware systems/devices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the app/content server 2438 provides an edge hosting environment that provides support required for Edge Application Server's execution.

In some embodiments, the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic. In these embodiments, the edge compute nodes may be included in, or co-located with one or more RAN2410, 2414. For example, the edge compute nodes can provide a connection between the RAN 2414 and UPF 2448 in the 5GC 2440. The edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 2414 and UPF 2448.

The interfaces of the 5GC 2440 include reference points and service-based itnterfaces. The reference points include: N1 (between the UE 2402 and the AMF 2444), N2 (between RAN 2414 and AMF 2444), N3 (between RAN 2414 and UPF 2448), N4 (between the SMF 2446 and UPF 2448), N5 (between PCF 2456 and AF 2460), N6 (between UPF 2448 and DN 2436), N7 (between SMF 2446 and PCF 2456), N8 (between UDM 2458 and AMF 2444), N9 (between two UPFs 2448), N10 (between the UDM 2458 and the SMF 2446), Ni l (between the AMF 2444 and the SMF 2446), N12 (between AUSF 2442 and AMF 2444), N13 (between AUSF 2442 and UDM 2458), N14 (between two AMFs 2444; not shown), N15 (between PCF 2456 and AMF 2444 in case of a non-roaming scenario, or between the PCF 2456 in a visited network and AMF 2444 in case of a roaming scenario), N16 (between two SMFs 2446; not shown), and N22 (between AMF 2444 and NSSF 2450). Other reference point representations not shown in Figure 24 can also be used. The service-based representation of Figure 24 represents NFs within the control plane that enable other authorized NFs to access their services. The service-based interfaces (SBIs) include: Namf (SBI exhibited by AMF 2444), Nsmf (SBI exhibited by SMF 2446), Nnef (SBI exhibited by NEF 2452), Npcf (SBI exhibited by PCF 2456), Nudm (SBI exhibited by the UDM 2458), Naf (SBI exhibited by AF 2460), Nnrf (SBI exhibited by NRF 2454), Nnssf (SBI exhibited by NSSF 2450), Nausf (SBI exhibited by AUSF 2442). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in Figure 24 can also be used. In some embodiments, the NEF 2452 can provide an interface to edge compute nodes 2436x, which can be used to process wireless connections with the RAN 2414.

As discussed previously, the system 2400 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 2402 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 2442 and UDM 2458 for a notification procedure that the UE 2402 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 2458 when UE 2402 is available for SMS).

The 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE's SUPI, SUCI or GPSI (see e.g., 3GPP TS 23.501 section 6.3). Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific. The SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path between various NF Services. The SCP, although not an NF instance, can also be deployed distributed, redundant, and scalable.

Figure 25 schematically illustrates a wireless network 2500 in accordance with various embodiments. The wireless network 2500 includes a UE 2502 in wireless communication with an AN 2504. The UE 2502 and AN 254 may be the same, similar to, and/or substantially interchangeable with, like-named components described elsewhere herein such as the UE 2402 and RAN 2404 of Figure 24.

The UE 2502 may be communicatively coupled with the AN 2504 via connection 2506. The connection 2506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 2502 may include a host platform 2508 coupled with a modem platform 2510. The host platform 2508 may include application processing circuitry 2512, which may be coupled with protocol processing circuitry 2514 of the modem platform 2510. The application processing circuitry 2512 may run various applications for the UE 2502 that source/sink application data. The application processing circuitry 2512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 2514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 2506. The layer operations implemented by the protocol processing circuitry 2514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 2510 may further include digital baseband circuitry 2516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 2514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 2510 may further include transmit circuitry 2518, receive circuitry 2520, RF circuitry 2522, and RF front end (RFFE) 2524, which may include or connect to one or more antenna panels 2526. Briefly, the transmit circuitry 2518 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 2520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 2522 may include a low-noise amplifier, a power amplifier, power tracking components, etc. ; RFFE 2524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 2518, receive circuitry 2520, RF circuitry 2522, RFFE 2524, and antenna panels 2526 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 2514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 2526, RFFE 2524, RF circuitry 2522, receive circuitry 2520, digital baseband circuitry 2516, and protocol processing circuitry 2514. In some embodiments, the antenna panels 2526 may receive a transmission from the AN 2504 by receive-beamforming signals received by a plurality of antennas/ antenna elements of the one or more antenna panels 2526.

A UE transmission may be established by and via the protocol processing circuitry 2514, digital baseband circuitry 2516, transmit circuitry 2518, RF circuitry 2522, RFFE 2524, and antenna panels 2526. In some embodiments, the transmit components of the UE 2504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 2526.

Similar to the UE 2502, the AN 2504 may include a host platform 2528 coupled with a modem platform 2530. The host platform 2528 may include application processing circuitry 2532 coupled with protocol processing circuitry 2534 of the modem platform 2530. The modem platform may further include digital baseband circuitry 2536, transmit circuitry 2538, receive circuitry 2540, RF circuitry 2542, RFFE circuitry 2544, and antenna panels 2546. The components of the AN 2504 may be similar to and substantially interchangeable with like-named components of the UE 2502. In addition to performing data transmission/reception as described above, the components of the AN 2508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 26 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, Figure 26 shows a diagrammatic representation of hardware resources 2600 including one or more processors (or processor cores) 2610, one or more memory /storage devices 2620, and one or more communication resources 2630, each of which may be communicatively coupled via a bus 2640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 2602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 2600.

The processors 2610 include, for example, processor 2612 and processor 2614. The processors 2610 include circuitry such as, but not limited to one or more processor cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors 2610 may be, for example, a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acom RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more Digital Signal Processors (DSPs) such as a baseband processor, Application-Specific Integrated Circuits (ASICs), an Field-Programmable Gate Array (FPGA), a radio-frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof. In some implementations, the processor circuitry 2610 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGA, complex programmable logic devices (CPLDs), etc.), or the like.

The memory /storage devices 2620 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 2620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, phase change RAM (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may incorporate three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®. The memory /storage devices 2620 may also comprise persistent storage devices, which may be temporal and/or persistent storage of any type, including, but not limited to, non-volatile memory, optical, magnetic, and/or solid state mass storage, and so forth.

The communication resources 2630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 2604 or one or more databases 2606 or other network elements via a network 2608. For example, the communication resources 2630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 2650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 2610 to perform any one or more of the methodologies discussed herein. The instructions 2650 may reside, completely or partially, within at least one of the processors 2610 (e.g., within the processor’s cache memory), the memory /storage devices 2620, or any suitable combination thereof. Furthermore, any portion of the instructions 2650 may be transferred to the hardware resources 2600 from any combination of the peripheral devices 2604 or the databases 2606. Accordingly, the memory of processors 2610, the memory /storage devices 2620, the peripheral devices 2604, and the databases 2606 are examples of computer-readable and machine-readable media.

III. EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 24-26, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. For example, Figure 27 illustrates a process 2700 in accordance with various embodiments. In some embodiments, the process 2700 may be performed by a gNB or a portion thereof.

At 2702, the process 2700 may include determining a physical beam index for a synchronization signal block (SSB) based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID), or a generated sequence. At 2704, the process 2700 may include encoding the SSB for transmission based on the determined physical beam index.

Figure 28 illustrates another process 2800 in accordance with various embodiments. The process 2800 may be performed by a UE or a portion thereof. At 2802, the process 2800 may include determining a physical beam index for a synchronization signal block (SSB) based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID), or a generated sequence. At 2804, the process 2800 may include encoding the SSB for transmission based on the determined physical beam index.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

IV. EXAMPLES

Additional examples of the presently described embodiments include the following, nonlimiting implementations. Each of the following non-limiting examples may stand on its own or may be combined in any permutation or combination with any one or more of the other examples provided below or throughout the present disclosure.

Note for gNB the examples may correspond to transmission of the SSB, and for UE the examples may correspond to reception of the SSB.

Example A01 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i+SFN+cell ID) mod Q, where i is the SSB index, SFN is the system frame number of the transmission instance of the SSB, and cell ID is the cell identification number associated with the base station that is transmitting the SSB.

Example A02 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a length-4 maximum length sequence with initialization value = cell ID. The initialization value can be obtained from binary representation of the cell ID, and SFN value can determine the order of the window (overlapping or non-overlapping) used to obtain the randomization value. Example A02 may be combined with example A01 and/or some other example(s) herein.

Example A03 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a length-4 maximum length sequence with initialization value = cell ID + SFN. The initialization value can be obtained from binary representation of the cell ID, and SFN value can determine the order of the window (overlapping or non-overlapping) used to obtain the randomization value. Example A03 may be combined with examples A01-A02 and/or some other example(s) herein.

Example A04 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a length- 16 and length-31 gold code sequence. Beam index is derived by dividing the long sequence into (non-overlapping) chunks of length n and each chunk of binary sequence being converted into integer value using the cell ID as initialization value. Example A04 may be combined with examples A01-A03 and/or some other example(s) herein.

Example A05 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a length-31 gold code sequence with initialization value = cell ID + SFN *(210) such that the SFN is shifted by 11 bits. Initialization value is configured by placing SFN, which can be represented by 10-bits, and cell ID, which can be represented by 10 bits, such that they do not overlap within the 31 bits of initialization bit sequence. Example A05 may be combined with examples A01-A04 and/or some other example(s) herein.

Example A06 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a length-31 gold code sequence with initialization value = cell ID* 210 + SFN, such that the cell ID is shifted by 10 bits. Initialization value is configured by placing SFN, which can be represented by 10-bits, and cell ID, which can be represented by 10 bits, such that they do not overlap within the 31 bits of initialization bit sequence. Example A06 may be combined with examples A01-A05 and/or some other example(s) herein.

Example A07 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a hashing function f_n = ( ₀. f_n-1)mod D where n corresponds the n-th iteration of the hashing function, fO corresponds to the initialization value of the hashing function. The initialization of the hashing function can be configured as cell ID and n-th iterated hashing function value is used as the randomization value. Example A07 may be combined with examples A01-A06 and/or some other example(s) herein.

Example A08 includes a method of randomizing the physical beam index for each SSB, that defines the beam index is derived using the formula (i + f(n)) mod Q, where i is the SSB index, and f(n) is generated using a hashing function f_n = ( ₀. f_n-1)mod D where n corresponds the n-th iteration of the hashing function, fO corresponds to the initialization value of the hashing function. The initialization of the hashing function can be configured as cell ID + SFN and n-th iterated hashing function value is used as the randomization value. Example A08 may be combined with examples A01-A07 and/or some other example(s) herein.

Example A09 includes a method of randomizing the physical beam index for each SSB, where the base station (BS) may select non-contiguous set of SSBs corresponding to set of beam indices. Example A09 may be combined with examples A01-A08 and/or some other example(s) herein.

Example A10 includes a method of randomizing the physical beam index for each SSB, where BS randomizes the beams used by the SSB in each DRS transmission instance by decoupling the SSB candidate position from the SSB beam index and indicating both indices separately. Example A10 may be combined with examples A01-A09 and/or some other example(s) herein.

Example B01 includes a method of randomizing a physical beam index for a synchronization signal block (SSB), the method comprising: determining the beam index for the SSB based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID), and/or a generated sequence.

Example B02 includes the method of example B01 and/or some other example(s) herein, further comprising: determining the beam index using (i+SFN+cell ID) mod Q, wherein i is an SSB index of the SSB, SFN is the SFN of a transmission instance of the SSB, and cell ID is a cell identity associated with a transmitter (Tx) transmitting the SSB.

Example B03 includes the method of example B01 and/or some other example(s) herein, further comprising: determining the beam index using (i + f(n)) mod Q, wherein i is the SSB index, and f(n) is a generated sequence Example B04 includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a length-4 maximum length sequence with initialization value based on the cell ID.

Example B05 includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a length-4 maximum length sequence with an initialization value based on the cell ID plus a system frame number.

Example B06 includes the method of examples B04-B05 and/or some other example(s) herein, further comprising: determining the initialization value from a binary representation of the cell ID; and determining an order of an overlapping or non-overlapping window using the SFN, the window being used to obtain the randomization value.

Example B07 includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a length-16 and/or length-31 gold code sequence.

Example B08 includes the method of example B07 and/or some other example(s) herein, further comprising: determining the beam index by dividing a long sequence into non-overlapping chunks of length n; and converting each chunk of binary sequence into an integer value using the cell ID as an initialization value.

Example B09 includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a length-31 gold code sequence with an initialization value based on the cell ID plus SFN *(2¹⁰) such that the SFN is shifted by 11 bits.

Example BIO includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a length-31 gold code sequence with initialization value based on the cell ID* 2¹⁰ plus the SFN such that the cell ID is shifted by 10 bits.

Example Bl l includes the method of examples B09-B10 and/or some other example(s) herein, further comprising: determining the initialization value by arranging the SFN represented by 10-bits and the cell ID represented by 10 bits such that they do not overlap within the 31 bits of initialization bit sequence.

Example B12 includes the method of example B03 and/or some other example(s) herein, further comprising: generating the sequence f(n) using a hash function f_n = ( ₀. f_n-1)mod D where n is an n-th iteration of the hash function, and fO is an initialization value of the hash function.

Example Bl 3 includes the method of example B12 and/or some other example(s) herein, further comprising: determining an initialization value of the hash function based on the cell ID, and the n-th iterated hash function value is used as a randomization value.

Example B14 includes the method of example B12 and/or some other example(s) herein, further comprising: determining an initialization value of the hash function based on the cell ID plus the SFN, and n-th iterated hash function value is used as a randomization value.

Example Bl 5 includes the method of examples B12-B14 and/or some other example(s) herein, wherein A_o = 39827 and D = 65537

Example B16 includes the method of examples B01-B15 and/or some other example(s) herein, further comprising: selecting a non-contiguous set of SSBs corresponding to set of beam indices.

Example Bl 7 includes the method of examples BO 1 -Bl 6 and/or some other example(s) herein, further comprising: randomizing beams used by the SSB in each Discovery Reference Signal (DRS) transmission instance by decoupling the SSB candidate position from the SSB beam index; and indicating both indices separately.

Example Bl 8 includes the method of examples BO 1 -Bl 7 and/or some other example(s) herein, wherein the method is performed by a next generation node B (gNB) or a user equipment (UE).

Example Cl includes one or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB) cause the gNB to: determine a physical beam index for a synchronization signal block (SSB) based on a randomization function to randomize the physical beam index; and encode the SSB for transmission based on the determined physical beam index.

Example C2 includes the one or more NTCRM of example Cl, wherein the physical beam index is determined based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID) associated with the transmission of the SSB, or a generated sequence.

Example C3 includes the one or more NTCRM of example C2, wherein the physical beam index is determined based on the generated sequence, and wherein the instructions, when executed, are further to cause the gNB to generate the sequence using a Gold code sequence or a hashing function.

Example C4 includes the one or more NTCRM of example C3, wherein the generated sequence is initialized based on the cell ID.

Example C5 includes the one or more NTCRM of example C4, wherein the generated sequence is initialized further based on the SFN.

Example C6 includes the one or more NTCRM of example C3, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

Example C7 includes the one or more NTCRM of example C3, wherein the generated sequence has a maximum length of 4 bits.

Example C8 includes the one or more NTCRM of example C3, wherein the physical beam index is determined using (i + f(n)) mod Q, wherein i is the SSB index, and f(n) is the generated sequence.

Example C9 includes the one or more NTCRM of any one of examples Cl to C8, wherein the sequence is a first sequence of a plurality of sequences used to determine respective physical beam indexes, and wherein, to determine the respective physical beam indexes, the gNB is to: obtain a base sequence; generate the plurality of sequences as respective overlapping or non-overlapping subsets of the base sequence; and generate the plurality of physical beam indexes based on the respective generated sequences and an initialization value.

Example CIO includes the one or more NTCRM of example Cl, wherein the physical beam index is determined using (i+SFN+cell ID) mod Q, wherein i is the SSB index of the SSB, SFN is the SFN of a transmission instance of the SSB, and cell ID is a cell identity associated with the transmission of the SSB.

Example Cl l includes one or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE) cause the UE to: determine a physical beam index for a synchronization signal block (SSB) based on a randomization function to randomize the physical beam index; and receive the SSB based on the determined physical beam index.

Example C12 includes the one or more NTCRM of example Cl l, wherein the physical beam index is determined based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID) associated with the transmission of the SSB, or a generated sequence.

Example C 13 includes the one or more NTCRM of example C 12, wherein the physical beam index is determined based on the generated sequence, and wherein the instructions, when executed, are further to cause the UE to generate the sequence using a Gold code sequence or a hashing function.

Example C14 includes the one or more NTCRM of example Cl 3, wherein the generated sequence is initialized based on the cell ID.

Example C15 includes the one or more NTCRM of example C14, wherein the generated sequence is initialized further based on the SFN.

Example C16 includes the one or more NTCRM of example Cl 3, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

Example Cl 7 includes the one or more NTCRM of example Cl 3, wherein the generated sequence has a maximum length of 4 bits.

Example C 18 includes the one or more NTCRM of example C 13, wherein the physical beam index is determined using (i + f(n)) mod Q, wherein i is the SSB index, and f(n) is the generated sequence.

Example Cl 9 includes the one or more NTCRM of any one of examples Cl l to Cl 8, wherein the sequence is a first sequence of a plurality of sequences used to determine respective physical beam indexes, and wherein, to determine the respective physical beam indexes, the UE is to: obtain a base sequence; generate the plurality of sequences as respective overlapping or nonoverlapping subsets of the base sequence; and generate the plurality of physical beam indexes based on the respective generated sequences and an initialization value.

Example C20 includes the one or more NTCRM of example Cl 1, wherein the physical beam index is determined using (i+SFN+cell ID) mod Q, wherein i is the SSB index of the SSB, SFN is the SFN of a transmission instance of the SSB, and cell ID is a cell identity associated with the transmission of the SSB.

Example C21 includes an apparatus to be implemented in a next generation Node B (gNB), the apparatus comprising: a radio frequency (RF) interface; and processor circuitry coupled to the RF interface. The processor circuitry is to: generate a sequence based on a Gold code sequence or a hashing function and an initialization value; determine a physical beam index for a synchronization signal block (SSB) based on the generated sequence; and encode the SSB for transmission via the RF interface based on the determined physical beam index.

Example C22 includes the apparatus of example C21, wherein the initialization value is based on a cell identity (ID) associated with the transmission of the SSB.

Example C23 includes the apparatus of example C21, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

Example C24 includes the apparatus of any of examples C21-C23, wherein the generated sequence has a length of 4 bits or less.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples A01-A10, B01-B18, C1-C24, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples A01-A10, BO 1 -Bl 8, Cl-C24,or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples A01-A10, B01-B18, Cl-C24,or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples A01-A10, B01-B18, Cl-C24,or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A10, B01-B18, Cl-C24,or portions thereof.

Example Z06 may include a signal as described in or related to any of examples A01-A10, BO 1 -Bl 8, Cl-C24,or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A10, BO 1 -Bl 8, Cl-C24,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples A01-A10, B01-B18, Cl-C24,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A10, B01- B18, Cl-C24,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A10, B01-B18, Cl-C24,or portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples A01-A10, BO 1 -Bl 8, C1-C24, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

V. ABBREVIATIONS Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 V16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

3GPP Third Generation 35 ASN.1 Abstract Syntax CAPEX CAPital Partnership Notation One 70 Expenditure Project AUSF Authentication CBRA Contention Based

4G Fourth Generation Server Function Random Access 5G Fifth Generation AWGN Additive CC Component 5GC 5G Core network 40 White Gaussian Carrier, Country ACK Noise 75 Code, Cryptographic

Acknowledgemen BAP Backhaul Checksum t Adaptation Protocol CCA Clear Channel AF Application BCH Broadcast Assessment Function 45 Channel CCE Control Channel

AM Acknowledged BER Bit Error Ratio 80 Element Mode BFD Beam Failure CCCH Common Control

AMBRAggregate Detection Channel Maximum Bit Rate BLER Block Error Rate CE Coverage AMF Access and 50 BPSK Binary Phase Shift Enhancement Mobility Keying 85 CDM Content Delivery

Management BRAS Broadband Network Function Remote Access CDMA Code- AN Access Network Server Division Multiple ANR Automatic 55 BSS Business Support Access Neighbour Relation System 90 CFRA Contention Free

/VP Application BS Base Station Random Access Protocol, Antenna BSR Buffer Status CG Cell Group

Port, Access Point Report CI Cell Identity API Application 60 BW Bandwidth CID Cell-ID (e g., Programming Interface BWP Bandwidth Part 95 positioning method) /VPN Access Point C-RNTI Cell Radio CIM Common Name Network Temporary Information Model ARP Allocation and Identity CIR Carrier to Retention Priority 65 CA Carrier Interference Ratio ARQ Automatic Repeat Aggregation, 100 CK Cipher Key Request Certification CM Connection AS Access Stratum Authority Management, Conditional 35 Cloud RAN CSS Common Search

Mandatory CRB Common 70 Space, Cell- specific

CMAS Commercial Resource Block Search Space

Mobile Alert Service CRC Cyclic CTS Clear-to-Send

CMD Command Redundancy Check CW Codeword

CMS Cloud 40 CRI Channel-State CWS Contention

Management System Information Resource 75 Window Size

CO Conditional Indicator, CSI-RS D2D Device-to-Device

Optional Resource DC Dual

CoMP Coordinated Indicator Connectivity, Direct

Multi-Point 45 C-RNTI Cell RNTI Current

CORESET Control CS Circuit Switched 80 DCI Downlink Control

Resource Set CSAR Cloud Service Information

COTS Commercial Off- Archive DF Deployment

The-Shelf CSI Channel-State Flavour

CP Control Plane, 50 Information DL Downlink Cyclic Prefix, CSI-IM CSI 85 DMTF Distributed

Connection Point Interference Management Task Force

CPD Connection Point Measurement DPDK Data Plane Descriptor CSI-RS CSI Development Kit

CPE Customer Premise 55 Reference Signal DM-RS, DMRS Equipment CSI-RSRP CSI 90 Demodulation

CPICH Common Pilot reference signal Reference Signal

Channel received power DN Data network

CQI Channel Quality CSI-RSRQ CSI DRB Data Radio Bearer Indicator 60 reference signal DRS Discovery

CPU CSI processing received quality 95 Reference Signal unit, Central Processing CSI-SINR CSI signal- DRX Discontinuous Unit to-noise and Reception

C/R interference ratio DSL Domain Specific

Command/Respon 65 CSMA Carrier Sense Language. Digital se field bit Multiple Access 100 Subscriber Line

CRAN Cloud Radio CSMA/CA CSMA DSLAM DSL

Access Network, with collision avoidance Access Multiplexer DwPTS Downlink 35 eNB evolved NodeB, F1AP Fl Application

Pilot Time Slot E-UTRAN Node B 70 Protocol

E-LAN Ethernet EN-DC E-UTRA- Fl-C Fl Control plane

Local Area Network NR Dual interface

E2E End-to-End Connectivity Fl-U Fl User plane

ECCA extended clear 40 EPC Evolved Packet interface channel Core 75 FACCH Fast assessment, EPDCCH enhanced Associated Control extended CCA PDCCH, enhanced CHannel

ECCE Enhanced Control Physical FACCH/F Fast

Channel Element,

Downlink Control Associated Control

Enhanced CCE Cannel 80 Channel/Full rate

ED Energy Detection EPRE Energy per FACCH/H Fast

EDGE Enhanced resource element Associated Control

Datarates for GSM EPS Evolved Packet Channel/Half rate

Evolution (GSM 50 System FACH Forward Access

Evolution) EREG enhanced REG, 85 Channel

EGMF Exposure enhanced resource FAUSCH Fast

Governance element groups Uplink Signalling

Management ETSI European Channel

Function 55 Telecommuni catio FB Functional Block

EGPRS Enhanced ns Standards Institute 90 FBI Feedback

GPRS ETWS Earthquake and Information

EIR Equipment Tsunami Warning FCC Federal

Identity Register System Communications eLAA enhanced

eUICC embedded UICC, Commission

Licensed Assisted embedded Universal 95 FCCH Frequency

Access, enhanced Integrated Circuit Correction CHannel

LAA Card FDD Frequency

EM Element Manager E-UTRA Evolved Division Duplex eMBB Enhanced Mobile 65 UTRA FDM Frequency

Broadband E-UTRAN Evolved 100 Division Multiplex

EMS Element UTRAN FDM A Frequency

Management System EV2X Enhanced V2X Division Multiple Access 35 gNB Next Generation Repeat Request

FE Front End NodeB 70 HANDO Handover

FEC Forward Error gNB-CU gNB- HFN HyperFrame Correction centralized unit, Next Number

FFS For Further Study Generation NodeB HHO Hard Handover FFT Fast Fourier 40 centralized unit HLR Home Location

Transformation gNB-DU gNB- 75 Register feLAA further enhanced distributed unit, Next HN Home Network Licensed Assisted Generation NodeB HO Handover Access, further distributed unit HPLMN Home enhanced LAA 45 GNSS Global Navigation Public Land Mobile FN Frame Number Satellite System 80 Network FPGA Field- GPRS General Packet HSDPA High Programmable Gate Radio Service Speed Downlink

Array GSM Global System for Packet Access

FR Frequency Range 50 Mobile HSN Hopping G-RNTI GERAN Communications, 85 Sequence Number Radio Network Groupe Special HSPA High Speed

Temporary Mobile Packet Access Identity GTP GPRS Tunneling HSS Home Subscriber GERAN 55 Protocol Server

GSM EDGE GTP-UGPRS Tunnelling 90 HSUPA High RAN, GSM EDGE Protocol for User Speed Uplink Packet

Radio Access Plane Access Network GTS Go To Sleep HTTP Hyper Text

GGSN Gateway GPRS 60 Signal (related to Transfer Protocol Support Node WUS) 95 HTTPS Hyper GLONASS GUMMEI Globally Text Transfer Protocol

GLObal'naya Unique MME Identifier Secure (https is

NAvigatsionnaya GUTI Globally Unique http/1.1 over SSL,

Sputnikovaya 65 Temporary UE i.e. port 443)

Sistema (Engl.: Identity 100 I-Block Global Navigation HARQ Hybrid ARQ, Information Block

Satellite System) Hybrid Automatic ICCID Integrated Circuit Card Identification 35 mobile group identity Standardisation

I AB Integrated Access IMPI IP Multimedia 70 ISP Internet Service and Backhaul Private Identity Provider

ICIC Inter-Cell IMPU IP Multimedia IWF Interworking-

Interference PUblic identity Function

Coordination 40 IMS IP Multimedia I-WLAN

ID Identity, identifier Subsystem 75 Interworking

IDFT Inverse Discrete IMSI International WLAN

Fourier Transform Mobile Subscriber Constraint length

IE Information Identity of the convolutional element 45 loT Internet of Things code, USIM Individual

IBE In-Band Emission IP Internet Protocol 80 key

Ipsec IP Security, kB Kilobyte (1000

IEEE Institute of Internet Protocol bytes)

Electrical and Electronics Security kbps kilo-bits per

Engineers 50 IP-CAN IP- second

IEI Information Connectivity Access 85 Kc Ciphering key

Element Identifier Network Ki Individual

IEIDL Information IP-M IP Multicast subscriber

Element Identifier IPv4 Internet Protocol authentication key

Data Length 55 Version 4 KPI Key Performance

IETF Internet IPv6 Internet Protocol 90 Indicator

Engineering Task Version 6 KQI Key Quality

Force IR Infrared Indicator

IF Infrastructure IS In Sync KSI Key Set Identifier

IM Interference 60 IRP Integration ksps kilo-symbols per

Measurement, Reference Point 95 second

Intermodulation, ISDN Integrated KVM Kernel Virtual

IP Multimedia Services Digital Machine

IMC IMS Credentials Network LI Layer 1 (physical

IMEI International 65 ISIM IM Services layer)

Mobile Equipment Identity Module 100 Ll-RSRP Layer 1

Identity ISO International reference signal

IMGI International Organisation for received power L2 Layer 2 (data link 35 Evolution Channel Occupancy layer) M2M Machine-to- 70 Time

L3 Layer 3 (network Machine MCS Modulation and layer) MAC Medium Access coding scheme

LAA Licensed Assisted Control (protocol MDAF Management Data

Access 40 layering context) Analytics Function

LAN Local Area MAC Message 75 MDAS Management Data

Network authentication code Analytics Service

LBT Listen Before (security/encry ption MDT Minimization of

Talk context) Drive Tests

LCM LifeCycle 45 MAC -A MAC used ME Mobile Equipment

Management for authentication and 80 MeNB master eNB

LCR Low Chip Rate key agreement (TSG T MER Message Error

LCS Location Services WG3 context) Ratio

LCID Logical MAC -IMAC used for MGL Measurement Gap

Channel ID 50 data integrity of Length

LI Layer Indicator signalling messages (TSG 85 MGRP Measurement Gap

LLC Logical Link T WG3 context) Repetition Period Control, Low Layer MANO MIB Master Compatibility Management and Information Block,

LPLMN Local 55 Orchestration Management

PLMN MBMS 90 Information Base

LPP LTE Positioning Multimedia MIMO Multiple Input Protocol Broadcast and Multicast Multiple Output

LSB Least Significant Service MLC Mobile Location

Bit 60 MBSFN Centre

LTE Long Term Multimedia 95 MM Mobility

Evolution Broadcast multicast Management

LWA LTE-WLAN service Single Frequency MME Mobility aggregation Network Management Entity

LWIP LTE/WLAN 65 MCC Mobile Country MN Master Node

Radio Level Integration Code 100 MnS Management with IPsec Tunnel MCG Master Cell Group Service

LTE Long Term MCOT Maximum MO Measurement Object, Mobile 35 Subscriber ISDN NF Network Function

Originated Number 70 NFP Network

MPBCH MTC MT Mobile Forwarding Path

Physical Broadcast Terminated, Mobile NFPD Network

CHannel Termination Forwarding Path

MPDCCH MTC 40 MTC Machine-Type Descriptor

Physical Downlink Communications 75 NFV Network

Control CHannel mMTCmassive MTC, Functions

MPDSCH MTC massive Machine- Virtualization

Physical Downlink Type Communications NFVI NFV

Shared CHannel 45 MU-MIMO Multi User Infrastructure

MPRACH MTC MIMO 80 NFVO NFV Orchestrator

Physical Random MWUS MTC NG Next Generation,

Access CHannel wake-up signal, MTC Next Gen

MPUSCH MTC wus NGEN-DC NG-RAN

Physical Uplink Shared 50 NACKNegative E-UTRA-NR Dual

Channel Acknowledgement 85 Connectivity

MPLS MultiProtocol NAI Network Access NM Network Manager

Label Switching Identifier NMS Network

MS Mobile Station NAS Non-Access Management System

MSB Most Significant 55 Stratum, Non- Access N-PoP Network Point of

Bit Stratum layer 90 Presence

MSC Mobile Switching NCT Network NMIB, N-MIB

Centre Connectivity Topology Narrowband MIB

MSI Minimum System NC-JT NonNPBCH

Information, 60 coherent Joint Narrowband

MCH Scheduling Transmission 95 Physical Broadcast

Information NEC Network CHannel

MSID Mobile Station Capability Exposure NPDCCH

Identifier NE-DC NR-E- Narrowband

MSIN Mobile Station 65 UTRA Dual Physical Downlink

Identification Connectivity 100 Control CHannel

Number NEF Network Exposure NPDSCH

MSISDN Mobile Function Narrowband Physical Downlink

S-NNSAI Single- Broadcast Channel Shared CHannel NSSAI 70 PC Power Control, NPRACH NSSF Network Slice Personal Computer

Narrowband Selection Function PCC Primary

Physical Random NW Network Component Carrier, Access CHannel

NWUSNarrowband Primary CC NPUSCH wake-up signal, 75 PCell Primary Cell

Narrowband Narrowband WUS PCI Physical Cell ID,

Physical Uplink NZP Non-Zero Power Physical Cell Shared CHannel O&M Operation and Identity NPSS Narrowband

Maintenance PCEF Policy and Primary ODU2 Optical channel 80 Charging

Synchronization Data Unit - type 2 Enforcement Signal OFDM Orthogonal Function

NSSS Narrowband Frequency Division PCF Policy Control Secondary 50 Multiplexing Function

Synchronization OFDMA 85 PCRF Policy Control Signal Orthogonal and Charging Rules NR New Radio, Frequency Division Function Neighbour Relation Multiple Access PDCP Packet Data

NRF NF Repository 55 OOB Out-of-band Convergence Protocol, Function OOS Out of Sync 90 Packet Data

NRS Narrowband OPEX OPerating Convergence

Reference Signal EXpense Protocol layer NS Network Service OSI Other System PDCCH Physical

NSA Non-Standalone 60 Information Downlink Control operation mode OSS Operations 95 Channel NSD Network Service Support System PDCP Packet Data Descriptor OTA over-the-air Convergence Protocol

NSR Network Service PAPR Peak-to-Average PDN Packet Data Record

Power Ratio Network, Public

NSSAINetwork Slice PAR Peak to Average 100 Data Network Selection Assistance Ratio PDSCH Physical Information PBCH Physical Downlink Shared Channel 35 block PTT Push-to-Talk

PDU Protocol Data PRG Physical resource 70 PUCCH Physical Unit block group Uplink Control PEI Permanent ProSe Proximity Channel Equipment Identifiers Services, Proximity- PUSCH Physical PFD Packet Flow 40 Based Service Uplink Shared Description PRS Positioning 75 Channel P-GW PDN Gateway Reference Signal QAM Quadrature PHICH Physical PRR Packet Reception Amplitude hybrid-ARQ indicator Radio Modulation channel 45 PS Packet Services QCI QoS class of

PHY Physical layer PSBCH Physical 80 identifier PLMN Public Land Sidelink Broadcast QCL Quasi co-location Mobile Network Channel QFI QoS Flow ID, PIN Personal PSDCH Physical QoS Flow Identifier

Identification Number 50 Sidelink Downlink QoS Quality of Service PM Performance Channel 85 QPSK Quadrature Measurement PSCCH Physical (Quaternary) Phase Shift PMI Precoding Matrix Sidelink Control Keying Indicator Channel QZSS Quasi-Zenith

PNF Physical Network 55 PSFCH Physical Satellite System Function Sidelink Feedback 90 RA-RNTI Random

PNFD Physical Network Channel Access RNTI

Function Descriptor PSSCH Physical RAB Radio Access

PNFR Physical Network Sidelink Shared Bearer, Random

Function Record 60 Channel Access Burst

POC PTT over Cellular PSCell Primary SCell 95 RACH Random Access

PP, PTP Point-to- PSS Primary Channel

Point Synchronization RADIUS Remote

PPP Point-to-Point Signal Authentication Dial In

Protocol 65 PSTN Public Switched User Service

PRACH Physical Telephone Network too RAN Radio Access

RACH PT-RS Phase-tracking Network

PRB Physical resource reference signal RAND RANDom number (used for 35 RM Registration Protocol authentication) Management 70 RTS Ready-To-Send

RAR Random Access RMC Reference RTT Round Trip Time

Response Measurement Channel Rx Reception,

RAT Radio Access RMSI Remaining MSI, Receiving, Receiver

Technology 40 Remaining Minimum S1AP SI Application

RAU Routing Area System 75 Protocol

Update Information SI -MME SI for the

RB Resource block, RN Relay Node control plane

Radio Bearer RNC Radio Network Sl-U SI for the user

RBG Resource block 45 Controller plane group RNL Radio Network 80 S-GW Serving Gateway

REG Resource Element Layer S-RNTI SRNC

Group RNTI Radio Network Radio Network

Rel Release Temporary Identifier Temporary

REQ REQuest 50 ROHC RObust Header Identity

RF Radio Frequency Compression 85 S-TMSI SAE

RI Rank Indicator RRC Radio Resource Temporary Mobile

RIV Resource indicator Control, Radio Station Identifier value Resource Control SA Standalone

RL Radio Link 55 layer operation mode

RLC Radio Link RRM Radio Resource 90 SAE System

Control, Radio Management Architecture Evolution

Link Control layer RS Reference Signal SAP Service Access

RLC AM RLC RSRP Reference Signal Point

Acknowledged Mode 60 Received Power SAPD Service Access

RLC UM RLC RSRQ Reference Signal 95 Point Descriptor

Unacknowledged Mode Received Quality SAPI Service Access

RLF Radio Link RS SI Received Signal Point Identifier

Failure Strength Indicator SCC Secondary

RLM Radio Link 65 RSU Road Side Unit Component Carrier,

Monitoring RSTD Reference Signal 100 Secondary CC

RLM-RS Reference Time difference SCell Secondary Cell

Signal for RLM RTP Real Time SC-FDMA Single Carrier Frequency 35 Time Diversity, SFN Measurement Timing

Division Multiple and frame timing 70 Configuration

Access difference SN Secondary Node,

SCG Secondary Cell SFN System Frame Sequence Number

Group Number or SoC System on Chip

SCM Security Context 40 Single Frequency SON Self-Organizing Management Network 75 Network

SCS Subcarrier SgNB Secondary gNB SpCell Special Cell

Spacing SGSN Serving GPRS SP-CSI-RNTISemi-

SCTP Stream Control Support Node Persistent CSI RNTI

Transmission 45 S-GW Serving Gateway SPS Semi-Persistent

Protocol SI System 80 Scheduling

SDAP Service Data Information SQN Sequence number

Adaptation Protocol, SI-RNTI System SR Scheduling Service Data Adaptation Information RNTI Request Protocol layer 50 SIB System SRB Signalling Radio

SDL Supplementary Information Block 85 Bearer

Downlink SIM Subscriber SRS Sounding

SDNF Structured Data Identity Module Reference Signal

Storage Network SIP Session Initiated SS Synchronization

Function 55 Protocol Signal

SDP Session SiP System in 90 SSB SS Block

Description Protocol Package SSBRI SSB Resource

SDSF Structured Data SL Sidelink Indicator

Storage Function SLA Service Level SSC Session and

SDU Service Data Unit 60 Agreement Service Continuity

SEAF Security Anchor SM Session 95 SS-RSRP Function Management Synchronization

SeNB secondary eNB SMF Session Signal based Reference

SEPP Security Edge Management Function Signal Received

Protection Proxy 65 SMS Short Message Power

SFI Slot format Service 100 SS-RSRQ indication SMSF SMS Function Synchronization

SFTD Space-Frequency SMTC SSB-based Signal based Reference Signal Received 35 TCP Transmission Technical

Quality Communication 70 Standard

SS-SINR Protocol TTI Transmission

Synchronization TDD Time Division Time Interval Signal based Signal to Duplex Tx Transmission, Noise and Interference 40 TDM Time Division Transmitting,

Ratio Multiplexing 75 Transmitter

SSS Secondary TDMATime Division U-RNTI UTRAN

Synchronization Multiple Access Radio Network

Signal TE Terminal Temporary

SSSG Search Space Set 45 Equipment Identity Group TEID Tunnel End Point 80 UART Universal

SSSIF Search Space Set Identifier Asynchronous Indicator TFT Traffic Flow Receiver and

SST Slice/Service Template Transmitter

Types 50 TMSI Temporary UCI Uplink Control

SU-MIMO Single Mobile Subscriber 85 Information

User MIMO Identity UE User Equipment

SUL Supplementary TNL Transport UDM Unified Data

Uplink Network Layer Management

TA Timing Advance, 55 TPC Transmit Power UDP User Datagram Tracking Area Control 90 Protocol TAC Tracking Area TPMI Transmitted UDR Unified Data

Code Precoding Matrix Repository

TAG Timing Advance Indicator UDSF Unstructured Data

Group 60 TR Technical Report Storage Network

TAU Tracking Area TRP, TRxP 95 Function

Update Transmission UICC Universal

TB Transport Block Reception Point Integrated Circuit TBS Transport Block TRS Tracking Card Size 65 Reference Signal UL Uplink

TBD To Be Defined TRx Transceiver 100 UM Unacknowledged

TCI Transmission TS Technical Mode Configuration Indicator Specifications, UML Unified Modelling Language 35 V2X Vehicle-to- Network

UMTS Universal Mobile every thing 70 WPANWireless Personal

Telecommunicatio VIM Virtualized Area Network ns System Infrastructure Manager X2-C X2-Control plane

UP User Plane VL Virtual Link, X2-U X2-User plane

UPF User Plane 40 VLAN Virtual LAN, XML extensible

Function Virtual Local Area 75 Markup Language

URI Uniform Resource Network XRES EXpected user

Identifier VM Virtual Machine RESponse

URL Uniform Resource VNF Virtualized XOR exclusive OR

Locator 45 Network Function ZC Zadoff-Chu

URLLC UltraVNFFG VNF 80 ZP Zero Power

Reliable and Low Forwarding Graph

Latency VNFFGD VNF

USB Universal Serial Forwarding Graph

Bus 50 Descriptor

USIM Universal VNFMVNF Manager

Subscriber Identity VoIP Voice-over-IP,

Module Voice-over- Internet

USS UE-specific Protocol search space 55 VPLMN Visited

UTRA UMTS Terrestrial Public Land Mobile

Radio Access Network

UTRAN Universal VPN Virtual Private

Terrestrial Radio Network

Access Network 60 VRB Virtual Resource

UwPTS Uplink Block

Pilot Time Slot WiMAX Worldwide

V2I Vehicle-to- Interoperability for

Infrastruction Microwave Access

V2P Vehicle-to- 65 WLANWireless Local

Pedestrian Area Network

V2V Vehicle-to- WMAN Wireless

Vehicle Metropolitan Area VI. TERMINOLOGY

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “memory” and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory, ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data. The term “computer-readable medium” may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NF VI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “element” refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof. The term “device” refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity. The term “entity” refers to a distinct component of an architecture or device, or information transferred as a payload. The term “controller” refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.

The term “cloud computing” or “cloud” refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like). The term “computing resource” or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network. Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software/applications, computer files, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. As used herein, the term “cloud service provider” (or CSP) indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud). In other examples, a CSP may also be referred to as a Cloud Service Operator (CSO). References to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.

As used herein, the term “data center” refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems. The term may also refer to a compute and data storage node in some contexts. A data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).

As used herein, the term “edge computing” refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data privacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership). As used herein, the term “edge compute node” refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network. References to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub-system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting.

Additionally or alternatively, the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to- end latency and load on the transport network. As used herein, the term “Edge Computing Service Provider” refers to a mobile network operator or a 3rd party service provider offering Edge Computing service. As used herein, the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications. As used herein, the term “Edge Hosting Environment” refers to an environment providing support required for Edge Application Server's execution. As used herein, the term “Application Server” refers to application software resident in the cloud performing the server function.

The term “Internet of Things” or “loT” refers to a system of interrelated computing devices, mechanical and digital machines capable of transferring data with little or no human interaction, and may involve technologies such as real-time analytics, machine learning and/or Al, embedded systems, wireless sensor networks, control systems, automation (e.g., smarthome, smart building and/or smart city technologies), and the like. loT devices are usually low-power devices without heavy compute or storage capabilities. “Edge loT devices” may be any kind of loT devices deployed at a network’s edge.

As used herein, the term “cluster” refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e.g., applications, functions, security constructs, containers), and the like. In some locations, a “cluster” is also referred to as a “group” or a “domain”. The membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various example techniques discussed herein which may add, modify, or remove an entity in a cluster. Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. As used herein, the term “radio technology” refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer. The term “radio access technology” or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network. As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term “SSB” refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Synchronization Signal (SSS), and a PBCH.

The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA. The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMS What is claimed is:

1. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB) cause the gNB to: determine a physical beam index for a synchronization signal block (SSB) based on a randomization function to randomize the physical beam index; and encode the SSB for transmission based on the determined physical beam index.

2. The one or more NTCRM of claim 1, wherein the physical beam index is determined based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID) associated with the transmission of the SSB, or a generated sequence.

3. The one or more NTCRM of claim 2, wherein the physical beam index is determined based on the generated sequence, and wherein the instructions, when executed, are further to cause the gNB to generate the sequence using a Gold code sequence or a hashing function.

4. The one or more NTCRM of claim 3, wherein the generated sequence is initialized based on the cell ID.

5. The one or more NTCRM of claim 4, wherein the generated sequence is initialized further based on the SFN.

6. The one or more NTCRM of claim 3, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

7. The one or more NTCRM of claim 3, wherein the generated sequence has a maximum length of 4 bits.

8. The one or more NTCRM of claim 3, wherein the physical beam index is determined using (i + f(n)) mod Q, wherein i is the SSB index, and f(n) is the generated sequence.

9. The one or more NTCRM of any one of claims 1 to 8, wherein the sequence is a first sequence of a plurality of sequences used to determine respective physical beam indexes, and wherein, to determine the respective physical beam indexes, the gNB is to: obtain a base sequence; generate the plurality of sequences as respective overlapping or non-overlapping subsets of the base sequence; and generate the plurality of physical beam indexes based on the respective generated sequences and an initialization value.

10. The one or more NTCRM of claim 1, wherein the physical beam index is determined using (i+SFN+cell ID) mod Q, wherein i is the SSB index of the SSB, SFN is the SFN of a transmission instance of the SSB, and cell ID is a cell identity associated with the transmission of the SSB.

11. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE) cause the UE to: determine a physical beam index for a synchronization signal block (SSB) based on a randomization function to randomize the physical beam index; and receive the SSB based on the determined physical beam index.

12. The one or more NTCRM of claim 11, wherein the physical beam index is determined based on one or more of a system frame number (SFN) of the SSB, a cell identity (ID) associated with the transmission of the SSB, or a generated sequence.

13. The one or more NTCRM of claim 12, wherein the physical beam index is determined based on the generated sequence, and wherein the instructions, when executed, are further to cause the UE to generate the sequence using a Gold code sequence or a hashing function.

14. The one or more NTCRM of claim 13, wherein the generated sequence is initialized based on the cell ID.

15. The one or more NTCRM of claim 14, wherein the generated sequence is initialized further based on the SFN.

16. The one or more NTCRM of claim 13, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

17. The one or more NTCRM of claim 13, wherein the generated sequence has a maximum length of 4 bits.

18. The one or more NTCRM of claim 13, wherein the physical beam index is determined using (i + f(n)) mod Q, wherein i is the SSB index, and f(n) is the generated sequence.

19. The one or more NTCRM of any one of claims 11 to 18, wherein the sequence is a first sequence of a plurality of sequences used to determine respective physical beam indexes, and wherein, to determine the respective physical beam indexes, the UE is to: obtain a base sequence; generate the plurality of sequences as respective overlapping or non-overlapping subsets of the base sequence; and generate the plurality of physical beam indexes based on the respective generated sequences and an initialization value.

20. The one or more NTCRM of claim 11, wherein the physical beam index is determined using (i+SFN+cell ID) mod Q, wherein i is the SSB index of the SSB, SFN is the SFN of a transmission instance of the SSB, and cell ID is a cell identity associated with the transmission of the SSB.

21. An apparatus to be implemented in a next generation Node B (gNB), the apparatus comprising: a radio frequency (RF) interface; and processor circuitry coupled to the RF interface, the processor circuitry to: generate a sequence based on a Gold code sequence or a hashing function and an initialization value; determine a physical beam index for a synchronization signal block (SSB) based on the generated sequence; and encode the SSB for transmission via the RF interface based on the determined physical beam index.

22. The apparatus of claim 21, wherein the initialization value is based on a cell identity (ID) associated with the transmission of the SSB.

23. The apparatus of claim 21, wherein the Gold code sequence is a length 16 or length 31 Gold code sequence.

24. The apparatus of any of claims 21-23, wherein the generated sequence has a length of 4 bits or less.